4.9 Location Services
29.0103GPPInformation element mapping between Mobile Station - Base Station System (MS - BSS) and Base Station System - Mobile-services Switching Centre (BSS - MSC)Release 17Signalling Procedures and the Mobile Application Part (MAP)TS
The general principles of the location services procedures are given in Technical Specification 3GPP TS 23.271 [16].
3GPP TS 29.010 gives the necessary information for interworking between the 3GPP TS 25.413 [7] RANAP protocol and the 3GPP TS 48.008 [12] BSSMAP protocol. The interworking is necessary for positioning requests issued after a completed GSM to UMTS inter system handover. BSSMAP messages carried by MAP over the E-interface must be mapped by the non-anchor 3G-MSC into the corresponding RANAP messages to be sent over the Iu-interface and vice versa. For Inter-MSC GSM to GSM Handover and Inter-MSC UMTS to UMTS SRNS Relocation no mapping between the 3GPP TS 25.413 [7] RANAP protocol and the 3GPP TS 48.008 [12] BSSMAP protocol is necessary, but only the interworking with the MAP protocol over the E-interface needs to be described.
4.9.1 Completed Location Acquisition
4.9.1.1 Inter-MSC Handover (GSM to GSM)
After a successful Inter-MSC handover, any positioning request received by the anchor MSC via the MAP message Provide Subscriber Location triggers the BSSMAP procedure Location Acquisition described in 3GPP TS 48.008 [12]. For handover this procedure is executed according to GSM 3GPP TS 49.008 [14] with the anchor MSC playing the role of the MSC and the non anchor MSC playing the role of the BSS.
The needed BSSMAP signalling is sent over the E-interface encapsulated in the MAP messages Process Access Signalling and Forward Access Signalling.
At the non anchor MSC the BSSMAP messages received from the anchor MSC are forwarded to the BSS, and the BSSMAP messages received from the BSS are sent over the E-interface to the anchor MSC.
The signalling for a completed Location Acquisition procedure is shown in figures 65a.
GMLC MSC-A MSC-B
| | |
|MAP PROVIDE | |
|SUBSCRIBER | |
|LOCATION | |
|————–>|MAP FORWARD ACCESS |
| | SIGNALLING |
| |————————>|
| | -an-APDU( |
| | PERFORM LOCATION |
| | REQUEST) |
| | |
| | | BSS-B
| | | | | | | |
| | |——————>|
| | | |
| | | PERFORM LOCATION |
| | | REQUEST |
| | | |
| | | |
| | | +———–+
| | | |Positioning|
| | | | is |
| | | | performed |
| | | +———–+
| | | |
| | | | | | | |
| | |<——————|
| | |
| | | PERFORM LOCATION
| | | RESPONSE
| | |
| | MAP PROCESS ACCESS |
| | SIGNALLING |
| |<————————|
| | -an-APDU( |
| | PERFORM LOCATION |
| | RESPONSE) |
|MAP PROVIDE | |
|SUBSCRIBER | |
|LOCATION res | |
|<————–| |
| | |
Figure 65a: Signalling for a completed Location Acquisition procedure
After the inter-MSC handover, the MSC-B can perform intra-MSC GSM to UMTS handover. Any positioning request received by the anchor MSC after completion of the intra-MSC GSM to UMTS handover is handled as for Inter-MSC Handover GSM to UMTS (see clause 4.9.1.2).
4.9.1.2 Inter-MSC Handover (GSM to UMTS)
After a successful Inter-MSC GSM to UMTS inter system handover, any positioning request received by the anchor MSC via the MAP message Provide Subscriber Location triggers the BSSMAP procedure Location Acquisition described in 3GPP TS 48.008 [12]. For handover this procedure is executed according to 3GPP TS 49.008 [14] with the anchor MSC playing the role of the MSC and the non anchor 3G MSC playing the role of the BSS.
The needed BSSMAP signalling is sent over the E-interface encapsulated in the MAP messages Process Access Signalling and Forward Access Signalling.
At the non anchor 3G MSC the BSSMAP messages received from the anchor MSC are mapped into the corresponding RANAP messages to be sent to the RNS, and the received RANAP messages are mapped into the corresponding BSSMAP messages to be sent over the E-interface to the anchor MSC.
The signalling for a completed Location Acquisition procedure is shown in figures 65b.
GMLC MSC-A 3G-MSC-B
| | |
|MAP PROVIDE | |
|SUBSCRIBER | |
|LOCATION | |
|————–>|MAP FORWARD ACCESS |
| | SIGNALLING |
| |————————>|
| | -an-APDU( |
| | PERFORM LOCATION |
| | REQUEST) |
| | |
| | | RNS-B
| | | |
| | |LOCATION REPORTING |
| | | CONTROL |
| | |——————>|
| | | |
| | | +———–+
| | | |Positioning|
| | | | is |
| | | | performed |
| | | +———–+
| | | |
| | |LOCATION REPORT |
| | |<——————|
| |MAP PROCESS ACCESS |
| | SIGNALLING |
| |<————————|
| | -an-APDU( |
| | PERFORM LOCATION |
| | RESPONSE) |
|MAP PROVIDE | |
|SUBSCRIBER | |
|LOCATION res | |
|<————–| |
| | |
Figure 65b: Signalling for a completed Location Acquisition procedure
The interworking between the BSSMAP location aquisition messages in MAP and the RANAP location reporting messages is as follows:
—————————————————————-
| 29.002 25.413 |Notes
——–┼————————————————-┼—–
Forward | MAP FORWARD ACCESS SIG. LOCATION REPORTING |
message | request CONTROL |
| |
| -an-APDU( |
| PERFORM LOCATION REQUEST) |
| |
| BSSMAP information RANAP information |
| elements: elements: |
| |
| Location Type Request Type | 1
| >Current Geographic >Event = Direct |
| Location >Report Area = |
| Geo. Coord. |
| |
| Cell Identifier —- |
| Classmark Inf. Type3 —- |
| LCS Client Type —- |
| Chosen Channel —- |
| LCS Priority —- |
| LCS QoS Request Type |
| >Horizontal Accuracy >Accuracy Code |
| |
| GPS Assistance Data —- |
| APDU —- |
| |
——–┼————————————————-┼—–
Result | MAP PROCESS ACCESS SIG. LOCATION REPORT |
| request |
| -an-APDU( |
| PERFORM LOCATION RESPONSE) |
| |
| BSSMAP information RANAP information |
| elements: elements: |
| |
| |
| Location Estimate Area Identity |
| >Geographical Area |
| Positioning Data —- |
| Deciphering Keys —- |
| LCS Cause Cause |
| —- Request Type |
| |
| |
NOTE 1: All other Location Type possibilities are not supported by UMTS positioning
After the inter-MSC GSM to UMTS handover, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. Any positioning request received by the anchor MSC after completion of the intra-MSC UMTS to GSM handover is handled as for Inter-MSC Handover GSM to GSM (see clause 4.9.1.1).
4.9.1.3 Inter-MSC Handover (UMTS to GSM)
After a successful Inter-MSC UMTS to GSM inter system handover, any positioning request received by the anchor 3G-MSC via the MAP message Provide Subscriber Location triggers the BSSMAP procedure Location Acquisition described in 3GPP TS 48.008 [12]. For handover this procedure is executed according to 3GPP TS 49.008 [14] with the anchor 3G-MSC playing the role of the 3G-MSC and the non anchor MSC playing the role of the BSS.
The needed BSSMAP signalling is sent over the E-interface encapsulated in the MAP messages Process Access Signalling and Forward Access Signalling.
At the non anchor MSC the BSSMAP messages received from the anchor 3G-MSC are forwarded to the BSS, and the BSSMAP messages received from the BSS are sent over the E-interface to the anchor 3G-MSC.
The signalling for a completed Location Acquisition procedure is shown in figures 65c.
GMLC 3G-MSC-A MSC-B
| | |
|MAP PROVIDE | |
|SUBSCRIBER | |
|LOCATION | |
|————–>|MAP FORWARD ACCESS |
| | SIGNALLING |
| |————————>|
| | -an-APDU( |
| | PERFORM LOCATION |
| | REQUEST) |
| | |
| | | BSS-B
| | | | | | | |
| | |——————>|
| | | |
| | | PERFORM LOCATION |
| | | REQUEST |
| | | |
| | | |
| | | +———–+
| | | |Positioning|
| | | | is |
| | | | performed |
| | | +———–+
| | | |
| | | | | | | |
| | |<——————|
| | |
| | | PERFORM LOCATION
| | | RESPONSE
| | |
| | MAP PROCESS ACCESS |
| | SIGNALLING |
| |<————————|
| | -an-APDU( |
| | PERFORM LOCATION |
| | RESPONSE) |
|MAP PROVIDE | |
|SUBSCRIBER | |
|LOCATION res | |
|<————–| |
| | |
Figure 65c: Signalling for a completed Location Acquisition procedure
After the inter-MSC UMTS to GSM handover, the 3G MSC-B can perform intra-MSC GSM to UMTS handover. Any positioning request received by the anchor 3G MSC after completion of the intra-MSC GSM to UMTS handover is handled as for Inter-MSC Handover GSM to UMTS (see clause 4.9.1.2).
4.9.1.4 Inter-MSC SRNS Relocation
After a successful Inter-MSC SRNS Relocation, any positioning request received by the anchor 3G-MSC via the MAP message Provide Subscriber Location triggers the RANAP procedure Location Reporting Control described in TS 25.413. For handover this procedure is executed according to 23.009 with the anchor 3G-MSC playing the role of the 3G-MSC and the non anchor 3G-MSC playing the role of the RNS.
The needed RANAP signalling is sent over the E-interface encapsulated in the MAP messages Process Access Signalling and Forward Access Signalling.
At the non anchor 3G-MSC the RANAP messages received from the anchor 3G-MSC are forwarded to the RNS, and the RANAPmessages received from the RNS are sent over the E-interface to the anchor 3G-MSC.
The signalling for a completed Location Acquisition procedure is shown in figures 65d.
GMLC 3G-MSC-A 3G-MSC-B
| | |
|MAP PROVIDE | |
|SUBSCRIBER | |
|LOCATION | |
|————–>|MAP FORWARD ACCESS |
| | SIGNALLING |
| |————————>|
| | -an-APDU( |
| | LOCATION REPORTING |
| | CONTROL) |
| | |
| | | RNS-B
| | | | | | | |
| | |——————>|
| | | |
| | |LOCATION REPORTING |
| | | CONTROL |
| | | |
| | | |
| | | +———–+
| | | |Positioning|
| | | | is |
| | | | performed |
| | | +———–+
| | | |
| | | | | | | |
| | |<——————|
| | |
| | |LOCATION REPORT
| | |
| | |
| | MAP PROCESS ACCESS |
| | SIGNALLING |
| |<————————|
| | -an-APDU( |
| | LOCATION REPORT) |
| | |
|MAP PROVIDE | |
|SUBSCRIBER | |
|LOCATION res | |
|<————–| |
| | |
Figure 65d: Signalling for a completed Location Acquisition procedure
After the inter-MSC SRNS Relocation, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. Any positioning request received by the anchor 3G MSC after completion of the intra-MSC UMTS to GSM requires that at the non anchor 3G MSC the received RANAP messages are mapped into the corresponding BSSMAP messages to be sent to the BSS, and the received BSSMAP messages are mapped into the corresponding RANAP messages to be sent over the E-interface to the anchor 3G-MSC.
The signalling for a completed Location Acquisition procedure is shown in figures 65e.
|
GMLC 3G-MSC-A 3G-MSC-B | | | |MAP PROVIDE | | |SUBSCRIBER | | |LOCATION | | |————–>|MAP FORWARD ACCESS | | | SIGNALLING | | |————————>| | | -an-APDU( | | | LOCATION REPORTING | | | CONTROL) | | | | | | | BSS-B | | | | | | | | | | |——————>| | | | | | | |PERFORM LOCATION | | | | REQUEST | | | | | | | | | | | | +———–+ | | | |Positioning| | | | | is | | | | | performed | | | | +———–+ | | | | | | | | | | | | | | |<——————| | | | | | |PERFORM LOCATION | | | RESPONSE | | | | | MAP PROCESS ACCESS | | | SIGNALLING | | |<————————| | | -an-APDU( | | | LOCATION REPORT) | | | | |MAP PROVIDE | | |SUBSCRIBER | | |LOCATION res | | |<————–| | | | | |
Figure 65e: Signalling for a completed Location Acquisition procedure
the interworking between the RANAP messages encapsulated in MAP and the BSSMAP messages is as follows:
|
—————————————————————- | 29.002 48.008 |Notes ——–┼————————————————-┼—– Forward | MAP FORWARD ACCESS SIG. PERFORM LOCATION | message | request REQUEST | | | | -an-APDU( | | LOCATION REPORTING CONTROL) | | | | RANAP information BSSMAP information | | elements: elements: | | | | Request Type Location Type | | >Event = Direct >Current Geographic | | >Report Area = Location | | Geo. Coord. | | | | Request Type LCS QoS | | >Accuracy Code >Horizontal Accuracy | | | ——–┼————————————————-┼—– Result | MAP PROCESS ACCESS SIG. PERFORM LOCATION | | request RESPONSE | | -an-APDU( | | LOCATION REPORT) | | | | RANAP information BSSMAP information | | elements: elements: | | | | Area Identity Location Estimate | | >Geographical Area | | | | Cause LCS Cause | | Request Type —- | | | |
4.9.2 Cause Code Mapping
4.9.2.1 Inter-MSC Handover (GSM to GSM)
When a mobile station is handed over from GSM to GSM, no mapping of cause codes is required. The MSC shall use the cause codes specified in 3GPP TS 48.008 [12].
After the inter-MSC handover, the MSC-B can perform intra-MSC GSM to UMTS handover. A mapping of the cause codes used in the RANAP and the BSSMAP protocols is needed after completion of the intra-MSC GSM to UMTS handover and is the same as for Inter-MSC Handover GSM to UMTS (see clause 4.9.2.2)..
4.9.2.2 Inter-MSC Handover (GSM to UMTS)
When a Mobile Station is handed over between GSM and UMTS, a mapping of the cause codes used in the RANAP and the BSSMAP protocols is needed. The mapping described here is applicable to the BSSMAP protocol even when used inside MAP in the E-interface.
The mapping between the cause codes received in RANAP Location Report and the LCS cause codes sent in BSSMAP Perform Location Response is as follows:
—————————————————————-
25.413 48.008 |Notes
——————————————————-┼——–
LOCATION REPORT PERFORM LOCATION RESPONSE |
|
– Requested Report Type – Position method failure|
not Supported |
– Requested Information – Position method failure|
not Available |
– all other cause codes – System Failure |
After the inter-MSC GSM to UMTS handover, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. No mapping of cause codes is required after completion of the intra-MSC UMTS to GSM handover as for Inter-MSC Handover GSM to GSM (see clause 4.9.2.1).
4.9.2.3 Inter-MSC Handover (UMTS to GSM)
When a mobile station is handed over from UMTS to GSM, no mapping of cause codes is required. The 3G-MSC shall use the cause codes specified in 3GPP TS 48.008 [12].
After the inter-MSC UMTS to GSM handover, the 3G MSC-B can perform intra-MSC GSM to UMTS handover. A mapping of the cause codes used in the RANAP and the BSSMAP protocols is needed after completion of the intra-MSC GSM to UMTS handover and is the same as for Inter-MSC Handover GSM to UMTS (see clause 4.9.2.2)…
4.9.2.4 Inter-MSC SRNS Relocation
When a mobile station is handed over from UMTS to UMTS, no mapping of cause codes is required. Both 3G-MSCs shall use the cause codes specified in TS 25.413.
After the inter-MSC SRNS Relocation, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. A mapping of the cause codes used in the RANAP and the BSSMAP protocols is needed after completion of the intra-MSC UMTS to GSM handover.
The mapping between the cause codes received in BSSMAP Perform Location Response and the LCS cause codes sent in RANAP Location Report is as follows:
|
—————————————————————- 48.008 25.413 |Notes ——————————————————-┼——– PERFORM LOCATION RESPONSE LOCATION REPORT | | – Position method failure – Requested Report Type | not Supported | – System Failure – Unspecified Failure | – Protocol Error – Unspecified Failure | – Data missing – Unspecified Failure | in position request | – Unexpected data value – Unspecified Failure | in position request | – Target MS Unreachable – Unspecified Failure | – Location request aborted – Unspecified Failure | – Facility not supported – Requested Report Type | not Supported | – Inter-BSC Handover Ongoing – Unspecified Failure | – Intra-BSC – Unspecified Failure | Handover Complete | – Congestion – Unspecified Failure | – Unspecified – Unspecified Failure | |
4.9.3 Aborted Location Acquisition
4.9.3.1 Inter-MSC Handover (GSM to GSM)
When for any reason the on going location acquisition procedure needs to be aborted, the anchor MSC sends the BSSMAP message Perform Location Abort over the E-interface.
Figure 66a shows the signalling for an aborted Location Acquisition procedure.
GMLC MSC-A MSC-B
| | |
|MAP PROVIDE | |
|SUBSCRIBER | |
|LOCATION | |
|————–>|MAP FORWARD ACCESS |
| | SIGNALLING |
| |————————>|
| | -an-APDU( |
| | PERFORM LOCATION |
| | REQUEST) |
| | |
| | | BSS-B
| | | |
| | | |
| | | |
| | |——————–>|
| | | |
| | | PERFORM LOCATION |
| | | REQUEST)|
| | | |
| | | |
| |MAP FORWARD ACCESS | |
| | SIGNALLING | |
| |————————>| |
| | -an-APDU( | |
| | PERFORM LOCATION ABORT)| |
| | | |
| | | |
| | | |
| | | |
| | |——————–>|
| | | |
| | | PERFORM LOCATION |
| | | ABORT | | | | |
| | |<——————–| | | | |
| | | PERFORM LOCATION |
| | | RESPONSE | | | | |
| | | |
| | | |
| |MAP PROCESS ACCESS | |
| | SIGNALLING | |
| |<————————| |
| | -an-APDU( | |
| | PERFORM LOCATION | |
| | RESPONSE) | |
Figure 66a: Signalling for an aborted Location Acquisition procedure
After the inter-MSC handover, the MSC-B can perform intra-MSC GSM to UMTS handover. A positioning request that needs to be aborted by the anchor MSC after completion of the intra-MSC GSM to UMTS handover is handled as for Inter-MSC Handover GSM to UMTS (see clause 4.9.3.2).
4.9.3.2 Inter-MSC Handover (GSM to UMTS)
When for any reason the on going location acquisition procedure needs to be aborted, the anchor MSC sends the BSSMAP message Perform Location Abort over the E-interface.
Figure 66b shows the signalling for an aborted Location Acquisition procedure.
GMLC MSC-A 3G-MSC-B
| | |
|MAP PROVIDE | |
|SUBSCRIBER | |
|LOCATION | |
|————–>|MAP FORWARD ACCESS |
| | SIGNALLING |
| |————————>|
| | -an-APDU( |
| | PERFORM LOCATION |
| | REQUEST) |
| | |
| | | RNS-B
| | | |
| | |LOCATION REPORTING |
| | | CONTROL |
| | |——————>|
| | | |
| | | |
| |MAP FORWARD ACCESS | |
| | SIGNALLING | |
| |————————>| |
| | -an-APDU( | |
| | PERFORM LOCATION ABORT)| |
| | | |
| | | |
| | |LOCATION REPORTING |
| | | CONTROL |
| | |——————>|
| | | |
| | | |
| | |LOCATION REPORT |
| | | |
| | |<——————|
| | | |
| | | |
| | | |
| |MAP PROCESS ACCESS | |
| | SIGNALLING | |
| |<————————| |
| | -an-APDU( | |
| | PERFORM LOCATION | |
| | RESPONSE) | |
Figure 66b: Signalling for an aborted Location Acquisition procedure
The interworking between the BSSMAP location aquisition messages in MAP and the RANAP location reporting messages is as follows:
—————————————————————-
| 29.002 25.413 |Notes
——–┼————————————————-┼—–
Forward | MAP FORWARD ACCESS SIG. LOCATION REPORTING |
message | request CONTROL |
| |
| -an-APDU( |
| PERFORM LOCATION ABORT) |
| |
| BSSMAP information RANAP information |
| elements: elements: |
| |
| LCS Cause Request Type |
| >Event = Stop |
| >Report Area = |
| Geo. Coord. |
| |
| |
——–┼————————————————-┼—–
Result | MAP PROCESS ACCESS SIG. LOCATION REPORT |
| request | 1
| -an-APDU( |
| PERFORM LOCATION RESPONSE) |
| |
| BSSMAP information RANAP information |
| elements: elements: |
| |
| —- |
| LCS Cause Cause |
| —- |
| |
NOTE 1: PERFORM LOCATION RESPONSE with LCS cause shall be generated by 3G-MSC-B.
After the inter-MSC GSM to UMTS handover, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. A positioning request that needs to be aborted by the anchor MSC after completion of the intra-MSC UMTS to GSM handover is handled as for Inter-MSC Handover GSM to GSM (see clause 4.9.3.1).
4.9.3.3 Inter-MSC Handover (UMTS to GSM)
When for any reason the on going location acquisition procedure needs to be aborted, the anchor 3G-MSC sends the BSSMAP message Perform Location Abort over the E-interface.
Figure 66c shows the signalling for an aborted Location Acquisition procedure.
GMLC 3G-MSC-A MSC-B
| | |
|MAP PROVIDE | |
|SUBSCRIBER | |
|LOCATION | |
|————–>|MAP FORWARD ACCESS |
| | SIGNALLING |
| |————————>|
| | -an-APDU( |
| | PERFORM LOCATION |
| | REQUEST) |
| | |
| | | BSS-B
| | | |
| | | |
| | | |
| | |——————–>|
| | | |
| | | PERFORM LOCATION |
| | | REQUEST)|
| | | |
| | | |
| |MAP FORWARD ACCESS | |
| | SIGNALLING | |
| |————————>| |
| | -an-APDU( | |
| | PERFORM LOCATION ABORT)| |
| | | |
| | | |
| | | |
| | | |
| | |——————–>|
| | | |
| | | PERFORM LOCATION |
| | | ABORT |
| | | |
| | |<——————–|
| | | PERFORM LOCATION |
| | | RESPONSE | | | | |
| |MAP PROCESS ACCESS | |
| | SIGNALLING | |
| |<————————| |
| | -an-APDU( | |
| | PERFORM LOCATION | |
| | RESPONSE) | |
Figure 66c: Signalling for an aborted Location Acquisition procedure
After the inter-MSC UMTS to GSM handover, the 3G MSC-B can perform intra-MSC GSM to UMTS handover. A positioning request that needs to be aborted by the anchor 3G MSC after completion of the intra-MSC GSM to UMTS handover is handled as for Inter-MSC Handover GSM to UMTS (see clause 4.9.3.2)..
4.9.3.4 Inter-MSC SRNS Relocation
When for any reason the on going location acquisition procedure needs to be aborted, the anchor 3G-MSC sends the RANAP message Location Reporting Control over the E-interface.
Figure 66d shows the signalling for an aborted Location Acquisition procedure.
GMLC 3G-MSC-A 3G-MSC-B
| | |
|MAP PROVIDE | |
|SUBSCRIBER | |
|LOCATION | |
|————–>|MAP FORWARD ACCESS |
| | SIGNALLING |
| |————————>|
| | -an-APDU( |
| | LOCATION REPORTING |
| | CONTROL) |
| | |
| | | RNS-B
| | | |
| | | |
| | | |
| | |——————–>|
| | | |
| | | LOCATION REPORTING |
| | | CONTROL |
| | | |
| | | |
| |MAP FORWARD ACCESS | |
| | SIGNALLING | |
| |————————>| |
| | -an-APDU( | |
| | LOCATION REPORTING | |
| | CONTROL = STOP) | |
| | | |
| | | |
| | | |
| | |——————–>|
| | | |
| | | LOCATION REPORTING |
| | | CONTROL = | | | | STOP DIRECT |
| | | |
| | |<——————–|
| | | |
| | | LOCATION REPORT |
| | | |
| |MAP PROCESS ACCESS | |
| | SIGNALLING | |
| |<————————| |
| | -an-APDU( | |
| | LOCATION REPORT) | |
| | | |
Figure 66d: Signalling for an aborted Location Acquisition procedure
After the inter-MSC SRNS Relocation, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. A positioning request that needs to be aborted by the anchor 3G MSC after completion of the intra-MSC UMTS to GSM requires that at the non anchor 3G MSC the received RANAP messages are mapped into the corresponding BSSMAP messages to be sent to the BSS, and the received BSSMAP messages are mapped into the corresponding RANAP messages to be sent over the E-interface to the anchor 3G-MSC.
The signalling for a completed Location Acquisition procedure is shown in figures 65e.
|
GMLC 3G-MSC-A 3G-MSC-B | | | |MAP PROVIDE | | |SUBSCRIBER | | |LOCATION | | |————–>|MAP FORWARD ACCESS | | | SIGNALLING | | |————————>| | | -an-APDU( | | | LOCATION REPORTING | | | CONTROL) | | | | | | | BSS-B | | | | | | | | | | |——————>| | | | | | | |PERFORM LOCATION | | | | ABORT | | | | | | | | | | | | | | | |<——————| | | | | | | |PERFORM LOCATION | | | | RESPONSE | | | | | | MAP PROCESS ACCESS | | | SIGNALLING | | |<————————| | | -an-APDU( | | | LOCATION REPORT) | | | | |MAP PROVIDE | | |SUBSCRIBER | | |LOCATION res | | |<————–| | | | | |
Figure 65e: Signalling for an aborted Location Acquisition procedure
the interworking between the RANAP messages encapsulated in MAP and the BSSMAP messages is as follows:
|
—————————————————————- | 29.002 48.008 |Notes ——–┼————————————————-┼—– Forward | MAP FORWARD ACCESS SIG. PERFORM LOCATION | message | request ABORT | | | | -an-APDU( | | LOCATION REPORTING CONTROL) | | | | RANAP information BSSMAP information | | elements: elements: | | | | Request Type LCS Cause | | >Event = Stop Direct > Location request | | >Report Area = aborted | | Geo. Coord. | | | ——–┼————————————————-┼—– Result | MAP PROCESS ACCESS SIG. PERFORM LOCATION | | request RESPONSE | | -an-APDU( | | LOCATION REPORT) | | | | RANAP information BSSMAP information | | elements: elements: | | | | Cause LCS Cause | | >Unspecified > Location request | | Failure aborted | | | |
4.9.4 Request of Assistance Data or De-ciphering Keys: Successful Case
4.9.4.1 Inter-MSC Handover (GSM to GSM)
After a successful Inter-MSC handover, any request of Assistance Data or De-ciphering keys received by the non anchor MSC via the DTAP message LCS-MOLR is forwarded to the anchor MSC by encapsulating the DTAP message into the MAP messages Process Access Signalling. The anchor MSC triggers the BSSMAP procedure Location Acquisition described in 3G TS 48.008. For handover this procedure is executed according to 3G TS 49.008 with the anchor MSC playing the role of the MSC and the non anchor MSC playing the role of the BSS.
The needed BSSMAP signalling is sent over the E-interface encapsulated in the MAP messages Process Access Signalling and Forward Access Signalling.
At the non anchor MSC the BSSMAP messages received from the anchor MSC are forwarded to the BSS, and the BSSMAP messages received from the BSS are sent over the E-interface to the anchor MSC.
Once the BSSMAP procedure has been completed, the anchor MSC sends the DTAP message LCS-MOLR Response encapsulated in the MAP message Forward Access Signalling to the non anchor MSC, which relays it to the MS.
The signalling for a completed request of Assistance Data or De-ciphering Keys is shown in figures 67a.
MSC-A MSC-B MS
| | |
| | |
| | |
| | LCS-MOLR |
| |<————————————–|
| | |
| | |
|MAP PROCESS ACCESS | |
| SIGNALLING | |
|<——————–| |
| -an-APDU(LCS-MOLR) | |
| | |
| | |
|MAP FORWARD ACCESS | |
| SIGNALLING | |
|——————–>| |
| -an-APDU( | |
| PERFORM LOCATION | |
| REQUEST) | BSS-B |
| | |
| | | |
| |—————–>| |
| | | |
| | PERFORM LOCATION | |
| | REQUEST | |
| | | |
| | +————————+
| | | If Assistance Data were|
| | | requested then |
| | | Delivery of Assistance |
| | | Data to MS |
| | +————————+
| | | |
| |<—————–| |
| | | |
| | PERFORM LOCATION | |
| | RESPONSE | |
| | | |
| | | |
| | | |
|MAP PROCESS ACCESS | | |
| SIGNALLING | | |
|<——————–| | |
| -an-APDU( | | |
| PERFORM LOCATION | | |
| RESPONSE) | | |
| | | |
| | | |
|MAP FORWARD ACCESS | | |
| SIGNALLING | -+- |
|——————–>| |
| -an-APDU( | |
| LCS-MOLR Response) | |
| | |
| | LCS-MOLR Response |
| |————————————–>|
| | |
Figure 67a: Signalling for the request of Assistance Data or De-ciphering Keys
After the inter-MSC handover, the MSC-B can perform intra-MSC GSM to UMTS handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC GSM to UMTS handover is handled as for Inter-MSC Handover GSM to UMTS (see clause 4.9.4.2).
4.9.4.2 Inter-MSC Handover (GSM to UMTS)
After a successful Inter-MSC GSM to UMTS inter system handover, any request of Assistance Data or De-ciphering keys received by the non-anchor 3G MSC via the DTAP message LCS-MOLR is forwarded to the anchor MSC by encapsulating the DTAP message into the MAP messages Process Access Signalling. The anchor MSC triggers the BSSMAP procedure Location Acquisition described in 3G TS 48.008. For handover this procedure is executed according to 3G TS 49.008 with the anchor MSC playing the role of the MSC and the non anchor 3G MSC playing the role of the BSS.
The needed BSSMAP signalling is sent over the E-interface encapsulated in the MAP messages Process Access Signalling and Forward Access Signalling.
At the non-anchor 3G MSC the received BSSMAP messages are mapped into the corresponding RANAP messages to be sent to the RNS, and the received RANAP messages are mapped into the corresponding BSSMAP messages to be sent over the E-interface to the anchor MSC.
Once the BSSMAP procedure has been completed, the anchor MSC sends the DTAP message LCS-MOLR Response encapsulated in the MAP message Forward Access Signalling to the non anchor 3G MSC, which relays it to the UE.
The signalling for a completed request of Assistance Data or De-ciphering Keys is shown in figures 67b.
MSC-A 3G MSC-B UE
| | |
| | |
| | |
| | LCS-MOLR |
| |<————————————–|
| | |
| | |
|MAP PROCESS ACCESS | |
| SIGNALLING | |
|<——————–| |
| -an-APDU(LCS-MOLR) | |
| | |
| | |
|MAP FORWARD ACCESS | |
| SIGNALLING | |
|——————–>| |
| -an-APDU( | |
| PERFORM LOCATION | |
| REQUEST) | RNS-B |
| | |
| | | |
| |—————–>| |
| | | |
| |LOCATION RELATED | |
| | DATA REQUEST | |
| | | |
| | +————————+
| | | If Assistance Data were|
| | | requested then |
| | | Delivery of Assistance |
| | | Data to UE |
| | +————————+
| | | |
| |<—————–| |
| | | |
| |LOCATION RELATED | |
| | DATA RESPONSE | |
| | | |
| | | |
| | | |
|MAP PROCESS ACCESS | | |
| SIGNALLING | | |
|<——————–| | |
| -an-APDU( | | |
| PERFORM LOCATION | | |
| RESPONSE) | | |
| | | |
| | | |
|MAP FORWARD ACCESS | | |
| SIGNALLING | -+- |
|——————–>| |
| -an-APDU( | |
| LCS-MOLR Response) | |
| | |
| | LCS-MOLR Response |
| |————————————–>|
| | |
Figure 67b: Signalling for the request of Assistance Data or De-ciphering Keys
When the UE requires the delivery of Assistance Data for the GPS Assisted positioning method, the interworking between the BSSMAP messages encapsulated in MAP and the RANAP messages is as follows:
—————————————————————–
| 29.002 25.413 |Notes
——–┼————————————————–┼—–
Forward | MAP FORWARD ACCESS SIG. LOCATION RELATED |
message | request DATA REQUEST |
| |
| -an-APDU( |
| PERFORM LOCATION REQUEST) |
| |
| BSSMAP information RANAP information |
| elements: elements: |
| |
| Location Type. Requested Location |
| Location.Information Related Data Type |
| > location assistance >Dedicated Assistance |
| info for target MS Data for Assisted GPS|
| Location Type. |
| Positioning Method | 1
| > Assisted GPS |
| |
| |
| GPS Assistance Data Requested GPS |
| Assistance Data |
| |
——–┼————————————————–┼—–
Result | MAP PROCESS ACCESS SIG. LOCATION RELATED |
| request DATA RESPONSE |
| -an-APDU( |
| PERFORM LOCATION RESPONSE) |
| |
| BSSMAP information RANAP information | 2
| elements: elements: |
| |
| |
| |
| |
NOTE 1: All other Positioning Method possibilities are not supported by UMTS when Location Information is "location assistance information for the target MS".
NOTE 2: The absence of the Cause IE in the RANAP message Location Related Data Response is an indication that the requested assistance data has been successfully delivered to the UE..
If the UE requires the delivery of Assistance Data for an UMTS specific method, then the anchor MSC cannot forward the request to the non anchor 3G MSC, and replies with the error "System"to the LCS-MOLR message.
If the anchor MSC sends a request for assistance data for a GSM specific method in BSSMAP Perform Location Request encapsulated in MAP Forward Access Signalling, then the non anchor 3G MSC replies immediately by generating and encapsulating BSSMAP Perform Location Response with Cause "System Failure" in MAP Process Access Signalling. This traffic case can happen if an LCS-MOLR had been received in the anchor MSC before the initiation of the handover procedure.
When the UE requires the delivery of De-ciphering Keys for the GPS Assisted positioning method, the interworking between the BSSMAP messages encapsulated in MAP and the RANAP messages is as follows:
—————————————————————–
| 29.002 25.413 |Notes
——–┼————————————————–┼—–
Forward | MAP FORWARD ACCESS SIG. LOCATION RELATED |
message | request DATA REQUEST |
| |
| -an-APDU( |
| PERFORM LOCATION REQUEST) |
| |
| BSSMAP information RANAP information |
| elements: elements: |
| |
| Location Type. Requested Location |
| Location.Information Related Data Type |
| > deciphering keys > Deciphering Keys |
| for broadcast for Assisted GPS |
| assistance data |
| for the target MS |
| Location Type. |
| Positioning Method | 1
| > Assisted GPS |
| |
| |
——–┼————————————————–┼—–
Result | MAP PROCESS ACCESS SIG. LOCATION RELATED |
| request DATA RESPONSE |
| -an-APDU( |
| PERFORM LOCATION RESPONSE) |
| |
| BSSMAP information RANAP information |
| elements: elements: |
| |
| Deciphering Keys Broadcast Assistance |
| Data Deciphering Keys|
| |
| |
| |
NOTE 1: All other Positioning Method possibilities are not supported by UMTS when Location Information is "deciphering keys for broadcast assistance data for the target MS".
If the UE requires the delivery of De-ciphering Keys for an UMTS specific method, then the anchor MSC cannot forward the request to the non anchor 3G MSC, and replies with the error "System"to the LCS-MOLR message.
If the anchor MSC sends a request for De-ciphering Keys for a GSM specific method in BSSMAP Perform Location Request encapsulated in MAP Forward Access Signalling, then the non anchor 3G MSC replies immediately by generating and encapsulating BSSMAP Perform Location Response with Cause "System Failure" in MAP Process Access Signalling. This traffic case can happen if an LCS-MOLR had been received in the anchor MSC before the initiation of the handover procedure.
After the inter-MSC GSM to UMTS handover, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC UMTS to GSM handover is handled as for Inter-MSC Handover GSM to GSM (see clause 4.9.4.1).
4.9.4.3 Inter-MSC Handover (UMTS to GSM)
After a successful Inter-MSC UMTS to GSM inter system handover, any request of Assistance Data or De-ciphering keys received by the non-anchor MSC via the DTAP message LCS-MOLR is forwarded to the anchor 3G MSC by encapsulating the DTAP message into the MAP messages Process Access Signalling. The anchor 3G MSC triggers the BSSMAP procedure Location Acquisition described in 3G TS 48.008. For handover this procedure is executed according to 3G TS 49.008 with the anchor 3G MSC playing the role of the MSC and the non-anchor MSC playing the role of the BSS.
The needed BSSMAP signalling is sent over the E-interface encapsulated in the MAP messages Process Access Signalling and Forward Access Signalling.
At the non-anchor MSC the BSSMAP messages received from the anchor 3G MSC are forwarded to the BSS, and the BSSMAP messages received from the BSS are sent over the E-interface to the anchor 3G MSC.
Once the BSSMAP procedure has been completed, the anchor 3G MSC sends the DTAP message LCS-MOLR Response encapsulated in the MAP message Forward Access Signalling to the non-anchor MSC, which relays it to the UE.
The signalling for a completed request of Assistance Data or De-ciphering Keys is shown in figures 67c.
3G MSC-A MSC-B MS
| | |
| | |
| | |
| | LCS-MOLR |
| |<————————————–|
| | |
| | |
|MAP PROCESS ACCESS | |
| SIGNALLING | |
|<——————–| |
| -an-APDU(LCS-MOLR) | |
| | |
| | |
|MAP FORWARD ACCESS | |
| SIGNALLING | |
|——————–>| |
| -an-APDU( | |
| PERFORM LOCATION | |
| REQUEST) | BSS-B |
| | |
| | | |
| |—————–>| |
| | | |
| | PERFORM LOCATION | |
| | REQUEST | |
| | | |
| | +————————+
| | | If Assistance Data were|
| | | requested then |
| | | Delivery of Assistance |
| | | Data to MS |
| | +————————+
| | | |
| |<—————–| |
| | | |
| | PERFORM LOCATION | |
| | RESPONSE | |
| | | |
| | | |
| | | |
|MAP PROCESS ACCESS | | |
| SIGNALLING | | |
|<——————–| | |
| -an-APDU( | | |
| PERFORM LOCATION | | |
| RESPONSE) | | |
| | | |
| | | |
|MAP FORWARD ACCESS | | |
| SIGNALLING | -+- |
|——————–>| |
| -an-APDU( | |
| LCS-MOLR Response) | |
| | |
| | LCS-MOLR Response |
| |————————————–>|
| | |
Figure 67c: Signalling for the request of Assistance Data or De-ciphering Keys
After the inter-MSC UMTS to GSM handover, the 3G MSC-B can perform intra-MSC GSM to UMTS handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC GSM to UMTS handover is handled as for Inter-MSC Handover GSM to UMTS (see clause 4.9.4.2)..
4.9.4.4 Inter-MSC SRNS Relocation
After a successful Inter-MSC SRNS Relocation , any request of Assistance Data or De-ciphering keys received by the non anchor 3G MSC via the DTAP message LCS-MOLR is forwarded to the anchor 3G MSC by encapsulating the DTAP message into the MAP messages Process Access Signalling. The anchor 3G MSC triggers the RANAP procedure Location Related Data described in TS 25.413. For handover this procedure is executed according to 23.009 with the anchor 3G-MSC playing the role of the 3G-MSC and the non anchor 3G-MSC playing the role of the RNS.
The needed RANAP signalling is sent over the E-interface encapsulated in the MAP messages Process Access Signalling and Forward Access Signalling.
At the non anchor 3G MSC the RANAP messages received from the anchor 3G MSC are forwarded to the RNS, and the RANAP messages received from the RNS are sent over the E-interface to the anchor 3G MSC.
Once the RANAP procedure has been completed, the anchor 3G MSC sends the DTAP message LCS-MOLR Response encapsulated in the MAP message Forward Access Signalling to the non anchor 3G MSC, which relays it to the UE.
The signalling for a completed request of Assistance Data or De-ciphering Keys is shown in figures 67d.
3G MSC-A 3G MSC-B UE
| | |
| | |
| | |
| | LCS-MOLR |
| |<————————————–|
| | |
| | |
|MAP PROCESS ACCESS | |
| SIGNALLING | |
|<——————–| |
| -an-APDU(LCS-MOLR) | |
| | |
| | |
|MAP FORWARD ACCESS | |
| SIGNALLING | |
|——————–>| |
| -an-APDU( | |
| LOCATION RELATED | |
| DATA REQUEST) | RNS-B |
| | |
| | | |
| |—————–>| |
| | | |
| | LOCATION RELATED | |
| | DATA REQUEST | |
| | | |
| | +————————+
| | | If Assistance Data were|
| | | requested then |
| | | Delivery of Assistance |
| | | Data to UE |
| | +————————+
| | | |
| |<—————–| |
| | | |
| | LOCATION RELATED | |
| | DATA RESPONSE | |
| | | |
| | | |
| | | |
|MAP PROCESS ACCESS | | |
| SIGNALLING | | |
|<——————–| | |
| -an-APDU( | | |
| LOCATION RELATED | | |
| DATA RESPONSE) | | |
| | | |
| | | |
|MAP FORWARD ACCESS | | |
| SIGNALLING | -+- |
|——————–>| |
| -an-APDU( | |
| LCS-MOLR Response) | |
| | |
| | LCS-MOLR Response |
| |————————————–>|
| | |
Figure 67d: Signalling for the request of Assistance Data or De-ciphering Keys
After the inter-MSC SRNS Relocation, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC UMTS to GSM requires that at the non anchor 3G MSC the received RANAP messages are mapped into the corresponding BSSMAP messages to be sent to the BSS, and the received BSSMAP messages are mapped into the corresponding RANAP messages to be sent over the E-interface to the anchor 3G-MSC. The signalling for a completed request of Assistance Data or De-ciphering Keys in this traffic case is shown in figures 67e.
3G MSC-A 3G MSC-B UE
| | |
| | |
| | |
| | LCS-MOLR |
| |<————————————–|
| | |
| | |
|MAP PROCESS ACCESS | |
| SIGNALLING | |
|<——————–| |
| -an-APDU(LCS-MOLR) | |
| | |
| | |
|MAP FORWARD ACCESS | |
| SIGNALLING | |
|——————–>| |
| -an-APDU( | |
| LOCATION RELATED | |
| DATA REQUEST) | BSS-B |
| | |
| | | |
| |—————–>| |
| | | |
| | PERFORM LOCATION | |
| | REQUEST | |
| | | |
| | +————————+
| | | If Assistance Data were|
| | | requested then |
| | | Delivery of Assistance |
| | | Data to MS |
| | +————————+
| | | |
| |<—————–| |
| | | |
| | PERFORM LOCATION | |
| | RESPONSE | |
| | | |
| | | |
| | | |
|MAP PROCESS ACCESS | | |
| SIGNALLING | | |
|<——————–| | |
| -an-APDU( | | |
| LOCATION RELATED | | |
| DATA RESPONSE) | | |
| | | |
| | | |
|MAP FORWARD ACCESS | | |
| SIGNALLING | -+- |
|——————–>| |
| -an-APDU( | |
| LCS-MOLR Response) | |
| | |
| | LCS-MOLR Response |
| |————————————–>|
| | |
Figure 67e: Signalling for the request of Assistance Data or De-ciphering Keys
When the UE requires the delivery of Assistance Data for the GPS Assisted positioning method, the interworking between the RANAP messages encapsulated in MAP and the BSSMAP messages is as follows:
—————————————————————–
| 29.002 48.008 |Notes
——–┼————————————————–┼—–
Forward | MAP FORWARD ACCESS SIG. PERFORM LOCATION |
message | request REQUEST |
| |
| -an-APDU( |
| LOCATION RELATED |
| DATA REQUEST) |
| |
| RANAP information BSSMAP information |
| elements: elements: |
| |
| Requested Location Location Type. |
| Related Data Type Location Information |
| > Dedicated Assistance > location assistance | 1
| Data for Assisted info for target MS |
| GPS Location Type. |
| Positioning Method |
| > Assisted GPS |
| |
| Requested GPS GPS Assistance Data |
| Assistance Data |
| |
| |
——–┼————————————————–┼—–
Result | MAP PROCESS ACCESS SIG. PERFORM LOCATION |
| request RESPONSE |
| -an-APDU( |
| LOCATION RELATED |
| DATA RESPONSE) |
| |
| RANAP information BSSMAP information | 2
| elements: elements: |
| |
| |
| |
| |
NOTE 1: All other Positioning Method possibilities are not supported by GSM when Location Information is "deciphering keys for broadcast assistance data for the target MS".
NOTE 2: The absence of the Cause IE in the BSSMAP message Perform Location Response is an indicatioin that the requested assistance data has been successfully delivered to the UE..
If the UE requires the delivery of Assistance Data for a GSM specific method, then the anchor 3G-MSC cannot forward the request to the non anchor 3G MSC, and replies with the error "System"to the LCS-MOLR message.
If the anchor 3G MSC sends a request for Assistance Data for an UMTS specific method in RANAP Location Related Data Request encapsulated in MAP Forward Access Signalling, then the non anchor 3G MSC replies immediately by generating and encapsulating RANAP Location Related Data Failure with Cause "Unspecified Failure" in MAP Process Access Signalling. This traffic case can happen if an LCS-MOLR had been received in the anchor MSC before the initiation of the intra-MSC handover procedure.
When the UE requires the delivery of De-ciphering Keys for the GPS Assisted positioning method, the interworking between the RANAP messages encapsulated in MAP and the BSSMAP messages is as follows:
—————————————————————–
| 29.002 48.008 |Notes
——–┼————————————————–┼—–
Forward | MAP FORWARD ACCESS SIG. PERFORM LOCATION |
message | request REQUEST |
| |
| -an-APDU( |
| LOCATION RELATED |
| DATA REQUEST) |
| |
| RANAP information BSSMAP information |
| elements: elements: |
| |
| Requested Location Location Type. |
| Related Data Type Location Information |
| > Deciphering Keys > deciphering keys | 1
| for Assisted GPS for broadcast |
| assistance data |
| for the target MS |
| Location Type. |
| Positioning Method |
| > Assisted GPS |
| |
| |
——–┼————————————————–┼—–
Result | MAP PROCESS ACCESS SIG. PERFORM LOCATION |
| request RESPONSE |
| -an-APDU( |
| LOCATION RELATED |
| DATA RESPONSE) |
| |
| RANAP information BSSMAP information |
| elements: elements: |
| |
| Broadcast Assistance Deciphering Keys |
| Data Deciphering Keys |
| |
| |
| |
NOTE 1: All other Positioning Method possibilities are not supported by GSM when Location Information is "deciphering keys for broadcast assistance data for the target MS".
If the UE requires the delivery of De-ciphering Keys for a GSM specific method, then the anchor 3G-MSC cannot forward the request to the non anchor 3G MSC, and replies with the error "System"to the LCS-MOLR message.
If the anchor 3G MSC sends a request for De-ciphering Keys for an UMTS specific method in RANAP Location Related Data Request encapsulated in MAP Forward Access Signalling, then the non anchor 3G MSC replies immediately by generating and encapsulating RANAP Location Related Data Failure with Cause "Unspecified Failure" in MAP Process Access Signalling. This traffic case can happen if an LCS-MOLR had been received in the anchor MSC before the initiation of the intra-MSC handover procedure.
4.9.5 Request of Assistance Data or De-ciphering Keys: Failure Case
4.9.5.1 Inter-MSC Handover (GSM to GSM)
After a successful Inter-MSC handover, any request of Assistance Data or De-ciphering keys received by the non anchor MSC via the DTAP message LCS-MOLR is handled as described in clause 4.9.4.1.
If the request fails, either because the BSS-B cannot return the requested De-ciphering Keys to the anchor MSC or cannot deliver the required Assistance Data to the MS, the signalling is the same as for the successful case and is shown in figure 67a.
After the inter-MSC handover, the MSC-B can perform intra-MSC GSM to UMTS handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC GSM to UMTS handover is handled as for Inter-MSC Handover GSM to UMTS (see clause 4.9.4.2).
If the request fails the signalling is the same as for the failure case for Inter-MSC Handover GSM to UMTS (see clause 4.9.5.2)
4.9.5.2 Inter-MSC Handover (GSM to UMTS)
After a successful Inter-MSC GSM to UMTS handover, any request of Assistance Data or De-ciphering keys received by the non anchor 3G MSC via the DTAP message LCS-MOLR is handled as described in clause 4.9.4.2.
If the request fails, either because BSS-B cannot return the requested De-ciphering Keys to the anchor MSC or because BSS‑B cannot deliver the required Assistance Data to the MS, the signalling is as shown in figure 68a.
MSC-A 3G MSC-B UE
| | |
| | |
| | |
| | LCS-MOLR |
| |<————————————–|
| | |
| | |
|MAP PROCESS ACCESS | |
| SIGNALLING | |
|<——————–| |
| -an-APDU(LCS-MOLR) | |
| | |
| | |
|MAP FORWARD ACCESS | |
| SIGNALLING | |
|——————–>| |
| -an-APDU( | |
| PERFORM LOCATION | |
| REQUEST) | RNS-B |
| | |
| | | |
| |—————–>| |
| | | |
| |LOCATION RELATED | |
| | DATA REQUEST | |
| | | |
| | +————————+
| | | If Assistance Data were|
| | | requested then |
| | | Delivery of Assistance |
| | | Data to UE |
| | +————————+
| | | |
| |<—————–| |
| | | |
| |LOCATION RELATED | |
| | DATA FAILURE | |
| | | |
| | | |
| | | |
|MAP PROCESS ACCESS | | |
| SIGNALLING | | |
|<——————–| | |
| -an-APDU( | | |
| PERFORM LOCATION | | |
| RESPONSE) | | |
| | | |
| | | |
|MAP FORWARD ACCESS | | |
| SIGNALLING | -+- |
|——————–>| |
| -an-APDU( | |
| LCS-MOLR Response) | |
| | |
| | LCS-MOLR Response |
| |————————————–>|
| | |
Figure 68a: Signalling for a failed request of Assistance Data or De-ciphering Keys
When the delivery to the UE of Assistance Data for the GPS Assisted positioning method fails, the interworking between the BSSMAP messages encapsulated in MAP and the RANAP messages is as follows:
—————————————————————–
| 29.002 25.413 |Notes
——–┼————————————————–┼—–
Forward | |
message | "For the forward messages please refer to the |
| corresponding table in clause 4.9.4.2" |
| |
| |
——–┼————————————————–┼—–
Result | MAP PROCESS ACCESS SIG. LOCATION RELATED |
| request DATA FAILURE |
| -an-APDU( |
| PERFORM LOCATION RESPONSE) |
| |
| BSSMAP information RANAP information |
| elements: elements: |
| |
| LCS Cause Cause |
| > System Failure > Dedicated Assistance|
| Data Not Available |
| |
| |
When the RNS-B cannot satisfy the request for De-ciphering Keys, the interworking between the BSSMAP messages encapsulated in MAP and the RANAP messages is as follows:
—————————————————————–
| 29.002 25.413 |Notes
——–┼————————————————–┼—–
Forward | |
message | "For the forward messages please refer to the |
| corresponding table in clause 4.9.4.2" |
| |
| |
——–┼————————————————–┼—–
Result | MAP PROCESS ACCESS SIG. LOCATION RELATED |
| request DATA FAILURE |
| -an-APDU( |
| PERFORM LOCATION RESPONSE) |
| |
| BSSMAP information RANAP information |
| elements: elements: |
| |
| LCS Cause Cause |
| > System Failure > Deciphering Keys |
| Not Available |
| |
After the inter-MSC GSM to UMTS handover, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC UMTS to GSM handover is handled as for Inter-MSC Handover GSM to GSM (see clause 4.9.4.1).
If the request fails the signalling is the same as for the failure case for Inter-MSC Handover GSM to GSM (see clause 4.9.5.1)
4.9.5.3 Inter-MSC Handover (UMTS to GSM)
After a successful Inter-MSC UMTS to GSM handover, any request of Assistance Data or De-ciphering keys received by the non anchor MSC via the DTAP message LCS-MOLR is handled as described in clause 4.9.4.3.
If the request fails, either because the BSS-B cannot return the requested De-ciphering Keys to the anchor 3G MSC or BSS‑B cannot deliver the required Assistance Data to the MS, the signalling is the same as for the successful case and is shown in figure 67c.
After the inter-MSC UMTS to GSM handover, the 3G MSC-B can perform intra-MSC GSM to UMTS handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC GSM to UMTS handover is handled as for Inter-MSC Handover GSM to UMTS (see clause 4.9.4.2)..
If the request fails the signalling is the same as for the failure case for Inter-MSC Handover GSM to UMTS (see clause 4.9.5.2)
4.9.5.4 Inter-MSC SRNS Relocation
After a successful Inter-MSC SRNS Relocation , any request of Assistance Data or De-ciphering keys received by the non anchor 3G MSC via the DTAP message LCS-MOLR is handled as described in clause 4.9.4.4.
If the request fails, either because the RNS-B cannot return the requested De-ciphering Keys to the anchor 3G MSC or RNS‑B cannot deliver the required Assistance Data to the MS, the signalling is shown in figure 68b.
3G MSC-A 3G MSC-B UE
| | |
| | |
| | |
| | LCS-MOLR |
| |<————————————–|
| | |
| | |
|MAP PROCESS ACCESS | |
| SIGNALLING | |
|<——————–| |
| -an-APDU(LCS-MOLR) | |
| | |
| | |
|MAP FORWARD ACCESS | |
| SIGNALLING | |
|——————–>| |
| -an-APDU( | |
| LOCATION RELATED | |
| DATA REQUEST) | RNS-B |
| | |
| | | |
| |—————–>| |
| | | |
| | LOCATION RELATED | |
| | DATA REQUEST | |
| | | |
| | +————————+
| | | If Assistance Data were|
| | | requested then |
| | | Delivery of Assistance |
| | | Data to UE |
| | +————————+
| | | |
| |<—————–| |
| | | |
| | LOCATION RELATED | |
| | DATA FAILURE | |
| | | |
| | | |
| | | |
|MAP PROCESS ACCESS | | |
| SIGNALLING | | |
|<——————–| | |
| -an-APDU( | | |
| LOCATION RELATED | | |
| DATA FAILURE) | | |
| | | |
| | | |
|MAP FORWARD ACCESS | | |
| SIGNALLING | -+- |
|——————–>| |
| -an-APDU( | |
| LCS-MOLR Response) | |
| | |
| | LCS-MOLR Response |
| |————————————–>|
| | |
Figure 68b: Signalling for the request of Assistance Data or De-ciphering Keys
After the inter-MSC SRNS Relocation, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC UMTS to GSM requires that at the non anchor 3G MSC the received RANAP messages are mapped into the corresponding BSSMAP messages to be sent to the BSS, and the received BSSMAP messages are mapped into the corresponding RANAP messages to be sent over the E-interface to the anchor 3G-MSC.
If the request fails, either because the BSS-B cannot return the requested De-ciphering Keys to the anchor 3G MSC or BSS‑B cannot deliver the required Assistance Data to the MS, the signalling is as shown in figure 68c.
3G MSC-A 3G MSC-B UE
| | |
| | |
| | |
| | LCS-MOLR |
| |<————————————–|
| | |
| | |
|MAP PROCESS ACCESS | |
| SIGNALLING | |
|<——————–| |
| -an-APDU(LCS-MOLR) | |
| | |
| | |
|MAP FORWARD ACCESS | |
| SIGNALLING | |
|——————–>| |
| -an-APDU( | |
| LOCATION RELATED | |
| DATA REQUEST) | BSS-B |
| | |
| | | |
| |—————–>| |
| | | |
| | PERFORM LOCATION | |
| | REQUEST | |
| | | |
| | +————————+
| | | If Assistance Data were|
| | | requested then |
| | | Delivery of Assistance |
| | | Data to MS |
| | +————————+
| | | |
| |<—————–| |
| | | |
| | PERFORM LOCATION | |
| | RESPONSE | |
| | | |
| | | |
| | | |
|MAP PROCESS ACCESS | | |
| SIGNALLING | | |
|<——————–| | |
| -an-APDU( | | |
| LOCATION RELATED | | |
| DATA FAILURE) | | |
| | | |
| | | |
|MAP FORWARD ACCESS | | |
| SIGNALLING | -+- |
|——————–>| |
| -an-APDU( | |
| LCS-MOLR Response) | |
| | |
| | LCS-MOLR Response |
| |————————————–>|
| | |
Figure 68c: Signalling for the request of Assistance Data or De-ciphering Keys
After the inter-MSC SRNS Relocation, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC UMTS to GSM requires that at the non anchor 3G MSC the received RANAP messages are mapped into the corresponding BSSMAP messages to be sent to the BSS, and the received BSSMAP messages are mapped into the corresponding RANAP messages to be sent over the E-interface to the anchor 3G-MSC.
When the UE requires the delivery of Assistance Data for the GPS Assisted positioning method, the interworking between the RANAP messages encapsulated in MAP and the BSSMAP messages is as follows:
—————————————————————–
| 29.002 48.008 |Notes
——–┼————————————————–┼—–
Forward | |
message | "For the forward messages please refer to the |
| corresponding table in clause 4.9.4.4" |
| |
| |
——–┼————————————————–┼—–
Result | MAP PROCESS ACCESS SIG. PERFORM LOCATION |
| request RESPONSE |
| -an-APDU( |
| LOCATION RELATED |
| DATA FAILURE) |
| |
| RANAP information BSSMAP information |
| elements: elements: |
| |
| Cause LCS Cause |
| > Dedicated Assistance > <any value> |
| Data Not Available |
| |
When the UE requires the delivery of De-ciphering Keys for the GPS Assisted positioning method, the interworking between the RANAP messages encapsulated in MAP and the BSSMAP messages is as follows:
—————————————————————–
| 29.002 48.008 |Notes
——–┼————————————————–┼—–
Forward | |
message | "For the forward messages please refer to the |
| corresponding table in clause 4.9.4.4" |
| |
——–┼————————————————–┼—–
Result | MAP PROCESS ACCESS SIG. PERFORM LOCATION |
| request RESPONSE |
| -an-APDU( |
| LOCATION RELATED |
| DATA FAILURE) |
| |
| RANAP information BSSMAP information |
| elements: elements: |
| |
| Cause LCS Cause |
| > Deciphering Keys > <any value> |
| Not Available |
4.9.6 Abort of Request of Assistance Data or De-ciphering Keys:
4.9.6.1 Inter-MSC Handover (GSM to GSM)
After a successful Inter-MSC handover, any request of Assistance Data or De-ciphering keys received by the non anchor MSC via the DTAP message LCS-MOLR is handled as described in clause 4.9.4.1.
If the request is aborted by the anchor MSC the signalling is as shown in figure 69a.
MSC-A MSC-B MS
| | |
| | |
| | |
| | LCS-MOLR |
| |<————————————–|
| | |
| | |
|MAP PROCESS ACCESS | |
| SIGNALLING | |
|<——————–| |
| -an-APDU(LCS-MOLR) | |
| | |
| | |
|MAP FORWARD ACCESS | |
| SIGNALLING | |
|——————–>| |
| -an-APDU( | |
| PERFORM LOCATION | |
| REQUEST) | BSS-B |
| | |
| | | |
| |—————–>| |
| | | |
| | PERFORM LOCATION | |
| | REQUEST | |
| | | |
|MAP FORWARD ACCESS | | |
| SIGNALLING | | |
|——————–>| | |
| -an-APDU( | | |
| PERFORM LOCATION | | |
| ABORT) | | |
| |—————–>| |
| | | |
| | PERFORM LOCATION | |
| | ABORT | |
| | | |
| |<—————–| |
| | | |
| | PERFORM LOCATION | |
| | RESPONSE | |
| | | |
| | | |
| | | |
|MAP PROCESS ACCESS | | |
| SIGNALLING | | |
|<——————–| | |
| -an-APDU( | | |
| PERFORM LOCATION | | |
| RESPONSE) | | |
| | | |
| | | |
|MAP FORWARD ACCESS | | |
| SIGNALLING | -+- |
|——————–>| |
| -an-APDU( | |
| LCS-MOLR Response) | |
| | |
| | LCS-MOLR Response |
| |————————————–>|
| | |
Figure 69a: Signalling for the abortion of a request for Assistance Data or De-ciphering Keys
After the inter-MSC handover, the MSC-B can perform intra-MSC GSM to UMTS handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC GSM to UMTS handover is handled as for Inter-MSC Handover GSM to UMTS (see clause 4.9.4.2).
If the request is aborted the signalling is the same as for the abortion case for Inter-MSC Handover GSM to UMTS (see clause 4.9.6.2)
4.9.6.2 Inter-MSC Handover (GSM to UMTS)
After a successful Inter-MSC GSM to UMTS handover, any request of Assistance Data or De-ciphering keys received by the non anchor MSC via the DTAP message LCS-MOLR is handled as described in clause 4.9.4.1.
If the request is aborted by the anchor MSC the signalling is as shown in figure 69b.
MSC-A 3G MSC-B UE
| | |
| | |
| | |
| | LCS-MOLR |
| |<————————————–|
| | |
| | |
|MAP PROCESS ACCESS | |
| SIGNALLING | |
|<——————–| |
| -an-APDU(LCS-MOLR) | |
| | |
| | |
|MAP FORWARD ACCESS | |
| SIGNALLING | |
|——————–>| |
| -an-APDU( | |
| PERFORM LOCATION | |
| REQUEST) | RNS-B |
| | |
| | | |
| |—————–>| |
| | | |
| |LOCATION RELATED | |
| | DATA REQUEST | |
| | | |
| | | |
|MAP FORWARD ACCESS | | |
| SIGNALLING | | |
|——————–>| | |
| -an-APDU( | | |
| PERFORM LOCATION | | |
| ABORT) | | |
| | | |
| | | |
|MAP PROCESS ACCESS | | |
| SIGNALLING | | |
|<——————–| | |
| -an-APDU( | | |
| PERFORM LOCATION | | |
| RESPONSE) | | |
| | | |
| | | |
|MAP FORWARD ACCESS | | |
| SIGNALLING | -+- |
|——————–>| |
| -an-APDU( | |
| LCS-MOLR Response) | |
| | |
| | LCS-MOLR Response |
| |————————————–>|
| | |
Figure 69b: Signalling for the abortion of the request for Assistance Data or De-ciphering Keys
There"s no interworking between the BSSMAP Perform Location Abort and any RANAP message since it is not possible to abort a request for Assistance Data or De-ciphering Keys with RANAP. The BSSMAP message Perform Location Response is generated by the non-anchor 3G MSC.
After the inter-MSC GSM to UMTS handover, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC UMTS to GSM handover is handled as for Inter-MSC Handover GSM to GSM (see clause 4.9.4.1).
If the request is aborted the signalling is the same as for the abortion case for Inter-MSC Handover GSM to GSM (see clause 4.9.6.1)
4.9.6.3 Inter-MSC Handover (UMTS to GSM)
After a successful Inter-MSC UMTS to GSM handover, any request of Assistance Data or De-ciphering keys received by the non anchor MSC via the DTAP message LCS-MOLR is handled as described in clause 4.9.4.3.
If the request is aborted by the anchor 3G MSC the signalling is the same as for the abortion for Inter-MSC GSM to GSM handover abd is shown in figure 69a.
After the inter-MSC UMTS to GSM handover, the 3G MSC-B can perform intra-MSC GSM to UMTS handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC GSM to UMTS handover is handled as for Inter-MSC Handover GSM to UMTS (see clause 4.9.4.2)..
If the request is aborted the signalling is the same as for the abortion case for Inter-MSC Handover GSM to UMTS (see clause 4.9.6.2)
4.9.6.4 Inter-MSC SRNS Relocation
After a successful Inter-MSC SRNS Relocation , any request of Assistance Data or De-ciphering keys received by the non anchor 3G MSC via the DTAP message LCS-MOLR is handled as described in clause 4.9.4.4.
The request cannot be aborted by the 3G anchor MSC since RANAP does not support abortion of a request for Assistance Data or De-Ciphering Keys.