1、 ETSI TS 123 236 V13.0.0 (2016-03) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes (3GPP TS 23.236 version 13.0.0 Release 13) TECHNICAL
2、 SPECIFICATION ETSI ETSI TS 123 236 V13.0.0 (2016-03)13GPP TS 23.236 version 13.0.0 Release 13Reference RTS/TSGS-0223236vd00 Keywords GSM,LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C
3、Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
4、 print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version ke
5、pt on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.a
6、spx If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopyin
7、g and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2016. A
8、ll rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registere
9、d and owned by the GSM Association. ETSI ETSI TS 123 236 V13.0.0 (2016-03)23GPP TS 23.236 version 13.0.0 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any,
10、is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on t
11、he ETSI Web server (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may
12、be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities.
13、These should be interpreted as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should
14、not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 12
15、3 236 V13.0.0 (2016-03)33GPP TS 23.236 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions, symbols and abbreviations . 7g33.1 Definitions 7g33.2 Symbols 7g33.3 Abbreviations
16、 . 7g34 General Description 8g34.1 Iu Flex Technical Requirements . 8g34.2 Overview 8g34.3 Pool-Area and Network Resource Identification 9g34.4 NAS Node Selection Function . 10g34.5 Load Balancing 11g34.5a Load Re-Distribution 12g34.5a.1 General 12g34.5a.2 Network Mode of Operation = 1 . 13g34.6 Mob
17、ility Management 13g34.7 Default CN node and Backwards Compatibility 13g34.8 Support of combined mobility management procedures 14g34.8.1 Attach 14g34.8.2 Routing area update 14g34.9 VGCS/VBS Compatibility Issues . 14g34.10 Interactions with E-UTRAN. 14g35 Functional Description . 15g35.1 MS Functio
18、ns . 15g35.2 RNC Functions . 15g35.2.1 Load Re-Distribution function in RNC . 16g35.3 BSC Functions 16g35.3.1 A interface mode . 16g35.3.2 Gb mode . 16g35.3.3 Iu mode . 17g35.3.4 Load Re-Distribution function in BSC . 17g35.4 MSC Functions . 17g35.4.1 TMSI Allocation . 17g35.4.2 Mobility Management
19、and Handover/Relocation . 17g35.4.3 Backward Compatibility and Default MSC 18g35.4.4 Support of Combined Procedures . 18g35.4.5 Load Re-Distribution function in MSC 18g35.5 SGSN Functions . 18g35.5.1 P-TMSI Allocation . 18g35.5.2 Mobility Management and Handover/Relocation . 18g35.5.3 Backward Compa
20、tibility and Default SGSN 19g35.5.4 Support of Combined Procedures . 19g35.5.5 CS Paging . 19g35.5.6 Load Re-Distribution function in SGSN . 19g36 Application Examples 19g36.1 Network configuration example 1 19g36.2 Network configuration example 2 20g3ETSI ETSI TS 123 236 V13.0.0 (2016-03)43GPP TS 2
21、3.236 version 13.0.0 Release 137 Specific Examples 21g37.1 Building blocks for signalling flows 21g37.1.1 RAN node selecting CN node in A interface mode 21g37.1.2 RAN node selecting CN node in Gb interface mode 21g37.1.3 RAN node selecting CN node in Iu interface mode 21g37.1.4 New CN node selecting
22、 old CN node . 21g37.1.5 Old CN node selecting new CN node . 21g37.1.6 SGSN selecting MSC 21g37.2 Signalling flow for Attach (Iu interface mode) 21g37.3 Signalling flows for Service Request (Iu interface mode) 24g37.3.1 Service Request initiated by MS . 24g37.3.2 Service Request initiated by network
23、 25g37.4 Signalling flow for Routing Area Update (Iu interface mode) . 26g37.5 IMSI attach procedure / Location area update with IMSI 29g3Annex A (informative): Network configuration examples 32g3A.1 One city centre surrounded by residential areas . 32g3A.1.1 Assumptions . 32g3A.1.2. TMSI calculatio
24、n 32g3A.2 3 Neighbouring large city centres 33g3A.3 Support of Dedicated Core Networks. 38g3Annex B (informative): Change history . 40g3History 41g3ETSI ETSI TS 123 236 V13.0.0 (2016-03)53GPP TS 23.236 version 13.0.0 Release 13Foreword This Technical Specification has been produced by the 3rd Genera
25、tion 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 a
26、nd 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
27、enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction UMTS will build on the success of GSM and is likely to become even more widespread, increasing the importance of a flexible network structure to
28、permit the different operational configurations in which these networks will be deployed. The requirements to have a RNC or BSC controlled by a single MSC server or SGSN lead to certain limitations. Allowing the BSCs and RNCs to connect to a number of MSC servers or SGSNs increases the networks perf
29、ormance in terms of scalability, distributing the network load amongst the serving entities, and reducing the required signalling as the user roams. ETSI ETSI TS 123 236 V13.0.0 (2016-03)63GPP TS 23.236 version 13.0.0 Release 131 Scope This document covers the details for the Intra Domain Connection
30、 of RAN Nodes to Multiple CN Nodes for GERAN and UTRAN based systems. In particular, it details the impacts to GSM and UMTS systems and the stage 2 procedures for the support of connecting a RNC or BSC to multiple MSC servers or SGSNs. The overall solution is described, and the detailed impacts on t
31、he existing specifications are identified. The description of a broadly similar concept for E-UTRAN based systems is not described in the document: instead, it is described in TS 23.401 22. NOTE: The specified solution impacts RAN nodes. In case an upgrade of radio networks is not performed, the sol
32、utions for deploying NNSF functionality above RAN nodes described in TR 23.924 23 may be used as a guideline for connecting RAN nodes to multiple MSC servers. The reference model to which these procedures apply can be found within TS 23.002 1. Detailed architectural requirements within the subsystem
33、s are contained within the remainder of the 23 series of specifications e.g. the requirements for the Packet Switched (PS) domain are contained within TS 23.060 2 and the requirements for the Bearer Independent CS Core Network are contained in TS 23.205 14. 2 References The following documents conta
34、in 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-specifi
35、c reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 1 3GPP TS 23.002: “Network Architecture“. 2 3GPP TS 23.060
36、: “General Packet Radio Service (GPRS) Service description; Stage 2“. 3 3GPP TS 23.012: “Location management procedures“. 5 3GPP TS 25.331: “Radio Resource Control (RRC) Protocol Specification“. 6 3GPP TS 25.301: “Radio interface protocol architecture“. 7 3GPP TS 25.303: “UE functions and inter-laye
37、r procedures in connected mode“. 8 3GPP TR 21.905: “3G Vocabulary“. 9 3GPP TS 25.413: “UTRAN Iu interface RANAP signalling“. 10 3GPP TS 25.410: “UTRAN Iu Interface: General Aspects and Principles“. 11 3GPP TS 23.228: “IP Multimedia Subsystem Stage 2“. 12 3GPP TS 43.051: “GSM/EDGE Radio Access Networ
38、k (GERAN) overall description (Stage 2)“. 13 3GPP TS 23.153: “Out of Band Transcoder Control - Stage 2“. 14 3GPP TS 23.205: “Bearer Independent CS Core Network Stage 2“. 15 3GPP TR 25.931: “UTRAN Functions, examples on signalling procedures“. 16 GSM 08.18: “General Packet Radio Service (GPRS);Base S
39、tation System (BSS) -Serving GPRS Support Node (SGSN); BSS GPRS Protocol (BSSGP)“. 17 3GPP TS 48.008: “Mobile-services Switching Centre - Base Station System (MSC - BSS) interface; Layer 3 specification“. ETSI ETSI TS 123 236 V13.0.0 (2016-03)73GPP TS 23.236 version 13.0.0 Release 1318 3GPP TS 23.00
40、3: “Numbering, addressing and identification“. 19 3GPP TS 43.068: “Voice Group Call Service (VGCS); Stage 2“. 20 3GPP TS 43.069: “Voice Broadcast Service (VBS); Stage 2“. 21 3GPP TS 23.251: “Network Sharing; Architecture and functional description“. 22 3GPP TS 23.401: “General Packet Radio Service (
41、GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access“. 23 3GPP TS 924: “Feasibility Study on NAS Node Selection Function above BSC/RNC“. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms defined in TR 21
42、.905 8 apply: CN node: for the purpose of this specification, and unless otherwise stated, a CN node is either an MSC or an SGSN. NAS node selection Function: The function used to assign specific network resources (i.e. MSC or SGSN) to serve a mobile station and subsequently route the traffic to the
43、 assigned network resource. Network Resource Identifier: A specific parameter used to identify the CN node assigned to serve a mobile station. Non-broadcast LAI/RAI: Each CN node in a pool have to be assigned one unique non-broadcast LAI/RAI that it use in case it want to be offloaded. Each CN node
44、in the pool has to be aware of the non-broadcast LAI/RAI assigned to the other CN nodes in the pool, because in case of re-distribution the target CN node will retrieve data (e.g. IMSI, security context, MM e.g. the possible downlink traffic can be equally shared between the SGSNs, or the share of e
45、ach SGSN can be proportional to the capacity of the SGSN. In case a MSC sends a paging-request with IMSI via Gs-interface the SGSN has to add the MSC/VLR-identity to the paging-request message. The NAS node selection function in the BSC/RNC shall upon reception temporarily store the MSC/VLR-identity
46、. 5.3.3 Iu mode To support MSs in Iu mode the BSC provides the same functionality as described under “RNC Functions“. 5.3.4 Load Re-Distribution function in BSC When the BSC receives a message with a null-NRI it uses the NAS Node Selection Function for selecting a CN node where to forward the messag
47、e. This is also done for all messages with random TLLIs (Gb-mode). CN node(s) with re-distribution in progress should be excluded from the NAS Node Selection algorithm in the BSC. This is done by O&M configuration in the BSC. 5.4 MSC Functions 5.4.1 TMSI Allocation Every MSC is configured with its o
48、ne or more specific NRI (O&M). One of these specific NRIs is part of every temporary identity (TMSI) which the MSC assigns to an MS. The TMSI allocation mechanism in the MSC generates TMSIs which contain one of the specific NRIs in the relevant bit positions. An NRI has a flexible length between 10
49、and 0 bits (0 bits means the NRI is not used and the feature is not applied). The use of the bits not used to encode the NRI is implementation dependent (e.g. to extent the TMSI space). An MSC applying “Intra Domain Connection of RAN nodes to multiple CN nodes” shall allocate TMSIs to the served MSs. 5.4.2 Mobility Management and Handover/Relocation For MAP signalling between two MSCs which both support the Intra Domain Connection of RAN Nodes to Multiple CN Nodes the new MSC derives the address of the ol
