File 083

RAN Sharing
WCDMA RAN
Feature Guide
RAN Sharing Feature Guide

Version V4.5 Date 2010-10-15 Author Wang Yong Wang Yong Approved By Chen Hui, Wang Jicheng, Xu Bing Luyi Remarks Not open to the Third Party 3.7 is modified and the corresponding parameter is added
V5.0
2010-12-29
2011 ZTE Corporation. All rights reserved. ZTE CONFIDENTIAL: This document contains propriet ary information of ZTE and is not to be disclosed or used without the prior written permission of ZTE. Due to update and improvement of ZTE products and technologies, information in this document is subjected to change without notice.
ZTE Confidential Proprietary
2011 ZTE Corporation. All rights reserved.
TABLE OF CONTENTS
1 2 2.1 2.2 2.3 2.4 2.5 2.6 2.7 3 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.11 4 4.1 4.1.1 4.1.2 4.1.3 4.1.4 4.1.5 4.1.6 5 6 Function Attribute ............................................................................................... 1 Overview .............................................................................................................. 1 Function Introduction ............................................................................................ 1 Basic Network Sharing Support............................................................................ 2 RAN Sharing with Dedicated Carrier .................................................................... 3 Shared Network Access Control........................................................................... 4 RAN Sharing with Shared Carrier......................................................................... 5 Operator Specific CE Resource ........................................................................... 5 Operator Specific FM/PM/CM............................................................................... 6 Technical Description......................................................................................... 6 Shared Network Mode .......................................................................................... 6 RNC Multi-PLMN Configuration............................................................................ 6 Information Transfer Process ............................................................................... 7 SNA Access Information (lu) of A Single Specified User ..................................... 9 SNA Information Transfer in the DRNC Cell ...................................................... 10 Mobility Management of The Shared Network ................................................... 11 Routing Function in MOCN Mode....................................................................... 11 Paging of Network Sharing ................................................................................. 14 Reset Process in Network Sharing ..................................................................... 15 The support of system broadcast procedure for the network sharing ............... 15 CE Sharing Method............................................................................................. 19 Parameters and Configurations ...................................................................... 20 Parameter List..................................................................................................... 20 SHAREDNETMODE ........................................................................................... 20 PLMNNUM (UTRAN Cell)................................................................................... 21 COMMONPLMNIND ........................................................................................... 21 PLMNNUM (ExternUtranCell)............................................................................. 21 PLMNNUM (ExternGSMCell) ............................................................................. 21 ADJPHYGSMCID ............................................................................................... 22 Counters and Warnings ................................................................................... 24 Abbreviation ...................................................................................................... 24
II
FIGURES
Figure 2-1 The networking diagram of MOCN network sharing method ................................ 2 Figure 2-2 Gateway core network sharing .............................................................................. 2 Figure 2-3 Figure 3-1 Figure 3-2 Independent Carrier Network Sharing ................................................................... 4 Information Transfer Message Process ................................................................. 7 MOCN reroute procedure..................................................................................... 14
TABLES
Table 3-1 Shared Network Information Structure.................................................................... 8 Table 3-2 SNAC Structure ....................................................................................................... 9 Table 3-3 SNA Access Information Cell Structure .................................................................. 9 Table 3-4 SNA Information Transfer in the DRNC Cell......................................................... 10 Table 4-1 Network Sharing Parameter List ........................................................................... 20
III
Function Attribute
System version: [RNC V3.09, Node B V4.09, OMMR V3.09, and OMMB V4.09] Attribute: [Optional] Relat ed NEs: UE NodeB RNC MSCS MGW SGSN GGSN HLR
Note: * -: Not involved

* : Invol ved
Dependency: None Exclusion: None
2
2.1
Overview
Function Introduction
Due to the long period and high cost for establishing a 3G net work, a single operator is hard to establish a 3G network with complete co verage in a short time, while the business combination between operators requires the sharing bet ween different networks. To satisfy the above requirements, the 3GPP develops the sharing network technology. This technology can be adopted for operators to s hare the access network section that is the largest part in the network investment, thus reduce the investment of the 3G network, enhance the layout speed, and integrate the access network resources of different operators. It is particularly important for operators at the early stage. The following 6 features are supported in UNTRAN sharing. 1 2 3 4 5 6 Basic network sharing support. Dedic ated carrier network sharing support. Shared network access control. Shared carrier network sharing. Operator differentiated CE allocation. Operator differentiated network management.
2.2
Basic Network Sharing Support

ZTE RAN devices support two 3GPP-defined UTRA N net work sharing methods. Multi-operator core net work (MOCN)
Figure 2-1
The networking diagram of MOCN network sharing method

CN Operator B CN Operator C
CN Operator A
Iu
RNC
Node B
Radio Access Network Operator X
Node B
In this networking mode, different operat ors have different CN devices, and all the CN devic es are connected to the same RNC, sharing the RA N radio resources. Gateway core network (GWCN)
Figure 2-2
Gateway core network sharing
CN Operator A
CN Operator B
CN Operator C
Shared MSC/SGSN
Shared MSC/SGSN
Shared MSC/SGSN
Iu
RNC
RNC
Radio Access Network Operator X
RNC
The networking diagram of GWCN net work sharing method In this networking mode, different operators us e the same CN devices (MGW, MSCserver, SGSN) as the gateway to connect to independent HLR, GGSN, GMSC, GSGW, and systems (such as billing system) of different operators.
In the MOCN scenario, PLMNs are handled as following: ZTE RAN devices can configure different PLMN codes for multiple operators with shared networks. In the MOCN net working mode, the RNC can differentiate subscribed users of different operators, and route the signaling connections and services of subscribed users of different operators to the core network devices of each operator. The RNC searches a core net work node for the UE randomly . If the core network node is not the operator of the user, the RNC will ret ry other core net work nodes till it finds the core network node that the us er aut horiz es the access to. When the UTRA N is shared, it can also be connected t o one or some operators core networks by the Iu Flex connection method. If this feature is used to deploy the UTRA N network sharing, all UEs with transparent terminals can access in the shared network, and enjoy the services provided by their own operators. Because a UE can only obtain t he common P LMN code through the system message, it is advised to use the NITZ function (3GPP TS22.042) in the core network to identify the logo of its own operator. The net wo rk informs the terminal of the operator logo aft er successful location update.
2.3
RAN Sharing with Dedicated Carrier

When multiple operators work together to establish and s hare the UTRA N network, they use their own frequencies to develop their services, avoi ding that the capacities affect each other when users from different operators compete for air resources. If different operators have occupied their own frequency resources, ZTE RA N devices support independent carriers with multiple operators in the shared UTRA N net work, in other words, sharing the UTRA N devices and resources except carriers. When multiple operators work together to establish and s hare the UTRA N network, they use their own frequencies to develop their services, avoiding that the capacities affect each other because users of different operators compete for air resourc es. If different operators have occupied their own frequency resources, ZTE RA N devices support independent carriers with multiple operators in the shared UTRA N net work, in other words, sharing the UTRA N devices and resources except carriers. Carriers of different operators can be deployed in the same NodeB, sharing devices such as cabinets, power supply, and baseband processing board of the NodeB. RF devices such as PAs, feeders, and antennas can be shared or be deployed separately as required. Carriers of different operators can also be deployed in different NodeBs. They can be connected to the same RNC through the lub int erface, sharing the RNC devic es such as cabinets, power supply, and control plane and user plane processing boards.
Figure 2-3
Independent Carrier Network Sharing
Operator one
Shared RNC
Shared Node B
Operator two
Frequency one
Frequency one
MNC one MNC two
Frequency two
Frequency two
Different carriers of different operators can be identified by broadcastin g different PLMN codes through the system messages. UEs identify networks of different operators by reading the system broadcast of different cells, select their own PLMNs or the authorized PLMNs, and show the logo of the operator. This proc ess is same to the PLMN selection process of non-sharing net work. UEs do not need to know whether cells of different PLMNs use the shared resources. Therefore, all UEs can access the shared network, enjoying services provided by their own operators. The RNC routes the signaling connection and services of a UE to the core network node of the corresponding operator bas ed on the UE-accessed carrier.
2.4
Shared Network Access Control

This feature enables the access control over a UE in DCH status in the shared network and the boundary bet ween the shared net work and non -shared network based on the subscription relationships between this UE and different operators, ensuring that the UE always enjoys the services of the authorized network in mobile status. ZTE RAN devices implements the access control in the shared network area (SNA ). Each SNA is identified by the shared network area code (S NAC). One PLMN has only one S NAC; one SNA can contain one or multiple location areas (LA); one LA can belong to multiple SNAs. The area in where users can obtain the services is configured by the core network. The RNC can learn the S NACs of each LA under the RNC through the CN, and the S NAs that each user is authorized to access. In the cross -lur handover, the S RNC can learn the SNAs of the cells under the DRNC through the lur interface. The RNC reserves the SNAC that each user is allowed to access, and performs the filter in the construction of intra-frequency, inter-frequency, inter-system measured neighbouring cell list. Only the cell with the authorized SNA can be configured as the new neighbouring cell. Then it can be added into the cell list in the measurement control, for ensuring the UE performs the handover only in the authorized cells.
2.5
RAN Sharing with Shared Carrier

The feature provides the possibility for multi -operator to share the same carrier. It s useful to increase spectrum efficiency, when the UMTS frequency license is not enough, or the operator without a license wants to pool a frequency license with whom already have owned one. ZTE RAN equipment supports to broadcast multi-PLMN ID in the same cell whic h is defined as a sector with 5MHz frequency band. UEs with 3GPP R6 capability or above will be able to rec ognize operators on the shared carrier to choose a right PLMN to register and provide service. For UEs with 3GPP R6 capability or above, ZTE RNC routes them to the PLMN selected by themselves, which is indicated in Initial Direct Transfer message when they access to sharing net work. For UEs without 3GPP R6 capability, ZTE RNC suppo rts re-route function which is used to try to setup signaling connection between different core networks until find a right one if the PLMN is not declared . For UEs wit hout 3GPP R6 capability, ZTE RNC can set percentage for different operators to define the possibilities to be first-chosen-CN, which is useful to allocate roaming user to different operators.
When ZTE RNC products work in shared carrier RAN sharing situation, a physical RNC product is working as some logical RNC equipments for the operators which share the physical RNC. Each logical RNC belongs to an operator. The shared RNC can connect to not only shared Node Bs or shared RNCs, but non-shared Node Bs or non-shared RNCs as well. When the shared RNC connects to different operators CN, each operator also can deploy Iu flex for MS C/SGSN pooling purpose. When ZTE RNC works in shared carrier RAN sharing situation, it distinguishes each operators subscribers in shared or non-shared Node Bs controlled by itself or other shared RNC or non-shared RNC. RNC ensures that subscribers of an operator can access in the area its authorized operator and the service continuity among cells in those areas.
2.6
Operator Specific CE Resource

There are two ways to realize CE resources sharing by multi-operators: one is multioperators sharing CE resources in the same baseband pools, the other one is multi operators occupy different baseband pool independent in the same BBU. ZTE s RAN support both the two ways. ZTE support at most 6 cells in one baseband pool, and one bas eband pool includes 1 to 5 baseband boards, and one baseband board only belongs to one bas eband pool. The CE proportion belongs to each operator can be configured by OMC when cells of multi operators configured in the same baseband pool or in different baseband pools. And then the division of CE resources bet ween operators by proportion can be realized.
2.7
Operator Specific FM/PM/CM

The feature supports operator t o independently manage the c ell-level FM/PM/ CM of the network, that is: Independent CM Deferent operators can independently configure the parameters related to the cell which belongs to only one operat or. For example, deferent operators own dedicated the SW (software) function, features differentiation can be embodied in cell-level Configuration. Independent PM For those counters related to cells, performance statistics can be done based on operator. The operator dedicated results of performance statistics can only be accessed by the owner PM manager, for example, differentiate the count ers related to the network s KPI from different operators, independently manage own measurement jobs and measurement objects. Independent FM Fault management function can differentiate the cell-level alarms for different operators. The fault alarm corresponds to only one operator can be only accessed by its owner, so it can by only processed by the owner FM manager.
Technical Description
This section give detailed t echnical description about how RAN Sharing features are realized in ZTE s RAN system.
3.1
Shared Network Mode

Relat ed configuration parameters: rncFunction\ SHARE DNE TMODE: this parameter indicates the shared network mode, there are 2 modes of network sharing: GWCN(Gateway Core Net work) and MOCN(Multi-Operator Core Network). In GWCN mode, both CN and Access Network are shared; in MOCN mode, only the access network is shared.
3.2
RNC Mu lti-PLMN Configuration

For the scenario that a single cell belongs to only one operator, and there should be only one P LMN in the system broadcast message, which means that different cells under the
RNC belong to different operators, ZTE UMTS MultiPLMN Feature Guide has the det ail description. ZTE supports the broadcast and the routing of the RA N Sharing with Shared Carrier. One single cell can belong to max. 4 PLMNs. In the database, physical and logical cell concepts are introduc ed. The following parameters are added: the relationship between physical and logical cell, cell s common PLMN, multi-PLMN list information, configuration for operator specific access restriction etc. The database fills the SIB3 with additional multi-operator specific AC parameters. After the RNC receives the initial direct trans fer message from the UE, multi-PLMN list is added to the message for the CN routing purpose. Relat ed configuration parameters: utranCell\ COMMONP LMNI ND: this paramet er indicates if the PLMN is the common PLMN of the cell. UtranCell\ PLMNNUM:the number of PLMN who share this cell. externalGsmCell\ADJPHYGS MCID: Neighboring physical GSM cell ID, it is the self defned parameter in the RNC. One physical GSM cell is corresponding to max. 4 logical cells(MCC+MNC+LAC+ CI). externalGsmCell\PLMNNUM: This parameter indicates the number of PLMNs who share this GSM cell.
3.3
Information Transfer Process

When the net work sharing feature is introduced, the 3GPP adds a new lu interface for information trans fer (transfer the global information between the CN and RNC). When the CN or RNC is reset, or the related information at CN side is changed, the CN will originate the Information Trans fer message. If the RNC supports the handling of Provided Dat a cell in the Information Transfer message, the RNC returns the Information Trans fer Confirmation message; or else, the RNC returns the Information Trans fer Failure message.
Figure 3-1
Information Transfer Message Process
CN Information Transfer Information Transfer Confirmation
RNC
This is a connectionless message. It is sent by the CN to t he RNC. Then, the RNC handles the Provided Dat a cell in the message, and ret urns the confirmation to the CN. For the Shared Network Information structure in the Provided Data cell, see the following table.
Table 3-1
Shared Net work Information Structure Presence Range IE type and reference Semantics description
IE/Group Name Shared Network Information >PLMNs In Shared Network >>PLMN identity
1 to <maxPLMNsSN> M OCTE T STRING (SIZE (3)) digits 0 to 9, two digits per octet, each digit encoded 0000 to 1001, 1111 used as filler bit 4 to 1 of octet n encoding digit 2n-1 bit 8 to 5 of octet n encoding digit 2n The PLMN identity consists of 3 digits from MCC followed by either a filler plus 2 digits from MNC (in case of 2 digit MNC) or 3 digits from MNC (in case of a 3 digit MNC). 0000 and FFFE not allowed.
>>LA List >>>LAC M
1 to <maxLAs> OCTE T STRING (2) 1 to <maxSNAs>
>>>List Of SNAs Containing LA >>>>SNAC M
Table 2
The value range of SNA C is 0 - 65535. The value is assigned by the operator, and is valid in the same PLMN.
Table 3-2
SNA C Structure Presence M Range IE type and reference INTE GER (0..65535)
IE/Group Name SNAC
When the RNC receives this message, it should save the mapping between the LAC and S NAC in each PLMN. The mapping is used to query the LAC list under the PLMN that can provide UE services based on the SNAC.
3.4
SNA Access Information (lu) of A Single Specified User

To support the relocation request and COMMON ID of the network sharing lu interface, the SNA Access Information cell is added in the message. See the following table.
Table 3-3
SNA Access Information Cell Structure Presence Range IE type and reference
IE/Group Name SNA Acce ss Information >Authori sed PLMNs >>PLMN Identity >>Authori sed SNAs Li st >>>Authori sed SNAs >>>>SNAC
1 to <maxPLMNsSN> M O 1 to <maxSNAs> M Table 2 OCTE T S TRING (S IZE (3))
The table indicates the PLMN list authorized by the user and the authorized S NACs in each PLMN. While the air interface uses the LAC in fact. The RNC should determine whet her the UE is authorized in each cell based on the saved mapping between the LAC and SNA C in section 3.2. This cell is used for S NA access control. Based on the description of sections 3.2 and 3.5, the SRNC can control the UE, and let it obtain the resources only in the allowed SNA. The RNC should save the information for the construction of meas urement control message neighboring cell. See section 3.5.
3.5
SNA Information Transfer in the DRNC Cell

Add a SNA Information cell in the UP LINK S IGNALLING TRA NSFER INDICA TION message on the lur interface. The cell is used for the DRNC to transfer the SNA information of the current cell to the SRNC. Also, add a SNA Information cell in the Neighboring FDD Cell Information and Neighboring GSM Cell Information cells on t he lur int erface. The cell is used for the DRNC to transfer the SNA information of neighboring FDD and GSM cells to the SRNC. See the following SNA Information structure.
Table 3-4
SNA Information Transfer in the DRNC Cell Presence Range IE type and reference Semantics description
IE/Group Name PLMN Identity
OCTE T digits 0 to 9, STRING (3) two digits per octet, each digit encoded 0000 to 1001, 1111 used as filler bit 4 to 1 of octet n encoding digit 2n-1 bit 8 to 5 of octet n encoding digit 2n The PLMN Identity consists of 3 digits from MCC followed by either a filler plus 2 digits from MNC (in case of 2 digit MNC) or 3 digits from MNC (in case of a 3 digit MNC). 0..<maxnoofSNAs> INTE GER (0.. 65535)
List of SNAs > SNAC M
The DRNC queries the database, and specifies the SNACs authorized by the intrafrequency, inter-frequency, and inter-system neighboring cells in the S NA Information cell. The SRNC saves the cell information, so as to maintain the SNA C relationship of corresponding UE crossing lur interfac e neighboring cell.
10
3.6
Mobility Management of The Shared Network

When the RNC judges the mobility, if it has already learn the S NA C of each neighboring cell through s ections 3.2 and 3.4, and has obtained the aut horized SNA C of the UE through section 3. 3, the RNC should re -filter the SNA Cs in the neighboring cell list configured by the background in the construction of int ra-frequency, inter-frequency, and inter-system measured neighboring cell list. That is, the neighboring cell list can be sent to the UE only when the SNAC of the select neighboring cell is same to the neighboring cell of the authorized SNAC of the UE. In this way, the UE can perform the handover only in the authorized cell. The handover may cross cells of different PLMNs. If t he RNC can not obtain the SNA information of single user through the method in section 3.3, it does not perform t he S NAC filtering in the construction of measurement message neighboring cell list; or else, the RNC may perform the SNAC filtering in the construction of measurement message neighboring cell list. Whether to perform the SNAC filtering is determined by whether the RNC obtains the corres ponding SNAC of the neighboring cell through sections 3.2 and 3.4. If the RNC does not obtain the SNAC of a neighboring cell, the neighboring cell can be the target cell of the handover. All the inter-PLMN handovers are performed by the combination method of hard handover and relocation.
3.7
Routing Function in MOCN Mode

In the MOCN mode, the RNC will be connected to CNs of multiple operators. Thus, the RNC faces a problem, that is, how to establish the connection between a UE and a CN. The principles of routing: when the network sharing and lu Flex are used simultaneously, the network sharing has the priority. PLMNs selection is the first, then the NNSF of IuFlex is selected. If the PLMN selection fails, then return failure, no Iu connection is established. The PLMN selection for CS/PS domain must be identical. Otherwise abnormal procedure involved. The principles of P LMN selection: 1. If t he UE carries a Selected PLMN, then this PLMN is selected.2. If there are parallel connections in either CS/PS domain, then the P LMN for both CS/PS must be the same. 3. If a NRI is carried, then the corresponding P LMN of NRI must be selected. 4. If RNC needs to coordinate CS/PS access based on IMS I, then access ratio control bas ed on IMS I is carried out. Dedicated carrier network sharing: A cell can only belong to one PLMN. When a UE is power on, it will select the corresponding PLMN. When the signaling connection is established, the UE originates the initial directly transferred message. The RNC locates the office direction of the CN based on the PLMN that the UE cell belongs to in the initial directly transferred message, and sends the Initial UE Message. If multiple CNs belong to the same PLMN, select a target CN in thes e CNs based on the handling method of lu
11
Flex, and send the Initial UE Message. That is, when the network sharing and lu Flex are used simultaneously, the network sharing has the priority. Shared carrier network sharing: A cell can belong to max. 4 PLMNs. The procedure of the connection of a UE and a CN is described below: 1 After a UE is power on, the UE will choose to camp on one cell. The PLMN list, which the cell belongs to, can be obtained from the cell s system information MIB. After the signaling c onnect is established, the UE initiates the initial direct transfer message, according to the specifications of 3GPP, the Selected PLMN should be filled in the message by the UE NAS. Then the RNC can use the Selected PLMN in the message to accomplish the CN routing. But due to the PLMN identity in the Initial Direct Trans fer message is an optional IE, the UE may not fill the PLMN identity in the message, in this case the RNC accomplishes the routing function with PLMN list information configured in the Database,. PLMN access percentage( AcessPercent[ MAX_NUM_SH ARED_PLMN_PER_CELL ]) is included in the information.
3 3.1 The RNC uses the PLMN list to accomplish the routing function. If there is only one P LMN, then t he RNC sends the INITIA L UE MESSAGE to the corresponding CN, otherwise: 3.2. If there is IDNNS in the data information, the PLMN of the NRI is selected (this PLMN is in the PLMN list), Redirect Attempt Flag is carried and go to 4. Otherwise go to 3.3. 3.3 If there are multiple PLMN, then according to the configuration of PLMNSELE CTME THOD. If it is configured as IMS I bas ed CS/PS coordination, then the first PLMN is selected. If it is configured as Random selection then ration selection of P LMN is carried out. 3.4 RNC sends the INITIAL UE MESSAGE to the corresponding CN, Redirect Attempt Flag is carried. A timer Treroute is set to wait for the responding message from the CN. If the CN sends back DIRECT TRANSFE R message with Redirection completed, then the CN node routing is successful. The RNC sends the DOWNLINK DIRECT TRANSFE R message to the UE. 4 If the CN sends back DIRECT TRANSFE R message with Redirection Indication and the Reject Cause Value is that CS/PS coordination required, RNC obtains the UE Home PLMN through the IMSI send by the CN. If the Home PLMN is in the PLMN list configured by the database, then the RNC sends to the other domain of the CN the INITIA L UE MESSAGE. If the Home PLMN is not in the PLMN list configured by the database, then the RNC chooses the next PLMN in the PLMN list to send the INITIAL UE MESSAGE. In the PLMN list, the RNC doesnt store the Reject Cause Value IE and the NAS-P DU IE send by the CN.
12
If the CN sends back DIRECT TRANSFE R message with Redirection Indic ation 4.1 If the configuration of PLMNSELECTME THOD is as IMS I based CS/PS coordination, and if no IMS I obtained from CN previo usly, and there is IMSI in DIRE CT TRANSFE R, or IMS I is obtained from the UE previously and the RNC hasnt recovered the PLMN list, then RNC restore the PLMN list to the original status, IMSI is stored. Carrying out procedure to ensure CS/PS access the same PLMN. 4.2. If the configuration of PLMNSE LECTME THOD is as Random selection then this PLMN is deleted from the PLMN list, a PLMN is selected randomly from the rest PLMNs of the PLMN list, access ratio is guaranteed by procedure. 4.3. If no PLMN is selected, PLMN selection fails. 5 When the timer Treroute times out,but the CN doesnt start the procedure of Redirection, then t he proc edure stops. Waiting until the UE resends the initial direct transfer message and CN relocation is successful, the timer stops. In the step 4) and 5), if there are multi CNs with the same PLMN, Iu flex is applied to chose a target CN to send the INITIAL UE MESSAGE.
13
Figure 3-2
MOCN reroute procedure
UE
RNC
1. RRC Connection Establishment
MSC/ SGSN A
MSC/ SGSN B
MSC/ SGSN C
HLR
2. Initial Direct Transfer 4. Identity Req 4. Identity Resp (IMSI)
3. Initial UE (Attach request, redirect attempt flag)
Roaming not allowed for HPLMN of IMSI / Roaming allowed but CS/PS coordination required
5. Reroute Command 6. Initial UE (Attach request, redirect attempt flag, IMSI, ) 7. Authentication & Ciphering 8. Update Location / Insert Subscr. Data
Roaming not allowed for HPLMN of IMSI
9. Reroute Command 10. Initial UE (Attach request, redirect attempt flag, IMSI, ) 11. Authentication & Ciphering
12. Update Loc./ Cancel Loc./ Insert Subscr. Data
13. Reroute Complete ( Attach accept, ) 14. Direct Transfer( Attach accept ) 15. Attach Complete
3.8
Paging of Network Sharing

When the network sharing is introduced, the RNC should add the following judgment handlings for pagings without connection between the RRC and UE. If a paging message delivered by the CN includes the Paging Area cell, the RNC still perform the paging based on t he areas indicated by the PLMN and LAC in the Paging Area cell; if the paging message delivered by the CN does not include the Paging Area cell but the Global CN-ID, the RNC can obtain the cell list of the PLMN that is specified by the Global CN-ID on the RNC, and sends paging messages in these cells. When the paging message delivered by the CN does not include the Paging Area and Global CN-ID cells, in the MOCN mode, if the RNC can obtain the OPC of the CN that sends the paging message, search the CN office direction that sends the paging message and the corresponding PLMN based on the OPC, and then obtain the cell list of the PLMN that is specified on the RNC based on the PLMN. Then, send paging messages in these cells. If the RNC can not obtain the OPC that sends the paging
14
message or the GWCN sharing structure in the MOCN mode, perform the paging in all cells under the RNC.
3.9
Reset Process in Network Sharing

In the MOCN mode: 1 CN-originated reset If the reset message contains the Global CN-ID cell, reset the instance that establishes a lu connection with the CN. If the reset message does not contain the Global CN-ID cell, obtain the OP C of the CN that sends the reset message by using the handling method similar to the paging, and search the CN office direction that sends the paging message and the corresponding P LMN based on the OP C, and then reset the instance that establishes a lu connection with the CN.
RNC-originat ed reset Send the reset message to all connected CNs.
In the GWCN mode: 1 CN-originated reset If the reset message contains the Global CN-ID cell, reset the instance that establishes the lu connection with the CN. If the reset message does not contain the Global CN-ID cell, reset all instances under the RNC.
RNC-originat ed reset Construct different Global RNC-ID cells based on multiple PLMNs contained in the RNC, and send multiple corresponding reset messages.
3.10
The support of system broadcast procedure for the network sharing

ZTE supports the shared carrier net work sharing. In the system broadcast information MIB, Multiple PLMN List should be broadcasted. In the S IB3 IE, Domain Specific Access Restriction parameters must be added. Multiple PLMN List structure:
15
Information Element/Group name
Need
Multi
Type and reference
Semantics description The PLMN identity IE 10.3.1.11, broadcasted in the MIB, shall be included in the multiple PLMN list if and only if this IE is TRUE.
MIB PLMN Identity
MP
Boolean
Multiple PLMNs >PLMN identity with Optional MCC
MP
1 to 5 PLMN identity with Optional MCC
the structure of Domain Specific Access Restriction List in the SIB3: Information Element/Group name Need Multi Type and reference Semantics description This IE specifies the Domain Specific Access Restriction Paramet ers for UEs which has chosen the PLMN in the IE PLMN identity of the Master Information Block. If the cell is operating in MBSFN mode as indicated in subclause 8.1.1.6.3 the UE behaviour upon reception of this IE is unspecified. If the cell is operating in MBSFN mode as indicated in subclause 8.1.1.6.3 the UE behaviour upon reception of this IE is unspecified.
Domain Specific Access Restriction Paramet ers For PLMN Of MIB
OP
Domain Specific Access Restriction Parameters 10.3.1.3c
Domain Specific Access Restriction For Shared Network
OP
>CHOICE barring representation >>Domain Specific Access Restriction List
MP
16
>>>Domain Specific Access Restriction Parameters For Operator1
OP
This IE specifies the Domain Specific Access Restriction Paramet ers for UEs which has chosen the first PLMN in the IE multiplePLMNs in the IE Multiple PLMN List of the Master Information Block. This IE specifies the Domain Specific Access Restriction Paramet ers for UEs which has chosen the second PLMN in the IE multipleP LMNs in the IE Multiple PLMN List of the Master Information Block. This IE specifies the Domain Specific Access Restriction Paramet ers for UEs which has chosen the third PLMN in the IE multipleP LMNs in the IE Multiple PLMN List of the Master Information Block. This IE specifies the Domain Specific Access Restriction Paramet ers for UEs which has chosen the fourth PLMN in the IE multipleP LMNs in the IE Multiple PLMN List of the Master Information Block. This IE specifies the Domain Specific Access Restriction Paramet ers for UEs which has chosen the fifth PLMN in the IE multiplePLMNs in the IE Multiple PLMN List of the Master Information Block.
OP
OP
OP
OP
>>Domain Specific Access Restriction Parameters For All
17
>>>Domain Specific Access Restriction Parameters
This IE specifies the common Domain Specific Access Restriction Paramet ers applied to all PLMNs in the IE multiplePLMNs in the IE Multiple PLMN List of the Master Information Block.
Domain Specific Access Restriction Parameters structure: Information Element/Group name Need Multi Type and reference Domain Specific Access Restriction 10.3.1.3b Semantics description This IE contains Domain Specific Access Restriction Parameters for CS domain. This IE contains Domain Specific Access Restriction Parameters for PS domain. Version
CS Domain Specific Access Restriction
MP
REL-6
PS Domain Specific Access Restriction
MP
Domain Specific Access Restriction 10.3.1.3b
REL-6
Domain Specific Access Restriction structure: Information Element/Group name CHOICE restriction status >no restriction >restriction Need Multi Type and reference Semantics description Version
MP (no data)
REL-6 REL-6 REL-6
18
>>Domain Specific Access Class Barred List
MD
<MaxAC>
The first instance of the parameter corresponds to Access Class 0, the second to Access Class 1 and so on up to Access Class 15. UE reads this IE of its access class stored in SIM. The default value is the Access Cont rol Barred List contained in the IE "Cell Access Restriction" of the System Information Block Ty pe 3. Enumerated( barred, not barred)
REL-6
>>>Access Class Barred
MP
REL-6
3.11
CE Sharing Method
During admission control to access a subscriber, PLMN-based CE admission is performed: For the detailed description please refer to section Admission Control when the Cells in Different PLMNs Share the CE resources in ZTE UMTS Admission Control Feat ure Guide.doc To achieve the CE sharing among PLMNs, ZTE RNC has the following 4 parameters to be configured : 1 2 3 4 MINCEPERCE NT: Minimal percent of CE can be used by the PLMN MCC4RA NSHA RING: MCC for RA N Sharing(MCC) MNC4RA NSHA RING: MNC for RA N Sharing(MNC) PLMNNUM: PLMN Number of Sharing the Cell(only for shared carrier scenario)
19
4
4.1
Parameters and Configurations

Parameter List
Table 4-1 Id 1 2 3 4 Network Sharing Parameter List Abbreviate SHARE DNE TMODE PLMNNUM COMMONP LMNIND PLMNNUM Parameter name Shared Network Mode PLMN Number of Sharing the Cell Common PLMN Indicator PLMN Number of Sharing the Cell PLMN Number of Sharing the GSM Cell Physical Adjacent GSM Cell Identity Access Percent MCC for RA N Sharing Minimal percent of CE can be used by the PLMN MNC for RA N Sharing Number of PLMN for RAN Sharing PLMN Select Method Non-local rnc neighboring cell level parameter Neighboring GSM cell level parameter Note s RNC Level parameter Local RNC cell level parameter
5 6 7 8 9 10 11 12
PLMNNUM ADJP HYGSMCID ACCESSPERCENT MCC4RA NSHA RING MINCEPERCE NT MNC4RA NSHA RING PLMNNUM PLMNSELE CTME THOD
4.1.1
SHAREDNETMODE
OMC Path
Path: View->Configuration Management->RNC Managed Element ->RNC Radio Resource Management->Basic Information ->Shared Network Mode Parameter Configuration
This parameter indicates the shared network mode. There are two modes of shared network: GWCN (Gateway Core Network) and MOCN Multi -Operator Core Network. Both radio access network and core network are shared in GWCN mode. Only radio access network is shared by in MOCN mode.
20
4.1.2
PLMNNUM (UTRAN Cell)

OMC Path
Path: View->Configuration Management-> RNC Managed Element ->RNC Radio Resource Management-> UTRAN Cell -> UTRAN Cell XX -> UTRA N Cell Global Information->PLMN Number of Sharing the Cell Parameter Configuration cell must be in the range of
The PLMN number of sharing the 1~MA X_NUM_S HARE D_P LMN_PER_CE LL
4.1.3
COMMONPLMNIND
OMC Path
Path: View->Configuration Management-> RNC Managed Element ->RNC Radio Resource Management-> UTRAN Cell -> UTRAN Cell XX -> UTRA N Cell Global Information-> Common PLMN Indicator Parameter Configuration
The parameter indicates whether the PLMN is the common P LMN of the cell.
4.1.4
PLMNNUM (ExternUtranCell)
OMC Path
Path: View -> Configuration Management -> RNC Managed Element -> RNC Radio Resource Management ->External UTRAN Cell -> External UTRAN Cell XX -> Global Information-> PLMN Number of Sharing the Cell Parameter Configuration must be in the range of 1 ~
The PLMN number of sharing the cell MA X_NUM_S HARE D_PLMN_PER_CELL.
4.1.5
PLMNNUM (ExternGSMCell)
OMC Path
Path: View -> Configuration Management -> RNC Managed Element -> RNC Radio Resource Management->External GSM Cell -> External GSM Cell XX -> GSM Cell-> PLMN Number of Sharing the GSM Cell Parameter Configuration
21
The PLMN number of sharing the GSM 1~MA X_NUM_S HARE D_P LMN_PER_CE LL
cell
must
be
in
the
range
of
4.1.6
ADJPHYGSMCID
OMC Path
Path: View -> Configuration Management -> RNC Managed Element -> RNC Radio Resource Management->External GSM Cell -> External GSM Cell XX -> GSM Cell-> Physical Adjacent GSM Cell Identity Parameter Configuration
The parameter indicates physical adjacent GSM cell identity; it identifies a neighboring GSM cell uniquely. One physical cell corresponds to four logic cell (MCC+MNC+LAC+ CI) at most.
4.1.7
ACCESSPERCENT
OMC Path
Path: View->Configuration Management-> RNC NE-> RNC Radio Res ource Management-> UTRAN Cell -> UtranCell xx-> UTRA N Cell Global Information -> Access Percent of the PLMN for Non-Supporting UEs(%) Parameter Configuration
The paramet er indicates the access percent of the PLMN for non-s upporting UEs in a MOCN shared network configuration
4.1.8
MCC4RANSHARING
OMC Path
Path: View->Configuration Management-> RNC NE-> RNC Radio Res ource Management-> NodeB Configuration-> NodeB Configuration XXX -> MCC for RAN Sharing Parameter Configuration
The parameter indicates MCC for RAN Sharing while carrier sharing
4.1.9
MINCEPERCENT
OMC Path
22
Path:View->Configuration Management->RNC NE-> RNC Radio Resource Management>NodeB Configuration-> NodeB Configuration XXX -> Minimal percent of CE can be used by the PLMN Parameter Configuration
The parameter indicates Minimal percent of CE can be used by the PLMN for RAN Sharing while carrier sharing, which can not be occupied by other operat or(P LMN)
4.1.10
MNC4RANSHARING
OMC Path
Path:View->Configuration Management->RNC NE-> RNC Radio Resource Management>NodeB Configuration-> NodeB Configuration XXX -> MNC for RA N Sharing Parameter Configuration
The parameter indicates MNC for RAN Sharing while carrier sharing
4.1.11
PLMNNUM
OMC Path
Path:View->Configuration Management->RNC NE-> RNC Radio Resource Management>NodeB Configuration-> NodeB Configuration XXX -> Number of PLMN for RAN Sharing Parameter Configuration
The parameter indicates Number of PLMN for RA N Sharing while carrier sharing
4.1.12
PLMNSELECTMETHOD
OMC Path
Path:View->Configuration Management->RNC NE-> RNC Radio Resource Management> Advanced Parameter Manager -> RNC Radio Resource Management -> Plmn Select Method for MOCN Network Sharing Parameter Configuration
This paramet er indicates the mothod of PLMN selection , when MO CN is us ed for network sharing
23
Counters and Alarms

The feat ure S hared Carrier Network Sharing is introduced in RNC of ZTE UMTS product, the performance count ers measurement object is be updated according this new feat ure. In the Shared Carrier Network Sharing network of ZTE RNC, 4 different PLMNs can be broadcasted in one cell, one c ell can be severed for Maximal 4 different operators. To distinguish the servic e level performanc e of different PLMNs of one cell, the new measurement object, logical cell, is introduced. The counters of logical cell have two identifiers, Cell ID and PLMN ID, in serving RNC(S RNC). For other measurement doesn't need be count ed for each PLMN, the measurement object, physical cell, is used in the serving RNC(S RNC). In RNC of ZTE UMTS product, only traffic throughput related counters are operator differentiated, they are measured based on logical cell, the rest counters are physical cell based. For logical cell object, the counters are designed to statistic the real number of subscribers, the traffic real connection time and the UL/ DL traffic volume for each interface, this performance and utilization can reflect the occupation of the cell resource by different operators. The other counters such as count ers for mobility, accessibility, retain ability, and etc, are measured in physical cell object. For the neighbor cell type counters such as UtranRelation, GsmRelation are counted by physical cells pair object. For the counters detail definition, pleas e refer to the counter doc ument.
Abbreviation
B BPA C CN CS G GWCN I IDNNS IMEI IMSI Intra Domain NAS Node Selector International Mobile Equipment Identity International Mobile Subscriber Identity Gateway Core Network Core Network Circuit switched Base Pool Area
24
L LA M MBMS MCC MNC MOCN MS MSC N NNSF NRI NS-UE P PLMN PPA PS R RA RAN RNC S SGSN SNA SNAC Serving GP RS Support Node Shared Network Area Shared Network Area Code Routing Area Radio Access Network Radio Network Controller Public Land Mobile Net work Preferred Pool Area Packet switched NAS Node Selection Function Network Resource Identifier Non-supporting UE Multimedia B roadcast Multicast Service Mobile Country Code Mobile Network Code Multi-Operator Core Network Mobile Station Mobile S witching Centre Location Area
25
S-UE T TMS I W WCDMA
Supporting UE
Temporary Mobile Station Identity
Wideband CDMA, Code division multiple access
26

File 083

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

File 083

Uploaded by

Copyright:

Available Formats

RAN Sharing

RAN Sharing Feature Guide

RAN Sharing Feature Guide

ZTE Confidential Proprietary

2011 ZTE Corporation. All rights reserved.

RAN Sharing Feature Guide

ZTE Confidential Proprietary

2011 ZTE Corporation. All rights reserved.

RAN Sharing Feature Guide

ZTE Confidential Proprietary

2011 ZTE Corporation. All rights reserved.

RAN Sharing Feature Guide

Note: * -: Not involved

Dependency: None Exclusion: None

ZTE Confidential Proprietary

2011 ZTE Corporation. All rights reserved.

RAN Sharing Feature Guide

Basic Network Sharing Support

The networking diagram of MOCN network sharing method

Radio Access Network Operator X

Gateway core network sharing

ZTE Confidential Proprietary

2011 ZTE Corporation. All rights reserved.

RAN Sharing Feature Guide

RAN Sharing with Dedicated Carrier

ZTE Confidential Proprietary

2011 ZTE Corporation. All rights reserved.

RAN Sharing Feature Guide

Independent Carrier Network Sharing

MNC one MNC two

Shared Network Access Control

ZTE Confidential Proprietary

2011 ZTE Corporation. All rights reserved.

RAN Sharing Feature Guide

RAN Sharing with Shared Carrier

Operator Specific CE Resource

ZTE Confidential Proprietary

2011 ZTE Corporation. All rights reserved.

RAN Sharing Feature Guide

Operator Specific FM/PM/CM

Shared Network Mode

RNC Mu lti-PLMN Configuration

ZTE Confidential Proprietary

2011 ZTE Corporation. All rights reserved.

RAN Sharing Feature Guide

Information Transfer Process

Information Transfer Message Process

CN Information Transfer Information Transfer Confirmation

ZTE Confidential Proprietary

2011 ZTE Corporation. All rights reserved.

RAN Sharing Feature Guide

>>LA List >>>LAC M

1 to <maxLAs> OCTE T STRING (2) 1 to <maxSNAs>

>>>List Of SNAs Containing LA >>>>SNAC M

ZTE Confidential Proprietary

2011 ZTE Corporation. All rights reserved.

RAN Sharing Feature Guide

IE/Group Name SNAC

SNA Access Information (lu) of A Single Specified User

1 to <maxPLMNsSN> M O 1 to <maxSNAs> M Table 2 OCTE T S TRING (S IZE (3))

ZTE Confidential Proprietary

2011 ZTE Corporation. All rights reserved.

RAN Sharing Feature Guide

SNA Information Transfer in the DRNC Cell