hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.3.48 Broadcast Message Content Validity Indicator
|
This parameter is applicable for UMTS only.
The Broadcast Message Content Validity Indicator IE if included in the WRITE-REPLACE message indicates that the Broadcast Message Content IE does not contain any valid information and is to be ignored. This element is an enumerated type; see 3GPP TS 25.419 [29].
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.3.49 Failed-Cell-List
|
This parameter is applicable for E-UTRAN and NG-RAN only.
The Failed-Cell-List IE lists the cells where ongoing PWS operation has failed. See 3GPP TS 36.413 [36] for E‑UTRAN and 3GPP TS 38.413 [40] for NG-RAN.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.3.50 Cause-NG-RAN
|
This parameter is applicable for NG-RAN only.
The purpose of the Cause-NG-RAN IE is to indicate the reason for a particular event for the N50 protocol. This element is an integer; see 3GPP TS 29.518 [41].
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.3.51 Warning Message Content NG-RAN
|
This parameter is applicable for NG-RAN only.
The Warning Message Content NG-RAN IE contains user information, e.g., the message with warning contents, and will be broadcast over the radio interface. This element is a string of maximum 9600 octets; see 3GPP TS 38.413 [40].
NOTE: If the ePWS language-independent content functionality (clause 8.3) is supported by CBE, a user information can include a language-independent content mapped to an event or a disaster that is compatible with texts used to describe user information contained in the content of a CBS-Message-Information-Page transparently passed from CBC to UEs.
The content of Warning Message Content NG-RAN IE consists of the following parameters:
PARAMETER
REFERENCE
PRESENCE
Number-of-Pages
9.3.4
M
CBS-Message-Information-Page 1
9.3.19
M
CBS-Message-Information-Length 1
9.3.20
M
CBS-Message-Information-Page 2
9.3.19
O
CBS-Message-Information-Length 2
9.3.20
O
…
:
CBS-Message-Information-Page n
9.3.19
O
CBS-Message-Information-Length n
9.3.20
O
NOTE: n equal to or less than 15
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.3.52 Repetition-Period NG-RAN
|
This parameter is applicable for NG-RAN only.
The Repetition Period NG-RAN IE indicates the periodicity in seconds of the warning message to be broadcast.This element is an integer with a value between 0 and 217-1; see 3GPP TS 38.413 [40].
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.3.53 Global RAN Node ID
|
This parameter is applicable for NG-RAN only.
The Global RAN Node ID IE is used to globally identify a NG-RAN node (i.e. a Global gNB ID or a Global ng-eNB ID). See 3GPP TS 38.413 [40].
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.3.54 List of NG-RAN TAIs
|
This parameter is applicable for NG-RAN only.
The List of NG-RAN TAIs IE is used to uniquely identify NG-RAN Tracking Areas; see 3GPP TS 38.413 [40].
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.3.55 Warning Area List NG-RAN
|
This parameter is applicable for NG-RAN only.
The Warning Area List NG-RAN IE indicates the areas where the warning message needs to be broadcast. The Warning Area List NG-RAN consists of a Cell ID list (see clause 9.3.5) or a NG-RAN TAI list (see clause 9.3.54) or an Emergency Area ID list; see clause 9.3.47.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.3.56 RAT Selector NG-RAN
|
This parameter is applicable for NG-RAN only.
The RAT Selector NG-RAN IE shall be present to indicate to the AMF if the request shall be distributed to attached ng‑eNBs or to gNBs. See 3GPP TS 29.518 [41].
NOTE: The CBC and the AMF do not support handling of concurrent responses from ng-eNBs and gNBs for the same request.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.3.57 Unknown NG-RAN Tracking Area List
|
This parameter is applicable for NG-RAN only.
The Unknown NG-RAN Tracking Area List IE identifies the Tracking Areas that are unknown to the AMF and where the request cannot be delivered. This IE is of type List of NG-RAN TAIs (see clause 9.3.54).
This IE shall not be included if the Cause IE indicates Tracking area not valid. The Cause IE indicating Tracking area not valid is used when all Tracking Areas in the request are invalid.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.3.58 Broadcast Scheduled Area List NG-RAN
|
This parameter is applicable for NG-RAN only.
The Broadcast Scheduled Area List NG-RAN IE indicates the areas where initiation of a broadcast was performed successfully. A Broadcast Scheduled Area List is received by the AMF from an NG-RAN Node as Broadcast Completed Area List. See 3GPP TS 38.413 [40].
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.3.59 Broadcast Cancelled Area List NG-RAN
|
This parameter is applicable for NG-RAN only.
The Broadcast Cancelled Area List NG-RAN IE indicates the areas where broadcast was stopped successfully; see 3GPP TS 38.413 [40].
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.3.60 Broadcast Empty Area List NG-RAN
|
This parameter is applicable for NG-RAN only.
The Broadcast Empty Area List NG-RAN IE contains a list of the Global RAN Node IDs (see clause 9.3.53) of NG-RAN Nodes that have responded to the the AMF with a
- WRITE-REPLACE WARNING RESPONSE message in which the Broadcast Completed Area List IE was not included (see 3GPP TS 38.413 [40]), or
- PWS CANCEL RESPONSE message in which the Broadcast Cancelled Area List IE was not included (see 3GPP TS 38.413 [40]).
The AMF may aggregate NG-RAN Node IDs into the Broadcast Empty Area List NG-RAN.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.3.61 Restarted Cell List NG-RAN
|
This parameter is applicable for NG-RAN only.
The Restarted Cell List NG-RAN IE lists the cells which have restarted and where warning messages have been stopped if any were ongoing. See 3GPP TS 38.413 [40].
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.3.62 Failed Cell List NG-RAN
|
This parameter is applicable for NG-RAN only.
The Failed Cell List NG-RAN IE lists the cells where ongoing PWS operation has failed. See 3GPP TS 38.413 [40].
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.3.63 Warning Area Coordinates
|
This parameter is applicable for E-UTRAN and NG-RAN only.
The Warning Area Coordinates IE indicates alert area coordinates of a warning message. The eNB and NG-RAN node pass this information to the UE. The UE uses this information to conditionally display (see clause 9.1.3.4.2 and clause 9.1.3.5.2) the warning message contents.
The Warning Area Coordinates IE is encoded as specified in ATIS-0700041 [47].
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.3.64 Test Flag
|
The Test Flag IE may be included to indicate to the NG-RAN node that the request is to be processed and responded to normally, but shall not result in broadcast over the air and shall not allocate any resources (i.e. the request cannot be cancelled).
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4 Message Format on the Radio Network – MS/UE Interface
| |
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.1 GSM
|
The CBS messages which are transmitted by the BTS for the MS include the CBS Message (information for the user) and Schedule Message (schedule of CBS messages).
The use and the formatting of the CBS messages, which contain information for the MS user, is described in this clause.
The Schedule Message is broadcast to support CBS DRX mode for Mobile Stations. The Schedule Message is helpful in minimizing battery usage for Cell Broadcast in the Mobile Station, because it allows the MS to ignore transmissions of CBS messages the customer is not interested in. The use and formatting of the Schedule Message is described in 3GPP TS 44.012 [7].
The handling of the GSM only applicable ETWS Primary Notification messages differ from what is stated in this clause and is instead described in clause 9.4.1.3.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.1.1 General Description
|
Each page of a CBS Message sent to the MS by the BTS is a fixed block of 88 octets as coded in 3GPP TS 44.012 [7]. This is sent on the channel allocated as CBCH by 3GPP TS 45.002 [8]. The 88 octets of the CBS Message are formatted as described in clause 9.3.2.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.1.2 Message Parameter
|
Octet Number(s)
Field
1‑2
Serial Number
3‑4
Message Identifier
5
Data Coding Scheme
6
Page Parameter
7‑88
Content of Message
The octets in the above table are transmitted in order, starting with octet 1. The bits within these octets are numbered 0 to 7; bit 0 is the low order bit and is transmitted first.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.1.2.1 Serial Number
|
This parameter is a 16-bit integer which identifies a particular CBS message (which may be one to fifteen pages in length) from the source and type indicated by the Message Identifier and is altered every time the CBS message with a given Message Identifier is changed.
The two octets of the Serial Number field are divided into a 2-bit Geographical Scope (GS) indicator, a 10‑bit Message Code and a 4-bit Update Number as shown below:
Octet 1
Octet 2
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
GS
Message Code
Update Number
The most significant bit of the update number is octet 2 bit 3. The most significant bit of the Message Code is octet 1 bit 5 and the least significant bit of the Message Code is octet 2 bit 4. The most significant bit of the Geographical Scope is octet 1 bit 7.
Message Code:
The Message Code differentiates between CBS messages from the same source and type (i.e. with the same Message Identifier). Message Codes are for allocation by PLMN or SNPN operators.
The Message Code identifies different message themes. For example, let the value for the Message Identifier be "Automotive Association" (= source), "Traffic Reports" (= type). Then "Crash on A1 J5" could be one value for the message code, "Cow on A32 J4" could be another, and "Slow vehicle on M3 J3" yet another.
In the case of transmitting CBS messages for ETWS, i.e. the Message Identifier has a value for ETWS (see clause 9.4.1.2.2), a part of Message Code can be used to command mobile terminals to activate emergency user alert and message popup in order to alert the users. Message Code format for this purpose is as follows:
5
4
3
2
1
0
7
6
5
4
Emergency User Alert
Popup
NOTE 1: The exact behaviour of the UE is specified in 3GPP TS 22.268 [28]. Whether the UE setting is overridden is subject to regulatory requirements.
NOTE 2: Emergency user alert includes alerting tone and other user alerting means such as vibration, according to the UE's capability. The types of alert (e.g. the kind of tone, vibration, etc) are implementation dependent and may be subject to regulatory requirements.
NOTE 3: The popup indication shall take precedence over the setting of the DCS Message class (see 3GPP TS 23.038 [3]), and the Geographical Scope with regard to Display Mode 'immediate'.
The codings of the Emergency User Alert and Popup fields are shown below:
Field
Code
Instruction to Terminal
Emergency User Alert
0
No instruction as to emergency user alert.
1
Activate emergency user alert.
Popup
0
No instruction as to popup.
1
Activate popup on the display.
Geographical Scope:
The Geographical Scope (GS) indicates the geographical area over which the Message Code is unique, and the display mode. The CBS message is not necessarily broadcast by all cells within the geographical area. When two CBS messages are received with identical Serial Numbers/Message Identifiers in two different cells, the Geographical Scope may be used to determine if the CBS messages are indeed identical.
In particular, the Geographical Scope tells the mobile if the CBS message is:
- only cell wide (which means that if a message is displayed it is desirable that the message is removed from the screen when the UE selects the next cell and if any CBS message is received in the next cell it is to be regarded as "new"), or
- PLMN/SNPN wide (which means that the Message Code and/or Update Number must change in the next cell, of the PLMN or SNPN, for the CBS message to be "new". The CBS message is only relevant to the PLMN or SNPN in which it is broadcast, so any change of PLMN (including a change to another PLMN which is an ePLMN) or SNPN means the CBS message is "new"), or
- Location Area wide (in GSM) (which means that a CBS message with the same Message Code and Update Number may or may not be "new" in the next cell according to whether the next cell is in the same Location Area as the current cell), or
- Service Area wide (in UMTS) (which means that a CBS message with the same Message Code and Update Number may or may not be "new" in the next cell according to whether the next cell is in the same Service Area as the current cell), or
NOTE 4: According to 3GPP TS 23.003 [2] a Service Area consists of one cell only.
- Tracking Area wide (in E-UTRAN) (which means that a warning message with the same Message Code and Update Number may but need not be "new" in the next cell according to whether the next cell is in the same Tracking Area as the current cell), or
- Tracking Area wide (in NG-RAN) (which means that a warning message with the same Message Code and Update Number may but need not be "new" in the next cell according to whether the next cell is in the same Tracking Area as the current cell).
The display mode indicates whether the CBS message is supposed to be on the display all the time ("immediate") or only when the user wants to see it ("normal"). In either case, the CBS message will be displayed only if its Message Identifier is contained within the "search list" of the mobile (see clause 9.3.2). These display modes are indicative of intended use, without indicating a mandatory requirement or constraining the detailed implementation by mobile manufacturers. The user may be able to select activation of these different modes.
The coding of the Geographical Scope field is shown below:
GS Code
Display Mode
Geographical Scope
00
Immediate
Cell wide
01
Normal
PLMN/SNPN wide
10
Normal
Location Area wide in GSM,
Service Area wide in UMTS, Tracking Area wide in E-UTRAN, Tracking Area wide in NG-RAN
11
Normal
Cell wide
Immediate = default direct display.
Normal = default display under user interaction.
Code 00 is intended for use by the network operators for base station IDs but this code can also be used for other applications. Use of GS=00 takes precedence over the setting of the DCS Message class (see 3GPP TS 23.038 [3])
Update Number:
The Update Number indicates a change of the message content of the same CBS message, i.e. the CBS message with the same Message Identifier, Geographical Scope, and Message Code.
In other words, the Update Number will differentiate between older and newer versions of the same CBS message, within the indicated geographical area. A new CBS message may have Update Number 0000; however this number will increment by 1 for each update.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.1.2.2 Message Identifier
|
This parameter identifies the source and type of the CBS message. For example, "Automotive Association" (= source), "Traffic Reports" (= type) could correspond to one value. A number of CBS messages may originate from the same source and/or be of the same type. These will be distinguished by the Serial Number. The Message Identifier is coded in binary.
The ME shall attempt to receive the CBS messages whose Message Identifiers are in the "search list". This "search list" shall contain the Message Identifiers stored in the EFCBMI, EFCBMID and EFCBMIR files on the SIM (see 3GPP TS 11.11) and any Message Identifiers stored in the ME in a "list of CBS messages to be received". If the ME has restricted capabilities with respect to the number of Message Identifiers it can search for, the Message Identifiers stored in the SIM shall take priority over any stored in the ME.
The use/application of the Message Identifier is shown in the following table, with octet 3 of the Message Identifier in hex shown first, followed by octet 4. Thus "1234" (hex) represents octet 3 = 0001 0010 and octet 4 = 0011 0100.
In a PLMN, the MS shall discard a CBS message in Message Identifier value range "A000hex-AFFFhex" unless it is received from:
- HPLMN;
- EHPLMN; or
- PLMN that is equivalent to either HPLMN or EHPLMN.
In an SNPN, the MS shall discard a CBS message in Message Identifier value range "A000hex-AFFFhex" unless it is received from the subscribed SNPN or an SNPN equivalent to the subscribed SNPN.
Networks shall only use Message Identifiers from the range 4352 – 6399 (1100 hex – 18FF hex) for Public Warning System as defined in 3GPP TS 22.268 [28]. If a message Identifier from this range is in the "search list", the ME shall attempt to receive this CBS message. Processing of different language codes is specified in clause 9.4.1.2.3 and clause 9.4.2.2.4.
Decimal
Hex
Meaning
0 – 999
0000 – 03E7
To be allocated by GSMA(see GSMA AD.26 [25]). If a Message Identifier from this range is in the "search list", the ME shall attempt to receive such CBS message.
This version of this document does not prohibit networks from using Message Identifiers in the range 0000 - 03E7 (hex) for Cell Broadcast Data Download to the SIM.
1000
03E8
LCS CBS Message Identifier for E-OTD Assistance Data message.
1001
03E9
LCS CBS Message Identifier for DGPS Correction Data message.
1002
03EA
LCS CBS Message Identifier for GPS Ephemeris and Clock Correction Data message.
1003
03EB
LCS CBS Message Identifier for GPS Almanac and Other Data message.
1004 - 4095
03EC – 0FFF
Intended for standardization in future versions of this document. These values shall not be transmitted by networks that are compliant to this version of this document. If a Message Identifier from this range is in the "search list", the ME shall attempt to receive this CBS message.
4096 - 4223
1000 – 107F
Networks shall only use Message Identifiers from this range for Cell Broadcast Data Download in "clear" (i.e. unsecured) to the SIM (see 3GPP TS 11.14). If a message Identifier from this range is in the "search list", the ME shall attempt to receive this CBS message.
Not settable by MMI
4224 - 4351
1080 – 10FF
Networks shall only use Message Identifiers from this range for Cell Broadcast Data Download secured according to 3GPP TS 23.048 [15] to the SIM (see 3GPP TS 11.14). If a message Identifier from this range is in the "search list", the ME shall attempt to receive this CBS message.
Not settable by MMI
4352
1100
ETWS CBS Message Identifier for earthquake warning message.
4353
1101
ETWS CBS Message Identifier for tsunami warning message.
4354
1102
ETWS CBS Message Identifier for earthquake and tsunami combined warning message.
4355
1103
ETWS CBS Message Identifier for test message.
The UE silently discards this message. A UE specially designed for testing purposes may display its contents.
4356
1104
ETWS CBS Message Identifier for messages related to other emergency types.
4357 - 4359
1105 - 1107
ETWS CBS Message Identifier for future extension.
4360 - 4369
1108 - 1111
Intended for standardization in future versions of this document. These values shall not be transmitted by networks that are compliant to this version this document. If a Message Identifier from this range is in the "search list", the ME shall attempt to receive this CBS message.
4370
1112
CMAS CBS Message Identifier for CMAS Presidential Level Alerts.
EU-Alert Level 1 Message Identifier for the local language as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 0 Message Identifier for Extreme Emergency alerts in Korean language.
Not settable by MMI.
4371
1113
CMAS CBS Message Identifier for CMAS Extreme Alerts with Severity of Extreme, Urgency of Immediate, and Certainty of Observed.
EU-Alert Level 2 Message Identifier for the local language as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier for Emergency alerts in Korean language.
Settable by MMI
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
4372
1114
CMAS CBS Message Identifier for CMAS Extreme Alerts with Severity of Extreme, Urgency of Immediate, and Certainty of Likely.
EU-Alert Level 2 Message Identifier for the local language as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier for Public Safety alerts in Korean language.
Settable by MMI
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
4373
1115
CMAS CBS Message Identifier for CMAS Severe Alerts with Severity of Extreme, Urgency of Expected, and Certainty of Observed.
EU-Alert Level 3 Message Identifier for the local language as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier.
Settable by MMI
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
4374
1116
CMAS CBS Message Identifier for CMAS Severe Alerts with Severity of Extreme, Urgency of Expected, and Certainty of Likely.
EU-Alert Level 3 Message Identifier for the local language as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier.
Settable by MMI
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
4375
1117
CMAS CBS Message Identifier for CMAS Severe Alerts with Severity of Severe, Urgency of Immediate, and Certainty of Observed.
EU-Alert Level 3 Message Identifier for the local language as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier.
Settable by MMI
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
4376
1118
CMAS CBS Message Identifier for CMAS Severe Alerts with Severity of Severe, Urgency of Immediate, and Certainty of Likely.
EU-Alert Level 3 Message Identifier for the local language as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier.
Settable by MMI
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
4377
1119
CMAS CBS Message Identifier for CMAS Severe Alerts with Severity of Severe, Urgency of Expected, and Certainty of Observed.
EU-Alert Level 3 Message Identifier for the local language as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier.
Settable by MMI
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
4378
111A
CMAS CBS Message Identifier for CMAS Severe Alerts with Severity of Severe, Urgency of Expected, and Certainty of Likely.
EU-Alert Level 3 Message Identifier for the local language as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier.
Settable by MMI
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
4379
111B
CMAS CBS Message Identifier for Child Abduction Emergency (or Amber Alert).
EU-Amber Message Identifier for the local language as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier for Amber alerts in Korean language.
Settable by MMI
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
4380
111C
CMAS CBS Message Identifier for the Required Monthly Test.
According to CMAS requirements (see 3GPP TS 22.268 [28]), if this Message Identifier is in the "search list", the ME shall attempt to receive this CBS message.
4381
111D
CMAS CBS Message Identifier for CMAS Exercise.
According to CMAS requirements (see 3GPP TS 22.268 [28]), if this Message Identifier is in the "search list", the ME shall attempt to receive this CBS message.
4382
111E
CMAS CBS Message Identifier for operator defined use.
According to CMAS requirements (see 3GPP TS 22.268 [28]), if this Message Identifier is in the "search list", the ME shall attempt to receive this CBS message.
4383
111F
CMAS CBS Message Identifier for CMAS Presidential Level Alerts for additional languages.
EU-Alert Level 1 Message Identifier for additional languages as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 0 Message Identifier for Extreme Emergency alerts in additional languages.
Not settable by MMI.
The ME shall receive the messages dependent on the language indicated in the CBS message and the language indicator settings in the ME.
4384
1120
CMAS CBS Message Identifier for CMAS Extreme Alerts with Severity of Extreme, Urgency of Immediate, and Certainty of Observed for additional languages.
EU-Alert Level 2 Message Identifier for additional languages as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier for Emergency alerts in additional languages.
Settable by MMI.
The ME shall receive the messages dependent on the language indicated in the CBS message and the language indicator settings in the ME.
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
4385
1121
CMAS CBS Message Identifier for CMAS Extreme Alerts with Severity of Extreme, Urgency of Immediate, and Certainty of Likely for additional languages.
EU-Alert Level 2 Message Identifier for additional languages as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier for Public Safety alerts in additional languages.
Settable by MMI.
The ME shall receive the messages dependent on the language indicated in the CBS message and the language indicator settings in the ME.
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
4386
1122
CMAS CBS Message Identifier for CMAS Severe Alerts with Severity of Extreme, Urgency of Expected, and Certainty of Observed for additional languages.
EU-Alert Level 3 Message Identifier for additional languages as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier for additional languages.
Settable by MMI.
The ME shall receive the messages dependent on the language indicated in the CBS message and the language indicator settings in the ME.
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
4387
1123
CMAS CBS Message Identifier for CMAS Severe Alerts with Severity of Extreme, Urgency of Expected, and Certainty of Likely for additional languages.
EU-Alert Level 3 Message Identifier for additional languages as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier for additional languages.
Settable by MMI.
The ME shall receive the messages dependent on the language indicated in the CBS message and the language indicator settings in the ME.
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
4388
1124
CMAS CBS Message for CMAS Severe Alerts with Severity of Severe, Urgency of Immediate, and Certainty of Observed for additional languages.
EU-Alert Level 3 Message Identifier for additional languages as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier for additional languages.
Settable by MMI.
The ME shall receive the messages dependent on the language indicated in the CBS message and the language indicator settings in the ME.
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
4389
1125
CMAS CBS Message for CMAS Severe Alerts with Severity of Severe, Urgency of Immediate, and Certainty of Likely for additional languages.
EU-Alert Level 3 Message Identifier for additional languages as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier for additional languages.
Settable by MMI.
The ME shall receive the messages dependent on the language indicated in the CBS message and the language indicator settings in the ME.
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
4390
1126
CMAS CBS Message Identifier for CMAS Severe Alerts with Severity of Severe, Urgency of Expected, and Certainty of Observed for additional languages.
EU-Alert Level 3 Message Identifier for additional languages as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier for additional languages.
Settable by MMI.
The ME shall receive the messages dependent on the language indicated in the CBS message and the language indicator settings in the ME.
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
4391
1127
CMAS CBS Message Identifier for CMAS Severe Alerts with Severity of Severe, Urgency of Expected, and Certainty of Likely for additional languages.
EU-Alert Level 3 Message Identifier for additional languages as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier for additional languages.
Settable by MMI.
The ME shall receive the messages dependent on the language indicated in the CBS message and the language indicator settings in the ME.
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
4392
1128
CMAS CBS Message Identifier for Child Abduction Emergency (or Amber Alert) for additional languages.
EU-Amber Message Identifier for additional languages as defined in ETSI TS 102 900 [32].
Korean Public Alert System (KPAS) Class 1 Message Identifier for Amber alerts in additional languages.
Settable by MMI.
The ME shall receive the messages dependent on the language indicated in the CBS message and the language indicator settings in the ME.
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
4393
1129
CMAS CBS Message Identifier for the Required Monthly Test for additional languages.
According to CMAS requirements (see 3GPP TS 22.268 [28]), if this Message Identifier is in the "search list", the ME shall attempt to receive this CBS message dependent on the language indicated in the CBS message and the language indicator settings in the ME.
4394
112A
CMAS CBS Message Identifier for CMAS Exercise for additional languages.
According to CMAS requirements (see 3GPP TS 22.268 [28]), if this Message Identifier is in the "search list", the ME shall attempt to receive this CBS message dependent on the language indicated in the CBS message and the language indicator settings in the ME.
4395
112B
CMAS CBS Message Identifier for operator defined use for additional languages.
According to CMAS requirements (see 3GPP TS 22.268 [28]), if this Message Identifier is in the "search list", the ME shall attempt to receive this CBS message dependent on the language indicated in the CBS message and the language indicator settings in the ME.
4396
112C
CMAS CBS Message Identifier for CMAS Public Safety Alerts.
EU-Alert Level 4 Message Identifier for the local language as defined in ETSI TS 102 900 [32].
Settable by MMI.
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
4397
112D
CMAS CBS Message Identifier for CMAS Public Safety Alerts for additional languages.
EU-Alert Level 4 Message Identifier for additional languages as defined in ETSI TS 102 900 [32].
Settable by MMI.
The ME shall receive the messages dependent on the language indicated in the CBS message and the language indicator settings in the ME.
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
4398
112E
CMAS CBS Message Identifier for CMAS State/Local WEA Test.
Settable by MMI.
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
4399
112F
CMAS CBS Message Identifier for CMAS State/Local WEA Test for additional languages.
Settable by MMI.
The ME shall receive the messages dependent on the language indicated in the CBS message and the language indicator settings in the ME.
For subscriber opt-out requirements, see 3GPP TS 22.268 [28].
4400
1130
CMAS CBS Message Identifier for geo-fencing trigger messages.
EU-Alert Message Identifier for geo-fencing trigger messages.
Korean Public Alert System (KPAS) Message Identifier for geo-fencing trigger messages.
4401
1131
Non-ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality.
Not applicable for US WEA
4402
1132
Non-ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when an earthquake occurs.
Not applicable for US WEA
4403
1133
Non-ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when a volcanic eruption occurs.
Not applicable for US WEA
4404
1134
Non-ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when a disaster whose characteristic is water (e.g. flood, typhoon, hurricane or tsunami) occurs.
Not applicable for US WEA
4405
1135
Non-ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when a disaster whose characteristic is fire (e.g. forest fire or building fire) occurs.
Not applicable for US WEA
4406
1136
Non-ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when a disaster whose characteristic is pressure (e.g. landslide or avalanche) occurs.
Not applicable for US WEA
4407
1137
Non-ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when a disaster whose characteristic is wind (e.g. tornado or gale) occurs.
Not applicable for US WEA
4408
1138
Non-ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when a disaster whose characteristic is dust (e.g. yellow dust or sandstorm) occurs.
Not applicable for US WEA
4409
1139
Non-ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when a disaster whose characteristic is chemical hazard (e.g. radiation leak or toxic substance leak) occurs.
Not applicable for US WEA
4410
113A
Non-ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when an epidemic occurs.
Not applicable for US WEA
4411
113B
Non-ETWS CBS Message Identifier for test message dedicated to UEs with no user interface and with ePWS functionality.
Not applicable for US WEA
4412
113C
ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality.
Not applicable for Japan ETWS
4413
113D
ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when an earthquake occurs.
Not applicable for Japan ETWS
4414
113E
ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when a volcanic eruption occurs.
Not applicable for Japan ETWS
4415
113F
ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when a disaster whose characteristic is water (e.g. flood, typhoon, hurricane or tsunami) occurs.
Not applicable for Japan ETWS
4416
1140
ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when a disaster whose characteristic is fire (e.g. forest fire or building fire) occurs.
Not applicable for Japan ETWS
4417
1141
ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when a disaster whose characteristic is pressure (e.g. landslide or avalanche) occurs.
Not applicable for Japan ETWS
4418
1142
ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when a disaster whose characteristic is wind (e.g. tornado or gale) occurs.
Not applicable for Japan ETWS
4419
1143
ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when a disaster whose characteristic is dust (e.g. yellow dust or sandstorm) occurs.
Not applicable for Japan ETWS
4420
1144
ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when a disaster whose characteristic is chemical hazard (e.g. radiation leak or toxic substance leak) occurs.
Not applicable for Japan ETWS
4421
1145
ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality when an epidemic occurs.
Not applicable for Japan ETWS
4422
1146
ETWS CBS Message Identifier for test message dedicated to UEs with no user interface and with ePWS functionality.
Not applicable for Japan ETWS
4423 - 6399
1147 – 18FF
Intended as PWS range in future versions of the present document.
These values shall not be transmitted by networks that are compliant to this version of this document. If a Message Identifier from this range is in the "search list", the ME shall attempt to receive this CBS message.
6400
1900
EU-Info Message Identifier for the local language as defined in ETSI TS 102 900 [32].
6401 – 40959
1901 – 9FFF
Intended for standardization in future versions of this document . These values shall not be transmitted by networks that are compliant to this version of this document. If a Message Identifier from this range is in the "search list", the ME shall attempt to receive this CBS message.
40960 - 45055
A000 - AFFF
PLMN/SNPN operator specific range. The type of information provided by PLMN or SNPN operators using these Message Identifiers is not guaranteed to be the same across different PLMNs or SNPNs. If a Message Identifier from this range is in the "search list", the ME shall attempt to receive this CBS message. In a PLMN, the MS shall discard messages in this MI value range unless received from HPLMN, EHPLMN or PLMN that is equivalent to HPLMN or EHPLMN. In an SNPN, the MS shall discard messages in this MI value range unless received from the subscribed SNPN or an SNPN equivalent to the subscribed SNPN.
45056 - 61439
B000 - EFFF
Intended as PLMN/SNPN operator specific range in future versions of this document. These values shall not be transmitted by networks that are compliant to this version of this document. If a Message Identifier from this range is in the "search list", then the ME shall attempt to receive this CBS message.
61440 - 65534
F000 - FFFE
Intended as PLMN/SNPN operator specific range in future versions of this document. These values shall not be transmitted by networks that are compliant to this version of this document. If a Message Identifier from this range is in the "search list", then the ME shall attempt to receive this CBS message.
Not settable by MMI.
65535
FFFF
Reserved, and should not be used for new services, as this value is used on the SIM to indicate that no Message Identifier is stored in those two octets of the SIM. If this Message Identifier is in the "search list", the ME shall attempt to receive this CBS message.
Not settable by MMI.
Generally, the MMI for entering any Message in the ME is left to the manufacturers' discretion. However, the codes allowed to be set by MMI in the table above shall be capable of being specified via their decimal representation i.e.:
Octet 3 Octet 4.
0000 0000 0000 0000 (decimal '000').
0000 0000 0000 0001 (decimal '001').
0000 0000 0000 0010 (decimal '002').
0000 0000 0000 0011 (decimal '003').
: : :
0000 1111 1111 1111 (decimal '4095').
0001 0001 0000 0000 (decimal '4352').
: : :
0001 0001 0001 0001 (decimal '4369').
0001 0001 0001 0011 (decimal '4371').
: : :
0001 0001 0001 1110 (decimal '4382').
0001 0001 0010 0000 (decimal '4384').
: : :
1110 1111 1111 1111 (decimal '61439').
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.1.2.3 Data Coding Scheme
|
This parameter indicates the intended handling of the CBS message at the MS, the alphabet/coding, and the language (when applicable). This is defined in 3GPP TS 23.038 [3].
When the SIM indicates one or more language preferences, the ME shall, by default, use the language(s) stored in the SIM (in the EFPL file) to set any language filter mechanisms provided by the ME.
Optionally, when allowed by language code processing specified below, the user can select the language(s) required by using an MMI, to determine whether a particular CBS message should be displayed.
Where the message relates to a public warning system, the Message Identifier values 4370 through 4382, 4396 and 4398 relate to warning messages delivered in languages which are mandatory to receive. The ME shall not use any language filter mechanisms or use the language(s) selected through the MMI to determine whether a particular CBS message should be displayed for these Message Identifier values. This does not affect the ability to set a particular message identifier by MMI.
Where the message relates to a public warning system, the Message Identifier values 4383 through 4395, 4397 and 4399 relate to warning messages delivered in languages which are optional to receive. For these values, the ME can use language filter mechanisms and the MS may use the language(s) selected through the MMI to determine whether a particular CBS message should be displayed. Even if the Message Identifier is not settable by MMI, the message shall still be discarded if the language is not set to be displayed.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.1.2.4 Page Parameter
|
This parameter is coded as two 4-bit fields. The first field (bits 0‑3) indicates the binary value of the total number of pages in the CBS message and the second field (bits 4‑7) indicates binary the page number within that sequence. The coding starts at 0001, with 0000 reserved. If a mobile receives the code 0000 in either the first field or the second field then it shall treat the CBS message exactly the same as a CBS message with page parameter 0001 0001 (i.e. a single page message).
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.1.2.5 Content of Message
|
This parameter is a copy of the 'CBS-Message-Information-Page' as sent from the CBC to the BSC.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.1.3 ETWS Primary Notification message
| |
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.1.3.1 General Description
|
The ETWS Primary Notification message is transmitted to a MS in idle mode and dedicated mode as described in 3GPP TS 44.018 [26], and to a MS in packet transfer mode as described in 3GPP TS 44.060 [27]. The ETWS Primary Notification message is structured as in the table in clause 9.4.1.3.2.
This message is only applicable in GSM.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.1.3.2 Message Parameter
|
Octet Number(s)
Field
1‑2
Serial Number
3‑4
Message Identifier
5-6
Warning Type
7-56
Warning Security Information
The octets in the above table are transmitted in order, starting with octet 1. The bits within these octets are numbered 0 to 7; bit 0 is the low order bit and is transmitted first.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.1.3.3 Serial Number
|
This parameter identifies a particular ETWS Primary Notification message from the source and type indicated by the Message Identifier and is altered every time the ETWS Primary Notification message with a given Message Identifier is changed. The coding of this parameter is same as that defined in clause 9.4.1.2.1.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.1.3.4 Message Identifier
|
This parameter identifies the source and type of the ETWS Primary Notification message. The coding of this parameter is same as that defined in clause 9.4.1.2.2.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.1.3.5 Warning Type
|
This parameter identifies the warning type of the ETWS Primary Notification message. It is identical with the Warning Type described in clause 9.3.24 with respect to its structure and possible value range.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.1.3.6 Warning Security Information
|
This parameter identifies the warning security information of the ETWS Primary Notification message. The coding of this parameter is same as that defined in clause 9.3.25. The UE shall ignore this parameter.
NOTE: The Warning Security Information parameter is included due to requirements in earlier versions of this document.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.2 UMTS
|
The CBS messages which are transmitted by the RNS to the UE include two types of messages: CBS Message (user information) and Schedule Message (schedule of CBS messages).
The format of the CBS Message containing user information is described in this clause and in 3GPP TS 25.324 [19].
The format of the Schedule Message is described in 3GPP TS 25.324 [19].
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.2.1 General Description
|
The CBS message is transmitted as one unit over the radio interface. On layer two of the UMTS radio interface the logical channel CTCH is used.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.2.2 Message Parameter
|
Octet Number(s)
Parameter
1
Message Type
2 – 3
Message ID
4 – 5
Serial Number
6
Data Coding Scheme
7 – N
CB Data
The octets in the above table are transmitted in order, starting with octet 1. The bits within these octets are numbered 0 to 7; bit 0 is the low order bit and is transmitted first.
For ETWS, the transmission order of the parameter is only applicable to the secondary notification.
For value N in the above table see 3GPP TS 25.324 [19].
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.2.2.1 Message Type
|
This parameter indicates the type of a message, either a CBS message or a Schedule Message. The Coding of the Message Type is described in 3GPP TS 25.324 [19].
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.2.2.2 Message ID
|
This parameter identifies the source and type of the CBS Message (see also 3GPP TS 25.324 [19]). It is identical with the Message Identifier described in clause 9.4.1.2.2 with respect to its structure and possible value range. Within a multi technology network of one operator, e.g. GSM combined with UMTS, the values identifying a given topic shall be identical for both the Message ID and the Message Identifier described in clause 9.4.1.2.2.
The UE shall attempt to receive the CBS messages whose Message ID's are in the "search list". This "search list" shall contain the Message IDs stored in the EFCBMI, EFCBMID and EFCBMIR files on the USIM (see 3GPP TS 31.102 [18]) and any Message Identifiers stored in the UE in a "list of CBS messages to be received". If the UE has restricted capabilities with respect to the number of Message ID's it can search for, the IDs stored in the USIM shall take priority over any stored in the UE.
The MS shall discard a CBS message in Message Identifier value range "A000hex-AFFFhex" unless it is received from:
- HPLMN;
- EHPLMN; or
- PLMN that is equivalent to either HPLMN or EHPLMN.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.2.2.3 Serial Number
|
This parameter identifies a particular CBS Message from the source and type indicated by the Message ID (see also 3GPP TS 25.324 [19]). It is identical with the Serial Number described in clause 9.4.1.2.1 with respect to its structure and possible value range.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.2.2.4 Data Coding Scheme
|
This parameter identifies the the alphabet/coding and the language applied to a CBS Message as defined in 3GPP TS 23.038 [3].
When the USIM indicates one or more language preferences, the UE shall, by default, use the language(s) stored in the USIM (in the EFPL file) to set any language filter mechanisms provided by the UE.
Optionally, when allowed by language code processing specified below, the user can select the language(s) required by using an MMI, to determine whether a particular CBS message should be displayed.
Where the message relates to a public warning system, the Message Identifier values 4370 through 4382, 4396 and 4398, relate to warning messages delivered in languages which are mandatory to receive. The ME shall not use any language filter mechanisms or use the language(s) selected through the MMI to determine whether a particular CBS message should be displayed for these Message Identifier values. This does not affect the ability to set a particular message identifier by MMI.
Where the message relates to a public warning system, the Message Identifier values 4383 through 4395, 4397 and 4399, relate to warning messages delivered in languages which are optional to receive. For these values, the ME can use language filter mechanisms and the MS/UE may use the language(s) selected through the MMI to determine whether a particular CBS message should be displayed. Even if the Message Identifier is not settable by MMI, the message shall still be discarded if the language is filtered or is not set to be displayed.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.2.2.5 CB Data
|
This parameter consists of the following WRITE-REPLACE primitive parameters as received from the CBC (see clause 9.2.2):
- Number-of-Pages;
- CBS‑Message‑Information‑Page;
- CBS-Message-Information-Length.
Octet Number(s)
Parameter
1
Number-of-Pages
2 – 83
CBS‑Message‑Information‑Page 1
84
CBS-Message-Information-Length 1
…
…
CBS‑Message‑Information‑Page n
CBS-Message-Information-Length n
NOTE: n equal to or less than 15
The octets in the above table are transmitted in order, starting with octet 1. The bits within these octets are numbered 0 to 7; bit 0 is the low order bit and is transmitted first.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.3 E-UTRAN
| |
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.3.1 General Description
|
The warning message may be segmented within E-UTRAN for transmission over radio interface.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.3.2 Message Parameter
|
Parameter
Message Identifier
Serial Number
CB Data {Warning Message Content E-UTRAN},
Data Coding Scheme
Warning Area Coordinates (O)
The table gives a high-level description of the warning message content. The format of the warning message is described in 3GPP TS 36.331 [36].
For ETWS, the description of the warning message content is only applicable for the secondary notification. Description of the ETWS Primary Notification message is specified in clause 9.4.3.3.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.3.2.1 Message Identifier
|
This parameter identifies the source and type of the warning message. The contents of the parameter are specified in clause 9.4.1.2.2 with respect to its structure and possible value range.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.3.2.2 Serial Number
|
This parameter identifies a particular warning message from the source and type indicated by the Message Identifier. The contents of the parameter are specified in clause 9.4.1.2.1 with respect to its structure and possible value range.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.3.2.3 Data Coding Scheme
|
This parameter identifies the alphabet/coding and the language applied to the warning message as defined in 3GPP TS 23.038 [3]. The contents of the parameter are specified in clause 9.4.2.2.4 with respect to its structure and possible value range.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.3.2.4 CB Data
|
This parameter contains the content of the warning message and is contained in the Warning Message Content E-UTRAN IE (see clause 9.3.35) of the WRITE-REPLACE-WARNING-REQUEST Request message received from the CBC (see clause 9.2.16). It is encoded as specified in clause 9.4.2.2.5.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.3.2.5 Warning Area Coordinates
|
This parameter contains the coordinates of the warning area and is contained in the Warning Area Coordinates IE (see clause 9.3.63) of the WRITE-REPLACE-WARNING-REQUEST Request message received from the CBC (see clause 9.2.16) or WRITE-REPLACE-WARNING-REQUEST-NG-RAN request message received from the CBCF (see clause 9.2.26).
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.3.3 ETWS Primary Notification message
| |
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.3.3.1 General Description
|
The ETWS Primary Notification message for E-UTRAN radio interface is described in 3GPP TS 36.331 [36]. The ETWS Primary Notification message is structured as in the table in clause 9.4.3.3.2.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.3.3.2 Message Parameter
|
Octet Number(s)
Parameter
1‑2
Message Identifier
3‑4
Serial Number
5-6
Warning Type
7-56
dummy
The octets in the above table are transmitted in order, starting with octet 1. The bits within these octets are numbered 0 to 7; bit 0 is the low order bit and is transmitted first.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.3.3.3 Message Identifier
|
This parameter identifies the source and type of the ETWS Primary Notification message. The contents of the parameter are specified in clause 9.4.1.2.2 with respect to its structure and possible value range.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.3.3.4 Serial Number
|
This parameter identifies a particular ETWS Primary Notification message from the source and type indicated by the Message Identifier and is altered every time the ETWS Primary Notification message with a given Message Identifier is changed. The contents of the parameter are specified in clause 9.4.1.2.1 with respect to its structure and possible value range.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.3.3.5 Warning Type
|
This parameter identifies the warning type of the ETWS Primary Notification message. It is identical with the Warning Type described in clause 9.3.24 with respect to its structure and possible value range.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.3.3.6 Dummy
|
This parameter is not used in the specification. The UE shall ignore this parameter.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.4.4 NG-RAN
|
The format of the CBS Message for NG-RAN is same as format of the CBS Message defined for E-UTRAN as described in clause 9.4.3.2 and 3GPP TS 36.331 [36].
The format of the ETWS Primary Notification message is same as format of the ETWS Primary Notification message defined for E-UTRAN as described in clause 9.4.3.3 and 3GPP TS 36.331 [36].
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.5 CBS Compression
|
Cell Broadcast messages may be compressed in accordance with the compression algorithm described in 3GPP TS 23.042 [14].
The Data Coding Scheme parameter (see clause 9.4.1.2.3) indicates whether or not a CBS Message is compressed.
Compression and decompression may take place between a CBE and an MS/UE or between a CBC and an MS/UE.
The compression applies only to user information sent between the CBC and the MS/UE i.e. excludes any padding octets.
Padding in the case of CBS compression is defined as an integral number of octets where each padding octet has a value FF hexadecimal. The insertion of padding for different scenarios is described in the paragraphs below.
The compression footer (see 3GPP TS 23.042 [14]) delimits the compressed user information bit stream at an octet boundary. The remainder of the 'CBS-Message-Information-Page' sent between the CBC and the BSC contains padding octets. The parameter 'CBS-Message-Information-Length' identifies the sum of the compressed octets, the compression header, and the compression footer (see 3GPP TS 23.042 [14]), but not any padding.
Compression may apply to a single 'CBS-Message-Information-Page' or across multiple 'CBS‑Message‑Information‑Page's.
In the case where Compression applies only to a single 'CBS-Message-Information-Page', the compression header shall be the first octet in that 'CBS-Message-Information-Page' and the compression footer shall immediately follow the compressed data stream. Any remaining octets after the compression footer shall contain padding up to and including the 82nd octet position. However, if the 82nd octet position contains the compression footer then there is no padding.
In the case where compression applies across multiple 'CBS-Message-Information-Page's, the compression header shall be present only in the first octet position of the first 'CBS-Message-Information-Page'. The compression footer shall immediately follow the compressed data stream which will terminate within the last 'CBS-Message-Infirmation-Page'. Any remaining octets after the compression footer in the last 'CBS-Message-Information-Page' shall contain padding up to and including the 82nd octet position in the last 'CBS-Message-Information-Page'. However, if the 82nd octet position of the last 'CBS-Message-Information-Page' contains the compression footer then there is no padding.
If it is required to convey different blocks of information which are to be treated by the MS/UE as though they were physically independent pages rather than concatenated information then page break characters (see 3GPP TS 23.038 [3]) may be inserted in the character stream prior to compression. The boundaries created by the page breaks will not normally align with the boundaries set by the page number parameters and so the page number parameters cannot be used to identify physically separate blocks of meaningful information.
The decoding at the MS/UE may be achieved by first locating the compression footer octet by working back from the 82nd octet in the last 'CBS-Message-Information-Page'. If padding is present, the MS/UE must skip backwards over the padding until a non padding octet is found. By definition this octet must be the compression footer. The compression footer has a pre-defined bit combination which can never replicate a padding octet. If padding is not present in the 82nd octet position of the last 'CBS-Message-Information-Page', by definition the 82nd octet must be the compression footer.
The compression footer defined in 3GPP TS 23.042 [14] indicates whether there are any compressed data bits contained within the compression footer octet and, if not, how many compressed data bits are contained within the octet immediately preceding the compression footer. In order to prevent possible replication of the padding octet value in the compression footer octet value, the compression mechanism must ensure that when bits 0, 1, 2 in the compression footer are all ones all other bits in the compression footer octet are set to 0.
9A Service Based Interface for 5G System
9A.1 Introduction
Within the 5GCN, the AMF offers services to the CBCF via the Namf service-based interface (see 3GPP TS 23.501 [39] and 3GPP TS 23.502 [43]).
Figure 9A.1-1 depicts the 5GS PWS system architecture, using the service-based interface representation showing how the network functions interact with each other.
Figure 9A.1-1: 5GS PWS system architecture – CBCF/PWS-IWF - AMF
Service-based interface to support 5GS PWS:
Namf: Service-based interface exhibited by AMF.
NOTE: No services are provided by CBCF or PWS-IWF, thus no service-based interfaces are depicted for these NFs in the 5GS PWS system architecture.
The table 9A.1-1 shows the AMF Service and Service Operations specific for PWS:
Table 9A.1-1 AMF Service for PWS
Service Name
Service Operations
Operation Semantics
Consumer
Namf_Communication
NonUeN2MessageTransfer
Request/Response
CBCF, PWS-IWF
NonUeN2InfoSubscribe
Subscribe/Notify
CBCF, PWS-IWF
NonUeN2InfoUnSubscribe
Subscribe/Notify
CBCF, PWS-IWF
NonUeN2InfoNotify
Subscribe/Notify
CBCF, PWS-IWF
9A.2 Namf_Communication Service
9A.2.1 Service Description
The Namf_Communication service is specified in 3GPP TS 23.502 [43] clause 5.2.2.2 and stage 3 is specified in 3GPP TS 29.518 [41].
9A.2.2 Service Operations
9A.2.2.1 Namf_Communication_NonUeN2MessageTransfer service operation
The Namf_Communication_NonUeN2MessageTransfer service operation is specified in 3GPP TS 23.502 [43] clause 5.2.2.2.17.
The NonUeN2MessageTransfer service operation shall be invoked by the NF Service Consumer (e.g. CBCF or PWS-IWF) to initiate or stop broadcast in one or more cells as indicated in the Warning Area IE. The AMF shall accept the request and respond to the NF Service Consumer immediately.
When NonUeN2MessageTransfer service operation is used for PWS services:
a) PWS Write-Replace-Warning Request message (see clause 9.2.26) or the Stop-Warning Request message (see clause 9.2.28) are transferred in an N2 Message Container via the NonUeN2MessageTranfer request operation (along with a number of IEs);
The N2 Message Container contains all the available elements from the Write-Replace-Warning Request message or the Stop-Warning Request message with the exception of the List of TAIs IE and the Send Write-Replace-Warning Indication IE or the Send Stop-Warning Indication IE. The PWS message in the N2 Message Container is sent by the AMF via N2 to NG-RAN.
b) Write-Replace-Warning Confirm message (see clause 9.2.27) or the Stop-Warning Confirm message (see clause 9.2.29) returned to the NF Service Consumer via the NonUeN2MessageTranfer response operation;
c) the List of TAIs IE shall be used by the AMF to determine to which NG-RAN nodes the N2 Message Container needs to be forwarded to. The List of TAIs IE is not included in the N2 Message Container. If the List of TAIs IE is not present then the message shall be forwarded to all NG-RAN nodes served by the AMF, subject to the RAT Selector NG-RAN;
d) each NonUeN2MessageTransfer message is uniquely identified by the Message Identifier IE, the Serial Number IE and the Message Type IE. These IEs are also included in the N2 Message Container;
e) if the Send Write-Replace-Warning-Indication IE is present in the Write-Replace-Warning Request message then the AMF shall send the associated Write-Replace-Warning Indication message(s) to the NF Service Consumer as specified in clause 9A.2.2.3. The Send Write-Replace-Warning-Indication IE is not included in the N2 Message Container, and
f) if the Send Stop-Warning-Indication IE is present in the Stop-Warning Request message then the AMF shall send the associated Stop-Warning Indication message(s) to the NF Service Consumer as specified in clause 9A.2.2.3. The Send Stop-Warning-Indication IE is not included in the N2 Message Container.
9A.2.2.2 Namf_Communication_NonUeN2InfoSubscribe service operation
The Namf_Communication_NonUeN2InfoSubscribe service operation is specified in 3GPP TS 23.502 [43] clause 5.2.2.2.18.
The NonUeN2InfoSubscribe service operation shall be invoked by the NF Service Consumer (e.g. CBCF or PWS-IWF) to subscribe to the delivery of non-UE specific PWS information from the NG-RAN node, e.g. for PWS events, sent via N2 to the AMF.
When NonUeN2InfoSubscribe service operation is used for PWS services:
a) The NF Service Consumer ID is an identifier which is configured in the CBCF or PWS-IWF;
b) The N2 information types are:
- WarningIndications;
- RestartFailure;
c) if the N2 information type is WarningIndications then the NF Service Consumer subscribes to receiving Write-Replace-Warning Indication messages (see clause 9.2.30) and Stop-Warning Indication messages (see clause 9.2.31) from the AMF, and
NOTE: If the Indication messages are actually sent to the NF Service Consumer depends on the presence of the Send Write-Replace-Warning Indication IE or the Send Stop-Warning Indication IE; see clause 9A.2.2.1.
d) if the N2 information type is RestartFailure then the NF Service Consumer subscribes to receiving Restart Indications (see clause 9.2. 32) and Failure Indications (see clause 9.2. 33) from the NG-RAN node.
9A.2.2.2A Namf_Communication_NonUeN2InfoUnSubscribe service operation
The Namf_Communication_NonUeN2InfoUnSubscribe service operation is specified in 3GPP TS 23.502 [43] clause 5.2.2.2.19.
The NonUeN2InfoUnSubscribe service opration shall be invoked by the NF Service Consumer (e.g. CBCF or PWS‑IWF) to unsubscribe to stop notifying non-UE specific N2 information from the NG-RAN node, e.g. for PWS events.
9A.2.2.3 Namf_Communication_NonUeN2InfoNotify service operation
The Namf_Communication_NonUeN2InfoNotify service operation is specified in 3GPP TS 23.502 [43] clause 5.2.2.2.20.
The NonUeN2InfoNotify service operation is used by AMF to notify a particular PWS event towards the NF Service Consumer (e.g. CBCF or PWS-IWF) that has subscribed for the specific information. The AMF receives messages for such PWS events from NG-RAN via N2.
When NonUeN2InfoNotify service operation is used for PWS services, the N2 information consists of all (mandatory and optionally) available information provided via N2 in the Write-Replace Warning Indication (see clause 9.2.30), a Stop Warning Indication (see clause 9.2.31), a PWS Restart Indication (see clause 9.2.32) or a PWS Failure Indication (see clause 9.2.33).
9A.2.3 Service operation message flows
9A.2.3.1 Service flow for message transfer
Write-Replace-Warning Request messages and Stop-Warning-Request messages are transported with the NonUeMessageTransfer service operation. The procedure is shown in figure 9A.2.3-1.
Figure 9A.2.3.1-1: Message tranfer procedure
1) If the CBCF supports reception of Wrtite-Replace-Warning Notifications and Stop-Warning Notifications then the CBCF uses the Namf_Communication_NonUeInfoSubscribe service operation to subscribe to these notifications.
2a) The CBCF sends a Write-Replace-Warning Request message or a Stop-Warning-Request message to the AMF using the Namf_Communication_NonUeN2MessageTransfer service operation.
2b) The AMF returns a Namf_Communication_NonUeN2MessageTransfer response message.
3) The AMF determines from the List of TAIs IE to the NG-RAN nodes the N2 Message Container shall be forwarded to.
4) The AMF forwards the messages included in the N2 Message Container to the selected NG-RAN nodes via N2 and receives a response from the NG-RAN nodes.
5) The AMF may aggregate the responses it has received from the NG-RAN nodes.
6) The AMF forwards the (aggregated) response(s) as Write-Replace-Warning Notification(s) or Stop-Warning Notifications to the CBCF using the Namf_Communication_NonUeNotify service operation if the CBCF has subscribed to receiving these notificatins in step 1.
9A.2.3.2 Service flow for Restart and Failure Indication messages
Restart and Failure Indications are send by NG-RAN nodes and are forwarded to the CBCF by the AMF if the CBCF has subscribed to receiving such indications. The procedure is shown in figure 9A.2.4-1.
Figure 9A.2.3.2-1: Indication message transfer procedure
1 If the CBCF supports reception of Restart Indication messages and Failure Indication messages then the CBCF uses the Namf_Communication_NonUeInfoSubscribe service operation to subscribe to these notifications.
2 A RAN Node sends a Restart Indication or a Failure Indication to the AMF.
3 The AMF forwards the Restart Indication or a Failure Indication to the CBCF using the Namf_Communication_NonUeInfoNotify service operation.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
10 CBS Index
|
An index structure is defined in this clause. Index can be used by the operator to inform the end user about the type of CBS services available. Index has the structure of a tree. It can thus have sub parts which are called subindexes. A subindex can be embedded in the same index message as its parent ("embedded subindex") or it can physically be in a separate index message ("child subindex"). Every index message has a unique message identifier. They are always of the same type. Message Code 1010101010b shall be used to indicate this type. The root of the index structure shall be the index message with message identifier 0. Other index messages are linked to the root index with links. Definition of their message identifiers is left to the operator. A format ("enhanced format") for the index messages is described in this clause. If this enhanced format is used in the index message the MS/UE can present the index messages in its preferred format. Available CBS services are introduced in the index. This means that their message identifier and name are stated. Enhanced format includes a mechanism for separating a normal service introduction from embedded subindex introduction and child subindex introduction. The introduction of an embedded subindex specifies the "subindex-id" used for identifying services that belong to this subindex. Embedded subindexes can have subindexes embedded in them etc. If these "second level embedded subindexes" are introduced their subindex-id shall begin with the subindex-id of their parent. Same principle applies for subindexes in third, fourth etc. level. An example of an index structure is given in figure 6. Enhanced format includes a mechanism which allows the terminals to identify that the format of the index message is enhanced. The index-id -field and the above mentioned Message Code (1010101010b) constitute this mechanism: message-format = index-id index-element-intro+. index-id = "EI" version crlf. version = number+. number = "1" | "2" | "3" | "4" | "5" | "6" | "7" | "8" | "9" | "0". index-element-intro = subindex-intro | service-intro. subindex-intro = subindex-id " " subindex-name crlf. subindex-id = subindex-character+. subindex-character = "a" | "b" | … | "z" | "A" | "B" | … | "Z". subindex-name = name-character+. name-character = <gsm03.38character excluding <CR> and <LF> >. crlf = <CR> <LF>. service-intro = subindex-id message-id delimiter service-name crlf. message-id = number+. delimiter = "." | " ". service-name = name-character+. Current version used is 1. The use of "." as delimiter means that this service is a child subindex of the index structure. Delimiter " " is used in all other cases. Subindex-id shall not be used if the service introduced is in the first level of the index. Subindex-id:s are used in alphabetical order within an index message. They can be re-used in a child subindex. 0 Index: (MsgId=0, Message Code = 1010101010b) EI1 20 Hospitals 34 Taxis a News a201 Int News a202 Nat News a203 Local News b Sports b301 Football News b302 Hockey Results b303 Basketball c Finance c401 Finance News ca Quotes NYSE ca412 NYSE industrial ca413 NYSE electronics ca414 NYSE blue c420.Quotes Tokyo 420 Quotes Tokyo: (MsgId = 420, Message Code = 1010101010b) d Weather d501 Local Weather d502 National Weather d503 Weather in Europe d504 Weather in the World EI1 421 Tokyo Industrial 422 Tokyo Finance 423 Tokyo Blue 900.Buy and Sell 900 Buy and Sell: (MsgId = 900, Message Code = 1010101010b) EI1 901 Cars 902 Bikes 903 Boats a Home Electronics a911 Computers a912 Televisions a913 Radios 920 Baby Clothes 930 Magazines 940 Books Figure 6 Annex A (informative): Void Annex B (normative): 5GS Network Architecture, AMF to CBC inter-connection via PWS-IWF B.1 5GS PWS architecture with PWS-IWF Figure B.1-1 depicts the optional deployment network structure of PWS architecture in 5GS with AMF to CBC inter-connection via PWS-IWF using the reference point representation showing how the network functions interact with each other. In this option the PWS-IWF implements functionality to transfer messages between N50 and SBc reference points, and vice versa. Figure B.1-1: 5GS PWS architecture with PWS-IWF The PWS architecture using PWS-IWF contains the following reference points: N2: Reference point between the NG-RAN and the AMF. NOTE 1: NG-RAN can be NR based or E-UTRA based (See 3GPP TS 23.501 [39] and 3GPP TS 38.413 [40]). SBc: Reference point between the PWS-IWF and the CBC. NOTE 2: The requirements for SBc in this deployment option corresponds to the requirements for SBc in the EPS network architecture as (see 3GPP TS 29.168 [35]). N50: Reference point between the AMF and the PWS-IWF. NOTE 2: N50 uses service-based interfaces, further described in clause 9A of the present document. The CBE and the interface between CBE and CBC are out of scope of 3GPP specifications. The present document describes logical functional entities, and how these are realized in actual deployments is an implementation and deployment issue. It can however be foreseen that the PWS-IWF functionality may be co-located with the AMF, with the CBC, or deployed as a stand-alone network function. At AMF/PWS-IWF co-location, the AMF/PWS-IWF entity interacts with the CBC via SBc. At CBC/PWS-IWF co-location, the CBC/PWS-IWF interacts with the AMF via N50. At stand-alone PWS-IWF, the PWS-IWF interacts with the AMFvia N50 and with the CBC via SBc. A PWS-IWF co-located with AMF or a stand-alone PWS-IWF may interface to one CBC or multiple CBCs (i.e. the PWS-IWF is allowed to have SCTP transport associations established with one or multiple CBCs). A stand-alone PWS-IWF or a PWS-IWF co-located with the CBC may interface to several AMFs. B.2 CBE Functionality See clause 4 of the present document. B.3 CBC Functionality See clause 5 of the present document. B.4 PWS-IWF Functionality B.4.1 PWS-IWF generic functionality The PWS-IWF is a logical function which functionality is to translate from N50 to SBc. If the Write-Replace-Warning-Indication and Stop-Warning-Indication or the Restart-Indication-E-UTRAN and Failure-Indication-E-UTRAN are supported on SBc then the PWS-IWF shall manage the subscriptions for the corresponding notifications that may be received over N50. The PWS-IWF may interface to one or multiple AMFs. The PWS-IWF may interface to one or multiple CBCs. Exceptions from straightforward mapping by the PWS-IWF from SBc based messages and parameters to SBI based messages and parameters are described in the following clauses. B.4.2 Mapping of Repetition-Period If the PWS-IWF receives a Write-Replace-Warning Request message from the CBC which contains the Extended Repetition-Period IE then the PWS-IWF shall map the Extended Repetition-Period IE onto the Repetition-Period NG-RAN IE in the Write-Replace-Warning Request message towards the AMF and shall ignore the Repetition-Period IE that is received from the CBC. B.5 AMF Functionality See clause 6 of the present document. B.6 UE Functionality See clause 8 of the present document. B.7 Protocol stack when AMF and CBC inter-connects via PWS-IWF Figure B.7-1: CBC - NG-RAN with PWS-IWF Legend: - NG Application Protocol information for Cell Broadcast (NG-AP-CB): Subset of NG-AP information that the AMF transparently relays between the NG-RAN and the PWS-IWF. NG-AP-CB corresponds to a subset of NG-AP defined in TS 38.413 [40]. - NG Application Protocol (NGAP): Application Layer Protocol between the NG-RAN node and the AMF. The NGAP protocol is defined in 3GPP TS 38.413 [40]. - SBc Application Protocol (SBc-AP): Application Layer Protocol between PWS-IWF and CBC. This protocol supports transfer of warning messages. - SCTP for the control plane (SCTP): This protocol guarantees delivery of signalling messages between AMF and NG-RAN (N2), and between PWS-IWF and CBC (SBc). SCTP is defined in IETF RFC 4960 [33]. - HTTP/2: Application layer protocol for Service based interface between AMF and CBCF. HTTP/2 is defined in IETF RFC 9113 [42]. Annex C (informative): Change history TSG TSG Tdoc T2-Tdoc CR REL VERS NEW VERS SUBJECT T#5 TP-99179 New R99 2.0.0 3.0.0 Transfer of GSM 03.41 v7.1.0 to 3GPP T#6 TP-99237 T2-991064 001 R99 3.0.0 3.1.0 Adaptation of the scope of TS 23.041 from "GSM only" to "GSM and UMTS" T#6 TP-99237 T2-991062 002 R99 3.0.0 3.1.0 LCS Utilization of CBS T#7 TP-000024 T2-000134 003 R99 3.1.0 3.2.0 Addition of LCS message identifier to support GPS Navigation message T#7 TP-000024 T2-000130 004 R99 3.1.0 3.2.0 Adaptation of the scope from "GSM only" to "GSM and UMTS" - Part II T#9 TP-000143 T2-000553 005 R99 3.2.0 3.3.0 Defining Assisted GPS Broadcast Identifiers T#11 - - - Rel-4 3.3.0 4.0.0 Upgrade to Rel-4 T#12 TP-010128 T2-010532 007 Rel-4 4.0.0 4.1.0 Clarification of Geographical Scope T#14 TP-010280 T2-011024 008 Rel-4 4.1.0 4.2.0 Clarification on the use of Message IDs in multi-technology networks T#16 TP-020104 T2-020509 010 Rel-4 4.2.0 4.3.0 Update of references T#16 - - - 4.3.0 5.0.0 Upgrade to Rel-5 T#17 TP-020252 - 011 rev1 Rel-6 5.0.0 6.0.0 Identification of a directory number in a CBS-Message-Information-Page T#19 TP-030038 T2-030088 014 Rel-6 6.0.0 6.1.0 CB Data lenght T#22 TP-030267 T2-030575 016 Rel-6 6.1.0 6.2.0 CB Data structure CT#31 CP-060126 C1-060128 017r1 Rel-7 6.2.0 7.0.0 CBS – Reference correction CT#41 7.0.0 8.0.0 Upgrade to Rel-8 CT#41 CP-080535 C1-083618 0019r4 Rel-8 7.0.0 8.0.0 Additions to the protocol aspects of CBS for the realisation of ETWS CT#41 CP-080535 C1-083620 0018r5 Rel-8 7.0.0 8.0.0 Changes to CBS for the realisation of ETWS CT#41 CP-080535 C1-083621 0020r5 Rel-8 7.0.0 8.0.0 Changes to the radio message format aspect of CBS for the realisation of ETWS CT#42 CP-080836 C1-085355 0021r3 Rel-8 8.0.0 8.1.0 Clarification on EPS architecture and ETWS Instruction to terminal CT#42 CP-080836 C1-085354 0022r1 Rel-8 8.0.0 8.1.0 Addition of Warning Security Information CT#42 CP-080873 C1-085129 0023 Rel-8 8.0.0 8.1.0 CBS Message ID table CT#43 CP-090149 C1-091099 0026r2 Rel-8 8.1.0 8.2.0 ETWS Duplication Detection CT#43 CP-090159 C1-090442 0025r1 Rel-8 8.1.0 8.2.0 Clarification of non settable Message ID's through MMI CT#43 8.1.0 8.2.0 Editorial cleanup by MCC CT#44 CP-090320 0027r2 Rel-8 8.2.0 8.3.0 Definition of ETWS Primary Notification message format CT#44 CP-090434 C1-092257 0028r2 Rel-9 8.3.0 9.0.0 Message IDs for the U.S. Commercial Mobile Alert System (CMAS) CT#45 CP-090686 C1-092466 0029 Rel-9 9.0.0 9.1.0 Message Identifiers for PWS CT#45 CP-090670 C1-093124 0031r1 Rel-9 9.0.0 9.1.0 CBS activation time for ETWS information CT#45 CP-090682 C1-093812 0032r1 Rel-9 9.0.0 9.1.0 Cell wide Geographical Scope (GS) code 00 CT#45 CP-090682 C1-093249 0033 Rel-9 9.0.0 9.1.0 Updates on references CT#45 CP-090682 C1-093813 0034r1 Rel-9 9.0.0 9.1.0 Resolution of editor's note CT#45 CP-090682 C1-093251 0035 Rel-9 9.0.0 9.1.0 Fixes for typographical errors CT#45 CP-090682 C1-093252 0036r1 Rel-9 9.0.0 9.1.0 Clarification on duplicate use of "immediate display" CT#45 CP-090686 C1-093531 0037 Rel-9 9.0.0 9.1.0 Updating of references to stage 1 document CT#46 CP-090912 C1-094929 0039 Rel-9 9.1.0 9.2.0 Additional ETWS requirements for the BSC - CBC Cell Broadcast protocol CT#46 CP-090912 C1-095394 0041r1 Rel-9 9.1.0 9.2.0 Clarification on ETWS secondary notification CT#46 CP-090912 C1-095396 0043r1 Rel-9 9.1.0 9.2.0 Correction of duplicate detection in the UE CT#47 CP-100152 C1-101202 0044r1 Rel-9 9.2.0 9.3.0 Corrections to the Cell Broadcast Service (CBS) for ETWS CT#47 CP-100135 C1-100625 0045 Rel-9 9.2.0 9.3.0 Correction of figure 4b CT#47 CP-100152 C1-101263 0046r1 Rel-9 9.2.0 9.3.0 Addition of Broadcast Message Type CT#48 CP-100345 C1-101950 0050r1 Rel-9 9.3.0 9.4.0 PLMN handling for ETWS duplicate detection CT#48 CP-100345 C1-101551 0052 Rel-9 9.3.0 9.4.0 Removal of editor's note for ETWS CT#49 CP-100501 C1-102734 0053r1 Rel-9 9.4.0 9.5.0 Clarification of precedence for immediate display CT#49 CP-100504 C1-102216 0055 Rel-9 9.4.0 9.5.0 Removal of CMAS reference to a ETWS capability CT#49 CP-100520 C1-102735 0054r1 Rel-10 9.5.0 10.0.0 Clarification of Scope for CB in LTE CT#49 CP-100520 C1-103152 0057 Rel-10 9.5.0 10.0.0 Clarification of definition of "PLMN Wide" in Geographical Scope (GS) indicator CT#50 CP-100744 C1-105127 0058r2 Rel-10 10.0.0 10.1.0 Correction to CMAS Alert levels CT#50 CP-100768 C1-104243 0056r3 Rel-11 10.1.0 11.0.0 Message Identifiers for EU-Alert CT#50 CP-100768 C1-104483 0057 Rel-11 10.1.0 11.0.0 Message Identifier for EU-Info CT#51 CP-110876 C1-114785 0065r3 Rel-11 11.0.0 11.1.0 Correction on Message Identifier for Korean Public Alert System CT#51 CP-110882 C1-114427 0066r2 Rel-11 11.0.0 11.1.0 Coding of Geographical Scope parameter for E-UTRAN/LTE operation. CT#51 CP-110853 C1-115046 0070r3 Rel-11 11.0.0 11.1.0 Correction to UE warning message indication with regards to "digital signature" and "timestamp" CT#51 CP-110882 C1-115255 0071r2 Rel-11 11.0.0 11.1.0 Additional Message Identifiers for CMAS/EU-Alerts CT#51 CP-110882 C1-114923 0072r1 Rel-11 11.0.0 11.1.0 Update Number Processing CT#51 CP-110882 C1-114975 0073r1 Rel-11 11.0.0 11.1.0 Multiple languages used in CBS CT#55 CP-120125 C1-120857 0083r3 Rel-11 11.1.0 11.2.0 Sorting out inconsistency problem in ETWS/PWS specification CT#55 CP-120125 C1-120285 0084 Rel-11 11.1.0 11.2.0 Correction of binary coding in clause 9.4.1.2.2 CT#55 CP-120091 C1-120804 0077r2 Rel-11 11.1.0 11.2.0 Redocumentation and alignment of the public warning system CT#56 CP-120309 C1-122384 0081r4 Rel-11 11.2.0 11.3.0 Alignment of clause 9 for PWS CT#56 CP-120309 C1-121379 0091r1 Rel-11 11.2.0 11.3.0 Correction to the duplication detection mechanism CT#56 CP-120285 C1-121245 0092 Rel-11 11.2.0 11.3.0 Removal of security for ETWS/PWS over E-UTRAN CT#56 CP-120285 C1-122295 0088r3 Rel-11 11.2.0 11.3.0 Alignment and correction of aspects for public warning system for GERAN CT#57 CP-120573 C1-123198 0094r3 Rel-11 11.3.0 11.4.0 Correction to Figure 3.3-1 CT#57 CP-120567 C1-123186 0103r1 Rel-11 11.3.0 11.4.0 Correction of Warning Message Delivery Procedure in GSM CT#57 CP-120492 - 0098r1 Rel-11 11.3.0 11.4.0 Correction of reference to GSMA document "Coding of Cell Broadcast Functions" CT#58 CP-120794 C1-123955 0095r2 Rel-11 11.4.0 11.5.0 Correction for Repetition Rates CT#58 CP-120794 C1-123956 0107r1 Rel-11 11.4.0 11.5.0 Correction of reference in Restart Indication Request CT#58 CP-120774 C1-123875 0111r1 Rel-11 11.4.0 11.5.0 Correcting handling of unused security parameters for warning messages CT#58 CP-120794 C1-124990 0116r2 Rel-11 11.4.0 11.5.0 Message IDs for Operator specific services CT#58 CP-120794 C1-125024 0117r2 Rel-11 11.4.0 11.5.0 USIM file usage for PWS message reception CT#58 CP-120819 C1-124972 0097r5 Rel-12 11.5.0 12.0.0 Report from MME on Warning Message Delivery CT#58 CP-120819 C1-124971 0099r4 Rel-12 11.5.0 12.0.0 Failure List in WRITE-REPLACE-WARNING-CONFIRM and STOP-WARNING-CONFIRM CT#59 CP-130115 C1-130829 0120r2 Rel-12 12.0.0 12.1.0 Correction for Warning Area List CT#59 CP-130129 C1-130831 0123r2 Rel-12 12.0.0 12.1.0 Clause 9.4.3 for E-UTRAN CT#59 CP-130115 C1-130837 0124r2 Rel-12 12.0.0 12.1.0 Warning message reception in Limited Service CT#60 CP-130264 C1-132520 0125r3 Rel-12 12.1.0 12.2.0 CB Message parameter format on the eUTRAN Radio Network – UE interface CT#60 CP-130264 C1-131445 0127r1 Rel-12 12.1.0 12.2.0 CBS message parameter references correction CT#60 CP-130264 C1-131446 0128r1 Rel-12 12.1.0 12.2.0 Failure Indication and Restart Indication handling CT#60 CP-130264 C1-131725 0129r2 Rel-12 12.1.0 12.2.0 Clarification to data coding scheme usage for primary vs secondary notification CT#61 CP-130503 C1-133320 0118r3 Rel-12 12.2.0 12.3.0 Stop-all broadcasting of warning messages and report from MME on Stop Warning Messages in E-UTRAN CT#61 CP-130510 C1-133206 0132r1 Rel-12 12.2.0 12.3.0 CellID in E-UTRAN CT#61 CP-130510 C1-133207 0133r1 Rel-12 12.2.0 12.3.0 Clarification on Duplication Detection CT#61 CP-130510 C1-133646 0134r1 Rel-12 12.2.0 12.3.0 Clarification on PWS CB Data for the eUTRAN Radio interface Post CT#61 Rel-12 12.3.0 12.3.1 Correction of typos CT#62 CP-130750 C1-134137 0137r2 Rel-12 12.3.1 12.4.0 eNodeB ID in Stop-Warning Indication CT#62 CP-130762 C1-134530 0139 Rel-12 12.3.1 12.4.0 Removal of cells=all feature from RNC CT#62 CP-130751 C1-134930 0140r1 Rel-12 12.3.1 12.4.0 Stop all indicator clarification CT#63 CP-140140 C1-140609 0135r5 Rel-12 12.4.0 12.5.0 Restart Indication CT#63 CP-140144 C1-140440 0141r1 Rel-12 12.4.0 12.5.0 Capacity Indication Request not implemented CT#64 CP-140331 C1-141098 0142 Rel-12 12.5.0 12.6.0 Available-Capacity not implemented CT#64 CP-140327 C1-141642 0143r1 Rel-12 12.5.0 12.6.0 Support of category indication for prioritization of emergency alerts CT#66 CP-140836 C1-144414 0146 Rel-12 12.6.0 12.7.0 Removal of CAPACITY-INDICATION reference CT#66 CP-140858 C1-144827 0147r1 Rel-13 12.7.0 13.0.0 Missing Broadcast Message Content Validity Indicator IE CT#68 CP-150310 C1-150914 0149 Rel-13 13.0.0 13.1.0 Correction for List of TAIs CT#68 CP-150310 C1-151465 0151r1 Rel-13 13.0.0 13.1.0 Clarification on CBC Geo-redundancy support in LTE CT#68 CP-150329 C1-151463 0152r1 Rel-13 13.0.0 13.1.0 Serial Number handling for WRITE-REPLACE Request/Indication primitive CT#68 CP-150310 C1-151830 0154 Rel-13 13.0.0 13.1.0 Warning message indication delivery for PWS reporting enhancement CT#68 CP-150329 C1-151831 0155 Rel-13 13.0.0 13.1.0 ETWS Primary Notification message at E-UTRAN interface CT#68 CP-150329 C1-152386 0156r1 Rel-13 13.0.0 13.1.0 Reference corrections and editorial updates CT#70 CP-150700 C1-154874 0157r4 Rel-13 13.1.0 13.2.0 Failure Indication CT#71 CP-160086 C1-160316 0159 Rel-13 13.2.0 13.3.0 Failed cell list parameter content correction Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2016-09 CP-73 CP-160519 0160 2 F RESET COMPLETE and RESET FAILURE Response messages missing 14.0.0 2017-06 CP-76 CP-171092 0161 2 C Addition of new Message Identifiers for FCC mandated Wireless Emergency Alert (WEA, aka CMAS) enhancements 14.1.0 2017-12 CP-78 CP-173067 0165 1 F Correction to the Data Coding Scheme clause in support of NA regulatory requirement 14.2.0 2017-12 CP-78 CP-173069 0166 3 B Support of PWS in 5GS 15.0.0 2018-03 CP-79 CP-180077 0167 2 B PWS message format for NG-RAN in 5G 15.1.0 2018-03 CP-79 CP-180077 0168 3 B AMF to CBC inter-connectivity solution option with and without IWF 15.1.0 2018-03 CP-79 CP-180077 0169 2 B PWS in NR – clause 9.1.3.5 15.1.0 2018-03 CP-79 CP-180077 0170 2 B PWS in NR – clause 9.2.0 15.1.0 2018-03 CP-79 CP-180077 0171 1 B PWS in NR – clause 9.2.x 15.1.0 2018-03 CP-79 CP-180077 0172 3 B PWS in NR – clause 9.3.x 15.1.0 2018-03 CP-79 CP-180077 0173 1 B AMF, CBC and CBCF functionalities for PWS in 5G 15.1.0 2018-03 CP-79 CP-180077 0174 B Service Based Interface for 5G System 15.1.0 2018-06 CP-80 CP-181057 0175 1 F Corrections to table 6 and consistent use of terminology 15.2.0 2018-06 CP-80 CP-181057 0176 F Addition of reference to TS 23.502 15.2.0 2018-06 CP-80 CP-181057 0177 1 B Addition of entity functionality clauses in annex B 15.2.0 2018-06 CP-80 CP-181057 0178 1 F Correction for the use of NG-RAN node and other general corrections 15.2.0 2018-06 CP-80 CP-181057 0180 3 F Addition of reference point between AMF and CBCF 15.2.0 2018-06 CP-80 CP-181057 0181 F Removal of Extended Repetition-Period IE for NG-RAN 15.2.0 2018-06 CP-80 CP-181057 0182 F Correction Warning message content and removal of editor's 15.2.0 2018-06 CP-80 CP-181058 0183 2 F Clarification on no use of container for PWS messages via N2 15.2.0 2018-09 CP-81 CP-182128 0184 1 B Modifications needed to address NG-RAN over SBc 15.3.0 2018-09 CP-81 CP-182128 0185 1 F Corrections to IE names for NG-RAN 15.3.0 2018-09 CP-81 CP-182128 0186 1 F Solving Editor's notes for PWS 15.3.0 2018-09 CP-81 CP-182158 0189 6 B Warning Area Coordinates in WRITE-REPLACE WARNING REQUEST 15.3.0 2018-12 CP-82 CP-183030 0192 1 F Duplicate detection for EUTRA connected to both EPC and 5GCN 15.4.0 2018-12 CP-82 CP-183030 0193 F Resolving the EN for the PWS restoration procedure for NG-RAN 15.4.0 2019-03 CP-83 CP-190100 0194 4 F Additional Message Identifier to direct UEs to perform geo-fencing of CMAS messages 15.5.0 2019-03 CP-83 CP-190082 0195 1 F Corrections on Warning Area List and TAIs for NG-RAN 15.5.0 2019-03 CP-83 CP-190082 0198 1 F Correction on applicability of List of TAIs 15.5.0 2019-03 CP-83 CP-190064 0200 F Incorrect reference 16.0.0 2019-09 CP-85 CP-192071 0201 F Missing references and some editorial cleanup 16.1.0 2019-12 CP-86 CP-193105 0202 3 B Addition of the support of ePWS functionality via E-UTRAN and NG-RAN 16.2.0 2019-12 CP-86 CP-193105 0203 3 B Support of language-independent content mapped to a disaster in a warning message 16.2.0 2020-03 CP-87e CP-200128 0204 F Misalignment of 23.041 with 23.007 and 23.527 16.3.0 2020-03 CP-87e CP-200110 0205 F Procedures for an ETWS/CMAS-capable UE in NG-RAN 16.3.0 2020-03 CP-87e CP-200118 0208 2 B Addition of message identifiers for UEs with no user interface 16.3.0 2020-03 CP-87e CP-200118 0209 1 B Support of a stored language-independent content referenced by a warning message 16.3.0 2020-06 CP-88e CP-201100 0207 2 F Removal of Duplicate Service Operation Details 16.4.0 2020-06 CP-88e CP-201100 0212 F Correction to figure 16.4.0 2020-06 CP-88e CP-201100 0213 F Corrections to references 16.4.0 2020-06 CP-88e CP-201100 0214 1 F Subscription management in PWS-IWF 16.4.0 2020-06 CP-88e CP-201131 0217 1 F Handling of Concurrent Warning Message Indicator 16.4.0 2020-06 CP-88e CP-201115 0218 F Deletion of Editor's note in the clause 9.3.24 Warning-Type for ETWS 16.4.0 2020-09 CP-89e CP-202184 0220 3 F Geo-fencing check for no stored "warning message" matched 17.0.0 2021-06 CP-92e CP-211150 0222 F Geo-fencing check for none of stored "warning message" matched to geo-fencing trigger 17.1.0 2021-06 CP-92e CP-211150 0221 1 C Broadcast Empty Area List for Write-Replace-Warning Request 17.1.0 2021-09 CP-93e CP-212153 0215 3 F Addition of Test Flag 17.2.0 2021-09 CP-93e CP-212140 0224 - F Assign MI values for EU-Alert Level 4 17.2.0 2021-09 CP-93e CP-212124 0225 1 B Adding support for PWS in SNPNs 17.2.0 2021-09 CP-93e CP-212153 0226 - F Correction on PWS 5GS architecture depiction 17.2.0 2022-03 CP-95e CP-220236 0228 1 C UE configuration for warning message reception in SNPNs 17.3.0 2022-06 CP-96e CP-221203 0232 1 F Removal of Editor's note on USIM data file for configuration of warning message reception when the UE accesses an SNPN using the PLMN subscription 17.4.0 2022-06 CP-96e CP-221328 0231 2 F Device based geo-fencing for EU-alert 18.0.0 2022-12 CP-98e CP-223144 0233 2 B CBS Message Identifiers for additional KPAS services 18.1.0 2023-09 CP-101 CP-232195 0237 1 F Additional message Id for KPAS geo-fencing trigger messages 18.2.0 2023-12 CP-102 CP-233190 0239 - F Reference to obsoleted HTTP/2 RFC 18.3.0 2024-03 CP-103 CP-240125 0238 5 F Duplicate detection for PWS messages received over different PLMNs 18.4.0 2024-06 CP-104 CP-241176 0247 - F Message Identifier value range A000hex-AFFFhex in an SNPN that is equivalent to the subscribed SNPN 18.5.0 2024-06 CP-104 CP-241198 0245 1 F Architecture in shared RAN 18.5.0 2024-06 CP-104 CP-241198 0246 1 F Re-introduction of CBC in figure 1 18.5.0 2024-06 CP-104 CP-241199 0241 1 F Completing a reference 18.5.0 2024-09 CP-105 CP-242199 0248 2 F 5G procedure mentions wrong entity 18.6.0 2025-03 CP-107 CP-250179 0249 4 B Introduction of support for PWS over satellite E-UTRAN and satellite NG-RAN 19.0.0 2025-03 CP-107 CP-250179 0258 1 F Adding satellite E-UTRAN and satellite NG-RAN support for PWS 19.0.0
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
1 Scope
|
The present document gives an overview of the tasks undertaken by the Core network protocols of a Mobile Station (MS) when in idle mode, that is, switched on but typically not having a dedicated channel allocated. It also describes the corresponding network functions. The idle mode functions are also performed by a GPRS MS as long as no dedicated channel is allocated to the MS. The conditions when the idle mode functions are performed by an MS in the UTRA RRC connected mode states are specified in 3GPP TS 25.331 [33]. The conditions when the idle mode functions are performed by an MS in the E-UTRAN are specified in 3GPP TS 36.304 [43]. The conditions when the idle mode functions are performed by an MS in the NG-RAN are specified in 3GPP TS 36.304 [43] and 3GPP TS 38.304 [61]. The conditions when the idle mode functions are performed by an MS in the NG-RAN RRC inactive state are specified in 3GPP TS 36.331 [42] and 3GPP TS 38.331 [65].
The present document defines the PLMN selection for a multi mode MS that supports both 3GPP and 3GPP2 systems. The common PLMN selection logic covers also PLMNs that are available in 3GPP2 system, but the present document makes no changes on the cdma2000® signalling towards networks that are available via 3GPP2 system.
The present document gives procedures for using the CSG cells, whenever such use is permitted.
The present document gives procedures for using the CAG cells, when the MS supports CAG.
The present document specifies the SNPN selection.
This 3GPP TS outlines how the requirements of the 22 series Technical Specifications (especially 3GPP TS 22.011 [9]) on idle mode operation shall be implemented. Further details are given in 3GPP TS 24.008 [23].
Clause 2 of this 3GPP TS gives a general description of the idle mode process. Clause 3 outlines the main requirements and technical solutions of those requirements. Clause 4 describes the processes used in idle mode. There is inevitably some overlap between these clauses.
NOTE: cdma2000® is a registered trademark of the Telecommunications Industry Association (TIA-USA).
The present document describes the procedures for control plane solution of steering of roaming in 5GS in annex C.
Annex C is applicable to the MS, the AMF, the UDM and the SOR-AF in the 5GS.
The present document does not consider GERAN Iu mode.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
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. 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] Void.
[2] Void.
[3] Void.
[4] Void.
[5] Void.
[6] Void.
[7] Void
[8] Void.
[9] 3GPP TS 22.011: "Service accessibility".
[10] Void.
[11] Void.
[12] Void.
[13] Void.
[14] Void.
[15] Void.
[16] Void.
[17] Void.
[18] Void.
[19] Void.
[20] Void.
[21] Void.
[22] Void.
[22A] 3GPP TS 23.003: "Numbering, addressing and identification".
[23] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification, Core Network Protocols - Stage 3".
[23A] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3".
[24] 3GPP TS 45.002: "Multiplexing and multiple access on the radio path".
[25] 3GPP TS 45.008: "Radio subsystem link control".
[26] Void.
[27] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
[27A] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".
[28] Void.
[29] Void.
[30] Void.
[31] Void.
[32] 3GPP TS 25.304: "UE Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode".
[33] 3GPP TS 25.331: "RRC Protocol Specification".
[34] 3GPP TS 44.018:"Mobile radio interface layer 3 specification, Radio Resource Control Protocol".
[35] 3GPP TS 43.022: "Functions related to Mobile Station (MS) in idle mode and group receive mode".
[35A] 3GPP TS 43.318: "Generic Access Network (GAN); Stage 2".
[35B] 3GPP TS 44.318: "Generic Access Network (GAN); Mobile GAN interface layer 3 specification; Stage 3".
[36] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[37] Void.
[38] 3GPP TS 21.111: "USIM and IC card requirements".
[39] 3GPP TS 44.060: "General Packet Radio Service (GPRS);Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control/Medium Access Control (RLC/MAC) protocol".
[40] 3GPP TS 31.102: "Characteristics of the USIM Application".
[41] 3GPP TS 31.111: "Universal Subscriber Identity Module (USIM), Application Toolkit (USAT)".
[42] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC); Protocol specification".
[43] 3GPP TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode".
[44] 3GPP2 C.S0016-D v1.0: "Over-the-Air Service Provisioning of Mobile Stations in Spread Spectrum Standards".
[45] 3GPP2 C.S0011-C v2.0: "Recommended Minimum Performance Standards for cdma2000 Spread Spectrum Mobile Stations".
[46] 3GPP2 C.S0033-A v2.0: "Recommended Minimum Performance Standards for cdma2000 High Rate Packet Data Access Terminal".
[47] 3GPP TS 24.285: "Allowed Closed Subscriber Group (CSG) List Management Object (MO)".
[48] Void.
[49] 3GPP TS 22.220: "Service requirements for Home Node B (HNB) and Home eNode B (HeNB)".
[50] 3GPP TS 24.368: "Non-Access Stratum (NAS) configuration Management Object (MO)".
[51] 3GPP TS 24.334: "Proximity-services (ProSe) User Equipment (UE) to Proximity-services (ProSe) Function Protocol aspects; Stage 3".
[52] 3GPP TS 24.333: "Proximity-services (ProSe) Management Objects (MO)".
[53] 3GPP TS 24.105: "Application specific Congestion control for Data Communication (ACDC) Management Object (MO)".
[54] 3GPP TS 36.306: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio access capabilities".
[55] 3GPP TS 43.064: "Overall description of the GPRS Radio Interface; Stage 2".
[56] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description".
[57] 3GPP TS 23.167: "IP Multimedia Subsystem (IMS) emergency sessions".
[58] 3GPP TS 23.401: "GPRS enhancements for E-UTRAN access".
[59] 3GPP TS 24.386: "User Equipment (UE) to V2X control function; protocol aspects; Stage 3".
[60] 3GPP TS 24.385: "V2X services Management Object (MO)".
[61] 3GPP TS 38.304: "NR; User Equipment (UE) procedures in Idle mode and RRC Inactive state".
[62] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[63] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
[64] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
[65] 3GPP TS 38.331: "NR; Radio Resource Control (RRC) protocol specification".
[66] 3GPP TS 33.501: "Security architecture and procedures for 5G System".
[67] 3GPP TS 31.115: "Secured packet structure for (Universal) Subscriber Identity Module (U)SIM Toolkit applications".
[68] 3GPP TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and Functional Description".
[69] 3GPP TS 23.221: "Architectural requirements".
[70] 3GPP TS 23.273: "5G System (5GS) Location Services (LCS)".
[71] 3GPP TS 29.544: "5G System (5GS); Secured Packet Application Function (SP-AF) services; Stage 3".
[72] 3GPP TS 29.571: "5G System (5GS); Common Data Types for Service Based Interfaces; Stage 3".
[73] ETSI TS 102 225: "Smart Cards; Secured packet structure for UICC based applications".
[74] 3GPP TS 22.261: "Service requirements for the 5G system; Stage 1".
[75] 3GPP TS 24.587: "Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3".
[76] ITU-T Recommendation E.212: "The international identification plan for public networks and subscriptions".
[77] 3GPP TS 24.526: "UE policies for 5G System (5GS); Stage 3".
[78] 3GPP TS 29.503: "5G System; Unified Data Management Services; Stage 3".
[79] 3GPP TS 24.588: "Vehicle-to-Everything (V2X) services in 5G System (5GS); User Equipment (UE) policies; Stage 3".
[80] 3GPP TS 24.554: " Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3".
[81] 3GPP TS 24.555: "Proximity-services (ProSe) in 5G System (5GS); User Equipment (UE) policies; Stage 3".
[82] 3GPP TS 29.504: "5G System; Unified Data Repository Services; Stage 3".
[83] 3GPP TS 29.505: "5G System; Usage of the Unified Data Repository services for Subscription Data; Stage 3".
[84] 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[85] 3GPP TS 23.247: "Architectural enhancements for 5G multicast-broadcast services; Stage 2".
[86] 3GPP TS 24.577: "Aircraft-to-Everything (A2X) services in 5G System (5GS) protocol aspects; Stage 3".
[87] 3GPP TS 24.578: "Aircraft-to-Everything (A2X) services in 5G System (5GS); UE policies; Stage 3".
[88] 3GPP TS 29.550: "5G System; Steering of roaming application function services; Stage 3".
[89] 3GPP TS 38.306: "NR; User Equipment (UE) radio access capabilities".
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
1.2 Definitions and abbreviations
|
For the purposes of the present document, the abbreviations defined in 3GPP TR 21.905 [36] apply.
(A/Gb mode only): Indicates this clause applies only to a GSM system which operates in A/Gb mode. For multi system case this is determined by the current serving radio access network.
(Iu mode only): Indicates this clause applies only to UMTS. For multi system case this is determined by the current serving radio access network.
NOTE 1: In accordance with the description of packet services in Iu mode in 3GPPS TS 24.008 [23], the terms 'CS/PS mode of operation' and 'PS mode of operation' are not used in the present document. Instead the terms 'MS operation mode A' and 'MS operation mode C' are used.
(S1 mode only): Indicates this clause applies only to an EPS. For multi system case this is determined by the current serving radio access network.
Acceptable Cell: This is a cell that the MS may camp on to make emergency calls or to access RLOS. It must satisfy criteria which are defined for A/Gb mode in 3GPP TS 43.022 [35], for Iu mode in 3GPP TS 25.304 [32], for S1 mode in 3GPP TS 36.304 [43], and for NR access in N1 mode in 3GPP TS 38.304 [61] and for E-UTRA access in N1 mode in 3GPP TS 36.304 [43]. For an MS in eCall only mode, an acceptable cell must further satisfy the criteria defined in clause 4.4.3.1.1.
Access Technology: The access technology associated with a PLMN or SNPN. The MS uses this information to determine what type(s) of radio carrier to search for when attempting to select a specific PLMN or SNPN The following access technologies are defined: GSM, UTRAN, GSM COMPACT, EC-GSM-IoT, cdma2000 1xRTT, cdma2000 HRPD, E-UTRAN (WB-S1 mode and NB-S1 mode), NG-RAN, satellite NG-RAN and satellite E-UTRAN (WB-S1 mode and NB-S1 mode). A PLMN may support more than one access technology. SNPNs only support NG-RAN.
NOTE 2: Access technology "E-UTRAN" maps to core network type "EPC" and access technology "NG-RAN" maps to core network type "5GCN", see 3GPP TS 24.501 [64].
ACDC: Application specific Congestion control for Data Communication, see 3GPP TS 22.011 [9].
Allowable PLMN: In the case of an MS operating in MS operation mode A or B, this is a PLMN which is not in the list of "forbidden PLMNs" in the MS. In the case of an MS operating in MS operation mode C or an MS not supporting A/Gb mode and not supporting Iu mode, this is a PLMN which is not in the list of "forbidden PLMNs" and not in the list of "forbidden PLMNs for GPRS service" in the MS.
Allowable SNPN: In the case of an MS operating in SNPN access operation mode over 3GPP access and for an SNPN candidate which is not an SNPN selected for localized services in SNPN, this is an SNPN which is not in the list of "permanently forbidden SNPNs" which is, if the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, and is not in the list of "temporarily forbidden SNPNs" which is, if the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription. In the case of an MS operating in SNPN access operation mode over 3GPP access and for an SNPN candidate which is an SNPN selected for localized services in SNPN, this is an SNPN which is not in the list of "permanently forbidden SNPNs for access for localized services in SNPN" which is associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, and is not in the list of "temporarily forbidden SNPNs for access for localized services in SNPN" which is associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription. For onboarding services in SNPN, this is an SNPN which is not in the list of "permanently forbidden SNPNs for onboarding services in SNPN" and is not in the list of "temporarily forbidden SNPNs for onboarding services in SNPN".
Allowable PLMN/access technology combination: For an MS operating in MS operation mode C or an MS not supporting A/Gb mode and not supporting Iu mode, this is an allowable PLMN in any specific access technology. For an MS operating in MS operation mode A or B, this is a PLMN/access technology combination where:
- the PLMN is an allowable PLMN and the specific access technology is supporting non-GPRS services; or
- the PLMN is not in the list of "forbidden PLMNs" and not in the list of "forbidden PLMNs for GPRS service" in the MS and the specific access technology is only supporting GPRS services.
EXAMPLE: E-UTRAN, satellite E-UTRAN, satellite NG-RAN (see 3GPP TS 22.261 [74]) and NG-RAN are access technologies that are only supporting GPRS services.
Available PLMN: For GERAN A/Gb mode see 3GPP TS 43.022 [35]. For UTRAN see 3GPP TS 25.304 [32]. For E-UTRAN see 3GPP TS 36.304 [43]. For satellite E-UTRAN see 3GPP TS 36.304 [43]. For NG-RAN see 3GPP TS 36.304 [43] and 3GPP TS 38.304 [61]. For satellite NG-RAN, see 3GPP TS 38.304 [61]. For cdma2000® 1xRTT and cdma2000® HRPD see 3GPP2 C.S0016 [44].
Available SNPN: For NG-RAN see 3GPP TS 38.304 [61].
Available PLMN/access technology combination: This is an available PLMN in a specific access technology.
CAG-ID authorized based on "Allowed CAG list": A CAG-ID in an "Allowed CAG list", without a time validity information, or with a time validity information with at least one time period matching UE's current time.
Camped on a cell: The MS (ME if there is no SIM) has completed the cell selection/reselection process and has chosen a cell from which it plans to receive all available services. Note that the services may be limited, and that the PLMN or the SNPN may not be aware of the existence of the MS (ME) within the chosen cell.
Country: A country is identified by a single MCC value defined in ITU-T recommendation E.212 [76], with the exception of the following MCC ranges that identify a single country:
- values 310 through 316 (USA);
- values 404 through 406 (India);
- values 440 through 441 (Japan);
- values 460 through 461 (China); and
- values 234 through 235 (United Kingdom).
Permitted CSG list: See 3GPP TS 36.304 [43].
Current serving cell: This is the cell on which the MS is camped.
CTS MS: An MS capable of CTS services is a CTS MS.
Discontinuous coverage: Deployment option for satellite E-UTRAN access, in which shorter periods of satellite E-UTRAN access radio coverage are followed by longer periods of satellite E-UTRAN access coverage gaps. During coverage gaps, the access stratum may be deactivated. For more details see 3GPP TS 23.401 [58] and 3GPP TS 36.304 [43].
EAB: Extended Access Barring, see 3GPP TS 22.011 [9].
Extended Coverage in GSM for Internet of Things (EC-GSM-IoT): Extended coverage in GSM for IoT is a feature which enables extended coverage operation. See 3GPP TS 43.064 [55].
EHPLMN: Any of the PLMN entries contained in the Equivalent HPLMN list.
Equivalent HPLMN list: To allow provision for multiple HPLMN codes, PLMN codes that are present within this list shall replace the HPLMN code derived from the IMSI for PLMN selection purposes. This list is stored on the USIM and is known as the EHPLMN list. The EHPLMN list may also contain the HPLMN code derived from the IMSI. If the HPLMN code derived from the IMSI is not present in the EHPLMN list then the HPLMN code derived from the IMSI shall be treated as a Visited PLMN for PLMN selection purposes.
Generic Access Network (GAN): See 3GPP TS 43.318 [35A].
GAN mode: See 3GPP TS 43.318 [35A].
GPRS MS: An MS capable of GPRS services is a GPRS MS.
MS operation mode: See 3GPP TS 23.060 [27].
High quality signal: The high quality signal limit is used in the PLMN selection procedure. It is defined in the appropriate AS specification: 3GPP TS 43.022 [35] for the GSM radio access technology, 3GPP TS 25.304 [32] for the UMTS radio access technology (FDD or TDD mode), 3GPP TS 36.304 [43] for the E‑UTRAN radio access technology (WB-S1 mode, NB-S1 mode, WB-N1 mode or NB-N1 mode), 3GPP TS 36.304 [43] and 3GPP TS 38.304 [61] for the NG-RAN radio access technology. For 3GPP2 access technologies the high quality signal limit is defined in 3GPP2 C.S0011 [45] for cdma2000® 1xRTT and in 3GPP2 C.S0033 [46] for cdma2000® HRPD. A mobile station attempting to find a cell that supports EC-GSM-IoT (see 3GPP TS 43.064 [55]) does not use high quality signal limit in the PLMN selection procedure, i.e. for the purpose of PLMN selection, when attempting to find a cell that supports EC-GSM-IoT, any found cell supporting EC-GSM-IoT is considered to be received with high quality signal. A UE attempting to find a cell that supports enhanced coverage when operating in any WB-S1 or WB-N1 enhanced coverage mode does not use high quality signal limit in the PLMN selection procedure, i.e. for the purpose of PLMN selection, when attempting to find a cell that supports enhanced coverage, any found cell supporting enhanced coverage and satisfying the coverage specific quality signal limit defined for CE mode (see 3GPP TS 36.304 [43]) is considered to be received with high quality signal.
Home PLMN: This is a PLMN where the MCC and MNC of the PLMN identity match the MCC and MNC of the IMSI. Matching criteria are defined in Annex A.
In A/Gb mode: Indicates this clause applies only to a GSM system which operates in A/Gb mode. For multi system case this is determined by the current serving radio access network.
In Iu mode: Indicates this clause applies only to UMTS. For multi system case this is determined by the current serving radio access network.
In N1 mode: Indicates this clause applies only to an 5GS. For multi system case this is determined by the current serving radio access network.
In NB-N1 mode: Indicates this paragraph applies only to a system which operates in NB-N1 mode. For a multi-access system this case applies if the current serving radio access network provides access to 5G network services via E-UTRA connected to 5GCN by NB-IoT (see 3GPP TS 36.300 [56], 3GPP TS 36.331 [42], 3GPP TS 36.306 [54]).
In WB-N1 mode: Indicates this paragraph applies only to a system which operates in WB-N1 mode. For a multi-access system this case applies if the system operates in N1 mode with E-UTRA connected to 5GCN, but not in NB-N1 mode.
In S1 mode: Indicates this clause applies only to an EPS. The S1 mode includes WB-S1 mode and NB-S1 mode. For multi system case this is determined by the current serving radio access network.
In NB-S1 mode: Indicates this paragraph applies only to a system which operates in NB-S1 mode. For a multi-access system this case applies if the current serving radio access network provides access to network services via E-UTRA by NB-IoT (see 3GPP TS 36.300 [56], 3GPP TS 36.331 [22], 3GPP TS 36.306 [54]).
In WB-S1 mode: Indicates this paragraph applies only to a system which operates in WB-S1 mode. For a multi-access system this case applies if the system operates in S1 mode, but not in NB-S1 mode.
Limited Service State: See clause 3.5.
Localised Service Area (LSA): A localised service area consists of a cell or a number of cells. The cells constituting a LSA may not necessarily provide contiguous coverage.
Localized services in NPN: Localized services in NPN are services, which are provided by an NPN at specific or limited area, are bounded in time, or both.
Localized services in SNPN: Localized services in SNPN are localized services in NPN, which are provided by an SNPN at specific or limited area, are bounded in time, or both.
Location Registration (LR): An MS which is IMSI attached to non-GPRS services only performs location registration by the location updating procedure. A GPRS MS which is IMSI attached to GPRS services or to GPRS and non-GPRS services performs location registration by the routing area update procedure only when in a network of network operation mode I. Both location updating and routing area update procedures are performed independently by the GPRS MS when it is IMSI attached to GPRS and non-GPRS services in a network of network operation mode II (see 3GPP TS 23.060 [27]). An MS which is attached via the E-UTRAN performs location registration by the tracking area update procedure. An MS which is registered via the NG-RAN performs location registration by the registration procedure for mobility and periodic registration update (see 3GPP TS 24.501 [64]).
MINT: Minimization of service interruption (see 3GPP TS 22.261 [71]).
MS: Mobile Station. The present document makes no distinction between MS and UE.
N1 mode capability: Capability of the UE associated with an N1 NAS signalling connection between the UE and network. The present document refers to the N1 mode capability over 3GPP access only (see 3GPP TS 24.501 [64]).
NarrowBand Internet of Things (NB-IoT): NB-IoT is a non-backward compatible variant of E-UTRAN supporting a reduced set of functionality. NB-IoT allows access to EPC or 5GCN network services via E-UTRA with a channel bandwidth limited to 180 kHz (see 3GPP TS 36.300 [20], 3GPP TS 36.331 [42], 3GPP TS 36.306 [44]).
Network Type: The network type associated with HPLMN or a PLMN on the PLMN selector (see 3GPP TS 31.102 [40]). The MS uses this information to determine what type of radio carrier to search for when attempting to select a specific PLMN. A PLMN may support more than one network type.
Onboarding services in SNPN: Onboarding services in SNPN allow an MS to access an SNPN indicating that onboarding is allowed, using default UE credentials for primary authentication in order for the MS to be configured with one or more entries of the "list of subscriber data".
NOTE 3: When the MS is registered for onboarding services in SNPN, services other than the onboarding services in SNPN are not available. When the MS is not registered for onboarding services in SNPN, onboarding services in SNPN are not available.
UE determined PLMN with disaster condition: A PLMN to which a disaster condition applies, determined as described in clause 4.4.3.1.1.
Registered PLMN (RPLMN): This is the PLMN on which certain LR outcomes have occurred (see table 1). In a shared network the RPLMN is the PLMN defined by the PLMN identity of the CN operator that has accepted the LR.
Registered SNPN (RSNPN): This is the SNPN on which certain LR outcomes have occurred. In a shared network the RSNPN is the SNPN defined by the SNPN identity of the CN operator that has accepted the LR.
Registration: This is the process of camping on a cell of the PLMN or the SNPN and doing any necessary LRs.
Registration Area: A registration area is an area in which mobile stations may roam without a need to perform location registration. The registration area corresponds to location area (LA) for performing location updating procedure, to routing area for performing the GPRS attach or routing area update procedures, and to a list of tracking areas (TAs) for performing the EPS attach, tracking area update, or 5GS registration procedure.
The PLMN to which a cell belongs (PLMN identity):
- for GERAN, in the system information (MCC + MNC part of LAI) broadcast as specified in 3GPP TS 44.018 [34];
- for UTRA, see the broadcast information as specified in 3GPP TS 25.331 [33];
- for E-UTRA, see the broadcast information as specified in 3GPP TS 36.331 [42]; and
- for NR, see the broadcast information as specified in 3GPP TS 38.331 [65].
The SNPN to which a cell belongs (SNPN identity):
- for NR, see the broadcast information as specified in 3GPP TS 38.331 [65].
In a shared network, a cell belongs to all PLMNs given in the system information broadcasted as specified in 3GPP TS 44.018 [34] for GERAN, in 3GPP TS 25.331 [33] for UTRAN, and in 3GPP TS 36.331 [42] for E-UTRAN, and a cell belongs to all PLMNs, all SNPNs, or all PLMNs and all SNPNs, given in the system information broadcasted as specified in 3GPP TS 36.331 [42] for E-UTRA connected to 5GCN, and in 3GPP TS 38.331 [65] for NR.
Secured packet: In this specification, a secured packet contains one or more of the following:
- list of preferred PLMN/access technology combinations;
- SOR-CMCI; and
- SOR-SENSE
encapsulated with a security mechanism as described in 3GPP TS 31.115 [67].
Selected PLMN: This is the PLMN that has been selected according to clause 3.1, either manually or automatically.
Selected SNPN: This is the SNPN that has been selected according to clause 3.9, either manually or automatically.
Shared MCC: MCC assigned by ITU-T as shared MCC according to ITU-T E.212 [76], except within this specification for PLMN selection purposes the MCC of value 999 is not considered a shared MCC.
Shared Network: An MS considers a cell to be part of a shared network, when multiple PLMN identities are received as specified in 3GPP TS 44.018 [34] for GERAN, in 3GPP TS 25.331 [33] for UTRAN, and in 3GPP TS 36.331 [42] for E-UTRAN, and when multiple PLMN identities, multiple SNPN identities or one or more PLMN identities and one or more SNPN identities are received as specified in 3GPP TS 36.331 [42] for E-UTRA connected to 5GCN, and in 3GPP TS 38.331 [65] for NR.
SIM: Subscriber Identity Module (see 3GPP TS 21.111 [38]). The present document makes no distinction between SIM and USIM.
SNPN identity: a PLMN ID and an NID combination.
SoLSA exclusive access: Cells on which normal camping is allowed only for MS with Localised Service Area (LSA) subscription.
Steering of Roaming (SOR): A technique whereby a roaming UE is encouraged to roam to a preferred roamed-to-network indicated by the HPLMN.
Steering of Roaming application function (SOR-AF): An application function that can provide UDM with one of the following:
a) one or more of the following:
- list of preferred PLMN/access technology combinations;
- SOR-CMCI, together with the "Store SOR-CMCI in ME" indicator if applicable;
- SOR-SNPN-SI; and
- SOR-SNPN-SI-LS;
b) a secured packet, together with the indicator, if applicable, that "the list of preferred PLMN/access technology combinations is not included in the secured packet"; or
c) neither of a) or b),
generated dynamically based on operator specific data analytics solutions.
Steering of roaming connected mode control information (SOR-CMCI): HPLMN information to control the timing for a UE in connected mode to move to idle mode in order to perform steering of roaming.
Steering of roaming operator controlled signal threshold per access technology information (SOR-SENSE): Home operator’s provision of "Operator controlled signal threshold per access technology" for signal level enhance network selection (SENSE). This information is the EFOCST file provided in the secured packet by network.
Steering of Roaming information: This consists of the following HPLMN or subscribed SNPN protected information (see 3GPP TS 33.501 [66]):
a) the following indicators, of whether:
- the UDM requests an acknowledgement from the UE for successful reception of the steering of roaming information.
- the UDM requests the UE to store the SOR-CMCI in the ME, which is provided along with the SOR-CMCI in plain text; and
b) one of the following:
1) one or more of the following:
- list of preferred PLMN/access technology combinations with an indication that it is included;
- SOR-CMCI;
- SOR-SNPN-SI; and
- SOR-SNPN-SI-LS;
2) a secured packet with an indication that it is included;
3) the HPLMN indication that 'no change of the "Operator Controlled PLMN Selector with Access Technology" list stored in the UE is needed and thus no list of preferred PLMN/access technology combinations is provided'; or
4) the subscribed SNPN or HPLMN indication that 'no change of the SOR-SNPN-SI stored in the UE is needed and thus no SOR-SNPN-SI is provided'.
Steering of roaming SNPN selection information (SOR-SNPN-SI): Provisioning information for SNPN selection consisting of:
a) the credentials holder controlled prioritized list of preferred SNPNs;
b) the credentials holder controlled prioritized list of GINs; or
c) both of the above.
Steering of roaming SNPN selection information for localized services in SNPN (SOR-SNPN-SI-LS): Provisioning information for SNPN selection by an MS supporting access to an SNPN providing access for localized services in SNPN consisting of:
a) a "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN", where each entry contains:
1) an SNPN identity;
2) a validity information consisting of time validity information and optionally, location validity information; and
3) optionally, location assistance information;
b) a "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN", where each entry contains:
1) a GIN;
2) a validity information consisting of time validity information and optionally, location validity information; and
3) optionally, location assistance information; or
c) both of the above.
Subscribed SNPN: An SNPN for which the UE has a subscription.
Suitable Cell: This is a cell on which an MS may camp. It must satisfy criteria which are defined for GERAN A/Gb mode in 3GPP TS 43.022 [35], for UTRAN in 3GPP TS 25.304 [32], for E-UTRAN in 3GPP TS 36.304 [43] and for NG-RAN see 3GPP TS 36.304 [43] and 3GPP TS 38.304 [61]. For 3GPP2 access technologies the criteria are defined in 3GPP2 C.S0011 [45] for cdma2000® 1xRTT and in 3GPP2 C.S0033 [46] for cdma2000® HRPD. For an MS in eCall only mode, a suitable cell must further satisfy the criteria defined in clause 4.4.3.1.1.
Visited PLMN: This is a PLMN different from the HPLMN (if the EHPLMN list is not present or is empty) or different from an EHPLMN (if the EHPLMN list is present).
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.167 [57] apply:
eCall over IMS
EPC
E-UTRAN
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.401 [58] apply:
eCall only mode
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.221 [69] apply:
Restricted local operator services (RLOS)
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.501 [62] apply:
Closed Access Group (CAG)
Credentials holder
Group ID for Network Selection (GIN)
Network identifier (NID)
NG-RAN
Stand-alone Non-Public Network (SNPN)
For the purposes of the present document, the following terms and definitions given in 3GPP TS 24.501 [64] apply:
5GCN
CAG cell
Emergency PDU session
Initial registration for disaster roaming services
Initial registration for emergency services
Initial registration for onboarding services in SNPN
Mobility registration for disaster roaming services
Non-CAG cell
NSSAI
Registered for disaster roaming services
Registered for emergency services
Registered for onboarding services in SNPN
SNPN access operation mode
For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.261 [74] apply:
Disaster condition
Disaster roaming
For the purposes of the present document, the following terms and definitions given in 3GPP TS 33.501 [66] apply:
Default UE credentials for primary authentication
For the purposes of the present document, the following terms and definitions given in 3GPP TS 24.229 [84] apply:
IMS registration related signalling
For the purposes of the present document, the following terms and definitions given in 3GPP TS 38.306 [89] apply:
RedCap UE
eRedCap UE
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
2 General description of idle mode
|
When an MS is switched on, it attempts to make contact with a public land mobile network (PLMN) or stand-alone non-public network (SNPN). The particular PLMN or SNPN to be contacted may be selected either automatically or manually.
The MS looks for a suitable cell of the chosen PLMN or SNPN and chooses that cell to provide available services, and tunes to its control channel. This choosing is known as "camping on the cell". The MS will then register its presence in the registration area of the chosen cell if necessary, by means of a location registration (LR), GPRS attach, IMSI attach or registration procedure.
If the MS loses coverage of a cell, or find a more suitable cell, it reselects onto the most suitable cell of the selected PLMN or SNPN and camps on that cell. If the new cell is in a different registration area, an LR request is performed.
If the MS loses coverage of a PLMN or SNPN, either a new PLMN or SNPN is selected automatically, or an indication of which PLMNs or SNPNs are available is given to the user, so that a manual selection can be made.
Registration is not performed by MSs only capable of services that need no registration.
The purpose of camping on a cell in idle mode is fourfold:
a) It enables the MS to receive system information from the PLMN or SNPN.
b) If the MS wishes to initiate a call, it can do this by initially accessing the network on the control channel of the cell on which it is camped.
c) If the PLMN or SNPN receives a call for the MS, it knows (in most cases) the registration area of the cell in which the MS is camped. It can then send a "paging" message for the MS on control channels of all the cells in the registration area. The MS will then receive the paging message because it is tuned to the control channel of a cell in that registration area, and the MS can respond on that control channel.
d) It enables the MS to receive cell broadcast messages.
If the MS is unable to find a suitable cell to camp on, or the SIM is not inserted, or there is no valid entry in "list of subscriber data" in case the MS is operating in SNPN access operation mode over 3GPP access, or if it receives certain responses to an LR request (e.g., "illegal MS"), it attempts to camp on a cell irrespective of the PLMN identity or the SNPN identity, and enters a "limited service" state in which it can only attempt to make emergency calls or to access RLOS. An MS operating in NB-S1 mode, never attempts to make emergency calls or to access RLOS. An MS operating in N1 mode never attempts to access RLOS.
If the MS is in eCall only mode, it attempts to camp on a suitable cell and enters an "eCall inactive" state in which it can only attempt an eCall over IMS, or a call to a non-emergency MSISDN or URI for test or terminal reconfiguration services as specified in 3GPP TS 31.102 [40].
If the MS is in eCall only mode and is unable to find a suitable cell to camp on, it attempts to camp on an acceptable cell in limited service state, and enters an "eCall inactive" state in which it can only attempt an eCall over IMS.
While in eCall inactive state, the MS does not perform LR with the PLMN of the cell on which the MS is camped.
In A/Gb mode, if the CTS MS is in CTS mode only or in automatic mode with CTS preferred, it will start by attempting to find a CTS fixed part on which it is enrolled.
The idle mode tasks can be subdivided into the following processes:
- PLMN selection;
- SNPN selection (N1 mode only);
- CSG selection (Iu mode and S1 mode only);
- Cell selection and reselection;
- Location registration;
- CTS fixed part selection (A/Gb mode only); and
- CAG selection (N1 mode only).
In A/Gb mode, to make this initial CTS fixed part selection, the MS shall be enrolled on at least one fixed part.
Except for SNPN selection, the relationship between these processes is illustrated in figure 1 in clause 5. The states and state transitions within each process are shown in figure 2a, figure 2b, and figure 3 in clause 5.
In the present document, EMM-IDLE mode with suspend indication (see 3GPP TS 24.301 [23A]) and 5GMM-IDLE mode with suspend indication (see 3GPP TS 24.501 [64]) shall be considered the same as idle mode.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
3 Requirements and technical solutions
| |
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
3.0 General
|
The following clauses list the main requirements of idle mode operation and give an outline of the technical solution.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
3.1 PLMN selection and roaming
|
The MS normally operates on its home PLMN (HPLMN) or equivalent home PLMN (EHPLMN). However, a visited PLMN (VPLMN) may be selected, e.g., if the MS loses coverage. There are two modes for PLMN selection:
i) Automatic mode ‑ This mode utilizes a list of PLMN/access technology combinations in priority order. The highest priority PLMN/access technology combination which is available and allowable is selected.
ii) Manual mode ‑ Here the MS indicates to the user which PLMNs are available. Only when the user makes a manual selection does the MS try to obtain normal service on the VPLMN.
To prevent repeated attempts to have roaming service on a not allowed area (i.e. LA or TA), when the MS is informed that an area is forbidden, the LA or TA is added to a list of "forbidden location areas for roaming" or "forbidden tracking areas for roaming" respectively which is stored in the MS. These lists, if existing, are deleted when the MS is switched off or when the SIM is removed, and periodically (with period in the range 12 to 24 hours). LA area restrictions are always valid for complete location areas independent of possible subdivision into GPRS routing areas. The structure of the routing area identifier (see 3GPP TS 23.003 [22A]) supports area restriction on LA basis.
To prevent repeated attempts to obtain service on a PLMN through satellite NG-RAN or satellite E-UTRAN access technology, when the MS receives an integrity protected reject message with cause value #78 "PLMNs not allowed to operate at the present UE location" from a satellite NG-RAN cell or a satellite E-UTRAN cell, the MS maintains a list of "PLMNs not allowed to operate at the present UE location" in which it stores the PLMN ID of the rejecting PLMN, the current geographical location, if known by the MS. A timer is started when the PLMN ID of the rejecting PLMN is added to the list of "PLMNs not allowed to operate at the present UE location". If the geographical location exists, a MS implementation specific distance value needs to be stored. An entry in the list is deleted if the timer associated to the entry expires or the MS successfully registers to the PLMN stored in the entry. An entry in the list may be deleted if the current UE location is known, a geographical location is stored for the entry of this PLMN, and the distance to the current UE location is larger than a UE implementation specific value. For details see 3GPP TS 24.501 [64] and 3GPP TS 24.301 [23A].
NOTE 1: The list of "PLMNs not allowed to operate at the present UE location" is provided to the AS, see 3GPP TS 38.304 [61].
In automatic PLMN selection mode, if the MS detects a PLMN in satellite NG-RAN access technology which is part of the list of "PLMNs not allowed to operate at the present UE location" the MS shall consider the PLMN as PLMN selection candidate for satellite NG-RAN access technology only if the current MS location is known, a geographical location is stored for the entry of this PLMN, and the distance to the current MS location is larger than a MS implementation specific value.
This does not prevent selection of such a PLMN if it is available in another access technology.
A timer is started when the PLMN ID of the rejecting PLMN is added to the list of "PLMNs not allowed to operate at the present UE location".
In automatic PLMN selection mode, if the MS detects a PLMN in satellite E-UTRAN access technology which is part of the list of "PLMNs not allowed to operate at the present UE location" the MS shall consider the PLMN as PLMN selection candidate for satellite E-UTRAN access technology only if the current MS location is known, a geographical location is stored for the entry of this PLMN, and the distance to the current UE location is larger than a UE implementation specific value.
This does not prevent selection of such a PLMN if it is available in another access technology.
If a message with cause value #15 (see 3GPP TS 24.008 [23], 3GPP TS 24.301 [23A] and 3GPP TS 24.501 [64]) is received by an MS, then the MS shall take the following actions depending on the mode in which the message was received:
A/Gb mode or Iu mode:
The location area is added to the list of "forbidden location areas for roaming" which is stored in the MS. The MS shall then search for a suitable cell in the same PLMN but belonging to an LA or TA which is not in the "forbidden location areas for roaming" or "forbidden tracking areas for roaming" list respectively.
S1-mode:
The tracking area is added to the list of "forbidden tracking areas for roaming" which is stored in the MS. The MS shall then search for a suitable cell in the same PLMN but belonging to a TA or LA which is not in the "forbidden tracking areas for roaming" or "forbidden location areas for roaming" list respectively
N1-mode:
The tracking area is added to the list of "5GS forbidden tracking areas for roaming" which is stored in the MS. The MS shall then search for a suitable cell in the same PLMN but belonging to a tracking area which is not in the "5GS forbidden tracking areas for roaming" list.
In manual or automatic mode, a VPLMN is added to a list of "forbidden PLMNs" in the SIM if a message with cause value "PLMN not allowed" or "Requested service option not authorized in this PLMN" or "Serving network not authorized" or "IAB-node operation not authorized" is received by an MS in response to an LR request from that VPLMN and:
- the MS is configured to use timer T3245 as defined in 3GPP TS 24.008 [23], 3GPP TS 24.301 [23A], and 3GPP TS 24.501 [64];
- the MS is not configured to use timer T3245 and the message is integrity-protected;
- the MS is not configured to use timer T3245, the message is not integrity-protected and the MS does not maintain a list of PLMN-specific attempt counters; or
- the MS is not configured to use timer T3245, the message is not integrity-protected, the MS maintains a list of PLMN-specific attempt counters and the value of the PLMN-specific attempt counter for that VPLMN is equal to the MS implementation specific maximum value as defined in 3GPP TS 24.008 [23], 3GPP TS 24.301 [23A] and 3GPP TS 24.501 [64].
If:
- after a subsequent manual selection of that PLMN, there is a successful LR not for disaster roaming services, then the PLMN is removed from the "forbidden PLMNs" list;
- the MS is configured to use timer T3245 and the timer T3245 expires, then the PLMN is removed from the "forbidden PLMNs" list ; or
- the MS is not configured to use timer T3245 and:
1) the MS maintains a list of PLMN-specific attempt counters, the value of the PLMN-specific attempt counter for that PLMN is greater than zero and less than the MS implementation specific maximum value, and timer T3247 expires, then the PLMN is removed from the "forbidden PLMNs" list stored in memory as defined in 3GPP TS 24.301 [23A] and 3GPP TS 24.501 [64]; or
2) the MS does not maintain a list of PLMN-specific attempt counters, the PLMN is stored in the "forbidden PLMNs" list in the SIM, and the timer T3247 expires, then the PLMN is removed from the "forbidden PLMNs" list in the SIM as defined in 3GPP TS 24.301 [23A].
This list is retained when the MS is switched off or the SIM is removed. The HPLMN (if the EHPLMN list is not present or is empty) or an EHPLMN (if the EHPLMN list is present) shall not be stored on the list of "forbidden PLMNs".
In A/Gb mode, an ME not supporting SoLSA may consider a cell with the escape PLMN code (see 3GPP TS 23.073) to be a part of a PLMN belonging to the list of "forbidden PLMNs".
Optionally the ME may store in its memory an extension of the "forbidden PLMNs" list. The contents of the extension of the list shall be deleted when the MS is switched off or the SIM is removed.
A VPLMN may be stored in the extension of the "forbidden PLMNs" list if a message with cause value "PLMN not allowed" or "Requested service option not authorized in this PLMN" or "Serving network not authorized" or "IAB-node operation not authorized" is received by an MS in response to an LR request from that VPLMN, and the following is valid:
- the MS is not configured to use timer T3245, the message is not integrity-protected, the MS maintains a list of PLMN-specific attempt counters and the value of the PLMN-specific attempt counter for that VPLMN is less than an MS implementation specific maximum value as defined in 3GPP TS 24.008 [23], 3GPP TS 24.301 [23A] and 3GPP TS 24.501 [64].
In manual or automatic mode, if a message with cause value "GPRS services not allowed in this PLMN" or "EPS services not allowed in this PLMN" is received by an MS in response to an GPRS attach, routing area update, EPS attach or tracking area update request or received in a network initiated GPRS detach or EPS detach request (see 3GPP TS 24.008 [23] and 3GPP TS 24.301 [23A]) from a VPLMN, that VPLMN is added to a list of "forbidden PLMNs for GPRS service" which is stored in the MS. This list is deleted when the MS is switched off or when the SIM is removed. A PLMN is removed from the list of "forbidden PLMNs for GPRS service" if:
- after a subsequent manual selection of that PLMN, there is a successful GPRS attach, routing area update, EPS attach, tracking area update or registration procedure (see 3GPP TS 24.501 [64]);
- the MS is configured to use timer T3245 and timer T3245 expires; or
- the MS is not configured to use timer T3245, the MS maintains a list of PLMN-specific PS-attempt counters as specified in 3GPP TS 24.008 [23] and 3GPP TS 24.301 [23A], the value of the PLMN-specific PS-attempt counter for that PLMN has a value greater than zero and less than the MS implementation-specific maximum value as defined in clause 5.3.7b in 3GPP TS 24.301 [23A], and T3247 expires.
The maximum number of possible entries in this list is implementation dependant, but must be at least one entry. The HPLMN (if the EHPLMN list is not present or is empty) or an EHPLMN (if the EHPLMN list is present) shall not be stored on the list of "forbidden PLMNs for GPRS service".
An MS that is:
- attaching or attached for emergency bearer services or for access to RLOS; or
- registering or registered for emergency services;
may access PLMNs in the list of "forbidden PLMNs" or the list of "forbidden PLMNs for GPRS service". The MS shall not remove any entry from the list of "forbidden PLMNs" or the list of "forbidden PLMNs for GPRS service" as a result of such accesses.
An MS that is registered for disaster roaming services, may access PLMNs in the list of "forbidden PLMNs" or the list of "forbidden PLMNs for GPRS service" following the criteria as specified in clause 4.4.3.1.1 and shall not remove any entry from the list of "forbidden PLMNs" or the list of "forbidden PLMNs for GPRS service" as a result of such accesses.
A UE capable of S101 mode maintains a list "forbidden PLMNs for attach in S101 mode"; the properties and handling in NAS signalling is defined in clause 5.3.3 of 3GPP TS 24.301 [23A].
If the MS is in GAN mode and a "Location not allowed" message is received (see 3GPP TS 44.318 [35B]), then the MS may attempt to select another PLMN so that further GAN registrations may again be attempted. The selection of the PLMN either automatically or manually is implementation dependent.
If an MS that has disabled its E-UTRA capability re-enables it when PLMN selection is performed, then the MS of which usage setting is "voice centric":
- should, for duration of timer TD, memorize the PLMNs where E-UTRA capability was disabled as PLMNs where voice service was not possible in E-UTRAN. The number of PLMNs where voice service was not possible in E-UTRAN that the MS can store is implementation specific, but it shall be at least one. The value of timer TD is MS implementation specific, but shall not exceed the maximum possible value of background scanning timer T as specified in clause 4.4.3.3.1.
- in automatic PLMN selection, shall not consider PLMNs where voice service was not possible in E-UTRAN as PLMN selection candidates for E-UTRA access technology, unless no other PLMN is available. This does not prevent selection of such a PLMN if it is available in another RAT; and
- shall delete stored information on PLMNs where voice service was not possible in E-UTRAN when the MS is switched off, the USIM is removed, timer TD expires, the MS is camping on an E-UTRAN cell of PLMN where the E-UTRA capability was disabled and the upper layer provides indication that the UE is available for voice services in the IMS or MS voice domain configuration changes so that E-UTRA capability disabling is no longer necessary.
The MS may support "E-UTRA Disabling for EMM cause #15" as specified in 3GPP TS 24.301 [23A]. If the MS supports "E-UTRA Disabling for EMM cause #15" and the "E-UTRA Disabling Allowed for EMM cause #15" parameter as specified in 3GPP TS 24.368 [50] or 3GPP TS 31.102 [40] is present and set to enabled:
- the MS shall maintain a list of "PLMNs with E-UTRAN not allowed";
- when the MS disables its E-UTRA capability on a PLMN due to E-UTRAN not allowed, it shall add the PLMN to the "PLMNs with E-UTRAN not allowed" list, and start timer TE if timer TE is not already running;
- the number of PLMNs that the MS can store in the "PLMNs with E-UTRAN not allowed" list is implementation specific, but it shall be at least one;
- the value of timer TE is MS implementation specific, but it shall not exceed the maximum possible value of background scanning timer T (8 hours or 240 hours for MSs supporting EC-GSM-IoT, Category M1 or Category NB1 as defined in 3GPP TS 36.306 [54])) as specified in clause 4.4.3.3.1;
- in automatic PLMN selection the MS shall not consider PLMNs included in the "PLMNs with E-UTRAN not allowed" list as PLMN selection candidates for E-UTRAN access technology, unless no other PLMN is available. This does not prevent selection of such a PLMN if it is available in another RAT; and
- the MS shall delete stored information in the "PLMNs with E-UTRAN not allowed" list when the MS is switched off, the USIM is removed or timer TE expires.
The MS may support "Satellite Disabling Allowed for 5GMM cause #15" as specified in 3GPP TS 24.501 [64]. If the MS supports "Satellite Disabling Allowed for 5GMM cause #15" and the "Satellite Disabling Allowed for 5GMM cause #15" parameter as specified in 3GPP TS 24.368 [50] or 3GPP TS 31.102 [40] is present and set to enabled:
- the MS shall maintain a list of "PLMNs with satellite NG-RAN not allowed";
- when the MS disables its satellite NG-RAN capability on a PLMN due to Satellite NG-RAN not allowed in PLMN, it shall add the PLMN to the "PLMNs with satellite NG-RAN not allowed" list, and start timer TS if timer TS is not already running;
- the number of PLMNs that the MS can store in the "PLMNs with satellite NG-RAN not allowed" list is implementation specific, but it shall be at least one;
- the value of timer TS is MS implementation specific, but it shall not exceed the maximum possible value of 24 hours;
- in automatic PLMN selection the MS shall not consider PLMNs included in the "PLMNs with satellite NG-RAN not allowed" list as PLMN selection candidates for satellite NG-RAN access technology, unless no other PLMN is available. This does not prevent selection of such a PLMN if it is available in another access technology; and
- the MS shall delete stored information in the "PLMNs with satellite NG-RAN not allowed" list when the MS is switched off, the USIM is removed or timer TS expires.
NOTE 1a: The expiry of timer TS does not cause the removal of the PLMNs from the list of PLMNs where N1 mode is not allowed for 3GPP access or from the list of PLMNs where voice service was not possible in N1 mode, if any.
The MS may support "Satellite Disabling Allowed for EMM cause #15" as specified in 3GPP TS 24.301 [23A]. If the MS supports "Satellite Disabling Allowed for EMM cause #15" and the "Satellite Disabling Allowed for EMM cause #15" parameter as specified in 3GPP TS 24.368 [50] or 3GPP TS 31.102 [40] is present and set to enabled:
- the MS shall maintain a list of "PLMNs with satellite E-UTRAN not allowed";
- when the MS disables its satellite E-UTRAN capability on a PLMN due to Satellite E-UTRAN not allowed in PLMN, it shall add the PLMN to the "PLMNs with satellite E-UTRAN not allowed" list, and start timer TL if timer TL is not already running;
- the number of PLMNs that the MS can store in the "PLMNs with satellite E-UTRAN not allowed" list is implementation specific, but it shall be at least one;
- the value of timer TL is MS implementation specific, but it shall not exceed the maximum possible value of 24 hours;
- in automatic PLMN selection the MS shall not consider PLMNs included in the "PLMNs with satellite E-UTRAN not allowed" list as PLMN selection candidates for satellite E-UTRAN access technology, unless no other PLMN is available. This does not prevent selection of such a PLMN if it is available in another access technology; and
- the MS shall delete stored information in the "PLMNs with satellite E-UTRAN not allowed" list when the MS is switched off, the USIM is removed or timer TL expires.
The MS should maintain a list of PLMNs where the N1 mode capability was disabled because IMS voice was not available and the MS's usage setting was "voice centric" as PLMNs where voice service was not possible in N1 mode. When the MS disables its N1 mode capability because IMS voice was not available and the MS's usage setting was "voice centric":
- the MS should add the identity of the PLMN to the list of PLMNs where voice service was not possible in N1 mode and should start timer TF if timer TF is not already running. The number of PLMNs that the MS can store where voice services is not possible is implementation specific, but it shall be at least one. The value of timer TF is MS implementation specific, but shall not exceed the maximum possible value of background scanning timer T as specified in clause 4.4.3.3.1;
- in automatic PLMN selection the MS shall not consider PLMNs where voice service was not possible in N1 mode as PLMN selection candidates for NG-RAN access technology, unless no other PLMN is available. This does not prevent selection of such a PLMN if it is available in another RAT; and
- the MS shall delete stored information on PLMNs where voice service was not possible in N1 mode when the MS is switched off, the USIM is removed, timer TF expires, the MS is camping on an NG-RAN cell of PLMN where the N1 mode capability was disabled and the upper layer provides indication that the UE is available for voice services in the IMS or the MS's usage setting changes so that N1 mode capability disabling is no longer necessary.
The MS should maintain a list of PLMNs where the satellite NG-RAN capability was disabled because IMS voice was not available over satellite NG-RAN and the MS's usage setting was "voice centric" as PLMNs where voice service was not possible over satellite NG-RAN in N1 mode. When the MS disables its satellite NG-RAN capability because IMS voice was not available over satellite NG-RAN and the MS's usage setting was "voice centric":
- the MS should add the identity of the PLMN to the list of PLMNs where voice service was not possible over satellite NG-RAN in N1 mode and should start timer TW if timer TW is not already running. The number of PLMNs that the MS can store where voice services is not possible over satellite NG-RAN is implementation specific, but it shall be at least one. The value of timer TW is MS implementation specific;
- in automatic PLMN selection the MS shall not consider PLMNs where voice service was not possible over satellite NG-RAN in N1 mode as PLMN selection candidates for satellite NG-RAN access technology, unless no other PLMN is available. This does not prevent selection of such a PLMN if it is available in another access technology; and
- the MS shall delete stored information on PLMNs where voice service was not possible over satellite NG-RAN in N1 mode when the MS is switched off, the USIM is removed, timer TW expires, the MS is camping on a satellite NG-RAN cell of PLMN where the satellite NG-RAN capability was disabled and the upper layer provides indication that the UE is available for voice services in the IMS or the MS's usage setting changes so that satellite NG-RAN capability disabling is no longer necessary.
The MS should maintain a list of PLMNs where the N1 mode capability was disabled due to receipt of a reject from the network with 5GMM cause #27 "N1 mode not allowed", as PLMNs where N1 mode is not allowed for 3GPP access. When the MS disables its N1 mode capability due to receipt of a reject from the network with 5GMM cause #27 "N1 mode not allowed":
- the MS should add the identity of the PLMN to the list of PLMNs where N1 mode is not allowed for 3GPP access and should start timer TG if timer TG is not already running. The number of PLMNs that the MS can store where N1 mode is not allowed for 3GPP access is implementation specific, but it shall be at least one. The value of timer TG is MS implementation specific, but shall not exceed the maximum possible value of background scanning timer T as specified in clause 4.4.3.3.1;
- in automatic PLMN selection the MS shall not consider PLMNs where N1 mode is not allowed for 3GPP access as PLMN selection candidates for NG-RAN access technology, unless no other PLMN is available. This does not prevent selection of such a PLMN if it is available in another RAT;
- if the MS is not configured to use timer T3245, the MS maintains a list of PLMN-specific N1 mode attempt counters for 3GPP access as specified in 3GPP TS 24.501 [64] and T3247 expires, then the MS removes for each PLMN-specific N1 mode attempt counter for 3GPP access that has a value greater than zero and less than the MS implementation-specific maximum value the respective PLMN from the list of PLMNs where N1 mode is not allowed for 3GPP access, as specified in clause 5.3.20.2 in 3GPP TS 24.501 [64]; and
- the MS shall delete stored information on PLMNs where N1 mode is not allowed for 3GPP access when the MS is switched off, the USIM is removed or timer TG expires.
NOTE 2: The expiry of timer TG does not cause a reset of the PLMN-specific N1 mode attempt counters for 3GPP access (see 3GPP TS 24.501 [64]).
NOTE 3: If an access technology is disabled for a PLMN that is part of the list of "equivalent PLMNs", the UE implementation ensures that registration to a different PLMN within the list of "equivalent PLMNs" does not result in reselection or inter-system change to the disabled access technology of that PLMN.
The MS in NB-S1 mode may maintain a list of "PLMNs with NB-IoT not allowed" where the NB-IoT capability was disabled due to receipt of a reject from the network with EMM cause #15 "no suitable cells in tracking area" and an Extended EMM cause IE with value "NB-IoT not allowed", as PLMNs where NB-S1 mode is not allowed. When the MS disables its NB-IoT capability due to receipt of a reject from the network with EMM cause #15 "no suitable cells in tracking area" and an Extended EMM cause IE with value "NB-IoT not allowed":
- the MS may add the identity of the PLMN to the list of "PLMNs with NB-IoT not allowed" and start timer TH if timer TH is not already running. The number of PLMNs that the MS can store in the "PLMNs with NB-IoT not allowed" list is implementation specific, but it shall be at least one. The value of timer TH is MS implementation specific, but shall not exceed the maximum possible value of background scanning timer T as specified in clause 4.4.3.3.1;
- in automatic PLMN selection the MS shall not consider PLMNs included in the "PLMNs with NB-IoT not allowed" list as PLMN selection candidates for the access technology E-UTRAN in NB-S1 mode, unless no other PLMN is available. This does not prevent selection of such a PLMN if it is available in another access technology; and
- the MS shall delete stored information in the "PLMNs with NB-IoT not allowed" list when the MS is switched off, the USIM is removed or timer TH expires.
If the MS supports access technology utilization control, the MS shall maintain a list of "PLMNs with associated access technology restrictions". When the MS receives the access technology utilization control information from the network (see 3GPP TS 24.501 [64] and 3GPP TS 24.301 [23A]):
- the MS shall store the received access technology utilization control information together with the PLMN identity of the current PLMN in the list of "PLMNs with associated access technology restrictions". The number of entries that the MS can store in the list of "PLMNs with associated access technology restrictions" is implementation specific, but it shall be at least one. The list of "PLMNs with associated access technology restrictions" is stored in the non-volatile memory of the ME;
- if the stored access technology utilization control information is applicable for the PLMN from which it is received and its equivalent PLMNs the MS shall apply it for the PLMN from which it is received and its equivalent PLMNs in PLMN selection, cell selection and cell reselection;
- in automatic PLMN selection, the MS shall not consider a restricted PLMN/access technology combination as a PLMN selection candidate;
- to prevent repeated attempts to obtain normal service on a restricted PLMN/access technology combination, the MS shall exclude the restricted access technologies for cell selection and cell reselection on this PLMN; and
- the MS is allowed to access a restricted PLMN/access technology combination included in the list of "PLMNs with associated access technology restrictions" to attach for emergency bearer services or to register for emergency services.
Editor's note (WID:ECRATU, CR:1287): It is FFS whether or not the "PLMNs with associated access technology restrictions" list will be stored in the non-volatile-memory.
Editor's note (WID:ECRATU, CR:1287): CT1 is awaiting feedback from RAN2 to determine the approach as to how the MS can exclude the restricted access technologies for cell selection and reselection purpose.
3.1A CSG selection / restriction
If the MS supports CSG, it is provisioned with an Allowed CSG list and an Operator CSG list and associated PLMN identities. Both lists can be retrieved either from the USIM if the lists are available in the USIM, or as described in 3GPP TS 24.285 [47] if the lists are not available in the USIM. These lists have zero or more entries.
NOTE 1: The network also updates the Allowed CSG list in the same updating operation if one or more entries are removed from the Operator CSG list. This avoids an entry removed from the Operator CSG list remaining in the Allowed CSG list.
There are two modes of CSG selection:
- Automatic mode: This mode utilizes the Allowed CSG list and the Operator CSG list. After a PLMN is selected, the MS camps on a cell in that PLMN only if the cell is either not a CSG cell or it is a CSG cell with a CSG identity that is in the Allowed CSG list or in the Operator CSG List. The idle mode procedures of NAS are not impacted by this mode. Upon switch on the MS is in automatic mode.
- Manual mode: In this mode, the MS indicates to the user a list of available CSGs and the associated PLMNs. Based on configuration by the HPLMN, the list of CSGs provided to the user for a certain PLMN is either:
- not restricted by the Allowed CSG list and the Operator CSG List stored in the MS; or
- restricted to entries in the Operator CSG List only.
After the user makes a selection, the MS camps on a cell with the selected CSG identity and may attempt to register with the associated PLMN (see 3GPP TS 24.008 [23] and 3GPP TS 24.301 [23A]).
The permitted CSG list is a combination of Operator CSG list and the Allowed CSG list. NAS shall provide the permitted CSG list to the AS. If the contents of the permitted CSG list have changed, NAS shall provide an updated permitted CSG list to the AS.
NOTE 2: The same CSG ID and its associated PLMN can exist in both the Operator CSG list and the Allowed CSG list. Such duplicates can be removed when combining these lists to form the permitted CSG list.
If an integrity protected message with cause value #25 (see 3GPP TS 24.008 [23] and 3GPP TS 24.301 [23A]) is received by an MS for a CSG ID and associated PLMN identity present in the Operator CSG list, then for an implementation dependent time which is not shorter than 60 minutes, or until the MS is switched off, or the SIM/USIM is removed, or the Operator CSG list is updated:
a) The NAS shall not include this CSG ID and the associated PLMN identity in the permitted CSG list provided to the AS; and
b) In CSG manual mode selection, the MS shall not indicate to the user that this CSG ID and the associated PLMN identity is in the Operator CSG List stored in the MS.
NOTE 3: As an implementation option, the user can be informed that the MS has not been authorized for a CSG included in the Operator CSG list.
3.1B PLMN selection triggered by ProSe communications
If the MS supports ProSe communications and needs to perform PLMN selection for ProSe communications as specified in 3GPP TS 24.334 [51] or 3GPP TS 24.554 [80], then the MS shall proceed as follows:
i) the MS shall store a duplicate value of the RPLMN and a duplicate of the PLMN selection mode that were in use before PLMN selection due to ProSe communications was initiated, unless this PLMN selection due to ProSe communications follows another PLMN selection due to ProSe communications or a manual CSG selection as specified in clause 4.4.3.1.3.3;
ii) the MS shall enter into Automatic mode of PLMN selection as specified in clause 4.4 taking into account the additional requirements in items iii) to x) below;
iii) among the PLMNs advertised by the E-UTRA cell or NR cell operating in the radio resources provisioned to the MS for ProSe communications as specified in 3GPP TS 24.333 [52], 3GPP TS 24.555 [81] or 3GPP TS 31.102 [40], the MS shall choose one allowable PLMN which meets:
1) the following:
- is advertised by the E-UTRA cell;
- provides radio resources for ProSe communications over E-UTRA PC5;
- is in the list of authorised PLMNs for ProSe communications as specified in 3GPP TS 24.334 [51];
- is not in the list of "PLMNs with E-UTRAN not allowed" as specified in clause 3.1; and
- is not in the list of "PLMNs with satellite E-UTRAN not allowed" as specified in clause 3.1; or
2) the following:
- is advertised by the NR cell;
- provides radio resources for 5G ProSe communications over NR PC5;
- is in the list of authorised PLMNs for 5G ProSe communications over PC5 as specified in 3GPP TS 24.554 [80];
- is the advertised PLMN(s) of the 5G ProSe layer-2 UE-to-network relay UE if the MS is acting as a 5G ProSe layer-2 remote UE;
- is not in the list of PLMNs where the N1 mode capability was disabled due to IMS voice not available and the MS's usage setting was "voice centric" as PLMNs where voice service was not possible;
- is not in the list of PLMNs where the N1 mode capability was disabled due to receipt of a reject from the network with 5GMM cause #27 "N1 mode not allowed" in N1 mode as specified in clause 3.1; and
- is not in the list of "PLMNs with satellite NG-RAN not allowed" as specified in clause 3.1;
if either condition 1) or condition 2) above is met then the MS shall attempt to register on that PLMN. If none of the PLMNs meet either condition 1) or condition2) above, the MS shall return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action;
iv) if the registration fails due to "PLMN not allowed" or "EPS services not allowed" as specified in 3GPP TS 24.334 [51], or due to "PLMN not allowed" or "5GS services not allowed" as specified in 3GPP TS 24.554 [80], then the MS shall update the appropriate list of forbidden PLMNs as specified in clause 3.1, and shall either:
A) if the PLMN provides common radio resources needed by the MS to do ProSe communications as specified in 3GPP TS 36.331 [42] or 3GPP TS 38.331 [65], perform ProSe communications on the selected PLMN in limited service state. In this case the MS shall not search for available and allowable PLMNs during the duration of ProSe communications;
B) return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action; or
C) perform the action described in iii) again with the choice of PLMNs further excluding the PLMNs on which the MS has failed to register.
Whether the MS performs A), B) or C) above is left up to MS implementation.
v) if the registration fails due to causes other than "PLMN not allowed" or "EPS services not allowed" or "5GS services not allowed", the MS shall:
- if the handling of the failure requires updating a list of forbidden PLMNs, update the appropriate list (as specified in 3GPP TS 24.301 [23A] or 3GPP TS 24.501 [64]); and
- if the handling of the failure does not require updating a list of forbidden PLMNs (as specified in 3GPP TS 24.301 [23A] or 3GPP TS 24.501 [64]), remember the PLMN as a PLMN on which the MS has failed to register;
NOTE 1: How long the MS memorizes the PLMNs on which it has failed to register is implementation dependent.
and the MS shall either:
A1) return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action;
B1) perform the action described in iii) again with the choice of PLMNs further excluding the PLMNs on which the MS has failed to register; or
C1) perform ProSe communications in limited service state on a PLMN advertised by the cell operating in the radio resources provisioned to the MS for ProSe communications as specified in 3GPP TS 24.333 [52], 3GPP TS 24.555 [81] or 3GPP TS 31.102 [40], if registration on this PLMN has previously failed due to "PLMN not allowed" or "EPS services not allowed" as specified in 3GPP TS 24.334 [51] or due to "PLMN not allowed" or "5GS services not allowed" as specified in 3GPP TS 24.554 [80] and if this PLMN provides common radio resources needed by the MS to do ProSe communications as specified in 3GPP TS 36.331 [42] or 3GPP TS 38.331 [65]. In this case the MS shall not search for available and allowable PLMNs during the duration of ProSe communications;
Whether the MS performs A1), B1) or C1) above is left up to MS implementation.
vi) if the MS is no longer in the coverage of the selected PLMN, then the MS shall either:
A2) perform ProSe communications procedures for MS to use provisioned radio resources as specified in 3GPP TS 24.334 [51] or 3GPP TS 24.554 [80]; or
B2) return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action.
Whether the MS performs A2) or B2) above is left up to MS implementation.
vii) if the MS is unable to find a suitable cell on the selected PLMN as specified in 3GPP TS 24.334 [51] or 3GPP TS 24.554 [80], then the MS shall either:
A3) if the PLMN provides common radio resources needed by the MS to do ProSe communications as specified in 3GPP TS 36.331 [42] or 3GPP TS 38.331 [65], perform ProSe communications on the selected PLMN in limited service state. In this case the MS shall not search for available and allowable PLMNs during the duration of ProSe communications; or
B3) return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action.
Whether the MS performs A3) or B3) above is left up to MS implementation.
viii) if the MS is switched off while on the selected PLMN and switched on again, the MS shall use the stored duplicate value of RPLMN as RPLMN and behave as specified in clause 4.4.3.1;
ix) if the user initiates a PLMN selection while on the selected cell, the MS shall delete the stored duplicate value of PLMN selection mode, use the stored duplicate value of RPLMN as RPLMN and follow the procedures (as specified for switch-on or recovery from lack of coverage) in clause 4.4.3.1. The MS shall delete the stored duplicate value of RPLMN once the MS has successfully registered to the selected PLMN; and
x) if the MS no longer needs to perform Prose communications, the MS shall return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action.
NOTE 2: If the MS returns to the RPLMN due to a failure to register in the selected PLMN, the upper layers of the MS can trigger PLMN selection again to initiate ProSe communications.
If the PLMN selected for ProSe communications is a VPLMN, the MS shall not periodically scan for higher priority PLMNs during the duration of ProSe communications.
The solution to prevent potential ping-pong between the RPLMN and the PLMN selected for ProSe communications is MS implementation specific.
3.1C PLMN selection triggered by V2X communication over PC5
If the MS supports V2X communication over E-UTRA-PC5 or NR-PC5 and needs to perform PLMN selection for V2X communication over PC5 as specified in 3GPP TS 24.386 [59] or 3GPP TS 24.587 [75], then the MS shall proceed as follows:
i) the MS shall store a duplicate value of the RPLMN and a duplicate of the PLMN selection mode that were in use before PLMN selection due to V2X communication over PC5 was initiated, unless this PLMN selection due to V2X communication over PC5 follows another PLMN selection due to V2X communication over PC5 or a manual CSG selection as specified in clause 4.4.3.1.3.3;
ii) the MS shall enter into Automatic mode of PLMN selection as specified in clause 4.4 taking into account the additional requirements in items iii) to x) below;
iii) Among the PLMNs advertised by the E-UTRA or NG-RAN cell operating in the radio resources provisioned to the MS for V2X communication over PC5 as specified in 3GPP TS 24.385 [60], 3GPP TS 24.588 [79] or 3GPP TS 31.102 [40], the MS shall choose one allowable PLMN which meets:
1) the following:
- provides radio resources for V2X communication over PC5;
- is in the list of authorised PLMNs for V2X communication over PC5 as specified in 3GPP TS 24.386 [59] or 3GPP TS 24.587 [75];
- is not in the list of "PLMNs with E-UTRAN not allowed" as specified in clause 3.1; and
- is not in the list of "PLMNs with satellite E-UTRAN not allowed" as specified in clause 3.1; or
2) the following:
- provides radio resources for V2X communication over PC5;
- is in the list of authorised PLMNs for V2X communication over PC5 as specified in 3GPP TS 24.386 [59] or 3GPP TS 24.587 [75];
- is not in the list of PLMNs where the N1 mode capability was disabled due to IMS voice not available and the MS's usage setting was "voice centric" as PLMNs where voice service was not possible;
- is not in the list of PLMNs where the N1 mode capability was disabled due to receipt of a reject from the network with 5GMM cause #27 "N1 mode not allowed" in N1 mode as specified in clause 3.1; and
- is not in the list of "PLMNs with satellite NG-RAN not allowed" as specified in clause 3.1;
if condition 1) or 2) above are met then the MS shall attempt to register on that PLMN. If none of the PLMNs meet condition 1) or 2) above, the MS shall return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action;
iv) if the registration fails due to "PLMN not allowed" or "EPS services not allowed" as specified in 3GPP TS 24.386 [59], or due to "PLMN not allowed" or "5GS services not allowed" as specified in 3GPP TS 24.587 [75], or both, then the MS shall update the appropriate list of forbidden PLMNs as specified in clause 3.1, and shall:
A) if the PLMN provides common radio resources needed by the MS to do V2X communication over PC5 as specified in 3GPP TS 36.331 [42] or 3GPP TS 38.331 [65], perform V2X communication over PC5 on the selected PLMN in limited service state. In this case the MS shall not search for available and allowable PLMNs during the duration of V2X communication over PC5;
B) return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action; or
C) perform the action described in iii) again with the choice of PLMNs further excluding the PLMNs on which the MS has failed to register.
Whether the MS performs A), B) or C) above is left up to MS implementation.
v) if the registration fails due to causes other than "PLMN not allowed" or "EPS services not allowed" or "5GS services not allowed", the MS shall:
- if the handling of the failure requires updating a list of forbidden PLMNs, update the appropriate list (as specified in 3GPP TS 24.301 [23A] or 3GPP TS 24.501 [64]); and
- if the handling of the failure does not require updating a list of forbidden PLMNs (as specified in 3GPP TS 24.301 [23A] or 3GPP TS 24.501 [64]), remember the PLMN as a PLMN on which the MS has failed to register;
NOTE 1: How long the MS memorizes the PLMNs on which it has failed to register is implementation dependent.
and the MS shall:
A1) return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action;
B1) perform the action described in iii) again with the choice of PLMNs further excluding the PLMNs on which the MS has failed to register; or
C1) perform V2X communication over PC5 in limited service state on a PLMN advertised by the cell operating in the radio resources provisioned to the MS for V2X communication over PC5 as specified in 3GPP TS 24.385 [60], 3GPP TS 24.588 [79] or 3GPP TS 31.102 [40], if registration on this PLMN has previously failed due to "PLMN not allowed" or "EPS services not allowed" as specified in 3GPP TS 24.386 [59], or due to "PLMN not allowed" or "5GS services not allowed" as specified in 3GPP TS 24.587 [75], or both, and if this PLMN provides common radio resources needed by the MS to do V2X communication over PC5 as specified in 3GPP TS 36.331 [42] or 3GPP TS 38.331 [65]. In this case the MS shall not search for available and allowable PLMNs during the duration of V2X communication over PC5;
Whether the MS performs A1), B1) or C1) above is left up to MS implementation.
vi) if the MS is no longer in the coverage of the selected PLMN, then the MS shall:
A2) perform V2X communication over PC5 procedures for MS to use provisioned radio resources as specified in 3GPP TS 24.386 [59] or 3GPP TS 24.587 [75]; or
B2) return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action.
Whether the MS performs A2) or B2) above is left up to MS implementation.
vii) if the MS is unable to find a suitable cell on the selected PLMN as specified in 3GPP TS 24.386 [59] or 3GPP TS 24.587 [75], then the MS shall:
A3) if the PLMN provides common radio resources needed by the MS to do V2X communication over PC5 as specified in 3GPP TS 36.331 [42] or 3GPP TS 38.331 [65], perform V2X communication over PC5 on the selected PLMN in limited service state. In this case the MS shall not search for available and allowable PLMNs during the duration of V2X communication over PC5; or
B3) return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action.
Whether the MS performs A3) or B3) above is left up to MS implementation.
viii) if the MS is switched off while on the selected PLMN and switched on again, the MS shall use the stored duplicate value of RPLMN as RPLMN and behave as specified in clause 4.4.3.1;
ix) if the user initiates a PLMN selection while on the selected cell, the MS shall delete the stored duplicate value of PLMN selection mode, use the stored duplicate value of RPLMN as RPLMN and follow the procedures (as specified for switch-on or recovery from lack of coverage) in clause 4.4.3.1. The MS shall delete the stored duplicate value of RPLMN once the MS has successfully registered to the selected PLMN; and
x) if the MS no longer needs to perform V2X communication over PC5, the MS shall return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action.
NOTE 2: If the MS returns to the RPLMN due to a failure to register in the selected PLMN, the upper layers of the MS can trigger PLMN selection again to initiate V2X communication over PC5.
If the PLMN selected for V2X communication over PC5 is a VPLMN, the MS shall not periodically scan for higher priority PLMNs during the duration of V2X communication over PC5.
The solution to prevent potential ping-pong between the RPLMN and the PLMN selected for V2X communication over PC5 is MS implementation specific.
3.1D PLMN selection triggered by A2X communication over PC5
If the MS supports A2X communication over E-UTRA-PC5 or NR-PC5 and needs to perform PLMN selection for A2X communication over PC5 as specified in 3GPP TS 24.577 [86], then the MS shall proceed as follows:
i) the MS shall store a duplicate value of the RPLMN and a duplicate of the PLMN selection mode that were in use before PLMN selection due to A2X communication over PC5 was initiated, unless this PLMN selection due to A2X communication over PC5 follows another PLMN selection due to A2X communication over PC5 or a manual CSG selection as specified in clause 4.4.3.1.3.3;
ii) the MS shall enter into Automatic mode of PLMN selection as specified in clause 4.4 taking into account the additional requirements in items iii) to x) below;
iii) among the PLMNs advertised by the E-UTRA cell or NR cell operating in the radio resources provisioned to the MS for A2X communication over PC5 as specified in 3GPP TS 24.577 [86], 3GPP TS 24.578 [87] or 3GPP TS 31.102 [40], the MS shall choose one allowable PLMN which meets:
1) the following:
- provides radio resources for A2X communication over PC5;
- is in the list of authorised PLMNs for A2X communication over PC5 as specified in 3GPP TS 24.577 [86];
- is not in the list of "PLMNs with E-UTRAN not allowed" as specified in clause 3.1; and
- is not in the list of "PLMNs with satellite E-UTRAN not allowed" as specified in clause 3.1; or
2) the following:
- provides radio resources for A2X communication over PC5;
- is in the list of authorised PLMNs for A2X communication over PC5 as specified in 3GPP TS 24.577 [86];
- is not in the list of PLMNs where the N1 mode capability was disabled due to IMS voice not available and the MS's usage setting was "voice centric" as PLMNs where voice service was not possible;
- is not in the list of PLMNs where the N1 mode capability was disabled due to receipt of a reject from the network with 5GMM cause #27 "N1 mode not allowed" in N1 mode as specified in clause 3.1; and
- is not in the list of "PLMNs with satellite NG-RAN not allowed" as specified in clause 3.1;
if either condition 1) or condition 2) above is met then the MS shall attempt to register on that PLMN. If none of the PLMNs meet either condition 1) or condition 2) above, the MS shall return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action;
iv) if the registration fails due to "PLMN not allowed" or "EPS services not allowed" in case of EPS, due to "PLMN not allowed" or "5GS services not allowed" in case of 5GS, or both as specified in 3GPP TS 24.577 [86], then the MS shall update the appropriate list of forbidden PLMNs as specified in clause 3.1, and shall:
A) if the PLMN provides common radio resources needed by the MS to do A2X communication over PC5 as specified in 3GPP TS 36.331 [42] or 3GPP TS 38.331 [65], perform A2X communication over PC5 on the selected PLMN in limited service state. In this case the MS shall not search for available and allowable PLMNs during the duration of A2X communication over PC5;
B) return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action; or
C) perform the action described in iii) again with the choice of PLMNs further excluding the PLMNs on which the MS has failed to register.
Whether the MS performs A), B) or C) above is left up to MS implementation.
v) if the registration fails due to causes other than "PLMN not allowed" or "EPS services not allowed" or "5GS services not allowed", the MS shall:
- if the handling of the failure requires updating a list of forbidden PLMNs, update the appropriate list (as specified in 3GPP TS 24.301 [23A] or 3GPP TS 24.501 [64]); and
- if the handling of the failure does not require updating a list of forbidden PLMNs (as specified in 3GPP TS 24.301 [23A] or 3GPP TS 24.501 [64]), remember the PLMN as a PLMN on which the MS has failed to register;
NOTE 1: How long the MS memorizes the PLMNs on which it has failed to register is implementation dependent.
and the MS shall either:
A1) return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action;
B1) perform the action described in iii) again with the choice of PLMNs further excluding the PLMNs on which the MS has failed to register; or
C1) perform A2X communication over PC5 in limited service state on a PLMN advertised by the cell operating in the radio resources provisioned to the MS for A2X communication over PC5 as specified in 3GPP TS 24.577 [86], 3GPP TS 24.578 [87] or 3GPP TS 31.102 [40], if registration on this PLMN has previously failed due to "PLMN not allowed" or "EPS services not allowed" in case of EPS, due to "PLMN not allowed" or "5GS services not allowed" in case of 5GS, or both as specified in 3GPP TS 24.577 [86], and if this PLMN provides common radio resources needed by the MS to do A2X communication over PC5 as specified in 3GPP TS 36.331 [42] or 3GPP TS 38.331 [65]. In this case the MS shall not search for available and allowable PLMNs during the duration of A2X communication over PC5;
Whether the MS performs A1), B1) or C1) above is left up to MS implementation.
vi) if the MS is no longer in the coverage of the selected PLMN, then the MS shall:
A2) perform A2X communication over PC5 procedures for MS to use provisioned radio resources as specified in 3GPP TS 24.577 [86]; or
B2) return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action.
Whether the MS performs A2) or B2) above is left up to MS implementation.
vii) if the MS is unable to find a suitable cell on the selected PLMN as specified in 3GPP TS 24.577 [86], then the MS shall:
A3) if the PLMN provides common radio resources needed by the MS to do A2X communication over PC5 as specified in 3GPP TS 36.331 [42] or 3GPP TS 38.331 [65], perform A2X communication over PC5 on the selected PLMN in limited service state. In this case the MS shall not search for available and allowable PLMNs during the duration of A2X communication over PC5; or
B3) return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action.
Whether the MS performs A3) or B3) above is left up to MS implementation.
viii) if the MS is switched off while on the selected PLMN and switched on again, the MS shall use the stored duplicate value of RPLMN as RPLMN and behave as specified in clause 4.4.3.1;
ix) if the user initiates a PLMN selection while on the selected cell, the MS shall delete the stored duplicate value of PLMN selection mode, use the stored duplicate value of RPLMN as RPLMN and follow the procedures (as specified for switch-on or recovery from lack of coverage) in clause 4.4.3.1. The MS shall delete the stored duplicate value of RPLMN once the MS has successfully registered to the selected PLMN; and
x) if the MS no longer needs to perform A2X communication over PC5, the MS shall return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action.
NOTE 2: If the MS returns to the RPLMN due to a failure to register in the selected PLMN, the upper layers of the MS can trigger PLMN selection again to initiate A2X communication over PC5.
If the PLMN selected for A2X communication over PC5 is a VPLMN, the MS shall not periodically scan for higher priority PLMNs during the duration of A2X communication over PC5.
The solution to prevent potential ping-pong between the RPLMN and the PLMN selected for A2X communication over PC5 is MS implementation specific.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
3.2 Regional provision of service
|
An MS may have a "regionally restricted service" where it can only obtain service on certain areas (i.e. LAs or TAs). If such an MS attempts to camp on a cell of an area for which it does not have service entitlement, when it does an LR request, it will receive a message with cause value #12 (see 3GPP TS 24.008 [23], 3GPP TS 24.301 [23A] and 3GPP TS 24.501 [64]). In this case, the MS shall take the following actions depending on the mode in which the message was received:
A/Gb mode or Iu mode:
- The MS stores the forbidden LA identity (LAI) in a list of "forbidden location areas for regional provision of service", to prevent repeated access attempts on a cell of the forbidden LA. This list is deleted when the MS is switched off, the SIM is removed or periodically (with period in the range 12 to 24 hours). The MS enters the limited service state.
S1-mode:
The MS stores the forbidden TA identity (TAI) in a list of "forbidden tracking areas for regional provision of service", to prevent repeated access attempts on a cell of the forbidden TA. This list is deleted when the MS is switched off, the SIM is removed or periodically (with period in the range 12 to 24 hours). The MS enters the limited service state.
N1-mode:
The MS stores the forbidden TA identity (TAI) in a list of "5GS forbidden tracking areas for regional provision of service", to prevent repeated access attempts on a cell of the forbidden TA. This list is deleted when the MS is switched off, the SIM is removed or periodically (with period in the range 12 to 24 hours). The MS enters the limited service state.
In A/Gb mode, a cell may be reserved for SoLSA exclusive access (see 3GPP TS 24.008 [23] and 3GPP TS 44.060 [39]). An MS is only allowed to camp normally on such a cell if it has a Localised Service Area subscription to the cell. Other MS may enter the limited service state.
NOTE 1: In A/Gb mode, in a SoLSA exclusive cell the MCC+MNC code is replaced by a unique escape PLMN code (see 3GPP TS 23.073), not assigned to any PLMN, in SI3 and SI4. An MS not supporting SoLSA may request for location update to an exclusive access cell. In this case the location attempt is rejected with the cause "PLMN not allowed" and the escape PLMN code is added to the list of the "forbidden PLMNs".
The MS operating in SNPN access operation mode over 3GPP access shall maintain one or more lists of "5GS forbidden tracking areas for regional provision of service", each associated with an SNPN and, if the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, entry of the "list of subscriber data" or, if the MS supports access to an SNPN using credentials from a credentials holder, the PLMN subscription. The MS shall use the list of "5GS forbidden tracking areas for regional provision of service" associated with the selected SNPN and, if the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the MS selects a new SNPN, the MS shall keep the list of "5GS forbidden tracking areas for regional provision of service" associated with the previously selected SNPN and, if the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the previously selected entry of the "list of subscriber data" or the previously selected PLMN subscription. If the number of the lists to be kept is higher than supported, the MS shall delete the oldest stored list of "5GS forbidden tracking areas for regional provision of service". The MS shall delete all lists of "5GS forbidden tracking areas for regional provision of service", when the MS is switched off. The MS shall delete the list of "5GS forbidden tracking areas for regional provision of service" associated with an SNPN:
a) when the entry with the subscribed SNPN identifying the SNPN in the "list of subscriber data" is updated;
b) when the USIM is removed if:
- EAP based primary authentication and key agreement procedure using EAP-AKA'; or
- 5G AKA based primary authentication and key agreement procedure;
was performed in the selected SNPN; or
c) if the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, when the list of "5GS forbidden tracking areas for regional provision of service" is associated with:
- the entry of the "list of subscriber data" and the entry of the "list of subscriber data" is updated; or
- the PLMN subscription and USIM is removed.
NOTE 2: The number of the lists of "5GS forbidden tracking areas for regional provision of service" supported by the MS is MS implementation specific.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
3.3 Borders between registration areas
|
If the MS is moving in a border area between registration areas, it might repeatedly change between cells of different registration areas. Each change of registration area would require an LR, which would cause a heavy signalling load and increase the risk of a paging message being lost. The access stratum shall provide a mechanism to limit this effect.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
3.4 Access control
| |
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
3.4.1 Access control
|
Due to problems in certain areas, network operators may decide to restrict access from some MSs (e.g., in case of congestion), and for this reason, a mechanism for common access control is provided. In A/Gb mode and Iu mode a mechanism for domain specific access control is also provided (see 3GPP TS 43.022 [35], 3GPP TS 44.018 [34] and 3GPP TS 25.304 [32]).
A mechanism to restrict access is provided via EAB. A network operator can restrict network access of those MSs that are configured for EAB in addition to common access control and domain specific access control.
The MS can be configured for EAB in the USIM (see 3GPP TS 31.102 [40]) or in the ME (see 3GPP TS 24.368 [50]). An MS that supports EAB shall follow the EAB mechanism (see 3GPP TS 24.008 [23], 3GPP TS 24.301 [23A], 3GPP TS 44.018 [34], 3GPP TS 25.331 [33], 3GPP TS 36.331 [42]) when configured for EAB.
The MS can be configured for ACDC in the USIM (see 3GPP TS 31.102 [40]) or in the ME (see 3GPP TS 24.105 [53]). An MS that supports ACDC shall follow the ACDC mechanism (see 3GPP TS 24.008 [23], 3GPP TS 24.301 [23A], 3GPP TS 25.331 [33], 3GPP TS 36.331 [42]) when configured for ACDC.
The MS can be configured in the USIM (see 3GPP TS 31.102 [40]) or in the ME (see 3GPP TS 24.368 [50]) to override EAB. An MS that supports overriding EAB shall follow the overriding EAB mechanism (see 3GPP TS 24.008 [23], 3GPP TS 24.301 [23A]) when configured to allow overriding EAB.
In the case that a network operator decides to restrict access they may as an option allow restricted MSs to respond to paging messages and/or to perform location registrations. Mechanisms to allow this optional access are provided (see 3GPP TS 25.304 [32]).
A network operator can also restrict some MSs to access the network for location registration, although via common access class control or domain specific access class control the MSs are permitted to access the network for other purposes.
If the MS is accessing the network with a special access class (Access classes 11 to 15), then the MS shall ignore EAB and ACDC.
NOTE: The conditions when the MS is allowed to access the network with access class 11 – 15 are specified in 3GPP TS 22.011 [138].
If an MS configured for EAB is initiating an emergency call, then the MS shall ignore EAB.
If an MS configured for EAB is responding to paging, then the MS shall ignore EAB.
If an MS configured for ACDC is responding to paging, then the MS shall ignore ACDC.
If an MS configured for ACDC is initiating an emergency call, then the MS shall ignore ACDC.
If an MS configured for ACDC and the MO MMTEL voice call is started, the MO MMTEL video call is started or the MO SMSoIP is started (see 3GPP TS 24.008 [23], 3GPP TS 24.301 [23A]), then the MS shall ignore ACDC.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
3.4.2 Forbidden LA or TA for regional provision of service
|
The MS is not allowed to initiate establishment of a CM connection except for an emergency call when camped on a cell of an LA or TA of which belongs to the list of "forbidden location areas for regional provision of service" or "forbidden tracking areas for regional provision of service". The MS may respond to paging.
The MS is not allowed to request GPRS services except for an emergency bearer services or for access to RLOS when camped on a cell of an LA or TA of which belongs to the list of "forbidden location areas for regional provision of service" or "forbidden tracking areas for regional provision of service".
The MS is not allowed to request 5GS services except emergency services when camped on a cell of a TA of which belongs to the list of "5GS forbidden tracking areas for regional provision of service".
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
3.5 No suitable cell (limited service state)
|
There are a number of situations in which the MS is unable to obtain normal service from a PLMN or SNPN. These include:
a) Failure to find a suitable cell of the selected PLMN or of the selected SNPN;
b) No SIM in the MS or the "list of subscriber data" with no valid entry;
c) A "PLMN not allowed", "Requested service option not authorized in this PLMN", "Serving network not authorized", "PLMNs not allowed to operate at the present UE location" or "IAB-node operation not authorized" response in case of PLMN or a "Temporarily not authorized for this SNPN", "Permanently not authorized for this SNPN" or "IAB-node operation not authorized" response in case of SNPN when an LR is received;
d) An "illegal MS" or "illegal ME" response when an LR is received (Any SIM or the corresponding entry of the "list of subscriber data" in the ME is then considered "invalid");
e) An "IMSI unknown in HLR" response when an LR is received (Any SIM in the ME is then considered "invalid" for non-GPRS services);
f) A "GPRS services not allowed" response when an LR of a GPRS MS attached to GPRS services only is received (The cell selection state of GPRS MSs attached to GPRS and non-GPRS depends on the outcome of the location updating), or an "EPS services not allowed" response is received when an EPS attach, tracking area update or service request is performed, or a "5GS services not allowed" response is received when a registration or service request is performed;
g) Void;
h) Void;
i) MS supporting CAG is camped on a CAG cell belonging to a PLMN, the CAG-ID of the CAG cell is not manually selected by the user and none of the CAG-ID(s) of the CAG cell are authorized based on the "Allowed CAG list" associated with that PLMN in the "CAG information list";
j) MS supporting CAG is camped on a non-CAG cell belonging to a PLMN, the PLMN ID of the non-CAG cell without a CAG-ID is not manually selected by the user and the UE is configured with "indication that the MS is only allowed to access 5GS via CAG cells" for that PLMN in the "CAG information list"; and
k) MS supporting CAG is camped on a CAG cell belonging to a PLMN, the CAG-ID of the CAG cell is not manually selected by the user and the "CAG information list" does not contain an entry for the PLMN (e.g. because the UE is not (pre-)configured with a "CAG information list").
l) MS selected a PLMN for disaster roaming, the timer precluding registration for disaster roaming in the selected PLMN for disaster roaming is running and the MS is not registering or registered for emergency services in the selected PLMN for disaster roaming.
m) MS determined that a disaster condition has ended as specified in clause 3.10, selected the PLMN previously with disaster condition, the timer precluding registration in the PLMN previously with disaster condition is running and the MS is not registering or registered for emergency services in the PLMN previously with disaster condition.
(In automatic PLMN selection mode, items a, c and f would normally cause a new PLMN selection, but even in this case, the situation may arise when no PLMNs are available and allowable for use).
(In automatic SNPN selection mode, items a, c, d, and f would normally cause a new SNPN selection if there are two or more entries in the "list of subscriber data", but even in this case, the situation may arise when no SNPNs are available and allowable for use).
For the items a to f, if the MS does not operate in SNPN access operation mode over 3GPP access, the MS attempts to camp on an acceptable cell, irrespective of its PLMN identity, so that emergency calls or access to RLOS can be made if necessary, with the exception that an MS operating in NB-S1 mode, shall never attempt to make emergency calls or to access RLOS. When in the limited service state with a valid SIM, the MS shall search for available and allowable PLMNs in the manner described in clause 4.4.3.1 and when indicated in the SIM also as described in clause 4.4.3.4. For an MS that is not in eCall only mode, with the exception of performing GPRS attach or EPS attach for emergency bearer services, performing an initial registration for emergency services, or performing EPS attach for access to RLOS, no LR requests are made until a valid SIM is present and either a suitable cell is found or a manual network reselection is performed. For an MS in eCall only mode, no LR requests are made except for performing EPS attach for emergency bearer services or an initial registration for emergency services. When performing GPRS attach or EPS attach for emergency bearer services, an initial registration for emergency services, or performing EPS attach for access to RLOS, the PLMN of the current serving cell is considered as the selected PLMN for the duration the MS is attached for emergency bearer services, registered for emergency services, or attached for access to RLOS. In the limited service state the presence of the MS need not be known to the PLMN on whose cell it has camped. If the MS is enabled for SNPN, the MS needs to make an emergency call, there is no available PLMN supporting emergency services and the MS determines that there is an available SNPN supporting emergency services (based on broadcasted information of SNPN support for emergency services), the MS may start operating in SNPN access operation mode over 3GPP access and attempt to camp on a cell of the SNPN supporting emergency services. After an emergency call is released, the MS should stop operating in SNPN access operation mode over 3GPP access and perform PLMN selection. If the MS is enabled for SNPN and wants to perform configuration of SNPN subscription parameters in PLMN via the user plane, but there is no available PLMN for normal services, either because of no available PLMN or all available PLMNs being in forbidden PLMN list due to LR failure, the MS may start operating in SNPN access operation mode over 3GPP access (if the MS is configured with default UE credentials) and perform SNPN selection as per subclause 4.9.3.1.3 or 4.9.3.1.4. After the onboarding services in SNPN are complete, the MS may stop operating in SNPN access operation mode over 3GPP access and perform PLMN selection.
For the items a, c, d and f, if the MS operates in SNPN access operation mode over 3GPP access and the MS has a valid entry in the "list of subscriber data", the MS shall search for available and allowable SNPNs in the manner described in clause 4.9.3.1. For the item b, if the MS operates in SNPN access operation mode over 3GPP access, the MS:
- attempts to camp on an acceptable cell so that emergency calls can be made if supported and necessary; and
- may perform SNPN selection procedure for onboarding services in SNPN if the MS is configured with the default UE credentials for primary authentication.
For the item l, the MS shall search for available and allowable PLMNs in the manner described in clause 4.4.3.1 and when indicated in the SIM also as described in clause 4.4.3.4.
When in the limited service state, with the exception of performing an initial registration for emergency services, no LR requests are made until a valid entry of the "list of subscriber data" is present and either a suitable cell is found or a manual network reselection is performed. In the limited service state, the presence of the MS need not be known to the SNPN on whose cell it has camped. If the MS needs to make an emergency call, the MS supports accessing a PLMN, and there is no available SNPN supporting emergency services and the MS determines that there is an available PLMN supporting emergency services (based on broadcasted information of PLMN support for emergency services), the MS shall stop operating in SNPN access operation mode over 3GPP access and attempt to camp on a cell of the PLMN supporting emergency services so that emergency calls can be made. After an emergency call is released, the MS may re-start operating in SNPN access operation mode over 3GPP access and perform SNPN selection. If the MS is enabled for SNPN and wants to select an SNPN for onboarding services in SNPN, but finds no suitable SNPN as per subclause 4.9.3.1.3 or 4.9.3.1.4, the MS may stop operating in SNPN access operation mode over 3GPP access, and perform PLMN selection (if the MS is configured with PLMN credentials in USIM). The MS may perform PLMN selection as per clause 4.4. After the configuration of SNPN subscription parameters in PLMN via the user plane is complete, the MS may start operating in SNPN access operation mode over 3GPP access and perform SNPN selection. If the MS supports access to an SNPN providing access for localized services in SNPN and access for localized services in SNPN is enabled, and the MS is in limited service state because no SNPN is available as per subclause 4.9.3.1, when the validity information of an SNPN based on the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" or "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" changes from not met to met, the MS shall perform an SNPN selection as per subclause 4.9.3.1.
There are also other conditions under which only emergency calls or access to RLOS may be made if the MS does not operate in SNPN access operation mode over 3GPP access. These are shown in table 2 in clause 5. ProSe communications can be initiated in case of PLMN if necessary (see 3GPP TS 24.334 [51] or 3GPP TS 24.554 [80]) when in the limited service state due to items a) or c) or f). V2X communication over PC5 can be initiated if necessary (see 3GPP TS 24.386 [59] or 3GPP TS 24.587 [75]) when in the limited service state due to items a) or c) or f). A2X communication over PC5 can be initiated if necessary (see 3GPP TS 24.577 [86]) when in the limited service state due to items a) or c) or f).
For the items i and j for an MS operating in automatic PLMN selection mode, when the time validity information of one or more CAG-IDs change from not authorized to authorized based on the "Allowed CAG list" associated with a PLMN other than the current PLMN in the "CAG information list" stored in the MS, and the MS does not have a PDU session for emergency services, the MS shall perform PLMN selection as per subclause 4.4.3.1. If the MS has an emergency PDU session established, then the MS shall attempt to perform PLMN selection after the emergency PDU session is released if the time validity information of one or more CAG-IDs are still authorized based on the "Allowed CAG list" associated with that PLMN.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
3.6 CTS fixed part selection (A/Gb mode only)
|
In CTS mode only or in automatic mode with CTS preferred, the CTS MS normally operates on a CTS fixed part on which the mobile station is already enrolled. If the CTS MS loses CTS coverage in these modes, it shall attempt periodically to select again a CTS fixed part.
To select a CTS fixed part, the CTS MS shall listen to the CTSBCH frequencies of all the fixed parts on which the MS is currently enrolled.
If the CTS MS is moving in a border area between one area with CTS coverage and one without it, it might repeatedly require CTS attachments and LU on the PLMN. To prevent this, the criteria C1_CTS and C2_CTS (defined in 3GPP TS 45.008 [25] clause 11.1) are used. To attach to a CTS FP, the C1_CTS criterion shall be greater than zero. When the C2_CTS criterion falls below zero, the CTS MS shall consider itself to be no more under CTS coverage.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
3.7 NAS behaviour configuration
|
NAS behaviour can be operator configurable using parameters in the USIM (see 3GPP TS 31.102 [40]) or in the ME (see 3GPP TS 24.368 [50]). For parameters available in both the USIM and the ME, precedence is specified in 3GPP TS 31.102 [40] clause 5.2.29.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
3.8 CAG selection (N1 mode only)
|
The MS may support CAG.
The MS may support enhanced CAG information. If the MS supports enhanced CAG information, the MS shall support CAG.
If the MS supports CAG, the MS can be provisioned by the network with a "CAG information list", consisting of zero or more entries, each containing:
a) a PLMN ID;
b) an "Allowed CAG list". The "Allowed CAG list" contains zero or more CAG-IDs .If the UE supports enhanced CAG information, each CAG-ID in the "Allowed CAG list" can be associated with time validity information. The time validity information contains one or more time periods; and
c) an optional "indication that the MS is only allowed to access 5GS via CAG cells".
The "CAG information list" provisioned by the network is stored in the non-volatile memory of the ME, as specified in 3GPP TS 24.501 [64] annex C.
NOTE 1: When the MS is registering or registered to a PLMN other than the HPLMN or EHPLMN, then the HPLMN will send a "CAG information list" consisting of CAG subscription information related to the serving PLMN only. When the MS is registering or registered to the HPLMN or EHPLMN then the HPLMN or EHPLMN can send CAG subscription information related to any PLMN in the "CAG information list".
In addition, the MS can also be pre-configured with a "CAG information list" stored in the USIM (see 3GPP TS 31.102 [40]). The "Allowed CAG list" included in the entry for the HPLMN or EHPLMN in "CAG information list" stored in the USIM can contain a range of CAG-IDs.
NOTE 2: For a given PLMN ID, no more than one entry containing the MCC value and the MNC value of the PLMN ID is necessary to be provided in the "CAG information list" stored in the USIM (see TS 31.102 [22]).
3GPP TS 24.501 [64] annex C specifies condition under which the "CAG information list" stored in the ME is deleted. Additionally, when a USIM is inserted, if:
- no "CAG information list" is stored in the non-volatile memory of the ME; or
- the SUPI from the USIM does not match the SUPI stored together with the "CAG information list" in the non-volatile memory of the ME;
and the MS has a "CAG information list" stored in the USIM (see 3GPP TS 31.102 [22]), the MS shall store the "CAG information list" from the USIM into the ME, as specified in 3GPP TS 24.501 [64] annex C. If an entry in the "CAG information list" stored in the USIM includes an "Allowed CAG list" which contains a range of CAG-IDs, the range of CAG-IDs can be replaced with individual CAG-IDs matching the range up to ME implementation.
NOTE 3: The MS ignores the "CAG information list" stored in the USIM except when the USIM is inserted.
If the MS supports CAG and a PLMN is selected as described in clause 4.4.3.1.1, the automatic CAG selection is performed as part of clause 4.4.3.1.1.
If the MS supports CAG and a PLMN is selected as described in clause 4.4.3.1.2, the manual CAG selection is performed as part of clause 4.4.3.1.2.
The NAS shall provide the AS with a "CAG information list", if available, where the "CAG information list" contains only the CAG-IDs authorized by the "Allowed CAG list" for the entries in the "CAG information list", if available. If the contents of the "CAG information list" have changed, or the time validity information of an entry of "Allowed CAG list" in the "CAG information list" starts or stops matching the MS’s current time, the NAS shall provide an updated "CAG information list" to the AS, where the "CAG information list" contains only the CAG-IDs authorized by the "Allowed CAG list" for the entries in the "CAG information list", if available. If an entry in the "CAG information list" includes an "Allowed CAG list" which contains a range of CAG-IDs, whether the NAS provides the AS the range of CAG-IDs or individual CAG-IDs matching the range is up to ME implementation.
The "indication that the MS is only allowed to access 5GS via CAG cells" is not applicable in EPS.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
3.9 SNPN selection
|
An MS may be enabled for SNPN.
An MS enabled for SNPN may operate in SNPN access operation mode over 3GPP access.
An MS may support onboarding services in SNPN.
An MS enabled for SNPN may support access to an SNPN using credentials from a credentials holder.
An MS enabled for SNPN may support access to an SNPN providing access for localized services in SNPN. If the MS supports access to an SNPN providing access for localized services in SNPN, the MS shall support access to an SNPN using credentials from a credentials holder.
With the exception of onboarding services in SNPN, the MS operating in SNPN access operation mode over 3GPP access selects:
a) an SNPN for which it is configured with a subscriber identifier and credentials;
b) if the MS supports equivalent SNPNs, an equivalent SNPN; or
c) if the MS supports access to an SNPN using credentials from a credentials holder, an SNPN which supports access using credentials from a credentials holder.
The MS can have several sets of subscriber identifiers, credentials, SNPN identities, and other parameters related to SNPN selection (see clause 4.9.3.0). There are two modes for SNPN selection:
i) Automatic SNPN selection mode.
ii) Manual SNPN selection mode.
For onboarding services in SNPN, the MS operating in SNPN access operation mode over 3GPP access selects an SNPN indicating that onboarding is allowed. There are two modes for SNPN selection for onboarding services in SNPN:
i) Automatic SNPN selection mode.
ii) Manual SNPN selection mode.
An SNPN selected for localized services in SNPN is an SNPN that is selected by an MS supporting access to an SNPN providing access for localized services in SNPN, when the access for localized services in SNPN is enabled, and the SNPN is selected according to:
a) clause 4.9.3.1.1 bullet a0);
b) clause 4.9.3.2.1 bullet a0); or
c) is manually selected by the user; and
i) the validity information of the SNPN is met;
ii) the validity information of GIN(s) broadcasted by the SNPN is met; or
iii) both.
3.9A SNPN selection triggered by ProSe communications
If the MS is enabled for SNPN and supports ProSe communications and needs to perform SNPN selection for ProSe communications as specified in 3GPP TS 24.554 [80], then the MS shall proceed as follows:
i) the MS shall store a duplicate value of the RSNPN and a duplicate of the SNPN selection mode that were in use before SNPN selection due to ProSe communications was initiated, unless this SNPN selection due to ProSe communications follows another SNPN selection due to ProSe communications;
ii) the MS shall enter into automatic mode of SNPN selection as specified in clause 4.9 taking into account the additional requirements in items iii) to x) below;
iii) among the SNPN advertised by the NR cell operating in the radio resources provisioned to the MS for ProSe communications as specified in 3GPP TS 24.555 [81] or 3GPP TS 31.102 [40], the MS shall choose one allowable SNPN which meets:
1) the following:
- is advertised by the NR cell;
- provides radio resources for 5G ProSe communications over NR PC5;
- is authorised for 5G ProSe communications over PC5 as specified in 3GPP TS 24.554 [80];
- is the advertised SNPN(s) of the 5G ProSe layer-2 UE-to-network relay UE if the MS is acting as a 5G ProSe layer-2 remote UE;
- is not in the list of SNPNs where the N1 mode capability was disabled due to IMS voice not available and the MS's usage setting was "voice centric" as SNPNs where voice service was not possible; and
- is not in the list of SNPNs where the N1 mode capability was disabled due to receipt of a reject from the network with 5GMM cause #27 "N1 mode not allowed" in N1 mode as specified in clause 3.1;
if condition 1) above is met then the MS shall attempt to register on that SNPN. If none of the SNPNs meet condition 1) above, the MS shall return to the stored duplicate SNPN selection mode and use the stored duplicate value of RSNPN for further action;
iv) if the registration fails due to "Temporarily not authorized for this SNPN", "Permanently not authorized for this SNPN" or "5GS services not allowed" as specified in 3GPP TS 24.554 [80], then the MS shall update the appropriate list of forbidden SNPN as specified in clause 4.9, and shall either:
A) if the SNPN provides common radio resources needed by the MS to do ProSe communications as specified in 3GPP TS 38.331 [65], perform ProSe communications on the selected SNPN in limited service state. In this case the MS shall not search for available and allowable SNPNs during the duration of ProSe communications;
B) return to the stored duplicate SNPN selection mode and use the stored duplicate value of RSNPN for further action; or
C) perform the action described in iii) again with the choice of SNPNs further excluding the SNPNs on which the MS has failed to register.
Whether the MS performs A), B) or C) above is left up to MS implementation.
v) if the registration fails due to causes other than "Temporarily not authorized for this SNPN" or "Permanently not authorized for this SNPN" or "5GS services not allowed", the MS shall:
- if the handling of the failure requires updating a list of forbidden SNPNs, update the appropriate list (as specified in 3GPP TS 24.501 [64]); and
- if the handling of the failure does not require updating a list of forbidden SNPNs (as specified in 3GPP TS 24.501 [64]), remember the SNPN as a SNPN on which the MS has failed to register;
NOTE 1: How long the MS memorizes the SNPNs on which it has failed to register is implementation dependent.
and the MS shall either:
A1) return to the stored duplicate SNPN selection mode and use the stored duplicate value of RSNPN for further action;
B1) perform the action described in iii) again with the choice of SNPNs further excluding the SNPNs on which the MS has failed to register; or
C1) perform ProSe communications in limited service state on a SNPN advertised by the cell operating in the radio resources provisioned to the MS for ProSe communications as specified in 3GPP TS 24.555 [81] or 3GPP TS 31.102 [40], if registration on this SNPN has previously failed due to "Temporarily not authorized for this SNPN" or "Permanently not authorized for this SNPN" or "5GS services not allowed" as specified in 3GPP TS 24.554 [80] and if this SNPN provides common radio resources needed by the MS to do ProSe communications as specified in 3GPP TS 38.331 [65]. In this case the MS shall not search for available and allowable SNPNs during the duration of ProSe communications;
Whether the MS performs A1), B1) or C1) above is left up to MS implementation.
vi) if the MS is no longer in the coverage of the selected SNPN, then the MS shall either:
A2) perform ProSe communications procedures for MS to use provisioned radio resources as specified in 3GPP TS 24.554 [80]; or
B2) return to the stored duplicate SNPN selection mode and use the stored duplicate value of RSNPN for further action.
Whether the MS performs A2) or B2) above is left up to MS implementation.
vii) if the MS is unable to find a suitable cell on the selected SNPN as specified in 3GPP TS 24.554 [80], then the MS shall either:
A3) if the SNPN provides common radio resources needed by the MS to do ProSe communications as specified in 3GPP TS 38.331 [65], perform ProSe communications on the selected SNPN in limited service state. In this case the MS shall not search for available and allowable SNPNs during the duration of ProSe communications; or
B3) return to the stored duplicate SNPN selection mode and use the stored duplicate value of RSNPN for further action.
Whether the MS performs A3) or B3) above is left up to MS implementation.
viii) if the MS is switched off while on the selected SNPN and switched on again, the MS shall use the stored duplicate value of RSNPN as RSNPN and behave as specified in clause 4.9.3.1;
ix) if the user initiates a SNPN selection while on the selected cell, the MS shall delete the stored duplicate value of SNPN selection mode, use the stored duplicate value of RSNPN as RSNPN and follow the procedures (as specified for switch-on or recovery from lack of coverage) in clause 4.9.3.1. The MS shall delete the stored duplicate value of RSNPN once the MS has successfully registered to the selected SNPN ; and
x) if the MS no longer needs to perform Prose communications, the MS shall return to the stored duplicate SNPN selection mode and use the stored duplicate value of RSNPN for further action.
NOTE 2: If the MS returns to the RSNPN due to a failure to register in the selected SNPN, the upper layers of the MS can trigger SNPN selection again to initiate ProSe communications.
The solution to prevent potential ping-pong between the RSNPN and the SNPN selected for ProSe communications is MS implementation specific.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
3.10 Minimization of service interruption
|
The MS may support Minimization of service interruption (MINT).
MINT is not applicable in SNPNs.
For a PLMN that provides disaster roaming services, if one of the CAG-ID(s) broadcasted by a CAG cell for the PLMN is authorized based on the "Allowed CAG list" included in the entry for the PLMN in the "CAG information list", then the UE may attempt to access the PLMN on the CAG cell for disaster roaming services.
If the MS supports MINT, the MS can be provisioned by the network with:
a) an indication of whether disaster roaming is enabled in the UE, provided by the HPLMN;
b) a "list of PLMN(s) to be used in disaster condition" provided by the HPLMN, consisting of zero or more entries, each containing a PLMN ID. The PLMNs are listed in order of decreasing priority, with the first PLMN being the highest priority PLMN;
c) one or more "list of PLMN(s) to be used in disaster condition", where each VPLMN can provide one "list of PLMN(s) to be used in disaster condition", consisting of zero or more entries, each containing a PLMN ID. The PLMNs are listed in order of decreasing priority, with the first PLMN being the highest priority PLMN;
d) a disaster roaming wait range consisting of a minimum wait time and a maximum wait time;
e) a disaster return wait range consisting of a minimum wait time and a maximum wait time; and
f) an indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN', provided by the HPLMN.
The network may provide the "list of PLMN(s) to be used in disaster condition", the disaster roaming wait range and the disaster return wait range to the UE during a successful registration procedure or a generic UE configuration update procedure. The network may also provide the disaster return wait range to the UE during a network initiated de-registration procedure, an unsuccessful registration procedure or an unsuccessful service request procedure. The HPLMN may also provide an indication of whether disaster roaming is enabled in the UE and an indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN' during a UE parameters update procedure.
The indication of whether disaster roaming is enabled in the UE, the indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN', one or more instances of "list of PLMN(s) to be used in disaster condition" each stored with the PLMN identity of the PLMN that provided it, the disaster roaming wait range and the disaster return wait range provisioned by the network are stored in the non-volatile memory of the ME, as specified in 3GPP TS 24.501 [64] annex C.
In addition, the MS can also be pre-configured with an indication of whether disaster roaming is enabled in the UE, the indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN', a "list of PLMN(s) to be used in disaster condition" provided by the HPLMN, a disaster roaming wait range and a disaster return wait range stored in the USIM (see 3GPP TS 31.102 [40]).
3GPP TS 24.501 [64] annex C specifies the conditions under which the indication of whether disaster roaming is enabled in the UE, the indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN', the one or more "lists of PLMN(s) to be used in disaster condition", the disaster roaming wait range and the disaster return wait range stored in the ME are deleted. Additionally:
a) when a USIM is inserted:
1) if:
i) no indication of whether disaster roaming is enabled in the UE is stored in the non-volatile memory of the ME; or
ii) the SUPI from the USIM does not match the SUPI stored together with the indication of whether disaster roaming is enabled in the UE in the non-volatile memory of the ME;
and the MS has an indication of whether disaster roaming is enabled in the UE stored in the USIM (see 3GPP TS 31.102 [22]), the MS shall store the indication of whether disaster roaming is enabled in the UE from the USIM into a non-volatile memory in the ME together with the SUPI from the USIM, as specified in 3GPP TS 24.501 [64] annex C;
2) if:
i) no disaster roaming wait range is stored in the non-volatile memory of the ME; or
ii) the SUPI from the USIM does not match the SUPI stored together with the disaster roaming wait range in the non-volatile memory of the ME;
and the MS has a disaster roaming wait range stored in the USIM (see 3GPP TS 31.102 [22]), the MS shall store the disaster roaming wait range from the USIM into a non-volatile memory in the ME together with the SUPI from the USIM, as specified in 3GPP TS 24.501 [64] annex C; and
3) if:
i) no disaster return wait range is stored in the non-volatile memory of the ME; or
ii) the SUPI from the USIM does not match the SUPI stored together with the disaster return wait range in the non-volatile memory of the ME;
and the MS has a disaster return wait range stored in the USIM (see 3GPP TS 31.102 [22]), the MS shall store the disaster return wait range from the USIM into a non-volatile memory in the ME together with the SUPI from the USIM, as specified in 3GPP TS 24.501 [64] annex C;
4) if:
i) the indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN' is stored in the non-volatile memory of the ME; or
ii) the SUPI from the USIM does not match the SUPI stored together with the indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN' in the non-volatile memory of the ME;
and the MS has an indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN' stored in the USIM (see 3GPP TS 31.102 [22]), the MS shall store the indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN' from the USIM into a non-volatile memory in the ME together with the SUPI from the USIM, as specified in 3GPP TS 24.501 [64] annex C; and
5) if:
i) no "list of PLMN(s) to be used in disaster condition" provided by the HPLMN is stored in the non-volatile memory of the ME; or
ii) the SUPI from the USIM does not match the SUPI stored together with the "list of PLMN(s) to be used in disaster condition" provided by the HPLMN in the non-volatile memory of the ME;
and the MS has a "list of PLMN(s) to be used in disaster condition" provided by the HPLMN stored in the USIM (see 3GPP TS 31.102 [22]), the MS shall store the "list of PLMN(s) to be used in disaster condition" provided by HPLMN from the USIM into a non-volatile memory in the ME together with the SUPI from the USIM, as specified in 3GPP TS 24.501 [64] annex C;
b) when the ME receives a USAT REFRESH command indicating that:
1) the indication of whether disaster roaming is enabled in the UE stored in the USIM has been updated, the MS shall store the indication of whether disaster roaming is enabled in the UE from the USIM into a non-volatile memory in the ME together with the SUPI from the USIM, as specified in 3GPP TS 24.501 [64] annex C;
2) the disaster roaming wait range stored in the USIM has been updated, the MS shall store the disaster roaming wait range from the USIM into a non-volatile memory in the ME together with the SUPI from the USIM, as specified in 3GPP TS 24.501 [64] annex C;
3) the disaster return wait range stored in the USIM has been updated, the MS shall store the disaster return wait range from the USIM into a non-volatile memory in the ME together with the SUPI from the USIM, as specified in 3GPP TS 24.501 [64] annex C;
4) the indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN' stored in the USIM has been updated, the MS shall store the indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN' from the USIM into a non-volatile memory in the ME together with the SUPI from the USIM, as specified in 3GPP TS 24.501 [64] annex C; or
5) the "list of PLMN(s) to be used in disaster condition" provided by the HPLMN stored in the USIM has been updated, the MS shall store the "list of PLMN(s) to be used in disaster condition" provided by the HPLMN from the USIM into a non-volatile memory in the ME together with the SUPI from the USIM, as specified in 3GPP TS 24.501 [64] annex C; or
NOTE 1: The MS ignores the indication of whether disaster roaming is enabled in the UE stored in the USIM except when the USIM is inserted or when the ME receives a USAT REFRESH command indicating that the indication of whether disaster roaming is enabled in the UE stored in the USIM has been updated.
NOTE 2: The MS ignores the disaster roaming wait range stored in the USIM except when the USIM is inserted or when the ME receives a USAT REFRESH command indicating that the disaster roaming wait range stored in the USIM has been updated.
NOTE 3: The MS ignores the disaster return wait range stored in the USIM except when the USIM is inserted or when the ME receives a USAT REFRESH command indicating that the disaster return wait range stored in the USIM has been updated.
NOTE 4: The MS ignores the indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN' stored in the USIM except when the USIM is inserted or when the ME receives a USAT REFRESH command indicating that the indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN' stored in the USIM has been updated.
NOTE 5: The MS ignores the "list of PLMN(s) to be used in disaster condition" provided by the HPLMN stored in the USIM except when the USIM is inserted or when the ME receives a USAT REFRESH command indicating that the "list of PLMN(s) to be used in disaster condition" provided by the HPLMN stored in the USIM has been updated.
If the MS does not have an indication of whether disaster roaming is enabled in the UE stored in the ME, or the indication of whether disaster roaming is enabled in the UE stored in the ME is set to "Disaster roaming is disabled in the UE", disaster roaming is disabled at the MS. In this case, the MS shall not perform disaster roaming.
Upon selecting a PLMN for disaster roaming, if there is a disaster roaming wait range stored in the ME, and
a) the MS is configured with access identity 1, 2, 12, 13, or 14 and the configured access identity is invalid in the selected PLMN, or
b) the MS is not configured with access identity with 1, 2, 12, 13, or 14,
the MS shall generate a random number within the disaster roaming wait range and start a timer set to the generated random number. While the timer is running, the MS shall not initiate registration with the exception of performing an initial registration for emergency services, in the selected PLMN. If performing an initial registration for emergency services in the selected PLMN, the MS shall keep the timer running. Upon expiration of the timer, if the MS does not have an emergency PDU session, the MS may initiate registration, if still camped on the selected PLMN. Upon expiration of the timer, if the MS has an emergency PDU session, the MS shall initiate registration after release of the emergency PDU session, if still camped on the selected PLMN.
The UE determines that a disaster condition has ended if:
a) the UE has successfully registered over non-3GPP access on a PLMN;
b) the UE has successfully registered with an allowable PLMN;
c) the UE is not registered for disaster roaming services and an NG-RAN cell selected for camping of the selected PLMN broadcasts neither the disaster related indication nor a "list of one or more PLMN(s) with disaster condition for which disaster roaming services is offered by the available PLMN" including the MS determined PLMN with disaster condition; or
NOTE 6: If the UE is registered for disaster roaming services and the serving NG-RAN cell of the registered PLMN broadcasts neither the disaster related indication nor a "list of one or more PLMN(s) with disaster condition for which disaster roaming services is offered by the available PLMN" including the MS determined PLMN with disaster condition, the UE does not determine that disaster condition has ended.
d) the UE is registered for disaster roaming services receives cause value #11 "PLMN not allowed" or #13 "Roaming not allowed in this tracking area" during a registration procedure for mobility registration update or a service request procedure or receives cause value #11 "PLMN not allowed" during a network-initiated de-registration procedure.
NOTE 7: If the network informs the UE registered for disaster roaming services that it is registered for emergency services, then while the UE is registered for emergency services, the UE does not determine that disaster condition has ended.
Upon determining that a disaster condition has ended and selecting the PLMN previously with disaster condition, if a disaster return wait range stored in the ME is provided by:
1) the PLMN providing disaster roaming services; or
2) the selected PLMN,
and
a) the MS configured with access identity 1, 2, 11, 12, 13, 14, or 15 and the access identity is invalid in the selected PLMN, or
b) the MS is not configured with access identity 1, 2, 11, 12, 13, 14, or 15,
the MS shall generate a random number within the disaster return wait range and start a timer set to the generated random number. While the timer is running, the MS shall not initiate registration with the exception of performing an initial registration for emergency services, in the selected PLMN. If performing an initial registration for emergency services in the selected PLMN, the MS shall keep the timer running. Upon expiration of the timer or in the case the timer is not started, if the MS does not have an emergency PDU session, the MS may initiate registration, if still camped on the selected PLMN. Upon expiration of the timer, if the MS has an emergency PDU session, the MS shall initiate registration after release of the emergency PDU session, if still camped on the selected PLMN.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
3.11 Signal level enhanced network selection
|
Signal level enhanced network selection is optionally supported by the home operator.
Signal level enhanced network selection applies only to NB-IoT, GERAN EC-GSM-IoT and Category M1 or M2 of E-UTRA. An MS supporting any, or a combination, of NB-IoT, GERAN EC-GSM-IoT and Category M1 or M2 of E-UTRA shall apply signal level enhanced network selection if the following conditions are fulfilled:
1) The MS is in automatic PLMN selection mode;
2) The MS supports the "Operator controlled signal threshold per access technology" as specified in 3GPP TS 22.011 [19];
3) The MS is configured for using signal level enhanced network selection as specified in 3GPP TS 24.368 [50];
4) The MS is configured for using signal level enhanced network selection as specified in 3GPP TS 31.102 [40]; and
5) The "Operator controlled signal threshold per access technology" is configured in the USIM as specified in 3GPP TS 31.102 [40].
NOTE 1: The usage of the "Operator controlled signal threshold per access technology" is intended only for IoT stationary devices (see 3GPP TS 22.011 [19]).
NOTE 2: "Operator controlled signal threshold per access technology" is not expected to be supported by non-IoT devices.
The HPLMN can configure the MS with an "Operator controlled signal threshold per access technology" stored in the USIM (see 3GPP TS 31.102 [40]), which consists of one or more entries, each containing:
a) a home operator controlled signal threshold; and
b) an access technology.
The "Operator controlled signal threshold per access technology" is specific for a certain access technology and when applicable, applies to all allowable PLMNs with the corresponding access technology combination.
The HPLMN can update the "Operator controlled signal threshold per access technology" via steering of roaming information. When the ME receives a USAT REFRESH command indicating that the "Operator controlled signal threshold per access technology" stored in the USIM has been updated, an MS which applies SENSE shall use the "Operator controlled signal threshold per access technology" provided by the HPLMN for the subsequent PLMN selections.
The "Operator controlled signal threshold per access technology" can also be received from the HPLMN over the control plane steering of roaming mechanism.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4 Overall process structure
| |
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.1 Process goal
|
The aim of the idle mode processes is to ensure that the registered PLMN is the selected PLMN and that the registered SNPN is the selected SNPN.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.2 States description
|
Each of the processes of PLMN selection and SNPN selection, cell selection and location registration can be described by a set of states. The overall state of the mobile is thus a composite of the states of the three processes. In some cases, an event which causes a change of state in one process may trigger a change of state in another process, e.g., camping on a cell in a new registration area triggers an LR request. Except for SNPN selection, the relationship between the processes is illustrated in figure 1 in clause 5.
Except for SNPN selection, the states in which the MS may be, for each of the processes, are described below and illustrated in figures 2a, 2b and 3 in clause 5. For many of the states, a fuller description can be found in other Technical Specifications, and a reference to the Technical Specification is given after the state description.
In the event of any conflict between the diagrams and the text in the present document, the text takes precedence.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.3 List of states
| |
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.3.1 List of states for the PLMN selection process
| |
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.3.1.1 List of states for automatic mode (figure 2a)
|
A1 Trying RPLMN ‑ The MS is trying to perform a Location Registration on the registered PLMN.
A2 On PLMN ‑ The MS has successfully registered on a PLMN.
A3 Trying PLMN ‑ The MS is trying to register on a PLMN in the ordered list of PLMNs.
A4 Wait for PLMNs to appear ‑ There are no allowable and available PLMNs at present and the MS is waiting for one to appear.
A5 HPLMN search in progress ‑ The MS is trying to find if the HPLMN is available.
A6 No SIM ‑ There is no SIM in the MS, or certain LR responses have been received.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.3.1.2 List of states for manual mode (figure 2b)
|
M1 Trying registered PLMN ‑ The MS is trying to perform a Location Registration on the registered PLMN.
M2 On PLMN ‑ The MS has successfully registered on a PLMN.
M3 Not on PLMN ‑ The MS has failed to register on the selected PLMN.
M4 Trying PLMN ‑ The MS is trying to register on a user selected PLMN.
M5 No SIM ‑ There is no SIM in the MS, or certain LR responses have been received.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.3.2 Void
| |
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.3.3 List of states for location registration (figure 3)
|
The states are entered depending on responses to location registration (LR) requests. Independent update states exist for GPRS and for non-GPRS operation in MSs capable of GPRS and non-GPRS services.
L0 Null – The MS is considered in this state when switched off.
L1 Updated ‑ The MS enters this state if an LR request is accepted. The update status is set to "UPDATED". The GPRS and the non-GPRS update state of an MS may enter "Updated" as a result of combined signalling or as a result of individual signalling depending on the capabilities of the network.
L2 Idle, No IMSI ‑ The MS enters this state if an LR request is rejected with cause:
a) IMSI unknown in HLR;
b) illegal ME;
c) illegal MS;
d) GPRS services not allowed,
e) GPRS services and non-GPRS services not allowed,
or if there is no SIM. All update states of an MS enter this state regardless whether received by individual or combined signalling for events b) and c). Event a) has no influence on the GPRS update state. Events b) and c) result in "ROAMING NOT ALLOWED" for the GPRS and/or non-GPRS update status depending on the specific location registration procedure. Event d) results in "ROAMING NOT ALLOWED" for the GPRS update status. Event e) results in "ROAMING NOT ALLOWED" for the GPRS update status and non-GPRS update status.
If a SIM is present, the non-GPRS update status of the SIM is set to "ROAMING NOT ALLOWED".
L3 Roaming not allowed ‑ The MS enters this state if it receives an LR reject message with the cause:
a) PLMN not allowed;
b) Location area not allowed;
c) Tracking area not allowed;
d) Roaming not allowed in this location area;
e) Roaming not allowed in this tracking area;
f) GPRS services not allowed in this PLMN;
g) No suitable cells in location area;
h) No suitable cells in tracking area;
i) Not authorized for this CSG.
Except from event f) all update states of the MS are set to "Roaming not allowed" regardless whether received by individual or combined signalling. Event f) results in "Roaming not allowed" for the GPRS update state only. Event f) has no influence on the non-GPRS update state. The behaviour of the MS in the roaming not allowed state is dependent on the LR reject cause as shown in table 2 in clause 5. Additionally:
- in automatic mode, "PLMN not allowed", "Roaming not allowed in this location area" and "Roaming not allowed in this tracking area" cause the Automatic Network Selection procedure of clause 4.4.3.1.1 to be started; it is also caused by "GPRS services not allowed in this PLMN" when received by a GPRS MS operating in MS operation mode C;
- in manual mode, "PLMN not allowed" and "Roaming not allowed" cause the Manual Network Selection procedure of clause 4.4.3.1.2 to be started; it is also caused by "GPRS services not allowed in this PLMN" when received by a GPRS MS operating in MS operation mode C.
L4 Not updated ‑ The MS enters this state if any LR failure not specified for states L2 or L3 occurs, in which cases the MS is not certain whether or not the network has received and accepted the LR attempt. The non-GPRS update status on the SIM and/or the GPRS update status are set to "NOT UPDATED" depending on the specific location registration procedure and their outcome.
L5 LR request – The MS enters this state when determining that a LR request is to be made.
L6 LR pending – The MS enters this state after having started the LR, waiting for the outcome (response message from the network).
NOTE This clause does not describe all the cases. For more details refer to 3GPP TS 24.008 [23], 3GPP TS 24.301 [23A] and 3GPP TS 24.501 [64].
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.4 PLMN selection process
| |
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.4.1 Introduction
|
There are two modes for PLMN selection, automatic and manual. These are described in clauses 4.4.3 below and illustrated in figures 2a to 2b in clause 5.
NOTE: Figures 2a to 2b in clause 5 do not cover CAG selection aspects.
The MS not operating in SNPN access operation mode over 3GPP access shall perform PLMN selection process.
The MS operating in SNPN access operation mode over 3GPP access shall not perform PLMN selection process.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.4.2 Registration on a PLMN
|
The MS shall perform registration on the PLMN if the MS is capable of services which require registration. In both automatic and manual modes, the concept of registration on a PLMN is used. An MS successfully registers on a PLMN if:
a) the MS has found a suitable cell of the PLMN to camp on; and
b) an LR request from the MS has been accepted in the registration area of the cell on which the MS is camped (see table 1).
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.4.3 PLMN selection
| |
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.4.3.0 General
|
The registration on the selected PLMN and the location registration are only necessary if the MS is capable of services which require registration. Otherwise, the PLMN selection procedures are performed without registration.
The ME shall utilise all the information stored in the SIM related to the PLMN selection; e.g. "HPLMN Selector with Access Technology", "User Controlled PLMN Selector with Access Technology", "Forbidden PLMNs", "Equivalent HPLMN", see 3GPP TS 31.102 [40]. The ME shall also utilise the extension of the "forbidden PLMNs" list that it has stored locally on the ME if available.
The ME shall either utilise the "Operator controlled PLMN Selector with Access Technology" that it has stored locally on the ME, or the Operator controlled PLMN Selector with Access Technology" stored in the SIM, for the purposes of PLMN selection.
The "HPLMN Selector with Access Technology", "User Controlled PLMN Selector with Access Technology" and "Operator Controlled PLMN Selector with Access Technology" data files in the SIM include associated access technologies for each PLMN entry, see 3GPP TS 31.102 [40]. The PLMN/access technology combinations are listed in priority order. If an entry indicates more than one access technology, then no priority is defined for the access technologies within this entry and the priority applied to each access technology within this entry is an implementation issue. If no particular access technology is indicated in an entry, it shall be assumed that all access technologies supported by the ME apply to the entry. If an entry only indicates access technologies not supported by the ME, the entry shall be ignored. If an entry indicates at least one access technology supported by the ME, the entry shall be used in the PLMN selection procedures if the other criteria defined for the specific PLMN selection procedures are fulfilled.
The Mobile Equipment stores a list of "equivalent PLMNs". This list is replaced or deleted at the end of each location update procedure, routing area update procedure, GPRS attach procedure, tracking area update procedure, EPS attach procedure, and registration procedure. The list is deleted by an MS attached for emergency bearer services or for access to RLOS after detach or registered for emergency services after de-registration. The stored list consists of a list of equivalent PLMNs as downloaded by the network plus the PLMN code of the registered PLMN that downloaded the list. All PLMNs in the stored list, in all access technologies supported by the PLMN, are regarded as equivalent to each other for PLMN selection, cell selection/re-selection and handover.
When the MS reselects to a cell in a shared network, and the cell is a suitable cell for multiple PLMN identities received on the BCCH or on the EC-BCCH the AS indicates these multiple PLMN identities to the NAS according to 3GPP TS 44.018 [34], 3GPP TS 44.060 [39], 3GPP TS 25.304 [32], 3GPP TS 36.304 [43] and 3GPP TS 38.304 [61]. The MS shall choose one of these PLMNs. If the registered PLMN is available among these PLMNs, the MS shall not choose a different PLMN.
The MS shall not use the PLMN codes contained in the "HPLMN Selector with Access Technology" data file.
It is possible for the home network operator to identify alternative Network IDs as the HPLMN. If the EHPLMN list is present, and not empty, the entries in the EHPLMN list are used in the network selection procedures. When attempting to select a network the highest priority EHPLMN that is available shall be selected. If the EHPLMN list is present and is empty or if the EHPLMN list is not present, the HPLMN derived from the IMSI is used for network selection procedures.
NOTE 1: The "HPLMN Selector with Access Technology" data file is only used by the MS to get the HPLMN access technologies related to the HPLMN code which corresponds to the PLMN code included in the IMSI if the EHPLMN list is not present or is empty. If the EHPLMN list is present then this data field is applicable to all the entries within the EHPLMN list.
NOTE 2: Different GSM frequency bands (e.g. 900, 1800, 1900, 400) are all considered GSM access technology. An MS supporting more than one band should scan all the bands it's supports when scanning for GSM frequencies. However GSM COMPACT systems which use GSM frequency bands but with the CBPCCH broadcast channel are considered as a separate access technology from GSM.
NOTE 3: The inclusion of the HPLMN derived from the IMSI in the EHPLMN list is allowed. The priority of the HPLMN derived from the IMSI is given by its position in the EHPLMN list, see 3GPP TS 31.102 [40].
The MS may support minimization of service interruption (MINT).
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.4.3.1 At switch‑on or recovery from lack of coverage
| |
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.4.3.1.0 General
|
At switch on, following recovery from lack of coverage, or when the MS stops operating in the SNPN access operation mode over 3GPP access:
a) if:
- signal level enhanced network selection is not applicable (see clause 3.11), or
- the MS has stopped applying signal level enhanced network selection according to requirement v) of clause 4.4.3.1.1,
then the MS shall select the registered PLMN or equivalent PLMN (if it is available) using all access technologies that the MS is capable of, without considering the "Operator controlled signal threshold per access technology" stored in the USIM; or
b) if:
- signal level enhanced network selection is applicable (see clause 3.11), and
- the received signal quality from a candidate PLMN/access technology combination comprising of a registered PLMN or an equivalent PLMN (if it is available) is equal to or greater than the "Operator controlled signal threshold per access technology" of the access technology configured in the USIM,
then the MS shall select the registered PLMN or equivalent PLMN (if it is available) and the access technology for which the received signal quality is equal to or greater than the "Operator controlled signal threshold per access technology" stored in the USIM. If for the registered PLMN or equivalent PLMN there are two or more access technologies for which the received signal quality is equal to or greater than the "Operator controlled signal threshold per access technology" stored in the USIM, it is up to implementation which access technology is selected by the MS,
and if necessary (in the case of recovery from lack of coverage, see clause 4.5.2), attempts to perform a Location Registration.
NOTE 1: The MS in automatic network selection mode can end the PLMN search procedure once the registered PLMN or equivalent PLMN is found on an access technology.
NOTE 2: An MS in automatic network selection mode can use location information to determine which PLMNs can be available in its present location.
EXCEPTION: As an alternative option to this, if the MS is in automatic network selection mode and it finds coverage of an EHPLMN, the MS may register to that EHPLMN and not return to the registered PLMN or equivalent PLMN. If the EHPLMN list is not present or is empty, and the HPLMN is available, the MS may register on the HPLMN and not return to the registered PLMN or equivalent PLMN. The operator shall be able to control by SIM configuration whether an MS that supports this option is permitted to perform this alternative behaviour. If signal level enhanced network selection is applicable (see clause 3.11), the MS may register to that EHPLMN or HPLMN only over an access technology for which the received signal quality is equal to or greater than the "Operator controlled signal threshold per access technology" stored in the USIM.
EXCEPTION: As an alternative option to this, if the MS is in automatic network selection mode, the MS has a list of "PLMNs where registration was aborted due to SOR" and the registered PLMN is part of the list of "PLMNs where registration was aborted due to SOR", the MS may choose not to return to the registered PLMN or equivalent PLMN and proceed as defined in clause 4.4.3.1.1 with the exception that in iii), the MS considers PLMNs which are in the list of "PLMNs where registration was aborted due to SOR" as lowest priority.
EXCEPTION: As an alternative option to this, if the MS supports eCall and normal call (see 3GPP TS 31.102 [40]), the MS is in automatic network selection mode and receives a request from upper layer to start an eCall, the MS may proceed as defined in clause 4.4.3.1.1 for the MS in eCall only mode.
EXCEPTION: In A/Gb mode an MS with voice capability, shall not search for CPBCCH carriers. In A/Gb mode an MS not supporting packet services shall not search for CPBCCH carriers.
If successful registration is achieved, the MS indicates the selected PLMN.
If:
- there is no registered PLMN;
- registration is not possible due to the PLMN being unavailable or registration failure; or
- signal level enhanced network selection is applicable (see clause 3.11) and the received signal quality of all access technologies (if the MS is capable of and if it is available) from the registered PLMN or equivalent PLMN (if available) is lower than the "Operator controlled signal threshold per access technology" stored in the USIM of the corresponding access technology,
then the MS follows one of the following two procedures depending on its PLMN selection operating mode. At switch on, if the MS provides the optional feature of user preferred PLMN selection operating mode at switch on then this operating mode shall be used. Otherwise, the MS shall use the PLMN selection mode that was used before switching off.
EXCEPTION: At switch on, if the MS is in manual mode and neither registered PLMN nor PLMN that is equivalent to it is available, but EHPLMN is available, then instead of performing the manual network selection mode procedure of clause 4.4.3.1.2 the MS may select and attempt registration on the highest priority EHPLMN. If the EHPLMN list is not available or is empty and the HPLMN is available, then the MS may select and attempt registration on the HPLMN. If the MS supports CAG and needs to select or attempt registration on the highest priority EHPLMN or HPLMN, the MS follows network selection procedures of clause 4.4.3.1.1 bullet m). The MS shall remain in manual mode.
NOTE 3: If successful registration is achieved, then the current serving PLMN becomes the registered PLMN and the MS does not store the previous registered PLMN for later use.
EXCEPTION: If registration is not possible on recovery from lack of coverage due to the registered PLMN being unavailable, an MS attached to GPRS services, attached via E-UTRAN or registered via the NG-RAN may, optionally, continue looking for the registered PLMN for an implementation dependent time.
NOTE 4: An MS attached to GPRS services, attached via E-UTRAN or registered via the NG-RAN should use the above exception only if one or more PDP contexts, PDN connections or PDU sessions are currently active.
EXCEPTION: At switch on, if the RPLMN is a PLMN with which the MS was registered for disaster roaming services and the MS is registered via non-3GPP access connected to 5GCN or an NG-RAN cell of the RPLMN broadcasts neither the disaster related indication nor a "list of one or more PLMN(s) with disaster condition for which disaster roaming services is offered by the available PLMN" including the UE determined PLMN with disaster condition or an allowable PLMN is available then the MS will ignore RPLMN and its equivalent PLMN.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.4.3.1.1 Automatic Network Selection Mode Procedure
|
The MS selects and attempts registration on other PLMN/access technology combinations, if available and, for bullets i, ii, iii, iv, v, allowable, in the following order:
i) either the HPLMN (if the EHPLMN list is not present or is empty) or the highest priority EHPLMN that is available (if the EHPLMN list is present);
ii) each PLMN/access technology combination in the "User Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order);
iii) each PLMN/access technology combination in the "Operator Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order) or stored in the ME (in priority order);
iv) other PLMN/access technology combinations with received high quality signal in random order;
NOTE 1: High quality signal is defined in the appropriate AS specification.
v) other PLMN/access technology combinations in order of decreasing signal quality.
vi) PLMN/NG-RAN combinations for any forbidden PLMNs broadcasting the PLMN ID of the UE determined PLMN with disaster condition or broadcasting the disaster related indication and matching the below conditions:
a) if the indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN' is set to true:
- each PLMN in the "list of PLMN(s) to be used in disaster condition" stored in the ME which is associated with the PLMN ID of the UE determined PLMN with disaster condition, if any, ordered based on this list; otherwise
- if the ME does not have a stored "list of PLMN(s) to be used in disaster condition" associated with the PLMN ID of the UE determined PLMN with disaster condition, each PLMN in the "list of PLMN(s) to be used in disaster condition" stored in the ME which is associated with the PLMN ID of the HPLMN, if any, ordered based on this list.
b) if the indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN' is set to false:
- each PLMN in the "list of PLMN(s) to be used in disaster condition" stored in the ME which is associated with the HPLMN, if any, ordered based on this list.
vii) PLMN /NG-RAN combinations for other forbidden PLMNs broadcasting the PLMN ID of the UE determined PLMN with disaster condition or broadcasting the disaster related indication, in random order.
When following the above procedure the following requirements apply:
a) An MS with voice capability shall ignore PLMNs for which the MS has identified at least one GSM COMPACT.
b) In A/Gb mode or GSM COMPACT, an MS with voice capability, or an MS not supporting packet services shall not search for CPBCCH carriers.
c) In ii and iii, the MS should limit its search for the PLMN to the access technology or access technologies associated with the PLMN in the appropriate PLMN Selector with Access Technology list (User Controlled or Operator Controlled selector list).
An MS using a SIM without access technology information storage (i.e. the "User Controlled PLMN Selector with Access Technology" and the "Operator Controlled PLMN Selector with Access Technology" data files are not present) shall instead use the "PLMN Selector" data file, for each PLMN in the "PLMN Selector" data file, the MS shall search for all access technologies it is capable of. The priority ordering amongst the access technologies is implementation dependent.
d) In iv, v, vi and vii, the MS shall search for all access technologies it is capable of, before deciding which PLMN to select.
e) In ii, and iii, a packet only MS which supports GSM COMPACT, but using a SIM without access technology information storage (i.e. the "User Controlled PLMN Selector with Access Technology" and the "Operator Controlled PLMN Selector with Access Technology" data files are not present) shall instead use the "PLMN Selector" data file, for each PLMN in the "PLMN Selector" data file, the MS shall search for all access technologies it is capable of and shall assume GSM COMPACT access technology as the lowest priority radio access technology.
f) In i, the MS shall search for all access technologies it is capable of. No priority is defined for the preferred access technology and the priority is an implementation issue, but "HPLMN Selector with Access Technology" data file on the SIM may be used to optimise the procedure.
g) In i, an MS using a SIM without access technology information storage (i.e. the "HPLMN Selector with Access Technology" data file is not present) shall search for all access technologies it is capable of. The priority ordering amongst the access technologies is implementation dependent. A packet only MS which supports GSM COMPACT using a SIM without access technology information storage shall also assume GSM COMPACT access technology as the lowest priority radio access technology.
NOTE 2: For f) and g), the MS in automatic network selection mode can end the PLMN search procedure once the HPLMN or the highest priority EHPLMN is found on an access technology.
NOTE 3: For i, ii and iii, the MS can use location information to determine which PLMNs can be available in its present location.
h) In v, the MS shall order the PLMN/access technology combinations in order of decreasing signal quality within each access technology. The order between PLMN/access technology combinations with different access technologies is an MS implementation issue.
NOTE 4: Requirements a) and b) apply also to requirement d), so a GSM voice capable MS should not search for GSM COMPACT PLMNs, even if capable of GSM COMPACT.
NOTE 5: Requirements a) and b) apply also to requirement f), so a GSM voice capable MS should not search for GSM COMPACT PLMNs, even if this is the only access technology on the "HPLMN Selector with Access Technology" data file on the SIM.
i) In i to vii, the MS shall not consider PLMNs where voice service was not possible as PLMN selection candidate, unless such PLMN is available in GERAN or UTRAN or no other allowed PLMN is available.
j) In i to v, if the MS only supports EMM-REGISTERED without PDN connection (see 3GPP TS 24.301 [23A]), the MS shall not consider PLMNs which do not advertise support of EMM-REGISTERED without PDN connection.
k) In i to v, if the MS only supports control plane CIoT EPS optimization (see 3GPP TS 24.301 [23A]) and the MS camps on a E-UTRA cell which is not NB-IoT cell (see 3GPP TS 36.304 [43], 3GPP TS 36.331 [42]), the MS shall not consider PLMNs which do not advertise support of EPS services with control plane CIoT EPS optimization.
l) In i to vii, if the MS is in eCall only mode, the MS shall not consider PLMN/access technology combinations which do not advertise support for eCall over IMS, unless such PLMNs are available in GERAN or UTRAN.
NOTE 6: As an implementation option, an MS in eCall only mode that was not able to select any PLMN according to l) can perform a second iteration of i to v with no restriction.
m) In i to vii, if the MS supports CAG and:
1) is provisioned with a non-empty "CAG information list", the MS shall consider a PLMN indicated by an NG-RAN cell only if:
A) the cell is a CAG cell and broadcasts a CAG-ID for the PLMN such that there exists an entry with the PLMN ID of the PLMN in the "CAG information list" and the CAG-ID is authorized based on the "Allowed CAG list" of the entry; or
B) the cell is not a CAG cell and:
- there is no entry with the PLMN ID of the PLMN in the "CAG information list"; or
- there exists an entry with the PLMN ID of the PLMN in the "CAG information list" but the "indication that the MS is only allowed to access 5GS via CAG cells" is not included in the entry; or
2) is provisioned with an empty "CAG information list" or is not provisioned with a "CAG information list", the MS shall consider a PLMN indicated by an NG-RAN cell only if the cell is not a CAG cell.
n) In i to vii, if the MS only supports control plane CIoT 5GS optimization (see 3GPP TS 23.501 [62]) and the MS camps on an E-UTRA cell connected to 5GCN, which is not NB-IoT cell (see 3GPP TS 36.304 [43], 3GPP TS 36.331 [42]), the MS shall not consider PLMNs which do not advertise support of 5GS services with control plane CIoT 5GS optimization.
o) In i to vii, if the MS supports CIoT 5GS optimizations, the MS shall not consider the PLMN/access technology combinations for which the MS preferred CIoT network behaviour is not advertised as supported by the PLMN/access technology combination (see 3GPP TS 24.501 [64]).
NOTE 7: As an implementation option, the MS supporting CIoT 5GS optimizations that was not able to select any PLMN according to o) can perform a second iteration of i to v with no restriction.
p) In iii, the MS shall use the PLMN/access technology combination in the "Operator Controlled PLMN Selector with Access Technology" stored in the ME, if the last update of the "Operator Controlled PLMN Selector with Access Technology" was due to receiving steering of roaming information containing the "list of preferred PLMN/access technology combinations" (see annex C) and storing it in the ME. Otherwise, the MS shall use the "Operator Controlled PLMN Selector with Access Technology" list retrieved from the SIM.
q1) for vi and vii, if a forbidden PLMN is broadcasting the "list of one or more PLMN(s) with disaster condition for which disaster roaming services is offered by the available PLMN", the MS shall determine the UE determined PLMN with disaster condition as follows:
i) if the MS's RPLMN is included in any "list of one or more PLMN(s) with disaster condition for which disaster roaming services is offered by the available PLMN" broadcast by any NG-RAN cell and is allowable, the MS shall consider that the MS's RPLMN is the UE determined PLMN with disaster condition; or
ii) if the MS's RPLMN is not included in any "list of one or more PLMN(s) with disaster condition for which disaster roaming services is offered by the available PLMN" broadcast by any NG-RAN cell or the MS's RPLMN is not allowable or the MS does not have a RPLMN (see table 1), the MS shall determine the UE determined PLMN with disaster condition from PLMNs:
- in the "list of one or more PLMN(s) with disaster condition for which disaster roaming services is offered by the available PLMN" broadcast by any NG-RAN cell; and
- which are allowable;
in the following order:
- either the HPLMN (if the EHPLMN list is not present or is empty) or the highest priority EHPLMN that is available (if the EHPLMN list is present);
- each PLMN in the "User Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order);
- each PLMN in the "Operator Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order) or stored in the ME (in priority order); and
- other PLMNs.
q2) for vi and vii, if a forbidden PLMN is broadcasting the "disaster related indication", the MS shall attempt to determine the UE determined PLMN with disaster condition as follows:
1) if the country of the MS's RPLMN matches the country of a PLMN for which any NG-RAN cell broadcasts the "disaster related indication" and the MS's RPLMN is allowable, the MS shall consider that the MS's RPLMN is the UE determined PLMN with disaster condition; or
2) if the country of the MS's RPLMN does not match the country of any PLMN for which any NG-RAN cell broadcasts the "disaster related indication" or the MS's RPLMN is not allowable, the MS shall determine the UE determined PLMN with disaster condition from allowable PLMN(s) where the country of allowable PLMN(s) matches the country of a PLMN for which any NG-RAN cell broadcasts the "disaster related indication" in the following order:
- either the HPLMN (if the EHPLMN list is not present or is empty) or the highest priority EHPLMN that is available (if the EHPLMN list is present);
- each PLMN in the "User Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order);
- each PLMN in the "Operator Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order) or stored in the ME (in priority order).
r) The MS shall perform vi and vii to select a PLMN for disaster roaming services only if:
1) the MS supports MINT;
2) the indication of whether disaster roaming is enabled in the UE is set to "Disaster roaming is enabled in the UE";
3) there is no available PLMN which is allowable;
4) the MS is not in 5GMM-REGISTERED state over non-3GPP access and not in 5GMM-CONNECTED mode over non-3GPP access (see 3GPP TS 24.501 [64]);
4a) the MS does not have a PDN connection via an ePDG connected to EPC; and
5) an NG-RAN cell of the PLMN or of a shared network where the PLMN is available:
A) broadcasts the disaster related indication for the PLMN. The disaster related indication broadcasted by the NG-RAN cell for the PLMN indicates that the PLMN is accessible for disaster inbound roamers, that this PLMN accepts disaster inbound roamers from any PLMN(s) other than the PLMN(s) available on the NG-RAN cell, and that a disaster condition applies to all PLMN(s) other than the PLMN(s) available on the NG-RAN cell in the location of the broadcast. If the disaster related indication is broadcasted, the disaster inbound roamers attempt to determine the UE determined PLMN with disaster condition as per bullet q2); or
NOTE 8: In case of a shared network, the disaster related indication is broadcasted per PLMN.
B) broadcasts a "list of one or more PLMN(s) with disaster condition for which disaster roaming services is offered by the available PLMN" which includes the UE determined PLMN with disaster condition as determined in bullet q1).
s) In i to vii, if the RedCap UE camps on an NR cell connected to 5GCN, the MS shall not consider PLMNs which do not advertise support of RedCap UE.
s1) In i to vii, if the eRedCap UE camps on an NR cell connected to 5GCN, the MS shall not consider PLMNs which do not advertise support of eRedCap UE.
t) In i to vii, if the MS detects a PLMN in satellite NG-RAN access technology which fulfils the conditions related to the list of "PLMNs not allowed to operate at the present UE location" as defined in clause 3.1, it shall not consider the PLMN as PLMN selection candidate for satellite NG-RAN access technology.
u) In i to vii, if the MS detects a PLMN in a satellite E-UTRAN access technology which fulfils the conditions related to the list of "PLMNs not allowed to operate at the present UE location" as defined in clause 3.1, it shall not consider the PLMN as PLMN selection candidate for the satellite E-UTRAN access technology.
v) In i), ii), iii), and v), if:
- signal level enhanced network selection is applicable (see clause 3.11); and
- the received signal quality of the candidate PLMN/access technology combination is lower than the threshold value indicated for the access technology in the "Operator controlled signal threshold per access technology" stored in the USIM.
the MS shall not consider the PLMN(s) in i) and PLMN/access technology combination(s) in ii), iii) and v) as selection candidate. If the received signal quality from none of the candidate PLMN(s) or PLMN/access technology combination(s) is equal to or greater than the "Operator controlled signal threshold per access technology" stored in the USIM, the MS shall stop applying signal level enhanced network selection and repeat the network selection procedure as specified in clause 4.4.3.1.
If successful registration is achieved, the MS indicates the selected PLMN.
If registration cannot be achieved because no PLMNs are available and allowable, and the MS does not support access to RLOS, the MS indicates "no service" to the user, waits until a new PLMN is available and allowable and then repeats the procedure.
If there were one or more PLMNs which were available and allowable, but an LR failure made registration on those PLMNs unsuccessful or an entry in any of the lists "forbidden location areas for roaming", "forbidden tracking areas for roaming", "5GS forbidden tracking areas for roaming", "forbidden location areas for regional provision of service", "forbidden tracking areas for regional provision of service", "5GS forbidden tracking areas for regional provision of service", "CAG information list", or "PLMNs not allowed to operate at the present UE location" prevented a registration attempt, the MS selects the first such PLMN again and enters a limited service state.
If there were one or more PLMN/NG-RAN combinations which were available and which are forbidden PLMNs broadcasting the PLMN ID of the UE determined PLMN with disaster condition or broadcasting the disaster related indication, but an LR failure made registration on those PLMNs unsuccessful due to "Disaster roaming for the determined PLMN with disaster condition not allowed", the MS selects the first such PLMN again and enters a limited service state.
If:
- the MS supports access to RLOS;
- either the UICC containing the USIM is not present in the MS, or the UICC containing the USIM is present in the MS and the MCC part of the IMSI in the USIM is present in the RLOS allowed MCC list configured in the USIM (see 3GPP TS 31.102 [40]) or in the ME (see 3GPP TS 24.368 [50]);
- one or more PLMNs offering access to RLOS has been found;
- registration cannot be achieved on any PLMN; and
- the MS is in limited service state,
the MS shall select a PLMN offering access to RLOS as follows:
a) if at least one preferred PLMN exists based on the RLOS preferred PLMN list configured in the USIM (see 3GPP TS 31.102 [40]) or in the ME (see 3GPP TS 24.368 [50]) and the MCC part of the preferred PLMN ID is present in the RLOS allowed MCC list configured in the USIM (see 3GPP TS 31.102 [40]) or in the ME (see 3GPP TS 24.368 [50]), the MS shall select the preferred PLMN offering access to RLOS and indicate the selected preferred PLMN for access to RLOS; and
b) if none of the preferred PLMNs for access to RLOS is available, the MS shall evaluate the remaining PLMNs offering access to RLOS that are not in the RLOS preferred PLMN list. If the MCC part of a PLMN ID is present in the RLOS allowed MCC list configured in the USIM (see 3GPP TS 31.102 [40]) or in the ME (see 3GPP TS 24.368 [50]), the MS shall select this PLMN and indicate the selected PLMN for access to RLOS.
If registration cannot be achieved because no PLMNs are available and allowable, and if no PLMN offering access to RLOS has been found, or none of the PLMNs offering access to RLOS is allowed to be accessed according to the RLOS allowed MCC list configured in the USIM (see 3GPP TS 31.102 [40]) or in the ME (see 3GPP TS 24.368 [50]), or the MS does not support access to RLOS, the MS indicates "no service" to the user, waits until a new PLMN is available and then repeats the procedure.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.4.3.1.2 Manual Network Selection Mode Procedure
|
The MS indicates whether there are any PLMNs, which are available using all supported access technologies. This includes PLMNs in the "forbidden PLMNs" list, "forbidden PLMNs for GPRS service" list, PLMNs which only offer services not supported by the MS, and the list of "PLMNs not allowed to operate at the present UE location". An MS which supports GSM COMPACT shall also indicate GSM COMPACT PLMNs (which use PBCCH).
If displayed, PLMNs meeting the criteria above are presented in the following order:
i) either the HPLMN (if the EHPLMN list is not present or is empty) or, if one or more of the EHPLMNs are available then based on an optional data field on the SIM either only the highest priority available EHPLMN is to be presented to the user or all available EHPLMNs are presented to the user in priority order. If the data field is not present on the SIM, then only the highest priority available EHPLMN is presented;
ii) PLMN/access technology combinations contained in the " User Controlled PLMN Selector with Access Technology " data file in the SIM (in priority order);
iii) PLMN/access technology combinations contained in the "Operator Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order) or stored in the ME (in priority order);
iv) other PLMN/access technology combinations with received high quality signal in random order;
NOTE 1: High quality signal is defined in the appropriate AS specification.
v) other PLMN/access technology combinations in order of decreasing signal quality.
In ii and iii, an MS using a SIM without access technology information storage (i.e. the "User Controlled PLMN Selector with Access Technology" and the "Operator Controlled PLMN Selector with Access Technology" data files are not present) shall instead present the PLMNs contained in the "PLMN Selector" data file in the SIM (in priority order).
In v, requirement h) in clause 4.4.3.1.1 applies.
In i to v, requirements j), k) and l) in clause 4.4.3.1.1 apply.
In iii, requirement p) in clause 4.4.3.1.1 applies.
In GSM COMPACT, the non-support of voice services shall be indicated to the user.
The HPLMN may provide on the SIM additional information on the available PLMNs. If this information is provided, then the MS shall indicate it to the user. This information, provided as free text may include:
- preferred partner,
- roaming agreement status,
- supported services
Furthermore, the MS may indicate whether the available PLMNs are present on the EHPLMN list, the Forbidden list, the User Controlled PLMN List or the Operator Controlled PLMN List. The MS may also indicate that the PLMN is not present on any of these lists.
If:
- the MS supports MINT;
- the MS is not registered via non-3GPP access connected to 5GCN;
- the MS has detected that the RPLMN is a UE determined PLMN with disaster condition as broadcasted by an NG-RAN cell of an available PLMN(s) (see clause 4.4.3.1.1);
- only forbidden PLMN(s) are available; and
- the MS receives indication that some of the forbidden PLMN(s) provide disaster roaming services to the MS(s) of the RPLMN (see clause 4.4.3.1.1),
then the MS may indicate to the user that those PLMN(s) support disaster roaming services.
In i to v, if the MS supports CAG, for each PLMN/access technology combination of NG-RAN access technology, the MS shall present to the user:
a) the PLMN/access technology combination and a list of CAG-IDs composed of one or more CAG-IDs such that for each CAG-ID:
1) there is an available CAG cell which broadcasts the CAG-ID for the PLMN; and
2) the following is true:
i) there exists an entry with the PLMN ID of the PLMN in the "CAG information list" and the CAG-ID is authorized based on the "Allowed CAG list" of the entry; or
ii) the available CAG cell broadcasting the CAG-ID for the PLMN also broadcasts that the PLMN allows a user to manually select the CAG-ID.
For each of the presented CAG-ID, the MS may indicate to the user whether the CAG-ID is authorized based on the "Allowed CAG list" stored in the UE; and
b) the PLMN/access technology combination without a list of CAG-IDs, if there is an available NG-RAN cell which is not a CAG cell for the PLMN. If there exists an entry for the presented PLMN in the "CAG information list" and the entry includes an "indication that the MS is only allowed to access 5GS via CAG cells", the MS may indicate to the user that the MS is only allowed to access the PLMN via CAG cells.
If the NAS receives a human-readable network name associated with a CAG-ID and a PLMN ID from the AS, the human-readable network name shall be sent along with the CAG-ID and PLMN ID to the upper layer for use in manual CAG selection.
NOTE 2: A human-readable network name can be broadcasted per CAG-ID and PLMN ID by a CAG cell.
Upon selection of a PLMN (and CAG-ID if the user selected a desired CAG-ID as well) by the user, the NAS shall provide the AS with the selected PLMN ID (and CAG-ID if the user selected a desired CAG-ID as well or an indication to select a non-CAG cell if the user did not select any CAG-ID) and the MS initiates registration on this PLMN (and on a cell which broadcasts the CAG-ID if the user selected a desired CAG-ID as well) using the access technology chosen by the user for that PLMN or using the highest priority available access technology for that PLMN, if the associated access technologies have a priority order (this may take place at any time during the presentation of PLMNs). For such a registration, the MS shall ignore the contents of the "forbidden location areas for roaming", "forbidden tracking areas for roaming", "5GS forbidden tracking areas for roaming", "forbidden location areas for regional provision of service", "forbidden tracking areas for regional provision of service", "5GS forbidden tracking areas for regional provision of service", "forbidden PLMNs for GPRS service", "PLMNs not allowed to operate at the present UE location", "forbidden PLMNs" lists and the list of "PLMNs with associated access technology restrictions". Also for such a registration, if the NAS has provided the AS with an indication to select:
- a non-CAG cell, the MS shall ignore the "indication that the MS is only allowed to access 5GS via CAG cells", if any, in the "CAG information list" for the selected PLMN; or
- a selected CAG-ID and the CAG-ID is not authorized based on the "Allowed CAG list" associated with that PLMN in the "CAG information list", the MS shall consider the selected CAG-ID of the selected PLMN as authorized based on the "Allowed CAG list" for the selected PLMN for this registration attempt.
NOTE 3: It is an MS implementation option whether to indicate access technologies to the user. If the MS does display access technologies, then the access technology selected by the user is only used for initial registration on the selected PLMN. If the MS does not display access technologies, then the access technology chosen for a particular PLMN should be the highest priority available access technology for that PLMN, if the associated access technologies have a priority order, and is only used for initial registration.
If the MS has, or is establishing, a PDU session for emergency services, a PDN connection for emergency bearer services or a PDP context for emergency bearer services or CS emergency call, being registered for emergency services or having an ongoing emergency services fallback procedure, manual network selection shall not be performed.
After selection of a PLMN and CAG-ID, if the AS does not provide an indication of finding a cell belonging to the selected PLMN and which broadcasts the selected CAG-ID for the registration procedure (see 3GPP TS 38.304 [40]), then:
i) the MS shall indicate to user that it cannot find the selected PLMN and CAG-ID; and
ii) If there is an "indication that the MS is only allowed to access 5GS via CAG cells" in the "CAG information list" for the selected PLMN, the MS may attempt to camp on a suitable CAG cell broadcasting a CAG-ID authorized based on the "Allowed CAG list" for the selected PLMN or an acceptable cell, otherwise the MS may attempt to camp on a suitable cell belonging to the selected PLMN (i.e. a non-CAG cell or a CAG cell broadcasting a CAG-ID authorized based on the "Allowed CAG list" for the selected PLMN) or an acceptable cell.
Once the MS has registered on a PLMN selected by the user, the MS shall not automatically register on a different PLMN unless:
i) the new PLMN is declared as an equivalent PLMN by the registered PLMN. If the MS is registered for disaster roaming services, the UE shall also detect that the new PLMN offers disaster roaming services to the UE determined PLMN with disaster condition as broadcasted by the NG-RAN cell of the new PLMN (see clause 4.4.3.1.1) and that the UE determined PLMN with disaster condition in the old PLMN is also a UE determined PLMN with disaster condition in the new PLMN;
ii) the user selects automatic mode;
iii) the user initiates an emergency call while the MS is in limited service state and either the network does not broadcast the indication of support of emergency calls in limited service state, the registration request for emergency services is rejected by the network or the attach request for emergency bearer services is rejected by the network; or
iv) the user initiates access to RLOS, while the MS is in limited service state and either the network does not broadcast the indication of support of RLOS in limited service state, or the EPS attach request for access to RLOS is rejected by the network, or the EPS tracking area update request for access to RLOS is rejected by the network.
NOTE 4: If case iii) or iv) occurs, the MS can provide an indication to the upper layers that the MS has exited manual network selection mode.
NOTE 5: If case iii) or iv) occurs, then as an implementation option, MS memorizes the PLMN selected by the user before exiting the manual network selection mode. Once, the emergency call is ended or user initiated access to RLOS is ended, MS moves to the manual network selection mode and selects the memorized PLMN.
Once the MS has registered on a PLMN selected by the user, the MS may automatically register on a different PLMN if:
1) the MS supports MINT;
2) the indication of whether disaster roaming is enabled in the UE is set to "Disaster roaming is enabled in the UE";
3) there is no available PLMN which is declared as an equivalent PLMN by the RPLMN; and
4) the RPLMN of the MS is considered as the UE determined PLMN with disaster condition based on the determination of the UE determined PLMN with disaster condition as specified in clause 4.4.3.1.1.
NOTE 6: If the above case occurs, the MS can provide an indication to the upper layers that the MS has exited manual network selection mode.
NOTE 7: If the above case occurs, then as an implementation option, MS memorizes the PLMN selected by the user before exiting the manual network selection mode. When the UE determines that a disaster condition has ended, MS moves to the manual network selection mode and selects the memorized PLMN.
If the user does not select a PLMN (or PLMN and CAG-ID), the selected PLMN shall be the one that was selected before the PLMN selection procedure started. If no such PLMN was selected or that PLMN is no longer available, then the MS shall attempt to camp on any acceptable cell and enter the limited service state.
If:
- the MS supports access to RLOS;
- either the UICC containing the USIM is not present in the MS, or the UICC containing the USIM is present in the MS and the MCC part of the IMSI in the USIM is present in the RLOS allowed MCC list configured in the USIM (see 3GPP TS 31.102 [40]) or in the ME (see 3GPP TS 24.368 [50]);
- one or more PLMNs offering access to RLOS has been found;
- registration cannot be achieved on any PLMN; and
- the MS is in limited service state,
the MS indicates the PLMNs offering access to RLOS, presented in the following order:
i) PLMNs contained in the RLOS preferred PLMN list configured in the USIM (see 3GPP TS 31.102 [40]) or in the ME (see 3GPP TS 24.368 [50]) (in priority order) if the MCC part of the preferred PLMN ID is present in the RLOS allowed MCC list configured in the USIM (see 3GPP TS 31.102 [40]) or in the ME (see 3GPP TS 24.368 [50]); and
ii) any of the remaining PLMNs offering access to RLOS that are not in the RLOS preferred PLMN list if the MCC part of the PLMN ID is present in the RLOS allowed MCC list configured in the USIM (see 3GPP TS 31.102 [40]) or in the ME (see 3GPP TS 24.368 [50]).
Upon selection of a PLMN by the user, the MS initiates registration for access to RLOS on the PLMN chosen by the user (this may take place at any time during the presentation of PLMNs).
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.4.3.1.3 Manual CSG selection
|
4.4.3.1.3.1 General
The HPLMN may configure the MS whether to provide to the user CSGs for a certain PLMN without any restriction or to provide to the user only CSGs in the Operator CSG List for that PLMN.This configuration may be done either:
- in the USIM if the Operator CSG list is available in the USIM; or
- as described in 3GPP TS 24.285 [47].
In the absence of such configuration from the HPLMN for a certain PLMN, the MS shall by default provide to the user CSGs for that PLMN without any restriction.
For PLMNs where no restriction is configured, the MS provides to the user the CSGs that are available and the associated PLMNs using all access technologies which support CSGs (see 3GPP TS 23.003 [22A]) and which are supported by the MS. For each entry in the list, an indication is provided whether that CSG identity is in the Allowed CSG list or in the Operator CSG list stored in the MS for this PLMN.
For PLMNs where the MS is configured to provide to the user only CSGs in the Operator CSG List, the MS provides to the user the CSGs that are available and in the Operator CSG list, using all access technologies which support CSGs (see 3GPP TS 23.003 [22A]) and which are supported by the MS. For each entry in the list, the MS provides to the user the associated PLMN and an indication that the CSG identity is in the Operator CSG List stored in the MS for this PLMN.
Additional requirements for the display, including for the display of HNB name, can be found in 3GPP TS 22.220 [49].
The user may select a CSG from the indicated CSGs.
If the MS has a PDN connection for emergency bearer services, manual CSG selection shall not be performed.
4.4.3.1.3.2 Manual CSG selection within the RPLMN
If the user selects a CSG whose CSG identity is not included in the Allowed CSG list or Operator CSG list, then the MS shall attempt to register on a cell that corresponds to the CSG. For such a registration, the MS shall ignore the contents of the "forbidden location areas for roaming", "forbidden tracking areas for roaming", "forbidden location areas for regional provision of service", "forbidden tracking areas for regional provision of service" and "forbidden PLMNs for GPRS service" lists.
Upon successful or unsuccessful completion of the registration or if registration is not possible, because the MS is no longer in the coverage of the selected CSG, the MS shall return to automatic CSG selection mode.
Manual CSG selection within the RPLMN does not affect the current PLMN selection mode.
4.4.3.1.3.3 Manual CSG selection in a PLMN different from the RPLMN
If the user selects a CSG in a PLMN that is different from the RPLMN, then the following applies:
i) The MS shall store a duplicate of the RPLMN and a duplicate of the PLMN selection mode that were in use before the manual CSG selection was initiated, unless this manual CSG selection follows another manual CSG selection or a PLMN selection triggered by ProSe communications as specified in clause 3.1B or a PLMN selection triggered by V2X communication over PC5 as specified in clause 3.1C or a PLMN selection triggered by A2X communication over PC5 as specified in clause 3.1D;
ii) The MS shall enter into Manual mode of PLMN selection in state M4 (Trying PLMN) as defined in clause 4.3.1.2;
iii) The MS shall select the PLMN corresponding to the CSG and attempt to register on the selected CSG cell in the PLMN. For such a registration, the MS shall ignore the contents of the "forbidden location areas for roaming", "forbidden tracking areas for roaming", "forbidden location areas for regional provision of service", "forbidden tracking areas for regional provision of service", "forbidden PLMNs for GPRS service" and "forbidden PLMNs" lists. If the registration is successful the MS remains in manual CSG selection mode, until the user selects automatic CSG selection mode, the MS is switched off or the condition of any of items iv) to viii) below is fulfilled;
iv) If the registration fails or the MS is no longer in the coverage of the selected CSG, then the MS shall return to the stored duplicate PLMN selection mode and automatic CSG selection mode and use the stored duplicate value of RPLMN for further action;
v) If the MS is switched off while on the selected CSG and switched on again, the MS should return to the stored duplicate PLMN selection mode, unless the MS provides the optional feature of user preferred PLMN selection operating mode at switch on. Additionally, the MS shall use the stored duplicate value of RPLMN and automatic CSG selection mode for further action;
vi) If the user initiates a PLMN selection while on the selected CSG, the MS shall delete the stored duplicate PLMN selection mode, use the stored duplicate value of RPLMN as RPLMN, return to automatic CSG selection mode and follow the procedures (as specified for switch-on or recovery from lack of coverage) in clause 4.4.3.1. The MS shall delete the stored duplicate value of RPLMN once the PLMN selection has been completed successfully;
vii) If the MS's E-UTRA capability is disabled as a result of successful registration (as described in 3GPP TS 24.301 [23A] clauses 5.5.1.3.4.2, 5.5.1.3.4.3, 5.5.3.3.4.2 and 5.5.3.3.4.3) and the selected CSG is not available on UTRAN radio access technology, the MS shall re-enable the E-UTRA capability, return to the stored duplicate PLMN selection mode and automatic CSG selection mode and use the stored duplicate value of RPLMN for further action; and
viii) If the MS's E-UTRA capability is disabled as a result of performing the service request procedure (as described in 3GPP TS 24.301 [23A] clause 5.6.1.5), the selected CSG is not available on UTRAN radio access technology and the MS performed a CS call, then after the end of the call, the MS shall re-enable the E-UTRA capability, return to the stored duplicate PLMN selection mode and automatic CSG selection mode and use the stored duplicate value of RPLMN for further action.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.4.3.2 User reselection
| |
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.4.3.2.0 General
|
At any time the user may request the MS to initiate reselection and registration onto an available PLMN, according to the following procedures, dependent upon the operating mode.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.4.3.2.1 Automatic Network Selection Mode
|
The MS selects and attempts registration on PLMN/access technology combinations, if available and allowable, in all of its bands of operation in accordance with the following order:
i) the HPLMN (if the EHPLMN list is not present or is empty) or the highest priority EHPLMN that is available (if the EHPLMN list is present);
ii) PLMN/access technology combinations contained in the "User Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order) excluding the previously selected PLMN/access technology combination;
iii) PLMN/access technology combinations contained in the "Operator Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order) or stored in the ME (in priority order) excluding the previously selected PLMN/access technology combination;
iv) other PLMN/access technology combinations with the received high quality signal in random order excluding the previously selected PLMN/access technology combination;
NOTE 1: High quality signal is defined in the appropriate AS specification.
v) other PLMN/access technology combinations, excluding the previously selected PLMN/access technology combination in order of decreasing signal quality or, alternatively, the previously selected PLMN/access technology combination may be chosen ignoring its signal quality;
vi) The previously selected PLMN/access technology combination.
The previously selected PLMN/access technology combination is the PLMN/access technology combination which the MS has selected prior to the start of the user reselection procedure.
NOTE 2: If the previously selected PLMN is chosen, and registration has not been attempted on any other PLMNs, then the MS is already registered on the PLMN, and so registration is not necessary.
The equivalent PLMNs list shall not be applied to the user reselection in Automatic Network Selection Mode.
When following the above procedure, the requirements a), b), c), e), f), g), h), j), k), l), m), n), o), p) and v) in clause 4.4.3.1.1 apply: Requirement d) shall apply as shown below:
d) In iv, v, and vi, the MS shall search for all access technologies it is capable of before deciding which PLMN/access technology combination to select.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.