Modifying Application Context Name

Top  Previous  Next

Descriptions

 

Service users are engaged with each other via a service-provider during a certain period of time. This common engagement is well known as association, or interaction. In ETSI, the term dialogue is used for this engagement.

 

Two service users engaged in a dialogue, interact with a service-provider for the transfer of their messages. The point at which an interaction takes place is called service access point (SAP) located at the boundary of the service-provider, and the exchange of messages at the SAPs is accomplished by the performance of service primitives (SPs).

 

The SPs of the common MAP service elements contain a parameter, called Application Context Name. The value of this parameter refers to an user-specific MAP service, e.g., handover control. It is used to indicate the purpose of a dialogue. Besides it could partly be used as an identifier for a certain dialogue, by which corresponding independent message flows (of parallel dialogues) can be distinguished. A version negotiation mechanism based on the use of an application-context-name is used to negotiate the protocol version used between two entities for supporting a MAP-user signalling procedure.

 

The ACN facility enables the version negotiation for the following messages, which makes the UltraWAVE system more compatible with the other networks by means of flexible message version adjustment.

 

hmtoggle_plus1Supported Messages

 

1.Network Location Update

 

2.Location Cancel

 

3.Roaming number enquiry

 

4.Location Info Retrieval

 

5.Reset Context

 

6.Handover Control

 

7.Equipment management

 

8.Info Retrieval

 

9.Inter VLR Info Retrieval

 

10.Subscriber Data Management

 

11.Tracing

 

12.Network Functional SS

 

13.Network Unstructured SS

 

14.Short Message Gateway

 

15.Short Message MO Relay

 

16.Short Message Alert

 

17.Short Message Waiting Data Management

 

18.Mobile Terminating Short Message Relay

 

19.IMSI Retrieval

 

20.MS purging

 

21.Subscriber Info Enquiry

 

22.Any Time Info Enquiry

 

23.Call Control Transfer

 

24.Invocation Notification

 

25.SIWFS Allocation

 

26.Group Call Control

 

27.GPRS Location Update

 

28.GPRS Location Info Retrieval

 

29.Failure Report

 

30.GPRS Notify

 

31.Reporting

 

32.Call Completion

 

33.Security Triplets

 

34.Subscriber Interrogate

 

35.HLR Subscriber Management

 

36.HLR Ping AUC

 

37.VLR Supported CAMEL Phases: Phase 1, Phases 1+2, Phases 1+2+3

 

 

 

Implementation

 

hmtoggle_arrow1Configure and Appoint ACN

 

1.Go to EMS >Configuration >NSS >SCCP.

 

2.Make sure the System ID at the upper right corner displays SCCP(MSS_pub), click the 2_035 button.

 

2_53_09

 

1.Click to open the Network tab.

 

2.Click the hyperlinked index number to open an existing ACN entry, or click New to create a new ACN entry.

 

3.Select version for supported messages, click highlight SAVE after change.

 

4.Click the 2_041 button to update parameters to application servers.

 

2_53_10

 

1.Click to open the GTT tab.

 

2.Click the hyperlinked index number to open the targeted GTT entry.

 

3.Enter the index number of the pre-configured ACN Version entry, click highlight SAVE after change.

 

4.Click the 2_041 button to update parameters to application servers.

 

 

 

Return to

 

Tasks List

 

Elements List

 

 

 

 

 

2.53