hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
148fa1179989b1c16824d457a74e1069
|
123 012
|
3 General procedures in the network related to Location Mana
|
gement .....................................................8
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
3.1 Procedures in the MSC related to Location Updating
|
....................................................................................... 8
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
3.2 Procedures in the VLR related to Location Updating
|
........................................................................................ 8
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
3.3 Procedures in the HLR related to Location Updating
|
........................................................................................ 8 3.4 Normal Location Updating and IMSI detach/attach operation .......................................................................... 8
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
3.5 IMSI enquiry procedure
|
..................................................................................................................................... 8
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
3.6 Information transfer between Visitor and Home Location R
|
egisters................................................................. 8
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
3.6.1 Procedures for location management
|
........................................................................................................... 8
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
3.6.1.1 Location updating procedure
|
.................................................................................................................. 9
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
3.6.1.2 Downloading of subscriber parameters to the VLR
|
............................................................................... 9
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
3.6.1.3 Location cancellation procedure
|
............................................................................................................. 9
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
3.6.1.4 Mobile subscriber purging procedure
|
..................................................................................................... 9
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4 Detailed Procedures in the network related to Location Man
|
agement ....................................................9
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.1 Location Updating
|
........................................................................................................................................... 10
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.1.1 Detailed procedure in the MSC
|
.................................................................................................................. 10
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.1.1.1 Process Update_Location_Area_MSC
|
................................................................................................. 10
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.1.1.2 Procedure Authenticate_MSC
|
.............................................................................................................. 14
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.1.2 Detailed procedure in the VLR
|
.................................................................................................................. 15
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.1.2.1 Process Update_Location_Area_VLR
|
.................................................................................................. 15
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.1.2.2 Procedure Authenticate_VLR
|
............................................................................................................... 20
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.1.2.3 Procedure Location_Update_Completion_VLR
|
................................................................................... 22
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.1.2.4 Process Update_HLR_VLR
|
................................................................................................................. 25
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.1.2.5 Process Insert_Subs_Data_VLR
|
........................................................................................................... 26
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.1.2.6 Process Activate_Tracing_VLR
|
........................................................................................................... 27
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.1.2.7 Process Send_Identification_PVLR
|
..................................................................................................... 28
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.1.2.8 Process Trace_Subscriber_Activity_VLR
|
............................................................................................ 29
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.1.3 Detailed procedure in the HLR
|
.................................................................................................................. 30
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.1.3.1 Process Update_Location_HLR
|
........................................................................................................... 30
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.1.3.2 Procedure Insert_Subscriber_Data_HLR
|
............................................................................................. 34
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.1.3.3 Process Subscriber_Present_HLR
|
........................................................................................................ 36
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.1.3.4 Procedure Control_Tracing_HLR
|
........................................................................................................ 37
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.2 Location Cancellation
|
...................................................................................................................................... 38
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.2.1 Detailed procedure in the VLR
|
.................................................................................................................. 38
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.2.1.1 Process Cancel_Location_VLR
|
............................................................................................................ 38
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.2.2 Detailed procedure in the HLR
|
.................................................................................................................. 39
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.2.2.1 Process Cancel_Location_HLR
|
............................................................................................................ 39
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.3 Detach IMSI
|
..................................................................................................................................................... 40
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.3.1 Detailed procedure in the MSC
|
.................................................................................................................. 40
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.3.1.1 Process Detach_IMSI_MSC
|
................................................................................................................. 40
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.3.2 Detailed procedure in the VLR
|
.................................................................................................................. 41
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.3.2.1 Process Detach_IMSI_VLR
|
................................................................................................................. 41
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.4 Purge MS
|
......................................................................................................................................................... 43
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.4.1 Detailed procedure in the VLR
|
.................................................................................................................. 43 ETSI ETSI TS 123 012 V3.3.0 (2000-06) 4 3G TS 23.012 version 3.3.0 Release 1999
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.4.1.1 Procedure Purge_MS_VLR
|
.................................................................................................................. 43
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.4.2 Detailed procedure in the HLR
|
.................................................................................................................. 45
|
148fa1179989b1c16824d457a74e1069
|
123 012
|
4.4.2.1 Procedure Purge_MS_HLR
|
.................................................................................................................. 45 Annex A (informative): Change history...............................................................................................47 ETSI ETSI TS 123 012 V3.3.0 (2000-06) 5 3G TS 23.012 version 3.3.0 Release 1999 Foreword This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). The present document defines the location management procedures within the 3GPP system. 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 012 V3.3.0 (2000-06) 6 3G TS 23.012 version 3.3.0 Release 1999 1 Scope The present document describes the location management procedures for the circuit switched domain, with respect to the application level functional behaviour. This is to be distinguished from the corresponding protocol handling behaviour, which is specified in 3G TS 29.002. The following location management procedures are included: - location updating; - location cancellation; - MS purging; - IMSI attach/detach. The procedures in the Mobile Station (MS) are described in GSM 03.22. The procedures between MSC, VLR and HLR utilise the Mobile Application Part (MAP) and details concerning the protocol handling are contained in 3G TS 29.002. The present document excludes location management procedures for the packet switched domain, which are covered in 3G TS 23.060. The descriptions herein depict a logical separation between the MSC and VLR. This logical separation, as well as the messages transferred between the two logical entities are the basis of a model used to define the externally visible behaviour of the MSC/VLR, which a may be a single physical entity. They do not impose any requirement except the definition of the externally visible behaviour. 1.1 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. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. [1] 3G TR 21.905: "3G Vocabulary". [2] 3G TS 23.002: "Network architecture". [3] 3G TS 23.003: "Numbering, addressing and identification". [4] 3G TS 23.007: "Restoration procedures". [5] 3G TS 23.008: "Organization of subscriber data". [6] 3G TS 23.022: "Functions related to Mobile Station (MS) in idle mode". [7] 3G TS 23.116: "Super-Charger Technical Realisation; Stage 2". [8] 3G TS 29.002: "Mobile Application Part (MAP) specification". [9] 3G TS 29.007: "General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)". [10] GSM 03.20: "Digital cellular telecommunication system (Phase 2+); Security related network functions". ETSI ETSI TS 123 012 V3.3.0 (2000-06) 7 3G TS 23.012 version 3.3.0 Release 1999 [11] 3G TS 23.078: "CAMEL phase3 – stage2 " 1.2 Abbreviations Abbreviations are listed in 3G TR 21.905. 2 Definitions 2.1 Location management Location management means that the PLMNs keep track of where the MSs are located in the system area. The location information for each MS is stored in functional units called location registers. Functionally, there are two types of location registers: - the Home Location Register where all subscriber parameters of an MS are permanently stored, and where the current location may be stored; - the Visitor Location Register where all relevant data concerning an MS are stored as long as the station is within the area controlled by that visitor location register. See also GSM 03.02 where the network architecture is described, and GSM 03.08 where the data stored in the location registers are described. The action taken by a MS in order to provide location information to the PLMN will be referred to as location updating. 2.2 Location area and MSC area The MSC area is composed of the area covered by all base stations controlled by the MSC. An MSC area may consist of several location areas. A location area is an area in which, after having performed a location update once, MSs may roam without being required to perform subsequent location updates for reason of location change. A location area consists of one or more cells. For further details of the network architecture, see GSM 03.02. 2.3 Location area identification The Location Area Identification (LAI) plan is part of the base station identification plan. The base stations are identified uniquely (see GSM 03.03). 2.4 IMSI detach/attach operation The support of IMSI detach/attach operation is mandatory in MSs. The facility is optional in the fixed infrastructure of the PLMN. 2.4.1 Explicit IMSI detach/attach Explicit IMSI detach operation is the action taken by an MS to indicate to the PLMN that the station has entered an inactive state (e.g. the station is powered down). Explicit IMSI attach operation is the action taken by an MS to indicate that the station has re-entered an active state (e.g. the station is powered up). 2.4.2 Implicit IMSI detach Implicit IMSI detach operation is the action taken by the VLR to mark an MS as detached when there has been no successful contact between the MS and the network for a time determined by the implicit detach timer. The value of the implicit detach timer is derived from the periodic location updating timer. During an established radio contact, the ETSI ETSI TS 123 012 V3.3.0 (2000-06) 8 3G TS 23.012 version 3.3.0 Release 1999 implicit detach timer shall be prevented from triggering implicit detach. At the release of the radio connection, the implicit detach timer shall be reset and restarted. Implicit IMSI detach shall also be performed in the case of a negative response to an IMEI check. 2.5 Use of the term mobile station (MS) in the present document In order to simplify the text the term Mobile Station (MS) as used in relation to location management refers to the entity where the IMSI is stored, i.e., in card operated MSs the term Mobile Station (MS) refers to the card. 3 General procedures in the network related to Location Management 3.1 Procedures in the MSC related to Location Updating The MSC shall pass messages related to location updating between the MS and the VLR. 3.2 Procedures in the VLR related to Location Updating FFS 3.3 Procedures in the HLR related to Location Updating FFS 3.4 Normal Location Updating and IMSI detach/attach operation When receiving a Location Updating Request or an IMSI detach/attach message from an MS, the MSC shall convey the message to its associated Visitor Location Register. Any response from the location register shall similarly be conveyed to the MS. 3.5 IMSI enquiry procedure The MS shall identify itself by either the IMSI or the TMSI plus Location Area Identification of the previous VLR. In the latter case the new VLR shall attempt to request the IMSI and authentication parameters from the previous VLR by the methods defined in GSM 09.02. If this procedure fails, or if the TMSI is not allocated, the VLR shall request that the MS identifies itself by use of the IMSI. 3.6 Information transfer between Visitor and Home Location Registers 3.6.1 Procedures for location management Detailed procedures for exchange of and location updating information between visitor and home location registers are given in GSM 09.02. Below follows an overview of these procedures. ETSI ETSI TS 123 012 V3.3.0 (2000-06) 9 3G TS 23.012 version 3.3.0 Release 1999 3.6.1.1 Location updating procedure This procedure is used when an MS registers with a Visitor Location Register. The VLR provides its address to the HLR. The VLR may also allocate an optional identity for the MS at location updating: the Local Mobile Station Identity (see GSM 03.03). 3.6.1.2 Downloading of subscriber parameters to the VLR As a part of the location updating procedure, the Home Location Register will convey the subscriber parameters of the MS which need to be known by the visitor location register for proper call handling. This procedure is also used whenever there is a change in the subscriber parameters that need to be conveyed to the VLR (e.g. change in subscription, a change in supplementary services activation status). If the HPLMN applies the multinumbering option, different MSISDNs are allocated for different Basic Services (see GSM 09.07) and stored in the HLR. Among these MSISDNs, the Basic MSISDN Indicator as part of the HLR subscriber data (see GSM 03.08) marks the 'Basic MSISDN' to be sent to the VLR at location update. It is used in the VLR for call handling as calling party and as line identity. 3.6.1.3 Location cancellation procedure The procedure is used by the home location register to remove a MS from a visitor location register. The procedure will normally be used when the MS has moved to an area controlled by a different location register. The procedure can also be used in other cases, e.g. an MS ceases to be a subscriber of the Home PLMN. 3.6.1.4 Mobile subscriber purging procedure A VLR may purge the subscriber data for an MS which has not established radio contact for a period determined by the network operator. Purging means to delete the subscriber data and to "freeze" the TMSI that has been allocated to the purged MS in order to avoid double TMSI allocation. The VLR shall inform the HLR of the purging. When the HLR is informed of the purging, it shall set the flag "MS purged" in the IMSI record of the MS concerned. Presence of the "MS purged" flag will cause any request for routing information for a call or short message to the MS to be treated as if the MS were not reachable. In the VLR, the "frozen" TMSI is freed for usage in the TMSI allocation procedure by location updating for the purged MS in the same VLR, location cancellation for the purged MS or, in exceptional cases, by O&M. In the HLR, the "MS purged" flag is reset by the location updating procedure and after reload of data from the non- volatile back-up that is performed when the HLR restarts after a failure. 4 Detailed Procedures in the network related to Location Management 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. This specification shows the location management application processes interworking with the MAP protocol handler, which is specified in 3G TS 29.002. The MAP protocol defines supervision timers. If a supervision timer expires before a distant entity responds to a signal, the handling is as defined in 3G TS 29.002. In general, the protocol handler reports timer expiry to the application as an error condition or negative response. Where a timer is shown in this specification, therefore, it is an application timer rather than a protocol timer. Interworking with the protocol handlers uses functional signal names which do not necessarily have a one-to-one correspondence with the names of messages used in the MAP protocols. ETSI ETSI TS 123 012 V3.3.0 (2000-06) 10 3G TS 23.012 version 3.3.0 Release 1999 4.1 Location Updating 4.1.1 Detailed procedure in the MSC 4.1.1.1 Process Update_Location_Area_MSC Sheet 1: Location Update corresponds to a Location_Registration_Request indicating any of the following: - Normal location update; - Periodic location update; - IMSI attach. Sheet 2: When the MSC receives a Set Ciphering Mode request from the VLR, it sends a Start ciphering request towards the MS. After that, the Forward new TMSI and Update Location Area ack may be received in any order. ETSI ETSI TS 123 012 V3.3.0 (2000-06) 11 3G TS 23.012 version 3.3.0 Release 1999 Process in the MSC to handle an incoming Location Update Request and trigger the correct application process Process Update_Location_Area_MSC 1(3) Signals to/from the left are to/from the BSS Signals to/from the right are to/from the VLR Idle Location Update Update Location Area Wait_for_Location_ Updating_result Update Location Area ack Location Update ack Idle Update Location Area negative reponse Location Update reject Idle Trace Subscriber Activity 'Start active tracing' Wait_for_Location_ Updating_result Check IMEI Check_IMEI_ MSC See TS 23.018 Result= Pass? Idle Provide IMSI Obtain_IMSI_ MSC Authenticate Authenticate_ MSC Set Ciphering Mode 1 2 Yes No Figure 4.1.1.1 (sheet 1 of 3): Process Update_Location_Area_MSC ETSI ETSI TS 123 012 V3.3.0 (2000-06) 12 3G TS 23.012 version 3.3.0 Release 1999 Process in the MSC to handle an incoming Location Update Request and trigger the correct application process Process Update_Location_Area_MSC 2(3) Signals to/from the left are to/from the BSS Signals to/from the right are to/from the VLR Wait_for_Location_ Updating_result Forward check SS Check SS Wait_for_Location_ Updating_result MM release Abort Idle Figure 4.1.1.1 (sheet 2 of 3): Process Update_Location_Area_MSC ETSI ETSI TS 123 012 V3.3.0 (2000-06) 13 3G TS 23.012 version 3.3.0 Release 1999 Process in the MSC handle an incoming Location Update Req Process Update_Location_Area_MSC 3(3) Signals to/from the left are to/from the BSS Signals to/from the right are to/from the VLR 1 Cipher Command Wait_for_TMSI New TMSI Save TMSI Continue_to_Wait_ for_Location_ Updating_result Update Location Area ack Location Update ack Including new LAI and new TMSI Wait_for_TMSI_ Acknowledge_ from_MS New TMSI accepted Forward new TMSI ack Release Transaction Idle New TMSI rejected Forward new TMSI negative response Update Location Area negative response 2 Check IMEI Check_IMEI_MSC Result=Pass? Wait_for_TMSI Forward check SS Check SS MM release Abort Idle Update Location Area negative response 2 Update Location Area ack From VLR No Yes Figure 4.1.1.1 (sheet 3 of 3): Process Update_Location_Area_MSC ETSI ETSI TS 123 012 V3.3.0 (2000-06) 14 3G TS 23.012 version 3.3.0 Release 1999 4.1.1.2 Procedure Authenticate_MSC Procedure in the MSC to obtain an authentication response from the MS and relay it to the VLR Procedure Authenticate_MSC AUT_MSC1(1) Signals to/from the left are to/from the BSS; Signals to/from the right are to/from the VLR Authenticate Wait_For_ Auth_Response Authenticate ack Authenticate ack Result:= Pass Authenticate negative response Release transaction Authenticate negative response Result:= Aborted Figure 4.1.1.2 (sheet 1 of 1): Procedure Authenticate_MSC ETSI ETSI TS 123 012 V3.3.0 (2000-06) 15 3G TS 23.012 version 3.3.0 Release 1999 4.1.2 Detailed procedure in the VLR 4.1.2.1 Process Update_Location_Area_VLR General comment: at any stage in the location updating process the MSC may receive an indication from the BSS that the MM transaction has been released. The MSC then sends an Abort signal to the VLR. Upon receipt of this message, the VLR shall follow one of two possible courses of action. The two possible courses of action and the conditions determining which course shall be taken are as follows: 1. If a successfully authenticated radio connection is already established before the Abort message is received, the VLR shall ignore the message. 2. If a successfully authenticated radio connection has not been established before the Abort message is received, the VLR shall abort the Update Location Area process and return to the idle state. Sheet 1: the location area updating process will be activated by receiving an Update Location Area indication from the MSC. If there are parameter errors in the indication, the process is terminated with the appropriate error sent in the Update Location Area response to the MSC. Else, the behaviour will depend on the subscriber identity received, either an IMSI or a TMSI. Sheet 2: at the decision "HLR updating required?" the "True" branch shall be taken if and only if one or more of the following conditions is true: (1) Location Info Confirmed in HLR is false. (2) Data Confirmed by HLR is false. The type of Location Update is retrieved in 3G TS 23.078 procedure ‘Set_Notification_Type’ and is returned into the ‘Notify’ variable; this information is necessary for the CAMEL Mobility Management event notification procedure 3G TS 23.078 ‘Notify_gsmSCF’. ETSI ETSI TS 123 012 V3.3.0 (2000-06) 16 3G TS 23.012 version 3.3.0 Release 1999 Process in the VLR to handle an incoming Location Update Request and trigger the correct application process Process Update_Location_Area_VLR ULA_VLR1(4) Signals to/from the left are to/from the MSC Idle Update Location Area Identity used Previous LAI in this VLR? TMSI known? MSC area change? Location Info Confirmed in HLR:=False Subscriber Tracing active? Trace Subscriber Actibity 1 Data Confirmed by HLR:=False 2 Location Info Confirmed in HLR:=False PVLR address derivable? 3 Subscriber known in VLR? Previous LAI in this VLR? Location Info Confirmed in HLR:=False TMSI Yes Yes Yes Yes No No No No No Yes IMSI Yes No Yes No Figure 4.1.2.1 (sheet 1 of 4): Process Update_Location_Area_VLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 17 3G TS 23.012 version 3.3.0 Release 1999 Process in the VLR to handle an incoming Location Update Request and trigger the correct application process Process Update_Location_Area_VLR ULA_VLR2(4) Signals to/from the left are to/from the MSC 1 Authentication_ required? Authenticate_ VLR Authentication Result? Failure case? Idle Delete subscriber record Set negative response: Unknown Subscriber Update Location negative response Idle Set negative response: Illegal Subscriber Set negative response: system failure Confirmed by Radio Contact:=True Update LAI HLR updating required? 4 Location_Update_ Completion_VLR Result= Pass? Update Register Set_Notification_ _Type Procedure defined in 3G TS 23.078 Notify_gsmSCF Procedure defined in 3G TS 23.078 Authenticated Radio Contact Established ARC timer Application process Yes Fail Aborted Unknown Subscriber Illegal Subscriber Procedure Error Pass True False Yes No No Figure 4.1.2.1 (sheet 2 of 4): Process Update_Location_Area_VLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 18 3G TS 23.012 version 3.3.0 Release 1999 Process in the VLR to handle an incoming Location Update Request and trigger the correct application process Process Update_Location_Area_VLR ULA_VLR3(4) Signals to/from the right are to/from the PVLR 3 Request IMSI Attempt to retrieve IMSI from PVLR Wait_For_ PVLR_Response Request IMSI ack 1 Request IMSI negative response Obtain_IMSI_VLR See TS 23.018 Result= Pass? 1 Idle 2 Yes No Figure 4.1.2.1 (sheet 3 of 4): Process Update_Location_Area_VLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 19 3G TS 23.012 version 3.3.0 Release 1999 Process in the VLR to handle an incoming Location Update Request and trigger the correct application process Process Update_Location_Area_VLR ULA_VLR4(4) Signals to/from the left are to/from the MSC 4 Unknown HLR Update_HLR_VLR Result? Location_Update_ Completion_VLR Result= Pass? Update Register Set_Notification_ _Type Procedure defined in 3G TS 23.078 Notify_gsmSCF Procedure defined in 3G TS 23.078 Authenticated Radio Contact Established ARC timer Application process Idle Stand alone mode Set negative response: System Failure Update Location Area negative response Location_Update_ Completion_VLR Data confirmed by HLR:=False Delete Subscriber record Set negative response: Roaming Not Allowed Delete Subscriber record Set negative response: Unknown Subscriber 5 5 No Pass Yes No Procedure Error no Yes Roaming Not Allowed Unknown Subscriber Abort Yes Figure 4.1.2.1 (sheet 4 of 4): Process Update_Location_Area_VLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 20 3G TS 23.012 version 3.3.0 Release 1999 4.1.2.2 Procedure Authenticate_VLR Procedure in the VLR to authenticate an MS via the MSC Procedure Authenticate_VLR AUT_VLR1(2) Signals to/from the left are to/from the MSC; signals to/from the right are to/from the HLR. Authentication Failure Report Authentication sets available? Obtain_ Authentication_ Sets_VLR Result= Pass? Result= Aborted? Result:= Aborted Result= Procedure Error? Result:= Procedure Error Result:= Unknown Subscriber Authenticate Wait_For_ Authenticate_ Result Authenticate ack Received SRES= expected SRES? More authentication sets needed? Fetch_ Authentication_ Sets_VLR Authentication accepted Result:= Pass 1 Authenticate negative response More authentication sets needed? Fetch_ Authentication_ Sets_VLR Result:= Aborted 2 No No Yes No Yes No Yes Yes Yes No No Yes No Yes Figure 4.1.2.2 (sheet 1 of 2): Procedure Authenticate_VLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 21 3G TS 23.012 version 3.3.0 Release 1999 Procedure in the VLR to authenticate an MS via the MSC Procedure Authenticate_VLR AUT_VLR2(2) Signals to the left are to the MSC. Authentication Failure Report 1 Identity=IMSI? Retry with IMSI? Obtain_ IMSI_VLR Result= Pass? IMSI known? IMSI matches TMSI? Authentication rejected Result:= Illegal Subscriber Identity:= IMSI 2 Authentication accepted Result:= Unidentified Subscriber Result:= Aborted No Yes Yes Yes Yes No No No No Yes Figure 4.1.2.2 (sheet 2 of 2): Procedure Authenticate_VLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 22 3G TS 23.012 version 3.3.0 Release 1999 4.1.2.3 Procedure Location_Update_Completion_VLR Sheet 1: Decision "National Roaming Restrictions Exist?" distinguishes whether or not the subscriber is allowed service in the target LA, based on the current location of the MS and the VLR's knowledge of other networks. The "Yes" branch results in the sending of "Update Location Area Negative Response" toward the MSC (and the MS), with cause "National Roaming Not Allowed." However, subscriber data shall not be deleted from the VLR. This is to avoid unnecessary HLR updating should the subscriber be allowed subsequently to roam in other LAs of the same MSC. Sheet 1: Decision "Roaming restriction due to Unsupported Feature received in subscriber data?" distinguishes whether or not the subscriber data received from the HLR indicates "roaming restriction due to unsupported feature." The "Yes" branch results in the sending of "Update Location Area Negative Response" toward the MSC (and the MS), with cause "National Roaming Not Allowed." However, subscriber data shall not be deleted from the VLR. This is to avoid unnecessary HLR updating should the subscriber be allowed subsequently to roam in other LAs of the same MSC. Sheet 1: Decision "Regional subscription restriction" distinguishes whether or not the subscriber is allowed service in the target LA, which the VLR deduces based on regional subscription information received from the HLR. The "Yes" branch results in the sending of "Update Location Area Negative Response" toward the MSC (and the MS), with cause "location area not allowed." However, subscriber data shall not be deleted from the VLR. This is to avoid unnecessary HLR updating should the subscriber be allowed subsequently to roam in other LAs of the same MSC. ETSI ETSI TS 123 012 V3.3.0 (2000-06) 23 3G TS 23.012 version 3.3.0 Release 1999 Procedure in the VLR to complete Location Update Procedure Location_Update_Completion_VLR LUC_VLR1(2) Signals to/from the left are to/from the MSC National roaming restrictions exist? Roaming restriction Due To Unsupported Feature received in subscriber data? Set negative response: National Roaming Not Allowed LA Allowed:= False Result:=Pass Update Register Update Location Area negative response Regional subscription restriction 1 Set negative response: Location Area Not Allowed No Yes No No Yes Yes Figure 4.1.2.3 (sheet 1 of 2): Procedure Location_Update_Completion_VLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 24 3G TS 23.012 version 3.3.0 Release 1999 Procedure in the VLR to complete Location Update Procedure Location_Update_Completion_VLR LUC_VLR2(2) Signals to/from the left are to/from the MSC 1 LA Allowed:=True IMSI Detached := False Subscriber_ _Present_VLR See TS 29.002 Trace_Subscriber_ Activity_VLR TMSI to be reallocated? IMEI check required? Check_IMEI_VLR See TS 23.018 Result? Result:=Fail TMEI check Fail VLR application (Detach IMSI VLR) Set negative response: Illegal Equipment Update Location Area negative response Result:=Aborted Result:=Pass Update Location Area ack Set Ciphering Mode IMEI check required? Check_IMEI_VLR Result? Result:=Pass New TMSI Update Location Area ack WAIT_FOR_ _TMSI_Cnf Forward new TMSI ack Forward new TMSI negative response Freeze old TMSI No Yes Fail Aborted Pass No Yes Yes Pass Fail Aborted No Figure 4.1.2.3 (sheet 2 of 2): Procedure Location_Update_Completion_VLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 25 3G TS 23.012 version 3.3.0 Release 1999 4.1.2.4 Process Update_HLR_VLR Sheet 1: The procedure Check_User_Error_In_Serving_Network_Entity is specific to Super-Charger; it is specified in 3G TS 23.116 [7]. HL R up da ting in VL R Procedure U pdate_H LR _VLR U_HLR_VLR1(1) Sig na ls to /from th e rig ht a re to/fro m the H LR Sig na ls to /from th e le ft a re to /fro m the MS C Up dat e Lo ca tio n W A IT_ FO R _ DATA Ins ert Su b sc rib er Dat a Activa te Tra ce M od e Fo rwa rd Ch eck SS In dication Up dat e L o ca tio n a ck Upd ate L oca tion n eg ati ve respo n se In sert_ Sub s_ Data _ VLR Activa te _Tracin g_ VL R Fo rwa rd Ch eck SS In dicatio n Fa ilure Ca se ? W AIT_ FOR_ DATA W AIT_ FOR_ DA TA W AIT_ FOR_ DA TA R esult:= Ro am ing Not Allowed Re sult:= Un known Su bscribe r Res ult:= Pro ced ure Error Resu lt:= Ab ort Resu lt := Pass Ch eck_ Use r_E rror_ I n_ Se rving _ Ne two rk_E ntity S ee TS 2 3 .1 1 6 Da ta Co nfirm ed by H L R:=True Da ta Co nfirme d b y HLR:=False Loca tio n In fo Co nfirm ed in HL R: =True L oca tion In fo Co nfirme d in HLR:=Fal se Roa min g n ot Allowed Un kno wn Su bscribe r Proced u re Erro r A bo rt Figure 4.1.2.4 (sheet 1 of 1): Process Update_HLR_VLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 26 3G TS 23.012 version 3.3.0 Release 1999 4.1.2.5 Process Insert_Subs_Data_VLR Procedure to receive and store subscriber data in the VLR Procedure Insert_Subs_Data_VLR Insert_Subs_Data_VLR(1) Signals to/from the right are to/from the HLR Check_Parameters See TS 23.018 Result= Pass? All received features & services supported ? Update Subscriber Data MSC area restricted by regional subscription? Set MSC Area Restricted Insert Subscriber Data Ack Update subscriber data for supported feature(s) Set parameters for unsupported features Insert Subscriber Data negative response Yes Yes Yes No No No Figure 4.1.2.5 (sheet 1 of 1): Process Insert_Subs_Data_VLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 27 3G TS 23.012 version 3.3.0 Release 1999 4.1.2.6 Process Activate_Tracing_VLR Handling the Activate Trace Mode in the VLR Procedure Activate_Tracing_VLR 1(1) Signals to/from the right are to/from the HLR Signals to/from the left are to/from the MSC Check_Parameters See TS 23.018 Result= Pass? Subscriber Known? Tracing supported Set negative response Facility not supported Active Trace Mode negative response Tracing buffer full? Set Subscriber Tracing := Active Active Trace Mode Ack Set negative response Tracing buffer full Set negative response Unidentified subscriber Yes Yes No Yes No No No No Figure 4.1.2.6 (sheet 1 of 1): Process Activate_Tracing_VLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 28 3G TS 23.012 version 3.3.0 Release 1999 4.1.2.7 Process Send_Identification_PVLR Handling of the Send in the Previous VLR (PVLR) Process Send_Identification_PVLR SI_PVLR1(1) Signals to/from the are to/from the new Idle Send Identification Check Parameters Result= Pass? TMSI Known? Set IMSI Authentication sets available? Set Authentication Info Send Identification ack Idle Set negative unidentified subscriber Send Identification negative response Yes Yes Yes No No No Send Current SecurityContext Set Current Security Context Yes No Figure 4.1.2.7 (sheet 1 of 1): Process Send_Identification_PVLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 29 3G TS 23.012 version 3.3.0 Release 1999 4.1.2.8 Process Trace_Subscriber_Activity_VLR Proce du re in th e V LR to jud ge wh eth er to sen d tra ce su b scrib er a ctivity or n ot Pro cedure Trace_Subscriber_Activity_VLR 1(1) Sig na ls to /from th e le ft are to/ from th e M SC S ub scrib er Tra ce= a ctive ? T ra ce S ub scrib er A ctivity Yes No Figure 4.1.2.8 (sheet 1 of 1): Process Trace_Subscriber_Activity_VLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 30 3G TS 23.012 version 3.3.0 Release 1999 4.1.3 Detailed procedure in the HLR 4.1.3.1 Process Update_Location_HLR Sheet 1: The procedure Super_Charged_Cancel_Location_HLR is specific to Super-Charger; it is specified in TS 23.116 [7]. If the previous VLR and the originating HLR support the Super-Charger functionality, processing continues from the "Yes" exit of the test "Result=Pass?". Sheet 2: The procedure Super_Charged_Location_Updating_HLR is specific to Super-Charger; it is specified in TS 23.116 [7]. If subscription data needs to be sent to the VLR, processing continues from the "No" exit of the test "Result=Pass?". ETSI ETSI TS 123 012 V3.3.0 (2000-06) 31 3G TS 23.012 version 3.3.0 Release 1999 Proces s In th e HL R App licatio n to h an dlle L oca tion Upd atin g Process Update_Location_HLR 1(3) Sig na ls to /from th e le ft a re to /fro m th e VLR I DL E Up da te L oca tio n Ch eck_ P aram ete rs Se e TS 2 3.0 18 Re sult = P ass? S ub scrib er K nown ? S ubs crib er Tra cin g A ctive in V LR =False Ne twork A cc ess M od e= GP RS O nly? Ne w VLR ? S et ne ga tive re spo nse : Unk nown S ub sc rib er Su per_ Charg ed _ Ca n cel_L oc atio n_ HL R Se e TS 23 .11 6 Re sult : Pa ss? Upd ate L oca tion Neg at ive Res po nse Ca n ce l_L oca tio n_ HL R IDL E 1 Yes No No No Yes Yes No No Ye s Figure 4.1.3.1 (sheet 1 of 3): Process Update_Location_HLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 32 3G TS 23.012 version 3.3.0 Release 1999 Proces s In th e HL R App licatio n to h an dlle L oca tion Upd atin g Process Update_Location_HLR 2(3) Sig na ls to /from th e le ft a re to /fro m th e VLR 1 Su bscribe r Allo we d to Roa m in to PL MN? Upda te Ro ute ing Inf o S et Ne ga tive Re spo nse : Ro amin g Not Allow e d Re set Flag MS Purg ed Dele te Routein g I nfo Co ntro l_ Tra cin g _ HL R Upd ate L oca tion Neg a tive Re spo nse Re su lt = Pas s? I DL E IDLE Sup er_Ch arge d_ Lo ca tio n_ Upd atin g_ HL R See TS 23 .11 6 Re sult: = P ass? I nse rt_ S ub scrib er_ Da ta_ HLR Re sult = P ass? MSC A rea Re stricte d? OR Ro am ing Restricte d Du e t o Un sup po rted Fea tu re ? Resu lt= Ab orte d? Sub scribe r_ Pres ent _ HL R Upd ate L oca tion Neg at ive Res po nse IDLE 3 IDL E Ye s No No Ye s No Ye s Yes No No Yes No Y es Figure 4.1.3.1 (sheet 2 of 3): Process Update_Location_HLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 33 3G TS 23.012 version 3.3.0 Release 1999 Process In the HLR Application to handlle Location Updating Process Update_Location_HLR 3(3) Signals to/from the left are to/from the VLR 3 Check_SS_ Required Forward Check SS Indication Check_SS_ Required:= False Update Location Ack Location Updating Complete To Process CCBS_ Coordinator_HLR See 3GPP 23.093 Idle True False Figure 4.1.3.1 (sheet 3 of 3): Process Update_Location_HLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 34 3G TS 23.012 version 3.3.0 Release 1999 4.1.3.2 Procedure Insert_Subscriber_Data_HLR Procedure in the HLR Application for handling the insertion of subscriber data into the VLR Procedure Insert_Subscriber_Data_HLR 1(2) Signals to/from the left are to/from the VLR Insert Subscriber Data Count:=1 More Data To Send? Insert Subscriber Data Count:= Count + 1 WAIT_FOR_ ISD_Ack ISD_Ack Count:= Count - 1 1 Abort Result:= Aborted ISD Negative Response Set Negative Response System Failure Result:= Fail 2 3 Yes No Figure 4.1.3.2 (sheet 1 of 2): Procedure Insert_Subscriber_Data_HLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 35 3G TS 23.012 version 3.3.0 Release 1999 Procedure in the HLR Application for handling the insertion of subscriber data into the VLR Procedure Insert_Subscriber_Data_HLR 2(2) Signals to/from the left are to/from the VLR 1 Any services not supported in VLR? Ignore Unsupported Service? Replace Service In VLR? Unsupported Service Critical? HLR Internal Action MSC Area Restricted? Set MSC Area Restricted Count>0? WAIT_FOR_ ISD_Ack More data to send? Result:= Pass 3 Roaming Restricted Due To Unsupported Feature=True; MSC Area Restricted= True 2 Replace Service Yes No No No Yes Yes No No Yes No Yes Yes Yes No Figure 4.1.3.2 (sheet 2 of 2): Procedure Insert_Subscriber_Data_HLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 36 3G TS 23.012 version 3.3.0 Release 1999 4.1.3.3 Process Subscriber_Present_HLR Process in the HLR Application to perform actions required for short message alerting Process Subscriber_Present_HLR 1(1) MWD Set? Alert_Service_ Centre_HLR See TS 29.002 Section 25.10.2 Yes No Figure 4.1.3.3: Process Subscriber_Present_HLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 37 3G TS 23.012 version 3.3.0 Release 1999 4.1.3.4 Procedure Control_Tracing_HLR Procedure for Controlling Tracing in the HLR Application Procedure Control_Tracing_HLR 1(1) Signals to/from the left are to/from the VLR Subscriber tracing active in HLR? Subscriber Tracing active in VLR? Subscriber in HPLMN area? Result:=Pass Activate Trace Mode WAIT_FOR_ ATM_RESULT ATM_ack. Set Subscriber Tracing Active in VLR Result:=Pass ATM Negative Response Set Subscriber Tracing Inctive in VLR Report Error To O&M Center Result:=Fail Yes No Yes Figure 4.1.3.4 (sheet 1 of 1): Procedure Control_Tracing_HLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 38 3G TS 23.012 version 3.3.0 Release 1999 4.2 Location Cancellation 4.2.1 Detailed procedure in the VLR 4.2.1.1 Process Cancel_Location_VLR Handlig of the Cancel Location in the VLR Process Cancel_Location_VLR 1(1) Signals to/from the right are to/from the HLR Idle Cancel Location Check_Parameters See TS 23.018 Result= Pass? Subscriber registered Delete subscriber from register Release TMSI Cancel Location ack Idle Cancel Location negative response Idle Yes Yes No No Figure 4.2.1.1 (Sheet 1 of 1): Process Cancel_Location_VLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 39 3G TS 23.012 version 3.3.0 Release 1999 4.2.2 Detailed procedure in the HLR 4.2.2.1 Process Cancel_Location_HLR Process in the HLR application to initiate cancellation of location registration in a VLR Process Cancel_Location_HLR 1(1) Signals to/from the left are to/from the VLR Cancel Location WAIT_FOR_ ACK Cancel Location Ack Abort Repeat Location Cancellation? Wait for time expiry Cancel Location Negative Response Yes No Figure 4.2.2.1: Process Cancel_Location_HLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 40 3G TS 23.012 version 3.3.0 Release 1999 4.3 Detach IMSI 4.3.1 Detailed procedure in the MSC 4.3.1.1 Process Detach_IMSI_MSC Process in the MSC to handle an IMSI detach Process Detach_IMSI_MSC 1(1) Signals to/from the left are to/from the BSS Signals to/from the right are to/from the VLR Idle IMSI detach Explicit IMSI detach Idle Figure 4.3.1.1 (Sheet 1 of 1): Process Detach_IMSI_MSC ETSI ETSI TS 123 012 V3.3.0 (2000-06) 41 3G TS 23.012 version 3.3.0 Release 1999 4.3.2 Detailed procedure in the VLR 4.3.2.1 Process Detach_IMSI_VLR Sheet 1: The signal "Authenticated Radio Contact Terminated" is sent to Process Detach_IMSI_VLR from RR handling in the MSC whenever authenticated radio contact is terminated, e.g. at the release of a call. The 3G TS 23.078 procedure ‘Notify_gsmSCF’ with ‘Notify’ variable set either to ‘explicit’ or to ‘implicit detach’ allows the handling of CAMEL Mobility Management events notification. ETSI ETSI TS 123 012 V3.3.0 (2000-06) 42 3G TS 23.012 version 3.3.0 Release 1999 Process in the VLR to handle an Detach IMSI timer Process Detach_IMSI_VLR 1(1) Signals to/from the left are to/from the MSC unless marked otherwise Signals to/from the right are to/from the detach timer Idle Authenticated Radio Contact Established From Process Update_ Location_Area_VLR or Procedure Process_ Access_Request Stop timer Reload timer Idle Authenticated Radio Contact terminated IMSI Detached =False Restart timer Idle IMEI check fail From VLR application when IMEI check failed IMSI Detached =True Stop timer Idle Timer Expired Notify = implicit IMSI detach Notify_gsmSCF Procedure defined in 3G TS 23.078 Explicit IMSI detach Notify = explicit IMSI detach Figure 4.3.1.1 (Sheet 1 of 1): Process Detach_IMSI_VLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 43 3G TS 23.012 version 3.3.0 Release 1999 4.4 Purge MS 4.4.1 Detailed procedure in the VLR 4.4.1.1 Procedure Purge_MS_VLR Sheet 1: The procedure Purge_MS_In_Serving_Network_Entity is specific to Super-Charger; it is specified in TS 23.116 [7]. If the VLR and the originating HLR support the Super-Charger functionality, processing continues from the "Yes" exit of the test "Result=Pass?". ETSI ETSI TS 123 012 V3.3.0 (2000-06) 44 3G TS 23.012 version 3.3.0 Release 1999 Proces s in t he VL R to p urg e M S. Pro cess Purge_MS_ VLR 1(1) Sig nal s to /from th e rig ht a re to/ from th e HL R Sig na ls to /from th e le ft a re to /fro m t he Op eratio n & M aint en an ce Ce nt re I dle O &M Pu rg e MS P urge _M S_In_ S ervin g_ Ne tw ork_ E ntity S ee TS 23 .11 6 Re su lt:= P ass? P urge M S W A IT_FO R_ A CK Purg e M S Ack De lete Sub scribe r Da ta TMS I t o b e frozen ? Fre eze TM SI Set Purg ing Suc ce ssfu l O&M Pu rge MS ack Idle Pu rge _M S n eg ative resp o nse Se t Pu rge Fa ile d O &M Purg e M S n eg ative resp o nse Id le No Ye s No Yes Figure 4.4.1.1 (Sheet 1 of 1): Procedure Purge_MS_VLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 45 3G TS 23.012 version 3.3.0 Release 1999 4.4.2 Detailed procedure in the HLR Sheet 1: If the received VLR number and the stored VLR number do not match, the HLR sends Purge MS ack containing an empty result to indicate successful outcome. Since the MS is known by the HLR to be in a different VLR area, it is not appropriate to block mobile terminated calls or short messages to the MS, but the VLR which initiated the purging procedure can safely purge its record for the MS without freezing the TMSI. Sheet 1: If the received SGSN number and the stored SGSN number do not match, the HLR sends a Purge MS ack containing an empty result to indicate successful outcome. Since the MS is known by the HLR to be in a different SGSN area, it is not appropriate to block short messages to the MS, but the SGSN which initiated the purging procedure can safely purge its record for the MS without freezing the P-TMSI. ETSI ETSI TS 123 012 V3.3.0 (2000-06) 46 3G TS 23.012 version 3.3.0 Release 1999 Process in the HLR Application for handling the purging of MS data from a VLR Process Purge_MS_HLR 1(1) Signals to/from the left are to/from the VLR Idle Purge MS Check_ Parameters See TS 23.018 Result= Pass? Subscriber Known? Received VLR No. = Stored VLR No.? Set Flag MS Purged for non- GPRS Set Flag Freeze TMSI Received SGSN No. = Stored SGSN No.? Set Flag MS Purged for GPRS Set Flag Freeze P-TMSI Purge MS Ack. Idle Set Negative Response= Unknown Susbcriber Report Error to O&M Purge MS Negative Response Idle Purge MS Negative Response Idle Yes Yes Yes Yes No No No No Figure 4.4.2.1 (Sheet 1 of 1): Procedure Purge_MS_HLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 47 3G TS 23.012 version 3.3.0 Release 1999 Annex A (informative): Change history Change history TSG CN# Spec Version CR <Phase> New Version Subject/Comment Apr 1999 GSM 03.12 6.0.0 Transferred to 3GPP CN1 CN#03 23.012 3.0.0 Approved at CN#03 CN#06 23.012 3.0.0 001r1 R99 3.1.0 Restructuring of MAP Location Management Procedures, Stage 2 CN#06 23.012 3.0.0 002 R99 3.1.0 Introduction of Super-Charger into TS 23.012 CN#07 23.012 3.1.0 003r3 R99 3.2.0 Introduction of Enhanced User Identity Confidentiality CN#07 23.012 3.1.0 004 R99 3.2.0 Addition of Current Security Context Data to Send_Identification_PVLR CN#07 23.012 3.1.0 005 R99 3.2.0 Introduction of Authentication Failure Report 23.012 3.2.0 R99 3.2.1 CR 23.012-003r3 removed because implemented in error CN#08 23.012 3.2.1 006 R99 3.3.0 Introduction of Mobility Management event notification into 23.012 procedures 48 ETSI ETSI TS 123 012 V3.3.0 (2000-06) 3G TS 23.012 version 3.3.0 Release 1999 History Document history V3.1.0 January 2000 Publication V3.2.0 March 2000 Publication V3.3.0 June 2000 Publication
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
1 Scope
|
........................................................................................................................................................5
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
2 References
|
................................................................................................................................................5
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
3 Definitions and abbreviations
|
..................................................................................................................6
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
3.1 Definitions
|
......................................................................................................................................................... 6
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
3.2 Abbreviations
|
..................................................................................................................................................... 6
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
4 Applicability
|
............................................................................................................................................8
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
5 Description
|
...............................................................................................................................................8
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
6 Normal procedures with successful outcome
|
...........................................................................................9
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
7 Exceptional procedures
|
............................................................................................................................9
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
8 Addressing
|
...............................................................................................................................................9
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
9 Supplementary Services and Service Interworking
|
.................................................................................9
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
9.1 Calling line identification presentation (CLIP)
|
.................................................................................................. 9
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
9.2 Calling line identification restriction (CLIR)
|
..................................................................................................... 9 9.3 Connected line identification presentation COLP) .......................................................................................... 10
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
9.4 Connected line identification restriction (COLR)
|
............................................................................................ 10
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
9.5 Call Forwarding Unconditional (CFU)
|
............................................................................................................ 10
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
9.6 Call Forwarding on mobile subscriber Busy (CFB)
|
........................................................................................ 10
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
9.7 Call Forwarding on No Reply (CFNRy)
|
.......................................................................................................... 10 9.8 Call Forwarding on mobile subscriber Not Reachable (CFNRc)..................................................................... 10
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
9.9 Call Waiting (CW)
|
........................................................................................................................................... 10
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
9.10 Call hold (HOLD)
|
............................................................................................................................................ 10
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
9.11 Multiparty services (MPTY)
|
............................................................................................................................ 10
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
9.12 Closed User Group
|
.......................................................................................................................................... 10
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
9.13 Advice of Charge services
|
............................................................................................................................... 10
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
9.14 Barring of All Outgoing Calls (BAOC)
|
........................................................................................................... 10
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
9.15 Barring of Outgoing International Calls (BOIC)
|
............................................................................................. 11
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
9.16 Barring of Outgoing International Calls except those di
|
rected to the Home PLMN Country (BOIC- exHC)............................................................................................................................................................... 11
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
9.17 Barring of All Incoming Calls (BAIC)
|
............................................................................................................ 11
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
9.18 Barring of Incoming Calls when roaming outside the home
|
PLMN country (BIC-Roam) ............................. 11
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
9.19 Explicit Call Transfer (ECT)
|
........................................................................................................................... 11
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
9.20 Completion of Calls to Busy Subscriber (CCBS)
|
............................................................................................ 11
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
9.21 Support of Private Numbering Plan (SPNP)
|
.................................................................................................... 11
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
9.22 Multiple Subscriber Profile (MSP)
|
.................................................................................................................. 11
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
9.23 enhanced Multi-Level Priority and Pre-emption (eMLPP)
|
.............................................................................. 11
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
10 Interworking with other network features
|
..............................................................................................12
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
10.1 Customised Applications for Mobile network Enhanced Log
|
ic (CAMEL)..................................................... 12
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
10.2 Support of Optimal Routing (SOR)
|
................................................................................................................. 12
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
11 Networking interworking
|
.......................................................................................................................12
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
12 Charging aspects
|
....................................................................................................................................12
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
13 Lawful Interception Issues
|
.....................................................................................................................12 Annex A: (informative) Change history .......................................................................13 ETSI ETSI TS 122 066 V3.2.0 (2000-06) 4 3G TS 22.066 version 3.2.0 Release 1999 Foreword This Technical Specification has been produced by the 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 this TS, 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 specification; ETSI ETSI TS 122 066 V3.2.0 (2000-06) 5 3G TS 22.066 version 3.2.0 Release 1999 1 Scope This TS defines the stage one description of the Support of Mobile Number Portability between networks in the same country as well as North America cross-sector portability (i.e.,. number portability between fixed and GSM mobile networks). Stage one is an overall service description, primarily from the service subscriber's and user's points of view, but does not deal with the details of the human interface itself. Mobile Number Portability (MNP) is applicable only to those telecommunication services identified by an MSISDN. This specification includes information applicable to network operators, service providers and terminal, switch and database manufacturers. This specification contains the core requirements for the Support of Mobile Number Portability between network operators in the same country as well as North America cross-sector portability which are sufficient to provide a complete service. Other cross-sector portability options (e.g. number portability between fixed and mobile networks outside the North American Region) are outside the scope of this technical specification. It is highly desirable however, that technical solutions for MNP should be sufficiently flexible to allow for possible enhancements, e.g. cross-sector number portability, and MNP between analogue and digital mobile networks. Additional functionalities not documented in this specification may implement requirements which are considered outside the scope of this specification. This additional functionality may be on a network-wide basis, nation-wide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the core requirements of the service. Porting between Service Providers (i.e. service provider portability) which does not involve a change of Network Operator is outside the scope of this specification. The relationship between Service Providers and Network Operators is outside the scope of this specification. The relationship between a Service Provider and subscriber is outside the scope of this specification. The interface between the Mobile Station (MS) and any external applications are outside the scope of this specification. Charging principles are outside the scope of this specification except where explicitly stated in the text. 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. • For this Release 1999 document, references to GSM documents are for Release 1999 versions (version 8.x.y). [1] GSM 01.04 (ETSI ETR 350): “Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms”. [2] 3G TR 21.905: "Vocabulary for 3GPP Specifications". ETSI ETSI TS 122 066 V3.2.0 (2000-06) 6 3G TS 22.066 version 3.2.0 Release 1999 3 Definitions and abbreviations 3.1 Definitions For the purposes of this specification the following definitions apply: number range owner network: The network to which the number range containing the ported number has been allocated. directory number: any E.164 dialable number assigned to a wireline or a wireless subscriber. A DN can be a 10-digit number in the context of the North American Numbering Plan (without a country code) or up to 15 digits for an international number(country code included). donor network: The subscription network from which a number is ported in the porting process. This may or may not be the number range owner network. mobile number portability: The ability for a mobile subscriber to change digital mobile subscription network within the same country retaining their original DN(s). Additional regulatory constraints apply in North America. network operator: A PLMN operator. North American GSM number portability: the ability for a subscriber to change subscription between North American GSM networks and other subscription networks within an FCC regulated geographical area within North America originating network: the network where the calling party is located. ported number: Is a MSISDN that has undergone the porting process. ported subscriber: The subscriber of a ported number. porting process: A description of the transfer of a number between network operators. recipient network: The network which receives the number in the porting process. This network becomes the subscription network when the porting process is complete. service provider: An entity which offers service subscriptions to individual subscribers and contracts with a network operator to implement services for a specific DN. A service provider may contract with more than one network operator. service provider portability: The transfer of numbers between two unique Service Providers. subscription network: The network with which the customer’s Service Provider has a contract to implement the customer’s services for a specific DN. NOTE: The term "recipient network" is used during the porting process. The recipient network becomes the "subscription network" after the completion of the porting process. 3.2 Abbreviations For the purposes of this specification the following abbreviations apply: DN Directory Number MMI Man Machine Interface MNP Mobile Number Portability MSISDN Mobile Station ISDN number NAGNP North American GSM Number Portability PLMN Public Land Mobile Network SIM Subscriber Identity Module USIM Universal Subscriber Identity Module ETSI ETSI TS 122 066 V3.2.0 (2000-06) 7 3G TS 22.066 version 3.2.0 Release 1999 Further related abbreviations are given in GSM 01.04 [1] and TR 21.905 [2]. ETSI ETSI TS 122 066 V3.2.0 (2000-06) 8 3G TS 22.066 version 3.2.0 Release 1999 4 Applicability Mobile Number Portability cannot be offered to a subscriber as a stand alone service. Mobile Number Portability is applicable to all teleservices (e.g. SMS, voice, fax) and bearer services (e.g. data), except for TS12 (emergency call). The implementation of MNP shall be flexible enough to apply to each DN of a subscriber separately. Where the DNs used in the donor network are ported to different recipient mobile networks then a new IMSI (and SIM/USIM) will be required for each recipient network. The basic and supplementary services provisioned in the recipient network shall not be dependent on those that were provisioned in the donor network. 5 Description Mobile Number Portability (MNP) is the ability for a mobile subscriber to change digital mobile subscription networks within the same country whilst retaining her original DN or DNs. Additional regulatory constraints apply in North America. North American GSM Number Portability (NAGNP) is the ability for a subscriber to change subscription between North American GSM networks and other subscription networks within an FCC regulated geographical area within North-America. The IMSI shall not be ported, hence the recipient mobile network of the porting process will issue a new IMSI for the ported subscription. The porting process may, but need not, include a change in service provider. The ported subscriber can use exactly the same services as non-ported customers in the same subscription network. That is: whether the DN of a subscriber belongs to a subscription network or is ported to the subscription network shall have no influence on the services offered to the customer by that subscription network. The services offered by the number range owner network and/or the donor network have no influence on the services offered by the subscription network. When a subscriber ports a DN to a new network then the donor network no longer provides support for the services of the ported number (this includes supplementary and value added services). NOTE: This also implies that if a service supported in the donor network is not available on the recipient network then number portability mechanisms need not provide that service for the ported subscriber. A network can be a donor of numbers and a recipient of numbers. A DN can be ported more than once; a ported number can be ported back to its number range owner network. Even after multiple portings, the technical solution shall involve only the number range owner network and recipient network. The solution for MNP/NAGNP shall have a minimal adverse effect upon the quality of service offered to ported and non-ported subscribers. It may be the case that the quality of service for ported and non-ported subscribers differs slightly (e.g. due to additional call set-up delay). Any additional delay in call set-up to ported numbers shall be minimised. The process of porting a number may involve a disruption in service to the customer. The time that no service is available shall be minimised. The technical implementation of the support of MNP/NAGNPin a network should not impede number availability and efficient use of numbers. The technical implementation for the support of MNP/NAGNPshall not involve loss of functionality in the number range owner, donor or subscription network. The technical implementation of MNP/NAGNPshall support optimisation of the use of network and inter-network resources so as to minimise costs associated with transport of traffic and/or appropriate signalling and/or processing activities (e.g. optimal routing). In addition, for the porting process an efficient and effective way is needed to exchange porting information between all types of network operators. ETSI ETSI TS 122 066 V3.2.0 (2000-06) 9 3G TS 22.066 version 3.2.0 Release 1999 6 Normal procedures with successful outcome Mobile Number Portability is offered to all subscribers of telephone services subject to regulatory requirements. A porting process is initiated at a subscriber’s request on their selected DN(s) with the relevant networks. Initiation of the porting process is an off-line administrative process and cannot be invoked via a specific MMI on the hand-set. After successful porting the subscriber, is able to use the provisioned telephone services and network specific services of the subscription network as offered to non-ported subscribers on that network. Porting will effectively initiate a new subscription As part of the porting process, the donor, number range owner and recipient networks shall update their relevant network elements in order to perform the porting. After the porting process is complete, the subscription details related to the ported DN on the donor network shall not be required and can be deleted. Therefore, only the number range owner network and the recipient network are involved in the MNP/NAGNPsolution for support of service to the ported subscriber. The originating network may not be aware of the ported nature of the number; therefore the technical solution shall work even if networks other than the number range owner and recipient have no knowledge of the ported nature of the number. NOTE: Other networks may be involved to increase the efficiency of call-set-up to ported numbers. When a ported subscriber takes an additional DN at her subscription network that additional DN should not have to come from the number range owner network(s) of the subscriber’s ported numbers. Where number ranges are assigned to network operators, the number range owner network shall receive the ported number back from the recipient network when the subscriber relinquishes the ported number, i.e. when the ported number ceases to be an active service number. 7 Exceptional procedures Service related data (e.g. numbers used in the call-forwarding service, etc.) may not be transferred to the recipient network during the porting process. 8 Addressing As a consequence of MNP, the DN of a subscriber may no longer explicitly identify the subscription network of that subscriber. 9 Supplementary Services and Service Interworking The support of mobile Number Portability in a network shall not affect the handling of supplementary service for the subscribers, i.e. there shall be no difference in the handling of the supplementary services between ported in and normal subscribers of the same network. 9.1 Calling line identification presentation (CLIP) No impact. 9.2 Calling line identification restriction (CLIR) No impact. ETSI ETSI TS 122 066 V3.2.0 (2000-06) 10 3G TS 22.066 version 3.2.0 Release 1999
|
c2b2d90a0f1db38b8cdf511166e9abaa
|
122 066
|
9.3 Connected line identification presentation (COLP)
|
No impact. 9.4 Connected line identification restriction (COLR) No impact. 9.5 Call Forwarding Unconditional (CFU) No impact. 9.6 Call Forwarding on mobile subscriber Busy (CFB) No impact. 9.7 Call Forwarding on No Reply (CFNRy) No impact. 9.8 Call Forwarding on mobile subscriber Not Reachable (CFNRc) No impact. 9.9 Call Waiting (CW) No impact. 9.10 Call hold (HOLD) No impact. 9.11 Multiparty services (MPTY) No impact. 9.12 Closed User Group No impact. 9.13 Advice of Charge services No impact. 9.14 Barring of All Outgoing Calls (BAOC) No impact. ETSI ETSI TS 122 066 V3.2.0 (2000-06) 11 3G TS 22.066 version 3.2.0 Release 1999 9.15 Barring of Outgoing International Calls (BOIC) No impact. 9.16 Barring of Outgoing International Calls except those directed to the Home PLMN Country (BOIC-exHC) No impact. 9.17 Barring of All Incoming Calls (BAIC) No impact. 9.18 Barring of Incoming Calls when roaming outside the home PLMN country (BIC-Roam) No impact. 9.19 Explicit Call Transfer (ECT) No impact. 9.20 Completion of Calls to Busy Subscriber (CCBS) No impact. 9.21 Support of Private Numbering Plan (SPNP) No impact. 9.22 Multiple Subscriber Profile (MSP) The porting process may apply on a per profile basis. 9.23 enhanced Multi-Level Priority and Pre-emption (eMLPP) No impact. ETSI ETSI TS 122 066 V3.2.0 (2000-06) 12 3G TS 22.066 version 3.2.0 Release 1999 10 Interworking with other network features 10.1 Customised Applications for Mobile network Enhanced Logic (CAMEL) No impact. 10.2 Support of Optimal Routing (SOR) No impact. NOTE: This is a service requirement. However, it may be difficult to find an MNP solution with no impact on Optimal Routing. 11 Networking interworking All services offered in co-operation with other types of networks shall still be offered in combination with MNP. This includes the basic services, all supplementary services and all network features. 12 Charging aspects No additional charging mechanisms relating to the calling party are to be standardised. Enough information should be collected to allow the involved networks to workout inter-network charging. 13 Lawful Interception Issues Lawful interception shall be possible on a ported MSISDN. ETSI ETSI TS 122 066 V3.2.0 (2000-06) 13 3G TS 22.066 version 3.2.0 Release 1999 Annex A: (informative) Change history Change history TSG SA# SA Doc. SA1 Doc Spec CR Rev Rel Cat Subject/Comment Old New Jun 1999 02.66 Transferred to 3GPP SA1 7.0.0 SA#04 22.066 Version 3.0.0 Approved 3.0.0 SP-05 SP-99479 S1-99621 22.066 001 R99 D Editorial changes for alignment to 3GPP 3.0.0 3.0.1 SP-07 SP-000061 S1-000134 22.066 002 R99 B PCS-1900 Service Provider Number Portability impacts for Mobile Number Portability 3.0.1 3.1.0 SP-08 SP-000207 S1-000434 22.066 003 R99 F North American Service Provider Number Portability impacts for Mobile Number Portability 3.1.0 3.2.0 14 ETSI ETSI TS 122 066 V3.2.0 (2000-06) 3G TS 22.066 version 3.2.0 Release 1999 History Document history V3.0.1 January 2000 Publication V3.1.0 March 2000 Publication V3.2.0 June 2000 Publication
|
612acd83a10f97488996fc4a31d9f8db
|
124 072
|
1 Scope
|
........................................................................................................................................................5
|
612acd83a10f97488996fc4a31d9f8db
|
124 072
|
2 References
|
................................................................................................................................................5
|
612acd83a10f97488996fc4a31d9f8db
|
124 072
|
3 Definitions and abbreviations
|
..................................................................................................................5
|
612acd83a10f97488996fc4a31d9f8db
|
124 072
|
3.1 Abbreviations
|
..................................................................................................................................................... 5
|
612acd83a10f97488996fc4a31d9f8db
|
124 072
|
4 Call Deflection (CD)
|
................................................................................................................................6
|
612acd83a10f97488996fc4a31d9f8db
|
124 072
|
4.1 Normal operation
|
............................................................................................................................................... 6
|
612acd83a10f97488996fc4a31d9f8db
|
124 072
|
4.1.1 Served mobile subscriber side
|
...................................................................................................................... 6
|
612acd83a10f97488996fc4a31d9f8db
|
124 072
|
4.1.2 Deflected-to mobile subscriber side
|
............................................................................................................. 7
|
612acd83a10f97488996fc4a31d9f8db
|
124 072
|
4.1.3 Calling mobile subscriber side
|
..................................................................................................................... 7 Annex A: Change history........................................................................................................................8 History................................................................................................................................................................9 ETSI TS 124 072 V3.0.0 (2000-01) (3G TS 24.072 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.072 V3.0.0 (1999-05) 4 3G TS 24.072 version 3.0.0 Foreword This Technical Specification has been produced by the 3GPP. This TS describes procedures on the radio interface for the call deflection supplementary service within the 3GPP system. 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 this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version 3.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 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 specification; ETSI TS 124 072 V3.0.0 (2000-01) (3G TS 24.072 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.072 V3.0.0 (1999-05) 5 3G TS 24.072 version 3.0.0 1 Scope This Global System for Mobile communications Technical Specification specifies the procedures used at the radio interface (reference point Um as defined in GSM 04.02) for normal operation of Call Deflection (CD) supplementary service. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface. 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. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] GSM 02.72: "Digital cellular telecommunications system (Phase 2+); Call Deflection (CD) supplementary service Stage 1". [3] GSM 04.02: " Digital cellular telecommunications system (Phase 2+); GSM Public Land Mobile Network (PLMN) access reference configuration". [4] GSM 04.08: " Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". [5] GSM 04.80: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 supplementary services specification; Formats and coding". 3 Definitions and abbreviations 3.1 Abbreviations Abbreviations used in this specification are listed in GSM 01.04. ETSI TS 124 072 V3.0.0 (2000-01) (3G TS 24.072 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.072 V3.0.0 (1999-05) 6 3G TS 24.072 version 3.0.0 4 Call Deflection (CD) 4.1 Normal operation 4.1.1 Served mobile subscriber side The served mobile subscriber may invoke the call deflection supplementary service if an incoming call is offered. According to GSM 02.72 this may happen as an automatic response from the mobile station if the call is offered or as the result of a subscriber action. The mobile station shall invoke the call deflection supplementary service by initiating call clearing with a DISCONNECT message including the call deflection request (refer to figure 4.1). The call deflection request shall contain the DeflectedToNumber which may be accompanied by a DeflectedToSubAddress. The MS may invoke the call deflection supplementary service at every time after call confirmation until the call is accepted (refer to GSM 04.08). If the network accepts the call deflection request, it shall continue call clearing. The result indication shall be returned to the mobile station in the RELEASE message. If the network cannot accept the call deflection request, it shall continue call clearing. The corresponding error indication shall be returned to the mobile station in the RELEASE message. Error values are specified in GSM 04.80. During the call deflection request the MS shall run a timer TCD. This timer is started when the call deflection request is sent and stopped when a response is received from the network. If this timer expires the MS shall assume that the call deflection request has failed, locally release the invokeID, inform the user of the failure and continue call clearing as defined in GSM 04.08. MS Network SETUP <------------------------------------------------------------------------------------------------------------------------ CALL CONFIRMED ------------------------------------------------------------------------------------------------------------------------> • • • DISCONNECT ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = CallDeflection (DeflectedToNumber, DeflectedToSubAddress)) RELEASE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result) RELEASE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject = (Invoke Problem)) RELEASE COMPLETE ------------------------------------------------------------------------------------------------------------------------> Figure 4.1: Call deflection invocation for an incoming call ETSI TS 124 072 V3.0.0 (2000-01) (3G TS 24.072 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.072 V3.0.0 (1999-05) 7 3G TS 24.072 version 3.0.0 4.1.2 Deflected-to mobile subscriber side As for the call forwarding supplementary services the deflected-to mobile subscriber will receive a NotifySS operation containing the SS Notification indicating that the incoming call is a forwarded call. When available, the SS Code of the Call Deflection supplementary service is included, see figure 4.2. When multiple diversions occurs the value of the SS Code shall relate to the last invoked diversion service. In addition the deflected-to subscriber will receive the redirecting party BCD number and optionally, a redirecting party subaddress. The redirecting party BCD number information element is made up of a number of information units as defined in GSM 04.08. In addition to or instead of the redirecting party's digits, the subscriber may be given the following information: - screening indicator; - presentation indicator. Indicator values are given in GSM 04.08. The redirecting party subaddress information element is made up of a number of information units as defined in GSM 04.08. MS Network SETUP <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (CD, SS-Notification)), Redirecting party BCD number (screening indicator, presentation indicator, redirecting party digits), Redirecting party subaddress Figure 4.2: Notification to the forwarded to mobile subscriber that the incoming call is a forwarded call As a subscription option, the served mobile subscriber can request that the calling mobile subscriber receives a NotifySS operation containing the SS Notification indicating that the call has been deflected. When available, the SS Code of the call deflection supplementary service is included, see figure 4.3. MS Network SETUP ------------------------------------------------------------------------------------------------------------------------> FACILITY <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (CD, SS-Notification)) Figure 4.3: Notification to the calling mobile subscriber that the call is forwarded ETSI TS 124 072 V3.0.0 (2000-01) (3G TS 24.072 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.072 V3.0.0 (1999-05) 8 3G TS 24.072 version 3.0.0 Annex A: Change history Change history TSG CN# Spec Version CR <Phase> New Version Subject/Comment Apr 1999 GSM 04.72 7.0.0 Transferred to 3GPP CN1 CN#03 24.072 3.0.0 Approved at CN#03 ETSI TS 124 072 V3.0.0 (2000-01) (3G TS 24.072 version 3.0.0 Release 1999) ETSI 9 ETSI ETSI TS 124 072 V3.0.0 (2000-01) (3G TS 24.072 version 3.0.0 Release 1999) History Document history V3.0.0 January 2000 Publication
|
c4dcc5fb97678154a0beb0ac23aec589
|
122 096
|
2 References
|
................................................................................................................................................5
|
c4dcc5fb97678154a0beb0ac23aec589
|
122 096
|
3 Definitions and abbreviations
|
..................................................................................................................5
|
c4dcc5fb97678154a0beb0ac23aec589
|
122 096
|
3.1 Definitions
|
......................................................................................................................................................... 5
|
c4dcc5fb97678154a0beb0ac23aec589
|
122 096
|
3.2 Abbreviations
|
..................................................................................................................................................... 6
|
c4dcc5fb97678154a0beb0ac23aec589
|
122 096
|
4 Calling Name Presentation (CNAP)
|
........................................................................................................6
|
c4dcc5fb97678154a0beb0ac23aec589
|
122 096
|
4.1 Definition
|
........................................................................................................................................................... 6
|
c4dcc5fb97678154a0beb0ac23aec589
|
122 096
|
4.2 Description
|
......................................................................................................................................................... 6
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.