hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
7.11.1.1.3 Location Calculation and Release Procedure
|
................................................................................ 118
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
7.11.1.2 MT-LR for a previously obtained location estimate
|
........................................................................... 118
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
7.11.1.3 Network Induced Location Request (NI-LR)
|
..................................................................................... 119 7.11.1.4 Network Induced Location Request (NI-LR) from a Serving RNC for a target UE in dedicated mode................................................................................................................................................... 119
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
7.11.2 Mobile Originating Location Request
|
...................................................................................................... 119
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
7.11.2.1 Mobile Originating Location Request, Circuit Switched (CS-MO-LR)
|
............................................. 119
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
7.12 IST of non-CAMEL implementation
|
............................................................................................................. 119
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
7.13 The interaction with Super-Charger
|
............................................................................................................... 119
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
7.13.1 First Location Updating Procedure in the Super-Charged network
|
......................................................... 119
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
7.13.2 Second and further Location Updating Procedure in the Super-Charged networks
|
................................. 121
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
7.13.3 Cancel Location Procedure in the Super-Charged networks
|
.................................................................... 122
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
7.13.4 Functional requirement for the GLR
|
........................................................................................................ 123
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
7.13.4.1 Procedure Super_Charged_Cancel_Location_GLR
|
........................................................................... 123
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
7.13.4.2 Procedure Super_Charged_Location_Updating_GLR
|
....................................................................... 124
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
8 The subscriber information stored in the GLR
|
....................................................................................125
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
8.1 Information for HLR emulation
|
..................................................................................................................... 125
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
8.2 Information for address and identity conversion
|
........................................................................................... 125
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
8.3 Information for Location updating Screening
|
................................................................................................ 125
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
8.4 Information for support of Super-Charger functionality
|
................................................................................ 126
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
8.5 Other Information
|
.......................................................................................................................................... 126
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
8.6 IMSI Record in the GLR
|
............................................................................................................................... 127 Change Request History.................................................................................................................................128 ETSI ETSI TS 123 119 V3.0.0 (2000-03) 6 3G TS 23.119 version 3.0.0 Release 1999 Foreword This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 7 3G TS 23.119 version 3.0.0 Release 1999 1 Scope The present document gives the stage 2 description of the Gateway Location Register (GLR) within the UMTS Core Network as a means of reducing the amount of MAP signalling traffic associated with location management carried over inter-PLMN links for roaming users. The present document will be restricted of the case where the GLR supports one VPLMN only. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • For a non-specific reference, the latest version applies. [1] 3G TS 22.003: "Teleservices Supported by a GSM Public Land Mobile Network (PLMN)". [2] 3G TS 23.007: "Restore procedure". [3] 3G TS 23.012: "Location management". [4] 3G TS 23.018: "Basic call handling". [5] 3G TS 23.040: "Technical realization of the Short Message Service (SMS); Point-to-Point (PP)". [6] 3G TS 23.060: "General Packet Radio Service; Service description; Stage 2". [7] 3G TS 23.171: "Location Services (LCS); Functional Description; Stage 2". [8] 3G TS 23.093: "Technical realization of Completion of Calls to Busy Subscriber (CCBS) - Stage 2". [9] 3G TS 23.116: "Super-Charger Technical Realisation; Stage2". [10] 3G TS 29.002: "Mobile Application Part (MAP) specification". [11] 3G TS 29.120: "Mobile Application Part (MAP) specification for GLR". [12] 3G TS 33.102: "3G Security". ETSI ETSI TS 123 119 V3.0.0 (2000-03) 8 3G TS 23.119 version 3.0.0 Release 1999 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply. Gateway Location Register: this entity handles location management of roaming subscriber in visited network without involving HLR Intermediate GSN: this entity is used as serving GSN towards home network and relay some PDU notification messages between serving GSN and Gateway GSN Intermediate MSC: this entity is used as serving MSC towards home network and relay some messages between serving MSC and home network 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CCBS Completion of Calls to Busy Subscriber GLR Gateway Location Register GPRS General Packet Radio Service IM-GSN Intermediate GSN IM-MSC Intermediate MSC SGSN Serving GPRS Support Node 4 Introduction UMTS will build on the success of GSM and is likely to become even more widespread. UMTS/ IMT-2000 networks based on GSM evolution are planned for Europe, Japan, USA and Korea. Coupled with steadily increasing rates of international travel for business and leisure, this means a significant increase in the number of roaming users needing to be supported. This will lead to an increase of the signalling traffic on "short -haul" and "long-haul" international links. The GLR (Gateway Location Register) is a node between the VLR and/or SGSN and the HLR, which may be used to optimise the location updating and the handling of subscriber profile data across network boundaries. When a subscriber is roaming the GLR plays the role of the HLR towards the VLR and SGSN in the visited network and the role of the VLR and SGSN towards the HLR in the home network. The GLR is an optional entity within the VPLMN. The network architecture where the presence of a GLR within a UMTS PLMN is not visible to either a second generation HPLMN (i.e. GSM release 98 or earlier) or a 3G HPLMN (i.e. GSM Release 99 or later). 5 Roaming Scenario Figure 1 shows that the GLR is deployed at the edge of visited network. It contains roamer’s subscriber profile and location information, and handles mobility management within the visited network. The subscriber information is downloaded from HLR to GLR at the first location update procedure under the GLR. Using the information, GLR handles Update Location message from VLR as if it is the HLR of the subscriber at second and further location updating procedures. GLR enables the procedure invisible from the home network so that this hierarchical location management can reduce the inter-network signalling for the location management. The GLR keeps the information until receiving Cancel Location message from HLR. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 9 3G TS 23.119 version 3.0.0 Release 1999 5.1 Relationship between GLR and HLR A GLR interacts with multiple HLRs, which will be located in different PLMNs. The relationship between the GLR and the HLR is the same as that between the VLR and the HLR. The implication of supporting multiple HPLMNs is that the GLR will need to store a large amount of profile data. 5.2 Relationship between GLR and VLR A GLR interacts with multiple VLRs. For the purposes of this Technical Specification, the GLR supports only one VPLMN. The support of multiple VPLMNs by the GLR is outside the scope of this Technical Specification. However, it is an assumption of this specification that the proposed GLR architecture must not prevent future expansion to support multiple VPLMNs. HLR HPLMN A HLR GLR VLR/SGSNVLR/SGSN VPLMN a HPLMN B HLR GLR VLR/SGSNVLR/SGSN VPLMN b HPLMN C Figure 5.2/1: Possible Location of GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 10 3G TS 23.119 version 3.0.0 Release 1999 5.3 Roaming to VPLMN with GLR from HPLMN without GLR Figure 5.3/1 shows the roaming scenario in case of a subscriber roaming to a new VPLMN with the GLR. HLR HPLMN A HLR GLR VLR/SGSNVLR/SGSN VPLMN a HPLMN B HLR GLR VLR/SGSNVLR/SGSN VPLMN b HPLMN C MS-a : Location Update Subscriber Data Figure 5.3/1: Roaming to VPLMN with the GLR from HPLMN without the GLR 5.4 Intra-VPLMN with GLR roaming In this case, the second and further location updating procedure is handled within the VPLMN. No location management message issent to the HPLMN. HLR HPLMN A HLR GLR VLR/SGSNVLR/SGSN VPLMN a HPLMN B HLR GLR VLR/SGSNVLR/SGSN VPLMN b HPLMN C MS-a : Location Update : Cancel Location Subscriber Data Figure 5.4/1: Intra-VPLMN with GLR roaming ETSI ETSI TS 123 119 V3.0.0 (2000-03) 11 3G TS 23.119 version 3.0.0 Release 1999 5.5 Inter-VPLMNs with GLR Roaming This roaming case is similar to the case of roaming from HPLMN to VPLMN. The first location update procedure is handle by HLR and VLR via GLR of a new VPLMN. HLR HPLMN A HLR GLR VLR/SGSNVLR/SGSN VPLMN a HPLMN B HLR GLR VLR/SGSNVLR/SGSN VPLMN b HPLMN C MS-a : Location Update : Cancel Location Subscriber Data Figure 5.5/1: Inter-VPLMN with GLR roaming 5.6 Roaming to VPLMN without GLR from VPLMN with GLR In this case the cancel location procedure is handled by HLR and VLR via GLR of old VPLMN. HLR HPLMN A HLR GLR VLR/SGSNVLR/SGSN VPLMN a HPLMN B HLR GLR VLR/SGSNVLR/SGSN VPLMN b HPLMN C MS-a : Location Update : Cancel Location Subscriber Data VLR/SGSNVLR/SGSN VPLMN c Figure 5.6/1: Roaming to VPLMN without GLR from VPLMN with GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 12 3G TS 23.119 version 3.0.0 Release 1999 6 Logical Network Model The GLR is logically located between HLR and VLR as an optional node to optimise inter-network signalling for location management. The overall GLR concept is achieved by the GLR itself, Intermediate-MSC (IM-MSC) and Intermediate-GSN (IM-GSN). The logical network model is shown in figure 6/1. Signalling and Data Transfer Interface Signalling Interface GLR Other PLMN IM-GSN HLR GGSN SGSN IM-MSC Gate node VLR/MSC Figure 6/1: GLR Network Model 6.1 GLR The GLR is pseudo-HLR located in visited network. The roamer’s information is stored in it and handles location management of it within the network. Presence of GLR is invisible from home network therefore interface between HLR and GLR is same as one of HLR and VLR. Also, the interface between the VLR and GLR is the same as the one between the VLR and the HLR. The GLR is a logical node and acts as a VLR for MAP signalling (e.g. PRN) from the HPLMN point of view. The GLR acts as a HLR for MAP signalling (e.g. Register SS) from the VPLMN point of view. The GLR also acts as an SGSN for MAP signalling only (e.g. ISD) from the HPLMN point of view. This is because MAP operations such as ISD must be terminated at the GLR for the purpose of subscriber data caching. The GLR shall terminate all TC dialogues and start new dialogues towards the HLR or the VLR. The GLR shall generate SCCP address of the HLR (i.e. E.214 MGT) from IMSI. 6.2 Intermediate MSC The Intermediate MSC (IM-MSC) is the logical node, which represent MSCs in the visited network. Some service features use the MSC Number stored in the HLR directly to deliver message from a certain node in home network (e.g. SMS-GMSC) to serving MSC in visited network. In such case, the message is firstly distributed to representative MSC (i.e., IM-MSC) and it relays it to actual serving MSC interrogating routing information to GLR. - The Intermediate MSC (IM-MSC) is a logical node and represents the VMSC in the GLR equipped VPLMN. - The IM-MSC acts as the VMSC for the HPLMN in the same way that the GLR acts as a VLR for HPLMN. The IM-MSC terminates MAP signalling from the HPLMN towards the VMSC and forwards the signal to the actual VMSC. - The IM-MSC has an address interrogation function with which it is able to obtain the actual VMSC Number from the GLR. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 13 3G TS 23.119 version 3.0.0 Release 1999 - The IM-MSC is implemented in the same physical node as the one in which the GLR is implemented. - The GLR alters the VMSC Number to the IM-MSC Number within an Update Location message. - The IM-MSC Number is the E.164 Number assigned to the IM-MSC. - The interrogation function of the IM-MSC is similar to that in the SMS-GMSC. 6.3 Intermediate GSN The Intermediate GSN (IM-GSN) is a logical node and represents the SGSN for some GTP signalling termination in a GLR equipped VPLMN. The IM-GSN acts as an SGSN for only some GTP signalling messages (i.e. PDU_Notification request/response, PDU_Notification_reject request/response) from the HPLMN. The IM-GSN terminates these GTP signalling messages from the HPLMN towards SGSN and forwards the signal to the actual SGSN. The IM-GSN has an address interrogation function with which it is able to request the actual SGSN address from the GLR. Apart from the case described above (i.e. PDU_Notification request/response, PDU_Notification_reject request/response), all other GTP signalling should be handled directly between the SGSN and the GGSN. NOTE: MAP signalling towards the SGSN is NOT terminated at the IM-GSN. Instead it is terminated at the GLR. 6.4 Gate Node The Gate Node represents a GMSC, GMLC or SMS-GMSC. 7 Functional Description 7.1 Logical Functions This subclause gives the logical functions performed within the GLR. 7.1.1 Message Relay Function This function is used for the exchange of MAP operation between HLR and VLR/SGSN via GLR. When a message is received from VLR or SGSN, the GLR identifies the relevant HLR using appropriate logic, and vice versa. 7.1.2 Address Conversion Function The Address Conversion function in the GLR is performed when the GLR receives the Update Location message from the VLR or the Update GPRS Location message from the SGSN, and the HLR updating is required. The GLR will convert visited node addresses as follows: - VLR Number converts to the GLR Number. - MSC Number converts to the IM-MSC Number. - SGSN Number converts to the GLR Number. - SGSN Address converts to the IM-GSN Address. The converted numbers are sent to the HLR with the Update Location message or Update GPRS message. The HLR stores these addresses as the location information. The HLR uses the GLR Number as the destination address of the messages to VLR and SGSN (e.g., Insert Subscriber Data) and the messages are actually routed to the GLR. The IM- MSC Number is sent to e.g., the SMS-GMSC with a Send Routing Info for Short Message ack message as a destination ETSI ETSI TS 123 119 V3.0.0 (2000-03) 14 3G TS 23.119 version 3.0.0 Release 1999 address to the MSC and the SMS-GMSC uses the IM-MSC Number as the destination address of a Forward Short Message. The IM-GSN Address is sent to the GGSN with Send Routing Info for GPRS ack message and used as the destination address of PDU Notification message. According to this scheme, the actual visited node addresses would be stored only in the GLR. The GLR can hide second and further UL messages towards the HLR. Consequently inter-PLMN signalling will be reduced. The address conversion function in the GLR is performed also when the GLR receives any messages that include the HLR Number from the HLR. The GLR will modify the HLR Number as follows. - HLR Number converts to the GLR Number. The GLR Number is sent to the VLR or SGSN with the same message received from HLR. The VLR or SGSN stores the GLR Number as the HLR number. 7.1.3 Subscriber Information Caching Function This function is to store the subscriber’s information, which is obtained from HLR during location updating procedure. When the HLR send Insert Subscriber Data message to VLR and/or SGSN via GLR for the location update, the subscriber information is also stored in the GLR and kept until it receives Cancel Location message from HLR. The stored information is used for HLR emulation Function. 7.1.4 Subscriber Information Cancellation Function This function is to delete subscriber information stored in GLR and also in VLR and SGSN as requested from HLR or from Location Updating Screening Function in the GLR. 7.1.5 HLR emulation Function This function is to handle the location management procedure only within the visited network. When it is decided that the request of location update can be handled at the GLR without involving HLR by Location Updating Screening Function, this function is invoked and GLR acts like the HLR of the subscriber. 7.1.6 Location Updating Screening Function This function is used to judge, whether requested location updating is necessary to be indicated to HLR or not. When the GLR has the IMSI record, the GLR may not indicate the location updating to HLR and HLR emulation function is invoked. However, even though the GLR stores the IMSI record, the update location has to be indicated to HLR in some cases. The detail procedures of the cases are shown below. 7.1.7 Routeing Information Providing Function This function is used to provide routeing information to the Intermediate MSC and the Intermediate GSN. An Address Interrogation function is located within the IM-MSC, IM-GSN and GLR. The IM-MSC, IM-GSN and GLR need the actual visited node address when they need to forward messages to the actual visited node. The IM-MSC and IM-GSN interrogate the GLR to obtain these actual visited node addresses. The GLR holds the actual visited node address internally. 7.1.8 Regional Restriction and Unsupported Services handling Function This function is used to handle the regional restriction indication or unsupported service indication in Insert Subscriber Data ack message. When the GLR receives the indication, the GLR initiates the location updating procedure toward the HLR. And later, when the user returns to an MSC/SGSN area that is not restricted due to regional subscription or an area that supports the services subscribed, the GLR identifies the need to notify the HLR of the return. Therefore the location updating procedure is initiated toward the HLR for this handling. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 15 3G TS 23.119 version 3.0.0 Release 1999 7.1.9 Super Charger function This function is used handle the location management procedure from the serving node (i.e. VLR or SGSN) which supports the Super-Charger features. This is basically the same as the Super-Charged HLR. (Refer to 3G TS 23.116 [9]) Followings are supplementary explanation for the GLR behaviour as Super-Charged HLR: - When the subscription data is updated by insert subscriber data procedure from the HLR, the GLR shall update the age indicator to reflect the change of the subscription data and sends the subscription data to the serving node identified by the GLR. If the GLR receives location registration request from the Super-Charged serving node and has no subscription data for the user, whatever the content of the age indicator in the request is, when the GLR receives the subscription data from the HLR, it relays the data to the serving node. 7.2 Circuit Switched Service 7.2.1 Location Management Procedures [Editor’s Note: This section may be modified after the finalising of restructuring of 3G TS 23.012 [3] and section 19 of 3G TS 29.002 [10].] 7.2.1.1 Location Updating Procedure In case of first location updating procedure in the network that introduces the GLR, this procedure is handled by HLR and VLR via GLR. For the second and further location updating, HLR is no longer involved with the procedure. The distinction of those two cases is controlled by GLR so that HLR and VLR is not necessary to be conscious of the difference. 7.2.1.1.1 First Location Updating Procedure The first location updating procedure in a network is illustrated in figure 7.2/1. Each step is explained in the following list. GLR HLR 1. Update Location 1. Update Location 2. Insert Subscriber Data 2. Insert Subscriber Data 2. Insert Subscriber Data ack 2. Insert Subscriber Data ack 3. Update Location ack 3. Update Location ack Visited NW Home NW VLR Figure 7.2/1: First Location Updating Procedure in the Network Procedure: ETSI ETSI TS 123 119 V3.0.0 (2000-03) 16 3G TS 23.119 version 3.0.0 Release 1999 1) When the GLR receives an Update Location message from a VLR and does not hold the subscriber’s information for the user (i.e. at first location updating to the GLR), the GLR: - stores the VLR Number and serving MSC Number included in the received message, and - sends an Update Location message to the HLR with the GLR Number as VLR Number, and IM-MSC Number as MSC Number. 2) The HLR stores the GLR Number and IM-MSC Number from received message as respectively VLR Number and serving MSC Number. Thereafter the HLR initiates insert subscriber data procedure and cancel location procedure. When the GLR receives Insert Subscriber Data message from the HLR, the GLR stores the subscriber’s information in the message and transport it to the VLR. 3) After these procedures, the HLR replies to an Update Location message from the GLR and the GLR transports the response to the VLR. 7.2.1.1.2 Second and further Location Updating Procedure The second and further location updating procedure in the network is illustrated in figure 7.2/2. Each step is explained in the following list. GLR HLR 1. Update Location 3. Insert Subscriber Data 3. Insert Subscriber Data ack 4. Update Location ack Visited NW Home NW VLRNEW 2. Cancel Location 2. Cancel Location ack VLROLD Figure 7.2/2: Second and further Location Updating Procedure in the Network Procedure: 1) When the GLR receives an Update Location message from newly visited VLR and holds the subscriber information for the user (i.e. at second or further location updating to the GLR), the GLR stores the new VLR Number and new serving MSC Number included in the received message. 2) Thereafter the GLR initiates insert subscriber data procedure and cancel location procedure. 3) After these procedures, the GLR replies to an Update Location message from the VLR. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 17 3G TS 23.119 version 3.0.0 Release 1999 7.2.1.1.3 Functional requirements of GLR 7.2.1.1.3.1 Process Update_Location_GLR Figure 7.2/3 shows SDL chart for Process Update_Location_GLR. Sheet1: the test “HLR update required?” takes the “yes” exit the GLR checks some flags (ex. CCBS mon. flag) to perform the “Location Updating Screening Function (see to section 7.1.6)” and if it is needed to update location information to the HLR. Sheet1: CCBS_Status_Report_GLR procedure is called only if Alternative 2 for CCBS is performed in GLR. Sheet2: after the GLR sends an Update Location message to the HLR, the GLR receives the response with: - an Insert Subscriber Data message handled by the procedure Insert_Subscriber_Data_GLR. - a Forward Check SS indication message. This message will be relayed to the VLR without any change of the current state. - an Update Location ack message. If the GLR receives this message, this indicates that updating has been successfully completed. The GLR sets the "(Location and Subscriber information) LSIC by HLR" indicator to "Confirmed". The GLR send an Update Location ack message to the VLR. - an Update Location negative response message. If the GLR receives this message, this indicates that updating has been unsuccessfully completed. The GLR sets the “(Location and Subscriber information) LSIC by HLR” indicator to “False”. The GLR sends an Update Location negative to the VLR. Sheet1: process Cancel_Location_Initiated_GLR is specified in subclause 7.2.1.2.1.2. Sheet5: CCBS_Start_Report_GLR procedure is called only if Alternative 2 for CCBS performed in GLR. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 18 3G TS 23.119 version 3.0.0 Release 1999 Process in the G LR to handle an Update Location request and trigger the correct application process Process Update_Location_G LR 1(7) Signales to/from the left are to/from the VLR Signales to/from the right are to/from the HLR Idle Update Location Check Param eter See TS 23.018 Result= Pass subscriber known in GLR Netw ork access m ode = G PRS only Set negative response: Unknown Subscriber Update Location negative response Idle HLR update required? New VLR? Super_Charged_ Cancel_Location _GLR Result =Pass? Cancel_Location_ Initiated_GLR CC BS_status_ report_GLR 1 Set GLR Num ber as VLR N um ber Set IM -M SC N um ber as M SC N um ber Update Location W ait_For_ Data Yes Yes Yes No No Yes No Yes No Yes No No Figure7.2/3(1): Process Update_Location_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 19 3G TS 23.119 version 3.0.0 Release 1999 P rocess in the G LR to handle an U pdate Location request and trigger the correct application process Process Update_Location_GLR 2(7) S ignales to/from the left are to/from the VLR S ignales to/from the right are to/from the HLR W ait_For_ Data Insert Subscriber Data Insert_ Subscriber_ Data_G LR W ait_For_ Data_from _H LR _ and_IS D_ack_ from _V LR Forward C heck SS indication Forward Check SS indicator W ait_For_ Data Update Location ack Result:=P ass LS IC by H LR := Confirm ed S et G LR N um ber as HLR Num ber Update Location ack Idle Update Location negative response Failure C ase? Result:= Roam ing Not A llow ed Delete Subscriber Data LS IC by H LR := False Update Location negative response Idle Result:= Unknow n Subscriber Delete Subscriber Data Result:= P rocedure E rror Abort Abort Idle Roam ing Not A llow ed Unknow n Subscriber P rocedure E rror Figure7.2/3(2): Process Update_Location_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 20 3G TS 23.119 version 3.0.0 Release 1999 P rocess in the G LR to handle an U pdate Location request and trigger the correct application process Process Update_Location_GLR 3(7) S ignales to/from the left are to/from the VLR S ignales to/from the right are to/from the HLR W ait_For_ Data_from _H LR _ and_IS D_ack_ from _V LR Insert Subscriber Data Forward C heck SS indication Update Location ack Update Location negative responseAbort Insert_ Subscriber_ Data_G LR Forward Check SS indicator Result:=P ass A bort W ait_For_ Data_from _H LR _ and_IS D_ack_ from _V LR W ait_For_ Data_from _H LR _ and_IS D_ack_ from _V LR LS IC by H LR := Confirm ed Idle S et G LR N um ber as HLR Num ber Update Location ack Failure C ase? Idle Result:= Roam ing Not A llow ed Result:= Unknow n Subscriber Result:= P rocedure E rror Delete Subscriber Data Delete Subscriber Data LS IC by H LR := False Update Location negative response Idle Roam ing Not A llow ed Unknow n Subscriber P rocedure E rror Figure7.2/3(3): Process Update_Location_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 21 3G TS 23.119 version 3.0.0 Release 1999 Process in the G LR to handle an U pdate Location request and trigger the correct application process Process Update_Location_GLR 4(7) Signals to/from the left are to/from the VLR Signals to/from the right are to/from the HLR W ait_For_ Data_from _HLR _ and_ISD_ack_ from _VLR Insert Subscriber Data ack Insert Subscriber D ata negative response All received feature & service supported? Insert Subscriber D ata negative response Update subscriber data for supported features Update Seubscriber Data set parameters for unsupported features W ait_For_ Data_from _HLR _ and_ISD_ack_ from _VLR M SC area restricted by regional subscription? Set MSC area restricted Insert Subscriber Data ack W ait_For_ Data_from _HLR _ and_ISD_ack_ from _VLR No Yes Yes No Figure7.2/3(4): Process Update_Location_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 22 3G TS 23.119 version 3.0.0 Release 1999 Process in the G LR to handle an U pdate Location request and trigger the correct application process Process Update_Location_GLR 5(7) Signales to/from the left are to/from the V LR S ignales to/from the right are to/from the HLR 1 S uper_Charged_ Location_Updating_ G LR R esult =P ass? IS D_G LR R esult = P ass? M S C Area R estricted? O R R oam ing Restricted Due to U nsupported Feature? Subscriber_Present_ G LR Check_S S _ Required? Forw ard CheckS S Indication Check_S S _ R equired:= False C hanged supported services? C hanged M S C area restricted S et G LR N um ber as VLR N um ber S et IM -M S C N um ber as M S C N um ber U pdate Location W ait_For_ inform ation U pdate Location ack C C B S _start_ report_G LR Idle R esult = A borted? U pdate Location negative response Idle Idle U pdate Location ack Idle N o Y es N o True N o Y es N o Y es False Y es N o N o Y es Y es Figure7.2/3(5): Process Update_Location_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 23 3G TS 23.119 version 3.0.0 Release 1999 Process in the G LR to handle an U pdate Location request and trigger the correct application process Process Update_Location_GLR 6(7) Signales to/from the left are to/from the VLR Signales to/from the right are to/from the HLR W ait_For_ Information Insert Subscriber Data 2 Forward Check SS indication Forward Check SS indication W ait_For_ information Update Location ack Result:= Pass LSIC by H LR :=True Set GLR Number as HLR Num ber Update Location ack Idle Update Location negative response Failure case? Result:= Roam ing Not Allow ed Delete Subscriber Data LSIC by H LR :=False Update Location negative response Idle Result:= Unknow n Subscriber Delete Subscriber Data Result:= Procedure Error Abort Abort Idle Roam ing not Allowed Unknow n Subscriber Procedure Error Figure7.2/3(6): Process Update_Location_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 24 3G TS 23.119 version 3.0.0 Release 1999 Process in the G LR to handle an Update Location request and trigger the correct application process Process Update_Location_GLR 7(7) Signales to/from the left are to/from the VLR Signales to/from the right are to/from the HLR 2 Check Parameter See TS 23.018 Result= Pass? Subscriber know n? All received features & services supported? Update Subscriber Data M SC area restricted by regional subscription? Set M SC area restricted Insert Subscriber Data ack W ait_For_ Inform ation Update Subscriber Data for supported features Set param eters for unsupported features Insert Subscriber Data negative response Idle Yes Yes Yes Yes No No No No Figure7.2/3(7): Process Update_Location_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 25 3G TS 23.119 version 3.0.0 Release 1999 7.2.1.1.3.2 Process Subscriber_Present_GLR Figure 7.2/4 shows SDL chart for Process Subscriber_Present_GLR. Process in the GLR Application to perform actions required for short message alerting Process Subscriber_Present_GLR 1(1) MNRF Set? Subscriber_ Present_ GLR_AS_VLR See TS 29.120 Section 25.4 Yes No Figure7.2/4: Process Subscriber_Present_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 26 3G TS 23.119 version 3.0.0 Release 1999 7.2.1.1.3.3 Procedure Insert_Subscriber_Data_GLR Figure 7.2/5 shows SDL chart for Procedure Insert_Subscriber_Data_GLR. This procedure is initiated by receiving Insert Subscriber Data from the HLR. This procedure is used by Process Update_Location_GLR and Process Update_GPRS_Location_GLR. Procedure to receive and store subscriber data in the GLR Procedure Insert_Subscriber_Data_GLR 1(1) Signals to/from the left are to/from the VLR/SGSN SIgnals to/from the right are to/from the HLR Check Parameter See TS 23.018 Result= Pass? Subscriber known? Store Subscriber Data Insert Subscriber Data Insert Subscriber Data negative response Yes Yes No No Figure7.2/5: Procedure Insert_Subscriber_Data_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 27 3G TS 23.119 version 3.0.0 Release 1999 7.2.1.1.3.4 Procedure Insert_Subscriber_Data_Initiated_GLR Figure 7.2/6 shows SDL chart for Procedure Insert_Subscriber_Data_Initiated_GLR. This procedure is initiated if HLR update is not required. P rocedure in the G LR A pplica tio n fo r ha ndling the insertion of subscriber data in to the V L R Procedure Insert_Subscriber_Data_Initiated_G LR 1(2) S igna ls to/from th e left are to /from the V L R Inse rt S u bscriber Da ta C ount:= 1 M ore Da ta To S end ? Inse rt S u bscriber Da ta C ou nt:= Co unt+ 1 W a it_ For_ IS D_A ck Inse rt S u bscriber Da ta ack C ou nt:= Cou nt-1 1 A bort R esult:= A borte d Insert S ubscriber Da ta ne gative respo nse S et N egative R espo nse System Failure R esult:= Fail 2 Y es N o Figure7.2/6(1): Procedure Insert_Subscriber_Data_Initiated_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 28 3G TS 23.119 version 3.0.0 Release 1999 P rocedu re in the G LR A p plica tio n fo r ha nd ling the insertion o f su bscriber data into the V L R Procedure Insert_Subscriber_Data_Initiated_GLR 2(2) S ig na ls to/from th e left are to /from the V LR 1 A ny se rvice s not suppo rte d in V LR ? Ignore Un su pporte d S e rvice ? R ep la se S ervice in V LR ? Un suppo rte d S ervice C ritica l? G LR In ternal A ctio n M S C A re a Restricted ? S et M S C A rea Re stricted Cou nt>0 ? R esult := Pass W a it_ For_ IS D_A ck Roa m in g Re stricted Du e T o Un su ppo rte d F eatu re= True; M S C A re a R estricted= Tru e 2 Rep lace S ervice Y es N o N o N o Y es N o Y es N o Y es Y es Y es N o Figure7.2/6(2): Procedure Insert_Subscriber_Data_Initiated_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 29 3G TS 23.119 version 3.0.0 Release 1999 7.2.1.2 Cancel Location Procedure The cancel location procedure in the network when MS leave the network is illustrated in figure 7.2/7. Each step is explained in the following list. GLR HLR 1. Update Location 3. Insert Subscriber Data 3. Insert Subscriber Data ack 4. Update Location ack Visited NW Home NW 2. Cancel Location 2. Cancel Location ack VLRNEW VLROLD 2. Cancel Location 2. Cancel Location ack Figure 7.2/7: Cancel Location Procedure in the Network Procedure: 1) When the HLR receives an Update Location message from newly visited VLR after the MS left the network with the GLR, the HLR initiates cancel location procedure to the GLR. 2) The GLR receives a Cancel Location message from the HLR and transport to the previously visited VLR. When the GLR receives the response, the GLR transports it to the HLR and delete the roamer’s subscriber profile and location information. 3) The HLR initiates insert subscriber data procedure to the newly visited VLR. 4) After the procedure, the HLR returns the response of an Update Location message to the newly visited VLR. 7.2.1.2.1 Functional requirements of GLR 7.2.1.2.1.1 Process Cancel_Location_GLR Figure 7.2/8 shows SDL chart for Process Cancel_Location_GLR. This process is initiated from the HLR. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 30 3G TS 23.119 version 3.0.0 Release 1999 Process in the GLR application to initiate cancellation of location registeration in a VLR Process Cancel_Location_G LR 1(1) Signals to/from the left are to/from the VLR Signals to/from the right are to/from the HLR Idle Cancel Location Check Param eter See TS 23.018 R esult= Pass? Super_Charged_ Cancel_Location_ GLR R esult =Pass? C ancel Location W ait_For_ R esponse Cancel Location ack D elete Subscriber data C ancel Location ack Idle Cancel Location negative response Cancel Location negative response Cancel Location negative response Idle Yes N o Yes N o Figure7.2/8: Process Cancel_Location_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 31 3G TS 23.119 version 3.0.0 Release 1999 7.2.1.2.1.2 Process Cancel_Location_Initiated_GLR Figure 7.2/9 shows SDL chart for Process Cancel_Location_Initiated_GLR. This process is initiated if HLR update is not required. Process in the G LR application to initiate cancellation of location registeration in a VLR Process Cancel_Location_Initiated_GLR 1(1) SIgnals to/from the left are to/from the VLR Cancel Location W ait_For_ CL_Response Cancel Location ack Abort Repeat Location Cancellation? W ait for tim e expiry Cancel Location negative response Yes No Figure7.2/9: Process Cancel_Location_Initiated_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 32 3G TS 23.119 version 3.0.0 Release 1999 7.2.1.3 Handling of unsupported service The procedure can be used to handle the case where the VLR does not support the full set of services required by the user. See figure 7.2/10. When the GLR receives the Insert Subscriber Data Acknowledge message indicating “Service Not Supported”, it initiates the location updating procedure toward the HLR. The HLR takes some appropriate reaction (e.g. initiates service substitution or roaming restriction etc.) and determines whether to accept the location updating request or not for the user. The HLR generates a new profile (i.e. the profile after service substitution), which must be forwarded by the GLR to the VLR. The GLR must also maintain a copy of the actual service profile for the subscriber (i.e. the profile before service substitution). The GLR will have to perform some transaction level processing on message 3 (i.e. Insert Subscriber Data ack) from the VLR. Subsequently, when the GLR sends message 6 (i.e. Insert Subscriber Data ack) to the HLR, the message format will have to match that of message 5 (Insert Subscriber Data) from the HLR. GLR HLR Visited NW Home NW Can’t Support The Full Set of Subscribed Services VLR 1. Update Location 2. Insert Subscriber Data 3. Insert Subscriber Data ack (Service Not Supported) Some appropriate action 4. Update Location 5. Insert Subscriber Data 7. Update Location ack OR Update Location error Identifies unsupported and Decides to initiate UL 6. Insert Subscriber Data ack (Service Not Supported) 8. Update Location ack OR Update Location error Figure 7.2/10: MS Arrives at a VLR That Cannot Handle all Services When the user roams from a VLR area with restricted service support into a VLR area where the VLR can support the full set of subscribed services, the GLR must: - Identify that the new VLR can support the actual service profile required by the HLR, i.e. the profile before service substitution. - notify the HLR to take the appropriate reaction to restore services. Therefore, the GLR initiates the location updating procedure towards the HLR. (refer to figure 7.2/11 in the case of circuit switched mode). ETSI ETSI TS 123 119 V3.0.0 (2000-03) 33 3G TS 23.119 version 3.0.0 Release 1999 The GLR will have to perform some transaction level processing on message 3 (i.e. Insert Subscriber Data ack) from the VLR. Subsequently, when the GLR sends message 6 (i.e. Insert Subscriber Data ack) to the HLR, the message format will have to match that of message 5 (Insert Subscriber Data) from the HLR. GLR HLR Visited NW Home NW Can Support The Full Set of Subscribed Services VLR 1. Update Location 2. Insert Subscriber Data 3. Insert Subscriber Data ack Some appropriate action 4. Update Location 5. Insert Subscriber Data 7. Update Location ack Identifies the full set of subscribed service ssupported and Decides to 6. Insert Subscriber Data ack 8. Update Location The Procedure for Unsupported Service handling was initiated On location updating in the previously visited VLR Figure 7.2/11: MS Arrives at a VLR That Handles all Services 7.2.2 Retrieval of routeing information procedure In 3G TS 23.018 [4](Basic Call Handling) specification, the description for the basic call handling about MO and MT is stated. Only the retrieval of routeing information for an MT call is related with the GLR. Therefore, this specification states the retrieval of routeing information for an MT call. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 34 3G TS 23.119 version 3.0.0 Release 1999 7.2.2.1 Information flow for retrieval of routeing information for an MT call The information flow for retrieval of routeing information for an MT call is shown in figure 7.2/12. Solid lines show ISUP signalling between the originating exchange and GMSCB, and between GMSCB and VMSCB; signalling over the MAP interfaces between GMSCB and HLRB and between HLRB and VLRB is shown by chain lines. IAM GMSC HLRB GLRB VMSCB SRI SRI ack PRN PRN ack IAM VLRB PRN PRN ack Figure 7.2/12: Information flow for retrieval of routeing information for a basic mobile terminated call When GMSCB receives an IAM, it analyses the called party address. If GMSCB can derive an HLR address from the B party address, it sends a request for routeing information (SRI) to HLRB. HLRB sends a request for a roaming number (PRN) to VLRB via GLRB. VLRB returns the roaming number in the PRN ack via GLR, and HLRB relays the roaming number to GMSCB in the SRI ack. GMSCB constructs an IAM using the roaming number, and sends it to VMSCB. If the VLRB supports the Super-Charger features, when the VLRB receives a request for a roaming number (PRN) and has no subscriber data for the user, it checks whether the subscriber data record was removed by the Super-Charger database management function or not. (See 3G TS 23.116 [9]) If the subscriber data was removed by the Super-Charger feature, the VLRB shall return the cause information set to Purged MS to the GLR by sending PRN negative response. When the GLR receives this information, it deletes the subscriber data for the user and relays the message to the HLR. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 35 3G TS 23.119 version 3.0.0 Release 1999 7.2.2.2 Functional requirements of network entities The text in this clause is a supplement to the definition in the SDL diagrams; it does not duplicate the information in the SDL diagrams. The entities described in this clause interwork with other entities over the D interfaces, used to interwork between the VLR & HLR. The protocol used over the D interfaces is MAP, which is specified in 3G TS 29.002 [10]. For the purposes of this specification, the protocol used over telephony signalling interfaces is ISUP, which is specified in ETS 300 356-1 [27]; other telephony signalling systems may be used instead. The SDL diagrams in this clause show the handling for a number of optional features and services. If the handling consists only of a call to a procedure specific to the feature or service, the procedure call is omitted if the entity does not support an optional feature or service. If the handling consists of more than a call to a procedure specific to the feature or service, the text associated with each SDL diagram specifies the handling that applies if the entity does not support an optional feature or service. 7.2.2.2.1 Functional requirements of GLR 7.2.2.2.1.1 Process PRN_GLR Figure 7.2/13 shows SDL chart for Process PRN_GLR. Sheet1: the GLR receives a PRN message from the HLR. Sheet1: after the GLR transfers the VLR Number, the GLR relays a PRN message to the VLR. Sheet1: the GLR waits a PRN response and receives a PRN ack message or a PRN negative response message from the VLR. Sheet1: after the GLR transfers the HLR Number, the GLR relays a PRN ack message or a PRN negative response message to the HLR. Figure 7.2/14 shows SDL chart for Procedure Super_Charged_PRN_Error_GLR. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 36 3G TS 23.119 version 3.0.0 Release 1999 P rocess in the G LR to handle a request for a roam ing num ber Process PRN_GLR 1(1) S ignals to/from the left are to/from the HLR: signals to/from the right are to/from the VLR . Idle Provide Roam ing N um ber from H LR S et G LR N um ber as M S C num ber Provide Roam ing N um ber to V LR W ait for Provide Roam ing N um ber response Provide Roam ing N um ber ack from VLR P rovide Roam ing N um ber ack to HLR Idle Provide Roam ing Num ber negative response from V LR Provide Roam ing Num ber negative response to HLR S uper_Charged_ PR N _Error_ G LR Idle Figure7.2/13: Process PRN_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 37 3G TS 23.119 version 3.0.0 Release 1999 The procedure Super_Charged_PR N_Error_GLR determ ines w hether the G LR shall delete its data for the M S based on the outcom e of a Provide R oam ing N um ber Procedure Super_Charged_PRN_Error_G LR 1(1) Super-C harged GLR Absent Subscriber Error: Purged M S? Delete Subscriber Data Yes Yes N o N o Figure7.2/14: Procedure Super_Charged_PRN_Error_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 38 3G TS 23.119 version 3.0.0 Release 1999 7.2.2.2.1.2 Process PSI_GLR Figure 7.2/15 shows SDL chart for Process PSI_GLR. Sheet1: the GLR receives a PSI message from the HLR. Sheet1: after the GLR transfers the VLR Number, the GLR relays a PSI message to the VLR. Sheet1: the GLR waits a PSI response and receives a PSI ack message or a PSI negative response message from the VLR. Sheet1: after the GLR transfers the HLR Number, the GLR relays a PSI ack message or a PSI negative response message to the HLR. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 39 3G TS 23.119 version 3.0.0 Release 1999 P rocess in the G LR to handle a request from the H LR for subscriber inform ation Process PSI_GLR 1(1) S ignals to/from the left are to/from the HLR: signals to/from the right are to/from the VLR. Idle Provide Subscriber Info from HLR Provide Subscriber Info to V LR W ait for Provide S ubscriber Info response Provide S ubscriber Info ack from VLR from V LR Provide S ubscriber Info negative response S et G L R N um ber as VLR N um ber P rovide Subscriber Info ack to HLR to HLR Provide S ubscriber Info negative response Idle Idle Figure7.2/15: Process PSI_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 40 3G TS 23.119 version 3.0.0 Release 1999 7.2.2.3 Contents of messages (HLR-GLR, GLR-VLR) There is no different between the contents of the following messages sent between HLR and VLR and the contents of the following messages sent between HLR and GLR, GLR and VLR. The same contents are sent from the HLR to VLR via the GLR. See 3G TS 23.018 [4]. - Provide Roaming Number. - Provide Roaming Number ack. - Provide Roaming Number negative response. - Provide Subscriber Info. - Provide Subscriber Info ack. - Provide Subscriber Info negative response. 7.2.3 Authentication Information Retrieval procedure ARRI The Authentication Information Retrieval procedure is illustrated in figure 7.2/16. Each step is explained in the following list. GLR HLR Visited NW Home NW VLR 1. Send Authentication Info 2. Send Authentication Info 3. Send Authentication Info ack 4. Send Authentication Info ack Figure 7.2/16: Send Authentication Info Procedure: 1) When the VLR receives a service indication concerning a location registration, call set-up, operation on a supplementary service to initiate authentication. The VLR sends a Send Authentication Info message to the GLR in order to retrieve the authentication information. 2) The GLR transfers the received message to the HLR. 3) When the GLR receives the response with authentication information for the user from the HLR, it transports to the VLR. 4) The VLR receives the authentication information of user by the response of Send Authentication Info message. 7.2.4 Subscriber Data management procedure 7.2.4.1 Insert Subscriber Data Procedure The Insert Subscriber Data procedure is illustrated in figure 7.2/17. Each step is explained in the following list. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 41 3G TS 23.119 version 3.0.0 Release 1999 GLR HLR Visited NW Home NW VLR 1. Insert Subscriber Data 2. Insert Subscriber Data 3. Insert Subscriber Data ack 4. Insert Subscriber Data ack Figure 7.2/17: Insert Subscriber Data Procedure: 1) The HLR sends Insert Subscriber Data message to the GLR in order to update with the certain subscriber data. 2) The GLR updates the subscriber data and transfer the received message to the VLR. 3) The GLR receives the response from the VLR. The response may indicate regional restriction or unsupported services. The detail procedures are described in subclause 7.5. 4) The GLR transfers the received message to the HLR. 7.2.4.2 Delete Subscriber Data Procedure The Delete Subscriber Data procedure is used by an HLR to remove certain subscriber data from a VLR and a SGSN if the subscription of one or more supplementary services or basic services is withdrawn. Note that this service is not used in case of erasure or deactivation of supplementary services. And the Delete Subscriber Data procedure is illustrated in figure 7.2/18. Each step is explained in the following list. GLR HLR Visited NW Home NW VLR 1. Delete Subscriber Data 2. Delete Subscriber Data 3. Delete Subscriber Data ack 4. Delete Subscriber Data ack Figure 7.2/18: Delete Subscriber Data ETSI ETSI TS 123 119 V3.0.0 (2000-03) 42 3G TS 23.119 version 3.0.0 Release 1999 Procedure: 1) The HLR sends a Delete Subscriber Data message to the GLR in order to remove with the certain subscriber data. 2) The GLR deletes the subscriber data indicated and transfers the received message to the VLR. 3) The GLR receives a Delete Subscriber Data ack message from the VLR. 4) The GLR transfers the received message to the HLR. 7.2.5 Supplementary services procedures Activation, deactivation, registration, erasure, and interrogation are the procedures involving the interface between the VLR and the HLR related to the control of state of the supplementary services. Also Registration of password and use of password are the procedures involving the interface. Additionally, Unstructured SS Data service and CCBS includes the procedure involving the interface. If the GLR is located between the HLR and the VLR, the GLR relays the messages between HLR and VLR of the procedures transparently. The registration procedure involving the GLR is described in figure 7.2/19 as a typical case. The following procedures are the similar to the registration procedure. Each step is explained in the following list. GLR HLR Visited NW Home NW VLR 1. Register SS 2. Register SS 3. Register SS ack 4. Register SS ack Figure 7.2/19: Register SS Procedure: 1) When the VLR receives a service indication of registration of SS data, such as a Forwarded-to-Number, the VLR sends a Register SS message. 2) The GLR transfers the received message to the HLR. 3) The GLR receives the acknowledgement from the HLR. 4) The GLR transfers the received message to the VLR. 7.3 Packet Switched Service This subclause describes the GPRS procedures involving GLR except Short Message Service, Recovery and Restoration. The procedures for Short Message Service of GPRS are described in the subclause “Short Message Service.” The procedures for Recovery and Restoration of GPRS are described in the subclause “Recovery and Restoration.” ETSI ETSI TS 123 119 V3.0.0 (2000-03) 43 3G TS 23.119 version 3.0.0 Release 1999 7.3.1 GPRS Attach Procedure Three cases are described in this section: - The new SGSN is within a VPLMN served by the GLR. The old SGSN interfaces to the HLR directly. - The new SGSN and old SGSN are within a VPLMN served by the same GLR. - The new SGSN is within a VPLMN served by the GLR. The old SGSN is within a different VPLMN served by the GLR. - The new SGSN interfaces to the HLR directly. The old SGSN is within a VPLMN served by the GLR. 7.3.1.1 New SGSN served by GLR, old SGSN served by HLR 6d. Insert Subscriber Data 6c. Cancel Location Ack 6b. Cancel Location 3. Identity Response 2. Identification Response 2. Identification Request 1. Attach Request 5. IMEI Check 3. Identity Request 4. Authentication 6a. Update Location 6f. Update Location Ack 6e. Insert Subscriber Data Ack MS BSS new SGSN old SGSN GGSN HLR EIR 9. Attach Complete 8. Attach Accept GLR Figure 7.3/1: GPRS Attach Procedure involving GLR (new SGSN is under the GLR. Old SGSN interfaces the HLR directly) 1) to 5) These steps are the same as the steps not involving GLR. See TS 23.060 [6]. 6) If the SGSN number has changed since the GPRS detach, or if it is the very first attach, then the SGSN informs the HLR via GLR: a) The SGSN sends an Update Location (SGSN Number, SGSN Address, and IMSI) to the GLR. Then the GLR sends an Update Location (GLR Number, IM-GSN address, IMSI) to the HLR, if the GLR does have the IMSI record. Note that, GLR Number and IM-GSN address should respectively be set in SGSN Number parameter and SGSN address parameters. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 44 3G TS 23.119 version 3.0.0 Release 1999 b) The HLR sends Cancel Location (IMSI, Cancellation Type) to the old SGSN with Cancellation Type set to Update Procedure. c) The old SGSN acknowledges with Cancel Location Ack (IMSI). If there are any ongoing procedures for that MS, the old SGSN shall wait until these procedures are finished before removing the MM and PDP contexts. d) The HLR sends Insert Subscriber Data (IMSI, GPRS subscription data) to the GLR. The GLR sends Insert Subscriber Data (IMSI, GPRS subscription data) to the new SGSN. e) The new SGSN validates the MS's presence in the (new) RA. If due to regional subscription restrictions the MS is not allowed to attach in the RA, the SGSN rejects the Attach Request with an appropriate cause, and may return an Insert Subscriber Data Ack (IMSI, SGSN Area Restricted) message to the GLR. Then, the GLR set the SGSN area restricted flag “true” and transfers the SGSN area restricted indication to the HLR within the Insert Subscriber Data Ack message. Note that some modification at the application level might be needed here to maintain compatibility with the message format of (6d). If subscription checking fails for other reasons, the SGSN rejects the Attach Request with an appropriate cause and returns an Insert Subscriber Data Ack (IMSI, Cause) message to the GLR, which the GLR transfers to the HLR within the Insert Subscriber Data Ack message. Note that some modification at the application level might be needed here to maintain compatibility with the message format of (6d). If all checks are successful then the SGSN constructs an MM context for the MS and returns an Insert Subscriber Data Ack (IMSI) message to the GLR, which the GLR transfers to the HLR. f) The HLR acknowledges the Update Location message by sending an Update Location Ack to the GLR and the GLR send it to the SGSN after the cancelling of old MM context and insertion of new MM context are finished. If the Update Location is rejected by the HLR, the SGSN rejects the Attach Request from the MS with an appropriate cause. 8) and 9) These steps are the same as the steps not involving GLR. See TS 23.060 [6]. If the Attach Request cannot be accepted, the SGSN returns an Attach Reject (IMSI, Cause) message to the MS. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 45 3G TS 23.119 version 3.0.0 Release 1999 7.3.1.2 New SGSN and old SGSN served by the same GLR 6d. Insert Subscriber Data 6c. Cancel Location Ack 6b. Cancel Location 3. Identity Response 2. Identification Response 2. Identification Request 1. Attach Request 5. IMEI Check 3. Identity Request 4. Authentication 6a. Update Location 6f. Update Location Ack 6e. Insert Subscriber Data Ack MS BSS new SGSN old SGSN GGSN HLR EIR 9. Attach Complete 8. Attach Accept GLR Figure 7.3/2: GPRS Attach Procedure involving GLR (new SGSN and old SGSN are under in the same GLR) 1) to 5) These steps are the same as the steps not involving GLR. See TS 23.060 [6]. 6) If the SGSN number has changed since the GPRS detach, or if it is the very first attach, then the SGSN informs the GLR: a) The SGSN sends an Update Location (SGSN Number, SGSN Address, and IMSI) to the GLR. If the GLR has the IMSI record, the GLR does not send an Update Location message to the HLR. b) The GLR sends Cancel Location (IMSI, Cancellation Type) to the old SGSN with Cancellation Type set to Update Procedure. c) The old SGSN acknowledges with Cancel Location Ack (IMSI). If there are any ongoing procedures for that MS, the old SGSN shall wait until these procedures are finished before removing the MM and PDP contexts. d) The GLR sends Insert Subscriber Data (IMSI, GPRS subscription data) to the new SGSN. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 46 3G TS 23.119 version 3.0.0 Release 1999 e) The new SGSN validates the MS's presence in the (new) RA. If due to regional subscription restrictions the MS is not allowed to attach in the RA, the SGSN rejects the Attach Request with an appropriate cause, and may return an Insert Subscriber Data Ack (IMSI, SGSN Area Restricted) message to the GLR. If the SGSN area restricted flag is set “false” in the GLR, the GLR sets the lag “true” and sends an Update Location (GLR Number, IM-GSN address, IMSI) to the HLR. Subclause 7.5 describes the detail procedure. Note that, GLR Number and IM-GSN address should respectively be set in SGSN Number parameter and SGSN address parameters. If subscription checking fails for other reasons, the SGSN rejects the Attach Request with an appropriate cause and returns an Insert Subscriber Data Ack (IMSI, Cause) message to the GLR. If all checks are successful then the SGSN constructs an MM context for the MS and returns an Insert Subscriber Data Ack (IMSI) message to the GLR. f) The GLR acknowledges the Update Location message by sending an Update Location Ack to the SGSN after the cancelling of old MM context and insertion of new MM context are finished. If the Update Location is rejected by the GLR, the SGSN rejects the Attach Request from the MS with an appropriate cause. 8) and 9) These steps are the same as the steps not involving GLR. See TS 23.060 [6]. If the Attach Request cannot be accepted, the SGSN returns an Attach Reject (IMSI, Cause) message to the MS. 7.3.1.3 New SGSN served by the GLR, and old SGSN served by the other GLR 6d. Insert Subscriber Data 6c. Cancel Location Ack 6b. Cancel Location 3. Identity Response 2. Identification Response 2. Identification Request 1. Attach Request 5. IMEI Check 3. Identity Request 4. Authentication 6a. Update Location 6f. Update Location Ack 6e. Insert Subscriber Data Ack MS BSS new SGSN old SGSN GGSN HLR EIR 9. Attach Complete 8. Attach Accept new GLR old GLR Figure 7.3/3: GPRS Attach Procedure involving GLR (new SGSN and old SGSN are under in the different GLR) 1) to 5) These steps are the same as the steps not involving GLR. See TS 23.060 [6]. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 47 3G TS 23.119 version 3.0.0 Release 1999 6) If the SGSN number has changed since the GPRS detach, or if it is the very first attach, then the SGSN informs the HLR via GLR: a) The SGSN sends an Update Location (SGSN Number, SGSN Address, and IMSI) to the GLR. Then the GLR sends an Update Location (GLR Number, IM-GSN address, IMSI) to the HLR if the GLR does not have the IMSI record. Note that, GLR Number and IM-GSN address should respectively be set in SGSN Number parameter and SGSN address parameters in the actual MAP operation. b) The HLR sends Cancel Location (IMSI, Cancellation Type) to the old GLR with Cancellation Type set to Update Procedure. Then the GLR sends Cancel Location (IMSI, Cancellation Type) to the old SGSN with Cancellation Type set to Update Procedure. c) The old SGSN acknowledges with Cancel Location Ack (IMSI). If there are any ongoing procedures for that MS, the old SGSN shall wait until these procedures are finished before removing the MM and PDP contexts. d) The HLR sends Insert Subscriber Data (IMSI, GPRS subscription data) to the GLR. The GLR sends Insert Subscriber Data (IMSI, GPRS subscription data) to the new SGSN. e) The new SGSN validates the MS's presence in the (new) RA. If due to regional subscription restrictions the MS is not allowed to attach in the RA, the SGSN rejects the Attach Request with an appropriate cause, and may return an Insert Subscriber Data Ack (IMSI, SGSN Area Restricted) message to the GLR. The GLR sets the SGSN area restricted flag “true” and transfers the SGSN area restricted indication to the HLR within the Insert Subscriber Data Ack message. Note that some modification at the application level might be needed here to maintain compatibility with the message format of (6d). If subscription checking fails for other reasons, the SGSN rejects the Attach Request with an appropriate cause and returns an Insert Subscriber Data Ack (IMSI, Cause) message to the GLR, which the GLR transfers to the HLR within the Insert Subscriber Data Ack message. Note that some modification at the application level might be needed here to maintain compatibility with the message format of (6d). If all checks are successful then the SGSN constructs an MM context for the MS and returns an Insert Subscriber Data Ack (IMSI) message to the GLR, which the GLR transfers to the HLR. f) The HLR acknowledges the Update Location message by sending an Update Location Ack to the GLR and the GLR send it to the SGSN after the cancelling of old MM context and insertion of new MM context are finished. If the Update Location is rejected by the HLR, the SGSN rejects the Attach Request from the MS with an appropriate cause. 8) and 9) These steps are the same as the steps not involving GLR. See TS 23.060 [6]. If the Attach Request cannot be accepted, the SGSN returns an Attach Reject (IMSI, Cause) message to the MS. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 48 3G TS 23.119 version 3.0.0 Release 1999 7.3.1.4 New SGSN served by HLR, old SGSN served by GLR 6d. Insert Subscriber Data 6c. Cancel Location Ack 6b. Cancel Location 3. Identity Response 2. Identification Response 2. Identification Request 1. Attach Request 5. IMEI Check 3. Identity Request 4. Authentication 6a. Update Location 6f. Update Location Ack 6e. Insert Subscriber Data Ack MS BSS new SGSN old SGSN GGSN HLR EIR 9. Attach Complete 8. Attach Accept GLR Figure 7.3/4: GPRS Attach Procedure involving GLR (new SGSN interfaces the HLR directly. Old SGSN is under the GLR) 1) to 5) These steps are the same as the steps not involving GLR. See TS 23.060 [6]. 6) If the SGSN number has changed since the GPRS detach, or if it is the very first attach, then the SGSN informs the HLR: a) The SGSN sends an Update Location (SGSN Number, SGSN Address, and IMSI) to the HLR. b) The HLR sends Cancel Location (IMSI, Cancellation Type) to the old GLR, then the GLR sends Cancel Location (IMSI, Cancellation Type) to the old SGSN with Cancellation Type set to Update Procedure. c) The old SGSN acknowledges with Cancel Location Ack (IMSI) via the GLR. If there are any ongoing procedures for that MS, the old SGSN shall wait until these procedures are finished before removing the MM and PDP contexts. d) The HLR sends Insert Subscriber Data (IMSI, GPRS subscription data) to the new SGSN. e) The new SGSN validates the MS's presence in the (new) RA. If due to regional subscription restrictions the MS is not allowed to attach in the RA, the SGSN rejects the Attach Request with an appropriate cause, and may return an Insert Subscriber Data Ack (IMSI, SGSN Area Restricted) message to the HLR. If subscription checking fails for other reasons, the SGSN rejects the Attach Request with an appropriate cause and returns an Insert Subscriber Data Ack (IMSI, Cause) message to the HLR. If all checks are successful then the SGSN constructs an MM context for the MS and returns an Insert Subscriber Data Ack (IMSI) message to the HLR. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 49 3G TS 23.119 version 3.0.0 Release 1999 f) The HLR acknowledges the Update Location message by sending an Update Location Ack to the SGSN after the cancelling of old MM context and insertion of new MM context are finished. If the Update Location is rejected by the HLR, the SGSN rejects the Attach Request from the MS with an appropriate cause. 8) and 9) These steps are the same as the steps not involving GLR. See TS 23.060 [6]. If the Attach Request cannot be accepted, the SGSN returns an Attach Reject (IMSI, Cause) message to the MS. 7.3.1.5 Functional requirements of GLR 7.3.1.5.1 Process Update_GPRS_Location_GLR Figure 7.3/5 shows SDL chart for Process Update_GPRS_Location_GLR. Sheet1: the test “HLR update required?” takes the “yes” exit the GLR checks some flags to perform the “Location Updating Screening Function (see to section 7.1.6)” and if it is needed to update location information to the HLR. Sheet2: after the GLR sends an Update GPRS Location message to the HLR, the GLR receives the response with: - an Insert Subscriber Data message, handled by the procedure Insert_Subscriber_Data_GLR shown in subclause 7.2.1; - an Update GPRS Location ack message. If the GLR receives this message, this indicates that updating has been successfully completed. The GLR sets the "(Location and Subscriber information) LSIC by HLR" indicator to "Confirmed". The GLR send an Update GPRS Location ack message to the SGSN; - an Update GPRS Location negative response message. If the GLR receives this message, this indicates that updating has been unsuccessfully completed. The GLR sets the “(Location and Subscriber information) LSIC by HLR” indicator to “False”. The GLR sends an Update GPRS Location negative to the SGSN. Sheet3: process Cancel_GPRS_Location_Initiated_GLR is specified in subclause 7.3.1.5.4. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 50 3G TS 23.119 version 3.0.0 Release 1999 Process in the G LR to handle an Update G PRS Location request and trigger the correct application process Process Update_GPRS_Location_GLR 1(7) Signales to/from the left are to/from the SG SN Signales to/from the right are to/from the HLR Idle Update G PRS Location Check Param eter See TS 23.018 Result= Pass subscriber know n in GLR Network access m ode = G PRS Set negative response: Unknow n Subscriber Update G PRS Location negative response Idle HLR update required? New SGSN ? Super_Charged_ Cancel_Location_ GLR Result = pass? Cancel_G PRS_Location_ Initiated_GLR 1 Set GLR Num ber as SG SN N um ber Set IM-G SN address as SGSN address Update Location W ait_For_ Data Yes Yes No Yes No Yes No Yes No Yes No No Figure7.3/5(1): Process Update_GPRS_Location_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 51 3G TS 23.119 version 3.0.0 Release 1999 Process in the G LR to handle an Update GPR S Location request and trigger the correct application process Process Update_GPRS_Location_GLR 2(7) Signales to/from the left are to/from the SG SN Signales to/from the right are to/from the HLR W ait_For_ Data Insert Subscriber Data Update GPRS Location ack Update GPRS Location negative response Abort Insert_ Subscriber_ Data_GLR Result:=Pass Abort W ait_For_ Data_from _H LR_ and_ISD_ack_ from _SGSN LSIC by HLR :=Confirmed Idle Set GLR Num ber as HLR Number Update Location ack Failure C ase? Idle Result:= Roam ing Not Allowed Result:= Unknown Subscriber Result:= Procedure Error Delete Subscriber Data Delete Subscriber Data LSIC by HLR :=False Update GPRS Location negative response Idle Roam ing Not Allowed Unknown Subscriber Procedure Error Figure7.3/5(2): Process Update_GPRS_Location_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 52 3G TS 23.119 version 3.0.0 Release 1999 Process in the G LR to handle an U pdate GPR S Location request and trigger the correct application process Process Update_GPRS_Location_GLR 3(7) Signales to/from the left are to/from the SG SN Signales to/from the right are to/from the HLR W ait_For_ Data_from _HLR _ and_ISD_ack_ from _SGSN Insert Subscriber Data Update GPRS Location ack Update GPRS Location negative response Abort Insert_ Subscriber_ Data_GLR Result:=Pass Abort W ait_For_ Data_from _HLR _ and_ISD_ack_ from _SGSN LSIC by H LR :=Confirmed Idle Set GLR Number as HLR Number Update Location ack Failure Case? Idle Result:= Roam ing Not Allow ed Result:= Unknow n Subscriber Result:= Procedure Error Delete Subscriber Data Delete Subscriber Data LSIC by H LR :=False Update GPRS Location negative response Idle Roam ing Not Allow ed Unknow n Subscriber Procedure Error Figure7.3/5(3): Process Update_GPRS_Location_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 53 3G TS 23.119 version 3.0.0 Release 1999 Process in the G LR to handle an U pdate GPR S Location request and trigger the correct application process Process Update_GPRS_Location_GLR 4(7) Signals to/from the left are to/from the SG SN Signals to/from the right are to/from the HLR W ait_For_ Data_from _HLR _ and_ISD_ack_ from _SGSN Insert Subscriber Data ack Insert Subscriber D ata negative response Insert Subscriber D ata negative response Update Subscriber D ata W ait_For_ Data_from _HLR _ and_ISD_ack_ from _SGSN SGSN area restricted by regional subscription? Set SGSN area restricted Insert Subscriber Data ack W ait_For_ Data_from _HLR _ and_ISD_ack_ from _SGSN Yes No Figure7.3/5(4): Process Update_GPRS_Location_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 54 3G TS 23.119 version 3.0.0 Release 1999 Process in the G LR to handle an Update G P RS Location request and trigger the correct application process Process Update_GPRS_Location_GLR 5(7) Signales to/from the left are to/from the S G S N S ignales to/from the right are to/from the HLR 1 S uper_Charged_ Location_Updating_ G LR R esult = pass? IS D_G LR R esult = P ass? S G S N Area R estricted? Subscriber_Present_G PR S_ G LR Changed SG SN area restricted Update G P RS Location ack Idle S et G LR N um ber as SG S N N um ber Set IM -G SN address as SG SN address Update G P RS Location W ait_For_ inform ation R esult = A borted? Update G P RS Location negative response Idle Idle Update G P RS Location Idle N o Y es N o N o Y es Y es N o N o Y es Y es Figure7.3/5(5): Process Update_GPRS_Location_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 55 3G TS 23.119 version 3.0.0 Release 1999 Process in the G LR to handle an U pdate GPR S Location request and trigger the correct application process Process Update_GPRS_Location_GLR 6(7) Signales to/from the left are to/from the VLR Signales to/from the right are to/from the HLR W ait_For_ Information Insert Subscriber Data Update GPRS Location ack Update GPRS Location negative response Abort 2 Result:= Pass Abort LSIC by H LR :=True Idle Set GLR Number as HLR Num ber Failure case? Update GPRS Location ack Idle Result:= Roam ing Not Allow ed Result:= Unknow n Subscriber Result:= Procedure Error Delete Subscriber Data Delete Subscriber Data LSIC by H LR :=False Update Location negative response Idle Roam ing not Allowed Unknow n Subscriber Procedure Error Figure7.3/5(6): Process Update_GPRS_Location_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 56 3G TS 23.119 version 3.0.0 Release 1999 Process in the G LR to handle an Update GPR S Location request and trigger the correct application process Process Update_G PRS_Location_GLR 7(7) Signales to/from the left are to/from the SG SN Signales to/from the right are to/from the HLR 2 Check Parameter See TS 23.018 Result= Pass? Subscriber known? Insert Subscriber Data negative response Update Subscriber Data Idle SGSN area restricted by regional subscription? Set SGSN area restricted Insert Subscriber Data ack W ait_For_ Inform ation Yes No No Yes Yes No Figure7.3/5(7): Process Update_GPRS_Location_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 57 3G TS 23.119 version 3.0.0 Release 1999 7.3.1.5.2 Process Subscriber_Present_GPRS_GLR Figure 7.3/6 shows SDL chart for Process Subscriber_Present_GPRS_GLR. Process in the GLR Application to perform actions required for short message alerting Process Subscriber_Present_GPRS_GLR 1(1) MNRG Set? Subscriber_ Present_ GLR_AS_SGSN See TS 29.120 Section 25.4 Yes No Figure7.3/6: Process Subscriber_Present_GPRS_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 58 3G TS 23.119 version 3.0.0 Release 1999 7.3.1.5.3 Procedure Insert_Subscriber_Data_GPRS_Initiated_GLR Figure 7.3/7 shows SDL chart for Procedure Insert_Subscriber_Data_GPRS_Initiated_GLR. This procedure is initiated if HLR update is not required. Procedure in the G LR Application for handling the insertion of subscriber data into the SGSN Procedure Insert_Subscriber_D ata_G PRS_Initiated_G LR 1(1) Signals to/from the left are to/from the VLR Insert Subscriber Data Count:=1 M ore D ata To Send? Insert Subscriber Data W ait_For_ ISD_Ack Count:= Count+1 Insert Subscriber Data ack Abort Insert Subscriber Data negative response Count:= Count-1 Result:= Aborted Set N egative Response System Failure SGSN Area Restricted? Result:= Fail Set SGSN Area Restricted Count>0? W ait_For_ ISD_Ack Result := Pass Yes No Yes No Yes No Figure7.3/7: Procedure Insert_Subscriber_Data_GPRS_Initiated_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 59 3G TS 23.119 version 3.0.0 Release 1999 7.3.1.5.4 Process Cancel_GPRS_Location_Initiated_GLR Figure 7.3/8 shows SDL chart for Process Cancel_GPRS_Location_Initiated_GLR. This procedure is initiated if HLR update is not required. Process in the G LR application to initiate cancellation of location registeration in a SGSN Process Cancel_GPRS_Location_Initiated_GLR 1(1) SIgnals to/from the left are to/from the SG SN Cancel Location W ait_For_ CL_R esponse Cancel Location ack Abort Cancel Location negative response Repeat Location Cancellation? W ait for time expiry Yes No Figure7.3/8: Process Cancel_GPRS_Location_Initiated_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 60 3G TS 23.119 version 3.0.0 Release 1999 7.3.2 Detach procedure 7.3.2.1 HLR-Initiated Detach Procedure The HLR-Initiated Detach procedure is initiated by the HLR. The HLR uses this procedure for operator-determined purposes to request the removal of a subscriber’s MM and PDP contexts at the SGSN. The HLR-Initiated Detach Procedure is illustrated in Figure 7.3/9. Each step is explained in the following list. GLR MS BSS GGSN SGSN HLR 3. Delete PDP Context Request 1. Cancel Location 4. GPRS Detach Indication 2. Detach Request 6. Cancel Location Ack 3. Delete PDP Context Response 5. Detach Accept MSC/VLR Figure 7.3/9: HLR-Initiated GPRS Detach Procedure 1) If the HLR wants to request the immediate deletion of a subscriber’s MM and PDP contexts from the SGSN, the HLR shall send a Cancel Location (IMSI, Cancellation Type) message to the SGSN via GLR with Cancellation Type set to Subscription Withdrawn. 2) The SGSN informs the MS that it has been detached by sending Detach Request (Detach Type) to the MS. Detach Type shall indicate that the MS is not requested to make a new attach and PDP context activation. 3) The active PDP contexts in the GGSNs regarding this particular MS are deactivated by the SGSN sending Delete PDP Context Request (TID) messages to the GGSNs. The GGSNs acknowledge with Delete PDP Context Response (TID) messages. 4) If the MS was both IMSI- and GPRS-attached, the SGSN sends a GPRS Detach Indication (IMSI) message to the VLR. The VLR removes the association with the SGSN and handles paging and location updating without going via the SGSN. 5) The MS sends a Detach Accept message to the SGSN any time after step 2. 6) The SGSN shall confirm the deletion of the MM and PDP contexts with a Cancel Location Ack (IMSI) message via GLR. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 61 3G TS 23.119 version 3.0.0 Release 1999 7.3.2.2 Functional requirements of GLR 7.3.2.2.1 Process Cancel_GPRS_Location_GLR Figure 7.2/10 shows SDL chart for Process Cancel_GPRS_Location_GLR. This process is initiated from the HLR. Process in the G LR application to initiate cancellation of location registeration in a SG SN Process Cancel_GPR S_Location_G LR 1(1) S ignals to/from the left are to/from the SG S N S ignals to/from the right are to/from the HLR Idle Cancel Location Check P aram eter S ee TS 23.018 R esult= P ass? Super_Charger_ Cancel_Location_ G LR R esult = pass? C ancel Location W ait_For_ R esponse Cancel Location ack D elete subscriber data C ancel Location ack Idle Cancel Location negative response Cancel Location negative response Cancel Location negative response Idle Y es N o yes N o Figure7.3/10: Process Cancel_GPRS_Location_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 62 3G TS 23.119 version 3.0.0 Release 1999 7.3.3 Authentication of Subscriber Authentication procedures already defined in GSM shall be used, with the distinction that the procedures are executed from the SGSN. Additionally, the authentication procedure performs the selection of the ciphering algorithm and the synchronisation for the start of ciphering. Authentication triplets are stored in the SGSN. The MSC/VLR shall not authenticate the MS via the SGSN upon IMSI attach, nor location update, but may authenticate the MS during CS connection establishment. Security-related network functions are described in TS 33.102 [12]. The Authentication procedure is illustrated in Figure 7.3/11. Each step is explained in the following list. n 1. Send Authentication Info 2. Authentication Request 1. Send Authentication Info Ack 2. Authentication Response MS BSS GLR SGSN HLR Figure 7.3/11: Authentication Procedure 1) If the SGSN does not have previously stored authentication triplets, a Send Authentication Info (IMSI) is sent to the GLR, which the GLR sends to the HLR without modification at the application layer. The HLR responds with Send Authentication Info Ack (Authentication Triplets). Each Authentication Triplet includes RAND, SRES and Kc. 2) The SGSN sends Authentication Request (RAND, CKSN, and Ciphering Algorithm). The MS responds with Authentication Response (SRES). The MS starts ciphering after sending the Authentication Response message. The SGSN starts ciphering when a valid Authentication Response is received from the MS. 7.3.4 Inter SGSN Routeing Area Update Procedure [Editor’s note] This procedure may be replaced with inter SGSN SRNS relocation procedure. [Editor’s note] This procedure may not need to be detailed, because the part of this procedure between SGSN and HLR is the same as the part of Attach procedure. The Inter SGSN Routeing Area Update procedure is illustrated in Figure 7.3/12. Each step is explained in the following list. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 63 3G TS 23.119 version 3.0.0 Release 1999 MS BSS new SGSN GLR GGSN old SGSN 2. SGSN Context Response 3. Security Functions 1. Routeing Area Update Request 2. SGSN Context Request 6. Update PDP Context Request 6. Update PDP Context Response 7. Update Location 10. Update Location Ack 11. Routeing Area Update Accept 8. Cancel Location 8. Cancel Location Ack 9. Insert Subscriber Data Ack 9. Insert Subscriber Data 12. Routeing Area Update Complete 5. Forward Packets 4. SGSN Context Acknowledge HLR Figure 7.3/12: Inter SGSN Routeing Area Update Procedure 1) The MS sends a Routeing Area Update Request (old RAI, old P-TMSI Signature, and Update Type) to the new SGSN. Update Type shall indicate RA update or periodic RA update. The BSS shall add the Cell Global Identity including the RAC and LAC of the cell where the message was received before passing the message to the SGSN. 2) The new SGSN sends SGSN Context Request (old RAI, TLLI, old P-TMSI Signature, and New SGSN Address) to the old SGSN to get the MM and PDP contexts for the MS. The old SGSN validates the old P-TMSI Signature and responds with an appropriate error cause if it does not match the value stored in the old SGSN. This should initiate the security functions in the new SGSN. If the security functions authenticate the MS correctly, the new SGSN shall send an SGSN Context Request (old RAI, TLLI, MS Validated, and New SGSN Address) message to the old SGSN. MS Validated indicates that the new SGSN has authenticated the MS. If the old P-TMSI Signature was valid or if the new SGSN indicates that it has authenticated the MS, the old SGSN responds with SGSN Context Response (MM Context, PDP Contexts, and LLC Ack). If the MS is not known in the old SGSN, the old SGSN responds with an appropriate error cause. The old SGSN stores New SGSN Address, to allow the old SGSN to forward data packets to the new SGSN. LLC Ack contains the acknowledgements for each LLC connection used by the MS. Each PDP Context includes the GTP sequence number for the next downlink N-PDU to be sent to the MS and the GTP sequence number for the next uplink N-PDU to be tunnelled to the GGSN. The old SGSN starts a timer and stops the transmission of N-PDUs to the MS. 3) Security functions may be executed. These procedures are defined in subclause "Security Function". Ciphering mode shall be set if ciphering is supported. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 64 3G TS 23.119 version 3.0.0 Release 1999 4) The new SGSN sends an SGSN Context Acknowledge message to the old SGSN. This informs the old SGSN that the new SGSN is ready to receive data packets belonging to the activated PDP contexts. The old SGSN marks in its context that the MSC/VLR association and the information in the GGSNs and the GLR are invalid. This triggers the MSC/VLR, the GGSNs, and the GLR to be updated if the MS initiates a routeing area update procedure back to the old SGSN before completing the ongoing routeing area update procedure. If the security functions do not authenticate the MS correctly, then the routing area update shall be rejected, and the new SGSN shall send a reject indication to the old SGSN. The old SGSN shall continue as if the SGSN Context Request was never received. 5) The old SGSN duplicates the buffered N-PDUs and starts tunnelling them to the new SGSN. Additional N-PDUs received from the GGSN before the timer described in step 2 expires are also duplicated and tunnelled to the new SGSN. N-PDUs that were already sent to the MS in acknowledged mode and that are not yet acknowledged by the MS are tunnelled together with the number of the LLC frame that transferred the last segment of the N-PDU. No N-PDUs shall be forwarded to the new SGSN after expiry of the timer described in step 2. 6) The new SGSN sends Update PDP Context Request (new SGSN Address, TID, and QoS Negotiated) to the GGSNs concerned. The GGSNs update their PDP context fields and return Update PDP Context Response (TID). 7) The new SGSN informs the GLR of the change of SGSN by sending Update Location (SGSN Number, SGSN Address, and IMSI) to the GLR. 8) The GLR sends Cancel Location (IMSI, Cancellation Type) to the old SGSN with Cancellation Type set to Update Procedure. If the timer described in step 2 is not running, then the old SGSN removes the MM and PDP contexts. Otherwise, the contexts are removed only when the timer expires. This allows the old SGSN to complete the forwarding of N-PDUs. It also ensures that the MM and PDP contexts are kept in the old SGSN in case the MS initiates another inter SGSN routeing area update before completing the ongoing routeing area update to the new SGSN. The old SGSN acknowledges with Cancel Location Ack (IMSI). 9) The GLR sends Insert Subscriber Data (IMSI, GPRS subscription data) to the new SGSN. The new SGSN validates the MS's presence in the (new) RA. If due to regional subscription restrictions the MS is not allowed to be attached in the RA, the SGSN rejects the Routeing Area Update Request with an appropriate cause, and may return an Insert Subscriber Data Ack (IMSI, SGSN Area Restricted) message to the GLR. If all checks are successful then the SGSN constructs an MM context for the MS and returns an Insert Subscriber Data Ack (IMSI) message to the GLR. 10)The GLR acknowledges the Update Location by sending Update Location Ack (IMSI) to the new SGSN. 11)The new SGSN validates the MS's presence in the new RA. If due to roaming restrictions the MS is not allowed to be attached in the SGSN, or if subscription checking fails, then the new SGSN rejects the routeing area update with an appropriate cause. If all checks are successful then the new SGSN constructs MM and PDP contexts for the MS. A logical link is established between the new SGSN and the MS. The new SGSN responds to the MS with Routeing Area Update Accept (P-TMSI, LLC Ack, and P-TMSI Signature). LLC Ack contains the acknowledgements for each LLC connection used by the MS, thereby confirming all mobile-originated N-PDUs successfully transferred before the start of the update procedure. 12)The MS acknowledges the new P-TMSI with a Routeing Area Update Complete (P-TMSI, LLC Ack). LLC Ack contains the acknowledgements for each LLC connection used by the MS, thereby confirming all mobile- terminated N-PDUs successfully transferred before the start of the update procedure. If LLC Ack confirms reception of N-PDUs that were forwarded from the old SGSN, then these N-PDUs shall be discarded by the new SGSN. LLC and SNDCP in the MS are reset. In the case of a rejected routeing area update operation, due to regional subscription or roaming restrictions, the new SGSN shall not construct an MM context. A reject shall be returned to the MS with an appropriate cause. The MS shall not re-attempt a routeing area update to that RA. The RAI value shall be deleted when the MS is powered-up. If the SGSN is unable to update the PDP context in one or more GGSNs, then the SGSN shall deactivate the corresponding PDP contexts as described in subclause "PDP Context Deactivation Initiated by SGSN Procedure". This shall not cause the SGSN to reject the routeing area update. If the timer described in step 2 expires and no Cancel Location (IMSI) was received from the GLR, then the old SGSN shall stop forwarding N-PDUs to the new SGSN. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 65 3G TS 23.119 version 3.0.0 Release 1999 If the routeing area update procedure fails a maximum allowable number of times, or if the SGSN returns a Routeing Area Update Reject (Cause) message, the MS shall enter IDLE state. 7.3.5 Subscriber Management Procedures Whenever the GPRS subscription data is changed for a GPRS subscriber in the HLR, and the changes affect the GPRS subscription data stored in the SGSN, then the SGSN node shall be informed about these changes by means of the following procedures: - Insert Subscriber Data procedure, used to add or modify GPRS subscription data in the SGSN; or - Delete Subscriber Data procedure, used to remove GPRS subscription data in the SGSN. 7.3.5.1 Insert Subscriber Data Procedure In addition to the insertion and modification of general GPRS subscription data for a GPRS subscriber, see TS 29.002 [10], the HLR may request the insertion or modification of one or several new or existing PDP contexts in the SGSN. The Insert Subscriber Data procedure is illustrated in Figure 7.3/13. Each step is explained in the following list. 1. Insert Subscriber Data 2. Insert Subscriber Data Ack GLR HLR 1. Insert Subscriber Data 2. Insert Subscriber Data Ack SGSN Figure 7.3/13: Insert Subscriber Data Procedure 1) The HLR sends an Insert Subscriber Data (IMSI, GPRS Subscription Data) message to the GLR. The GLR updates its GPRS subscription data and sends an Insert Subscriber Data (IMSI, GPRS Subscription Data) message to the SGSN. 2) The SGSN updates its GPRS subscription data and acknowledges the Insert Subscriber Data message by returning an Insert Subscriber Data Ack (IMSI) message. The GLR receives the ack message, then it sends the Insert Subscriber Data Ack (IMSI) message to the HLR. For each PDP context that is included in GPRS Subscription Data the SGSN shall check whether it is a new, an active, or an inactive PDP context: - For a new or inactive PDP context, no further action is required except storage in the SGSN. - For an active PDP context, the SGSN shall in addition compare the new QoS Subscribed with QoS Negotiated and shall, if necessary, initiate a PDP Context Modification procedure as described in subclause "Modification Procedures". Furthermore, if VPLMN Address Allowed is changed, the SGSN shall, if necessary (e.g., if the PDP context is currently routed via a GGSN in the VPLMN and VPLMN Address Allowed is changed to not allowed), initiate a PDP Context Deactivation procedure as explained in subclause "Deactivation Procedures". ETSI ETSI TS 123 119 V3.0.0 (2000-03) 66 3G TS 23.119 version 3.0.0 Release 1999 7.3.5.2 Delete Subscriber Data Procedure In addition to the deletion of general GPRS subscription data for a GPRS subscriber, see TS 29.002 [10], the HLR may request the deletion of one or several PDP contexts from the SGSN. The Delete Subscriber Data procedure is illustrated in Figure 7.3/14. Each step is explained in the following list. 1. Delete Subscriber Data 2. Delete Subscriber Data Ack GLR HLR 1. Delete Subscriber Data 2. Delete Subscriber Data Ack SGSN Figure 7.3/14: Delete Subscriber Data Procedure 1) The HLR sends a Delete Subscriber Data (IMSI, PDP Context Identifiers List) message to the GLR. The GLR deletes its PDP Context indicated and sends an Insert Subscriber Data (IMSI, PDP Context Identifiers List) message to the SGSN. 2) The SGSN acknowledges the Delete Subscriber Data message by returning a Delete Subscriber Data Ack (IMSI) message. For each PDP context identifier included in PDP Context Identifiers List, the SGSN shall check whether it belongs to an active or an inactive PDP context: - For an inactive PDP context no further action is required except deletion of the PDP context. - For an active PDP context, the SGSN shall initiate the PDP Context Deactivation Initiated by SGSN procedure as explained in subclause "Deactivation Procedures" before the PDP context is deleted. 7.3.6 PDP Context Activation Procedure 7.3.6.1 Successful Network-Requested PDP Context Activation Procedure with GLR The Successful Network-Requested PDP Context Activation procedure is illustrated in Figure 7.3/15. Each step is explained in the following list. MS SGSN IM-GSN 3. PDU Notification Request GLR 3. Send Routeing Info for GPRS 3. Send Routeing Info for GPRS Ack 4. Request PDP Context Activation 5. PDP Context Activation procedure 3. PDU Notification Response GGSN HLR 1. PDP PDU 2. Send Routeing Info for GPRS 2. Send Routeing Info for GPRS Ack 3. PDU Notification Request 3. PDU Notification Response Figure 7.3/15: Successful Network-Requested PDP Context Activation Procedure ETSI ETSI TS 123 119 V3.0.0 (2000-03) 67 3G TS 23.119 version 3.0.0 Release 1999 1) When receiving a PDP PDU the GGSN determines if the Network-Requested PDP Context Activation procedure has to be initiated. The GGSN may store subsequent PDUs received for the same PDP address. 2) The GGSN may send a Send Routeing Information for GPRS (IMSI) message to the HLR. If the HLR determines that the request can be served, it returns a Send Routeing Information for GPRS Ack (IMSI, SGSN Address, Mobile Station Not Reachable Reason) message to the GGSN. The SGSN Address parameter includes actually the value of the IM-GSN Address. The Mobile Station Not Reachable Reason parameter is included if the MNRG flag is set in the HLR. The Mobile Station Not Reachable Reason parameter indicates the reason for the setting of the MNRG flag as stored in the MNRR record (see TS 23.040 [5]). If the MNRR record indicates a reason other than 'No Paging Response', the HLR shall include the GGSN number in the GGSN-list of the subscriber. - If the HLR determines that the request cannot be served (e.g., IMSI unknown in HLR), the HLR shall send a Send Routeing Information for GPRS Ack (IMSI, MAP Error Cause) message. Map Error Cause indicates the reason for the negative response. 3) If the SGSN address is present and either Mobile Station Not Reachable Reason is not present or Mobile Station Not Reachable Reason indicates 'No Paging Response', the GGSN shall send a PDU Notification Request (IMSI, PDP Type, PDP Address) message to the IM-GSN indicated by the HLR. Otherwise, the GGSN shall set the MNRG flag for that MS. The IM-GSN sends a Send Routeing Information for GPRS (IMSI) message to the GLR. If the GLR determines that the request can be served, it returns a Send Routeing Information for GPRS Ack (IMSI, SGSN Address, Mobile Station Not Reachable Reason) message to the IM-GSN. If the SGSN address is present and either Mobile Station Not Reachable Reason is not present or Mobile Station Not Reachable Reason indicates 'No Paging Response', the IM-GSN shall send a PDU Notification Request (IMSI, PDP Type, PDP Address) message to the SGSN indicated by the GLR. The SGSN returns a PDU Notification Response (Cause) message to the GGSN via the IM-GSN in order to acknowledge that it shall request the MS to activate the PDP context indicated with PDP Address. 4) The SGSN sends a Request PDP Context Activation (TI, PDP Type, and PDP Address) message to request the MS to activate the indicated PDP context. 5) The PDP context is activated with the PDP Context Activation procedure (see subclause "PDP Context Activation Procedure" in 3G TS 23.060 [6]). 7.3.6.2 Unsuccessful Network-Requested PDP Context Activation Procedure with GLR If the PDP context requested by the GGSN cannot be established, the SGSN sends a PDU Notification Response (Cause) or a PDU Notification Reject Request (IMSI, PDP Type, PDP Address, Cause) message to the GGSN depending on whether the context activation fails before or after the SGSN has sent a Request PDP Context Activation message to the MS. Cause indicates the reason why the PDP context could not be established: - 'IMSI Not Known'. The SGSN has no MM context for that IMSI (Cause in PDU Notification Response). - 'MS GPRS Detached'. The MM state of the MS is IDLE (Cause in PDU Notification Response). - 'MS Not GPRS Responding'. The MS is GPRS-attached to the SGSN but the MS does not respond. This may be due to: - the lack of a response to a GPRS Paging Request; - an Abnormal RLC condition, or - no Activate PDP Context Request message received within a certain time after the Request PDP Context Activation message was delivered to the MS (Cause in PDU Notification Reject Request). - 'MS Refuses'. The MS refuses explicitly the network-requested PDP context (Cause in PDU Notification Reject Request). When receiving the PDU Notification Response or the PDU Notification Reject Request message the GGSN may reject or discard the PDP PDU depending on the PDP type. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 68 3G TS 23.119 version 3.0.0 Release 1999 After an unsuccessful Network-Requested PDP Context Activation procedure the network may perform some actions to prevent unnecessary enquires to the HLR. The actions taken depend on the cause of the delivery failure. - If the MS is not reachable or if the MS refuses the PDP PDU (Cause value 'MS Not GPRS Responding' or 'MS Refuses'), then the SGSN shall not change the setting of MNRG for this MS. The GGSN may refuse any PDP PDU for that PDP address during a certain period. The GGSN may store the SGSN address during a certain period and send subsequent PDU Notification Request messages to that SGSN via IM-GSN. - If the MS is GPRS-detached or if the IMSI is not known in the SGSN (Cause value 'MS GPRS Detached' or 'IMSI Not Known'), then the SGSN, the GGSN, and the HLR may perform the Protection and Mobile User Activity procedures. The Protection procedure is illustrated in Figure 7.3/16. Each step is explained in the following list. IM-GSN HLR GGSN 1. PDU Notification Response 3. Send Routeing Info for GPRS 3. Send Routeing Info for GPRS Ack 4. Failure Report 4. Failure Report Ack 2. PDU Notification Reject Response 2. PDU Notification Reject Request SGSN GLR 3. Send Routeing Info for GPRS 3. Send Routeing Info for GPRS Ack 4. Failure Report 4. Failure Report Ack 1. PDU Notification Response 2. PDU Notification Reject Response 2. PDU Notification Reject Request Figure 7.3/16: Protection Procedure 1) If the MM context of the mobile is IDLE or if the SGSN has no information about that user, the SGSN returns a PDU Notification Response (Cause) message to the GGSN via IM-GSN with Cause equal to 'MS GPRS Detached' or 'IMSI Not Known', otherwise the Cause shall be 'Activation Proceeds'. If the Cause is 'MS GPRS Detached' or 'IMSI Not Known' and if the SGSN has an MM context for that user, the SGSN sets MNRG to indicate the need to report to the HLR when the next contact with that MS is performed. 2) If the MS does not respond or refuses the activation request, the SGSN sends a PDU Notification Reject Request (IMSI, PDP Type, PDP Address, Cause) message to the GGSN via IM-GSN with Cause equal to 'MS Not GPRS Responding' or 'MS Refuses'. The GGSN returns a PDU Notification Reject Response message to the SGSN via IM-GSN. 3) If Cause equals 'IMSI Not Known' the IM-GSN may send a Send Routeing Information for GPRS (IMSI) message to the GLR before sending the PDP Notification response to GGSN. The GLR returns a Send Routeing Information for GPRS Ack (IMSI, SGSN Address, and Cause) message to the IM-GSN indicating the address of the SGSN that currently serves the MS. If SGSN Address is different from the one previously stored by the IM- GSN, then steps 3, 4, and 5 in Figure 6 are followed. If Cause equals 'IMSI Not Known' the GGSN may send a Send Routeing Information for GPRS (IMSI) message to the HLR. The HLR returns a Send Routeing Information for GPRS Ack (IMSI, SGSN Address, Cause) message to the GGSN (Note that the SGSN Address parameter includes actually the value of the IM-GSN Address.) indicating the address of the IM-GSN that currently serves the MS. If IM-GSN Address is different from the one previously stored by the GGSN, then steps 3, 4, and 5 in Figure 6 are followed. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 69 3G TS 23.119 version 3.0.0 Release 1999 4) If SGSN Address is the same as the one previously stored in the IM-GSN or if the Cause value returned in step 1 equals 'MS GPRS Detached', then the IM-GSN sets MNRG for that PDP address and sends a Failure Report (IMSI) message to the GLR to request MNRG to be set in the GLR. The GLR sets (if not already set) MNRG for the IMSI. Note that GLR does not store IM-GSN address and IM-GSN address to report to when activity from that IMSI is detected, and IM-GSN forgets the SGSN address after receiving PDU notification response or sending PDU notification reject response. If IM-GSN Address is the same as the one previously stored in the GGSN, or if the Cause value returned in step 1 equals 'MS GPRS Detached', then the GGSN sets MNRG for that PDP address and sends a Failure Report (IMSI, GGSN Number, GGSN Address) message to the HLR to request MNRG to be set in the HLR. The HLR sets (if not already set) MNRG for the IMSI and adds GGSN Number and GGSN Address to the list of GGSNs to report to when activity from that IMSI is detected. GGSN Number is either the number of the GGSN, or, if a protocol converting GSN is used as an intermediate node, the number of the protocol-converting GSN. GGSN Address is an optional parameter that shall be included if a protocol-converting GSN is used. The Mobile User Activity procedure is illustrated in Figure 7.3/17. Each step is explained in the following list. 3. Note MS GPRS Present SGSN GLR GGSN 1. Attach Request 2a. Ready for SM 2b. Update Location MS HLR 2a. Ready for SM 2b. Update Location 2c. Ready for SM Figure 7.3/17: Mobile User Activity Procedure 1) The SGSN receives an indication that an MS is reachable, e.g., an Attach Request message from the MS. 2a)If the SGSN contains an MM context of the MS and MNRG for that MS is set, the SGSN shall send a Ready for SM (IMSI, MS Reachable) message to the GLR and clears MNRG for that MS. The GLR sends it without modification at the application level to HLR and clears MNRG for that MS. 2b)If the SGSN does not keep the MM context of the MS, the SGSN shall send an Update Location message (see subclause "Attach Function") to the GLR. If the GLR does not keep the MM context of the MS, the SGSN shall send an Update Location message (see subclause "Attach Function") to the HLR. 2c) If the GLR contains an MM context of the MS and MNRG for that MS is set, the SGSN shall send a Ready for SM (IMSI, MS Reachable) message to the HLR and clears MNRG for that MS. 3) When the HLR receives the Ready for SM message or the Update Location message for an MS that has MNRG set, it clears MNRG for that MS and sends a Note MS GPRS Present (IMSI, SGSN Address) message to all the GGSNs in the list of the subscriber. (The Ready for SM message also triggers the SMS alert procedure as described in subclause "Unsuccessful Mobile-terminated SMS Transfer".) SGSN Address contains the address of the IM-GSN that currently serves the MS. Upon reception of Note MS Present, each GGSN shall clear MNRG. 7.4 Purge MS Procedure This Purge MS procedure is used to cause the HLR to mark its data for an MS so that any request for routing information for a mobile terminated call, a mobile terminated short message or Network-requested PDP context activation will be treated as if the MS is not reachable. It is invoked when the subscriber record for the MS is to be deleted in the VLR or SGSN, either by MMI interaction or automatically, e.g. because the MS has been inactive for several days. This procedure is illustrated in figure 7.4/1. Each step is explained in the following list. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 70 3G TS 23.119 version 3.0.0 Release 1999 GLR HLR Visited NW Home NW VLR or SGSN 1. Purge MS 2. Purge MS 3. Purge MS ack 4. Purge MS ack Figure 7.4/1: Purge MS procedure Procedure: 1) The serving node, i.e., the VLR or the SGSN, sends a Purge MS message to the GLR. 2) When the GLR receives the Purge MS message from the serving node, it checks whether the subscriber is registered. If the subscriber is not registered, the GLR may report an error to the O&M interface, and sends back a negative response to the serving node. If the subscriber is registered, the GLR checks whether the purging notification came from the serving node where the MS was last registered. - If the serving node that sent the purge MS request is the registered serving node, the GLR transports the received message to the HLR. - If the serving node that sent the purge MS request is not the registered serving node, the GLR sends a purge MS ack to the serving node indicating that the TMSI or P-TMSI shall not be frozen. 3) When the GLR receives the response from the HLR, the GLR deletes the subscriber data and transports the received message to the serving node. 4) The serving node receives the Purge MS ack message indicating successful outcome of the procedure. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 71 3G TS 23.119 version 3.0.0 Release 1999 7.4.1 Functional requirements of GLR 7.4.1.1 Process Purge_MS_GLR Figure 7.4/2 shows SDL chart for Process Purge_MS_GLR. G LR application process for Purge M S. Process Purge_MS_GLR 1(2) S ignals from/to left are from /to VLR or SG SN . S ignals from/to right are from/to HLR. Idle P urge M S from V LR o r SG S N Check P arameter S ee TS 23.018 Result= P ass? S ubscriber registered? P urge MS indication came from the registered serving node P urge MS from V LR ? S et negative response := S ubscriber unknow n. S et G LR N um ber as S GS N Num ber S et G LR N um ber as V LR N umber P urge MS ack Don't set Flag Freeze TM S I or P-TM S I P urge MS negative response P urge MS Idle W ait_For_ Response Yes No Yes No Yes No No Yes Figure 7.4/2(1): Process Purge_MS_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 72 3G TS 23.119 version 3.0.0 Release 1999 G LR application process for Purge M S. Process Purge_MS_GLR 2(2) S ignals from /to left are from /to VLR or SG SN . S ignals from /to right are from/to H LR . W ait_For_ Response P urge M S ack P urge MS negative response P urge MS from V LR ? delete subscriber data for P S delete subscriber data for CS S end as it is received from the HLR. P urge M S ack A bort Idle No Yes Figure 7.4/2(2): Process Purge_MS_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 73 3G TS 23.119 version 3.0.0 Release 1999 7.5 Regional Restriction Procedure In the case that GLR is introduced, during second and subsequent location updating, there is no interaction between the GLR and the HLR. However, the regional restriction service needs the location updating procedure towards the HLR. The GLR stores the Zone Code List sent by the HLR in the Insert Subscriber Data message. On the location updates the GLR sends its stored Zone Code list to the VLR and/or SGSN (refer to figure 7.2/10). The GLR stores also the MSC area restricted flag and/or the SGSN are restricted flag. These flags are set “False” if the location updating procedure executed successfully. When the GLR receives the Insert Subscriber Data Acknowledge message indicating “MSC area restricted” or “SGSN area restricted” and the MSC area restricted flag or the SGSN area restricted flag is set as “False”, the GLR initiates the location updating procedure toward the HLR. In addition, the GLR sets the MSC area restricted flag or the SGSN area restricted flag “True”. Also, the HLR sets the MSC area restricted flag or the SGSN area restricted flag “True”, and the location updating for the IMSI is rejected. These flags contribute to the “MS Not Reachable” state for handling of terminating traffic (i.e. mobile terminated call and mobile terminated SMS and so on) in the HLR. GLR HLR 1. Update Location or Update GPRS Location 2. Update Location or Update GPRS Location 3. Insert Subscriber Data (Zone Code List) Second and Further Location Updating 12. Update Location ack or Update GPRS Location ack (Rejected) Visited NW Home NW Store Zone Code List 4. Insert Subscriber Data (Zone Code List) Aware of whole new MSC area restricted old VLR/ old SGSN new VLR/ new SGSN 5. Update Location or Update GPRS Location 6. Insert Subscriber Data (Zone Code List) 7. Insert Subscriber Data ack (MSC area restricted) “the MSC area restricted flag” is set First Location Updating 9. Insert Subscriber Data 10. Insert Subscriber Data ack (MSC area restricted) Identifies restricted and Decides to initiate UL 8. Update Location or Update GPRS Location 11. Update Location ack or Update GPRS Location ack (Rejected) Figure 7.5/1: Regional Restriction Procedure (MS Enters a restricted Area) ETSI ETSI TS 123 119 V3.0.0 (2000-03) 74 3G TS 23.119 version 3.0.0 Release 1999 When the GLR receives the Insert Subscriber Data Acknowledge message indicating “MSC area restricted” or “SGSN area restricted” and the MSC area restricted flag or the SGSN area restricted flag is set as “True”, The GLR reject the location updating procedure for the IMSI. No interaction with the HLR is needed. When the user returns to an MSC area that is not restricted due to regional subscription (see figure 7.2/11), i.e., when the GLR receives the Insert Subscriber Data Acknowledge message NOT indicating “MSC area restricted” or “SGSN area restricted” and the MSC area restricted flag or the SGSN area restricted flag is set as “True”, the GLR initiates the location updating procedure toward the HLR. GLR HLR 8. Update Location ack Visited NW Home NW Aware of Not whole new MSC area restricted VLROLD VLRNEW 1. Update Location 2. Insert Subscriber Data (Zone Code List) 3. Insert Subscriber Data ack “the MSC area restricted flag” is cleared 4. Update Location 5. Insert Subscriber Data 6. Insert Subscriber Data ack 7. Update Location ack Identifies No more restricted and Decides to initiate UL The Regional Restriction Procedure was initiated on location updating In the previously visited VLR Figure 7.5/2: Regional Restriction Procedure (MS leaves the restricted area) 7.6 Recovery and Restoration The recovery and restoration procedures are intended to maintain service if inconsistencies in databases occur and at lost or invalid database information. "Invalid" in this context means that the database entry cannot be regarded as reliable. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 75 3G TS 23.119 version 3.0.0 Release 1999 7.6.1 GLR Failure A consequence of GLR restart is that an Update Location has to be performed for all roaming subscribers within the VPLMN. The GLR will keep a part of the IMSI record in non-volatile memory by periodical backup. If the IMSI record in main memory is lost or broken by restart, it is retrieved from non-volatile backup memory as in HLR. This backup data would contain enough information to send “Provide Roaming Number” message to the VLR when it is requested by the HLR. The data which shall be stored in backed-up would be “VLR number”, “SGSN number”, “IMSI”. In case of GLR restart, it sends “Reset” message including the GLR number as the HLR number to VLR/SGSN where one or more of its mobile terminals are registered to prompt location updating attempt from VLR/SGSN. On receiving the location updating request, the GLR relays it to the HLR to restore its location and subscriber data. The restoration trigger can be the normal location updating from mobile terminal, call origination and call termination and so on. The assumption in the case of terminating call in circuit switched service is that GLR would have VLR number in non- volatile memory so that it could know the exact VLR mobile terminal registered. If GLR loses VLR number or has only old VLR number, it loses the opportunity to restore its data at the timing of terminating call. This situation is the same as the case of HLR that loses VLR number after restart. Also in this case, GLR shall have an indicator representing restart of GLR. This indicator is set “Not Confirmed” when GLR restarts, and kept the status until subscriber profile is successfully downloaded from HLR. This shall be triggered by radio contact of the mobile terminal. The restoration indicator is called the “Location and Subscriber information Confirmed by HLR” (LSIC) and defined as follows: If the LSIC is set to “Not confirmed,” the GLR send Update Location message to HLR. “Location and Subscriber information confirmed by HLR” is set to “Not Confirmed” at any of following events: - The GLR receives an “Update Location” request for an MS for which the GLR has no IMSI records. - The GLR receives a “Reset” message from the HLR with which the MS is registered. - The GLR detects the restart of itself and the IMSI record does not seem to be guaranteed (e.g. data retrieved from backup non-volatile memory). “Location and Subscriber information confirmed by HLR” is set to “Confirmed” at any of following events: - The GLR successfully performs an “Update Location” to the HLR. The recovery procedure of GLR Failure is illustrated in Figure 7.6/1. Each step is explained in the following list. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 76 3G TS 23.119 version 3.0.0 Release 1999 HLR 3. Insert Subscriber Data VLR or SGSN 2. Update Location or Restore Data 3. Insert Subscriber Data ack GLR 4. Update Location ack or Restore Data ack 2. Update Location or Restore Data The VLR/SGSN received Mobile Originated Activity/Location Updating Request or Mobile Terminated Request 1. Reset 3. Insert Subscriber Data 4. Update Location ack or Restore Data ack 3. Insert Subscriber Data ack Restart Figure 7.6/1: Recovery of the GLR Procedure: 1. After restart of the GLR it sets the “LSIC” “not confirmed” and sends the Reset message to the VLR and/or SGSN. The VLR sets the indicator “Location Information Confirmed in HLR” of affected user “not confirmed” and waits for access from/to the user. 2. After identifying access from the user and successful authentication the VLR or SGSN sends Update Location message to the GLR. After identifying access to the user and successful authentication the VLR or SGSN sends Restore data message to the GLR. If the GLR identifies the “LSIC” set in “Not Confirmed”, it relays the message to the HLR. 3. When the HLR receives the Update Location or Restore Data message from the GLR, it initiates insert subscriber procedure. During the procedure the GLR relay messages. 4. After the insert subscriber procedure, the HLR returns Update Location ack or Restore Data ack message to the VLR via the GLR. When the VLR and the GLR receives the message, each indicator in both nodes is set “confirmed”. 7.6.2 HLR Failure In the case of HLR restart when the GLR receives a reset message from a HLR, it marks all subscriber records for which the HLR number matches the HLR number received in the reset message. This indicates that when the MS next makes radio contact the GLR needs to initiate a location registration procedure to the HLR. If the HLR included an HLR-ID list in the reset message, then only those subscriber records for which the leading digits of the IMSI match one of the HLR-IDs in the HLR-ID list will be marked. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 77 3G TS 23.119 version 3.0.0 Release 1999 Then the GLR sends a RESET message, which includes the GLR number as the HLR number and HLR-ID list if the GLR received it from the HLR, to the serving node (i.e. VLR or SGSN). The receiving serving node may use the HLR number or HLR-ID list (if present) to identify the affected users. In the case that the serving node uses the HLR number, it regards the users as affected, whose subscriber record stores the number as HLR number equal to the received GLR number. On the other hand in the case that the serving node uses the HLR-ID list, it regards the users as affected, whose IMSI has the leading digits equal to one of HLR-IDs. After that when the affected user accesses the network, the serving node initiates a location registration procedure to the GLR. When the GLR receives an Update Location message from the serving node and identifies that the subscriber record in the GLR is marked as needing to notify the HLR when the MS makes radio contact then the GLR sends the Update Location message to the HLR. The recovery procedure of HLR Failure is illustrated in Figure 7.6/2. Each step is explained in the following list. HLR 4. Insert Subscriber Data Visited NW VLR Restart GLR 3. Update Location 1. Reset (HLR No, HLR id List(*)) 4. Insert Subscriber Data ack 6. Update Location ack Home NW 4. Insert Subscriber Data 4. Insert Subscriber Data ack 2. Reset (GLR No, HLR id List(*)) The VLR received Mobile Originated Activity/Location Updating Request Or Mobile Terminated Request 3. Update Location 6. Update Location ack 5. Forward Check SS ind 5. Forward Check SS ind Optional for Mark subscriber records for all affected users Identify this registration comes form affected user (*) This parameter is optionally provided by HLR CS domain Figure 7.6/2: Recovery procedure of HLR Failure Procedure: 1. When the HLR restart occurs and the GLR receives a RESET message, the GLR identifies affected users by received HLR number and sets the indicator (“LSIC”) “not confirmed” for the users. If the HLR included an HLR –ID list in the reset message, then only those subscriber records for which the leading digits of the IMSI match one of the HLR-IDs in the HLR-ID list will be marked. 2. The GLR sends reset messages to the serving node where the affected users are roaming. The reset message includes the GLR number as HLR number and HLR-ID list if the GLR receives it from the HLR. Receiving serving node may regard the users as affected by HLR number or HLR-ID list (if present). ETSI ETSI TS 123 119 V3.0.0 (2000-03) 78 3G TS 23.119 version 3.0.0 Release 1999 3. When the affected user accesses the network, the serving node initiates an update location procedure to the GLR. If the GLR identifies that the indicator (“LSIC”) set to “not confirmed” for the user, it relays the message to the HLR. 4. When the HLR receives the Update Location message, it initiates the insert subscriber data procedure. During the procedure the GLR relays the messages between the serving node and HLR transparently. 5. If the HLR implements Forward Check SS indication, it sends the Forward Check SS ind message to the GLR and the GLR relays the message to the VLR. (implemented only for CS domain). 6. When the serving node receives the Update Location ack message, the restoration procedure is completed. 7.6.2.1 Suppression of Intra-PLMN signalling During the HLR restoration procedure involving the GLR, the GLR notifies the GLR number as the HLR number to the serving node in a Reset message. Therefore, in case the serving node does not use the HLR-ID list (i.e. the case that HLR did not send the HLR-ID list to the serving node via GLR or the case that the serving node does not support the usage of the HLR-ID list), the serving node regards all users accommodated into the GLR as affected. This leads to the unnecessary location updates for the restoration of the users not from the restarting HLR. To suppress this unnecessary signalling within VPLMN some mechanism as shown in following subsections may be used. 7.6.2.1.1 Usage of the HLR id List (Tool 1) In this tool the GLR generates HLR-ID list, which is composed of MCC+MNC, by translating the CC and NDC of the HLR and sends it to the serving node in the Reset message. On receiving the HLR-ID list the serving node may or may not use this. If the serving node uses the HLR-ID list and identifies HPLMN where the restarting HLR exists, no unnecessary signaling traffic for the users from the other PLMNs occurs. 7.6.2.1.2 Multiple GLR number allocation (Tool 2) In this tool the GLR has multiple GLR numbers corresponding to each HLR. The numbers, which can be routed to the GLR, are allocated as multiple GLR numbers. The correspondence between HLR numbers and GLR numbers is statistically kept in the non-volatile memory. See Figure 7.6/3. HLR#2 HLR#1 HLR#3 … HLR#n GLR #A #B #c #C VLR#1 VLR#2 Reset #1 Reset #A Multiple GLR numbers Reset #A HLR-GLR number Correspondence Table HLR# GLR# #1 #A #2 #B #3 #C Figure 7.6/3: Multiple GLR number allocation Possible scenarios for GLR number allocation are as follows. In this tool, if one GLR number is allocated for one HLR and VPLMN has the roaming agreements with many PLMNs, many GLR numbers are needed. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 79 3G TS 23.119 version 3.0.0 Release 1999 As possible variation of scenario, a GLR number may be assigned to a group of HLRs. This group can be grouped by, for instance, country code or network destination code and so on. If one GLR number is assigned for many HLRs, the occupied address space is small, however the unnecessary signalling traffic for the users not associated to restarting HLR increases. On the other hand, if one GLR number is assigned for few HLRs, the unnecessary signalling traffic is small, however the occupied address space is larger. How many HLRs are grouped is operator dependent. 7.6.3 VLR Failure In the case of VLR restart, the VLR retrieves subscriber data from the GLR to recover its database. The required capability of the GLR to support this procedure is the same as that of the HLR in the case of VLR restart without GLR. The procedure is described in 3G TS 23.007 [2]. Basically, data recovery is achieved through the restore procedure requested from the VLR in the case of mobile terminating call, or normal location updating in the case where there is radio contact (for example on location updating and call originating from the user). The restoration procedure of VLR Failure is illustrated in Figure 7.6/4 and 7.6/5. Each step is explained in the following list. HLR 3. Insert Subscriber Data 1. Provide Roaming Number 2. Restore Data Visited NW Home NW VLR Restart 1. Provide Roaming Number ack 4. Restore Data ack 3. Insert Subscriber Data ack GLR 1. Provide Roaming Number ack 1. Provide Roaming Number Figure 7.6/4: Restoration of the VLR by Mobile Terminated call Procedure: 1) When the VLR receives Provide Roaming Number message, it identifies that no IMSI record exists and creates a skeleton IMSI record and returns the Provide Roaming Number ack message with MSRN to the HLR via the GLR. The GLR only relays these messages. 2) The VLR also sends the Restore Data message to the GLR when it identifies that no IMSI record exists in order to recover subscriber record for the IMSI. 3) The GLR that receives the message initiates insert subscriber procedure to the VLR. 4) The recovery of IMSI record in the VLR is completed after it receives Restore Data ack message. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 80 3G TS 23.119 version 3.0.0 Release 1999 GLR 3. Insert Subscriber Data Error: Unidentified Subscriber Visited NW MSC 1. Update Location Area 3. Insert Subscriber Data ack VLR 4. Update Location ack 2. Update Location 5. Update Location Area ack Mobile Originated Activity Request Restart MO case 1. Update Location Area UL case Authentication Figure 7.6/5: Restoration of the VLR by Mobile Originated activity and Update Location Procedure: 1) (Mobile Originated case). When the VLR receives MO activity request and identifies that no IMSI record exists, it returns negative response with cause (Unidentified Subscriber). The user who receives the negative response initiates update location procedure and then the VLR creates a skeleton IMSI record. (Update Location case). When the user initiates location update procedure and the VLR identifies that no IMSI record exists, the VLR creates a skeleton IMSI record. 2) After successful authentication the VLR sends Update Location message to the GLR. 3) When the GLR receives the Update Location message from the VLR, it initiates insert subscriber procedure normally. 4) After insert subscriber procedure completed the GLR sends Update Location ack message to the VLR. 5) When the VLR receives the Update Location ack message, it confirms the registration for the user. At this time the recovery of IMSI record in the VLR is completed. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 81 3G TS 23.119 version 3.0.0 Release 1999 7.6.4 SGSN Failure After an SGSN restart, the SGSN deletes all MM and PDP contexts affected by the restart. When GGSN detects the SGSN restarted by polling function (echo request and response), it shall delete all PDP contexts associated to the SGSN. After that during restoration procedure the SGSN initiates location update procedure. However the GLR does not need to know that the SGSN restart and it only proceeds usual location procedure. The restoration procedure of SGSN Failure is illustrated in Figure 7.6/6. Each step is explained in the following list. 3. Insert Subscriber Data 1. RESET 2. Attach Request Visited NW SGSN 4. Update GPRS Location ack 3. Insert Subscriber Data ack GLR 2.Update GPRS Location MS GGSN Restart 5. Attach Request ack Re-Initiate PDP Context Activation procedures Identifies No MM context Figure 7.6/6: Restoration of the SGSN Procedure: 1. After the SGSN restart, it may broadcast a Reset message within SGSN area. This causes the MS to reinitiate Attach and Activate PDP context procedures. 2. When the SGSN receives Attach Request message and identifies no MM context for the MS, it initiates update location procedure. 3. The GLR initiates insert subscriber data procedure as normal update location procedure. 4. When the SGSN receives the Update GPRS Location ack message from the GLR, it returns the Attach Request ack message to the MS. 5. The MS which receives the message re-initiates Activate PDP context procedures, if needed. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 82 3G TS 23.119 version 3.0.0 Release 1999 7.6.5 Functional requirements of GLR 7.6.5.1 Process Restore_Data_GLR Figure 7.6/7 shows SDL chart for Process Restore_Data_GLR. Process in the G LR to handle an R estore Data request and trigger the correct application process Process Restore_Data_G LR 1(7) Signales to/from the left are to/from the VLR Signales to/from the right are to/from the HLR Idle Restore Data Check Parameter See TS 23.018 Result= Pass subscriber known in GLR Set negative response: Unknown Subscriber HLR update required? Set GLR Num ber as VLR N umber Update Location negative response 1 Set IM-MSC Number as M SC Num ber Restore data Idle W ait_For_ Data Yes No Yes No Yes No Figure 7.6/7(1): Process Restore_Data_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 83 3G TS 23.119 version 3.0.0 Release 1999 Process in the G LR to handle an Restore Data request and trigger the correct application process Process Restore_Data_G LR 2(7) Signales to/from the left are to/from the VLR Signales to/from the right are to/from the HLR W ait_For_ Data Insert Subscriber Data Restore data ack Restore data negative response Abort Insert_ Subscriber_ Data_GLR Result:=Pass Abort W ait_For_ Data_from _HLR _ and_ISD_ack_ from _VLR LSIC by H LR :=Confirmed Idle Set GLR N um ber as HLR Number M NR F set? Failure Case? Set M S_Not_Reachable Result:= Roaming Not Allow ed Result:= Unknow n Subscriber Result:= Procedure Error Restore data ack Delete Subscriber Data Delete Subscriber Data Idle LSIC by H LR :=False Restore D ata negative response Idle yes No Roaming Not Allow ed Unknow n Subscriber Procedure Error Figure 7.6/7(2): Process Restore_Data_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 84 3G TS 23.119 version 3.0.0 Release 1999 Process in the G LR to handle an Restore Data request and trigger the correct application process Process Restore_Data_GLR 3(7) Signales to/from the left are to/from the VLR Signales to/from the right are to/from the HLR W ait_For_ Data_from _H LR_ and_ISD_ack_ from _VLR Insert Subscriber Data Restore data ack Restore Data negative response Abort Insert_ Subscriber_ Data_GLR Result:=Pass Abort W ait_For_ Data_from _H LR_ and_ISD_ack_ from _VLR LSIC by HLR :=Confirmed Idle Set GLR Num ber as HLR Number M NR F set? Failure C ase? Set M S_Not_Reachable Result:= Roam ing Not Allowed Result:= Unknown Subscriber Result:= Procedure Error Restore data ack Delete Subscriber Data Delete Subscriber Data Idle LSIC by HLR :=False Restore Data negative response Idle yes No Roam ing Not Allowed Unknown Subscriber Procedure Error Figure 7.6/7(3): Process Restore_Data_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 85 3G TS 23.119 version 3.0.0 Release 1999 Process in the G LR to handle an Restore Data request and trigger the correct application process Process Restore_Data_GLR 4(7) Signals to/from the left are to/from the VLR Signals to/from the right are to/from the HLR W ait_For_ Data_from _HLR _ and_ISD_ack_ from _VLR Insert Subscriber Data ack All received feature & service supported? Update subscriber data for supported features set param eters for unsupported features M SC area restricted by regional subscription? Set M SC area restricted Insert Subscriber Data ack W ait_For_ Data_from _HLR _ and_ISD_ack_ from _VLR Update Seubscriber Data Insert Subscriber Data negative response Insert Subscriber Data negative response W ait_For_ Data_from _HLR _ and_ISD_ack_ from _VLR No Yes No Yes Figure 7.6/7(4): Process Restore_Data_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 86 3G TS 23.119 version 3.0.0 Release 1999 Process in the G LR to handle an Restore Data request and trigger the correct application process Process Restore_Data_GLR 5(7) Signales to/from the left are to/from the VLR Signales to/from the right are to/from the HLR 1 ISD _GLR Result = Pass? M SC Area Restricted? OR Roam ing Restricted Due to Unsupported Feature? Subscriber_Present_ GLR Changed supported services? Changed MSC area restricted Set GLR Num ber as VLR N umber Set IM-MSC Number as M SC Number Restore Data W ait_For_ information M NR F set? Set M S_Not_Reachable Restore data ack Idle Result = Aborted? Restore Data negative response Idle Idle Yes No No Yes No yes No Yes No No Yes Figure 7.6/7(5): Process Restore_Data_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 87 3G TS 23.119 version 3.0.0 Release 1999 Process in the G LR to handle an Restore Data request and trigger the correct application process Process Restore_Data_GLR 6(7) Signales to/from the left are to/from the VLR Signales to/from the right are to/from the HLR W ait_For_ Information Insert Subscriber Data 2 Restore data ack Result:= Pass LSIC by HLR :=True Set GLR Num ber as HLR N um ber M NR F set? Set M S_Not_Reachable Restore data ack Idle Restore data negative response Failure case? Result:= Roam ing Not Allowed Delete Subscriber Data LSIC by HLR :=False Restore data negative response Idle Result:= Unknown Subscriber Delete Subscriber Data Result:= Procedure Error Abort Abort Idle yes No Roam ing not Allow ed Unknown Subscriber Procedure Error Figure 7.6/7(6): Process Restore_Data_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 88 3G TS 23.119 version 3.0.0 Release 1999 Process in the G LR to handle an R estore Data request and trigger the correct application process Process Restore_Data_G LR 7(7) Signales to/from the left are to/from the VLR Signales to/from the right are to/from the HLR 2 Check Parameter See TS 23.018 Result= Pass? Subscriber know n? All received features & services supported? Update Subscriber Data M SC area restricted by regional subscription? Set M SC area restricted Insert Subscriber Data ack W ait_For_ Inform ation Update Subscriber Data for supported features Set param eters for unsupported features Insert Subscriber Data negative response Idle Yes Yes Yes Yes No No No No Figure 7.6/7(7): Process Restore_Data_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 89 3G TS 23.119 version 3.0.0 Release 1999 7.7 Short Message Service The Short Message Mobile Terminated is realised by MAP signalling between SMS-GMSC and the visited node (i.e. MSC or SGSN). Signalling address is the E.164 MSC Number or the E.164 SGSN Number. Since in the case of GLR introduction address conversion (see subclause 7.1.2) is performed some mechanism is needed to restore the actual visited node address from the converted one generated by the GLR. In principle that restoration is performed by the GLR itself. 7.7.1 Scope This subclause describes only SM MT with GLR under the following condition: - The recipient MS in the visited PLMN with the GLR is roamed into the PLMN from other PLMN. Since SM MT in the case that is not applied to the above condition and SM MO have no relation to the introduction of the GLR those cases are not treated in this subclause and just refer to 3G TS 23.040 [5]. This subclause defines: - the services and service elements (with regard to the GLR introduction); - the network architecture (with regard to the GLR introduction); - the IM-MSC functionality (with regard to the SMS); - the GLR functionality (with regard to the SMS); - the protocols and protocol layering (with regard to the GLR introduction); for the Teleservices 22, as specified in the 3G TS 22.003 [1]. 7.7.2 Definitions This clause only provides definitions specific to the GLR introduction. Other definitions regarding SMS are provided in 3G TS 23.040 [5]. Intermediate-MSC (IM-MSC): The Intermediate MSC is an exchange which performs address interrogation to the GLR and relays the SMS to the MSC in the case of SM MT. Mobile-Station-Not-Reachable-Flag (MNRF): The part of the MWI to be stored in the VLR and the HLR. It shall be stored also in the GLR. MNRF is a Boolean parameter indicating if the address list of MWD contains one or more entries because an attempt to deliver a short message to an MS has failed with a cause of Absent Subscriber. Mobile-station-Not-Reachable-for-GPRS (MNRG): The part of the MWI to be stored in the SGSN and the HLR. It shall be stored also in the GLR. MNRG is a Boolean parameter indicating if the address list of MWD contains one or more entries because an attempt to deliver a short message to an MS has failed with a cause of Absent Subscriber. More-Messages-To-Send (MMS): The GLR shall keep a MAP dialogue open between the SMS-GMSC and the GLR and between the GLR and the SGSN where there are more messages to send. The IM-MSC shall keep a MAP dialogue open between the SMS-GMSC and the IM-MSC and between the IM-MSC and the MSC. Gateway Location Register (GLR): The Gateway Location Register is an exchange that relays the SMS MT from SMS-GMSC to the SGSN. The GLR shall have interrogation function to forward the SM MT to the correct MSC or the SGSN. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 90 3G TS 23.119 version 3.0.0 Release 1999 7.7.3 Services and service elements 7.7.3.1 Short Message Service elements 7.7.3.1.1 Messages-Waiting Refer to 3G TS 23.040 [5] for the definition of the Message-Waiting service element. The GLR shall have only the MNRF and the MNRG for the Message-Waiting. The GLR does not have other datum for the Message-Waiting service element. Setting the MNRF and the MNRG is mandatory in the GLR as in the VLR/SGSN. When the MS has been detected as becoming active, the VLR or the SGSN shall: - send the "MS Reachable" message (see subclause 7.7.7) to the HLR via the GLR, and then - clear MNRF in the VLR or the MNRG in SGSN (see 3G TS 23.040 [5]). When the GLR receives the “MS Reachable” message it is mandatory for the GLR to relay the “MS Reachable” message to the HLR and then clear MNRF or MNRG in the GLR. The MNRG and MNRF in the GLR are updated in the following way: 1a)When a mobile terminated short message delivery fails due to the MS being temporarily absent (i.e. either IMSI DETACH flag is set or there is no response from the MS to a paging request via the MSC), the MNRF is set (if it is not already set). 1b)When a mobile terminated short message delivery fails due to the MS being temporarily absent (i.e. either GPRS DETACH flag is set or there is no response from the MS to a paging request via the SGSN), the MNRG is set (if it is not already set). 1c)When a mobile terminated short message delivery fails due to the MS memory capacity via the MSC being exceeded, the MNRF is cleared. 1d)When a mobile terminated short message delivery fails due to the MS memory capacity via the SGSN being exceeded, the MNRG is cleared. 2a)When either the HLR or VLR detects that the MS (with a non-empty MWD and the MCEF clear in the HLR and the MNRF set in the VLR) has recovered operation (e.g. has responded to a paging request over MSC), the HLR directly, or on request of the VLR or of the GLR, will invoke operations to alert the SCs within the MWD (see subclause 7.7.3.1.2 and subclause 7.7.7). Once the Alert SC operations have been invoked, the MNRF is cleared in the VLR and the GLR. 2b)When either the HLR or SGSN detects that the MS (with a non-empty MWD and the MCEF clear in the HLR and the MNRG set in the SGSN) has recovered operation (e.g. has responded to a paging request via the SGSN), the HLR directly or on request of the SGSN or the GLR will invoke operations to alert the SCs within the MWD (see subclause 7.7.3.1.2 and subclause 7.7.7). Once the Alert SC operations have been invoked, the MNRG is cleared in the SGSN and the GLR. 2c)When the HLR receives (via the MSC, the VLR and the GLR) a notification that the MS (with a non-empty MWD and the MCEF set in the HLR) has memory capacity available to receive one or more short messages, the HLR will invoke operations to alert the SCs within the MWD (see subclause 7.7.3.1.2 and subclause 7.7.7). Once the Alert SC operations have been invoked, the MNRF is cleared in the VLR and the GLR. 2d)When the HLR receives (via the SGSN and the GLR) a notification that the MS (with a non-empty MWD and the MCEF set in the HLR) has memory capacity available to receive one or more short messages, the HLR will invoke operations to alert the SCs within the MWD (see subclause 7.7.3.1.2 and subclause 7.7.7). Once the Alert SC operations have been invoked, the MNRG is cleared in the SGSN and the GLR. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 91 3G TS 23.119 version 3.0.0 Release 1999 7.7.3.1.2 Alert-SC Considering the Alert-SC service element, when the GLR receives the Update Location or the Update GPRS Location from the VLR or the SGSN if and only if the MNRF or the MNRG is set in the GLR the GLR shall send "MS Reachable" message (see clause 7.7.7) to the HLR. That enables the HLR to initiate Alert-SC. 7.7.3.2 Unsuccessful short message TPDU transfer SC -> MS Some error(s) may occur in the IM-MSC or the GLR (see subclauses 7.7.5 and 7.7.7). 7.7.4 Network architecture 7.7.4.1 Basic network structure The exchange of messages between an MS and an SME involves the entities shown in figure 7.7/1. The basic network structure of the SM MT with GLR is depicted in figure 7.7/2. Inside the scope of the 3GPP Specifications SME SC SMS-GMSC IM-MSC/GLR MSC/SGSN MS Outside the scope of the 3GPP Specifications Figure 7.7/1: Entities involved in the provision of SM MT with GLR The links of figure 7.7/2 support the SM MT with GLR in the following way: - the operations performed on links 1, 2, 3 and 4 is described in 3G TS 29.002 [10]; - interface E is internal interface in one physical node. Procedure in the IM-MSC, the GLR and between them regarding interface 5 is described in 3G TS 29.002 [10]. SC SMS-GMSC IM-MSC MSC/VL MS GLR SGSN 1 2 5 3 4 Figure 7.7/2: The main network structure serving as a basis for the SM MT with GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 92 3G TS 23.119 version 3.0.0 Release 1999 7.7.5 Node functionality related to SM MT 7.7.5.1 General In the case of the GLR introduction as an option for the visited network operator, the existing functionality of the GSM entities regarding SMS MT (i.e. SMS-GMSC, MSC, VLR, SGSN and HLR) shall not be needed to modify. 7.7.5.2 Functionality of the GLR When receiving a short message TPDU from the SMS-GMSC ("forwardShortMessage", see subclause 7.7.7.1), the GLR is responsible for the following operations: - reception of the short message TPDU; if errors are detected by the GLR: - returning the appropriate error information to the SMS-GMSC in a failure report (negative outcome of "forwardShortMessage" see clauses 7.7.7.1); if no errors are detected by the GLR: - retrieve the SGSN Number from the identity of the recipient MS; - transferring the short message to the SGSN. When a delivery report is received by the GLR: - relaying the delivery report (positive outcome of “forwardShortMessage” see subclause 7.7.7.1) to the SMS-GMSC. When a failure report is received by the GLR: - relaying the failure report (negative outcome of “forwardShortMessage” see subclause 7.7.7.1) to the SMS-GMSC. When receiving “ReadyForSM” from the MSC or the SGSN: if errors are detected by the GLR: - returning the appropriate error information to the MSC or the SGSN in a failure report (negative outcome of "ReadyForSM", see subclause 7.7.7.3); if no errors are detected by the GLR: - relaying the “ReadyForSM” to the HLR (see subclause 7.7.7.3). 7.7.5.3 Functionality of the IM-MSC When receiving a short message TPDU from the SMS-GMSC ("forwardShortMessage", see subclause 7.7.7.1), the IM- MSC is responsible for the following operations: - reception of the short message TPDU; - retrieving information from the GLR ("ObtainMSCNumber", see subclause 7.7.7.1); MSC Number and, when appropriate, error information; if errors are indicated by the GLR: - returning the appropriate error information to the SMS-GMSC in a failure report (negative outcome of "forwardShortMessage" see clauses 7.7.7.1); if no errors are indicated by the GLR: - relaying the "forwardShortMessage" to the MSC is indicated by the retrieved MSC Number. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 93 3G TS 23.119 version 3.0.0 Release 1999 When a delivery report is received by the IM-MSC: - relaying the delivery report (positive outcome of “forwardShortMessage” see subclause 7.7.7.1) to the SMS-GMSC. When a failure report is received by the IM-MSC: - relaying the failure report (negative outcome of “forwardShortMessage” see subclause 7.7.7.1) to the SMS-GMSC. 7.7.6 Protocols and protocol architecture SM-RL shall be terminated at the GLR and the IM-MSC, since the GLR and the IM-MSC shall be able to retrieve the actual visited node address (i.e. the MSC Number or the SGSN Number) from the recipient MS identity. The protocol layers of the SMS are structured as shown in figure 7.7/3. SC SMS-GMSC IM-MSC/GLR MSC/SGSN MS SM-AL SM-TL SM-RL SM-LL Figure 7.7/3: Protocol layer overview for the SM MT with GLR 7.7.6.1 Service provided by the SM-RL 7.7.6.1.1 General SM-RL messages and its information elements are the same as in the network without the GLR. 7.7.6.1.2 Protocol element repertoire at SM-RL Protocol element repertoire at SM-RL is the same as in the network without the GLR. Refer to 3G TS 23.040 [5] for the presence (i.e. mandatory, optional or not present) of each information element by replacing the term in the following manner. - SMS-GMSC <-> IM-MSC or IM-MSC <-> MSC : MSC <-> MSC. - SMS-GMSC <-> GLR or GLR <-> SGSN : MSC <-> SGSN. 7.7.7 Fundamental procedures within the point-to-point SMS This subclause provides the procedures specific to the GLR introduction. 7.7.7.1 Short message mobile terminated The entities involved in this procedure are depicted in figure 7.7/4. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 94 3G TS 23.119 version 3.0.0 Release 1999 SC SMS- GMSC SGSN MS GLR VLR MSC IM-MSC HLR NOTE: The GLR and the IM-MSC shall not visible to the other entities. Especially the SMS-GMSC shall regard the GLR and the IM-MSC as the SGSN and the MSC respectively. Further the SGSN and MSC shall regard the GLR and the IM-MSC as the SMS-GMSC. Figure 7.7/4: Interface involved in the short message mobile terminated procedure with GLR In figures 7.7/5, sequence diagrams are shown for the following basic situations of short message mobile terminated transfer attempt: - Successful short message transfer via the MSC;…a). - Successful short message transfer via the SGSN;…b). - Short message transfer attempt failing due to error at the MSC;…c). - Short message transfer attempt failing due to error at the SGSN;…d). - Short message transfer attempt failing due to error at the IM-MSC;…e). - Short message transfer attempt failing due to error at the IM-MSC/GLR;…f). - Short message transfer attempt failing due to error at the GLR;…g). - Short message transfer attempt failing over the SGSN as the first path and succeeding over the MSC as the second path;…h). - Short message transfer attempt failing over the SGSN as the first path and over the MSC as the second path;…I). ETSI ETSI TS 123 119 V3.0.0 (2000-03) 95 3G TS 23.119 version 3.0.0 Release 1999 SC SMS- GMSC HLR IM-MSC GLR MSC VLR SGSN MS SendRoutingInfoForShortMsg 1a. ForwordShortMessage 2. ObtainMSCNumber Message Transfer 3a. ForwordShortMessage SendInfoFor-MT-SMS Message Transfer 1b. Delivery report 3b. Delivery report SM-Delivery ReportStatus Delivery report Operation invocation or message transfer Successful operation invocation or message transfer including report Figure 7.7/5a): Successful short message transfer attempt via the MSC ETSI ETSI TS 123 119 V3.0.0 (2000-03) 96 3G TS 23.119 version 3.0.0 Release 1999 SC SMS- GMSC HLR IM-MSC GLR MSC VLR SGSN MS SendRoutingInfoForShortMsg 1a. ForwordShortMessage Message Transfer 3a. ForwordShortMessage Message Transfer 1b. Delivery report 3b. Delivery report SM-Delivery ReportStatus Delivery report Operation invocation or message transfer Successful operation invocation or message transfer including report Figure 7.7/5b): Successful short message transfer attempt via the SGSN ETSI ETSI TS 123 119 V3.0.0 (2000-03) 97 3G TS 23.119 version 3.0.0 Release 1999 SC SMS- GMSC HLR IM-MSC GLR MSC VLR SGSN MS SendRoutingInfoForShortMsg 1a. ForwordShortMessage 2. ObtainMSCNumber Message Transfer 3a. ForwordShortMessage 1c. Failure report 3c. Failure report SM-DeliveryReportStatus Failure report Operation invocation or message transfer Successful operation invocation or message transfer including report Error report Unsuccessful operation invocation or message transfer including report (or with missing confirmation) 4. InformSMDeliveryFailure Figure 7.7/5c): Short message transfer attempt failing due to error at the MSC ETSI ETSI TS 123 119 V3.0.0 (2000-03) 98 3G TS 23.119 version 3.0.0 Release 1999 SC SMS- GMSC HLR IM-MSC GLR MSC VLR SGSN MS SendRoutingInfoForShortMsg 1a. ForwordShortMessage Message Transfer 3a. ForwordShortMessage 1c. Failure report 3c. Failure report SM-Delivery ReportStatus Failure report Operation invocation or message transfer Successful operation invocation or message transfer including report Error report Unsuccessful operation invocation or message transfer including report (or with missing confirmation) Figure 7.7/5d): Short message transfer attempt failing due to error at the SGSN SC SMS- GMSC HLR IM-MSC GLR MSC VLR SGSN MS SendRoutingInfoForShortMsg 1a. ForwordShortMessage Message Transfer 1c. Failure report SM-Delivery ReportStatus Failure report Operation invocation or message transfer Successful operation invocation or message transfer including report Error report Unsuccessful operation invocation or message transfer including report (or with missing confirmation) Figure 7.7/5e): Short message transfer attempt failing due to error at the IM-MSC ETSI ETSI TS 123 119 V3.0.0 (2000-03) 99 3G TS 23.119 version 3.0.0 Release 1999 SC SMS- GMSC HLR IM-MSC GLR MSC VLR SGSN MS SendRoutingInfoForShortMsg 1a. ForwordShortMessage 2. ObtainMSCNumber Message Transfer 1c. Failure report SM-DeliveryReportStatus Failure report Operation invocation or message transfer Successful operation invocation or message transfer including report Error report Unsuccessful operation invocation or message transfer including report (or with missing confirmation) Figure 7.7/5f): Short message transfer attempt failing due to error at the IM-MSC/GLR SC SMS- GMSC HLR IM-MSC GLR MSC VLR SGSN MS SendRoutingInfoForShortMsg 1a. ForwordShortMessage Message Transfer 1c. Failure report SM-Delivery ReportStatus Failure report Operation invocation or message transfer Successful operation invocation or message transfer including report Error report Unsuccessful operation invocation or message transfer including report (or with missing confirmation) Figure 7.7/5g): Short message transfer attempt failing due to error at the GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 100 3G TS 23.119 version 3.0.0 Release 1999 SC SMS- GMSC HLR IM-MSC GLR MSC VLR SGSN MS SendRoutingInfoForShortMsg 1a. ForwordShortMessage Message Transfer 3a. ForwordShortMessage 1c. Failure report 3c. Failure report SM-DeliveryReportStatus Delivery report 1a. ForwordShortMessage 3a. ForwordShortMessage 3c. Delivery report 1c. Delivery report 2. ObtainMSCNumber SendInfoFor-MT-SMS Message Transfer Operation invocation or message transfer Successful operation invocation or message transfer including report Error report Unsuccessful operation invocation or message transfer including report (or with missing confirmation) Figure 7.7/5h): Short message transfer attempt failing over the SGSN as the first path and succeeding over the MSC as the second path ETSI ETSI TS 123 119 V3.0.0 (2000-03) 101 3G TS 23.119 version 3.0.0 Release 1999 SC SMS- GMSC HLR IM-MSC GLR MSC VLR SGSN MS SendRoutingInfoForShortMsg 1a. ForwordShortMessage Message Transfer 3a. ForwordShortMessage 1c. Failure report 3c. Failure report SM-Delivery ReportStatus Failure report 1a. ForwordShortMessage 3a. ForwordShortMessage 3c. Failure report 1c. Failure report 2. ObtainMSCNumber SendInfoFor-MT-SMS Operation invocation or message transfer Successful operation invocation or message transfer including report Error report Unsuccessful operation invocation or message transfer including report (or with missing confirmation) 4. InformSMDeliveryFailure Figure 7.7/5i): Short message transfer attempt failing over the SGSN as the first path and over the MSC as the second path Operation 1: Message transfer SMS-GMSC -> GLR or IM-MSC. This operation is used to transfer a short message from an SMS-GMSC to a GLR or IM-MSC. The operation consists of: - the transfer of a message containing the TPDU from the SMS-GMSC to the GLR or IM-MSC (see "1a. ForwardShortMessage" in figure 7.7.5), and - the return of either a "Failure report" (see 1c. in figure 7.7.5) or a "Delivery report" (see 1b. in figure 7.7.5). "Failure report" is returned to the SMS-GMSC when the GLR or IM-MSC has received indication from another entity (MSC, SGSN) or when an error has occurred in the GLR or IM-MSC the procedure was unsuccessful. The error indications which the GLR or IM-MSC may receive from the MSC, SGSN, VLR or MS enable the GLR or IM-MSC to return one of the error indications given in Table 23.040/1 back to the SMS-GMSC. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 102 3G TS 23.119 version 3.0.0 Release 1999 Note that the SMS-GMSC shall regard the GLR as a SGSN and the IM-MSC a MSC and it is not aware the GLR and the IM-MSC as individual entities. Operation 2: ObtainMSCNumber. When the IM-MSC receives "1a. ForwardShortMessage" from an SMS-GMSC, the IM-MSC interrogates the GLR internally and obtains the E.164 number of the MSC at which the MS is currently located. Operation 3: forwardShortMessage. The operation provides a means for the GLR or IM-MSC to transfer a short message to the MSC or to the SGSN respectively at which the MS is currently located. The operation works in tandem with the forwarding of the short message from the MSC or from the SGSN to the MS. Thus, the outcome of the operation comprises either success, i.e. that the message has been delivered to the MS; or a failure that may be caused by several reasons, e.g. failure in the transfer IM-MSC -> MSC or GLR -> SGSN, MS being detached, or no paging response. Note that the MSC and the SGSN shall not be aware of existence of the GLR and the IM-MSC. Operation 4: InformSMDeliveryFailure. When the IM-MSC receives “3c. FailureReport” with absent subscriber cause, IM-MSC informs it to the GLR. The GLR checks if the reason of absent subscriber is due to the purged MS in the serving node (i.e. MSC or SGSN). If so, the GLR deletes the subscriber data for the user. Otherwise the GLR sets MNRF. When the GLR receives “3c. FailureReport” with absent subscriber cause, the GLR checks if the reason of absent subscriber is due to the purged MS in the serving node (i.e. MSC or SGSN). If so, the GLR deletes the subscriber data for the user. Otherwise the GLR sets MNRG. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 103 3G TS 23.119 version 3.0.0 Release 1999 7.7.7.2 Functional requirements of GLR 7.7.7.2.1 Process Obtain_MSC_Number_GLR Figure 7.7/6 shows the SDL chart for Process Obtain_MSC_Number_GLR. G LR application process for Obtain M SC N um ber Process Obtain_MSC_Number_GLR 1(1) Signals from /to the left are to/from the IM-M SC Idle Obtain M SC N um ber Subscriber know n in G LR ? Obtain M SC N um ber ack Obtain M SC Num ber negative response Idle Idle Yes N o Figure 7.7/6: Process Obtain_MSC_Number_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 104 3G TS 23.119 version 3.0.0 Release 1999 7.7.7.2.2 Process Inform_SM_Delivery_Failure_GLR Figure 7.7/7 shows the SDL chart for Process Inform_SM_Delivery_Failure_GLR. G LR application process for Inform SM Delivery Failure Process Inform _SM _D elivery_Failure_G LR 1(1) Signals to/from the left are to/from IM-MSC Idle Inform SM Delivery Failure set MNRF Check_Absent_ SUbscriberSM_In_GLR Idle Figure 7.7/7: Process Inform_SM_Delivery_Failure_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 105 3G TS 23.119 version 3.0.0 Release 1999 7.7.7.2.3 Procedure Check_Absent_SubscriberSM_In_GLR Figure 7.7/8 shows the SDL chart for Procedure Check_Absent_SubscriberSM_In_GLR. T he proced ure Check_A bsent_S ubscribe rS M _In_G LR determ ines w hether the G LR shall delete its data for the M S based on the outcom e of a MT -S M S delivery attem pt for PS d om ain Procedure Check_Absent_SubscriberSM_In_G LR 1(1) Super-C harged G LR Ab sent Su bscriber SM E rror Pu rg ed M S ? De lete Su bscriber Data yes yes no no Figure 7.7/8: Procedure Check_Absent_SubscriberSM_In_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 106 3G TS 23.119 version 3.0.0 Release 1999 7.7.7.3 Alert transfer The entities involved in this procedure are depicted in figure 7.7/9. SC SMS- IWMSC SGSN MS GLR VLR MSC HLR NOTE: The GLR shall not visible to the other entities. Especially the HLR shall regard the GLR as the VLR or the SGSN. Further the SGSN and the VLR shall regard the GLR as the HLR. Figure 7.7/9: Interfaces involved in the Alert procedure with GLR This procedure consists of the operations shown in figure 7.7/10. Regarding the GLR introduction, the following four cases are distinguished: - the MS becomes reachable when the MNRF is set in the VLR (figure 7.7/10a); - the MS becomes reachable when the MNRG is set in the SGSN (figure 7.7/10b); - the MS performs Location Update when the MNRF is not set in the VLR (figure 7.7/10c); - the MS performs Routing Area Update when the MNRG is not set in the SGSN (figure 7.7/10d). The operations between HLR and GLR are equivalent for HLR to those between HLR and VLR or between HLR and SGSN. The operations between GLR and SGSN are equivalent for SGSN to those between HLR and SGSN. The operations between GLR and VLR are equivalent for VLR to those between HLR and VLR. The procedures in HLR, VLR and SGSN regarding the operations are the same as in the network without GLR. The procedures regarding the operations in GLR and IM-MSC are defined in 3G TS 29.002 [10]. SC SMS- GMSC HLR IM-MSC GLR MSC VLR SGSN MS alertServiceCentre ReadyForSM ServiceCentreAler ReadyForSM Figure 7.7/10a: The alert procedure when the MS becomes reachable, MNRF is set ETSI ETSI TS 123 119 V3.0.0 (2000-03) 107 3G TS 23.119 version 3.0.0 Release 1999 SC SMS- GMSC HLR IM-MSC GLR MSC VLR SGSN MS alertServiceCentre ReadyForSM ServiceCentreAler ReadyForSM Figure 7.7/10b: The alert procedure when the MS becomes reachable, MNRG is set SC SMS- IWMSC HLR IM-MSC GLR MSC VLR SGSN MS alertServiceCentre UpdateLocation ServiceCentreAler ReadyForSM LA Update Figure 7.7/10c: The alert procedure when the GLR receives UpdateLocation, MNRF or MNRG is set SC SMS- IWMSC HLR IM-MSC GLR MSC VLR SGSN MS alertServiceCentre UpdateGprsLocation ServiceCentreAler 5. ReadyForSM RA Update Figure 7.7/10d: The alert procedure when the GLR receives UpdateGprsLocation, MNRF or MNRG is set Operation 5: ReadyForSM (invoked by UpdateLocation or UpdateGprsLocation). When the GLR receives UpdateLocation (see 7.7/10c) or UpdateGprsLocation (see 7.7/10d) the GLR shall invoke ReadyForSM to the HLR if and only if MNRF or MNRG is set. Note that if the GLR in which the MNRG is set receives Update Location the GLR shall invoke ReadyForSM also in that case. The converse case is also the case. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 108 3G TS 23.119 version 3.0.0 Release 1999 7.8 Subscriber and Equipment Trace 3G TS29.002 [10] states that subscriber and equipment trace is only available for subscribers within their HPLMN area. If the HLR receives a trace request for a subscriber, and the HLR detects that the subscriber is not in the HPLMN, then the HLR does not forward the trace request to the VPLMN. The trace request never reaches the GLR. Therefore it is concluded that the GLR has no impact on subscriber and equipment trace. 7.9 Impact of GLR on CAMEL 7.9.1 The VLR supports CAMEL Phase 2 onwards When the GLR receives the MAP_UPDATE_LOCATION request message from the subscriber, the GLR checks that the CAMEL supported phase it previously received for that subscriber matches the CAMEL supported phase carried by MAP_UPDATE_LOCATION request message. If a difference is detected, the GLR relays the MAP_UPDATE_LOCATION request message to the HLR in order to obtain the proper CAMEL subscription information that corresponds to the current VLR. Refer to figure 7.9.1/1. In order to perform this scenario, the CAMEL supported phase information needs to be added to the ‘IMSI record in GLR’ table. It is possible that all the VLRs within a VPLMN do not support the same phase of CAMEL. This could happen in the case of an incremental upgrade of these VLRs within the VPLMN. In this case, it is possible that the HLR may receive frequent changes of the CAMEL supported phase information in the MAP_UPDATE_LOCATION request message from the GLR. The effect is that the HLR would perceive the GLR as a VLR that changes its CAMEL supported phase. Other CAMEL related messages between HLR and VLR, e.g. Provide Subscriber Info, Provide Subscriber Info ack are always relayed transparently from the HLR to the VLR or vice versa. MS VLR GLR HLR Location update req. Update Location Update Location Compare the CAMEL Supported phase between that held in the GLR and newly received in the MAP_LU. If difference is detected, relay MAP_UL to HLR. Insert Sub. Data CAMEL sub. Info. Location update conf. GLR number VLR number CAMEL sub. Info. Store the received CAMEL Supported phase information in GLR Insert Sub. Data Insert Sub. Data ack Insert Sub. Data ack Update Location Update Location Figure 7.9/1: CAMEL Subscription Information ETSI ETSI TS 123 119 V3.0.0 (2000-03) 109 3G TS 23.119 version 3.0.0 Release 1999 7.9.2 The VLR supports CAMEL Phase 1 or has no CAMEL Support If the Location Update Request message received by the GLR contains no indication that the VLR supports CAMEL, then this shows to the GLR that the VLR: - either has no support for CAMEL. - or supports CAMEL Phase 1. The GLR will interpret this situation to mean that there is no CAMEL support within the VLR. Therefore the GLR will treat this as a case of an unsupported service (see subclause 7.2.1.4). This will lead to an update location procedure being initiated between the GLR and HLR, causing the HLR to activate its service substitution rules. Note the following description of a current GSM network, i.e. where there is no GLR between the HLR and VLR. When the HLR receives a Location Update request with no indication of CAMEL support, then the HLR will attempt to request CAMEL Phase 1 support in the ISD message. If the ISD is accepted by the VLR, then support for CAMEL Phase 1 is indicated. If the ISD is rejected, then no support for CAMEL Phase 1 is indicated. 7.10 Interaction with CCBS 7.10.1 Two possible treatments for interaction with CCBS In order to treat CCBS function in the GLR, There may be two possible treatments applied. When a subscriber is monitored (either as being a target or being the initiator of CCBS request), and roams to visited network which contains the GLR, the GLR manages monitoring state of subscriber. If monitoring is ongoing when the GLR receives a Location Update request from the new VLR, the GLR can take one of the following actions: - (Alternative 1): Relay the Location Update request to the HLR to inform the appropriate CCBS processes in the HLR, or - (Alternative 2): Send a StatusReport MAP operation, indicating “Idle” to the HLR, handle the Location Update request locally in the GLR, and start monitoring on the new VLR, by sending a SetReportingState MAP operation to the new VLR. Should the SetReportingState response from the new VLR indicate “Not reachable” or “Not Idle”, then the GLR will send this status information in a StatusReport towards the HLR. The alternative 1 has the advantage that the GLR monitoring functionality is straightforward, but implies unnecessary MAP LU traffics. The alternative 2 has the advantage that MAP LU traffic is saved, but implies monitoring logic to be available in the GLR. Both options imply that the GLR needs to keep track of subscribers being monitored. 7.10.2 The functionality in the GLR The CCBS Monitoring Flag is used in the GLR to judge whether requested location updating is necessary to be indicated to HLR or not. The figure 7.10/1 and figure 7.10/2 show how to handle a Location Update request signal referring with the CCBS Monitoring Flag in the GLR by using the alternative 1 treatment, the alternative 2 treatment respectively. These figures only indicate how a Location Update request signal is treated in the GLR. Refer to the 3G TS 23.093 [8] for a more detail treatment about the CCBS service. Other CCBS related MAP operations, e.g. RegisterCC-entry, EraseCC-Entry and RemoteUserFree are always relayed transparently from the HLR to the VLR or vice versa. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 110 3G TS 23.119 version 3.0.0 Release 1999 Stop reporting ack. Stop reporting MS MSC1/VLR1 MSC2/VLR2 GLR HLR Update Location Subsequent Location Update in GLR area Insert subscriber data process CCBS mon. Flag = off as default value Location Update ack. Start reporting Start reporting Start reporting ack. Start reporting ack. CCBS mon. Flag = on Update Location Location Update Busy Idle Idle Location Update Relay transparently Location Update ack. Location Update ack. Due to CCBS call Stop reporting Stop reporting ack. CCBS mon. Flag = off Insert subscriber data process Busy MS status Figure 7.10/1: Update Location request signal handling for CCBS in the GLR (Alternative 1) ETSI ETSI TS 123 119 V3.0.0 (2000-03) 111 3G TS 23.119 version 3.0.0 Release 1999 Stop reporting ack. Stop reporting MS MSC1/VLR1 MSC2/VLR2 GLR HLR Update Location Subsequent Location Update in GLR area Insert subscriber data process CCBS mon. Flag = off as default value Location Update ack. Start reporting Start reporting Start reporting ack. Start reporting ack. CCBS mon. Flag = Update Location Location Update Busy Idle Idle Status report (Idle) Launch Status report message Location Update ack. Due to CCBS call Stop reporting Stop reporting ack. CCBS mon. Flag = Insert subscriber data process Busy MS status Start reporting Start reporting ack. Launch Start reporting Figure 7.10/2: Update Location request signal handling for CCBS in the GLR (Alternative 2) 7.10.2.1 Functional requirements of GLR The Alternative 1 introduced in this section for Update Location request signal handling for CCBS in the GLR is illustrated in the section 7.2.1 Location Management Procedures as one possible alternative. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 112 3G TS 23.119 version 3.0.0 Release 1999 7.10.2.1.1 Process Set_reporting_GLR Figure 7.10/3 shows the SDL chart for Process Set_reporting_GLR. Process in the to hanle set Process 1(1) Signals to/from the are to/from the Signals to/from the are to/from the Idle Set HLR Check Paramete See TS Result: pass Set CCBS flag Copy from Set HLR Set VLR Wait_For Respons Set VLR Abort Set VLR respons Copy from Set VLR Copy respons Set HLR Abort Set HLR respons Idle Yes No Figure 7.10/3: Process Set_reporting_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 113 3G TS 23.119 version 3.0.0 Release 1999 7.10.2.1.2 Process Status report GLR Figure 7.10/4 shows the SDL chart for Process Status_report_GLR. Process in the GLR to handle Status report Process Status_report_GLR 1(1) Signals to/from the left are to/from the VLR Signals to/from the right are to/from the HLR Idle Status report VLR Check Parameter See TS 23.018 Result:= pass? Copy information from Status report VLR Status report HLR W ait_For_ Response Status report HLR ack Copy information from Status report HLR ack Status report VLR ack Idle Abort Abort Status report H LR negative response C opy negative response Status report VLR negative response Yes No Figure 7.10/4: Process Status_report_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 114 3G TS 23.119 version 3.0.0 Release 1999 7.10.2.1.3 Process Remote_User_Free_GLR Figure 7.10/5 shows the SDL chart for Process Remote_User_Free_GLR. Process in the GLR to handle Remote User Free Process 1(1) Signals to/from the left are to/from the VLR Signals to/from the rig are to/from the HLR Idle RUF HLR Check Parameter See TS 23.018 Result:= pass? Copy information from RUF HLR RUF VLR Wait_For_ Response RUF VLR ack Copy information from RUF VLR ack RUF HLR ack Idle Abort Abort RUF VLR negative response Copy negative response RUF HLR negative response Yes No Figure 7.10/5: Process Remote_User_Free_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 115 3G TS 23.119 version 3.0.0 Release 1999 7.10.2.1.4 Procedure CCBS_status_report_GLR Figure 7.10/6 shows the SDL chart for Procedure CCBS_status_report_GLR. Procedure to send status report in GLR Procedure CCBS_status_report_G LR 1(1) Signals to/from the right are to/from the HLR CCBS mon flag on ? Set subscruber status = idle Status report HLR Wait_For_ Response Status report HLR ack Status report HLR negative response Abort Yes No Figure 7.10/6: Procedure CCBS_Status_Report_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 116 3G TS 23.119 version 3.0.0 Release 1999 7.10.2.1.5 Procedure CCBS_start_report_GLR Figure 7.10/7 shows the SDL chart for Procedure CCBS_start_report_GLR Procedure to send CCBS start report in GLR Procedure CCBS_start_report_G LR 1(1) Signals to/from the right are to/from the VLR CCBS mon flag on ? set start reporting Set reporting VLR Wait_For_ Response Set reporting VLR ack Set reporting VLR negative response Abort Yes No Figure 7.10/7: Procedure CCBS_Start_Report_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 117 3G TS 23.119 version 3.0.0 Release 1999 7.11 Location Service This section is based on that in 3G TS 23.171 [7]. 7.11.1 Mobile Terminating Location Request 7.11.1.1 Circuit Switched Mobile Terminating Location Request (CS-MT-LR) MS HLR GMLC SRNC Client 12. LCS Service Response 2. MAP Send Routing Info for LCS 1. LCS Service Request 3. MAP Send Routing Info for LCS ack. 4. MAP Provide Subscriber Location 11. MAP Provide Subscriber Location ack. IM-MSC 4’. MAP Provide Subscriber Location 11’. MAP Provide Subscriber Location ack. 3G-VMSC GLR 2’. MAP Send Routing Info for LCS 3’. MAP Send Routing Info for LCS ack. 10. RANAP Location Report 8. RANAP Location Reporting Control 5. MS Paging, Authentication, Ciphering 9. Messages for individual positioning methods [6. LCS Location Notification Invoke?] [7. LCS Location Notification Return Result?] Figure 7.11/1: General Network Positioning for a MT-LR 7.11.1.1.1 Location Preparation Procedure 1) and 2) Same as the steps not involving GLR. See 3G TS 23.171 [7]. 3) The HLR returns the current 3G-VMSC address that includes actually IM-MSC address. The other action is the same as the step not involving GLR. See 3G TS 23.171 [7]. 4) The GMLC sends a MAP_PROVIDE_SUBSCRIBER_LOCATION message to the IM-MSC indicated by the HLR. The other action is the same as the step not involving GLR. See 3G TS 23.171 [7]. 2’) If the IM-MSC already knows the VMSC location for the particular IMSI (e.g. from a previous location request), this step and step 3’ may be skipped. Otherwise, the IM-MSC sends a MAP_SEND_ROUTING_INFO_FOR_LCS message to the GLR of the target MS to be located with the IMSI of this MS. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 118 3G TS 23.119 version 3.0.0 Release 1999 3’) The GLR returns the current VMSC address and whichever of the IMSI and MSISDN was not provided in step (2’) for the particular MS. 4’) The IM-MSC sends a MAP_PROVIDE_SUBSCRIBER_LOCATION message to the VMSC indicated by the GLR. 5) to 8) Same as the steps not involving GLR. See 3G TS 23.171 [7]. 7.11.1.1.2 Positioning Measurement Establishment Procedure 9) Same as the step not involving GLR. See 3G TS 23.171 [7]. 7.11.1.1.3 Location Calculation and Release Procedure 10)Same as the step not involving GLR. See 3G TS 23.171 [7]. 11’) The VMSC returns the location estimate and its age to the IM-MSC. The other action is the same as the step not involving GLR. See 3G TS 23.171 [7]. 11)The IM-MSC receives the location estimate and its age, then sends them to the GMLC. 12)Same as the step not involving GLR. See 3G TS 3G 23.171 [7]. 7.11.1.2 MT-LR for a previously obtained location estimate UE HLR GMLC SRNC Client 3G-VMSC 6. LCS Service Response 2. MAP Send Routing Info for LCS 1. LCS Service Request 3. MAP Send Routing Info for LCS ack. 4. MAP Provide Subscriber Location 5. MAP Provide Subscriber Location ack. SRNC HLR 2’. MAP Send Routing Info for LCS 3’. MAP Send Routing Info for LCS ack. 4’. MAP Provide Subscriber Location 5’. MAP Provide Subscriber Location ack. Figure 7.11/2: MT-LR for a previously obtained location estimate (1) to (4) Same as the step not involving GLR. See 3G TS 23.171 [7]. (2’) to (3’) Same as step 2’ for an MT-LR. (4’) Same as step 4’ for an MT-LR. The message sent to the 3G-VMSC requests either an initial location or current or last known location with “no delay”. (5’) Same as step 11 for an MT-LR. (5) Same as step 11 for an MT-LR. (6) Same as the step not involving GLR. See 3G TS 23.171 [7]. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 119 3G TS 23.119 version 3.0.0 Release 1999 7.11.1.3 Network Induced Location Request (NI-LR) This procedure is the same as the procedure not involving GLR. See 3G TS 23.171 [7]. 7.11.1.4 Network Induced Location Request (NI-LR) from a Serving RNC for a target UE in dedicated mode This procedure is not related to GLR. 7.11.2 Mobile Originating Location Request 7.11.2.1 Mobile Originating Location Request, Circuit Switched (CS-MO-LR) This procedure is the same as the procedure not involving GLR. See 3G TS 23.171 [7]. 7.12 IST of non-CAMEL implementation If the GLR supports IST, when the GLR receives an Update Location request that indicates that the MSC/VLR supports IST, it relays the indication to the HLR. If not, the GLR may ignore the indication. When the GLR receives an IST Alert Request from the MSC, it relays the message to the HLR. The HLR sends an IST Alert Response to the GLR, and then the GLR relays the message to the MSC. When the IM-MSC receives an IST Command Request from the HLR, it retrieves the location information, i.e., MSC Number, from the GLR and sends the message to the MSC. Then the IM-MSC receives the response from the MSC and sends the response to the HLR. 7.13 The interaction with Super-Charger Following sub-clauses show the location updating procedures in the case that the serving nodes in the network with the GLR support the Super-Charger functionality. 7.13.1 First Location Updating Procedure in the Super-Charged network The first location updating procedure in a Super-Charged network is illustrated in figure 7.13/1. Each step is explained in the following list. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 120 3G TS 23.119 version 3.0.0 Release 1999 GLR HLR 1. Update Location or 2. Insert Subscriber Data 2. Insert Subscriber Data ack 3. Update Location ack or Visited NW Home NW VLR/SGSN Update GPRS Location Update GPRS Location 1. Update Location or 2. Insert Subscriber Data 2. Insert Subscriber Data ack Update GPRS Location ack 3. Update Location ack or Update GPRS Location ack Figure 7.13/1: First Location Updating Procedure in the case that visited NW supports the Super- Charger features Procedure: 1) When the GLR receives an Update Location or Update GPRS Location message from a serving node (i.e., VLR or SGSN) and does not hold the subscriber’s information for the user (ex. at the first location updating to the GLR), it relays the message without age indicator (if age indicator is received from the serving node, the GLR deletes it) to the HLR. 2) The HLR stores the address and number of serving node. Thereafter the HLR initiates insert subscriber data procedure and cancel location procedure (only if both the HLR and previous serving node support the Super- Charger features). When the GLR receives Insert Subscriber Data message from the HLR, the GLR creates an age indicator and stores the subscriber’s information in the message and transports it to the serving node with the age indicator. 3) After these procedures, the HLR replies to an Update Location or Update GPRS Location message from the GLR and the GLR transports the response to the serving node. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 121 3G TS 23.119 version 3.0.0 Release 1999 7.13.2 Second and further Location Updating Procedure in the Super- Charged networks The second and further location updating procedure in a Super-Charged network is illustrated in figure 7.13/2. Each step is explained in the following list. GLR HLR 1. Update Location or 3. Insert Subscriber Data 3. Insert Subscriber Data ack 4. Update Location ack Visited NW Home NW 2. Cancel Location 2. Cancel Location ack VLR/SGSN OLD VLR/SGSN NEW Update GPRS Location Update GPRS Location ack Note2: This procedure is initiated only if the serving node requests the subscriber data or the subscriber data in the serving node is not consistent with that in the GLR Note2 Note1: This procedure is initiated only when the serving node doesn’t support SC feature Note1 Figure 7.13/2: Second and further Location Updating Procedure in the case that visited NW supports the Super-Charger features Procedure: 1) When the GLR receives an Update Location or Update GPRS Location message with an age indicator from newly visited serving node (i.e. VLR or GSSN) and holds the subscriber information for the user (i.e. at second or further location updating to the GLR), it stores the address and number of newly visited serving node included in the received message. 2) The GLR does not initiate cancel location procedure if the previous node supports the Super-Charger features. 3) When the age indicator from the serving node indicates the serving node does not request the subscription data, the GLR checks if the subscription data retained in serving node is consistent with that stored in the GLR. If so, the GLR shall not send subscription data to the newly visited serving node. Otherwise the GLR initiates the insert subscriber procedure to the serving node. 4) After these procedures, the GLR replies to an Update Location or Update GPRS Location message from the serving node. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 122 3G TS 23.119 version 3.0.0 Release 1999 7.13.3 Cancel Location Procedure in the Super-Charged networks The cancel location procedure in a Super-Charged network when MS leave the network is illustrated in figure 7.13/3. Each step is explained in the following list. GLR HLR Visited NW Home NW 1. Cancel Location 3. Cancel Location ack 2. Cancel Location 2. Cancel Location ack VLR/SGSN OLD Note Note: This procedure is initiated only when the serving node doesn’t support SC feature Figure 7.13/3: Cancel Location Procedure in the case that visited NW supports the Super-Charger features Procedure: 1) When the GLR receives a Cancel Location message from the HLR, it checks whether the serving node supports the Super-Charger features or not. 2) If the serving node does not supports the Super-Charger features, the GLR initiates a cancel location procedure to the serving node. 3) When the GLR receives the response of the Cancel Location message, it responses to the HLR by sending the Cancel Location ack message. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 123 3G TS 23.119 version 3.0.0 Release 1999 7.13.4 Functional requirement for the GLR 7.13.4.1 Procedure Super_Charged_Cancel_Location_GLR Figure 7.13/4 shows SDL chart for Procedure Super_Charged_Cancel_Location_GLR. The procedure Super_C harged_Cancel_Location_G LR determ ines whether a Super-Charged GLR shall send the cancel location m essage to the previous network entity. Procedure Super_Charged_C ancel_Location_G LR 1(1) Super-C harged GLR Previous Network Entity Supports Super-Charger? R esult:= Pass Result:= Fail yes no yes no Figure 7.13/4: Procedure Super_Charged_Cancel_Location_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 124 3G TS 23.119 version 3.0.0 Release 1999 7.13.4.2 Procedure Super_Charged_Location_Updating_GLR Figure 7.13/5 shows SDL chart for Procedure Super_Charged_Location_Updating_GLR. The procedure Super_Charged_Location_Updating_GLR determines whether a Super-Charged GLR shall send subscription data to the requesting network entity. Procedure Super_Charged_Location_Updating_GLR 1(1) Super-Charged GLR Serving Network Entity Supports Super-Charger? Send subscriber data ? Subscriber data valid? Result:=Pass Result:=Fail yes no yes no no yes yes no Figure 7.13/5: Procedure Super_Charged_Location_Updating_GLR ETSI ETSI TS 123 119 V3.0.0 (2000-03) 125 3G TS 23.119 version 3.0.0 Release 1999 8 The subscriber information stored in the GLR The subscriber information stored in the GLR can be categorised in the following types. 8.1 Information for HLR emulation The GLR retrieves this kind of subscriber information mainly from Insert Subscriber Data message received from the HLR and stores it. Then this message is transported to the VLR transparently. This type of information is for example: - IMSI. - International MS ISDN number. - PDP Type. 8.2 Information for address and identity conversion On location updating the VLR or SGSN sends Update Location message to the GLR and notifies its VLR number and MSC number or SGSN number and SGSN address by the message. On the first updating in the newly visited network, the GLR relays Update Location message to the HLR setting. - The GLR number as the VLR number(E.164 address). - The IM_MSC number as the MSC number(E.164 address). - The GLR number as the SGSN number(E.164 address). - The IM-GSN address as the SGSN address(IP address). The GLR keeps the association of these numbers and addresses and updates it on the second and further updating. And when the GLR receives and stores the HLR number in Update Location ack message form the HLR, it relays the message to the VLR setting. - The GLR number as the HLR number (E. 164 address). - Identity Conversion. On location updating the VLR creates and allocates the LMSI number (denote LMSIv) for the user and sends it to the GLR in Update Location message. When the GLR receives the message, it creates and allocates another LMSI number (denote LMSIg) and associates LMSIg with received LMSIv. The GLR notifies LMSIg to the HLR sending Update Location message. This method can speed up the search for subscriber data in the GLR when the GLR receives some message from the HLR. 8.3 Information for Location updating Screening This information is used for the GLR to judge whether requested location updating is necessary to be indicated to HLR or not. Following are information categorized in this type. MNRF, MNRG. - CCBS Monitoring Flag. - MSC area restricted flag. - SGSN area restricted flag. - Location and Subscriber information Confirmed by HLR indicator (LSIC). ETSI ETSI TS 123 119 V3.0.0 (2000-03) 126 3G TS 23.119 version 3.0.0 Release 1999 Subclause 7.7 shows the procedure for SMS alerting in the network with the GLR. In the procedure Mobile station Not Reachable Flag (MNRF) and Mobile station Not Reachable for GPRS (MNRG) are needed. The CCBS Monitoring Flag is set when the user in the GLR area is CCBS monitored by the VLR. As one option, while it is set, the Update Location message is relayed to the HLR to inform the appropriate CCBS process in the HLR. More detailed procedures for the CCBS are included in section 7.10. MSC area restricted flag and SGSN area restricted flag are needed for regional restriction service. See section 7.5 for more detailed procedures. LSIC is used for restart procedures. Section 7.6.3 includes more detailed description for the usage of this indicator. 8.4 Information for support of Super-Charger functionality This information is used for the GLR to behave as the HLR supporting the Super-Charger functionality towards the serving node (i.e. VLR or SGSN) which also supports Super-Charger functionality. Following is information categorised in this type. - Age indicator for CS. - Age indicator for PS. 8.5 Other Information The GLR has Service Substitution Induced Flag list. This information show which service is replaced by service substitution. See section 7.2.1.3 for more detail on the handling of unsupported services. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 127 3G TS 23.119 version 3.0.0 Release 1999 Table 8.5/1: Subscriber Information stored in the GLR PARAMETER PRESENCE CATEGORY (*1) NOTE IMSI M A Network Access Mode C A International MS ISDN number M A LMSI allocated by VLR C B LMSI allocated by GLR C B Mobile Station Category M A LMU Identifier C A VLR number M B MSC number M B HLR number C B Zone Code List C A Roaming restriction due to unsupported feature C A MSC area restricted flag M C LSA Identity C A LSA Priority C A LSA Only Access Indicator C A LSA Active Mode Indicator C A Provision of bearer service M A Provision of teleservice M A BC allocation C A Subscriber status C A Barring of outgoing calls C A Barring of premium rate calls C A Barring of supplementary service management C A Barring of invocation of call transfer C A Mobile Station Not Reachable Flag M C VGCS Group Membership List C A VBS Group Membership List C A Broadcast Call Initiation Allowed List C A Originating CAMEL Subscription Information C A SS invocation notification (SS-CSI) C A CCBS Monitoring Flag C C Location and Subscriber information Confirmed by HLR indicator M C CAMEL Supported phases information C C Service Substitution Induced Flag list C E Forwarding information List C A Call barring information List C A CUG information List C A SS-Data List C A EMLPP Subscription C A North American Equal Access preferred Carrier Id List C A Privacy Exception List C A Home GMLC Numbers C A IST Alert Timer C A Age indicator for CS C D Packet Specific Data SGSN number M B Roaming Restriction in the SGSN due to unsupported feature M A SGSN area restricted flag M C MNRG M C PDP Type C A PDP Address C A SGSN address M B Access Point Name C A VPLMN Address Allowed C A Quality of Service Subscribed C A Age indicator for PS C D (*1) A: Information for HLR emulation. B: Information for address and identity conversion. C: Information for Location updating Screening. D: Information for support of Super-Charger functionality. E: Others. ETSI ETSI TS 123 119 V3.0.0 (2000-03) 128 3G TS 23.119 version 3.0.0 Release 1999 Change Request History Document history V0.1.0 Aug 1999 The first draft. V0.2.0 Sep 1999 Addition of section 7.10 and some editorial corrections. V0.3.0 Oct 1999 Addition of section 7.5.2, modification of section 7.2.1.3 and section 7.2.2, and, some editorial corrections. V0.4.0 Nov 1999 Moved, modified and merged Purge MS descriptions from section 7.3.1.3 and 7.3.3 to section 7.4. Deleted section 7.10 Location Service and remove LCS related data from table 8.5/1. Corrected some editing errors. V0.5.0 Nov 1999 Modified section 2 References. Deleted one sentence from section 4. Corrected minor editing errors in section 5.3 and section 8.5. Restored section 7.11 Location Services and LCS related data to table 8.5/1. V1.0.0 Feb 2000 Agreed by CN2B, Milan V2.0.0 Mar 2000 Submitted for approval to TSG CN#07 V3.0.0 March 2000 Approved by CN#07 129 ETSI ETSI TS 123 119 V3.0.0 (2000-03) 3G TS 23.119 version 3.0.0 Release 1999 History Document history V3.0.0 March 2000 Publication
|
01cf386a661f37797b151545792903a0
|
123 110
|
1 Scope
|
........................................................................................................................................................6
|
01cf386a661f37797b151545792903a0
|
123 110
|
2 References
|
................................................................................................................................................6
|
01cf386a661f37797b151545792903a0
|
123 110
|
3 Definitions and abbreviations
|
..................................................................................................................6
|
01cf386a661f37797b151545792903a0
|
123 110
|
3.1 Definitions
|
......................................................................................................................................................... 6
|
01cf386a661f37797b151545792903a0
|
123 110
|
3.2 Abbreviations
|
..................................................................................................................................................... 7
|
01cf386a661f37797b151545792903a0
|
123 110
|
4 Basic Assumptions
|
...................................................................................................................................7
|
01cf386a661f37797b151545792903a0
|
123 110
|
4.1 Boundaries of the Access Stratum
|
..................................................................................................................... 7
|
01cf386a661f37797b151545792903a0
|
123 110
|
4.2 Main design guidelines
|
...................................................................................................................................... 7 5 Functions location inside/outside Access Stratum...................................................................................8
|
01cf386a661f37797b151545792903a0
|
123 110
|
5.1 Call Control
|
....................................................................................................................................................... 9
|
01cf386a661f37797b151545792903a0
|
123 110
|
5.2 (Connection) Bearer Control
|
............................................................................................................................. 9
|
01cf386a661f37797b151545792903a0
|
123 110
|
5.3 Supplementary Services (CLIP, CF etc.)
|
......................................................................................................... 10
|
01cf386a661f37797b151545792903a0
|
123 110
|
5.4 Location Management
|
..................................................................................................................................... 10 5.5 Attach/ Detach ................................................................................................................................................. 10
|
01cf386a661f37797b151545792903a0
|
123 110
|
5.6 Resource management
|
..................................................................................................................................... 10
|
01cf386a661f37797b151545792903a0
|
123 110
|
5.7 Handover
|
......................................................................................................................................................... 10
|
01cf386a661f37797b151545792903a0
|
123 110
|
5.7.1 Handover - outside Access Stratum
|
........................................................................................................... 10
|
01cf386a661f37797b151545792903a0
|
123 110
|
5.7.2 Handover - inside Access Stratum
|
............................................................................................................. 10
|
01cf386a661f37797b151545792903a0
|
123 110
|
5.7.3 Handover scenarios supported by the Iu interface
|
...................................................................................... 10
|
01cf386a661f37797b151545792903a0
|
123 110
|
5.7.3.1 Classification A
|
.................................................................................................................................... 10
|
01cf386a661f37797b151545792903a0
|
123 110
|
5.7.3.2 Classification B
|
.................................................................................................................................... 11
|
01cf386a661f37797b151545792903a0
|
123 110
|
5.7.3.3 Classification C
|
.................................................................................................................................... 11
|
01cf386a661f37797b151545792903a0
|
123 110
|
5.7.3.4 Classification D
|
.................................................................................................................................... 12
|
01cf386a661f37797b151545792903a0
|
123 110
|
5.8 Macrodiversity
|
................................................................................................................................................. 12
|
01cf386a661f37797b151545792903a0
|
123 110
|
5.9 Encryption
|
........................................................................................................................................................ 12
|
01cf386a661f37797b151545792903a0
|
123 110
|
5.10 Authentication of Subscriber
|
........................................................................................................................... 12
|
01cf386a661f37797b151545792903a0
|
123 110
|
5.11 (Non source dependent coding) Compression
|
................................................................................................. 12
|
01cf386a661f37797b151545792903a0
|
123 110
|
5.12 Source (e.g. voice or video) Coding
|
................................................................................................................ 12
|
01cf386a661f37797b151545792903a0
|
123 110
|
5.13 Radio Channel Coding
|
..................................................................................................................................... 12
|
01cf386a661f37797b151545792903a0
|
123 110
|
5.14 UE Location Identification
|
.............................................................................................................................. 13
|
01cf386a661f37797b151545792903a0
|
123 110
|
5.15 Charging
|
.......................................................................................................................................................... 13
|
01cf386a661f37797b151545792903a0
|
123 110
|
6 Access Stratum services
|
.........................................................................................................................13
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.1 Service Access Points (SAPs)
|
.......................................................................................................................... 14
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.1.1 General Control SAPs
|
................................................................................................................................ 15
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.1.2 Notification SAPs
|
....................................................................................................................................... 15
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.1.3 Dedicated Control SAPs
|
............................................................................................................................. 15
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.2 Operations
|
........................................................................................................................................................ 15
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.2.1 General
|
....................................................................................................................................................... 15
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.2.2 Common operations
|
................................................................................................................................... 16
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.2.2.1 General Control SAP
|
............................................................................................................................ 16
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.2.2.1.1 Information broadcast
|
..................................................................................................................... 16
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.2.2.2 Notification SAPs
|
................................................................................................................................. 16
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.2.2.2.1 Paging Request, IF side
|
................................................................................................................... 17
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.2.2.2.2 Notification Broadcast Request, IF side
|
.......................................................................................... 17
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.2.2.2.3 Notification Indication, UE side
|
..................................................................................................... 17
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.2.2.3 Dedicated Control SAPs
|
....................................................................................................................... 17
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.2.2.3.1 UE Side Initiated Connection Establishment
|
.................................................................................. 18
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.2.2.3.2 Connection Release
|
......................................................................................................................... 19
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.2.2.3.3 Information Transfer
|
....................................................................................................................... 19
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.2.2.3.4 IF Side Initiated Radio Access Bearer Establishment
|
..................................................................... 21 6.2.2.3.4.1 IF Side Initiated Radio Access Bearer Establishment Request, IF Side.................................... 21 6.2.2.3.4.2 IF Side Initiated Radio Access Bearer Establishment Indication, UE Side............................... 21 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 4 Release 1999 6.2.2.3.4.3 IF Side Initiated Radio Access Bearer Establishment Response, UE Side................................ 21 6.2.2.3.4.4 IF Side Initiated Radio Access Bearer Establishment Confirm, IF Side................................... 21
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.2.2.3.5 IF Side Initiated Radio Access Bearer Release
|
............................................................................... 22 6.2.2.3.5.1 IF Side Initiated Radio Access Bearer Release Request, IF Side.............................................. 22 6.2.2.3.5.2 IF Side Initiated Radio Access Bearer Release Indication, UE Side......................................... 22
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.2.3 IF side only operations
|
............................................................................................................................... 22
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.2.3.1 Dedicated control SAPs
|
........................................................................................................................ 22
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.2.3.1.1 Position update indication
|
............................................................................................................... 22
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.2.3.1.2 Connection loss indication
|
.............................................................................................................. 22
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.2.3.1.3 Streamlining required indication
|
..................................................................................................... 22
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.2.3.1.4 Branch establishment request
|
.......................................................................................................... 22
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.2.3.1.5 Branch establishment confirm
|
........................................................................................................ 23
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.2.3.1.6 UE location information request
|
..................................................................................................... 23
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.2.3.1.7 UE location information confirm
|
.................................................................................................... 23
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.2.4 UE side only operations
|
............................................................................................................................. 23
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.2.4.1 Dedicated control SAPs
|
........................................................................................................................ 23
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.2.4.1.1 Connection loss indication
|
.............................................................................................................. 23
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.3 Parameters structure
|
......................................................................................................................................... 24
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.3.1 Local
|
........................................................................................................................................................... 24
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.3.2 Bit string
|
..................................................................................................................................................... 24
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.3.3 Enumerated
|
................................................................................................................................................ 24
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.3.4 Geographical description
|
............................................................................................................................ 24
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.3.5 QoS
|
............................................................................................................................................................ 24
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.3.6 Route
|
.......................................................................................................................................................... 24
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.3.7 Transaction identifier
|
................................................................................................................................. 24
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.3.8 Transaction list
|
........................................................................................................................................... 24
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.3.9 Transmission mode
|
.................................................................................................................................... 25 6.3.10 AN/CN Point List....................................................................................................................................... 25
|
01cf386a661f37797b151545792903a0
|
123 110
|
6.3.11 Localisation
|
................................................................................................................................................ 25 Annex A (informative): Change history...............................................................................................26 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 5 Release 1999 Foreword This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 6 Release 1999 1 Scope The present document specifies the services provided by the Access Stratum to the rest of the system. The adopted architecture is given by 3G TS 23.101 [2]. The present document describes the main functions visible at the boundary between the Access Stratum and the rest of the system, it describes in general terms the information flows, both control and user data, over this boundary and relevant for the Access Stratum. The present document is the basis of the detailed specifications of the protocols which rule the information flows, both control and user data, between the Access Stratum and the parts of UMTS outside the Access Stratum, and of the detailed specifications of the UTRAN. These detailed specifications are to be found in other Technical Specifications. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • For a non-specific reference, the latest version applies. [1] 3G TS 22.101: "Universal Mobile Telecommunications System (UMTS): Service aspects; Service principles". [2] 3G TS 23.101: "Universal Mobile Telecommunications System (UMTS): General UMTS Architecture". [3] 3G TS 23.105: "Universal Mobile Telecommunications System (UMTS): Network Principles". [4] ITU-T Recommendation X.210 (November 1993): "Information Technology - Open Systems Interconnection - Basic Reference Model: Conventions for the Definition of OSI Services". [5] 3G TS 23.107: "QoS Concept and Architecture". 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3G TS 23.101 [2] and the following apply. Access Stratum: defined in [2]. Access Network: defined in [2]. Edge-Node: core network node which is connected to the URAN at a particular instance. URAN: defined in [TBD]. 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 7 Release 1999 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: AN Access Network AS Access Stratum CC Call Control DC Dedicated Control SAP CN Core Network FFS For Further Study GC General Control (SAP) GPRS General Packet Radio Service GSM Global System for Mobile communications HPLMN Home Public Land Mobile Network IF Infrastructure ME Mobile Equipment MM Mobility Management MS Mobile Station NAS Non Access Stratum Nt Notification (SAP) PDN Packet Data Network PTM Point to Multipoint RAN Radio Access Network SAP Service Access Point SAPI Service Access Point Identifier [???] SIM Subscriber Identity Module SMS Short Message Service SS Supplementary Services TBD To Be Defined UE User Equipment UMTS Universal Mobile Telecommunications System URAN UMTS Radio Access Network USIM UMTS Subscriber Identity Module USSD Unstructured Supplementary Service Data UTRA UMTS Terrestrial Radio Access UTRAN UMTS Terrestrial Radio Access Network VBS Voice Broadcast Service VGCS Voice Group Call Service VPLMN Visited Public Land Mobile Network 4 Basic Assumptions 4.1 Boundaries of the Access Stratum The Access Stratum (AS) is defined in [2]. It consists of a functional grouping which includes all the layers embedded in the URAN; and part of the layers in the User Equipment (UE) and the infrastructure (IF); i.e. the edge-node. Its boundary is the frontier between the layers which are independent of the access technique and the ones which are dependent on it. This frontier is located in the UE (mobile boundary) and in an edge-node (fixed boundary). There is a direct or "transparent" dialogue (i.e. not interpreted by the AS) between the UE and the edge-node for the Non-Access Stratum layers. 4.2 Main design guidelines 1) The Access Stratum contains all access specific functionality, e.g. all mode specific functionality in case of the UTRAN. 2) Reconfiguration of the AN, or changes in the AN domain functionality shall have minimal impact on Core Network functions, and vice-versa. 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 8 Release 1999 3) A given Access Network (e.g., the UTRAN) may provide access to different type of Core Networks via the Iu reference point. 4) The services, access signalling, mobility and subscriber management specific to each Core Network are completely outside the Access Stratum, and are transferred transparently by the Access Stratum. 5) The Access Stratum provides flexible radio access bearers characterised by parameters describing the type of information and QoS transported over the radio interface (i.e. not the actual radio resources). Some radio access bearers may be asymmetric, i.e., have different parameters on uplink and downlink. 6) There are radio access bearers for both connection oriented packet-switched services, connectionless (store-and- forward) services, and circuit-switched traffic. 7) Parameters for connection-oriented radio access bearers may change during connection (bandwidth on demand, quality management). 8) Whether a terminal can be registered and have connections to several Core Networks simultaneously (i.e., over different instances of Iu) is FFS. 9) The Access Stratum can provide several parallel and independent radio access bearers to one user equipment each with its own characteristics. 10)Multimedia is handled outside the Access Stratum by multiplexing several streams onto one radio access bearer or by requesting several parallel radio access bearers. In the latter case, the possibly needed synchronisation is handled outside the Access Stratum. 11)Connection of a user equipment to several URAN at a time has to be studied. 12)Handover and if applied macrodiversity within one Access Network is handled within the Access Stratum. 13)Handover between two Access Networks (e.g., two UTRANs, or between UTRAN and GSM BSS) may use support from the Core Network. 14)The Access Stratum should hide all access -specific parameters, e.g., location data provided to the Core Networks should be independent from the actual configuration of the Access Network. 15)The user equipment can be connected to different AN/CN points via a single Access Network. The Access Stratum should be able to provide a flexible routing to the appropriate AN/CN point. 5 Functions location inside/outside Access Stratum Following table shows the functional split between Access Stratum and the rest of the system. 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 9 Release 1999 Table 1: Functions inside/outside the Access Stratum LOCATION \ FUNCTION Outside the Access Stratum Inside the Access Stratum Call set up/release yes no (Connection) Bearer Set-Up Release CN bearer [tbd] Radio Access Bearer [tbd] Supplementary Services yes no Location management yes (IWF/CN related) yes (Radio related) Attach/ Detach yes FFS, Contr expected Resource Management yes (for NAS resource) yes (for AS resource incl. radio) Handover yes* yes Macrodiversity [ffs] yes* yes Encryption yes yes** Authentication yes no compression (non source dependent) yes yes source dependent coding yes no radio channel coding (could be many) no yes (could be many) UE location identification may be supported yes Charging yes no NOTE *: Optionally execution. In some CNs, it may not be present but not full service will be supported (e.g. limited to RLL type of service). NOTE **: Contributions expected to clarify the role between encryption and subscriber data. 5.1 Call Control This Functionality is placed in the NAS, since it manipulates the call state machine. An example is termination of Q.931 message and sending of ISUP. Not part of AS. NAS specific signalling messages, e.g. Q.931, Q.2931 and ISUP. 5.2 (Connection) Bearer Control It is distinguished between the bearers used in the NAS and the common bearer used in the AS (radio access bearer). Basic principles for radio access bearers are: 1) Radio access bearers provide information transport between the non-access stratum parts of the infrastructure side (i.e. the edge node) and the user equipment side. Radio access bearers shall support real time as well as non real time user traffic. 2) Radio access bearers must be flexible enough to support different traffic types, activity levels, throughput rates, transfer delays and bit error rates. Attributes allowing efficient use of radio resources are crucial. 3) Efficient mapping from the traffic attributes used by non-UMTS applications, given by dominating external network technologies, to the attributes of the radio access bearer layer of the access stratum is essential. Complexity in mapping procedures should be avoided. 4) Definitions of traffic attributes and traffic management for radio access bearers shall be consistent with the predominant networking technology on the market (e.g. N-ISDN and IP networks for UMTS phase 1). As networking technologies emerge, adapted radio access bearer attributes and types shall gradually be added. 5) Radio access bearer definitions must allow for straightforward and efficient traffic management and resource handling of the radio resources in the access stratum. This procedure is part of the NAS. Example are 13.0 kbit/s (for GSM speech) and 2B+D (for ISDN BRI). 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 10 Release 1999 The protocols required in AS to provide a radio access bearer should be able to describe both packet switch and circuit switch types of connections. 5.3 Supplementary Services (CLIP, CF etc.) Supplementary services are part of the NAS, since they manipulate the Call state machine. Supplementary services are not part of AS since they manipulate the call state machine. 5.4 Location Management "Location Updating Management" and "Paging" is an existing example of Location Management. Location Management may be supported in the NAS. Radio related Location Management may be part of the AS. 5.5 Attach/ Detach If the Attach/ Detach procedures are supported in the NAS they use CN specific identifiers to mark the attached/detached subscriber. As an example in GSM, the attach/detach procedure is performed on the IMSI flag, and therefore it is a NAS functionality. Attach/Detach may be performed in the AS using the URAN unique identifiers. This is FFS. 5.6 Resource management This function allocates resources for a given information stream, as to allow to convey it with a given QoS. This information stream may support either signalling data (CC, MM, ...) or user data. Both circuit switched and packet access are supported, offering both connection oriented and connectionless services. The AS resource management is transparent for the NAS and vice versa. 5.7 Handover 5.7.1 Handover - outside Access Stratum Handover may be a NAS functionality, but it can not be expected that all CNs will support handover therefore the IWF may take care of any required handover functionality. The AN may leave certain parameters, e.g. the address to a new IWF/CN-AN connection point, to which the IWF/CN may switch if it has the capabilities. 5.7.2 Handover - inside Access Stratum Handover is performed in the AS, to hide all radio specific details from the NAS. 5.7.3 Handover scenarios supported by the Iu interface The following sections describe which functions will be supported by the Iu interface. Some functions have no impact on the Iu interface and therefore will be supported de-facto, nevertheless they are explicitly mentioned for completeness of the scenarios. 5.7.3.1 Classification A Classification A describes the way the handover is prepared: 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 11 Release 1999 HO A1: the network has informed the target cell before the MS changes cell; HO A2: the network has not informed the target cell before the MS changes cell; HO A3: the mobile has informed the target cell before it leaves the source cell. HO A1 is typical of the existing handover in GSM. HO A2 reflects the call re-establishment in GSM, mobile directed handovers in general, or even GPRS to some extent (although the GPRS vocabulary is different). HO A1, HO A2 and HO A3 shall be supported by the service primitives of the Iu interface. 5.7.3.2 Classification B Classification B describes the way the decision to initiate a handover is taken: HO B1: decision is taken by the terminal; HO B2: decision is taken by the network. When the network takes the decision, it can be either in the RAN (HO B2a), or in the CN (probably based on information provided by the RAN and/or the MS) (HO B2b). In order to keep the radio independence from the CN, it would be desirable that the decision be taken only in the RAN. This means that a communication mechanism is needed between URANs, that interface being logically different from the Iu interface. HO B1 and HO B2 shall be supported by the service primitives of the Iu interface. NOTE 1: FFS:For HO B2 cases, handover initiation/decisions shall be taken by the source URAN. NOTE 2: FFS: There is a URAN to URAN signalling mechanism transparent to the CN. A standardised protocol will be implemented across that interface to allow handover decisions by the URAN in HO B2 cases. 5.7.3.3 Classification C Classification C concerns the kind of handover performed: 1) intra-cell handover; 2) intra-URAN handover; 3) inter-URAN handover (without change of CN access point); 4) intra-CN handover with same URAN type; 5) intra-CN handover with different URAN type; 6) inter-CN handover with same URAN type and same CN type; 7) inter-CN handover with different URAN type and same CN type; 8) inter-CN handover with same URAN type and different CN type; 9) inter-CN handover with different URAN type and different CN type; 10)inter-CN handover without change of URAN. The type of URAN type should be relatively transparent to the Iu interface. Regarding handovers across multiple CN, it is proposed that this is supported (and this is already possible with GSM). C1 to C7 scenarios shall be supported by the service primitives of the Iu interface. NOTE: FFS: scenarios C8 to C10 shall be supported by the service primitives of the Iu interface. 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 12 Release 1999 5.7.3.4 Classification D Regarding how a handover is performed, there is the possibility to either have the notion of anchor point, or not to have it. Example is circuit switched GSM, using anchor points, and GPRS, not using that notion. Furthermore, the notion of anchor point may be handled differently for the signalling plane and the transmission plane. The notion of anchor point shall be supported by the service primitives of the Iu interface. NOTE 1: FFS: the notion of transmission plane anchor point is supported by the service primitives of the Iu interface. NOTE 2: FFS: the notion of signalling plane anchor point is supported by the service primitives of the Iu interface. NOTE 3: FFS: the anchor points for the signalling plane and transmission plane need not necessarily be the same or even exist simultaneously. The flexibility should be left in UMTS by the Iu service principles. 5.8 Macrodiversity (if needed, dependent of the choice of multiple access technology) Not all IWF/CNs will support macrodiversity. Macrodiversity may be supported in the AS, dependent on the choice of multiple access technology. 5.9 Encryption The NAS may support encryption to protect the transmitted data. The AS needs to support encryption to prevent from eavesdropping at the radio interface. 5.10 Authentication of Subscriber Subscriber data is stored in the NAS and therefore authentication should be considered a NAS functionality. NAS data is not stored in the URAN, and subscriber authentication can therefore not be a URAN functionality. 5.11 (Non source dependent coding) Compression NAS may support compression. The AS should support compression to optimise usage of radio resources. 5.12 Source (e.g. voice or video) Coding Source coding is different dependent on IWF/CN and is therefore a NAS functionality. 5.13 Radio Channel Coding Radio Channel coding is needed due to the radio interface and could therefore be considered a radio functionality. Radio Channel coding is not a NAS functionality. Radio Channel coding is supported by URAN. 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 13 Release 1999 5.14 UE Location Identification The UE location identification may be supported by the UE and/or the access network side of the AS; i.e., URAN; e.g., as defined in the GSM LCS (Location Services) specifications or by some other means. The UE location identification is provided to identify the likely location of specific UEs. This is meant to be used for charging, location-based services, lawful interception, emergency calls, etc., as well as the positioning services. When location identification is supported by URAN, the following apply: 1) URAN obtains ‘Area ID’ and/or geographic co-ordinates with uncertainty parameters for identification of the likely location of UE, to be sent to the NAS entity side of the CN (i.e., edge node) ‘Area ID’ represents either a radio access cell/sector or a geographic area. ‘Area ID’ is coded in the same format as Cell Global Identification (CGI), for compatibility to GSM. 2) Location information is categorised to two levels of accuracy. The Basic Level of information is what URAN obtains without extra signalling with the UE. The advanced level is obtained through extra signalling for positioning. Both levels can be used for both, Positioning services and other applications. 3) Location information is always at least obtained from URAN by the appropriate edge node(s) at the activation of a Call/PDP Context. Mechanism to make it possible to obtain the location information at the release of a Call/PDP Context should be specified. Location information sent to the edge node at other occasions is on the basis of asynchronous requests from the edge node to URAN. An edge node can request URAN to send the location information with the two types of requests, Type 1 (Direct request) where URAN sends location information only once at the request and Type 2 (Event request) where URAN sends location information at each specified event (e.g. Cell Update) requested by the edge node. 5.15 Charging The functions related to charging are not part of the AS. These functions are mainly: - charging information generation; - charging processing. 6 Access Stratum services The modelling of the services follow the basic principles as set by ITU-T Recommendation X.210 [4]. In this recommendation the following figure is given as an example for peer-to-peer connection-mode services. TISO2530-94/d03 Service User A Service User B OSI-Service-Provider Request (requestor.submit) Confirm (requestor.deliver) Indication (acceptor.deliver) Response (acceptor.submit) Figure 1: Example of a peer-to-peer connection-mode service [4] For connectionless-mode services the basic primitives are "request" and "indication". 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 14 Release 1999 6.1 Service Access Points (SAPs) The SAPs offered by the Access Stratum (AS) to the rest of the system (Non Access Stratum: NAS) are reflected in the following figure. UE-Uu CN-Iu NAS NAS IF-Uu RAN-Iu Edge node RAN UE Infrastructure Side User Equipment Side AS AS RNC Functions GC GC GC Nt GC GC GC Nt Nt Nt Nt Nt DC DC DC DC DC DC Uu Svcs: e.g., RRC Iu Svcs: e.g., RANAP : SAPs Figure 2: Service Access Points (SAPs) offered by the Access Stratum (AS) For the time being, the SAPs offered be the AS are symmetric, i.e. the same SAPs are offered on the infrastructure side (CN-AS) and on the user equipment side (UE-AS). These SAPs are: GC: General Control (see 6.1.1 for a general presentation and 6.2.2.1 for a detailed information). Nt: Notification (see 6.1.2 for a general presentation and 6.2.2.2 for a detailed information). DC: Dedicated Control (see 6.1.3 for a general presentation and 6.2.2.3 for a detailed information). Note: Broadcast and Multicast services can not be described using the services and functions defined so far in the present document. The nature of Broadcast and Multicast services, like Cell Broadcast Service (CBS), is very different from other specified services. The following model characteristics are missing to fulfil the CBS requirements, namely: 1. CBS uses two segments with different QoS requirements to deliver CB messages to the UE: 1a. From Cell Broadcast Center (CBC) to RNC, a SAP is required where for instance, 1 second turnaround time, interactive class, with a reliable transport is required. 1b. From RNC to UE, a SAP is required where for instance, a maximum delay of 10 seconds and a background class is required. 2. Because of (item 1), the service primitives used by each of the segments may also be different; i.e., the related SAPs to those primitives may differ in the two segments and a combination of GC, Nt, and DC SAPs requires study. 3. CBS traffic is asymmetric in nature. The communication flow is only in one direction from the CBC to the UE . There is no uplink channel needed and the UE can not initiate a communication or request specific information. At least two changes are envisaged and thus detailed contributions are expected: i. Introduce a new SAP type. 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 15 Release 1999 ii. Mapping example between the two communication segments. Figure 2 shows also, as an example, some details of the AS architecture. The details are out of the scope of this document and are further specified in the 25-series. This model does not exclude, nor imply, which protocol is specified between the UE-AS entity and the CN-AS entity. These protocols are ‘transparent’ for the AN, but participate in the service provided by the AS. 6.1.1 General Control SAPs These SAPs are used to enable the Core Network to provide information and to give commands that do not relate to specific users or specific [sessions] (group calls, conference). There is typically one General Control SAP per AN/CN connection point. On the UE side, a possible model is to consider that there is a single General Control SAP in an MS. 6.1.2 Notification SAPs These SAPs are used to broadcast data to identified Users. The typical use is for initiating paging in the AN. There is typically one Notification SAP per AN/CN connection point. On the UE side, a possible model is to consider that there is a single Notification SAP (a Paging SAP) in an MS. 6.1.3 Dedicated Control SAPs These SAPs are used to establish, release connections with specific User Equipment, and to exchange information related to these connections. A connection is a relationship between temporary contexts respectively in the AN and in the CN. The context in the AN is initiated at the establishment of the connection, and erased when the connection is released. Several types of connections are identified, such as point connection (single user) and group connections. There are typically a great number of Dedicated Control SAPs per AN/CN connection point. SAPs are identified by a SAPI at the AS boundary. During the lifetime of a connection, the connection can be identified unambiguously by the SAPI of the associated SAP, and the SAPI is used as a reference in the exchanges at the AS boundary on the infrastructure side. A SAPI is used as a connection identifier allocated unambiguously to each connection during its lifetime, and used in the exchanges at the AS boundary on the infrastructure side. On the UE side, a possible modelling is to consider that there is a single dedicated control SAP in an MS. NOTE 1: On the UE side, an open issue is whether simultaneous services from distinct ANs can be provided to an MS. Settling this issue may lead to a different model, for instance with the possibility to have several Dedicated Control SAPs, one per AN with which an active context exists. Another issue, visible when analysing Point-to-Multipoint services in GSM, is the SAP modelling for those PTM services. NOTE 2: The model is limited in this version to the cases where all the activity between a User Equipment and the infrastructure pertains to the same subscriber. Extension to cases with several subscriber sharing a User Equipment requires further study. 6.2 Operations 6.2.1 General The operations are described both for the AS boundary on the Infrastructure side and on the User Equipment side. The description of the operations on the Infrastructure side is given with sufficient details to develop on this basis a concrete control protocol at the AN/CN inter-connection. The description of the operations on the User Equipment side may be used [to be discussed] for developing a concrete API, allowing an open modular design of the User Equipment software. The operations are described in three sections, one for operations that involve both the IF side and the UE side, one for operations local to the IF and finally one for operations local to the UE side. In each sections, operations are sorted per SAP category. 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 16 Release 1999 Request and confirm primitives are always toward the Access Stratum. Indication and response primitives are always from the Access Stratum. 6.2.2 Common operations 6.2.2.1 General Control SAP 6.2.2.1.1 Information broadcast This operation consists in the broadcast from IF toward User Equipment of some information in some geographical area. This information is to be used by the User Equipment for instance to choose among access points or to be taken into account during initial access. The information can also be destinated to an application. NOTE: This concerns only information to be broadcasted on behalf of Non Access Strata. Other information may be broadcasted for the internal use of the Access Stratum. 6.2.2.1.1.1 Information broadcast request, IF side The parameters are: Category enumerated (access point selection, initial access, application) Geographical area geographical area Information to broadcast bit string The size of the information to broadcast is not bound by this description, but may be constrained by the access system. The geographical area is used by the AN to determine which access points are concerned. The rules are not specified in the external specification of the AS, but must exist and must be consistent with other translations between geographical descriptions and access points (e.g., in the connection establishment). The category is used by the AN to determine priority and more generally the parameters governing information repetition over time. NOTE: The category field could be enhanced, e.g., to allow a more precise control of priorities and repetitions. 6.2.2.1.1.2 Information Broadcast Indication, UE Side The parameters are: Access point reference local Broadcast information bit string The access point reference identifies the point on the access boundary (e.g., the cell) where the information was received. NOTE: The access point reference is a local reference, to be used in other primitives at the AS/NAS boundary in the same UE. 6.2.2.2 Notification SAPs Notification operations consists of sending information to a dedicated user/terminal, or a group of users/terminals over a defined geographic area. Typically the request is forwarded to the user/terminal on a broadcast resource. If the AN knows of an existing signalling relation to the user/terminal, the information might be sent through the existing relation, according to Access Stratum specifications. 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 17 Release 1999 6.2.2.2.1 Paging Request, IF side The parameters are the following: User/Terminal Identity pageable identity Geographical area where to broadcast geographical area Paging resource parameters paging resource parameters Information to send bit string The user/terminal identity is provided to determine if a signalling relation with the user/terminal exists. The geographical area indicates the area in which the Core Network knows the User/Terminal(s) to be. The size of the information to send is not bound by this description, but may be constrained by the access system. The paging resource parameters are used to determine which paging resource to be used when several are available. The organisation of paging resources is known in advance by the User Equipment, and are used by the User Equipment to choose the paging resources to listen to. The exact use of the paging resource parameters is specified as part of Access Stratum specifications. NOTE: This function is typically used for paging, i.e., to trigger an access from the User/Terminal. However, this is not relevant to the Access Stratum, and other uses can be envisaged without impacting the Access Stratum. The action required from the MS, if any, is indicated, implicitly or explicitly, in the information to send, the content of which being part of the Non Access Strata specifications and not of the Access Stratum specifications. 6.2.2.2.2 Notification Broadcast Request, IF side The parameters are the following: Geographical area where to broadcast geographical area Notification resource parameters paging resource parameters Information to broadcast bit string The size of the information to broadcast is not bound by this description, but may be constrained by the access system. The paging resource parameters are used to determine which paging resource to be used when several are available. The organisation of paging resources is known in advance by the User Equipment, and are used by the User Equipment to choose the paging resources to listen to. The exact use of the paging resource parameters is specified as part of Access Stratum specifications. NOTE: This operation is used typically to inform all MSes of some starting or on-going activities, such as group calls. 6.2.2.2.3 Notification Indication, UE side Parameters Access point reference local Broadcast information bit string NOTE: This primitive applies both for a paging sent on broadcast resources and for the reception of an information broadcast to many users. 6.2.2.3 Dedicated Control SAPs Dedicated Control operations are done within the scope of a connection, embodied by corresponding SAPs on the UE and IF sides. This scope is determined by local references (respectively on the UE side and on the IF side). All operations contain such a local reference, and, at a given AN/CN interconnection point, all operations with the same local reference from the establishment event to the release event pertain to the same connection. The correspondence 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 18 Release 1999 between Dedicated Control SAPs on the UE and IF side is dynamic, and established through the connection establishment operations. The local connection references have only a local scope, and their values do not necessarily have any predictable relationship with the corresponding reference local to the other side, or with a reference used over some interface to multiplex the messages pertaining to the connection with messages pertaining to other connections. 6.2.2.3.1 UE Side Initiated Connection Establishment This operation consists in the establishment of a new connection at the initiative of NAS on the User Equipment side. 6.2.2.3.1.1 UE Side Initiated Connection Establishment Request, UE side Parameters Local connection reference local Routing parameters routing parameters Initial message bit string The routing parameters are to be used by the AS on the Infrastructure side to choose the AN/CN connection point through which the connection is to be established. The initial message is to be forwarded to the non-access strata. The size of the initial message should not be constrained by the access system. 6.2.2.3.1.2 UE Side Initiated Connection Establishment Indication, IF side Parameters Local connection reference local Initial message bit string Localisation data localisation data The localisation data indicate the knowledge the AN has of the localisation of the initiating User Equipment. It includes typically a geographical area and some accuracy indication. 6.2.2.3.1.3 UE Side Initiated Connection Establishment Confirm, IF Side Parameters Local connection reference local Status enumerated (terminated by NAS, going on) Initial answer bit string The NAS can choose not to pursue the connection (status = terminated by NAS). Reasons can be that the information provided by the User Equipment did not require more than a single message answer (e.g., store-and-forward service), or some exception conditions prevented the CN to pursue the connection. The initial answer is to be provided to the requesting part in the non-access strata. 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 19 Release 1999 6.2.2.3.1.4 UE Side Initiated Connection Establishment Response, UE side Parameters Local connection reference local Status enumerated (terminated by NAS, terminated by AS, going on) Initial answer bit string The initial answer is not provided in the case the status is 'terminated by AS'. The status 'going on' and 'terminated by NAS' indicates that the initial message was delivered to the NAS; on the other hand, the status 'terminated by AS' can happen whether or not the initial message was delivered to the NAS. 6.2.2.3.2 Connection Release This operation is the termination of a connection, at the request of non-access strata on the Infrastructure side. The use of this operation may lead to the non-completion of other previously started operations in the same connection (e.g., transparent data transfer). 6.2.2.3.2.1 IF Initiated Connection Release Request, IF Side Parameter Local connection reference local 6.2.2.3.2.2 IF Initiated Connection Release Indication UE side Parameter Local connection reference local 6.2.2.3.3 Information Transfer These operations allow the transfer of messages between Non-Access Strata elements on each side of the access interface. The service is essentially that of a transport layer, with multiplexing, and possibly guarantee of order and correct transmission (transmission difficulties lead to connection loss), including the effect of user movements. The operation caters only for transmission from AS boundary to access boundary. Upper layers of protocol are typically added for addressing and routing beyond this boundary. Several independent streams can exist simultaneously on the same connection, as distinguished by a routing and transaction identifiers. Message order is guaranteed, if applicable, on a stream basis. Routing identifiers are typically used to indicate originator and destination (e.g., USIM to Home, ME to Serving, and also distinctions such as GSM between MM and CC for instance...). Transaction identifiers are used to distinguish streams with the same originator and destination. Messages can be sent within a transaction or not. Transactions are explicitly set up and released, either in-band (i.e., together with information transfer) or out-band. Transaction identifiers have only a local significance. NOTE 1: There is a difficulty behind the message order. In some cases it may be important to keep message order in a combination of streams, e.g., within a route, or even involving two routes. The model presented so far is too simple to cope with such cases. A quality of service indication is present in sending requests. This covers such aspects as message order, effect on other on-going traffic (e.g., speech pre-emption), delay. A finite number of quality of service classes will be identified, and the one to apply to a message indicated. With each transaction is associated a default quality of service, established at transaction establishment or by a subsequent modification request. A transmission mode indication is present in reception indications. This gives information from the Access Stratum on the aspects of the transmission related to service quality of service (e.g., speech has been pre-empted). 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 20 Release 1999 NOTE 2: This covers circuit data transport, including cases where each message is very small (down to 1 bit or other information quantum). Obviously, in such cases these primitives are a model not to be followed in implementations. 6.2.2.3.3.1 Data Transfer Request, IF Side Parameters Local connection reference local Route route Transaction identification local Transaction management enumerated (single, first, subsequent, last) Quality of Service indication QoS Message bit string The transaction management field indicates if the message is independent from transactions (single), is the first of the transaction and hence initialises the transaction (first), is the last of the transaction and hence releases the transaction (last), or is in the middle of a transaction. The primitive can be used with an empty message for transaction management alone (value 'single' is then meaningless). 6.2.2.3.3.2 Data Transfer Indication, UE Side Parameters Local connection reference local Route route Transaction identification local Transaction management enumerated (single, first, subsequent, last) Transmission mode indication transmission mode Message bit string 6.2.2.3.3.3 Data Transfer Request, UE Side Parameters Local connection reference local Route route Transaction identification local Transaction management enumerated (single, first, subsequent, last) Quality of Service indication QoS Message bit string 6.2.2.3.3.4 Data Transfer Indication, IF Side Parameters Local connection reference local Route route Transaction identification local Transaction management enumerated (single, first, subsequent, last) Transmission mode indication transmission mode Message bit string 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 21 Release 1999 6.2.2.3.4 IF Side Initiated Radio Access Bearer Establishment These operations allow the transfer of control messages for radio access bearer establishment between non-access strata elements on each side of the access interface. The operations pertain to the connection identified by the local connection reference parameter. The operations allow the IF side to initialise a radio access bearer. The operation also implies a request to the AS to allocate transmission resources to the radio access bearer. A radio access bearer identification uniquely identifies the radio access bearer. It is used in all primitives that pertain to the radio access bearer. It also serves as the binding to a NAS call. The Iu bearer identification identifies the Iu connection. A quality of service request specifies the bearer characteristics that apply to the radio access bearer. 6.2.2.3.4.1 IF Side Initiated Radio Access Bearer Establishment Request, IF Side Parameters Local connection reference local Radio access bearer identification bit string Iu bearer identification bit string Quality of Service request QoS 6.2.2.3.4.2 IF Side Initiated Radio Access Bearer Establishment Indication, UE Side Parameters Local connection reference local Radio access bearer identification bit string Iu bearer identification bit string 6.2.2.3.4.3 IF Side Initiated Radio Access Bearer Establishment Response, UE Side Parameters Local connection reference local Radio access bearer identification bit string Status enumerated (terminated by NAS, going on) 6.2.2.3.4.4 IF Side Initiated Radio Access Bearer Establishment Confirm, IF Side Parameters Local connection reference local Radio access bearer identification bit string Status enumerated (terminated by NAS, terminated by AS, going on) 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 22 Release 1999 6.2.2.3.5 IF Side Initiated Radio Access Bearer Release These operations allow the transfer of radio access bearer release messages between non-access strata elements on each side of the access interface. The operations pertain to the connection identified by the local connection reference parameter. The operations allow IF side to release a radio access bearer. NOTE: A radio access bearer release procedure is normally initiated by the IF side. Abnormal cases such as termination by the AS are FFS. 6.2.2.3.5.1 IF Side Initiated Radio Access Bearer Release Request, IF Side Parameters Local connection reference local Radio access bearer identification bit string 6.2.2.3.5.2 IF Side Initiated Radio Access Bearer Release Indication, UE Side Parameters Local connection reference local Radio access bearer identification bit string 6.2.3 IF side only operations 6.2.3.1 Dedicated control SAPs 6.2.3.1.1 Position update indication Parameters Local connection reference local Position position 6.2.3.1.2 Connection loss indication Parameters Local connection reference local 6.2.3.1.3 Streamlining required indication This operation is used by the AS to indicate that the connection runs the risk to be aborted unless a streamlining is done. Parameters Local connection reference local Proposed list of alternative AN/CN points AN/CN point list 6.2.3.1.4 Branch establishment request This operation establishes a new branch supporting dedicated mode transport for a given UE. 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 23 Release 1999 Parameters Local connection reference local Transaction list transaction list The transaction list describes the transactions for which the establishment prior the first transmission of data is required. 6.2.3.1.5 Branch establishment confirm This indicates that the branch is successfully established up to the UE and can then be used for transmission. As a result, the NAS may decide to remove the old branch. Parameters Local connection reference local 6.2.3.1.6 UE location information request This operation is sent from the NAS entity inside the CN (i.e. edge node) to the access network side of AS (i.e. URAN) to request the location information of a specific UE. Parameters: Local connection reference local Level of accuracy basic level or advanced level Type of request direct request or event request Event conditions to send information The level of accuracy describes the granularity required on the UE location information, either basic or advanced. The type of request describes whether the request is to get the current UE location or to get the location when some conditions specified by event are satisfied. 6.2.3.1.7 UE location information confirm This operation is sent in response to the UE location information request operation. Parameters: Local connection reference local Area ID UE location information in terms of CGI format Geographic coordinates UE location information in terms of coordinates Event conditions met The Area ID is to be formatted in accordance with the CGI (Cell Global Identity). The geographic co-ordinates represents the physical co-ordinates on the earth and uncertainty parameters. [To be completed] 6.2.4 UE side only operations 6.2.4.1 Dedicated control SAPs 6.2.4.1.1 Connection loss indication Parameters 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 24 Release 1999 Local connection reference local [To be completed] 6.3 Parameters structure 6.3.1 Local The structure is not relevant in the scope of this document, and can be decided on an implementation basis. 6.3.2 Bit string A finite ordered sequence of bit values. 6.3.3 Enumerated The parameter can take one value out of a list explicitly given. 6.3.4 Geographical description TBI 6.3.5 QoS This section describes the radio access bearer (RAB) by referencinga list of attributes related to the QoS. The radio access bearers are divided into two categories: - Restricted radio access bearers; - Unrestricted radio access bearers. An unrestricted radio access bearer is meant for data requiring bit sequence integrity (;e.g., N-ISDN data transport), whereas a restricted radio access bearer contains a description of the nature of the information (;e.g., encoded voice). For a restricted radio access bearer, the characteristics are implicitly given. The characterisation of a radio access bearer is made by using a set of attributes. A radio access bearer attribute is a specific characteristic that distinguishes it from other radio access bearer services. Refer to ref. [5] for a list of these QoS attributes. Particular values are also indicated in that specification for different services. In order to describe the desired radio access bearer service, QoS attributes are defined at the SAP. Note that it is not necessary, nor meaningful to support all possible combinations of parameter settings. NOTE: In case of an unrestricted radio access bearer, for every SDU provided at the SAP, bit sequence integrity should be maintained. 6.3.6 Route TBI 6.3.7 Transaction identifier Local. 6.3.8 Transaction list A list of transactions, each described by a transaction identifier (local) and by QoS parameters. 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 25 Release 1999 6.3.9 Transmission mode TBI 6.3.10 AN/CN Point List TBI TBI 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 26 Release 1999 Annex A (informative): Change history Document history 23.110 3.0.0 Approved at SMG#28. Document for Transfer to TSG-SA Document history 0.0.0 04.04.97 Initial Draft; preliminarily indicated as 23.yy 0.1.0 19.05.97 Second Draft; major improvements in clause 4.2 0.1.1 12.06.97 Revised version according to - decisions during the meeting 20-22.05.97, Sophia Antipolis - ETSI drafting rules, renamed as "23.10" 0.2.0 07.07.97 Revised version according to decisions during the meeting 30.06.-04.07.97, Sophia Antipolis. Major improvements in clause 5. 0.2.1 28.08.97 Revised version according to decisions during the meeting 30.06.-04.07.97, Sophia Antipolis. Some changes in clause 5. 0.3.0 22.09.97 Renumbered due to ETSI Drafting Rules, no changes since 0.2.1 0.3.1 12.11.97 Some editorial changes, in particular adding notes to invite contributions in order to align "older parts" of the document and "scope" 0.4.0 08.01.98 Revised version according to decisions during the meeting 17.-21.11.97, Kista: - adoption of document incl. title to the scope - improvements in clauses 4, 4.3.6 and 5.2.2.2. 0.5.0 23.01.98 Revised version according to decisions during the meeting 19.-21.01.98, Malmö: - figure 1 in clause 5.1 added 0.6.0 1998-04 Revised version according to decisions during the meeting 23.-27.03.98, Bad Aibling: - chapter 4 restructured (=> new chapter 5) - table on functions in-/outside Access stratum revised - some improvements in new chapter 5.6 0.6.1 1998-06 No changes since 0.6.0 but deletion of revision marks and reformatting to paper size "LETTER" instead of "A4" 0.7.0 1998-08 Revisions as agreed on TD 98s357 in June meeting (Chicago). NOTE: Other agreed revisions could not be inserted as the relevant documents were not electronically available (TDocs 466, 467, 469, 476) 0.7.1 1998-08 Editorial changes: - Some information from X.210 added. - some further textual alignment to the current state of 23.01 3G TS 23.110 version 3.4.0 Release 1999 ETSI ETSI TS 123 110 3.4.0 (2000-03) 27 Release 1999 0.8.0 1998-08 Revisions as agreed in August meeting (Sophia Antipolis). NOTE: Revisions according to TDocs 466, 467, 469, 476 are integrated also. 0.8.1 1998-09 Editorial alignment due to rapporteur´s notes on revisions as provided by TD 98s654 and additional text alignment. 1.0.0 1998-09 Version 1.0.0 for presentation for information to SMG#27 1.0.1 draft 1998-11 Editorial updates from ver. 0.8.0 to ver. 0.8.1, and text alignments. Addition of primitives, sections 6.2.2.3.4 and 6.2.2.3.5, for Control messages (Dedicated Control SAP) - RAB control procedures, Tdoc 98S720 (Rome). 1.0.1 1998-12 Addition of editorial comments from November (Castle Combe) meeting. 1.1.0 1999-01 Replacement of previous Section 5.14, Terminal Positioning, by new Section: UE Location Identification. With two enumerated bullet items, as agreed in the San Francisco meeting. 1.2.0 1999-02 Addition of third enumerated item into section 5.14. In same section, an editor´s note was inserted, regarding the need of primitives and operations, when the location services item is finalized. Title of section 5.4, replaced from ‘MS Tracking’ to ‘Location Management’. In Table 1, replacement of ‘UE positioning’ to ‘UE location identification’ and ‘UE Tracking’ to ‘UE location management’. Remove superfluous editor`s notes throughout the specification. 2.0.0 1999-02 Update in revision numbering for presentation to SMG#28 and provision to 3GPP for their baseline documentation. 3.0.0 1999-02 Approved at SMG#28. Document for Transfer to TSG-SA 3.1.0 1999-03 Addition of background information on UE location identification to section 5.14. Addition of primitives related to UE location information, sections 6.2.3.1.6-7: UE location information request and confirm, respectively. Both updates approved in S2#3, Nynaeshamn. Update related to transcoder location at the core network and source depending coding belonging to the non-access stratum. Updates agreed in Ad hoc in February in Paris and approved in S2#3. Table 1, editorial section 5.12, section 6.3.5, QoS, and Table A.1 - speech codec in access stratum. 3.2.0 1999-11 Inclusion of CR 002 (editorial) and CR003 (removal of the QoS parameters) as agreed by TSG SA#5. 3.3.0 2000-01 Inclusion of CR004 (note on CBS functions) and introduction of the figure in CR 003 (removal of the QoS parameters) not introduced by error in v.3.2.0, as approved by TSG SA#6. 3.4.0 2000-04 Inclusion of CR005 to clarify that the RAB identity can be used to by NAS elements to bind a RAB to the NAS API or corresponding. 3G TS 23.110 version 3.4.0 Release 1999 28 ETSI ETSI TS 123 110 V3.4.0 (2000-03) 3G TS 23.110 version 3.4.0 Release 1999 History Document history V3.4.0 March 2000 Publication
|
68bc2b39288c8c858c2e033e2c457f4f
|
123 108
|
1 Scope
|
........................................................................................................................................................5
|
68bc2b39288c8c858c2e033e2c457f4f
|
123 108
|
1.1 Scope of the Technical Specification
|
................................................................................................................. 5
|
68bc2b39288c8c858c2e033e2c457f4f
|
123 108
|
1.2 Application to the interface structures
|
............................................................................................................... 5
|
68bc2b39288c8c858c2e033e2c457f4f
|
123 108
|
1.3 Structure of layer 3 procedures
|
.......................................................................................................................... 5
|
68bc2b39288c8c858c2e033e2c457f4f
|
123 108
|
1.4 Test procedures
|
.................................................................................................................................................. 5
|
68bc2b39288c8c858c2e033e2c457f4f
|
123 108
|
1.5 Use of logical channels
|
...................................................................................................................................... 6
|
68bc2b39288c8c858c2e033e2c457f4f
|
123 108
|
1.6 Overview of control procedures
|
......................................................................................................................... 6
|
68bc2b39288c8c858c2e033e2c457f4f
|
123 108
|
1.6.1 List of procedures
|
......................................................................................................................................... 6
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.