Search is not available for this dataset
doc_id
int64 1
6.72k
⌀ | Section
stringlengths 5
247
⌀ | Content
stringlengths 501
147k
⌀ | Source
stringclasses 456
values | Document Title
stringclasses 22
values | Working Group
stringclasses 21
values | Series Subject
stringclasses 9
values | Subclause
stringlengths 1
13
⌀ |
|---|---|---|---|---|---|---|---|
6,301 | 4.6.3.4 Session management based network slice replacement | If: a) the UE and network support network slice replacement; b) the UE is provided with the mapping information between the S-NSSAI to be replaced and the alternative S-NSSAI; and c) the UE decides to establish a new PDU session with the S-NSSAI to be replaced, the UE provides both the S-NSSAI to be replaced and the alternative S-NSSAI during PDU session establishment procedure. If the timer T3584 or timer T3585 is running for the S-NSSAI to be replaced, the UE should not stop the timer during PDU session establishment procedure. If the SMF receives both the S-NSSAI to be replaced and the alternative S-NSSAI during PDU session establishment procedure, the SMF proceeds with the PDU session establishment procedure with the alternative S-NSSAI. If the PDU session establishment request is accepted, the SMF includes the alternative S-NSSAI in the PDU session establishment accept message. If the UE is provided with the mapping of the VPLMN S-NSSAI to a VPLMN alternative S-NSSAI, the UE provides both the VPLMN alternative S-NSSAI and the VPLMN S-NSSAI in the PDU SESSION ESTABLISHMENT REQUEST message. If the UE is provided with the mapping of the HPLMN S-NSSAI to a HPLMN Alternative S-NSSAI, the UE provides both the HPLMN alternative S-NSSAI and the HPLMN S-NSSAI in the PDU SESSION ESTABLISHMENT REQUEST message. The AMF sends both HPLMN alternative S-NSSAI and HPLMN S-NSSAI to the SMF. If the SMF receives from the AMF an alternative S-NSSAI for existing PDU session and: a) if the SMF decides to retain the existing PDU session (i.e. the SMF can serve both the alternative S-NSSAI and the S-NSSAI to be replaced with), the SMF sends the alternative S-NSSAI to the UE during network-requested PDU session modification procedure; or b) if the SMF decides to re-activate the existing PDU session and: 1) if the SSC mode of the PDU session is SSC mode 3, the SMF initiates PDU session modification procedure to trigger PDU session reactivation by the UE; or 2) if the SSC mode of the PDU session is SSC mode 1 or SSC mode 2, the SMF initiates PDU session release procedure to trigger PDU session reactivation by the UE. If the timer T3584 or timer T3585 is running for the S-NSSAI that was replaced and the S-NSSAI that was replaced in alternative NSSAI is available and the AMF provides the updated allowed NSSAI and configured NSSAI to the UE, the UE should stop the timer. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.6.3.4 |
6,302 | 5.6.2 Paging procedure 5.6.2.1 General | The paging procedure is used by the network to request the establishment or resumption of a NAS signalling connection to the UE. Another purpose of the paging procedure is to prompt the UE to reattach if necessary as a result of a network failure. If the UE is not attached when it receives a paging for EPS services, the UE shall ignore the paging. Additionally, the network can use the paging procedure to initiate the mobile terminating CS fallback procedure or SMS or user data transfer via the MME. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.6.2 |
6,303 | 5.17 Home eNodeB Multicast Packet Forwarding Function | A Home eNodeB L-GW should receive and process multicast group membership report messages (e.g. according to RFC 3376 [62] / RFC 3810 [63]) sent either by the network accessed by LIPA or by the UE. Based upon these messages, the L-GW should forward multicast IP datagrams sent by the UE to the network accessed by LIPA, or from the network accessed by LIPA to the UE, as appropriate. The UE may implement RFC3376 [62] or RFC 3810 [63] to report multicast groups that the UE seeks to receive. To make UPnP/DLNA service advertisements sent with an IP TTL=1 available to UEs that employ LIPA, a proxying function in the L-GW may be implemented, e.g. to retransmit UPnP service advertisements to UEs after changing the source address. This proxying to the UE shall not be performed if the multicast packet is transmitted with an IPv4 or IPv6 link-local source address, RFC 3927 [64], RFC 4291 [65]. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.17 |
6,304 | 5.5.2.6 Reporting configuration removal | The UE shall: 1> for each reportConfigId included in the received reportConfigToRemoveList that is part of the current UE configuration in VarMeasConfig: 2> remove the entry with the matching reportConfigId from the reportConfigList within the VarMeasConfig; 2> remove all measId associated with the reportConfigId from the measIdList within the VarMeasConfig, if any; 2> if a measId is removed from the measIdList: 3> remove the measurement reporting entry for this measId from the VarMeasReportList, if included; 3> stop the periodical reporting timer or timer T321 or timer T322, whichever one is running, and reset the associated information (e.g. timeToTrigger) for this measId. NOTE: The UE does not consider the message as erroneous if the reportConfigToRemoveList includes any reportConfigId value that is not part of the current UE configuration. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.2.6 |
6,305 | 7.6.3.1A Minimum requirements for CA | For inter-band carrier aggregation with one component carrier per operating band and the uplink assigned to one E-UTRA band the narrow-band blocking requirements are defined with the uplink active on the band(s) other than the band whose downlink is being tested. The UE shall meet the requirements specified in subclause 7.6.3.1 for each component carrier while all downlink carriers are active. For E-UTRA CA configurations including an operating band without uplink band or an operating band with an unpaired DL part (as noted in Table 5.5-1), the requirements for all downlinks shall be met with the single uplink carrier active in each band capable of UL operation. For E-UTRA CA configurations listed in Table 7.3.1A-0a under conditions for which reference sensitivity for the operating band being tested is N/A, the narrow-band blocking requirements of subclause 7.6.3.1A do not apply. For E-UTRA CA configurations with a component carrier assigned in Band 46, narrow-band blocking requirements do not apply in the presence of a narrow-band interferer in Band 46. For intra-band contiguous carrier aggregation the downlink SCC(s) shall be configured at nominal channel spacing to the PCC. For FDD, the PCC shall be configured closest to the uplink band. All downlink carriers shall be active throughout the test. The uplink output power shall be set as specified in Table .1A-1 with the uplink configuration set according to Table 7.-1 for the applicable carrier aggregation configuration. For UE(s) supporting one uplink, the uplink configuration of the PCC shall be in accordance with Table 7.3.1-2. The UE shall fulfil the minimum requirement in presence of an interfering signal specified in Table .1A-1 being on either side of the aggregated signal. The throughput of each carrier shall be ≥ 95% of the maximum throughput of the reference measurement channels as specified in Annexes , A.2.3 and A.3.2 (with one sided dynamic OCNG Pattern OP.1 FDD/TDD for the DL-signal as described in Annex /A.5.2.1) with parameters specified in Table 7.6.3.1A-1. For operating bands with an unpaired DL part (as noted in Table 5.5-1), the requirements also apply for an SCC assigned in the unpaired part with parameters specified in Table 7.6.3.1A-1. For intra-band non-contiguous carrier aggregation with one uplink carrier and two or more downlink sub-blocks, the narrow band blocking requirements are defined with the uplink configuration in accordance with Table 7.3.1A-3. For this uplink configuration, the UE shall meet the requirements for each sub-block as specified in subclauses 7.6.3.1 and 7.6.3.1A for one component carrier and two component carriers per sub-block, respectively. The requirements apply for in-gap and out-of-gap interferers while all downlink carriers are active. Table .1A-1: Narrow-band blocking For combinations of intra-band and inter-band carrier aggregation and one uplink carrier assigned to one E-UTRA band, the requirement is defined with the uplink active in a band other than that supporting the downlink(s) under test. The uplink configuration shall be in accordance with Table 7.3.1A-3 when the uplink is active in the band supporting two or more non-contiguous component carriers, Table 7.3.1A-1 when the uplink is active in a band supporting two contiguous component carriers and in accordance with Table 7.3.1-2 when the uplink is active in a band supporting one carrier per band. The downlink PCC shall be configured closer to the uplink operating band than the downlink SCC(s) when the uplink is active in band(s) supporting contiguous aggregation. For these uplink configurations, the UE shall meet the narrow-band blocking requirements for intra-band non-contiguous carrier aggregation with RIBNC = 0 dB for all sub-block gaps (Table 7.3.1A-3) for the two or more non-contiguous downlink sub-blocks, the requirements for intra-band contiguous carrier aggregation for the contiguously aggregated downlink carriers and for any remaining component carrier(s) the requirements specified in subclause 7.6.3. For E-UTRA CA configurations with component carriers assigned in Band 46, narrow-band blocking requirements do not apply in the presence of a narrow-band interferer in Band 46. All downlink carriers shall be active throughout the tests and the requirements for the downlinks shall be met with the single uplink carrier active in each band capable of UL operation. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 7.6.3.1A |
6,306 | 4.9.1.3.3a Execution phase for DAPS handover | This procedure applies only if at the end of the Preparation phase it has been determined that at least one DRB of the UE is subject to a DAPS related Handover. Figure 4.9.1.3.3a-1: inter NG-RAN node N2 based DAPS handover, execution phase 1 to 2. Same as step 1 to step 2 in clause 4.9.1.3.3 with the following difference. DAPS Response information received in the Target to Source Transparent Container indicates the DAPS handover is accepted for one or more DRBs. 2a to 2c. The S-RAN sends the Uplink RAN Early Status Transfer message to the S-AMF as specified in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10]. For the DRBs not subjecting to DAPS, steps 2a to 2c in clause 4.9.1.3.3 may be performed. If there is an AMF change, the S-AMF sends this information to the T-AMF via the Namf_Communication_N1N2MessageTransfer service operation and the T-AMF acknowledges. The S-AMF or, if the AMF is relocated, the T-AMF, sends the information to the T-RAN via the Downlink RAN Early Status Transfer message, as specified in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10]. 3. Same as step 3 in clause 4.9.1.3.3. 4. Same as step 4 in clause 4.9.1.3.3. 5. T-RAN to T-AMF: same as step 5 in clause 4.9.1.3.3 with the difference that the Handover Notify includes a Notify Source NG-RAN node information which is used to notify the S-RAN that the UE has successfully accessed the T-RAN. 6a. [Conditional] T-AMF to S-AMF: Namf_Communication_N2InfoNotify. The T-AMF notifies the S-AMF as in step 6a in clause 4.9.1.3.3 with the difference that Notify Source NG-RAN node information is included. 6b. [Conditional] S-AMF to T-AMF: Namf_Communication_N2InfoNotify ACK. The S-AMF acknowledges by sending the Namf_Communication_N2InfoNotify ACK to the T-AMF as in step 6b in clause 4.9.1.3.3. 7. S-AMF to S-RAN: Handover Success. The S-AMF informs the S-RAN node that the UE has successfully accessed the T-RAN as described in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10], S-RAN stops the UL data transfer for the UE. 8a to 8c. The S-RAN initiates step 8a. Step 8a to 8c are the same as step 2a to 2c in clause 4.9.1.3.3 for the DRB(s) subject to DAPS. 9. Step 6c to step 15 in clause 4.9.1.3.3 are performed. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.9.1.3.3a |
6,307 | 5.8.10.5 Sidelink measurement reporting 5.8.10.5.1 General | Figure 5.8.10.5.1-1: NR sidelink measurement reporting The purpose of this procedure is to transfer measurement results from the UE to the peer UE associated. For the sl-MeasId for which the NR sidelink measurement reporting procedure was triggered, the UE shall set the sl-MeasResults within the MeasurementReportSidelink message as follows: 1> set the sl-MeasId to the measurement identity that triggered the NR sidelink measurement reporting; 1> if the sl-ReportConfig associated with the sl-MeasId that triggered the NR sidelink measurement reporting is set to sl-EventTriggered or sl-Periodical: 2> if the sl-RS-Type within sl-ReportConfig is set to dmrs: 3> set sl-ResultDMRS within sl-MeasResult to include the NR sidelink DMRS based quantity indicated in the sl-ReportQuantity within the concerned sl-ReportConfig; 2> if the sl-RS-Type within sl-ReportConfig is set to sl-prs: 3> set sl-Result-SL-PRS within sl-MeasResult to include the NR SL-PRS based quantity indicated in the sl-ReportQuantity within the concerned sl-ReportConfig; 1> increment the sl-NumberOfReportsSent as defined within the VarMeasReportListSL for this sl-MeasId by 1; 1> stop the periodical reporting timer, if running; 1> if the sl-NumberOfReportsSent as defined within the VarMeasReportListSL for this sl-MeasId is less than the sl-ReportAmount as defined within the corresponding sl-ReportConfig for this sl-MeasId: 2> start the periodical reporting timer with the value of sl-ReportInterval as defined within the corresponding sl-ReportConfig for this sl-MeasId; 1> else: 2> if the sl-ReportType is set to sl-Periodical: 3> remove the entry within the VarMeasReportListSL for this sl-MeasId; 3> remove this sl-MeasId from the sl-MeasIdList within VarMeasConfigSL; 1> submit the MeasurementReportSidelink message to lower layers for transmission, upon which the procedure ends. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.10.5 |
6,308 | 5.21.1.1 TNL associations | 5G-AN node shall have the capability to support multiple TNL associations per AMF, i.e. AMF name. An AMF shall provide the 5G-AN node with the weight factors for each TNL association of the AMF. The AMF shall be able to request the 5G-AN node to add or remove TNL associations to the AMF. The AMF shall be able to indicate to the 5G-AN node the set of TNL associations used for UE-associated signalling and the set of TNL associations used for non-UE associated signalling. NOTE: The TNL association(s) indicated for UE-associated and non-UE associated signalling can either be overlap or be different. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.21.1.1 |
6,309 | – SI-SchedulingInfo | The IE SI-SchedulingInfo contains information needed for acquisition of SI messages. SI-SchedulingInfo information element -- ASN1START -- TAG-SI-SCHEDULINGINFO-START SI-SchedulingInfo ::= SEQUENCE { schedulingInfoList SEQUENCE (SIZE (1..maxSI-Message)) OF SchedulingInfo, si-WindowLength ENUMERATED {s5, s10, s20, s40, s80, s160, s320, s640, s1280, s2560-v1710, s5120-v1710 }, si-RequestConfig SI-RequestConfig OPTIONAL, -- Cond MSG-1 si-RequestConfigSUL SI-RequestConfig OPTIONAL, -- Cond SUL-MSG-1 systemInformationAreaID BIT STRING (SIZE (24)) OPTIONAL, -- Need R ... } SchedulingInfo ::= SEQUENCE { si-BroadcastStatus ENUMERATED {broadcasting, notBroadcasting}, si-Periodicity ENUMERATED {rf8, rf16, rf32, rf64, rf128, rf256, rf512}, sib-MappingInfo SIB-Mapping } SI-SchedulingInfo-v1700 ::= SEQUENCE { schedulingInfoList2-r17 SEQUENCE (SIZE (1..maxSI-Message)) OF SchedulingInfo2-r17, dummy SI-RequestConfig OPTIONAL } SI-SchedulingInfo-v1740 ::= SEQUENCE { si-RequestConfigRedCap-r17 SI-RequestConfig OPTIONAL -- Cond REDCAP-MSG-1 } SI-SchedulingInfo-v1800 ::= SEQUENCE { si-RequestConfigMSG1-Repetition-r18 SI-RequestConfigRepetition-r18 OPTIONAL, -- Cond MSG-1 si-RequestConfigRedCap-MSG1-Repetition-r18 SI-RequestConfigRepetition-r18 OPTIONAL, -- Cond SUL-MSG-1 si-RequestConfigSUL-MSG1-Repetition-r18 SI-RequestConfigRepetition-r18 OPTIONAL -- Cond REDCAP-MSG-1 } SchedulingInfo2-r17 ::= SEQUENCE { si-BroadcastStatus-r17 ENUMERATED {broadcasting, notBroadcasting}, si-WindowPosition-r17 INTEGER (1..256), si-Periodicity-r17 ENUMERATED {rf8, rf16, rf32, rf64, rf128, rf256, rf512}, sib-MappingInfo-r17 SIB-Mapping-v1700 } SIB-Mapping ::= SEQUENCE (SIZE (1..maxSIB)) OF SIB-TypeInfo SIB-Mapping-v1700 ::= SEQUENCE (SIZE (1..maxSIB)) OF SIB-TypeInfo-v1700 SIB-TypeInfo ::= SEQUENCE { type ENUMERATED {sibType2, sibType3, sibType4, sibType5, sibType6, sibType7, sibType8, sibType9, sibType10-v1610, sibType11-v1610, sibType12-v1610, sibType13-v1610, sibType14-v1610, spare3, spare2, spare1,... }, valueTag INTEGER (0..31) OPTIONAL, -- Cond SIB-TYPE areaScope ENUMERATED {true} OPTIONAL -- Need S } SIB-TypeInfo-v1700 ::= SEQUENCE { sibType-r17 CHOICE { type1-r17 ENUMERATED {sibType15, sibType16, sibType17, sibType18, sibType19, sibType20, sibType21, sibType22-v1800, sibType23-v1800 ,sibType24-v1800, sibType25-v1800, spare5, spare4, spare3, spare2, spare1,...}, type2-r17 SEQUENCE { posSibType-r17 ENUMERATED {posSibType1-9, posSibType1-10, posSibType2-24, posSibType2-25, posSibType6-4, posSibType6-5, posSibType6-6, posSibType2-17a-v1770, posSibType2-18a-v1770, posSibType2-20a-v1770, posSibType1-11-v1800, posSibType1-12-v1800, posSibType2-26-v1800, posSibType2-27-v1800, spare2, spare1,...}, encrypted-r17 ENUMERATED { true } OPTIONAL, -- Need R gnss-id-r17 GNSS-ID-r16 OPTIONAL, -- Need R sbas-id-r17 SBAS-ID-r16 OPTIONAL -- Cond GNSS-ID-SBAS } }, valueTag-r17 INTEGER (0..31) OPTIONAL, -- Cond NonPosSIB areaScope-r17 ENUMERATED {true} OPTIONAL -- Need S } -- TAG-SI-SCHEDULINGINFO-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,310 | 6.5.4.6 Abnormal cases on the network side | The following abnormal cases can be identified: a) Unknown EPS bearer context: If the EPS bearer identity provided in the EPS bearer identity for packet filter IE in the BEARER RESOURCE MODIFICATION REQUEST message indicates an EPS bearer identity value and this does not belong to any already activated EPS bearer context, the MME shall reply with a BEARER RESOURCE MODIFICATION REJECT message with ESM cause #43 "invalid EPS bearer identity". b) BEARER RESOURCE MODIFICATION REQUEST message received for a PDN connection established for emergency bearer services: The MME shall reply with a BEARER RESOURCE MODIFICATION REJECT message with ESM cause #30 "request rejected by Serving GW or PDN GW". c) Collision of UE requested bearer resource modification procedure and EPS bearer context modification procedure: The handling of the same abnormal case as described in clause 6.4.3.6 applies. d) BEARER RESOURCE MODIFICATION REQUEST message received from a UE which is in a location where the PLMN is not allowed to operate: If the MME determines that the UE is in a location where the PLMN is not allowed to operate, the MME discards the message. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.5.4.6 |
6,311 | 5.4.1 Primary authentication and key agreement procedure 5.4.1.1 General | The purpose of the primary authentication and key agreement procedure is to enable mutual authentication between the UE and the network and to provide keying material that can be used between the UE and network in subsequent security procedures, as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. Two methods are defined: a) EAP based primary authentication and key agreement procedure. b) 5G AKA based primary authentication and key agreement procedure. The UE and the AMF shall support the EAP based primary authentication and key agreement procedure and the 5G AKA based primary authentication and key agreement procedure. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.1 |
6,312 | 4.14.2.6 Number of successful additions of LWIP DRB | a) This measurement provides the number of successful additions of LWIP DRB. b) CC c) On receipt of RRCConnectionReconfigurationComplete message (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]) corresponding to transmitted RRCConnectionReconfiguration message which triggered the measurement "Number of attempted additions of LWIP DRB" (see section 4.x.z.5). d) An integer value e) LWI.LwipDrbAddSucc f) WLANMobilitySet g) Valid for packet switched traffic h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.14.2.6 |
6,313 | D.3.1.1 Inputs and outputs | The input parameters to the integrity algorithm are a 128-bit integrity key named KEY, a 32-bit COUNT, a 5-bit bearer identity called BEARER, the 1-bit direction of the transmission i.e. DIRECTION, and the message itself i.e. MESSAGE. The DIRECTION bit shall be 0 for uplink and 1 for downlink. The bit length of the MESSAGE is LENGTH. Figure D.3.1.1-1 illustrates the use of the integrity algorithm NIA to authenticate the integrity of messages. Figure D.3.1.1-1: Derivation of MAC-I/NAS-MAC (or XMAC-I/XNAS-MAC) Based on these input parameters the sender computes a 32-bit message authentication code (MAC-I/NAS-MAC) using the integrity algorithm NIA. The message authentication code is then appended to the message when sent. For integrity protection algorithms, the receiver computes the expected message authentication code (XMAC-I/XNAS-MAC) on the message received in the same way as the sender computed its message authentication code on the message sent and verifies the data integrity of the message by comparing it to the received message authentication code, i.e. MAC-I/NAS-MAC. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | D.3.1.1 |
6,314 | 9.3.23.1.2 Bearer capability 1 and bearer capability 2 | The bearer capability 1 information element may be omitted in the case where the mobile subscriber is allocated only one directory number for all services (ref.: 3GPP TS 29.007[ General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN) ] [38]). The bearer capability 2 IE is missing at least if the bearer capability 1 IE is missing. If the MSC wishes to indicate capability for an altenative call mode, which can be entered through fallback, this is indicated by adding a bearer capability information element (bearer capability) 2 element (see subclause 5.3.6). | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.3.23.1.2 |
6,315 | – AdditionalSpectrumEmission | The IE AdditionalSpectrumEmission is used to indicate emission requirements to be fulfilled by the UE (see TS 38.101[ None ] -1 [15], clause 6.2.3/6.2A.3, TS 38.101[ None ] -2 [39], clause 6.2.3/6.2A.3, and TS 38.101[ None ] -5 [75], clause 6.2.3). If an extension is signalled using the extended value range (as defined by the IE AdditionalSpectrumEmission-v1760), the corresponding original field, using the value range as defined by the IE AdditionalSpectrumEmission (without suffix) shall be set to value 7. AdditionalSpectrumEmission information element -- ASN1START -- TAG-ADDITIONALSPECTRUMEMISSION-START AdditionalSpectrumEmission ::= INTEGER (0..7) AdditionalSpectrumEmission-v1760 ::= INTEGER (8..39) AdditionalSpectrumEmission-r18 ::= INTEGER (0..39) -- TAG-ADDITIONALSPECTRUMEMISSION-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,316 | A.25 Evaluation of long inactivity timer | The services from the point of view the time between the newly successful RRC connection setup and the last RRC Connection Release can be divided into the two groups. First group is build from the services the time is quite long (tens of minutes or hours) while for the second group it is tens of seconds. Typical example of the service from the first group can be VoLTE call with a common characteristic that data transmission is accumulated into the time period the call is active without any long interruptions and sufficiently long period between the two consequent calls from the same UE. A second type of service can be web browsing with a common characteristic that data transmission is accumulated into the smaller time periods the service is active i.e. with long interruptions between data transmissions. In the past operators had only option to set the inactivity timer commonly for all kind of services. This may lead to the situation that for the services from the first group UE had to spend ineffectively longer time in RRC Connected state which had negative impact on UE’s battery live. On the other hand for the services from the second group the inactivity timer setting can be insufficient which then may lead to significant increase of the UE movements from RRC Idle to RRC Connected state. Operators shall therefore accurately tune the inactivity timers to avoid some bottlenecks in the RRC Connection setup on one side and prolongation of the UE’s battery life on the second side. Especially regarding the services where long inactivity timer applies operator needs to have an option to estimate how intended prolongation of the long inactivity timer is going to decrease the number of RRC Connection Setups on one side and prolong the UEs’ state in RRC Connected state on second side, using the "Number of successful RRC connection setups in relation to the time between successful RRC connection setup and last RRC connection release". | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | A.25 |
6,317 | 9.3.10 Hold | This message is sent by the mobile user to request the hold function for an existing call. See table 9.62c/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] for the content of the HOLD message. For the use of this message, see 3GPP TS 24.010[ Mobile radio interface layer 3; Supplementary services specification; General aspects ] [21]. Message type: HOLD Significance: local Direction: mobile station to network Table 9.62c/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : HOLD message content | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.3.10 |
6,318 | 15.5.1 Support for Mobility Load Balancing 15.5.1.1 General | The objective of mobility load balancing is to distribute load evenly among cells and among areas of cells, or to transfer part of the traffic from congested cell or from congested areas of cells, or to offload users from one cell, cell area, carrier or RAT to achieve network energy saving. This can be done by means of optimization of cell reselection/handover parameters and handover actions. The automation of such optimisation can provide high quality user experience, while simultaneously improving the system capacity and also to minimize human intervention in the network management and optimization tasks. Intra-RAT, intra-system inter-RAT and inter-system load balancing scenarios are supported. In general, support for mobility load balancing consists of one or more of following functions: - Load reporting for intra-RAT and intra-system inter-RAT load balancing; - Load balancing action based on handovers; - Adapting handover and/or reselection configuration; - Load reporting for inter-system load balancing. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 15.5.1 |
6,319 | 6.1.5.2 Security mechanisms | The UDM may initiate primary authentication based on procedures initiated by the UE (e.g. UE registration in 5GC) or towards the UE (e.g. SoR/UPU) or events from other NFs, considering the local policy into account as well. Figure 6.1.5.2-1 Home Network triggered primary authentication procedure 0a. The UDM may be pre-configured with an operator authentication policy in order to determine when to trigger a primary authentication procedure. 0b. The UE registers to the network. As part of the registration, the serving AMF registers the UE with the UDM via the Nudm_UECM_Registration as per TS 23.502[ Procedures for the 5G System (5GS) ] [8], clause 4.2.2.2.2. The AMF shall provide a callback URI within the AMF registration for the UDM to create an implicit subscription to later notify the AMF for potential home network triggered re-authentication using the Nudm_UECM_Re-AuthenticationNotification service operation as in step 2. 1a-c. The UDM decides itself based on events (e.g., SoR/UPU or NF requests such as AAnF requests as defined in TS 33.535[ Authentication and Key Management for Applications (AKMA) based on 3GPP credentials in the 5G System (5GS) ] [91]) or authentication policy and performs home network triggered primary authentication as described in the following steps. The NF such as the AAnF considers based on operator's local authentication policy described in TS 33.535[ Authentication and Key Management for Applications (AKMA) based on 3GPP credentials in the 5G System (5GS) ] [91] to send Nudm_UECM_AuthTrigger request to the UDM for primary authentication using the UDM services as described in clause 14.2.6. The NF may send a Nudm_UECM_AuthTrigger Request message to the UDM with the SUPI of the target UE. NOTE A: For the NF (e.g., AAnF) request event, the UDM can decide not to proceed with triggering the primary authentication based on the UDM’s local authentication policy. In case of AAnF being the NF, as AAnF sets the AF key expiry based on operator’s local authentication policy, no frequent AF key expiry can happen and there is no risk of signalling overload. Based on a received event and the local operator authentication policy, if there is no ongoing primary authentication for the UE, and if the UDM determines to trigger the primary authentication, the UDM determines the serving AMF/SEAF of the target UE. If there are different AMFs registered in the UDM for different access, the UDM shall select one AMF to perform the re-authentication. The criteria for selecting the AMF are dependent of the local UDM authentication policy. NOTE 1: The reasons for the UDM determining that the UE needs to be authenticated can be different. For example, the UDM can determine to initiate a primary authentication when the AMF registers the UE upon the Registration procedure during the mobility from EPC or when SoR/UPU counters are about to wrap around, or when required based on authentication policy, or based on the request from AAnF. The UDM behaviour is determined by operator policy which takes into account the support of certain features in the PLMN. For example, if the PLMN does not support the SoR/UPU feature, then SoR/UPU counter wrap around will not happen and primary authentication will not be required for this case. The UDM acknowledges the Nudm_UECM_AuthTrigger Response. 2. The UDM sends a Nudm_UECM_Re-AuthenticationNotification message to the AMF/SEAF with the UE’s SUPI. 3. After receiving the Nudm_UECM_Re-AuthenticationNotification message from the UDM, the AMF/SEAF shall decide whether to run the primary authentication procedure based on its own local authentication policy, and the UE state (e.g. , if the UE is under handover, or if the UE is already under authentication by the AMF before receiving the authentication notification from the UDM). If the AMF/SEAF determines that it cannot run a primary authentication as described in step 4 (e.g., due to local policy), the AMF/SEAF sends the authentication response message to the UDM with a failure cause else it acknowledges the request. If the AMF/SEAF acknowledged the request but the AMF/SEAF is not able to initiate the primary authentication towards the UE (e.g. if UE is not reachable), the AMF/SEAF shall set the authentication pending flag. When UE re-attaches to the same AMF or becomes reachable, the AMF checks the authentication pending flag and performs the reauthentication if needed. Once UE reauthentication is done, the AMF resets the authentication pending flag. NOTE B: In the case that the UE attaches to a new AMF, the new AMF will register to the UDM using the NudM_UECM_Registration message. In this case, the UDM can determine again on whether to trigger the primary authentication as described in 1b. Upon receiving a failure from the AMF, the UDM may check if another AMF is available over the other access. If available, the UDM may select another AMF and retry Step 2. 4. The AMF/SEAF starts the primary authentication procedure as defined in clause 6.2.1 of the present document. The UDM may execute other procedures (e.g. SoR/UPU) depending on the reason that motivated the UDM triggered (re-)authentication procedure in step 1. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.1.5.2 |
6,320 | 5.27.5 5G System Bridge delay | This clause applies if 5GS is integrated as a bridge into an IEEE TSN network. In order for the 5G System to participate as a TSN bridge according to transmission gate schedules specified, the 5GS Bridge is required to provide Bridge Delays as defined in IEEE Std 802.1Q [98] for each port pair and traffic class of the 5GS bridge to an IEEE 802.1 TSN system. In order to determine 5GS Bridge Delays, the following components are needed: 1. UE-DS-TT Residence Time. 2. Per traffic class minimum and maximum delays between the UE and the UPF/NW-TT that terminates the N6 interface (including UPF and NW-TT residence times), independent of frame length that a given 5GS deployment supports. The per-traffic class delays between the UE and the UPF/NW-TT are pre-configured in the TSN AF (see clause 5.28.4). The TSN AF calculates the 5GS independentDelayMin and independentDelayMax values for each port pair and for each traffic class using the above components. If the UE-DS-TT Residence Time has not been provided by the UE, then the TSN AF uses a locally configured minimum UE-DS-TT Residence Time for the calculation of independentDelayMin and a locally configured maximum UE-DS-TT Residence Time for the calculation of independentDelayMax. The dependentDelayMin and dependentDelayMax for 5GS Bridge specify the time range for a single octet of an Ethernet frame to transfer from ingress to egress and include the time to receive and store each octet of the frame, which depends on the link speed of the ingress Port as per IEEE Std 802.1Q [98]. NOTE: Further details how TSN AF determines dependentDelayMin and dependentDelayMax are up to implementation. Since residence times may vary among UEs and per traffic class delay between the UE and the UPF/NW-TT may vary among UPFs, the 5GS Bridge Delay is determined after the PDU Session Establishment for the corresponding UPF and the UE by the TSN AF. The TSN AF deduces the related port pair(s) from the port number of the DS-TT Ethernet port and port number of the NW-TT Ethernet port(s) of the same 5GS Bridge when the TSN AF receives the 5GS Bridge information for a newly established PDU Session and calculates the bridge delays per port pair. Additionally, TSN AF deduces the port pair(s) consisting of two DS-TT ports connecting to the same 5GS bridge and determines the 5GS bridge delay as sum of bridge delays related to PDU Sessions of two DS-TT ports. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.27.5 |
6,321 | 10.5.4.5.1 Static conditions for the bearer capability IE contents | If the information transfer capability field (octet 3) indicates "speech", octets 4, 5, 5a, 5b, 6, 6a, 6b, 6c, 6d, 6e, 6f, 6g and 7 shall not be included. If the information transfer capability field (octet 3) indicates "speech", octet 3a etc. shall be included only if the mobile station supports CTM text telephony or if it supports at least one speech version for GERAN other than: - GSM full rate speech version 1; or - GSM half rate speech version 1. If the information transfer capability field (octet 3) indicates a value different from "speech", octets 4, 5, 6, 6a, 6b, and 6c shall be included, octets 6d, 6e, 6f and 6g are optional. In the network to MS direction in case octet 6d is included, octets 6e, 6f and 6g may be included. In the MS to network direction in case octet 6d is included octet 6e shall also be included and 6f and 6g may be included. If the information transfer capability field (octet 3) indicates "facsimile group 3", the modem type field (octet 6c) shall indicate "none". If the information transfer capability field (octet 3) indicates "other ITC" or the rate adaption field (octet 5) indicates "other rate adaption", octet 5a shall be included. If the rate adaption field (octet 5) indicates "other rate adaption" and the other rate adaption field (octet 5a) indicates "V.120", octet 5b shall be included. The modem type field (octet 6c) shall not indicate "autobauding type 1" unless the connection element field (octet 6c) indicates "non transparent". | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.4.5.1 |
6,322 | 5.5.2.1.1 Reference signal sequence | The PUSCH demodulation reference signal sequence associated with layer is defined by where and if - the higher-layer parameter ul-DMRS-IFDMA is set and the most recent uplink-related DCI contains the Cyclic Shift Field mapping table for DMRS bit field which is set to 1 to indicate the use of Table 5.5.2.1.1-3, or, - the Cyclic Shift Field mapping table for DMRS bit field is set to 1 in the most recent uplink-related DCI format 7 which indicates the use of Table 5.5.2.1.1-4, or, - subslot-PUSCH/slot-PUSCH for the transport block is semi-persistently scheduled (i.e. higher layer parameter sps-ConfigUL-STTI is configured, see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [9]), and ifdma-Config-SPS is set. In all other cases, . Clause 5.5.1 defines the sequence where, for PUSCH demodulation reference signal sequence, when - the higher-layer parameter ul-DMRS-IFDMA is set and the most recent uplink-related DCI contains the Cyclic Shift Field mapping table for DMRS bit field which is set to 1 to indicate the use of Table 5.5.2.1.1-3, or, - the Cyclic Shift Field mapping table for DMRS bit field is set to 1 in the most recent uplink-related DCI format 7 which indicates the use of Table 5.5.2.1.1-4, or, - subslot-PUSCH/slot-PUSCH for the transport block is semi-persistently scheduled (i.e. higher layer parameter sps-ConfigUL-STTI is configured, see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [9]), and ifdma-Config-SPS is set. In all other cases, . The orthogonal sequence is given by for subslot-PUSCH/slot-PUSCH. In all other cases, it is given by for DCI format 0 if the higher-layer parameter Activate-DMRS-with OCC is not set or if the temporary C-RNTI was used to transmit the most recent uplink-related DCI for the transport block associated with the corresponding PUSCH transmission. Otherwise, - if higher-layer parameter ul-DMRS-IFDMA is not set, is given by Table 5.5.2.1.1-1 using the cyclic shift field in the most recent uplink-related DCI [3], - if higher-layer parameter ul-DMRS-IFDMA is set and the Cyclic Shift Field mapping table for DMRS bit field is not present in the most recent uplink-related DCI, is given by Table 5.5.2.1.1-1 using the cyclic shift field in the most recent uplink-related DCI, - if higher-layer parameter ul-DMRS-IFDMA is set and the Cyclic Shift Field mapping table for DMRS bit field is present in the most recent uplink-related DCI, is given by Table 5.5.2.1.1-1 using the cyclic shift field in the most recent uplink-related DCI when the Cyclic Shift Field mapping table for DMRS bit field is set to 0, and - if higher-layer parameter ul-DMRS-IFDMA is set and the Cyclic Shift Field mapping table for DMRS bit field is present in the most recent uplink-related DCI, is given by Table 5.5.2.1.1-3 using the cyclic shift field in the most recent uplink-related DCI when the Cyclic Shift Field mapping table for DMRS bit field is set to 1. The cyclic shift in a slot is given as if the ul-V-SPS-RNTI-r14 was used to transmit the most recent uplink-related DCI for the transport block associated with the corresponding PUSCH transmission. For PUSCH transmissions not using sub-PRB allocations, if pusch-CyclicShift in higher layer parameter PUR-PUSCH-Config is configured, then for PUSCH (re)transmission corresponding to preconfigured uplink resource it provides the value of and the cyclic shift in a slot is given as . Otherwise, the cyclic shift in a slot is given as with where the value of is given by Table 5.5.2.1.1-2 according to the parameter cyclicShift provided by higher layers. For non-BL/CE UEs is given using the most recent uplink-related DCI TS 36.212[ Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding ] [3] for the transport block associated with the corresponding PUSCH transmission, except for subslot-PUSCH/slot-PUSCH, as follows: - if the higher-layer parameter ul-DMRS-IFDMA is not set, is given by Table 5.5.2.1.1-1 using the cyclic shift field in the most recent uplink-related DCI, - if higher-layer parameter ul-DMRS-IFDMA is set and the Cyclic Shift Field mapping table for DMRS bit field is not present in the most recent uplink-related DCI, is given by Table 5.5.2.1.1-1 using the cyclic shift field in the most recent uplink-related DCI, - if higher-layer parameter ul-DMRS-IFDMA is set and the Cyclic Shift Field mapping table for DMRS bit field is present in the most recent uplink-related DCI, is given by Table 5.5.2.1.1-1 using the cyclic shift field in the most recent uplink-related DCI when the Cyclic Shift Field mapping table for DMRS bit field is set to 0, and - if higher-layer parameter ul-DMRS-IFDMA is set and the Cyclic Shift Field mapping table for DMRS bit field is present in the most recent uplink-related DCI, is given by Table 5.5.2.1.1-3 using the cyclic shift field in the most recent uplink-related DCI when the Cyclic Shift Field mapping table for DMRS bit field is set to 1. For subslot-PUSCH/slot-PUSCH for non-BL/CE UEs, is given by Table 5.5.2.1.1-4, using the cyclic shift field in the most recent uplink-related DCI. If the Cyclic Shift Field mapping table for DMRS bit field is set to 0, in Table 5.5.2.1.1-4 is ignored. If the Cyclic Shift Field mapping table for DMRS bit field is set to 1, both and are given by Table 5.5.2.1.1-4. For BL/CE UEs, a cyclic shift field of '000' shall be assumed when determining from Table 5.5.2.1.1-1. For subframe-based PUSCH transmission, the first row of Table 5.5.2.1.1-1 shall be used to obtain and if there is no uplink-related DCI for the same transport block associated with the corresponding PUSCH transmission, and - if the initial PUSCH for the same transport block is semi-persistently scheduled and cyclicShiftSPS is not configured, or - if the initial PUSCH for the same transport block is scheduled by the random-access response grant. An exception applies if subframe-based PUSCH for the transport block is semi-persistently scheduled and the higher-layer parameter cyclicShiftSPS is configured. In this case, the value of is given by Table 5.5.2.1.1-1 according to the higher-layer parameter cyclicShiftSPS. An exception applies if subslot-PUSCH/slot-PUSCH for the transport block is semi-persistently scheduled (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] , sps-ConfigUL-sTTI). In this case: - is given by Table 5.5.2.1.1-1 according to the higher-layer parameter cyclicShiftSPS-STTI if the higher layer parameter ifdma-Config-SPS is not set, and, - and are given by Table 5.5.2.1.1-3 according to the higher-layer parameter cyclicShiftSPS-STTI if the higher layer parameter ifdma-Config-SPS is set. The quantity is given by where the pseudo-random sequence is defined by clause 7.2. The application of is cell-specific. The pseudo-random sequence generator shall be initialized with at the beginning of each radio frame. The quantity is given by if no value for is configured by higher layers for PUSCH/(S)PUCCH format 4/PUCCH format 5 or the PUSCH transmission corresponds to a Random Access Response Grant or a retransmission of the same transport block as part of the contention based random access procedure, otherwise it is given by . The vector of reference signals shall be precoded according to where is the number of antenna ports used for PUSCH transmission. For PUSCH transmission using a single antenna port, , and . For spatial multiplexing, or and the precoding matrix shall be identical to the precoding matrix used in clause 5.3.3A.2 for precoding of the PUSCH in the same subframe. Table 5.5.2.1.1-1: Mapping of Cyclic Shift Field in uplink-related DCI format to and Table 5.5.2.1.1-2: Mapping of cyclicShift to values Table 5.5.2.1.1-3: Mapping of Cyclic Shift Field in uplink-related DCI format to , , and Table 5.5.2.1.1-4: for subslot-PUSCH/slot-PUSCH | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.5.2.1.1 |
6,323 | 8.13.1 Signalling based MDT activation | The signalling flow for Signalling based MDT activation involving E1 and F1 is shown in Figure 8.13.1-1. Figure8.13.1-1 Signalling based MDT Activation 1. The AMF starts a trace session and sends a TRACE START message to the gNB. The AMF shall consider the MDT user consent information when activating an MDT trace session for the UE as defined in TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ] [20]. TRACE START message includes the parameters for configuring MDT measurements. 2. The gNB-CU-CP decides if the gNB-CU-UP, or the gNB-DU, or both, should be involved in the MDT measurement. If the gNB-CU-UP should be involved in the MDT measurement, the gNB-CU-CP sends TRACE START message to the gNB-CU-UP, including MDT configuration parameters. 3. If the gNB-DU should be involved in the MDT measurement, the gNB-CU-CP sends TRACE START message to the gNB-DU, including MDT configuration parameters. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.13.1 |
6,324 | 5.4.6.3 Core Network assisted RAN paging information | Core Network assisted RAN paging information aids the RAN to formulate a RAN paging policy and strategy in RRC_INACTIVE state, besides the PPI and QoS information associated to the QoS Flows as indicated in clause 5.4.3. CN assisted RAN paging information may be derived by the AMF per UE and/or per PDU Session based on collection of UE behaviour statistics, Expected UE Behaviour and/or other available information about the UE (such as subscribed DNN, SUPI ranges, Multimedia priority service), and/or information received from other network functions when downlink signalling is triggered. The CN assisted RAN paging information consists of a service priority (values 1 to 256) which provides AN with a way to understand how important the downlink signalling is. The AMF derives this service priority based on available information as described above. The method to derive the service priority is implementation depended and can be controlled by operator. The Core Network may provide the CN assisted RAN paging information to RAN in different occasions, e.g. during downlink N1 and N2 message delivery, etc. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.4.6.3 |
6,325 | 4.11.0a.2a.8 UE Policy Association Termination initiated by PCF for PDU session | The following case is considered for UE Policy Association Termination: 1. UE Detach from the EPS. 2. PDN connection for UE which is used for delivery of UE Policy Container in EPS is released. 3. Changing of RAT type from EPS to 5GS, notified to PCF for the PDU Session by SMF+P-GW-C. Figure 4.11.0a.2a.8-1: UE Policy Association termination in EPS This procedure applies for non-roaming scenarios, LBO roaming scenarios and Home Routed roaming scenario. In the non-roaming case, the V-PCF for the UE is not involved, the role of the V-PCF for the PDU session is performed by the PCF for the PDU session and the role of the H-PCF for the UE is performed by the PCF for the UE. For the LBO roaming scenarios, the V-PCF for the PDU session interacts with the V-PCF for the UE and the V-PCF for the UE interacts with the H-PCF for the UE. In the Home Routed roaming scenario, the V-PCF for the UE is not involved, the role of the V-PCF for the PDU session is performed by the PCF for the PDU session in HPLMN and the role of the H-PCF for the UE is performed by the PCF for the UE in HPLMN. 1. The (V-)PCF for the PDU session terminates a UE Policy Association with the (V-)PCF for the UE when: - The SMF+P-GW-C notifies the changing of RAT type from EPS to 5GS; or - The SMF+P-GW-C terminates the SM policy association with (V-)PCF for the PDU session due to UE detached from EPS or the PDN connection for UE which is used for delivery of UE Policy Container in EPS is released. 2. Same as in clause 4.16.13.1 step 2, replace AMF with (V-)PCF for the PDU session. 3. Same as in clause 4.16.13.1 step 3, replace AMF with (V-)PCF for the PDU session. 4. Same as in clause 4.16.13.1 step 4. 5. Same as in clause 4.16.13.1 step 5. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.0a.2a.8 |
6,326 | 9.3.2.2 Handover and redirection | The source NG-RAN node decides between handover or redirection to EPS based on radio criteria and availability of the N26 interface. NOTE: Information about the availability of the N26 interface may be configured by OAM at the NG-RAN. Inter RAT handover is characterised by the following: - The Source RAT configures Target RAT measurement and reporting. - The source RAT decides on the preparation initiation and provides the necessary information to the target RAT in the format required by the target RAT. - Radio resources are prepared in the target RAT before the handover. - The RRC reconfiguration message from the target RAT is delivered to the source RAT via a transparent container, and is passed to the UE by the source RAT in the handover command. - In-sequence and lossless handovers are not supported. - Security procedures for handover to E-UTRA/EPC should follow E-UTRA handover procedures. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 9.3.2.2 |
6,327 | 9.5.5.1 FDD | The minimum performance requirement in Table 9.5.5.1-2 is defined as a) The ratio of the throughput obtained when transmitting based on UE reported RI and that obtained when transmitting with fixed rank 1 shall be ≥ ; b) The ratio of the throughput obtained when transmitting based on UE reported RI and that obtained when transmitting with fixed rank 2 shall be ≥ ; c) For Test 2, the RI reported for CSI process 1 shall be the same as the most recent RI reported for CSI process 0 if UE is configured with multiple CSI processes. For the parameters specified in Table 9.5.5.1-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.5.5.1-2. Table 9.5.5.1-1: RI Test (FDD) Table 9.5.5.1-2: Minimum requirement (FDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.5.5.1 |
6,328 | 6.10.1 Cell-specific Reference Signal (CRS) | The UE may assume cell-specific reference signals are, unless otherwise stated in [4, clause 12], transmitted in - all downlink subframes for frame structure type 1, - all downlink subframes and DwPTS for frame structure type 2, - non-empty subframes for frame structure type 3 in a cell supporting PDSCH transmission. If special subframe configuration 10 is configured by the higher layer signalling ssp10-CRS-LessDwPTS, the UE cannot assume that cell specific reference signals are transmitted in the 5th OFDM symbol of the special subframe. Cell-specific reference signals are transmitted on one or several of antenna ports 0 to 3. Cell-specific reference signals are transmitted in subframes where only. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.10.1 |
6,329 | 5.27.1.6 Distribution of Announce messages and best master clock selection | The procedure described in this clause is applicable if DS-TT and NW-TT support operating as a Boundary Clock described in IEEE Std 1588 [126] or as a time-aware system (support of the IEEE 802.1AS [104] PTP profile) and when the PTP instance in 5GS is configured to operate as a time-aware system or as a Boundary Clock. Whether DS-TT/NW-TT support operating as a Boundary Clock or as a time-aware system may be determined as described in clause K.2.1. The externally-observable behaviour of the Announce message handling by 5GS needs to comply with IEEE Std 802.1AS [104] or IEEE Std 1588 [126], respective to the configured mode of operation. The DS-TT forwards the received Announce messages to NW-TT over User plane. The NW-TT port forwards the received Announce messages from N6 interface to NW-TT. The NW-TT maintains the PTP port state for each DS-TT port and NW-TT port. The PTP port states may be determined by NW-TT either via: - Method a), BMCA procedure. - Method b), local configuration. When Method b) is used, the following applies: - When the PTP GM is external to the 5GS, for one of the NW-TT or DS-TT ports (per each PTP domain) the PTP port state is Follower and for all other NW-TT and DS-TT ports of the same PTP domain the PTP port state is set either to Passive or Leader (depending on implementation). - When the 5GS is configured as a grandmaster for a (g)PTP domain for the connected networks, all NW-TT ports and DS-TT ports are set to Leader state for that (g)PTP domain. The local configuration of PTP port states in DS-TT and NW-TT for Method b is described in clause K.2. When the Method a) is used (PTP port states are determined by BMCA procedure), the NW-TT needs to process the received Announce messages (from NW-TT port(s) and over user plane from the DS-TT(s)) for BMCA procedure, determine port states within the 5GS, and maintain the Leader-Follower hierarchy. The DS-TT maintains the Disabled, Initializing and Faulty (if applicable) state for the PTP ports in DS-TT. While in Disabled, Initializing or Faulty state, the port in the DS-TT discards any (g)PTP messages it may receive from the upstream PTP instance or from the NW-TT via user plane. When the 5GS Clock is determined as a grandmaster for a (g)PTP domain, the Announce messages are distributed as described in clause 5.27.1.7. When the grandmaster is external to the 5GS, the NW-TT regenerates the Announce messages based on the Announce messages received from Follower port in NW-TT or DS-TT for the Leader ports in NW-TT and DS-TT(s). The NW-TT/UPF forwards the regenerated Announce messages to the PDU session(s) related to the Leader ports in the DS-TT(s). NOTE 1: The TSN AF or TSCTSF can use the portDS.portState in the "Time synchronization information for each DS-TT port" element in UMIC to read and get notified for the port state changes for the PTP ports in DS-TT(s), and the portDS.portState in PMIC to read and get notified for the port state changes for the PTP ports in NW-TT. Based on the change of the port states, TSN AF or TSCTSF can determine that an external Grandmaster PTP Instance is found to be used instead of the GM in 5GS, or the GM in 5GS is selected as the Grandmaster PTP Instance, and TSN AF or TSCTSF can disable or enable the (g)PTP grandmaster functionality in DS-TT(s), respectively. NOTE 2: The TSN AF or TSCTSF can use the portDS.portState in PMIC to read and get notified for the port state changes for the PTP ports in DS-TT for the port state Disabled, Initializing or Faulty (if applicable). The TSCTSF or TSN AF can use the portDS.portEnable to indicate to the NW-TT that the DS-TT port is disabled. This avoids unnecessary (g)PTP traffic over User Plane to a DS-TT port in Disabled, Initializing or Faulty state. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.27.1.6 |
6,330 | 4.4.4.3 Integrity checking of NAS signalling messages in the AMF | Except the messages listed below, no NAS signalling messages shall be processed by the receiving 5GMM entity in the AMF or forwarded to the 5GSM entity, unless the secure exchange of NAS messages has been established for the NAS signalling connection: a) REGISTRATION REQUEST; b) IDENTITY RESPONSE (if requested identification parameter is SUCI); c) AUTHENTICATION RESPONSE; d) AUTHENTICATION FAILURE; e) SECURITY MODE REJECT; f) DEREGISTRATION REQUEST; and g) DEREGISTRATION ACCEPT; NOTE 1: The REGISTRATION REQUEST message is sent by the UE without integrity protection, if the registration procedure is initiated due to an inter-system change in 5GMM-IDLE mode and no current 5G NAS security context is available in the UE. The other messages are accepted by the AMF without integrity protection, as in certain situations they are sent by the UE before security can be activated. NOTE 2: The DEREGISTRATION REQUEST message can be sent by the UE without integrity protection, e.g. if the UE is registered for emergency services and there is no valid 5G NAS security context available, or if due to user interaction a registration procedure is cancelled before the secure exchange of NAS messages has been established. For these cases the network can attempt to use additional criteria (e.g. whether the UE is subsequently still performing periodic registration update or still responding to paging) before marking the UE as 5GMM-DEREGISTERED. Integrity protection is never applied directly to 5GSM messages, but to the 5GMM message in which the 5GSM message is included. Once a current 5G NAS security context exists, until the secure exchange of NAS messages has been established for the NAS signalling connection, the receiving 5GMM entity in the AMF shall process the following NAS signalling messages, even if the MAC included in the message fails the integrity check or cannot be verified, as the 5G NAS security context is not available in the network: a) REGISTRATION REQUEST; b) IDENTITY RESPONSE (if requested identification parameter is SUCI); c) AUTHENTICATION RESPONSE; d) AUTHENTICATION FAILURE; e) SECURITY MODE REJECT; f) DEREGISTRATION REQUEST; g) DEREGISTRATION ACCEPT; h) SERVICE REQUEST; and i) CONTROL PLANE SERVICE REQUEST; NOTE 3: These messages are processed by the AMF even when the MAC that fails the integrity check or cannot be verified, as in certain situations they can be sent by the UE protected with a 5G NAS security context that is no longer available in the network. If a REGISTRATION REQUEST message for initial registration fails the integrity check and it is not a registration request for emergency services, the AMF shall authenticate the subscriber before processing the registration request any further. Additionally, the AMF shall initiate a security mode control procedure, and include the Additional 5G security information IE with the RINMR bit set to "Retransmission of the initial NAS message requested" in the SECURITY MODE COMMAND message as specified in subclause 5.4.2.2. If authentication procedure is not successful the AMF shall maintain, if any, the 5GMM-context and 5G NAS security context unchanged.For the case when the registration procedure is for emergency services see subclause 5.5.1.2.3 and subclause 5.4.1.3.5. If a REGISTRATION REQUEST message for mobility and periodic registration update fails the integrity check and the UE provided EPS NAS message container IE which was successfully verified by the source MME, the AMF may create a mapped 5G NAS security context and initiate a security mode control procedure to take the new mapped 5G NAS security context into use; otherwise if the UE has only a non-emergency PDU session established, the AMF shall initiate a primary authentication and key agreement procedure to create a new native 5G NAS security context. Additionally, the AMF shall initiate a security mode control procedure, and include the Additional 5G security information IE with the RINMR bit set to "Retransmission of the initial NAS message requested" in the SECURITY MODE COMMAND message as specified in subclause 5.4.2.2. If authentication procedure is not successful the AMF shall maintain, if any, the 5GMM-context and 5G NAS security context unchanged. For the case when the UE has an emergency PDU session see subclause 5.5.1.3.3 and subclause 5.4.1.3.5. If a DEREGISTRATION REQUEST message fails the integrity check, the AMF shall proceed as follows: - If it is not a deregistration request due to switch off, and the AMF can initiate an authentication procedure, the AMF should authenticate the subscriber before processing the deregistration request any further. - If it is a deregistration request due to switch off, or the AMF does not initiate an authentication procedure for any other reason, the AMF may ignore the deregistration request and remain in state 5GMM-REGISTERED. NOTE 4: The network can attempt to use additional criteria (e.g. whether the UE is subsequently still performing periodic registration update or still responding to paging) before marking the UE as 5GMM-DEREGISTERED. If a SERVICE REQUEST or CONTROL PLANE SERVICE REQUEST message fails the integrity check and the UE has only non-emergency PDU sessions established, the AMF shall send the SERVICE REJECT message with 5GMM cause #9 "UE identity cannot be derived by the network" and keep the 5GMM-context and 5G NAS security context unchanged. For the case when the UE has an emergency PDU session and integrity check fails, the AMF may skip the authentication procedure even if no 5G NAS security context is available and proceed directly to the execution of the security mode control procedure as specified in subclause 5.4.2. Additionally, the AMF shall include the Additional 5G security information IE with the RINMR bit set to "Retransmission of the initial NAS message requested" in the SECURITY MODE COMMAND message as specified in subclause 5.4.2.2. After successful completion of the service request procedure, the network shall perform a local release of all non-emergency PDU sessions. The emergency PDU session shall not be released. Once the secure exchange of NAS messages has been established for the NAS signalling connection, the receiving 5GMM entity in the AMF shall not process any NAS signalling messages unless they have been successfully integrity checked by the NAS. If any NAS signalling message, having not successfully passed the integrity check, is received, then the NAS in the AMF shall discard that message. If any NAS signalling message is received, as not integrity protected even though the secure exchange of NAS messages has been established, then the NAS shall discard this message. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.4.4.3 |
6,331 | 5.2.27.3.5 Ntsctsf_QoSandTSCAssistance_Notify operation | Service operation name: Ntsctsf_QoSandTSCAssistance_Notify Description: TSCTSF reports the QoS Flow level event(s) to the consumer. Inputs, Required: Notification Correlation ID, Reports of the events as defined in clause 6.1.3.18 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. Inputs, Optional: When the event report is for QoS Monitoring, includes QoS Monitoring report for the QoS parameter(s) to be measured defined in clause 5.45 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], e.g. UL packet delay, DL packet delay, or round trip packet delay of the single UP path or two UP paths in the case of redundant transmission, as defined in clause 5.33.3.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. When the AF has provided Capability for BAT Adaptation or BAT Window, can include BAT offset as described in clause 5.27.2.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Outputs, Required: None. Output (optional): None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.27.3.5 |
6,332 | 4.7.7.6.1 MS behaviour towards a network that has failed the authentication procedure | If the MS deems that the network has failed the authentication check, then it shall request RR or RRC to release the RR connection and the PS signalling connection, if any, and bar the active cell or cells (see 3GPP TS 25.331[ None ] [23c] and 3GPP TS 44.018[ None ] [84]). The MS shall start any retransmission timers (i.e. T3310, T3321, T3330 or T3317), if they were running and stopped when the MS received the first AUTHENTICATION AND CIPHERING REQUEST message containing an invalid MAC or invalid SQN, or no AUTN when a UMTS authentication challenge was expected. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.7.6.1 |
6,333 | 6.10 Bandwidth Adaptation | With Bandwidth Adaptation (BA), the receive and transmit bandwidth of a UE need not be as large as the bandwidth of the cell and can be adjusted: the width can be ordered to change (e.g. to shrink during period of low activity to save power); the location can move in the frequency domain (e.g. to increase scheduling flexibility); and the subcarrier spacing can be ordered to change (e.g. to allow different services). A subset of the total cell bandwidth of a cell is referred to as a Bandwidth Part (BWP) and BA is achieved by configuring the UE with BWP(s) and telling the UE which of the configured BWPs is currently the active one. Figure 6.10-1 below describes a scenario where 3 different BWPs are configured: - BWP1 with a width of 40 MHz and subcarrier spacing of 15 kHz; - BWP2 with a width of 10 MHz and subcarrier spacing of 15 kHz; - BWP3 with a width of 20 MHz and subcarrier spacing of 60 kHz. Figure 6.10-1: BA Example | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 6.10 |
6,334 | 4.17.2 NF service update | Figure 4.17.2-1: NF Service Update procedure 1. NF service consumer i.e. an NF instance sends Nnrf_NFManagement_NFUpdate Request message (the updated NF profile of NF service consumer) to NRF to inform the NRF of its updated NF profile (e.g. with updated capacity) when e.g. triggered after a scaling operation. See clause 5.2.7.2.3 for relevant input and output parameters. NOTE: The updated NF profile of NF instance are configured by OAM system. 2. The NRF updates the NF profile of NF service consumer. 3. The NRF acknowledge NF Update is accepted via Nnrf_NFManagement_NFUpdate response. NOTE 4: When the NF service consumer registers to NRF via the SCP, the NF Service registration procedure can also be used by the SCP to derive the relation among NF instances, e.g. whether they belong to a specific NF Set. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.17.2 |
6,335 | 8.2.2.4.1E Minimum Requirement Single-Layer Spatial Multiplexing 2 Tx Antenna Ports with CRS assistance information | The requirements are specified in Table 8.2.2.4.1E-2, with the addition of parameters in Table 8.2.2.4.1E-1. The purpose is to verify the closed loop rank-one performance with wideband precoding when CRS assistance information [7] is configured. In Table 8.2.2.4.1E-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] includes Cell 2 and Cell 3. Table 8.2.2.4.1E-1: Test Parameters for Single-Layer Spatial Multiplexing (FRC) Table 8.2.2.4.1E-2: Minimum Performance Single-Layer Spatial Multiplexing (FRC) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.2.4.1E |
6,336 | 5.5.4.2 Event A1 (Serving becomes better than threshold) | The UE shall: 1> consider the entering condition for this event to be satisfied when condition A1-1, as specified below, is fulfilled; 1> consider the leaving condition for this event to be satisfied when condition A1-2, as specified below, is fulfilled; 1> for this measurement, consider the NR serving cell corresponding to the associated measObjectNR associated with this event. Inequality A1-1 (Entering condition) Ms – Hys > Thresh Inequality A1-2 (Leaving condition) Ms + Hys < Thresh The variables in the formula are defined as follows: Ms is the measurement result of the serving cell, not taking into account any offsets. Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigNR for this event). Thresh is the threshold parameter for this event (i.e. a1-Threshold as defined within reportConfigNR for this event). Ms is expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR. Hys is expressed in dB. Thresh is expressed in the same unit as Ms. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.4.2 |
6,337 | 9.3.1.1.5 TDD (when csi-SubframeSet –r12 is configured) | The following requirements apply to UE Category ≥1 which supports Rel-12 CSI subframe sets. For the parameters specified in Table 9.3.1.1.5-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.3.1.1.5-2 and by the following a) a sub-band differential CQI offset level of 0 shall be reported at least % of the time but less than % for each sub-band for each CSI subframe set; b) the ratio of the throughput obtained when transmitting on a randomly selected sub-band among the sub-bands with the highest differential CQI offset level the corresponding TBS and that obtained when transmitting the TBS indicated by the reported wideband CQI median on a randomly selected sub-band in set S shall be ≥ for each CSI subframe set; c) when transmitting on a randomly selected sub-band among the sub-bands with the highest differential CQI offset level the corresponding TBS, the average BLER for the indicated transport formats shall be greater or equal to 0.05 and less than 0.60 for each CSI subframe set. d) the difference of the wide-band median CQI obtained by reports in CSI subframe sets CCSI,0 and the wide-band median CQI obtained by reports in CSI subframe sets CCSI,1 shall be larger than or equal to 3. The requirements only apply for sub-bands of full size and the random scheduling across the sub-bands is done by selecting a new sub-band in each available downlink transmission instance. Sub-bands of a size smaller than full size are excluded from the test. Table 9.3.1.1.5-1: Sub-band test for TDD Table 9.3.1.1.5-2: Minimum requirement (TDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.3.1.1.5 |
6,338 | 4.7.9.1.1 Paging for GPRS services using P-TMSI | The network shall initiate the paging procedure for GPRS services using P-TMSI when GMM signalling messages or user data is pending to be sent to the MS while the mobile reachable timer is running. The network may page only GPRS MSs which are GMM-REGISTERED and identified by a local P-TMSI. In Iu mode, for the MS using eDRX, the network initiates the paging procedure when the paging trigger is received within the paging time window. If the paging trigger is received outside the paging time window, the network initiates the paging procedure at T time ahead of the beginning of the next paging time window. NOTE: T time is a short time period based on implementation. The operator can take possible imperfections in the synchronization between the CN and the MS into account when choosing T time. In Iu mode, to initiate the procedure the GMM entity in the network requests the lower layer to start paging (see 3GPP TS 25.331[ None ] [23c] and 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [19c]) and shall start the timer: - T3315 for this paging procedure, if the network accepted to use eDRX for the MS. - Otherwise T3313 for this paging procedure. In Iu mode, if the network starts the timer T3315, the network shall set the timer T3315 to a value smaller than the value of timer T3-RESPONSE (see 3GPP TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [16D] for further details on timer T3-RESPONSE). In Iu mode, the GMM entity in the network may provide the lower layer with a list of CSG IDs, including the CSG IDs of both the expired and the unexpired subscriptions. If there is a PDN connection for emergency bearer services established, the GMM entity in the network shall not provide the list of CSG IDs to the lower layer. Upon reception of a paging indication, the MS shall stop the timer T3346, if running, and: - initiate a service request procedure to respond to the paging, the MS shall set the service type to "paging response" in the SERVICE REQUEST message (see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20], 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74], 3GPP TS 25.331[ None ] [23c] and 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [19c]); or - initiate a routing area update procedure as specified in subclauses 4.7.5.1 and 4.7.5.2.1. If the paging request for GPRS services was received during an ongoing MS initiated GMM specific procedure, then the MS shall progress the GMM specific procedure, and the network shall proceed with the GMM specific procedure. In A/Gb mode, to initiate the procedure the GMM entity requests the RR sublayer to start paging (see 3GPP TS 44.018[ None ] [84], 3GPP TS 44.060[ None ] [76]), and shall start the timer: - T3315 for this paging procedure, if the network accepted to use eDRX for the MS. - Otherwise T3313 for this paging procedure. In A/Gb mode, if the network starts the timer T3315, the network shall set the timer T3315 to a value smaller than the value of timer T3-RESPONSE (see 3GPP TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [16D] for further details on timer T3-RESPONSE). In A/Gb mode, upon reception of a paging indication, the MS shall respond to the paging with any LLC frame (see 3GPP TS 44.064[ Mobile Station - Serving GPRS Support Node (MS-SGSN); Logical Link Control (LLC) Layer Specification ] [78a], 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20], 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74]). At intersystem change, an MS not having the READY timer running in A/Gb mode or an MS in PMM-IDLE mode in Iu mode, being paged in a different access network as when it last sent user data or signalling message, uses the ROUTING AREA UPDATE REQUEST message as paging response, i.e. the routing area updating procedure shall be performed instead according to the selective routing area updating procedure. The network shall stop the timer for the paging procedure (i.e. either timer T3313 or timer T3315) when a response is received from the MS. Upon expiry ofthe timer T3313, the network may re-initiate paging. Upon expiry of the timer T3315, the network shall abort the paging procedure and shall proceed as specified in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74]. In Iu mode, when a response is received from the MS, the network shall change from PMM-IDLE mode to PMM-CONNECTED mode. In A/Gb mode, when a response different from an LLC NULL frame is received from the MS, the network shall start the READY timer. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.9.1.1 |
6,339 | 9.11.4.25 DS-TT Ethernet port MAC address | The purpose of the DS-TT Ethernet port MAC address information element is to signal the MAC address of the DS-TT Ethernet port used for a PDU session of "Ethernet" PDU session type. The DS-TT Ethernet port MAC address information element is coded as shown in figure 9.11.4.25.1 and table 9.11.4.25.1. The DS-TT Ethernet port MAC address is a type 4 information element with a length of 8 octets. Figure 9.11.4.25.1: DS-TT Ethernet port MAC address information element Table 9.11.4.25.1: DS-TT Ethernet port MAC address information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.4.25 |
6,340 | 5.3.5.13.7 sk-Counter configuration addition/modification/removal | The UE shall: 1> for each securityCellSetId received in the sk-CounterConfigToAddModList IE: 2> if an entry with the matching securityCellSetId exists in the sk-CounterConfigToAddModList within the VarConditionalReconfig: 3> replace the sk-CounterList within the VarConditionalReconfig with the sk-CounterList according to the received securityCellSetId; 2> else: 3> add a new entry for this securityCellSetId within the VarConditionalReconfig; 1> for each securityCellSetId value included in the sk-CounterConfigToRemoveList that is part of the current sk-CounterConfigToAddModList in VarConditionalReconfig: 2> remove the entry with the matching securityCellSetId from the sk-CounterConfigToAddModList; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.13.7 |
6,341 | 4.11.1 N26 based Interworking Procedures 4.11.1.1 General | N26 interface is used to provide seamless session continuity for single registration mode UE. Interworking between EPS and 5GS is supported with IP address preservation by assuming SSC mode 1. When the UE is served by the 5GC, during PDU Session establishment and GBR QoS Flow establishment, SMF+PGW-C performs EPS QoS mappings, from the 5G QoS parameters obtained from the PCF and allocates TFT with the PCC rules obtained from the PCF if PCC is deployed. Otherwise, EPS QoS mappings and TFT allocation are mapped by the SMF+PGW-C locally. The PGW+SMF ignores 5G QoS parameters that are not applicable to EPC (e.g. QoS Notification control). If a TFT is to be allocated for a downlink unidirectional EPS bearer mapped from a downlink only QoS Flow, the SMF+PGW-C shall allocate a TFT packet filter that effectively disallows any useful uplink packet as specified in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. EPS Bearer IDs are allocated by the serving AMF requested by the SMF if the SMF determines that EPS Bearer IDs need to be assigned to the QoS Flows. For each PDU Session, EPS bearer IDs are allocated to the default EPS bearer and dedicated bearers. The SMF shall be able to determine the QoS flows that require EPS Bearer IDs, based on the QoS profile and operator policies. NOTE 1: Based on operator policies, an SMF can map all non-GBR QoS flows to default EPS bearer in which case it requests only one EBI for all the non-GBR QoS flows. Alternatively, an SMF can also map one non-GBR QoS flow to one dedicated EPS bearer in which case it requests a dedicated EBI for non-GBR QoS flow that should be mapped to dedicated EPS bearer. In between these two extreme cases, the SMF can also map more than one (but not all) non-GBR QoS Flow to the same EPS bearer (either default EPS bearer or dedicated EPS bearer). NOTE 2: To reduce the probability of AMF revoking the EBI corresponding to the QoS Flow associated with the default QoS rule, ARP priority level of dedicated QoS Flows can be set to higher value than that of the QoS Flow associated with the default QoS rule within the same PDU Session. When a new QoS Flow needs to be mapped to an EPS Bearer ID that has already been assigned for an existing QoS Flow, the SMF includes the already assigned EPS Bearer ID in the QoS Flow description sent to the UE. If there is a possibility to run into a restriction regarding the number of TFT packet filters that can be allocated for the PDU Session, - in the case that PCC is deployed, the PCF may include in the PCC rules the Precedence for TFT packet filter allocation parameter, which determines the order of the PCC rules in allocation of TFT packet filter(s) by the SMF+PGW-C. - in the case that PCC is deployed but the Precedence for TFT packet filter allocation parameter is not received, or in the case that PCC is not deployed, the SMF+PGW-C makes the decision how to allocate TFT packet filter(s) based on operator policy or implementation. NOTE 3: An EPS bearer can have up to 16 TFT packet filters. For Ethernet and Unstructured PDU Session Types, only EPS Bearer ID for the default EPS Bearer is allocated. The EPS Bearer IDs for these EPS bearers are provided to the SMF+PGW-C by the AMF and are provided to the UE and NG-RAN by the SMF+PGW-C using N1 SM NAS message and N2 SM message. The UE is also provided with the mapped QoS parameters. The UE and the SMF+PGW-C store the association between the QoS Flow and the corresponding EBI and the EPS QoS parameters. When the QoS Flow is deleted e.g. due to PDU Session status synchronization or PDU Session Modification, the UE and the SMF+PGW-C delete any possibly existing EPS QoS parameters associated with the deleted QoS Flow. In this release, for a PDU Session for a LADN or for Multi-homed IPv6 PDU Session, the SMF doesn't allocate any EBI or mapped QoS parameters. For PDU Sessions with UP integrity protection of UP Security Enforcement Information set to Required, the SMF does not allocate any EBI or mapped QoS parameters unless the UE support User Plane Integrity Protection with EPS and the AMF supports the associated functionality. If the UE supports User Plane Integrity Protection with EPS, as indicated in the S1 UE network capability and the AMF supports the related functionality, the AMF indicates the UE support for EPS User Plane Integrity Protection to SMF. Then, for PDU Sessions with UP integrity protection of UP Security Enforcement Information set to Required, the SMF may perform the EPS bearer ID allocation procedure as described in clause 4.11.1.4. If the MME indicates support for EPS User Plane Integrity Protection to SMF+PGW-C, the SMF+PGW-C provides User Plane Security Enforcement Information for the EPS bearer contexts to the MME (via the SGW). When the UE is served by the EPC, during PDN connection establishment, the UE allocates the PDU Session ID and sends it to the SMF+PGW-C via PCO. During PDN Connection establishment and dedicated bearer establishment, SMF+PGW-C performs EPS QoS mappings, from the 5G QoS parameters obtained from the PCF and allocates TFT with the PCC rules obtained from the PCF if PCC is deployed. Otherwise, EPS QoS mappings and TFT allocation are mapped by the SMF+PGW-C locally. Other 5G QoS parameters corresponding to the PDN connection, e.g. Session AMBR and QoS rules and QoS Flow level QoS parameters if needed for the QoS Flow(s) associated with the QoS rule(s), are sent to UE in PCO. The UE and the SMF+PGW-C store the association between the EPS Context and the PDU Session Context to use it in the case of handover from EPS to 5GS. During the EPS bearer establishment/modification procedure, QoS rules corresponding to the related EPS bearers are allocated and sent to UE in PCO. The 5G QoS parameters are stored in the UE and are to be used when the UE is handed over from EPS to the 5GS. The 5G QoS parameters may be provided to SMF+PGW-C by the PCF, if PCC is deployed. On mobility from EPS to 5GS, the UE sets the SSC mode of the mapped PDU Session to SSC mode 1. The UE and the SMF+PGW-C store the association between the EPS bearer and the corresponding 5G QoS Rules and QoS Flow level QoS parameters if needed for the QoS Flow(s) associated with the QoS rule(s). When the EPS bearer is deleted e.g. due to EPS bearer status synchronization or bearer deactivation, the UE and the SMF+PGW-C delete any possibly existing 5G QoS Rule(s) and QoS Flow level QoS parameters if any for the QoS Flow(s) associated with the QoS rule(s) associated with the deleted EPS bearer. In the roaming case, if the VPLMN supports interworking with N26, the UE shall operate in Single Registration mode. During the 5GS-EPS handover, indirect forwarding may apply for the downlink data forwarding performed as part of the handover. From its configuration data the AMF knows whether indirect forwarding applies and it requests to allocate downlink data forwarding paths on UPFs for indirect forwarding. From its configuration data the MME knows whether indirect forwarding applies and it requests to allocate downlink data forwarding paths on Serving GWs for indirect forwarding. It is configured on AMF and MME whether indirect downlink data forwarding does not apply, applies always or applies only for inter PLMN inter RAT handovers. During the 5GS-EPS handover, direct forwarding may apply for the downlink data forwarding performed as part of the handover. From its configuration data the source RAN node knows whether direct forwarding applies and indicates to source CN the direct data forwarding is available. During 5GS-EPS handover, on the target side, the CN informs the target RAN node whether data forwarding is possible or not. During interworking from EPS to 5GS, as the SMF+PGW-C may have different IP addresses when being accessed over S5/S8 and N11/N16 respectively, the AMF shall discover the SMF instance by an NF/NF service discovery procedure using the FQDN for the S5/S8 interface received from the MME as a query parameter. This is required for both non-roaming and roaming with local breakout, as well as for home routed roaming. NOTE 4: As the AMF is not aware of the S-NSSAI assigned for the PDN Connection, the NF/NF service discovery used to find the SMF instance can use PLMN level NRF. During interworking from 5GS to EPS, for QoS Flows without EPS bearer ID(s) assigned or for QoS Flows with PCC rules that do not have allocated TFT packet filters, the SMF+PGW-C deletes the PCC rules associated with those QoS Flows and informs the PCF about the removed PCC rule(s). During interworking from 5GS to EPS, as a PDU Session may be released while the UE is served by EPS, if Small Data Rate Control is used the SMF+PGW-C obtains the Small Data Rate Control Status from the PGW-U+UPF in the N4 Session Modification procedure or from the SCEF+NEF and passes the Small Data Rate Control Status in the PDU Session Context Response to the AMF, for the AMF to store. The time to store the Small Data Rate Control Statuses is implementation specific. If the UE and PGW-U+UPF / SCEF+NEF have stored APN Rate Control parameters and optionally APN Rate Control Status they are only applied when the UE is served by EPS. During interworking from 5GS to EPS, for PDU Sessions with UP integrity protection of UP Security Enforcement Information set to Required, the SMF+PGW-C does not provide the EPS bearer context unless both the UE, the target eNB and the target MME support User Plane Integrity Protection with EPS. During interworking from EPS to 5GS the UE and PGW-U+UPF / SCEF+NEF store the APN Rate Control parameters and APN Rate Control Status while the UE is served by 5GS, so they can be used if the UE moves back to EPS. At EPS to 5GS mobility: - The UE considers the PDN connections released if those PDN connections were established over EPS and for which the UE has not received mapped 5GS QoS parameters from the network. NOTE 5: UE not receiving mapped 5GS QoS parameters from the network covers the case that a UE did not provide a PDU Session ID to the network when establishing a PDN connection while UE's N1 mode is disabled and the case that a UE provided PDU Session ID where the network (SMF+PGW-C) does not provide mapped 5GS parameters. - The MME does not transfer to 5GS a PDN connection that does not support 5GS interworking, e.g. PDN connection was established on a stand-alone PGW, or 5GS interworking is restricted by subscription data. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.1 |
6,342 | 6.5.2.3 UE requested PDN disconnection procedure accepted by the network | Upon receipt of the PDN DISCONNECT REQUEST message, if it is accepted by the network, the MME shall initiate the bearer context deactivation procedure by sending the DEACTIVATE EPS BEARER CONTEXT REQUEST message including the linked EPS bearer identity of the default bearer associated with the PDN to disconnect from and the PTI. The behaviour of the MME is described in clause 6.4.4. Upon receipt of the DEACTIVATE EPS BEARER CONTEXT REQUEST message with a PTI which matches the value used for the PDN DISCONNECT REQUEST message, the UE shall stop the timer T3492 and enter the state PROCEDURE TRANSACTION INACTIVE. The behaviour of the UE is described in clause 6.4.4. The UE should ensure that the procedure transaction identity (PTI) assigned to this procedure is not released immediately. The way to achieve this is implementation dependent. While the PTI value is not released, the UE regards any received DEACTIVATE EPS BEARER CONTEXT REQUEST message with the same PTI value as a network retransmission (see clause 7.3.1). On reception of DEACTIVATE EPS BEARER CONTEXT ACCEPT message from the UE, the MME releases all the resources reserved for the PDN in the network. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.5.2.3 |
6,343 | – SL-LBT-FailureRecoveryConfig | The IE SL-LBT-FailureRecoveryConfig-r18 is used to configure the parameters used for detection and cancellation of sidelink consistent LBT failures for operation with shared spectrum channel access, as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]. SL-LBT-FailureRecoveryConfig information element -- ASN1START -- TAG-SL-LBT-FAILURERECOVERYCONFIG-START SL-LBT-FailureRecoveryConfig-r18 ::= SEQUENCE { sl-lbt-FailureInstanceMaxCount-r18 ENUMERATED {n4, n8, n16, n32, n64, n128} OPTIONAL, -- Need M sl-lbt-FailureDetectionTimer-r18 ENUMERATED {ms10, ms20, ms40, ms80, ms160, ms320} OPTIONAL, -- Need M sl-LBT-RecoveryTimer-r18 ENUMERATED {ms10, ms20, ms40, ms80, ms160, ms320} OPTIONAL, -- Need M ... } -- TAG-SL-LBT-FAILURERECOVERYCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,344 | 4.2.5.1.8 Substate, PLMN-SEARCH | When the MM state is IDLE, the GMM substate PLMN-SEARCH may be entered if the MS is in automatic network selection mode and the maximum allowed number of consecutive unsuccessful routing area update attempts controlled by the GPRS routing area updating attempt counter (subclause 4.7.5) have been performed. If a new PLMN is selected, the MS shall reset the routing area updating attempt counter and perform the routing area updating procedure. If the selected cell is known not to be able to provide normal service, the MS may initiate GPRS attach for emergency bearer services (UTRAN Iu mode only). | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.2.5.1.8 |
6,345 | 30.5 Structure of Associated Session ID | The concept of Associated Session ID is defined in 3GPP TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [140]. The Associated Session ID is used to enable NG-RAN to identify the multiple MBS sessions delivering the same content when AF creates multiple broadcast MBS Sessions via different Core Networks in network sharing scenarios. An Associated Session ID may comprise a Source Specific IP Multicast Address (SSM) or a string. See clause 5.9.4.21.1 of 3GPP TS 29.571[ 5G System; Common Data Types for Service Based Interfaces; Stage 3 ] [129] for the encoding of Associated Session ID in 5GC SBIs. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 30.5 |
6,346 | 6.3.3A.1 Minimum requirement for CA | For inter-band carrier aggregation with uplink assigned to two E-UTRA bands, transmit OFF power requirement is defined per carrier and the requirement is specified in subclause 6.3.3.1. If two contiguous component carriers are assigned to one E-UTRA band, the requirements in subclause 6.3.3A.1 apply for those component carriers. For intra-band contiguous and non-contiguous carrier aggregation the transmit OFF power is defined as the mean power in a duration of at least one sub-frame (1ms) excluding any transient periods. The transmit OFF power shall not exceed the values specified in Table 6.3.3A.1-1. Table 6.3.3A.1-1: Transmit OFF power for intra-band contiguous and non-contiguos CA UE | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.3.3A.1 |
6,347 | 4.3.8.2 Serving GW selection function | The Serving GW selection function selects an available Serving GW to serve a UE. The selection bases on network topology, i.e. the selected Serving GW serves the UE's location and for overlapping Serving GW service areas, the selection may prefer Serving GWs with service areas that reduce the probability of changing the Serving GW. When SIPTO is allowed then it is also considered as a criterion for Serving GW selection, e.g. when the first PDN connection is requested. Other criteria for Serving GW selection should include load balancing between Serving GWs, UE support for dual connectivity with NR, CIoT EPS Optimisation(s) impacting Serving GW e.g. Non-IP support, Ethernet support, NB-IoT RAT support (for generation of accounting information), etc. When the Serving GW IP addresses returned from the DNS server include Weight Factors, the MME should use it if load balancing is required. The Weight Factor is typically set according to the capacity of a Serving GW node relative to other Serving GW nodes serving the same Tracking area. For further details on DNS procedure see TS 29.303[ Domain Name System Procedures; Stage 3 ] [61]. When the MME supports the GTP-C Load Control feature, it takes into account the Load Information received from the Serving GW in addition to the Weight Factors received from the DNS server to perform selection of an appropriate Serving GW. NOTE 1: How Weight Factors can be used in conjunction with Load Information received via GTP control plane signalling is left up to Stage 3. If a subscriber of a GTP only network roams into a PMIP network, the PDN GWs selected for local breakout support the PMIP protocol, while PDN GWs for home routed traffic use GTP. This means the Serving GW selected for such subscribers may need to support both GTP and PMIP, so that it is possible to set up both local breakout and home routed sessions for these subscribers. For a Serving GW supporting both GTP and PMIP, the MME/SGSN should indicate the Serving GW which protocol should be used over S5/S8 interface. The MME/SGSN is configured with the S8 variant(s) on a per HPLMN granularity. If a subscriber of a GTP only network roams into a PMIP network, the PDN GWs selected for local breakout may support GTP or the subscriber may not be allowed to use PDN GWs of the visited network. In both cases a GTP only based Serving GW may be selected. These cases are considered as roaming between GTP based operators. If combined Serving and PDN GWs are configured in the network the Serving GW Selection Function may preferably derive a Serving GW that is also a PDN GW for the UE. In order to provide SIPTO at the local network service with stand-alone GW, the L-GW and Serving GW shall be co-located. The Serving GW selection function in the MME is used to ensure that the Serving GW is provided according to operator policy as described in clause 4.3.15a. When the L-GW is collocated with the (H)eNB, the Serving GW remains located in the mobile operator's core network. The Domain Name Service function may be used to resolve a DNS string into a list of possible Serving GW addresses which serve the UE's location. The specific interaction between the MME/SGSN and the Domain Name Service function may include functionality to allow for the retrieval or provision of additional information regarding the Serving GW capabilities (e.g. whether the Serving GW supports PMIP-based or GTP-based S5/S8, or both). The details of the selection are implementation specific. For handover from non-3GPP accesses in roaming scenario, the Serving GW selection function for local anchoring is described in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. The Serving GW selection function in the MME is used to ensure that all Tracking Areas in the Tracking Area List belong to the same Serving GW service area. When DCNs with dedicated Serving GWs are used, the DNS procedure (TS 29.303[ Domain Name System Procedures; Stage 3 ] [61]) for Serving GW selection may be used such that a Serving GW belonging to a DCN serving a particular category of UEs, e.g. identified by UE Usage Type, is selected. When UEs with the same UE Usage type are served by multiple DCNs, it shall also be possible to select the Serving GW belonging to the DCN serving the particular UE. NOTE 2: Selection of Serving GWs optimised for different RATs (e.g. NB-IoT) can be achieved by using UE Usage Type and/or by using different TAIs for different RATs. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.8.2 |
6,348 | 7.5 UE Capability Retrieval framework | The UE reports its UE radio access capabilities which are static at least when the network requests. The gNB can request what capabilities for the UE to report based on band information. The UE capability can be represented by a capability ID, which may be exchanged in NAS signalling over the air and in network signalling instead of the UE capability structure. In IAB, it is optional for an IAB-MT to support UE capability Retrieval framework and the related signalling. In case IAB-MT does not support UE capability Retrieval framework, IAB-MT capabilities are assumed to be known to the network by other means, e.g. OAM. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 7.5 |
6,349 | 16a.2 Diameter Accounting | Diameter Accounting shall be used according to RFC 7155 [120]. The Diameter accounting client function may reside in a GGSN/P-GW. The Diameter accounting client may send information to an accounting server, which is identified during the APN provisioning. The accounting server may store this information and use it to automatically identify the user. This information can be trusted because the PS access network has authenticated the subscriber (i.e. SIM card and possibly other authentication methods). Diameter Accounting messages may be used during both primary and secondary PDP context activation for non-EPC based packet domain (both the default bearer and dedicated bearer for the EPC based packet domain) and deactivation procedures respectively. If the AAA server is used for IPv4 address and/or IPv6 prefix assignment, then, upon reception of a Diameter Accounting-Request STOP message for all IP-CAN bearers associated to an IP-CAN session defined by APN and IMSI or MSISDN, the AAA server may make the associated IPv4 address and/or IPv6 prefix available for assignment. For PDN/PDP type IPv4v6 and deferred IPv4 address allocation, when the IPv4 address is allocated or re-allocated, the accounting session that was established for the IPv6 prefix allocation shall be used to inform the accounting server about the allocated IPv4 address by sending Diameter Accounting-Request Interim-Update with Framed-IP-Address AVP and its value field containing the allocated IPv4 address. Similarly, the release of IPv4 address shall be indicated to the accounting server by sending Diameter Accounting-Request Interim-Update without the Framed-IP-Address AVP. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 16a.2 |
6,350 | 9.3.31 User information | This message is sent by the mobile station to the network to transfer information to the remote user. This message is also sent by the network to the mobile station to deliver information transferred from the remote user. This message is used if the user-to-user transfer is part of an allowed information transfer as defined in 3GPP TS 24.010[ Mobile radio interface layer 3; Supplementary services specification; General aspects ] [21]. See table 9.78/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: USER INFORMATION Significance: access Direction: both Table 9.78/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : USER INFORMATION message content | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.3.31 |
6,351 | 5.2.12.2 Nudr_DataManagement (DM) service 5.2.12.2.1 General | The operations defined for Nudr_DM service use following set of parameters defined in this clause: - Data Set Identifier: uniquely identifies the requested set of data within the UDR (see clause 4.2.5). - Data Subset Identifier: it uniquely identifies the data subset within each Data Set Identifier. As specified in the procedures in clause 4, e.g. subscription data can consist of subsets particularised for specific procedures like mobility, session, etc. - Data Keys defined in Table 5.2.12.2.1-1 For Nudr_DM_Subscribe and Nudr_DM_Notify operations: - The Target of Event Reporting is made up of a Data Key and possibly a Data Sub Key both defined in Table 5.2.12.2.1-1. When a Data Sub Key is defined in the table but not present in the Nudr_DM_Subscribe this means that all values of the Data Sub Key are targeted. - The Data Set Identifier plus (if present) the (set of) Data Subset Identifier(s) corresponds to a (set of) Event ID(s) as defined in clause 4.15.1 An NF Service Consumer may include an indicator when it invokes Nudr_DM Query/Create/Update service operation to subscribe the changes of the data, to avoid a separate Nudr_DM_Subscribe service operation. Depending on the use case, it is possible to use a Data Key and/or one or multiple Data sub keys to further identify the corresponding data, as defined in Table 5.2.12.2.1-1 below. Table 5.2.12.2.1-1: Data keys The content of the UDR storage for (Data Set Id= Application Data, Data Subset Id = AF TrafficInfluence request information) is specified in clause 5.6.7, Table 5.6.7-1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. This information is written by the NEF and read by the PCF(s). PCF(s) may also subscribe to changes onto this information. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.12.2 |
6,352 | 7B Security for wireline access to the 5G core network 7B.1 General | To support Wireless and Wireline Convergence for the 5G system, two new network entities, 5G-RG and FN-RG, are introduced in the architecture specificaction TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The 5G-RG acts as a 5G UE and can connect to 5GC via wireline access network (W-5GAN) or via Fixed Wireless Access (FWA). Existing security procedures defined in this document are reused. The 5G-RG also acts as end point of N1 and provides the NAS signaling connection to the 5GC on behalf of the AUN3 devices behind the 5G-RG. The FN-RG can connect to 5GC via wireline access network (W-5GAN). The W-AGF performs the registration procedure on behalf of the FN-RG. It acts as end point of N1 and provides the NAS signalling connection to the 5GC on behalf of the FN-RG. A 5G -capable UE can connect to 5GC through an RG that’s connected to the 5GC via wireline access network (W-5GAN) or NG-RAN. The UE supports untrusted non-3GPP access and/or trusted non-3GPP access. NOTE: Roaming of AUN3, FN-RG and 5G-RG are not supported. NOTE: Informative Annex O provides an example of how N5GC devices behind a residential gateway in private or in isolated scenarios with wireline access make use of additional EAP methods for authentication. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 7B |
6,353 | 5.7.4 Standardized 5QI to QoS characteristics mapping | Standardized 5QI values are specified for services that are assumed to be frequently used and thus benefit from optimized signalling by using standardized QoS characteristics. Dynamically assigned 5QI values (which require a signalling of QoS characteristics as part of the QoS profile) can be used for services for which standardized 5QI values are not defined. The one-to-one mapping of standardized 5QI values to 5G QoS characteristics is specified in table 5.7.4-1. Table 5.7.4-1: Standardized 5QI to QoS characteristics mapping NOTE: It is preferred that a value less than 64 is allocated for any new standardised 5QI of Non-GBR resource type. This is to allow for option 1 to be used as described in clause 5.7.1.3 (as the QFI is limited to less than 64). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7.4 |
6,354 | 4.9.2.2 Handover of a PDU Session procedure from 3GPP to untrusted non-3GPP access (non-roaming and roaming with local breakout) | Clause 4.9.2.2 specifies how to hand over a UE from a source 3GPP access to a target Untrusted non-3GPP access and how a UE can handover a PDU Session from 3GPP access to untrusted non-3GPP access. It is based on the PDU Session Establishment procedure for non-3GPP access as specified in clause 4.12.5. Figure 4.9.2.2-1: Handover of a PDU Session from 3GPP access to untrusted non-3GPP access (non-roaming and roaming with local breakout) 1. If the UE is not registered via untrusted non-3GPP access, the UE shall initiate Registration procedure as defined in clause 4.12.2. 2. The UE performs PDU Session Establishment procedure with the PDU Session ID of the PDU Session to be moved as specified in clause 4.12.5. When sending the PDU Session Establishment Accept, within the N1 SM container and in the N2 SM information, the SMF shall include all QoS information (e.g. QoS Rule(s) in N1 SM container, QFI(s) and QoS Profile(s) in N2 SM information) for the QoS Flow(s) that are applicable to the PDU Session for the target access. 3. If the User Plane of the PDU Session is activated in 3GPP access, the SMF executes the release of resource in 3GPP access by performing step 3b, then steps 4 to 7a/7b specified in clause 4.3.4.2 (UE or network requested PDU Session Release for Non-Roaming and Roaming with Local Breakout) in order to release the resources over the source 3GPP access. Because the PDU Session shall not be released, the SMF shall not send the PDU Session Release Command to the UE. Hence, in steps 3b, 4, 6 and 7a of clause 4.3.4.2, messages do not include the N1 SM container but only the N2 Resource Release Request (resp. Ack). Since the PDU Session is not to be released, the SMF shall not execute step 11 of clause 4.3.4.2 and the SM context between the AMF and the SMF is maintained. If the User Plane of the PDU Session is deactivated in 3GPP access, this step is skipped. The steps 2 and 3 shall be repeated for all PDU Sessions to be moved from 3GPP access to untrusted non-3GPP access. If the PDU Session is associated with Control Plane Only Indication, the AMF shall reject the PDU Session establishment request as the Control Plane CIoT Optimisation feature is not supported over non-3GPP accesses as described in clause 5.4.5.2.5 of TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [25]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.9.2.2 |
6,355 | 16.3.3.2 Handling of Slice Resources | The NG-RAN node may use Multi-Carrier Resource Sharing or Resource Repartitioning to allocate resources to a slice during the procedures described in 16.3.4 to support the slice service continuity in case of slice resources shortage. In Multi-Carrier Resource Sharing the RAN node can setup the dual connectivity or carrier aggregation with different frequency and overlapping coverage where the same slice is available. The Resource Repartitioning allows a slice to use resources from the shared pool or/and prioritized pool when its own dedicated or prioritized resources are not available and the use of unused resources in the prioritized pool is as specified in TS 28.541[ Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3 ] [49]. Slice RRM policies/restrictions associated with Resource Repartitioning are configured from O&M. Measurements of RRM policy utilization according to resource types defined in TS 28.541[ Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3 ] [49] are reported from RAN nodes to O&M and may lead O&M to update the configuration of the Slice RRM policies/restrictions. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.3.3.2 |
6,356 | 6.14.2 Requirements | An IoT device which is able to access a 5G PLMN in direct network connection mode using a 3GPP RAT shall have a 3GPP subscription. The 5G system shall allow the operator to identify a UE as an IoT device based on UE characteristics (e.g. identified by an equipment identifier or a range of equipment identifiers) or subscription or the combination of both. The 5G system shall be able to provide mechanisms to change the association between a subscription and address/number of an IoT device (e.g. changing the owner and subscription information associated with the IoT device) within the same operator and in between different operators in an automated or manual way. The 5G system shall be able to support identification of subscriptions independently of identification of IoT devices. Both identities shall be secure. An IoT device which is able to connect to a UE in direct device connection mode shall have a 3GPP subscription, if the IoT device needs to be identifiable by the core network (e.g. for IoT device management purposes or to use indirect network connection mode). Based on operator policy, the 5G system shall support a mechanism to provision on-demand connectivity (e.g. IP connectivity for remote provisioning). This on-demand mechanism should enable means for a user to request on-the-spot network connectivity while providing operators with identification and security tools for the provided connectivity. The 5G system shall support a secure mechanism for a home operator to remotely provision the 3GPP credentials of a uniquely identifiable and verifiably secure IoT device. The 5G system shall support a secure mechanism for the network operator of an NPN to remotely provision the non-3GPP identities and credentials of a uniquely identifiable and verifiably secure IoT device. Based on MNO and NPN policy, the 5G system shall support a mechanism to enable MNO to update the subscription of an authorized UE in order to allow the UE to connect to a desired NPN. This on-demand mechanism should enable means for a user to request on-the-spot network connectivity which is authorized by its MNO. Based on operator policy, the 5G system shall provide means for authorised 3rd parties to request changes to UE subscription parameters for access to data networks, e.g., static IP address and configuration parameters for data network access. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.14.2 |
6,357 | 9.11.3.77 Paging restriction | The purpose of the Paging restriction information element is to request the network to restrict paging. The Paging restriction information element is coded as shown in figure 9.11.3.77.1, figure 9.11.3.77.2 and table 9.11.3.77.1. The Paging restriction is a type 4 information element with a minimum length of 3 octets and a maximum length of 35 octets. Figure 9.11.3.77.1: Paging restriction information element for Paging restriction type = "All paging is restricted" and for Paging restriction type = "All paging is restricted except voice" Figure 9.11.3.77.2: Paging restriction information element for Paging restriction type = "All paging is restricted except for specified PDU session(s)" and for Paging restriction type = "All paging is restricted except for voice service and specified PDU session(s)" Table 9.11.3.77.1: Paging restriction information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.3.77 |
6,358 | 28.3.2.4.3 NSSF URI | In absence of any other local configuration available in the vNSSF, the API URIs of the hNSSF shall be constructed by deriving the API root (see 3GPP TS 29.501[ 5G System; Principles and Guidelines for Services Definition; Stage 3 ] [128]) as follows: - the authority part shall be set to the NSSF FQDN as specified in 28.3.2.4.2 - the scheme shall be "https" - the port shall be the default port for the "https" scheme, i.e. 443. - the API prefix optional component shall not be used EXAMPLE: For an MCC = 012 and MNC = 345, the API root of the NSSF services shall be: "https://nssf.5gc.mnc345.mcc012.3gppnetwork.org/" | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.3.2.4.3 |
6,359 | 5.4.2C PUCCH format 5 | The block of bits shall be scrambled with a UE-specific scrambling sequence, resulting in a block of scrambled bits according to where the scrambling sequence is given by clause 7.2. The scrambling sequence generator shall be initialised with at the start of each subframe where is the C-RNTI. The block of scrambled bits shall be QPSK modulated as described in Clause 7.1, resulting in a block of complex-valued modulation symbols where . The complex-valued symbols shall be divided into sets, each corresponding to one SC-FDMA symbol. Block-wise spreading shall be applied according to where , and are given by Table 5.4.2C-1 for normal PUCCH format 5 and shortened PUCCH format 5, and is given by Table 5.4.2C-2 with provided by higher layers. The block-wise spread complex-valued symbols shall be transform precoded according to where , resulting in a block of complex-valued symbols . Table 5.4.2C-1: The quantities and Table 5.4.2C-2: Orthogonal sequences | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.4.2C |
6,360 | 6.9 Supplementary Uplink | In case of Supplementary Uplink (SUL, see TS 38.101[ None ] -1 [18]), the UE is configured with 2 ULs for one DL of the same cell, and uplink transmissions on those two ULs are controlled by the network to avoid overlapping PUSCH/PUCCH transmissions in time. Overlapping transmissions on PUSCH are avoided through scheduling while overlapping transmissions on PUCCH are avoided through configuration (PUCCH can only be configured for only one of the 2 ULs of the cell). In addition, initial access is supported in each of the uplink (see clause 9.2.6). An example of SUL is given in Annex B. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 6.9 |
6,361 | 6.4.3.2 UE-requested PDU session release procedure initiation | In order to initiate the UE-requested PDU session release procedure, the UE shall create a PDU SESSION RELEASE REQUEST message. The UE may set the 5GSM cause IE of the PDU SESSION RELEASE REQUEST message to indicate the reason for releasing the PDU session. The 5GSM cause IE typically indicates one of the following 5GSM cause values: #26 insufficient resources; #36 regular deactivation; #44 Semantic errors in packet filter(s); #45 Syntactical error in packet filter(s); #83 Semantic error in the QoS operation; #84 Syntactical error in the QoS operation; #96 Invalid mandatory information. The UE shall allocate a PTI value currently not used and shall set the PTI IE of the PDU SESSION RELEASE REQUEST message to the allocated PTI value. The UE shall transport the PDU SESSION RELEASE REQUEST message and the PDU session ID, using the NAS transport procedure as specified in subclause 5.4.5, and the UE shall start timer T3582 (see example in figure 6.4.3.2.1). If the UE is releasing the PDU session due to: a) errors in QoS operations or packet filters; or b) the number of the authorized QoS rules, the number of the packet filters, or the number of the authorized QoS flow descriptions associated with the PDU session have reached the maximum number supported by the UE, the UE shall include the 5GSM cause IE in the PDU SESSION RELEASE REQUEST message as described in subclauses 6.3.2.4 and 6.4.1.3. Figure 6.4.3.2.1: UE-requested PDU session release procedure | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.4.3.2 |
6,362 | Suspend Notification | The Suspend Notification message shall be sent on the S11 interface by the MME to the SGW and on the S5/S8 interface by the SGW to the PGW as part of the 1xRTT CS fallback procedures in 3GPP TS 23.272[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ] [21]. The Suspend Notification message shall be sent on the S3 interface by the SGSN to the MME, on the S11 interface by the MME to the SGW, and on the S5/S8 interface by the SGW to the PGW as part of the SRVCC procedures in 3GPP TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [43] or the CS fallback from E-UTRAN access to UTRAN/GERAN CS domain access related procedures in 3GPP TS 23.272[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ] [21]. The Suspend Notification message shall be sent on the S16 interface as per the inter-SGSN suspend procedures in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [35]. The Suspend Notification message shall be sent on the S16, the S4 and the S5/S8 interfaces as part of the SRVCC from UTRAN (HSPA) to GERAN without DTM support procedure in 3GPP TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [43]. The Suspend Notification message shall be sent on the S4 and the S5/S8 interfaces as part of the CS fallback from E-UTRAN to GERAN CS domain related procedures in 3GPP TS 23.272[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ] [21]. After receiving a Suspend Notification message, the SGW/PGW marks all the non-GBR bearers as suspended status. The PGW should discard packets it receives for the suspended UE. Table 7.4.1-1 specifies the presence requirements and conditions of the IEs in the message. Table -1: Information Element in Suspend Notification | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | Suspend |
6,363 | 5.6.1.4.2 UE is using EPS services with control plane CIoT EPS optimization | For case a in clause 5.6.1.1, upon receipt of the CONTROL PLANE SERVICE REQUEST message with Control plane service type indicating "mobile terminating request", after completion of the EMM common procedures according to clause 5.6.1.3: 1) if the MME needs to perform an EPS bearer context status synchronization - for an EPS bearer context associated with Control plane only indication; or - for an EPS bearer context not associated with Control plane only indication, there is no downlink user data pending to be delivered via the user plane, and the UE did not set the "active" flag in the Control plane service type IE to 1; 2) if the control plane data back-off time for the UE is stored in MME and the MME decides to deactivate congestion control for transport of user data via the control plane, or 3) if the MME needs to provide the UE with Forbidden TAI(s) for the list of "forbidden tracking areas for roaming" IE or Forbidden TAI(s) for the list of "forbidden tracking areas for regional provision of service" IE, then the MME shall send a SERVICE ACCEPT message. Furthermore the MME may: 1) initiate the transport of user data via the control plane procedure or any other NAS signalling procedure; 2) if supported by the UE and required by the network, initiate the setup of the user plane radio bearer(s); or 3) send a NAS signalling message not related to an EMM common procedure to the UE if downlink signalling is pending. For case b in clause 5.6.1.1, upon receipt of the CONTROL PLANE SERVICE REQUEST message with Control plane service type indicating "mobile originating request", after completion of the EMM common procedures according to clause 5.6.1.3, if any, if the MME needs to provide the UE with Forbidden TAI(s) for the list of "forbidden tracking areas for roaming" IE or Forbidden TAI(s) for the list of "forbidden tracking areas for regional provision of service" IE or to perform an EPS bearer context status synchronization - for an EPS bearer context associated with Control plane only indication; or - for an EPS bearer context not associated with Control plane only indication, there is no downlink user data pending to be delivered via the user plane, and the UE did not set the "active" flag in the Control plane service type IE to 1, then the MME shall send a SERVICE ACCEPT message. Furthermore, the MME may: 1) initiate release of the NAS signalling connection upon receipt of an indication from the ESM layer (see clause 6.6.4.2), unless the MME has additional downlink user data or signalling pending; 2) initiate the setup of the user plane radio bearer(s), if downlink user data is pending to be delivered via the user plane or the UE has set the "active" flag in the Control plane service type IE to 1; 3) send an ESM DATA TRANSPORT message to the UE, if downlink user data is pending to be delivered via the control plane; 4) send a NAS signalling message not related to an EMM common procedure to the UE if downlink signalling is pending; or 5) send a SERVICE ACCEPT message to complete the service request procedure, if no NAS security mode control procedure was initiated, the MME did not send a SERVICE ACCEPT message as specified above to perform an EPS bearer context status synchronization, and the MME did not initiate any of the procedures specified in item 1 to 4 above. NOTE 1: The MME can initiate the setup of the user plane radio bearer(s) if the MME decides to activate the congestion control for transport of user data via the control plane. For case m in clause 5.6.1.1, upon receipt of the CONTROL PLANE SERVICE REQUEST message with Control plane service type indicating "mobile originating request" and the "active" flag in the Control plane service type IE set to 1: 1) if the MME accepts the request, the MME shall initiate the setup of the user plane radio bearer(s) for all active EPS bearer contexts of SGi PDN connections that are established without control plane only indication. 2) if the MME does not accept the request, the MME shall send a SERVICE ACCEPT message to complete the service request procedure. NOTE 2: The MME takes into account the maximum number of user plane radio bearers supported by the UE, in addition to local policies and the UE's preferred CIoT network behaviour when deciding whether to accept the request to establish user plane bearer(s) as described in clause 5.3.15. If the MME accepts the request, all SGi PDN connections are considered as established without Control plane only indication. NOTE 3: In this release of the specification, a UE in NB-S1 mode can support a maximum of 2 user plane radio bearers (see clause 6.5.0). For case c in clause 5.6.1.1, upon receipt of the CONTROL PLANE SERVICE REQUEST message with Control plane service type indicating "mobile originating request" and without an ESM message container IE, after completion of the EMM common procedures according to clause 5.6.1.3, if any, the MME proceeds as follows: If the MME needs to perform an EPS bearer context status synchronization - for an EPS bearer context associated with Control plane only indication; or - for an EPS bearer context not associated with Control plane only indication, and there is no downlink user data pending to be delivered via the user plane, then the MME shall send a SERVICE ACCEPT message. Furthermore, the MME may: 1) initiate the setup of the user plane radio bearer(s), if downlink user data is pending to be delivered via the user plane; 2) send an ESM DATA TRANSPORT message to the UE, if downlink user data is pending to be delivered via the control plane; 3) send a NAS signalling message not related to an EMM common procedure to the UE, if downlink signalling is pending; or 4) send a SERVICE ACCEPT message to complete the service request procedure, if no NAS security mode control procedure was initiated, the MME did not send a SERVICE ACCEPT message as specified above to perform an EPS bearer context status synchronization, and the MME did not initiate any of the procedures specified in item 1 to 3 above. If the MUSIM UE does not include the Paging restriction IE in the CONTROL PLANE SERVICE REQUEST message, the MME shall delete any stored paging restriction for the UE and stop restricting paging. For cases p and q in clause 5.6.1.1 when the MUSIM UE sets the Request type to "NAS signalling connection release" or to "Rejection of paging" in the UE request type IE in the CONTROL PLANE SERVICE REQUEST message and if the UE requests restriction of paging by including the Paging restriction IE, the MME: - if accepts the paging restriction, shall include the EPS additional request result IE in the SERVICE ACCEPT message and set the Paging restriction decision to "paging restriction is accepted". The MME shall store the paging restriction of the UE, enforce these restrictions in the paging procedure as described in clause 5.6.2; or - if rejects the paging restriction, shall include the EPS additional request result IE in the SERVICE ACCEPT message and set the Paging restriction decision to "paging restriction is rejected", and shall discard the received paging restriction. The MME shall delete any stored paging restriction for the UE and stop restricting paging; and - shall initiate the release of the NAS signalling connection after the completion of the service request procedure. In NB-S1 mode, for cases a, b, c and m in clause 5.6.1.1, if the MME needs to initiate the setup of user plane radio bearer(s), the MME shall check if the UE can support the establishment of additional user plane radio bearer based on the multiple DRB support indicated by UE in the UE network capability IE. For cases a, b and c in clause 5.6.1.1, if the EPS bearer context status IE is included in the CONTROL PLANE SERVICE REQUEST message, the network shall deactivate all those EPS bearer contexts locally (without peer-to-peer signalling between the network and the UE) which are active on the network side but are indicated by the UE as being inactive. If a default EPS bearer context is marked as inactive in the EPS bearer context status IE included in the CONTROL PLANE SERVICE REQUEST message, and this default bearer is not associated with the last PDN connection of the UE in the MME, the MME shall locally deactivate all EPS bearer contexts associated to the PDN connection with the default EPS bearer context without peer-to-peer ESM signalling to the UE. If the default bearer is associated with the last remaining PDN connection of the UE in the MME, and EMM-REGISTERED without PDN connection is supported by the UE and the MME, the MME shall locally deactivate all EPS bearer contexts associated to the PDN connection with the default EPS bearer context without peer-to-peer ESM signalling to the UE. If the EPS bearer context status IE is included in the CONTROL PLANE SERVICE REQUEST and the MME decides to respond with a SERVICE ACCEPT message, the MME shall include an EPS bearer context status IE, indicating which EPS bearer contexts are active in the MME, except for the case when no EPS bearer context exists on the network side. If the MME needs to initiate an EPS bearer context status synchronization, the MME may include an EPS bearer context status IE in the SERVICE ACCEPT message also if no EPS bearer context status IE was included in the CONTROL PLANE SERVICE REQUEST message. If the MME sends a SERVICE ACCEPT message upon receipt of the CONTROL PLANE SERVICE REQUEST message piggybacked with the ESM DATA TRANSPORT message: - if the Release assistance indication IE is set to "No further uplink and no further downlink data transmission subsequent to the uplink data transmission is expected" in the message; - if the UE has indicated support for the control plane data back-off timer; and - if the MME decides to activate the congestion control for transport of user data via the control plane, then the MME shall include the T3448 value IE in the SERVICE ACCEPT message. If the MME sends a SERVICE ACCEPT message and decides to deactivate congestion control for transport of user data via the control plane then the MME shall delete the stored control plane data back-off time for the UE and the MME shall not include timer T3448 value IE in SERVICE ACCEPT message. For cases a, b, c and m in clause 5.6.1.1, if the EPS bearer context status IE is included in the CONTROL PLANE SERVICE REQUEST message or the MME needs to initiate an EPS bearer context status synchronization, the MME shall consider the service request procedure successfully completed when it sends the SERVICE ACCEPT message. If the EPS bearer context status IE is not included in the CONTROL PLANE SERVICE REQUEST message and the MME does not need to initiate an EPS bearer context status synchronization, the MME shall consider the service request procedure successfully completed in the following cases: - when it successfully completes a NAS security mode control procedure; - when it receives an indication from the lower layer that the user plane is setup, if radio bearer establishment is required; - upon receipt of the CONTROL PLANE SERVICE REQUEST message and completion of the EMM common procedures, if any, if the CONTROL PLANE SERVICE REQUEST message was successfully integrity checked and the ESM message container or NAS message container in the CONTROL PLANE SERVICE REQUEST message, if applicable, was successfully deciphered, radio bearer establishment is not required, and the MME has downlink user data or signalling not related to an EMM common procedure pending; and - with the transmission of a SERVICE ACCEPT message or with the decision to initiate release of the NAS signalling connection, if the CONTROL PLANE SERVICE REQUEST message was successfully integrity checked and the ESM message container or NAS message container in the CONTROL PLANE SERVICE REQUEST message, if applicable, was successfully deciphered, radio bearer establishment is not required, and the MME does not have any downlink user data or signalling pending. If the MME considers the service request procedure successfully completed the MME shall: 1) forward the contents of the ESM message container IE, if any, to the ESM layer; and 2) forward the contents of the NAS message container IE, if any. For cases a, b and c in clause 5.6.1.1, the UE shall treat the receipt of any of the following as successful completion of the procedure: - a SECURITY MODE COMMAND message; - a security protected EMM message different from a SERVICE REJECT message and not related to an EMM common procedure; - a security protected ESM message; and - receipt of the indication from the lower layers that the user plane radio bearers are set up. Upon successful completion of the procedure, the UE shall reset the service request attempt counter, stop the timer T3417 and enter the state EMM-REGISTERED. If the CONTROL PLANE SERVICE REQUEST message was sent with the "active" flag in the Control plane service type IE set to "Radio bearer establishment requested", the UE shall locally deactivate the EPS bearer contexts that do not have a user plane radio bearer established upon successful completion of the service request procedure, except for the case when the MUSIM UE in the CONTROL SERVICE REQUEST message sets the Request type to "NAS signalling connection release" or to "Rejection of paging" in the UE request type IE. NOTE 4: The security protected EMM message can be e.g. a SERVICE ACCEPT message and the ESM message an ESM DATA TRANSPORT message. For case m in clause 5.6.1.1, the UE shall treat the indication from the lower layers that the user plane radio bearers are set up as successful completion of the procedure. The UE shall treat the receipt of a SERVICE ACCEPT message as completion of the procedure without the establishment of the user plane radio bearers. For both cases, the UE shall reset the service request attempt counter, stop the timer T3417 and enter the state EMM-REGISTERED. For case b in clause 5.6.1.1, the UE shall also treat the indication from the lower layers that the RRC connection has been released as successful completion of the procedure. The UE shall reset the service request attempt counter, stop the timer T3417 and enter the state EMM-REGISTERED. For cases a, c and m in clause 5.6.1.1, the UE shall treat the indication from the lower layers that the RRC connection has been released as an abnormal case and shall follow the procedure described in clause 5.6.1.6, item b. For cases p and q in clause 5.6.1.1, when the MUSIM UE in the CONTROL PLANE SERVICE REQUEST message sets the Request type to "NAS signalling connection release" or to "Rejection of paging" in the UE request type IE, the UE shall treat the receipt of SERVICE ACCEPT message as the successful completion of the procedure and the UE shall reset the service request attempt counter, stop timer T3417, enter the state EMM-REGISTERED and not deactivate EPS bearer contexts locally. For case o in clause 5.6.1.1, the UE shall treat the receipt of SERVICE ACCEPT message as the successful completion of the procedure. The UE shall reset the service request attempt counter, stop timer T3417 and enter the state EMM-REGISTERED. For cases a, b and c in clause 5.6.1.1, - if the MME needs to initiate an EPS bearer context status synchronization or to provide the UE with Forbidden TAI(s) for the list of "forbidden tracking areas for roaming" IE or Forbidden TAI(s) for the list of "forbidden tracking areas for regional provision of service", the UE can receive a SERVICE ACCEPT message even after it received a SECURITY MODE COMMAND message or an indication from the lower layers that the user plane radio bearers are set up and determined successful completion of the service request procedure. Upon receipt of the SECURITY MODE COMMAND message or an indication from the lower layers that the user plane radio bearers are set up, the UE shall start timer T3449. If the UE receives a security protected ESM message or a security protected EMM message not related to an EMM common procedure, the UE shall stop the timer T3449. If the UE receives a SERVICE ACCEPT message while the timer T3449 is running, the UE shall treat the SERVICE ACCEPT message and stop the timer T3449. If the UE is not in state EMM-SERVICE-REQUEST-INITIATED and timer T3449 is not running, the receipt of the SERVICE ACCEPT message is considered as protocol error and the UE shall return EMM STATUS message as specified in clause 7.4; otherwise the UE shall treat the SERVICE ACCEPT message; and - if the UE treats the SERVICE ACCEPT message and an EPS bearer context status IE is included in the message, the UE shall deactivate all those EPS bearers contexts locally (without peer-to-peer signalling between the UE and the MME) which are active in the UE, but are indicated by the MME as being inactive. If a default EPS bearer context is marked as inactive in the EPS bearer context status IE included in the SERVICE ACCEPT message, and this default bearer is not associated with the last remaining PDN connection in the UE, the UE shall locally deactivate all EPS bearer contexts associated to the PDN connection with the default EPS bearer context without peer-to-peer ESM signalling to the MME. If the default bearer is associated with the last remaining PDN connection of the UE in the MME, and EMM-REGISTERED without PDN connection is supported by the UE and the MME, the UE shall locally deactivate all EPS bearer contexts associated to the PDN connection with the default EPS bearer context without peer-to-peer ESM signalling to the MME. If the T3448 value IE is present in the received SERVICE ACCEPT message, the UE shall: - stop timer T3448 if it is running; - consider the transport of user data via the control plane as successful; and - start timer T3448 with the value provided in the T3448 value IE. If the UE is using EPS services with control plane CIoT EPS optimization, the T3448 value IE is present in the SERVICE ACCEPT message and the value indicates that this timer is either zero or deactivated, the UE shall consider this case as an abnormal case and proceed as if the T3448 value IE is not present. If the UE in EMM-IDLE mode initiated the service request procedure by sending a CONTROL PLANE SERVICE REQUEST message and the SERVICE ACCEPT message does not include the T3448 value IE and if timer T3448 is running, then the UE shall stop timer T3448. If the MME received the list of TAIs from the satellite E-UTRAN as described in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10], and determines that, by UE subscription and operator's preference, any but not all TAIs in the received list of TAIs is forbidden for roaming or for regional provision of service, the MME shall include the TAI(s) in: a) the Forbidden TAI(s) for the list of "forbidden tracking areas for roaming" IE; b) the Forbidden TAI(s) for the list of "forbidden tracking areas for regional provision of service" IE; or c) both, in the SERVICE ACCEPT message. NOTE 5: "Forbidden tracking areas for roaming" corresponds to cause values #13 and #15, and "forbidden tracking areas for regional provision of service" corresponds cause value #12. If the UE receives the Forbidden TAI(s) for the list of "forbidden tracking areas for roaming" IE in the SERVICE ACCEPT message and the TAI(s) included in the IE which are belonging to the serving PLMN or equivalent PLMN(s) is not part of the list of "forbidden tracking areas for roaming", the UE shall store the TAI(s) included in the IE into the list of "forbidden tracking areas for roaming" and ignore the TAI(s) which do not belong to the serving PLMN or equivalent PLMN(s). If the UE receives the Forbidden TAI(s) for the list of "forbidden tracking areas for regional provision of service" IE in the SERVICE ACCEPT message and the TAI(s) included in the IE which are belonging to the serving PLMN or equivalent PLMN(s) is not part of the list of "forbidden tracking areas for regional provision of service", the UE shall store the TAI(s) included in the IE into the list of "forbidden tracking areas for regional provision of service" and ignore the TAI(s) which do not belong to the serving PLMN or equivalent PLMN(s). | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.6.1.4.2 |
6,364 | 5.5.3.3.6 Abnormal cases in the UE | The UE shall proceed as follows: 1) if the UE requested the combined tracking area update for EPS services and "SMS only" and the TRACKING AREA UPDATE ACCEPT message indicates a combined tracking area updating procedure successful for EPS and non-EPS services, the UE shall behave as if the combined tracking area updating procedure was successful for EPS services and "SMS only"; NOTE: In this case the UE can ignore the CS SERVICE NOTIFICATION message or the Paging with CN domain indicator set to "CS", as specified in clause 5.6.2.3.2. 2) if the combined tracking area update was successful for EPS services only and the TRACKING AREA UPDATE ACCEPT message contained an EMM cause value not treated in clause 5.5.3.3.4.3 or the EMM Cause IE is not included in the message, the UE shall proceed as follows: a) The UE shall stop timer T3430 if still running, and shall enter state MM IDLE. The tracking area updating attempt counter shall be incremented, unless it was already set to 5; b) If the tracking area updating attempt counter is less than 5: - the UE shall start timer T3411, shall set the EPS update status to EU1 UPDATED and shall enter state EMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM. When timer T3411 expires the combined tracking area updating procedure indicating "combined TA/LA updating with IMSI attach" is triggered again; c) If the tracking area updating attempt counter is equal to 5: - a UE operating in CS/PS mode 2 of operation and a UE operating in CS/PS mode 1 of operation with "IMS voice available" shall start timer T3402 if the value indicated by the network is not zero, shall set the EPS update status to EU1 UPDATED and shall enter state EMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM. - If the value of T3402 as indicated by the network is zero, the UE shall perform the actions defined for the expiry of the timer T3402. - When timer T3402 expires the combined tracking area updating procedure indicating "combined TA/LA updating with IMSI attach" is triggered again; and - a UE operating in CS/PS mode 1 of operation with "IMS voice not available" shall attempt to select GERAN, UTRAN or NG-RAN radio access technology, proceed with appropriate MM, GMM or 5GMM specific procedures and disable the E-UTRA capability (see clause 4.5); and d) If there is a CS fallback emergency call or CS fallback call pending, or a paging for CS fallback, the UE shall attempt to select GERAN or UTRAN radio access technology. If the UE finds a suitable GERAN or UTRAN cell, it then proceeds with the appropriate MM and CC specific procedures; otherwise, if there is a CS fallback emergency call or CS fallback call pending, the EMM sublayer shall indicate the abort of the EMM procedure to the MM sublayer; and 3) otherwise, the abnormal cases specified in clause 5.5.3.2.6 apply with the following modification. If the tracking area updating attempt counter is incremented according to clause 5.5.3.2.6 the next actions depend on the value of the tracking area updating attempt counter. - If the tracking area updating attempt counter is less than 5, the UE shall set the update status to U2 NOT UPDATED, but shall not delete any LAI, TMSI, ciphering key sequence number and list of equivalent PLMNs and additionally if the tracking area updating procedure was performed due to cases h, m, n, z, zc in clause 5.5.3.3.2 the update status shall be changed to EU2; or - if the tracking area updating attempt counter is equal to 5, the UE shall delete any LAI, TMSI and ciphering key sequence number and set the update status to U2 NOT UPDATED. If there is a CS fallback emergency call pending or CS fallback call pending, or a paging for CS fallback, the UE shall attempt to select GERAN or UTRAN radio access technology. If the UE finds a suitable GERAN or UTRAN cell, it then proceeds with the appropriate MM and CC specific procedures; otherwise if there is a CS fallback emergency call or CS fallback call pending, the EMM sublayer shall indicate the abort of the EMM procedure to the MM sublayer. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.3.3.6 |
6,365 | 2 Identification of mobile subscribers 2.1 General | A unique International Mobile Subscription Identity (IMSI) shall be allocated to each mobile subscriber in the GSM/UMTS/EPS system. NOTE: This IMSI is the concept referred to by ITU-T as "International Mobile Subscription Identity". In order to support the subscriber identity confidentiality service the VLRs, SGSNs and MME may allocate Temporary Mobile Subscriber Identities (TMSI) to visiting mobile subscribers. The VLR,SGSN and MME must be capable of correlating an allocated TMSI with the IMSI of the MS to which it is allocated. An MS may be allocated three TMSIs, one for services provided through the MSC, one for services provided through the SGSN (P-TMSI for short) and one for the services provided via the MME (M-TMSI part GUTI for short). For addressing on resources used for GPRS, a Temporary Logical Link Identity (TLLI) is used. The TLLI to use is built by the MS either on the basis of the P-TMSI (local or foreign TLLI), or directly (random TLLI). In order to speed up the search for subscriber data in the VLR a supplementary Local Mobile Station Identity (LMSI) is defined. The LMSI may be allocated by the VLR at location updating and is sent to the HLR together with the IMSI. The HLR makes no use of it but includes it together with the IMSI in all messages sent to the VLR concerning that MS. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 2 |
6,366 | 16.14.2.1 Scheduling and Timing | DL and UL are frame aligned at the uplink time synchronization reference point (RP) with an offset given by NTA,offset (see clause 4.2 of TS 38.213[ NR; Physical layer procedures for control ] [38]). To accommodate the propagation delay in NTNs, several timing relationships are enhanced by a Common Timing Advance (Common TA) and two offsets and : - is a configured timing offset that is equal to the RTT between the RP and the NTN payload. - is a configured scheduling offset that needs to be larger or equal to the sum of the service link RTT and the Common TA. - is a configured offset that is approximately equal to the RTT between the RP and the gNB. The scheduling offset is used to allow the UE sufficient processing time between a downlink reception and an uplink transmission, see TS 38.213[ NR; Physical layer procedures for control ] [38]. The offset is used to delay the application of a downlink configuration indicated by a MAC CE command on PDSCH, see TS 38.213[ NR; Physical layer procedures for control ] [38], and in estimation of UE-gNB RTT, see TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [6]. It may be provided by the network when downlink and uplink frame timing are not aligned at gNB. The is also used in the random access procedure, to determine the start time of RAR window/MsgB window after a Msg1/MsgA transmission (see TS 38.213[ NR; Physical layer procedures for control ] [38]). The Service link RTT, Feeder link RTT, RP, Common TA, and TTA (see clause 16.14.2.2) are illustrated in Figure 16.14.2.1-1. Figure 16.14.2.1-1: Illustration of timing relationship (for collocated gNB and NTN Gateway) The network may configure the HARQ operation as follows: - For downlink, HARQ feedback can be enabled or disabled per HARQ process (as specified in clause 5.3.2.2 and clause 5.7 of TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [6]). Disabling HARQ feedback allows scheduling a HARQ process before one HARQ RTT has elapsed since last scheduled. - For uplink, HARQ mode (i.e. HARQ mode A or HARQ mode B) can be configured per HARQ process (as specified in clause 5.4.3.1 and clause 5.7 of TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [6]). HARQ mode B allows scheduling a HARQ process before one HARQ RTT has elapsed since last scheduled. NOTE: For the HARQ processes configured with HARQ feedback enabled/disabled, it is up to network implementation to ensure a proper configuration of HARQ feedback (e.g., either all enabled or all disabled) for HARQ processes used by an SPS configuration. For the HARQ processes configured with HARQ mode, it is up to network implementation to ensure a proper configuration of HARQ mode (e.g., either all HARQ mode A or all HARQ mode B) for HARQ processes used by a CG configuration. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.14.2.1 |
6,367 | 5.10.2 Uplink | After a Semi-Persistent Scheduling uplink grant is configured, the MAC entity shall: - if twoIntervalsConfig is enabled by upper layer: - set the Subframe_Offset according to Table 7.4-1. - else: - set Subframe_Offset to 0. - consider sequentially that the Nth grant occurs in the TTI for which: - subframe SPS is used: - (10 * SFN + subframe) = [(10 * SFNstart time + subframestart time) + N * semiPersistSchedIntervalUL + Subframe_Offset * (N modulo 2)] modulo 10240. - slot or subslot SPS is used: - (10 * SFN * sTTI_Number_Per_Subframe + subframe * sTTI_Number_Per_Subframe + sTTI_number) = [(10 * SFNstart time * sTTI_Number_Per_Subframe + subframestart time * sTTI_Number_Per_Subframe + sTTIStartTimeUl) + N * semiPersistSchedIntervalUL-sTTI+ Subframe_Offset * (N modulo 2) * sTTI_Number_Per_Subframe] modulo (10240 * sTTI_Number_Per_Subframe). Where SFNstart time, subframestart time and sTTIStartTimeUl are the SFN, subframe and sTTI_number, respectively, at the time the configured uplink grant were (re-)initialised. The sTTI_Number_Per_Subframe is 6 when subslot TTI is configued and 2 when slot TTI is configured for short TTI operation. sTTI_number refers to the index of the short TTI, i.e., index of subslot or slot within the subframe. Except for NB-IoT, for TDD, the MAC entity is configured with semiPersistSchedIntervalUL shorter than 10 subframes, the Nth grant shall be ignored if it occurs in a downlink subframe or a special subframe. Except for NB-IoT, if the MAC entity is not configured with skipUplinkTxSPS, the MAC entity shall clear the configured uplink grant immediately after implicitReleaseAfter, as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8], number of consecutive new MAC PDUs each containing zero MAC SDUs have been provided by the Multiplexing and Assembly entity, on the Semi-Persistent Scheduling resource. If SPS confirmation has been triggered and not cancelled: - if the MAC entity has UL resources allocated for new transmission for this TTI: - instruct the Multiplexing and Assembly procedure to generate an SPS confirmation MAC Control Element as defined in clause 6.1.3.11; - cancel the triggered SPS confirmation. The MAC entity shall clear the configured uplink grant immediately after first transmission of SPS confirmation MAC Control Element triggered by the SPS release. NOTE: Retransmissions for Semi-Persistent Scheduling can continue after clearing the configured uplink grant. For NB-IoT UEs, BL UEs or UEs in enhanced coverage SFNstart time and subframestart time refer to SFN and subframe of the first transmission of PUSCH where configured uplink grant was (re-)initialized. In the event of a resource conflict between multiple UL SPS configurations configured with Uplink Semi-Persistent Scheduling V-RNTI, the UE behaviour is undefined. In the event of a resource conflict in the same serving cell between the initial transmision within a configured grant bundle from multiple different UL SPS configurations configured with Uplink Semi-Persistent Scheduling C-RNTI, the UE behaviour is undefined. For NB-IoT UEs, a configured uplink grant shall be used only for BSR or SPS confirmation transmission, and skipUplinkTxSPS is implicitly configured. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.10.2 |
6,368 | 4.7.7.8 Handling of keys at intersystem change from Iu mode to A/Gb mode | At an inter-system change from Iu mode to A/Gb mode, ciphering may be started (see 3GPP TS 44.064[ Mobile Station - Serving GPRS Support Node (MS-SGSN); Logical Link Control (LLC) Layer Specification ] [78a]) without any new authentication and ciphering procedure. Deduction of the appropriate security key for ciphering in A/Gb mode, depends on the current GSM/UMTS security context stored in the MS and the network. The ME shall handle the GPRS GSM ciphering key and a potential GPRS GSM Kc128 according to table 4.7.7.8.1. In the case of an established GSM security context, before any initial GMM message is sent in the new cell in A/Gb mode, the GMM layer in the MS shall notify the LLC layer if ciphering shall be used or not. If ciphering shall be used, then the GPRS GSM ciphering key and the applicable GEA ciphering algorithm according to the stored Ciphering Algorithm IE in the MS shall also be indicated to the LLC layer (see 3GPP TS 44.064[ Mobile Station - Serving GPRS Support Node (MS-SGSN); Logical Link Control (LLC) Layer Specification ] [78a]). In the case of an established UMTS security context, before any initial GMM message is sent in the new cell in A/Gb mode, the GMM layer in the MS shall notify the LLC layer if ciphering shall be used or not. If ciphering shall be used, then the GPRS GSM ciphering key or GPRS GSM Kc128 and the applicable GEA ciphering algorithm according to the stored Ciphering Algorithm IE in the MS shall also be indicated to the LLC layer (see 3GPP TS 44.064[ Mobile Station - Serving GPRS Support Node (MS-SGSN); Logical Link Control (LLC) Layer Specification ] [78a]). If the network has selected a GEA-algorithm that requires a 128-bit ciphering key, then the ME shall apply a GPRS GSM Kc128 derived from the GPRS UMTS ciphering key and the GPRS UMTS integrity key of the established UTMS security context as specified in 3GPP TS 33.102[ 3G security; Security architecture ] [5a]. Table 4.7.7.8.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Inter-system change from Iu mode to A/Gb mode NOTE: A USIM with UMTS security context, passes the GPRS UMTS ciphering key, the GPRS UMTS integrity key and the derived GPRS GSM ciphering key to the ME independent on the current radio access being UTRAN or GERAN. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.7.8 |
6,369 | 5.1.4 Coordination between EMM and GMM | If GMM and EMM are both enabled, a UE capable of S1 mode and A/Gb mode or Iu mode or both shall maintain one common registration for GMM and EMM indicating whether the UE is registered for packet services or not. A UE that is not registered shall be in state GMM-DEREGISTERED and in state EMM-DEREGISTERED. If the UE performs a successful attach or combined attach procedure in S1 mode, it shall enter substates GMM-REGISTERED.NO-CELL-AVAILABLE and EMM-REGISTERED.NORMAL-SERVICE. The UE resets the attach attempt counter and the GPRS attach attempt counter (see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13]). If the UE performs a successful GPRS attach or combined GPRS attach procedure in A/Gb or Iu mode, it shall enter substates GMM-REGISTERED.NORMAL-SERVICE and EMM-REGISTERED.NO-CELL-AVAILABLE. The UE resets the attach attempt counter and the GPRS attach attempt counter (see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13]). At intersystem change from A/Gb or Iu mode to S1 mode when no PDP context is active, if EMM-REGISTERED without PDN connection is not supported by the UE or the MME, the UE shall move to state EMM-DEREGISTERED and state GMM-DEREGISTERED and then initiate an attach procedure. If EMM-REGISTERED without PDN connection is supported by the UE and the MME, the UE shall enter substates EMM-REGISTERED.NORMAL-SERVICE and GMM-REGISTERED.NO-CELL-AVAILABLE and initiate a tracking area updating procedure. After successful completion of routing area updating or combined routing area updating and tracking area updating or combined tracking area updating procedures in both S1 mode and A/Gb or Iu mode, if the network has indicated that ISR is activated, the UE shall maintain registration and related periodic update timers in both GMM and EMM. NOTE: As specified in clause 5.5.3.2.4 of this document or clause 4.7.5.1.3 of 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13], the UE does not activate the ISR even if the network has indicated that the ISR is activated e.g. in the tracking area updating procedure triggered due to a change in UE network capability. In these scenarios, the UE only maintains one registration and related periodic update timer in GMM or EMM. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.1.4 |
6,370 | 4.6.3.7 Session management aspect of handling network slices with NS-AoS not matching deployed tracking areas | If a UE is outside the NS-AoS of an S-NSSAI (see subclause 4.6.2.10), the UE shall not: a) attempt to request the establishment of user plane resources of any PDU session associated with the S-NSSAI; and b) initiate UL NAS TRANSPORT messages carrying control plane user data. If a UE is outside the NS-AoS of an S-NSSAI (see subclause 4.6.2.10), the SMF shall not: a) attempt to establish user plane resources of any PDU session associated with the S-NSSAI; and b) send control plane user data to the UE. NOTE: A PDU session associated with an S-NSSAI is not released solely because a UE is outside the NS-AoS of the S-NSSAI. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.6.3.7 |
6,371 | 15.4 Home Network Realm | The home network realm shall be in the form of an Internet domain name, e.g. operator.com, as specified in IETF RFC 1035 [19] and IETF RFC 1123 [20]. The home network realm consists of one or more labels. Each label shall consist of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-) in accordance with IETF RFC 1035 [19]. Each label shall begin and end with either an alphabetic character or a digit in accordance with IETF RFC 1123 [20]. The case of alphabetic characters is not significant. During the MBMS service activation in roaming scenario, the BM-SC in the visited network shall derive the home network domain name from the IMSI as described in the following steps: 1. Take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used (see 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [27], 3GPP TS 51.011[ Specification of the Subscriber Identity Module - Mobile Equipment (SIM-ME) interface ] [66]) and separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning; 2. Use the MCC and MNC derived in step 1 to create the "mnc<MNC>.mcc<MCC>.3gppnetwork.org" realm name; 3. Add the label "mbms." to the beginning of the realm name. An example of a home realm used in the MBMS roaming case is: IMSI in use: 234150999999999; Where: MCC = 234; MNC = 15; MSIN = 0999999999 Which gives the home network realm: mbms.mnc015.mcc234.3gppnetwork.org. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 15.4 |
6,372 | 8.7.16 FDD (1024QAM and up to 4Rx supported) | The common parameters are specified in Table 8.7.16-1 for UE which is capable of supporting 1024QAM. Table 8.7.16-1: Common Test Parameters (FDD) The UE capability for 1024QAM is signalled per band or per band combination, hence the SDR tests with the mixed modulation orders and the mixed receiver antenna numbers across CC-s are specified. For UE not supporting CA and supporting 1024QAM, the TB success rate shall be higher than 85% when PDSCH is scheduled with FRC in Table 8.7.16-4 according the UE capability. The maximum supported channel bandwidth and MIMO layer are configured during the test. For UE supporting CA and supporting 1024QAM at least on one CC for a supported CA configuration, the SDR requirements are specified as follows: - If UE is capable of supporting 256QAM, the TB success rate shall be higher than 85% on each CC when PDSCH-s are scheduled with FRC-s in Table 8.7.16-3 for the transmission with 256QAM and Table 8.7.16-4 for the transmission with 1024QAM according to the reported capability of supported modulation order for the determined CA configuration. - If UE is not capable of supporting 256QAM, the TB success rate shall be higher than 85% on each CC when PDSCH-s are scheduled with FRC-s in Table 8.7.16-2 for the transmission with 64QAM and Table 8.7.16-4 for the transmission with 1024QAM according to the reported capability of supported modulation order for the determined CA configuration. For UE supporting 1024 QAM, the SDR requirement with 64QAM and 256QAM only is not applicable. The CA configuration or band for single carrier, bandwidth combination or bandwidth for single carrier, modulation order on each CC and MIMO layer on each CC are determined by the following procedure. - Among all the supported CA configurations which support 1024QAM at least on one CC, select one set of {CA configuration or a band, bandwidth combination or bandwidth, modulation order on each CC, MIMO layer on each CC}, which leads to the largest equivalent aggregated bandwidth. The equivalent aggregated bandwidth is defined as Where N is the number of CCs, represents the MIMO layer, represents the bandwidths on each CC, [ is the scaling factor according to the supported modulation order on each CC, where Mi = 0.75 is used if the maximum modulation order of CC i is 64QAM, Mi = 1 is used if the maximum modulation order of CC i is 256QAM, and Mi = 1.25 is used if the maximum modulation order of CC i is 1024QAM.] - When there are multiple sets of {CA configuration or a band, bandwidth combination or bandwidth, modulation order on each CC, MIMO layer on each CC} which can reach the same equivalent aggregated bandwidth, select one among the sets with the largest number of CCs supporting 1024QAM. - When there are multiple sets of {CA configuration or a band, bandwidth combination or bandwidth, modulation order on each CC, MIMO layer on each CC} which can reach the same equivalent aggregated bandwidth with the same number of CCs supporting 1024QAM, select one among the sets with the largest number of CCs supporting 4 layer. - The procedure applies also for the single carrier operating band instead of CA configuration, and bandwidth instead of bandwidth combination. The TB success rate for single carrier or on each CC for CA is defined as 100%*NDL_correct_rx/ (NDL_newtx + NDL_retx), where NDL_newtx is the number of newly transmitted DL transport blocks, NDL_retx is the number of retransmitted DL transport blocks, and NDL_correct_rx is the number of correctly received DL transport blocks. The TB success rate shall be sustained during at least 300 frames. Table 8.7.16-2: Per-CC FRC for SDR test (FDD 64QAM) Table 8.7.16-3: Per-CC FRC for SDR test (FDD 256QAM) Table 8.7.16-4: Per-CC FRC for SDR test (FDD 1024QAM) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.7.16 |
6,373 | 4.4.2.6 Change of security keys | When the AMF initiates a re-authentication to create a new 5G NAS security context, the messages exchanged during the authentication procedure are integrity protected and ciphered using the current 5G NAS security context, if any. Both UE and AMF shall continue to use the current 5G NAS security context, until the AMF initiates a security mode control procedure. The SECURITY MODE COMMAND message sent by the AMF includes the ngKSI of the new 5G NAS security context to be used. The AMF shall send the SECURITY MODE COMMAND message integrity protected with the new 5G NAS security context, but unciphered. When the UE responds with a SECURITY MODE COMPLETE message, it shall send the message integrity protected and ciphered with the new 5G NAS security context. The AMF can also modify the current 5G NAS security context or take the non-current native 5G NAS security context, if any, into use, by sending a SECURITY MODE COMMAND message including the ngKSI of the 5G NAS security context to be modified and including a new set of selected NAS security algorithms. In this case the AMF shall send the SECURITY MODE COMMAND message integrity protected with the modified 5G NAS security context, but unciphered. When the UE replies with a SECURITY MODE COMPLETE message, it shall send the message integrity protected and ciphered with the modified 5G NAS security context. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.4.2.6 |
6,374 | 9.9.3.56 Ciphering key data | The purpose of the Ciphering key data information element is to transfer a list of ciphering data sets from the network to the UE for deciphering of ciphered assistance data. The Ciphering key data information element is coded as shown in figure 9.9.3.56.1, figure 9.9.3.56.2 and table 9.9.3.56.1. The Ciphering key data is a type 6 information element, with a minimum length of 35 octets and a maximum length of 2291 octets. The list can contain a maximum of 16 ciphering data sets. Figure 9.9.3.56.1: Ciphering key data information element Figure 9.9.3.56.2: Ciphering data set Table 9.9.3.56.1: Ciphering key data information element | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.9.3.56 |
6,375 | 19.2.2.1 Service Provided by the BM-SC in home PLMN | Figure 30a: Deactivation of an MBMS multicast service in roaming scenario with service provided in the home PLMN 1. Upon receiving the leave indication, the GGSN sends an STR to the BM-SC in visited PLMN, indicating that the roaming UE is requesting to leave the multicast service. The session to be terminate is uniquely identified by the Diameter session-id. 2. Upon reception of the STR, the BM-SC in visited PLMN finds the BM-SC in home PLMN which serves the roaming UE, and sends an STR to it for the roaming UE to deactivate a particular service. 3. Upon reception of the STR, the BM-SC in home PLMN verifies that the IP multicast address corresponds to a valid MBMS bearer service and responds the BM-SC in visited PLMN with an ST-Answer. The APN shall be the same that was provided during service activation. 4. Upon reception of the STA, the BM-SC in visited PLMN sends an STA to the GGSN that orignated the Leave Indication. 5. The GGSN which is used to establish the MBMS bearer service deletes the MBMS UE Context and sends an STR to the BM-SC in home PLMN to confirm the successful deactivation of the MBMS UE Context. 6. The BM-SC in home PLMN then, deletes the MBMS UE Context and sends a confirmation to the GGSN in an STA message. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 19.2.2.1 |
6,376 | 4.3.2.10.1 PDN connection with integrity protection | At PS to CS domain change from S1 mode due to SRVCC or vSRVCC handover of a PDN connection for which the "null integrity protection algorithm" EIA0 has not been used (see 3GPP TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [126]), when the MS receives the command to perform handover, the MS shall derive a UMTS security context for the CS domain from the current EPS security context. The MS shall set the CKSN of the derived UMTS security context to the value of the eKSI of the EPS security context and derive security keys CKSRVCC and IKSRVCC as specified in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [123]. The ME shall also derive the security key GSM ciphering key Kc from CKSRVCC and IKSRVCC using the conversion function c3 as specified in 3GPP TS 33.102[ 3G security; Security architecture ] [5a]. The MS shall apply these derived security keys, handle the STARTCS value as specified in 3GPP TS 25.331[ None ] [23c] and replace an already established UMTS security context for the CS domain, if any, in the USIM, when the SRVCC or vSRVCC handover from S1 mode has been completed successfully. NOTE: Because of deriving a new UMTS security context for the CS domain, a new GSM ciphering key needs also to be derived from the new derived UMTS security keys for the CS domain (i.e. CKSRVCC and IKSRVCC). Note that the new GSM ciphering key is also part of the new UMTS security context for the CS domain as well, as any old GSM ciphering key stored in the USIM and in the ME, belongs to an old UMTS security context for the CS domain and can no longer be used. The network shall replace an already established UMTS security context for the CS domain, if any, when the SRVCC or vSRVCC handover from S1 mode has been completed successfully. If the SRVCC or vSRVCC handover from S1mode has not been completed successfully, the MS and the network shall delete the new derived GSM or UMTS security context for the CS domain. Additionally, the network shall delete the already established GSM or UMTS security context for the CS domain, if the CKSN of the already established GSM or UMTS security context is equal to the CKSN of the new derived GSM or UMTS security context for the CS domain. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.3.2.10.1 |
6,377 | I.2 Authentication in standalone non-public networks I.2.1 General | One of the major differences of non-public networks is that authentication methods other than AKA based ones may be used in a standalone non-public network (SNPN). When an AKA-based authentication method is used, clause 6.1 shall apply. When an authentication method other than 5G AKA or EAP-AKA' is used, only the non-AKA specific parts of clause 6.1 shall apply. An example of running such an authentication method is given in Annex B with EAP-TLS. The choice of the supported authentication methods for access to SNPNs follows the principles described in clauses I.2.2 and I.2.3. The authentication server can be an internal authentication server or an external authentication server. The internal authentication server is the AUSF, and the authentication method can be 5G-AKA or EAP-AKA´ as described in clause 6.1, or can be EAP-TLS as described in Annex B. When external authentication server is the AAA, the primary authentication procedure is described in Annex I.2.2.2.2. When external authentication server is an AUSF, then the primary authentication procedure is described in Annex I.2.4. The UDM decides to run primary authentication with internal authentication server or external authentication server. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | I.2 |
6,378 | 6.3.1.2.3 Abnormal cases on the network side | The following abnormal cases can be identified: a) T3590 expired. The SMF shall, on the first expiry of the timer T3590, retransmit the PDU SESSION AUTHENTICATION COMMAND message and shall reset and start timer T3590. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3590, the SMF shall abort the procedure. b) Collision of UE-requested PDU session release procedure and a PDU session authentication and authorization procedure. When the SMF receives a PDU SESSION RELEASE REQUEST message during the PDU session authentication and authorization procedure, and the PDU session indicated in the PDU SESSION RELEASE REQUEST message is the PDU session that the SMF had requested to authenticate, the SMF shall abort the PDU session authentication and authorization procedure and proceed with the UE-requested PDU session release procedure. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.3.1.2.3 |
6,379 | 19.6A NR Cell Identity (NCI) and NR Cell Global Identity (NCGI) | The NR Cell Global Identity (NCGI) shall be composed of the concatenation of the PLMN Identifier (PLMN-Id) and the NR Cell Identity (NCI) as shown in figure 19.6A-1 and shall be globally unique: Figure 19.6A-1: Structure of NR Cell Global Identity The NCI shall be of fixed length of 36 bits and shall be coded using full hexadecimal representation. The exact coding of the NCI is the responsibility of each PLMN operator. For more details on NCI and NCGI, see 3GPP TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [123]. NOTE: In the 5G Core Network protocols, when the NCGI needs to be identified in the context of Standalone Non-Public Networks (SNPN), the Network Identifier (NID) of the SNPN is included as part of the NCGI Information Element (see 3GPP TS 29.571[ 5G System; Common Data Types for Service Based Interfaces; Stage 3 ] [129]); this is a protocol aspect that does not imply any change on the system-wide definition of the NCGI. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 19.6A |
6,380 | 4.23.9.3 Change of PDU Session Anchor for IPv6 multi-homing or UL CL controlled by I-SMF | This clause describes a change of UL-CL/BP function, e.g. addition of a new PDU Session Anchor (i.e. PSA2) and release of the existing additional PDU Session Anchor (i.e. PSA0), via modifying IPv6 multi-homing or UL CL rule in the same Branching Point or UL CL under controlled by the same I-SMF. Figure 4.23.9.3-1: Change of PDU Session Anchor for Branching Point or UL CL controlled by I-SMF 1. The UE has an established PDU Session with a UPF including the PDU Session Anchor 1(controlled by SMF) and the PDU Session Anchor 0 (PSA0) and an I-UPF acting as UL CL or BP (controlled by I-SMF). Events described in item 1 and 2 of clause 4.23.9.0 have taken place. 2. At some point the I-SMF decides to establish a new PDU Session Anchor and release the existing PDU Session Anchor e.g. due to UE mobility. The I-SMF selects a UPF and using N4 establishes the new PDU Session Anchor 2 of the PDU Session. In the case of IPv6 multi-homing PDU Session, the I-SMF ensures allocation of a new IPv6 prefix corresponding to PSA2. 3. The I-SMF invokes Nsmf_PDUSession_Update Request (Indication of Change of traffic offload, (new allocated IPv6 prefix @PSA2, DNAI(s) supported by PSA2), (Removal of IPv6 prefix @PSA0, DNAI(s) supported by PSA0)) to SMF. The I-SMF informs the SMF that a change of traffic offload may occur. Multiple local PSAs may be changed. The I-SMF provides: - for each local PSA to be added, the DNAI now reachable and in the case of multi-homing: the new allocated IPv6 prefix @PSA2; - for each local PSA no more reachable, the DNAI no more reachable and in the case of multi-homing, the old IPv6 prefix @PSA0. 4. The SMF may issue a SM Policy Association Modification (clause 4.16.5) corresponding to the IP address allocation/release PCRT. The SMF may also send an "early" notification to the AF, as described in clause 4.23.6.3. 5. The SMF generates the N4 information based on DNAI(s) information received in step 3.The SMF provides I-SMF with N4 information for the PSA and for the UL CL with a SMF initiated Nsmf_PDUSession_Update Request (set of (N4 information, involved DNAI), Indication of no DNAI change, Indication of no local PSA change)). The information includes N4 information to remove the traffic offload related to the DNAI(s) that are no more reachable and to enable the traffic offload related to the DNAI(s) that are now reachable. 6-7. Same as step 7-8 of clause 4.23.9.1 8. The I-SMF releases via N4 the PSA0 if PSA0 is not collocated with UL CL/BP, or updates the UL CL/BP to remove corresponding rules if PSA0 is collocated with UL CL/BP. 9. The I-SMF issues a Nsmf_PDUSession_Update Response to SMF that may include N4 information received from the local UPF(s) including the PSA0. 10. Same as step 7-8 of clause 4.3.5.4 are performed. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.9.3 |
6,381 | 28.7.2 NAI format for SUPI | The NAI for SUPI shall have the form username@realm as specified in clause 2.2 of IETF RFC 7542 [126]. A SUPI containing a network specific identifier shall take the form of a Network Access Identifier (NAI). See clause 5.9.2 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [119] for the definition and use of the network specific identifier. In SNPN scenarios, the realm part of the NAI may include MCC, MNC and the NID of the SNPN (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] clauses 5.30.2.3, 5.30.2.9, 6.3.4, and 6.3.8; for the realm part format see Home Network Domain for an SNPN in clause 28.2). See clauses 28.15.2 and 28.16.2 for the NAI format for a SUPI containing a GCI or a GLI. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.7.2 |
6,382 | 8.13.3.4.1 Minimum Requirement Enhanced Performance Requirement Type A – Single-layer Spatial Multiplexing with TM9 interference model (User-Specific Reference Symbols) for FDD PCell | The purpose of these tests is to verify closed loop rank one performance on one of the antenna ports 7 or 8 without a simultaneous transmission on the other antenna port in the serving cell when the PDSCH transmission in the serving cell is interfered by PDSCH of one dominant interfering cell applying transmission mode 9 interference model defined in clause B.5.4. In 8.13.3.4.1-1, Cell 1 is the serving cell, and Cell 2 is the interfering cell. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1 and Cell 2, respectively. For TDD FDD CA with FDD PCell with 2 DL CCs, the requirements are specified in Table 8.13.3.4.1-4, based on single carrier requirement specified in Table 8.13.3.4.1-2 and Table 8.13.3.4.1-3, with the addition of the parameters in Table 8.13.3.4.1-1 and the downlink physical channel setup according to Annex C.3.2. Table 8.13.3.4.1-1: Test Parameters for Testing CDM-multiplexed DM RS (single layer) with TM9 interference model for CA Table 8.13.3.4.1-2: Single carrier performance for Enhanced Performance Requirement Type A, CDM-multiplexed DM RS for FDD PCell (FRC) Table 8.13.3.4.1-3: Single carrier performance for Enhanced Performance Requirement Type A, CDM-multiplexed DM RS for TDD SCell (FRC) Table 8.13.3.4.1-4: Minimum performance (FRC) based on single carrier performance for CA with 2 DL CCs | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.13.3.4.1 |
6,383 | 6.4.2.4.2 Handling of network rejection due to congestion control | If: - the 5GSM cause value #26 "insufficient resources" and the Back-off timer value IE are included in the PDU SESSION MODIFICATION REJECT message; or - an indication that the 5GSM message was not forwarded due to DNN based congestion control is received along a Back-off timer value and a PDU SESSION MODIFICATION REQUEST message with the PDU session ID IE set to the PDU session ID of the PDU session; the UE shall ignore the Re-attempt indicator IE or the 5GSM congestion re-attempt indicator IE provided by the network, if any, and the UE shall take different actions depending on the timer value received for timer T3396 in the Back-off timer value IE or depending on the Back-off timer value received from the 5GMM sublayer (if the UE is a UE configured for high priority access in selected PLMN or SNPN, exceptions are specified in subclause 6.2.7): a) If the timer value indicates neither zero nor deactivated and a DNN was provided during the PDU session establishment, the UE shall stop timer T3396 associated with the corresponding DNN, if it is running. If the timer value indicates neither zero nor deactivated and no DNN was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop timer T3396 associated with no DNN if it is running. In an SNPN, the timer T3396 to be stopped includes: 1) the timer T3396 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and 2) the timer T3396 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE shall then start timer T3396 with the value provided in the Back-off timer value IE or with the Back-off timer value received from the 5GMM sublayer and: 1) shall not send another PDU SESSION ESTABLISHMENT REQUEST message, or PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the same DNN that was sent by the UE, until timer T3396 expires or timer T3396 is stopped; and 2) shall not send another PDU SESSION ESTABLISHMENT REQUEST message without a DNN and with request type different from "initial emergency request" and different from "existing emergency PDU session", or another PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for a non-emergency PDU session established without a DNN provided by the UE, if no DNN was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", until timer T3396 expires or timer T3396 is stopped. The UE shall not stop timer T3396 upon a PLMN change, SNPN change, or inter-system change. b) if the timer value indicates that this timer is deactivated and a DNN was provided during the PDU session establishment, the UE shall stop timer T3396 associated with the corresponding DNN, if it is running. If the timer value indicates that this timer is deactivated and no DNN was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop timer T3396 associated with no DNN if it is running. In an SNPN, the timer T3396 to be stopped includes: 1) the timer T3396 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and 2) the timer T3396 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE: 1) shall not send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST with exception of those identified in subclause 6.4.2.1, for the same DNN until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated, or the UE receives a PDU SESSION MODIFICATION COMMAND message for the same DNN from the network, or a PDU SESSION AUTHENTICATION COMMAND message for the same DNN from the network, or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE for the same DNN from the network; and 2) shall not send another PDU SESSION ESTABLISHMENT REQUEST message without a DNN and with request type different from "initial emergency request" and different from "existing emergency PDU session", or another PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for a non-emergency PDU session established without a DNN provided by the UE, if no DNN was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated, or the UE receives a PDU SESSION MODIFICATION COMMAND message for a non-emergency PDU session established without a DNN provided by the UE, a PDU SESSION AUTHENTICATION COMMAND message for a non-emergency PDU session established without a DNN provided by the UE, or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE for a non-emergency PDU session established without a DNN provided by the UE. The timer T3396 remains deactivated upon a PLMN change, SNPN change, or inter-system change. c) if the timer value indicates zero, the UE: 1) shall stop timer T3396 associated with the corresponding DNN, if running. In an SNPN, the timer T3396 to be stopped includes: i) the timer T3396 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and ii) the timer T3396 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE may send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message for the same DNN; and 2) if no DNN was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop timer T3396 associated with no DNN, if running. In an SNPN, the timer T3396 to be stopped includes: i) the timer T3396 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and ii) the timer T3396 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE may send another PDU SESSION ESTABLISHMENT REQUEST message without a DNN, or another PDU SESSION MODIFICATION REQUEST message without a DNN provided by the UE. In an SNPN, if the UE supports equivalent SNPNs then the UE shall apply the timer T3396 for all the equivalent SNPNs. Otherwise, the UE shall apply the timer T3396 for the registered SNPN. If the Back-off timer value IE is not included or no Back-off timer value is received from the 5GMM sublayer, then the UE may send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message for the same DNN or without a DNN. If the timer T3396 is running when the UE enters state 5GMM-DEREGISTERED, the UE remains switched on, and the USIM in the UE (if any) remains the same and the entry in the "list of subscriber data" for the SNPN to which timer T3396 is associated (if any) is not updated, then timer T3396 is kept running until it expires or it is stopped When the timer T3396 is running or the timer is deactivated, the UE is allowed to initiate a PDU session establishment procedure for emergency services. If the UE is switched off when the timer T3396 is running, and if the USIM in the UE (if any) remains the same and the entry in the "list of subscriber data" for the SNPN to which timer T3396 is associated (if any) is not updated when the UE is switched on, the UE shall behave as follows: - let t1 be the time remaining for T3396 timeout at switch off and let t be the time elapsed between switch off and switch on. If t1 is greater than t, then the timer shall be restarted with the value t1 – t. If t1 is equal to or less than t, then the timer need not be restarted. If the UE is not capable of determining t, then the UE shall restart the timer with the value t1. If the UE is a UE operating in single-registration mode in a network supporting N26 interface and the PDU SESSION MODIFICATION REQUEST message was sent for a PDN connection established when in S1 mode after an inter-system change from S1 mode to N1 mode and timer T3396 associated with the corresponding DNN (or no DNN) is running, then the UE shall re-initiate the UE-requested PDU session modification procedure after expiry of timer T3396. If: - the 5GSM cause value #67 "insufficient resources for specific slice and DNN" and the Back-off timer value IE are included in the PDU SESSION MODIFICATION REJECT message; or - an indication that the 5GSM message was not forwarded due to S-NSSAI and DNN based congestion control is received along a Back-off timer value and a PDU SESSION MODIFICATION REQUEST message with the PDU session ID IE set to the PDU session ID of the PDU session; the UE shall ignore the Re-attempt indicator IE provided by the network, if any, and take different actions depending on the timer value received for timer T3584 in the Back-off timer value IE or depending on the Back-off timer value received from the 5GMM sublayer (if the UE is a UE configured for high priority access in selected PLMN or SNPN, exceptions are specified in subclause 6.2.8): a) If the timer value indicates neither zero nor deactivated, and both an S-NSSAI and a DNN were provided by the UE during the PDU session establishment, the UE shall stop timer T3584 associated with the [S-NSSAI of the PDU session, DNN] combination, if it is running. If the timer value indicates neither zero nor deactivated, an S-NSSAI and no DNN was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop timer T3584 associated with [S-NSSAI of the PDU session, no DNN] combination, if it is running. If the timer value indicates neither zero nor deactivated, no S-NSSAI and a DNN was provided during the PDU session establishment, the UE shall stop timer T3584 associated with the [no S-NSSAI, DNN] combination, if it is running. If the timer value indicates neither zero nor deactivated and neither S-NSSAI nor DNN was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop timer T3584 associated with the [no S-NSSAI, no DNN] combination, if it is running. The timer T3584 to be stopped includes: 1) in a PLMN: i) the timer T3584 applied for all the PLMNs, if running; and ii) the timer T3584 applied for the registered PLMN, if running; or 2) in an SNPN: i) the timer T3584 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and ii) the timer T3584 applied for the registered SNPN, associated with the RSNPN and, if the UE 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, if running. The UE shall then start timer T3584 with the value provided in the Back-off timer value IE or with the Back-off timer value received from the 5GMM sublayer and: 1) shall not send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message with the exception of those identified in subclause 6.4.2.1, for the [S-NSSAI, DNN] combination, until timer T3584 expires or timer T3584 is stopped; 2) shall not send another PDU SESSION ESTABLISHMENT REQUEST message with request type different from "initial emergency request" and different from "existing emergency PDU session", or another PDU SESSION MODIFICATION REQUEST message with the exception of those identified in subclause 6.4.2.1, for the [S-NSSAI of the PDU session, no DNN] combination, if no DNN was provided during the PDU session establishment, until timer T3584 expires or timer T3584 is stopped; 3) shall not send another PDU SESSION ESTABLISHMENT REQUEST message, or another PDU SESSION MODIFICATION REQUEST message with the exception of those identified in subclause 6.4.2.1, for the [no S-NSSAI, DNN] combination, if no S-NSSAI was provided during the PDU session establishment, until timer T3584 expires or timer T3584 is stopped; and 4) shall not send another PDU SESSION ESTABLISHMENT REQUEST message with request type different from "initial emergency request" and different from "existing emergency PDU session", or another PDU SESSION MODIFICATION REQUEST message with the exception of those identified in subclause 6.4.2.1, for the [no S-NSSAI, no DNN] combination, if neither S-NSSAI nor DNN was provided during the PDU session establishment, until timer T3584 expires or timer T3584 is stopped. The UE shall not stop timer T3584 upon a PLMN change, SNPN change, or inter-system change; b) if the timer value indicates that this timer is deactivated: 1) if both S-NSSAI and DNN were provided by the UE during the PDU session establishment, the UE shall stop timer T3584 associated with the [S-NSSAI of the PDU session, DNN] combination, if running. The timer T3584 to be stopped includes: i) in a PLMN: A) the timer T3584 applied for all the PLMNs, if running; and B) the timer T3584 applied for the registered PLMN, if running; or ii) in an SNPN: A) the timer T3584 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and B) the timer T3584 applied for the registered SNPN, associated with the RSNPN and, if the UE 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, if running. The UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the [S-NSSAI of the PDU session, DNN] combination that was sent by the UE, until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated, or the UE receives a PDU SESSION MODIFICATION COMMAND message for the [S-NSSAI of the PDU session, DNN] combination from the network, or a PDU SESSION AUTHENTICATION COMMAND message for the [S-NSSAI of the PDU session, DNN] combination from the network, or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE for the [S-NSSAI of the PDU session, DNN] combination from the network; 2) if an S-NSSAI was provided but a DNN was not provided by the UE during the PDU session establishment, the UE shall stop timer T3584 associated with the [S-NSSAI of the PDU session, no DNN] combination, if running. The timer T3584 to be stopped includes: i) in a PLMN: A) the timer T3584 applied for all the PLMNs, if running; and B) the timer T3584 applied for the registered PLMN, if running; or ii) in an SNPN: A) the timer T3584 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and B) the timer T3584 applied for the registered SNPN, associated with the RSNPN and, if the UE 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, if running. The UE shall not send a PDU SESSION ESTABLISHMENT REQUEST message with request type different from "initial emergency request" and different from "existing emergency PDU session", or a PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the [S-NSSAI of the PDU session, no DNN] combination, if no DNN was provided during the PDU session establishment, until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated, or the UE receives a PDU SESSION MODIFICATION COMMAND message for a non-emergency PDU session established for the [S-NSSAI of the PDU session, no DNN] combination from the network, or a PDU SESSION AUTHENTICATION COMMAND message for a non-emergency PDU session established for the [S-NSSAI of the PDU session, no DNN] combination from the network, or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE for a non-emergency PDU session established for the [S-NSSAI of the PDU session, no DNN] combination from the network; 3) if an S-NSSAI was not provided but a DNN was provided by the UE during the PDU session establishment, the UE shall stop timer T3584 associated with the [no S-NSSAI, DNN] combination, if running. The timer T3584 to be stopped includes: i) in a PLMN: A) the timer T3584 applied for all the PLMNs, if running; and B) the timer T3584 applied for the registered PLMN, if running; or ii) in an SNPN: A) the timer T3584 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and B) the timer T3584 applied for the registered SNPN, associated with the RSNPN and, if the UE 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, if running. The UE shall not send a PDU SESSION ESTABLISHMENT REQUEST message, or a PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the [no S-NSSAI, DNN] combination, if no S-NSSAI was provided during the PDU session establishment, until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated, or the UE receives a PDU SESSION MODIFICATION COMMAND message for the [no S-NSSAI, DNN] combination from the network, or a PDU SESSION AUTHENTICATION COMMAND message for the [no S-NSSAI, DNN] combination from the network, or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE for the [no S-NSSAI, DNN] combination from the network; and 4) if neither S-NSSAI nor DNN were provided by the UE during the PDU session establishment, the UE shall stop timer T3584 associated with the [no S-NSSAI, no DNN] combination, if running. The timer T3584 to be stopped includes: i) in a PLMN: A) the timer T3584 applied for all the PLMNs, if running; and B) the timer T3584 applied for the registered PLMN, if running; or ii) in an SNPN: A) the timer T3584 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and B) the timer T3584 applied for the registered SNPN, associated with the RSNPN and, if the UE 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, if running. The UE shall not send a PDU SESSION ESTABLISHMENT REQUEST message with request type different from "initial emergency request" and different from "existing emergency PDU session", or a PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the [no S-NSSAI, no DNN] combination, if neither S-NSSAI nor DNN was provided during the PDU session establishment, until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated, or the UE receives a PDU SESSION MODIFICATION COMMAND message for a non-emergency PDU session established for the [no S-NSSAI, no DNN] combination from the network, or a PDU SESSION AUTHENTICATION COMMAND message for a non-emergency PDU session established for the [no S-NSSAI, no DNN] combination from the network, or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE for a non-emergency PDU session established for the [no S-NSSAI, no DNN] combination from the network. The timer T3584 remains deactivated upon a PLMN change, SNPN change, or inter-system change; and c) if the timer value indicates zero: 1) if both S-NSSAI and DNN were provided by the UE during the PDU session establishment, the UE shall stop timer T3584 associated with the [S-NSSAI of the PDU session, DNN] combination, if running. The timer T3584 to be stopped includes: i) in a PLMN: A) the timer T3584 applied for all the PLMNs, if running; and B) the timer T3584 applied for the registered PLMN, if running; or ii) in an SNPN: A) the timer T3584 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and B) the timer T3584 applied for the registered SNPN, associated with the RSNPN and, if the UE 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, if running. The UE may send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message for the [S-NSSAI of the PDU session, DNN] combination; 2) if an S-NSSAI was provided but a DNN was not provided by the UE during the PDU session establishment, the UE shall stop timer T3584 associated with the [S-NSSAI of the PDU session, no DNN] combination, if running. The timer T3584 to be stopped includes: i) in a PLMN: A) the timer T3584 applied for all the PLMNs, if running; and B) the timer T3584 applied for the registered PLMN, if running; or ii) in an SNPN: A) the timer T3584 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and B) the timer T3584 applied for the registered SNPN, associated with the RSNPN and, if the UE 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, if running. The UE may send another PDU SESSION ESTABLISHMENT REQUEST message, or PDU SESSION MODIFICATION REQUEST message for the [S-NSSAI of the PDU session, no DNN] combination if the request type was different from "initial emergency request" and different from "existing emergency PDU session"; 3) if an S-NSSAI was not provided but a DNN was provided by the UE during the PDU session establishment, the UE shall stop timer T3584 associated with the [no S-NSSAI, DNN] combination, if running. The timer T3584 to be stopped includes: i) in a PLMN: A) the timer T3584 applied for all the PLMNs, if running; and B) the timer T3584 applied for the registered PLMN, if running; or ii) in an SNPN: A) the timer T3584 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and B) the timer T3584 applied for the registered SNPN, associated with the RSNPN and, if the UE 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, if running. The UE may send another PDU SESSION ESTABLISHMENT REQUEST message, or PDU SESSION MODIFICATION REQUEST message for the [no S-NSSAI, DNN] combination; and 4) if neither S-NSSAI nor DNN were provided by the UE during the PDU session establishment, the UE shall stop timer T3584 associated with the [no S-NSSAI, no DNN] combination, if running. The timer T3584 to be stopped includes: i) in a PLMN: A) the timer T3584 applied for all the PLMNs, if running; and B) the timer T3584 applied for the registered PLMN, if running; or ii) in an SNPN: A) the timer T3584 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and B) the timer T3584 applied for the registered SNPN, associated with the RSNPN and, if the UE 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, if running. The UE may send another PDU SESSION ESTABLISHMENT REQUEST message, or PDU SESSION MODIFICATION REQUEST message for the [no S-NSSAI, no DNN] combination and the request type was different from "initial emergency request" and different from "existing emergency PDU session". If the 5GSM congestion re-attempt indicator IE with the ABO bit set to "The back-off timer is applied in all PLMNs or all equivalent SNPNs" is included in the PDU SESSION MODIFICATION REJECT message with the 5GSM cause value #67 "insufficient resources for specific slice and DNN", then the UE shall apply the timer T3584 for all the PLMNs or all the equivalent SNPNs. Otherwise, the UE shall apply the timer T3584 for the registered PLMN or the registered SNPN. If the Back-off timer value IE is not included or no Back-off timer value is received from the 5GMM sublayer, then the UE may send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message for the same [S-NSSAI, DNN] combination, or for the same [S-NSSAI, no DNN] combination, or for the same [no S-NSSAI, DNN] combination, or for the same [no S-NSSAI, no DNN] combination. When the timer T3584 is running or the timer is deactivated, the UE is allowed to initiate a PDU session establishment procedure for emergency services. If the timer T3584 is running when the UE enters state 5GMM-DEREGISTERED, the UE remains switched on, and the USIM in the UE (if any) remains the same and the entry in the "list of subscriber data" for the SNPN to which timer T3584 is associated (if any) is not updated, then timer T3584 is kept running until it expires or it is stopped. If the UE is switched off when the timer T3584 is running, and if the USIM in the UE (if any) remains the same and the entry in the "list of subscriber data" for the SNPN to which timer T3584 is associated (if any) is not updated when the UE is switched on, the UE shall behave as follows: - let t1 be the time remaining for T3584 timeout at switch off and let t be the time elapsed between switch off and switch on. If t1 is greater than t, then the timer shall be restarted with the value t1 – t. If t1 is equal to or less than t, then the timer need not be restarted. If the UE is not capable of determining t, then the UE shall restart the timer with the value t1. If the UE is a UE operating in single-registration mode in a network supporting N26 interface and the PDU SESSION MODIFICATION REQUEST message was sent for a PDN connection established when in S1 mode after an inter-system change from S1 mode to N1 mode and timer T3584 associated with the corresponding [no S-NSSAI, DNN] combination or [no S-NSSAI, no DNN] combination is running, then the UE shall re-initiate the UE-requested PDU session modification procedure after expiry of timer T3584. If: - the 5GSM cause value #69 "insufficient resources for specific slice" and the Back-off timer value IE are included in the PDU SESSION MODIFICATION REJECT message; or - an indication that the 5GSM message was not forwarded due to S-NSSAI only based congestion control is received along a Back-off timer value and a PDU SESSION MODIFICATION REQUEST message with the PDU session ID IE set to the PDU session ID of the PDU session; the UE shall ignore the bit "RATC" and the bit "EPLMNC" in the Re-attempt indicator IE provided by the network, if any, and take different actions depending on the timer value received for timer T3585 in the Back-off timer value IE or depending on the Back-off timer value received from the 5GMM sublayer (if the UE is a UE configured for high priority access in selected PLMN or SNPN, exceptions are specified in subclause 6.2.8): a) If the timer value indicates neither zero nor deactivated and an S-NSSAI was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop timer T3585 associated with the S-NSSAI of the PDU session, if it is running. If the timer value indicates neither zero nor deactivated and no S-NSSAI was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop timer T3585 associated with no S-NSSAI if it is running. The timer T3585 to be stopped includes: 1) in a PLMN: i) the timer T3585 applied for all the PLMNs and for the access over which the PDU SESSION MODIFICATION REJECT is received, if running; ii) the timer T3585 applied for all the PLMNs and for both 3GPP access type and non-3GPP access type, if running; iii) the timer T3585 applied for the registered PLMN and for the access over which the PDU SESSION MODIFICATION REJECT is received, if running; and iv)- the timer T3585 applied for the registered PLMN and for both 3GPP access type and non-3GPP access type, if running; or 2) in an SNPN: i) the timer T3585 applied for all the equivalent SNPNs and for the access over which the PDU SESSION AUTHENTICATION COMMAND message is received, associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; ii) the timer T3585 applied for all the equivalent SNPNs and for both 3GPP access type and non-3GPP access type, associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; iii) the timer T3585 applied for the registered SNPN and for the access over which the PDU SESSION AUTHENTICATION COMMAND message is received, associated with the RSNPN and, if the UE 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, if running; and iv) the timer T3585 applied for the registered PLMN and for both 3GPP access type and non-3GPP access type, associated with the RSNPN and, if the UE 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, if running. The UE shall then start timer T3585 with the value provided in the Back-off timer value IE or with the Back-off timer value received from the 5GMM sublayer and: 1) if an S-NSSAI was provided by the UE during the PDU session establishment, the UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message with request type different from "initial emergency request" and different from "existing emergency PDU session", or another PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for a non-emergency PDU session for the S-NSSAI of the PDU session, until timer T3585 expires or timer T3585 is stopped; and 2) if the request type was different from "initial emergency request" and from "existing emergency PDU session", and an S-NSSAI was not provided by the UE during the PDU session establishment, the UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message without an S-NSSAI and with request type different from "initial emergency request" and different from "existing emergency PDU session", or another PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for a non-emergency PDU session established without an S-NSSAI provided by the UE, until timer T3585 expires or timer T3585 is stopped. The UE shall not stop timer T3585 upon a PLMN change, SNPN change, or inter-system change; b) if the timer value indicates that this timer is deactivated and an S-NSSAI was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop timer T3585 associated with the S-NSSAI of the PDU session, if it is running. If the timer value indicates that this timer is deactivated and no S-NSSAI was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop timer T3585 associated with no S-NSSAI if it is running. The timer T3585 to be stopped includes: 1) in a PLMN: i) the timer T3585 applied for all the PLMNs and for the access over which the PDU SESSION MODIFICATION REJECT is received, if running; ii) the timer T3585 applied for all the PLMNs and for both 3GPP access type and non-3GPP access type, if running; iii) the timer T3585 applied for the registered PLMN and for the access over which the PDU SESSION MODIFICATION REJECT is received, if running; and iv) the timer T3585 applied for the registered PLMN and for both 3GPP access type and non-3GPP access type, if running; or 2) in an SNPN: i) the timer T3585 applied for all the equivalent SNPNs and for the access over which the PDU SESSION AUTHENTICATION COMMAND message is received, associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; ii) the timer T3585 applied for all the equivalent SNPNs and for both 3GPP access type and non-3GPP access type, associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; iii) the timer T3585 applied for the registered SNPN and for the access over which the PDU SESSION AUTHENTICATION COMMAND message is received, associated with the RSNPN and, if the UE 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, if running; and iv) the timer T3585 applied for the registered PLMN and for both 3GPP access type and non-3GPP access type, associated with the RSNPN and, if the UE 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, if running. In addition: 1) if an S-NSSAI was provided by the UE during the PDU session establishment, the UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message with request type different from "initial emergency request" and different from "existing emergency PDU session", or another PDU SESSION MODIFICATION REQUEST with exception of those identified in subclause 6.4.2.1, for a non-emergency PDU session for the S-NSSAI of the PDU session until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated, or the UE receives a PDU SESSION MODIFICATION COMMAND message for a non-emergency PDU session for the S-NSSAI of the PDU session from the network, or a PDU SESSION AUTHENTICATION COMMAND message for a non-emergency PDU session for the S-NSSAI of the PDU session from the network, or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE for the S-NSSAI of the PDU session from the network; and 2) if the request type was different from "initial emergency request" and from "existing emergency PDU session", and an S-NSSAI was not provided by the UE during the PDU session establishment, the UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message without an S-NSSAI and with request type different from "initial emergency request" and different from "existing emergency PDU session", or another PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for a non-emergency PDU session established without an S-NSSAI provided by the UE, until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated, or the UE receives a PDU SESSION MODIFICATION COMMAND message for a non-emergency PDU session established without an S-NSSAI provided by the UE, or a PDU SESSION AUTHENTICATION COMMAND message for a non-emergency PDU session established without an S-NSSAI provided by the UE, or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE for a non-emergency PDU session established without an S-NSSAI provided by the UE. The timer T3585 remains deactivated upon a PLMN change, SNPN change, or inter-system change; and c) if the timer value indicates zero: 1) if an S-NSSAI was provided by the UE during the PDU session establishment, the UE shall stop timer T3585 associated with the S-NSSAI of the PDU session, if running. The timer T3585 to be stopped includes: i) in a PLMN: A) including the timer T3585 applied for all the PLMNs and for the access over which the PDU SESSION RELEASE COMMAND is received, if running; B) the timer T3585 applied for all the PLMNs and for the access over which the PDU SESSION RELEASE COMMAND is received, if running; C) the timer T3585 applied for the registered PLMN and for current access type or both 3GPP access type and non-3GPP access type, if running; and D) the timer T3585 applied for the registered PLMN and for both 3GPP access type and non-3GPP access type, if running; or ii) in an SNPN: A) the timer T3585 applied for all the equivalent SNPNs and for the access over which the PDU SESSION AUTHENTICATION COMMAND message is received, associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; B) the timer T3585 applied for all the equivalent SNPNs and for both 3GPP access type and non-3GPP access type, associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; C) the timer T3585 applied for the registered SNPN and for the access over which the PDU SESSION AUTHENTICATION COMMAND message is received, associated with the RSNPN and, if the UE 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, if running; and D) the timer T3585 applied for the registered PLMN and for both 3GPP access type and non-3GPP access type, associated with the RSNPN and, if the UE 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, if running. The UE may send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message for the S-NSSAI of the PDU session; and 2) if no S-NSSAI was provided during the PDU session establishment and the request type was different from “initial emergency request “ and different from “existing emergency PDU session”, the UE shall stop timer T3585 associated with no S-NSSAI The timer T3585 to be stopped includes: i) in a PLMN: A) the timer T3585 applied for all the PLMNs and for the access over which the PDU SESSION RELEASE COMMAND is received, if running; B) the timer T3585 applied for all the PLMNs and for the access over which the PDU SESSION RELEASE COMMAND is received, if running; C) the timer T3585 applied for the registered PLMN and for current access type or both 3GPP access type and non-3GPP access type, if running; and D) the timer T3585 applied for the registered PLMN and for both 3GPP access type and non-3GPP access type, if running; or ii) in an SNPN: A) the timer T3585 applied for all the equivalent SNPNs and for the access over which the PDU SESSION AUTHENTICATION COMMAND message is received, associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; B) the timer T3585 applied for all the equivalent SNPNs and for both 3GPP access type and non-3GPP access type, associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; C) the timer T3585 applied for the registered SNPN and for the access over which the PDU SESSION AUTHENTICATION COMMAND message is received, associated with the RSNPN and, if the UE 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, if running; and D) the timer T3585 applied for the registered PLMN and for both 3GPP access type and non-3GPP access type, associated with the RSNPN and, if the UE 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, if running. The UE may send another PDU SESSION ESTABLISHMENT REQUEST message without an S-NSSAI, or another PDU SESSION MODIFICATION REQUEST message without an S-NSSAI provided by the UE. If the 5GSM congestion re-attempt indicator IE with the ABO bit set to "The back-off timer is applied in all PLMNs or all SNPNs " is included in the PDU SESSION MODIFICATION REJECT message with the 5GSM cause value #69 "insufficient resources for specific slice", then the UE shall apply the timer T3585 for all the PLMNs or all the equivalent SNPNs. Otherwise, the UE shall apply the timer T3585 for the registered PLMN or the registered SNPN. If the Back-off timer value IE is not included or no Back-off timer value is received from the 5GMM sublayer, then the UE may send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message for the same S-NSSAI or without an S-NSSAI. When the timer T3585 is running or the timer is deactivated, the UE is allowed to initiate a PDU session establishment procedure for emergency services. If the timer T3585 is running when the UE enters state 5GMM-DEREGISTERED, the UE remains switched on, and the USIM in the UE (if any) remains the same and the entry in the "list of subscriber data" for the SNPN to which timer T3585 is associated (if any) is not updated, then timer T3585 is kept running until it expires or it is stopped. If the UE is switched off when the timer T3585 is running, and if the USIM in the UE (if any) remains the same and the entry in the "list of subscriber data" for the SNPN to which timer T3585 is associated (if any) is not updated when the UE is switched on, the UE shall behave as follows: - let t1 be the time remaining for T3585 timeout at switch off and let t be the time elapsed between switch off and switch on. If t1 is greater than t, then the timer shall be restarted with the value t1 – t. If t1 is equal to or less than t, then the timer need not be restarted. If the UE is not capable of determining t, then the UE shall restart the timer with the value t1. If the UE is a UE operating in single-registration mode in a network supporting N26 interface and the PDU SESSION MODIFICATION REQUEST message was sent for a PDN connection established when in S1 mode after an inter-system change from S1 mode to N1 mode and timer T3585 associated with no S-NSSAI is running, then the UE shall re-initiate the UE-requested PDU session modification procedure after expiry of timer T3585. NOTE 3: As described in this subclause, upon PLMN change, SNPN change, or inter-system change, the UE does not stop the timer T3584 or T3585. This means the timer T3584 or T3585 can still be running or be deactivated for the given 5GSM procedure, the PLMN, the S-NSSAI and optionally the DNN combination when the UE returns to the PLMN or when it performs inter-system change back from S1 mode to N1 mode. Thus the UE can still be prevented from sending another PDU SESSION ESTABLISHMENT REQUEST or PDU SESSION MODIFICATION REQUEST message in the PLMN for the same S-NSSAI and optionally the same DNN. Upon PLMN change or SNPN change, if T3584 applied for the registered PLMN or the registered SNPN is running or is deactivated for an S-NSSAI, a DNN, and old PLMN or old SNPN, but T3584 is not running and is not deactivated for the S-NSSAI, the DNN, and new PLMN or new SNPN, then the UE is allowed to send a PDU SESSION ESTABLISHMENT REQUEST message for the same S-NSSAI and the same DNN in the new PLMN or new SNPN. Upon PLMN change or SNPN change, if T3585 applied for the registered PLMN or the registered SNPN is running or is deactivated for an S-NSSAI and old PLMN or old SNPN, but T3585 is not running and is not deactivated for the S-NSSAI and new PLMN or new SNPN, then the UE is allowed to send a PDU SESSION ESTABLISHMENT REQUEST message for the same S-NSSAI in the new PLMN or new SNPN. Upon SNPN change, if T3585 applied for all the equivalent SNPNs is running or is deactivated for an S-NSSAI and old SNPN, but T3585 is not running and is not deactivated for the S-NSSAI and new non-equivalent SNPN, then the UE is allowed to send a PDU SESSION ESTABLISHMENT REQUEST message for the same S-NSSAI in the new SNPN. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.4.2.4.2 |
6,384 | – NCR-FwdConfig | The IE NCR-FwdConfig contains configuration related to periodic, aperiodic and semi-persistent beam indication for NCR-Fwd access link. NCR-FwdConfig information element -- ASN1START -- TAG-NCR-FWDCONFIG-START NCR-FwdConfig-r18 ::= SEQUENCE { periodicFwdRsrcSetToAddModList-r18 SEQUENCE (SIZE (1..maxNrofPeriodicFwdResourceSet-r18)) OF NCR-PeriodicFwdResourceSet-r18 OPTIONAL, -- Need N periodicFwdRsrcSetToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofPeriodicFwdResourceSet-r18)) OF NCR-PeriodicFwdResourceSetId-r18 OPTIONAL, -- Need N aperiodicFwdConfig-r18 NCR-AperiodicFwdConfig-r18 OPTIONAL, -- Need N semiPersistentFwdRsrcSetToAddModList-r18 SEQUENCE (SIZE (1..maxNrofSemiPersistentFwdResourceSet-r18)) OF NCR-SemiPersistentFwdResourceSet-r18 OPTIONAL, -- Need N semiPersistentFwdRsrcSetToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofSemiPersistentFwdResourceSet-r18)) OF NCR-SemiPersistentFwdResourceSetId-r18 OPTIONAL, -- Need N ... } -- TAG-NCR-FWDCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,385 | 8.2.3.5.2 Minimum Requirement for TDD PCell | For TDD FDD CA with TDD PCell and 2DL CCs, the requirements are specified in Table 8.2.3.5.2-4 based on single carrier requirement specified in Table 8.2.5.2.2-2 and Table 8.2.3.5.2-3, with the addition of the parameters in Table 8.2.3.5.2-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of large delay CDD with 2 transmitter antennas. For TDD FDD CA with TDD PCell and 3DL CCs, the requirements are specified in Table 8.2.3.5.2-5 based on single carrier requirement specified in Table 8.2.3.5.2-2 and Table 8.2.3.5.2-3, with the addition of the parameters in Table 8.2.3.5.2-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of large delay CDD with 2 transmitter antennas. For TDD FDD CA with TDD PCell and 4DL CCs, the requirements are specified in Table 8.2.3.5.2-6 based on single carrier requirement specified in Table 8.2.3.5.2-2 and Table 8.2.3.5.2-3, with the addition of the parameters in Table 8.2.3.5.2-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of large delay CDD with 2 transmitter antennas. For TDD FDD CA with TDD PCell and 5DL CCs, the requirements are specified in Table 8.2.3.5.2-7 based on single carrier requirement specified in Table 8.2.3.5.2-2 and Table 8.2.3.5.2-3, with the addition of the parameters in Table 8.2.3.5.2-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of large delay CDD with 2 transmitter antennas. The test coverage for different number of component carriers is defined in 8.1.2.4. Table 8.2.3.5.2-1: Test Parameters for Large Delay CDD (FRC) for CA Table 8.2.3.5.2-2: Single carrier performance with different bandwidths for multiple CA configurations for FDD SCell (FRC) Table 8.2.3.5.2-3: Single carrier performance with different bandwidths for multiple CA configurations for TDD PCell and SCell (FRC) Table 8.2.3.5.2-4: Minimum performance for multiple CA configurations with 2DL CCs (FRC) Table 8.2.3.5.2-5: Minimum performance for multiple CA configurations with 3DL CCs (FRC) Table 8.2.3.5.2-6: Minimum performance for multiple CA configurations with 4DL CCs (FRC) Table 8.2.3.5.2-7: Minimum performance for multiple CA configurations with 5DL CCs (FRC) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.3.5.2 |
6,386 | 9.2.2.4.2 Network triggered transition from RRC_INACTIVE to RRC_CONNECTED | The following figure describes the network triggered transition from RRC_INACTIVE to RRC_CONNECTED: Figure 9.2.2.4.2-1: Network triggered transition from RRC_INACTIVE to RRC_CONNECTED 1. A RAN paging trigger event occurs (incoming DL user plane, DL signalling from 5GC, etc.). 2. RAN paging is triggered; either only in the cells controlled by the last serving gNB or also by means of Xn RAN Paging in cells controlled by other gNBs, configured to the UE in the RAN-based Notification Area (RNA). 3. The UE is paged with the I-RNTI. 4. If the UE has been successfully reached, it attempts to resume from RRC_INACTIVE, as described in clause 9.2.2.4.1. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 9.2.2.4.2 |
6,387 | 6.6.2.2A.3 Minimum requirement CA_66C (network signalled value "CA_NS_09") | Additional spectrum emission requirements are signalled by the network to indicate that the UE shall meet an additional requirement for a specific deployment scenario as part of the cell handover/broadcast message. When "CA_NS_09" is indicated in the cell, the power of any UE emission shall not exceed the levels specified in Table 6.6.2.2A.3-1. Table 6.6.2.2A.3-1: Additional requirements NOTE: As a general rule, the resolution bandwidth of the measuring equipment should be equal to the measurement bandwidth. However, to improve measurement accuracy, sensitivity and efficiency, the resolution bandwidth may be smaller than the measurement bandwidth. When the resolution bandwidth is smaller than the measurement bandwidth, the result should be integrated over the measurement bandwidth in order to obtain the equivalent noise bandwidth of the measurement bandwidth. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.6.2.2A.3 |
6,388 | 4.13.6 Support of Tracking Area Update | A moving cell for NB-IoT, LTE-M or WB-E-UTRAN satellite access may indicate support for one or more Tracking Areas Codes (TACs) for each PLMN (see clause 4.13.7). A UE that is registered with a PLMN may access a cell and does not need to perform a Tracking Area Update procedure for mobility reasons as long as at least one supported TAC for the RPLMN or equivalent to the RPLMN indicated in the cell is part of the UE's Tracking Area List. A UE shall perform a Tracking Area Update procedure when entering a cell where none of the supported TACs for the RPLMN or equivalent to the RPLMN indicated in the cell are part of the UE's Tracking Area List. When indicating a last visited TAI in an Attach Request or a TAU Request, a UE may indicate any TAI supported in the last visited cell for that RPLMN or PLMN equivalent to the RPLMN. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.13.6 |
6,389 | 6.16.2.4 Connection Resume in CM-IDLE with Suspend to the same ng-eNB | The target ng-eNB may be the same as the source ng-eNB in the description in the previous subclause. If so the single ng-eNB performs the roles of both the source and target ng-eNB. In particular, a new KNG-RAN* shall be derived even if the UE is resuming to the same cell from where it was suspended. However, there is the following difference. After a successful resume, the ng-eNB shall send N2 Resume Request message to the AMF. Upon reception of the N2 Resume Request message, the AMF shall check its local policy. If the local policy in the AMF indicates that a new NH derivation is needed, the AMF shall increase its locally kept NCC value by one and compute a fresh NH from its stored data using the function defined in Annex A.10. The AMF shall store that fresh pair and send it to the ng-eNB in the N2 Resume Response message. Upon receipt of the N2 Resume Response message from the AMF and if the message includes a {NH, NCC} pair, the ng-eNB shall store the {NH, NCC} pair in the N2 Resume Response message and remove any existing unused stored {NH, NCC} pairs. The {NH, NCC} pair may be used in the next suspend/resume or Xn handover procedures. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.16.2.4 |
6,390 | 4.1.1.6A Specific requirements for the MS when receiving non-integrity protected reject messages | This subclause specifies the requirements for an MS that is not configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112]) and receives a LOCATION UPDATING REJECT, CM SERVICE REJECT, ABORT, ATTACH REJECT, ROUTING AREA UPDATE REJECT or SERVICE REJECT message without integrity protection with specific MM or GMM causes. NOTE 1: Additional MS requirements for this case, requirements for other MM or GMM causes, and requirements for the case when the MS receives a successfully integrity checked reject message are specified in subclauses 4.4.4.7, 4.5.1.1, 4.7.3.1.4, 4.7.3.2.4, 4.7.5.1.4, 4.7.5.2.4 and 4.7.13.4. The present subclause is applicable to A/Gb mode and Iu mode. In A/Gb mode, - for the CS domain, as integrity protection is not supported, all messages received by the MS are considered to be received "before the network has activated the integrity protection"; and - for the PS domain, if integrity protection is not required (see subclause 4.7.1.2a.), all messages received by the MS are considered to be received "before the network has activated the integrity protection". The MS may maintain a list of PLMN-specific attempt counters and a list of PLMN-specific PS-attempt counters. The maximum number of possible entries in each list is implementation dependent. Additionally, the MS may maintain one counter for "SIM/USIM considered invalid for non-GPRS services" events and one counter for "SIM/USIM considered invalid for GPRS services" events. If the MS maintains the above lists of attempt counters and the event counters, a MS supporting N1 mode, shall store them in its non-volatile memory. The UE shall erase the lists and reset the event counters to zero when the UICC containing the USIM is removed. The counter values shall not be affected by the activation or deactivation of power saving mode. The MS may also maintain a list of "forbidden location areas for non-GPRS services" and a list of "forbidden location areas for GPRS services". If the MS is in a location area which is included in the list of "forbidden location areas for non-GPRS services", the MS shall not initiate any MM procedure. If the MS is in a location area which is included in the list of "forbidden location areas for GPRS services", the MS shall not initiate any GMM, SM, SMS or SS procedure for GPRS services. If the MS receives a LOCATION UPDATING REJECT message without integrity protection with MM cause value #2, #3, #6, #11, #12, #13 or #15 before the network has activated the integrity protection for the CS domain, the MS shall start timer T3247 with a random value uniformly drawn from the range between 30 minutes and 60 minutes, if the timer is not running, and take the following actions: 1) if the MM cause value received is #3 or #6, and a) if the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services" events and the counter has a value less than an MS implementation-specific maximum value, the MS shall: i) delete any LAI, TMSI and ciphering key sequence number stored in the SIM/USIM, reset the location update attempt counter, and set the update status to ROAMING NOT ALLOWED (and store it in the SIM/USIM according to subclause 4.1.2.2); delete the list of equivalent PLMNs; in Iu mode, increment the counter for "SIM/USIM considered invalid for non-GPRS services" events, if not already incremented over the same RRC connection; in A/Gb mode, increment the counter for "SIM/USIM considered invalid for non-GPRS services" events; store the current LAI in the list of "forbidden location areas for roaming"; and search for a suitable cell in another location area or a tracking area according to 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [121]; or ii) proceed as specified in subclause 4.4.4.7 and; in Iu mode, increment the counter for "SIM/USIM considered invalid for non-GPRS services" events, if not already incremented over the same RRC connection; in A/Gb mode, increment the counter for "SIM/USIM considered invalid for non-GPRS services" events; and b) else the MS shall proceed as specified in subclause 4.4.4.7; 2) if the MM cause value received is #2, and a) if the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services" events and the counter has a value less than an MS implementation-specific maximum value, the MS shall: i) delete any LAI, TMSI and ciphering key sequence number stored in the SIM/USIM, reset the location update attempt counter, and set the update status to ROAMING NOT ALLOWED (and store it in the SIM/USIM according to subclause 4.1.2.2); delete the list of equivalent PLMNs; in Iu mode, increment the counter for "SIM/USIM considered invalid for non-GPRS services" events, if not already incremented over the same RRC connection; in A/Gb mode, increment the counter for "SIM/USIM considered invalid for non-GPRS services" events; if the MS maintains a list of "forbidden location areas for non-GPRS services" and a list of "forbidden location areas for GPRS services", proceed as follows: if the current LAI is already included in the list of "forbidden location areas for GPRS services" or the MS is not operating in MS operation mode A or B, store the current LAI in the list of "forbidden location areas for roaming"; otherwise store the current LAI in the list of "forbidden location areas for non-GPRS services"; and attempt to select a suitable cell according to 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [121], different from the cell where the LOCATION UPDATING REJECT was received; or NOTE 2: The cell on which the reject was received could still be a suitable cell. ii) proceed as specified in subclause 4.4.4.7 and; in Iu mode, increment the counter for "SIM/USIM considered invalid for non-GPRS services" events, if not already incremented over the same RRC connection; in A/Gb mode, increment the counter for "SIM/USIM considered invalid for non-GPRS services" events; and b) else the MS shall proceed as specified in subclause 4.4.4.7; 3) if the MM cause value received is #12, #13 or #15, the MS shall additionally proceed as specified in subclause 4.4.4.7; 4) if the MM cause value received is #11 and the MS is in its HPLMN or in a PLMN that is within the EHPLMN list (if the EHPLMN list is present): the MS shall delete any LAI, TMSI and ciphering key sequence number stored in the SIM/USIM, reset the location update attempt counter, and set the update status to ROAMING NOT ALLOWED (and store it in the SIM/USIM according to subclause 4.1.2.2). Additionally, the MS shall store the current LAI in the list of "forbidden location areas for roaming"; and the MS shall search for a suitable cell in another location area or a tracking area according to 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [121]; and 5) if the MM cause value received is #11 and if the MS is not in its HPLMN or in a PLMN that is within the EHPLMN list (if the EHPLMN list is present), in addition to the MS requirements specified in subclause 4.4.4.7, - if the MS maintains a list of PLMN-specific attempt counters and the PLMN-specific attempt counter for the PLMN sending the reject message has a value less than an MS implementation-specific maximum value, the MS shall increment the PLMN-specific attempt counter for the PLMN. If the MS receives a CM SERVICE REJECT or ABORT message with MM cause value #6 without integrity protection before the network has activated the integrity protection for the CS domain, the MS shall start timer T3247 with a random value uniformly drawn from the range between 30 minutes and 60 minutes, if the timer is not running, and a) if the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services" events and the counter has a value less than an MS implementation-specific maximum value, the MS shall: i) proceed as specified in subclauses 4.5.1.1 or 4.3.5.2 respectively with the exception that the MS shall not consider the SIM/USIM as invalid for non-GPRS services and; delete the list of equivalent PLMNs; in Iu mode, increment the counter for "SIM/USIM considered invalid for non-GPRS services" events, if not already incremented over the same RRC connection; in A/Gb mode, increment the counter for "SIM/USIM considered invalid for non-GPRS services" events; reset the location update attempt counter; store the current LAI in the list of "forbidden location areas for roaming"; and search for a suitable cell in another location area or a tracking area according to 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [121]; or ii) proceed as specified in subclauses 4.5.1.1 or 4.3.5.2 respectively and; in Iu mode, increment the counter for "SIM/USIM considered invalid for non-GPRS services" events, if not already incremented over the same RRC connection; in A/Gb mode, increment the counter for "SIM/USIM considered invalid for non-GPRS services" events; and b) else the MS shall proceed as specified in subclause 4.5.1.1 or 4.3.5.2 respectively. If the MS receives an ATTACH REJECT or ROUTING AREA UPDATE REJECT message without integrity protection with GMM cause value #3, #6, #7, #8, #11, #12, #13, #14 or #15 before the network has activated the integrity protection for the PS domain, the MS shall start timer T3247 with a random value uniformly drawn from the range between 30 minutes and 60 minutes, if the timer is not running, and shall take the following actions: 6) if the GMM cause value received is #3, #6, or #8, and a) if the MS maintains a counter for "SIM/USIM considered invalid for GPRS services" events and the counter has a value less than an MS implementation-specific maximum value, the MS shall: i) set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) and shall delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number; delete the list of equivalent PLMNs; increment the counter for "SIM/USIM considered invalid for GPRS services" events; if the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services" events and the counter has a value less than an MS implementation-specific maximum value, set the update status to U3 ROAMING NOT ALLOWED, delete any TMSI, LAI and ciphering key sequence number. If the MS is operating in MS operation mode A and an RR connection exists, the MS shall abort the RR connection, unless an emergency call is ongoing. In Iu mode, the MS shall increment the counter for "SIM/USIM considered invalid for non-GPRS services" events, if not already incremented over the same RRC connection. In A/Gb mode, the MS shall increment the counter for "SIM/USIM considered invalid for non-GPRS services" events; if a GPRS attach or routing area updating procedure was performed, reset the GPRS attach attempt counter or the routing area updating attempt counter, respectively; if S1 mode is supported by the MS, handle the EMM parameters attach attempt counter or tracking area updating attempt counter, EMM state, EPS update status, GUTI, last visited registered TAI, TAI list and KSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when an EPS attach or tracking area update procedure is rejected with the EMM cause of the same value in a NAS message without integrity protection; store the current LAI in the list of "forbidden location areas for roaming" and enter the state GMM-DEREGISTERED.LIMITED-SERVICE; and search for a suitable cell in another location area or a tracking area according to 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [121]; or ii) proceed as specified in subclauses 4.7.3.1.4, 4.7.3.2.4, 4.7.5.1.4, 4.7.5.2.4 and 4.7.13.4; increment the counter for "SIM/USIM considered invalid for GPRS services" events; and if the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services" events and the counter has a value less than an MS implementation-specific maximum value: in Iu mode, increment the counter for "SIM/USIM considered invalid for non-GPRS services" events, if not already incremented over the same RRC connection in A/Gb mode, increment the counter for "SIM/USIM considered invalid for non-GPRS services" events; and b) else the MS shall proceed as specified in subclause 4.7.3.1.4, 4.7.3.2.4, 4.7.5.1.4, 4.7.5.2.4 and 4.7.13.4; 7) if the GMM cause value received is #7, and a) if the MS maintains a counter for "SIM/USIM considered invalid for GPRS services" events and the counter has a value less than an MS implementation-specific maximum value, the MS shall: i) set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) and shall delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number; delete the list of equivalent PLMNs; increment the counter for "SIM/USIM considered invalid for GPRS services" events; - if a GPRS attach or routing area updating procedure was performed, reset the GPRS attach attempt counter or the routing area updating attempt counter, respectively; if S1 mode is supported by the MS, handle the EMM parameters attach attempt counter or tracking area updating attempt counter, EMM state, EPS update status, GUTI, last visited registered TAI, TAI list and KSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when an EPS attach or tracking area update procedure is rejected with the EMM cause of the same value in a NAS message without integrity protection; enter the state GMM-DEREGISTERED.LIMITED-SERVICE; if the MS maintains a list of "forbidden location areas for non-GPRS services" and a list of "forbidden location areas for GPRS services", proceed as follows: if the current LAI is already included in the list of "forbidden location areas for non-GPRS services" or the MS is operating in MS operation mode C, store the current LAI in the list of "forbidden location areas for roaming"; otherwise store the current LAI in the list of "forbidden location areas for GPRS services"; and attempt to select a suitable cell according to 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [121], different from the cell where the ATTACH REJECT or ROUTING AREA UPDATING REJECT was received; or NOTE 3: The cell on which the reject was received could still be a suitable cell. ii) proceed as specified in subclauses 4.7.3.1.4, 4.7.3.2.4, 4.7.5.1.4, 4.7.5.2.4 and 4.7.13.4; and increment the counter for "SIM/USIM considered invalid for GPRS services" events; and b) else the MS shall proceed as specified in subclause 4.7.3.1.4, 4.7.3.2.4, 4.7.5.1.4, 4.7.5.2.4 and 4.7.13.4; 8) if the GMM cause value received is #12, #13 or #15, the MS shall additionally proceed as specified in subclauses 4.7.3.1.4, 4.7.3.2.4, 4.7.5.1.4, 4.7.5.2.4 and 4.7.13.4; 9) if the GMM cause value received is #11 or #14 and the MS is in its HPLMN or in a PLMN that is within the EHPLMN list (if the EHPLMN list is present): - the MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) and shall delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number. The MS shall delete the list of equivalent PLMNs. Additionally, if a GPRS attach or the routing area updating procedure was performed, the MS shall reset the GPRS attach attempt counter or the routing area updating attempt counter respectively; - for GMM cause value #11, the MS shall store the current LAI in the list of "forbidden location areas for roaming", and enter the state GMM-DEREGISTERED.LIMITED-SERVICE; - for GMM cause value #14, the MS shall enter the state GMM-DEREGISTERED.LIMITED-SERVICE. If the MS maintains a list of "forbidden location areas for non-GPRS services" and a list of "forbidden location areas for GPRS services", proceed as follows: if the current LAI is already included in the list of "forbidden location areas for non-GPRS services" or the MS is operating in MS operation mode C, store the current LAI in the list of "forbidden location areas for roaming"; otherwise store the current LAI in the list of "forbidden location areas for GPRS services"; - if S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list, KSI and attach attempt counter or tracking area updating attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the procedure is rejected with the EMM cause with the same value without integrity protection; and - the MS shall search for a suitable cell in another location area or in another tracking area according to 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [121]. 10) if the GMM cause value received is #11 and the MS is not in its HPLMN or in a PLMN that is within the EHPLMN list (if the EHPLMN list is present), the MS shall additionally proceed as specified in subclauses 4.7.3.1.4, 4.7.3.2.4, 4.7.5.1.4, 4.7.5.2.4 and 4.7.13.4: - Furthermore, if the MS maintains a list of PLMN-specific attempt counters and the PLMN-specific attempt counter for the PLMN sending the reject message has a value less than an MS implementation-specific maximum value, the MS shall increment the PLMN-specific attempt counter for the PLMN. 11) if the GMM cause value received is #14 and the MS is not in its HPLMN or in a PLMN that is within the EHPLMN list (if the EHPLMN list is present), the MS shall additionally proceed as specified in subclauses 4.7.3.1.4, 4.7.3.2.4, 4.7.5.1.4, and 4.7.5.2.4: - Furthermore, if the MS maintains a list of PLMN-specific PS-attempt counters and the PLMN-specific PS-attempt counter for the PLMN sending the reject message has a value less than an MS implementation-specific maximum value, the MS shall increment the PLMN-specific PS-attempt counter for the PLMN. - If the MS maintains a list of "forbidden location areas for non-GPRS services" and a list of "forbidden location areas for GPRS services", proceed as follows: if the current LAI is already included in the list of "forbidden location areas for non-GPRS services" or the MS is operating in MS operation mode C, store the current LAI in the list of "forbidden location areas for roaming"; otherwise store the current LAI in the list of "forbidden location areas for GPRS services" and the MS shall enter the state GMM-DEREGISTERED.LIMITED-SERVICE. If the MS receives a SERVICE REJECT message without integrity protection with GMM cause value #3, #6, #7, #8, #11, #12, #13 or #15 before the network has activated the integrity protection for the PS domain, the MS shall start timer T3247 with a random value uniformly drawn from the range between 30 minutes and 60 minutes, if the timer is not running, and proceed as specified under items 6, 7, 8, 9 and 10 above. Upon expiry of timer T3247, the MS shall: - erase the list of "forbidden location areas for regional provision of service" and the list of "forbidden location areas for roaming"; - set the SIM/USIM to valid for non-GPRS services, if - the MS does not maintain a counter for "SIM/USIM considered invalid for non-GPRS services" events; or - the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services" events and this counter has a value less than an MS implementation-specific maximum value. - set the SIM/USIM to valid for GPRS services, if - the MS does not maintain a counter for "SIM/USIM considered invalid for GPRS services" events; or - the MS maintains a counter for "SIM/USIM considered invalid for GPRS services" events and this counter has a value less than an MS implementation-specific maximum value. - erase the list of "forbidden location areas for non-GPRS services" and the list of "forbidden location areas for GPRS services", if the MS maintains these lists; - if the MS maintains a list of PLMN-specific attempt counters, for each PLMN-specific attempt counter that has a value greater than zero and less than an MS implementation-specific maximum value, remove the respective PLMN from the extension of the "forbidden PLMNs" list; - if the MS maintains a list of PLMN-specific PS-attempt counters, for each PLMN-specific PS-attempt counter that has a value greater than zero and less than an MS implementation-specific maximum value, remove the respective PLMN from the "forbidden PLMNs for GPRS service" list. If the resulting "forbidden PLMNs for GPRS service" list is empty and the MS is supporting S1 mode, the MS re-enables the E-UTRA capability as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when timer T3247 expires; - if the MS is supporting S1 mode, perform the actions as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when timer T3247 expires; - if the MS is supporting N1 mode, perform the actions as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [167] for the case when timer T3247 expires; and - initiate a location updating procedure, GPRS attach procedure or routing area updating procedure, if still needed, dependent on MM state and update status, and GMM state and GPRS update status, or perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. If the MS maintains a list of PLMN-specific attempt counters and PLMN-specific PS-attempt counters, when the MS is switched off, the MS shall, for each PLMN-specific attempt counter that has a value greater than zero and less than the MS implementation-specific maximum value, remove the respective PLMN from the forbidden PLMN list. When the SIM/USIM is removed, the MS should perform this action. NOTE 4: If the respective PLMN was stored in the extension of the "forbidden PLMNs" list, then according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14] the MS will delete the contents of this extension when the MS is switched off or the SIM/USIM is removed. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.1.1.6A |
6,391 | 6.2.11 Multi-homed IPv6 PDU session | The UE supporting IPv6 may support multi-homed IPv6 PDU session. If the UE supports the multi-homed IPv6 PDU session: a) the UE shall support acting as a type C host as specified in IETF RFC 4191 [36]; and b) the UE indicates support of the multi-homed IPv6 PDU session: 1) during the UE-requested PDU session establishment of a PDU session of "IPv6" or "IPv4v6" PDU session type; and 2) during the UE-requested PDU session modification performed after an inter-system change from S1 mode to N1 mode, for a PDU session associated with a PDN connection established when in S1 mode, if the UE is a UE operating in single-registration mode in a network supporting N26 interface, the PDU session is of "IPv6" or "IPv4v6" PDU session type, and the UE has not previously successfully performed the UE-requested PDU session modification to provide this indication. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.2.11 |
6,392 | 6.1.4 Coordination between ESM and SM | For inter-system change from S1 mode to A/Gb mode or Iu mode, SM uses the following parameters from each active EPS bearer context: - EPS bearer identity to map to NSAPI; NOTE 1: If the UE and the MME support signalling for a maximum number of 15 EPS bearer contexts, any active EPS bearer contexts using EPS bearer identity 1 to 4 are not mapped but deactivated locally before inter-system change to A/Gb mode or Iu mode. - linked EPS bearer identity (if available) to map to linked TI; - PDN address and APN of the default EPS bearer context to map to PDP address and APN of the default PDP context; - TFT of the default EPS bearer context, if any, to map to the TFT of the default PDP context; - TFTs of the dedicated EPS bearer contexts to map to TFTs of the secondary PDP contexts; and - GERAN/UTRAN parameters as provided by the MME while on E-UTRAN access, i.e. R99 QoS, LLC SAPI, radio priority, packet flow identifier, transaction identifier and BCM (if available). If the MME also provided an Extended EPS QoS IE, then the bit rates signalled with this IE are also applicable to the R99 QoS. NOTE 2: Some networks not supporting mobility from S1 mode to A/Gb mode or Iu mode or both do not provide the UE with the GERAN/UTRAN parameters. However, for this case there is no need for the UE to perform mapping to GERAN/UTRAN parameters (i.e. the PDP contexts cannot be transferred to A/Gb mode or Iu mode). The MME performs the mapping from EPS to R99 QoS parameters according to 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10], annex E. At inter-system change from S1 mode to A/Gb mode, SM shall not activate the PDP context(s) if SM does not have the following parameters from the active EPS bearer context(s): - LLC SAPI; - radio priority; - transaction identifier; and - R99 QoS. At inter-system change from S1 mode to Iu mode, SM shall not activate the PDP context(s) if SM does not have the following parameter from the active EPS bearer context(s): - transaction identifier; and - R99 QoS. For inter-system change from A/Gb mode or Iu mode to S1 mode, ESM uses the following parameters from each active PDP context: - NSAPI to map to EPS bearer identity; - NSAPI of the default PDP context to map to linked EPS bearer identity; - PDP address and APN of the default PDP context to map to PDN address and APN of the default EPS bearer context; - TFT of the default PDP context, if any, to map to the TFT of the default EPS bearer context; and - TFTs of the secondary PDP contexts to map to the TFTs of the dedicated EPS bearer contexts. The MME and the UE perform the mapping from R99 to EPS QoS parameters according to 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10], annex E. In particular the MME derives the APN-AMBR for the corresponding PDN connection from the MBR of the R99 subscribed QoS profile and the UE maps the MBR of its default PDP context to the APN-AMBR of the corresponding PDN connection. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.1.4 |
6,393 | 6.4.1.3 UE-requested PDU session establishment procedure accepted by the network | If the connectivity with the requested DN is accepted by the network, the SMF shall create a PDU SESSION ESTABLISHMENT ACCEPT message. If the UE requests establishing an emergency PDU session, the network shall not check for service area restrictions or subscription restrictions when processing the PDU SESSION ESTABLISHMENT REQUEST message. The SMF shall set the Authorized QoS rules IE of the PDU SESSION ESTABLISHMENT ACCEPT message to the authorized QoS rules of the PDU session and may include the authorized QoS flow descriptions IE of the PDU SESSION ESTABLISHMENT ACCEPT message set to the authorized QoS flow descriptions of the PDU session. NOTE 1: This is applicable also if the PDU session establishment procedure was initiated to perform handover of an existing PDU session between 3GPP access and non-3GPP access, and even if the authorized QoS rules and authorized QoS flow descriptions for source and target access of the handover are the same. The SMF shall ensure that the number of the packet filters used in the authorized QoS rules of the PDU Session does not exceed the maximum number of packet filters supported by the UE for the PDU session. If the received request type is "initial emergency request", the SMF shall set the Authorized QoS flow descriptions IE according to the QoS parameters used for establishing emergency services as specified in subclause 5.16.4 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]. SMF shall set the Authorized QoS flow descriptions IE to the authorized QoS flow descriptions of the PDU session, if: a) the Authorized QoS rules IE contains at least one GBR QoS flow; b) the QFI is not the same as the 5QI of the QoS flow identified by the QFI; c) the QoS flow can be mapped to an EPS bearer as specified in subclause 4.11.1 of 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]; or d) the QoS flow is established for the PDU session used for relaying, as specified in subclause 5.6.2.1 of 3GPP TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [6E]. NOTE 2: In cases other than above listed cases, it is up to the SMF implementation to include the authorized QoS flow description for the QoS flow in the Authorized QoS flow descriptions IE of the PDU SESSION ESTABLISHMENT ACCEPT message. If interworking with EPS is supported for the PDU session, the SMF shall set in the PDU SESSION ESTABLISHMENT ACCEPT message: a) the Mapped EPS bearer contexts IE to the EPS bearer contexts mapped from one or more QoS flows of the PDU session; and b) the EPS bearer identity parameter in the Authorized QoS flow descriptions IE to the EPS bearer identity corresponding to the QoS flow, for each QoS flow which can be transferred to EPS. If the "Create new EPS bearer" operation code in the Mapped EPS bearer contexts IE was received, and there is no corresponding Authorized QoS flow descriptions IE in the PDU SESSION ESTABLISHMENT ACCEPT message, the UE shall send a PDU SESSION MODIFICATION REQUEST message including a Mapped EPS bearer contexts IE to delete the mapped EPS bearer context. If the EPS bearer identity parameter in the Authorized QoS flow descriptions IE was received, the operation code is "Create new QoS flow description" and there is no corresponding Mapped EPS bearer contexts IE in the PDU SESSION ESTABLISHMENT ACCEPT message, the UE shall not diagnose an error, and shall keep storing the association between the QoS flow and the corresponding EPS bearer identity. Furthermore, the SMF shall store the association between the QoS flow and the mapped EPS bearer context, for each QoS flow which can be transferred to EPS. The SMF shall set the selected SSC mode IE of the PDU SESSION ESTABLISHMENT ACCEPT message to: a) the received SSC mode in the SSC mode IE included in the PDU SESSION ESTABLISHMENT REQUEST message based on one or more of the PDU session type, the subscription and the SMF configuration; b) either the default SSC mode for the data network listed in the subscription or the SSC mode associated with the SMF configuration, if the SSC mode IE is not included in the PDU SESSION ESTABLISHMENT REQUEST message. NOTE 3: For bullet b), to avoid issues for UEs not supporting all SSC modes, the network operator can, in the subscription data and local configuration, include at least SSC mode 1 in the allowed SSC modes, and set the default SSC mode to "SSC mode 1" as per 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]. If the PDU session is an emergency PDU session, the SMF shall set the Selected SSC mode IE of the PDU SESSION ESTABLISHMENT ACCEPT message to "SSC mode 1". If the PDU session is a non-emergency PDU session of "Ethernet" or "Unstructured" PDU session type, the SMF shall set the Selected SSC mode IE to "SSC mode 1" or "SSC mode 2". If the PDU session is a non-emergency PDU session of "IPv4", "IPv6" or "IPv4v6" PDU session type, the SMF shall set the selected SSC mode IE to "SSC mode 1", "SSC mode 2", or "SSC mode 3". If the PDU session is a non-emergency PDU session and the UE is not registered for onboarding services in SNPN, the SMF shall set the S-NSSAI IE of the PDU SESSION ESTABLISHMENT ACCEPT message to: a) the S-NSSAI of the PDU session; and b) the mapped S-NSSAI (in roaming scenarios). The S-NSSAI or the mapped S-NSSAI (in roaming scenarios) of the PDU session shall be the alternative S-NSSAI if the SMF has received an alternative S-NSSAI from the AMF. The SMF shall set the Selected PDU session type IE of the PDU SESSION ESTABLISHMENT ACCEPT message to the selected PDU session type, i.e. the PDU session type of the PDU session. If the PDU SESSION ESTABLISHMENT REQUEST message includes a PDU session type IE set to "IPv4v6", the SMF shall select "IPv4", "IPv6" or "IPv4v6" as the Selected PDU session type. If the subscription, the SMF configuration, or both, are limited to IPv4 only or IPv6 only for the DNN selected by the network, the SMF shall include the 5GSM cause value #50 "PDU session type IPv4 only allowed", or #51 "PDU session type IPv6 only allowed", respectively, in the 5GSM cause IE of the PDU SESSION ESTABLISHMENT ACCEPT message. If the selected PDU session type is "IPv4", the SMF shall include the PDU address IE in the PDU SESSION ESTABLISHMENT ACCEPT message and shall set the PDU address IE to an IPv4 address is allocated to the UE in the PDU session. If the selected PDU session type is "IPv6", the SMF shall include the PDU address IE in the PDU SESSION ESTABLISHMENT ACCEPT message and shall set the PDU address IE to an interface identifier for the IPv6 link local address allocated to the UE in the PDU session. If the selected PDU session type is "IPv4v6", the SMF shall include the PDU address IE in the PDU SESSION ESTABLISHMENT ACCEPT message and shall set the PDU address IE to an IPv4 address and an interface identifier for the IPv6 link local address, allocated to the UE in the PDU session. If the selected PDU session type of a PDU session established by the W-AGF acting on behalf of the FN-RG is "IPv4v6" or "IPv6", the SMF shall also indicate the SMF's IPv6 link local address in the PDU address IE of the PDU SESSION ESTABLISHMENT ACCEPT message. If the PDU session is a non-emergency PDU session and the UE is not registered for onboarding services in SNPN, the SMF shall set the DNN IE of the PDU SESSION ESTABLISHMENT ACCEPT message to the DNN determined by the AMF of the PDU session. The SMF shall set the Session-AMBR IE of the PDU SESSION ESTABLISHMENT ACCEPT message to the Session-AMBR of the PDU session. If the selected PDU session type is "IPv4", "IPv6", "IPv4v6" or "Ethernet" and if the PDU SESSION ESTABLISHMENT REQUEST message includes a 5GSM capability IE with the RQoS bit set to "Reflective QoS supported", the SMF shall consider that reflective QoS is supported for QoS flows belonging to this PDU session and may include the RQ timer IE set to an RQ timer value in the PDU SESSION ESTABLISHMENT ACCEPT message. If the selected PDU session type is "IPv4", "IPv6", "IPv4v6" or "Ethernet" and if the PDU SESSION ESTABLISHMENT REQUEST message includes a Maximum number of supported packet filters IE, the SMF shall consider this number as the maximum number of packet filters that can be supported by the UE for this PDU session. Otherwise the SMF considers that the UE supports 16 packet filters for this PDU session. The SMF shall consider that the maximum data rate per UE for user-plane integrity protection supported by the UE for uplink and the maximum data rate per UE for user-plane integrity protection supported by the UE for downlink are valid for the lifetime of the PDU session. If the value of the RQ timer is set to "deactivated" or has a value of zero, the UE considers that RQoS is not applied for this PDU session. NOTE 4: If the 5G core network determines that reflective QoS is to be used for a QoS flow, the SMF sends reflective QoS indication (RQI) to UPF to activate reflective QoS. If the QoS flow is established over 3GPP access, the SMF also includes reflective QoS Attribute (RQA) in QoS profile of the QoS flow during QoS flow establishment. If the selected PDU session type is "IPv6" or "IPv4v6" and if the PDU SESSION ESTABLISHMENT REQUEST message includes a 5GSM capability IE with the MH6-PDU bit set to "Multi-homed IPv6 PDU session supported", the SMF shall consider that this PDU session is supported to use multiple IPv6 prefixes. If the selected PDU session type is "Ethernet", the PDU SESSION ESTABLISHMENT REQUEST message includes a 5GSM capability IE with the EPT-S1 bit set to "Ethernet PDN type in S1 mode supported" and the network supports Ethernet PDN type in S1 mode, the SMF shall set the EPT-S1 bit of the 5GSM network feature support IE of the PDU SESSION ESTABLISHMENT ACCEPT message to "Ethernet PDN type in S1 mode supported". If the AMF has indicated to the SMF that the UE supports the non-3GPP access path switching and the SMF supports the non-3GPP access path switching, the SMF shall set the NAPS bit of the 5GSM network feature support IE of the PDU SESSION ESTABLISHMENT ACCEPT message to "non-3GPP access path switching supported". If the DN authentication of the UE was performed and completed successfully, the SMF shall set the EAP message IE of the PDU SESSION ESTABLISHMENT ACCEPT message to an EAP-success message as specified in IETF RFC 3748 [34], provided by the DN. Based on local policies or configurations in the SMF and the Always-on PDU session requested IE in the PDU SESSION ESTABLISHMENT REQUEST message (if available), if the SMF determines that either: a) the requested PDU session needs to be established as an always-on PDU session (e.g. because the PDU session is for time synchronization or TSC, for URLLC, or for both), the SMF shall include the Always-on PDU session indication IE in the PDU SESSION ESTABLISHMENT ACCEPT message and shall set the value to "Always-on PDU session required"; or b) the requested PDU session shall not be established as an always-on PDU session and: i) if the UE included the Always-on PDU session requested IE, the SMF shall include the Always-on PDU session indication IE in the PDU SESSION ESTABLISHMENT ACCEPT message and shall set the value to "Always-on PDU session not allowed"; or ii) if the UE did not include the Always-on PDU session requested IE, the SMF shall not include the Always-on PDU session indication IE in the PDU SESSION ESTABLISHMENT ACCEPT message. If the PDU session is an MA PDU session, the SMF shall include the ATSSS container IE in the PDU SESSION ESTABLISHMENT ACCEPT message. The SMF shall set the content of the ATSSS container IE as specified in 3GPP TS 24.193[ 5G System;Access Traffic Steering, Switching and Splitting (ATSSS); Stage 3 ] [13B]. If the UE requests to establish user plane resources over the second access of an MA PDU session which has already been established over the first access and the parameters associated with ATSSS previously provided to the UE are not to be updated, the "ATSSS container contents" shall not be included in the ATSSS container IE in the PDU SESSION ESTABLISHMENT ACCEPT message. If the PDU session is a single access PDU session containing the MA PDU session information IE with the value set to "MA PDU session network upgrade is allowed" and: a) if the SMF decides to establish a single access PDU session, the SMF shall not include the ATSSS container IE in the PDU SESSION ESTABLISHMENT ACCEPT message; or b) if the SMF decides to establish an MA PDU session, the SMF shall include the ATSSS container IE in the PDU SESSION ESTABLISHMENT ACCEPT message, which indicates to the UE that the requested single access PDU session was established as an MA PDU Session. If the network decides that the PDU session is only for control plane CIoT 5GS optimization, the SMF shall include the control plane only indication in the PDU SESSION ESTABLISHMENT ACCEPT message. If: a) the UE provided the IP header compression configuration IE in the PDU SESSION ESTABLISHMENT REQUEST message; and b) the SMF supports IP header compression for control plane CIoT 5GS optimization; the SMF shall include the IP header compression configuration IE in the PDU SESSION ESTABLISHMENT ACCEPT message. If: a) the UE provided the Ethernet header compression configuration IE in the PDU SESSION ESTABLISHMENT REQUEST message; and b) the SMF supports Ethernet header compression for control plane CIoT 5GS optimization; the SMF shall include the Ethernet header compression configuration IE in the PDU SESSION ESTABLISHMENT ACCEPT message. If the PDU SESSION ESTABLISHMENT REQUEST included the Requested MBS container IE with the MBS operation set to "Join MBS session", the SMF: a) shall include the TMGI for the multicast MBS session IDs that the UE is allowed to join, if any, in the Received MBS container IE, shall set the MBS decision to "MBS join is accepted" for each of those Received MBS information, may include the MBS start time to indicate the time when the multicast MBS session starts and shall include the MBS security container in each of those Received MBS information if security protection is applied for that multicast MBS session and the control plane security procedure is used as specified in annex W.4.1.2 in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24], and shall use separate QoS flows dedicated for multicast by including the Authorized QoS flow descriptions IE if no separate QoS flows dedicated for multicast exist or if the SMF wants to establish new QoS flows dedicated for multicast; NOTE 5: The network determines whether security protection applies or not for the multicast MBS session as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. b) shall include the TMGI for multicast MBS session IDs that the UE is not allowed to join, if any, in the Received MBS container IE, shall set the MBS decision to "MBS join is rejected" for each of those Received MBS information, shall set the Rejection cause for each of those Received MBS information with the reason of rejection, and if the Rejection cause is set to "multicast MBS session has not started or will not start soon", may include an MBS back-off timer value; and c) may include in the Received MBS container IE the MBS service area for each multicast MBS session and include in it the MBS TAI list, the NR CGI list or both, that identify the service area(s) for the local MBS service NOTE 6: For an multicast MBS session that has multiple MBS service areas, the MBS service areas are indicated to the UE using MBS service announcement as described in 3GPP TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [53], which is out of scope of this specification. in the PDU SESSION ESTABLISHMENT ACCEPT message. If the UE has set the Type of multicast MBS session ID to "Source specific IP multicast address" in the Requested multicast MBS container IE for certain MBS session(s) in the PDU SESSION ESTABLISHMENT REQUEST message, the SMF shall include the Source IP address information and Destination IP address information in the Received MBS information together with the TMGI for each of those multicast MBS sessions. NOTE 7: Including the Source IP address information and Destination IP address information in the Received MBS information in that case is to allow the UE to perform the mapping between the requested multicast MBS session ID and the provided TMGI. NOTE 8: In SNPN, TMGI is used together with NID to identify an MBS Session. If the request type is "existing PDU session", the SMF shall not perform network slice admission control for the PDU session, except for the following cases: a) when EPS counting is not required for the S-NSSAI of the PDU session for network slice admission control and the PDU session is established due to transfer the PDN connection from S1 mode to N1 mode in case of inter-system change; or b) handover of an existing PDU session between 3GPP access and non-3GPP access is performed. The SMF shall send the PDU SESSION ESTABLISHMENT ACCEPT message. Upon receipt of a PDU SESSION ESTABLISHMENT ACCEPT message and a PDU session ID, using the NAS transport procedure as specified in subclause 5.4.5, the UE shall stop timer T3580, shall release the allocated PTI value and shall consider that the PDU session was established. If the PDU session establishment procedure was initiated to perform handover of an existing PDU session between 3GPP access and non-3GPP access, then upon receipt of the PDU SESSION ESTABLISHMENT ACCEPT message the UE shall locally delete any authorized QoS rules, authorized QoS flow descriptions, the session-AMBR and the parameters provided in the Protocol configuration options IE when in S1 mode or the Extended protocol configuration options IE stored for the PDU session before processing the new received authorized QoS rules, authorized QoS flow descriptions, the session-AMBR and the parameters provided in the Extended protocol configuration options IE, if any. NOTE 9: For the case of handover from 3GPP access to non-3GPP access, deletion of the QoS flow descriptions implies deletion of the associated EPS bearer identities, if any, and according to subclause 6.1.4.1 also deletion of the associated EPS bearer contexts. Regarding the reverse direction, for PDU sessions via non-3GPP access the network does not allocate associated EPS bearer identities (see 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9], subclause 4.11.1.4.1). If the PDU session establishment procedure was initiated to perform handover of an existing PDU session from 3GPP access to non-3GPP access and that existing PDU session is associated with one or more multicast MBS sessions, the UE shall locally leave the associated multicast MBS sessions and the SMF shall consider the UE as removed from the associated multicast MBS sessions. For an MA PDU session already established on a single access, except for all those MA PDU sessions with a PDN connection established as a user-plane resource, upon receipt of PDU SESSION ESTABLISHMENT ACCEPT message over the other access: a) the UE shall delete the stored authorized QoS rules and the stored session-AMBR; b) if the authorized QoS flow descriptions IE is included in the PDU SESSION ESTABLISHMENT ACCEPT message, the UE shall delete the stored authorized QoS flow descriptions; and c) if the mapped EPS bearer contexts IE is included in the PDU SESSION ESTABLISHMENT ACCEPT message, the UE shall delete the stored mapped EPS bearer contexts. If the UE supports network slice usage control and: a) a PDU session is successfully established for the on-demand S-NSSAI, the UE shall stop and reset the slice deregistration inactivity timer for the on-demand S-NSSAI over corresponding access type, if running; and b) an MA PDU session is successfully established for the on-demand S-NSSAI, the UE shall stop and reset the slice deregistration inactivity timer for the on-demand S-NSSAI over both 3GPP access and non-3GPP access, if running. The UE shall store the authorized QoS rules, and the session-AMBR received in the PDU SESSION ESTABLISHMENT ACCEPT message for the PDU session. The UE shall also store the authorized QoS flow descriptions if it is included in the Authorized QoS flow descriptions IE of the PDU SESSION ESTABLISHMENT ACCEPT message for the PDU session. If the number of the authorized QoS rules, the number of the packet filters, or the number of the authorized QoS flow descriptions associated with the PDU session have reached the maximum number supported by the UE upon receipt of a PDU SESSION ESTABLISHMENT ACCEPT message, then the UE may initiate the PDU session release procedure by sending a PDU SESSION RELEASE REQUEST message with 5GSM cause #26 "insufficient resources". For a PDU session that is being established with the request type set to "initial request", "initial emergency request" or "MA PDU request", or a PDU session that is being transferred from EPS to 5GS and established with the request type set to "existing PDU session" or "existing emergency PDU session" or a PDU session that is being handed over between non-3GPP access and 3GPP access and established with the request type set to "existing PDU session" or "existing emergency PDU session ", the UE shall verify the authorized QoS rules and the authorized QoS flow descriptions provided in the PDU SESSION ESTABLISHMENT ACCEPT message for different types of errors as follows: a) Semantic errors in QoS operations: 1) When the rule operation is "Create new QoS rule", and the DQR bit is set to "the QoS rule is the default QoS rule" when there's already a default QoS rule. 2) When the rule operation is "Create new QoS rule", and there is no rule with the DQR bit set to "the QoS rule is the default QoS rule". 3) When the rule operation is "Create new QoS rule" and two or more QoS rules associated with this PDU session would have identical precedence values. 4) When the rule operation is an operation other than "Create new QoS rule". 5) When the rule operation is "Create new QoS rule", the DQR bit is set to "the QoS rule is not the default QoS rule", and the UE is in NB-N1 mode. 6) When the rule operation is "Create new QoS rule" and there is already an existing QoS rule with the same QoS rule identifier. 7) When the rule operation is "Create new QoS rule", the DQR bit is set to "the QoS rule is not the default QoS rule", and the PDU session type of the PDU session is "Unstructured". 8) When the flow description operation is an operation other than "Create new QoS flow description". 8a) When the flow description operation is "Create new QoS flow description" and there is already an existing QoS flow description with the same QoS flow identifier. 9) When the flow description operation is "Create new QoS flow description", the QFI associated with the QoS flow description is not the same as the QFI of the default QoS rule and the UE is NB-N1 mode. 10) When the flow description operation is "Create new QoS flow description", the QFI associated with the QoS flow description is not the same as the QFI of the default QoS rule, and the PDU session type of the PDU session is "Unstructured". 11) When the rule operation is "Create new QoS rule" and the DQR bit is set to "the QoS rule is not the default QoS rule" and one match-all packet filter is to be associated with the QoS rule. In case 4, case 5, or case 7 if the rule operation is for a non-default QoS rule, the UE shall send a PDU SESSION MODIFICATION REQUEST message to delete the QoS rule with 5GSM cause #83 "semantic error in the QoS operation". In case 6, if the existing QoS rule is not the default QoS rule and the DQR bit of the new QoS rule is set to "the QoS rule is not the default QoS rule", the UE shall not diagnose an error, further process the create request and, if it was processed successfully, delete the old QoS rule (i.e. the QoS rule that existed when case 6 was detected). If the existing QoS rule is the default QoS rule or the DQR bit of the new QoS rule is set to "the QoS rule is the default QoS rule", the UE shall initiate a PDU session release procedure by sending a PDU SESSION RELEASE REQUEST message with 5GSM cause #83 "semantic error in the QoS operation". In case 8, case 9, or case 10, the UE shall send a PDU SESSION MODIFICATION REQUEST message to delete the QoS flow description with 5GSM cause #83 "semantic error in the QoS operation". In case 8a, the UE shall not diagnose an error, further process the create request and, if it was processed successfully, delete the old QoS flow description (i.e. the QoS flow description that existed when case 8a was detected). Otherwise for all the cases above, the UE shall initiate a PDU session release procedure by sending a PDU SESSION RELEASE REQUEST message with 5GSM cause #83 "semantic error in the QoS operation". b) Syntactical errors in QoS operations: 1) When the rule operation is "Create new QoS rule", the QoS rule is a QoS rule of a PDU session of IPv4, IPv6, IPv4v6 or Ethernet PDU session type, and the packet filter list in the QoS rule is empty. 2) When the rule operation is "Create new QoS rule", the DQR bit is set to "the QoS rule is the default QoS rule", the PDU session type of the PDU session is "Unstructured", and the packet filter list in the QoS rule is not empty. 3) When there are other types of syntactical errors in the coding of the Authorized QoS rules IE or the Authorized QoS flow descriptions IE, such as: a mismatch between the number of packet filters subfield and the number of packet filters in the packet filter list when the rule operation is create new QoS rule", or the number of packet filters subfield is larger than the maximum possible number of packet filters in the packet filter list (i.e., there is no QoS rule precedence subfield included in the QoS rule IE), the QoS Rule Identifier is set to "no QoS rule identifier assigned", or the QoS flow identifier is set to "no QoS flow identifier assigned". 4) When, the rule operation is "Create new QoS rule", there is no QoS flow description with a QFI corresponding to the QFI of the resulting QoS rule and the UE determines, by using the QoS rule’s QFI as the 5QI, that there is a resulting QoS rule for a GBR QoS flow (as described in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] table 5.7.4-1). 5) When the flow description operation is "Create new QoS flow description", and the UE determines that there is a QoS flow description of a GBR QoS flow (as described in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] table 5.7.4-1) which lacks at least one of the mandatory parameters (i.e., GFBR uplink, GFBR downlink, MFBR uplink and MFBR downlink). If the QoS flow description does not include a 5QI, the UE determines this by using the QFI as the 5QI. In case 1, case 3 or case 4, if the QoS rule is the default QoS rule, the UE shall initiate a PDU session release procedure by sending a PDU SESSION RELEASE REQUEST message with 5GSM cause #84 "syntactical error in the QoS operation". Otherwise, the UE shall send a PDU SESSION MODIFICATION REQUEST message including a requested QoS rule IE, a requested QoS flow description IE or both to delete the QoS rule, the QoS flow description or both with 5GSM cause #84 "syntactical error in the QoS operation". In case 2, if the QoS rule is the default QoS rule, the UE shall send a PDU SESSION MODIFICATION REQUEST message including a requested QoS rule IE to delete all the packet filters of the default QoS rule. The UE shall include the 5GSM cause #84 "syntactical error in the QoS operation". In case 5, if the default QoS rule is associated with the QoS flow description which lacks at least one of the mandatory parameters, the UE shall initiate a PDU session release procedure by sending a PDU SESSION RELEASE REQUEST message with 5GSM cause #84 "syntactical error in the QoS operation". Otherwise, the UE shall send a PDU SESSION MODIFICATION REQUEST message to delete the QoS flow description which lacks at least one of the mandatory parameters and the associated QoS rule(s), if any, with 5GSM cause #84 "syntactical error in the QoS operation". NOTE 10: It is not considered an error if the UE determines that after processing all QoS operations on QoS rules and QoS flow descriptions there is a QoS flow description that is not associated with any QoS rule and the UE is not in NB-N1 mode. c) Semantic errors in packet filters: 1) When a packet filter consists of conflicting packet filter components which would render the packet filter ineffective, i.e. no IP packet will ever fit this packet filter. How the UE determines a semantic error in a packet filter is outside the scope of the present document. If the QoS rule is the default QoS rule, the UE shall initiate a PDU session release procedure by sending a PDU SESSION RELEASE REQUEST message with 5GSM cause #44 "semantic error in packet filter(s)". Otherwise, the UE shall send a PDU SESSION MODIFICATION REQUEST message to delete the QoS rule with 5GSM cause #44 "semantic error in packet filter(s)". d) Syntactical errors in packet filters: 1) When the rule operation is "Create new QoS rule" and two or more packet filters in the resultant QoS rule would have identical packet filter identifiers. 2) When there are other types of syntactical errors in the coding of packet filters, such as the use of a reserved value for a packet filter component identifier. If the QoS rule is the default QoS rule, the UE shall initiate a PDU session release procedure by sending a PDU SESSION RELEASE REQUEST message with 5GSM cause #45 "syntactical errors in packet filter(s)". Otherwise, the UE shall send a PDU SESSION MODIFICATION REQUEST message to delete the QoS rule with 5GSM cause #45 "syntactical errors in packet filter(s)". If the Always-on PDU session indication IE is included in the PDU SESSION ESTABLISHMENT ACCEPT message and: a) the value of the IE is set to "Always-on PDU session required", the UE shall consider the established PDU session as an always-on PDU session; or b) the value of the IE is set to "Always-on PDU session not allowed", the UE shall not consider the established PDU session as an always-on PDU session. The UE shall not consider the established PDU session as an always-on PDU session if the UE does not receive the Always-on PDU session indication IE in the PDU SESSION ESTABLISHMENT ACCEPT message. The UE shall store the mapped EPS bearer contexts, if received in the PDU SESSION ESTABLISHMENT ACCEPT message. Furthermore, the UE shall also store the association between the QoS flow and the mapped EPS bearer context, for each QoS flow which can be transferred to EPS, based on the received EPS bearer identity parameter in Authorized QoS flow descriptions IE and the mapped EPS bearer contexts. The UE shall check each mapped EPS bearer context for different types of errors as follows: NOTE 11: An error detected in a mapped EPS bearer context does not cause the UE to discard the Authorized QoS rules IE and Authorized QoS flow descriptions IE included in the PDU SESSION ESTABLISHMENT ACCEPT, if any. a) Semantic error in the mapped EPS bearer operation: 1) When the operation code is an operation code other than "Create new EPS bearer". 2) When the operation code is "Create new EPS bearer" and there is already an existing mapped EPS bearer context with the same EPS bearer identity associated with any PDU session. 3) When the operation code is "Create new EPS bearer" and the resulting mapped EPS bearer context has invalid mandatory parameters or missing mandatory parameters (e.g., mapped EPS QoS parameters or traffic flow template for a dedicated EPS bearer context). In case 2, if the existing mapped EPS bearer context is associated with the PDU session that is being established, the UE shall not diagnose an error, further process the create request and, if it was process successfully, delete the old EPS bearer context. Otherwise, the UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #85 "Invalid mapped EPS bearer identity". b) if the mapped EPS bearer context includes a traffic flow template, the UE shall check the traffic flow template for different types of TFT IE errors as follows: 1) Semantic errors in TFT operations: i) When the TFT operation is an operation other than "Create new TFT" The UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #41 "semantic error in the TFT operation". 2) Syntactical errors in TFT operations: i) When the TFT operation = "Create new TFT" and the packet filter list in the TFT IE is empty. ii) When there are other types of syntactical errors in the coding of the TFT IE, such as a mismatch between the number of packet filters subfield, and the number of packet filters in the packet filter list. The UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message with to delete the mapped EPS bearer context 5GSM cause #42 "syntactical error in the TFT operation". 3) Semantic errors in packet filters: i) When a packet filter consists of conflicting packet filter components which would render the packet filter ineffective, i.e. no IP packet will ever fit this packet filter. How the UE determines a semantic error in a packet filter is outside the scope of the present document. ii) When the resulting TFT, which is assigned to a dedicated EPS bearer context, does not contain any packet filter which applicable for the uplink direction. The UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #44 "semantic errors in packet filter(s)". 4) Syntactical errors in packet filters: i) When the TFT operation = "Create new TFT" and two or more packet filters in the resultant TFT would have identical packet filter identifiers. ii) When the TFT operation = "Create new TFT" and two or more packet filters in all TFTs associated with this PDN connection would have identical packet filter precedence values. iii) When there are other types of syntactical errors in the coding of packet filters, such as the use of a reserved value for a packet filter component identifier. In case ii, if the old packet filters do not belong to the default EPS bearer context, the UE shall not diagnose an error and shall delete the old packet filters which have identical filter precedence values. In case ii, if one or more old packet filters belong to the default EPS bearer context, the UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #45 "syntactical errors in packet filter(s)". In cases i and iii the UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #45 "syntactical error in packet filter(s)". If the UE detects different errors in the mapped EPS bearer contexts, QoS rules or QoS flow descriptions, the UE may send a single PDU SESSION MODIFICATION REQUEST message to delete the erroneous mapped EPS bearer contexts, QoS rules or QoS flow descriptions. In that case, the UE shall include a single 5GSM cause in the PDU SESSION MODIFICATION REQUEST message. NOTE 12: The 5GSM cause to use cannot be different from: #41 "semantic error in the TFT operation", #42 "syntactical error in the TFT operation", #44 "semantic error in packet filter(s)", #45 "syntactical errors in packet filter(s)", #83 "semantic error in the QoS operation", #84 "syntactical error in the QoS operation", and #85 "Invalid mapped EPS bearer identity". The selection of a 5GSM cause is up to the UE implementation. If there are mapped EPS bearer context(s) associated with a PDU session, but none of them is associated with the default QoS rule, the UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context(s) with 5GSM cause #85 "Invalid mapped EPS bearer identity" and shall locally delete the stored EPS bearer identity (EBI) in all the QoS flow descriptions of the PDU session, if any. The UE shall only use the Control plane CIoT 5GS optimization for this PDU session if the Control plane only indication is included in the PDU SESSION ESTABLISHMENT ACCEPT message. If the UE requests the PDU session type "IPv4v6" and: a) the UE receives the selected PDU session type set to "IPv4" and does not receive the 5GSM cause value #50 "PDU session type IPv4 only allowed"; or b) the UE receives the selected PDU session type set to "IPv6" and does not receive the 5GSM cause value #51 "PDU session type IPv6 only allowed"; the UE may subsequently request another PDU session for the other IP version using the UE-requested PDU session establishment procedure to the same DNN (or no DNN, if no DNN was indicated by the UE) and the same S-NSSAI associated with (in roaming scenarios) a mapped S-NSSAI (or no S-NSSAI, if no S-NSSAI was indicated by the UE) with a single address PDN type (IPv4 or IPv6) other than the one already activated. If the UE requests the PDU session type "IPv4v6", receives the selected PDU session type set to "IPv4" and the 5GSM cause value #50 "PDU session type IPv4 only allowed", the UE shall not subsequently request another PDU session using the UE-requested PDU session establishment procedure to the same DNN (or no DNN, if no DNN was indicated by the UE) and the same S-NSSAI associated with (in roaming scenarios) a mapped S-NSSAI (or no S-NSSAI, if no S-NSSAI was indicated by the UE) to obtain a PDU session type different from the one allowed by the network until any of the following conditions is fulfilled: a) the UE is registered to a new PLMN; b) the UE is switched off; c) the USIM is removed; d) the entry in the "list of subscriber data" for the current SNPN is updated if the UE does not support access to an SNPN using credentials from a credentials holder and equivalent SNPNs; or e) the selected entry of the "list of subscriber data" is updated or USIM is removed for the selected PLMN subscription, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both. If the UE requests the PDU session type "IPv4v6", receives the selected PDU session type set to "IPv6" and the 5GSM cause value #51 "PDU session type IPv6 only allowed", the UE shall not subsequently request another PDU session using the UE-requested PDU session establishment procedure to the same DNN (or no DNN, if no DNN was indicated by the UE) and the same S-NSSAI associated with (in roaming scenarios) a mapped S-NSSAI (or no S-NSSAI, if no S-NSSAI was indicated by the UE) to obtain a PDU session type different from the one allowed by the network until any of the following conditions is fulfilled: a) the UE is registered to a new PLMN; b) the UE is switched off; c) the USIM is removed d) the entry in the "list of subscriber data" for the current SNPN is updated if the UE does not support access to an SNPN using credentials from a credentials holder and equivalent SNPNs; or e) the selected entry of the "list of subscriber data" is updated or USIM is removed for the selected PLMN subscription, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both. NOTE 13: For the 5GSM cause values #50 "PDU session type IPv4 only allowed", and #51 "PDU session type IPv6 only allowed", re-attempt in S1 mode for the same DNN (or no DNN, if no DNN was indicated by the UE) is only allowed using the PDU session type(s) indicated by the network. If the selected PDU session type of the PDU session is "Unstructured" or "Ethernet", the UE supports inter-system change from N1 mode to S1 mode, the UE does not support establishment of a PDN connection for the PDN type set to "non-IP" in S1 mode, and the parameters list field of one or more authorized QoS flow descriptions received in the Authorized QoS flow descriptions IE of the PDU SESSION ESTABLISHMENT ACCEPT message contains an EPS bearer identity (EBI), then the UE shall locally remove the EPS bearer identity (EBI) from the parameters list field of such one or more authorized QoS flow descriptions. Additionally the UE shall also initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #85 "Invalid mapped EPS bearer identity". If the selected PDU session type of the PDU session is "Ethernet", the UE supports inter-system change from N1 mode to S1 mode, the UE does not support establishment of a PDN connection for the PDN type set to "non-IP" in S1 mode, the UE, the network or both of them do not support Ethernet PDN type in S1 mode, and the parameters list field of one or more authorized QoS flow descriptions received in the Authorized QoS flow descriptions IE of the PDU SESSION ESTABLISHMENT ACCEPT message contains an EPS bearer identity (EBI), then the UE shall locally remove the EPS bearer identity (EBI) from the parameters list field of such one or more authorized QoS flow descriptions. Additionally, the UE shall also initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #85 "Invalid mapped EPS bearer identity". For a UE which is registered for disaster roaming services and for a PDU session which is not a PDU session for emergency services: a) if the parameters list field of one or more authorized QoS flow descriptions received in the Authorized QoS flow descriptions IE of the PDU SESSION ESTABLISHMENT ACCEPT message contains an EPS bearer identity (EBI), then the UE shall locally remove the EPS bearer identity (EBI) from the parameters list field of such one or more authorized QoS flow descriptions; and b) the UE shall locally delete the contents of the Mapped EPS bearer contexts IE if it is received in the PDU SESSION ESTABLISHMENT ACCEPT message. If the UE receives an IPv4 Link MTU parameter, an Ethernet Frame Payload MTU parameter, an Unstructured Link MTU parameter, or a Non-IP Link MTU parameter in the Extended protocol configuration options IE of the PDU SESSION ESTABLISHMENT ACCEPT message, the UE shall pass to the upper layer the received IPv4 link MTU size, the received Ethernet frame payload MTU size, the unstructured link MTU size, or the non-IP link MTU size. NOTE 14: The IPv4 link MTU size corresponds to the maximum length of user data packet that can be sent either via the control plane or via N3 interface for a PDU session of the "IPv4" PDU session type. NOTE 15: The Ethernet frame payload MTU size corresponds to the maximum length of a payload of an Ethernet frame that can be sent either via the control plane or via N3 interface for a PDU session of the "Ethernet" PDU session type. NOTE 16: The unstructured link MTU size correspond to the maximum length of user data packet that can be sent either via the control plane or via N3 interface for a PDU session of the "Unstructured" PDU session type. NOTE 17: A PDU session of "Ethernet" or "Unstructured" PDU session type can be transferred to a PDN connection of "non-IP" PDN type, thus the UE can request the non-IP link MTU parameter in the PDU session establishment procedure. The non-IP link MTU size corresponds to the maximum length of user data that can be sent either in the user data container in the ESM DATA TRANSPORT message or via S1-U interface as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]. If the 5G-RG receives an ACS information parameter in the Extended protocol configuration options IE of the PDU SESSION ESTABLISHMENT ACCEPT message, the 5G-RG shall pass the ACS URL in the received ACS information parameter to the upper layer. If the UE has indicated support for CIoT 5GS optimizations and receives a small data rate control parameters container in the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT ACCEPT message, the UE shall store the small data rate control parameters value and use the stored small data rate control parameters value as the maximum allowed limit of uplink user data for the PDU session in accordance with 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]. If the UE has indicated support for CIoT 5GS optimizations and receives an additional small data rate control parameters for exception data container in the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT ACCEPT message, the UE shall store the additional small data rate control parameters for exception data value and use the stored additional small data rate control parameters for exception data value as the maximum allowed limit of uplink exception data for the PDU session in accordance with 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]. If the UE has indicated support for CIoT 5GS optimizations and receives an initial small data rate control parameters container or an initial additional small data rate control parameters for exception data container in the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT ACCEPT message, the UE shall use these parameters for the newly established PDU Session. When the validity period of the initial parameters expire, the parameters received in a small data rate control parameters container or an additional small data rate control parameters for exception data container shall be used. If the UE receives a Serving PLMN rate control IE in the PDU SESSION ESTABLISHMENT ACCEPT message, the UE shall store the Serving PLMN rate control IE value and use the stored serving PLMN rate control value as the maximum allowed limit of uplink control plane user data for the corresponding PDU session in accordance with 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]. If the UE receives an APN rate control parameters container or an additional APN rate control for exception data parameters container in the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT ACCEPT message, the UE shall store these parameters and use them to limit the rate at which it generates uplink user data messages for the PDN connection corresponding to the PDU session if the PDU session is transferred to EPS upon inter-system change from N1 mode to S1 mode in accordance with 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]. The received APN rate control parameters and additional APN rate control for exception data parameters shall replace any previously stored APN rate control parameters and additional APN rate control for exception data parameters, respectively, for this PDN connection. If the UE receives an initial APN rate control parameters container or an initial additional APN rate control for exception data parameters container in the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT ACCEPT message, the UE shall store these parameters in the APN rate control status and use them to limit the rate at which it generates exception data messages for the PDN connection corresponding to the PDU session if the PDU session is transferred to EPS upon inter-system change from N1 mode to S1 mode in accordance with 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]. The received APN rate control status shall replace any previously stored APN rate control status for this PDN connection. NOTE 18: In the PDU SESSION ESTABLISHMENT ACCEPT message, the SMF provides either APN rate control parameters container, or initial APN rate control parameters container, in the Extended protocol configuration options IE, but not both. NOTE 19: In the PDU SESSION ESTABLISHMENT ACCEPT message, the SMF provides either additional APN rate control for exception data parameters container, or initial additional APN rate control for exception data parameters container, in the Extended protocol configuration options IE, but not both. If the network accepts the use of Reliable Data Service to transfer data for the PDU session, the network shall include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT ACCEPT message and include the Reliable Data Service accepted indicator. The UE behaves as described in subclause 6.2.15. If - the UE indicates support of DNS over (D)TLS by providing DNS server security information indicator to the network; - optionally, the UE indicates which security protocol type(s) are supported by the UE, by providing the DNS server security protocol support to the network; and - the network wants to enforce the use of DNS over (D)TLS, the network may include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT ACCEPT message and include the DNS server security information with length of two octets. Upon receiving the DNS server security information, the UE shall pass it to the upper layer. The UE shall use this information to send the DNS over (D)TLS (See 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]). NOTE 20: Support of DNS over (D)TLS is based on the informative requirements as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24] and it is implemented based on the operator requirement. If the PDU SESSION ESTABLISHMENT REQUEST message includes the Service-level-AA container IE with the service-level device ID set to the CAA-level UAV ID, and the SMF is provided by the UAS-NF the successful UUAA-SM result and the CAA-level UAV ID, the SMF shall store the successful result together with the authorized CAA-level UAV ID and transmit the PDU SESSION ESTABLISHMENT ACCEPT message to the UE, where the PDU SESSION ESTABLISHMENT ACCEPT message shall include the Service-level-AA container IE containing: a) the service-level-AA response, with the SLAR field set to "Service level authentication and authorization was successful"; b) the service-level device ID with the value set to the CAA-level UAV ID; and c) if a payload is received from the UAS-NF,the service-level-AA payload, with the value set to the payload; d) if a payload type associated with the payload is received from the UAS-NF, the service-level-AA payload type with the values set to the associated payload type. NOTE 21: UAS security information can be included in the UUAA payload by the USS as specified in 3GPP TS 33.256[ Security aspects of Uncrewed Aerial Systems (UAS) ] [24B]. If the network accepts the request of the PDU session establishment for C2 communication, the network shall send the PDU SESSION ESTABLISHMENT ACCEPT message including the Service-level-AA container IE containing: a) the service-level-AA response with the value of C2AR field set to the "C2 authorization was successful"; b) if a payload is provided from the UAS-NF, the service-level-AA payload with the value set to the payload; c) if a payload type associated with the payload is provided from the UAS-NF, the service-level-AA payload type with the value set to the payload type; and d) if the CAA-level UAV ID is provided from the UAS-NF, the service-level device ID with the value set to the CAA-level UAV ID. NOTE 22:The C2 authorization payload in the service-level-AA payload can include one or both of the C2 session security information, and pairing information for direct C2 communication. Upon receipt of the PDU SESSION ESTABLISHMENT ACCEPT message of the PDU session for C2 communication, if the Service-level-AA container IE is included, the UE shall forward the service-level-AA contents of the Service-level-AA container IE to the upper layers. The SMF may be configured with one or more PVS IP addresses or PVS names or both associated with the DNN and S-NSSAI used for onboarding services in SNPN, for configuration of SNPN subscription parameters in PLMN via the user plane, or for configuration of a UE via the user plane with credentials for NSSAA or PDU session authentication and authorization procedure. If the PDU session was established for onboarding services in SNPN, or the PVS information request is included in the Extended protocol configuration options IE of the PDU SESSION ESTABLISHMENT REQUEST message establishing a PDU session providing connectivity for configuration of SNPN subscription parameters in PLMN via the user plane, the network may include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT ACCEPT message and include the PVS IP address(es) or the PVS name(s) or both associated with the DNN and S-NSSAI of the established PDU session, if available. If the PVS information request is included in the Extended protocol configuration options IE of the PDU SESSION ESTABLISHMENT REQUEST message establishing the PDU session providing connectivity for configuration of a UE via the user plane with credentials for PDU session authentication and authorization procedure, based on the subscribed DNN(s) and S-NSSAI(s) of the UE and the DNN and S-NSSAI of the established PDU session, the network should include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT ACCEPT message and include the PVS IP address(es) or the PVS name(s) or both, which are associated with the established PDU session and per subscribed DNN(s) and S-NSSAI(s) of the UE, if available. If the PVS information request is included in the Extended protocol configuration options IE of the PDU SESSION ESTABLISHMENT REQUEST message establishing the PDU session providing connectivity for configuration of a UE via the user plane with credentials for NSSAA, based on the subscribed S-NSSAI(s) of the UE and the S-NSSAI of the established PDU session, the network should include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT ACCEPT message and include the PVS IP address(es) or the PVS name(s) or both, which are associated with the established PDU session and per subscribed S-NSSAI(s) of the UE, if available. NOTE 23: If the PVS information request is included in the Extended protocol configuration options IE of the PDU SESSION ESTABLISHMENT REQUEST message establishing a PDU session providing connectivity for configuration of SNPN subscription parameters in SNPN via the user plane by a UE which is not registered for onboarding services in SNPN, the SMF can include the PVS IP address(es) or the PVS name(s) or both, associated with the DNN and S-NSSAI of the established PDU session, if available, in the Extended protocol configuration options IE of the PDU SESSION ESTABLISHMENT ACCEPT message. NOTE 24: The PVS IP address(es) or the PVS name(s) or both in the SMF can either be locally configured or provided by DCS. The SMF can send the PVS IP address(es) or the PVS name(s) or both that are available in the SMF as the PVS IP address(es) or the PVS name(s) or both to the UE, respectively. If the PDU session was established for onboarding services in SNPN not supporting localized services in SNPN, the PVS IP address(es) or the PVS name(s) or both provided by DCS takes precedence over the PVS IP address(es) or the PVS name(s) or both locally configured, respectively. If the PDU session was established for onboarding services in SNPN supporting localized services in SNPN, the SMF can include both the DCS provided PVS IP address(es) or the PVS name(s) or both associated with the DNN and S-NSSAI of the established PDU session and the locally configured PVS IP address(es) or the PVS name(s) or both associated with the DNN and S-NSSAI of the established PDU session, if available. The UE upon receiving one or more PVS IP address(es), if any, one or more the PVS name(s), if any, or both shall pass them to the upper layers. NOTE 25: If several PVS IP addresses, several PVS name(s), or one or more PVS IP addresses and one or more PVS name(s) are received, how the UE uses this information is up to UE implementation. If the UE indicates support for ECS configuration information provisioning by providing the ECS configuration information provisioning support indicator in the Extended protocol configuration options IE of the PDU SESSION ESTABLISHMENT REQUEST message, then the SMF may include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT ACCEPT message with - at least one of ECS IPv4 Address(es), ECS IPv6 Address(es), and ECS FQDN(s); - at least one associated ECSP identifier; and - optionally, spatial validity conditions associated with the ECS address. The UE upon receiving one or more ECS IPv4 address(es), if any, ECS IPv6 address(es), if any, or ECS FQDN(s), if any, with the associated spatial validity condition, if any, and an ECSP identifier shall pass them to the upper layers. NOTE 26: The IP address(es), FQDN(s), or both are associated with the ECSP identifier and replace previously provided ECS configuration information associated with the same ECSP identifier, if any. If the SMF needs to provide DNS server address(es) to the UE and the UE has provided the DNS server IPv4 address request, the DNS server IPv6 address request or both of them, in the PDU SESSION ESTABLISHMENT REQUEST message, then the SMF shall include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT ACCEPT message with one or more DNS server IPv4 address(es), one or more DNS server IPv6 address(es) or both of them. If the UE supports receiving DNS server addresses in protocol configuration options and receives one or more DNS server IPv4 address(es), one or more DNS server IPv6 address(es) or both of them, in the Extended protocol configuration options IE of the PDU SESSION ESTABLISHMENT ACCEPT message, then the UE shall pass the received DNS server IPv4 address(es), if any, and the received DNS server IPv6 address(es), if any, to upper layers. NOTE 27: The received DNS server address(es) replace previously provided DNS server address(es), if any. If the PDU SESSION ESTABLISHMENT ACCEPT message includes the Received MBS container IE, for each of the Received MBS information: a) if MBS decision is set to "MBS join is accepted", the UE shall consider that it has successfully joined the multicast MBS session. The UE shall store the received TMGI and shall use it for any further operation on that multicast MBS session. The UE shall store the received MBS service area associated with the received TMGI, if any, and provide the received TMGI to lower layers. The UE may provide the MBS start time if it is included in the Received MBS information to upper layers; or b) if MBS decision is set to "MBS join is rejected", the UE shall consider the requested join as rejected. The UE shall store the received MBS service area associated with the received TMGI, if any. If the received Rejection cause is set to "User is outside of local MBS service area", the UE shall not request to join the same multicast MBS session if neither current TAI nor CGI of the current cell is part of the received MBS service area. If the received Rejection cause is set to "multicast MBS session has not started or will not start soon" and an MBS back-off timer value is included with value that indicates neither zero nor deactivated, the UE shall start a back-off timer T3587 with the value provided in the MBS back-off timer value for the received TMGI, and shall not attempt to join the multicast MBS session with the same TMGI until the expiry of T3587. If the MBS back-off timer value indicates that this timer is deactivated, the UE shall not attempt to join the multicast MBS session with the same TMGI, the Source IP address information of the TMGI, or the Destination IP address information of the TMGI until the UE is switched off, the USIM is removed, or the entry in the "list of subscriber data" for the current SNPN is updated. If the MBS back-off timer value indicates zero, the UE may attempt to join the multicast MBS session with the same TMGI. If the PDU session is established for IMS signalling and the UE has requested P-CSCF IPv6 address or P-CSCF IPv4 address, the SMF shall include P-CSCF IP address(es) in the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT ACCEPT message. NOTE 28: The P-CSCF selection functionality is specified in subclause 5.16.3.11 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]. Upon receipt of the PDU SESSION ESTABLISHMENT ACCEPT message, if the UE included the PDU session pair ID in the PDU SESSION ESTABLISHMENT REQUEST message, the UE shall associate the PDU session with the PDU session pair ID. If the UE included the RSN in the PDU SESSION ESTABLISHMENT REQUEST message, the UE shall associate the PDU session with the RSN. If the UE supports EDC and the network allows the use of EDC, the SMF shall include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT ACCEPT message with the EDC usage allowed indicator. If the UE supports EDC and receives the EDC usage allowed indicator in the Extended protocol configuration options IE of the PDU SESSION ESTABLISHMENT ACCEPT message, the UE shall indicate to upper layers that network allows the use of EDC. If the UE supports EDC and the network requires the use of EDC, the SMF shall include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT ACCEPT message with the EDC usage required indicator. If the UE supports EDC and receives the EDC usage required indicator in the Extended protocol configuration options IE of the PDU SESSION ESTABLISHMENT ACCEPT message, the UE shall indicate to upper layers that network requires the use of EDC. If the PDU SESSION ESTABLISHMENT REQUEST message includes a MS support of MAC address range in 5GS indicator in the Extended protocol configuration options IE, the SMF: a) shall consider that the UE supports a "destination MAC address range type" packet filter component and a "source MAC address range type" packet filter component; and b) if the SMF supports a "destination MAC address range type" packet filter component and a "source MAC address range type" packet filter component and enables the UE to request QoS rules with a "destination MAC address range type" packet filter component and a "source MAC address range type" packet filter component, shall include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT ACCEPT message and shall include the Network support of MAC address range in 5GS indicator in the Extended protocol configuration options IE. If the UE receives the 5GSM network feature support IE in the PDU SESSION ESTABLISHMENT ACCEPT message with the non-3GPP access path switching bit set to "non-3GPP access path switching supported" during the PDU session establishment procedure of any PDU session, the UE may include the NSONR bit with value set to "non-3GPP path switching while using old non-3GPP resources requested" in the Non-3GPP path switching information IE in the REGISTRATION REQUEST message while performing the registration procedure for mobility registration update for non-3GPP access path switching. NOTE 29: If the UE is registered to different PLMNs over 3GPP and non-3GPP accesses, the UE uses the capability received over non-3GPP access to determine whether to initiate the registration procedure for mobility registration update for non-3GPP path switching. NOTE 30: If the AMF selects an SMF not supporting non-3GPP access path switching, the non-3GPP access path switching can still be performed with the AMF triggering release of the old user plane resources before new user plane resources are established. If the PDU SESSION ESTABLISHMENT ACCEPT message includes a Network support of MAC address range in 5GS indicator in the Extended protocol configuration options IE, the UE shall consider that the network supports a "destination MAC address range type" packet filter component and a "source MAC address range type" packet filter component. NOTE 31: Handling of indication that network allows the use of EDC or that network requires the use of EDC is specified in 3GPP TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [182]. If the SMF includes the authorized QoS flow descriptions and the SMF determines to provide the N3QAI to the UE, the SMF shall include the N3QAI in the PDU SESSION ESTABLISHMENT ACCEPT message. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.4.1.3 |
6,394 | 5.2.27.2.6 Ntsctsf_TimeSynchronization_CapsSubscribe operation | Service operation name: Ntsctsf_TimeSynchronization_CapsSubscribe Description: The AF subscribes to receive notification about time synchronization capabilities for a list of UE(s) or a group of UEs or any UE using DNN/S-NSSAI combination. Event Filters are used to specify the conditions to match for notifying the event. If there are no conditions to match then the Event Filter is not provided. The following table describes the Event Filters supported by the service: Table 5.2.27.2.6-1: Time Synchronization capability event filters Inputs, Required: Either a combination of (DNN, S-NSSAI) or an AF-Service-Identifier and Notification Target Address. Inputs, Optional: Event Filter(s) as described in Table 5.2.27.2.6-1, Report Type (can be either one-time reporting, periodic reporting or event based reporting). Outputs, Required: Operation execution result indication. When the subscription is accepted: Subscription Correlation ID, Expiry time. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.27.2.6 |
6,395 | 4.7.4.3 Topological Redundancy | The IAB-node may have redundant routes to the IAB-donor-CU(s). For IAB-nodes operating in SA-mode, NR DC can be used to enable route redundancy in the BH by allowing the IAB-MT to have concurrent BH links with two parent nodes. The parent nodes may be connected to the same or to different IAB-donor-CUs, which control the establishment and release of redundant routes via these two parent nodes. Either parent node's gNB-DU functionality together with the respective IAB-donor-CU assumes the role of the IAB-MT's master node or secondary node. The NR DC framework (e.g., MCG/SCG-related procedures) is used to configure the dual radio links with the parent nodes (TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [21]). The procedure for establishment of topological redundancy for IAB-nodes operating in SA-mode is captured in TS 38.401[ NG-RAN; Architecture description ] [4]. An IAB-node operating in NR-DC may also use one of its links for BH connectivity with an IAB-donor and the other link for access-only connectivity with a separate gNB that does not assume IAB-donor role. The IAB-donor can assume the MN or the SN role. The IAB-node may exchange F1-C traffic with the IAB-donor via the backhaul link and/or via the access link with the gNB. In the latter case, the F1-C messages are carried over NR RRC between the IAB-node and the gNB, and via XnAP between the gNB and the IAB-donor. IAB-nodes operating in EN-DC can exchange F1-C traffic with the IAB-donor via the MeNB. The F1-C message is carried over LTE RRC using SRB2 between IAB-node and MeNB and via X2AP between the MeNB and the IAB-donor. The procedures for establishment of redundant transport of F1-C for IAB-nodes using NR-DC and EN-DC are captured in TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [21] and TS 38.401[ NG-RAN; Architecture description ] [4]. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 4.7.4.3 |
6,396 | 6.12.1 Subscription permanent identifier | In the 5G system, the globally unique 5G subscription permanent identifier is called SUPI as defined in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The SUCI is a privacy preserving identifier containing the concealed SUPI. The SUPI is privacy protected over-the-air by using the SUCI which is described in clause 6.12.2. Handling of SUPI and privacy provisioning related to concealing the SUPI shall be done according to the requirements specified in clause 5 and details provided in clause 6.12.2. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.12.1 |
6,397 | 4.2.5.1 Average Number of simultaneous E-RABs. | a) This measurement provides the average number of simultaneous E-RABs. The measurement is split into subcounters per E-RAB QoS level (QCI). b) SI. c) This measurement is obtained by sampling at a pre-defined interval, the number of simultaneous E-RABs and then taking the arithmetic mean. The measurement is split into subcounters per QCI, and the possible QCIs are included in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]. In case only a subset of per QCI measurements is supported, a sum subcounter will be provided first. d) Each measurement is an integer value. The number of measurements is equal to the number of QCIs plus a possible sum value identified by the .sum suffix. e) The measurement name has the form ERAB.UsageNbrMean.QCI where QCI identifies the E-RAB level quality of service class. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switching. h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.2.5.1 |
6,398 | 16.8.2.2 Network timing synchronization monitoring towards CN | For NG-RAN timing synchronization monitoring support, the 5GC initiates RAN Timing Synchronisation Status (TSS) Reporting procedure to obtain the change of network timing synchronization status of gNBs. The gNB may receive RAN timing synchronization status information request from the AMF, see TS 23.501[ System architecture for the 5G System (5GS) ] [3]. The RAN timing synchronization status information includes the gNB node-level information about timing synchronization operation status. The gNB timing synchronization status may comprise one or more of the following information elements: synchronization state, traceability to UTC, traceability to GNSS, clock frequency stability, clock accuracy, parent time source, as defined in Table 5.27.1.12-1 in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. Based on NG-RAN's capabilities of reporting timing synchronisation status, NG-RAN accepts or rejects the request from AMF. NG-RAN can be pre-configured with thresholds for attributes on timing synchronisation status reporting via OAM. When the thresholds are met or exceeded, events will be triggered and NG-RAN reports Timing Synchronization Status to AMF. For detailed procedure on the Timing Synchronization Status reporting, refer to TS 38.401[ NG-RAN; Architecture description ] Clause 8.x.1 [4]. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.8.2.2 |
6,399 | 6.4.3.2 NAS integrity activation | NAS integrity shall be activated using the NAS SMC procedure or after an inter-system handover from EPC. Replay protection shall be activated when integrity protection is activated, except when the NULL integrity protection algorithm is selected. Replay protection shall ensure that the receiver only accepts each incoming NAS COUNT value once using the same NAS security context. Once NAS integrity has been activated, NAS messages without integrity protection shall not be accepted by the UE or the AMF. Before NAS integrity has been activated, NAS messages without integrity protection shall only be accepted by the UE or the AMF in certain cases where it is not possible to apply integrity protection. NAS integrity shall stay activated until the 5G security context is deleted in either the UE or the AMF. It shall not be possible to change from non-NULL integrity protection algorithm to NULL integrity protection. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.4.3.2 |
6,400 | 9.2.5 Minimum requirement PUCCH 1-1 (when csi-SubframeSet –r12 and EIMTA-MainConfigServCell-r12 are configured) | The following requirements apply to UE Category ≥2 which supports eIMTA TDD UL-DL reconfiguration for TDD serving cell(s) via monitoring PDCCH with eIMTA-RNTI and Rel-12 CSI subframe sets. For the parameters specified in table 9.2.5-1, and using the downlink physical channels specified in Tables C.3.2-1 and C.3.2-2, for each CSI subframe set, the reported CQI value shall be in the range of ±1 of the reported median more than 90% of the time. For each CSI subframe set, if the PDSCH BLER using the transport format indicated by median CQI is less than or equal to 0.1, the BLER using the transport format indicated by the (median CQI + 1) shall be greater than 0.1. If the PDSCH BLER using the transport format indicated by the median CQI is greater than 0.1, the BLER using transport format indicated by (median CQI – 1) shall be less than or equal to 0.1. The difference of the median CQI obtained by reports in CSI subframe sets CCSI,0 and the median CQI obtained by reports in CSI subframe sets CCSI,1 shall be larger than or equal to 3. Table 9.2.5-1: PUCCH 1-1 static test (TDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.2.5 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.