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
⌀ |
|---|---|---|---|---|---|---|---|
3,201 | 5.16.3.4 P-CSCF address delivery | At PDU Session Establishment procedure related to IMS, SMF shall support the capability to send the P-CSCF address(es) to UE. The SMF is located in VPLMN if LBO is used. This is sent by visited SMF if LBO is used. For Home routed, this information is sent by the SMF in HPLMN. P-CSCF address(es) shall be sent transparently through AMF, and in the case of Home Routed also through the SMF in VPLMN. The P-CSCF IP address(es) may be locally configured in the SMF, or discovered using NRF as described in clause 5.16.3.11. NOTE 1: Other options to provide P-CSCF to the UE as defined in TS 23.228[ IP Multimedia Subsystem (IMS); Stage 2 ] [15] is not excluded. NOTE 2: PDU Session for IMS is identified by "APN" or "DNN". In the case of SNPN access the SMF is always located in the serving SNPN (no support for Home Routed traffic); therefore, the serving SMF sends the P-CSCF address(es) to the UE. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.16.3.4 |
3,202 | 6.8.4.2 GSM security context | A GSM security context in UTRAN is only established for a GSM subscribers with a R99+ ME. At the network side, two cases are distinguished: a) In case of a handover to a GSM BSS controlled by the same MSC/VLR, the MSC/VLR sends the 64-bit GSM cipher key Kc from the key set used before the intersystem handover to the target BSC (which forwards it to the BTS). b) In case of a handover to a GSM BSS controlled by another MSC/VLR (R99+ or R98-), the initial MSC/VLR sends the 64-bit GSM cipher key Kc from the key set used before the intersystem handover to the BSC via the new MSC/VLR controlling the target BSC. The initial MSC/VLR remains the anchor point throughout the service. If the non-anchor MSC/VLR is R99+, then the anchor MSC/VLR also derives and sends to the non-anchor MSC/VLR the UMTS cipher/integrity keys CK and IK. The non-anchor MSC/VLR stores all keys. This is done to allow subsequent handovers in a non-anchor R99+ MSC/VLR. At the user side, in either case, the ME applies the GSM cipher key Kc from the key set which was used before the intersystem handover. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.4.2 |
3,203 | – FeatureSetDownlink | The IE FeatureSetDownlink indicates a set of features that the UE supports on the carriers corresponding to one band entry in a band combination. FeatureSetDownlink information element -- ASN1START -- TAG-FEATURESETDOWNLINK-START FeatureSetDownlink ::= SEQUENCE { featureSetListPerDownlinkCC SEQUENCE (SIZE (1..maxNrofServingCells)) OF FeatureSetDownlinkPerCC-Id, intraBandFreqSeparationDL FreqSeparationClass OPTIONAL, scalingFactor ENUMERATED {f0p4, f0p75, f0p8} OPTIONAL, dummy8 ENUMERATED {supported} OPTIONAL, scellWithoutSSB ENUMERATED {supported} OPTIONAL, csi-RS-MeasSCellWithoutSSB ENUMERATED {supported} OPTIONAL, dummy1 ENUMERATED {supported} OPTIONAL, type1-3-CSS ENUMERATED {supported} OPTIONAL, pdcch-MonitoringAnyOccasions ENUMERATED {withoutDCI-Gap, withDCI-Gap} OPTIONAL, dummy2 ENUMERATED {supported} OPTIONAL, ue-SpecificUL-DL-Assignment ENUMERATED {supported} OPTIONAL, searchSpaceSharingCA-DL ENUMERATED {supported} OPTIONAL, timeDurationForQCL SEQUENCE { scs-60kHz ENUMERATED {s7, s14, s28} OPTIONAL, scs-120kHz ENUMERATED {s14, s28} OPTIONAL } OPTIONAL, pdsch-ProcessingType1-DifferentTB-PerSlot SEQUENCE { scs-15kHz ENUMERATED {upto2, upto4, upto7} OPTIONAL, scs-30kHz ENUMERATED {upto2, upto4, upto7} OPTIONAL, scs-60kHz ENUMERATED {upto2, upto4, upto7} OPTIONAL, scs-120kHz ENUMERATED {upto2, upto4, upto7} OPTIONAL } OPTIONAL, dummy3 DummyA OPTIONAL, dummy4 SEQUENCE (SIZE (1.. maxNrofCodebooks)) OF DummyB OPTIONAL, dummy5 SEQUENCE (SIZE (1.. maxNrofCodebooks)) OF DummyC OPTIONAL, dummy6 SEQUENCE (SIZE (1.. maxNrofCodebooks)) OF DummyD OPTIONAL, dummy7 SEQUENCE (SIZE (1.. maxNrofCodebooks)) OF DummyE OPTIONAL } FeatureSetDownlink-v1540 ::= SEQUENCE { oneFL-DMRS-TwoAdditionalDMRS-DL ENUMERATED {supported} OPTIONAL, additionalDMRS-DL-Alt ENUMERATED {supported} OPTIONAL, twoFL-DMRS-TwoAdditionalDMRS-DL ENUMERATED {supported} OPTIONAL, oneFL-DMRS-ThreeAdditionalDMRS-DL ENUMERATED {supported} OPTIONAL, pdcch-MonitoringAnyOccasionsWithSpanGap SEQUENCE { scs-15kHz ENUMERATED {set1, set2, set3} OPTIONAL, scs-30kHz ENUMERATED {set1, set2, set3} OPTIONAL, scs-60kHz ENUMERATED {set1, set2, set3} OPTIONAL, scs-120kHz ENUMERATED {set1, set2, set3} OPTIONAL } OPTIONAL, pdsch-SeparationWithGap ENUMERATED {supported} OPTIONAL, pdsch-ProcessingType2 SEQUENCE { scs-15kHz ProcessingParameters OPTIONAL, scs-30kHz ProcessingParameters OPTIONAL, scs-60kHz ProcessingParameters OPTIONAL } OPTIONAL, pdsch-ProcessingType2-Limited SEQUENCE { differentTB-PerSlot-SCS-30kHz ENUMERATED {upto1, upto2, upto4, upto7} } OPTIONAL, dl-MCS-TableAlt-DynamicIndication ENUMERATED {supported} OPTIONAL } FeatureSetDownlink-v15a0 ::= SEQUENCE { supportedSRS-Resources SRS-Resources OPTIONAL } FeatureSetDownlink-v1610 ::= SEQUENCE { -- R1 22-4e/4f/4g/4h: CBG based reception for DL with unicast PDSCH(s) per slot per CC with UE processing time Capability 1 cbgPDSCH-ProcessingType1-DifferentTB-PerSlot-r16 SEQUENCE { scs-15kHz-r16 ENUMERATED {one, upto2, upto4, upto7} OPTIONAL, scs-30kHz-r16 ENUMERATED {one, upto2, upto4, upto7} OPTIONAL, scs-60kHz-r16 ENUMERATED {one, upto2, upto4, upto7} OPTIONAL, scs-120kHz-r16 ENUMERATED {one, upto2, upto4, upto7} OPTIONAL } OPTIONAL, -- R1 22-3e/3f/3g/3h: CBG based reception for DL with unicast PDSCH(s) per slot per CC with UE processing time Capability 2 cbgPDSCH-ProcessingType2-DifferentTB-PerSlot-r16 SEQUENCE { scs-15kHz-r16 ENUMERATED {one, upto2, upto4, upto7} OPTIONAL, scs-30kHz-r16 ENUMERATED {one, upto2, upto4, upto7} OPTIONAL, scs-60kHz-r16 ENUMERATED {one, upto2, upto4, upto7} OPTIONAL, scs-120kHz-r16 ENUMERATED {one, upto2, upto4, upto7} OPTIONAL } OPTIONAL, intraFreqDAPS-r16 SEQUENCE { intraFreqDiffSCS-DAPS-r16 ENUMERATED {supported} OPTIONAL, intraFreqAsyncDAPS-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL, intraBandFreqSeparationDL-v1620 FreqSeparationClassDL-v1620 OPTIONAL, intraBandFreqSeparationDL-Only-r16 FreqSeparationClassDL-Only-r16 OPTIONAL, -- R1 11-2: Rel-16 PDCCH monitoring capability pdcch-Monitoring-r16 SEQUENCE { pdsch-ProcessingType1-r16 SEQUENCE { scs-15kHz-r16 PDCCH-MonitoringOccasions-r16 OPTIONAL, scs-30kHz-r16 PDCCH-MonitoringOccasions-r16 OPTIONAL } OPTIONAL, pdsch-ProcessingType2-r16 SEQUENCE { scs-15kHz-r16 PDCCH-MonitoringOccasions-r16 OPTIONAL, scs-30kHz-r16 PDCCH-MonitoringOccasions-r16 OPTIONAL } OPTIONAL } OPTIONAL, -- R1 11-2b: Mix of Rel. 16 PDCCH monitoring capability and Rel. 15 PDCCH monitoring capability on different carriers pdcch-MonitoringMixed-r16 ENUMERATED {supported} OPTIONAL, -- R1 18-5c: Processing up to X unicast DCI scheduling for DL per scheduled CC crossCarrierSchedulingProcessing-DiffSCS-r16 SEQUENCE { scs-15kHz-120kHz-r16 ENUMERATED {n1,n2,n4} OPTIONAL, scs-15kHz-60kHz-r16 ENUMERATED {n1,n2,n4} OPTIONAL, scs-30kHz-120kHz-r16 ENUMERATED {n1,n2,n4} OPTIONAL, scs-15kHz-30kHz-r16 ENUMERATED {n2} OPTIONAL, scs-30kHz-60kHz-r16 ENUMERATED {n2} OPTIONAL, scs-60kHz-120kHz-r16 ENUMERATED {n2} OPTIONAL } OPTIONAL, -- R1 16-2b-1: Support of single-DCI based SDM scheme singleDCI-SDM-scheme-r16 ENUMERATED {supported} OPTIONAL } FeatureSetDownlink-v1700 ::= SEQUENCE { -- R1 36-2: Scaling factor to be applied to 1024QAM for FR1 scalingFactor-1024QAM-FR1-r17 ENUMERATED {f0p4, f0p75, f0p8} OPTIONAL, -- R1 24 feature for existing UE cap to include new SCS timeDurationForQCL-v1710 SEQUENCE { scs-480kHz ENUMERATED {s56, s112} OPTIONAL, scs-960kHz ENUMERATED {s112, s224} OPTIONAL } OPTIONAL, -- R1 23-6-1 SFN scheme A (scheme 1) for PDSCH and PDCCH sfn-SchemeA-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-6-1-1 SFN scheme A (scheme 1) for PDCCH only sfn-SchemeA-PDCCH-only-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-6-1a Dynamic switching - scheme A sfn-SchemeA-DynamicSwitching-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-6-1b SFN scheme A (scheme 1) for PDSCH only sfn-SchemeA-PDSCH-only-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-6-2 SFN scheme B (TRP based pre-compensation) for PDSCH and PDCCH sfn-SchemeB-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-6-2a Dynamic switching - scheme B sfn-SchemeB-DynamicSwitching-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-6-2b SFN scheme B (TRP based pre-compensation) for PDSCH only sfn-SchemeB-PDSCH-only-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-2-1d PDCCH repetition for Case 2 PDCCH monitoring with a span gap mTRP-PDCCH-Case2-1SpanGap-r17 SEQUENCE { scs-15kHz-r17 PDCCH-RepetitionParameters-r17 OPTIONAL, scs-30kHz-r17 PDCCH-RepetitionParameters-r17 OPTIONAL, scs-60kHz-r17 PDCCH-RepetitionParameters-r17 OPTIONAL, scs-120kHz-r17 PDCCH-RepetitionParameters-r17 OPTIONAL } OPTIONAL, -- R1 23-2-1e PDCCH repetition for Rel-16 PDCCH monitoring mTRP-PDCCH-legacyMonitoring-r17 SEQUENCE { scs-15kHz-r17 PDCCH-RepetitionParameters-r17 OPTIONAL, scs-30kHz-r17 PDCCH-RepetitionParameters-r17 OPTIONAL } OPTIONAL, -- R1 23-2-4 Simultaneous configuration of PDCCH repetition and multi-DCI based multi-TRP mTRP-PDCCH-multiDCI-multiTRP-r17 ENUMERATED {supported} OPTIONAL, -- R1 33-2: Dynamic scheduling for multicast for PCell dynamicMulticastPCell-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-2-1 PDCCH repetition mTRP-PDCCH-Repetition-r17 SEQUENCE { numBD-twoPDCCH-r17 INTEGER (2..3), maxNumOverlaps-r17 ENUMERATED {n1,n2,n3,n5,n10,n20,n40} } OPTIONAL } FeatureSetDownlink-v1720 ::= SEQUENCE { -- R1 25-19: RTT-based Propagation delay compensation based on CSI-RS for tracking and SRS rtt-BasedPDC-CSI-RS-ForTracking-r17 ENUMERATED {supported} OPTIONAL, -- R1 25-19a: RTT-based Propagation delay compensation based on DL PRS for RTT-based PDC and SRS rtt-BasedPDC-PRS-r17 SEQUENCE { maxNumberPRS-Resource-r17 ENUMERATED {n1, n2, n4, n8, n16, n32, n64}, maxNumberPRS-ResourceProcessedPerSlot-r17 SEQUENCE { scs-15kHz-r17 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, n32, n48, n64} OPTIONAL, scs-30kHz-r17 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, n32, n48, n64} OPTIONAL, scs-60kHz-r17 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, n32, n48, n64} OPTIONAL, scs-120kHz-r17 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, n32, n48, n64} OPTIONAL } } OPTIONAL, -- R1 33-5-1: SPS group-common PDSCH for multicast on PCell sps-Multicast-r17 ENUMERATED {supported} OPTIONAL } FeatureSetDownlink-v1730 ::= SEQUENCE { -- R1 25-19b: Support of PRS as spatial relation RS for SRS prs-AsSpatialRelationRS-For-SRS-r17 ENUMERATED {supported} OPTIONAL } FeatureSetDownlink-v1800 ::= SEQUENCE { -- R1 40-3-3-6: Maximum number of TRS resource sets in a report configuration maxNumberTRS-ResourceSet-r18 INTEGER (2..3) OPTIONAL, -- R1 40-4-1b: 1 symbol FL DMRS and 2 additional DMRS symbols for more than one port for Rel.18 enhanced DMRS ports for PDSCH pdsch-1SymbolFL-DMRS-Addition2Symbol-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-4-1c: Alternative additional DMRS position for co-existence with LTE CRS for Rel.18 enhanced DMRS ports for PDSCH pdsch-AlternativeDMRS-Coexistence-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-4-1d: 2 symbols FL-DMRS for Rel.18 enhanced DMRS ports for PDSCH pdsch-2SymbolFL-DMRS-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-4-1e: 2-symbol FL DMRS + one additional 2-symbols DMRS for Rel.18 enhanced DMRS ports for PDSCH pdsch-2SymbolFL-DMRS-Addition2Symbol-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-4-1f: 1 symbol FL DMRS and 3 additional DMRS symbols for Rel.18 enhanced DMRS ports for PDSCH pdsch-1SymbolFL-DMRS-Addition3Symbol-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-4-1g: DMRS type for Rel.18 enhanced DMRS ports for PDSCH pdsch-DMRS-Type-r18 ENUMERATED {etype1, etype1And2} OPTIONAL, -- R1 40-4-1h: 1 port DL PTRS for Rel.18 enhanced DMRS ports for PDSCH with rank 1-8 pdsch-1PortDL-PTRS-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-4-1j: Support 1 symbol FL DMRS and 2 additional DMRS symbols for at least one port for mapping type A mappingTypeA-1SymbolFL-DMRS-Addition2Symbol-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-4-4: Reception of PDSCH without the scheduling restriction for Rel.18 eType1 DMRS ports pdsch-ReceptionWithoutSchedulingRestriction-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-4-5a: Additional row(s) for antenna ports (0,2,3) for Rel.18 DMRS ports for single-DCI based M-TRP dmrs-MultiTRP-AddtionRows-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-4-12: Support of Rel-18 DMRS and PDSCH processing capability 2 simultaneously simulDMRS-PDSCH-r18 SEQUENCE { scs-15kHz-r18 INTEGER (0..4) OPTIONAL, scs-30kHz-r18 INTEGER (0..5) OPTIONAL, scs-60kHz-r18 INTEGER (0..7) OPTIONAL } OPTIONAL, -- R1 53-1: Support RLM/BM/BFD and gapless L3 intra-frequency measurements based on CD-SSB outside active BWP without interruptions bwpOperationMeasWithoutInterrupt-r18 ENUMERATED {supported} OPTIONAL, -- R1 53-2: Support RLM/BM/BFD measurements based on CD-SSB outside active BWP with interruptions bwpOperationMeasWithInterrupt-r18 ENUMERATED {supported} OPTIONAL, -- R1 55-6: (2, 2) span-based PDCCH monitoring with additional restriction(s) pdcch-MonitoringSpan2-2-r18 SEQUENCE{ pdsch-ProcessingType1-r18 SEQUENCE{ scs-15kHz-r18 ENUMERATED {supported} OPTIONAL, scs-30kHz-r18 ENUMERATED {supported} OPTIONAL }, pdsch-ProcessingType2-r18 SEQUENCE{ scs-15kHz-r18 ENUMERATED {supported} OPTIONAL, scs-30kHz-r18 ENUMERATED {supported} OPTIONAL } } OPTIONAL, -- R1 55-6b: Mix of Rel-16 PDCCH monitoring capability and Rel. 15 PDCCH monitoring capability on different carriers pdcch-MonitoringMixed-r18 ENUMERATED {supported} OPTIONAL, multicastInactive-r18 ENUMERATED {supported} OPTIONAL } PDCCH-MonitoringOccasions-r16 ::= SEQUENCE { period7span3-r16 ENUMERATED {supported} OPTIONAL, period4span3-r16 ENUMERATED {supported} OPTIONAL, period2span2-r16 ENUMERATED {supported} OPTIONAL } PDCCH-RepetitionParameters-r17 ::= SEQUENCE { supportedMode-r17 ENUMERATED {intra-span, inter-span, both}, limitX-PerCC-r17 ENUMERATED {n4, n8, n16, n32, n44, n64, nolimit} OPTIONAL, limitX-AcrossCC-r17 ENUMERATED {n4, n8, n16, n32, n44, n64, n128, n256, n512, nolimit} OPTIONAL } DummyA ::= SEQUENCE { maxNumberNZP-CSI-RS-PerCC INTEGER (1..32), maxNumberPortsAcrossNZP-CSI-RS-PerCC ENUMERATED {p2, p4, p8, p12, p16, p24, p32, p40, p48, p56, p64, p72, p80, p88, p96, p104, p112, p120, p128, p136, p144, p152, p160, p168, p176, p184, p192, p200, p208, p216, p224, p232, p240, p248, p256}, maxNumberCS-IM-PerCC ENUMERATED {n1, n2, n4, n8, n16, n32}, maxNumberSimultaneousCSI-RS-ActBWP-AllCC ENUMERATED {n5, n6, n7, n8, n9, n10, n12, n14, n16, n18, n20, n22, n24, n26, n28, n30, n32, n34, n36, n38, n40, n42, n44, n46, n48, n50, n52, n54, n56, n58, n60, n62, n64}, totalNumberPortsSimultaneousCSI-RS-ActBWP-AllCC ENUMERATED {p8, p12, p16, p24, p32, p40, p48, p56, p64, p72, p80, p88, p96, p104, p112, p120, p128, p136, p144, p152, p160, p168, p176, p184, p192, p200, p208, p216, p224, p232, p240, p248, p256} } DummyB ::= SEQUENCE { maxNumberTxPortsPerResource ENUMERATED {p2, p4, p8, p12, p16, p24, p32}, maxNumberResources INTEGER (1..64), totalNumberTxPorts INTEGER (2..256), supportedCodebookMode ENUMERATED {mode1, mode1AndMode2}, maxNumberCSI-RS-PerResourceSet INTEGER (1..8) } DummyC ::= SEQUENCE { maxNumberTxPortsPerResource ENUMERATED {p8, p16, p32}, maxNumberResources INTEGER (1..64), totalNumberTxPorts INTEGER (2..256), supportedCodebookMode ENUMERATED {mode1, mode2, both}, supportedNumberPanels ENUMERATED {n2, n4}, maxNumberCSI-RS-PerResourceSet INTEGER (1..8) } DummyD ::= SEQUENCE { maxNumberTxPortsPerResource ENUMERATED {p4, p8, p12, p16, p24, p32}, maxNumberResources INTEGER (1..64), totalNumberTxPorts INTEGER (2..256), parameterLx INTEGER (2..4), amplitudeScalingType ENUMERATED {wideband, widebandAndSubband}, amplitudeSubsetRestriction ENUMERATED {supported} OPTIONAL, maxNumberCSI-RS-PerResourceSet INTEGER (1..8) } DummyE ::= SEQUENCE { maxNumberTxPortsPerResource ENUMERATED {p4, p8, p12, p16, p24, p32}, maxNumberResources INTEGER (1..64), totalNumberTxPorts INTEGER (2..256), parameterLx INTEGER (2..4), amplitudeScalingType ENUMERATED {wideband, widebandAndSubband}, maxNumberCSI-RS-PerResourceSet INTEGER (1..8) } -- TAG-FEATURESETDOWNLINK-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,204 | 10.5.1.12.2 CS domain specific system information | The purpose of the CN domain specific GSM-MAP NAS system information element, when used for the CS domain, is to provide the MS with actual parameter settings of parameters relevant only for MM functionality. The coding of the information element identifier and length information is defined in the 3GPP TS 25.331[ None ] [23c]. Only the coding of the content is in the scope of the present document. For CS domain, the content of the CN domain specific GSM-MAP NAS system information element is coded as shown in figure 10.5.1.12.2/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.1.12.2/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The length of this element content is two octets. The MS shall ignore any additional octets received. Figure 10.5.1.12.2/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] CS domain specific system information element Table 10.5.1.12.2/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : CS domain specific system 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.1.12.2 |
3,205 | – MeasurementReportSidelink | The MeasurementReportSidelink message is used for the indication of measurement results of NR sidelink. Signalling radio bearer: SL-SRB3 RLC-SAP: AM Logical channel: SCCH Direction: UE to UE MeasurementReportSidelink message -- ASN1START -- TAG-MEASUREMENTREPORTSIDELINK-START MeasurementReportSidelink ::= SEQUENCE { criticalExtensions CHOICE { measurementReportSidelink-r16 MeasurementReportSidelink-r16-IEs, criticalExtensionsFuture SEQUENCE {} } } MeasurementReportSidelink-r16-IEs ::= SEQUENCE { sl-MeasResults-r16 SL-MeasResults-r16, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE{} OPTIONAL } SL-MeasResults-r16 ::= SEQUENCE { sl-MeasId-r16 SL-MeasId-r16, sl-MeasResult-r16 SL-MeasResult-r16, ... } SL-MeasResult-r16 ::= SEQUENCE { sl-ResultDMRS-r16 SL-MeasQuantityResult-r16 OPTIONAL, ..., [[ sl-Result-SL-PRS-r18 SL-MeasQuantityResult-r16 OPTIONAL ]] } SL-MeasQuantityResult-r16 ::= SEQUENCE { sl-RSRP-r16 RSRP-Range OPTIONAL, ..., [[ sl-Rsrp-DedicatedSL-PRS-RP-r18 INTEGER (0..13) OPTIONAL ]] } SL-MeasResultListRelay-r17 ::= SEQUENCE (SIZE (1..maxNrofRelayMeas-r17)) OF SL-MeasResultRelay-r17 SL-MeasResultRelay-r17 ::= SEQUENCE { cellIdentity-r17 CellAccessRelatedInfo, sl-RelayUE-Identity-r17 SL-SourceIdentity-r17, sl-MeasResult-r17 SL-MeasResult-r16, ..., [[ sl-MeasQuantity-r18 ENUMERATED { sl-rsrp, sd-rsrp } OPTIONAL ]] } -- TAG-MEASUREMENTREPORTSIDELINK-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,206 | 10.8.2 MR-DC with 5GC | The MN to ng-eNB/gNB Change procedure is used to transfer UE context data from a source MN/SN to a target ng-eNB/gNB. Both the cases where the source MN and the target node belong to the same RAT (i.e. they are both ng-eNBs or both gNBs) and the cases where the source MN and the target node belong to different RATs are supported. NOTE 0: Inter-system HO from ng-eNB/gNB MN to eNB is also supported. Figure 10.8.2-1: MN to ng-eNB/gNB Change procedure Figure 10.8.2-1 shows an example signalling flow for the MN to ng-eNB/gNB Change procedure: 1. The source MN starts the MN to ng-eNB/gNB Change procedure by initiating the Xn Handover Preparation procedure, including both MCG and SCG configuration. NOTE 1: The source MN may trigger the MN-initiated SN Modification procedure (to the source SN) to retrieve the current SCG configuration and to allow provision of data forwarding related information before step 1. 2. The target ng-eNB/gNB includes the field in HO command which releases the SCG configuration, and may also provide forwarding addresses to the source MN. 3. If the resource allocation of target ng-eNB/gNB was successful, the MN initiates the release of the source SN resources towards the source SN including a Cause indicating MCG mobility. The SN acknowledges the release request. If data forwarding is needed, the MN provides data forwarding addresses to the source SN. Reception of the SN Release Request message triggers the source SN to stop providing user data to the UE and, if applicable, to start data forwarding. NOTE 1a: In case the handover is a conditional handover, step 3a and step 3b are performed after the source MN receives an indication that the UE has successfully accessed one of the potential target gNB(s) as described in step 8a in Figure 9.2.3.4.2-1 in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [3], i.e., after step 6 in Figure 10.8.2-1. NOTE 1b: In case the handover is a conditional handover, the step 3c is executed right after step 2. The Xn-U Address Indication message notifies conditional handover to the source SN, for which it may decide to perform, if applicable, early data forwarding for SN-terminated bearers, together with the sending of an EARLY STATUS TRANSFER message to the source MN. Separate Xn-U Address Indication procedures may be invoked to provide different forwarding addresses of the prepared conditional handovers. In this case, it is up to the source MN and SN implementations to make sure that the EARLY STATUS TRANSFER message(s) from the source SN, if any, is forwarded to the right target destination. The Xn-U Address Indication procedure may further be invoked to indicate to the source SN to stop already initiated early data forwarding for some SN-terminated bearers if they are no longer subject to data forwarding due to the modification or cancellation of the prepared conditional handovers. If applicable, the normal data forwarding and SN STATUS TRANSFER message would follow from the source SN once it receives the SN Release Request message of the step 3a that is performed after step 6. In case the step 3c Xn-U Address Indication procedure corresponding to the conditional handover that the UE successfully accessed was rejected by the source SN, the source MN re-sends it after the step 3b that is performed after step 6. 4. The MN triggers the UE to perform HO and apply the new configuration. Upon receiving the new configuration, the UE releases the entire SCG configuration. 5/6. The UE synchronizes to the target ng-eNB/gNB. 7. If PDCP termination point is changed for bearers using RLC AM, the SN sends the SN Status Transfer message, which the source MN sends then to the target ng-eNB/gNB. 8. If applicable, data forwarding takes place from the source side. 9a. The source SN sends the Secondary RAT Data Usage Report message to the source MN and includes the data volumes delivered to and received from the UE as described in clause 10.11.2. NOTE 2: The order the SN sends the Secondary RAT Data Usage Report message and performs data forwarding with MN is not defined. The SN may send the report when the transmission of the related QoS flow is stopped. 9b. The source MN sends the Secondary RAT Report message to AMF to provide information on the used NR/E-UTRA resource. 10-14. The target ng-eNB/gNB initiates the Path Switch procedure. 15. The target ng-eNB/gNB initiates the UE Context Release procedure towards the source MN. 16. Upon reception of the UE Context Release message from the MN, the source SN releases radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue. | 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 | 10.8.2 |
3,207 | 5.4.5.2.3 UE-initiated NAS transport of messages accepted by the network | Upon reception of a UL NAS TRANSPORT message, if the Payload container type IE is set to: a) "N1 SM information", the AMF looks up a PDU session routing context for: 1) the UE and the PDU session ID IE in case the Old PDU session ID IE is not included, and: NOTE 1: If the Old PDU session ID IE is not included in the UL NAS TRANSPORT message and the AMF has received a reallocation requested indication from the SMF, the AMF needs to ignore the reallocation requested indication. i) if the AMF has a PDU session routing context for the PDU session ID and the UE, and the Request type IE is either not included or is included but set to other value than "initial request", "existing PDU session", "initial emergency request", "existing emergency PDU session" or "MA PDU request", the AMF shall send the 5GSM message, and the PDU session ID IE towards the SMF identified by the SMF ID of the PDU session routing context; ii) if the AMF has a PDU session routing context for the PDU session ID and the UE, the PDU session routing context indicates that the PDU session is not an emergency PDU session, the Request type IE is included and is set to "existing PDU session" or "MA PDU request", and the S-NSSAI associated with the PDU session identified by the PDU session ID is allowed for the target access type, the AMF shall send the 5GSM message, the PDU session ID, the S-NSSAI, the mapped S-NSSAI (in roaming scenarios), the DNN (if received) and the request type towards the SMF identified by the SMF ID of the PDU session routing context; iii) if the AMF does not have a PDU session routing context for the PDU session ID and the UE, and the Request type IE is included and is set to "initial request" or "MA PDU request": A) the AMF shall select an SMF with following handlings in case the UE is not registered for onboarding services in SNPN: If the S-NSSAI IE is not included, the UE does not have a partially allowed NSSAI, and the allowed NSSAI contains: - one S-NSSAI, the AMF shall use the S-NSSAI in the allowed NSSAI as the S-NSSAI. Additionally, for a UE for which the AMF has provided a NS-AoS, the AMF shall use the S-NSSAI in the allowed NSSAI if the UE is inside the NS-AoS with respect to the S-NSSAI; - two or more S-NSSAIs and the user's subscription context obtained from UDM contains only one default S-NSSAI that is included in the allowed NSSAI, the AMF shall use the S-NSSAI in the allowed NSSAI that matches the default S-NSSAI as the S-NSSAI; or - two or more S-NSSAIs and the user's subscription context obtained from UDM contains two or more default S-NSSAI(s) included in the allowed NSSAI, the AMF shall use an S-NSSAI in the allowed NSSAI selected based on operator policy as the S-NSSAI. If S-NSSAI IE is not included, the UE has both a partially allowed NSSAI and an allowed NSSAI, the AMF shall select an S-NSSAI from the partially allowed NSSAI or the allowed NSSAI based on operator policy. Additionally: - for the case when the AMF determines to use the allowed NSSAI for selecting an S-NSSAI and for a UE for which the AMF has provided a NS-AoS, the AMF shall use the S-NSSAI in the allowed NSSAI if the UE is inside the NS-AoS with respect to the S-NSSAI; or - for the case when the AMF determines to use the partially allowed NSSAI for selecting an S-NSSAI, the AMF shall use the S-NSSAI in the partially allowed NSSAI if the current TAI is in the list of TAs where the S-NSSAI is allowed. If the S-NSSAI or the mapped S-NSSAI (in roaming scenarios) is an S-NSSAI to be replaced and the alternative S-NSSAI is not provided by the UE, the AMF shall retrieve an alternative S-NSSAI (see subclause 5.15.19 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]). If the DNN IE is included, the AMF shall use the UE requested DNN as the DNN determined by the AMF; and If the DNN IE is not included, and the user's subscription context obtained from UDM: - contains the default DNN for the S-NSSAI, the AMF shall use the default DNN as the DNN determined by the AMF; and - does not contain the default DNN for the S-NSSAI, the AMF shall use a locally configured DNN as the DNN determined by the AMF; A1) the AMF shall select an SMF with following handlings in case the UE is registered for onboarding services in SNPN: - if the AMF onboarding configuration data does not contain a configured SMF used for onboarding services in SNPN and contains the S-NSSAI used for onboarding services in SNPN, the AMF shall use the S-NSSAI used for onboarding services in SNPN as the S-NSSAI; - if the AMF onboarding configuration data does not contain a configured SMF used for onboarding services in SNPN and contains the DNN used for onboarding services in SNPN, the AMF shall use the DNN used for onboarding services in SNPN as the DNN; - if the AMF onboarding configuration data does not contain the S-NSSAI used for onboarding services in SNPN, does not contain the DNN used for onboarding services in SNPN, and contains a configured SMF used for onboarding services in SNPN, the AMF shall select the configured SMF used for onboarding services in SNPN; - if the AMF onboarding configuration data contains the S-NSSAI used for onboarding services in SNPN, the DNN used for onboarding services in SNPN, or both, and contains a configured SMF used for onboarding services in SNPN, the AMF shall use the S-NSSAI used for onboarding services in SNPN, if any, as the S-NSSAI, and use the DNN used for onboarding services in SNPN, if any, as the DNN or shall select the configured SMF used for onboarding services in SNPN, according to local policy; and - if the AMF onboarding configuration data contains none of the S-NSSAI used for onboarding services in SNPN, the DNN used for onboarding services in SNPN and a configured SMF used for onboarding services in SNPN, the AMF handling is implementation specific; and NOTE 2: The AMF can e.g. use a locally configured DNN used for onboarding services in SNPN as the DNN determined by the AMF. NOTE 3: SMF selection is outside the scope of the present document. NOTE 4: As part of SMF selection, the PCF can provide the AMF with a DNN selected by the network different from the DNN determined by the AMF. B) if the SMF selection is successful: - if the DNN selected by the network is a LADN DNN, the AMF shall determine the UE presence in LADN service area (see subclause 6.2.6); - the AMF shall store a PDU session routing context for the PDU session ID and the UE, shall set the SMF ID in the stored PDU session routing context to the SMF ID corresponding to the DNN in the user's subscription context obtained from the UDM; and - the AMF shall send the 5GSM message, the PDU session ID, the S-NSSAI, the mapped S-NSSAI (in roaming scenarios), the DNN determined by the AMF, DNN selected by the network (if different from DNN determined by the AMF), the request type, the MA PDU session information, the non-3GPP access path switching indication, UE presence in LADN service area (if DNN received corresponds to an LADN DNN), the onboarding indication (if the UE is registered for onboarding services in SNPN), and the alternative S-NSSAI associated with the S-NSSAI to be replaced (if available) towards the SMF identified by the SMF ID of the PDU session routing context; NOTE 5: The MA PDU session information is not sent towards the SMF if the DNN received corresponds to an LADN DNN. iv) if the AMF does not have a PDU session routing context for the PDU session ID and the UE, the Request type IE is included and is set to "existing PDU session" or "MA PDU request", and the AMF retrieves an SMF ID associated with: A) the PDU session ID matching the PDU session ID received from the UE, if any; or B) the DNN matching the DNN received from the UE, otherwise; such that the SMF ID includes a PLMN identity corresponding to the UE's HPLMN or the current PLMN, then: A) the AMF shall store a PDU session routing context for the PDU session ID and the UE, shall set the SMF ID in the stored PDU session routing context to the retrieved SMF ID; and B) the AMF shall send the 5GSM message, the PDU session ID, the S-NSSAI, the mapped S-NSSAI (in roaming scenarios), the DNN (if received) and the request type towards the SMF identified by the SMF ID of the PDU session routing context; v) if the AMF does not have a PDU session routing context for the PDU session ID and the UE, the Request type IE is included and is set to "initial emergency request", and the AMF does not have a PDU session routing context for another PDU session ID of the UE indicating that the PDU session is an emergency PDU session: A) the AMF shall select an SMF. The AMF shall use the emergency DNN from the AMF emergency configuration data as the DNN, if configured. The AMF shall derive the SMF from the emergency DNN or use the statically configured SMF from the AMF emergency configuration data, if configured; and B) if the SMF selection is successful: - the AMF shall store a PDU session routing context for the PDU session ID and the UE, shall set the SMF ID in the stored PDU session routing context to the SMF ID of the selected SMF, and shall store an indication that the PDU session is an emergency PDU session in the stored PDU session routing context; and - the AMF shall send the 5GSM message, the PDU session ID, the S-NSSAI (if configured in the AMF emergency configuration data), the DNN (if configured in the AMF emergency configuration data), and the request type towards the SMF identified by the SMF ID of the PDU session routing context; and vi) if the AMF does not have a PDU session routing context for the PDU session ID and the UE, the Request type IE is included and is set to "initial emergency request", and the AMF has a PDU session routing context indicating that the PDU session is an emergency PDU session for another PDU session ID of the UE: A) the AMF shall store a PDU session routing context for the PDU session ID and the UE and shall set the SMF ID in the stored PDU session routing context to the SMF ID of the PDU session routing context for the other PDU session ID of the UE; and B) the AMF shall send the 5GSM message, the PDU session ID, the S-NSSAI (if configured in the AMF emergency configuration data), the DNN (if configured in the AMF emergency configuration data) and the request type towards the SMF identified by the SMF ID of the PDU session routing context; or vii) if the AMF has a PDU session routing context for the PDU session ID and the UE, the PDU session routing context indicates that the PDU session is an emergency PDU session, and the Request type IE is included and is set to "existing emergency PDU session", the AMF shall send the 5GSM message, the PDU session ID, the S-NSSAI (if configured in the AMF emergency configuration data), the DNN (if configured in the AMF emergency configuration data), and the request type towards the SMF identified by the SMF ID of the PDU session routing context; and viii) if the AMF does not have a PDU session routing context for the PDU session ID and the UE, the Request type IE is included and is set to "existing emergency PDU session", and the AMF retrieves an SMF ID associated with emergency services such that the SMF ID includes a PLMN identity corresponding to the current PLMN, then: A) the AMF shall store a PDU session routing context for the PDU session ID and the UE, shall set the SMF ID in the stored PDU session routing context to the retrieved SMF ID; and B) the AMF shall send the 5GSM message, the PDU session ID, the S-NSSAI (if configured in the AMF emergency configuration data), the DNN (if configured in the AMF emergency configuration data), and the request type towards the SMF identified by the SMF ID of the PDU session routing context; or 2) the UE and the Old PDU session ID IE in case the Old PDU session ID IE is included, and: i) the AMF has a PDU session routing context for the old PDU session ID and the UE and does not have a PDU session routing context for the PDU session ID and the UE, the Request type IE is included and is set to "initial request", and the AMF received a reallocation requested indication from the SMF indicating that the SMF is to be reused, the AMF shall store a PDU session routing context for the PDU session ID and the UE, set the SMF ID in the stored PDU session routing context to the SMF ID of the PDU session routing context for the old PDU session ID and the UE. If the DNN is a LADN DNN, the AMF shall determine the UE presence in LADN service area (see subclause 6.2.6). The AMF shall send the 5GSM message, the PDU session ID, the old PDU session ID, the S-NSSAI (if received), the mapped S-NSSAI (in roaming scenarios), the DNN, the request type, UE presence in LADN service area (if DNN received corresponds to an LADN DNN), and the alternative S-NSSAI (if received) towards the SMF identified by the SMF ID of the PDU session routing context; ii) the AMF has a PDU session routing context for the old PDU session ID and the UE and does not have a PDU session routing context for the PDU session ID and the UE, the Request type IE is included and is set to "initial request", and the AMF received a reallocation requested indication from the SMF indicating that the SMF is to be reallocated: A) the AMF shall select an SMF with the following handling; If the S-NSSAI IE is not included and the allowed NSSAI contains: - one S-NSSAI, the AMF shall use the S-NSSAI in the allowed NSSAI as the S-NSSAI; - two or more S-NSSAIs and the user's subscription context obtained from UDM contains only one default S-NSSAI that is included in the allowed NSSAI, the AMF shall use the S-NSSAI in the allowed NSSAI that matches the default S-NSSAI; or - two or more S-NSSAIs and the user's subscription context obtained from UDM contains two or more default S-NSSAI(s) included in the allowed NSSAI, the AMF shall use an S-NSSAI in the allowed NSSAI selected based on operator policy as the S-NSSAI. If the DNN is a LADN DNN, the AMF shall determine the UE presence in LADN service area (see subclause 6.2.6). B) if the SMF selection is successful: - the AMF shall store a PDU session routing context for the PDU session ID and the UE and set the SMF ID of the PDU session routing context to the SMF ID of the selected SMF; and - the AMF shall send the 5GSM message, the PDU session ID, the old PDU session ID, the S-NSSAI, the mapped S-NSSAI (in roaming scenarios), the DNN, the request type, the MA PDU session information, the non-3GPP access path switching indication, UE presence in LADN service area (if DNN received corresponds to an LADN DNN), and the alternative S-NSSAI (if received) towards the SMF identified by the SMF ID of the PDU session routing context for the PDU session ID and the UE; NOTE 6: The MA PDU session information is not sent towards the SMF if the DNN received corresponds to an LADN DNN. b) "SMS", the AMF shall send the content of the Payload container IE to the SMSF associated with the UE; c) "LTE Positioning Protocol (LPP) message container", the AMF shall send the Payload container type and the content of the Payload container IE to the LMF associated with the routing information included in the Additional information IE of the UL NAS TRANSPORT message; c1) "SLPP message container", the AMF shall send the Payload container type and the content of the Payload container IE to the LMF associated with the routing information included in the Additional information IE of the UL NAS TRANSPORT message; d) "SOR transparent container", the AMF shall send the content of the Payload container IE to the UDM (see 3GPP TS 29.503[ 5G System; Unified Data Management Services; Stage 3 ] [20AB]); e) "UE policy container", the AMF shall send the content of the Payload container IE to the PCF. f) "UE parameters update transparent container", the AMF shall send the content of the Payload container IE to the UDM. g) "Location services message container": 1) if the Additional information IE is not included in the UL NAS TRANSPORT message, the AMF shall provide the Payload container type and the content of the Payload container IE and Payload container information IE, if included, to the location services application; and 2) if the Additional information IE is included in the UL NAS TRANSPORT message, the AMF shall send the Payload container type and the content of the Payload container IE and Payload container information, if included, to an LMF associated with routing information included in the Additional information IE of the UL NAS TRANSPORT message or to a selected LMF if the Payload container information IE is included in the UL NAS TRANSPORT message and the PRU bit of the Payload container information IE indicates "Payload container related to PRU". h) "CIoT user data container", the AMF shall look up a PDU session routing context for the UE and the PDU session ID, and 1) send the content of the Payload container IE towards the SMF identified by the SMF ID of the PDU session routing context; and 2) initiate the release of the N1 NAS signalling connection: i) if the Release assistance indication IE is included in the UL NAS TRANSPORT message and the DDX field of the Release assistance indication IE indicates "No further uplink and no further downlink data transmission subsequent to the uplink data transmission is expected" and if there is no downlink signalling or downlink data for the UE; or ii) upon subsequent delivery of the next received downlink data transmission to the UE if the Release assistance indication IE is included in the UL NAS TRANSPORT message and the DDX field of the Release assistance indication IE indicates "Only a single downlink data transmission and no further uplink data transmission subsequent to the uplink data transmission is expected" and if there is no additional downlink signalling or downlink data for the UE. i) "Service-level-AA container" and the Service-level-AA container is included in the Payload container IE of the UL NAS TRANSPORT message, and the Service-level device ID included in the Service-level-AA container is set to a CAA-level UAV ID, the AMF shall send the content of the Payload container IE to the UAS-NF corresponding to the CAA-level UAV ID. If the Service-level device ID is not included in the Service-level-AA container and a CAA-level UAV ID is included in the 5GMM context of the UE, then the AMF shall send the content of the Payload container IE to the UAS-NF corresponding to the CAA-level UAV ID included in the 5GMM context of the UE. j) "UPP-CMI container", the AMF shall send the content of the Payload container IE to the LMF selected for user plane positioning. NOTE 7: LMF selection for user plane positioning is outside the scope of the present document. k) "Multiple payloads", the AMF shall first decode the content of the Payload container IE (see subclause 9.11.3.39) to obtain the number of payload container entries and for each payload container entry, the AMF shall: i) decode the payload container type field; ii) decode the optional IE fields and the payload container contents field in the payload container entry; and iii) handle the content of each payload container entry the same as the content of the Payload container IE and the associated optional IEs as specified in bullets a) to j) above according to the payload container type field. | 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.5.2.3 |
3,208 | 4.3.20.2 RN startup and attach procedure 4.3.20.2.1 General | The startup procedure for the Relay Node is based on the normal UE attach procedure and consists of the following two phases: - Phase I: Attach for RN preconfiguration. - Phase II: Attach for RN operation (MME of the RN). NOTE: When the certificate-based solution is used, the RN uses USIM-INI in Phase I and USIM-RN in Phase II with necessarily different IMSIs. When pre-shared key is used, there is only need for one USIM and the RN uses the same IMSI during Phase I and Phase II. The MME does not treat certificate-based and pre-shared key-based solution differently. The use of the certificate-based and pre-shared key solutions is specified in Annex D of TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [41]. | 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.20.2 |
3,209 | 5.6.4.3 Usage of IPv6 multi-homing for a PDU Session | A PDU Session may be associated with multiple IPv6 prefixes. This is referred to as multi-homed PDU Session. The multi-homed PDU Session provides access to the Data Network via more than one PDU Session Anchor. The different user plane paths leading to the different PDU Session Anchors branch out at a "common" UPF referred to as a UPF supporting "Branching Point" functionality. The Branching Point provides forwarding of UL traffic towards the different PDU Session Anchors and merge of DL traffic to the UE i.e. merging the traffic from the different PDU Session Anchors on the link towards the UE. The UPF supporting a Branching Point functionality may also be controlled by the SMF to support traffic measurement for charging, traffic replication for LI and bit rate enforcement (Session-AMBR per PDU Session). The insertion and removal of a UPF supporting Branching Point is decided by the SMF and controlled by the SMF using generic N4 and UPF capabilities. The SMF may decide to insert in the data path of a PDU Session a UPF supporting the Branching Point functionality during or after the PDU Session Establishment, or to remove from the data path of a PDU Session a UPF supporting the Branching Point functionality after the PDU Session Establishment. Multi homing of a PDU Session applies only for PDU Sessions of IPv6 type. When the UE requests a PDU Session of type "IPv4v6" or "IPv6" the UE also provides an indication to the network whether it supports a Multi-homed IPv6 PDU Session. The use of multiple IPv6 prefixes in a PDU Session is characterised by the following: - The UPF supporting a Branching Point functionality is configured by the SMF to spread UL traffic between the PDU Session Anchors based on the Source Prefix of the PDU (which may be selected by the UE based on routing information and preferences received from the network). - IETF RFC 4191 [8] is used to configure routing information and preferences into the UE to influence the selection of the source Prefix. NOTE 1: This corresponds to Scenario 1 defined in IETF RFC 7157 [7] "IPv6 Multi-homing without Network Address Translation". This allows to make the Branching Point unaware of the routing tables in the Data Network and to keep the first hop router function in the PDU Session Anchors. - The multi-homed PDU Session may be used to support make-before-break service continuity to support SSC mode 3. This is illustrated in Figure 5.6.4.3-1. - The multi-homed PDU Session may also be used to support cases where UE needs to access both a local service (e.g. local server) and a central service (e.g. the internet), illustrated in Figure 5.6.4.3-2. - The UE shall use the method specified in clause 4.3.5.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] to determine if a multi-homed PDU Session is used to support the service continuity case shown in Figure 5.6.4.3-1, or if it is used to support the local access to DN case shown in Figure 5.6.4.3-2. Figure 5.6.4.3-1: Multi-homed PDU Session: service continuity case NOTE 2: It is possible for a given UPF to support both the Branching Point and the PDU Session Anchor functionalities. Figure 5.6.4.3-2: Multi-homed PDU Session: local access to same DN NOTE 3: It is possible for a given UPF to support both the Branching Point and the PDU Session Anchor functionalities. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.6.4.3 |
3,210 | 6.2.6.2 NF profile | NF profile of NF instance maintained in an NRF includes the following information: - NF instance ID. - NF type. - PLMN ID in the case of PLMN, PLMN ID + NID in the case of SNPN. - Network Slice related Identifier(s) e.g. S-NSSAI, NSI ID. - FQDN or IP address of NF. - NF capacity information. - NF priority information. NOTE 1: This parameter is used for AMF selection, if applicable, as specified in clause 6.3.5. See clause 6.1.6.2.2 of TS 29.510[ 5G System; Network function repository services; Stage 3 ] [58] for its detailed use. - NF Set ID. - NF Service Set ID of the NF service instance. - NF Specific Service authorization information. - if applicable, Names of supported services. - Endpoint Address(es) of instance(s) of each supported service. - Identification of stored data/information. NOTE 2: This is only applicable for a UDR profile. See applicable input parameters for Nnrf_NFManagement_NFRegister service operation in clause 5.2.7.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. This information applicability to other NF profiles is implementation specific. - Other service parameter, e.g. DNN or DNN list, notification endpoint for each type of notification that the NF service is interested in receiving. - Location information for the NF instance. NOTE 3: This information is operator specific. Examples of such information can be geographical location, data centre. - TAI(s). - NF load information. - Routing Indicator, Home Network Public Key identifier, for UDM and AUSF. - For UDM, AUSF and NSSAAF in the case of access to an SNPN using credentials owned by a Credentials Holder with AAA Server, identification of Credentials Holder (i.e. the realm of the Network Specific Identifier based SUPI). - For UDM and AUSF, and if UDM/AUSF is used for access to an SNPN using credentials owned by a Credentials Holder, identification of Credentials Holder (i.e. the realm if Network Specific Identifier based SUPI is used or the MCC and MNC if IMSI based SUPI is used); see clause 5.30.2.1. - For AUSF and NSSAAF in the case of SNPN Onboarding using a DCS with AAA server, identification of DCS (i.e. the realm of the Network Specific Identifier based SUPI). - For UDM and AUSF, and if UDM/AUSF is used as DCS in the case of SNPN Onboarding, identification of DCS (i.e. the realm if Network Specific Identifier based SUPI, or the MCC and MNC if IMSI based SUPI). - One or more GUAMI(s), in the case of AMF. - For the UPF, see clause 5.2.7.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. - UDM Group ID, range(s) of SUPIs, range(s) of GPSIs, range(s) of internal group identifiers, range(s) of external group identifiers for UDM. - UDR Group ID, range(s) of SUPIs, range(s) of GPSIs, range(s) of external group identifiers for UDR. - AUSF Group ID, range(s) of SUPIs for AUSF. - PCF Group ID, range(s) of SUPIs for PCF. - HSS Group ID, set(s) of IMPIs, set(s) of IMPU, set(s) of IMSIs, set(s) of PSIs, set(s) of MSISDN for HSS. - For NWDAF, the following information are supported: - Analytics ID(s) (possibly per service). - NWDAF Serving Area information (i.e. list of TAIs for which the NWDAF can provide services and/or data). - Supported Analytics Delay per Analytics ID (if available). - NF types of the NF data sources, NF Set IDs of the NF data sources, if available. - Analytics aggregation capability (if available). - Analytics metadata provisioning capability (if available). - ML model Filter information parameters include S-NSSAI(s) and Area(s) of Interest for the trained ML model(s) per Analytics ID(s). - ML Model Interoperability indicator (if available) per Analytics ID(s). - FL capability information per analytics ID including FL capability type (i.e. FL server NWDAF or FL client NWDAF, if available). - Time interval supporting FL (if available). - Accuracy checking capability for ML model accuracy monitoring or Analytics Accuracy Monitoring (if available). - Roaming exchange capability (if available). NOTE 4: The NWDAF's Serving Area information is common to all its supported Analytics IDs. NOTE 5: The Analytics IDs supported by the NWDAF may be associated with a Supported Analytics Delay i.e. the Analytics report can be generated with a time (including data collection delay and inference delay) in less than or equal to the Supported Analytics Delay. NOTE 6: The determination of Supported Analytics Delay, and how the NWDAF avoid updating its Supported Analytics Delay in NRF frequently is NWDAF implementation specific. - Event ID(s) supported by AFs, in the case of NEF. - Event Exposure service supported event ID(s) by UPF. - Application Identifier(s) supported by AFs, in the case of NEF. - Range(s) of External Identifiers, or range(s) of External Group Identifiers, or the domain names served by the NEF, in the case of NEF. NOTE 7: This is applicable when NEF exposes AF information for analytics purpose as detailed in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86]. NOTE 8: It is expected service authorization information is usually provided by OA&M system, and it can also be included in the NF profile in the case that e.g. an NF instance has an exceptional service authorization information. NOTE 9: The NRF may store a mapping between UDM Group ID and SUPI(s), UDR Group ID and SUPI(s), AUSF Group ID and SUPI(s) and PCF Group ID and SUPI(s), to enable discovery of UDM, UDR, AUSF and PCF using SUPI, SUPI ranges as specified in clause 6.3 or interact with UDR to resolve the UDM Group ID/UDR Group ID/AUSF Group ID/PCF Group ID based on UE identity, e.g. SUPI (see clause 6.3.1 for details). - IP domain list as described in clause 6.1.6.2.21 of TS 29.510[ 5G System; Network function repository services; Stage 3 ] [58], Range(s) of (UE) IPv4 addresses or Range(s) of (UE) IPv6 prefixes, Range(s) of SUPIs or Range(s) of GPSIs or a BSF Group ID, in the case of BSF. - SCP Domain the NF belongs to. - DCCF Serving Area information, NF types of the data sources, NF Set IDs of the data sources, if available, in the case of DCCF. - Supported DNAI list, in the case of SMF. - For SNPN, capability to support SNPN Onboarding in the case of AMF and capability to support User Plane Remote Provisioning in the case of SMF. - IP address range, DNAI for UPF. - Additional V2X related NF profile parameters are defined in TS 23.287[ Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services ] [121]. - Additional ProSe related NF profile parameters are defined in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [128]. - Additional MBS related NF profile parameters are defined in TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [129]. - Additional UAS related NF profile parameters are defined in TS 23.256[ Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2 ] [136]. - Additional Ranging based services and Sidelink Positioning related NF profile parameters are defined in TS 23.586[ Architectural Enhancements to support Ranging based services and Sidelink Positioning ] [180]. - For additional information in PCF profile, see clause 5.2.7.2.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") | 6.2.6.2 |
3,211 | 8.4.3 SCG suspend/resume in RRC_INACTIVE | In the following, the procedure for SCG resume in RRC_INACTIVE is described. Figure 8.4.3-1: SCG Suspend/Resume in RRC_INACTIVE 1. The CU of SN sends the UE CONTEXT MODIFICATION REQUEST message to the DU of SN to suspend the SCG of the UE before the UE enters into RRC_INACTIVE state from RRC_CONNECTED state. 2. The DU of SN sends the UE CONTEXT MODIFICATION RESPONSE to the CU of SN, and keeps all lower layer configuration for UEs without transmitting or receiving data from UE. 3~4: refer to TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [12]. 5. The CU of SN sends the UE CONTEXT MODIFICATION REQUEST message to the DU of SN to resume the SCG of the UE before the UE enters into RRC_CONNECTED state from RRC_INACTIVE state. 6. The DU of SN sends the UE CONTEXT MODIFICATION RESPONSE message to the CU of SN, and uses the previously stored lower layer configuration for the UE. 7~11: refer to TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [12]. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.4.3 |
3,212 | I.9.2.2 Primary authentication without using DCS | When the primary authentication is performed between the UE and the ON-SNPN, any one of the existing authentication methods defined in the present document may be used, i.e., 5G AKA, EAP-AKA’ or any other key-generating EAP authentication method (e.g., EAP-TLS). The choice of primary authentication method used is left to the decision of the ON-SNPN. Credentials required to authenticate the UE using default UE credentials for primary authentication, are provisioned at the AUSF or AUSF/UDM of the ON-SNPN. The provisioning of this information is out of scope of this document. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | I.9.2.2 |
3,213 | 4.15.6 External Parameter Provisioning 4.15.6.1 General | Provisioning capability allows an external party to provision the information, such as expected UE behaviour and service specific parameters or the 5G VN group information to 5G network functions. In the case of provisioning the expected UE behavioural information, the expected UE behavioural information consists of information on expected UE movement and communication characteristics. In the case of provisioning the 5G VN group information the provisioning information consists of information on 5G VN group. The service specific information consists of information to support the specific service in 5G system. Provisioned data can be used by the other NFs. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.6 |
3,214 | 5.4.1 Secure messaging between the USIM and the network | USIM Application Toolkit, as specified in TS 31.111[ Universal Subscriber Identity Module (USIM) Application Toolkit (USAT) ] [15], provides the capability for operators or third party providers to create applications which are resident on the USIM (similar to SIM Application Toolkit in GSM). There exists a need to secure messages which are transferred over the network to applications on the USIM, with the level of security chosen by the network operator or the application provider. Security features for USIM Application Toolkit are implemented by means of the mechanisms described in TS 23.048[ Security mechanisms for the (U)SIM application toolkit; Stage 2 ] [7]. These mechanisms address the security requirements identified in TS 22.048[ Security mechanisms for the (U)SIM application toolkit; Stage 1 ] [16]. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 5.4.1 |
3,215 | 5.4.7 NG-RAN location reporting | NG-RAN supports the NG-RAN location reporting for the services that require accurate cell identification (e.g. emergency services, lawful intercept, charging) or for the UE mobility event notification service subscribed to the AMF by other NFs. The NG-RAN location reporting may be used by the AMF when the target UE is in CM-CONNECTED state. The NG-RAN location reporting may be used by the AMF to determine the geographically located TAI in the case of NR satellite access. The AMF may request the NG-RAN location reporting with event reporting type (e.g. UE location or UE presence in Area of Interest), reporting mode and its related parameters (e.g. number of reporting). If the AMF requests UE location, the NG-RAN reports the current UE location (or last known UE location with time stamp if the UE is in RRC_INACTIVE state) based on the requested reporting parameter (e.g. one-time reporting or continuous reporting). If the AMF requests UE location, in the case of NR satellite access, the NG-RAN provides all broadcast TAIs to the AMF as part of the ULI. The NG-RAN also reports the TAI where the UE is geographically located if this TAI can be determined. If the AMF requests UE presence in the Area Of Interest, the NG-RAN reports the UE location and the indication (i.e. IN, OUT or UNKNOWN) when the NG-RAN determines the change of UE presence in Area Of Interest. After N2 based Handover, if the NG-RAN location reporting information is required, the AMF shall re-request the NG-RAN location reporting to the target NG-RAN node. For Xn based Handover, the source NG-RAN shall transfer the requested NG-RAN location reporting information to target NG-RAN node. The AMF requests the location information of the UE either through independent N2 procedure (i.e. NG-RAN location reporting as specified in clause 4.10 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]), or by including the request in some specific N2 messages as specified in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.4.7 |
3,216 | 5.2.18.3.1 Nucmf_UECapabilityManagement Resolve service operation | Service Operation name: Nucmf_UECapabilityManagement_Resolve Description: Consumer NF gets the UE Radio Access Capability and one or more UE Radio Capability for Paging corresponding to a specific UE Radio Capability ID (either Manufacturer-assigned or PLMN-assigned) and Coding Format. Inputs, Required: UE Radio Capability ID, Coding format, one or more UE Radio Capability for Paging. Inputs, Optional: None. Outputs, Required: UE Radio Access Capability, UE Radio Capability for Paging. Outputs, Optional: None. The Coding format indicates the format as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [16] or TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12] of the UE Radio Access Capability expected by the NF in output. When the Coding Format is TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [16], the UCMF shall provide the UE Radio Capability for Paging for E-UTRA. When the Coding Format is TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12], the UCMF shall provide the UE Radio Capability for Paging for NR and if the PLMN supports E-UTRA connected to 5GC, shall provide the UE Radio Capability for Paging for E-UTRA. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.18.3.1 |
3,217 | 4.4.3 IMS support | IMS support for 5GC is defined in TS 23.228[ IP Multimedia Subsystem (IMS); Stage 2 ] [15]. The 5G System architecture supports N5 interface between PCF and P-CSCF and supports Rx interface between PCF and P-CSCF, to enable IMS service. See TS 23.228[ IP Multimedia Subsystem (IMS); Stage 2 ] [15], TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45] and TS 23.203[ Policy and charging control architecture ] [4]. NOTE 1: Rx support between PCF and P-CSCF is for backwards compatibility for early deployments using Diameter between IMS and 5GC functions. NOTE 2: When service based interfaces are used between the PCF and P-CSCF in the same PLMN, the P-CSCF performs the functions of a trusted AF in the 5GC. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.4.3 |
3,218 | 5.2.5.4.5 Npcf_SMPolicyControl_Update service operation | Service operation name: Npcf_SMPolicyControl_Update. Description: The NF Service Consumer can request the update of the SM Policy Association to receive updated Policy information for the PDU Session. Inputs, Required: SM Policy Association ID. Inputs, Optional: Information on the Policy Control Request Trigger condition that has been met, as defined in clause 6.1.3.5 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. W-5GAN specific PDU Session information provided by the SMF is specified in TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [53]. Outputs, Required: Success or not. Outputs, Optional: Policy information for the PDU Session as defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20] and Policy Control Request Trigger(s) of SM Policy Association as defined in clause 6.1.3.5 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20] and UE Policy Container. See clause 4.16.5.1 for the usage of this service operation. NOTE: When this service operation is invoked by SMF, race conditions apply, which are defined in TS 29.513[ 5G System; Policy and Charging Control signalling flows and QoS parameter mapping; Stage 3 ] [47]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.5.4.5 |
3,219 | 4.4 RF requirements in later releases | The standardisation of new frequency bands and carrier aggregation configurations (downlink and uplink aggregation) may be independent of a release. However, in order to implement a UE that conforms to a particular release but supports a band of operation or a carrier aggregation configuration that is specified in a later release, it is necessary to specify some extra requirements. TS 36.307[ Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements on User Equipments (UEs) supporting a release-independent frequency band ] [8] specifies requirements on UEs supporting a frequency band or a carrier aggregation configuration that is independent of release. NOTE: For UEs conforming to the 3GPP release of the present document, some RF requirements of later releases may be mandatory independent of whether the UE supports the bands specif or carrier aggregation configurations ied in later releases or not. The set of RF requirements of later releases that is also mandatory for UEs conforming to the 3GPP release of the present document is determined by regional regulation. | 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 | 4.4 |
3,220 | 4.23.11.2 Xn based handover with insertion of intermediate SMF | This procedure is used to hand over a UE from a Source NG-RAN to a Target NG-RAN using Xn interface (in this case the AMF is unchanged) and the AMF decides that insertion of a new intermediate I-SMF is needed. This procedure is used for non-roaming or local breakout roaming scenario. The call flow is shown in figure 4.23.11.2-1. Figure 4.23.11.2-1: Xn based inter NG-RAN handover with insertion of intermediate SMF 1. Step 1 is the same as described in clause 4.9.1.2.2. 2. For each PDU Session Rejected in the list of PDU Sessions received in the N2 Path Switch Request, the AMF perform same step as step 2 in clause 4.9.1.2.2. The rest of this procedure applies for each PDU Session To Be Switched. 3a. The AMF checks if an I-SMF needs to be selected as described in clause 5.34.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 3b. If a new I-SMF is selected the AMF sends Nsmf_PDUSession_CreateSMContext Request (SUPI, AMF ID, SMF ID, SM Context ID, PDU Session To Be Switched with N2 SM Information (Secondary RAT usage data), UE Location Information, UE presence in LADN service area) to the new selected I-SMF. 4. The new I-SMF sends Nsmf_PDUSession_Context Request (SM context type, SM Context ID) to SMF to retrieve the SM Context. The new I-SMF uses SM Context ID received from AMF for this service operation. SM context type indicates that the requested information is all SM context, i.e. PDN Connection Context and 5G SM context. The SM Context ID is used by the recipient of Nsmf_PDUSession_Context Request in order to determine the targeted PDU Session. 5a. I-SMF to I-UPF: N4 Session Establishment Request (Target NG-RAN Tunnel Info). The I-SMF then selects a I-UPF based on UPF Selection Criteria according to clause 6.3.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. An N4 Session Establishment Request message is sent to the I-UPF. The target NG-RAN Tunnel Info is included in the N4 Session Establishment Request message. 5b. I-UPF to I-SMF: N4 Session Establishment Response. The I-UPF sends an N4 Session Establishment Response message to the I-SMF. The UL CN Tunnel Info and DL CN Tunnel Info of I-UPF are sent to the I-SMF. 6. I-SMF to SMF: Nsmf_PDUSession_Create Request to the SMF (SUPI, PDU Session ID, Secondary RAT usage data, UE Location Information, UE presence in LADN service area, DL CN Tunnel Info of the I-UPF, DNAI list supported by the I-SMF). The I-SMF provides the DNAI list it supports to the SMF as defined in Figure 4.23.9.1-1 step 1. Secondary RAT usage data is extracted from N2 SM Information within PDU Session To Be Switched received from NG RAN. 7a. SMF to UPF (PSA): N4 Session Modification Request (DL CN Tunnel Info of the I-UPF). The SMF provides the DL CN Tunnel Info of the I-UPF to the UPF(PSA). If old I-UPF controlled by SMF does not exist and if different CN Tunnel Info need to be used by PSA UPF, i.e. the CN Tunnel Info at the PSA for N3 and N9 are different, the CN Tunnel Info at the PSA for N9 needs to be allocated. The CN Tunnel Info is provided from UPF to SMF in the response. 7b. UPF (PSA) to SMF: N4 Session Modification Response. The PDU Session Anchor responds with the N4 Session Modification Response message after requested PDU Sessions are switched. At this point, PDU Session Anchor starts sending downlink packets to the Target NG-RAN via I-UPF. PDU Session Anchor sends one or more "end marker" packets for each N3/N9 tunnel on the old path immediately after switching the path, the source NG-RAN shall forward the "end marker" packets to the target NG-RAN. 8. In order to assist the reordering function in the Target NG-RAN, the PDU Session Anchor sends one or more "end marker" packets for each N3/N9 tunnel on the old path immediately after switching the path, the source NG-RAN shall forward the "end marker" packets to the target NG-RAN. 9. SMF to I-SMF: Nsmf_PDUSession_Create Response(Information for local traffic steering location, CN Tunnel Info at the PSA for N9, updated CN PDB in the QoS parameters for accepted QoS Flows). The SMF may update the CN PDB in the response or using a separate PDU Session Modification procedure, based on local configuration. 9a. If the CN Tunnel Info at PSA for N9 is allocated, it is included in the response and the I-SMF provides the CN Tunnel Info at the PSA for N9 to I-UPF via N4 Session Modification Request. In the case of I-SMF insertion and the PDU session corresponds to a LADN, the SMF shall release the PDU session after the handover procedure is completed. 10. I-SMF to AMF: Nsmf_PDUSession_CreateSMContext Response (UL CN Tunnel Info of the I-UPF, updated CN PDB in the QoS parameters for accepted QoS Flows). The SMF sends an Nsmf_PDUSession_CreateSMContext response to the AMF. 11-13. Steps 11-13 are same as steps 7-9 defined in clause 4.9.1.2.2 with the following addition: If a Source I-UPF controlled by SMF was serving the PDU Session, the SMF initiates Source I-UPF Release procedure by sending an N4 Session Release Request toward the Source I-UPF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.11.2 |
3,221 | 8.10.1.1.5 Enhanced Performance Requirement Type A – Single-layer Spatial Multiplexing with TM9 interference model (User-Specific Reference Symbols) | The requirements are specified in Table 8.10.1.1.5-2, with the addition of the parameters in Table 8.10.1.1.5-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify closed loop rank one performance on one of the antenna ports 7 or 8 without a simultaneous transmission on the other antenna port in the serving cell when the PDSCH transmission in the serving cell is interfered by PDSCH of one dominant interfering cell applying transmission mode 9 interference model defined in clause B.5.4. In 8.10.1.1.5-1, Cell 1 is the serving cell, and Cell 2 is the interfering cell. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1 and Cell 2, respectively. Table 8.10.1.1.5-1: Test Parameters for Testing CDM-multiplexed DM RS (single layer) with TM9 interference model and 4 RX Antenna Ports Table 8.10.1.1.5-2: Enhanced Performance Requirement Type A, CDM-multiplexed DM RS with TM9 interference model and 4 RX Antenna Ports | 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.10.1.1.5 |
3,222 | 5.15.5.2.3 AMF Re-allocation due to Network Slice(s) Support | During a Registration procedure in a PLMN, if the network decides that the UE should be served by a different AMF based on Network Slice(s) aspects, then the AMF that first received the Registration Request shall redirect the Registration request to target AMF via the 5G-AN or via direct signalling between the initial AMF and the target AMF. If the target AMF(s) are returned from the NSSF and identified by a list of candidate AMF(s), the redirection message shall only be sent via the direct signalling between the initial AMF and the target AMF. If the redirection message is sent by the AMF via the 5G-AN, the message shall include information for selection of a new AMF to serve the UE. When during a Registration procedure the UE requests a new S-NSSAI which is not supported in the UE's current Tracking Area, the serving AMF itself or by interacting with the NSSF as described in clause 5.15.5.2.1 may determine a Target NSSAI. The AMF provides the Target NSSAI to the NG-RAN and the NG-RAN may apply redirection or handover of the UE to a cell in another TA supporting the Target NSSAI as described in clause 5.3.4.3.3. During a EPS to 5GS handover using N26 interface procedure, if the network decides that the UE should be served by a different AMF based on Network Slice(s) aspects, then the AMF, which received the Forward Relocation Request from MME, shall forward the UE context to target AMF via direct signalling between the initial AMF and the target AMF as described in clause 4.11.1.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. For a UE that is already registered, the system shall support a redirection initiated by the network of a UE from its serving AMF to a target AMF due to Network Slice(s) considerations (e.g. the operator has changed the mapping between the Network Slice instances and their respective serving AMF(s)). Operator policy determines whether redirection between AMFs is allowed. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.5.2.3 |
3,223 | – SI-RequestConfig | The IE SI-RequestConfig contains configuration for Msg1 based SI request without Msg1 repetition. SI-RequestConfig information element -- ASN1START -- TAG-SI-REQUESTCONFIG-START SI-RequestConfig ::= SEQUENCE { rach-OccasionsSI SEQUENCE { rach-ConfigSI RACH-ConfigGeneric, ssb-perRACH-Occasion ENUMERATED {oneEighth, oneFourth, oneHalf, one, two, four, eight, sixteen} } OPTIONAL, -- Need R si-RequestPeriod ENUMERATED {one, two, four, six, eight, ten, twelve, sixteen} OPTIONAL, -- Need R si-RequestResources SEQUENCE (SIZE (1..maxSI-Message)) OF SI-RequestResources } SI-RequestResources ::= SEQUENCE { ra-PreambleStartIndex INTEGER (0..63), ra-AssociationPeriodIndex INTEGER (0..15) OPTIONAL, -- Need R ra-ssb-OccasionMaskIndex INTEGER (0..15) OPTIONAL -- Need R } -- TAG-SI-REQUESTCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,224 | A.2 Cause related to subscription options | Cause #5 – IMEI not accepted This cause is sent to the UE if the network does not accept an attach procedure for emergency bearer services using an IMEI. Cause #7 – EPS services not allowed This EMM cause is sent to the UE when it is not allowed to operate EPS services. Cause #8 – EPS services and non-EPS services not allowed This EMM cause is sent to the UE when it is not allowed to operate either EPS or non-EPS services. Cause #11 – PLMN not allowed This EMM cause is sent to the UE if it requests service, or if the network initiates a detach request, in a PLMN where the UE, by subscription or due to operator determined barring, is not allowed to operate. Cause #12 – Tracking area not allowed This EMM cause is sent to the UE if it requests service, or if the network initiates a detach request, in a tracking area where the HPLMN determines that the UE, by subscription, is not allowed to operate. NOTE 1: If EMM cause #12 is sent to a roaming subscriber the subscriber is denied service even if other PLMNs are available on which registration was possible. Cause #13 – Roaming not allowed in this tracking area This EMM cause is sent to an UE which requests service, or if the network initiates a detach request, in a tracking area of a PLMN which by subscription offers roaming to that UE but not in that tracking area. Cause #14 – EPS services not allowed in this PLMN This EMM cause is sent to the UE which requests service, or if the network initiates a detach request, in a PLMN which does not offer roaming for EPS services to that UE. NOTE 2: Since only one list of forbidden PLMNs for packet services is maintained in the UE, then the "forbidden PLMNs for GPRS service" is the maintained list and the forbidden PLMNs for EPS service is equivalent to it. Cause #15 – No suitable cells in tracking area This EMM cause is sent to the UE if it requests service, or if the network initiates a detach request, in a tracking area where the UE, by subscription, is not allowed to operate, but when it should find another allowed tracking area or location area in the same PLMN or an equivalent PLMN. NOTE 3: Cause #15 and cause #12 differ in the fact that cause #12 does not trigger the UE to search for another allowed tracking area on the same PLMN. Cause #25 – Not authorized for this CSG This EMM cause is sent to the UE if it requests access, or if the network initiates a detach request, in a CSG cell with CSG ID where the UE either has no subscription to operate or the UE's subscription has expired and it should find another cell in the same PLMN or an equivalent PLMN. Cause #35 – Requested service option not authorized in this PLMN This EMM cause is sent to the UE if it requests in a PLMN a service option for which it is not authorized, e.g. if it attempts to attach for relay node operation in a PLMN with a USIM which does not belong to a relay node-specific subscription. Cause #36 – IAB-node operation not authorized This EMM cause is sent to the UE if a UE operating as an IAB-node requests service, or if the network initiates a detach request, in a PLMN where the UE, by subscription, is not authorized for IAB operation. Cause #40 – No EPS bearer context activated This EMM cause is sent to the UE, if during a tracking area updating procedure or a service request, the MME detects that there is no active EPS bearer context in the network. Cause #31 – Redirection to 5GCN required This EMM cause is sent to the UE if it requests service in a PLMN where the UE by operator policy, is not allowed in EPC and redirection to 5GCN is required. | 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 | A.2 |
3,225 | 5.5.1.2.3 EMM common procedure initiation | The network may initiate EMM common procedures, e.g. the identification, authentication and security mode control procedures during the attach procedure, depending on the information received in the ATTACH REQUEST message (e.g. IMSI, GUTI and KSI). If the network receives an ATTACH REQUEST message containing the Old GUTI type IE and the EPS mobile identity IE with type of identity indicating "GUTI", and the network does not follow the use of the most significant bit of the < group id> as specified in 3GPP TS 23.003[ Numbering, addressing and identification ] [2], clause 2.8.2.2.2, the network shall use the Old GUTI type IE to determine whether the mobile identity included in the EPS mobile identity IE is a native GUTI or a mapped GUTI. During an attach for emergency bearer services or an attach for access to RLOS, the MME may choose to skip the authentication procedure even if no EPS security context is available and proceed directly to the execution of the security mode control procedure as specified in clause 5.4.3. | 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.3 |
3,226 | 5.2.5.8.5 Npcf_AMPolicyAuthorization_Notify service operation | Service operation name: Npcf_AMPolicyAuthorization_Notify Description: provided by the PCF to notify NF consumers of the subscribed events. Inputs, Required: Subscription Correlation ID, Event ID. The event that can be subscribed is the event for request for allocation of service area coverage defined in clause 6.1.3.18 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. Inputs, Optional: Event information as defined in clause 6.1.3.18 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. 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.5.8.5 |
3,227 | 6.4.2.4 UE-requested PDU session modification procedure not accepted by the network 6.4.2.4.1 General | Upon receipt of a PDU SESSION MODIFICATION REQUEST message, if the SMF does not accepts the request to modify the PDU session, the SMF shall create a PDU SESSION MODIFICATION REJECT message. The SMF shall set the 5GSM cause IE of the PDU SESSION MODIFICATION REJECT message to indicate the reason for rejecting the PDU session modification. The 5GSM cause IE typically indicates one of the following SM cause values: #26 insufficient resources; #29 user authentication or authorization failed; #31 request rejected, unspecified; #32 service option not supported; #33 requested service option not subscribed; #35 PTI already in use; #37 5GS QoS not accepted; #43 Invalid PDU session identity; #44 Semantic errors in packet filter(s); #45 Syntactical error in packet filter(s); #46 out of LADN service area; #59 unsupported 5QI value; #67 insufficient resources for specific slice and DNN; #69 insufficient resources for specific slice; #83 Semantic error in the QoS operation; #84 Syntactical error in the QoS operation; or #95 – 111 protocol errors. If the UE requests a PDU session modification for an LADN when the UE is located outside of the LADN service area, the SMF shall include the 5GSM cause value #46 "out of LADN service area" in the 5GSM cause IE of the PDU SESSION MODIFICATION REJECT message. If the Extended protocol configuration options IE of the PDU SESSION MODIFICATION REQUEST message indicates 3GPP PS data off UE status and the SMF detects the change of the 3GPP PS data off UE status, the SMF shall not include the 5GSM cause value #26 "insufficient resources", the 5GSM cause value #67 "insufficient resources for specific slice and DNN", the 5GSM cause value #69 "insufficient resources for specific slice" and the 5GSM cause value #46 "out of LADN service area" in the 5GSM cause IE of the PDU SESSION MODIFICATION REJECT message. If the UE initiates UE-requested PDU session modification procedure to modify the PDU session transferred from EPS to an MA PDU session with the Request type IE set to "MA PDU request" in the UL NAS TRANSPORT message as specified in 3GPP TS 24.193[ 5G System;Access Traffic Steering, Switching and Splitting (ATSSS); Stage 3 ] [13B] and the SMF determines, based on operator policy and subscription information, that the PDU SESSION MODIFICATION REQUEST message is to be rejected, the SMF shall include the 5GSM cause value #33 "requested service option not subscribed" in the 5GSM cause IE of the PDU SESSION MODIFICATION REJECT message. NOTE: If the SMF determines, based on operator policy and subscription information, that the PDU SESSION MODIFICATION REQUEST message is to be accepted as single access PDU session, the ATSSS container IE cannot be included in the PDU SESSION MODIFICATION COMMAND message. The network may include a Back-off timer value IE in the PDU SESSION MODIFICATION REJECT message. If the 5GSM cause value is #26"insufficient resources", #67 "insufficient resources for specific slice and DNN", or #69 "insufficient resources for specific slice" and the PDU SESSION MODIFICATION REQUEST message was received from a UE configured for high priority access in selected PLMN or SNPN or the request type provided during the PDU session establishment is set to "initial emergency request" or "existing emergency PDU session", the network shall not include a Back-off timer value IE. The SMF shall send the PDU SESSION MODIFICATION REJECT message. Upon receipt of a PDU SESSION MODIFICATION REJECT message and a PDU session ID, using the NAS transport procedure as specified in subclause 5.4.5, the UE shall stop timer T3581, release the allocated PTI value, and enter the state PROCEDURE TRANSACTION INACTIVE. If the PDU SESSION MODIFICATION REQUEST message was sent with the Requested MBS container IE included and the MBS operation set to "Join MBS session", and the UE receives a PDU SESSION MODIFICATION REJECT message, then the UE shall consider the requested MBS join as rejected. If the PDU SESSION MODIFICATION REQUEST message was sent with the Requested MBS container IE included and the MBS operation set to "Leave MBS session", and the UE receives a PDU SESSION MODIFICATION REJECT message, then the UE shall locally leave the multicast MBS session(s) corresponding to the TMGI(s) in the Requested MBS container IE of the PDU SESSION MODIFICATION REQUEST message. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.4.2.4 |
3,228 | G.3 An SCP based on independent deployment units | This clause shows an overview of SCP deployment based on the 5GC functionality and SCP being deployed in independent deployment units. Figure G.3-1: Independent deployment units for SCP and 5GC functionality The SCP deployment unit can internally make use of microservices, however these microservices are up to vendors implementation and can be for example SCP agents and SCP controller as used in this example. The SCP agents implement the http intermediaries between service consumers and service producers. The SCP agents are controlled by the SCP controller. Communication between SCP controller and SCP agents is via SCP internal interface (4) and up to vendors implementation. In this model it is a deployment choice to co-locate SCP and other 5GC functions or not. The SCP interfaces (1), (2) and (3) are service based interfaces. SCP itself is not a service producer itself, however acting as http proxy it registers services on behave of the producers in NRF. Interface (2) represents same services as (1) however using SCP proxy addresses. Interface (3) is interfacing NRF e.g. for service registration on behalf of the 5GC functions or service discovery. Figure G.3-2: 5GC functionality and SCP co-location choices For SBI-based interactions with other 5GC functions, a consumer communicates through a SCP agent via SBI (1). SCP agent selects a target based on the request and routes the request to the target SCP agent (2). What routing and selection policies each SCP agent applies for a given request is determined by routing and selection policies determined by the SCP controller using for example information provided via NRF (3) or locally configured in the SCP controller. The routing and selection information is provided by the SCP controller to the SCP agents via SCP internal interface (4). Direct communication can coexist in the same deployment based on 3GPP specified mechanisms. Figure G.3-3: Overview of SCP deployment | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | G.3 |
3,229 | 6.1.3.17 PDCP Duplication Activation/Deactivation MAC Control Element | PDCP Duplication Activation/Deactivation MAC control element is identified by a MAC PDU subheader with LCID as specified in table 6.2.1-1. It has a fixed size, consists of a single octet containing eight D-fields, and is defined, for a MAC entity, as follows (figure 6.1.3.17-1): - Di: this field refers to the i-th DRB in the ascending order of the DRB identity among the established DRB(s) configured with duplication and with RLC entity(ies) associated with this MAC entity. Di field set to "1" indicates that the duplication shall be activated and Di field set to "0" indicates that the duplication shall be deactivated. Figure 6.1.3.17-1: PDCP Duplication Activation/Deactivation MAC Control Element | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.1.3.17 |
3,230 | 6.2.2 MAC header for Random Access Response | The MAC header is of variable size and consists of the following fields: - E: The Extension field is a flag indicating if more fields are present in the MAC header or not. The E field is set to "1" to indicate at least another set of E/T/RAPID fields follows. The E field is set to "0" to indicate that a MAC RAR or padding starts at the next byte; - T: The Type field is a flag indicating whether the MAC subheader contains a Random Access ID or a Backoff Indicator. The T field is set to "0" to indicate the presence of a Backoff Indicator field in the subheader (BI). The T field is set to "1" to indicate the presence of a Random Access Preamble ID field in the subheader (RAPID); - R: Reserved bit, set to "0"; - BI: The Backoff Indicator field identifies the overload condition in the cell. The size of the BI field is 4 bits; - RAPID: The Random Access Preamble IDentifier field identifies the transmitted Random Access Preamble (see clause 5.1.3). The size of the RAPID field is 6 bits. The MAC header and subheaders are octet aligned. NOTE: For NB-IoT, the Random Access Preamble IDentifier field corresponds to the start subcarrier index. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.2.2 |
3,231 | 5.4.8 E-UTRAN initiated UE Context Modification procedure | When split bearer option is applied to support dual connectivity operation, this procedure is used is by the eNodeB to request the modifications on the established UE Context. In the current version of the specification, this procedure is only used for membership verification, as described in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. Figure 5.4.7-1: E-UTRAN initiated UE context modification procedure 1. The addition of an hybrid HeNB as the SeNodeB is triggered, providing the CSG-ID and the CSG Membership Information to the MeNodeB. 2. The Master eNodeB sends UE Context Modification Indication message to the MME, which includes the CSG Membership Information of the SeNodeB. 3. The MME verifies the CSG membership based on the provided CSG Membership Information as specified in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5], but does not update the User CSG Information in the Core Network. A failure of the CSG Membership Information verification does not impact the E-UTRAN UE Context Modification procedure. 4. The MME confirms the UE Context Modification Indication with the UE Context Modification Confirm (CSG Membership Status) message. If CSG Membership Information was not present in the UE Context Modification Indication message, the MME can not perform CSG Membership Information verification and does not provide CSG Membership Status in the UE Context Modification Confirm message. 5. If the CSG Membership Status returned by the MME is different from what was reported by the UE, the eNodeB may decide on further actions. | 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.4.8 |
3,232 | 5.2.2.4.8 Actions upon reception of SIB7 | Upon receiving the SIB7 the UE shall: 1> if there is no current value for messageIdentifier and serialNumber for SIB7; or 1> if either the received value of messageIdentifier or of serialNumber, or of both messageIdentifier and serialNumber are different from the current values of messageIdentifier and serialNumber for SIB7: 2> use the received values of messageIdentifier and serialNumber for SIB7 as the current values of messageIdentifier and serialNumber for SIB7; 2> discard any previously buffered warningMessageSegment; 2> if all segments of a warning message have been received: 3> assemble the warning message from the received warningMessageSegment(s); 3> forward the received warning message, messageIdentifier, serialNumber and dataCodingScheme to upper layers; 3> stop reception of SIB7; 3> discard the current values of messageIdentifier and serialNumber for SIB7; 2> else: 3> store the received warningMessageSegment; 3> continue reception of SIB7; 1> else if all segments of a warning message have been received: 2> assemble the warning message from the received warningMessageSegment(s); 2> forward the received complete warning message, messageIdentifier, serialNumber and dataCodingScheme to upper layers; 2> stop reception of SIB7; 2> discard the current values of messageIdentifier and serialNumber for SIB7; 1> else: 2> store the received warningMessageSegment; 2> continue reception of SIB7; The UE should discard any stored warningMessageSegment and the current value of messageIdentifier and serialNumber for SIB7 if the complete warning message has not been assembled within a period of 3 hours. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.2.2.4.8 |
3,233 | 6.9.2.1.2 Non access stratum | During mobility, NAS aspects that need to be considered are the possible KAMF change, the possible NAS algorithm change at AMF change, and the possible presence of a parallel NAS connection. There is the possibility that the source AMF and the target AMF do not support the same set of NAS algorithms or have different priorities regarding the use of NAS algorithms. In this case, the target AMF re-derives the NAS keys from the existing KAMF (if unchanged) or derives the NAS keys from the new KAMF (if changed) using the NAS algorithm identities and NAS algorithm types as input to the NAS key derivation functions (see Annex A.8). When the KAMF has not changed, all inputs, in particular the KAMF, will be the same in the re-derivation except for the NAS algorithm identity. When the KAMF has changed, new NAS keys are derived irrespective of change in NAS algorithms. In case the KAMF has changed or the target AMF decides to use NAS algorithms different from the ones used by the source AMF, the target AMF shall provide needed parameters to the UE as defined in Clause 6.9.2.3.3 for N2-Handover (i.e., using NAS Container) and Clause 6.9.3 for mobility registration update (i.e., using NAS SMC). NOTE 1: It is per operator's policy how to configure selection of handover types. Depending on an operator's security requirements, the operator can decide whether to have Xn or N2 handovers for a particular gNB/ng-eNB according to the security characteristics of a particular gNB/ng-eNB. NOTE 2: Following key change indicators are involved with N2 handovers. 1) Source AMF indicates AS key re-keying required meaning that the KAMF sent by source AMF to the target AMF is not in sync with current gNB/ng-eNB with keyAmfChangeInd (KAMF Change Indicator). 2) Source AMF indicates that the KAMF sent by source AMF to target AMF has been calculated using horizontal KAMF derivation with keyAmfHDerivationInd (KAMF Horizontal Derivation Indicator). 3) The target AMF indicates a horizontal KAMF derivation to the UE with K_AMF_change_flag in the NAS Container to tell the NAS layer of the UE to change KAMF. 4). The target AMF indicates anAS key re-keying to the gNB/ng-eNB with NSCI (New Security Context Indicator). 5) The gNB/ng-eNB indicates a AS re-keying to the UE with keySetChangeIndicator so that the AS layer of the UE knows that new KgNB needs to be derived from new KAMF instead of NH, and NCC needs to be reset to zero. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.9.2.1.2 |
3,234 | 28.4.2 Format of the S-NSSAI | The structure of the S-NSSAI is depicted in Figure 28.4.2-1 Figure 28.4.2-1: Structure of S-NSSAI The S-NSSAI may include both the SST and SD fields (in which case the S-NSSAI length is 32 bits in total), or the S-NSSAI may just include the SST field (in which case the S-NSSAI length is 8 bits only). The SST field may have standardized and non-standardized values. Values 0 to 127 belong to the standardized SST range and they are defined in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [119]. Values 128 to 255 belong to the Operator-specific range. The SD field has a reserved value "no SD value associated with the SST" defined as hexadecimal FFFFFF. In certain protocols, the SD field is not included to indicate that no SD value is associated with the SST. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.4.2 |
3,235 | 8.3.1.3.4 Minimum requirement with Different Cell ID and non-colliding CRS (with single NZP CSI-RS resource and CRS assistance information is configured) | The requirements are specified in Table 8.3.1.3.4-3, with the additional parameters in Table 8.3.1.3.4-1 and Table 8.3.1.3.4-2. The purpose of this test is to verify the UE capability of supporting non quasi-colocated antenna ports when the UE receives DCI format 2D in a scenario where three transmission points have different Cell ID and non-colliding CRS. In particular the test verifies that the UE, configured with quasi co-location type B, performs correct tracking and compensation of the frequency difference and time difference between two transmission points, channel parameters estimation and rate matching behaviour according to the ‘PDSCH RE Mapping and Quasi-Co-Location Indicator’ signalling defined in [6]. Further, the test verifies that the UE, configured with the CRS assistance information [7], can mitigate interference from CRS for demodulation. The CRS assistance information [7] includes TP 3. In Table 8.3.1.3.4-1, transmission point 1 (TP 1) is serving cell transmitting PDCCH, synchronization signals and PBCH, transmission point 2 (TP 2) transmits PDSCH with different Cell ID, and Transmission point 3 (TP 3) is the aggressor transmission point. The downlink physical channel setup for TP 1 is according to Table C.3.4-1, for TP 2 is according to Table C.3.4-2, and for TP 3 is according to Annex C.3.2. Table 8.3.1.3.4-1: Test Parameters for quasi co-location type B with different Cell ID and non-Colliding CRS when CRS assistance information is configured Table 8.3.1.3.4-2: Configurations of PQI and DL transmission hypothesis for each PQI set Table 8.3.1.3.4-3: Performance Requirements for quasi co-location type B with different Cell ID and non-Colliding CRS when CRS assistance information is configured | 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.3.1.3.4 |
3,236 | 4.2.2.8 Distribution of Abnormally Released Call (QCI1 E-RAB) Duration | a) This measurement provides the histogram result of the samples related to abnormally released call (QCI1 E-RAB) duration collected during measurement period duration. b) CC c) Each sample is measured from the point in time the QCI1 E-RAB has been successfully established via initial Context setup or additional E-RAB setup procedure or incoming handover till the point in time the E-RAB is released via eNB or EPC initiated release procedure according to 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] due to abnormal release cause. The time period with ongoing RLF or user inactivity timer are excluded from measurement the sample duration. Triggering is done for the bin the given sample falls in. d) Each measurement is an integer value. e) The measurement name has the form QCI1ERAB.AbnormCallDurationBinX where X denotes the X-th bin from total number of N configured bins. X-th bin stands for the normal call duration which is within the range from tx-1 to tx. f) Cell g) Valid for packet switched traffic h) EPS i) Each histogram function is represented by the configured number of bins with configured bin width by operator. h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.2.2.8 |
3,237 | 5.43.3.3 Local switching with UL CL/BP and local PSA UPF deployed on satellite | If the UEs using GEO satellite backhaul are served by the same SMF and the GEO satellite(s) serving the UEs has UPF deployed, the SMF may determine to activate local switching and N19 forwarding for the UEs, based on: 1) AF request including of UE identifiers which require communication between UEs as described in clause 5.29.2; and/or 2) Destination IP address(es) reported by on-ground PSA UPF as current reporting mechanism in clause 5.8.5.7. To enable the destination IP address(es) reporting, SMF configures the on-ground PSA UPF to detect UL packets with destination IP addresses which belong to the current UPF address pool. If the SMF determines that the UEs (i.e. corresponding to AF request in bullet 1) and/or the Destination IP address(es) reported in bullet 2)) are under the same GEO satellite (or multiple connectable GEO satellites) based on GEO Satellite ID(s) reported by AMF and the UEs are allowed to access the DNAIs corresponding to the GEO satellite IDs, for each UE communicating with target UE(s) in the communication group, the SMF may select and insert the UPF deployed on GEO satellite according to the DNAI as UL CL/BP and L-PSA, and configures UL CL/BP with the following rule: - Route the data traffic received from the UE and destined to IP address(es) of the target UE(s) to the L-PSA. - Route other data traffic received from the UE to the PSA UPF of the UE's PDU Session. NOTE 1: The SMF determines the GEO satellites are connectable based on configuration. The SMF configures the Local PSA with local forwarding rules to forward the data traffic to the target UEs directly. If the selected L-PSAs are different for the UEs in the communication group, N19 tunnel is established between the L-PSAs. For establishing N19 tunnel between the UPFs onboard the satellite, the UPFs are controlled by the same SMF. If UEs are members of the same 5G VN group, the SMF may configure the local data forwarding rules on L-PSA(s) using 5GVN user plane handing mechanism in clause 5.8.2.13.1 (Support for unicast traffic forwarding of a 5G VN). NOTE 2: The selected UPF deployed on satellite can be inserted as UL CL/BP/L-PSA reusing existing UL CL/BP insertion procedures defined in TS 23.502[ Procedures for the 5G System (5GS) ] [3] or TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130]. N6 may be used for carrying traffic between L-PSA UPFs deployed on different satellites. If N6 is used, SMF configures corresponding N4 rules for processing traffic to/from N6. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.43.3.3 |
3,238 | 5.25.1 Support of Tracing: Signalling Based Activation/Deactivation of Tracing | 5GS supports tracing as described in TS 32.421[ Telecommunication management; Subscriber and equipment trace; Trace concepts and requirements ] [66]. 5GS support may include subscriber tracing (tracing targeting a SUPI) or equipment tracing (tracing targeting a PEI) but also other forms of tracing further described in TS 32.421[ Telecommunication management; Subscriber and equipment trace; Trace concepts and requirements ] [66]. NOTE 1: TS 23.501[ System architecture for the 5G System (5GS) ] / TS 23.502[ Procedures for the 5G System (5GS) ] [3] / TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45] only describe how 5GS signalling supports delivery of Trace Requirements about a UE (Signalling Based Activation/Deactivation of Tracing). OAM delivery of tracing requirements as well as the transfer of tracing results to one or more Operations Systems are out of scope of these documents. The content of Trace Requirements about a UE (e.g. trace reference, address of the Trace Collection Entity, etc.) is defined in TS 32.421[ Telecommunication management; Subscriber and equipment trace; Trace concepts and requirements ] [66]. Trace Requirements about a UE may be configured in subscription data of the UE and delivered together with other subscription data by the UDM towards the AMF, the SMF and/or the SMSF. The AMF propagates Trace Requirements about a UE received from the UDM to network entities not retrieving subscription information from UDM, i.e. to the 5G-AN, to the AUSF and to the PCF. The AMF also propagates Trace Requirements to the SMF and to the SMSF. If the I-SMF or V-SMF is needed for the PDU session, the AMF propagates Trace Requirements to the I-SMF or V-SMF. The I-SMF or V-SMF also propagates Trace Requirements received from the AMF to the I-UPF or V-UPF (over N4). Trace Requirements about a UE may be sent by the AMF to the 5G-AN as part of: - the N2 procedures used to move the UE from CM-IDLE to CM-CONNECTED or, - the N2 procedures to request a Hand-over from a target NG-RAN or, - a stand-alone dedicated N2 procedure when tracing is activated while the UE is CM-CONNECTED. Trace Requirements about a UE sent to a 5G-AN shall not contain information on the SUPI or on the PEI of the UE. Trace Requirements are directly sent from Source to Target NG-RAN in the case of Xn Hand-Over. The SMF propagates Trace Requirements about a UE received from the UDM to the UPF (over N4) and to the PCF. The SMF provides Trace Requirements to the PCF when it has selected a different PCF than the one received from the AMF. Once the SMF or the SMSF has received subscription data, Trace Requirements received from UDM supersede Trace requirements received from the AMF. Trace Requirements are exchanged on N26 between the AMF and the MME. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.25.1 |
3,239 | 5.3.3.2 Initiation | The UE initiates the procedure when upper layers request establishment of an RRC connection while the UE is in RRC_IDLE and it has acquired essential system information, or for sidelink communication as specified in clause 5.3.3.1a. The UE shall ensure having valid and up to date essential system information as specified in clause 5.2.2.2 before initiating this procedure. Upon initiation of the procedure, the UE shall: 1> if the upper layers provide an Access Category and one or more Access Identities upon requesting establishment of an RRC connection: 2> perform the unified access control procedure as specified in 5.3.14 using the Access Category and Access Identities provided by upper layers; 3> if the access attempt is barred, the procedure ends; 1> if the upper layers provide NSAG information and one or more S-NSSAI(s) triggering the access attempt (TS 23.501[ System architecture for the 5G System (5GS) ] [32] and TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [23]): 2> apply the NSAG with highest NSAG priority among the NSAGs that are included in SIB1 (i.e., in FeatureCombination and/or in RA-PrioritizationSliceInfo), and that are associated with the S-NSSAI(s) triggering the access attempt, in the Random Access procedure (TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3], clause 5.1); NOTE: If there are multiple NSAGs with the same highest NAS-provided NSAG priority identified for access attempt as above, it is left to UE implementation to select the NSAG to be applied in the Random Access procedure. 1> if the UE is acting as L2 U2N Remote UE: 2> establish a SRAP entity as specified in TS 38.351[ NR; Sidelink Relay Adaptation Protocol (SRAP) Specification ] [66], if no SRAP entity has been established; 2> apply the specified configuration of SL-RLC0 as specified in 9.1.1.4; 2> apply the SDAP configuration and PDCP configuration as specified in 9.1.1.2 for SRB0; 1> else: 2> apply the default L1 parameter values as specified in corresponding physical layer specifications except for the parameters for which values are provided in SIB1; 2> apply the default MAC Cell Group configuration as specified in 9.2.2; 2> apply the CCCH configuration as specified in 9.1.1.2; 2> apply the timeAlignmentTimerCommon included in SIB1; 1> start timer T300; 1> initiate transmission of the RRCSetupRequest message in accordance with 5.3.3.3; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.3.2 |
3,240 | 8.23.3 Mobile IAB-DU migration procedure | To support the mobile IAB-DU migration procedure, the mobile IAB-node concurrently supports two logical mobile IAB-DUs, which have F1 connections set up with the source F1-terminating IAB-donor-CU and target F1-terminating IAB-donor-CU, respectively. The mobile IAB-MT’s IAB-donor-CU may be same as either the source F1-termainting IAB-donor CU or the target F1-terminating IAB-donor-CU, or it may be different from both source and target F1-terminating IAB-donor-CUs. The UE(s) connected to the mobile IAB-node are handed over from the cell(s) of the source logical mobile IAB-DU that have F1 set up with the source F1-terminating IAB-donor-CU to the cell(s) of the target logical mobile IAB-DU that have F1 set up with the target F1-terminating IAB-donor-CU. After the UE(s) are handed over, the F1 between the source logical mobile IAB-DU’s and the source F1-terminating IAB-donor-CU may be removed. Figure 8.23.3-1 shows an example of the mobile IAB-DU migration procedure. In this example, the source and the target F1-terminating IAB-donor-CUs are different from the RRC-terminating IAB-donor-CU. Figure 8.23.3-1: Mobile IAB-DU inter-CU migration procedure 1. The source F1-terminating IAB-donor-CU may send an MIAB F1 SETUP TRIGGERING message to the source logical mobile IAB-DU to initialize the F1 Setup procedure towards the target F1-terminating IAB-donor-CU. The MIAB F1 SETUP TRIGGERING message includes the gNB ID of the target F1-terminating IAB-donor-CU and the information needed to establish the TNL connection with the target F1-terminating IAB-donor-CU for F1-C. NOTE: The mobile IAB-DU migration can also be triggered by the OAM. In this case, the OAM provides the mobile IAB-node with all information to initiate the F1 Setup procedure towards the target F1-terminating IAB-donor-CU, and step 1 is omitted. 2. The target logical mobile IAB-DU initiates TNL establishment and F1 setup (as defined in clause 8.5) with the target F1-terminating IAB-donor-CU. During the F1 Setup procedure, the target logical mobile IAB-DU includes the gNB ID of the RRC-terminating IAB-donor-CU, and the BAP address of the co-located mobile IAB-MT in the F1 SETUP REQUEST message. 3. The target F1-terminating IAB-donor-CU responds to the target logical mobile IAB-DU with an F1 SETUP RESPONSE message. After F1 setup with the target F1-terminating IAB-donor-CU, the target logical mobile IAB-DU can serve UEs via the target mobile IAB-DU’s activated cell(s). 4. By sending the MIAB F1 SETUP OUTCOME NOTIFICATION message, the source logical mobile IAB-DU informs the source F1-terminating IAB-donor-CU about the outcome of the F1 interface setup between the co-located target logical mobile IAB-DU and the target F1-terminating IAB-donor-CU. The source logical mobile IAB-DU may provide the source F1-terminating IAB-donor-CU with a mapping between activated cells of the source logical mobile IAB-DU and activated cells of the target logical mobile IAB-DU. If the mobile IAB-DU migration is triggered by the OAM, the gNB-ID of the target F1-terminating IAB-donor-CU is included in this message. 5. The source F1-terminating IAB-donor-CU hands over the UE from a source cell served by the source logical mobile IAB-DU to a target cell served by the target logical mobile IAB-DU. The target F1-terminating IAB-donor-CU initiates the IAB Transport Migration Management procedure towards the RRC-terminating IAB-donor-CU for offloading the UE’s traffic during this step. In case the IAB Transport Migration Management procedure is the first procedure for the mobile IAB-MT, it includes the mobile IAB-MT’s BAP address in the IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message. After the completion of the UE handover, the source F1-terminating IAB-donor-CU requests the release of the UE’s traffic offloaded to the RRC-terminating IAB-donor-CU by initiating IAB Transport Migration Management procedure. NOTE 1: In step 5, the sequence of procedures for UE Handover and the IAB Transport Migration Management procedure initiated by the target F1-terminating IAB-donor-CU is up to implementation. NOTE 2: It is up to RRC-terminating IAB-donor-CU’s implementation to set up new backhaul resources or reuse the existing backhaul resources for the UE’s traffic. NOTE 3: How to perform the IAB Transport Migration Management/Modification procedures, and the IAB Resource Coordination procedure between the target F1-terminating IAB-donor-CU and the RRC-terminating IAB-donor-CU without Xn interface is up to implementation. 6. After all the UEs are handed over, the source F1-terminating IAB-donor-CU may initiate the removal of the F1 interface towards the source logical mobile IAB-DU. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.23.3 |
3,241 | 9.7.1.2 TDD | The following requirements apply to UE DL Category 0. For the parameters specified in Table 9.7.1.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.16 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.7.1.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.7.1.2 |
3,242 | 5.3.1 DL Assignment reception | Downlink assignments transmitted on the PDCCH indicate if there is a transmission on a DL-SCH for a particular MAC entity and provide the relevant HARQ information. When the MAC entity has a C-RNTI, Semi-Persistent Scheduling C-RNTI, PUR-RNTI or Temporary C-RNTI, the MAC entity shall for each TTI during which it monitors PDCCH and for each Serving Cell: - if a downlink assignment for this TTI and this Serving Cell has been received on the PDCCH for the MAC entity's C-RNTI, PUR-RNTI, or Temporary C-RNTI: - if this is the first downlink assignment for this Temporary C-RNTI; or - if this is the first downlink assignment corresponding to uplink transmission using previous preconfigured uplink grant for this PUR-RNTI: - consider the NDI to have been toggled. - if the downlink assignment is for the MAC entity's C-RNTI and if the previous downlink assignment indicated to the HARQ entity of the same HARQ process was either a downlink assignment received for the MAC entity's Semi-Persistent Scheduling C-RNTI or a configured downlink assignment: - consider the NDI to have been toggled regardless of the value of the NDI. - indicate the presence of a downlink assignment and deliver the associated HARQ information to the HARQ entity for this TTI. - else, if a downlink assignment for this TTI has been received for this Serving Cell on the PDCCH for the MAC entity's Semi-Persistent Scheduling C-RNTI: - if the NDI in the received HARQ information is 1: - consider the NDI not to have been toggled; - indicate the presence of a downlink assignment and deliver the associated HARQ information to the HARQ entity for this TTI. - else, if the NDI in the received HARQ information is 0: - if PDCCH contents indicate SPS release: - clear the configured downlink assignment (if any); - if the timeAlignmentTimer, associated with the TAG containing the serving cell on which the acknowledgement for the downlink SPS release is to be transmitted, is running: - indicate a positive acknowledgement for the downlink SPS release to the physical layer. - else: - store the downlink assignment and the associated HARQ information as configured downlink assignment; - initialise (if not active) or re-initialise (if already active) the configured downlink assignment to start in this TTI, or in TTI according to N=0 in clause 5.10.1 for short TTI, and to recur according to rules in clause 5.10.1; - set the HARQ Process ID to the HARQ Process ID associated with this TTI; - consider the NDI bit to have been toggled; - indicate the presence of a configured downlink assignment and deliver the stored HARQ information to the HARQ entity for this TTI. - else, if a downlink assignment for this TTI has been configured for this Serving Cell and there is no measurement gap in this TTI and there is no Sidelink Discovery Gap for Reception in this TTI; and - if this TTI is not an MBSFN subframe or the MAC entity is configured with transmission mode tm9 or tm10: - instruct the physical layer to receive, in this TTI, transport block on the DL-SCH according to the configured downlink assignment and to deliver it to the HARQ entity; - set the HARQ Process ID to the HARQ Process ID associated with this TTI; - consider the NDI bit to have been toggled; - indicate the presence of a configured downlink assignment and deliver the stored HARQ information to the HARQ entity for this TTI. - if the MAC entity is configured with rach-Skip or rach-SkipSCG and a UE Contention Resolution Identity MAC control element for this TTI has been received on the PDSCH indicated by the PDCCH of the SpCell addressed to the C-RNTI: - indicate to upper layer the successful reception of a PDCCH transmission addressed to the C-RNTI. For configured downlink assignments, the HARQ Process ID associated with this TTI is derived from the following equation: - if the TTI is a subframe TTI: - HARQ Process ID = [floor(CURRENT_TTI/semiPersistSchedIntervalDL)] modulo numberOfConfSPS-Processes, where CURRENT_TTI=[(SFN * 10) + subframe number]. - else: - HARQ Process ID = [floor(CURRENT_TTI/semiPersistSchedIntervalDL-sTTI)] modulo numberOfConfSPS-Processes-sTTI, where CURRENT_TTI = [(SFN * 10 * sTTI_Number_Per_Subframe) + subframe number * sTTI_Number_Per_Subframe + sTTI_number]. Refer to 5.10.1 for sTTI_Number_Per_Subframe and sTTI_number. For BL UEs or UEs in enhanced coverage, CURRENT_TTI refers to the TTI where first transmission of repetition bundle takes place. When the MAC entity needs to read BCCH or BR-BCCH, the MAC entity may, based on the scheduling information from RRC: - if the UE is a BL UE or a UE in enhanced coverage: - the redundancy version of the received downlink assignment for this TTI is determined by RVK = ceiling(3/2*k) modulo 4, where k depends on the type of system information message. - for SystemInformationBlockType1-BR - if number of repetitions for PDSCH carrying SystemInformationBlockType1-BR is 4, k = floor(SFN/2) modulo 4, where SFN is the system frame number. - else if number of repetitions for PDSCH carrying SystemInformationBlockType1-BR is 8, k = SFN modulo 4, where SFN is the system frame number. - else if number of repetitions for PDSCH carrying SystemInformationBlockType1-BR is 16, k = (SFN*10+i) modulo 4, where SFN is the system frame number, and i denotes the subframe within the SFN. NOTE: the set of subframes for SystemInformationBlockType1-BR when number of repetitions for PDSCH is 16 are given by Table 6.4.1-2 in TS 36.211[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation ] [7]. - for SystemInformation-BR messages, k=i modulo 4, i =0,1,…, nsw–1, where i denotes the subframe number within the SI window nsw; - indicate a downlink assignment and redundancy version for the dedicated broadcast HARQ process to the HARQ entity for this TTI. - else if a downlink assignment for this TTI has been received on the PDCCH for the SI-RNTI, except for NB-IoT; - if the redundancy version is not defined in the PDCCH format: - the redundancy version of the received downlink assignment for this TTI is determined by RVK = ceiling(3/2*k) modulo 4, where k depends on the type of system information message: for SystemInformationBlockType1 message, k = (SFN/2) modulo 4, where SFN is the system frame number; for SystemInformation messages, k=i modulo 4, i =0,1,…, nsw–1, where i denotes the subframe number within the SI window nsw; - indicate a downlink assignment and redundancy version for the dedicated broadcast HARQ process to the HARQ entity for this TTI. When the MAC entity has SC-RNTI and/or G-RNTI, the MAC entity shall for each TTI during which it monitors PDCCH for SC-RNTI as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8] for UEs other than NB-IoT UEs, BL UEs or UEs in enhanced coverage and in clause 5.7a for NB-IoT UEs, BL UEs or UEs in enhanced coverage and for G-RNTI as specified in clause 5.7a and for each Serving Cell and cell that may be additionally configured as a Serving Cell according to the UE capabilities: - if a downlink assignment for this TTI and this Serving Cell has been received on the PDCCH for the MAC entity's SC-RNTI or G-RNTI: - attempt to decode the received data. - if the data which the MAC entity attempted to decode was successfully decoded for this TB: - deliver the decoded MAC PDU to the disassembly and demultiplexing entity. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.3.1 |
3,243 | – UplinkTxDirectCurrentList | The IE UplinkTxDirectCurrentList indicates the Tx Direct Current locations per serving cell for each configured UL BWP in the serving cell, based on the BWP numerology and the associated carrier bandwidth. UplinkTxDirectCurrentList information element -- ASN1START -- TAG-UPLINKTXDIRECTCURRENTLIST-START UplinkTxDirectCurrentList ::= SEQUENCE (SIZE (1..maxNrofServingCells)) OF UplinkTxDirectCurrentCell UplinkTxDirectCurrentCell ::= SEQUENCE { servCellIndex ServCellIndex, uplinkDirectCurrentBWP SEQUENCE (SIZE (1..maxNrofBWPs)) OF UplinkTxDirectCurrentBWP, ..., [[ uplinkDirectCurrentBWP-SUL SEQUENCE (SIZE (1..maxNrofBWPs)) OF UplinkTxDirectCurrentBWP OPTIONAL ]] } UplinkTxDirectCurrentBWP ::= SEQUENCE { bwp-Id BWP-Id, shift7dot5kHz BOOLEAN, txDirectCurrentLocation INTEGER (0..3301) } -- TAG-UPLINKTXDIRECTCURRENTLIST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,244 | 4.6.2.8 Mobility management for optimised handling of temporarily available network slices | The UE and the network may support optimised handling of temporarily available network slices. The support for S-NSSAI time validity information by the UE and the network, respectively, is optional. If the UE has indicated that it supports S-NSSAI time validity information, then the AMF may include the S-NSSAI time validity information for one or more S-NSSAIs included in the configured NSSAI in the Registration Accept message or the CONFIGURATION UPDATE COMMAND message. If the AMF determines that the S-NSSAI time validity information for an S-NSSAI in the configured NSSAI is changed, the AMF may provide the UE with a new S-NSSAI time validity information for that S-NSSAI via the CONFIGURATION UPDATE COMMAND message. If the UE supporting S-NSSAI time validity information, is configured with S-NSSAI time validity information for an S-NSSAI and: a) the S-NSSAI time validity information indicates that the S-NSSAI is available, then the UE may request the S-NSSAI in the requested NSSAI in the Registration Request message; b) the S-NSSAI time validity information indicates that the S-NSSAI is not available, then: i) the UE shall not include the S-NSSAI in the requested NSSAI in the Registration Request message; ii) the UE shall remove the S-NSSAI from the stored allowed NSSAI (if any) and the stored partially allowed NSSAI (if any) in the non-volatile memory in the ME, as specified in annex C; and iii) the S-NSSAI time validity information indicates that the S-NSSAI will not become available again, then the UE shall remove the S-NSSAI from the stored configured NSSAI in the non-volatile memory in the ME, as specified in annex C. When the S-NSSAI time validity information of an S-NSSAI indicates that the S-NSSAI is not available, then: a) if the AMF receives a requested NSSAI in the REGISTRATION REQUEST message with the S-NSSAI identifying the network slice, the AMF shall: i) to a UE which has indicated that it supports S-NSSAI time validity information, provide: 1) a configured NSSAI including the S-NSSAI together with the S-NSSAI time validity information in the Registration Accept message if the S-NSSAI will become available again; or 2) a configured NSSAI not including the S-NSSAI in the Registration Accept message if the S-NSSAI will not become available again; or ii) to a UE which has not indicated that it supports S-NSSAI time validity information, reject the S-NSSAI for the current PLMN or SNPN. If the registration request is accepted, the AMF shall include a configured NSSAI not including the S-NSSAI; b) if the AMF detects that the S-NSSAI is included in the allowed NSSAI or the partially allowed NSSAI of a UE which has: i) indicated that it supports S-NSSAI time validity information, the AMF shall locally remove the S-NSSAI from the allowed NSSAI (if any) and the partially allowed NSSAI (if any); or ii) not indicated that it supports S-NSSAI time validity information, the AMF shall remove the S-NSSAI from the stored configured NSSAI (if any), allowed NSSAI (if any), and partially allowed NSSAI (if any) by sending the CONFIGURATION UPDATE COMMAND message. When the S-NSSAI time validity information of an S-NSSAI indicates that the S-NSSAI becomes available again, the AMF shall update the configured NSSAI including the S-NSSAI to a UE which has not indicated that it supports S-NSSAI time validity information by sending CONFIGURATION UPDATE COMMAND message if the UE is subscribed to the S-NSSAI. The S-NSSAI time validity information is applicable for the current PLMN or SNPN regardless of the access type. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.6.2.8 |
3,245 | 16.12.2.1 L2 UE-to-Network Relay | The protocol stacks for the user plane and control plane of L2 U2N Relay architecture are illustrated in Figure 16.12.2.1-1 and Figure 16.12.2.1-2. The SRAP sublayer is placed above the RLC sublayer for both CP and UP at both PC5 interface and Uu interface. The Uu SDAP, PDCP and RRC are terminated between L2 U2N Remote UE and gNB, while SRAP, RLC, MAC and PHY are terminated in each hop (i.e., the link between L2 U2N Remote UE and the L2 U2N Relay UE and the link between L2 U2N Relay UE and the gNB). For L2 U2N Relay, the SRAP sublayer over PC5 hop is only for the purpose of bearer mapping. The SRAP sublayer is not present over PC5 hop for relaying the L2 U2N Remote UE's message on BCCH and PCCH. For L2 U2N Remote UE's message on SRB0, the SRAP header is not present over PC5 hop, but the SRAP header is present over Uu hop for both DL and UL. Figure 16.12.2.1-1: User plane protocol stack for L2 UE-to-Network Relay Figure 16.12.2.1-2: Control plane protocol stack for L2 UE-to-Network Relay For L2 U2N Relay, for uplink: - The Uu SRAP sublayer performs UL bearer mapping between end-to-end Uu Radio Bearers of L2 U2N remote UE (identified for the purposes of this mapping by the local Remote UE ID and an associated bearer ID) and egress Uu Relay RLC channels over the L2 U2N Relay UE Uu interface. For uplink relaying traffic, the different end-to-end Uu Radio Bearers (SRBs or DRBs) of the same L2 U2N Remote UE and/or different L2 U2N Remote UEs can be multiplexed over the same egress Uu Relay RLC channel; - The Uu SRAP sublayer supports L2 U2N Remote UE identification for the UL traffic. The identity information of L2 U2N Remote UE end-to-end Uu Radio Bearer and a local Remote UE ID are included in the Uu SRAP header at UL in order for gNB to correlate the received packets for the specific PDCP entity associated with the right end-to-end Uu Radio Bearer of the L2 U2N Remote UE; - The PC5 SRAP sublayer at the L2 U2N Remote UE supports UL bearer mapping between L2 U2N Remote UE end-to-end Uu Radio Bearers and egress PC5 Relay RLC channels. For L2 U2N Relay, for downlink: - The Uu SRAP sublayer performs DL bearer mapping at gNB to map end-to-end Uu Radio Bearer (SRB, DRB) of L2 U2N Remote UE (identified for the purposes of this mapping by the local Remote UE ID and an associated bearer ID) into Uu Relay RLC channel. The Uu SRAP sublayer performs DL bearer mapping and data multiplexing between multiple end-to-end Radio Bearers (SRBs or DRBs) of a L2 U2N Remote UE and/or different L2 U2N Remote UEs and one Uu Relay RLC channel over the L2 U2N Relay UE Uu interface; - The Uu SRAP sublayer supports L2 U2N Remote UE identification for DL traffic. The identity information of L2 U2N Remote UE end-to-end Uu Radio Bearer and a local Remote UE ID are included into the Uu SRAP header by the gNB at DL for the L2 U2N Relay UE to identify the corresponding end-to-end Uu Radio Bearer(s) of L2 U2N Remote UE; - The PC5 SRAP sublayer at the L2 U2N Relay UE performs DL bearer mapping between end-to-end Uu Radio Bearers of L2 U2N remote UE and egress PC5 Relay RLC channels; - The PC5 SRAP sublayer at the L2 U2N Remote UE correlates the received packets with the right PDCP entity associated with the given end-to-end Uu Radio Bearer of the L2 U2N Remote UE based on the identity information included in the PC5 SRAP header. A local Remote UE ID is included in both PC5 SRAP header and Uu SRAP header. L2 U2N Relay UE is configured by the gNB with the local Remote UE ID(s) to be used in SRAP header. L2 U2N Remote UE obtains the local Remote ID from the gNB via Uu RRC messages including RRCSetup, RRCReconfiguration, RRCResume and RRCReestablishment. The end-to-end DRB(s) or end-to-end SRB(s), except SRB0, of L2 U2N Remote UE can be multiplexed to the PC5 Relay RLC channels and Uu Relay RLC channels in both PC5 hop and Uu hop, but an end-to-end DRB and an end-to-end SRB can neither be mapped into the same PC5 Relay RLC channel nor be mapped into the same Uu Relay RLC channel. It is the gNB responsibility to avoid collision on the usage of local Remote UE ID. The gNB can update the local Remote UE ID by sending the updated local Remote UE ID via RRCReconfiguration message. The serving gNB can perform local Remote UE ID update independent of the PC5 unicast link L2 ID update procedure. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.12.2.1 |
3,246 | 9.11.3.96 Extended LADN information | The purpose of the Extended LADN information information element is to provide the UE with the LADN service area for each available LADN associated for an LADN DNN and an S-NSSAI in the current registration area or to delete the Extended LADN information at the UE. The Extended LADN information information element is coded as shown in figure 9.11.3.96.1, figure 9.11.3.96.2 and table 9.11.3.96.1. The Extended LADN information is a type 6 information element with a minimum length of 3 octets and a maximum length of 1787 octets. The Extended LADN information information element can contain a minimum of 0 and a maximum of 8 different LADNs each including a DNN, an S-NSSAI and a 5GS tracking area identity list. Figure 9.11.3.96.1: Extended LADN information information element Figure 9.11.3.96.2: LADN Table 9.11.3.96.1: Extended LADN information 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.96 |
3,247 | 5.14.2.1 Addressing | All the Configuration Transfer messages contain the addresses of the source and destination RAN nodes. An eNodeB is addressed by the Target eNodeB Identifier. For Dual Connectivity with E-UTRAN as Master RAN node and NR as Secondary RAN node as defined in TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [85], the destination RAN node includes the candidate en-gNB Identifier and may include a target eNodeB Identifier for the target eNodeB which is X2 connected to the candidate en-gNB and a TAI associated with the en-gNB. | 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.14.2.1 |
3,248 | 17.5.5 De-registration procedure (GGSN initiated) | The MBMS de-registration is the procedure by which the GGSN informs the BM-SC that it does not need to receive signalling, session attributes and data for a particular multicast MBMS bearer service anymore and therefore would like to be removed from the corresponding distribution tree. Figure 30: MBMS De-Registration procedure 1. When the "list of downstream nodes" of a particular MBMS Bearer Context in the GGSN becomes empty and the GGSN has no MBMS UE Contexts linked to that MBMS Bearer Context, the GGSN sends a STR message to the BM-SC. If a bearer plane had been established over Gi for this MBMS bearer service, the bearer plane is released. 2. The BM-SC removes the identifier of the GGSN from the "list of downstream nodes" parameter of the affected MBMS Bearer Context and confirms the operation by sending a STA message to the GGSN. | 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.5 |
3,249 | 8.9.7 Trace activation/deactivation over F1 and E1 | Figure 8.9.6-1 shows the procedure used for the activation and the deactivation of UE traces in the gNB-DU, the gNB-CU-UP or both. Figure 8.9.6-1: Trace activation/deactivation over F1 and E1 1. The gNB-CU-CP receives a TRACE START message from the AMF or the MeNB (in case of EN-DC). 2. The gNB-CU-CP initiates the Trace Start procedure by sending a TRACE START message to the gNB-DU, the gNB-CU-UP or both. 3. Upon reception of the TRACE START message, the gNB-DU, the gNB-CU-UP or both initiate the requested trace session and report it as described in TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ] [20]. 4. The gNB-CU-CP receives a DEACTIVATE TRACE message from the AMF or the MeNB (in case of EN-DC). 5. The gNB-CU-CP initiates the Deactivate Trace procedure by sending a DEACTIVATE TRACE message to the gNB-DU, the gNB-CU-UP or both. 6. Upon reception of the DEACTIVATE TRACE message, the gNB-DU, the gNB-CU-UP or both stop the trace session for the indicated trace reference. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.9.7 |
3,250 | 10.3 Timers of EPS session management | Table 10.3.1: EPS session management timers – UE side NOTE 1: The back-off timer is used to describe a logical model of the required UE behaviour. This model does not imply any specific implementation, e.g. as a timer or timestamp. NOTE 2: Reference to back-off timer in this section can either refer to use of timer T3396 or to use of a different packet system specific timer within the UE. Whether the UE uses T3396 as a back-off timer or it uses different packet system specific timers as back-off timers is left up to UE implementation. Table 10.3.2: EPS session management timers – network side | 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 | 10.3 |
3,251 | 8.2.1.3.1 Minimum Requirement 2 Tx Antenna Port | For single carrier, the requirements are specified in Table 8.2.1.3.1-2, with the addition of the parameters in Table 8.2.1.3.1-1 and the downlink physical channel setup according to Annex C.3.2. For CA with 2 DL CC, the requirements are specified in Table 8.2.1.3.1-4, with the addition of the parameters in Table 8.2.1.3.1-3 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of large delay CDD with 2 transmitter antennas. For CA with 3 DL CCs, the requirements are specified in Table 8.2.1.3.1-6, based on single carrier requirement specified in Table 8.2.1.3.1-5, with the addition of the parameters in Table 8.2.1.3.1-3 and the downlink physical channel setup according to Annex C.3.2. For CA with 4 DL CCs, the requirements are specified in Table 8.2.1.3.1-7, based on single carrier requirement specified in Table 8.2.1.3.1-5, with the addition of the parameters in Table 8.2.1.3.1-3 and the downlink physical channel setup according to Annex C.3.2. For CA with 5 DL CCs, the requirements are specified in Table 8.2.1.3.1-8, based on single carrier requirement specified in Table 8.2.1.3.1-5, with the addition of the parameters in Table 8.2.1.3.1-3 and the downlink physical channel setup according to Annex C.3.2. For CA with 6 DL CCs, the requirements are specified in Table 8.2.1.3.1-9, based on single carrier requirement specified in Table 8.2.1.3.1-5, with the addition of the parameters in Table 8.2.1.3.1-3 and the downlink physical channel setup according to Annex C.3.2. For CA with 7 DL CCs, the requirements are specified in Table 8.2.1.3.1-10, based on single carrier requirement specified in Table 8.2.1.3.1-5, with the addition of the parameters in Table 8.2.1.3.1-3 and the downlink physical channel setup according to Annex C.3.2. The test coverage for different number of component carriers is defined in 8.1.2.4. Table 8.2.1.3.1-1: Test Parameters for Large Delay CDD (FRC) Table 8.2.1.3.1-2: Minimum performance Large Delay CDD (FRC) Table 8.2.1.3.1-3: Test Parameters for Large Delay CDD (FRC) for CA Table 8.2.1.3.1-4: Minimum performance Large Delay CDD (FRC) for CA with 2DL CCs Table 8.2.1.3.1-5: Single carrier performance for multiple CA configurations Table 8.2.1.3.1-6: Minimum performance (FRC) based on single carrier performance for CA with 3 DL CCs Table 8.2.1.3.1-7: Minimum performance (FRC) based on single carrier performance for CA with 4 DL CCs Table 8.2.1.3.1-8: Minimum performance (FRC) based on single carrier performance for CA with 5 DL CCs Table 8.2.1.3.1-9: Minimum performance (FRC) based on single carrier performance for CA with 6 DL CCs Table 8.2.1.3.1-10: Minimum performance (FRC) based on single carrier performance for CA with 7 DL CCs | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.1.3.1 |
3,252 | 13.3.0 Static authorization | Static authorization is based on local authorization policy at the NRF and the NF Service Producer. It can be used when token-based authorization is not used. During the Nnrf_NFDiscovery procedure, the NRF ensures that the NF Service Consumer is authorized to discover the NF Service Producer service(s) as specified in clause 13.3.1.3 of this document. If token-based authorization is not used within one PLMN and the NF Service Producer receives a service request, the NF Service Producer shall check authorization of the NF Service Consumer based on its local policy. If the NF Service Consumer is authorized to receive the service requested, the NF Service Producer shall grant the NF Service Consumer access to the service API. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.3.0 |
3,253 | 10.5.4.28 Stream Identifier | The purpose of the stream identifier (SI) information element is to associate a particular call with a Radio Access Bearer (RAB), and to identify whether a new traffic channel shall be assigned within the interface controlled by these signalling procedures. The SI value indicated in the CC protocol shall be sent in the RAB setup message. And mobile station is informed the relationship between the call and the RAB. The Stream identifier information element is coded as shown in figure 10.5.117/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.134/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Stream Identifier is a type 4 information element with 3 octets length. Figure 10.5.117/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Stream Identifier information element Table 10.5.134/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Stream Identifier 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.28 |
3,254 | A.3.6 Fields with conditional presence | A field with conditional presence is declared with the keyword OPTIONAL. In addition, a short comment text shall be included at the end of the paragraph including the keyword OPTIONAL. The comment text includes the keyword "Cond", followed by a condition tag associated with the field ("UL" in this example): -- /example/ ASN1START LogicalChannelConfig ::= SEQUENCE { ul-SpecificParameters SEQUENCE { priority INTEGER (0), ... } OPTIONAL -- Cond UL } -- ASN1STOP When conditionally present fields are included in an ASN.1 clause, the field description table after the ASN.1 clause shall be followed by a conditional presence table. The conditional presence table specifies the conditions for including the fields with conditional presence in the particular ASN.1 clause. The conditional presence table has two columns. The first column (heading: "Conditional presence") contains the condition tag (in italic font style), which links the fields with a condition tag in the ASN.1 clause to an entry in the table. The second column (heading: "Explanation") contains a text specification of the conditions and requirements for the presence of the field. The second column may also include semantics, in case of an optional presence of the field, under certain conditions i.e. using the same predefined tags as defined for optional fields in A.3.5. Conditional presence should primarily be used when presence of a field depends on the presence and/or value of other fields within the same message. If the presence of a field depends on whether another feature/function has been configured, while this function can be configured independently e.g. by another message and/or at another point in time, the relation is best reflected by means of a statement in the field description table. If the ASN.1 clause does not include any fields with conditional presence, the conditional presence table shall not be included. Whenever a field is only applicable in specific cases e.g. TDD, use of conditional presence should be considered. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | A.3.6 |
3,255 | 19.5 Mz specific Experimental-Result-Code AVP values | There are two different types of errors in Diameter; protocol and application errors. A protocol error is one that occurs at the base protocol level, those are covered in the Diameter Base IETF RFC 6733 [111] specific procedures. Application errors, on the other hand, generally occur due to a problem with a function specified in a Diameter application. Diameter Base IETF RFC 6733 [111] defines a number of Result-Code AVP values that are used to report protocol errors and how those are used. Those procedures and values apply for the present specification. Note that according to IETF RFC 6733 [111], the Diameter node reports only the first error encountered and only one Result-Code AVP or one Experimental-Result AVP is included in the Diameter answer. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 19.5 |
3,256 | – CellReselectionPriority | The IE CellReselectionPriority concerns the absolute priority of the concerned carrier frequency, as used by the cell reselection procedure. Corresponds to parameter "priority" in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]. Value 0 means lowest priority. The UE behaviour for the case the field is absent, if applicable, is specified in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]. CellReselectionPriority information element -- ASN1START -- TAG-CELLRESELECTIONPRIORITY-START CellReselectionPriority ::= INTEGER (0..7) -- TAG-CELLRESELECTIONPRIORITY-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,257 | – HandoverCommand | This message is used to transfer the handover command as generated by the target gNB. Direction: target gNB to source gNB/source RAN. HandoverCommand message -- ASN1START -- TAG-HANDOVER-COMMAND-START HandoverCommand ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE{ handoverCommand HandoverCommand-IEs, spare3 NULL, spare2 NULL, spare1 NULL }, criticalExtensionsFuture SEQUENCE {} } } HandoverCommand-IEs ::= SEQUENCE { handoverCommandMessage OCTET STRING (CONTAINING RRCReconfiguration), nonCriticalExtension HandoverCommand-v1800-IEs OPTIONAL } HandoverCommand-v1800-IEs ::= SEQUENCE { candPSCellExecutionConditionInfo-r18 CandPSCellExecutionConditionInfo-r18 OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } CandPSCellExecutionConditionInfo-r18 ::= SEQUENCE { candPSCellExecCondReportConfigNR-r18 ReportConfigNR, ... } -- TAG-HANDOVER-COMMAND-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,258 | 9.11.3.18C Ciphering key data | The purpose of the Ciphering key data information element is to transfer a list of ciphering data sets from the network to the UE for deciphering of ciphered assistance data. The Ciphering key data information element is coded as shown in figure 9.11.3.18C.1, figure 9.11.3.18C.2 and table 9.11.3.18C.1. The Ciphering key data is a type 6 information element, with a minimum length of 34 octets and a maximum length of 2675 octets. The list can contain a maximum of 16 ciphering data sets. Figure 9.11.3.18C.1: Ciphering key data information element Figure 9.11.3.18C.2: Ciphering data set Table 9.11.3.18C.1: Ciphering key data 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.18C |
3,259 | 4.2.7.2.4 NGAP UE-TNLA-binding update procedure | At any time the AMF may decide to re-bind the NGAP UE association to a new TNL association: - by sending a UE-specific NGAP message on a new TNL association (triangular redirection), if: - AMF responds to the 5G-AN node initiated NGAP message (i.e. triangular redirection) as described in clauses 4.2.7.2.1, 4.2.7.2.2 and 4.2.7.2.3; or - AMF initiated UE-specific NGAP message needs to be sent to 5G-AN node; - by sending a UE-specific NGAP UE-TNLA binding release message to 5G-AN and the 5G-AN node updates the NGAP UE-TNLA binding with the new TNL association. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.7.2.4 |
3,260 | 5.5a.3.2 Initiation | While T330 is running and SDT procedure is not ongoing, the UE shall: 1> if measurement logging is suspended: 2> if during the last logging interval the IDC problems detected by the UE is resolved, resume measurement logging; 1> if not suspended, perform the logging in accordance with the following: 2> if the reportType is set to periodical in the VarLogMeasConfig: 3> if the UE is in any cell selection state (as specified in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]): 4> perform the logging at regular time intervals, as defined by the loggingInterval in the VarLogMeasConfig; 3> if the UE is in camped normally state on an NR cell and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport; or 3> if the UE is in camped normally state on an NR cell and if the registered SNPN is included in snpn-ConfigIDList stored in VarLogMeasReport: 4> if areaConfiguration is not included in VarLogMeasConfig; or 4> if the serving cell is part of the area indicated by areaConfig in areaConfiguration in VarLogMeasConfig; or 4> if the serving cell is part of the area indicated by cag-ConfigList in areaConfiguration in VarLogMeasConfig; or 4> if the serving cell is part of the area indicated by snpn-ConfigList in areaConfiguration in VarLogMeasConfig: 5> perform the logging at regular time intervals, as defined by the loggingInterval in the VarLogMeasConfig; 2> else if the reportType is set to eventTriggered, and eventType is set to outOfCoverage: 3> perform the logging at regular time intervals as defined by the loggingInterval in VarLogMeasConfig only when the UE is in any cell selection state; 3> upon transition from any cell selection state to camped normally state in NR: 4> if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport, or if the registered SNPN is included in snpn-ConfigIDList stored in VarLogMeasReport; and 4> if areaConfiguration is not included in VarLogMeasConfig or if the current camping cell is part of the area indicated by areaConfig of areaConfiguration in VarLogMeasConfig, or if the current camping cell is part of the area indicated by cag-ConfigList of areaConfiguration in VarLogMeasConfig, or if the current camping cell is part of the area indicated by snpn-ConfigList of areaConfiguration in VarLogMeasConfig: 5> perform the logging; 2> else if the reportType is set to eventTriggered and eventType is set to eventL1: 3> if the UE is in camped normally state on an NR cell and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport; or 3> if the UE is in camped normally state on an NR cell and if the registered SNPN is included in snpn-ConfigIDList stored in VarLogMeasReport: 4> if areaConfiguration is not included in VarLogMeasConfig; or 4> if the serving cell is part of the area indicated by areaConfig in areaConfiguration in VarLogMeasConfig; or 4> if the current serving cell is part of the area indicated by cag-ConfigList of areaConfiguration in VarLogMeasConfig, or if the current camping cell is part of the area indicated by snpn-ConfigList of areaConfiguration in VarLogMeasConfig; 5> perform the logging at regular time intervals as defined by the loggingInterval in VarLogMeasConfig only when the conditions indicated by the eventL1 are met; 2> when performing the logging: 3> if InterFreqTargetInfo is configured and if the UE detected IDC problems on at least one of the frequencies included in InterFreqTargetInfo or any inter-RAT frequency during the last logging interval, or 3> if InterFreqTargetInfo is not configured and if the UE detected IDC problems during the last logging interval: 4> if measResultServingCell in the VarLogMeasReport is not empty: 5> include inDeviceCoexDetected; 5> suspend measurement logging from the next logging interval; 4> else: 5> suspend measurement logging; 3> set the relativeTimeStamp to indicate the elapsed time since the moment at which the logged measurement configuration was received; 3> if location information became available during the last logging interval, set the content of the locationInfo as in 5.3.3.7: 3> if the UE is in any cell selection state (as specified in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]): 4> set anyCellSelectionDetected to indicate the detection of no suitable or no acceptable cell found; 4> if the reportType is set to eventTriggered in the VarLogMeasConfig; and 4> if the RPLMN at the time of entering the any cell selection state is included in plmn-IdentityList stored in VarLogMeasReport; and 4> if areaConfiguration is not included in VarLogMeasConfig or if the last suitable cell that the UE was camping on is part of the area indicated by areaConfig of areaConfiguration in VarLogMeasConfig, or if last suitable cell that the UE was camping on is part of the area indicated by cag-ConfigList of areaConfiguration in VarLogMeasConfig, or if last suitable cell that the UE was camping on is part of the area indicated by snpn-ConfigList of areaConfiguration in VarLogMeasConfig: 5> set the servCellIdentity to indicate global cell identity of the last suitable cell that the UE was camping on; 5> set the measResultServingCell to include the quantities of the last suitable cell the UE was camping on; 4> else if the reportType is set to periodical in the VarLogMeasConfig: 5> set the servCellIdentity to indicate global cell identity of the last logged cell that the UE was camping on; 5> set the measResultServingCell to include the quantities of the last logged cell the UE was camping on; 3> else: 4> set the servCellIdentity to indicate global cell identity of the cell the UE is camping on; Editor´s note: Including list of equivalent SNPN IDs in MDT report is FFS. 4> set the measResultServingCell to include the quantities of the cell the UE is camping on; 3> if available, set the measResultNeighCells, in order of decreasing ranking-criterion as used for cell re-selection, to include measurements of neighbouring cell that became available during the last logging interval and according to the following: 4> include measurement results for at most 6 neighbouring cells on the NR serving frequency and for at most 3 cells per NR neighbouring frequency and for the NR neighbouring frequencies in accordance with the following: 5> if interFreqTargetInfo is included in VarLogMeasConfig: 6> if earlyMeasIndication is included in VarLogMeasConfig; 7> include measurement results for NR neighbouring frequencies that are included in both interFreqTargetInfo and either in measIdleCarrierListNR (within the VarMeasIdleConfig) or SIB4; 6> else: 7> include measurement results for NR neighbouring frequencies that are included in both interFreqTargetInfo and SIB4; 5> else: 6> if earlyMeasIndication is included in VarLogMeasConfig; 7> include measurement results for NR neighbouring frequencies that are included in either measIdleCarrierListNR (within the VarMeasIdleConfig) or SIB4; 6> else: 7> include measurement results for NR neighbouring frequencies that are included in SIB4; 4> include measurement results for at most 3 neighbours per inter-RAT frequency in accordance with the following: 5> if earlyMeasIndication is included in VarLogMeasConfig: 6> include measurement results for inter-RAT neighbouring frequencies that are included in either measIdleCarrierListEUTRA (within the VarMeasIdleConfig) or SIB5; 5> else: 6> include measurement results for inter-RAT frequencies that are included in SIB5; 4> for each neighbour cell included, include the optional fields that are available; NOTE 1: The UE includes the latest results of the available measurements as used for cell reselection evaluation in RRC_IDLE or RRC_INACTIVE, which are performed in accordance with the performance requirements as specified in TS 38.133[ NR; Requirements for support of radio resource management ] [14]. NOTE 2: For logging the measurements on frequencies (indicated in measIdleCarrierListNR/ measIdleCarrierListEUTRA) in the logged measurement, the qualityThreshold in measIdleConfig should not be applied, and how the UE logs the measurements on the frequencies is left to the UE implementation. 2> when the memory reserved for the logged measurement information becomes full, stop timer T330 and perform the same actions as performed upon expiry of T330, as specified in 5.5a.1.4. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5a.3.2 |
3,261 | 5.2.2.2.2 Namf_Communication_UEContextTransfer service operation | Service operation name: Namf_Communication_UEContextTransfer Description: Provides the UE context to the consumer NF. Input, Required: 5G-GUTI or SUPI, Access Type, Reason. Input, Optional: Integrity protected message from the UE that triggers the context transfer. Output, Required: The UE context of the identified UE or only the SUPI and an indication that the Registration Request has been validated. The UE context is detailed in table 5.2.2.2.2-1. Output, Optional: Mobile Equipment Identifier (if available), Allowed NSSAI, Mapping Of Allowed NSSAI. See clause 4.2.2.2.2 for example of usage of this service operation. If the consumer NF sent an integrity protected message from the UE, the AMF uses it to verify whether this request is permitted to retrieve the UE context of the UE. If it is permitted, the AMF provides UE context to the consumer NF in the Namf_Communication_UEContextTransfer response. The following table illustrates the UE Context: Table 5.2.2.2.2-1: UE Context in AMF | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.2.2.2 |
3,262 | 4.3.4 IMSI detach procedure 4.3.4.0 General | The IMSI detach procedure may be invoked by a mobile station if the mobile station is deactivated or if the Subscriber Identity Module (see 3GPP TS 42.017[ Subscriber Identity Module (SIM); Functional characteristics ] [7] and 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112]) is detached from the mobile station or as part of the eCall inactivity procedure defined in subclause 4.4.7. In A/Gb mode and GERAN Iu mode, the network indicates whether the IMSI detach/attach procedures are required by using the ATT flag which is broadcast in the L3-RR SYSTEM INFORMATION TYPE 3 message on the BCCH (see 3GPP TS 44.018[ None ] [84] subclause 10.5.2.11). The mobile station shall use the value of the ATT flag that was broadcast when the mobile station was in the MM IDLE state. In UTRAN Iu mode, the network indicates whether the IMSI detach/attach procedures are required by using the ATT flag which is included in the CS domain specific system information element (see subclause 10.5.1.12.2). The mobile station shall use the latest received value of the ATT flag. If a RR connection exists and the ATT flag indicates that the IMSI detach/attach procedures are not required, the MM sublayer will release locally any ongoing MM connections before releasing the RR connection. If an MM specific procedure is active, the release of the RR connection may be delayed until the MM specific procedure is complete. The IMSI detach procedure causes the mobile station to be indicated as inactive in the network. The mobile station is allowed to initiate the IMSI detach procedure even if the timer T3246 is running. The network proceeds with the IMSI detach procedure even if NAS level mobility management congestion control is 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 | 4.3.4 |
3,263 | 6.3.2.2 Multiple registrations in the same PLMN | When the UE is registered in the same AMF in the same PLMN serving network over both 3GPP and non-3GPP accesses, the UE shall establish two NAS connections with the network. Upon receiving the registration request message, the AMF should check whether the UE is authenticated by the network. The AMF may decide to skip a new authentication run in case there is an available 5G security context for this UE by means of 5G-GUTI, e.g. when the UE successfully registered to 3GPP access. If the UE registers to the same AMF via non-3GPP access, the AMF can decide not to run a new authentication if it has an available security context to use. In this case, the UE shall directly take into use the available common 5G NAS security context and use it to protect the registration over the non-3GPP access. If there are stored NAS counts for the non-3GPP access for the PLMN in the UE, then the stored NAS counts for the non-3GPP access for the PLMN shall be used to protect the registration over the non-3GPP access. Otherwise, the common 5G NAS security context is taken into use for the first time (partial) over non-3GPP access. In this case, the UL NAS COUNT value and DL NAS COUNT value for the non-3GPP access needs to be set to zero by the UE before the UE is taking the 5G NAS security context into use over non 3GPP access. The AMF and the UE shall establish a common NAS security context consisting of a single set of NAS keys and algorithm at the time of first registration over any access. The AMF and the UE shall also store parameters specific to each NAS connection in the common NAS security context including two pairs of NAS COUNTs for each access (i.e. 3GPP access and non-3GPP access). The connection specific parameters are specified in clause 6.4.2.2 of the present document. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.3.2.2 |
3,264 | 5.3.5.2 Initiation | The Network may initiate the RRC reconfiguration procedure to a UE in RRC_CONNECTED. The Network applies the procedure as follows: - the establishment of RBs (other than SRB1, that is established during RRC connection establishment) is performed only when AS security has been activated; - the establishment of BH RLC Channels for IAB is performed only when AS security has been activated; - the configuration of NCR-Fwd is performed only when AS security has been activated; - the establishment of Uu Relay RLC channels and PC5 Relay RLC channels (other than SL-RLC0 and SL-RLC1) for L2 U2N Relay UE is performed only when AS security has been activated, and the establishment of PC5 Relay RLC channels for L2 U2N Remote UE (other than SL-RLC0 and SL-RLC1) is performed only when AS security has been activated; - the establishment of PC5 Relay RLC channels for L2 U2U Relay UE and L2 U2U Remote UE is performed only when AS security has been activated; - the addition of Secondary Cell Group and SCells is performed only when AS security has been activated; - the reconfigurationWithSync is included in secondaryCellGroup only when at least one RLC bearer or BH RLC channel is setup in SCG; - the reconfigurationWithSync is included in masterCellGroup only when AS security has been activated, and SRB2 with at least one DRB or multicast MRB or, for IAB and NCR, SRB2, are setup and not suspended; - the conditionalReconfiguration for CPC is included only when at least one RLC bearer is setup in SCG; - the conditionalReconfiguration for CHO or CPA is included only when AS security has been activated, and SRB2 with at least one DRB or multicast MRB or, for IAB, SRB2, are setup and not suspended; - the addition of indirect path for MP is performed only when AS security has been activated; - the ltm-Config for LTM on the MCG is included only when AS security has been activated, and SRB2 with at least one DRB are setup and not suspended; - the ltm-Config for LTM on the SCG is included only when at least one RLC bearer is setup in SCG. Editor's Note: Coexistance of LTM with other features is addressed during the ASN.1 review or maintainance. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.2 |
3,265 | 4.2.7.2.1 Creating NGAP UE-TNLA-bindings during Registration and Service Request | When a UE connects to the 5GC via a 5G-AN node without providing any UE identities (i.e. a GUAMI or a 5G-S-TMSI), or the UE provides a GUAMI or a 5G-S-TMSI but the 5G-AN node cannot associate to any of its connected AMFs, the following steps are performed: 1. The 5G-AN node selects an AMF as defined in clause 6.3.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 2. The 5G-AN node creates an NGAP UE-TNLA-binding for the UE by selecting a TNL association from the available TNL associations permitted for the initial message e.g. N2 INITIAL UE MESSAGE for the selected AMF, as defined in clause 5.21.1.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and forwards the UE message to the AMF via the selected TNL association. 3. The AMF may decide to use the TNL association selected by the 5G-AN or the AMF may modify the NGAP UE-TNLA-binding by triangular redirection. NOTE 1: This process could take place during the Registration procedure (for Initial Registration, Mobility Registration Update). 4. The AMF may decide to modify the NGAP UE-TNLA-binding toward other 5G-AN nodes such as N3IWF. This is done if the AMF is changed and old AMF have existing NGAP UE-TNLA-bindings toward other 5G-AN nodes. When a UE connects to the 5GC via a 5G-AN node with a 5G-S-TMSI or GUAMI associated with the AMF usable by the 5G-AN node, the following steps are performed: 1. The 5G-AN node creates an NGAP UE-TNLA-binding for the UE by selecting a TNL association from the available TNL associations permitted for the initial N2 message for the AMF identified by the UE's 5G-S-TMSI or GUAMI. 2. The AMF may decide to use the TNL association selected by the 5G-AN or the AMF may modify the NGAP UE-TNLA-binding by triangular redirection. NOTE 2: This process could take place during the Registration procedure or Service Request procedure. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.7.2.1 |
3,266 | 9.11.1 Minimum requirement (with eMIMO-Type configured as Class B with more than one CSI-RS resource configured and eMIMO-Type2 as Class B with one CSI-RS resource configured) | The purpose of this test is to verify that the reported CRI(1) from eMIMO-Type and PMI(2) from eMIMO-Type2 are accurate. The accuracy of CRI and PMI reporting are determined by the ratio of the throughput obtained when transmitting based on UE reported CRI(1) and PMI(2) compared to that obtained when transmitting based on the random precoding and fixed CRI: - is [70%] of the maximum throughput obtained at using following precoder according to UE reported PMI(2) for eMIMO-Type2 and power scaling factor according to UE reported CRI (1) for eMIMO-Type - is throughput obtained at using random precoder and power scaling factor according to the one configured CSI-RS resource - is specified based on CRS RE power | 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.11.1 |
3,267 | 4.2.2.2 Service State, ATTEMPTING TO UPDATE | When in state MM IDLE and service state ATTEMPTING TO UPDATE the mobile station shall: - perform location updating procedure at expiry of timer T3211, T3213 or T3246; - perform normal location updating when entering a new PLMN, if timer T3246 is running and the new PLMN is not equivalent to the PLMN where the MS started timer T3246; - perform normal location updating when the location area identification of the serving cell changes, if timer T3246 is not running; - if entry into this state was caused by c) or d) or f) (with cause different from "abnormal release, unspecified") or g) (with cause "retry upon entry into a new cell") of subclause 4.4.4.9, then location updating shall be performed when a new cell is entered; - if entry into this state was caused by e) or f) (with cause "abnormal release, unspecified"), g) (with cause different from "retry upon entry into a new cell"), i) or j) of subclause 4.4.4.9, then location updating shall not be performed because a new cell is entered; - perform normal location updating at expiry of timer T3212; - not perform IMSI detach unless timer T3246 is running and the location area of the current cell is same as the stored location area; - support request for emergency calls; - use other request from CM layer as triggering of normal location updating procedure (if the location updating procedure is successful, then the request for MM connection is accepted, see subclause 4.5.1), if timer T3246 is not running; - respond to paging, if the location area of the current cell is same as the stored location area; - respond to paging (with IMSI) ; and - for an eCall only mobile station (as determined by information configured in USIM), perform the eCall inactivity procedure at expiry of timer T3242 or timer T3243. In addition, mobile stations supporting VGCS listening or VBS listening shall: - indicate notifications to the GCC or BCC sublayer for which a channel description has been received in the notification by the RR sublayer; - reject requests of the GCC or BCC sublayer to respond to notifications for which no channel description has been received in the notification by the RR sublayer; - request the RR sublayer to receive a voice group or broadcast call if the GCC or BCC sublayer requests the reception of a voice group or broadcast call for which a channel description has been received in the notification by the RR sublayer and then go to the service state RECEIVING GROUP CALL (LIMITED SERVICE). | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.2.2.2 |
3,268 | 5.5.3.2 'Visitors' from other PLMNs | The CDRs collected from the network also include details of the services employed by visiting (roaming) subscribers. The charges for Mobile Originated Calls (MOCs) and for supplementary services used are calculated as for home subscribers, converted to an agreed accounting currency and included in the CDRs for the TAP. Even if Mobile Terminated Calls (Cs) are zero-priced in the visited network (VPLMN), in the absence of 'optimized routing' the C TAP records are still required by the home network (HPLMN) in order to determine the re-routing charges from the HPLMN to the VPLMN. The TAP records generated are exchanged with each HPLMN on a regular basis. These TAP records form the basis of the invoice submitted by the VPLMN for the traffic carried. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 5.5.3.2 |
3,269 | 16a.6 Gi/Sgi specific Experimental-Result-Code AVP | Diameter Base IETF RFC 6733 [111] defines a number of Result-Code AVP values that are used to report protocol errors and how those are used. Those procedures and values apply for the present specification. Due to the Gi/Sgi specific AVPs, new application results can occur and the Experimental-Result AVP is used to transfer the 3GPP-specific result codes. The Experimental-Result AVP is a grouped AVP containing the Vendor-Id AVP set to the value of 3GPP’s vendor identifier (10415) and an Experimental-Result-Code AVP. The following Gi/Sgi specific Experimental-Result-Code value is defined: DIAMETER_PDP_CONTEXT_DELETION_INDICATION (2021) For GGSN this is an indication to the server that the requested PDP Context or IP-CAN session has been deleted. For P-GW this is an indication to the server that the requested bearer or IP-CAN session has been deleted. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 16a.6 |
3,270 | 5.8.9.10.3 Actions related to transmission of NotificationMessageSidelink message | The Relay UE shall set the indication type as follows: 1> if the UE is acting as U2N Relay UE: 2> if the UE initiates transmission of the NotificationMessageSidelink message due to Uu RLF: 3> set the indicationType as relayUE-Uu-RLF; 2> else if the UE initiates transmission of the NotificationMessageSidelink message due to reconfiguration with sync: 3> set the indicationType as relayUE-HO; 2> else if the UE initiates transmission of the NotificationMessageSidelink message due to cell reselection: 3> set the indicationType as relayUE-CellReselection; 2> if the UE initiates transmission of the NotificationMessageSidelink message due to Uu RRC connection establishment/Resume failure: 3> set the indicationType as relayUE-Uu-RRC-Failure; 2> submit the NotificationMessageSidelink message to lower layers for transmission. 1> if the UE is acting as L2 U2U Relay UE: 2> if the UE initiates transmission of the NotificationMessageSidelink message due to PC5 RLF with L2 U2U Remote UE: 3> set the sl-IndicationType as relayUE-PC5-RLF; 3> set the sl-DestinationIdentityRemoteUE as the associated destination for L2 U2U Remote UE; 3> submit the NotificationMessageSidelink message to lower layers for transmission; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.9.10.3 |
3,271 | 4.3.19 Core Network node resolution 4.3.19.1 General | The indication of mapped or native GUTI shall be signalled by the UE to the MME as an explicit indication in Attach Request and TAU Request messages. The indication of mapped or native P-TMSI/RAI shall be signalled by the UE to the SGSN as an explicit indication in Attach Request and RAU Request messages. The MME/SGSN resolves the old MME/SGSN using old GUTI respective old P-TMSI/RAI sent in the Attach request and TAU/RAU request messages, and determines if the old GUTI or the old P-TMSI/RAI is mapped or native by one of the following two methods: - Indication using most significant bit (MSB) in LAC and MME Group ID. - Explicit indication sent from UE to MME and SGSN. | 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.19 |
3,272 | 5.5.3.1 UE reachability in CM-IDLE | This clause applies to Non-3GPP access network corresponding to the Untrusted Non-3GPP access network, to the Trusted Non-3GPP access network and to the W-5GAN. The UE mentioned in this clause corresponds to 5G-RG, in the case of W-5GAN or to W-AGF in the case of support of FN-RG. In the case of N5CW devices access 5GC via trusted WLAN access networks, the UE mentioned in this clause corresponds to TWIF. An UE cannot be paged over Non-3GPP access network. If the UE states in the AMF are CM-IDLE and RM-REGISTERED for the non-3GPP access, there may be PDU Sessions that were last routed over the non-3GPP access and without user plane resources. If the AMF receives a message with a Non-3GPP Access Type indication from an SMF for a PDU Session corresponding to a UE that is CM-IDLE for non-3GPP access, and the UE is registered over 3GPP access in the same PLMN as the one registered over non-3GPP access, a Network Triggered Service Request may be performed over the 3GPP access independently of whether the UE is CM-IDLE or CM-CONNECTED over the 3GPP access. In this case, the AMF provides an indication that the procedure is related to non-3GPP access, as specified in clause 5.6.8. NOTE: The UE behaviour upon such network triggered Service Request is specified in clause 5.6.8. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.5.3.1 |
3,273 | 7.3.2 Forward Relocation Response | A Forward Relocation Response message shall be sent as a response to Forward Relocation Request during S1-based handover procedure, Inter RAT handover procedures, SRNS Relocation procedure and PS handover procedures, EPS to 5GS handover and 5GS to EPS handover procedures, 5G-SRVCC from NG-RAN to UTRAN procedure. Based on the List of Set-up Bearers IE in the Forward Relocation Response, the source MME/AMF shall determine whether the bearer contexts for SGi (IP, Non-IP or Ethernet) PDN connections were successfully transferred to the target MME/AMF. Based on the List of Set-up Bearers for SCEF PDN Connections IE in the Forward Relocation Response, the source MME shall determine whether the bearer contexts for SCEF PDN connections were successfully transferred to the target MME, and initiate procedures to release the SCEF PDN connections which were not successfully handed over. Table -1 specifies the presence requirements and conditions of the IEs in the message. Cause IE indicates if the relocation has been accepted, or not. The relocation has not been accepted by the target MME/SGSN/AMF if the Cause IE value differs from "Request accepted". Possible Cause values are specified in Table 8.4-1. Message specific cause values are: - "Relocation failure". Table -1: Information Elements in a Forward Relocation Response Bearer Context IE in this message is specified in Table -2, the source system shall use this IE for data forwarding in handover. Table -2: Bearer Context | 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.3.2 |
3,274 | 15 Management security for network slices 15.1 General | The creation, modification, and termination of a Network Slice Instance (NSI) is part of the Management Services provided by the 5G management systems. A management service is accessed by management service consumers via standardized service interfaces given in 3GPP TS 28.533[ Management and orchestration; Architecture framework ] [54]. The typical service consumers for the above NSI provisioning and NSI provisioning exposure are operators and vertical industry respecitively, as described in 3GPP TS 28.531[ Management and orchestration; Provisioning ] [55]. These management services are securely protected through mutual authentication and authorization below. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 15 |
3,275 | 4.3.23a Access network selection and traffic steering based on RAN-Controlled WLAN interworking | As described in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5] E-UTRAN may support RAN-Controlled WLAN interworking (RCLWI) for controlling traffic steering between E-UTRAN and WLAN for UEs in RRC_CONNECTED. When E-UTRAN sends an "offload" command to the UE, the UE passes an indication to the upper layers indicating that traffic steering to/from WLAN is needed. The upper layers determine to initiate traffic steering to/from WLAN based on the UE capability and the configuration information that has received from NAS layer indicating which PDN connections are offloadable. When the UE receives the "offload" command from the EUTRAN, the UE shall perform handover to WLAN only the PDN connections that have been authorized for offloading. The NAS level indication about "offloadability" of PDN connections is defined in clause 4.3.23. The UE uses the RCLWI procedures to perform access network selection and traffic steering decisions between 3GPP access and WLAN or using ANDSF policies defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. Co-existence between the procedures defined for RCLWI, ANDSF policies and user preference is described in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. | 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.23a |
3,276 | 5.2.17.2.4 Nchf_SpendingLimitControl Notify service operation | Service operation name: Nchf_SpendingLimitControl_Notify Description: Notify the change of the status of the subscribed policy counters available at the CHF. Alternatively, it can be used by the CHF to provide one or more pending statuses for a subscribed policy counter together with the time they have to be applied. Alternatively, it is also used by the CHF to notify the removal of a subscriber from the CHF system, so that the NF consumer can terminate the subscriptions of all the policy counters of the subscriber. Inputs, Required: Notification Target Address, SUPI. Inputs, Optional: policy counter status as Event Information, Pending policy counter statuses and their activation times as Event Information. Subscriber removal from the CHF system as Event Information. Outputs, Required: Success or Failure. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.17.2.4 |
3,277 | 16.14.3.2.2 Conditional Handover | The same principle as described in 9.2.3.4 applies to NTN unless hereunder specified. NTN supports the following additional trigger conditions upon which UE may execute CHO to a candidate cell, as defined in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]: - The RRM measurement-based event A4; - A time-based trigger condition; - A location-based trigger condition. Time-based or location-based trigger conditions may be configured independently from the measurement condition for CHO in NTN in at least hard satellite switch case where the service discontinuity gap time length is assumed to be zero or negligible. Otherwise, a time-based or a location-based trigger condition is always configured together with one of the measurement-based trigger conditions (CHO events A3/A4/A5) as defined in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]. A time-based or a location-based trigger condition is always configured together with one of the measurement-based trigger conditions (CHO events A3/A4/A5) as defined in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]. It is up to UE implementation how the UE evaluates the time- or location-based trigger condition together with the RRM measurement-based event. When a time-based trigger condition is used, the source gNB may signal the corresponding parameters to a single target gNB via the Source NG-RAN Node to Target NG-RAN Node Transparent Container in an NG-C based handover, see TS 23.502[ Procedures for the 5G System (5GS) ] [22]. The source gNB signals the corresponding CHO configuration to the UE in the RRC Reconfiguration message during handover execution. When time-based trigger condition is used, the source NG-RAN node should consider the time indicated to the UE to decide when to start the early data forwarding to the target NG-RAN node. Time-based CHO can be performed via RACH-less. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.14.3.2.2 |
3,278 | 8.3.2 Procedure | Figure 8.3.2-1 Handover from 5GS to EPC over N26 NOTE 1: This procedure is based on clause 4.11.1.2.1 in TS 23.502[ Procedures for the 5G System (5GS) ] and only includes steps and description that are relevant to security. If the UE is initially registered and connected to the 5GC, the 5GC has a current security context for the UE. The current 5G security context may be a mapped 5G security context resulting from a previous mobility from EPC, or a native 5G security context resulting from a primary authentication with the 5GC. 1. The gNB/ng-eNB sends a Handover Required message to the AMF, including UE’s identity . 2. When the source AMF performs a handover procedure to the EPC, after checking the UE's access rights and security capabilities, the source AMF shall prepare a UE context including a mapped EPS security context for the target MME. To construct the mapped EPS security context, the source AMF shall derive a K’ASME using the KAMF key and the current downlink 5G NAS COUNT of the current 5G security context as described in clause 8.6.1 and then increments its stored downlink 5G NAS COUNT value by one. The source AMF shall select the EPS NAS algorithms identifiers (it has stored) to be used in the target MME at interworking handover to EPS, for encryption and integrity protection. NOTE 2: A legacy target MME is expecting to receive the selected EPS NAS algorithms identifiers over N26 from the source AMF as the target MME believes the source AMF is another MME. The source AMF has therefore provisioned the EPS NAS security algorithms identifiers to be used at interworking handover to EPS to the UE in the 5G NAS SMC in 5G access as described in clause 6.7.2. The target MME could re-select different EPS NAS algorithms though to be used with the UE by running a NAS SMC in the following Tracking Area Update procedure. The uplink and downlink EPS NAS COUNT associated with the newly derived KASME' key are set to the values as described in clause 8.6.1. The eKSI for the newly derived KASME' key is defined as described in clause 8.6.1. The source AMF shall also derive the initial KeNB key from the KASME' key and the uplink NAS COUNT as specified in Annex A.3 of TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10] using 232-1 as the value of the uplink NAS COUNT parameter. NOTE 3: The source AMF and the UE only uses the 232-1 as the value of the uplink NAS COUNT for the purpose of deriving KeNB and do not actually set the uplink NAS COUNT to 232-1. The reason for choosing such a value not in the normal NAS COUNT range, i.e., [0, 224-1] is to avoid any possibility that the value may be used to derive the same KeNB again. The source AMF subsequently derives NH two times as specified in clause A.4 of TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10]. The {NH, NCC=2} pair is provided to the target MME as a part of UE security context in the Forward Relocation Request message. 3. The source AMF shall transfer the UE security context (including new KASME', eKSI, uplink and downlink EPS NAS COUNT’s, UE EPS security capabilities, selected EPS NAS algorithms identifiers) to the target MME in the Forward Relocation Request message. The UE NR security capabilities may be sent by the source AMF as well. 4. When the target MME receives Forward Relocation Request message from source AMF, then the target MME shall derive EPS NAS keys (i.e., KNASenc and KNASint) from the received KASME' key with the received EPS NAS security algorithm identifiers as input, to be used in EPC as described in Annex A.7 in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10]. The target MME needs to include the {NH, NCC=2} pair and the UE security capabilities in the S1 HANDOVER REQUEST message to the target LTE eNB. The UE security capabilities include the UE EPS security capabilities received from the source AMF. 5. Upon receipt of the S1 HANDOVER REQUEST from the target MME, the target LTE eNB selects AS security algorithmsfrom the UE EPS security capabilities as described in clause 7.2.4.2.3 in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10] and computes the KeNB to be used with the UE and proceed as described in clause 7.2.8.4.3 in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10]. The target LTE eNB then sends the selected AS security algorithms in the target to source transparent container in the S1 Handover Request Ack Message to the target MME. 6. The target MME shall include the target to source transparent container received from the target LTE eNB in the Forward Relocation Response message sent to the source AMF. 7. The source AMF shall include the target to source transparent container and the 8 LSB of the downlink NAS COUNT value used in KASME’ derivation in step 2, in the Handover command sent to the source gNB/ng-eNB. 8. The source gNB/ng-eNB shall include the target to source transparent container and the 8 LSB of the downlink NAS COUNT value in the Handover command sent to the UE. Upon the reception of the Handover Command message, the UE shall estimate the downlink NAS COUNT value using the received 8 LSB of the downlink NAS COUNT value and its stored downlink NAS COUNT value. The UE shall ensure that the estimated downlink NAS COUNT value is greater than the stored downlink NAS COUNT value. Then, the UE shall derive the mapped EPS security context, i.e. derive KASME' from KAMF as described in clause 8.6.1 using the estimated downlink 5G NAS COUNT value. After the derivation the UE shall set the downlink NAS COUNT value in the 5G NAS security context to the received downlink NAS COUNT value. 9. The eKSI for the newly derived KASME' key is defined as described in clause 8.6.1. The UE shall also derive the EPS NAS keys (i.e. KNASenc and KNASint) as the MME did in step 4 using the EPS NAS security algorithms identifiers stored in the ME and provisioned by the AMF to the UE in 5G NAS SMC in earlier 5G access. The UE shall also derive the initial KeNB from the KASME' and the uplink NAS COUNT as specified in Annex A.3 of TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10] using 232-1 as the value of the uplink NAS COUNT parameter. The UE shall also derive the {NH, NCC=2} pair as described in A.4 of TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10] and further derive the KeNB to be used with the UE by performing the key derivation defined in Annex A.5 in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10]. The UE shall derive the AS RRC keys and the AS UP keys based on the KeNB and the received AS EPS security algorithms identifiers selected by the target eNB as described in Annex A.7 in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10]. The uplink and downlink EPS NAS COUNT associated with the derived EPS NAS keys are set to the values as described in clause 8.6.1. The UE shall immediately take into use the newly created mapped EPS security context, both for NAS and AS communication. 10. The UE sends the Handover Complete message to the target LTE eNB. The UE shall cipher and integrity protect this message using the newly created mapped EPS security context. 11. The target LTE eNB notifies the target MME with a Handover Notify message. After successful completion of the Handover procedure, the UE shall delete any mapped 5G security context. After deleting the mapped 5G security context, if the UE has a full non-current native 5G NAS security context then the UE shall make the non-current native 5G NAS security context the current one. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 8.3.2 |
3,279 | Frequency error for CA | For inter-band carrier aggregation with uplink assigned to two E-UTRA bands, the frequency error requirements defined in subclause 6.5.1 shall apply on each component carrier with all component carriers active. For intra-band contiguous carrier aggregation the UE modulated carrier frequencies per band shall be accurate to within ±0.1 PPM observed over a period of one timeslot compared to the carrier frequency of primary component carrier received from the E-UTRA in the corresponding band. For intra-band non-contiguous carrier aggregation the requirements in Section 6.5.1 applies per component carrier. | 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 | Frequency |
3,280 | 12.5 Service Area Identifier | The Service Area Identifier (SAI) is used to identify an area consisting of one or more cells belonging to the same Location Area. Such an area is called a Service Area and can be used for indicating the location of a UE to the CN. The Service Area Code (SAC) together with the PLMN-Id and the LAC constitute the Service Area Identifier. - SAI = PLMN-Id || LAC || SAC The SAC is defined by the operator, and set in the RNC via O&M. For the syntax description and the use of this identifier in RANAP signalling, see 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [17]. 3GPP TS 25.423[ UTRAN Iur interface Radio Network Subsystem Application Part (RNSAP) signalling ] [37] and 3GPP TS 25.419[ UTRAN Iu-BC interface: Service Area Broadcast Protocol (SABP) ] [38] define the use of this identifier in RNSAP and SABP signalling. A cell may belong to one or two Service Areas. If it belongs to two Service Areas, one is applicable in the Broadcast (BC) domain and the other is applicable in both the CS and PS domains. The Broadcast (BC) domain requires that its Service Areas each consist of only one cell. This does not limit the use of Service Areas for other domains. Refer to 3GPP TS 25.410[ UTRAN Iu interface: General aspects and principles ] [39] for a definition of the BC domain. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 12.5 |
3,281 | 5.2.3.3 Nudm_SubscriberDataManagement (SDM) Service 5.2.3.3.1 General | Subscription data types used in the Nudm_SubscriberDataManagement Service are defined in Table 5.2.3.3.1-1 below. Table 5.2.3.3.1-1: UE Subscription data types Table 5.2.3.3.1-2: Group Subscription data types At least a mandatory key is required for each Subscription Data Type to identify the corresponding data. Depending on the use case, for some Subscription Data Types it is possible to use one or multiple sub keys to further identify the corresponding data, as defined in Tables 5.2.3.3.1-3 and 5.2.3.3.1-4 below. Table 5.2.3.3.1-3: UE Subscription data types keys Table 5.2.3.3.1-4: Group Subscription data types keys Wireline access specific subscription data parameters are specified in TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [53]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.3.3 |
3,282 | – SchedulingRequestResourceConfig | The IE SchedulingRequestResourceConfig determines physical layer resources on PUCCH where the UE may send the dedicated scheduling request (D-SR) (see TS 38.213[ NR; Physical layer procedures for control ] [13], clause 9.2.4). SchedulingRequestResourceConfig information element -- ASN1START -- TAG-SCHEDULINGREQUESTRESOURCECONFIG-START SchedulingRequestResourceConfig ::= SEQUENCE { schedulingRequestResourceId SchedulingRequestResourceId, schedulingRequestID SchedulingRequestId, periodicityAndOffset CHOICE { sym2 NULL, sym6or7 NULL, sl1 NULL, -- Recurs in every slot sl2 INTEGER (0..1), sl4 INTEGER (0..3), sl5 INTEGER (0..4), sl8 INTEGER (0..7), sl10 INTEGER (0..9), sl16 INTEGER (0..15), sl20 INTEGER (0..19), sl40 INTEGER (0..39), sl80 INTEGER (0..79), sl160 INTEGER (0..159), sl320 INTEGER (0..319), sl640 INTEGER (0..639) } OPTIONAL, -- Need M resource PUCCH-ResourceId OPTIONAL -- Need M } SchedulingRequestResourceConfigExt-v1610 ::= SEQUENCE { phy-PriorityIndex-r16 ENUMERATED {p0, p1} OPTIONAL, -- Need M ... } SchedulingRequestResourceConfigExt-v1700 ::= SEQUENCE { periodicityAndOffset-r17 CHOICE { sl1280 INTEGER (0..1279), sl2560 INTEGER (0..2559), sl5120 INTEGER (0..5119) } OPTIONAL -- Need M } -- TAG-SCHEDULINGREQUESTRESOURCECONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,283 | – MultiFrequencyBandListNR-SIB | The IE MultiFrequencyBandListNR-SIB indicates the list of frequency bands, for which cell (re-)selection parameters are common, and a list of additionalPmax and additionalSpectrumEmission. MultiFrequencyBandListNR-SIB information element -- ASN1START -- TAG-MULTIFREQUENCYBANDLISTNR-SIB-START MultiFrequencyBandListNR-SIB ::= SEQUENCE (SIZE (1.. maxNrofMultiBands)) OF NR-MultiBandInfo NR-MultiBandInfo ::= SEQUENCE { freqBandIndicatorNR FreqBandIndicatorNR OPTIONAL, -- Cond OptULNotSIB2 nr-NS-PmaxList NR-NS-PmaxList OPTIONAL -- Need S } MultiFrequencyBandListNR-SIB-v1760 ::= SEQUENCE (SIZE (1.. maxNrofMultiBands)) OF NR-MultiBandInfo-v1760 NR-MultiBandInfo-v1760 ::= SEQUENCE { nr-NS-PmaxList-v1760 NR-NS-PmaxList-v1760 OPTIONAL -- Need S } MultiFrequencyBandListNR-Aerial-SIB-r18 ::= SEQUENCE (SIZE (1.. maxNrofMultiBands)) OF NR-MultiBandInfoAerial-r18 NR-MultiBandInfoAerial-r18 ::= SEQUENCE { freqBandIndicatorNR-Aerial-r18 FreqBandIndicatorNR OPTIONAL, -- Cond OptULNotSIB2 nr-NS-PmaxListAerial-r18 NR-NS-PmaxListAerial-r18 OPTIONAL -- Need S } -- TAG-MULTIFREQUENCYBANDLISTNR-SIB-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,284 | 7.4.1G Minimum requirements for V2X | The throughput shall be ≥ 95% of the maximum throughput of the reference measurement channels as specified in Annexes A.8.2 with parameters specified in Table 7.4.1G-1. Table 7.4.1G-1: Maximum input level When UE is configured for simultaneous E-UTRA V2X sidelink and E-UTRA downlink reception for inter-band E-UTRA V2X / E-UTRA bands specified in Table 5.5G-2, the requirements in subclause 7.4.1G apply for the E-UTRA V2X sidelink reception and the requirements in subclause 7.4.1 apply for the E-UTRA downlink reception while all downlink carriers are active. For intra-band contiguous multi-carrier operation, maximum input level is defined as the powers received at the UE antenna port over the Transmission bandwidth configuration of each CC, at which the specified relative throughput shall meet or exceed the minimum requirements for the specified reference measurement channel over each component carrier. Table 7.4.1G-2: Maximum input level for intra-band contiguous multi-carrier for V2X UE | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 7.4.1G |
3,285 | 7.3.12 Detach Notification | A Detach Notification message shall be sent from an MME to the associated SGSN, or from an SGSN to the associated MME as a part of Detach procedure if the ISR is activated between the MME and SGSN for the UE. Possible Cause values are: "Local Detach". "Complete Detach". A Detach Notification message shall also be sent from an SGSN to the associated MME as a part of Detach procedure if the ISR is activated between the MME and SGSN for the UE. Possible Cause values are: "IMSI Detach only". "Local Detach" indicates that this detach is local to the MME/SGSN and so the associated SGSN/MME registration where the ISR is activated shall not be detached. The MME/SGSN that receives this message including this Cause value of "Local Detach" only deactivates the ISR. This Cause value shall be included in the procedures: MME/SGSN-initiated Detach Procedure in case of implicit detach. "Complete Detach" indicates both the MME registration and the SGSN registration that the ISR is activated for, shall be detached. This "Complete Detach" Cause value shall be included in the procedures: UE-initiated Detach Procedure. MME/SGSN-initiated Detach Procedure in case of explicit detach. For the purpose of SGs handling, the SGSN shall include Detach Type in the Detach Notification message for "Complete Detach" when the UE is combined IMSI/EPS attached and the ISR is activated. Possible Detach Type values are: "PS Detach". "Combined PS/CS Detach". "PS Detach" indicates that the MME shall perform explicit IMSI detach from EPS service as specified in clause 5.4, 3GPP TS 29.118[ Mobility Management Entity (MME) - Visitor Location Register (VLR) SGs interface specification ] [22]. "Combined PS/CS detach" indicates that the MME shall perform explicit IMSI detach from non-EPS service as specified in clause 5.5, 3GPP TS 29.118[ Mobility Management Entity (MME) - Visitor Location Register (VLR) SGs interface specification ] [22]. "IMSI Detach only" indicates that combined IMSI/EPS attached UE initiates IMSI only GPRS detach from non-GPRS service as specified in clause 4.7.4.1, 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [5], and both the SGSN/MME registration shall be remained. The MME shall perform explicit IMSI detach from non-EPS service for the SGs handling purpose, which is specified in clause 5.5, 3GPP TS 29.118[ Mobility Management Entity (MME) - Visitor Location Register (VLR) SGs interface specification ] [22]. This "IMSI Detach only" Cause value shall be included in the procedures: UE-initiated Detach Procedure for GERAN/UTRAN for "IMSI Detach only". Table -1 specifics the presence of the IEs in the message. Table -1: Information Elements in a Detach Notification | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 7.3.12 |
3,286 | 9.9.4.29 Extended APN aggregate maximum bit rate | The purpose of the extended APN aggregate maximum bit rate information element is to indicate the initial subscribed APN-AMBR with a value higher than 65280 Mbps when the UE establishes a PDN connection or to indicate the new APN-AMBR with a value higher than 65280 Mbps if it is changed by the network. The receiving entity shall ignore the bit rate values which are included in the extended APN aggregate maximum bit rate information element and not higher than 65280 Mbps. The extended APN aggregate maximum bit rate information element is coded as shown in figure 9.9.4.29.1 and table 9.9.4.29.1. The extended APN aggregate maximum bit rate is a type 4 information element with a length of 8 octets. Figure 9.9.4.29.1: Extended APN aggregate maximum bit rate information element Table 9.9.4.29.1: Extended APN aggregate maximum bit rate information element | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.9.4.29 |
3,287 | 5.34.8 Support for Cellular IoT | This clause defines the specific impacts of deployments topologies with specific SMF Service Areas on how 5GS supports Cellular IoT as defined in clause 5.31. For a PDU Session supporting Control Plane CIoT 5GS Optimisation as defined in clause 5.31.4: - For a PDU session towards a DNN/S-NSSAI for which the subscription includes a NEF Identity for NIDD (i.e. for a PDU session which will be anchored in NEF), the AMF never inserts an I-SMF. When an I-SMF is inserted to serve a PDU Session, the I-SMF supports the features that, as specified in clause 5.31, apply to the V-SMF in the case of Home Routed. NOTE: This can require the SMF to subscribe onto I-SMF about RAT type change for a PDU Session as described in clause 4.23 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.34.8 |
3,288 | – MBSInterestIndication | The MBSInterestIndication message is used to inform network that the UE is receiving/ interested to receive or no longer receiving/ interested to receive MBS broadcast service(s) via a broadcast MRB. Signalling radio bearer: SRB1 RLC-SAP: AM Logical channel: DCCH Direction: UE to Network MBSInterestIndication message -- ASN1START -- TAG-MBSINTERESTINDICATION-START MBSInterestIndication-r17 ::= SEQUENCE { criticalExtensions CHOICE { mbsInterestIndication-r17 MBSInterestIndication-r17-IEs, criticalExtensionsFuture SEQUENCE {} } } MBSInterestIndication-r17-IEs ::= SEQUENCE { mbs-FreqList-r17 CarrierFreqListMBS-r17 OPTIONAL, mbs-Priority-r17 ENUMERATED {true} OPTIONAL, mbs-ServiceList-r17 MBS-ServiceList-r17 OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension MBSInterestIndication-v1800 OPTIONAL } MBSInterestIndication-v1800 ::= SEQUENCE { mbs-NonServingInfoList-r18 MBS-NonServingInfoList-r18 OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-MBSINTERESTINDICATION-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,289 | A.7 Monitoring of interference situation | In the LTE radio technology interference has to be coordinated on the basis uplink and downlink i.e. in a coordinated usage of the UL resources (Physical Resource Blocks, PRBs) and DL Transmitted Power, which lead to improve SIR and corresponding throughput. These are achieved by means of mechanisms employing channel quality indicators in support of scheduling/radio resource allocation functions. These RRM functions in the eNB require the setting of frequency / power restrictions and preferences for the resource usage in the different cells. Setting and updating these parameters is the task of a network optimisation (done by operator or automatically by SON). Use cases for the related interference measurements are e.g. optimisation of ICIC related RRM functionality, the detection of long distance interferer and the interference due to spurious emissions of neighbour cells. The later case is assumed only in high load scenarios or unsufficent ICIC functionality due to the the fact that ICIC functionality would minimise interference autonomously if sufficient bandwidth is available. The necessary measurements to identify and anylse the interference situation as input for optimisation tasks has to be defined. | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | A.7 |
3,290 | B.4 Derivation of Kc’ from Kc for HSPA to UTRAN/GERAN SRVCC handover | This input string is used for GSM subscribers when there is a need to derive Kc’ from the 64-bit Kc during mapping the security contexts from HSPA to UTRAN/GERAN. The Key is the concatenation of Kc || Kc || Kc || Kc || (which are 64 bits each), and the output Kc’ is the 64 most significant bits of the KDF output. - FC = 0x31 - P0 = NONCE - L0 = length of NONCE (i.e. 0x00 0x10) The Kc’ used in GERAN directly. When the access is over UTRAN, CK’CS||IK’CS shall be further derived from Kc’ using the key conversion functions c4 and c5 defined in this specification. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | B.4 |
3,291 | 5.4.2B PUCCH format 4 | The block of bits shall be scrambled with a UE-specific scrambling sequence, resulting in a block of scrambled bits according to where the scrambling sequence is given by clause 7.2. The scrambling sequence generator shall be initialised with at the start of each subframe where is the C-RNTI. The block of scrambled bits shall be QPSK modulated as described in Clause 7.1, resulting in a block of complex-valued modulation symbols where . The block of complex-valued symbols is divided into sets, each corresponding to one SC-FDMA symbol. Transform precoding shall be applied according to where , and are given by Table 5.4.2C-1 for normal PUCCH format 4 and shortened PUCCH format 4, resulting in a block of complex-valued symbols . The variable, where represents the bandwidth of the PUCCH format 4 in terms of resource blocks, shall fulfil where is a set of non-negative integers. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.4.2B |
3,292 | 9.11.3.73 NB-N1 mode DRX parameters | The purpose of the NB-N1 mode DRX parameters information element is to indicate that the UE wants to use DRX in NB-N1 mode and for the network to indicate the DRX cycle value to be used at paging in NB-N1 mode. The NB-N1 mode DRX parameters is a type 4 information element with a length of 3 octets. The NB-N1 mode DRX parameters information element is coded as shown in figure 9.11.3.73.1 and table 9.11.3.73.1. The value part of a DRX parameter information element is coded as shown in table 9.11.3.73.1. Figure 9.11.3.73.1: NB-N1 mode DRX parameters information element Table 9.11.3.73.1: NB-N1 mode DRX 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.73 |
3,293 | 8.22.2 Inter-DU indirect path addition on top of direct path | The signalling flow for inter-DU indirect path addition is shown in Figure 8.22.2-1. Figure 8.22.2-1 Signalling procedure of inter-DU indirect path addition on top of direct path 1. If the MP Remote UE is connected with the MP Relay UE using PC5 link, the Uu measurement configuration and measurement report signalling are performed between MP Remote UE and the gNB-CU to evaluate relay link measurement and Uu link measurement. The MP Remote UE may report Uu measurement results of neighboring cells and one or multiple candidate MP Relay UE(s). In case that the MP Remote UE is connected with the MP Relay UE using N3C and the MP Relay UE is in RRC_CONNECTED state, the MP Remote UE reports at least the list of the C-RNTI and the cell ID of one or multiple candidate MP Relay UE(s). 2. The gNB-CU decides to add the indirect path via MP Relay UE to MP Remote UE under a different gNB-DU (i.e., gNB-DU2). NOTE: Mode 1 resource configuration cannot be configured for MP Remote UE in inter-gNB-DU multi-path relay in this release. 3. The reconfiguration to MP Relay UE is performed among MP Relay UE, the gNB-DU2 and the gNB-CU if MP Relay UE is in RRC_CONNECTED state. The gNB-CU sends an RRCReconfiguration message to the MP Relay UE. If the MP Relay UE is in RRC_IDLE/INACTIVE state, this step is skipped. 4. The gNB-CU sends the UE CONTEXT SETUP REQUEST message for the MP Remote UE to the gNB-DU2, which contains the indirect path addition configuration at least. 5. The gNB-DU2 responds to the gNB-CU with a UE CONTEXT SETUP RESPONSE message. 6. The gNB-CU sends the DL RRC MESSAGE TRANSFER message for MP Remote UE by including the RRCReconfiguration message to gNB-DU1. If the MP Remote UE is connected with the MP Relay UE using the PC5 link, the contents in the RRCReconfiguration message may include at least indirect path addition configuration, PC5 Relay RLC channel configuration for relay traffic, bearer mapping and the associated radio bearer(s). If the MP Remote UE is using N3C, the contents in the RRCReconfiguration message may include at least indirect path addition configuration, bearer mapping and the associated radio bearer(s). 7. The gNB-DU1 sends the RRCReconfiguration message to the MP Remote UE. 8. If the MP Remote UE is using the PC5 link, the MP Remote UE establishes PC5 connection with the target MP Relay UE. If the MP Remote UE is connected with the MP Relay UE using N3C, this step is skipped. 9. The MP Remote UE sends the RRCReconfigurationComplete message to the gNB-DU1 via direct path in order to complete the indirect path addition procedure. 9a. In case the SRB1 with duplication is configured, the MP Remote UE also sends the RRCReconfigurationComplete message to the gNB-DU2 via indirect path. NOTE: In the case that the target MP Relay UE for indirect path addition is in RRC_IDLE/INACTIVE state, how the MP Remote UE triggers the MP Relay UE to be in RRC_CONNECTED state is specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [2]. 10. The gNB-DU1 sends the UL RRC MESSAGE TRANSFER message to gNB-CU by including the RRCReconfigurationComplete message received in step 9. 10a. In case the SRB1 with duplication is configured, the gNB-DU2 also sends the UL RRC MESSAGE TRANSFER message to gNB-CU by including the RRCReconfigurationComplete message received in step 9a. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.22.2 |
3,294 | 5.8.2 Scenario | A UAV control center operates a UAV using 3GPP communication. Through this 3GPP communication link toward the UAV, the UAV control center can see the video image transmitted by the UAV and sends flight command to the UAV. To avoid collision among UAVs, the UAV transmits identification messages to identify itself to other UAVs, using direct device connection. These identification messages can be received also by observation devices deployed by UAV service operator on the ground. These ground-based observation devices report the location and the identity of the detected UAVs to the UAV control center, to assist the control of the UAV. Furthermore, national ATC system can be enhanced to receive identification messages transmitted by UAVs using 3GPP communication, to have a nation-wide view of aerospace. | 3GPP TS 22.825 | Study on Remote Identification of Unmanned Aerial Systems (UAS) | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 5.8.2 |
3,295 | 5.3.4 Equivalent PLMNs list | The UE shall store a list of equivalent PLMNs. These PLMNs shall be regarded by the UE as equivalent to each other for PLMN selection and cell selection/re-selection. The same list is used by 5GMM, EMM, GMM and MM. The UE shall update or delete this list at the end of each attach or combined attach or tracking area updating or combined tracking area updating procedure. The stored list consists of a list of equivalent PLMNs as downloaded by the network plus the PLMN code of the registered PLMN that downloaded the list. When the UE is switched off, it shall keep the stored list so that it can be used for PLMN selection after switch on. The UE shall delete the stored list if the USIM is removed or when the UE attached for emergency bearer services or access to RLOS enters the state EMM-DEREGISTERED. The maximum number of possible entries in the stored list is 16. | 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.3.4 |
3,296 | – SCellActivationRS-Config | The IE SCellActivationRS-Config is used to configure a Reference Signal for fast activation of the SCell where the IE is included (see TS 38.214[ NR; Physical layer procedures for data ] [19], clause 5.2.1.5.3. Usage of an SCellActivationRS-Config is indicated by including its scellActivationRS-Id in the Enhanced SCell activation MAC CE (see TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3] clause 6.1.3.55). SCellActivationRS-Config information element -- ASN1START -- TAG-SCELLACTIVATIONRS-CONFIG-START SCellActivationRS-Config-r17 ::= SEQUENCE { scellActivationRS-Id-r17 SCellActivationRS-ConfigId-r17, resourceSet-r17 NZP-CSI-RS-ResourceSetId, gapBetweenBursts-r17 INTEGER (2..31) OPTIONAL, -- Need R qcl-Info-r17 TCI-StateId, ... } -- TAG-SCELLACTIVATIONRS-CONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,297 | 6.12 OFDM baseband signal generation | The time-continuous signal on antenna port in OFDM symbol in a downlink slot is defined by for where and. The variable equals 2048 for subcarrier spacing, 4096 for subcarrier spacing, 12288 for , 24576 for subcarrier spacing , and 82944 for . For frame structure type 3, if PDCCH is to be transmitted in a subframe starting with OFDM symbol based on the received uplink control information that indicates channel occupancy time sharing '1' as specified in [11], OFDM symbol in the previous subframe may be transmitted, given by The OFDM symbols in a slot shall be transmitted in increasing order of , starting with , where OFDM symbol starts at time within the slot. In case the first OFDM symbol(s) in a slot use normal cyclic prefix and the remaining OFDM symbols use extended cyclic prefix, the starting position the OFDM symbols with extended cyclic prefix shall be identical to those in a slot where all OFDM symbols use extended cyclic prefix. Thus there will be a part of the time slot between the two cyclic prefix regions where the transmitted signal is not specified. For , there is one OFDM symbol per slot and one slot per subframe. For , there is one OFDM symbol per slot and one slot per 3ms. Table 6.12-1 lists the value of that shall be used. Note that different OFDM symbols within a slot in some cases have different cyclic prefix lengths. In case NB-IoT is supported, the OFDM baseband signal generation is defined in clause 10.2.8. Table 6.12-1: OFDM parameters | 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.12 |
3,298 | 6.1.3.4 PDP context deactivation procedure | The purpose of this procedure is to deactivate an existing PDP context between the MS and the network. The PDP context deactivation may be initiated by the MS or by the network. The tear down indicator information element may be included in the DEACTIVATE PDP CONTEXT REQUEST message in order to indicate whether only the PDP context associated with this specific TI or all active PDP contexts sharing the same PDP address and APN as the PDP context associated with this specific TI shall be deactivated. If the tear down is requested, all other active PDP contexts sharing the same PDP address and APN as the PDP context associated with this specific TI shall be deactivated locally without peer-to-peer signalling. In this case, the network should not include WLAN offload indication in the DEACTIVATE PDP CONTEXT REQUEST message, and if the UE receives the WLAN offload indication, the UE shall ignore the indication. If the tear down indicator information element is not included in the DEACTIVATE PDP CONTEXT REQUEST message, only the PDP context associated with this specific TI shall be deactivated. For an exception when the PDP context is a default PDP context and there are other active PDP contexts sharing the same PDP address and APN, see subclause 6.1.3.4.3. An MS supporting S1 mode shall always include the tear down indicator when deactivating the default PDP context. An MS not supporting S1 mode should apply the same behavior (see 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74]). Local deactivation of a NBIFOM multi-access PDN connection can be triggered by an NBIFOM procedure (see 3GPP TS 24.161[ Network-Based IP Flow Mobility (NBIFOM); Stage 3 ] [158]). If such a trigger is received then the associated PDP contexts mentioned in this specification shall be deactivated locally without peer-to-peer signalling. After successful PDP context deactivation, the associated NSAPI and TI values are released and can be reassigned to another PDP context. If one or more MBMS contexts are linked to a PDP context that has been deactivated, the MS shall deactivate all those MBMS contexts locally (without peer to peer signalling between the MS and the network). The MS is allowed to initiate the PDP context deactivation procedure even if the timer T3396 is running. | 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.4 |
3,299 | 4.3.7 CN-initiated selective deactivation of UP connection of an existing PDU Session | The following procedure is used to deactivate UP connection (i.e. data radio bearer and N3 tunnel) for an established PDU Session of a UE in CM-CONNECTED state. For an always-on PDU Session, the SMF should not configure the UPF to report inactivity. Figure 4.3.7-1: CN-initiated deactivation of UP connection for an established PDU Session 1. The SMF determines that the UP connection of the PDU Session can be deactivated in following cases: - During handover procedure, if all the QoS Flows of a PDU Session are rejected by the target NG-RAN (as described in clause 4.9.1), or if a PDU Session is failed to setup indicated by the AMF (see step 7 of clause 4.9.1.3.3). SMF proceeds with step 2 and step 3, the steps 5 to 9 are skipped; - The UPF detects that the PDU Session has no data transfer for a specified Inactivity period as described in clause 4.4.2.2; - For PDU sessions belonging to a network slice that is in the Partially Allowed NSSAI (see clause 5.15.17 in TS 23.501[ System architecture for the 5G System (5GS) ] [2]), or with Network Slice Area of Service not matching deployed Tracking Areas (see clause 5.15.18 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) the AMF notifies to the SMF that it has detected that the UE moved out of the network slice area of support or availability; - For a LADN PDU Session, the AMF notifies to the SMF that the UE moved out of the LADN service area; or - The AMF notifies to the SMF that the UE moved out of the Allowed Area. The SMF may decide to release the UPF of N3 terminating point. In that case the SMF proceeds with step 2 and step 3. Otherwise, if the SMF decides to keep the UPF of N3 terminating points, the SMF proceeds with step 4. To assist SMF in this decision the SMF may make use of UE presence pattern in LADN service area based on UE mobility analytics from the NWDAF as described in clause 6.7.2 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. The SMF may make use of UE Communication analytics provided by NWDAF, as described in clause 6.7.3 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50], to determine the value of an Inactivity Timer for a PDU Session provided to the UPF. 2. The SMF may initiate an N4 Session Release procedure to release the intermediate UPF of N3 terminating point. If there are multiple intermediate UPFs, this step can be performed for each UPFs to be released. The SMF needs to initiate N4 Session Modification procedure to the UPF (i.e. N9 terminating point or PDU Session Anchor) connecting to the released UPF in step 3. 3. If the intermediate UPF(s) of N3 terminating point is released in step 2, the SMF initiates an N4 Session Modification procedure towards the UPF (PDU Session Anchor or another intermediate UPF) connecting to the released UPF, indicating the need to remove CN Tunnel Info for N9 tunnel of the corresponding PDU Session. In this case, the UPF connecting to the released UPF buffers the DL packets for this PDU Session or drops the DL packets for this PDU session or forwards the DL packets for this PDU session to the SMF, based on buffering instruction provided by the SMF as described in clause 5.8.3.2 or clause 5.8.3.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the PDU Session corresponds to a LADN and the UE moved out of the LADN service area, the SMF may notify the UPF connecting to the released UPF to discard downlink data for the PDU Sessions and/or to not provide further Data Notification messages. Otherwise, N4 Session Modification procedure occurs toward N3 terminating point. 4. If the UPF of N3 terminating point is not released in step 2, the SMF initiates an N4 Session Modification procedure indicating the need to remove AN Tunnel Info for N3 tunnel of the corresponding PDU Session. In this case, the UPF buffers the DL packets for this PDU Session or drops the DL packets for this PDU session or forwards the DL packets for this PDU session to the SMF, based on buffering instruction provided by the SMF as described in clause 5.8.3.2 or clause 5.8.3.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the PDU Session corresponds to a LADN and the UE moved out of the LADN service area, the SMF may notify the UPF to discard downlink data for the PDU Sessions and/or to not provide further Data Notification messages. 5. The SMF invokes the Namf_Communication_N1N2MessageTransfer service operation (PDU Session ID, N2 SM Information (N2 Resource Release Request (PDU Session ID))) to release the NG-RAN resources associated with the PDU Session. 6. The AMF sends the N2 PDU Session Resource Release Command including N2 SM information (N2 Resource Release Request (PDU Session ID)) received from the SMF via N2 to the NG-RAN. 7. The NG-RAN may issue NG-RAN specific signalling exchange (e.g. RRC Connection Reconfiguration) with the UE to release the NG-RAN resources related to the PDU Session received from the AMF in step 5. When a User Plane connection for a PDU Session is released, the AS layer in the UE indicates it to the NAS layer. If the UE is in RRC_INACTIVE state, this step is skipped. When the UE becomes RRC_CONNECTED state from RRC_INACTIVE state, the NG-RAN and UE synchronize the released radio resources for the deactivated PDU Session as described in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [16] and TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]. 8. The NG-RAN acknowledges the N2 PDU Session Resource Release Command to the AMF including N2 SM Resource Release Ack (User Location Information, Secondary RAT Usage Data). 9. The AMF invokes the Nsmf_PDUSession_UpdateSMContext service operation (N2 SM Information(Secondary RAT Usage Data)) to acknowledge the Namf service received in step 5. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.7 |
3,300 | 5.7.7 PDU Set QoS Parameters 5.7.7.1 General | PDU Set QoS Parameters are used to support PDU Set based QoS handling in the NG-RAN. At least one PDU Set QoS Parameter shall be sent to the NG-RAN to enable PDU Set based QoS handling. The following PDU Set QoS Parameters are specified: 1. PDU Set Delay Budget (PSDB). 2. PDU Set Error Rate (PSER). 3. PDU Set Integrated Handling Information (PSIHI). For a given QoS Flow, the values of PSDB, PSER and PSIHI can be different for UL and DL. The QoS Profile may include the PDU Set QoS Parameters described in this clause (see clause 5.7.1.2) for UL and/or DL direction. The PCF determines the PDU Set QoS Parameters based on information provided by AF and/or local configuration. The PDU Set QoS parameters are sent to the SMF as part of PCC rule. The SMF sends them to NG-RAN as part of the QoS Profile. If the NG-RAN receives PDU Set QoS Parameters, it enables the PDU Set based QoS handling and applies PDU Set QoS Parameters as described in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27], TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34] and TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [51]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7.7 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.