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
⌀ |
|---|---|---|---|---|---|---|---|
901 | 3.3 Structure of Mobile Subscriber ISDN number (MSISDN) | Mobile Subscriber ISDN numbers (i.e. E.164 numbers) are assigned from the E.164 numbering plan [10]; see also ITU-T Recommendation E.213 [12]. The structure of the MSISDN will then be as shown in figure 2. Figure 2: Number Structure of MSISDN The number consists of: - Country Code (CC) of the country in which the MS is registered, followed by: - National (significant) number, which consists of: - National Destination Code (NDC) and - Subscriber Number (SN). For GSM/UMTS applications, a National Destination Code is allocated to each PLMN. In some countries more than one NDC may be required for each PLMN/mobile number ranges. The composition of the MSISDN should be such that it can be used as a global title address in the Signalling Connection Control Part (SCCP) for routeing messages to the home location register of the MS. The country code (CC) and the national destination code (NDC) will provide such routeing information. If further routeing information is required, it should be contained in the first few digits of the subscriber number (SN). A sub-address may be appended to an E.164 number for use in call setup and in supplementary service operations where an E.164 number is required (see ITU-T Recommendations E.164, clause Annex B, B.3.3, and X.213 annex A). The sub-address is transferred to the terminal equipment denoted by the ISDN number. The maximum length of a sub-address is 20 octets, including one octet to identify the coding scheme for the sub-address (see ITU-T Recommendation X.213, annex A). All coding schemes described in ITU-T Recommendation X.213, annex A are supported in 3GPP networks As an exception to the rules above, the MSISDN shall take the dummy MSISDN value composed of 15 digits set to 0 (encoded as an international E.164 number) when the MSISDN is not available in messages in which the presence of the MSISDN parameter is required for backward compatibility reason. See the relevant stage 3 specifications. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 3.3 |
902 | – OtherConfig | The IE OtherConfig contains configuration related to miscellaneous other configurations. OtherConfig information element -- ASN1START -- TAG-OTHERCONFIG-START OtherConfig ::= SEQUENCE { delayBudgetReportingConfig CHOICE{ release NULL, setup SEQUENCE{ delayBudgetReportingProhibitTimer ENUMERATED {s0, s0dot4, s0dot8, s1dot6, s3, s6, s12, s30} } } OPTIONAL -- Need M } OtherConfig-v1540 ::= SEQUENCE { overheatingAssistanceConfig SetupRelease {OverheatingAssistanceConfig} OPTIONAL, -- Need M ... } OtherConfig-v1610 ::= SEQUENCE { idc-AssistanceConfig-r16 SetupRelease {IDC-AssistanceConfig-r16} OPTIONAL, -- Need M drx-PreferenceConfig-r16 SetupRelease {DRX-PreferenceConfig-r16} OPTIONAL, -- Need M maxBW-PreferenceConfig-r16 SetupRelease {MaxBW-PreferenceConfig-r16} OPTIONAL, -- Need M maxCC-PreferenceConfig-r16 SetupRelease {MaxCC-PreferenceConfig-r16} OPTIONAL, -- Need M maxMIMO-LayerPreferenceConfig-r16 SetupRelease {MaxMIMO-LayerPreferenceConfig-r16} OPTIONAL, -- Need M minSchedulingOffsetPreferenceConfig-r16 SetupRelease {MinSchedulingOffsetPreferenceConfig-r16} OPTIONAL, -- Need M releasePreferenceConfig-r16 SetupRelease {ReleasePreferenceConfig-r16} OPTIONAL, -- Need M referenceTimePreferenceReporting-r16 ENUMERATED {true} OPTIONAL, -- Need R btNameList-r16 SetupRelease {BT-NameList-r16} OPTIONAL, -- Need M wlanNameList-r16 SetupRelease {WLAN-NameList-r16} OPTIONAL, -- Need M sensorNameList-r16 SetupRelease {Sensor-NameList-r16} OPTIONAL, -- Need M obtainCommonLocation-r16 ENUMERATED {true} OPTIONAL, -- Need R sl-AssistanceConfigNR-r16 ENUMERATED{true} OPTIONAL -- Need R } OtherConfig-v1700 ::= SEQUENCE { ul-GapFR2-PreferenceConfig-r17 ENUMERATED {true} OPTIONAL, -- Need R musim-GapAssistanceConfig-r17 SetupRelease {MUSIM-GapAssistanceConfig-r17} OPTIONAL, -- Need M musim-LeaveAssistanceConfig-r17 SetupRelease {MUSIM-LeaveAssistanceConfig-r17} OPTIONAL, -- Need M successHO-Config-r17 SetupRelease {SuccessHO-Config-r17} OPTIONAL, -- Need M maxBW-PreferenceConfigFR2-2-r17 ENUMERATED {true} OPTIONAL, -- Cond maxBW maxMIMO-LayerPreferenceConfigFR2-2-r17 ENUMERATED {true} OPTIONAL, -- Cond maxMIMO minSchedulingOffsetPreferenceConfigExt-r17 ENUMERATED {true} OPTIONAL, -- Cond minOffset rlm-RelaxationReportingConfig-r17 SetupRelease {RLM-RelaxationReportingConfig-r17} OPTIONAL, -- Need M bfd-RelaxationReportingConfig-r17 SetupRelease {BFD-RelaxationReportingConfig-r17} OPTIONAL, -- Need M scg-DeactivationPreferenceConfig-r17 SetupRelease {SCG-DeactivationPreferenceConfig-r17} OPTIONAL, -- Cond SCG rrm-MeasRelaxationReportingConfig-r17 SetupRelease {RRM-MeasRelaxationReportingConfig-r17} OPTIONAL, -- Need M propDelayDiffReportConfig-r17 SetupRelease {PropDelayDiffReportConfig-r17} OPTIONAL -- Need M } OtherConfig-v1800 ::= SEQUENCE { idc-AssistanceConfig-v1800 SetupRelease {IDC-AssistanceConfig-v1800} OPTIONAL, -- Need M multiRx-PreferenceReportingConfigFR2-r18 SetupRelease {MultiRx-PreferenceReportingConfigFR2-r18} OPTIONAL, -- Need M uav-FlightPathAvailabilityConfig-r18 ENUMERATED {true} OPTIONAL, -- Need R ul-TrafficInfoReportingConfig-r18 SetupRelease {UL-TrafficInfoReportingConfig-r18} OPTIONAL, -- Need M n3c-RelayUE-InfoReportConfig-r18 ENUMERATED {true} OPTIONAL, -- Need R successPSCell-Config-r18 SetupRelease {SuccessPSCell-Config-r18} OPTIONAL, -- Need M sn-InitiatedPSCellChange-r18 ENUMERATED {true} OPTIONAL, --Need M musim-GapPriorityAssistanceConfig-r18 ENUMERATED {true} OPTIONAL, -- Cond musimGapConfig musim-CapabilityRestrictionConfig-r18 SetupRelease {MUSIM-CapabilityRestrictionConfig-r18} OPTIONAL -- Need M } IDC-AssistanceConfig-v1800 ::= SEQUENCE { idc-FDM-AssistanceConfig-r18 SetupRelease {IDC-FDM-AssistanceConfig-r18} OPTIONAL, -- Need M idc-TDM-AssistanceConfig-r18 ENUMERATED {setup} OPTIONAL -- Cond FDM } MultiRx-PreferenceReportingConfigFR2-r18 ::= SEQUENCE { multiRx-PreferenceReportingConfigFR2ProhibitTimer-r18 ENUMERATED { s0, s0dot5, s1, s2, s3, s4, s5, s6, s7, s8, s9, s10, s20, s30, spare2, spare1} } CandidateServingFreqListNR-r16 ::= SEQUENCE (SIZE (1..maxFreqIDC-r16)) OF ARFCN-ValueNR MUSIM-GapAssistanceConfig-r17 ::= SEQUENCE { musim-GapProhibitTimer-r17 ENUMERATED {s0, s0dot1, s0dot2, s0dot3, s0dot4, s0dot5, s1, s2, s3, s4, s5, s6, s7, s8, s9, s10} } MUSIM-LeaveAssistanceConfig-r17 ::= SEQUENCE { musim-LeaveWithoutResponseTimer-r17 ENUMERATED {ms10, ms20, ms40, ms60, ms80, ms100, spare2, spare1} } MUSIM-CapabilityRestrictionConfig-r18 ::= SEQUENCE { musim-CandidateBandList-r18 MUSIM-CandidateBandList-r18 OPTIONAL, -- Need M musim-WaitTimer-r18 ENUMERATED {ms10, ms20, ms40, ms60, ms80, ms100, spare2, spare1}, musim-ProhibitTimer-r18 ENUMERATED {ms0, ms10, ms20, ms40, ms60, ms80, spare2, spare1} } MUSIM-CandidateBandList-r18::= SEQUENCE (SIZE (1..maxCandidateBandIndex-r18)) OF FreqBandIndicatorNR SuccessHO-Config-r17 ::= SEQUENCE { thresholdPercentageT304-r17 ENUMERATED {p40, p60, p80, spare5, spare4, spare3, spare2, spare1} OPTIONAL, --Need R thresholdPercentageT310-r17 ENUMERATED {p40, p60, p80, spare5, spare4, spare3, spare2, spare1} OPTIONAL, --Need R thresholdPercentageT312-r17 ENUMERATED {p20, p40, p60, p80, spare4, spare3, spare2, spare1} OPTIONAL, --Need R sourceDAPS-FailureReporting-r17 ENUMERATED {true} OPTIONAL, --Need R ... } SuccessPSCell-Config-r18 ::= SEQUENCE { thresholdPercentageT304-SCG-r18 ENUMERATED {p40, p60, p80, spare5, spare4, spare3, spare2, spare1} OPTIONAL, --Need R thresholdPercentageT310-SCG-r18 ENUMERATED {p40, p60, p80, spare5, spare4, spare3, spare2, spare1} OPTIONAL, --Need R thresholdPercentageT312-SCG-r18 ENUMERATED {p20, p40, p60, p80, spare4, spare3, spare2, spare1} OPTIONAL, --Need R ... } OverheatingAssistanceConfig ::= SEQUENCE { overheatingIndicationProhibitTimer ENUMERATED {s0, s0dot5, s1, s2, s5, s10, s20, s30, s60, s90, s120, s300, s600, spare3, spare2, spare1} } IDC-AssistanceConfig-r16 ::= SEQUENCE { candidateServingFreqListNR-r16 CandidateServingFreqListNR-r16 OPTIONAL, -- Need R ... } DRX-PreferenceConfig-r16 ::= SEQUENCE { drx-PreferenceProhibitTimer-r16 ENUMERATED { s0, s0dot5, s1, s2, s3, s4, s5, s6, s7, s8, s9, s10, s20, s30, spare2, spare1} } MaxBW-PreferenceConfig-r16 ::= SEQUENCE { maxBW-PreferenceProhibitTimer-r16 ENUMERATED { s0, s0dot5, s1, s2, s3, s4, s5, s6, s7, s8, s9, s10, s20, s30, spare2, spare1} } MaxCC-PreferenceConfig-r16 ::= SEQUENCE { maxCC-PreferenceProhibitTimer-r16 ENUMERATED { s0, s0dot5, s1, s2, s3, s4, s5, s6, s7, s8, s9, s10, s20, s30, spare2, spare1} } MaxMIMO-LayerPreferenceConfig-r16 ::= SEQUENCE { maxMIMO-LayerPreferenceProhibitTimer-r16 ENUMERATED { s0, s0dot5, s1, s2, s3, s4, s5, s6, s7, s8, s9, s10, s20, s30, spare2, spare1} } MinSchedulingOffsetPreferenceConfig-r16 ::= SEQUENCE { minSchedulingOffsetPreferenceProhibitTimer-r16 ENUMERATED { s0, s0dot5, s1, s2, s3, s4, s5, s6, s7, s8, s9, s10, s20, s30, spare2, spare1} } ReleasePreferenceConfig-r16 ::= SEQUENCE { releasePreferenceProhibitTimer-r16 ENUMERATED { s0, s0dot5, s1, s2, s3, s4, s5, s6, s7, s8, s9, s10, s20, s30, infinity, spare1}, connectedReporting ENUMERATED {true} OPTIONAL -- Need R } RLM-RelaxationReportingConfig-r17 ::= SEQUENCE { rlm-RelaxtionReportingProhibitTimer ENUMERATED {s0, s0dot5, s1, s2, s5, s10, s20, s30, s60, s90, s120, s300, s600, infinity, spare2, spare1} } BFD-RelaxationReportingConfig-r17 ::= SEQUENCE { bfd-RelaxtionReportingProhibitTimer ENUMERATED {s0, s0dot5, s1, s2, s5, s10, s20, s30, s60, s90, s120, s300, s600, infinity, spare2, spare1} } SCG-DeactivationPreferenceConfig-r17 ::= SEQUENCE { scg-DeactivationPreferenceProhibitTimer-r17 ENUMERATED { s0, s1, s2, s4, s8, s10, s15, s30, s60, s120, s180, s240, s300, s600, s900, s1800} } RRM-MeasRelaxationReportingConfig-r17 ::= SEQUENCE { s-SearchDeltaP-Stationary-r17 ENUMERATED {dB2, dB3, dB6, dB9, dB12, dB15, spare2, spare1}, t-SearchDeltaP-Stationary-r17 ENUMERATED {s5, s10, s20, s30, s60, s120, s180, s240, s300, spare7, spare6, spare5, spare4, spare3, spare2, spare1} } PropDelayDiffReportConfig-r17 ::= SEQUENCE { threshPropDelayDiff-r17 ENUMERATED {ms0dot5, ms1, ms2, ms3, ms4, ms5, ms6 ,ms7, ms8, ms9, ms10, spare5, spare4, spare3, spare2, spare1} OPTIONAL, -- Need M neighCellInfoList-r17 SEQUENCE (SIZE (1..maxCellNTN-r17)) OF NeighbourCellInfo-r17 OPTIONAL -- Need M } NeighbourCellInfo-r17 ::= SEQUENCE { epochTime-r17 EpochTime-r17, ephemerisInfo-r17 EphemerisInfo-r17 } IDC-FDM-AssistanceConfig-r18 ::= SEQUENCE { candidateServingFreqRangeListNR-r18 CandidateServingFreqRangeListNR-r18 OPTIONAL, -- Need R ... } CandidateServingFreqRangeListNR-r18 ::= SEQUENCE (SIZE (1..maxFreqIDC-r16)) OF CandidateServingFreqRangeNR-r18 CandidateServingFreqRangeNR-r18 ::= SEQUENCE { candidateCenterFreq-r18 ARFCN-ValueNR, candidateBandwidth-r18 ENUMERATED {khz200, khz400, khz600, khz800, mhz1, mhz2, mhz3, mhz4, mhz5, mhz6, mhz8, mhz10, mhz20, mhz30, mhz40, mhz50, mhz60, mhz80, mhz100, mhz200, mhz300, mhz400} OPTIONAL -- Need R } UL-TrafficInfoReportingConfig-r18 ::= SEQUENCE { pdu-SessionsToReportUL-TrafficInfoList-r18 SEQUENCE (SIZE (1.. maxNrofPDU-Sessions-r17)) OF PDU-SessionToReportUL-TrafficInfo-r18, ul-TrafficInfoProhibitTimer-r18 ENUMERATED {s0, s0dot5, s1, s2, s5, s10, s20, s30, s60, s90, s120, s300, s600, spare3, spare2, spare1} } PDU-SessionToReportUL-TrafficInfo-r18 ::= SEQUENCE { pdu-SessionID PDU-SessionID, qfi-ToReportUL-TrafficInfoList-r18 SEQUENCE (SIZE (1..maxNrofQFIs)) OF QFI } -- TAG-OTHERCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
903 | 6.30.2 Requirements | The following set of requirements complement the requirements listed in 3GPP TS 22.011[ Service accessibility ] [3], clause 3.2.2.8. The 5G system shall support a mechanism for the HPLMN to control the timing when a UE registered on a VPLMN, in automatic mode (see clause 3.1 of TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [25]) and currently in CONNECTED mode, enters IDLE mode and initiates higher priority PLMN selection based on the type of ongoing communication. NOTE 1: Changes needed to support the above requirement are expected to have minimum impact on the 5G system. UE is expected to initiate the above-mentioned PLMN selection e.g. by locally releasing the established N1 NAS signalling connection. NOTE 1a: The requirement above applies also to the case of a UE registered to a non-subscribed (standalone) NPN, in order to select a higher priority PLMN or NPN. The UE shall be able to delay conforming to steering of roaming control information from the HPLMN while it is engaged in priority service (e.g. emergency call, MPS session), or a service defined by HPLMN policy not to be interrupted (e.g. MMTEL voice/video call). NOTE 2: The HPLMN policy can take into account the user's preference for the service(s) not to be interrupted. User preferences can be communicated utilizing non-standard operator-specific mechanisms, e.g. web-based. The mechanism mentioned above in this clause shall be available to the HPLMN even if the VPLMN the UE is registered on is compliant to an earlier release of the 5G system. The 5G system shall support mechanisms to enable a credentials holder (e.g. HPLMN or subscribed standalone NPN) to send steering of roaming information to a UE for selecting standalone NPNs (e.g prioritized list of preferred NPNs). | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.30.2 |
904 | 6.3.5.2.1 Minimum requirements | The requirements specified in Table 6.3.5.2.1-1 apply when the power of the target and reference sub-frames are within the power range bounded by the Minimum output power as defined in subclause 6.3.2 and the measured PUMAX as defined in subclause 6.2.5 (i.e, the actual power as would be measured assuming no measurement error). This power shall be within the power limits specified in subclause 6.2.5. To account for RF Power amplifier mode changes 2 exceptions are allowed for each of two test patterns. The test patterns are a monotonically increasing power sweep and a monotonically decreasing power sweep over a range bounded by the requirements of minimum power and maximum power specified in subclauses 6.3.2 and 6.2.2. For these exceptions the power tolerance limit is a maximum of ±6.0 dB in Table 6.3.5.2.1-1 Table 6.3.5.2.1-1 Relative power tolerance for transmission (normal conditions) The power step (ΔP) is defined as the difference in the calculated setting of the UE Transmit power between the target and reference sub-frames with the power setting according to subclause 5.1 of [TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] ]. The error is the difference between ΔP and the power change measured at the UE antenna port with the power of the cell-specific reference signals kept constant. The error shall be less than the relative power tolerance specified in Table 6.3.5.2.1-1. For sub-frames not containing an SRS symbol, the power change is defined as the relative power difference between the mean power of the original reference sub-frame and the mean power of the target subframe not including transient durations. The mean power of successive sub-frames shall be calculated according to Figure 6.3.4.3-1 and Figure 6.3.4.1-1 if there is a transmission gap between the reference and target sub-frames. If at least one of the sub-frames contains an SRS symbol, the power change is defined as the relative power difference between the mean power of the last transmission within the reference sub-frame and the mean power of the first transmission within the target sub-frame not including transient durations. A transmission is defined as PUSCH, PUCCH or an SRS symbol. The mean power of the reference and target sub-frames shall be calculated according to Figures 6.3.4.1-1, 6.3.4.2-1, 6.3.4.4-1, 6.3.4.4-2 and 6.3.4.4-3 for these cases. | 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.5.2.1 |
905 | 9.2.1.10 TDD (Modulation and TBS index Table 3 and 4-bit CQI Table 4 are used) | The following requirements apply to UE DL Category 20 and DL Category ≥22. For the parameters specified in Table 9.2.1.10-1, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2, the reported CQI value according to RC.X TDD in Table A.4-1 shall be in the range of ±1 of the reported median more than 90% of the time. 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. In this test, 4-bit CQI Table 3 in Table 7.2.3-4 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6], and Modulation and TBS index table 3 in Table 7.1.7.1-1B for PDSCH in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6] are applied. Table 9.2.1.10-1: PUCCH 1-0 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.1.10 |
906 | 4.4.3 Handling of NAS COUNT and NAS sequence number 4.4.3.1 General | Each 5G NAS security context shall be associated with two separate counters NAS COUNT per access type in the same PLMN: one related to uplink NAS messages and one related to downlink NAS messages. If the 5G NAS security context is used for access via both 3GPP and non-3GPP access in the same PLMN, there are two NAS COUNT counter pairs associated with the 5G NAS security context. The NAS COUNT counters use 24-bit internal representation and are independently maintained by UE and AMF. The NAS COUNT shall be constructed as a NAS sequence number (8 least significant bits) concatenated with a NAS overflow counter (16 most significant bits). When NAS COUNT is input to NAS ciphering or NAS integrity algorithms it shall be considered to be a 32-bit entity which shall be constructed by padding the 24-bit internal representation with 8 zeros in the most significant bits. The value of the uplink NAS COUNT that is stored or read out of the USIM or non-volatile memory as described in annex C, is the value that shall be used in the next NAS message. The value of the downlink NAS COUNT that is stored or read out of the USIM or non-volatile memory as described in annex C, is the largest downlink NAS COUNT used in a successfully integrity checked NAS message. The value of the uplink NAS COUNT stored in the AMF is the largest uplink NAS COUNT used in a successfully integrity checked NAS message. The value of the downlink NAS COUNT stored in the AMF is the value that shall be used in the next NAS message. The NAS sequence number part of the NAS COUNT shall be exchanged between the UE and the AMF as part of the NAS signalling. After each new or retransmitted outbound SECURITY PROTECTED 5GS NAS MESSAGE message, the sender shall increase the NAS COUNT number by one, except for the initial NAS messages if the lower layers indicated the failure to establish the RRC connection (see 3GPP TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [30]). Specifically, on the sender side, the NAS sequence number shall be increased by one, and if the result is zero (due to wrap around), the stored NAS overflow counter shall also be incremented by one (see subclause 4.4.3.5). If, through implementation-dependent means, the receiver determines that the NAS message is a replay of an earlier NAS message, then the receiver handles the received NAS message as described in subclause 4.4.3.2. Otherwise, in order to determine the estimated NAS COUNT value to be used for integrity verification of a received NAS message: - The sequence number part of the estimated NAS COUNT value shall be equal to the sequence number in the received NAS message; and - If the receiver can guarantee that this NAS message was not previously accepted, then the receiver may select the estimated NAS overflow counter so that the estimated NAS COUNT value is lower than the stored NAS COUNT value; otherwise, the receiver selects the estimated NAS overflow counter so that the estimated NAS COUNT value is higher than the stored NAS COUNT value. During the inter-system change from S1 mode to N1 mode in 5GMM-CONNECTED mode, when a mapped 5G NAS security context is derived and taken into use, the AMF shall set both the uplink and downlink NAS COUNT counters of this 5G NAS security context to zero. The UE shall set both the uplink and downlink NAS COUNT counters of this 5G NAS security context to zero. During the inter-system change from S1 mode to N1 mode in 5GMM-CONNECTED mode, the AMF shall increment the downlink NAS COUNT by one after it has created an S1 mode to N1 mode NAS transparent container (see subclause 9.11.2.9). During the inter-system change from N1 mode to S1 mode in 5GMM-CONNECTED mode, the AMF shall increment the downlink NAS COUNT by one after it has created an N1 mode to S1 mode NAS transparent container (see subclause 9.11.2.7). During N1 mode to N1 mode handover: a) if the new 5G NAS security context is created with the same KAMF, the AMF shall signal the 8 least significant bits of the current downlink NAS COUNT value in an Intra N1 mode NAS transparent container (see subclause 9.11.2.6). The AMF shall then increment the downlink NAS COUNT by one; or b) if the new 5G NAS security context is created with a new KAMF, the AMF shall signal the 8 least significant bits of the current downlink NAS COUNT value in an Intra N1 mode NAS transparent container (see subclause 9.11.2.6) and shall then set both the uplink and downlink NAS COUNT counters of this 5G NAS security context to zero. The AMF shall then increment the downlink NAS COUNT by one. The UE shall also set both the uplink and downlink NAS COUNT counters to zero. NOTE: During the inter-system change from S1 mode to N1 mode in 5GMM-CONNECTED mode, the S1 mode to N1 mode NAS transparent container (see subclause 9.11.2.9) is treated as an implicit SECURITY MODE COMMAND message for the UE and the AMF, and therefore the AMF regards the sending of the S1 mode to N1 mode NAS transparent container as the sending of an initial SECURITY MODE COMMAND message in order to derive and take into use a mapped 5G NAS security context for the purpose of the NAS COUNT handling. | 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.3 |
907 | 5.2.5.7 Npcf_EventExposure service 5.2.5.7.1 General | Service description: This service enables an NF to subscribe and get notified about PCF events for a group of UE(s) or any UE accessing a combination of (DNN, S-NSSAI). The events can be subscribed by a NF consumer are described in clause 6.1.3.18 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. The following service operations are defined for the Npcf_EventExposure service: - Npcf_EventExposure_Subscribe. - Npcf_EventExposure_UnSubscribe. - Npcf_EventExposure_Notify. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.5.7 |
908 | 6.11 Synchronization signals | There are 504 unique physical-layer cell identities. The physical-layer cell identities are grouped into 168 unique physical-layer cell-identity groups, each group containing three unique identities. The grouping is such that each physical-layer cell identity is part of one and only one physical-layer cell-identity group. A physical-layer cell identity is thus uniquely defined by a numberin the range of 0 to 167, representing the physical-layer cell-identity group, and a number in the range of 0 to 2, representing the physical-layer identity within the physical-layer cell-identity group. | 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.11 |
909 | 5.7.2b.3 Actions related to transmission of ULInformationTransferIRAT message | The UE shall set the contents of the ULInformationTransferIRAT message as follows: 1> if there is a need to transfer dedicated LTE information related to V2X sidelink communications: 2> set the ul-DCCH-MessageEUTRA to include the V2X sidelink communication information to be transferred (e.g. the E-UTRA RRC MeasurementReport message, the E-UTRA RRC SidelinkUEInformation message, or the E-UTRA RRC UEAssistanceInformation message); 1> submit the ULInformationTransferIRAT 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.7.2b.3 |
910 | 6.2.3 Resource blocks | Resource blocks are used to describe the mapping of certain physical channels to resource elements. Physical and virtual resource blocks are defined. A physical resource block is defined as consecutive OFDM symbols in the time domain and consecutive subcarriers in the frequency domain, where and are given by Table 6.2.3-1. A physical resource block thus consists of resource elements, corresponding to one slot in the time domain and 180 kHz in the frequency domain. Physical resource blocks are numbered from 0 to in the frequency domain. The relation between the physical resource block number in the frequency domain and resource elements in a slot is given by Table 6.2.3-1: Physical resource blocks parameters Except for subcarrier spacing and , a physical resource-block pair is defined as the two physical resource blocks in one subframe having the same physical resource-block number . A virtual resource block is of the same size as a physical resource block. Two types of virtual resource blocks are defined: - Virtual resource blocks of localized type - Virtual resource blocks of distributed type For each type of virtual resource blocks, a pair of virtual resource blocks over two slots in a subframe is assigned together by a single virtual resource block number, . | 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.2.3 |
911 | 8.12 Indication | Indication is coded as depicted in Figure 8.12-1. Figure 8.12-1: Indication For each message the applicable flags of the Indication IE shall be clearly specified in the individual message clause. The remaining flags of the Indication IE not so indicated shall be discarded by the receiver. The receiver shall consider the value of the applicable flags as "0", if the Indication IE is applicable for the message but not included in the message by the sender. The following bits within Octet 5 shall indicate: - Bit 8 – DAF (Dual Address Bearer Flag): This bit shall be set when the PDN Type, determined based on UE request and subscription record, is set to IPv4v6 and all SGSNs which the UE may be handed over to are Release 8 or above supporting dual addressing, which is determined based on node pre-configuration by the operator.. - Bit 7 – DTF (Direct Tunnel Flag): This bit shall be set when the UE is in UTRAN and Direct Tunnel is selected - Bit 6 – HI (Handover Indication): If this bit is set to 1 over S11/S4 and S5/S8 interfaces, it shall indicate a UE handover attach. This bit is applicable during the Handover from Trusted or Untrusted Non-3GPP IP Access to E-UTRAN or a Handover from Trusted or Untrusted Non-3GPP IP Access to UTRAN/GERAN procedures (see clauses 8.2, 8.6 and 16.11 of 3GPP TS 23.402[ Architecture enhancements for non-3GPP accesses ] [45]), or a 5GS to EPS handover without the N26 interface (see clause 4.11.2.2 of 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [83]). If this bit is set to 1 over GTP based S2a interface, it shall indicate a UE handover from 3GPP access to Trusted Non-3GPP access and UE requested IP address preservation. If this bit is set to 1 over GTP based S2b interface, it shall indicate a UE handover from 3GPP access to Untrusted Non-3GPP Access and UE requested IP address preservation. - Bit 5 – DFI (Direct Forwarding Indication): If this bit is set to 1, it shall indicate that direct data forwarding applies between the source RAN and the target RAN during an S1 based handover procedure or during an inter-system handover between 5GS and EPS. - Bit 4 – OI (Operation Indication): - If this bit is set to 1, it shall denote that the receiving SGW of a "Create Session Request" shall send a Modify Bearer Request immediately to the PGW. This allows the SGW to differentiate if the "Create Session Request" received on S4/S11 interface belongs to a TAU/RAU with an SGW relocation (OI = 1), or X2-based handover with SGW relocation (OI = 1) or Enhanced SRNS Relocation with SGW relocation (OI=1) or MME triggered Serving GW relocation (OI = 1) or S1-based handover with SGW relocation (OI = 0). - It shall be set to 1 on S4/S11 interface if the SGW needs to forward the Delete Session Request message to PGW. - Bit 3 – ISRSI (Idle mode Signalling Reduction Supported Indication): If this is set to 1, it shall indicate that the old/source SGSN/MME and the associated SGW are capable to activate ISR. - Bit 2 – ISRAI (Idle mode Signalling Reduction Activation Indication): If this bit is set to 1, it shall indicate that the ISR is established between the MME and the S4 SGSN during a TAU/RAU without an SGW change procedure or during an Inter RAT handover without an SGW change procedure. The SGW shall retain the resources for the other CN node that has its bearer resources on the SGW reserved. The old/source SGSN/MME shall maintain the UE's contexts and activate ISR. - Bit 1 – SGWCI (SGW Change Indication): - If this bit is set to 1, it shall indicate that the target MME/SGSN has selected a new SGW during a TAU/RAU or handover with an SGW change procedure. - It shall be set to 1 by the target AMF during the EPS to 5GS handover/Idle mode Mobility using N26 interface. The following bits within Octet 6 shall indicate: - Bit 8 – SQCI (Subscribed QoS Change Indication): If this bit is set to 1, it indicates that the subscribed QoS profile of the related PDN connection has changed in the old MME/SGSN when the UE is in ECM-IDLE state and ISR is activated. The new MME/SGSN shall trigger the Subscribed QoS Modification procedure. See 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3], clause 5.3.9.2. - Bit 7 – UIMSI (Unauthenticated IMSI): If this bit is set to 1, it indicates that the IMSI present in the message is not authenticated and is for emergency or RLOS attached UE. - Bit 6 – CFSI (Change F-TEID support indication): if this bit is set to 1, it indicates that the SGW can change the assigned GTP-U F-TEID in the current procedure. If the SGW needs to modify the GTP-U F-TEID and the CFSI flag is set to 1 in the corresponding request message, the SGW shall include the new F-TEID in the Modify Bearer Response/Modify Access Bearers Response message. - Bit 5 – CRSI (Change Reporting support indication): if this bit is set to 1, it indicates that the MME/S4 SGSN supports Location Change Reporting mechanism for the corresponding session. - Bit 4 – PS (Piggybacking Supported). This bit denotes whether the MME/SGW support piggybacking feature as described in Annex F of 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3]. If set to 1, it indicates that the node is capable of processing two different GTP-C messages appearing back to back in a single UDP payload. - Bit 3 – PT (S5/S8 Protocol Type) If this bit set to 1, it shall indicate that the protocol type for the S5/S8 interface is PMIP; this bit is set to 0 to indicate that the protocol type for the S5/S8 interface is GTP. - Bit 2 – SI (Scope Indication): If this bit is set to 1, it indicates that all bearer resources of the UE shall be released by the SGW. This flag is set in messages during TAU/RAU/Handover with SGW change /SRNS Relocation Cancel Using S4 with SGW change/Inter RAT handover Cancel procedure with SGW change/S1 Based handover Cancel procedure with SGW change. - Bit 1 – MSV (MS Validated): If this bit is set to 1, it shall indicate that the new MME/SGSN has successfully authenticated the UE. The following bits within Octet 7shall indicate: - Bit 8 – RetLoc (Retrieve Location Indication Flag): if this bit is set to 1, it indicates that the PGW requests the MME/SGSN or TWAN/ePDG to provide the User Location Information. Bit 7 – PBIC (Propagate BBAI Information Change): if this bit is set to 1, it indicates a change in the H(e)NB local IP address and/or UDP port number, i.e. the UE moves from an (e)NB to a H(e)NB, or from one H(e)NB to another H(e)NB with the fixed network backhaul changed, or the UE moves from a H(e)NB to a (e)NB. - Bit 6 – SRNI (SGW Restoration Needed Indication): if this bit is set to 1, it indicates that the source MME/S4-SGSN has not performed the SGW relocation procedure after the source SGW has failed with or without restart, when the source and target MME/S4-SGSN support the MME/S4-SGSN triggered SGW restoration procedure as specified in 3GPP TS 23.007[ Restoration procedures ] [17]. - Bit 5 – S6AF (Static IPv6 Address Flag): if this bit is set to 1, it indicates that PDP/PDN IPv6 address is static. - Bit 4 – S4AF (Static IPv4 Address Flag): if this bit is set to 1, it indicates that PDP/PDN IPv4 address is static. - Bit 3 – MBMDT (Management Based MDT allowed flag): if this bit is set to 1, it indicates that management based MDT is allowed. - Bit 2 – ISRAU (ISR is activated for the UE): if this bit is set to 1, it indicates that ISR is activated for the UE before the UE moving to the new SGSN/MME. - Bit 1 – CCRSI (CSG Change Reporting support indication): if this bit is set to 1, it indicates that the MME/S4 SGSN supports CSG Information Change Reporting mechanism for the corresponding session. The following bits within Octet 8 shall indicate: - Bit 8 – CPRAI (Change of Presence Reporting Area information Indication): when ISR is active if this bit is set to 1, it indicates that the Presence Reporting Area information, which is provided as a part of the Presence Reporting Area Information IE, has changed since last reported by the MME/S4-SGSN. The SGW shall ignore this flag when ISR is not active. - Bit 7 – ARRL (Abnormal Release of Radio Link): if this bit is set to 1 by the MME, it indicates to the SGW that the access bearers are released due to an abnormal release of the radio link. Based on operator policy, this indication may be used by the SGW in subsequent decisions to trigger PDN charging pause if the PGW Pause of Charging feature has been enabled on that PDN connection. - Bit 6 – PPOFF (PDN Pause Off Indication): if this bit is set to 1 by the SGW, it indicates to the PGW that the charging for the PDN connection shall be unpaused. - Bit 5 – PPON (PDN Pause On Indication) / PPEI (PDN Pause Enabled Indication): if this bit is set to 1 by the SGW, it indicates to the PGW that the charging for the PDN connection shall be paused; if it is set to 1 by the PGW, it indicates that PGW enables the SGW to use the PGW Pause of Charging procedure for the PDN connection. - Bit 4 – PPSI (PDN Pause Support Indication): if this bit is set to 1 by the SGW, it indicates that the SGW supports the PGW Pause of Charging procedure; if it is set to 1 by the PGW, it indicates that the PGW supports the PGW Pause of Charging procedure. - Bit 3 – CSFBI (CSFB Indication): if this bit is set to 1, it indicates that the UE has been subject to CSFB. - Bit 2 – CLII (Change of Location Information Indication): when ISR is active if this bit is set to 1, it indicates that the location information, which is provided as a part of ULI IE, has changed since last reported by the MME/S4-SGSN. The SGW shall ignore this flag when ISR is not active. - Bit 1 – CPSR (CS to PS SRVCC indication): if this bit is set to 1, it indicates that a UTRAN/GERAN to E-UTRAN/UTRAN (HSPA) SRVCC procedure is underway and the associated message, i.e. Modify Bearer Request shall be forwarded to the PGW from the SGW as specified in 3GPP TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [43]. The following bits within Octet 9 shall indicate: - Bit 8 – NSI (NBIFOM Support Indication): if this bit is set to 1, it indicates to the PGW that the NBIFOM is supported (see clause 5.10 of 3GPP TS 23.161[ Network-Based IP Flow Mobility (NBIFOM); Stage 2 ] [71]). - Bit 7 – UASI (UE Available for Signaling Indication): if this bit is set to 1, it indicates that the UE is available for end to end signalling and that the PGW should re-attempt the pending network initiated procedure. - Bit 6 – DTCI (Delay Tolerant Connection Indication): if this bit is set to 1, it indicates that the PDN connection is delay tolerant according to the local policies in the PGW, e.g. per APN.For this PDN connection the PGW supports receiving the rejection cause "UE is temporarily not reachable due to power saving" from the MME/SGSN via the SGW during a network initiated procedure and holding the network initiated procedure, until the PGW receives the subsequent Modify Bearer Request message with the UASI flag indicating that the UE is available for end to end signalling. - Bit 5 – BDWI (Buffered DL Data Waiting Indication): if this bit is set to 1, it indicates that there is DL data buffered in the (old) SGW or (V-)SMF/UPF, i.e. that the new MME/SGSN shall invoke data forwarding if there is an SGW change as specified in clause 5.3.3.1A of 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3] or upon idle mode mobility between 5GS and EPS with data forwarding as specified in clauses 4.11.1.3.2A, 4.11.1.3.3A, 4.23.12.2a and 4.23.12.3a of 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [83], and that it shall setup the user plane in conjunction with the TAU/RAU procedure for delivery of the buffered DL data to the UE. - Bit 4 – PSCI (Pending Subscription Change Indication): If this bit is set to 1, it indicates that there is a pending report of the changed subscribed QoS profile of the related PDN connection in the old MME, so that the new MME/SGSN shall trigger the HSS Initiated Subscribed QoS Modification procedure towards the PGW. See clause 5.3.9.2 of 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3]. - Bit 3 – PCRI (P-CSCF Restoration Indication): if this bit is set to 1, it indicates a request to trigger a P-CSCF restoration for the corresponding user (see 3GPP TS 23.380[ IMS Restoration Procedures ] [61]). - Bit 2 – AOSI (Associate OCI with SGW node's Identity): if this bit is set to 1, it indicates that the SGW provided "SGW's Overload Control Information" which shall be associated with the node identity (i.e. FQDN or the IP address received from the DNS during the SGW selection) of the serving SGW. - Bit 1 – AOPI (Associate OCI with PGW node's Identity): if this bit is set to 1, it indicates that the PGW provided "PGW's Overload Control Information" which shall be associated with the node identity (i.e. FQDN or the IP address received from the HSS or DNS during the PGW selection) of the serving PGW. The following bits within Octet 10 shall indicate: - Bit 8 – ROAAI (Release Over Any Access Indication): If this bit is set to 1, it indicates to the PGW that, if this is an NB-IFOM PDN connection, the PGW shall initiate the release of the corresponding PDN connection over the non-3GPP access over the S2a/S2b interface with the cause "Local release". - Bit 7 – EPCOSI (Extended PCO Support Indication): If this bit is set to 1, it indicates to the receiver that the Extended PCO is supported, e.g. when the PGW is the receiver, it indicates that the UE, the MME and the SGW support Extended PCO; when the target MME is the receiver, during an inter-MME mobility, it indicates that UE and the source MME support Extended PCO. - Bit 6 – CPOPCI (Control Plane Only PDN Connection Indication): If this bit is set to 1, it indicates that the PDN Connection is set to Control Plane Only, i.e. the user data pertaining to this PDN connection can only be transferred in NAS PDUs via the control plane. - Bit 5 – PMTSMI (Pending MT Short Message Indication): If this bit is set to 1, it indicates to the target MME/S4-SGSN that there is one (or more) pending MT Short Message(s) in the SMS-GMSC, i.e. that the target MME/S4-SGSN shall provide its E.164 address and Diameter Identity if available to receive the MT Short message and maintain the signalling connection with the UE for a longer time to enable the retransmission of the Short Message. - Bit 4 – S11-U Tunnel Flag (S11TF): This flag shall be set to 1 on the S11 interface if user data is transported in NAS signalling. - Bit 3 – PNSI (Pending Network Initiated PDN Connection Signalling Indication): if this bit is set to 1, it indicates to the target MME/SGSN that there is pending network initiated PDN connection signalling for the PDN connection, i.e. the target MME/SGSN shall set UASI flag in the Create Session Request or Modify Bearer Request message to indicate to the PGW that the UE is available for end to end signalling. - Bit 2 – UNACCSI (UE Not Authorised Cause Code Support Indication): If this bit is set to 1, it indicates that the Cause Code for "UE not authorized by OCS or external AAA Server" is supported by the S4-SGSN/MME. - Bit 1 - WLCP PDN Connection Modification Support Indication (WPMSI): if this bit is set to 1, it indicates that the TWAN supports the WLCP PDN Connection Modification procedure. This indication is used by the P-CSCF restoration extension procedure for TWAN access (see 3GPP TS 23.380[ IMS Restoration Procedures ] [61]). The following bits within Octet 11 shall indicate: - Bit 8 – 5GSNN26 (5GS Interworking without N26 Indication): if this bit is set to 1 and the 5GS Interworking Indication (5GSIWKI) is set to 1, it indicates to the PGW-C+SMF that 5GS Interworking is supported without the N26 interface. If this bit is set to 0 and the 5GSIWKI (5GS Interworking Indication) is set to 1, it indicates to the PGW-C+SMF that 5GS Interworking is supported with the N26 interface. - Bit 7 – REPREFI (Return Preferred Indication): This flag shall be set to 1 to indicate a preferred return of the UE to the last used EPS or 5GS PLMN at a later access change to an EPS or 5GS shared network. - Bit 6 –5GSIWKI (5GS Interworking Indication): This flag shall be set to 1 for UEs supporting N1 mode and not restricted from interworking with 5GS by user subscription (see "5GC" bit within Core-Network-Restrictions AVP and Interworking-5GS-Indicator AVP specified in 3GPP TS 29.272[ Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol ] [70] and 3GPP TS 29.273[ Evolved Packet System (EPS); 3GPP EPS AAA interfaces ] [68]). - Bit 5 –EEVRSI (Extended EBI Value Range Support Indication): if this bit is set to 1, it indicates that the sending GTPv2 entity supports the 15 EPS Bearers, i.e. it supports to use EPS Bearer ID with a value between '1' and '15'. - Bit 4 –LTEMUI (LTE-M UE Indication): if this bit is set to 1, it indicates that the UE is a LTE-M UE (see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3]); - Bit 3 – LTEMPI (LTE-M RAT Type reporting to PGW Indication): if this bit is set to 1, it indicates to the SGW to forward the LTE-M RAT type to the PGW; - Bit 2 – ENBCRSI (eNB Change Reporting Support Indication): if this bit is set to 1, it indicates that the MME supports Macro eNodeB Change Reporting mechanism for the corresponding session. - Bit 1 –TSPCMI (Triggering SGSN initiated PDP Context Creation/Modification Indication): if this bit is set to 1, it indicates to the S4-SGSN that in the UE_initiated PDP Context Modification procedure, when the NBIFOM container is included, the S4-SGSN accepts the UE initiated PDP Context Modification procedure and initiates SGSN initiated PDP Context Creation/modification procedures respectively towards UE to transfer the NBIFOM container received from the PGW either in Create Bearer Request or Update Bearer Request message as specified in 3GPP TS 23.161[ Network-Based IP Flow Mobility (NBIFOM); Stage 2 ] [71]. The following bits within Octet 12 shall indicate: - Bit 8 – CSRMFI (Create Session Request Message Forwarded Indication): if this bit is set to 1, it indicates that the Create Session Request message has been forwarded by a PGW, and the receiving PGW shall include its PGW FQDN in the Create Session Response message if the creation of the PDN connection is accepted. - Bit 7 – MTEDTN (MT-EDT Not Applicable): if this bit is set to 1, it indicates that MT-EDT is not applicable for the PDN connection. - Bit 6 – MTEDTA (MT-EDT Applicable): if this bit is set to 1, it indicates that MT-EDT is applicable for the PDN connection. - Bit 5 – N5GNMI (No 5GS N26 Mobility Indication): if this bit is set to 1, it indicates that the PDN connection cannot be moved to 5GS via N26. - Bit 4 –5GCNRS (5GC Not Restricted Support): if this bit is set to 1, this indicates to the PGW-C+SMF that the sending node (i.e. MME or ePDG) supports setting the 5GCNRI flag. An MME or an ePDG compliant with this version of the specification shall support setting the 5GCNRI flag. - Bit 3 –5GCNRI (5GC Not Restricted Indication): if this bit is set to 1, this indicates to the PGW-C+SMF that access to the 5GC is not restricted for the PDN connection. If the 5GCNRS bit is set to 1 and the 5GCNRI bit is set to 0, this indicates that access to the 5GC is restricted for the PDN connection. The 5GCNRI flag shall be ignored by the PGW-C+SMF if the 5GSIWKI flag is set to 1 (i.e. 5GS Interworking is supported), except for the case noted in Note 27 in Table 7.2.1-1. - Bit 2 – 5SRHOI (5G-SRVCC HO Indication): if this bit is set to 1, it indicates the HO is used for 5G-SRVCC as specified in 3GPP TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [43]. - Bit 1 – ETHPDN (Ethernet PDN Support Indication): if this bit is set to 1, it indicates the support of Ethernet PDN Connection. The following bits within Octet 13 shall indicate: - Bit 8 – NSPUSI (Notify Start Pause of charging via User plane Support Indication): if this bit is set to 1, it indicates that the PGW-C and PGW-U support Notify Start Pause of Charging via user plane feature as specified in clause 5.30 of 3GPP TS 29.244[ Interface between the Control Plane and the User Plane nodes ] [80]. - Bit 7 – PGWRNSI (PGW Redirection due to mismatch with Network Slice subscribed by UE Support Indication): if this bit is set to 1, it indicates that the MME supports receiving a Create Session rejection response with the cause "PGW redirection due to mismatch with network slice subscribed by the UE" and to establish the PDN connection towards the Alternative PGW-C/SMF indicated in the Create Session rejection response. - Bit 6 – RPPCSI (Restoration of PDN connections after an PGW-C/SMF Change Support Indication): if this bit is set to 1, it indicates that the sending GTPv2 entity, i.e. the MME/ePDG and/or the SGW, supports the Restoration of PDN connections after an PGW-C/SMF Change procedure as specified in clause 31 of 3GPP TS 23.007[ Restoration procedures ] [17]. - Bit 5 – PGWCHI (PGW CHange Indication): if this bit is set to 1, it indicates that the Create Session Request is triggered to move an existing PDN connection to the new PGW-C/SMF as specified in clauses 31.3 and 31.3A of 3GPP TS 23.007[ Restoration procedures ] [17]. - Bit 4 – SISSME (Same IWK-SCEF Selected for Monitoring Event Indication): if this bit is set to 1, it indicates that same IWK-SCEF is selected by target MME/SGSN for Monitoring Event. - Bit 3 – NSENBI (Notify Source eNodeB Indication): if this bit is set to 1, it indicates that the source MME shall send a Handover Success to the source eNodeB (see clause 5.5.1.2.2a of 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3]). - Bit 2 – IDFUPF (Indirect Data Forwarding with UPF Indication): if this bit is set to 1, it indicates that indirect data forwarding is required for user plane routes from/to a UPF. - Bit 1 – EMCI (Emergency PDU Session Indication): if this bit is set to 1, it indicates the UE has emergency PDU session, as specified in 3GPP TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [43]. The following bits within Octet 14 shall indicate: - Bits 4 to 8: Spare, for future use and set to 0. - Bit 3 –LTEMSAI (LTE-M Satellite Access Indication): if this bit is set to 1, it indicates that the LTE-M UE is accessing Satellite E-UTRAN (see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3]); - Bit 2 –SRTPI (Satellite RAT Type reporting to PGW Indication): if this bit is set to 1, it indicates to the SGW to forward the Satellite related RAT type to the PGW; - Bit 1 – UPIPSI (User Plane Integrity Protection Support Indication): if this bit is set to 1, it indicates that the UE, MME and E-UTRAN supports User Plane Integrity Protection with EPS as specified in clause 4.11.0a.5 of 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [83]. | 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 | 8.12 |
912 | 9.9.4 Reporting of Rank Indicator (RI) | The purpose of this test for 4Rx UEs is to verify that the reported rank indicator accurately represents the channel rank. The accuracy of RI (CQI) reporting is determined by the relative increase of the throughput obtained when transmitting based on the reported rank compared to the case for which a fixed rank is used for transmission. Transmission mode 4 is used with the specified CodebookSubSetRestriction in section 9.9.4.1, transmission mode 9 is used with the specified CodebookSubSetRestriction in section 9.9.4.2. For the fixed rank 1 transmission with 2 Tx ports the RI and PMI reporting is restricted to two single-layer precoders, For fixed rank 2 transmission with 2 Tx ports the RI and PMI reporting is restricted to one two-layer precoder. For the follow RI transmission for rank 1 and 2 and 2 Tx ports the RI and PMI reporting is restricted to select the union of these precoders. For the fixed rank 2 transmission with 4 Tx ports the RI and PMI reporting is restricted to any 2 Layer precoder, for the follow RI transmission the RI and PMI reporting is not restricted at all. Channels with low and high correlation are used to ensure that RI reporting reflects the channel condition. | 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.9.4 |
913 | 9.11.3.70 Truncated 5G-S-TMSI configuration | The purpose of the Truncated 5G-S-TMSI configuration information element is to provide the size of the components of the truncated 5G-S-TMSI to the UE in NB-N1 mode to create the truncated 5G-S-TMSI. The Truncated 5G-S-TMSI configuration information element is coded as shown in figure 9.11.3.70.1 and table 9.11.3.70.1. The Truncated 5G-S-TMSI configuration is a type 4 information element with 3 octets length. Figure 9.11.3.70.1: Truncated 5G-S-TMSI configuration information element Table 9.11.3.70.1: Truncated 5G-S-TMSI configuration 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.70 |
914 | 5.4.3.4 Successful completion of the mobility from NR | Upon successfully completing the handover, at the source side the UE shall: 1> reset MAC; 1> stop all timers that are running except T325, T330 and T400; 1> release ran-NotificationAreaInfo, if stored; 1> release the AS security context including the KRRCenc key, the KRRCint key, the KUPint key and the KUPenc key, if stored; 1> release all radio resources, including release of the RLC entity and the MAC configuration; 1> release the associated PDCP entity and SDAP entity for all established RBs; NOTE : PDCP and SDAP configured by the source RAT prior to the handover that are reconfigured and re-used by target RAT when delta signalling (i.e., during inter-RAT intra-system handover when fullConfig is not present) is used, are not released as part of this procedure. 1> if the UE was configured with successHO-Config when connected to the source PCell and the targetRAT-Type is set to eutra: 2> perform the actions for the successful handover report determination as specified in clause 5.7.10.6. 1> if the targetRAT-Type is set to eutra and the nas-SecurityParamFromNR is included: or 1> if the targetRAT-Type is set to utra-fdd: 2> indicate the release of the RRC connection to upper layers together with the release cause 'other'. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.4.3.4 |
915 | 4.3 Session Management procedures 4.3.1 General | Clause 4.3 defines the Session Management related procedures. It refers to clause 4.4 for the N4 interactions. As defined in clause 5.6.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], considering the case of Home Routed PDU Session, the NAS SM information processing by SMF considers following kind of NAS SM information: - Information that both the V-SMF and H-SMF process: indication of the nature of the NAS SM signalling (e.g. PDU Session Establishment Request), PDU Session Type, Session-AMBR, UE addressing information (allocated IPv4 address, interface identifier). - Information that is not visible to the V-SMF, only processed by the H-SMF: SSC mode, Protocol Configuration Options, SM PDU DN Request Container, QoS Rule(s) and QoS Flow level QoS parameters if any for the QoS Flow(s) associated with the QoS rule(s). NOTE 1: "Information that is not visible to the V-SMF" refers to information that the V-SMF is to relay between the UE and the H-SMF (and that it can store in CDR) but that the V-SMF is not assumed to process otherwise. The NAS SM information processing split between V-SMF and H-SMF is transparent to the UE. Both V-SMF and H-SMF process information interpreted by the AMF as the PDU Session ID, the DNN, the S-NSSAI (with values for the Serving PLMN and HPLMN processed by the V-SMF and with a value for the HPLMN processed by the H-SMF). In the case of Home Routed PDU Session the H-SMF provides also the V-SMF with the IPv6 Prefix allocated to the PDU Session. NOTE 2: IPv6 Prefix allocated to the PDU Session is provided to allow the V-SMF fulfilling regulatory requirements for data storage in the visited country. In non roaming and LBO cases the SMF processes all NAS SM information. In HR roaming scenarios, in order to support SM features only requiring support from the H-SMF without impacting the V-SMF, as specified in detail in TS 29.502[ 5G System; Session Management Services; Stage 3 ] [36]: - The V-SMF transfers NAS SM information, which is not visible to the V-SMF, in a container towards the H-SMF; - The V-SMF transfers NAS SM information which it does not comprehend (unknown IEs or IEs with an unknown value not set to "reserved" according to the release to which the V-SMF complies), in a different container towards the H-SMF; - The H-SMF transfers NAS SM information which the V-SMF does not need to interpret, in one container towards the V-SMF; - The V-SMF appends unknown NAS SM information received in the N16 container at the end of the NAS SM message it sends to the UE. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3 |
916 | 5.7.7.2 Initiation | A UE capable of UL RRC message segmentation in RRC_CONNECTED will initiate the procedure when the following conditions are met: 1> if the RRC message segmentation is enabled based on the field rrc-SegAllowed, rrc-SegAllowedSRB4 or rrc-SegAllowedSRB5 received, and 1> if the encoded RRC message is larger than the maximum supported size of a PDCP SDU specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5]; Upon initiating the procedure, the UE shall: 1> initiate transmission of the ULDedicatedMessageSegment message as specified in 5.7.7.3; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.7.2 |
917 | B.6 Derivation of CK'PS || IK'PS from CKCS || IKCS | This input string is used for UMTS subscribers when there is a need to derive CK'PS || IK'PS from CKCS || IKCS during mapping the security contexts from UTRAN/GERAN to HSPA. The input parameter Key is the concatenation of CKCS || IKCS (which are 128 bits each), and the output is CK'PS ||IK'PS (which are 128 bits each). - FC = 0x33 - P0 = NONCEMSC - L0 = length of NONCEMSC (i.e. 0x00 0x10) Further, the GPRS Kc' used in GERAN shall be derived from CK'PS||IK'PS using the key conversion function c3 defined in this specification. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | B.6 |
918 | – VarLogMeasReport | The UE variable VarLogMeasReport includes the logged measurements information. VarLogMeasReport UE variable -- ASN1START -- TAG-VARLOGMEASREPORT-START VarLogMeasReport-r16 ::= SEQUENCE { absoluteTimeInfo-r16 AbsoluteTimeInfo-r16, traceReference-r16 TraceReference-r16, traceRecordingSessionRef-r16 OCTET STRING (SIZE (2)), tce-Id-r16 OCTET STRING (SIZE (1)), logMeasInfoList-r16 LogMeasInfoList-r16, sigLoggedMeasType-r17 ENUMERATED {true}, identityList-r18 CHOICE { plmn-IdentityList-r18 PLMN-IdentityList2-r16, snpn-ConfigIDList-r18 SNPN-ConfigIDList-r18 } } -- TAG-VARLOGMEASREPORT-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
919 | 8.3.1.10 IP header compression configuration | The UE shall include the IP header compression configuration IE if: - the PDU session type value of the PDU session type IE is set to "IPv4", "IPv6" or "IPv4v6"; - the UE indicates "Control Plane CIoT 5GS optimization supported" and "IP header compression for control plane CIoT 5GS optimization supported" in the 5GMM capability IE of the REGISTRATION REQUEST message; and - the network indicates "Control plane CIoT 5GS optimization supported" and "IP header compression for control plane CIoT 5GS optimization supported" in the 5GS network support feature IE of the REGISTRATION 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 | 8.3.1.10 |
920 | 6.1.3.3.3 MS initiated PDP Context Modification not accepted by the network 6.1.3.3.3.1 General | Upon receipt of a MODIFY PDP CONTEXT REQUEST message, the network may reject the MS initiated PDP context modification request by sending a MODIFY PDP CONTEXT REJECT message to the MS. The message shall contain a cause code that typically indicates one of the following: # 26: insufficient resources; # 30: activation rejected by GGSN, Serving GW or PDN GW; # 32: Service option not supported; # 37: QoS not accepted; # 41: semantic error in the TFT operation; # 42: syntactical error in the TFT operation; # 44: semantic errors in packet filter(s); # 45: syntactical errors in packet filter(s); # 48: request rejected, Bearer Control Mode violation; # 60: bearer handling not supported; or # 95 - 111: protocol errors. If upon the reception of a MODIFY PDP CONTEXT REQUEST message the network fails to re-establish the radio access bearer for a PDP context whose maximum bit rate in uplink and downlink is set to 0kbit/s, the network shall reply with a MODIFY PDP CONTEXT REJECT message with cause #26 "insufficient resources". If a TFT modification was requested and the requested TFT is not available, then the MODIFY PDP CONTEXT REJECT message shall be sent. The network shall reply with a MODIFY PDP CONTEXT REJECT message with cause #48 "request rejected, Bearer Control Mode violation", if - the selected Bearer Control Mode is 'MS/NW' and the MS requests to create a TFT for a PDP context that was established without TFT; - the selected Bearer Control Mode is 'MS/NW' and the MS requests to upgrade the QoS of a PDP context without downlink packet filters, unless uplink packet filters already exist for the PDP context and the MS requests with the same MODIFY PDP CONTEXT REQUEST message to create downlink packet filters ; - the selected Bearer Control Mode is 'MS/NW' and the MS requests to modify the QoS, but does not include a TFT with at least apacket filter identifiers to indicate which packet filters in the TFT that is associated with the QoS change; or - the selected Bearer Control Mode is 'MS/NW' and the MS requests to modify the QoS for a PDP context associated with a TFT containing packet filters established by both the MS and the network and the MS tries to modify other parameters than the bitrate parameters in the QoS profile of that PDP context. If a TFT modification was requested and the MS requests to modify or delete packet filters which were added by the network, then the MODIFY PDP CONTEXT REJECT message shall be sent. If the MS has requested to modify the QoS of a default PDP context, the network shall reply with a MODIFY PDP CONTEXT REJECT message with cause code "QoS not accepted". If the MS has requested to modify the PDP context of a LIPA PDN connection or SIPTO at the local network PDN connection, then the network shall reply with a MODIFY PDP CONTEXT REJECT message with cause code "bearer handling not supported". The TFT in the request message is checked by the network for different types of TFT IE errors as specified in subclause 6.1.3.3.4. The network may include a Back-off timer value IE in the MODIFY PDP CONTEXT REJECT message. The network shall not include the SM cause value #26 "insufficient resources" in the MODIFY PDP CONTEXT REJECT message due to APN based congestion control being active. If the Back-off timer value IE is included and the SM cause value is not #26 "insufficient resources", the network may include the Re-attempt indicator IE to indicate whether the MS is allowed to attempt a bearer resource modification procedure in the PLMN for the same in S1 mode, and whether another attempt in A/Gb and Iu mode or in S1 mode is allowed in an equivalent PLMN. Upon receipt of a MODIFY PDP CONTEXT REJECT message, the MS shall stop timer T3381 and enter the state PDP-ACTIVE. | 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 | 6.1.3.3.3 |
921 | 5.4.3.5 NAS security mode command not accepted by the UE | If the security mode command cannot be accepted, the UE shall send a SECURITY MODE REJECT message. The SECURITY MODE REJECT message contains an EMM cause that typically indicates one of the following cause values: #23: UE security capabilities mismatch; #24: security mode rejected, unspecified. Upon receipt of the SECURITY MODE REJECT message, the MME shall stop timer T3460. The MME shall also abort the ongoing procedure that triggered the initiation of the NAS security mode control procedure. Both the UE and the MME shall apply the EPS security context in use before the initiation of the security mode control procedure, if any, to protect the SECURITY MODE REJECT message and any other subsequent messages according to the rules in clauses 4.4.4 and 4.4.5. | 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.4.3.5 |
922 | 5.18 Network Sharing 5.18.1 General concepts | A network sharing architecture shall allow multiple participating operators to share resources of a single shared network according to agreed allocation schemes. The shared network includes a radio access network. The shared resources include radio resources. The shared network operator allocates shared resources to the participating operators based on their planned and current needs and according to service level agreements. In this Release of the specification, only the 5G Multi-Operator Core Network (5G MOCN) network sharing architecture, in which only the RAN is shared in 5G System, is supported. 5G MOCN for 5G System, including UE, RAN and AMF, shall support operators' ability to use more than one PLMN ID (i.e. with same or different country code (MCC) some of which is specified in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17] and different network codes (MNC)) or combinations of PLMN ID and NID. 5G MOCN supports NG-RAN Sharing with or without multiple Cell Identity broadcast as described in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]. 5G MOCN also supports the following sharing scenarios involving non-public networks, i.e.NG-RAN can be shared by any combination of PLMNs, PNI-NPNs (with CAG), and SNPNs (each identified by PLMN ID and NID). NOTE 1: PNI-NPNs (without CAG) are not explicitly listed above as it does not require additional NG-RAN sharing functionality compared to sharing by one or multiple PLMNs. In all non-public network sharing scenarios, each Cell Identity as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28] is associated with one of the following configuration options: - one or multiple SNPNs; - one or multiple PNI-NPNs (with CAG); or - one or multiple PLMNs only. NOTE 2: This allows the assignment of multiple cell identities to a cell and also allows the cell identities to be independently assigned, i.e. without need for coordination, by the network sharing partners, between PLMNs and/or non-public networks. NOTE 3: Different PLMN IDs (or combinations of PLMN ID and NID) can also point to the same 5GC. When same 5GC supports multiple SNPNs (identified by PLMN ID and NID), it is up to the operator's policy whether they are used as equivalent SNPNs for a UE. NOTE 4: There is no standardized mechanism to avoid paging collisions if the same 5G-S-TMSI is allocated to different UEs by different PLMNs or SNPNs of the shared network, as the risk of paging collision is assumed to be very low. If such risk is to be eliminated then PLMNs and SNPNs of the shared network needs to coordinate the value space of the 5G-S-TMSI to differentiate the PLMNs and SNPNs of the shared network. Figure 5.18.1-1: A 5G Multi-Operator Core Network (5G MOCN) in which multiple CNs are connected to the same NG-RAN | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.18 |
923 | 5.2.2.5.2 Namf_Location_ProvidePositioningInfo service operation | Service operation name: Namf_Location_ProvidePositioningInfo Description: Provides UE positioning information to the consumer NF. Input, Required: UE Identification (SUPI or PEI), Client Type. Input, Optional: required Location QoS instance(s), Supported GAD shapes, UE Privacy Requirements, LCS Client Identification, Deferred location type, Deferred location parameters, Notification Target address, Notification Correlation ID, Scheduled Location Time, service type, LMF ID, UE unaware indication, request for user plane reporting to an LCS Client or AF, user plane address of an LCS Client or AF, user plane security information for an LCS Client or AF, cumulative event report timer, maximum number of user plane event reports to an LCS Client or AF. Output, Required: Success/Failure indication Output, Optional: Geodetic Location, Local Location including Coordinate ID, Civic Location, Indoor/Outdoor indication, Position Methods Used, Failure Cause, achieved Location QoS Accuracy. See steps 4 and 10 of clause 6.1.1, steps 5, 14, 18 and 22 of clause 6.1.2 and steps 5 and 6 of clause 6.3.1 of TS 23.273[ 5G System (5GS) Location Services (LCS); Stage 2 ] [51], for examples of usage of this service operation. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.2.5.2 |
924 | 13.2 PDN Interworking Model of GGSN for DHCP | A DHCP relay agent shall be located in the GGSN used for interworking with the IP network as illustrated in the following figure 16b. Figure 16b: The protocol stacks for the Gi IP reference point for DHCP The DHCP relay agent relays the requests received from the DHCP client to the DHCP server(s), and the replies received from the server(s) to the corresponding client. The DHCP relay agent allows for the replies from DHCP servers to be delivered to the correct terminal, as the logical connection from the MT terminates in the GGSN, and consequently only the GGSN holds enough information to locate the DHCP client. How the DHCP relay agent identifies the MT based on the DHCP messages is out of the scope of 3GPP standardisation. DHCP provides mechanisms for user authentication and integrity protection, but does not offer any message confidentiality, therefore additional mechanisms (e.g. Ipsec tunnel) may be provided if the link towards the external network is not secure. However this is out of the scope of the present document. Apart from the particulars mentioned above, this model is basically the same as the one for interworking with IP networks described elsewhere in the present document. Using DHCP corresponds to the transparent access case as the GGSN does not take part in the functions of authentication, authorisation, address allocation, etc. | 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 | 13.2 |
925 | 5.2.5.2.3 Npcf_AMPolicyControl_UpdateNotify service operation | Service operation name: Npcf_AMPolicyControl_UpdateNotify Description: Provides to the NF Service Consumer, e.g. AMF, updated AM related Policy information for the AM Policy Association as defined in clause 6.5 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. NOTE: This notification corresponds to an implicit subscription. Inputs, Required: AM Policy Association ID. Inputs, Optional: Access and Mobility related information or indication of AM Policy Association termination. Outputs, Required: Success or failure. Outputs, Optional: None. See clause 4.16.2.2 for the usage of this service operation. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.5.2.3 |
926 | 5.5.2.2.1 UE-initiated de-registration procedure initiation | The de-registration procedure is initiated by the UE by sending a DEREGISTRATION REQUEST message (see example in figure 5.5.2.2.1). The De-registration type IE included in the message indicates whether the de-registration procedure is due to a "switch off" or not. The access type included in the message indicates whether the de-registration procedure is: a) for 5GS services over 3GPP access when the UE is registered over 3GPP access; b) for 5GS services over non-3GPP access when the UE is registered over non-3GPP access; or c) for 3GPP access, non-3GPP access or both when the UE is registered in the same PLMN over both accesses. If the UE has a valid 5G-GUTI, the UE shall populate the 5GS mobile identity IE with the valid 5G-GUTI. If the UE does not have a valid 5G-GUTI, the UE shall populate the 5GS mobile identity IE with its SUCI as follows: a) if timer T3519 is not running, generate a fresh SUCI as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24], send a DEREGISTRATION REQUEST message with the SUCI, start timer T3519 and store the value of the SUCI sent in the DEREGISTRATION REQUEST message; and b) if timer T3519 is running, send a DEREGISTRATION REQUEST message with the stored SUCI. If the UE does not have a valid 5G-GUTI and it does not have a valid SUCI, then the UE shall populate the5GS mobile identity IE with its PEI. If the de-registration request is not due to switch off and the UE is in the state 5GMM-REGISTERED or 5GMM-REGISTERED-INITIATED, timer T3521 shall be started in the UE after the DEREGISTRATION REQUEST message has been sent. The UE shall enter the state 5GMM-DEREGISTERED-INITIATED. If the UE is to be switched off, the UE shall try for a period of 5 seconds to send the DEREGISTRATION REQUEST message. During this period, the UE may be switched off as soon as the DEREGISTRATION REQUEST message has been sent. If the network indicated support for the unavailability period in the last registration procedure; and an event is triggered in the UE that would make the UE unavailable for a certain period, and: a) the use of unavailability period is not due to NR satellite access discontinuous coverage and the UE is unable to store its 5GMM and 5GSM contexts; or b) the use of unavailability period is due to NR satellite access discontinuous coverage, the UE shall include the Unavailability information IE, and set the De-registration type to "Normal de-registration" in the DEREGISTRATION REQUEST message. The UE shall start the timer T3521 and enter the state 5GMM-DEREGISTERED-INITIATED. If the UE is sending the DEREGISTRATION REQUEST message from 5GMM-IDLE mode and the UE needs to send non-cleartext IEs, the UE shall send the DEREGISTRATION REQUEST message including the NAS message container IE as described in subclause 4.4.6. The 5G-RG shall not initiate the de-registration procedure for itself until it successfully de-registers all the AUN3 devices connected to it, if any, by initiating the de-registration procedure on behalf of the AUN3 device. Figure 5.5.2.2.1.1: UE-initiated de-registration 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.5.2.2.1 |
927 | 4.2.8.5 Access to 5GC from devices that do not support 5GC NAS over WLAN access 4.2.8.5.1 General | The devices that do not support 5GC NAS signalling over WLAN access are referred to as "Non-5G-Capable over WLAN" devices, or N5CW devices for short. A N5CW device is not capable to operate as a 5G UE that supports 5GC NAS signalling over a WLAN access network, however, it may be capable to operate as a 5G UE over NG-RAN. Clause 4.2.8.5 specifies the 5GC architectural enhancements that enable N5CW devices to access 5GC via trusted WLAN access networks. A trusted WLAN access network is a particular type of a Trusted Non-3GPP Access Network (TNAN) that supports a WLAN access technology, e.g. IEEE 802.11. Not all trusted WLAN access networks support 5GC access from N5CW devices. To support 5GC access from N5CW devices, a trusted WLAN access network must support the special functionality specified below (e.g. it must support a TWIF function). When a N5CW device performs an EAP-based access authentication procedure to connect to a trusted WLAN access network, the N5CW device may simultaneously be registered to a 5GC of a PLMN or SNPN. The 5GC registration is performed by the TWIF function (see next clause) in the trusted WLAN access network, on behalf of the N5CW device. The type of EAP authentication procedure, which is used during the 5GC registration to authenticate the N5CW device, is specified in TS 33.501[ Security architecture and procedures for 5G System ] [29]. In this Release of the specification, Trusted WLAN Access for N5CW Device only supports IP PDU Session type. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.8.5 |
928 | 24.2.2 Format of ProSe Application ID Name in ProSe Application ID | The ProSe Application ID Name is composed of a string of labels. These labels represent hierarchical levels and shall be separated by dots (e.g. "Label1.Label2.Label3"). The ProSe Application ID Name shall contain at least one label. The first label on the left shall be "ProSeApp". NOTE: The hierarchical structure and the content of the ProSe Application ID Name are outside the scope of 3GPP. Any label in the ProSe Application ID Name except the first label on the left ("ProSeApp") can be wild carded. A wild card label is represented as "*", EXAMPLE: A ProSe Application ID Name used to discover nearby Italian restaurants could be "ProSeApp.Food.Restaurants.Italian". | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 24.2.2 |
929 | 5.5.2 Inter RAT handover 5.5.2.0 General | During Inter RAT handover indirect forwarding may apply for the downlink data forwarding performed as part of the handover. From its configuration data the MME knows whether indirect forwarding applies and it allocates a downlink data forwarding path on a Serving GWs for indirect forwarding. From its configuration data the S4 SGSN knows whether indirect forwarding applies and it allocates downlink data forwarding paths on Serving GWs for indirect forwarding. It is configured on MME and S4 SGSN whether indirect downlink data forwarding does not apply, applies always or applies only for inter PLMN inter RAT handovers. During the handover procedure, the source MME shall reject any PDN GW initiated EPS bearer(s) request received since handover procedure started and shall include an indication that the request has been temporarily rejected due to handover procedure in progress. The rejection is forwarded by the Serving GW to the PDN GW, with the indication that the request has been temporarily rejected. Upon reception of a rejection for an EPS bearer(s) PDN GW initiated procedure with an indication that the request has been temporarily rejected due to handover procedure in progress, the PDN GW behaves as specified in clause 5.5.1.2.1. For inter-PLMN handover to a CSG cell, if the source MME/S4-SGSN has the CSG-ID list of the target PLMN, the source MME/S4-SGSN shall use it to validate the CSG membership of the UE in the target CSG cell. Otherwise, based on operator's configuration the source MME/S4-SGSN may allow the handover by validating the CSG membership of the UE in the target CSG cell using the CSG-ID list of the registered PLMN-ID. If neither the CSG-ID list of the target PLMN nor the operator's configuration permits the handover, the source MME/S4-SGSN shall reject the handover due to no CSG membership information of the target PLMN-ID NOTE 1: Inter-PLMN handover to a CSG cell in a PLMN which is not an equivalent PLMN for the UE is not supported. NOTE 2: Inter-PLMN handover to a CSG cell of an equivalent PLMN is only supported if the CSG-ID of the cell is in the CSG-ID list of both equivalent PLMNs. NOTE 3: Upon bearer loss or UE-detected bearer QoS degradation during inter-RAT 3GPP handover, after receiving the Handover Command the UE can adopt an implementation dependent mechanism to trigger the handover of one or more PDN connections or mobility of one or more IP flows to WLAN (e.g. taking into account policies obtained from ANDSF). | 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.5.2 |
930 | 9.9.1.2.2 TDD | The following requirements apply to UE Category ≥2. For the parameters specified in table 9.9.1.2.2-1, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2, the reported offset level of the wideband spatial differential CQI for codeword #1 (Table 7.2-2 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6]) shall be used to determine the wideband CQI index for codeword #1 as wideband CQI1 = wideband CQI0 – Codeword 1 offset level The wideband CQI1 shall be within the set {median CQI1 -1, median CQI1, median CQI1 +1} for more than 90% of the time, where the resulting wideband values CQI1 shall be used to determine the median CQI values for codeword #1. For both codewords #0 and #1, the PDSCH BLER using the transport format indicated by the respective median CQI0 – 1 and median CQI1 – 1 shall be less than or equal to 0.1. Furthermore, for both codewords #0 and #1, the PDSCH BLER using the transport format indicated by the respective median CQI0 + 1 and median CQI1 + 1 shall be greater than or equal to 0.1. Table 9.9.1.2.2-1: PUCCH 1-1 submode 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.9.1.2.2 |
931 | 16.4 List of RADIUS attributes | The following tables describe the actual content of the RADIUS messages exchanged between the GGSN/P-GW and the AAA server. Other RADIUS attributes may be used as defined in RADIUS RFC(s). Unless otherwise stated, when the encoding scheme of an attribute is specified as UTF-8 encoding, this shall be interpreted as UTF-8 hexadecimal encoding. NOTE: Any digit is converted into UTF-8 character. For example, digit 5 is converted to UTF-8 character ‘5’, which in hexadecimal representation has a value 0x35. Similarly, a hexadecimal digit F is converted to either UTF-8 character ‘F’, which in hexadecimal representation has a value 0x46, or to UTF-8 character ‘f’, which in hexadecimal representation has a value 0x66. | 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 | 16.4 |
932 | 5.7.2 MME | The MME maintains MM context and EPS bearer context information for UEs in the ECM-IDLE, ECM-CONNECTED and EMM-DEREGISTERED states. Table 5.7.2-1 shows the context fields for one UE. Table 5.7.2-1: MME MM and EPS bearer Contexts The MME Emergency Configuration Data is used instead of UE subscription data received from the HSS, for all emergency bearer services that are established by an MME on UE request. Table 5.7.2-2: MME Emergency Configuration Data NOTE 1: QCI for Emergency APN's default bearer is set per operator configuration. The MME RLOS Configuration Data is used, for all RLOS PDN connection that are established by an MME on UE request instead of UE subscription data received from HSS. Table 5.7.2-3: MME RLOS Configuration Data NOTE 2: QCI and ARP for RLOS APN's default bearer is set per operator configuration. | 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.7.2 |
933 | 4.16.1.9 Number of SN terminated bearers attempted to setup at Secondary Node Additions | a) This measurement provides the number of SN terminated bearers attempted to setup at Secondary Node Additions. b) CC c) On transmission by the MN of an SgNB Addition Request message to SN,the request include SN terminated bearers. Each requested E-RAB in the message (IE E-RABs To Be Added List TS 36.423[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP) ] [10]) is added to the relevant measurement per bearer type. The sum of all supported per bearer type measurements shall equal the total number of E-RABs atttempted to setup. In case only a subset of per bearer measurements is supported, a sum subcounter will be provided first. SGNB Addition Trigger Indication (TS 36.423[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP) ] [10]) excludes SN change, inter-eNB HO, intra-eNB HO. d) Each measurement is an integer value. e) The measurement name has the form ERAB.EstabAttAtSnAddition, ERAB.EstabAttAtSnAddition.SCG, ERAB.EstabAttAtSnAddition.SCGSplit f) EUtranCellFDD EUtranCellTDD 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.16.1.9 |
934 | 6.10.3.3 Negotiation of security algorithms | The MN shall receive the UE security capabilities from the AMF or the previous NG-RAN node. These security capabilities include both LTE and NR security capabilities. When establishing one or more DRBs and/or SRBs for a UE at the SN, as shown on Figure 6.10.2.1-1, the MN shall provide the UE security capabilities of the UE to the SN in the SN Addition/Modification Request message. Upon receipt of this message, the SN shall select the algorithms with highest priority in its locally configured list of algorithms that are also present in the received UE security capabilities and include the selected algorithms in SN Addition/Modification Request Acknowledge. The MN shall provide the selected algorithms to the UE during the RRCConnectionReconfiguration procedure that configures the DRBs and/or SRB with the SN for the UE. The UE shall use the indicated algorithms for the DRBs and/or SRB whose PDCP terminates on the SN. NOTE: The algorithms that the UE uses with the MN can be the same or different to the algorithms used with the SN. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.10.3.3 |
935 | – NeedForGapNCSG-InfoNR | The IE NeedForGapNCSG-InfoNR indicates whether measurement gap or NCSG is required for the UE to perform SSB based measurements on an NR target band while NR-DC or NE-DC is not configured. NeedForGapNCSG-InfoNR information element -- ASN1START -- TAG-NEEDFORGAPNCSG-INFONR-START NeedForGapNCSG-InfoNR-r17 ::= SEQUENCE { intraFreq-needForNCSG-r17 NeedForNCSG-IntraFreqList-r17, interFreq-needForNCSG-r17 NeedForNCSG-BandListNR-r17 } NeedForNCSG-IntraFreqList-r17 ::= SEQUENCE (SIZE (1.. maxNrofServingCells)) OF NeedForNCSG-IntraFreq-r17 NeedForNCSG-BandListNR-r17 ::= SEQUENCE (SIZE (1..maxBands)) OF NeedForNCSG-NR-r17 NeedForNCSG-IntraFreq-r17 ::= SEQUENCE { servCellId-r17 ServCellIndex, gapIndicationIntra-r17 ENUMERATED {gap, ncsg, nogap-noncsg} } NeedForNCSG-NR-r17 ::= SEQUENCE { bandNR-r17 FreqBandIndicatorNR, gapIndication-r17 ENUMERATED {gap, ncsg, nogap-noncsg} } -- TAG-NEEDFORGAPNCSG-INFONR-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
936 | 10.5.6.6A SM cause 2 | The purpose of the SM cause 2 information element is to provide further information when PDP context activation initiated by the mobile station is successful. The SM cause 2 is a type 4 information element with 3 octets length. The SM cause 2 information element is coded as shown in figure 10.5.139a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.157a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.139a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : SM cause 2 information element Table 10.5.157a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : SM cause 2 information element | 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.6.6A |
937 | 10.5.4.34 Redial | The purpose of the Redial information element is to indicate to the network that a call is the result of a redial attempt to switch from speech to multimedia or vice-versa. The Redial information element is coded as shown in figure 10.5.118e/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] The Redial is a type 2 information element with a length of 1 octet. Figure 10.5.118e/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Redial information element | 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.34 |
938 | 17.5.7 Service deactivation | The multicast service deactivation is a signalling procedure that will terminate the user registration to a particular MBMS multicast service. The multicast service deactivation can be initiated by the GGSN, when indicated so by the UE, or by the BM-SC, for service specific reasons. Figure 32: MBMS Service deactivation procedure 1. The UE sends an IGMP (IPv4) or MLD (IPv6) Leave message over the default PDP context to leave a particular multicast service identified by an IP multicast address. 2. The GGSN sends a STR to the BM-SC, indicating that the UE is requesting to leave the multicast service. The session to be terminated is uniquely identified by the Diameter session-id. 3. Upon reception of the STR, the BM-SC verifies that the IP multicast address corresponds to a valid MBMS bearer service and sends a STA to the GGSN that originated the Leave Indication. The APN shall be the same that was provided during service activation (see " Service Activation" procedure). 4. Upon reception of the STA the GGSN sends an MBMS UE Context Deactivation Request to the SGSN. The IP multicast address, APN and IMSI together identify the MBMS UE Context to be deleted by the SGSN. The APN is the one received in step 3. 5. The GGSN receives a Delete MBMS Context Request (NSAPI). This GGSN may be different from the GGSN that receives IGMP Leave request in step 1. 6. The GGSN deletes the MBMS UE Context and sends a STR to the BM-SC to confirm the successful deactivation of the MBMS UE Context. 7. The BM-SC, then, deletes the MBMS UE Context and sends a confirmation to the GGSN in a STA message. 8. If the GGSN does not have any more users interested in this MBMS bearer service and the "list of downstream nodes" in the corresponding MBSM Bearer Context is empty, the GGSN initiates a De-Registration procedure as specified in 17.5.5. 9. The BM-SC confirms the operation by sending a STA message to the GGSN as specified in 17.5.5. | 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 | 17.5.7 |
939 | O.2 User-user protocol contents | The user-user protocol contents is included in the user-user information element described in subclause 10.5.4.25. The user-user protocol contents is structured like the non-imperative part of a standard L3 message (see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20], subclause 11.2) and is composed of a variable number of information elements of type 1, 2, 3 and 4. The different formats (TV, TLV) and the categories of information elements (type 1, 2, 3 and 4) are defined in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20]. Within the user-user protocol contents the information elements may occur in an arbitrary order. All information elements shall be included only once. Figure O.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] User-user information when the user-user protocol indicator is set to "3GPP capability exchange protocol" | 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 | O.2 |
940 | 24.3.3 Format of temporary identity in ProSe Application Code | The temporary identity in the ProSe Application Code is a bit string whose value is allocated by the ProSe Function. The length of the temporary identity in the ProSe Application Code is equal to: - 180 bits when the E bit of the PLMN ID in the ProSe Application Code is set to 0. - 160 bits when the E bit of the PLMN ID in the ProSe Application Code is set to 1. The temporary identity in the ProSe Application Code shall contain a metadata index to reflect the current metadata version if dynamic metadata is used when allocating the ProSe Application Code. The content, position and length of metadata index is operator specific. In this release, the MCC and the MNC of the ProSe Function that has assigned the ProSe Application Code are always included in the PLMN ID in ProSe Application Code. The length of the temporary identity in the ProSe Application Code shall always be equal to 160 bits. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 24.3.3 |
941 | 9.11.3.90 Relay key response parameters | The purpose of the relay key response parameters information element is to transport the parameters of the key response for 5G ProSe UE-to-network relay or 5G ProSe UE-to-UE relay as specified in 3GPP TS 33.503[ Security Aspects of Proximity based Services (ProSe) in the 5G System (5GS) ] [56]. The relay key response parameters information element is coded as shown in figure 9.11.3.90.1 and table 9.11.3.90.1. The relay key response parameters is a type 6 information element. Figure 9.11.3.90.1: Relay key response parameters information element Table 9.11.3.90.1: Relay key response parameters 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.90 |
942 | 4.22.9.5 Registration procedures for non-3GPP access path switching | If the UE supports non-3GPP access path switching and the AMF indicates that the network supports non-3GPP access path switching as described in clause 4.22.2, the UE may trigger a Mobility Registration Update via a new non-3GPP access to switch traffic from an old non-3GPP access (i.e. TNGF or N3IWF) to the new non-3GPP access (i.e. TNGF or N3IWF) if the PLMN of the selected new non-3GPP access is the same PLMN of the old non-3GPP access. The UE may trigger non-3GPP path switching if the AMF indicated support during registration as described in clause 4.22.9.1, even if the SMF did not indicate support to the UE during the MA PDU Session Establishment. In this case the Registration procedure described in clause 4.22.9.1 applies with the differences and clarifications described in this clause: Figure 4.22.9.5-1: Mobility Registration procedure for non-3GPP access path switching 1. This is the same as step 1 in clause 4.22.9.1, with the following additions: - If the UE wants to switch the user plane from an old non-3GPP access to a new non-3GPP access where the Mobility Registration Update is sent, the UE indicates PDU Session ID(s) of the PDU Session(s) in the List Of PDU Sessions To Be Activated. This may include both PDU Session ID(s) corresponding to MA PDU Sessions and single access PDU Sessions. NOTE 1: The PDU Sessions that are not indicated in the List Of PDU Sessions To Be Activated by the UE are not released but deactivated during the switching procedure. The UE or network can re-activate user plane resources by triggering Service Request procedure after non-3GPP path switching is completed. The UE may also provide an ("Non-3GPP access path switching while using old AN resources") indication in the Registration Request to indicate that the UP connection(s) via the old non-3GPP access can still be used for the MA PDU Session(s) during the Registration procedure. If the UP connection(s) via the old non-3GPP access cannot be used by the UE during the Registration procedure, the UE shall not provide a "Non-3GPP access path switching while using old AN resources" indication. The UE shall not perform non-3GPP access path switching if the PLMN of the selected new non-3GPP access is different from the PLMN of the old non-3GPP access. 2. This is the same as step 2 in Figure 4.2.2.2.2-1. 3. This is the same as step 3 in Figure 4.2.2.2.2-1 with the following additions: - If the UE provided an ("Non-3GPP access path switching while using old AN resources") indication in step 1 and the AMF supports to maintain two N2 connections for non-3GPP access during the Registration procedure and the SMF supports non-3GPP access path switching, the AMF delays the release of the old N2 connection until the UP connection via the new non-3GPP access is established. Otherwise, the AMF may trigger AN release towards the old non-3GPP access before proceeding with the Registration procedure in the new non-3GPP access, as described in clause 4.12.4.2 for untrusted non-3GPP access and clause 4.12a.4.2 for trusted non-3GPP access with the following clarifications: - During the AN release procedure, the AMF should notify the SMF to release the UP resources for the activated PDU Sessions before sending the N2 UE Context Release Command to the old non-3GPP access. - Due to pending downlink data in the UPF, the SMF may requests to establish user plane resources before non-3GPP path switching is finished. In this case, the AMF may reject the request with an indication that the Namf_Communication_N1N2MessageTransfer has been temporarily rejected. Upon reception of an Namf_Communication_N1N2MessageTransfer response with an indication that its request has been temporarily rejected, the SMF shall start a locally configured guard timer and wait for any message to come from an AMF. Upon reception of a message from an AMF, the SMF shall re-invoke the Namf_Communication_N1N2MessageTransfer (with N2 SM info and/or N1 SM info) to the AMF. 4. This is the same as steps 4-16 in Figure 4.2.2.2.2-1. 5-11. These steps are the same as step 17 in clause 4.22.9.1, with the following additions: - If the Registration procedure is triggered to switch traffic from the old non-3GPP access to the new non-3GPP access and the UE provided an ("Non-3GPP access path switching while using old AN resources") indication in step 1, the AMF, if it supports maintaining two N2 connections for non-3GPP access, forwards this indication to the SMF in case the PDU Session is a MA PDU Session. If the SMF receives this indication, the SMF does not trigger release of the UP connection in the old non-3GPP access towards the old N3IWF or TNGF (if any). - In step 7 and 8, the CN Tunnel Info is sent from SMF to the new non-3GPP AN via AMF. The IPSec child SA(s) between UE and the new non-3GPP AN are established. - In step 10, the SMF updates the N4 rules by replacing the AN Tunnel Info of the old non-3GPP AN with the AN Tunnel Info of the new non-3GPP AN to instruct the UPF to switch traffic from the old non-3GPP access path to the new non-3GPP access path. NOTE 2: The resource in the old non-3GPP access, i.e. the old N3IWF or TNGF, will in this case be released by the AMF in step 12. - After the UP connection via the new non-3GPP access is established, the UE and UPF start to send traffic via the new non-3GPP access. 12. After the UP connection has been established in new non-3GPP access, the AMF also triggers AN release towards the old non-3GPP access (i.e. old N3IWF or TNGF), unless done previously with following clarifications: - For the PDU Sessions indicated by the old non-3GPP access in the "List of PDU Session ID(s) with active N3 user plane" but not in the List Of PDU Sessions To Be Activated sent by the UE in step 1, the AMF requests the SMF to deactivate the PDU Session(s). For other PDU Sessions, the AMF shall not request the SMF to deactivate the PDU Session(s). - When the UE receives Registration Accept over the new non-3GPP access, the UE considers that the UE is deregistered from the old non-3GPP access. NOTE 3: In order to support RAT restrictions for non-3GPP access in the above procedure, it is assumed that UDM has provided restricted non-3GPP RAT types, if any, in the RAT restriction parameter in AM subscription data. In order to ensure that RAT restrictions are not violated in case the PDU Session is established in LBO roaming scenarios, the AMF in VPLMN may be configured to not indicate support for non-3GPP access path switching for inbound roaming UEs during MA PDU Session Establishment towards a SMF in VPLMN, unless it has been agreed in roaming agreements that non-3GPP access path switching can be supported for such UEs. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.22.9.5 |
943 | 6.2.2 Composition of IMEISV | The International Mobile station Equipment Identity and Software Version Number (IMEISV) is composed as shown in figure 11. Figure 11: Structure of IMEISV The IMEISV is composed of the following elements (each element shall consist of decimal digits only): - Type Allocation Code (TAC). Its length is 8 digits; - Serial Number (SNR) is an individual serial number uniquely identifying each equipment within each TAC. Its length is 6 digits; - Software Version Number (SVN) identifies the software version number of the mobile equipment. Its length is 2 digits. Regarding updates of the IMEISV: The security requirements of 3GPP TS 22.016[ International Mobile station Equipment Identities (IMEI) ] [32] apply only to the TAC and SNR, but not to the SVN part of the IMEISV. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.2.2 |
944 | 7.2.6 Bearer Resource Failure Indication | A Bearer Resource Failure Indication shall be sent by the PGW to an SGW and forwarded to the MME to indicate failure of the UE requested bearer resource allocation procedure or UE requested bearer resource modification procedure, as specified by 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [23]. The message shall also be sent by a PGW to an SGW and forwarded to an SGSN as part of the failure of an MS initiated PDP Context modification procedure or secondary PDP context activation procedure. The message shall also be sent on the S5/S8 or S2a/S2b interface by a PGW to a SGW or to a TWAN/ePDG and the S11/S4 interface by a SGW to an MME/S4-SGSN as part of the UE-initiated IP flow mobility procedure and the UE requested IP flow mapping procedure, as specified by 3GPP TS 23.161[ Network-Based IP Flow Mobility (NBIFOM); Stage 2 ] [71]. Table -1 specifies the presence of the IEs in the message. Possible Cause values are specified in Table 8.4-1. Message specific cause values are: - "Semantic error in the TAD operation". - "Syntactic error in the TAD operation". - "Semantic errors in packet filter(s)". - "Syntactic errors in packet filter(s)". - "Collision with network initiated request". - "Service denied". - "Bearer handling not supported". - "UE context without TFT already activated". Table -1: Information Elements in a Bearer Resource Failure Indication Table 7.2.6-2: Overload Control Information within Bearer Resource Failure Indication | 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 | 7.2.6 |
945 | 8.15.1.1 Broadcast MBS Session Setup | Figure 8.15.1.1-1 illustrates an exemplified interaction of NGAP, E1AP, F1AP and RRC protocol functions at Broadcast MBS Session Setup. Figure 8.15.1.1-1: Broadcast MBS Session Setup 1. The 5GC starts the broadcast session by sending the NGAP Broadcast Session Setup Request message to the gNB containing the TMGI, S-NSSAI, 5G QoS Profile, area information and transport information (for NG-U multicast transport it provides the IP multicast address and the IP source specific multicast address). 2/3. The gNB-CU-CP sets up the broadcast bearer context, providing NG-U transport information from the 5GC to the gNB-CU-UP and receiving from the gNB-CU-UP the NG-U GTP DL TEID in case NG-U unicast transport was selected and an F1-U GTP UL TEID per MRB. 4. In case of NG-U multicast transport, the gNB-CU-UP joins the NG-U multicast group. 5/6. The gNB-CU-CP establishes the Broadcast MBS Session Context at the gNB-DU, providing MRB configuration, other relevant session parameters and F1-U GTP UL TEID information, and receiving F1-U GTP DL TEID information. 7/8. The gNB-CU-CP triggers BC Bearer Context Modification Request towards the gNB-CU-UP to provide the F1-U GTP DL TEID information. 9. The gNB-DU configures broadcast resources and provides broadcast configuration information to the UEs by means of MCCH. 10. The gNB-CU CP successfully terminates the NGAP broadcast Session Setup procedure. In case the gNB has chosen NG-U unicast transport, NG-U GTP DL TEID information is provided to the 5GC. 11. The broadcast MBS media stream is provided to the UEs. On NG-U, in case of location dependent broadcast MBS Sessions, multiple shared NG-U transport tunnels may need to be setup, one per Area Session ID served by the gNB. In case of shared NG-U termination, - the gNB-CU-UP may provide the gNB-CU-CP at E1 setup or configuration update about established shared NG-U terminations, indicated by one or several MBS Session IDs. - at establishment of the BC bearer context in the gNB-CU-UP, the gNB-CU-CP may request the gNB-CU-UP to either apply the available MRB configuration of the shared NG-U termination, or to apply the MRB configuration requested by the gNB-CU-CP. The gNB-CU-UP provides the MRB configuration to the gNB-CU-CP if the MRB configuration requested by the gNB-CU-CP and the available MRB configuration of the shared NG-U termination are different. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.15.1.1 |
946 | 5.5.1 Generation of the reference signal sequence | Reference signal sequence is defined by a cyclic shift of a base sequence according to where - is the length of the reference signal sequence, , is defined in clause 5.5.2.1.2, and, - when either - 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 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, and - otherwise. Multiple reference signal sequences are defined from a single base sequence through different values of . Base sequences are divided into groups, where is the group number and is the base sequence number within the group, such that each group contains one base sequence () of each length , and two base sequences () of each length , . The sequence group number and the number within the group may vary in time as described in clauses 5.5.1.3 and 5.5.1.4, respectively. The definition of the base sequence depends on the sequence length. | 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.1 |
947 | 5.17.5.3 Availability or expected level of a service API | A service related with common north-bound API may become unavailable due to UE being served by a CN node not supporting the service. If the availability or expected level of support of a service API associated with a UE changes, for example due to a mobility between 5GC and EPC, the AF shall be made aware of the change. NOTE 1: If CAPIF is supported and the service APIs become (un)available for the 5GC or EPC network, the AF obtains such information from the CAPIF core function. If the SCEF+NEF receives the subscription request from the AF for the availability or expected level of support of a service API, the SCEF+NEF subscribes a CN Type Change event for the UE or Group of UEs to the HSS+UDM. If the HSS+UDM receives the subscription for CN Type Change event, the HSS+UDM includes the latest CN type for the UE or Group of UEs in the response for the subscription. If the HSS+UDM detects that the UE switches between being served by the MME and the AMF, the CN Type Change event is triggered, and the HSS+UDM notifies the latest CN type for the UE or Group of UEs to the SCEF+NEF. Based on the CN type information, the SCEF+NEF can determine the availability or expected level of support of a given service. The AF will be informed of such information via a subscription/notification service operation. The AF can subscribe for the availability or expected level of support of a service API with report type indicating either One-time report or Continuous report. If there is no CN type information for the UE in the SCEF+NEF, the SCEF+NEF subscribes monitoring event for a new CN Type Change event for the UE or Group of UEs to the HSS+UDM, otherwise, SCEF+NEF determines the CN type locally in the following conditions: - If the AF subscribes with report type indicating One-time report, the SCEF+NEF may consider the Freshness Timer of the latest CN type information for the UE or Group of UEs. The Freshness Timer is a parameter that is configured based on local SCEF+NEF policy. When a subscription request with One-time report type is received the SCEF+NEF checks if there is the latest CN type information received from the HSS+UDM for the indicated UE ID or External Group ID. If the elapsed time for the CN type information since the last reception is less than the Freshness Timer, then the SCEF+NEF may respond to the AF with the latest CN type information in order to avoid repeated query to HSS+UDM. - The SCEF+NEF has established a direct connection with MME or AMF or SMF. When the UE or all members of a Group of UEs are being served by a MME, EPC is determined as CN type. When the UE or all members of a Group of UEs are being served by an AMF, 5GC is determined as CN type. When the UE is registered both in EPC and 5GC, or some members of a Group of UEs are registered in EPC while some members are registered in 5GC, 5GC+EPC is determined as CN type. NOTE 2: If 5GC+EPC is determined as the CN type serving the UE or the group of UEs, the SCEF+NEF determines that service APIs for both 5GC and EPC are available to the UE or the group of UEs. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.17.5.3 |
948 | 13.4.1.1A Service access authorization in interconnect scenarios | In the inter-PLMN interconnect scenario, OAuth 2.0 roles are as follows: a. The NF Service Consumer's Network Repository Function (cNRF) shall be the OAuth 2.0 Authorization server for the PLMN of the NF Service Consumer (cPLMN) and authenticates the NF Service Consumer. b. The NF Service Producer's Network Repository Function (pNRF) shall be OAuth 2.0 Authorization server for the PLMN of the NF Service Producer (pPLMN) and generates the access token. c. The NF Service Consumer in the cPLMN shall be the OAuth 2.0 client. d. The NF Service Producer in the pPLMN shall be the OAuth 2.0 resource server. As an example of the inter-PLMN interconnect use case, service access authorization in the roaming scenario where the service consumer NF is located in the visiting PLMN and the service producer NF is located in the home PLMN is specified in clause 13.4.1.2. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.4.1.1A |
949 | 9.3.9.2 Facility (mobile station to network direction) | This message is sent by the mobile station to the network to request or acknowledge a supplementary service. The supplementary service to be invoked and its associated parameters are specified in the facility information element. See table 9.62b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: FACILITY Significance: local (note 1) Direction: mobile station to network Table 9.62b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : FACILITY message content (mobile station to network direction) NOTE 1: This message has local significance; however, it may carry information of global significance. NOTE 2: The facility information element has no upper length limit except that given by the maximum number of octets in a L3 message, see 3GPP TS 44.006[ None ] [19]. | 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.9.2 |
950 | 4.20.2 UE Parameters Update via UDM Control Plane Procedure | Figure 4.20.2-1: UE Parameters Update via UDM Control Plane Procedure 1. UDM decides to perform UE parameter update. 2. From UDM to the AMF: The UDM notifies the changes of the information related to the UE to the affected AMF by the means of invoking Nudm_SDM_Notification service operation. The Nudm_SDM_Notification service operation contains the UDM Update Data that needs to be delivered transparently to the UE over NAS within the Access and Mobility Subscription data. The UDM Update Data includes: - The updated parameters to be delivered to the UE (see clause 4.20.1 for parameters possible to deliver). - whether the UE needs to send an ack to the UDM. - whether the UE needs to re-register after updating the data. If the UE parameter update is performed due to "Routing Indicator update data" and the updated Routing Indicator value is not supported by the UDM where the AMF is currently registered, the UDM shall request the UE to re-register after updating the data. 3. From AMF to UDM: If AMF determines that the UE is not reachable, then AMF invokes the Nudm_SDM_Info service operation to UDM indicating that the transmission of UE Parameters Update data is not successful. The UDM considers the procedure as UE Parameters Update procedure as pending and subsequent steps from 4-7 are skipped. 4. From AMF to the UE: the AMF sends a DL NAS TRANSPORT message to the served UE. The AMF includes in the DL NAS TRANSPORT message the transparent container received from the UDM. The UE verifies based on mechanisms defined in TS 33.501[ Security architecture and procedures for 5G System ] [15] that the UDM Update Data is provided by HPLMN, SNPN, or CH; and: - If the security check on the UDM Update Data is successful, as defined in TS 33.501[ Security architecture and procedures for 5G System ] [15] the UE either stores the information and uses those parameters from that point onwards, or forwards the information to the USIM; and - If the security check on the UDM Update Data fails, the UE discards the contents of the UDM Update Data. 5. The UE to the AMF: If the UE has verified that the UDM Update Data is provided by HPLMN, SNPN, or CH and the UDM has requested the UE to send an ack to the UDM, the UE sends an UL NAS TRANSPORT message to the serving AMF with a transparent container including the UE acknowledgement. 6. The AMF to the UDM: If the AMF receives an UL NAS TRANSPORT message with a transparent container carrying a UE acknowledgement from the UE, the AMF sends a Nudm_SDM_Info request message including the transparent container to the UDM. 6a. If the UE parameter update is performed due to "Routing Indicator update data", the updated Routing Indicator value is also supported by the UDM where the AMF is currently registered and the UDM requests the UE to send an ack but does not request the UE to re-register, then upon reception of the transparent container indicating the acknowledgement of successful reception, the UDM shall trigger a Nudm_SDM_Notification service operation to update the UE Context in the AMF with the updated Routing Indicator Data (e.g. to avoid transmitting an outdated Routing Indicator on UE context transfer to another AMF). The UDM shall also notify other NFs registered in UDM (i.e. SMF and SMSF) about the update of the Routing Indicator value assigned to the SUPI using the Nudm_SDM_Notification service operation. 7. If the UDM has requested the UE to re-register, the UE waits until it goes back to RRC_IDLE and initiates a Registration procedure as defined in 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.20.2 |
951 | 5.31.7.2.4 Paging for extended DRX for RRC_INACTIVE in NR connected to 5GC | For NR, the NG-RAN may request the CN to handle mobile terminated (MT) communication for the UE configured with eDRX for RRC_INACTIVE state by means of the Connection Inactive procedure with CN based MT communication handling Procedure (see clause 4.8.1.1a of TS 23.502[ Procedures for the 5G System (5GS) ] [3]). This allows the CN to apply high latency communication functions as specified in clause 5.31.8. The NG-RAN provides the determined eDRX values (i.e. the eDRX cycle length and the Paging Time Window length) for RRC_INACTIVE to AMF (i.e. >10.24s). Based on the request from NG-RAN, the AMF responds to NG-RAN and informs other NFs (e.g. SMF and UPF) involved in downlink data or signalling handling and trigger the data buffering as specified in clause 4.8.1.1a of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. When MT data or signalling arrives for a UE in RRC_INACTIVE state, the other NFs communicate with the AMF for delivery of MT data or signalling. The AMF calculates the UE reachability based on the eDRX values for RRC_INACTIVE state provided by NG-RAN and triggers NG-RAN paging via an N2 RAN Paging Request message if the UE is considered reachable as specified in clause 4.8.2.2b of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. Otherwise, the AMF stores the information received in the NF request and replies to the requesting NF to apply high latency communication functions as specified in clause 5.31.8 based on eDRX values for RRC_INACTIVE (e.g. an Estimated Maximum Wait Time is calculated based on eDRX values for RRC_INACTIVE). When the AMF determines that the UE has become reachable for paging, the AMF uses the stored information to send an N2 RAN Paging Request message. If UPF/SMF provides the downlink data size information, the AMF provides the information to NG-RAN as described in clause 4.8.2.2b of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. When the UE resumes the RRC connection as specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27] (e.g. including mobile originated small data transmission procedure), if the NG-RAN had sent the indication for the CN to handle mobile terminated (MT) communication, NG-RAN proceeds as specified in clause 4.8.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], which indicates to the AMF that the UE is now reachable for downlink data and/or signalling. The AMF then informs other NFs that the UE is now reachable using the high latency communication functions as specified in clause 5.31.8 and MT data and signalling can be delivered to the UE. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.31.7.2.4 |
952 | 4.1 Frame structure type 1 | Frame structure type 1 is applicable to both full duplex and half duplex FDD only. Each radio frame is long and consists of 10 subframes of length , numbered from 0 to 9. Subframe in frame has an absolute subframe number where is the system frame number. For subframes using , , or , subframe is defined as two slots, and , of length each. For subframes using , subframe is defined as one slot, , of length . For transmissions using , a slot has a length of 92160. There are 13 slots, numbered in increasing order from 0 to 12, in a 40 ms period starting at with slot 0 starting at in the 40 ms period. For subframes using , the subframe can further be divided into six subslots according to Table 4.1-1. Downlink subslot pattern 1 is applied if the number of symbols used for PDCCH is equal to 1 or 3 and downlink subslot pattern 2 is applied if the number of symbols used for PDCCH is equal to 2. For system bandwidths , subslot transmission is not supported in case 4 symbols used for PDCCH. For FDD, 10 subframes, 20 slots, or up to 60 subslots are available for downlink transmission and 10 subframes, 20 slots, or up to 60 subslots are available for uplink transmissions in each 10 ms interval. Uplink and downlink transmissions are separated in the frequency domain. In half-duplex FDD operation, the UE cannot transmit and receive at the same time while there are no such restrictions in full-duplex FDD. Figure 4.1-1: Frame structure type 1 (assuming ). Table 4.1-1: SC-FDMA/OFDM symbols in different subslots of subframe i | 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 | 4.1 |
953 | 4.3.3.1 Non-roaming architecture | Figure 4.3.3-1 represents the non-roaming architecture for interworking between 5GC via non-3GPP access and EPC/E-UTRAN. Figure 4.3.3.1-1: Non-roaming architecture for interworking between 5GC via non-3GPP access and EPC/E-UTRAN NOTE 1: There can be another UPF (not shown in the figure above) between the N3IWF/TNGF and the UPF + PGW-U, i.e. the UPF + PGW-U can support N9 towards an additional UPF, if needed. NOTE 2: N26 interface is not precluded, but it is not shown in the figure because it is not required for the interworking between 5GC via non-3GPP access and EPC/E-UTRAN. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.3.1 |
954 | – FeatureSetCombinationId | The IE FeatureSetCombinationId identifies a FeatureSetCombination. The FeatureSetCombinationId of a FeatureSetCombination is the position of the FeatureSetCombination in the featureSetCombinations list (in UE-NR-Capability or UE-MRDC-Capability). The FeatureSetCombinationId = 0 refers to the first entry in the featureSetCombinations list (in UE-NR-Capability or UE-MRDC-Capability). NOTE: The FeatureSetCombinationId = 1024 is not used due to the maximum entry number of featureSetCombinations. FeatureSetCombinationId information element -- ASN1START -- TAG-FEATURESETCOMBINATIONID-START FeatureSetCombinationId ::= INTEGER (0.. maxFeatureSetCombinations) -- TAG-FEATURESETCOMBINATIONID-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
955 | 6.4 UE Rx – Tx time difference related measurements | a) This measurement provides a bin distribution (histogram) of the periodical E-UTRAN UE Rx–Tx time difference measurements received from all of UEs in the measured E-UTRAN cell. To collect this measurement, the eNodeB needs to trigger the periodical UE measurement reports towards all of the UEs in the measured E-UTRAN cell. b) CC c) Receipt by the eNodeB from the UE of MeasurementReport message indicating a periodical UE measurement report where IE MeasResults field includes ue-RxTxTimeDiffResult. The event triggered MeasurementReport messages are excluded. This measurement shall be increased for each reported value RX-TX_TIME_DIFFERENCE (See in 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [18]). For every 5 or 20 or 100 or 524 RX-TX_TIME_DIFFERENCEs a separate measurement is defined. (See in 3GPP TS 36.133[ Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management ] [19]) d) Each measurement is an integer value. e) MR.RxTxTimeDiff.y y is an integer from 00 to 47 Note: 00 of y indicates from RX-TX_TIME_DIFFERENCE_0000 to RX-TX_TIME_DIFFERENCE_0004, namely 0 Ts TUE Rx-Tx< 10 Ts, … 19 of y indicates from RX-TX_TIME_DIFFERENCE_0095 to RX-TX_TIME_DIFFERENCE_0099, namely 190Ts TUE RX-TX< 200 Ts, 20 of y indicates from RX-TX_TIME_DIFFERENCE_0100 to RX-TX_TIME_DIFFERENCE_0119, namely 200Ts TUE RX-TX< 240 Ts, … 39 of y indicates from RX-TX_TIME_DIFFERENCE_0480 to RX-TX_TIME_DIFFERENCE_0499, namely 960Ts TUE RX-TX< 1000 Ts, 40 of y indicates from RX-TX_TIME_DIFFERENCE_0500 to RX-TX_TIME_DIFFERENCE_0599, namely 1000Ts TUE RX-TX< 1200 Ts, … 44 of y indicates from RX-TX_TIME_DIFFERENCE_0900 to RX-TX_TIME_DIFFERENCE_0999, namely 1800Ts TUE RX-TX< 2000 Ts, 45 of y indicates from RX-TX_TIME_DIFFERENCE_1000 to RX-TX_TIME_DIFFERENCE_1523, namely 2000Ts TUE RX-TX< 3048 Ts, 46 of y indicates from RX-TX_TIME_DIFFERENCE_1524 to RX-TX_TIME_DIFFERENCE_2047, namely 3048 Ts TUE RX-TX< 4096 Ts, 47 of y indicates from RX-TX_TIME_DIFFERENCE_2048 to RX-TX_TIME_DIFFERENCE_4095, namely 4096 Ts TUE RX-TX (See in 3GPP TS36.133[ Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management ] [20]) f) EUtranCellTDD EUtranCellFDD 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 | 6.4 |
956 | 9.1.1 Physical channels | A sidelink physical channel corresponds to a set of resource elements carrying information originating from higher layers and is the interface defined between TS 36.212[ Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding ] [3] and the present document TS 36.211[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation ] . The following sidelink physical channels are defined: - Physical Sidelink Shared Channel, PSSCH - Physical Sidelink Control Channel, PSCCH - Physical Sidelink Discovery Channel, PSDCH - Physical Sidelink Broadcast Channel, PSBCH Generation of the baseband signal representing the different physical sidelink channels is illustrated in Figrue 5.3-1. | 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 | 9.1.1 |
957 | – RRCReconfigurationSidelink | The RRCReconfigurationSidelink message is the command to AS configuration of the PC5 RRC connection. It is only applied to unicast of NR sidelink communication. Signalling radio bearer: SL-SRB3 RLC-SAP: AM Logical channel: SCCH Direction: UE to UE RRCReconfigurationSidelink message -- ASN1START -- TAG-RRCRECONFIGURATIONSIDELINK-START RRCReconfigurationSidelink ::= SEQUENCE { rrc-TransactionIdentifier-r16 RRC-TransactionIdentifier, criticalExtensions CHOICE { rrcReconfigurationSidelink-r16 RRCReconfigurationSidelink-r16-IEs, criticalExtensionsFuture SEQUENCE {} } } RRCReconfigurationSidelink-r16-IEs ::= SEQUENCE { slrb-ConfigToAddModList-r16 SEQUENCE (SIZE (1..maxNrofSLRB-r16)) OF SLRB-Config-r16 OPTIONAL, -- Need N slrb-ConfigToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofSLRB-r16)) OF SLRB-PC5-ConfigIndex-r16 OPTIONAL, -- Need N sl-MeasConfig-r16 SetupRelease {SL-MeasConfig-r16} OPTIONAL, -- Need M sl-CSI-RS-Config-r16 SetupRelease {SL-CSI-RS-Config-r16} OPTIONAL, -- Need M sl-ResetConfig-r16 ENUMERATED {true} OPTIONAL, -- Need N sl-LatencyBoundCSI-Report-r16 INTEGER (3..160) OPTIONAL, -- Need M lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension RRCReconfigurationSidelink-v1700-IEs OPTIONAL } RRCReconfigurationSidelink-v1700-IEs ::= SEQUENCE { sl-DRX-ConfigUC-PC5-r17 SetupRelease { SL-DRX-ConfigUC-r17 } OPTIONAL, -- Need M sl-LatencyBoundIUC-Report-r17 SetupRelease { SL-LatencyBoundIUC-Report-r17 } OPTIONAL, -- Need M sl-RLC-ChannelToReleaseListPC5-r17 SEQUENCE (SIZE (1..maxSL-LCID-r16)) OF SL-RLC-ChannelID-r17 OPTIONAL, -- Need N sl-RLC-ChannelToAddModListPC5-r17 SEQUENCE (SIZE (1..maxSL-LCID-r16)) OF SL-RLC-ChannelConfigPC5-r17 OPTIONAL, -- Need N nonCriticalExtension RRCReconfigurationSidelink-v1800-IEs OPTIONAL } RRCReconfigurationSidelink-v1800-IEs ::= SEQUENCE { sl-SFN-DFN-Offset-r18 SetupRelease { SL-SFN-DFN-Offset-r18 } OPTIONAL, -- Need M sl-CarrierToAddModList-r18 SEQUENCE (SIZE (1..maxNrofFreqSL-1-r18)) OF SL-CarrierConfig-r18 OPTIONAL, -- Need N sl-CarrierToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofFreqSL-1-r18)) OF SL-CarrierId-r18 OPTIONAL, -- Need N sl-RLC-BearerToAddModList-r18 SEQUENCE (SIZE(1..maxNrofSLRB-r16)) OF SL-RLC-BearerConfig-r18 OPTIONAL, -- Need N sl-RLC-BearerToReleaseList-r18 SEQUENCE (SIZE(1..maxNrofSLRB-r16)) OF SL-RLC-BearerConfigIndex-r18 OPTIONAL, -- Need N sl-LocalID-PairToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-DestinationIdentity-r16 OPTIONAL, -- Need N sl-LocalID-PairToAddModList-r18 SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-SRAP-ConfigPC5-r18 OPTIONAL, -- Need N nonCriticalExtension SEQUENCE {} OPTIONAL } SL-CarrierConfig-r18 ::= SEQUENCE { sl-Carrier-Id-r18 SL-CarrierId-r18, sl-OffsetToCarrier-r18 INTEGER (0..2199), sl-AbsoluteFrequencyPointA-r18 ARFCN-ValueNR OPTIONAL -- Need R } SL-CarrierId-r18 ::= INTEGER (0..maxNrofFreqSL-1-r18) SL-RLC-BearerConfig-r18 ::= CHOICE { srb SEQUENCE { sl-SRB-IdentityWithDuplication INTEGER (1..3), sL-RLC-BearerConfigIndex-r18 SL-RLC-BearerConfigIndex-r18, ... }, drb SEQUENCE { slrb-PC5-ConfigIndex-r18 SLRB-PC5-ConfigIndex-r16, sL-RLC-BearerConfigIndex-r18 SL-RLC-BearerConfigIndex-r18, sl-RLC-ConfigPC5-r18 SL-RLC-ConfigPC5-r16 OPTIONAL, -- Need M sl-MAC-LogicalChannelConfigPC5-r18 SL-LogicalChannelConfigPC5-r16 OPTIONAL, -- Need M ... } } SL-RLC-BearerConfigIndex-r18 ::= INTEGER (1..maxSL-LCID-r16) SL-LatencyBoundIUC-Report-r17::= INTEGER (3..160) SLRB-Config-r16::= SEQUENCE { slrb-PC5-ConfigIndex-r16 SLRB-PC5-ConfigIndex-r16, sl-SDAP-ConfigPC5-r16 SL-SDAP-ConfigPC5-r16 OPTIONAL, -- Need M sl-PDCP-ConfigPC5-r16 SL-PDCP-ConfigPC5-r16 OPTIONAL, -- Need M sl-RLC-ConfigPC5-r16 SL-RLC-ConfigPC5-r16 OPTIONAL, -- Need M sl-MAC-LogicalChannelConfigPC5-r16 SL-LogicalChannelConfigPC5-r16 OPTIONAL, -- Need M ... } SLRB-PC5-ConfigIndex-r16 ::= INTEGER (1..maxNrofSLRB-r16) SL-SDAP-ConfigPC5-r16 ::= SEQUENCE { sl-MappedQoS-FlowsToAddList-r16 SEQUENCE (SIZE (1.. maxNrofSL-QFIsPerDest-r16)) OF SL-PQFI-r16 OPTIONAL, -- Need N sl-MappedQoS-FlowsToReleaseList-r16 SEQUENCE (SIZE (1.. maxNrofSL-QFIsPerDest-r16)) OF SL-PQFI-r16 OPTIONAL, -- Need N sl-SDAP-Header-r16 ENUMERATED {present, absent}, ... } SL-PDCP-ConfigPC5-r16 ::= SEQUENCE { sl-PDCP-SN-Size-r16 ENUMERATED {len12bits, len18bits} OPTIONAL, -- Need M sl-OutOfOrderDelivery-r16 ENUMERATED { true } OPTIONAL, -- Need R ... } SL-RLC-ConfigPC5-r16 ::= CHOICE { sl-AM-RLC-r16 SEQUENCE { sl-SN-FieldLengthAM-r16 SN-FieldLengthAM OPTIONAL, -- Need M ... }, sl-UM-Bi-Directional-RLC-r16 SEQUENCE { sl-SN-FieldLengthUM-r16 SN-FieldLengthUM OPTIONAL, -- Need M ... }, sl-UM-Uni-Directional-RLC-r16 SEQUENCE { sl-SN-FieldLengthUM-r16 SN-FieldLengthUM OPTIONAL, -- Need M ... } } SL-LogicalChannelConfigPC5-r16 ::= SEQUENCE { sl-LogicalChannelIdentity-r16 LogicalChannelIdentity, ..., [[ sl-LogicalChannelIdentity-v1800 INTEGER (33..38) ]] } SL-PQFI-r16 ::= INTEGER (1..64) SL-CSI-RS-Config-r16 ::= SEQUENCE { sl-CSI-RS-FreqAllocation-r16 CHOICE { sl-OneAntennaPort-r16 BIT STRING (SIZE (12)), sl-TwoAntennaPort-r16 BIT STRING (SIZE (6)) } OPTIONAL, -- Need M sl-CSI-RS-FirstSymbol-r16 INTEGER (3..12) OPTIONAL, -- Need M ... } SL-RLC-ChannelConfigPC5-r17::= SEQUENCE { sl-RLC-ChannelID-PC5-r17 SL-RLC-ChannelID-r17, sl-RLC-ConfigPC5-r17 SL-RLC-ConfigPC5-r16 OPTIONAL, -- Need M sl-MAC-LogicalChannelConfigPC5-r17 SL-LogicalChannelConfigPC5-r16 OPTIONAL, -- Need M ... } SL-SFN-DFN-Offset-r18 ::= SEQUENCE { sl-FrameOffset-r18 INTEGER (0..1023), sl-SubframeOffset-r18 INTEGER (0..9), sl-SlotOffset-r18 INTEGER (0..31) } SL-SRAP-ConfigPC5-r18 ::= SEQUENCE { sl-PeerRemoteUE-L2Identity-r18 SL-DestinationIdentity-r16 OPTIONAL, -- Need M sl-PeerRemoteUE-LocalIdentity-r18 INTEGER (0..255) OPTIONAL, -- Need M sl-RemoteUE-L2Identity-r18 SL-SourceIdentity-r17 OPTIONAL, -- Need M sl-RemoteUE-LocalIdentity-r18 INTEGER (0..255) OPTIONAL, -- Need M ... } -- TAG-RRCRECONFIGURATIONSIDELINK-STOP -- ASN1STOP Editor's note: Whether the field sl-AbsoluteFrequencyPointA, together with sl-OffsetToCarrier, is sufficient for Rx UE to understand the carrier to add/modify/release from Rx UE perspective. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
958 | 4.7.5.1.1 Normal and periodic routing area updating procedure initiation | To initiate the normal routing area updating procedure, the MS sends the message ROUTING AREA UPDATE REQUEST to the network, starts timer T3330 and changes to state GMM-ROUTING-AREA-UPDATING-INITIATED. If timer T3302 is currently running, the MS shall stop timer T3302. If timer T3311 is currently running, the MS shall stop timer T3311. If the MS supports S1 mode, the MS shall handle the P-TMSI IE as follows: - If the TIN indicates "GUTI" and the MS holds a valid GUTI allocated by an MME, the MS shall map the GUTI into a P-TMSI, P-TMSI signature and RAI as specified in 3GPP TS 23.003[ Numbering, addressing and identification ] [10]. The MS shall include the mapped RAI in the Old routing area identification IE and the mapped P-TMSI signature in the P-TMSI signature IE. In addition, the MS shall include the P-TMSI type IE with P-TMSI type set to "mapped P-TMSI". When the routing area updating procedure is initiated in Iu mode, the MS shall also include the mapped P-TMSI in the P-TMSI IE. Additionally, in Iu mode and A/Gb mode, if the MS holds a valid P-TMSI and RAI, the MS shall indicate the P-TMSI in the Additional mobile identity IE and the RAI in the Additional old routing area identification IE. - If the TIN indicates "P-TMSI" or "RAT-related TMSI" and the MS holds a valid P-TMSI and RAI, the MS shall indicate the RAI in the Old routing area identification IE. In addition, the MS shall include the P-TMSI type IE with P-TMSI type set to "native P-TMSI". When the routing area updating procedure is initiated in Iu mode, the MS shall also include the P-TMSI in the P-TMSI IE. If the MS does not support S1 mode, the MS shall include the P-TMSI type IE with P-TMSI type set to "native P-TMSI". If the MS supports PSM and requests the use of PSM, the MS shall include the T3324 value IE with a requested timer value in the ROUTING AREA UPDATE REQUEST message. When the MS includes the T3324 value IE and the MS indicates support for extended periodic timer value in the MS network feature support IE, it may also include the T3312 extended value IE to request a particular T3312 value to be allocated. If the routing area updating procedure is not initiated by the MS due to an S1 mode to Iu mode or S1 mode to A/Gb mode intersystem change, or if it is initiated due to such an intersystem change and the TIN indicates "RAT-related TMSI", the MS shall use the existing UMTS security context for the PS domain. The ROUTING AREA UPDATE REQUEST message shall contain the P-TMSI signature when received in a previous ATTACH ACCEPT or ROUTING AREA UPDATE ACCEPT message. If the MS has a valid UMTS security context, the MS shall indicate it in the GPRS ciphering key sequence number IE. If the routing area updating procedure is initiated by the MS due to an S1 mode to Iu mode or S1 mode to A/Gb mode inter-system change in idle mode, or if it is initiated by the MS due to PS to CS domain change from S1 mode due to SRVCC or vSRVCC handover, and the TIN indicates "GUTI", the MS shall derive a UMTS security context for the PS domain from the current EPS security context as described in the subclause 4.7.7.10. The ROUTING AREA UPDATE REQUEST message shall include a P-TMSI signature filled with a NAS token as specified in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [123]. Furthermore, the MS shall indicate the eKSI value, which is associated with the derived UMTS security keys, in the CKSN field of the GPRS GSM ciphering key sequence number IE in the ROUTING AREA UPDATE REQUEST message. NOTE: When the MS includes a P-TMSI signature filled with a NAS token, 8 bits of the NAS token will be filled with bits from the M-TMSI (see 3GPP TS 23.003[ Numbering, addressing and identification ] [10]). If the routing area updating procedure is initiated by the MS due to the S1 mode to Iu mode or S1 mode to A/Gb mode inter-system change in connected mode, the MS shall derive a UMTS security context for the PS domain from the current EPS security context as described in the subclause 4.7.7.10. Furthermore, the MS shall indicate the eKSI value, which is associated with the derived UMTS security keys, in the CKSN field of the GPRS GSM ciphering key sequence number IE in the ROUTING AREA UPDATE REQUEST message. In Iu mode, if the MS wishes to prolong the established PS signalling connection after the normal routing area updating procedure (for example, the MS has any CM application request pending), it may set a follow-on request pending indicator on (see subclause 4.7.13). In order to indicate the new DRX parameter while in GERAN or UTRAN coverage, the MS shall send the ROUTING AREA UPDATE REQUEST message containing the DRX parameter in the DRX parameter IE to the network, with the exception of the case if the MS had indicated its MS specific DRX parameter (3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120]) to the network while in E-UTRAN coverage. In this case, when the MS enters GERAN or UTRAN coverage and initiates a routing area updating procedure, the MS shall not include the DRX parameter in the DRX parameter IE in the ROUTING AREA UPDATE REQUEST message. If the MS supports eDRX and requests the use of eDRX, the MS shall include the extended DRX parameters IE in the ROUTING AREA UPDATE REQUEST message. In A/Gb mode, if the MS supports the restriction on use of enhanced coverage, then the MS shall set the Restriction on use of enhanced coverage capability bit to "Mobile station supports restriction on use of enhanced coverage" in the MS network capability IE of the ROUTING AREA UPDATE REQUEST message If the MS supports dual connectivity of E-UTRA with NR, then the MS shall set the Dual connectivity of E-UTRA with NR capability bit to "Mobile station supports dual connectivity of E-UTRA with NR" in the MS network capability IE of the ROUTING AREA UPDATE REQUEST message. In A/Gb mode, if a UMTS security context is available and if the MS indicates support of integrity protection in the MS network capability IE included in the ROUTING AREA UPDATE REQUEST message, then the MS shall use the current GPRS GSM Kint key and the current GPRS GSM integrity algorithm to integrity protect the ROUTING AREA UPDATE REQUEST message in the LLC layer. If LLC layer has not yet been configured, then the GMM layer in the MS shall assign the GPRS GSM Kint key, the GPRS GSM Kc128 key, the GPRS GSM integrity algorithm and the GPRS GSM ciphering algorithm to the LLC layer, and indicates to the LLC layer that it shall start integrity protection. This shall be done so that the LLC layer can integrity protect, but not cipher, the ROUTING AREA UPDATE REQUEST message. The MS shall include the CKSN in the CKSN IE in the ROUTING AREA UPDATE REQUEST message. If the MS has no UMTS security context available, then the MS shall not integrity protect the ROUTING AREA UPDATE REQUEST message in the LLC layer. The MS shall in this case set the CKSN IE to the value "no key is available" and send the ROUTING AREA UPDATE REQUEST message unprotected. | 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.5.1.1 |
959 | 7.6.1 AR/VR | Audio-visual interaction is characterised by a human being interacting with the environment or people, or controlling a UE, and relying on audio-visual feedback. In the use cases like VR and interactive conversation the latency requirements include the latencies at the application layer (e.g. codecs), which could be specified outside of 3GPP. To support VR environments with low motion-to-photon capabilities, the 5G system shall support: - motion-to-photon latency in the range of 7 ms to 15ms while maintaining the required resolution of up to 8k giving user data rate of up to [1Gbit/s] and - motion-to-sound delay of [< 20 ms]. NOTE: The motion-to-photon latency is defined as the latency between the physical movement of a user's head and the updated picture in the VR headset. The motion-to-sound latency is the latency between the physical movement of a user's head and updated sound waves from a head mounted speaker reaching their ears. To support interactive task completion during voice conversation, the 5G system shall support low-delay speech coding for interactive conversational services (100 ms, one-way mouth-to-ear). Due to the separate handling of the audio and video component, the 5G system will have to cater for the VR audio-video synchronisation in order to avoid having a negative impact on the user experience (i.e. viewers detecting lack of synchronization). To support VR environments the 5G system shall support audio-video synchronisation thresholds: - in the range of [125 ms to 5 ms] for audio delayed and - in the range of [45 ms to 5 ms] for audio advanced. The 5G system shall support service continuity for AR/VR to support immersive user experience under high UE mobility. When it comes to implementation of applications containing AR/VR components, the requirements on the 5G network could depend on architectural choices implementing these services. Note 3 in table 7.1-1 above gives an example on such dependences for a VR application in a 5G system. Table 7.6.1-1 below illustrates additional use cases and provides more corresponding requirements on the 5G system. - Cloud/Edge/Split Rendering – Cloud/Edge/Split Rendering is characterised by the transition and exchange of the rendering data between the rendering server and device. - Gaming or Training Data Exchanging – This use case is characterised by the exchange of the gaming or training service data between two 5G connected AR/VR devices. - Consume VR content via tethered VR headset – This use case involves a tethered VR headset receiving VR content via a connected UE; this approach alleviates some of the computation complexity required at the VR headset, by allowing some or all decoding functionality to run locally at the connected UE. The requirements in the table below refer to the direct wireless link between the tethered VR headset and the corresponding connected UE. Table 7.6.1-1 KPI Table for additional high data rate and low latency service | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 7.6.1 |
960 | 4.16.3.2 AMF-initiated AM Policy Association Termination | Figure 4.16.3.2-1: AMF-initiated AM Policy Association Termination This procedure concerns both roaming and non-roaming scenarios. In the non-roaming case the role of the V-PCF is performed by the PCF. For the roaming scenarios, the V-PCF interacts with the AMF. 1. The AMF decides to terminate the AM Policy Association during Deregistration procedure or due to mobility with change of AMF and (V-)PCF in the registration procedure or handover procedure, then if a AM Policy Association was established with the (V-)PCF steps 2 to 3 are performed. 2. The AMF sends the Npcf_AMPolicyControl_Delete service operation including AM Policy Association ID to the (V-)PCF. 3. The (V-)PCF removes the policy context for the UE and replies to the AMF with an Acknowledgement including success or failure. In the non-roaming case, the PCF may unsubscribes to analytics from NWDAF. The (V-)PCF may deregister from the BSF as the PCF that handles the AM Policy Association for this UE. This is performed by using the Nbsf_Management_Deregister service operation, providing the Binding Identifier that was obtained earlier from the BSF when performing the Nbsf_Management_Register service operation. If the PCF has subscribed to the policy counter status to the CHF, it invokes the procedure defined in clause 4.16.8 to unsubscribe to policy counter status reporting. 4. The AMF removes the AM Policy Association for this UE, including the Access and Mobility Control Policy related to the UE. The AMF deletes the subscription to AMF detected events requested for that Policy Association. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.16.3.2 |
961 | 9.8.4.2 TDD | The following requirements apply to UE supporting ce-ModeA-r13 and ce-CQI-AlternativeTable-r15. For the parameters specified in Table 9.8.4.2-1, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2, the reported CQI value according to RC.32 TDD in Table A.4-1 shall be in the range of ±1 of the reported median more than 90% of the time. 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. Table 9.8.4.2-1: PUCCH 1-0 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.8.4.2 |
962 | 5.6.3 Roaming | In the case of roaming the 5GC supports following possible deployments scenarios for a PDU Session: - "Local Break Out" (LBO) where the SMF and all UPF(s) involved by the PDU Session are under control of the VPLMN. - "Home Routed" (HR) where the PDU Session is supported by a SMF function under control of the HPLMN, by a SMF function under control of the VPLMN, by at least one UPF under control of the HPLMN and by at least one UPF under control of the VPLMN. In this case the SMF in HPLMN selects the UPF(s) in the HPLMN and the SMF in VPLMN selects the UPF(s) in the VPLMN. This is further described in clause 6.3. Home Routed with Session Breakout in VPLMN (HR-SBO) is described in clause 6.7 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130]. NOTE 1: The use of an UPF in the VPLMN e.g. enables VPLMN charging, VPLMN LI and minimizes the impact on the HPLMN of the UE mobility within the VPLMN (e.g. for scenarios where SSC mode 1 applies). Different simultaneous PDU Sessions of an UE may use different modes: Home Routed and LBO. The HPLMN can control via subscription data per DNN and per S-NSSAI whether a PDU Session is to be set-up in HR or in LBO mode. In the case of PDU Sessions per Home Routed deployment: - NAS SM terminates in the SMF in VPLMN. - The SMF in VPLMN forwards to the SMF in the HPLMN SM related information. - The SMF in the HPLMN receives the SUPI of the UE from the SMF in the VPLMN during the PDU Session Establishment procedure. - The SMF in HPLMN is responsible to check the UE request with regard to the user subscription and to possibly reject the UE request in the case of mismatch. The SMF in HPLMN obtains subscription data directly from the UDM. - The SMF in HPLMN may send QoS requirements associated with a PDU Session to the SMF in VPLMN. This may happen during the PDU Session Establishment procedure and after the PDU Session is established. The interface between SMF in HPLMN and SMF in VPLMN is also able to carry (N9) User Plane forwarding information exchanged between SMF in HPLMN and SMF in VPLMN. The SMF in the VPLMN may check QoS requests from the SMF in HPLMN with respect to roaming agreements. In home routed roaming case, the AMF selects an SMF in the VPLMN and a SMF in the HPLMN as described in clause 6.3.2 and in clause 4.3.2.2.3.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], and provides the identifier of the selected SMF in the HPLMN to the selected SMF in the VPLMN. In roaming with LBO, the AMF selects a SMF in the VPLMN as described in clause 6.3.2 and in clause 4.3.2.2.3.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. In this case, when handling a PDU Session Establishment Request message, the SMF in the VPLMN may reject the N11 message (related with the PDU Session Establishment Request message) with a proper N11 cause. This triggers the AMF to select both a new SMF in the VPLMN and a SMF in the HPLMN in order to handle the PDU Session using home routed roaming. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.6.3 |
963 | 6.5.2 RRC confidentiality mechanisms | RRC confidentiality protection is provided by the PDCP layer between UE and gNB. The use and mode of operation of the 128-NEA algorithms are specified in Annex D. The input parameters to the 128-bit NEA algorithms as described in Annex D are a 128-bit cipher Key KRRCenc as KEY, a 5-bit bearer identity BEARER which corresponds to the radio bearer identity, the 1-bit direction of transmission DIRECTION, the length of the keystream required LENGTH and a bearer specific direction dependent 32-bit input COUNT which corresponds to the 32-bit PDCP COUNT. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.5.2 |
964 | 4.25.6 NIDD Authorization Update | Figure 4.25.6-1 illustrates the procedure for updating or revoking an existing NIDD Authorization. The UDM may initiate the NIDD Authorization Update procedure with the NEF to send updated Authorization information to the NEF. Figure 4.25.6-1: NIDD Authorization Update procedure 0. UDM provided a successful authorization for a NIDD configuration request as defined in clause 4.25.3. The NIDD authorization is modified in UDM (e.g. subscription withdrawal, DNN used for NIDD service is removed from the UE subscription) before expiration of the NIDD Duration previously authorized. 1. The UDM sends an NIDD Authorization Update information using Nudm_NIDDAuthorisation_UpdateNotify Request (SUPI, GPSI, S-NSSAI, DNN, Result, Cause, NIDD Duration) message to the NEF to update an user's NIDD authorization. 2. The NEF sends Nudm_NIDDAuthorisation_UpdateNotify Response message to the UDM to acknowledge the authorization update. 3. If the authorization is removed, the NEF should initiate the SMF-NEF Connection release procedure as specified in clause 4.25.8. 4. The NEF informs the AF that the user's authorisation status has changed by sending Nnef_NIDDConfiguration_UpdateNotify Request (GPSI, TLTRI, Result, Cause, NIDD Duration) message to the AF to update a user's NIDD authorization. 5. The AF responds to the NEF with Nnef_NIDDConfiguration_UpdateNotify Response message. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.25.6 |
965 | 5.6.1.5 Service request procedure not accepted by the network | If the service request cannot be accepted, the network shall return a SERVICE REJECT message to the UE including an appropriate EMM cause value. NOTE 1: A service request can only be rejected before the network has initiated any procedure which will be interpreted by the UE as successful completion of the service request procedure (see clauses 5.6.1.4.1 and 5.6.1.4.2) and which will trigger a transition from state EMM-SERVICE-REQUEST-INITIATED to EMM-REGISTERED on the UE side. Based on local policies or configurations in the MME, if the MME determines to change the periodic tracking area update timer (T3412), or if the MME determines to change the PSM usage or the value of timer T3324 in the UE for which PSM is allowed by the MME, the MME may return a SERVICE REJECT with the cause #10 "implicitly detached" to the UE. Based on operator policy, if the service request procedure is rejected due to core network redirection for CIoT optimizations, the network shall set the EMM cause value to #31 "Redirection to 5GCN required". NOTE 2: The network can take into account the UE's N1 mode capability, the 5GS CIoT network behaviour supported by the UE or the 5GS CIoT network behaviour supported by the 5GCN to determine the rejection with the EMM cause value #31 "Redirection to 5GCN required". The MME may be configured to perform MME-based access control for mobile originating CS fallback calls for a certain area A by rejecting related service request with EMM cause #39 "CS service temporarily not available". NOTE 3: Dependent on implementation and operator configuration the area A can be configured with the granularity of an MME area, tracking area or eNodeB service area. The MME may further be configured for a certain area A' to exempt service requests for mobile originating CS fallback calls from this MME-based access control, if: - the service request is initiated in EMM-IDLE mode; and - the UE indicated support of eNodeB-based access control for mobile originating CS fallback calls during an attach or tracking area updating procedure. NOTE 4: The operator can use this second option when the eNodeBs in area A' are supporting the eNodeB-based access control for CS fallback calls. The area A' can be part of area A or the whole area A. It is the responsibility of the operator to coordinate the activation of MME-based access control and eNodeB-based access control for mobile originating CS fallback calls. When the EMM cause value is #39 "CS service temporarily not available", the MME shall include a value for timer T3442 in the SERVICE REJECT message. If a mobile terminating CS fallback call is aborted by the network during call establishment as specified in 3GPP TS 29.118[ Mobility Management Entity (MME) - Visitor Location Register (VLR) SGs interface specification ] [], the MME shall include the EMM cause value #39 "CS service temporarily not available" and set the value of timer T3442 to zero. If a service request from a UE with only LIPA PDN connections is not accepted due to the reasons specified in clause 5.6.1.4, depending on the service request received, the MME shall include the following EMM cause value in the SERVICE REJECT message: - if the service request received is not due to CS fallback or 1xCS fallback, EMM cause value #10 "implicitly detached"; or - if the service request received is due to CS fallback or 1xCS fallback, EMM cause value #40 "no EPS bearer context activated". If a service request from a UE with only remaining SIPTO at the local network PDN connections is not accepted due to the reasons specified in clause 5.6.1.4, depending on the service request received, the MME shall: - if the service request received is due to CS fallback or 1xCS fallback, include the EMM cause value #40 "no EPS bearer context activated" in the SERVICE REJECT message; or - if the service request received is not due to CS fallback or 1xCS fallback, abort the service request procedure and send a DETACH REQUEST message to the UE with detach type "re-attach required" (see clause 5.5.2.3.1). If the service request for mobile originated services is rejected due to general NAS level mobility management congestion control, the network shall set the EMM cause value to #22 "congestion" and assign a value for back-off timer T3346. In NB-S1 mode, if the service request for mobile originated services is rejected due to operator determined barring (see 3GPP TS 29.272[ Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol ] [16C]), the network shall set the EMM cause value to #22 "congestion" and assign a value for back-off timer T3346. If the service request for mobile originated services is rejected due to service gap control as specified in clause 5.3.17 i.e. the T3447 timer is running, the network shall set the EMM cause value to #22 "congestion" and may assign a back-off timer T3346 with the remaining time of the running T3447 timer. If the MME sends a SERVICE REJECT message upon receipt of the CONTROL PLANE SERVICE REQUEST message piggybacked with the ESM DATA TRANSPORT message: - if the Release assistance indication IE is not 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 a 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 set the EMM cause value to #22 "congestion" and assign a value for control plane data back-off timer T3448. In NB-S1 mode or WB-S1 mode via satellite E-UTRAN access, if the service request is from a UE via a satellite E-UTRA cell and the network using the User Location Information provided by the eNodeB (see 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [23]), is able to determine that the UE is in a location where the network is not allowed to operate, the network shall set the EMM cause value in the SERVICE REJECT message to #78 "PLMN not allowed to operate at the present UE location". On receipt of the SERVICE REJECT message, if the UE is in state EMM-SERVICE-REQUEST-INITIATED and the message is integrity protected or contains a reject cause other than EMM cause value #25, the UE shall reset the service request attempt counter, stop timer T3417, T3417ext or T3417ext-mt, if running. If the SERVICE REJECT message with EMM cause #25 or #78 was received without integrity protection, then the UE shall discard the message. If the MME received multiple TAIs from the satellite E-UTRAN as described in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [10], and determines that, by UE subscription and operator's preferences, all of the received TAIs are 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 REJECT message. Regardless of the EMM cause value received in the SERVICE REJECT message via satellite E-UTRAN, - if the UE receives the Forbidden TAI(s) for the list of "forbidden tracking areas for roaming" IE in the SERVICE REJECT message, the UE shall store the TAI(s) included in the IE which are belonging to the serving PLMN or equivalent PLMN(s), if not already stored, 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); and - if the UE receives the Forbidden TAI(s) for the list of "forbidden tracking areas for regional provision of service" IE in the SERVICE REJECT message, the UE shall store the TAI(s) included in the IE which are belonging to the serving PLMN or equivalent PLMN(s), if not already stored, 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). Furthermore, the UE shall take the following actions depending on the received EMM cause value in the SERVICE REJECT message. #3 (Illegal UE); #6 (Illegal ME); or #8 (EPS services and non-EPS services not allowed); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. The UE shall consider the USIM as invalid for EPS services until switching off or the UICC containing the USIM is removed or the timer T3245 expires as described in clause 5.3.7a. Additionally, the UE shall delete the list of equivalent PLMNs and shall enter the state EMM-DEREGISTERED.NO-IMSI. If the message has been successfully integrity checked by the NAS and the UE maintains a counter for "SIM/USIM considered invalid for GPRS services", then the UE shall set this counter to UE implementation-specific maximum value. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number and the MM parameters update status, TMSI, LAI and ciphering key sequence number as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the service request procedure is rejected with the GMM cause with the same value. The USIM shall be considered as invalid also for non-EPS services until switching off or the UICC containing the USIM is removed or the timer T3245 expires as described in clause 5.3.7a. If the message has been successfully integrity checked by the NAS and the UE maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the UE shall set this counter to UE implementation-specific maximum value. NOTE 5: The possibility to configure a UE so that the radio transceiver for a specific radio access technology is not active, although it is implemented in the UE, is out of scope of the present specification. For the EMM cause value #3 or #6, if the UE is operating in single-registration mode, the UE shall handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list and ngKSI as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the service request procedure performed over 3GPP access is rejected with the 5GMM cause with the same value. For the EMM cause value #8, if the UE is operating in single-registration mode, the UE shall in addition set the 5GMM state to 5GMM-DEREGISTERED, 5GS update status to 5U3 ROAMING NOT ALLOWED, and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. #7 (EPS services not allowed); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. The UE shall consider the USIM as invalid for EPS services until switching off or the UICC containing the USIM is removed or the timer T3245 expires as described in clause 5.3.7a. The UE shall enter the state EMM-DEREGISTERED. If the message has been successfully integrity checked by the NAS and the UE maintains a counter for "SIM/USIM considered invalid for GPRS services", then the UE shall set this counter to UE implementation-specific maximum value. A UE operating in CS/PS mode 1 or CS/PS mode 2 of operation which is already IMSI attached for non-EPS services is still IMSI attached for non-EPS services. A UE operating in CS/PS mode 1 or CS/PS mode 2 of operation shall set the update status to U2 NOT UPDATED, shall attempt to select GERAN or UTRAN radio access technology and proceed with appropriate MM specific procedure according to the MM service state. The UE shall not reselect E-UTRAN radio access technology until switching off or the UICC containing the USIM is removed. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the service request procedure is rejected with the GMM cause with the same value. If the UE is operating in single-registration mode, the UE shall handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list and ngKSI as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the service request procedure performed over 3GPP access is rejected with the 5GMM cause with the same value. #9 (UE identity cannot be derived by the network); The UE shall set the EPS update status to EU2 NOT UPDATED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. The UE shall enter the state EMM-DEREGISTERED.NORMAL-SERVICE. If the service request was initiated for CS fallback and a CS fallback cancellation request was not received, 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 and the EMM sublayer shall not indicate the abort of the service request procedure to the MM sublayer. Otherwise the EMM sublayer shall indicate the abort of the service request procedure to the MM sublayer. If the service request was initiated for 1xCS fallback, the UE shall select cdma2000® 1x radio access technology. The UE then proceeds with appropriate cdma2000® 1x CS procedures. If the service request was initiated for 1xCS fallback and the UE has dual Rx/Tx configuration and supports enhanced 1xCS fallback, the UE shall perform a new attach procedure. If the service request was initiated for any reason other than CS fallback, 1x CS fallback or initiating a PDN connection for emergency bearer services, the UE shall perform a new attach procedure. NOTE 6: User interaction is necessary in some cases when the UE cannot re-activate the EPS bearer(s) automatically. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the service request procedure is rejected with the GMM cause with the same value. A UE operating in CS/PS mode 1 or CS/PS mode 2 of operation which is already IMSI attached for non-EPS services is still IMSI attached for non-EPS services. A UE operating in CS/PS mode 1 or CS/PS mode 2 of operation shall set the update status to U2 NOT UPDATED. If the UE is operating in single-registration mode, the UE shall handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list and ngKSI as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the service request procedure performed over 3GPP access is rejected with the 5GMM cause with the same value. #10 (Implicitly detached); A UE in CS/PS mode 1 or CS/PS mode 2 of operation is IMSI detached for both EPS services and non-EPS services. The UE shall enter the state EMM-DEREGISTERED.NORMAL-SERVICE. The UE shall delete any mapped EPS security context or partial native EPS security context. If the service request was initiated for CS fallback and a CS fallback cancellation request was not received, 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 and the EMM sublayer shall not indicate the abort of the service request procedure to the MM sublayer. Otherwise the EMM sublayer shall indicate the abort of the service request procedure to the MM sublayer. If the service request was initiated for 1xCS fallback, the UE shall select cdma2000® 1x radio access technology. The UE then proceeds with appropriate cdma2000® 1x CS procedures. If the service request was initiated for 1xCS fallback and the UE has dual Rx/Tx configuration and supports enhanced 1xCS fallback, the UE shall perform a new attach procedure. If the service request was initiated for any reason other than CS fallback, 1x CS fallback or initiating a PDN connection for emergency bearer services, the UE shall perform a new attach procedure. NOTE 7: User interaction is necessary in some cases when the UE cannot re-activate the EPS bearer(s) automatically. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM state as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the service request procedure is rejected with the GMM cause with the same value. A UE operating in CS/PS mode 1 or CS/PS mode 2 of operation shall set the update status to U2 NOT UPDATED. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM state as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the service request procedure performed over 3GPP access is rejected with the 5GMM cause with the same value. #11 (PLMN not allowed); or #35 (Requested service option not authorized in this PLMN); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. The UE shall delete the list of equivalent PLMNs and shall enter the state EMM-DEREGISTERED.PLMN-SEARCH. The UE shall store the PLMN identity in the "forbidden PLMN list" and if the UE is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) then the UE shall start timer T3245 and proceed as described in clause 5.3.7a. If the message has been successfully integrity checked by the NAS and the UE maintains a PLMN-specific attempt counter for that PLMN, then the UE shall set this counter to the UE implementation-specific maximum value. The UE shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number and the MM parameters update status, TMSI, LAI, ciphering key sequence number and the location update attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the service request procedure is rejected with the GMM cause value #11. For the EMM cause value #11, if the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list and ngKSI as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the service request procedure performed over 3GPP access is rejected with the 5GMM cause with the same value. For the EMM cause value #35, if the UE is operating in single-registration mode, the UE shall in addition set the 5GMM state to 5GMM-DEREGISTERED, 5GS update status to 5U3 ROAMING NOT ALLOWED, and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. #12 (Tracking area not allowed); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. The UE shall enter the state EMM-DEREGISTERED.LIMITED-SERVICE. The UE shall store the current TAI in the list of "forbidden tracking areas for regional provision of service". If the SERVICE REJECT message is not integrity protected, the UE shall memorize the current TAI was stored in the list of "forbidden tracking areas for regional provision of service" for non-integrity protected NAS reject message. If the UE initiated service request for mobile originated CS fallback and a CS fallback cancellation request was not received, then 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 and the EMM sublayer shall not indicate the abort of the service request procedure to the MM sublayer. Otherwise the EMM sublayer shall indicate the abort of the service request procedure to the MM sublayer. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the service request procedure is rejected with the GMM cause with the same value. If the UE is operating in single-registration mode, the UE shall in addition handle the MM parameters update status, TMSI, LAI, ciphering key sequence number and the location update attempt counter, and the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list and ngKSI as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the service request procedure performed over 3GPP access is rejected with the 5GMM cause with the same value. #13 (Roaming not allowed in this tracking area); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3). The UE shall enter the state EMM-REGISTERED.PLMN-SEARCH. The UE shall store the current TAI in the list of "forbidden tracking areas for roaming" and remove the current TAI from the stored TAI list if present. If the SERVICE REJECT message is not integrity protected, the UE shall memorize the current TAI was stored in the list of "forbidden tracking areas for roaming" for non-integrity protected NAS reject message. The UE shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the MM parameters update status, TMSI, LAI, ciphering key sequence number and the location update attempt counter, and the GMM parameters GMM state and GPRS update status as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the service request procedure is rejected with the GMM cause with the same value. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the service request procedure performed over 3GPP access is rejected with the 5GMM cause with the same value. #15 (No suitable cells in tracking area); The UE shall enter the state EMM-REGISTERED.LIMITED-SERVICE. The UE shall store the current TAI in the list of "forbidden tracking areas for roaming" and remove the current TAI from the stored TAI list if present. If the SERVICE REJECT message is not integrity protected, the UE shall memorize the current TAI was stored in the list of "forbidden tracking areas for roaming" for non-integrity protected NAS reject message. If the UE initiated service request for mobile originated CS fallback and a CS fallback cancellation request was not received, then 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 and the EMM sublayer shall not indicate the abort of the service request procedure to the MM sublayer. Otherwise the EMM sublayer shall indicate the abort of the service request procedure to the MM sublayer. If the service request was not initiated for mobile originated CS fallback, the UE shall search for a suitable cell in another tracking area or in another location area according to 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the MM parameters update status, TMSI, LAI, ciphering key sequence number and the location update attempt counter, and the GMM parameters GMM state and GPRS update status as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the service request procedure is rejected with the GMM cause with the same value. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the service request procedure performed over 3GPP access is rejected with the 5GMM cause with the same value. #18 (CS domain not available); If the request was related to CS fallback, the UE shall send an indication to the MM sublayer and shall not attempt CS fallback until combined tracking area updating procedure has been successfully completed. The UE shall enter the state EMM-REGISTERED.NORMAL-SERVICE. The UE shall set the update status to U2 NOT UPDATED. If the UE is in CS/PS mode 1 of operation with "IMS voice not available" and the request was related to CS fallback, the UE shall attempt to select GERAN or UTRAN radio access technology and disable the E-UTRA capability (see clause 4.5). If the UE is in CS/PS mode 1 or CS/PS mode 2 mode of operation, the UE may provide a notification to the user or the upper layers that the CS domain is not available. If the request was related to 1xCS fallback, the UE shall cancel upper layer actions related to 1xCS fallback and enter the state EMM-REGISTERED.NORMAL-SERVICE. #22 (Congestion); If the T3346 value IE is present in the SERVICE REJECT message and the value indicates that this timer is neither zero nor deactivated, the UE shall proceed as described below, otherwise it shall be considered as an abnormal case and the behaviour of the UE for this case is specified in clause 5.6.1.6. If the rejected request was not for initiating a PDN connection for emergency bearer services, the UE shall abort the service request procedure and enter state EMM-REGISTERED, and stop timer T3417, T3417ext or T3417ext-mt if still running. The UE shall stop timer T3346 if it is running. If the SERVICE REJECT message is integrity protected, the UE shall start timer T3346 with the value provided in the T3346 value IE. If the SERVICE REJECT message is not integrity protected, the UE shall start timer T3346 with a random value from the default range specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13]. If the service request was initiated for CS fallback and a CS fallback cancellation request was not received, the UE in CS/PS mode 1 of operation 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 and the EMM sublayer shall not indicate the abort of the service request procedure to the MM sublayer. Otherwise the EMM sublayer shall indicate the abort of the service request procedure to the MM sublayer. NOTE 8: If the UE disables the E-UTRA capability, then subsequent mobile terminating calls could fail. If the service request was initiated for CS fallback for emergency call and a CS fallback cancellation request was not received, the UE may attempt to select GERAN or UTRAN radio access technology. It then proceeds with appropriate MM and CC specific procedures. The EMM sublayer shall not indicate the abort of the service request procedure to the MM sublayer. If the service request was initiated for 1xCS fallback, the UE shall select cdma2000® 1x radio access technology. The UE then proceeds with appropriate cdma2000® 1x CS procedures. If the service request was initiated for 1xCS fallback for emergency call, the UE may select cdma2000® 1x radio access technology. The UE then proceeds with appropriate cdma2000® 1x CS procedures. If the service request was initiated in EMM-CONNECTED mode with Control plane service type "mobile originating request" and with the "active" flag set to 1, the UE shall abort the procedure. If the service request procedure was initiated for an MO MMTEL voice call or an MO MMTEL video call is started, a notification that the service request was not accepted due to congestion shall be provided to the upper layers. NOTE 9: This can result in the upper layers requesting establishment of the originating voice call on an alternative manner e.g. requesting establishment of a CS voice call (see 3GPP TS 24.173[ IMS Multimedia telephony communication service and supplementary services; Stage 3 ] [13E]). For all other cases the UE stays in the current serving cell and applies normal cell reselection process. The service request procedure is started, if still necessary, when timer T3346 expires or is stopped. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM parameters GMM state and GPRS update status as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the service request procedure is rejected with the GMM cause with the same value. If the UE is using EPS services with control plane CIoT EPS optimization and if the T3448 value IE is present in the SERVICE REJECT message and the value indicates that this timer is neither zero nor deactivated, the UE shall: - stop timer T3448 if it is running; - consider the transport of user data via the control plane as unsuccessful; and - start timer T3448: - with the value provided in the T3448 value IE if the SERVICE REJECT message is integrity protected; or - with a random value from the default range specified in table 10.2.1 if the SERVICE REJECT message is not integrity protected. If the UE is using EPS services with control plane CIoT EPS optimization and if the T3448 value IE is present in the SERVICE REJECT message and the value indicates that this timer is either zero or deactivated, the UE shall ignore the T3448 value IE and- stop timer T3448 if it is running; and - consider the transport of user data via the control plane as unsuccessful. If the UE is using EPS services with control plane CIoT EPS optimization and if the T3448 value IE is not present in the SERVICE REJECT message, it shall be considered as an abnormal case and the behaviour of UE for this case is specified in clause 5.6.1.6. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters, 5GMM state and 5GS update status as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the service request procedure performed over 3GPP access is rejected with the 5GMM cause with the same value. #25 (Not authorized for this CSG); EMM cause #25 is only applicable when received from a CSG cell. EMM cause #25 received from a non-CSG cell is considered as an abnormal case and the behaviour of the UE is specified in clause 5.6.1.6. The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and store it according to clause 5.1.3.3). The UE shall enter the state EMM-REGISTERED.LIMITED-SERVICE. If the CSG ID and associated PLMN identity of the cell where the UE has initiated the service request procedure are contained in the Allowed CSG list, the UE shall remove the entry corresponding to this CSG ID and associated PLMN identity from the Allowed CSG list. If the CSG ID and associated PLMN identity of the cell where the UE has initiated the service request procedure are contained in the Operator CSG list, the UE shall apply the procedures defined in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6] clause 3.1A. The UE shall search for a suitable cell according to 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM parameters GMM state and GPRS update status as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the service request procedure is rejected with the GMM cause with the same value. If the UE is operating in single-registration mode, the UE shall in addition set the 5GMM state to 5GMM-REGISTERED and set the 5GS update status to 5U3 ROAMING NOT ALLOWED. #31 (Redirection to 5GCN required); EMM cause #31 received by a UE that has not indicated support for CIoT optimizations is considered as an abnormal case and the behaviour of the UE is specified in clause 5.6.1.6. The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3). The UE shall reset the service request attempt counter and shall enter the state EMM-REGISTERED.LIMITED-SERVICE. The UE shall enable N1 mode capability for 3GPP access if it was disabled and disable the E-UTRA capability (see clause 4.5). If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters, 5GMM state, and 5GS update status as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the service request procedure performed over 3GPP access is rejected with the 5GMM cause with the same value. #36 (IAB-node operation not authorized); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. The UE shall delete the list of equivalent PLMNs and shall enter the state EMM-DEREGISTERED.PLMN-SEARCH. The UE shall store the PLMN identity in the "forbidden PLMN list" and if the UE is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) then the UE shall start timer T3245 and proceed as described in subclause 5.3.7a. If the message has been successfully integrity checked by the NAS and the UE maintains a PLMN-specific attempt counter for that PLMN, then the UE shall set this counter to the UE implementation-specific maximum value. The UE shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list and ngKSI as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the service request procedure performed over 3GPP access is rejected with the 5GMM cause with the same value. #39 (CS service temporarily not available); If the T3442 value received in the SERVICE REJECT message is not zero, the UE shall start timer T3442 and enter the state EMM-REGISTERED.NORMAL-SERVICE. If the T3442 value received in the SERVICE REJECT message is zero, the UE shall not start timer T3442. The UE shall not try to send an EXTENDED SERVICE REQUEST message for mobile originating CS fallback to the network, except for mobile originating CS fallback for emergency calls, until timer T3442 expires or the UE sends a TRACKING AREA UPDATE REQUEST message. #40 (No EPS bearer context activated); The UE shall enter the state EMM-DEREGISTERED.NORMAL-SERVICE. The UE shall delete any mapped EPS security context or partial native EPS security context. If the service request was initiated for CS fallback and a CS fallback cancellation request was not received, 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 and the EMM sublayer shall not indicate the abort of the service request procedure to the MM sublayer. Otherwise the EMM sublayer shall indicate the abort of the service request procedure to the MM sublayer. If the service request was initiated for 1xCS fallback, the UE shall select cdma2000® 1x radio access technology. The UE then proceeds with appropriate cdma2000® 1x CS procedures. If the service request was initiated for 1xCS fallback and the UE has dual Rx/Tx configuration and supports enhanced 1xCS fallback, the UE shall perform a new attach procedure. If the service request was initiated for any reason other than CS fallback, 1x CS fallback or initiating a PDN connection for emergency bearer services, the UE shall perform a new attach procedure. NOTE 10: User interaction is necessary in some cases when the UE cannot re-activate the EPS bearer(s) automatically. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM state as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the service request procedure is rejected with the GMM cause value #10 "Implicitly detached". A UE operating in CS/PS mode 1 or CS/PS mode 2 of operation which is already IMSI attached for non-EPS services is still IMSI attached for non-EPS services in the network. A UE operating in CS/PS mode 1 or CS/PS mode 2 of operation shall set the update status to U2 NOT UPDATED. If the UE is operating in single-registration mode, the UE shall in addition set the 5GMM state to 5GMM-DEREGISTERED. #42 (Severe network failure); The UE shall set the EPS update status to EU2 NOT UPDATED, and shall delete any GUTI, last visited registered TAI, TAI list, eKSI, and list of equivalent PLMNs. The UE shall start an implementation specific timer, setting its value to 2 times the value of T as defined in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. While this timer is running, the UE shall not consider the PLMN + RAT combination that provided this reject cause as a candidate for PLMN selection. The UE then enters state EMM-DEREGISTERED.PLMN-SEARCH in order to perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition set the GMM state to GMM-DEREGISTERED, GPRS update status to GU2 NOT UPDATED, MM update status to U2 NOT UPDATED and shall delete the P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number, LAI, TMSI and ciphering key sequence number. If the UE is operating in single-registration mode, the UE shall in addition set the 5GMM state to 5GMM-DEREGISTERED, 5GS update status to 5U2 NOT UPDATED, and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. #78 (PLMN not allowed to operate at the present UE location). This cause value received from a non-satellite E-UTRA cell is considered as an abnormal case and the behaviour of the UE is specified in clause 5.5.6.1.6. The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. Additionally, the UE shall reset the registration attempt counter. The UE shall store the PLMN identity and, if it is known, the current geographical location in the list of "PLMNs not allowed to operate at the present UE location", start a corresponding timer instance (see subclause 4.11.2), enter state EMM-DEREGISTERED.PLMN-SEARCH and perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters, 5GMM state, and 5GS update status as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the service request procedure performed over 3GPP access is rejected with the 5GMM cause with the same value. Other values are considered as abnormal cases. The specification of the UE behaviour in those cases is described in clause 5.6.1.6. | 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.5 |
966 | 6.5.6 UIA identification | Each UMTS Integrity Algorithm (UIA) will be assigned a 4-bit identifier. Currently, the following values have been defined: "00012" : UIA1, Kasumi. "00102" : UIA2, SNOW 3G. The remaining values are not defined. UEs and RNCs shall implement UIA1 and UIA2. The use of Kasumi for the integrity protection function f9 is specified in TS 35.201[ 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 1: f8 and f9 specification ] [11] and TS 35.202[ 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 2: Kasumi specification ] [12]. Implementers' test data and design conformance data is provided in TS 35.203[ 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 3: Implementors' test data ] [13] and TS 35.204[ 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 4: Design conformance test data ] [14]. The use of SNOW 3G for the integrity protection function f9 is specified in TS 35.215[ Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 1: UEA2 and UIA2 specifications ] [24] and TS 35.216[ Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 2: SNOW 3G specification ] [25]. Implementers' test data and design conformance data is provided in TS 35.217[ Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 3: Implementors' test data ] [26] and TS 35.218[ Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 4: Design conformance test data ] [27]. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.5.6 |
967 | 5.38.3 Paging Cause Indication for Voice Service | A Multi-USIM UE and the network may support Paging Cause Indication for Voice Service feature. The network that supports Paging Cause Indication for Voice Service feature shall provide a Voice Service Indication for IMS voice service in the Paging message, only if the UE indicates the Paging Cause Indication for Voice Service feature is supported to the network. The network determines the IMS voice service based on the Paging Policy Indicator as specified in clause 5.4.3.2. Upon reception of the Voice Service Indication in NGAP Paging Message from AMF, the NG-RAN supporting Paging Cause Indication for Voice Service should include the Voice Service Indication in the Uu Paging message to the UE. When the UE context in the AMF indicates Paging Cause Indication for Voice Service feature is supported, in order to require NG RAN to deliver the Voice Service Indication in RAN paging for the UE in RRC_INACTIVE state, the AMF provides an indication indicating the Paging Cause Indication for Voice Service feature is supported to the NG-RAN. Upon reception of the indication, the NG-RAN that supports the feature stores a Paging Cause Indication for Voice Service indication in its the UE context. For a UE in RRC_INACTIVE, the NG-RAN should provide the Voice Service Indication in the RAN Paging message only when there is Paging Cause Indication for Voice Service indication in the UE context and detects the downlink data which triggers the RAN Paging message is related to voice service based on the Paging Policy Indicator, in the header of the received downlink data, as specified in clause 5.4.3.2. UE that supports the Paging Cause Indication for Voice Service feature is capable of differentiation between Paging from a network that does not support the Paging Cause Indication for Voice Service feature and Paging without the Voice Service Indication. How the UE distinguishes the Paging from a RAN that does not support the Paging Cause Indication for Voice Service feature and Paging without the Voice Service Indication is defined in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28]. The UE determines whether the Paging Cause Indication for Voice Service feature is supported in the current Registration Area by 5GC based on the MUSIM capability exchange with the AMF, see clause 5.38.1. The UE determines that the Paging Cause Indication for Voice Service feature is supported if it is supported by both the RAN, as indicated in the received Uu Paging message, and by 5GC, as indicated in the MUSIM capability exchange with the AMF. The UE uses the Paging Cause Indication for Voice Service as described in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47] and TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.38.3 |
968 | 6.8.2 PDCCH multiplexing and scrambling | The block of bits on each of the control channels to be transmitted in a subframe, where is the number of bits in one subframe to be transmitted on physical downlink control channel number , shall be multiplexed, resulting in a block of bits , where is the number of PDCCHs transmitted in the subframe. The block of bits shall be scrambled with a cell-specific sequence prior to modulation, 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. CCE number corresponds to bits . If necessary, <NIL> elements shall be inserted in the block of bits prior to scrambling to ensure that the PDCCHs starts at the CCE positions as described in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4] and to ensure that the length of the scrambled block of bits matches the amount of resource-element groups not assigned to PCFICH or PHICH. | 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.8.2 |
969 | 6.1.3.2.1 Successful Secondary PDP Context Activation Procedure Initiated by the MS | In order to request a PDP context activation with the same PDP address and APN as an already active PDP context, the MS shall send an ACTIVATE SECONDARY PDP CONTEXT REQUEST message to the network, enter the state PDP-ACTIVE-PENDING and start timer T3380. The message shall contain the selected NSAPI. The MS shall ensure that the selected NSAPI is not currently being used by another Session Management entity in the MS. The message shall also include a QoS profile, a requested LLC SAPI and the Linked TI. The QoS profile is the requested QoS. If present, the TFT shall be sent transparently through the SGSN to the GGSN to enable packet classification and policing for downlink data transfer. If the selected Bearer Control Mode is 'MS/NW' and a TFT IE is included in the ACTIVATE SECONDARY PDP CONTEXT REQUEST message, the MS shall set the packet filter direction parameter of each packet filter in the TFT to a value different from "00". The MS shall allocate packet filter identifiers for all packet filters included in the TFT. Upon receipt of an ACTIVATE SECONDARY PDP CONTEXT REQUEST, the network shall validate the message by verifying the TI given in the Linked TI IE to be any of the active PDP context(s). The same GGSN address shall be used by the SGSN as for the already established PDP context(s) for that PDP address. The network shall select a radio priority level based on the QoS negotiated and shall reply with an ACTIVATE SECONDARY PDP CONTEXT ACCEPT message, if the request can be accepted. NOTE 1: If the MS requested a value for a QoS parameter that is not within the range specified by 3GPP TS 23.107[ Quality of Service (QoS) concept and architecture ] [81], the network should negotiate the parameter to a value that lies within the specified range. Upon receipt of the message ACTIVATE SECONDARY PDP CONTEXT ACCEPT, the MS shall stop timer T3380 and enter the state PDP-ACTIVE. If the offered QoS parameters received from the network differ from the QoS requested by the MS, the MS shall either accept the negotiated QoS or initiate the PDP context deactivation procedure. In A/Gb mode the MS shall initiate establishment of the logical link for the LLC SAPI indicated by the network with the offered QoS and selected radio priority level if no logical link has been already established for that SAPI. If the LLC SAPI indicated by the network can not be supported by the MS, the MS shall initiate the PDP context deactivation procedure. In Iu mode, both SGSN and MS shall store the LLC SAPI and the radio priority in the PDP context. If an Iu mode to A/Gb mode Routing Area Update is performed, the new SGSN shall initiate establishment of the logical link using the negotiated LLC SAPI, the negotiated QoS profile and selected radio priority level stored in the PDP context as in an A/Gb mode to A/Gb mode Routing Area Update. An MS, which is capable of operating in A/Gb mode, shall use a valid LLC SAPI, while an MS which is not capable of operating in A/Gb mode shall indicate the LLC SAPI value as "LLC SAPI not assigned" in order to avoid unnecessary value range checking and any other possible confusion in the network. When the MS uses a valid LLC SAPI, the network shall return a valid LLC SAPI. The network shall return the "LLC SAPI not assigned" value only when the MS uses the "LLC SAPI not assigned" value. NOTE 2: The radio priority level and the LLC SAPI parameters, though not used in Iu mode, shall be included in the messages, in order to support handover between Iu mode and A/Gb mode networks. At inter-system change from Iu mode to A/Gb mode, SM shall locally deactivate the active PDP context(s) if SM does not have the following parameters: - LLC SAPI; and - radio priority. | 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 | 6.1.3.2.1 |
970 | 5.3.5 Requirements for key management inside the gNB | The 5GC provides subscription specific session keying material for the gNBs, which also hold long term keys used for authentication and security association setup purposes. Protecting all these keys is important. The following requirements apply: - Any part of a gNB deployment that stores or processes keys in cleartext shall be protected from physical attacks. If not, the whole entity is placed in a physically secure location, then keys in cleartext shall be stored and processed in a secure environment. Keys stored inside a secure environment in any part of the gNB shall never leave the secure environment except when done in accordance with this or other 3GPP specifications. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 5.3.5 |
971 | K.2.2.5 Configuration for Sync and Announce intervals | The TSN AF or TSCTSF uses the values in portDS.logSyncInterval (for Boundary Clock) or portDS.initialLogSyncInterval, portDS.useMgtSettableLogSyncInterval and portDS.mgtSettableLogSyncInterval (for time-aware system) to configure the interval for the Sync messages (per PTP port) as described in IEEE Std 1588 [126] or IEEE Std 802.1AS [104], respectively. The TSCTSF or TSN AF configures those values as follows: - TSCTSF or TSN AF use PMIC to configure the values for the PTP ports in NW-TT. - TSCTSF or TSN AF use the "Time synchronization information for each DS-TT port" element in UMIC to configure the values for PTP ports in DS-TT(s) if NW-TT acts as GM on behalf of those DS-TTs. - TSCTSF or TSN AF use PMIC to configure the values for the PTP ports in DS-TT if the DS-TT is capable of acting as a GM. When the NW-TT generates the (g)PTP Sync messages on behalf of the DS-TT, the NW-TT uses the values in the element "Time synchronization information for each DS-TT port" in UMIC to determine the Sync interval for the PTP ports the respective DS-TT. When DS-TT generates the (g)PTP Sync messages, the DS-TT uses the values in PMIC to determine the Sync interval for the PTP ports in this DS-TT. The TSN AF or TSCTSF uses the values in portDS.logAnnounceInterval (for Boundary Clock) or portDS.initialLogAnnounceInterval, portDS.useMgtSettableLogAnnounceInterval and portDS.mgtSettableLogAnnounceInterval (for time-aware system) to configure the interval for the Announce messages (per PTP port) as described in IEEE Std 1588 [126] and IEEE Std 802.1AS [104], respectively. The TSCTSF or TSN AF configures those values as follows: - TSCTSF or TSN AF use PMIC to configure the values for the PTP ports in NW-TT. - TSCTSF or TSN AF use the "Time synchronization information for each DS-TT port" element in UMIC to configure the values for PTP ports in DS-TT(s) if NW-TT acts as GM on behalf of those DS-TTs. - TSCTSF or TSN AF use PMIC to configure the values for the PTP ports in DS-TT if the DS-TT is capable of acting as a GM. When the NW-TT generates the (g)PTP Announce messages on behalf of the DS-TT, the NW-TT uses the values in the element "Time synchronization information for each DS-TT port" in UMIC to determine the Announce interval for the PTP ports the respective DS-TT. When DS-TT generates the (g)PTP Announce messages, the DS-TT uses the values in PMIC to determine the Announce interval for the PTP ports in this DS-TT. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | K.2.2.5 |
972 | 15.4.2.4 Conditional Handover | The same principle as described in 9.2.3.4 applies to conditional handover in case the source cell is using a network energy saving solution (e.g., the cell is activating cell DTX/DRX or turning off), unless hereunder specified. In this case, the following additional triggering conditions are supported, upon which UE may use NES-specific CHO event for executing CHO to a candidate cell, as defined in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]: - The UE may be notified via DCI to enable CHO conditions(s) configured with NES event indication. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 15.4.2.4 |
973 | 8.5.1.2.8 Enhanced Downlink Control Channel Performance Requirement Type B - 2 Tx Antenna Ports with Non-Colliding CRS Dominant Interferer | For the parameters specified in Table 8.5.1-1 and Table 8.5.1.2.8-1, the average probability of a miss-detecting ACK for NACK (Pm-an) shall be below the specified value in Table 8.5.1.2.8-2. The purpose of this test is to verify the PHICH performance with 2 transmit antennas when the serving cell PHICH transmission is interfered by two interfering cells with the dominant interferer having the non-colliding CRS pattern and applying interference model defined in clause B.7.1. In Table 8.5.1.2.8-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] is provided and includes Cell 2 and Cell 3. Table 8.5.1.2.8-1: Test Parameters for PHICH Table 8.5.1.2.8-2: Minimum performance PHICH for Enhanced Downlink Control Channel Performance Requirement Type B | 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.5.1.2.8 |
974 | 4.3.5.3 Tracking Area list management | Tracking Area list management comprises the functions to allocate and reallocate a Tracking Area Identity list to the UE. All the tracking areas in a Tracking Area List to which a UE is registered are served by the same serving MME. The "tracking area list concept" is used with E-UTRAN. With this concept, when the UE registers with the network, the MME allocates a set (a "list") of tracking areas to the UE. By making the centre of this set of tracking areas close to the UE's current location, the chance of a UE rapidly making another tracking area update can be reduced. If SIPTO at local network with stand-alone GW, Serving GW relocation without mobility and ISR are supported in the core network the Tracking Area list should only contain either Tracking Areas inside one local network or inside the macro network. If the tracking area list covers both local network and macro network, the ISR shall not be activated if the UE is allowed to use SIPTO at local network. The MME determines the RAT type the UE is camping on, i.e. NB-IoT or WB-E-UTRAN for terrestrial access and WB-E-UTRAN or NB-IoT RAT types for satellite access, based on the Tracking Area indicated in the INITIAL UE MESSAGE by the eNodeB. To ensure a UE initiates tracking area updating procedure when performing inter-RAT mobility between NB-IoT and WB-E-UTRAN, the E-UTRAN shall be configured such that a Tracking Area does not contain both WB-E-UTRAN and NB-IoT cells, and, the MME shall not allocate a Tracking Area Identity list that contains both NB-IoT and WB-E-UTRAN Tracking Areas. To ensure the UE initiates tracking area update procedure when it moves to and from an MME that supports 15 EPS bearers per UE as defined in clause 4.12 to an MME that does not support 15 EPS bearers per MME and vice versa, the MME shall allocate a Tracking Area Identity list that provides homogenous support for 15 EPS bearers per UE. Other features (e.g. User Plane CIoT EPS Optimisation, Supporting up to 15 EPS bearers per UE, satellite access) may require the MME to adapt how it creates the "list" of TAIs. NOTE: This TAI list functionality is different to the SGSN behaviour in GERAN and UTRAN systems. In GERAN/UTRAN the UE is only registered in one Routeing Area at a time. | 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.5.3 |
975 | 5.5.4.22 Event H2 (The Aerial UE altitude becomes lower than a threshold) | The UE shall: 1> consider the entering condition for this event to be satisfied when condition H2-1, as specified below, is fulfilled; 1> consider the leaving condition for this event to be satisfied when condition H2-2, as specified below, is fulfilled; Inequality H2-1 (Entering condition) Ms + Hys < Thresh Inequality H2-2 (Leaving condition) Ms – Hys > Thresh The variables in the formula are defined as follows: Ms is the Aerial UE altitude relative to the sea level. Hys is the hysteresis parameter for this event (i.e. h2-Hysteresis as defined within reportConfigNR for this event). Thresh is the threshold parameter for this event (i.e. h2-Threshold as defined within reportConfigNR for this event). Ms, Hys, Thresh are expressed in meters. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.4.22 |
976 | 5.6.10.3 Support of Unstructured PDU Session type | Different Point-to-Point (PtP) tunnelling techniques may be used to deliver Unstructured PDU Session type data to the destination (e.g. application server) in the Data Network via N6. Point-to-point tunnelling based on UDP/IP encapsulation as described below may be used. Other techniques may be supported. Regardless of addressing scheme used from the UPF to the DN, the UPF shall be able to map the address used between the UPF and the DN to the PDU Session. When Point-to-Point tunnelling based on UDP/IPv6 is used, the following considerations apply: - IPv6 prefix allocation for PDU Sessions are performed locally by the (H-)SMF without involving the UE. - The UPF(s) acts as a transparent forwarding node for the payload between the UE and the destination in the DN. - For uplink, the UPF forwards the received Unstructured PDU Session type data to the destination in the data network over the N6 PtP tunnel using UDP/IPv6 encapsulation. - For downlink, the destination in the data network sends the Unstructured PDU Session type data using UDP/IPv6 encapsulation with the IPv6 address of the PDU Session and the 3GPP defined UDP port for Unstructured PDU Session type data. The UPF acting as PDU Session Anchor decapsulates the received data (i.e. removes the UDP/IPv6 headers) and forwards the data identified by the IPv6 prefix of the PDU Session for delivery to the UE. - The (H-)SMF performs the IPv6 related operations but the IPv6 prefix is not provided to the UE, i.e. Router Advertisements and DHCPv6 are not performed. The SMF assigns an IPv6 Interface Identifier for the PDU Session. The allocated IPv6 prefix identifies the PDU Session of the UE. - For AF influence on traffic routing (described in clause 5.6.7), when the N6 PtP tunnelling is used over the DNAI and the AF provides, by value, information about N6 traffic routing requirements in the AF request, the AF provides N6 PtP tunnelling requirements (IPv6 address and UDP port of the tunnel end in the DN) as the N6 traffic routing information associated to the DNAI; when the SMF notifies the AF of UP path management events, it includes the N6 PtP tunnel information related to the UP (the IPv6 address and the 3GPP defined UDP port of the tunnel end at the UPF) as N6 traffic routing information in the notification. In this Release of the specification there is support for maximum one 5G QoS Flow per PDU Session of Type Unstructured. In this Release of specification, the PDU Session of Unstructured PDU Session type is restricted to SSC mode 1 and SSC mode 2. The UE may acquire from the SMF, at PDU Session Establishment, the MTU that the UE shall consider, see clause 5.6.10.4. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.6.10.3 |
977 | 6.2.19 SCP | The Service Communication Proxy (SCP) includes one or more of the following functionalities. Some or all of the SCP functionalities may be supported in a single instance of an SCP: - Indirect Communication (see clause 7.1.1 for details). - Delegated Discovery (see clauses 7.1.1 and 6.3.1 for details). - Message forwarding and routing to destination NF/NF service. - Message forwarding and routing to a next hop SCP. - Communication security (e.g. authorization of the NF Service Consumer to access the NF Service Producer API), load balancing, monitoring, overload control, etc. - Optionally interact with UDR, to resolve the UDM Group ID/UDR Group ID/AUSF Group ID/PCF Group ID/CHF Group ID/HSS Group ID based on UE identity, e.g. SUPI or IMPI/IMPU (see clause 6.3.1 for details). NOTE 1: Communication security, e.g. authorization of the NF Service Consumer to access the NF Service Producer's API is specified in TS 33.501[ Security architecture and procedures for 5G System ] [29]. NOTE 2: Load balancing, monitoring, overload control functionality provided by the SCP is left up to implementation. The SCP may be deployed in a distributed manner. NOTE 3: More than one SCP can be present in the communication path between NF Services. SCPs can be deployed at PLMN level, shared-slice level and slice-specific level. It is left to operator deployment to ensure that SCPs can communicate with relevant NRFs. In order to enable SCPs to route messages through several SCPs (i.e. next SCP hop discovery, see clause 6.3.16), an SCP may register its profile in the NRF. Alternatively, local configuration may be used. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.2.19 |
978 | 5.2.2.3.3 ATTEMPTING-TO-ATTACH | The UE: - shall initiate an attach or combined attach procedure on the expiry of timers T3411, T3402 or T3346 (see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13]); - may initiate an attach for emergency bearer services even if timer T3346 is running; - may initiate an attach if the UE is a UE configured to use AC11 - 15 in the selected PLMN, even if timer T3402, T3346 or timer T3447 is running; - shall initiate an attach or combined attach procedure when entering a new PLMN, if timer T3346 is running and the new PLMN is not equivalent to the PLMN where the UE started timer T3346, the PLMN identity of the new cell is not in one of the forbidden PLMN lists and the tracking area is not in one of the lists of forbidden tracking areas; - shall initiate an attach or combined attach procedure when the tracking area of the serving cell has changed, if timer T3346 is not running, the PLMN identity of the new cell is not in one of the forbidden PLMN lists and the tracking area of the new cell is not in one of the lists of forbidden tracking areas; - shall use requests for non-EPS services for non-emergency call from CM layers to trigger a combined attach procedure, if timer T3346 is not running (see clause 5.5.1.3), or to attempt to select GERAN or UTRAN radio access technology and proceed with the appropriate MM and CC specific procedures; - shall use requests for non-EPS services for emergency call from CM layers to attempt to select GERAN or UTRAN radio access technology and proceed with the appropriate MM and CC specific procedures; - may initiate an attach procedure upon receiving a request from upper layers to transmit user data related to an exceptional event and the UE is allowed to use exception data reporting (see the ExceptionDataReportingAllowed leaf of the NAS configuration MO in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A]) if timer T3346 is not already running for "MO exception data" and even if timer T3402 or timer T3411 is running; - may initiate an attach procedure upon request of the upper layers to establish a PDN connection for emergency bearer services; and - may initiate an attach procedure upon request of the upper layers to establish a PDN connection for RLOS, if timer T3346 is not running. | 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.2.2.3.3 |
979 | 8.1.2.6.2 Applicability rule and antenna connection for CA and DC tests with 2Rx | All tests specified in 8.2 to 8.8 with 2Rx with CA, TDD-FDD CA and DC are tested with 4 Rx capable UEs. Within the CA/DC configuration if any of the PCell and/or the SCells and/or PSCells is a 2Rx supported RF band, the antenna connection should follow the same method as defined in 8.1.2.6.1 for single carrier tests on any of the 2Rx supported RF bands, with same requirements specified with 2Rx applied. Within the CA configuration if any of the PCell and/or the SCells and/or PSCells is a 4Rx supported RF band, the antenna connection should follow the same as defined in 8.1.2.6.1 for single carrier tests on any of the 4 Rx supported RF bands, with the SNR requirements applied with 1.5 dB less than the number specified with 2Rx. Same applicability rules defined in 8.1.2.3, 8.1.2.3A, and 8.1.2.3B for CA, TDD-FDD CA and DC applied for different CA and DC configurations and bandwidth combination sets should be applied for 4 Rx capable UEs. | 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.1.2.6.2 |
980 | 4.9.1.2.4 Xn based inter NG-RAN handover with re-allocation of intermediate UPF | This procedure is used to hand over a UE from a Source NG-RAN to a Target NG-RAN using Xn when the AMF is unchanged and the SMF decides that the intermediate UPF (I-UPF) is to be changed. In the case of using UL CL, the I-UPF can be regarded as UL CL and additional PSA provides local access to a DN, the simultaneous change of UL-CL and the additional PSA is described in clause 4.3.5.7. In the case of using Branching Point, the I-UPF can be regarded as BP. It is assumed that the PDU Session for the UE comprises of a UPF that acts as a PDU Session Anchor and an intermediate UPF at the time of this Handover procedure for non-roaming and local breakout roaming scenario. In the case of home routed roaming scenario, the PDU Session of the UE comprises of at least one UPF in the VPLMN and UPF in the HPLMN which acts as a PDU Session Anchor at the time of this handover procedure. The Source UPF referred in this clause 4.9.1.2.4 is the UPF which terminates N3 interface in the 5GC. The presence of IP connectivity between the Source UPF and Source NG-RAN, between the source UPF and Target NG-RAN and between the Target UPF and Target NG-RAN, is assumed. (If there is no IP connectivity between source UPF and Target NG-RAN, it is assumed that the N2-based handover procedure in clause 4.9.1.3 shall be used instead). The call flow is shown in figure 4.9.1.2.4-1. Figure 4.9.1.2.4-1: Xn based inter NG-RAN handover with intermediate UPF re-allocation Steps 1-4 are same as steps 1-4 described in clause 4.9.1.2.3 except that the I-UPF in clause 4.9.1.2.3 is replaced by Target UPF. 5. [Conditional] The SMF sends N4 Session Modification Request message to the PDU Session Anchor. The DL CN Tunnel Info of the Target UPF is included in this message. If redundant transmission is performed for one or more QoS Flows of the PDU Session, the SMF provides two DL CN Tunnel Info (for N9) to the UPF (PSA) and indicates to the UPF (PSA) one of the DL CN Tunnel Info is used as redundancy tunnel of the PDU Session. In the case of home routed roaming, if the N9 terminating V-UPF, which is connected to with home UPF, is changed, the V-SMF invokes an Nsmf_PDUSession_Update Request (DL CN Tunnel Info) service operation toward the H-SMF. 6. [Conditional] The SMF associated with the PDU Session Anchor responds with the N4 Session Modification Response message. In the case of home routed roaming, the H-SMF responds with the Nsmf_PDUSession_Update Response service operation toward the V-SMF once H-UPF is updated with the DL Tunnel Info of the T-UPF. At this point, PDU Session Anchor starts sending downlink packets to the Target NG-RAN via Target UPF. Steps 7-11 are same as steps 7-11 described in clause 4.9.1.2.3 except that the I-UPF in clause 4.9.1.2.3 is replaced by Target UPF. If the Source UPF acts as a UL CL or BP, the SMF indicates to only one of the PDU Session Anchors to send the "end marker" packets. To ensure the "end marker" is the last user plane packet on the old path, the SMF should modify the path on other PDU Session Anchors before it indicates the PDU Session Anchor to send the "end marker" packets. 11. The timer is started in step 4 if the source UPF is not the PSA UPF. When this timer is expired, the SMF initiates Source UPF(s) Release procedure by sending an N4 Session Release Request (Release Cause). 12. The Source UPF(s) acknowledges with an N4 Session Release Response message to confirm the release of resources. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.9.1.2.4 |
981 | 8.7.12.3 TDD-FDD CA in licensed bands | The parameters specified in Table 8.7.12.3-1 are valid for all LAA CA SDR tests unless otherwise stated. Table 8.7.12.3-1: Common Test Parameters For UE not supporting 256QAM, the TB success rate shall be higher than 85% when PDSCH are scheduled with FRC in Table 8.7.12.3-2 with the downlink physical channel setup according to Annex C.3.2. For UE supporting 256QAM, the TB success rate shall be higher than 85% when PDSCH are scheduled with FRC in Table 8.7.12.3-3 with the downlink physical channel setup according to Annex C.3.2. For UE supporting 256QAM, the requirement with 64QAM is not applicable. For LAA SCell, per-CC separate FRCs are defined for different UE capability for endingDwPTS and secondSlotStartingPosition. The TB success rate 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.12.3-2: Per-CC FRC for SDR test (64QAM) Table 8.7.12.3-3: Per-CC FRC for SDR test (256QAM) CA configuration, bandwidth combination and MIMO layer on each CC is determined by following procedure. - Select one CA bandwidth combination among all supported CA configurations with bandwidth combination and MIMO layer on each CC following the equation that leads to largest equivalent aggregated bandwidth among all CA bandwidth combinations supported by UE. Equivalent aggregated bandwidth is defined as where is number of CCs, and is MIMO layer and bandwidth of CC . - When there are multiple sets of {CA configuration, bandwidth combination, MIMO layer} with same largest aggregated bandwidth, select one among sets with largest number of 4 layer 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.7.12.3 |
982 | 5.1.4.3 Coordination between 5GMM for 3GPP access and EMM without N26 interface | A UE operating in the single-registration mode that is not registered over 3GPP access shall be in state EMM-DEREGISTERED and in state 5GMM-DEREGISTERED for 3GPP access. In N1 mode, upon successful completion of a registration procedure over 3GPP access, the UE operating in the single-registration mode shall enter substates 5GMM-REGISTERED.NORMAL-SERVICE or 5GMM-REGISTERED.NON-ALLOWED-SERVICE as described in subclause 5.3.5.2 for 3GPP access and EMM-REGISTERED.NO-CELL-AVAILABLE. At inter-system change from N1 mode to S1 mode in 5GMM-IDLE mode, the UE shall behave as specified in subclause 4.8.2.3. In S1 mode, upon successful completion of an attach or tracking area updating procedure, the UE operating in the single-registration mode shall enter substates 5GMM-REGISTERED.NO-CELL-AVAILABLE for 3GPP access and EMM-REGISTERED.NORMAL-SERVICE. At inter-system change from S1 mode to N1 mode in 5GMM-IDLE mode, the UE operating in the single-registration mode shall enter substates EMM-REGISTERED.NO-CELL-AVAILABLE and 5GMM- REGISTERED.NORMAL-SERVICE for 3GPP access and then initiate the registration procedure for mobility and periodic registration update over 3GPP access indicating "mobility registration updating" in the 5GS registration type IE of the REGISTRATION REQUEST message (see subclause 5.5.1.3). | 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.1.4.3 |
983 | 5.31.16 Service Gap Control | Service Gap Control is an optional feature intended for CIoT UEs to control the frequency at which these UEs can access the network. That is, to ensure a minimum time gap between consecutive Mobile Originated data communications initiated by the UE. This helps reducing peak load situations when there are a large number of these UEs in an operator network. Service Gap Control is intended to be used for "small data allowance plans" for MTC/CIoT UEs where the applications are tolerant to service latency. NOTE 1: Time critical applications, such as regulatory prioritized services like Emergency services can suffer from the latency caused by the Service Gap Control feature. Therefore Service Gap Control feature is not recommended for subscriptions with such applications and services. Service Gap Time is a subscription parameter used to set the Service Gap timer and is enforced in the UE and in the AMF on a per UE level (i.e. the same Service Gap Timer applies for all PDU Sessions that the UE has). The UE indicates its capability of support for Service Gap Control in the Registration Request message to the AMF. The AMF passes the Service Gap Time to the UE in the Registration Accept message for a UE that has indicated its support of the Service Gap Control. The Service Gap Control shall be applied in a UE when a Service Gap Time is stored in the UE context and applied in the AMF when the Service Gap Time is stored in the UE Context in the AMF. Service Gap Control requires the UE to stay in CM-IDLE mode for at least the whole duration of the Service Gap timer before triggering Mobile Originated user data transmission, except for procedures that are exempted (see TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]). The Service Gap timer shall be started each time a UE moves from CM-CONNECTED to CM-IDLE, unless the connection request was initiated by the paging of a Mobile Terminated event, or after a Mobility or Periodic Registration procedure without Follow-on Request indication and without Uplink data status, which shall not trigger a new or extended Service Gap interval. When a Service Gap timer expires, the UE is allowed to send a connection request again. If the UE does so, the Service Gap timer will be restarted at the next CM-CONNECTED to CM-IDLE transition. The Service Gap control is applied in CM-IDLE state only and does not impact UE Mobile Originated user data transmission or Mobile Originated signalling in CM-CONNECTED state. The Service Gap timer is not stopped upon CM-IDLE state to CM-CONNECTED state transition. The UE shall not initiate connection requests for MO user plane data, MO control plane data, or MO SMS when a Service Gap timer is running. The UE shall not initiate PDU Session Establishment Requests when a Service Gap timer is running, unless it is for Emergency services which are allowed. CM-CONNECTED with RRC_INACTIVE is not used for UEs that have a Service Gap Time configured. NOTE 2: As a consequence of allowing Initial Registration Request procedure, the UE with a running Service Gap timer does not initiate further MO signalling, except for Mobility Registration procedure, until the UE receives MT signalling or after the UE has moved to CM-IDLE state and the Service Gap Timer is not running. NOTE 3: Implementations need to make sure that latest and up-to-date data are always sent when a Service Gap timer expires. The AMF may enforce the Service Gap timer by rejecting connection requests for MO user plane data, MO control plane data, or MO SMS when a Service Gap timer is running. The AMF may enforce the Service Gap timer by not allowing MO signalling after Initial Registration requests when a Service Gap timer is running except for Mobility Registration procedure, Periodic Registration procedure or access to the network for regulatory prioritized services like Emergency services, which are allowed. When rejecting the connection requests and the SM signalling after Initial Registration Requests while the Service Gap timer is running, the AMF may include a Mobility Management back-off timer corresponding to the time left of the current Service Gap timer. For UEs that do not support Service Gap Control (e.g. pre-release-16 UEs), Service Gap Control may be enforced using "General NAS level congestion control" as defined in clause 5.19.7.2. NOTE 4: After MT signalling in CM-CONNECTED state the AMF does not further restrict MO signalling when a Service Gap timer is running as this case is considered equal to a connectivity request in response to paging. When the AMF starts the Service Gap timer, the AMF should invoke the Service Gap timer with a value that is slightly shorter than the Service Gap Time value provided to the UE based on the subscription information received from the UDM. NOTE 5: This ensures that the AMF does not reject any UE requests just before the Service Gap timer expires e.g. because of slightly unsynchronized timers between UE and AMF. A UE which transitions from a MICO mode or eDRX power saving state shall apply Service Gap Control when it wakes up if the Service Gap timer is still running. Additional aspects of Service Gap Control: - Service Gap Control applies in all PLMNs. - When the Service Gap timer is running and the UE receives paging, the UE shall respond as normal. - Service Gap Control does not apply to exception reporting for NB-IoT. - Access to the network for regulatory prioritized services like Emergency services are allowed when a Service Gap timer is running. - Service Gap Control shall be effective also for UEs performing de-registration and re-registration unless access to the network for regulatory prioritized services like Emergency services is required. - If the Service Gap timer is running, the Service Gap is applied at PLMN selection as follows: a) Re-registration to the registered PLMN: The remaining Service Gap timer value survives. b) Registration to a different PLMN: The remaining Service Gap timer value survives. c) USIM swap: The Service Gap timer is no longer running and the Service Gap feature does not apply, unless re-instantiated by the serving PLMN. - Multiple uplink packets and downlink packets are allowed during one RRC connection for UE operating within its Rate Control limits. The following procedures are impacted by Service Gap Control: - Registration Procedure, see clause 4.2.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]; - UE Triggered Service Request, see clause 4.2.3.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]; NOTE 6: Since UE triggered Service Request is prevented by Service Gap timer, this implicitly prevents the UE from initiating UPF anchored Mobile Originated Data Transport in Control Plane CIoT 5GS Optimisation (see clause 4.24.1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]), NEF Anchored Mobile Originated Data Transport (see clause 4.25.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]) and MO SMS over NAS in CM-IDLE (see clause 4.13.3.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.31.16 |
984 | 5.3.1.4 5GMM-CONNECTED mode with RRC inactive indication | This subclause is only applicable for UE's 5GMM mode over 3GPP access. The 5GMM-CONNECTED mode with RRC inactive indication is not supported when the UE is in NB-N1 mode. The UE is in 5GMM-CONNECTED mode with RRC inactive indication when the UE is in: a) 5GMM-CONNECTED mode over 3GPP access at the NAS layer; and b) RRC_INACTIVE state at the AS layer (see 3GPP TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]). Unless stated otherwise, the UE behaviour in 5GMM-CONNECTED mode with RRC inactive indication follows the UE behaviour in 5GMM-CONNECTED over 3GPP access, except that: a) the UE shall apply the mobility restrictions; and b) the UE shall perform the PLMN selection procedures as in 5GMM-IDLE mode over 3GPP access. The UE shall transition from 5GMM-CONNECTED mode over 3GPP access to 5GMM-CONNECTED mode with RRC inactive indication upon receiving an indication from the lower layers that the RRC connection has been suspended. NOTE 1: Any pending procedure or uplink data packet when receiving an indication from the lower layers that the RRC connection has been suspended, triggers a request to the lower layers to transition to RRC_CONNECTED state. This is also the case when the pending procedure or uplink data packet triggered a previous request to the lower layers to transition to RRC_CONNECTED state. If the UE in 3GPP access is configured for eCall only mode as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22] then: - if the UE with the N1 NAS signalling connection established for eCall over IMS moved to 5GMM-CONNECTED mode with RRC inactive indication, the UE shall start timer T3444; and - if the UE with the N1 NAS signalling connection established for a call to an HPLMN designated non-emergency MSISDN or URI for test or terminal reconfiguration service moved to 5GMM-CONNECTED mode with RRC inactive indication, the UE shall start timer T3445. Upon: a) a trigger of a procedure which requires sending of a NAS message different from a REGISTRATION REQUEST message with the NG-RAN-RCU bit of the 5GS update type IE set to "UE radio capability update needed"; b) an uplink user data packet to be sent for a PDU session with suspended user-plane resources; c) a trigger to request resources for 5G ProSe direct discovery over PC5 or 5G ProSe direct communication over PC5; d) a trigger to request resources for V2X communication over PC5 (see 3GPP TS 23.287[ Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services ] [6C]); or e) a trigger to request resources for A2X communication over PC5 (see 3GPP TS 23.256[ Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2 ] [6AB]); the UE in 5GMM-CONNECTED mode with RRC inactive indication over 3GPP access shall request the lower layers to transition to RRC_CONNECTED state (see 3GPP TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]). For case b) above, the UE which supports S-NSSAI location validity information, and which has received S-NSSAI location validity information from the AMF, shall request the lower layers to transition to RRC_CONNECTED state only if the UE is inside the NS-AoS with respect to the S-NSSAI which is associated with the PDU session with suspended user-plane resources. NOTE 2: If the UE supports Small Data Transmission (SDT) (see 3GPP TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]), the following applies: a) if the UE due to pending uplink NAS messages or user data packets is requesting the lower layers to transition to RRC_CONNECTED state, but has not received a response from the lower layers, the UE can send the pending NAS messages or user data packets to the lower layers, and can receive multiple downlink NAS messages or multiple downlink user data packets from the lower layers while the UE remains in 5GMM-CONNECTED mode with RRC inactive indication over 3GPP access (i.e., without transitioning to 5GMM-CONNECTED mode). When the NAS layer triggers the transmission of pending uplink NAS messages or user data packets, and if the SDT is ongoing, the NAS layer will receive the response from the lower layers only after the SDT session has completed or failed; b) the NAS layer is not aware of the classification of NAS messages or the user data packets as belonging to the SDT session at the lower layers; and c) the setting of access category and the RRC establishment cause indicated to the lower layers when sending the pending uplink user data packets while the UE remains in 5GMM-CONNECTED mode with RRC inactive indication, is left to implementation. Upon a trigger to send a REGISTRATION REQUEST message with the NG-RAN-RCU bit of the 5GS update type IE set to "UE radio capability update needed", the UE in 5GMM-CONNECTED mode with RRC inactive indication shall move to 5GMM-IDLE mode over 3GPP access and proceed with the registration procedure for mobility and periodic registration update as specified in subclause 5.5.1.3.2. The UE shall transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-CONNECTED mode over 3GPP access upon receiving an indication from the lower layers that the UE has transitioned to RRC_CONNECTED state (see 3GPP TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]). NOTE 3: The AMF can be aware of the transition between 5GMM-CONNECTED mode and 5GMM-CONNECTED mode with RRC inactive indication for a UE (see 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]). The UE shall trigger a transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode upon selection of a PLMN or SNPN that is not an equivalent PLMN or SNPN to the registered PLMN or SNPN. The UE shall not trigger a transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode upon entering a new PLMN or SNPN which is in the list of equivalent PLMNs or SNPNs. The UE shall trigger a transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode upon receiving REFRESH command from the UICC as specified in subclause 5.4.5.3.3. If the UE in 5GMM-CONNECTED mode with RRC inactive indication receives an indication from the lower layers that the RRC connection has been suspended, the UE shall stay in 5GMM-CONNECTED mode with RRC inactive indication. The UE shall re-initiate any pending procedure that had triggered the request to the lower layers to transition to RRC_CONNECTED state, if still needed. When the UE in 5GMM-CONNECTED mode with RRC inactive indication receives a fallback indication from lower layers, and the UE has no pending NAS procedure and no pending uplink user data for PDU session(s) with user-plane resources already established, the UE shall: a) enter 5GMM-IDLE mode; and b) initiate the registration procedure for mobility and periodic registration update as specified for case o) in subclause 5.5.1.3.2. If the UE requests the lower layers to transition to RRC_CONNECTED state at initiation of a registration procedure, a service request procedure or a de-registration procedure, upon fallback indication from lower layers, the UE shall: - enter 5GMM-IDLE mode; - proceed with the pending procedure; and - if the pending procedure is a service request or registration request procedure and the SERVICE REQUEST message, the CONTROL PLANE SERVICE REQUEST message or the REGISTRATION REQUEST message does not include UE request type IE with Request type value set to "NAS signalling connection release", the UE shall include the Uplink data status IE in the SERVICE REQUEST message, the CONTROL PLANE SERVICE REQUEST message or in the REGISTRATION REQUEST message, indicating the PDU session(s) without active user-plane resources for which the UE has pending user data to be sent, if any, and the PDU session(s) for which user-plane resources were active prior to receiving the fallback indication, if any (see subclauses 5.5.1.3 and 5.6.1 for further details). If the UE requests the lower layers to transition to RRC_CONNECTED state for other reason than initiation of a registration procedure, or for other reason than a service request procedure, or for other reason than a de-registration procedure, upon fallback indication from lower layers, the UE shall: 1) enter 5GMM-IDLE mode; 2) initiate the service request procedure and include the Uplink data status IE in the SERVICE REQUEST message or the CONTROL PLANE SERVICE REQUEST message indicating the PDU session(s) for which user-plane resources were active prior to receiving the fallback indication, if any (see subclause 5.6.1 for further details). If the procedure that triggered the request to the lower layers to transition to RRC_CONNECTED state is the UE-initiated NAS transport procedure and the UE had SMS, location services message, or CIoT user data to send, the UE shall also include the SMS, location services message, or CIoT user data in the CONTROL PLANE SERVICE REQUEST message as described in subclause 5.6.1.2.2; and 3) upon successful service request procedure completion, proceed with any pending procedure. If the UE in 5GMM-CONNECTED mode with RRC inactive indication receives a fallback indication from lower layers, and the UE has pending uplink user data for PDU session(s) with user-plane resources already established but no pending NAS procedure, the UE shall: 1) enter 5GMM-IDLE mode; and 2) initiate the service request procedure and include the Uplink data status IE in the SERVICE REQUEST message or the CONTROL PLANE SERVICE REQUEST message indicating the PDU session(s) for which user-plane resources were active prior to receiving the fallback indication (see subclause 5.6.1 for further details). In the above cases when the UE receives a fallback indication from lower layers, if the UE is in non-allowed area or not in allowed area, the UE shall behave as specified in subclause 5.3.5. If the UE in 5GMM-CONNECTED mode with RRC inactive indication receives an indication from the lower layers that the resumption of the RRC connection has failed, and: a) if the lower layers indicate that access barring is applicable for all access categories except categories 0 and 2, or access barring is applicable for all access categories except category 0, the UE shall: 1) stay in 5GMM-CONNECTED mode with RRC inactive indication; b) else, the UE shall: 1) enter 5GMM-IDLE mode; and 2) if the UE - does not have pending uplink user data for PDU session(s) with user-plane resources already established, initiate the registration procedure for mobility and periodic registration update used for mobility (i.e. the 5GS registration type IE set to "mobility registration updating" in the REGISTRATION REQUEST message) for N1 NAS signalling connection recovery as specified for case f) in subclause 5.5.1.3.2; or - has pending uplink user data for PDU session(s) with user-plane resources already established or has pending NAS procedure other than a registration, service request, or de-registration procedure, then initiate the service request procedure for N1 NAS signalling connection recovery as specified for case i) or j) in subclause 5.6.1.1. NOTE 4: An indication from the lower layer that the RRC connection has been released with cause "RRC resume failure" can be considered as an indication that the resumption of the RRC connection has failed. The UE shall transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode over 3GPP access upon receiving from the lower layers: a) indication of transition from RRC_INACTIVE state to RRC_IDLE state; or b) indication of cell selection to E-UTRAN or another RAT that the UE supports. If the UE in 5GMM-CONNECTED mode with RRC inactive indication receives an indication from the lower layers about the cell (re-)selection to different RAT that the UE supports, the UE shall initiate the registration procedure for mobility or periodic registration update used for mobility (i.e. the 5GS registration type IE set to "mobility registration updating" in the REGISTRATION REQUEST message) as specified in subclause 5.5.1.3.2. If the UE in 5GMM-CONNECTED mode with RRC inactive indication receives an indication from the lower layers of a transition from RRC_INACTIVE state to RRC_IDLE state and 5GMM-REGISTERED.LIMITED-SERVICE is entered, the UE shall subsequently upon entering state 5GMM-REGISTERED.NORMAL-SERVICE and if there is no uplink user data or signalling pending, initiate the registration procedure for mobility and periodic registration update used for mobility (i.e. the 5GS registration type IE set to "mobility registration updating" in the REGISTRATION REQUEST message) for N1 NAS signalling connection recovery as specified in subclause 5.5.1.3.2. If the UE in 5GMM-CONNECTED mode with RRC inactive indication receives an indication from the lower layers about RAN paging and the MUSIM UE decides not to initiate the service request procedure with service type set to "mobile terminated services" or control plane service type set to "mobile terminating request" to respond to the RAN paging, the UE may initiate the service request procedure and set request type to "NAS signalling connection release" in the UE request type IE and service type to "signalling" in the SERVICE REQUEST message or set request type to "NAS signalling connection release" in the UE request type IE and control plane service type set to "mobile originating request" in the CONTROL PLANE SERVICE REQUEST message to reject the RAN paging as specified in subclause 5.6.1.2 for case o of subclause 5.6.1.1. The UE may include its paging restriction preferences in the Paging restriction IE in the SERVICE REQUEST message or CONTROL PLANE SERVICE REQUEST message as specified in subclause 5.6.1.2 for case o of subclause 5.6.1.1. NOTE 5: The interworking between the NAS layer and the AS layer triggered by RAN paging is up to UE implementation. NOTE 6: As an implementation option, the MUSIM UE is allowed to not respond to RAN paging based on the information available in the paging message, e.g. voice service indication. Upon receiving AMF paging indication from the lower layers, the UE shall transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode over 3GPP access and handle the AMF paging same as the paging request received in the 5GMM-IDLE mode over 3GPP access as specified in subclause 5.6.1. If the UE supporting the reconnection to the network due to RAN timing synchronization status change has been requested to reconnect to the network upon receiving an indication of a change in the RAN timing synchronization status (see subclauses 5.4.4.2, 5.5.1.2.4, and 5.5.1.3.4) and the UE receives an indication of a change in the RAN timing synchronization status, the UE in 5GMM-CONNECTED mode with RRC inactive indication shall request the lower layers to transition to RRC_CONNECTED state. | 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.3.1.4 |
985 | 5.6.3.4 Abnormal cases on the network side | The following abnormal cases can be identified: a) Expiry of timer T3565. The network shall, on the first expiry of the timer T3565, retransmit the NOTIFICATION message and shall reset and start timer T3565. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3565, the procedure shall be aborted. In addition, upon the fifth expiry of timer T3565: For case a) in subclause 5.6.3.1, the AMF should notify the SMF that the UE is unreachable. The AMF may enter 5GMM-IDLE mode over 3GPP access. For case b) in subclause 5.6.3.1, the AMF may either: 1) perform the paging procedure over the 3GPP access; or 2) notify the SMF that the UE is unreachable. NOTE: Whether the AMF performs the paging procedure or notifies the SMF is up to operator's policies. b) De-registration procedure collision If the network receives a DEREGISTRATION REQUEST message before it receives a SERVICE REQUEST message or REGISTRATION REQUEST message, the AMF shall stop timer T3565 and proceed de-registration procedure as specified in subclause 5.5.2. | 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.6.3.4 |
986 | 5.5.1.2.4A Attach successful for EPS services and not accepted for SMS services | Apart from the actions on the tracking area updating attempt counter, the description for attach for EPS services as specified in clause 5.5.1.2.4 shall be followed. In addition, the following description for attach for SMS services applies. In NB-S1 mode, if the UE requested "SMS only" in the Additional update type IE and supports NB-S1 mode only, the MME decides to accept the attach request for EPS services only and: - the location update for non-EPS services is not accepted by the VLR as specified in 3GPP TS 29.118[ Mobility Management Entity (MME) - Visitor Location Register (VLR) SGs interface specification ] [16A]; or - the MME decides to not accept the attach request for "SMS only", the MME shall set the EPS attach result IE to "EPS only", shall not indicate "SMS only" in the Additional update result IE in the ATTACH ACCEPT message and shall include an appropriate SMS services status value. The UE receiving the ATTACH ACCEPT message takes one of the following actions depending on the value included in the SMS services status IE: "SMS services not available" The UE shall stop timer T3410 if still running, shall reset the tracking area updating attempt counter, shall set the EPS update status to EU1 UPDATED and shall enter state EMM-REGISTERED.NORMAL-SERVICE. The USIM shall be considered as invalid for SMS services until switching off or the UICC containing the USIM is removed or the timer T3245 expires as described in clause 5.3.7a. "SMS services not available in this PLMN" The UE shall stop timer T3410 if still running, shall reset the tracking area updating attempt counter, shall set the EPS update status to EU1 UPDATED and shall enter state EMM-REGISTERED.NORMAL-SERVICE. The UE may provide a notification to the user or the upper layers that the SMS services are not available. The UE shall not attempt normal attach or tracking area updating procedures indicating "SMS only" with current PLMN until switching off the UE or the UICC containing the USIM is removed. Additionally, the UE may perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. "Network failure" The UE shall stop timer T3410 if still running. The tracking area updating attempt counter shall be incremented, unless it was already set to 5. 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.NORMAL-SERVICE. When timer T3411 expires the normal tracking area updating procedure for EPS services and "SMS only" or the combined tracking area updating procedure for EPS services and "SMS only" is triggered. If the tracking area updating attempt counter is equal to 5: - the UE shall start timer T3402, shall set the EPS update status to EU1 UPDATED and shall enter state EMM-REGISTERED.NORMAL-SERVICE. When timer T3402 expires the normal tracking area updating procedure for EPS services and "SMS only" or the combined tracking area updating procedure for EPS services and "SMS only" is triggered. "Congestion" The UE shall stop the timer T3410 if still running. The tracking area updating attempt counter shall be set to 5. The UE shall start the timer T3402, shall set the EPS update status to EU1 UPDATED, and shall enter state EMM-REGISTERED.NORMAL-SERVICE. When timer T3402 expires the normal tracking area updating procedure for EPS services and "SMS only" or the combined tracking area updating procedure for EPS services and "SMS only" is triggered. Other values are considered as abnormal cases. The attach procedure shall be considered as failed for SMS services. The behaviour of the UE in those cases is specified in clause 5.5.1.2.6A. | 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.1.2.4A |
987 | 5.2.2.2.4 Namf_Communication_N1MessageNotify service operation | Service operation name: Namf_Communication_N1MessageNotify Description: AMF notifies the N1 message received from the UE to a destination CN NF. Input, Required: AMF ID (GUAMI), N1 Message(s) Input, Optional: local time zone, UE's current location, AN access information (e.g. AN type AN N2 terminating point, CAG Identifier(s) of the CAG cell), Allowed NSSAI, Mapping Of Allowed NSSAI, SUPI, MM Context, LMF identification, PRU subscription verification result. Output, Required: None. Output, Optional: None. The destination NF type to be notified is determined based on one of the following: - The N1 message type is always known to be consumed by one particular NF type; or - An NF had explicitly subscribed for the particular N1 message type to be notified towards it. NOTE: Whether notification Ack need a separate message or be realized in the transport layer will be determined in TS 29.518[ 5G System; Access and Mobility Management Services; Stage 3 ] [18]. The optional AN access information (if available), SUPI, MM Context, Allowed NSSAI and Mapping Of Allowed NSSAI parameters are included if the service operation is invoked towards a peer AMF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.2.2.4 |
988 | 6.2.4A.6 A-MPR for CA_NS_06 | If the UE is configured to CA_7C and it receives IE CA_NS_06 the allowed maximum output power reduction applied to transmission on the PCC and the SCC for contiguously aggregated signals is specified in Table 6.2.4A.6-1. Table 6.2.4A.6-1: Contiguous Allocation A-MPR for CA_NS_06 If the UE is configured to CA_7C and it receives IE CA_NS_06 the allowed maximum output power reduction applied to transmissions on the PCell and the SCell with non-contiguous resource allocation is defined as follows: A-MPR = CEIL {MA, 0.5} Where MA is defined as follows MA = -13.33A + 17.5 ; 0 ≤ A < 0.15 -6.47A + 16.47 ; 0.15 ≤ A ≤ 1 Where A = NRB_alloc / NRB_agg. | 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.2.4A.6 |
989 | 4.5 Multi-Radio Dual Connectivity | NG-RAN supports Multi-Radio Dual Connectivity (MR-DC) operation whereby a UE in RRC_CONNECTED is configured to utilise radio resources provided by two distinct schedulers, located in two different NG-RAN nodes connected via a non-ideal backhaul, one providing NR access and the other one providing either E-UTRA or NR access. Further details of MR-DC operation, including Conditional PSCell Addition (CPA) and Conditional PSCell Change (CPC), can be found in TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [21]. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 4.5 |
990 | 5.20c Provisioning of traffic characteristics and monitoring of performance characteristics for a group | NEF provisioning capability as defined in clause 5.20 allows an AF to perform provisioning of traffic characteristics and monitoring of performance characteristics for a group of UEs as specified in clause 4.15.6.14 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] and clause 6.1.3.28 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. NOTE : The AF may use application layer functionalities to handle requests for UE-to-UE traffic as defined by SA WG6. The NEF determines whether or not to invoke the TSCTSF in the same way as for AF session with required QoS procedure, as described in step 2 of clause 4.15.6.6 in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. In the case that the TSCTSF is used, the TSCTSF receives the AF requested QoS information from the NEF. In the case that TSCTSF is not used, the AF request is handled as described in clause 4.15.6.14 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] and clause 6.1.3.28 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. When the TSCTSF receives the AF requested QoS information from NEF or the PCF(s) receive the AF requested QoS information from UDR, the TSCTSF or PCF (s) manage the AF requested QoS information for each UE group member within the group as follows: - Translate the External Group ID into a list of SUPIs by invoking Nudm_SDM_Get service. - Determine which of these UE group members have active PDU Sessions matching the DNN and S-NSSAI and determine the relevant UE address. - Manage the request status (activated, de-activated, failed) for each UE group member within the group: - Apply the AF requested QoS information if the UE group member is registered or has active PDU Session matching the DNN and S-NSSAI. Set the status to activated if the QoS resources are assigned for the UE group member, otherwise, failed. - Set the status to de-activated if the UE group member is not registered or has no active PDU Session matching the DNN and S-NSSAI. - Delete the request status for the UE group member if the UE group member is removed from the group, and further revokes AF request QoS information if the request status is activated. - Check whether to apply the AF requested QoS information and update the request status for the UE group member if the UE group member is newly added to the group. - When the AF requested QoS information contains temporal invalidity condition: - Revoke AF requested QoS information for each UE group member which is marked as active, so to e.g. to remove or modify PCC rules as defined in clause 4.16.5.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] if the start-time is reached. - Apply AF requested QoS information for each UE group member that has active PDU Sessions matching the DNN and S-NSSAI, e.g. to add or modify PCC rules as defined in clause 4.16.5.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.20c |
991 | 5.3.14 UE Radio Capability Match Request | If the MME, e.g. based on SRVCC capability in NAS, UE Usage Type or local policy, requires more information on the UE radio capabilities support to be able to set the IMS voice over PS Session Supported Indication (see clause 4.3.5.8), then the MME may send a UE Radio Capability Match Request message to the eNodeB. This procedure is typically used during the Initial Attach procedure, during Tracking Area Update procedure for the "first TAU following GERAN/UTRAN Attach" or for "UE radio capability update" or when MME has not received the Voice Support Match Indicator (as part of the MM Context). Figure 5.3.14-1: UE Radio Capability Match Request 1 The MME indicates whether the MME wants to receive Voice support match indicator. The MME may include the UE Radio Capability information that it has previously received from the eNodeB via a S1-AP UE CAPABILITY INFO INDICATION as described in clause 5.11.2. 2. Upon receiving a UE Radio Capability Match Request from the MME, if the eNodeB has not already received the UE radio capabilities from the UE or from MME in step 1, the eNodeB requests the UE to upload the UE radio capability information by sending the RRC UE Capability Enquiry. 3. The UE provides the eNodeB with its UE radio capabilities sending the RRC UE Capability Information. 4. The eNodeB checks whether the UE radio capabilities are compatible with the network configuration for ensuring voice service continuity of voice calls initiated in IMS. For determining the appropriate UE Radio Capability Match Response, the eNodeB is configured by the operator to check whether the UE supports certain capabilities required for Voice continuity of voice calls using IMS PS. In a shared network, the eNodeB keeps a configuration separately per PLMN. NOTE 1: What checks to perform depends on network configuration, i.e. following are some examples of UE capabilities to be taken into account: - the SRVCC, and UTRAN/E-UTRAN Voice over PS capabilities; - the Radio capabilities for UTRAN/E-UTRAN FDD and/or TDD; and/or - the support of UTRAN/E-UTRAN frequency bands. NOTE 2: The network configuration considered in the decision for the Voice Support Match Indicator is homogenous within a certain area (e.g. MME Pool Area) in order to guarantee that the Voice Support Match Indicator from the eNodeB is valid within such area. The eNodeB provides a Voice Support Match Indicator to the MME to indicate whether the UE capabilities and networks configuration are compatible for ensuring voice service continuity of voice calls initiated in IMS. The MME stores the received Voice support match indicator in the MM Context and uses it as an input for setting the IMS voice over PS Session Supported Indication. 5. If eNodeB requested radio capabilities from UE in step 2 and 3, eNodeB also sends the UE radio capabilities to the MME using the S1-AP UE CAPABILITY INFO INDICATION. The MME stores the UE radio capabilities without interpreting them for further provision to the eNodeB in cases described in clause 5.11.2. NOTE 3: Steps 4 and 5 may be received by the MME in any order. | 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.3.14 |
992 | 7.7 SCG/MCG failure handling | RLF is declared separately for the MCG and for the SCG. If radio link failure is detected for MCG, fast MCG link recovery is configured and the SCG is not deactivated, the UE triggers fast MCG link recovery. Otherwise, the UE initiates the RRC connection re-establishment procedure. During the execution of PSCell addition or PSCell change, if radio link failure is detected for MCG, the UE initiates the RRC connection re-establishment procedure. During fast MCG link recovery, the UE suspends MCG transmissions for all radio bearers, except SRB0, and, if any, BH RLC channels and reports the failure with MCGFailureInformation message to the MN via the SCG, using the SCG leg of split SRB1 or SRB3. The UE includes in the MCGFailureInformation message the measurement results available according to current measurement configuration of both the MN and the SN. Once the fast MCG link recovery is triggered, the UE maintains the current measurement configurations from both the MN and the SN, and continues measurements based on configuration from the MN and the SN, if possible. The UE initiates the RRC connection re-establishment procedure if it does not receive an RRCConnectionReconfiguration message, RRCReconfiguration message, MobilityFromNRCommand message, MobilityFromEUTRACommand message, RRCConnectionRelease message or RRCRelease message within a certain time after fast MCG link recovery was initiated. Upon reception of the MCGFailureInformation message, the MN can send RRCConnectionReconfiguration message, RRCReconfiguration message, MobilityFromNRCommand message, MobilityFromEUTRACommand message, RRCConnectionRelease message or RRCRelease message to the UE, using the SCG leg of split SRB1 or SRB3. Upon receiving an RRCConnectionReconfiguration message, RRCReconfiguration message, MobilityFromNRCommand message or MobilityFromEUTRACommand message, the UE resumes MCG transmissions for all radio bearers. Upon receiving an RRCConnectionRelease message or RRCRelease message, the UE releases all the radio bearers and configurations. NOTE 1: It is up to network implementation to guarantee that the RRC-related messages are delivered to the UE by the SN before the release of its control plane resources. The following SCG failure cases are supported: - SCG RLF; - SCG beam failure while the SCG is deactivated; - SN addition/change failure; - For EN-DC, NGEN-DC and NR-DC, SCG configuration failure or CPC configuration failure (only for messages on SRB3); - For EN-DC, NGEN-DC and NR-DC, SCG RRC integrity check failure (on SRB3); - For EN-DC, NGEN-DC and NR-DC, consistent UL LBT failure on PSCell; - For IAB-MT, reception of a BH RLF indication from SCG; - CPA/CPC or subsequent CPAC execution failure; - SCG LTM cell switch failure. Upon SCG failure, if MCG transmissions of radio bearers are not suspended, the UE suspends SCG transmissions for all radio bearers and, if any, BH RLC channels, if the SCG failure is not triggered by SCG beam failure, and reports the SCGFailureInformation to the MN, instead of triggering re-establishment. If SCG failure is detected while MCG transmissions for all radio bearers are suspended, the UE initiates the RRC connection re-establishment procedure. SCG/MCG failure handling by UE also applies to IAB MT. In all SCG failure cases, the UE maintains the current measurement configurations from both the MN and the SN and the UE continues measurements based on configuration from the MN and the SN if possible. The SN measurements configured to be routed via the MN will continue to be reported after the SCG failure. NOTE 2: UE may not continue measurements based on configuration from the SN after SCG failure in certain cases (e.g. UE cannot maintain the timing of PSCell). The UE includes in the SCGFailureInformation message the measurement results available according to current measurement configuration of both the MN and the SN. The MN handles the SCGFailureInformation message and may decide to keep, change, or release the SN/SCG. In all the cases, the measurement results according to the SN configuration and the SCG failure type may be forwarded to the old SN and/or to the new SN. In case of CPA/CPC, upon transmission of the SCGFailureInformation message to the MN, the UE stops evaluating the CPA/CPC execution condition. In case of subsequent CPAC, upon transmission of the SCGFailureInformation message to the MN or upon transmission of the MCGFailureInformation message to the SN, the UE stops evaluating the subsequent CPAC execution condition. The UE is not required to continue measurements for candidate PSCell(s) for execution condition upon transmission of the SCGFailureInformation message to the MN. | 3GPP TS 37.340 | Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 | RAN2 | 3GPP Series : 37 , Multiple radio access technology aspects | 7.7 |
993 | 6.3.5F.1 Absolute power tolerance | The minimum requirement for absolute power tolerance is given in Table 6.3.5F.1-1 over the power range bounded by the Maximum output power as defined in subclause 6.2.2F and the Minimum output power as defined in subclause 6.3.2F. Table 6.3.5F.1-1: Absolute power tolerance - I In case of -15 dB ≤ Ês/Iot < -6 dB, the absolute power tolerance given in Table 6.3.5F.1-2 applies if the UE transmit power is not mandated to be PCMAX,c according to the UE uplink power control procedure or random access procedure in Section 16 of [6] (e.g. the lowest configured repetition level is used for NPRACH transmission or the number of repetitions of the allocated NPUSCH RUs is no more than 2). Table 6.3.5F.1-2: Absolute power tolerance - II | 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.5F.1 |
994 | 6.10.1 Description | 3GPP SEES and (e)FMSS features allow the operator to expose network capabilities e.g. QoS policy to third-party ISPs/ICPs. With the advent of 5G, new network capabilities need to be exposed to the third-party (e.g. to allow the third-party to customize a dedicated physical or virtual network or a dedicated network slice for diverse use cases; to allow the third-party to manage a trusted third-party application in a Service Hosting Environment to improve user experience, and efficiently utilize backhaul and application resources). | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.10.1 |
995 | 5.6A Channel bandwidth for CA | For intra-band contiguous carrier aggregation Aggregated Channel Bandwidth, Aggregated Transmission Bandwidth Configuration and Guard Bands are defined as follows, see Figure -1. Figure 5.6A-1. Definition of Aggregated channel bandwidth and aggregated channel bandwidth edges The aggregated channel bandwidth, BWChannel_CA, is defined as BWChannel_CA = Fedge,high - Fedge,low [MHz]. The lower bandwidth edge Fedge,low and the upper bandwidth edge Fedge,high of the aggregated channel bandwidth are used as frequency reference points for transmitter and receiver requirements and are defined by Fedge,low = FC,low - Foffset,low Fedge,high = FC,high + Foffset,high The lower and upper frequency offsets depend on the transmission bandwidth configurations of the lowest and highest assigned edge component carrier and are defined as Foffset,low = (0.18NRB,low + f1)/2 + BWGB [MHz] Foffset,high = (0.18NRB,high + f1)/2 + BWGB [MHz] where f1 = f for the downlink with f the subcarrier spacing and f1 = 0 for the uplink, while NRB,low and NRB,high are the transmission bandwidth configurations according to Table 5.6-1 for the lowest and highest assigned component carrier, respectively. BWGB denotes the Nominal Guard Band and is defined in Table 5.6A-1, and the factor 0.18 is the PRB bandwidth in MHz. NOTE: The values of BWChannel_CA for UE and BS are the same if the lowest and the highest component carriers are identical. Aggregated Transmission Bandwidth Configuration is the number of the aggregated RBs within the fully allocated Aggregated Channel bandwidth and is defined per CA Bandwidth Class (Table 5.6A-1). For intra-band non-contiguous carrier aggregation Sub-block Bandwidth and Sub-block edges are defined as follows, see Figure -2. Figure -2. Non-contiguous intraband CA terms and definitions The lower sub-block edge of the Sub-block Bandwidth (BWChannel,block) is defined as Fedge,block, low = FC,block,low - Foffset,block, low. The upper sub-block edge of the Sub-block Bandwidth is defined as Fedge,block,high = FC,block,high + Foffset,block,high . The Sub-block Bandwidth, BWChannel,block, is defined as follows: BWChannel,block = Fedge,block,high - Fedge,block,low [MHz] The lower and upper frequency offsets Foffset,block,low and Foffset,block,high depend on the transmission bandwidth configurations of the lowest and highest assigned edge component carriers within a sub-block and are defined as Foffset,block,low = (0.18NRB,low + f1) /2 + BWGB [MHz] Foffset,block,high = (0.18NRB,high + f1)/2 + BWGB [MHz] where f1 = f for the downlink with f the subcarrier spacing and f1 = 0 for the uplink, while NRB,low and NRB,high are the transmission bandwidth configurations according to Table 5.6-1 for the lowest and highest assigned component carrier within a sub-block, respectively. BWGB denotes the Nominal Guard Band and is defined in Table 5.6A-1, and the factor 0.18 is the PRB bandwidth in MHz. The sub-block gap size between two consecutive sub-blocks Wgap is defined as Wgap = Fedge,block n+1,low - Fedge,block n,high [MHz] Table 5.6A-1: CA bandwidth classes and corresponding nominal guard bands The channel spacing between centre frequencies of contiguously aggregated component carriers is defined in subclause 5.7.1A. | 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 | 5.6A |
996 | 4.11.0a.2a.7 UE Policy Association Modification initiated by the PCF for a PDU Session | This procedure addresses the scenario where a Policy Control Request Trigger condition is met by the PCF for a PDU Session. The procedure is based on the one defined in clause 4.16.12.1.1 with the following differences: In the non-roaming case, the V-PCF is not involved, the AMF is replaced by the PCF for the PDU Session, and the role of the H-PCF is performed by the PCF for the UE. For the Home Routed roaming scenarios, the V-PCF is not involved, the AMF is replaced by the H-PCF for the PDU Session, and the role of the H-PCF is performed by the H-PCF for the UE. For the LBO roaming scenarios, the AMF is replaced by the V-PCF for the PDU Session, the role of the V-PCF is performed by the V-PCF for the UE and the role of the H-PCF is performed by the H-PCF for the UE. - Step 1: Same as in clause 4.16.12.1.1 step 1, with the following exceptions: In LBO roaming the V-PCF for the PDU Session contacts the V-PCF for the UE and steps 2 and 3 are executed. The V-PCF for the UE contacts with the H-PCF for the UE discovered during the establishment of the UE Policy association as described in clause 4.11.0a.2a.5. For non-roaming or Home Routed roaming the (H-)PCF for the PDU Session contacts the (H-)PCF for the UE and step 4 follows. - Steps 2, 3,4: Same as in clause 4.16.12.1.1. - Step 5: The (H-)PCF may create the UE policy container including UE policy information as defined in clause 6.6 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. The (H-) PCF checks whether the UE Policy Association for the UE is established for a UE in EPS by checking the RAT-Type of the UE Policy Association and in this case the (H-)PCF may send the UE Policy Container in the Npcf_UEPolicyControl UpdateNotify Request. - Step 6: Same as in clause 4.16.12.1.1. - Steps 7, 8 and 9 are replaced by steps 10-13 of procedure UE Policy Association Establishment in EPS from clause 4.11.0a.2a.5. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.0a.2a.7 |
997 | C.4 Guidelines for interoperability in a multi-vendor environment | The specification of a sequence number management scheme affects only the USIM and the AuC which are both under the control of one operator. Therefore, the specification of such a scheme is entirely at the discretion of an operator. Nevertheless, certain operators may not want to define a scheme of their own. Instead, they may want to rely on vendors implementing one of the schemes according to the profiles in C.3 or variants thereof. If these operators have multiple vendors for USIMs and/or AuCs, and the operators wish to move subscribers from the AuC of one vendor to that supplied by another one implementing a different scheme then this will work smoothly only when the following guidelines are adhered to by all the sequence number management schemes implemented in the operator’s domain. - The array mechanism specified in clauses C.1.2 and C.2 is used in the USIM to verify SQNs. The length of the used by the USIM to index the array shall be not less than the length of the used by the AuC when allocating index values. However, it is recommended that the same length of 5 bits is used in USIMs and AuCs. This is the same length as proposed for all profiles in clause C.3. - Relation to Annex F: if the AMF field is used to signal further parameters relevant to sequence number management (age limit L) then the formats of the AMF and its interpretation by the USIM must be the same for all implementations in the operator’s domain. - is larger than a specified minimum. This is necessary to accommodate schemes as in C.3.2 according to note 7 of C.2.3. We propose 228. - There are no requirements on the synchronicity of clocks in different AuCs for the time-based schemes. For the entirely time-based scheme, the following is recommended when moving users from one AuC to another one: The DIF value is updated in an appropriate manner when moving subscribers from an AuC to another AuC. More specifically, assume a user is moved from AuC1 to AuC2. If AuC1 is of profile 3 and AuC2 is of any profile then AuC1 sends GLC+DIF as SEQ_HE to AuC2. In the receiving end, if AuC2 is of profile 3 while AuC1 is of any profile then AuC2 sets DIF value for this user as DIF = SEQ_HE - GLC. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | C.4 |
998 | 5.4.2.3 NAS security mode command accepted by the UE | Upon receipt of the SECURITY MODE COMMAND message, the UE shall check whether the security mode command can be accepted or not. This is done by performing the integrity check of the message, and by checking that the received Replayed UE security capabilities IE has not been altered compared to the latest values that the UE sent to the network. When the SECURITY MODE COMMAND message includes an EAP-success message the UE handles the EAP-success message and the ABBA as described in subclause 5.4.1.2.2.8, 5.4.1.2.3.1, 5.4.1.2.3A.1, 5.4.1.2.3B.1 and 5.4.1.2.3C.1. If: a) the UE is registered for emergency services, performing initial registration for emergency services, establishing an emergency PDU session or has an emergency PDU session established; b) the W-AGF acts on behalf of the FN-RG; c) the W-AGF acts on behalf of the N5GC device; or d) the 5G-RG acts on behalf of the AUN3 device, and the SECURITY MODE COMMAND message is received with ngKSI value "000" and 5G-IA0 and 5G-EA0 as selected 5G NAS security algorithms, the UE shall locally derive and take in use 5G NAS security context. The UE shall delete existing current 5G NAS security context. The UE shall accept a SECURITY MODE COMMAND message indicating the "null integrity protection algorithm" 5G-IA0 as the selected 5G NAS integrity algorithm only if the message is received when a) the UE is registered for emergency services, performing initial registration for emergency services, establishing an emergency PDU session or has an emergency PDU session established; or b) the W-AGF acts on behalf of the FN-RG; c) the W-AGF acts on behalf of the N5GC device; or d) the 5G-RG acts on behalf of the AUN3 device. If the type of security context flag included in the SECURITY MODE COMMAND message is set to "native security context" and if the ngKSI matches a valid non-current native 5G NAS security context held in the UE while the UE has a mapped 5G NAS security context as the current 5G NAS security context, the UE shall take the non-current native 5G NAS security context into use which then becomes the current native 5G NAS security context and delete the mapped 5G NAS security context. The UE shall ignore the Replayed S1 UE security capabilities IE if this IE is included in the SECURITY MODE COMMAND message. If the SECURITY MODE COMMAND message can be accepted, the UE shall take the 5G NAS security context indicated in the message into use. The UE shall in addition reset the uplink NAS COUNT counter if: a) the SECURITY MODE COMMAND message is received in order to take a 5G NAS security context into use created after a successful execution of the 5G AKA based primary authentication and key agreement procedure or the EAP based primary authentication and key agreement procedure; or b) the SECURITY MODE COMMAND message received includes the type of security context flag set to "mapped security context" in the NAS key set identifier IE the ngKSI does not match the current 5G NAS security context, if it is a mapped 5G NAS security context. If the SECURITY MODE COMMAND message can be accepted and a new 5G NAS security context is taken into use and SECURITY MODE COMMAND message does not indicate the "null integrity protection algorithm" 5G-IA0 as the selected NAS integrity algorithm, the UE shall: - if the SECURITY MODE COMMAND message has been successfully integrity checked using an estimated downlink NAS COUNT equal to 0, then the UE shall set the downlink NAS COUNT of this new 5G NAS security context to 0; - otherwise the UE shall set the downlink NAS COUNT of this new 5G NAS security context to the downlink NAS COUNT that has been used for the successful integrity checking of the SECURITY MODE COMMAND message. If the SECURITY MODE COMMAND message includes the horizontal derivation parameter indicating "KAMF derivation is required", the UE shall derive a new K'AMF, as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24] for KAMF to K'AMF derivation in mobility, and set both uplink and downlink NAS COUNTs to zero. When the new 5G NAS security context is taken into use for current access and the UE is registered with the same PLMN over the 3GPP access and the non-3GPP access: a) the UE is in 5GMM-IDLE mode over the non-current access, the AMF and the UE shall activate the new 5G NAS security context over the non-current access as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. The AMF and the UE shall set the downlink NAS COUNT and uplink NAS COUNT to zero for the non-current access; or b) the UE is in 5GMM-CONNECTED mode over the non-current access, the AMF shall send the SECURITY MODE COMMAND message over the non-current access to activate the new 5G NAS security context that was activated over the current access as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. The AMF shall include the same ngKSI in the SECURITY MODE COMMAND message to identify the new 5G NAS security context. NOTE 1: If the UE was in 5GMM-CONNECTED mode over the non-current access when the new 5G NAS security context was taken into use for the current access and the UE enters 5GMM-IDLE mode over the non-current access before receiving a SECURITY MODE COMMAND message over the non-current access, the UE conforms to bullet a). NOTE 2: If the UE was in 5GMM-CONNECTED mode over the non-current access when the new 5G NAS security context was taken into use and the N1 NAS signalling connection is lost over the non-current access before sending a SECURITY MODE COMMAND message over the non-current access, the AMF conforms to bullet a). If the SECURITY MODE COMMAND message includes the horizontal derivation parameter indicating "KAMF derivation is not required" or the Additional 5G security information IE is not included in the message, the UE is registered with the same PLMN over the 3GPP access and non-3GPP access, then after the completion of a security mode control procedure over the current access: a) the UE is in 5GMM-IDLE mode over the non-current access, the AMF and the UE shall activate the new 5G NAS security context for the non-current access. If a primary authentication and key agreement procedure was completed before the security mode control procedure, the AMF and the UE shall set the downlink NAS COUNT and uplink NAS COUNT to zero for the non-current access, otherwise the downlink NAS COUNT and uplink NAS COUNT for the non-3GPP access are not changed; or b) the UE is in 5GMM-CONNECTED mode over the non-current access, the AMF shall send the SECURITY MODE COMMAND message over the non-current access to activate the new 5G NAS security context that was activated over the current access as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. The AMF shall include the same ngKSI in the SECURITY MODE COMMAND message to identify the new 5G NAS security context. NOTE 3: If the UE was in 5GMM-CONNECTED mode over the non-current access when the new 5G NAS security context was taken into use for the current access and the UE enters 5GMM-IDLE mode over the non-current access before receiving a SECURITY MODE COMMAND message over the non-current access, the UE conforms to bullet a). NOTE 4: If the UE was in 5GMM-CONNECTED mode over the non-current access when the new 5G NAS security context was taken into use and the N1 NAS signalling connection is lost over the non-current access before sending a SECURITY MODE COMMAND message over the non-current access, the AMF conforms to bullet a). If the SECURITY MODE COMMAND message can be accepted, the UE shall send a SECURITY MODE COMPLETE message integrity protected with the selected 5GS integrity algorithm and the 5G NAS integrity key based on the KAMF or mapped K'AMF if the type of security context flag is set to "mapped security context" indicated by the ngKSI. When the SECURITY MODE COMMAND message includes the type of security context flag set to "mapped security context" in the NAS key set identifier IE, then the UE shall check whether the SECURITY MODE COMMAND message indicates the ngKSI of the current 5GS security context, if it is a mapped 5G NAS security context, in order not to re-generate the K'AMF. Furthermore, if the SECURITY MODE COMMAND message can be accepted, the UE shall cipher the SECURITY MODE COMPLETE message with the selected 5GS ciphering algorithm and the 5GS NAS ciphering key based on the KAMF or mapped K'AMF indicated by the ngKSI. The UE shall set the security header type of the message to "integrity protected and ciphered with new 5G NAS security context". From this time onward the UE shall cipher and integrity protect all NAS signalling messages with the selected 5GS integrity and ciphering algorithms. If the AMF indicated in the SECURITY MODE COMMAND message that the IMEISV is requested and: a) if the UE: 1) supports at least one 3GPP access technology, the UE shall include its IMEISV in the IMEISV IE of the SECURITY MODE COMPLETE message; or 2) does not support any 3GPP access technology (i.e. satellite NG-RAN, NG-RAN, satellite E-UTRAN, E-UTRAN, UTRAN or GERAN) and supports NAS over untrusted or trusted non-3GPP access, the UE shall include its EUI-64 in the non-IMEISV PEI IE of the SECURITY MODE COMPLETE message; or b) if: 1) the 5G-RG contains neither an IMEISV nor an IMEI or when the 5G-RG acts on behalf of the AUN3 device; or 2) when the W-AGF acts on behalf of the FN-RG (or on behalf of the N5GC device), the 5G-RG or the W-AGF acting on behalf of the FN-RG (or on behalf of the N5GC device) shall include the MAC address and the MAC address usage restriction indication determined as specified in subclause 5.3.2 in the non-IMEISV PEI IE in the SECURITY MODE COMPLETE message. If during an ongoing registration procedure, deregistration procedure, or service request procedure, the UE receives a SECURITY MODE COMMAND message which includes the Additional 5G security information IE with the RINMR bit set to "Retransmission of the initial NAS message requested", the UE shall include the entire unciphered REGISTRATION REQUEST message, DEREGISTRATION REQUEST message, SERVICE REQUEST message or CONTROL PLANE SERVICE REQUEST message, which the UE had previously included in the NAS message container IE of the initial NAS message (i.e. REGISTRATION REQUEST message, DEREGISTRATION REQUEST MESSAGE, SERVICE REQUEST message or CONTROL PLANE SERVICE REQUEST message, respectively), in the NAS message container IE of the SECURITY MODE COMPLETE message. The retransmitted CONTROL PLANE SERVICE REQUEST message: a) shall not include any non-cleartext IE, except the Uplink data status IE; and b) may include the Uplink data status IE. If, prior to receiving the SECURITY MODE COMMAND message, the UE without a valid 5G NAS security context had sent a REGISTRATION REQUEST message the UE shall include the entire REGISTRATION REQUEST message in the NAS message container IE of the SECURITY MODE COMPLETE message as described in subclause 4.4.6. If the UE operating in the single-registration mode receives the Selected EPS NAS security algorithms IE, the UE shall use the IE according to 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. For a UE operating in single-registration mode in a network supporting N26 interface after an inter-system change from S1 mode to N1 mode in 5GMM-CONNECTED mode, the UE shall set the value of the Selected EPS NAS security algorithms IE in the 5G NAS security context to the NAS security algorithms that were received from the source MME when the UE was in S1 mode. | 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.2.3 |
999 | 15.3 Structure of MBMS SAI | The MBMS Service Area (MBMS SA) is defined in 3GPP TS 23.246[ Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description ] [52]. It comprises of one or more MBMS Service Area Identities (MBMS SAIs), in any case each MBMS SA shall not include more than 256 MBMS SAIs. An MBMS SAI shall identify a group of cells within a PLMN, that is independent of the associated Location/Routing/Service Area and the physical location of the cell(s). A cell shall be able to belong to one or more MBMS SAs, and therefore is addressable by one or more MBMS SAIs. The MBMS SAI shall be a decimal number between 0 and 65,535 (inclusive). The value 0 has a special meaning; it shall denote the whole PLMN as the MBMS Service Area and it shall indicate to a receiving RNC/BSS/MCE that all cells reachable by that RNC/BSS/MCE shall be part of the MBMS Service Area. With the exception of the specific MBMS Service Area Identity with value 0, the MBMS Service Area Identity shall be unique within a PLMN and shall be defined in such a way that all the corresponding cells are MBMS capable. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 15.3 |
1,000 | 5.2.6.25.8 Nnef_TimeSynchronization_CapsNotify operation | Service operation name: Nnef_TimeSynchronization_CapsNotify Description: Forward the notification for the time synchronization configuration. When the NEF receives a notification of a change corresponding to a Subscription from the TSCTSF, it forwards the notification by invoking a Nnef_TimeSynchronization_CapsNotify service operation to the NF consumer(s) that has subscribed for the event. The event parameters are described in Table 5.2.27.2.8-1. Known NF Service Consumers: AF. Inputs, Required: As specified in clause 5.2.27.2.8. Inputs, Optional: As specified in clause 5.2.27.2.8. Outputs, Required: Operation execution result indication. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.25.8 |
Subsets and Splits