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
⌀ |
|---|---|---|---|---|---|---|---|
4,301 | 5.9.2 Subscription Permanent Identifier | A globally unique 5G Subscription Permanent Identifier (SUPI) shall be allocated to each subscriber in the 5G System and provisioned in the UDM/UDR. The SUPI is used only inside 3GPP system, and its privacy is specified in TS 33.501[ Security architecture and procedures for 5G System ] [29]. The SUPI may contain: - an IMSI as defined in TS 23.003[ Numbering, addressing and identification ] [19], or - a network-specific identifier, used for private networks as defined in TS 22.261[ Service requirements for the 5G system ] [2]. - a GLI and an operator identifier of the 5GC operator, used for supporting FN-BRGs, as further described in TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [84]. - a GCI and an operator identifier of the 5GC operator, used for supporting FN-CRGs and 5G-CRG, as further described in TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [84]. A SUPI containing a network-specific identifier shall take the form of a Network Access Identifier (NAI) using the NAI RFC 7542 [20] based user identification as defined in TS 23.003[ Numbering, addressing and identification ] [19]. When UE needs to indicate its SUPI to the network (e.g. as part of the Registration procedure), the UE provides the SUPI in concealed form as defined in TS 23.003[ Numbering, addressing and identification ] [19]. In order to enable roaming scenarios, the SUPI shall contain the address of the home network (e.g. the MCC and MNC in the case of an IMSI based SUPI). For interworking with the EPC, the SUPI allocated to the 3GPP UE shall always be based on an IMSI to enable the UE to present an IMSI to the EPC. The usage of SUPI for W-5GAN is further specified in TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [84]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.9.2 |
4,302 | 6.6.3 Ciphering method | Figure 16b illustrates the use of the ciphering algorithm f8 to encrypt plaintext by applying a keystream using a bit per bit binary addition of the plaintext and the keystream. The plaintext may be recovered by generating the same keystream using the same input parameters and applying a bit per bit binary addition with the ciphertext. Figure 16b: Ciphering of user and signalling data transmitted over the radio access link The input parameters to the algorithm are the cipher key CK, a time dependent input COUNT-C, the bearer identity BEARER, the direction of transmission DIRECTION and the length of the keystream required LENGTH. Based on these input parameters the algorithm generates the output keystream block KEYSTREAM which is used to encrypt the input plaintext block PLAINTEXT to produce the output ciphertext block CIPHERTEXT. The input parameter LENGTH shall affect only the length of the KEYSTREAM BLOCK, not the actual bits in it. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.6.3 |
4,303 | 6.15a.6.2 Requirements | Subject to regulatory requirements and operators’ policies, the 5G system shall enable an operator to temporarily serve UEs of other operators within a geographical area for the purpose of saving energy of the other operators. NOTE 1: The other operators are assumed to stop providing access to their own network infrastructure within the same geographical area to save energy during that time. NOTE 2: Policies may include predefined times/locations, energy consumption/efficiency thresholds, etc. NOTE 3: It is assumed that the 5G system can collect charging information associated with serving UEs of other operators. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.15a.6.2 |
4,304 | 16.3.1 IP PDP type | Figure 22 represents the RADIUS message flows between a GGSN and an Authentication, Authorization and Accounting (AAA) server. NOTE 1: If some external applications require RADIUS Accounting request (Start) information before they can process user packets, then the selected APN (GGSN) may be configured in such a way that the GGSN drops user data until the Accounting Response (START) is received from the AAA server. The GGSN may wait for the Accounting Response (START) before sending the CreatePDPContextResponse. The GGSN may reject the PDP context if the Accounting Response (START) is not received. NOTE 2: Separate accounting and authentication servers may be used. NOTE 3: The Access-Request message shall be used for primary PDP context only. NOTE 4: The Accounting-Request (Start) message may be sent at a later stage, e.g. after IPv6 address has been assigned and PDP Context updated, in case of IP address allocation via DHCPv4 after successful PDP context activation signalling. Figure 22: RADIUS message flow for PDP type IP (successful user authentication case) When a GGSN receives a Create PDP Context Request message for a given APN, the GGSN may (depending on the configuration for this APN) send a RADIUS Access-Request to an AAA server. The AAA server authenticates and authorizes the user. If RADIUS is also responsible for IPv4 address and/or IPv6 prefix allocation the AAA server shall return the allocated IPv4 address and/or IPv6 prefix in the Access-Accept message. When PDP type is IPv4v6 and deferred IPv4 addressing via IPv4 address pool in the AAA server is used, the GGSN may intiate RADIUS re-authorization procedures after successful initial attach for the purpose of IPv4 address allocation or to renew the lease for a previously allocated IPv4 address. In this case, the GGSN shall set the Service-Type attribute to "Authorize Only" and the 3GPP-Allocate-IP-Type subattribute to the type of IP address to be allocated in the Access-Request message sent to the AAA server. See subclause 16.4.7.2 for the conditions to use 3GPP-Allocate-IP-Type sub-attribute in Access-Request messages. If the GGSN is using DHCPv4 signalling towards the MS and the RADIUS server includes the Session-Timeout attribute in the Access-Accept, the GGSN may use the Session-Timeout value as the DHCPv4 lease time. The GGSN shall not set the DHCPv4 lease time value higher than the Session-Timeout value. The GGSN may renew the DHCP lease to the MS without re-authorization towards the AAA server providing that the new lease expiry is no later than the Session-Timeout timer expiry. If the GGSN wishes to extend the lease time beyond the current Session-Timeout expiry, it shall initiate a new AAA re-authorization. Even if the GGSN was not involved in user authentication (e.g. transparent network access mode), it may send a RADIUS Accounting-Request START message to an AAA server. This message contains parameters, e.g. the tuple which includes the user-id and IPv4 address and/or IPv6 prefix, to be used by application servers (e.g. WAP gateway) in order to identify the user. This message also indicates to the AAA server that the user session has started. The session is uniquely identified by the Acct-Session-Id that is composed of the Charging-Id and the GGSN-Address. If some external applications require RADIUS Accounting request (Start) information before they can process user packets, then the selected APN (GGSN) may be configured in such a way that the GGSN drops user data until the Accounting Response (START) is received from the AAA server. The GGSN may wait for the Accounting Response (START) before sending the CreatePDPContextResponse. The GGSN may reject the PDP context if the Accounting Response (START) is not received. The authentication and accounting servers may be separately configured for each APN. For PDP type IPv4, at IPv4 address allocation via DHCP4 signalling between the TE and the PDN, no IPv4 address is available at PDP context activation. In that case the GGSN may wait to send the Accounting-Request START message until the TE receives its IPv4 address in a DHCPACK. For PDP type IPv4v6 and deferred IPv4 addressing, when the IPv4 address is allocated or re-allocated, the accounting session that was established for the IPv6 prefix allocation shall be used to inform the accounting server about the allocated IPv4 address by sending RADIUS Accounting-Request Interim-Update with the Framed-IP-Address attribute and its value field containing the allocated IPv4 address. When the GGSN receives a Delete PDP Context Request message and providing a RADIUS Accounting-Request START message was sent previously, the GGSN shall send a RADIUS Accounting-Request STOP message to the AAA server, which indicates the termination of this particular user session. The GGSN shall immediately send a Delete PDP context response, without waiting for an Accounting-Response STOP message from the AAA server. The AAA server shall deallocate the IPv4 address and/or IPv6 prefix (if any) initially allocated to the subscriber, if there is no session for the subscriber. For PDP type IPv4v6 and deferred IPv4 addressing, when the GGSN receives a message from the MS or the network indicating the release of the IPv4 address (e.g. receiving DHCPRELEASE) or decides to release the IPv4 address on its own (e.g. due to DHCP lease timer expiry or GGSN assigned IPv4 address), the GGSN shall inform the accounting server about the deallocation of the IPv4 address by sending RADIUS Accounting-Request Interim-Update without the Framed-IP-Address attribute. Accounting-Request ON and Accounting-Request OFF messages may be sent from the GGSN to the AAA server to ensure the correct synchronization of the session information in the GGSN and the AAA server. The GGSN may send an Accounting-Request ON message to the AAA server to indicate that a restart has occurred. The AAA server may then release the associated resources. Prior to a scheduled restart, the GGSN may send Accounting-Request OFF message to the AAA server. The AAA server may then release the associated resources. If an Access-Challenge is sent to the GGSN when an Access-Request message is pending and when IP PDP type is used, the GGSN shall silently discard the Access-Challenge message and it shall treat an Access-Challenge as though it had received an Access-Reject instead RFC 2865 [38]. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 16.3.1 |
4,305 | – CG-ConfigInfo | This message is used by master eNB or gNB to request the SgNB or SeNB to perform certain actions e.g. to establish, modify or release an SCG. The message may include additional information e.g. to assist the SgNB or SeNB to set the SCG configuration. It can also be used by a CU to request a DU to perform certain actions, e.g. to establish, or modify an MCG or SCG. Direction: Master eNB or gNB to secondary gNB or eNB, alternatively CU to DU. CG-ConfigInfo message -- ASN1START -- TAG-CG-CONFIG-INFO-START CG-ConfigInfo ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE{ cg-ConfigInfo CG-ConfigInfo-IEs, spare3 NULL, spare2 NULL, spare1 NULL }, criticalExtensionsFuture SEQUENCE {} } } CG-ConfigInfo-IEs ::= SEQUENCE { ue-CapabilityInfo OCTET STRING (CONTAINING UE-CapabilityRAT-ContainerList) OPTIONAL,-- Cond SN-AddMod candidateCellInfoListMN MeasResultList2NR OPTIONAL, candidateCellInfoListSN OCTET STRING (CONTAINING MeasResultList2NR) OPTIONAL, measResultCellListSFTD-NR MeasResultCellListSFTD-NR OPTIONAL, scgFailureInfo SEQUENCE { failureType ENUMERATED { t310-Expiry, randomAccessProblem, rlc-MaxNumRetx, synchReconfigFailure-SCG, scg-reconfigFailure, srb3-IntegrityFailure}, measResultSCG OCTET STRING (CONTAINING MeasResultSCG-Failure) } OPTIONAL, configRestrictInfo ConfigRestrictInfoSCG OPTIONAL, drx-InfoMCG DRX-Info OPTIONAL, measConfigMN MeasConfigMN OPTIONAL, sourceConfigSCG OCTET STRING (CONTAINING RRCReconfiguration) OPTIONAL, scg-RB-Config OCTET STRING (CONTAINING RadioBearerConfig) OPTIONAL, mcg-RB-Config OCTET STRING (CONTAINING RadioBearerConfig) OPTIONAL, mrdc-AssistanceInfo MRDC-AssistanceInfo OPTIONAL, nonCriticalExtension CG-ConfigInfo-v1540-IEs OPTIONAL } CG-ConfigInfo-v1540-IEs ::= SEQUENCE { ph-InfoMCG PH-TypeListMCG OPTIONAL, measResultReportCGI SEQUENCE { ssbFrequency ARFCN-ValueNR, cellForWhichToReportCGI PhysCellId, cgi-Info CGI-InfoNR } OPTIONAL, nonCriticalExtension CG-ConfigInfo-v1560-IEs OPTIONAL } CG-ConfigInfo-v1560-IEs ::= SEQUENCE { candidateCellInfoListMN-EUTRA OCTET STRING OPTIONAL, candidateCellInfoListSN-EUTRA OCTET STRING OPTIONAL, sourceConfigSCG-EUTRA OCTET STRING OPTIONAL, scgFailureInfoEUTRA SEQUENCE { failureTypeEUTRA ENUMERATED { t313-Expiry, randomAccessProblem, rlc-MaxNumRetx, scg-ChangeFailure}, measResultSCG-EUTRA OCTET STRING } OPTIONAL, drx-ConfigMCG DRX-Config OPTIONAL, measResultReportCGI-EUTRA SEQUENCE { eutraFrequency ARFCN-ValueEUTRA, cellForWhichToReportCGI-EUTRA EUTRA-PhysCellId, cgi-InfoEUTRA CGI-InfoEUTRA } OPTIONAL, measResultCellListSFTD-EUTRA MeasResultCellListSFTD-EUTRA OPTIONAL, fr-InfoListMCG FR-InfoList OPTIONAL, nonCriticalExtension CG-ConfigInfo-v1570-IEs OPTIONAL } CG-ConfigInfo-v1570-IEs ::= SEQUENCE { sftdFrequencyList-NR SFTD-FrequencyList-NR OPTIONAL, sftdFrequencyList-EUTRA SFTD-FrequencyList-EUTRA OPTIONAL, nonCriticalExtension CG-ConfigInfo-v1590-IEs OPTIONAL } CG-ConfigInfo-v1590-IEs ::= SEQUENCE { servFrequenciesMN-NR SEQUENCE (SIZE (1.. maxNrofServingCells-1)) OF ARFCN-ValueNR OPTIONAL, nonCriticalExtension CG-ConfigInfo-v1610-IEs OPTIONAL } CG-ConfigInfo-v1610-IEs ::= SEQUENCE { drx-InfoMCG2 DRX-Info2 OPTIONAL, alignedDRX-Indication ENUMERATED {true} OPTIONAL, scgFailureInfo-r16 SEQUENCE { failureType-r16 ENUMERATED { scg-lbtFailure-r16, beamFailureRecoveryFailure-r16, t312-Expiry-r16, bh-RLF-r16, beamFailure-r17, spare3, spare2, spare1}, measResultSCG-r16 OCTET STRING (CONTAINING MeasResultSCG-Failure) } OPTIONAL, dummy1 SEQUENCE { failureTypeEUTRA-r16 ENUMERATED { scg-lbtFailure-r16, beamFailureRecoveryFailure-r16, t312-Expiry-r16, spare5, spare4, spare3, spare2, spare1}, measResultSCG-EUTRA-r16 OCTET STRING } OPTIONAL, sidelinkUEInformationNR-r16 OCTET STRING (CONTAINING SidelinkUEInformationNR-r16) OPTIONAL, sidelinkUEInformationEUTRA-r16 OCTET STRING OPTIONAL, nonCriticalExtension CG-ConfigInfo-v1620-IEs OPTIONAL } CG-ConfigInfo-v1620-IEs ::= SEQUENCE { ueAssistanceInformationSourceSCG-r16 OCTET STRING (CONTAINING UEAssistanceInformation) OPTIONAL, nonCriticalExtension CG-ConfigInfo-v1640-IEs OPTIONAL } CG-ConfigInfo-v1640-IEs ::= SEQUENCE { servCellInfoListMCG-NR-r16 ServCellInfoListMCG-NR-r16 OPTIONAL, servCellInfoListMCG-EUTRA-r16 ServCellInfoListMCG-EUTRA-r16 OPTIONAL, nonCriticalExtension CG-ConfigInfo-v1700-IEs OPTIONAL } CG-ConfigInfo-v1700-IEs ::= SEQUENCE { candidateCellListCPC-r17 CandidateCellListCPC-r17 OPTIONAL, twoPHRModeMCG-r17 ENUMERATED {enabled} OPTIONAL, lowMobilityEvaluationConnectedInPCell-r17 ENUMERATED {enabled} OPTIONAL, nonCriticalExtension CG-ConfigInfo-v1730-IEs OPTIONAL } CG-ConfigInfo-v1730-IEs ::= SEQUENCE { fr1-Carriers-MCG-r17 INTEGER (1..32) OPTIONAL, fr2-Carriers-MCG-r17 INTEGER (1..32) OPTIONAL, nonCriticalExtension CG-ConfigInfo-v1800-IEs OPTIONAL } CG-ConfigInfo-v1800-IEs ::= SEQUENCE { musim-GapConfigInfo-r18 MUSIM-GapConfig-r17 OPTIONAL, musim-CapRestrictionInfo-r18 SEQUENCE { musim-CapRestriction-r18 MUSIM-CapRestriction-r18 OPTIONAL, musim-CandidateBandList-r18 MUSIM-CandidateBandList-r18 OPTIONAL } OPTIONAL, scpac-ReferenceConfiguration-r18 ReferenceConfiguration-r18 OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- Editor Note: FFS whether all fields in musim-CapRestriction should be sent to SN. ServCellInfoListMCG-NR-r16 ::= SEQUENCE (SIZE (1.. maxNrofServingCells)) OF ServCellInfoXCG-NR-r16 ServCellInfoListMCG-EUTRA-r16 ::= SEQUENCE (SIZE (1.. maxNrofServingCellsEUTRA)) OF ServCellInfoXCG-EUTRA-r16 SFTD-FrequencyList-NR ::= SEQUENCE (SIZE (1..maxCellSFTD)) OF ARFCN-ValueNR SFTD-FrequencyList-EUTRA ::= SEQUENCE (SIZE (1..maxCellSFTD)) OF ARFCN-ValueEUTRA ConfigRestrictInfoSCG ::= SEQUENCE { allowedBC-ListMRDC BandCombinationInfoList OPTIONAL, powerCoordination-FR1 SEQUENCE { p-maxNR-FR1 P-Max OPTIONAL, p-maxEUTRA P-Max OPTIONAL, p-maxUE-FR1 P-Max OPTIONAL } OPTIONAL, servCellIndexRangeSCG SEQUENCE { lowBound ServCellIndex, upBound ServCellIndex } OPTIONAL, -- Cond SN-AddMod maxMeasFreqsSCG INTEGER(1..maxMeasFreqsMN) OPTIONAL, dummy INTEGER(1..maxMeasIdentitiesMN) OPTIONAL, ..., [[ selectedBandEntriesMNList SEQUENCE (SIZE (1..maxBandComb)) OF SelectedBandEntriesMN OPTIONAL, pdcch-BlindDetectionSCG INTEGER (1..15) OPTIONAL, maxNumberROHC-ContextSessionsSN INTEGER(0.. 16384) OPTIONAL ]], [[ maxIntraFreqMeasIdentitiesSCG INTEGER(1..maxMeasIdentitiesMN) OPTIONAL, maxInterFreqMeasIdentitiesSCG INTEGER(1..maxMeasIdentitiesMN) OPTIONAL ]], [[ p-maxNR-FR1-MCG-r16 P-Max OPTIONAL, powerCoordination-FR2-r16 SEQUENCE { p-maxNR-FR2-MCG-r16 P-Max OPTIONAL, p-maxNR-FR2-SCG-r16 P-Max OPTIONAL, p-maxUE-FR2-r16 P-Max OPTIONAL } OPTIONAL, nrdc-PC-mode-FR1-r16 ENUMERATED {semi-static-mode1, semi-static-mode2, dynamic} OPTIONAL, nrdc-PC-mode-FR2-r16 ENUMERATED {semi-static-mode1, semi-static-mode2, dynamic} OPTIONAL, maxMeasSRS-ResourceSCG-r16 INTEGER(0..maxNrofCLI-SRS-Resources-r16) OPTIONAL, maxMeasCLI-ResourceSCG-r16 INTEGER(0..maxNrofCLI-RSSI-Resources-r16) OPTIONAL, maxNumberEHC-ContextsSN-r16 INTEGER(0..65536) OPTIONAL, allowedReducedConfigForOverheating-r16 OverheatingAssistance OPTIONAL, maxToffset-r16 T-Offset-r16 OPTIONAL ]], [[ allowedReducedConfigForOverheating-r17 OverheatingAssistance-r17 OPTIONAL, maxNumberUDC-DRB-r17 INTEGER(0..2) OPTIONAL, maxNumberCPCCandidates-r17 INTEGER(0..maxNrofCondCells-1-r17) OPTIONAL ]], [[ allowedResourceConfigNRDC-r17 ResourceConfigNRDC-r17 OPTIONAL ]] } SelectedBandEntriesMN ::= SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandEntryIndex BandEntryIndex ::= INTEGER (0.. maxNrofServingCells) PH-TypeListMCG ::= SEQUENCE (SIZE (1..maxNrofServingCells)) OF PH-InfoMCG PH-InfoMCG ::= SEQUENCE { servCellIndex ServCellIndex, ph-Uplink PH-UplinkCarrierMCG, ph-SupplementaryUplink PH-UplinkCarrierMCG OPTIONAL, ..., [[ twoSRS-PUSCH-Repetition-r17 ENUMERATED{enabled} OPTIONAL ]] } PH-UplinkCarrierMCG ::= SEQUENCE{ ph-Type1or3 ENUMERATED {type1, type3}, ... } BandCombinationInfoList ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombinationInfo BandCombinationInfo ::= SEQUENCE { bandCombinationIndex BandCombinationIndex, allowedFeatureSetsList SEQUENCE (SIZE (1..maxFeatureSetsPerBand)) OF FeatureSetEntryIndex } FeatureSetEntryIndex ::= INTEGER (1.. maxFeatureSetsPerBand) DRX-Info ::= SEQUENCE { drx-LongCycleStartOffset CHOICE { ms10 INTEGER(0..9), ms20 INTEGER(0..19), ms32 INTEGER(0..31), ms40 INTEGER(0..39), ms60 INTEGER(0..59), ms64 INTEGER(0..63), ms70 INTEGER(0..69), ms80 INTEGER(0..79), ms128 INTEGER(0..127), ms160 INTEGER(0..159), ms256 INTEGER(0..255), ms320 INTEGER(0..319), ms512 INTEGER(0..511), ms640 INTEGER(0..639), ms1024 INTEGER(0..1023), ms1280 INTEGER(0..1279), ms2048 INTEGER(0..2047), ms2560 INTEGER(0..2559), ms5120 INTEGER(0..5119), ms10240 INTEGER(0..10239) }, shortDRX SEQUENCE { drx-ShortCycle ENUMERATED { ms2, ms3, ms4, ms5, ms6, ms7, ms8, ms10, ms14, ms16, ms20, ms30, ms32, ms35, ms40, ms64, ms80, ms128, ms160, ms256, ms320, ms512, ms640, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 }, drx-ShortCycleTimer INTEGER (1..16) } OPTIONAL } DRX-Info2 ::= SEQUENCE { drx-onDurationTimer CHOICE { subMilliSeconds INTEGER (1..31), milliSeconds ENUMERATED { ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, ms80, ms100, ms200, ms300, ms400, ms500, ms600, ms800, ms1000, ms1200, ms1600, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 } } } MeasConfigMN ::= SEQUENCE { measuredFrequenciesMN SEQUENCE (SIZE (1..maxMeasFreqsMN)) OF NR-FreqInfo OPTIONAL, measGapConfig SetupRelease { GapConfig } OPTIONAL, gapPurpose ENUMERATED {perUE, perFR1} OPTIONAL, ..., [[ measGapConfigFR2 SetupRelease { GapConfig } OPTIONAL ]], [[ interFreqNoGap-r16 ENUMERATED {true} OPTIONAL ]] } MRDC-AssistanceInfo ::= SEQUENCE { affectedCarrierFreqCombInfoListMRDC SEQUENCE (SIZE (1..maxNrofCombIDC)) OF AffectedCarrierFreqCombInfoMRDC, ..., [[ overheatingAssistanceSCG-r16 OCTET STRING (CONTAINING OverheatingAssistance) OPTIONAL ]], [[ overheatingAssistanceSCG-FR2-2-r17 OCTET STRING (CONTAINING OverheatingAssistance-r17) OPTIONAL ]], [[ affectedCarrierFreqRangeCombList-r18 AffectedCarrierFreqRangeCombList-r18 OPTIONAL, affectedCarrierFreqCombList-r18 AffectedCarrierFreqCombList-r16 OPTIONAL, idc-TDM-Assistance-r18 IDC-TDM-Assistance-r18 OPTIONAL ]] } AffectedCarrierFreqCombInfoMRDC ::= SEQUENCE { victimSystemType VictimSystemType, interferenceDirectionMRDC ENUMERATED {eutra-nr, nr, other, utra-nr-other, nr-other, spare3, spare2, spare1}, affectedCarrierFreqCombMRDC SEQUENCE { affectedCarrierFreqCombEUTRA AffectedCarrierFreqCombEUTRA OPTIONAL, affectedCarrierFreqCombNR AffectedCarrierFreqCombNR } OPTIONAL } VictimSystemType ::= SEQUENCE { gps ENUMERATED {true} OPTIONAL, glonass ENUMERATED {true} OPTIONAL, bds ENUMERATED {true} OPTIONAL, galileo ENUMERATED {true} OPTIONAL, wlan ENUMERATED {true} OPTIONAL, bluetooth ENUMERATED {true} OPTIONAL } AffectedCarrierFreqCombEUTRA ::= SEQUENCE (SIZE (1..maxNrofServingCellsEUTRA)) OF ARFCN-ValueEUTRA AffectedCarrierFreqCombNR ::= SEQUENCE (SIZE (1..maxNrofServingCells)) OF ARFCN-ValueNR CandidateCellListCPC-r17 ::= SEQUENCE (SIZE (1..maxFreq)) OF CandidateCellCPC-r17 CandidateCellCPC-r17 ::= SEQUENCE { ssbFrequency-r17 ARFCN-ValueNR, candidateCellList-r17 SEQUENCE (SIZE (1..maxNrofCondCells-r16)) OF PhysCellId } -- TAG-CG-CONFIG-INFO-STOP -- ASN1STOP NOTE 3: The following table indicates per MN RAT and SN RAT whether RAT capabilities are included or not in ue-CapabilityInfo. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,306 | 4.8.1.2 Connection Suspend procedure | This procedure may be initiated by the serving NG-RAN node when the UE is in CM-CONNECTED and has at least one PDU session with active user plane connection and NG-eNB has received indication from the AMF that User Plane CIoT 5GS Optimisation, as defined in clause 5.31.18 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], is supported for the UE. Figure 4.8.1.2-1: NG-RAN initiated Connection Suspend procedure 1. NG-RAN to AMF: The NG-RAN sends the N2 Suspend Request message to the AMF, see TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10]. The AMF enters CM-IDLE with Suspend indicator. Context information related to the NGAP UE association, UE Context and PDU session context, necessary to resume the connection is stored in the UE, NG-RAN node and in the AMF. The NG-RAN may include the Suspend cause and the N2 SM information. If the UE is served by an NG-eNB that supports WUS, then the NG-eNB should include the Information On Recommended Cells And RAN nodes For Paging in the N2 Suspend Request message; otherwise NG-RAN may include the Information On Recommended Cells And NG-RAN For Paging in the N2 Suspend Request message. If available, the AMF shall store this information to be used when paging the UE. The NG-RAN includes Information for Enhanced Coverage, if available, in the N2 Suspend Request message. If Service Gap Control is being applied to the UE (see clause 4.3.17.9) and the Service Gap timer is not already running, the Service Gap timer shall be started in the AMF when entering CM-IDLE, unless the connection was initiated after a paging of an MT event, or after a mobility registration procedure without Follow-on Request indication or after a mobility registration procedure for regulatory prioritized services like Emergency services or exception reporting. 2. AMF to SMF: For each of the PDU Sessions in the N2 Suspend Request, the AMF invokes Nsmf_PDUSession_UpdateSMContext Request (PDU Session ID, Cause, Operation type, User Location Information, Age of Location Information, N2 SM Information (Secondary RAT usage data)). The Operation Type is set to "UP Suspend" to indicate suspend of user plane resources for the PDU Session. 3. SMF to UPF: N4 Session Modification Request (AN Tunnel Info to be suspended, Buffering on/off). The SMF initiates an N4 Session Modification procedure indicating the need to release the tunnel info of AN terminating N3 between AN and UPF. Buffering on/off indicates whether the UPF shall buffer incoming DL PDU or not. The UPF sends N4 Session Modification Response to acknowledge the SMF request. The SMF shall maintain the N3 tunnel info (including both AN Tunnel Info and the CN Tunnel Info). NOTE: The UPF maintains the CN tunnel info as it may receive uplink packets from the AN. 4. SMF to AMF: The SMF sends Nsmf_PDUSession_UpdateSMContext response to the AMF. 5. AMF to NG-RAN: After response for each PDU session in step 4, the AMF sends N2 Suspend Response to NG-RAN to successfully terminate the Connection Suspend procedure initiated by the NG-RAN, see TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10]. 6. The NG-RAN sends RRC message to suspend the RRC Connection towards the UE including UE Resume ID, see TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [46]). If Service Gap Control is applied for the UE (see clause 5.31.16 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) and the Service Gap timer is not already running, the Service Gap timer shall be started in the UE when entering CM-IDLE, unless the connection was initiated as a response to paging of an MT event, or after a mobility registration procedure without Follow-on Request Indication set or after a mobility registration procedure for regulatory prioritized services like Emergency services or exception reporting. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.8.1.2 |
4,307 | 5.2.12.2.6 Nudr_DM_Subscribe service operation | Service operation name: Nudr_DM_Subscribe. Description: NF service consumer performs the subscription to notification to data modified in the UDR. The events can be changes on existing data, addition of data. Inputs, Required: Data Set Identifier as defined in clause 5.2.12.2.1, Notification Target Address (+ Notification Correlation ID). Inputs, Optional: Target of Event Reporting as defined in clause 5.2.12.2.1, Data Subset Identifier(s) as defined in clause 5.2.12.2.1, Data Key(s), Subscription Correlation ID (in the case of modification of the event subscription). Outputs, Required: When the subscription is accepted: Subscription Correlation ID. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.12.2.6 |
4,308 | 7.1 Services and Functions | The main services and functions of the RRC sublayer over the Uu interface include: - Broadcast of System Information related to AS and NAS; - Paging initiated by 5GC or NG-RAN; - Establishment, maintenance and release of an RRC connection between the UE and NG-RAN including: - Addition, modification and release of carrier aggregation; - Addition, modification and release of Dual Connectivity in NR or between E-UTRA and NR. - Security functions including key management; - Establishment, configuration, maintenance and release of Signalling Radio Bearers (SRBs) and Data Radio Bearers (DRBs); - Mobility functions including: - Handover and context transfer; - UE cell selection and reselection and control of cell selection and reselection; - Inter-RAT mobility. - QoS management functions; - UE measurement reporting and control of the reporting; - Detection of and recovery from radio link failure; - NAS message transfer to/from NAS from/to UE. The sidelink specific services and functions of the RRC sublayer over the Uu interface include: - Configuration of sidelink resource allocation via system information or dedicated signalling; - Reporting of UE sidelink information; - Measurement configuration and reporting related to sidelink; - Reporting of UE assistance information for SL traffic pattern(s). | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 7.1 |
4,309 | .2 Delete Bearer Failure Indication | A Delete Bearer Failure Indication shall be sent on the S5/S8 interface by the PGW to the SGW and on the S11 interface by the SGW to the MME as part of failure of eNodeB requested bearer release or MME Initiated Dedicated Bearer Deactivation procedure. The message shall also be sent on the S5/S8 interface by the PGW to the SGW and on the S4 interface by the SGW to the SGSN as part of failure of MS and SGSN Initiated Bearer Deactivation procedure using S4. This message shall be sent back if none of the bearers (not even a single one) included in the Delete Bearer Command message could be deleted. The Cause IE indicates that the EPS bearer has not been deleted in the PGW. When the SGW receives a Delete Bearer Failure Indication message from the PGW with the TEID set to zero in the GTPv2 header and the Cause IE is set to "Context Not Found", which implies that the PDN connection does not exist in the PGW, the SGW may send a Delete Bearer Request message to delete the PDN connection towards the MME/SGSN after sending the Delete Bearer Failure Indication message. Possible Cause values are specified in Table 8.4-1. Message specific cause values are: - "Context not found" Table .2-1: Information Elements in a Delete Bearer Failure Indication Table .2-2: Bearer Context within Delete Bearer Failure Indication Table 7.2.17-3: Overload Control Information within Delete Bearer Failure Indication | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | .2 |
4,310 | 2.8.2.1.3 Mapping in the old MME | A new SGSN attempts to retrieve information regarding the UE, e.g. the IMSI, from the old MME. In order to find the UE context, the MME needs to map the RAI, P-TMSI (or TLLI) and the P-TMSI Signature (sent by the SGSN) to create the GUTI and compare it with the stored GUTI. The MME shall perform a reverse mapping to the mapping procedure specified in clause 2.8.2.1.2 "Mapping in the UE" (see 3GPP TS 29.060[ General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface ] [6] and 3GPP TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [88] for specifics of the messaging). For the reverse mapping, the E-UTRAN <MME Code> within the GUTI shall be set either to bits 23 to 16 of the GERAN/UTRAN <P-TMSI> (i.e., the NRI field) or to the GERAN/UTRAN <RAC>. For GERAN TLLI, the old MME replaces the two topmost bits of TLLI, received from new SGSN via GTPv1, with '11' before mapping the TLLI to the GUTI used for looking up the "UE Context". | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 2.8.2.1.3 |
4,311 | A.2 Cause related to subscription options | Cause #5 – PEI not accepted This cause is sent to the UE if the network does not accept an initial registration procedure for emergency services using a PEI. Cause #7 – 5GS services not allowed This 5GMM cause is sent to the UE when it is not allowed to operate 5GS services. Cause #11 – PLMN not allowed This 5GMM cause is sent to the UE if it requests service, or if the network initiates a de-registration request, in a PLMN where the UE, by subscription or due to operator determined barring, is not allowed to operate. This 5GMM cause can also be sent to the UE when the disaster condition is no longer being applicable in the current location of the UE. Cause #12 – Tracking area not allowed This 5GMM cause is sent to the UE if it requests service, or if the network initiates a de-registration request, in a tracking area where the HPLMN or SNPN determines that the UE, by subscription, is not allowed to operate. NOTE 1: If 5GMM 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 5GMM cause is sent to a UE which requests service, or if the network initiates a de-registration request, in a tracking area of a PLMN or SNPN which by subscription offers roaming to that UE but not in that tracking area. This 5GMM cause can also be sent to the UE when the disaster condition is no longer being applicable in the current location of the UE. Cause #15 – No suitable cells in tracking area This 5GMM cause is sent to the UE if it requests service, or if the network initiates a de-registration request, in a tracking area where the UE, by subscription, is not allowed to operate, but when it should find another allowed tracking area in the same PLMN or an equivalent PLMN or the same SNPN or an equivalent SNPN. NOTE 2: 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 or SNPN. Cause #27 – N1 mode not allowed This 5GMM cause is sent to the UE if it requests service, or if the network initiates a de-registration request, in a PLMN or SNPN where the UE by subscription or operator policy, is not allowed to operate in N1 mode. Cause #31 – Redirection to EPC required This 5GMM cause is sent to the UE if it requests service in a PLMN where the UE by operator policy, is not allowed in 5GCN and redirection to EPC is required. Cause #36 – IAB-node operation not authorized This 5GMM cause is sent to the UE if a UE operating as an IAB-node requests service, or if the network initiates a de-registration procedure, in a PLMN or SNPN where the UE by subscription is not authorized for IAB operation. Cause #72 – Non-3GPP access to 5GCN not allowed This 5GMM cause is sent to the UE if it requests accessing 5GCN over non-3GPP access in a PLMN or SNPN, where the UE by subscription, is not allowed to access 5GCN over non-3GPP access. Cause #74 – Temporarily not authorized for this SNPN This 5GMM cause is sent to the UE if it requests access, or if the network initiates a de-registration procedure, in a cell belonging to an SNPN for which the UE has no subscription to operate or for which the UE is not allowed to operate onboarding services. Cause #75 – Permanently not authorized for this SNPN This 5GMM cause is sent to the UE if it requests access, or if the network initiates a de-registration procedure, in a cell belonging to an SNPN with a globally-unique SNPN identity for which the UE either has no subscription to operate, the UE's subscription has expired or the UE is not allowed to operate onboarding services. Cause #76 – Not authorized for this CAG or authorized for CAG cells only This 5GMM cause is sent to the UE if the UE requests access or de-registration: i) in a CAG cell with a CAG-ID which is not authorized based on the UE's "allowed CAG list" for the PLMN; or ii) in a non-CAG cell, wherein the UE is only allowed to access 5GS via CAG cells Cause #77 – Wireline access area not allowed This 5GMM cause is sent to the 5G-RG or the W-AGF acting on behalf of the FN-CRG (or on behalf of the N5GC device) if the 5G-RG or the W-AGF acting on behalf of the FN-CRG (or on behalf of the N5GC device) request accessing 5GCN over a wireline access network belonging to a wireline access area, where the 5G-RG or the W-AGF acting on behalf of the FN-CRG (or on behalf of the N5GC device) are not allowed by subscription to access the 5GCN over the wireline access. Cause #79 – UAS services not allowed This 5GMM cause is sent to the UE to indicate that the request of UAS services is not allowed. Cause #80 – Disaster roaming for the determined PLMN with disaster condition not allowed This 5GMM cause is sent by the network in a PLMN where the UE has requested registration for disaster roaming service for the determined PLMN with disaster condition, but the AMF determines that it does not support providing disaster roaming services to the UE for the determined PLMN with disaster condition as roaming agreement for disaster roaming services with HPLMN of the UE does not exist, or the determined PLMN with disaster condition is a forbidden PLMN of the UE. Cause #94 – User plane positioning not authorized This 5GMM cause is sent to the UE if it requests the user plane positioning, where the UE by subscription is not authorized for user plane positioning. | 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 | A.2 |
4,312 | 8.2.2.2.6 Enhanced Performance Requirement Type B - 2 Tx Antenna Ports with TM2 interference model | The requirements are specified in Table 8.2.2.2.6-2, with the addition of parameters in Table 8.2.2.2.6-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of transmit diversity (SFBC) with 2 transmit antennas when the PDSCH transmission in the serving cell is interfered by PDSCH of two interfering cells applying transmission mode 2 interference model defined in clause B.6.1. In Table 8.2.2.2.6-1, Cell 1 is the serving cell, and Cell 2, 3 are interfering cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. Table 8.2.2.2.6-1: Test Parameters for Transmit Diversity Performance (FRC) with TM2 interference model Table 8.2.2.2.6-2: Minimum Performance for Enhanced Performance Requirement Type B, Transmit Diversity (FRC) with TM2 interference model | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.2.2.6 |
4,313 | – SON-Parameters | The IE SON-Parameters contains SON related parameters. SON-Parameters information element -- ASN1START -- TAG-SON-PARAMETERS-START SON-Parameters-r16 ::= SEQUENCE { rach-Report-r16 ENUMERATED {supported} OPTIONAL, ..., [[ rlfReportCHO-r17 ENUMERATED {supported} OPTIONAL, rlfReportDAPS-r17 ENUMERATED {supported} OPTIONAL, success-HO-Report-r17 ENUMERATED {supported} OPTIONAL, twoStepRACH-Report-r17 ENUMERATED {supported} OPTIONAL, pscell-MHI-Report-r17 ENUMERATED {supported} OPTIONAL, onDemandSI-Report-r17 ENUMERATED {supported} OPTIONAL ]], [[ spr-Report-r18 ENUMERATED {supported} OPTIONAL, successIRAT-HO-Report-r18 ENUMERATED {supported} OPTIONAL ]] } -- TAG-SON-PARAMETERS-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,314 | 16.10.5.3.2 Handover between Multicast supporting cells | Mobility procedures for multicast reception allow the UE to continue receiving multicast service(s) via PTM or PTP in a new cell after handover. During handover preparation phase, the source gNB transfers to the target gNB about the MBS multicast sessions the UE has joined in the UE context information. To support provision of local multicast service with location dependent content as specified in TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [45], for each active multicast session, service area information per Area Session ID may be provided to the target gNB. The source gNB may propose data forwarding for some MRBs to minimize data loss and may exchange the corresponding MRB PDCP Sequence Number with the target gNB during the handover preparation: - The lossless handover for multicast service is supported for the handover between MBS supporting cells if the UE is configured with PTP RLC AM entity in target cell MRB of a UE, regardless of whether the UE is configured with PTP RLC AM entity in the source cell or not. - In order to support lossless handover for multicast service, the network has to ensure DL PDCP COUNT value synchronization and continuity between the source cell and the target cell. Furthermore, data forwarding from the source gNB to the target gNB and/or PDCP status report provided by a UE for an MRB for multicast session can be used during lossless handover. For each multicast session with ongoing user data transmission for which no MBS Session Resources exist at the target gNB, the target gNB triggers the setup of MBS user plane resources towards the 5GC using the NGAP Distribution Setup procedure. If unicast transport is used, the target gNB provides the DL tunnel endpoint to be used to the MB-SMF. If multicast transport is used, the target gNB receives the IP multicast address from the MB-SMF. During handover execution, the MBS configuration decided at target gNB is sent to the UE via the source gNB within an RRC container as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]. The PDCP entities for multicast MRBs in the UE can either be re-established or remain as it is. When the UE connects to the target gNB, the target gNB sends an indication that it is an MBS-supporting node to the SMF in the Path Switch Request message (Xn handover) or Handover Request Acknowledge message (NG handover). Upon successful handover completion, the source gNB may trigger the release of the MBS user plane resources towards the 5GC using the NGAP Distribution Release procedure for any multicast session for which there is no remaining joined UE in the gNB. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.10.5.3.2 |
4,315 | 10 Multi-Connectivity operation related aspects 10.1 General | Similar procedures as defined under clause 10.1.2.8 (Dual Connectivity operation) in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [2] apply for MR-DC. Similar CHO principles as defined in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [2] and TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [3] apply for the Conditional PSCell Change and Conditional PSCell Addition in MR-DC. Similar LTM principles as defined in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [3] apply for MCG LTM and SCG LTM in NR-DC. MCG LTM with SCG release and MCG LTM without SCG change are supported. LTM for simultaneous PCell and PSCell change is not supported. Conditional PSCell Change and conditional PSCell addition are not supported for the MR-DC options NE-DC and NGEN-DC. Subsequent CPAC is only supported for NR-DC. Configuration of a deactivated SCG in a conditional configuration, configuration of CPC (or subsequent CPAC) while the SCG is deactivated and SCG deactivation while CPC (or subsequent CPAC) is configured are not supported. In MR-DC, CHO is supported in Master Node to eNB/gNB Change procedure and Conditional Handover with Secondary Node procedure. | 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 |
4,316 | 4.9.1.2.3 Xn based inter NG-RAN handover with insertion of intermediate UPF | This procedure is used to hand over a UE from a Source NG-RAN to a Target NG-RAN using Xn when the AMF is unchanged and the SMF decides that insertion of a new additional intermediate UPF is needed. If redundant transmission is performed for one or more QoS Flows of a PDU Session to be switched to the Target NG-RAN, the SMF may select two Intermediate UPFs (I-UPFs) and set up two N3 and N9 tunnels between the Target NG-RAN and the UPF (PSA) via the two I-UPFs as described in clause 5.33.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. In the case of using UL CL, the I-UPF can be regarded as UL CL and additional PSA providing local access to a DN. In the case of using Branching Point, the I-UPF can be regarded as BP. It is assumed that the PDU Session for the UE comprises of only one UPF that acts as a PDU Session Anchor at the time of this Handover procedure for non-roaming and local breakout roaming scenario. In the case of home routed roaming scenario, the PDU Session of the UE comprises of at least one UPF in the VPLMN and one UPF in the HPLMN at the time of this handover procedure. In this case, additional insertion of an N3 terminating intermediate UPF will not have impact on the connectivity between the UPF in VPLMN and UPF in HPLMN. The presence of IP connectivity between the UPF (PDU Session Anchor) and Source NG-RAN, between the UPF (PDU Session Anchor) and Target NG-RAN and between the intermediate UPF (I-UPF) and Target NG-RAN, is assumed. (If there is no IP connectivity between UPF (PDU Session Anchor) and Target NG-RAN, it is assumed that the N2-based handover procedure in clause 4.9.1.3 shall be used instead). The call flow is shown in figure 4.9.1.2.3-1. Figure 4.9.1.2.3-1: Xn based inter NG-RAN handover with insertion of intermediate UPF Steps 1-2 are the same as described in clause 4.9.1.2.2. 3a. [Conditional] SMF to UPF (PSA): N4 Session Modification Request. If the SMF selects a new UPF to act as intermediate UPF for the PDU Session and the different CN Tunnel Info need be used, the SMF sends N4 Session Modification Request message to UPF (PSA). 3b. [Conditional] UPF (PSA) to SMF: N4 Session Modification Response. The UPF (PSA) sends an N4 Session Modification Response message to the SMF. The UPF provides CN Tunnel Info (on N9) to the SMF. If redundant transmission is performed for one or more QoS Flows of the PDU Session, the UPF (PSA) provides two CN Tunnel Info (on N9) to the SMF and indicates the SMF that one CN Tunnel Info is used as redundancy tunnel of the PDU Session as described in in clause 5.33.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The UPF (PSA) associate the CN Tunnel Info (on N9) with UL Packet detection rules provided by the SMF. 4a. SMF to I-UPF: N4 Session Establishment Request (Target NG-RAN Tunnel Info, CN Tunnel Info of the PDU Session Anchor) For PDU Sessions to be updated, if the UE has moved out of the service area of UPF connecting to the serving NG-RAN node, the SMF then selects an 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 CN Tunnel Info of the PDU Session Anchor, which is used to setup N9 tunnel, is included in the N4 Session Establishment Request message. 4b. I-UPF to SMF: N4 Session Establishment Response. The I-UPF sends an N4 Session Establishment Response message to the SMF. The UL and DL CN Tunnel Info of I-UPF is sent to the SMF. If SMF select two Intermediate UPFs (I-UPFs) to perform redundant transmission for a PDU session, step 4a and 4b are performed between the SMF and each I-UPF. 5. SMF to PDU Session Anchor: N4 Session Modification Request (DL CN Tunnel Info of the I-UPF). The SMF sends N4 Session Modification Request message to the PDU Session Anchor. If a different CN Tunnel Info is used on N9 in UPF (PSA), the SMF starts a timer to release the CN Tunnel for N3. Otherwise the SMF does not need to start a timer to release the CN Tunnel Info used on N3 in UPF(PSA) (i.e. CN Tunnel Info is common for both N3 and N9). If redundant transmission is performed for one or more QoS Flows of the PDU Session, the SMF provides two DL CN Tunnel Info (for N9) to the UPF (PSA) and indicates to the UPF (PSA) one of the DL CN Tunnel Info is used as redundancy tunnel of the PDU Session. 6. PDU Session Anchor 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. 7. 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 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. SMF to AMF: Nsmf_PDUSession_UpdateSMContext Response (N2 SM Information (UL CN Tunnel Info of the I-UPF, updated QoS parameters for accepted QoS Flows)). The SMF sends an Nsmf_PDUSession_UpdateSMContext response to the AMF. Steps 8-11 are same as steps 6-9 defined in clause 4.9.1.2.2. 12. After the timer set in step 5 expires, the SMF informs the PDU Session Anchor to remove the CN Tunnel for N3 via N4 Session Modification procedure. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.9.1.2.3 |
4,317 | 6.3.1A.3 Service-level authentication and authorization procedure accepted by the UE | When the upper layers provide a service-level-AA payload, the UE shall create a SERVICE-LEVEL AUTHENTICATION COMPLETE message and set the service-level-AA payload of the Service-level-AA container IE to the service-level-AA payload received from the upper layers, and if the service-level-AA payload type is received in the SERVICE-LEVEL AUTHENTICATION COMMAND message from the SMF, set the service-level-AA payload type of the Service-level-AA container IE to the service-level-AA payload type received from the SMF. The UE shall transport the SERVICE-LEVEL AUTHENTICATION COMPLETE message and the PDU session ID, using the NAS transport procedure as specified in subclause 5.4.5. Apart from this action, the service-level authentication and authorization procedure initiated by the DN is transparent to the 5GSM layer of the UE. Upon receipt of a SERVICE-LEVEL AUTHENTICATION COMPLETE message, the SMF shall stop timer T3594 and provides the service-level-AA payload received in the Service-level-AA container IE of the SERVICE-LEVEL AUTHENTICATION COMPLETE message to the DN. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.3.1A.3 |
4,318 | 9.11.3.49 Service area list | The purpose of the Service area list information element is to transfer a list of allowed tracking areas for an allowed area or a list of non-allowed tracking areas for a non-allowed area from the network to the UE. The coding of the information element allows combining different types of lists. The lists of type "00" and "01" allow a more compact encoding, when the different TAIs are sharing the PLMN identity. The lists of type "11" indicate all TAIs of the PLMNs in the registration area are allowed area. The Service area list information element is coded as shown in figure 9.11.3.49.1, figure 9.11.3.49.2, figure 9.11.3.49.3, figure 9.11.3.49.4, figure 9.11.3.49.5 and table 9.11.3.49.1. The Service area list is a type 4 information element with a minimum length of 6 octets and a maximum length of 114 octets. The list can contain a maximum of 16 different tracking area identities. Figure 9.11.3.49.1: Service area list information element Figure 9.11.3.49.2: Partial service area list – type of list = "00" Figure 9.11.3.49.3: Partial service area list – type of list = "01" Figure 9.11.3.49.4: Partial service area list – type of list = "10" Figure 9.11.3.49.5: Partial service area list – type of list = "11" Table 9.11.3.49.1: Service area list 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.49 |
4,319 | 4.18.2.1 PFD management triggered by AF | Figure 4.18.2.1-1 procedure for PFD management via NEF (PFDF) triggered by AF 1. The AF invokes the Nnef_PFDManagement_Create/Update/Delete service. The Allowed Delay is an optional parameter. If the Allowed Delay is included, it indicates that the list of PFDs in this request should be provisioned within the time interval indicated by the Allowed Delay to the SMF(s) that have subscribed to the PFD management service using Nnef_PFDManagement_Subscribe service operation. 2. NEF checks whether the AF is authorized to perform this request and NEF (PFDF) checks if the AF is authorised to provision this PFD data based on the operator policies. Besides the information from the AF, the NEF may subscribe to the NWDAF to receive PFD Determination analytics defined in clause 6.16.3 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. 3. The NEF (PFDF) invokes the Nudr_DM_Create/Update/Delete (Application Identifier, one or more sets of PFDs, Allowed Delay) to the UDR. 4. The UDR updates the list of PFDs for the Application Identifier. 5. The UDR sends a Nudr_DM_Create/Update/Delete Response to the NEF (PFDF). 6. The NEF sends Nnef_PFDManagement_Create/Update/Delete Response to the Application Function. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.18.2.1 |
4,320 | 16.10 Multicast and Broadcast Services 16.10.1 General | NR system enables resource efficient delivery of multicast/broadcast services (MBS). For broadcast communication service, the same service and the same specific content data are provided simultaneously to all UEs in a geographical area (i.e., all UEs in the broadcast service area as defined in TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [45] are authorized to receive the data). A broadcast communication service is delivered to the UEs using a broadcast session. A UE can receive a broadcast communication service in RRC_IDLE, RRC_INACTIVE and RRC_CONNECTED state. For multicast communication service, the same service and the same specific content data are provided simultaneously to a dedicated set of UEs (i.e., not all UEs in the MBS service area as defined in TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [45] are authorized to receive the data). A multicast communication service is delivered to the UEs using a multicast session. A UE can receive a multicast communication service in RRC_CONNECTED state with mechanisms such as PTP and/or PTM delivery, as defined in clause 16.10.5.4. HARQ feedback/retransmission can be applied to both PTP and PTM transmission. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.10 |
4,321 | 5.4.5a Data Volume and Power Headroom Reporting | The Data Volume and Power Headroom reporting procedure is only applicable for NB-IoT UEs and is used to provide the serving eNB with information about the amount of data available for transmission in the UL buffers associated with the MAC entity, and to provide the serving eNB with information about the difference between the nominal UE maximum transmission power and the estimated transmission power for UL-SCH transmission for the Serving Cell. The reporting is done using the DPR MAC control element, which is sent in Msg3 together with a CCCH SDU. For EDT, the Data Volume in DPR MAC control element is set to zero. If enhancedPHR is configured and the UE supports extended power headroom reporting, the UE shall: - if the UE supports power class 14dBm and the MAC entity considers itself to be in enhanced coverage level other than 0: - report power headroom level using the DPR MAC control element; - else: - report extended power headroom level using the DPR MAC control element for Extended Power Headroom level reporting. | 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.4.5a |
4,322 | 8.2.4 Control Plane for untrusted non 3GPP Access | Figure 8.2.4-1: Control Plane before the signalling IPsec SA is established between UE and N3IWF Figure 8.2.4-2: Control Plane after the signalling IPsec SA is established between UE and N3IWF Large NAS messages may be fragmented by the "inner IP" layer or by TCP. Figure 8.2.4-3: Control Plane for establishment of user-plane via N3IWF In the above figures 8.2.4-1, 8.2.4-2 and 8.2.4-3, the UDP protocol may be used between the UE and N3IWF to enable NAT traversal for IKEv2 and IPsec traffic. The "signalling IPsec SA" is defined in clause 4.12.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") | 8.2.4 |
4,323 | 16.1.7 URLLC in Unlicensed Controlled Environment | URLLC services can be supported in shared spectrum where LBT failures are assumed to be not frequent. In this case, a channel access procedure for semi-static channel occupancy can be initiated by the gNB or the UE, or the gNB operates in dynamic channel access mode, as described in TS 37.213[ Physical layer procedures for shared spectrum channel access ] [37]. To handle potential LBT failures on configured grants (CG), the CG retransmission timer can be optionally configured to enable autonomous retransmissions, and it may be configured simultaneously with enhanced intra-UE overlapping resource prioritization mechanisms. When the CG retransmission timer is configured, the UE shall select the HARQ process for each CG resource by itself. If the enhanced intra-UE overlapping resource prioritization mechanisms is also configured, the UE may be further configured to select the HARQ process for a CG resource based on logical channel priority. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.1.7 |
4,324 | 10.5.7.2 Radio priority | The purpose of the radio priority information element is to specify the priority level that the MS shall use at the lower layers for transmission of data related to a PDP context or for mobile originated SMS transmission. The radio priority information element is coded as shown in figure 10.5.145/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.161/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The radio priority is a type 1 information element. Figure 10.5.145/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Radio priority information element Table 10.5.161/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Radio priority 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.7.2 |
4,325 | 6.2.2.2 Keys in the UE | For every key in a network entity, there is a corresponding key in the UE. Figure 6.2.2-2 shows the corresponding relations and derivations as performed in the UE. Figure 6.2.2-2: Key distribution and key derivation scheme for 5G for the UE Keys in the USIM The USIM shall store the same long-term key K that is stored in the ARPF. During an authentication and key agreement procedure, the USIM shall generate key material from K that it forwards to the ME. If provisioned by the home operator, the USIM shall store the Home Network Public Key used for concealing the SUPI. Keys in the ME The ME shall generate the KAUSF from the CK, IK received from the USIM. The generation of this key material is specific to the authentication method and is specified in clause 6.1.3. When 5G AKA is used, the generation of RES* from RES shall be performed by the ME. The UE shall store the latest KAUSF or replace the old KAUSF with the latest KAUSF, after successful completion of the latest primary authentication . If the USIM supports 5G parameters storage, KAUSF shall be stored in the USIM. Otherwise, KAUSF shall be stored in the non-volatile memory of the ME. In case 5G AKA is used as an authentication method, upon receiving the valid NAS Security Mode Command message from the AMF (to take the corresponding partial context derived from the newly generated KAUSF into use), the UE shall consider the performed primary authentication as successful and the UE shall store the newly generated KAUSF as the latest KAUSF or replace the old KAUSF with the latest KAUSF. In case of any key generating EAP method in the present document (EAP-AKA', EAP-TLS in Annex B, EAP methods in Annex I) is used as the authentication method for the primary (re)authentication, upon receiving the EAP-Success message, the primary authentication shall be considered as successful and the UE shall store the newly generated KAUSF as the latest KAUSF or replace the old KAUSF with the latest KAUSF. The ME shall perform the generation of KSEAF from the KAUSF. If the USIM supports 5G parameters storage, KSEAF shall be stored in the USIM. Otherwise, KSEAF shall be stored in the non-volatile memory of the ME. The ME shall perform the generation of KAMF. If the USIM supports 5G parameters storage, KAMF shall be stored in the USIM. Otherwise, KAMF shall be stored in the non-volatile memory of the ME. The ME shall perform the generation of all other subsequent keys that are derived from the KAMF. Any 5G security context, KAUSF and KSEAF that are stored at the ME shall be deleted from the ME if: a) the USIM is removed from the ME when the ME is in power on state; b) the ME is powered up and the ME discovers that the USIM is different from the one which was used to create the 5G security context; c) the ME is powered up and the ME discovers that there is no USIM is present at the ME. NOTE 1: The key derivation and distribution scheme for standalone non-public networks, when an authentication method other than 5G AKA or EAP-AKA' is used, is given in Annex I.2.3. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.2.2.2 |
4,326 | 8.3.1.14 Ethernet header compression configuration | The UE shall include the Ethernet header compression configuration IE if: - the PDU session type value of the PDU session type IE is set to "Ethernet"; - the UE indicated "Control Plane CIoT 5GS optimization supported" and "Ethernet header compression for control plane CIoT 5GS optimization supported" in the 5GMM capability IE of the REGISTRATION REQUEST message; and - the network indicated "Control plane CIoT 5GS optimization supported" and "Ethernet header compression for control plane CIoT 5GS optimization supported" in the 5GS network support feature IE of the REGISTRATION ACCEPT message. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 8.3.1.14 |
4,327 | 4.3.33.5 Paging Timing Collision Control | To avoid possible paging occasion collision and to enhance the likelihood that paging is received successfully for different USIMs, a Multi-USIM UE may provide, for at least one USIM, a Requested IMSI Offset value that is used for the determination of paging occasions. Upon reception of a Requested IMSI Offset value from UE in Attach Request or Tracking Area Update Request, a supporting MME provides an Accepted IMSI Offset value to the UE in the Attach Accept or Tracking Area Update Accept message to acknowledge it supports the feature and provide the accepted value. The Accepted IMSI Offset Value may be different from the Requested IMSI Offset provided by the UE. The Alternative IMSI value, determined as below, is stored in the UE context in the MME. If the UE does not provide any Requested IMSI Offset value in Attach Request or Tracking Area Request, the MME removes any stored Alternative IMSI value in the UE context. The UE and the network use the Accepted IMSI Offset to determine the paging occasion. The UE and MME use the Accepted IMSI Offset value to calculate the Alternative IMSI value that is determined based on UE's IMSI as follows: Alternative IMSI value = [MCC] [MNC] [(MSIN value + Accepted IMSI Offset) mod (MSIN address space)] where: the MCC, MNC and MSIN value are the fields of the UE's IMSI as defined in TS 23.003[ Numbering, addressing and identification ] [9]. The MME uses the Alternative IMSI value to compute the UE Identity Index Value. The MME sends the UE Identity Index Value to RAN in the Paging message (see TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]) for RAN to derive the paging occasions according to TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [34]. The UE uses the Alternative IMSI value for the determination of paging occasions as specified in TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [34]. NOTE 1: It is recommended to avoid excessive signalling load from UE due to this procedure. NOTE 2: The MME does not remove Alternative IMSI value if the Tracking Area Update Request is for periodic Tracking Area Update. | 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.33.5 |
4,328 | 4.5.6 Mapping between access categories/access identities and RRC establishment cause | When 5GMM requests the establishment of a NAS-signalling connection, the RRC establishment cause used by the UE shall be selected according to one or more access identities (see subclauses 4.5.2 and 4.5.2A) and the determined access category by checking the rules specified in table 4.5.6.1 and table 4.5.6.2. If the access attempt matches more than one rule, the RRC establishment cause of the lowest rule number shall be used. If the determined access category is an operator-defined access category, then the RRC establishment cause used by the UE shall be selected according to table 4.5.6.1 and table 4.5.6.2 based on one or more access identities (see subclauses 4.5.2 and 4.5.2A) and the standardized access category determined for the operator-defined access category as described in subclause 4.5.3. NOTE 1: Following an RRC release with redirection, the lower layers can set the RRC establishment cause or the resume cause to "mps-PriorityAccess" in the case of redirection to an NR cell connected to 5GCN (see 3GPP TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [30]) or to "highPriorityAccess" in the case of redirection to an E-UTRA cell connected to 5GCN (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [25A]), if the network indicates to the UE during RRC connection release with redirection that the UE has an active MPS session. NOTE 2: When the UE is acting as a 5G ProSe layer-2 UE-to-network relay UE, it is possible for the lower layer to decide an applicable RRC establishment cause according to the request from the 5G ProSe layer-2 remote UE or according to the indication from upper layers, including the case when the request from the 5G ProSe layer-2 remote UE is for emergency services, as specified in 3GPP TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [30]. Table 4.5.6.1: Mapping table for access identities/access categories and RRC establishment cause when establishing N1 NAS signalling connection via NR connected to 5GCN Table 4.5.6.2: Mapping table for access identities/access categories and RRC establishment cause when establishing N1 NAS signalling connection via E-UTRA connected to 5GCN | 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.5.6 |
4,329 | 5.3.15 CIoT EPS optimizations | CIoT EPS optimizations provide improved support of small data and SMS transfer. A UE supporting CIoT EPS optimizations can indicate the CIoT network behaviour the UE can support and prefers to use during attach or tracking area updating procedure (see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]). The UE may indicate the support for control plane CIoT EPS optimization, user plane CIoT EPS optimization, EMM-REGISTERED without PDN connection, S1-U data transfer and header compression (see clause 9.9.3.34). The UE may also request to use SMS transfer without combined attach procedure during the attach procedure. Furthermore, the UE may, separately from the indication of support, indicate preference for control plane CIoT EPS optimization or user plane CIoT EPS optimization (see clause 9.9.3.0B). The indication of preference is also considered as the request to use. A UE supporting CIoT 5GS optimizations can also indicate the 5GS CIoT network behaviour the UE can support during attach or tracking area updating procedure. Furthermore, the UE may, separately from the indication of support, indicate preference for control plane CIoT 5GS optimization or user plane CIoT 5GS optimization. NOTE 1: The UE supporting control plane CIoT EPS optimization and S1-U data transfer but not user plane CIoT EPS optimization does not indicate preference for user plane CIoT EPS optimization. The UE can be in NB-S1 mode or WB-S1 mode when requesting the use of CIoT EPS optimizations during an attach or tracking area updating procedure. A UE in NB-S1 mode always indicates support for control plane CIoT EPS optimization. A UE in NB-S1 mode can also request SMS transfer without combined procedure by using the normal attach or tracking area updating procedure (see clause 5.5.1 and 5.5.3). In NB-S1 mode, the UE, when requesting the use of CIoT EPS optimization, does not: - request an attach for emergency bearer services procedure; - request an attach procedure for initiating a PDN connection for emergency bearer services with attach type not set to "EPS emergency attach"; - indicate voice domain preference and UE's usage setting; or - request an attach for access to RLOS. The network does not indicate to the UE support of emergency bearer services when the UE is in NB-S1 mode (see clause 5.5.1.2.4 and 5.5.3.2.4). The control plane CIoT EPS optimization enables support of efficient transport of user data (IP, non-IP, Ethernet) or SMS messages over control plane via the MME without triggering data radio bearer establishment. The support of control plane CIoT EPS optimization is mandatory for the network in NB-S1 mode and optional in WB-S1 mode. Optional header compression of IP data can be applied to IP PDN type PDN connections that are configured to support header compression. The user plane CIoT EPS optimization enables support for change from EMM-IDLE mode to EMM-CONNECTED mode without the need for using the service request procedure (see clause 5.3.1.3). If the UE indicates support of EMM-REGISTERED without PDN connection in the attach request, the UE may include an ESM DUMMY MESSAGE instead of a PDN CONNECTIVITY REQUEST message as part of the attach procedure. If the EMM-REGISTERED without PDN connection is supported by the network, the UE and the network can at any time release all the PDN connections and the UE still remains EPS attached. NOTE 2: For both the UE and the network, the term "EMM-REGISTERED without PDN connection" is equivalent to the term "EPS attach without PDN connectivity" as specified in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]. In NB-S1 mode, if the UE indicates "SMS only" during a normal attach or tracking area updating procedure, the MME supporting CIoT EPS optimisations provides SMS so that the UE is not required to perform a combined attach or tracking area updating procedure. If the UE supports user plane CIoT EPS optimization, it shall also support S1-U data transfer. If the UE indicates support of one or more CIoT EPS optimizations and the network supports one or more CIoT EPS optimizations and decides to accept the attach or tracking area update request, the network indicates the supported CIoT EPS optimizations to the UE per TAI list when accepting the UE request. Network indication of support is interpreted by the UE as the acceptance to use the respective feature. After completion of the attach or tracking area updating procedure, the UE and the network can then use the accepted CIoT EPS optimizations for the transfer of user data (IP, non-IP, Ethernet and SMS). The UE supporting control plane CIoT EPS optimization may indicate support for control plane MT-EDT during the attach or tracking area updating procedure. For a UE that supports control plane MT-EDT and for which the network has accepted the use of control plane CIoT EPS optimization, the network may trigger the delivery of downlink data to the UE, when available, using procedures for control plane MT-EDT as specified in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]. The UE supporting user plane CIoT EPS optimization may indicate support for user plane MT-EDT during the attach or tracking area updating procedure. For a UE that supports user plane MT-EDT and for which the network has accepted the use of user plane CIoT EPS optimization, the network may trigger the delivery of downlink data to the UE, when available, using procedures for user plane MT-EDT as specified in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]. If the UE and the network support both the control plane CIoT EPS optimization and S1-U data transfer, then when receiving the UE's request for a PDN connection, the MME decides whether the PDN connection should be SCEF PDN connection or SGi PDN connection as specified in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]: - if SCEF PDN connection is to be established for non-IP data type, the MME shall include Control plane only indication for the requested PDN connection; - if SGi PDN connection is to be established and existing SGi PDN connections for this UE were established with Control plane only indication, the MME shall include Control plane only indication for the newly requested SGi PDN connection; - if SGi PDN connection is to be established and existing SGi PDN connections for this UE were established without Control plane only indication, the MME shall not include Control plane only indication for the newly requested SGi PDN connection; and - if SGi PDN connection is to be established and no SGi PDN connection for this UE exists, the MME determine whether to include Control plane only indication for the requested SGi PDN connection based on local policies, the UE's preferred CIoT network behaviour and the supported CIoT network behaviour. If the network supports user plane CIoT EPS optimization, it shall also support S1-U data transfer. Broadcast system information may provide information about support of CIoT EPS optimizations (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]). At reception of new broadcast system information, the lower layers deliver it to the EMM layer in the UE. The information provided by lower layers is per PLMN and used by the UE to determine whether certain CIoT EPS optimizations are supported in the cell. The UE shall not attempt to use CIoT EPS optimizations which are indicated as not supported. In NB-S1 mode, when the UE requests the lower layer to establish a RRC connection and the UE requests the use of EMM-REGISTERED without PDN connection or user plane CIoT EPS optimization, the UE shall pass an indication of the requested CIoT EPS optimizations to the lower layers. If the UE requests the use of S1-U data transfer without user plane CIoT optimization, then the UE shall also pass an indication of user plane CIoT EPS optimization to lower layers. In WB-S1 mode, when the UE requests the lower layer to establish a RRC connection and the UE requests the use of EMM-REGISTERED without PDN connection, control plane CIoT EPS optimization or user plane CIoT EPS optimization, the UE shall pass an indication of the requested CIoT EPS optimizations to the lower layers. | 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.15 |
4,330 | 5.4.1 Description | Some sort of infrastructure may be deployed in certain regions to ensure the safety of UAS operations outside of the airspace open to civil aviation. The purpose of such an infrastructure would be to provide control methods for enforcing flight restrictions on UAVs. Such an Unmanned Aerial System Traffic Management (UTM) server would require the ability to identify, locate, and instruct the UAS (via the UAV controller). The primary scope of the 3GPP involvement in such an Unmanned Aerial Vehicle Collision Avoidance System (UCAS) would be to provide accurate live positioning information into the UTM from the UAS or MNO, and to ensure timely feedback from the UTM to the UAS (via the UAV controller). Figure 5.4.1-1: Enforcement of no-fly zones | 3GPP TS 22.825 | Study on Remote Identification of Unmanned Aerial Systems (UAS) | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 5.4.1 |
4,331 | 6.9.4.3 NAS key refresh | If the AMF determines that NAS key refresh is required due to e.g. uplink or downlink NAS counter in the current security context is about to wrap around or based on a local operator policy to refresh the NAS keys after a certain time, the AMF may trigger a primary authentication run or may derive a new KAMF key using horizontal KAMF derivation upon the reception of an initial NAS message, e.g. a Registration Request or a Service Request using the uplink NAS COUNT value in the initial NAS message as described in clause 6.9.3 for mobility update registration. The AMF resets the corresponding uplink and downlink NAS counters and derive new NAS keys from the new KAMF key and the algorithms in use. The AMF activates the new KAMF key by running a NAS SMC with UE according to clause 6.7.2. When the new KAMF key is horizontally derived, the UE shall use the uplink NAS COUNT value that was sent in the initial NAS message to derive the same KAMF key as the AMF, reset the corresponding uplink and downlink NAS counters and then derive new NAS keys from the KAMF and the algorithms in use. In this case, if AS security is also established between the UE and gNB/ng-eNB, then the AMF and the UE shall derive a new initial KgNB from the new KAMF as specified in Annex A.9. Further, the AMF and the UE shall associate the derived new initial KgNB with a new NCC value equal to zero. Further, the derived new initial KgNB/KeNB is sent by the AMF to the gNB/ng-eNB triggering the gNB/ng-eNB to perform the AS key re-keying as described in clause 6.9.4.4. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.9.4.3 |
4,332 | 6.12.5 Subscription identifier de-concealing function (SIDF) | SIDF is responsible for de-concealing the SUPI from the SUCI. When the Home Network Public Key is used for encryption of SUPI, the SIDF shall use the Home Network Private Key that is securely stored in the home operator's network to decrypt the SUCI. The de-concealment shall take place at the UDM. Access rights to the SIDF shall be defined, such that only a network element of the home network is allowed to request SIDF. NOTE: One UDM can comprise several UDM instances. The Routing Indicator in the SUCI can be used to identify the right UDM instance that is capable of serving a subscriber. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.12.5 |
4,333 | 6.2.3D UE maximum output power for modulation / channel bandwidth for ProSe | When UE is configured for E-UTRA ProSe sidelink transmissions non-concurrent with E-UTRA uplink transmissions for E-UTRA ProSe operating bands specified in Table 5.5D-1, this subclause specifies the allowed Maximum Power Reduction (MPR) power for ProSe physical channels and signals due to higher order modulation and transmit bandwidth configuration (resource blocks). The allowed MPR for the maximum output power for ProSe physical channels PSDCH, PSCCH, PSSCH, and PSBCH shall be as specified in subclause 6.2.3 for PUSCH for the corresponding modulation and transmission bandwidth. The allowed MPR for the maximum output power for ProSe physical signal PSSS shall be as be as specified in subclause 6.2.3 for PUSCH QPSK modulation for the corresponding transmission bandwidth. The allowed MPR for the maximum output power for ProSe physical signal SSSS is specified in Table 6.2.3D-1. For a power class 2 capable UE operating on Band 41, the corresponding requirements for a power class 3 UE apply when an IE P-max as defined in [7] of 23 dBm or lower is indicated in the cell or if the uplink/downlink configuration is 0 or 6. For each supported frequency band other than Band 14 and Band 41, the UE shall: - if the UE supports a different power class than the default UE power class for the band and the supported power class enables the higher maximum output power than that of the default power class: - if the band is a TDD band whose frame configuration is 0 or 6; or - if the IE P-Max as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [7] is not provided; or - if the IE P-Max as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [7] is provided and set to the maximum output power of the default power class or lower; - meet all requirements for the default power class of the operating band in which the UE is operating and set its configured transmitted power as specified in sub-clause 6.2.5; - else (i.e the IE P-Max as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [7] is provided and set to the higher value than the maximum output power of the default power class): - meet all requirements for the supported power class and set its configured transmitted power class as specified in sub-clause 6.2.5. Table 6.2.3D-1: Maximum Power Reduction (MPR) for SSSS for Power Class 1, 2 and 3 When UE is configured for simultaneous E-UTRA ProSe sidelink and E-UTRA uplink transmissions for inter-band E-UTRA ProSe / E-UTRA bands specified in Table 5.5D-2, the requirements in subclause 6.2.3D apply for ProSe transmission and the requirements in subclause 6.2.3 apply for uplink transmission. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.2.3D |
4,334 | 4.2.7.1 N2 Configuration | At power up, restart and when modifications are applied, the 5G-AN node and AMF use non-UE related N2 signalling to exchange configuration data. Full details of this configuration data are specified in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10], but the following highlights some aspects. The AMF supplies the 5G-AN node with information about: a) the AMF Name and the GUAMI(s) configured on that AMF Name; b) the set of TNL associations to be established between the NG-RAN node and the AMF; c) weight factor associated with each of the TNL association within the AMF; and d) weight factor for each AMF Name within the AMF Set; and e) (optional) for each GUAMI(s) configured on that AMF the corresponding backup AMF Name. The weight factors are used for load distribution of the initial N2 messages. The AMF chooses whether or not to use the same TNL association for the initial N2 message and subsequent messages for that UE. TNL associations configured with a weight factor set to zero are not permitted for the initial N2 message, but can be used for subsequent N2 messages. Deployments that rely solely on 5GC-based load balancing can set the weight factors associated with TNL associations that are permitted for the initial N2 message to the same value. The 5G-AN supplies over N2 the AMF with information about the Tracking Area(s) it serves and the S-NSSAI(s) it supports in each of these Tracking Areas. See clause 5.3.2.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.7.1 |
4,335 | 6.6.4.2 UE initiated transport of user data via the control plane | Upon receipt of a request to transfer user data via the control plane, if the UE is in EMM-CONNECTED mode, the UE initiates the procedure by sending the ESM DATA TRANSPORT message including the user data to be sent in the User data container IE (see example in figure 6.6.4.2.1). The length of the value part of the User data container IE should not exceed the link MTU size for the respective type of user data (IPv4, IPv6 or Non-IP). If the user data in the value part of the User data container IE is an Ethernet frame, then the length of the Ethernet frame payload should not exceed the Ethernet frame payload MTU size. NOTE: The recommended maximum size for link MTU is 1358 octets to prevent fragmentation in the backbone network (see 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74]). Depending on the network configuration, setting link MTU size to a value larger than 1358 octets could lead to inefficient core network implementation due to fragmentation. If the UE is in EMM-IDLE mode, the UE initiates the procedure by sending the ESM DATA TRANSPORT message included in a CONTROL PLANE SERVICE REQUEST message. Based on information provided by the upper layers, the UE may include a Release assistance indication IE in the ESM DATA TRANSPORT message to inform the network that 1) subsequent to the current uplink data transmission no further uplink or downlink data transmission (e.g. an acknowledgement or response) is expected; i.e. the upper layers indicated that data exchanges have completed with the current UL data transfer; or 2) subsequent to the current uplink data transmission only a single downlink data transmission and no further uplink data transmission is expected; i.e. the upper layers indicated that data exchanges will have completed with the next downlink data transmission. When receiving the ESM DATA TRANSPORT message, the MME shall identify the PDN connection to the SCEF or to the PDN GW, based on the EPS bearer identity included in message, and forward the contents of the User data container IE accordingly. If the ESM DATA TRANSPORT message includes a Release assistance indication IE, then ESM layer indicates to the EMM layer to initiate release of the NAS signalling connection, 1) if the release assistance indication indicates that no further uplink and no further downlink data transmission subsequent to the uplink data transmission is expected; or 2) upon subsequent delivery of the next received downlink data transmission to the UE if the release assistance indication indicates that only a single downlink data transmission and no further uplink data transmission subsequent to the uplink data transmission is expected. Figure 6.6.4.2.1: UE initiated transport of user data via the control plane procedure | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.6.4.2 |
4,336 | 10.16.2 Inter-system handover from EPS to 5GS with the Secondary Node used as target | Inter-system handover from EPS to 5GS with the Secondary Node used as target refers to a deployment scenario where the source en-gNB and the target gNB are realised within the same network entity. Figure 10.16.2-1: Inter-system handover from EPS to 5GS with the Secondary Node used as target - Step 1: The (source) eNB, performing EN-DC with the (source) en-gNB triggers handover preparation including the SgNB UE X2AP ID within the Source NG-RAN to Target NG-RAN Transparent Container. - Step 2: The target gNB infers from the received SgNB UE X2AP ID in the Handover Request message that direct data forwarding can be performed in a node-internal way. - Step 3: DL UP data is forwarded in a node-internal way for the SN terminated bearers. - Step 4: After the end marker has arrived from the SGW, the (target) gNB processes UP data from the UPF. | 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.16.2 |
4,337 | 13.3.1.2 Indirect communication | In indirect communication, NF and NRF shall use one of the following methods for authentication: - Mutual authentication between NF and NRF provided by the transport layer protection solution. - Client credentials assertion (CCA) based authentication as specified in clause 13.3.8. NOTE 1: Client credentials assertion authentication is based on a CCA token sent by the NF Service Consumer to the NRF via an intermediate such as the SCP. CCA based authentication does not provide authentication of the NRF towards the NF Service Consumer or protection of the service request sent by the NF Service Consumer to the NRF. - Implicit, i.e. by relying on authentication between NF Service Consumer and SCP, and between SCP and NRF, provided by the hop-by-hop security protection at the transport layer, NDS/IP, or physical security. NOTE 2: Mutual authentication between NF Service Consumer and NRF is not achieved with hop-by-hop security. NOTE 3: If only hop-by-hop security is used in a PLMN, the NRF is not able to verify that an access token request sent by SCP on behalf of a certain NF Service Consumer, is actually authorized by this consumer. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.3.1.2 |
4,338 | 4.15.9.3.4 Time synchronization service deactivation | Figure 4.15.9.3.4-1: Time synchronization service deactivation 1. To remove an existing time synchronization service configuration of the PTP instance, the AF invokes a Nnef_TimeSynchronization_ConfigDelete service operation providing the corresponding PTP instance reference. 2. The NEF invokes the Ntsctsf_TimeSynchronization_ConfigDelete service operation with the corresponding TSCTSF. The AF that is part of operator's trust domain may invoke the services directly with TSCTSF. The TSCTSF may also invoke the Ntsctsf_TimeSynchronization_ConfigDelete service operation when it determines (based on notifications from the AMF(s), see steps 3-7 of clause 4.15.9.3.2) that the UE(s) are outside the Spatial validity condition. 3. The TSCTSF responds with the Ntsctsf_TimeSynchronization_ConfigDelete response. 4. The NEF responds with the Nnef_TimeSynchronization_ConfigDelete response. 5-6. The TSCTSF uses the PTP instance reference included in the Ntsctsf_TimeSynchronization_ConfigDelete request to identify the time synchronization service configuration and the corresponding AF sessions. The TSCTSF uses the procedures described in clause K.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] to disable the corresponding PTP instance(s) in the DS-TT(s) and NW-TT. The TSCTSF deletes the time synchronization service configuration for the respective PTP instance. The TSCTSF uses the procedure in clause 4.15.9.4 to deactivate the 5G access stratum time distribution for the UEs that are part of the impacted PTP instance. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.9.3.4 |
4,339 | 5.3.5.6 Radio Bearer configuration 5.3.5.6.1 General | The UE shall perform the following actions based on a received RadioBearerConfig IE: 1> if the RadioBearerConfig includes the srb3-ToRelease, srb4-ToRelease or srb5-ToRelease: 2> perform the SRB release as specified in 5.3.5.6.2; 1> if the RadioBearerConfig includes the srb-ToAddModList or if any DAPS bearer is configured: 2> perform the SRB addition or reconfiguration as specified in 5.3.5.6.3; 1> if the RadioBearerConfig includes the drb-ToReleaseList: 2> perform DRB release as specified in 5.3.5.6.4; 1> if the RadioBearerConfig includes the drb-ToAddModList: 2> perform DRB addition or reconfiguration as specified in 5.3.5.6.5; 1> if the RadioBearerConfig includes the mrb-ToReleaseList: 2> perform multicast MRB release as specified in 5.3.5.6.6; 1> if the RadioBearerConfig includes the mrb-ToAddModList: 2> perform multicast MRB addition or reconfiguration as specified in 5.3.5.6.7; 1> release all SDAP entities established for the PDU sessions, if any, that have no associated DRB as specified in TS 37.324[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Service Data Adaptation Protocol (SDAP) specification ] [24] clause 5.1.2, and indicate the release of the user plane resources for PDU Sessions associated with the released SDAP entities to upper layers; 1> release all SDAP entities established for the MBS multicast sessions, if any, that have no associated multicast MRB as specified in TS 37.324[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Service Data Adaptation Protocol (SDAP) specification ] [24] clause 5.1.2, and indicate the release of user plane resources for these MBS multicast sessions to upper layers. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.6 |
4,340 | 5.8 Sidelink 5.8.1 General | NR sidelink communication consists of unicast, groupcast and broadcast. For unicast, the PC5-RRC connection is a logical connection between a pair of a Source Layer-2 ID and a Destination Layer-2 ID in the AS. The PC5-RRC signalling, as specified in clause 5.8.9, can be initiated after its corresponding PC5 unicast link establishment (TS 23.287[ Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services ] [55]). The PC5-RRC connection and the corresponding sidelink SRBs and sidelink DRB(s) are released when the PC5 unicast link is released as indicated by upper layers. For each PC5-RRC connection of unicast, one sidelink SRB (i.e. SL-SRB0) is used to transmit the PC5-S message(s) before the PC5-S security has been established. One sidelink SRB (i.e. SL-SRB1) is used to transmit the PC5-S messages to establish the PC5-S security. One sidelink SRB (i.e. SL-SRB2) is used to transmit the PC5-S messages after the PC5-S security has been established, which is protected. One sidelink SRB (i.e. SL-SRB3) is used to transmit the PC5-RRC signalling, which is protected and only sent after the PC5-S security has been established. One sidelink SRB (i.e. SL-SRB4) is used to transmit/receive the NR sidelink discovery messages. For unicast of NR sidelink communication, AS security comprises of integrity protection of PC5 signalling (SL-SRB1, SL-SRB2 and SL-SRB3) and user data (SL-DRBs), and it further comprises of ciphering of PC5 signaling (SL-SRB1 only for the Direct Link Security Mode Complete message as specified in TS 24.587[ Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3 ] [57] for V2X service or TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [72] for Proximity-services, SL-SRB2 and SL-SRB3) and user data (SL-DRBs). The ciphering and integrity protection algorithms and parameters for a PC5 unicast link are exchanged by PC5-S messages in the upper layers as specified in TS 33.536[ Security aspects of 3GPP support for advanced Vehicle-to-Everything (V2X) services ] [60], and applied to the corresponding PC5-RRC connection in the AS. Once AS security is activated for a PC5 unicast link in the upper layers as specified in TS 33.536[ Security aspects of 3GPP support for advanced Vehicle-to-Everything (V2X) services ] [60], all messages on SL-SRB2 and SL-SRB3 and/or user data on SL-DRBs of the corresponding PC5-RRC connection are integrity protected and/or ciphered by the PDCP. For unicast of NR sidelink communication, if the change of the key is indicated by the upper layers as specified in TS 24.587[ Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3 ] [57] or TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [72], UE re-establishes the PDCP entity of the SL-SRB1, SL-SRB2, SL-SRB3 and SL-DRBs on the corresponding PC5-RRC connection. NOTE 1: In case the configurations for NR sidelink communication are acquired via the E-UTRA, the configurations for NR sidelink communication in SIB12 and sl-ConfigDedicatedNR within RRCReconfiguration used in clause 5.8 are provided by the configurations in SystemInformationBlockType28 and sl-ConfigDedicatedForNR within RRCConnectionReconfiguration as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], respectively. NOTE 2: In this release, there is one-to-one correspondence between the PC5-RRC connection and the PC5 unicast link as specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [2]. NOTE 3: All SL-DRBs related to the same PC5-RRC connection have the same activation/deactivation setting for ciphering and the same activation/deactivation setting for integrity protection as specified in TS 33.536[ Security aspects of 3GPP support for advanced Vehicle-to-Everything (V2X) services ] [60]. NOTE 4: When integrity check failure concerning SL-SRB1 for a specific destination is detected, the UE sends an indication to the upper layers [57]. NOTE 5: The selection of NULL algorithms means that the PC5 messages are considered protected for the purposes of being allowed to be sent or received. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8 |
4,341 | 6.15a.4.2 Requirements | Subject to operator's policy, the 5G network shall support energy consumption monitoring at per network slice and per subscriber granularity. NOTE 1: Energy consumption monitoring as described in the preceding requirement is done by means of averaging or applying a statistical model. The requirement does not imply that some form of 'real time' monitoring is required. The granularity of the subscription policies can either apply to the subscriber (all services), or to particular services. Subject to operator’s policy and agreement with 3rd party, the 5G system shall be able to monitor energy consumption for serving this 3rd party. NOTE 2: The granularity of energy consumption measurement could vary according to different situations, for example, when several services share a same network slice, etc. NOTE 3: The energy consumption information can be related to the network resources of network slice, NPNs, etc. Subject to operator policy and regulatory requirements, the 5G system shall be able to monitor the energy consumption for serving the 3rd party, together with the network performance statistic information for the services provided by that network, related to same time interval e.g. hourly or daily. NOTE 4: The network performance statistic information could be the data rate, packet delay and packet loss, etc. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.15a.4.2 |
4,342 | – CSI-ReportSubConfigTriggerList | The IE CSI-ReportSubConfigTriggerList is used to configure a list of sub-configuration ID(s) of N sub-configurations out of L configured sub-configurations within a CSI-ReportConfig associated with a triggering state for semi-persistent CSI reporting on PUSCH and aperiodic CSI reporting. CSI-ReportSubConfigTriggerList information element -- ASN1START -- TAG-CSI-REPORTSUBCONFIGTRIGGERLIST-START CSI-ReportSubConfigTriggerList-r18 ::= SEQUENCE (SIZE(1..maxNrofCSI-ReportSubconfigPerCSI-ReportConfig-r18)) OF CSI-ReportSubConfigId-r18 -- TAG-CSI-REPORTSUBCONFIGTRIGGERLIST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,343 | 4.3.1.4.2 Successful outgoing intra-frequency handovers | This measurement provides the number of successful outgoing intra-frequency handovers. CC. Receipt of a RRC message RRCConnectionReconfigurationComplete sent from the UE to the target (=source) eNB/RN, indicating a successful outgoing intra-eNB/RN intra-frequency handover (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]), orreceipt at the source eNB/RN of UE CONTEXT RELEASE [10] over the X2 from the target eNB or DeNB following a successful inter-eNB intra-frequency handover, or if handover is performed via S1, receipt of UE CONTEXT RELEASE COMMAND[9] at the source eNB following a successful inter-eNB intra-frequency handover. A single integer value. HO.IntraFreqOutSucc EUtranCellFDD EUtranCellTDD Valid for packet switched traffic 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.3.1.4.2 |
4,344 | 11.2 PDN Interworking Model | The Packet Domain can interwork with IP networks and networks handling Non-IP data services. When interworking with the IP networks, the Packet Domain can operate IPv4 and/or IPv6. The interworking point with the IP networks or networks handling Non-IP data services is at the Gi and Sgi reference point. Additionally, the interworking point with network handling Non-IP data services may also be the T6a (T6) reference point for Control Plane CIoT EPS Optimizations (see 3GPP TS 29.128[ Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) interfaces for interworking with packet data networks and applications ] [110]) . These interworking points are shown in figure 7. Figure 7: IP network interworking The GGSN/P-GW for interworking with the IP network is the access point of the Packet Domain (see figure 8). In this case the Packet Domain network will look like any other IP network or subnetwork. Figure 8: The protocol stacks of GGSN and P-GW for the IP network interworking Typically in the IP networks, the interworking with subnetworks is done via IP routers. The Gi reference point is between the GGSN and the external IP network; and the Sgi reference point is between the P-GW and the external IP network. From the external IP network’s point of view, the GGSN/P-GW is seen as a normal IP router. The L2 and L1 layers are operator specific. It is out of the scope of the present document to standardise the router functions and the used protocols in the Gi/Sgi reference point. Interworking with user defined ISPs and private/public IP networks is subject to interconnect agreements between the network operators. No user data or header compression is done in the GGSN/P-GW. Both the GGSN/P-GW (for both Control Plane and User Plane CIoT EPS Optimizations) and the SCEF (for Control Plane CIoT EPS Optimization) for interworking with the network handling Non-IP data services are the access points of the Packet Domain. See 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [77] and 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [3] for further details. | 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 | 11.2 |
4,345 | 20.2 MBMS session start / update/ stop | The MBMS session start shall be used by the BM-SC to trigger the bearer resource establishment and announce the arrival of data for a MBMS bearer service (along with the attributes of the data to be delivered e.g. QoS, MBMS service area, or MBMS-Cell-List) to every MBMS GW that will deliver the MBMS bearer service. The MBMS session update shall be used by the BM-SC to trigger the update of MBMS session attributes in the affected MBMS GWs. The attributes that can be modified are the MBMS service area, the MBMS-Cell-List and the list of MBMS control plane nodes (MMEs, SGSNs). The MBMS session stop shall be used by the BM-SC to indicate the end of the data stream for an MBMS bearer service to every MBMS GW that has been delivering the MBMS bearer service. | 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 | 20.2 |
4,346 | 9.3.3.1 Data Forwarding for the Control Plane | Control plane handling for inter-System data forwarding from EPS to 5GS follows the following key principles: - Only forwarding of downlink data is supported. - The target NG-RAN node receives in the Handover Request message the mapping between E-RAB ID(s) and QoS Flow ID(s). It decides whether to accept the data forwarding for E-RAB IDs proposed for forwarding within the Source NG-RAN Node to Target NG-RAN Node Transparent Container. Based on availability of direct data forwarding path the source eNB may request to apply direct data forwarding by indicating direct data forwarding availability to the CN. - In case of indirect data forwarding: - The target NG-RAN node assigns a TEID/TNL address for each PDU session for which at least one QoS flow is involved in the accepted data forwarding. - The target NG-RAN node sends the Handover Request Acknowledge message in which it indicates the list of PDU sessions and QoS flows for which it has accepted the data forwarding. - A single data forwarding tunnel is established between the UPF and the target NG-RAN node per PDU session for which at least data for a single QoS Flow is subject to data forwarding. - The source eNB receives in the Handover Command message the list of E-RAB IDs for which the target NG-RAN node has accepted data forwarding of corresponding PDU sessions and QoS flows. - In case of direct data forwarding: - The source eNB indicates direct path availability to the CN. The source eNB's decision is indicated by the CN to the target NG-RAN node. - The target NG-RAN node assigns a TEID/TNL address for each E-RAB it accepted for data forwarding. - The source eNB receives in the Handover Command message the list of E-RAB IDs for which the target NG-RAN node has accepted data forwarding. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 9.3.3.1 |
4,347 | 9.11.3.83 List of PLMNs to be used in disaster condition | The purpose of the list of PLMNs to be used in disaster condition information element is to provide the "list of PLMN(s) to be used in disaster condition" associated with the serving PLMN to the UE. The list of PLMNs to be used in disaster condition information element is coded as shown in figures 9.11.3.83.1 and 9.11.3.83.2 and table 9.11.3.83.1. The list of PLMNs to be used in disaster condition is a type 4 information element, with a minimum length of 2 octets. Figure 9.11.3.83.1: List of PLMNs to be used in disaster condition information element Figure 9.11.3.83.2: PLMN ID n Table 9.11.3.83.1: List of PLMNs to be used in disaster condition 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.83 |
4,348 | 9.11.3.53A UE parameters update transparent container | The purpose of the UE parameters update transparent container when sent from the network to the UE is to provide UE parameters update data, optional acknowledgement request and optional re-registration request. The purpose of the UE parameters update transparent container when sent from the UE to the network is to indicate the UE acknowledgement of successful reception of the UE parameters update transparent container. The UE parameters update transparent container information element is coded as shown in figure 9.11.3.53A.1, figure 9.11.3.53A.2, figure 9.11.3.53A.3, figure 9.11.3.53A.4, figure 9.11.3.53A.4B, figure 9.11.3.53A.5, figure 9.11.3.53A.6, figure 9.11.3.53A.7 and table 9.11.3.53A.1. The UE parameters update transparent container is a type 6 information element with a minimum length of 20 octets. Figure 9.11.3.53A.1: UE parameters update transparent container information element for UE parameters update data type with value "0" Figure 9.11.3.53A.2: UE parameters update list Figure 9.11.3.53A.3: UE parameters update data set for UE parameters update data set type with value "0001" Figure 9.11.3.53A.4: UE parameters update data set for UE parameters update data set type with value "0010" Figure 9.11.3.53A.4A: UE parameters update data set for UE parameters update data set type with value "0011" Figure 9.11.3.53A.4B: UE parameters update data set for UE parameters update data set type with value "0100" Figure 9.11.3.53A.5: UE parameters update transparent container information element for UE parameters update data type with value "1" Figure 9.11.3.53A.6: UE parameters update header for UE parameters update data type with value "0" Figure 9.11.3.53A.7: UE parameters update header for UE parameters update data type with value "1" Table 9.11.3.53A.1: UE parameters update transparent container 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.53A |
4,349 | 5.5F Operating bands for category NB1 and NB2 | Category NB1 and NB2 are designed to operate in the E-UTRA operating bands 1, 2, 3, 4, 5, 7, 8, 11, 12, 13, 14, 17, 18, 19, 20, 21, 24, 25, 26, 28, 31, 41, 42, 43, 48, 54, 65, 66, 70, 71, 72, 73, 74, 85, 87, 88, 103 and 106 which are defined in Table 5.5-1. Category NB1 and NB2 are designed to operate in the NR operating bands n1, n2, n3, n5, n7, n8, n12, n14, n18, n20, n24, n25, n26, n28, n31, n41, n54, n65, n66, n70, n71, n72, n74, n90. Category NB1 and NB2 systems operate in HD-FDD duplex mode or in TDD mode. In case UE receives network signaling value NS_04 or NS_06 on any of the operating bands listed in Table 5.5F-1 then the lower and upper limit of those bands are shown in Table 5.5F-1 to account for the USA emission requirements. Table 5.5F-1 E-UTRA operating bands for NB-IoT in the USA | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.5F |
4,350 | 28.15.2 NAI format for SUPI containing a GCI | A SUPI containing a GCI shall take the form of a Network Access Identifier (NAI). The NAI for SUPI shall have the form username@realm as specified in clause 2.2 of IETF RFC 7542 [126], where: - the username part shall be the GCI, as defined in clause 28.15.4; - the realm part shall identify the operator owning the subscription; if the operator owns a PLMN ID, the realm part should be in the form: "5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org" EXAMPLE 1: [email protected] EXAMPLE 2: [email protected] | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.15.2 |
4,351 | 4.23.4.4 Network Triggered Service Request | For network triggered service request procedure, if the procedure is triggered by downlink packet, the procedure in clause 4.2.3.3 are impacted as following: - if the I-SMF is available for the PDU Session, the procedure is triggered by I-SMF. Correspondingly, the SMF in that procedure is replaced by the I-SMF. - The referenced clause 4.4.4 for pause of charging is changed to clause 4.23.14. - Step 4a: - If I-SMF is not available for the PDU Session and no I-SMF insertion is needed, no additional change is needed. - If I-SMF is available for the PDU Session and no I-SMF change or removal is needed, steps 12 to 22 in clause 4.23.4.2 is performed where the SMF in that procedure is replaced by the I-SMF. - If I-SMF will be inserted, changed or removed, steps 2 to 25 in clause 4.23.4.3 is performed. - Step 6: If the UE is in CM-IDLE state in 3GPP access, upon reception of paging request for a PDU Session associated to 3GPP access: - If I-SMF is not available for the PDU Session and no I-SMF insertion is needed, no additional change is needed. - If I-SMF is available for the PDU Session and no I-SMF change or removal is needed, UE Triggered Service Request procedure as defined in clause 4.23.4.2 is performed. - If I-SMF will be inserted, changed or removed, UE Triggered Service Request procedure as defined in clause 4.23.4.3 is performed. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.4.4 |
4,352 | – MeasResultIdleEUTRA | The IE MeasResultIdleEUTRA covers the E-UTRA measurement results performed in RRC_IDLE and RRC_INACTIVE. MeasResultIdleEUTRA information element -- ASN1START -- TAG-MEASRESULTIDLEEUTRA-START MeasResultIdleEUTRA-r16 ::= SEQUENCE { measResultsPerCarrierListIdleEUTRA-r16 SEQUENCE (SIZE (1.. maxFreqIdle-r16)) OF MeasResultsPerCarrierIdleEUTRA-r16, ... } MeasResultsPerCarrierIdleEUTRA-r16 ::= SEQUENCE { carrierFreqEUTRA-r16 ARFCN-ValueEUTRA, measResultsPerCellListIdleEUTRA-r16 SEQUENCE (SIZE (1..maxCellMeasIdle-r16)) OF MeasResultsPerCellIdleEUTRA-r16, ... } MeasResultsPerCellIdleEUTRA-r16 ::= SEQUENCE { eutra-PhysCellId-r16 EUTRA-PhysCellId, measIdleResultEUTRA-r16 SEQUENCE { rsrp-ResultEUTRA-r16 RSRP-RangeEUTRA OPTIONAL, rsrq-ResultEUTRA-r16 RSRQ-RangeEUTRA-r16 OPTIONAL }, ... } -- TAG-MEASRESULTIDLEEUTRA-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,353 | D.4.3.1.1 Charging Trigger Function | For a service utilizing the distributed CTF, the CTF is divided into two functional blocks as described in clause 4.3.1.1. The Accounting Metrics Collection (AMC) function block is in the UE that supports the specific service. The AMC sends usage information collected to the Accounting Data Forwarding (ADF) function block of the CTF in the service NE over the service-specific reference point, denoted as X. The subset of X specific to usage information collection for charging purposes is denoted as Xch in figure D.3.2.1. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | D.4.3.1.1 |
4,354 | 5.6.1.2.1 UE is not using EPS services with control plane CIoT EPS optimization | For cases a, b, c, h, k, l and o in clause 5.6.1.1: - if the UE is not configured for NAS signalling low priority, the UE initiates the service request procedure by sending a SERVICE REQUEST message to the MME; - if the UE is configured for NAS signalling low priority, and the last received ATTACH ACCEPT message or TRACKING AREA UPDATE ACCEPT message from the network indicated that the network supports use of EXTENDED SERVICE REQUEST for packet services, the UE shall send an EXTENDED SERVICE REQUEST message with service type set to "packet services via S1"; or NOTE: A UE configured for dual priority is configured for NAS signalling low priority indicator. - if the UE is configured for NAS signalling low priority and the last received ATTACH ACCEPT message or TRACKING AREA UPDATE ACCEPT message from the network did not indicate that the network supports use of EXTENDED SERVICE REQUEST for packet services, the UE shall instead send a SERVICE REQUEST message. For cases a, b, c, h, k, l, and o in clause 5.6.1.1, after sending the SERVICE REQUEST message or the EXTENDED SERVICE REQUEST message with service type set to "packet services via S1", the UE shall start T3417 and enter the state EMM-SERVICE-REQUEST-INITIATED. For case d in clause 5.6.1.1, the UE shall send an EXTENDED SERVICE REQUEST message, start T3417ext and enter the state EMM-SERVICE-REQUEST-INITIATED. For case e in clause 5.6.1.1: - if the UE is in EMM-IDLE mode, the UE shall send an EXTENDED SERVICE REQUEST message, start T3417ext-mt and enter the state EMM-SERVICE-REQUEST-INITIATED; - if the UE is in EMM-CONNECTED mode and if the UE accepts the paging, the UE shall send an EXTENDED SERVICE REQUEST message with the CSFB response IE indicating "CS fallback accepted by the UE", start T3417ext-mt and enter the state EMM-SERVICE-REQUEST-INITIATED; or - if the UE is in EMM-CONNECTED mode and if the UE rejects the paging, the UE shall send an EXTENDED SERVICE REQUEST message with the CSFB response IE indicating "CS fallback rejected by the UE" and enter the state EMM-REGISTERED.NORMAL-SERVICE. The network shall not initiate CS fallback procedures. For cases f, g, i and j in clause 5.6.1.1, the UE shall send an EXTENDED SERVICE REQUEST message, start T3417 and enter the state EMM-SERVICE-REQUEST-INITIATED. For case o in clause 5.6.1.1, the UE may send an EXTENDED SERVICE REQUEST message with Service type set to "packet services via S1" and Request type set to "NAS signalling connection release" in the UE request type IE to remove the paging restriction and request the release of the NAS signalling connection at the same time. The UE shall start T3417 and enter the state EMM-SERVICE-REQUEST-INITIATED. The UE shall not include the Paging restriction IE in the EXTENDED SERVICE REQUEST message. For cases p and q in clause 5.6.1.1, the UE shall send an EXTENDED SERVICE REQUEST message, 1) for case p in clause 5.6.1.1, set Request type to "NAS signalling connection release" in the UE request type IE and Service type to "packet services via S1"; or 2) for case q in clause 5.6.1.1, set Request type to "Rejection of paging" in the UE request type IE and, a) if the UE needs to reject PS paging, the UE shall set Service type to "packet services via S1"; or b) if the UE needs to reject CS paging, the UE shall set Service type to "mobile terminating CS fallback or 1xCS fallback" and the CSFB response IE to "CS fallback rejected by the UE"; and start T3417, enter the state EMM-SERVICE-REQUEST-INITIATED and may include its paging restriction preference in the Paging restriction IE in the EXTENDED SERVICE REQUEST message. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.6.1.2.1 |
4,355 | – CSI-IM-Resource | The IE CSI-IM-Resource is used to configure one CSI Interference Management (IM) resource. CSI-IM-Resource information element -- ASN1START -- TAG-CSI-IM-RESOURCE-START CSI-IM-Resource ::= SEQUENCE { csi-IM-ResourceId CSI-IM-ResourceId, csi-IM-ResourceElementPattern CHOICE { pattern0 SEQUENCE { subcarrierLocation-p0 ENUMERATED { s0, s2, s4, s6, s8, s10 }, symbolLocation-p0 INTEGER (0..12) }, pattern1 SEQUENCE { subcarrierLocation-p1 ENUMERATED { s0, s4, s8 }, symbolLocation-p1 INTEGER (0..13) } } OPTIONAL, -- Need M freqBand CSI-FrequencyOccupation OPTIONAL, -- Need M periodicityAndOffset CSI-ResourcePeriodicityAndOffset OPTIONAL, -- Cond PeriodicOrSemiPersistent ... } -- TAG-CSI-IM-RESOURCE-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,356 | 8.13.2.1.3 Minimum Requirement Multi-Layer Spatial Multiplexing 4 Tx Antenna Port with 256QAM | The purpose of these tests is to verify the closed loop rank-two performance with frequency selective precoding with 256QAM under CA. For CA with 2 DL CCs, the requirements are specified in Table 8.13.2.1.3-3, based on single carrier requirement specified in Table 8.13.2.1.3-2, with the addition of the parameters in Table 8.13.2.1.3-1 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.13.2.1.3-1: Test Parameters for Multi-Layer Spatial Multiplexing (FRC) for CA Table 8.13.2.1.3-2: Single carrier performance for multiple CA configurations Table 8.13.2.1.3-3: Minimum performance (FRC) based on single carrier performance for CA with 2 DL CCs | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.13.2.1.3 |
4,357 | A.5 Causes related to invalid messages | Cause value #95 – Semantically incorrect message. See 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13], annex H, clause H.5.5. Cause value #96 – Invalid mandatory information. See 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13], annex H, clause H.6.1. Cause value #97 – Message type non-existent or not implemented. See 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13], annex H, clause H.6.2. Cause value #98 – Message type not compatible with protocol state. See 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13], annex H, clause H.6.3. Cause value #99 – Information element non-existent or not implemented. See 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13], annex H, clause H.6.4. Cause value #100 – Conditional IE error. See 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13], annex H, clause H.6.5. Cause value #101 – Message not compatible with protocol state. See 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13], annex H, clause H.6.6. Cause value #111 – Protocol error, unspecified. See 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13], annex H, clause H.6.8. | 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.5 |
4,358 | 8.8.2.2 TDD | The parameters specified in Table 8.8.2.2-1 are valid for all TDD TM9 localized ePDCCH tests unless otherwise stated. Table 8.8.2.2-1: Test Parameters for Localized EPDCCH with TM9 For the parameters specified in Table 8.8.2.2-1 the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.2.2.2-2. EPDCCH subframe monitoring is configured and the subframe monitoring requirement in EPDCCH restricted subframes is statDTX of 99.9%. The downlink physical setup is in accordance with Annex C.3.2. Table 8.8.2.2-2: Minimum performance Localized EPDCCH with TM9 | 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.8.2.2 |
4,359 | 7.3.2 Scheduling | The MIB is mapped on the BCCH and carried on BCH while all other SI messages are mapped on the BCCH, where they are dynamically carried on DL-SCH. The scheduling of SI messages part of Other SI is indicated by SIB1. For UEs in RRC_IDLE and RRC_INACTIVE while SDT procedure is not ongoing (see clause 18), a request for Other SI triggers a random access procedure (see clause 9.2.6) where MSG3 includes the SI request message unless the requested SI is associated to a subset of the PRACH resources, in which case MSG1 is used for indication of the requested Other SI. When MSG1 is used, the minimum granularity of the request is one SI message (i.e. a set of SIBs), one RACH preamble and/or PRACH resource can be used to request multiple SI messages and the gNB acknowledges the request in MSG2. When MSG 3 is used, the gNB acknowledges the request in MSG4. For UEs in RRC_CONNECTED, a request for Other SI may be sent to the network, if configured by the network, in a dedicated manner (i.e., via UL-DCCH) and the granularity of the request is one SIB. The gNB may respond with an RRCReconfiguration including the requested SIB(s). It is a network choice to decide which requested SIBs are delivered in a dedicated or broadcasted manner. The Other SI may be broadcast at a configurable periodicity and for a certain duration. The Other SI may also be broadcast when it is requested by UE in RRC_IDLE/RRC_INACTIVE/RRC_CONNECTED. For a UE to be allowed to camp on a cell it must have acquired the contents of the Minimum SI from that cell. There may be cells in the system that do not broadcast the Minimum SI and where the UE therefore cannot camp. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 7.3.2 |
4,360 | – ChildIE1-WithoutEM | The IE ChildIE1-WithoutEM is an example of a lower level IE, used to control certain radio configurations including a configurable feature which can be setup or released using the local IE ChIE1-ConfigurableFeature. The example illustrates how the new field chIE1-NewField is added in release N to the configuration of the configurable feature. The example is based on the following assumptions: – When initially configuring as well as when modifying the new field, the original fields of the configurable feature have to be provided also i.e. as if the extended ones were present within the setup branch of this feature. – When the configurable feature is released, the new field should be released also. – When omitting the original fields of the configurable feature the UE continues using the existing values (which is used to optimise the signalling for features that typically continue unchanged upon handover). – When omitting the new field of the configurable feature the UE releases the existing values and discontinues the associated functionality (which may be used to support release of unsupported functionality upon handover to an eNB supporting an earlier protocol version). The above assumptions, which affect the use of conditions and need codes, may not always apply. Hence, the example should not be re-used blindly. ChildIE1-WithoutEM information element -- /example/ ASN1START ChildIE1-WithoutEM ::= SEQUENCE { -- Root encoding, including: chIE1-ConfigurableFeature ChIE1-ConfigurableFeature OPTIONAL -- Need N } ChildIE1-WithoutEM-vNx0 ::= SEQUENCE { chIE1-ConfigurableFeature-vNx0 ChIE1-ConfigurableFeature-vNx0 OPTIONAL -- Cond ConfigF } ChIE1-ConfigurableFeature ::= CHOICE { release NULL, setup SEQUENCE { -- Root encoding } } ChIE1-ConfigurableFeature-vNx0 ::= SEQUENCE { chIE1-NewField-rN INTEGER (0..31) } -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,361 | 9.12.1 Serving network name (SNN) | The serving network name (SNN) is used: - in the Network name field of the AT_KDF_INPUT attribute defined in IETF RFC 5448 [40]; - in KAUSF derivation function as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24] annex A; and - in RES* and XRES* derivation function as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24] annex A. SNN shall contain a UTF-8 string without terminating null characters. SNN is of maximum length of 1020 octets. SNN consists of SNN-service-code and SNN-network-identifier, delimited by a colon. SNN-network-identifier identifies the serving PLMN or the serving SNPN. MCC and MNC in the SNN-PLMN-ID are MCC and MNC of the serving PLMN. If the MNC of the serving PLMN has two digits, then a zero is added at the beginning. MCC and MNC in the SNN-SNPN-ID are MCC and MNC of the serving SNPN. If the MNC of the serving SNPN has two digits, then a zero is added at the beginning. SNN-NID contains an NID in hexadecimal digits. ABNF syntax of SNN is specified in table 9.12.1.1 Table 9.12.1.1: ABNF syntax of SNN SNN = SNN-service-code ":" SNN-network-identifier SNN-service-code = %x35.47 ; "5G" SNN-network-identifier = SNN-PLMN-ID / SNN-SNPN-ID SNN-PLMN-ID = SNN-mnc-string SNN-mnc-digits "." SNN-mcc-string SNN-mcc-digits "." SNN-3gppnetwork-string "." SNN-org-string ; applicable when not operating in SNPN access operation mode. SNN-SNPN-ID = SNN-mnc-string SNN-mnc-digits "." SNN-mcc-string SNN-mcc-digits "." SNN-3gppnetwork-string "." SNN-org-string ":" SNN-NID ; applicable when operating in SNPN access operation mode. SNN-mnc-digits = DIGIT DIGIT DIGIT ; MNC of the PLMN ID SNN-mcc-digits = DIGIT DIGIT DIGIT ; MCC of the PLMN ID SNN-mnc-string = %x6d.6e.63 ; "mnc" in lower case SNN-mcc-string = %x6d.63.63 ; "mcc" in lower case SNN-3gppnetwork-string = %x33.67.70.70.6e.65.74.77.6f.72.6b ; "3gppnetwork" in lower case SNN-org-string = %x6f.72.67 ; "org" in lower case SNN-NID = 11SNN-hexadecimal-digit ; NID in hexadecimal digits SNN-hexadecimal-digit = DIGIT / %x41 / %x42 / %x43 / %x44 / %x45 / %x46 NOTE: SNN-service-code allows for distinguishing of ANID specified in 3GPP TS 24.302[ Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 ] [16] and SNN as either of SNN or ANID can be carried in the AT_KDF_INPUT attribute. EXAMPLE 1: In case of a PLMN, if PLMN ID contains MCC = 234 and MNC = 15, SNN is 5G:mnc015.mcc234.3gppnetwork.org. EXAMPLE 2: In case of an SNPN, if SNPN ID contains a PLMN ID of MCC = 234 and MNC = 15 and an NID of 123456ABCDEH, SNN is 5G:mnc015.mcc234.3gppnetwork.org:123456ABCDE. | 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.12.1 |
4,362 | 8.13.3.6.2 Minimum Requirement for TDD PCell | The purpose of these tests is to verify the closed loop rank-two performance with wideband and frequency selective precoding. For TDD FDD CA with TDD PCell and 2DL CCs, the requirements are specified in Table 8.13.3.6.2-4 based on single carrier requirement specified in Table 8.13.3.6.2-2 and Table 8.13.3.6.2-3, with the addition of the parameters in Table 8.13.3.6.2-1 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.13.3.6.2-1: Test Parameters for Multi-Layer Spatial Multiplexing (FRC) for CA Table 8.13.3.6.2-2: Single carrier performance with different bandwidths for multiple CA configurations for FDD SCell (FRC) Table 8.13.3.6.2-3: Single carrier performance with different bandwidths for multiple CA configurations for TDD PCell and SCell (FRC) Table 8.13.3.6.2-4: Minimum performance for multiple CA configurations with 2DL CCs (FRC) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.13.3.6.2 |
4,363 | 9.3.2.4 Data Forwarding for the Control Plane | Control plane handling for inter-System data forwarding from 5GS to EPS follows the following key principles: - Only forwarding of downlink data is supported. - PDU session information at the serving NG-RAN node contains mapping information per QoS Flow to a corresponding E-RAB. - At handover preparation, the source NG-RAN node shall decide which mapped E-RABs are proposed to be subject to data forwarding and provide this information in the source-to-target container to the target eNB. Based on availability of direct data forwarding path the source NG-RAN node may request to apply direct data forwarding by indicating direct data forwarding path availability to the 5GC. - The target eNB assigns forwarding TEID/TNL address(es) for the E-RAB(s) for which it accepts data forwarding. - In case of indirect data forwarding, a single data forwarding tunnel is established between the source NG-RAN node and UPF per PDU session for which at least data for a single QoS Flow is subject to data forwarding. - In case of direct data forwarding, the source NG-RAN node receives a TEID/TNL address for each E-RAB accepted for data forwarding as assigned by the target eNB. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 9.3.2.4 |
4,364 | 5.7.2b UL transfer of IRAT information 5.7.2b.1 General | Figure 5.7.2b.1-1: UL transfer of IRAT information The purpose of this procedure is to transfer from the UE to NR MCG dedicated information terminated at the NR MCG but specified by another RAT e.g. the E-UTRA MeasurementReport message, the E-UTRA SidelinkUEInformation message or the E-UTRA UEAssistanceInformation message. The specific information transferred in this message is set in accordance with: - the procedure specified in 5.6.10 of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] for E-UTRA UEAssistanceInformation message; - the procedure specified in 5.10.2 of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] for E-UTRA SidelinkUEInformation message; - the procedure specified in 5.5.5 of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] for E-UTRA MeasurementReport Message. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.2b |
4,365 | 5.5.6 Attach request message (for N1 mode only) | The attach procedure is used to construct an ATTACH REQUEST message for a UE performing a registration procedure for initial registration when a) the UE: 1) previously was registered in S1 mode before entering state EMM-DEREGISTERED; and 2) has received an "interworking without N26 interface not supported" indication from the network; and b) EPS security context and a valid 4G-GUTI are available. The ATTACH REQUEST message is created by EMM by request of 5GMM which further includes the message in the REGISTRATION REQUEST message as described in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54]. The ATTACH REQUEST message shall contain only mandatory information elements. The UE shall set the EPS attach type IE in the ATTACH REQUEST message to "EPS attach". The UE shall include the eKSI (KSIASME) in the NAS Key Set Identifier IE in the ATTACH REQUEST message. The UE shall integrity protect the ATTACH REQUEST message with the current EPS security context and increase the uplink NAS COUNT by one. The UE shall set associated GUTI in the EPS mobile identity IE. The UE shall set the UE network capability IE according to its capabilities. The UE shall include an ESM DUMMY MESSAGE in the ESM message container IE. | 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.6 |
4,366 | 5.2.3 Potential service requirements | The 3GPP system shall enable a UTM to be aware of the identity/identities of a UAS. The 3GPP system shall enable a UAS to update a UTM with the live location of a UAV. The 3GPP system shall enable a UAS to send the location of the UAV and UAV controller towards UTM with at least a periodicity of 1 update per second. The 3GPP system may enable an MNO to supplement location information sent to a UTM. NOTE: this supplement may be trust-based (i.e. the MNO informs the UTM that the UAV position information is trusted) or it may be additional location information based on network information. The 3GPP system shall enable a UTM to send route modification information to a UAS with a latency of less than 1 second. | 3GPP TS 22.825 | Study on Remote Identification of Unmanned Aerial Systems (UAS) | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 5.2.3 |
4,367 | 4.7.1.6.2 Change of network mode of operation in Iu mode (Iu mode only) | Whenever an MS moves to a new RA, the procedures executed by the MS depend on the network mode of operation in the old and new routing area. In case the MS is in state GMM-REGISTERED or GMM-ROUTING-AREA-UPDATING-INITIATED and is in operation mode A, the MS shall execute: Table 4.7.1.6.4/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Mode A (*) Intended to remove the Gs association in the MSC/VLR. (**) Intended to establish the Gs association in the MSC/VLR. (***) If the MS that needs only GPRS services and "SMS-only service" moves to a new routing area, see subclause 4.1.1.2.2. Further details are implementation issues. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.1.6.2 |
4,368 | – PUSCH-TimeDomainResourceAllocationList | The IE PUSCH-TimeDomainResourceAllocation is used to configure a time domain relation between PDCCH and PUSCH. PUSCH-TimeDomainResourceAllocationList contains one or more of such PUSCH-TimeDomainResourceAllocations. The network indicates in the UL grant which of the configured time domain allocations the UE shall apply for that UL grant. The UE determines the bit width of the DCI field based on the number of entries in the PUSCH-TimeDomainResourceAllocationList. Value 0 in the DCI field refers to the first element in this list, value 1 in the DCI field refers to the second element in this list, and so on. PUSCH-TimeDomainResourceAllocation information element -- ASN1START -- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-START PUSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofUL-Allocations)) OF PUSCH-TimeDomainResourceAllocation PUSCH-TimeDomainResourceAllocation ::= SEQUENCE { k2 INTEGER(0..32) OPTIONAL, -- Need S mappingType ENUMERATED {typeA, typeB}, startSymbolAndLength INTEGER (0..127) } PUSCH-TimeDomainResourceAllocationList-r16 ::= SEQUENCE (SIZE(1..maxNrofUL-Allocations-r16)) OF PUSCH-TimeDomainResourceAllocation-r16 PUSCH-TimeDomainResourceAllocation-r16 ::= SEQUENCE { k2-r16 INTEGER(0..32) OPTIONAL, -- Need S puschAllocationList-r16 SEQUENCE (SIZE(1..maxNrofMultiplePUSCHs-r16)) OF PUSCH-Allocation-r16, ... } PUSCH-Allocation-r16 ::= SEQUENCE { mappingType-r16 ENUMERATED {typeA, typeB} OPTIONAL, -- Cond NotFormat01-02-Or-TypeA startSymbolAndLength-r16 INTEGER (0..127) OPTIONAL, -- Cond NotFormat01-02-Or-TypeA startSymbol-r16 INTEGER (0..13) OPTIONAL, -- Cond RepTypeB length-r16 INTEGER (1..14) OPTIONAL, -- Cond RepTypeB numberOfRepetitions-r16 ENUMERATED {n1, n2, n3, n4, n7, n8, n12, n16} OPTIONAL, -- Cond Format01-02 ..., [[ numberOfRepetitionsExt-r17 ENUMERATED {n1, n2, n3, n4, n7, n8, n12, n16, n20, n24, n28, n32, spare4, spare3, spare2, spare1} OPTIONAL, -- Cond Format01-02-For-TypeA numberOfSlotsTBoMS-r17 ENUMERATED {n1, n2, n4, n8, spare4, spare3, spare2, spare1} OPTIONAL, -- Need R extendedK2-r17 INTEGER (0..128) OPTIONAL -- Cond MultiPUSCH ]] } -- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,369 | 5.2.3.2.3 LIMITED-SERVICE | The UE: - shall perform cell selection/reselection according to 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]; - may respond to paging (with IMSI); NOTE: As an implementation option, the MUSIM UE is allowed to not respond to paging based on the information available in the paging message, e.g. voice service indication. - may detach locally and initiate attach for emergency bearer services; - may detach locally and may initiate attach for access to RLOS; and - if configured for eCall only mode as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17], shall perform the eCall inactivity procedure at expiry of timer T3444 or T3445 (see clause 5.5.4). | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.2.3.2.3 |
4,370 | 5.19.2a Impacts to Handover Procedures | When DCNs are used, the impacts to the handover procedures are captured as below. - Forward Relocation Request message: When MME changes during handover, in the step where Forward Relocation Request message is sent from the Source MME/SGSN to Target MME/SGSN, the source MME/SGSN also includes the UE Usage Type, if available, in the message. This applies to the following clauses and step: - 5.5.1.2.2 S1-based handover, normal: Step 3 - 5.5.2.1.2 Preparation phase (E-UTRAN to UTRAN Iu mode Inter RAT handover): Step 3 - 5.5.2.2.2 Preparation phase (UTRAN Iu mode to E-UTRAN Inter RAT handover): Step 3 - 5.5.2.3.2 Preparation phase (E-UTRAN to GERAN A/Gb mode Inter RAT handover): Step 3 - 5.5.2.4.2 Preparation phase (GERAN A/Gb mode to E-UTRAN Inter RAT handover): Step 3 - Selection of new SGW: In the step, subsequent to the Forward Relocation Request message, in which the target MME/SGSN determines if the Serving GW is to be relocated, if the target MME/SGSN supports DCN, the target MME/SGWN also determines if the existing Serving GW supports the DCN for the UE based on UE Usage Type of the UE, locally configured operator's policies as well as UE related context information available at the target network, e.g. information about roaming. This applies to the following clauses and step: - 5.5.1.2.2 S1-based handover, normal: Step 4 - 5.5.2.1.2 Preparation phase (E-UTRAN to UTRAN Iu mode Inter RAT handover): Step 4 - 5.5.2.2.2 Preparation phase (UTRAN Iu mode to E-UTRAN Inter RAT handover): Step 4 - 5.5.2.3.2 Preparation phase (E-UTRAN to GERAN A/Gb mode Inter RAT handover): Step 4 - 5.5.2.4.2 Preparation phase (GERAN A/Gb mode to E-UTRAN Inter RAT handover): Step 4 - Handover from service area where DCN is not used to an area where DCN is supported: When handover occurs from a service area where DCN is not used to a service area where DCN is supported and the MME or SGSN changes, the target MME or SGSN obtains the UE Usage Type information from the HSS during the subsequent TAU or RAU procedure. If the target MME/SGSN determines that the Serving GW does not support the UE Usage Type, the target MME/SGSN triggers the Serving GW relocation as part of the handover procedures described in clause 5.5. If the target MME or SGSN does not serve the UE Usage type, the handover procedure should complete successfully and then the target MME or SGSN may use the procedure in clause 5.19.3 Step 5 onwards, to change the serving DCN of the UE. | 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.19.2a |
4,371 | 4.5.1 Offline mapping | The figures 4.5.1.1 – 4.5.1.4 below depict the mappings of the ubiquitous offline charging architecture onto physical implementations that are identified within the 3GPP standards. As stated previously in the present document, the CTF is a mandatory component of all NEs that have offline charging capabilities. In contrast, the CDF and the CGF may be implemented in any of the following ways: 1) CDF and CGF integrated in the NE. In this implementation, all network charging functions are embedded in the NE, i.e. the NE is fully self-contained in terms of offline charging. The (physical) NE itself produces the CDR files that are then transferred to the BD. Consequently, only the Bx reference point needs to be implemented as a physical interface. Figure 4.5.1.1: CDF and CGF integrated in the NE 2) CDF integrated in the NE, CGF in a separate physical element. In this implementation, the (physical) NE generates CDRs and sends them to an external CGF. Hence the Ga reference point must be implemented in the NE as a physical interface. If the CGF is a stand-alone entity, it must implement both the Ga and the Bx reference point as physical interface. As a variation of this construct, the CGF may be integrated in the BD, in which case the Bx reference point is internal to the BD. Figure 4.5.1.2: CDF integrated in the NE, CGF in a separate physical element 3) CDF and CGF in two separate physical elements. This scenario represents the fully distributed implementation where all reference points must be implemented as physical interfaces on the NE, CDF and CGF, respectively. Again, as a variation of this approach, the CGF may be an integral component of the BD, in which case the Bx reference point becomes internal to the BD. Figure 4.5.1.3: CDF and CGF in two separate physical elements 4) CDF and CGF in the same separate physical element. In contrast to scenario 3, there is no physical Ga interface, whereas the Rf and Bx reference points must exist as distinct interfaces in the same fashion as in scenario 3. The variation of the combined CDF/CGF being embedded in the BD is again possible, resulting in the Rf reference point being the only one that appears as a physical interface. Figure 4.5.1.4: CDF and CGF in the same separate physical element Details of the possible implementation options per domain / subsystem / service (usually a subset of the overall possible variants described above) are specified in the respective middle tier TS. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.5.1 |
4,372 | 4.7.7.3 APN Rate Control | The APN Rate Control is configured in the PDN GW or in the SCEF. The PDN GW or SCEF can send an APN Uplink Rate Control command to the UE using the PCO information element. The APN Uplink Rate Control applies to data PDUs sent on that APN by either Data Radio Bearers (S1-U) or Signalling Radio Bearers (NAS Data PDUs). The rate control information is separate for uplink and downlink and in the form of: - a positive integer 'number of packets per time unit', and - an indication as to whether or not exception reports can still be sent if this rate control limit has been met, and - if the UE indicated support for it, an integer 'number of additional allowed exception report packets per time unit' once the rate control limit has been reached. UEs supporting APN Rate Control shall support the 'number of additional allowed exception report packets per time unit' and shall provide an indication to the CN at PDN connection establishment. NOTE 1: Pre-Rel-14 UEs do not support the 'number of additional allowed exception report packets per time unit' and do not send an indication to the CN at PDN connection establishment. The UE shall comply with this uplink rate control instruction. If the UE exceeds the uplink 'number of packets per time unit', the UE may still send uplink exception reports if allowed and the 'number of additional allowed exception reports per time unit' has not been exceeded. The UE shall consider this rate control instruction as valid until it receives a new one from either PDN GW or from SCEF. When the last PDN connection using a given APN is released, the APN Rate Control Status (including the number of packets still allowed in the given time unit, the number of additional exception reports still allowed in the given time unit and the termination time of the current APN Rate Control validity period) may be stored in the MME so that it can be retrieved for a subsequent re-establishment of a new first PDN connection for that given APN. At subsequent establishment of a new first PDN connection for that given APN, the PDN GW/SCEF may receive the previously stored APN Rate Control Status and, if the first APN Rate Control validity period has not expired, it applies the received APN Rate Control Status and provides the related parameters to the UE in the PCO (instead of the configured APN Rate Control parameters). If the initially applied parameters differ from the configured APN Rate Control parameters, the PDN GW/SCEF uses the configured APN Rate Control parameters once the first APN Rate Control validity period expires, and sends an update to the UE with the configured APN Rate Control parameters. NOTE 2: The storage of the APN Rate Control Status information for very long time intervals can be implementation specific. The PDN GW or SCEF realises the APN rate control based on a 'maximum allowed rate' per direction. If PDN GW or SCEF provided the 'number of additional allowed exception report packets per time unit' to the UE, then the 'maximum allowed rate' is equal to the 'number of packets per time unit' plus the 'number of additional allowed exception report packets per time unit'. Otherwise, the 'maximum allowed rate' is equal to the 'number of packets per time unit'. NOTE 3: Pre-Rel-14 UEs understand only the 'number of packets per time unit', and, if an indication that exception reports are allowed has been sent to such UEs, there is a risk that exception report packets are discarded by the PDN GW or SCEF. To overcome this problem, the PDN GW or SCEF can still apply a configured 'number of additional allowed exception report packets per time unit' even though not sent to pre-Rel-14 UEs. The PDN GW or SCEF may enforce the uplink rate by discarding or delaying packets that exceed the 'maximum allowed rate'. The PDN GW or SCEF shall enforce the downlink rate by discarding or delaying packets that exceed the downlink part of the 'maximum allowed rate'. NOTE 4: It is assumed that the Serving PLMN Rate is sufficiently high to not interfere with the APN Rate Control as the APN Rate Control, if used, is assumed to allow fewer messages. NAS PDUs related to exception reports are not subject to the Serving PLMN Rate Control. | 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.7.7.3 |
4,373 | 9.3.11 Hold Acknowledge | This message is sent by the network to indicate that the hold function has been successfully performed. See table 9.62d/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] for the content of the HOLD ACKNOWLEDGE message. For the use of this message, see 3GPP TS 24.010[ Mobile radio interface layer 3; Supplementary services specification; General aspects ] [21]. Message type: HOLD ACKNOWLEDGE Significance: local Direction: network to mobile station Table 9.62d/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : HOLD ACKNOWLEDGE message content | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.3.11 |
4,374 | 5.2.1.10 Call queuing at mobile originating call establishment | If an idle traffic channel is not available at the assignment instant, the network may place the traffic channel request in a queue. Calls arriving when all positions in the queue are occupied shall be cleared by the network using the cause #34 "no circuit/channel available". The maximum queuing interval is supervised by the network. The limit is a network dependent choice. In case the network is not able to allocate a traffic channel within the queuing limit, the network will release the call using cause #34 "no circuit/channel available". Optionally, e.g. if eMLPP is used, the network may decide to pre-empt existing calls or to place the traffic channel request at some preferential position within the queue. Specific indications provided in the network to the remote user are a network dependent choice. | 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 | 5.2.1.10 |
4,375 | 5.8.10.2.6 Sidelink reporting configuration removal | The UE shall: 1> for each sl-ReportConfigId included in the received sl-ReportConfigToRemoveList that is part of the current UE configuration in VarMeasConfigSL: 2> remove the entry with the matching sl-ReportConfigId from the sl-ReportConfigList within the VarMeasConfigSL; 2> remove all sl-MeasId associated with the sl-ReportConfigId from the sl-MeasIdList within the VarMeasConfigSL, if any; 2> if a sl-MeasId is removed from the sl-MeasIdList: 3> remove the measurement reporting entry for this sl-MeasId from the VarMeasReportListSL, if included; 3> stop the periodical reporting timer and reset the associated information (e.g. sl-TimeToTrigger) for this sl-MeasId. NOTE: The UE does not consider the message as erroneous if the sl-ReportConfigToRemoveList includes any sl-ReportConfigId value that is not part of the current UE configuration. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.10.2.6 |
4,376 | 16.10.6.2 Configuration | MBS broadcast can be received by UEs in RRC_IDLE, RRC_INACTIVE and RRC_CONNECTED state. A UE can receive the MBS configuration for broadcast session (e.g., parameters needed for MTCH reception) via MCCH in RRC_IDLE, RRC_INACTIVE and RRC_CONNECTED state. The parameters needed for the reception of MCCH are provided via System Information. The following principles govern the MCCH structure: - MCCH provides the list of all broadcast services with ongoing sessions transmitted on MTCH(s) and the associated information for broadcast session includes MBS session ID, associated G-RNTI scheduling information and information about neighbouring cells providing certain service on MTCH(s). MCCH content is transmitted within periodically occurring time domain windows, referred to as MCCH transmission window defined by MCCH repetition period, MCCH window duration and radio frame/slot offset; - MCCH uses a modification period and MCCH contents are only allowed to be modified at each modification period boundary; a notification mechanism is used to announce the change of MCCH contents due to broadcast session start, modification or stop and due to neighbouring cell information modification; NOTE: It is up to UE implementation to use the start and stop times in the USD to determine when to start monitoring the MCCH for the session the UE is interested in. - When the UE receives an MCCH change notification, it acquires the updated MCCH in the same MCCH modification period where the change notification is sent. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.10.6.2 |
4,377 | 4.1 Overall Architecture | An NG-RAN node is either: - a gNB, providing NR user plane and control plane protocol terminations towards the UE; or - an ng-eNB, providing E-UTRA user plane and control plane protocol terminations towards the UE. The gNBs and ng-eNBs are interconnected with each other by means of the Xn interface. The gNBs and ng-eNBs are also connected by means of the NG interfaces to the 5GC, more specifically to the AMF (Access and Mobility Management Function) by means of the NG-C interface and to the UPF (User Plane Function) by means of the NG-U interface (see TS 23.501[ System architecture for the 5G System (5GS) ] [3]). NOTE: The architecture and the F1 interface for a functional split are defined in TS 38.401[ NG-RAN; Architecture description ] [4]. The NG-RAN architecture is illustrated in Figure 4.1-1 below. Figure 4.1-1: Overall Architecture | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 4.1 |
4,378 | 11.2.1.3.2 IPv6 Stateless Address Autoconfiguration | As described in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [3], the IPv6 prefix of a PDP Context of PDP type IPv6 or IPv4v6 activated by means of the IPv6 Stateless Address Autoconfiguration Procedure is uniquely identified by the prefix part of the IPv6 address only. The MS may select any value for the Interface-Identifier part of the address. The only exception is the Interface-Identifier for the link-local address used by the MS (see RFC 4291 [82]). This Interface-Identifier shall be assigned by the GGSN to avoid any conflict between the link-local address of the MS and that of the GGSN itself. This is described in subclause "IPv6 PDP Context Activation" above. For IPv6 the PDP Context Activation phase is followed by an address autoconfiguration phase. The procedure describing APNs configured to use Stateless Address Autoconfiguration, may be as follows: 1) After the first phase of setting up IPv6 access to an Intranet or ISP, the MS shall use the IPv6 Interface-Identifier, as provided by the GGSN, to create its IPv6 Link-Local Unicast Address according to RFC 4291 [82]. Before the MS can communicate with other hosts or Mses on the Intranet/ISP, the MS must obtain an IPv6 Global or Site-Local Unicast Address. The simplest way is the IPv6 Stateless Address Autoconfiguration procedure described below and in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [3]. The procedure is consistent with RFC 4862 [83]. The procedure below takes place through signalling in the user plane. It is done on the link between the MS and the GGSN. From the MS perspective the GGSN is now the first router on the link. 2) After the GGSN has sent a Create PDP Context Response message to the SGSN, it shall start sending Router Advertisements periodically on the new MS-GGSN link established by the PDP Context. The MS may issue a Router Solicitation directly after the user plane establishment. This shall trigger the GGSN to send a Router Advertisement immediately. To indicate to the MS that stateless address autoconfiguration shall be performed, the GGSN shall leave the M-flag cleared in the Router Advertisement messages. The GGSN may set the O-flag if there are additional configuration parameters that need to be fetched by the MS (see below). The Prefix sent in the Router Advertisements shall be identical to the Prefix returned in the Create PDP Context Response. The Prefix is contained in the Prefix Information Option of the Router Advertisements and shall have the A-flag set ("Autonomous address configuration flag") and the L-flag cleared (i.e. the prefix should not be used for on-link determination). The lifetime of the prefix shall be set to infinity. In practice, the lifetime of a Prefix will be the lifetime of its PDP Context. There shall be exactly one Prefix included in the Router Advertisements. The handling of Router Advertisements shall be consistent with what is specified in RFC 4861 [89]. For the MS-GGSN link however, some specific handling shall apply. The randomisation part to determine when Router Advertisements shall be sent may be omitted since the GGSN is the only router on the link. Furthermore, some 3GPP specific protocol constants and default values shall apply (see subclause "IPv6 Router Configuration Variables in the GGSN"). These relate to the periodicity of the Router Advertisements initially and during continued operation. The motivation for this is to have a faster user-plane set-up even in bad radio conditions and to minimize MS power consumption during long continued operation. 3) When creating a Global or Site-Local Unicast Address, the MS may use the Interface-Identifier received during the PDP Context Activation phase or it may generate a new Interface-Identifier. There is no restriction on the value of the Interface-Identifier of the Global or Site-Local Unicast Address, since the Prefix is unique. Interface-Identifiers shall in any case be 64-bit long. Since the GGSN guarantees that the Prefix is unique, the MS does not need to perform any Duplicate Address Detection on addresses it creates. That is, the ‘DupAddrDetectTransmits’ variable in the MS should have a value of zero. If the MS finds more than one Prefix in the Router Advertisement message, it shall only consider the first one and silently discard the others. The GGSN shall not generate any globally unique IPv6 addresses for itself using the Prefix assigned to the MS in the Router Advertisement. If the O-flag ("Other configuration flag") was set in the Router Advertisement, the MS may start a DHCP session to retrieve additional configuration parameters. See subclause 13.2.2 "Other configuration by the Intranet or ISP". If the MS is not DHCP capable, the O-flag may be ignored. Figure 11bb: IPv6 Stateless Address Autoconfiguration | 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 | 11.2.1.3.2 |
4,379 | 6.3.17 NSSAAF discovery and selection | In the case of NF consumer based discovery and selection, the following applies: - The NF consumer (e.g. AMF, AUSF) performs NSSAAF selection to select an NSSAAF Instance that supports authentication between the UE and the AAA-S associated with the HPLMN or in the Credentials Holder in the case of SNPN or in the DCS domain in the case of ON-SNPN. The NF consumer shall utilize the NRF to discover the NSSAAF instance(s) unless NSSAAF information is available by other means, e.g. locally configured on the NF consumer. The NSSAAF selection function in the NF consumer selects an NSSAAF instance based on the available NSSAAF instances (obtained from the NRF or locally configured in the NF consumer). In the case of SNPN, NSSAAF selection is only applicable to 3GPP access. Otherwise, NSSAAF selection is applicable to both 3GPP access and non-3GPP access. The NSSAAF selection function in NSSAAF NF consumers or in SCP should consider the following factor when it is available: 1. Home Network Identifier (e.g. MNC and MCC, realm) of SUPI (by an NF consumer in the Serving network). 2. S-NSSAI of the HPLMN. 3. SUPI or Internal Group ID; the NSSAAF NF consumer selects a NSSAAF instance based on the SUPI range the UE's SUPI belongs to or based on the results of a discovery procedure with NRF using the UE's SUPI or Internal Group ID as input for NSSAAF discovery. An HPLMN deploying NSSAAF instances supporting specific S-NSSAIs and/or sets of SUPIs (according to factors 2-3) shall also deploy NSSAAF instance(s) that can be selected using factor 1 if they need to interoperate with VPLMNs using only factor 1 for NSSAAF selection. In the case of delegated discovery and selection in SCP, the NSSAAF NF consumer shall send all available factors to the SCP. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.17 |
4,380 | 5.1.1.3 UE - MME | Legend: - NAS: The NAS protocol supports mobility management functionality and user plane bearer activation, modification and deactivation. It is also responsible of ciphering and integrity protection of NAS signalling. - LTE-Uu: The radio protocol of E-UTRAN between the UE and the eNodeB is 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]. Figure 5.1.1.3-1: Control Plane UE - MME | 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.1.1.3 |
4,381 | – CellAccessRelatedInfo | The IE CellAccessRelatedInfo indicates cell access related information for this cell. CellAccessRelatedInfo information element -- ASN1START -- TAG-CELLACCESSRELATEDINFO-START CellAccessRelatedInfo ::= SEQUENCE { plmn-IdentityInfoList PLMN-IdentityInfoList, cellReservedForOtherUse ENUMERATED {true} OPTIONAL, -- Need R ..., [[ cellReservedForFutureUse-r16 ENUMERATED {true} OPTIONAL, -- Need R npn-IdentityInfoList-r16 NPN-IdentityInfoList-r16 OPTIONAL -- Need R ]], [[ snpn-AccessInfoList-r17 SEQUENCE (SIZE (1..maxNPN-r16)) OF SNPN-AccessInfo-r17 OPTIONAL -- Need R ]] } SNPN-AccessInfo-r17 ::= SEQUENCE { extCH-Supported-r17 ENUMERATED {true} OPTIONAL, -- Need R extCH-WithoutConfigAllowed-r17 ENUMERATED {true} OPTIONAL, -- Need R onboardingEnabled-r17 ENUMERATED {true} OPTIONAL, -- Need R imsEmergencySupportForSNPN-r17 ENUMERATED {true} OPTIONAL -- Need R } -- TAG-CELLACCESSRELATEDINFO-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,382 | 4.2.2 Network Functions and entities | The 5G System architecture consists of the following network functions (NF): - Authentication Server Function (AUSF). - Access and Mobility Management Function (AMF). - Data Network (DN), e.g. operator services, Internet access or 3rd party services. - Unstructured Data Storage Function (UDSF). - Network Exposure Function (NEF). - Network Repository Function (NRF). - Network Slice Admission Control Function (NSACF). - Network Slice-specific and SNPN Authentication and Authorization Function (NSSAAF). - Network Slice Selection Function (NSSF). - Policy Control Function (PCF). - Session Management Function (SMF). - Unified Data Management (UDM). - Unified Data Repository (UDR). - User Plane Function (UPF). - UE radio Capability Management Function (UCMF). - Application Function (AF). - User Equipment (UE). - (Radio) Access Network ((R)AN). - 5G-Equipment Identity Register (5G-EIR). - Network Data Analytics Function (NWDAF). - CHarging Function (CHF). - Time Sensitive Networking AF (TSN AF). - Time Sensitive Communication and Time Synchronization Function (TSCTSF). - Data Collection Coordination Function (DCCF). - Analytics Data Repository Function (ADRF). - Messaging Framework Adaptor Function (MFAF). - Non-Seamless WLAN Offload Function (NSWOF). NOTE: The functionalities provided by DCCF and/or ADRF can also be hosted by an NWDAF. - Edge Application Server Discovery Function (EASDF). The 5G System architecture also comprises the following network entities: - Service Communication Proxy (SCP). - Security Edge Protection Proxy (SEPP). The functional descriptions of these Network Functions and entities are specified in clause 6. - Non-3GPP InterWorking Function (N3IWF). - Trusted Non-3GPP Gateway Function (TNGF). - Wireline Access Gateway Function (W-AGF). - Trusted WLAN Interworking Function (TWIF). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.2 |
4,383 | 4.17.4a NF/NF service discovery by NF service consumer in the same SNPN | The NF/NF service discovery by NF service consumer in the same SNPN follows the same principles as NF/NF service discovery by NF service consumer in the same PLMN, see clause 4.17.4. The following additions apply: - If the target NF is AUSF or NSSAAF and the Nnrf_NFDiscovery_Request includes a Home Network Identifier (HNI) in the form of a realm and the HNI belongs to a CH with AAA Server or a DCS with AAA Server, the NRF provides the AUSF or NSSAAF in the same SNPN, based on the NF profile as specified in clause 6.2.6.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - If the target NF is UDM and the Nnrf_NFDiscovery_Request includes a Home Network Identifier (HNI) in the form of a realm and the HNI belongs to a CH with AAA Server, the NRF provides the UDM in the same SNPN, based on the NF profile as specified in clause 6.2.6.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.17.4a |
4,384 | 5.4A.2.1 Slot-SPUCCH | Slot-SPUCCH format 1, 1a, 1b can be configured by higher layers to either have frequency hopping enabled or disabled (see n1SlotSPUCCH-FH-AN-List and n1SlotSPUCCH-NoFH-AN-List in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [9]). In case slot-SPUCCH format 1, 1a, 1b and frequency hopping is enabled, the scrambled and block-wise spread complex-valued symbols are generated as described in clause 5.4.1 for PUCCH format 1/1a/1b where , and. In case slot-SPUCCH format 1, 1a, 1b and frequency hopping is disabled, the scrambled and block-wise spread complex-valued symbols are generated as described in clause 5.4.1 for PUCCH format 1/1a/1b where . Irrespective of frequency hopping being enabled or disabled, is applied as described in clause 5.4.1 for the slot in which the slot-SPUCCH is transmitted in, i.e. either in the first or the second slot of the subframe. Resources used for transmission of slot-SPUCCH format 1, 1a and 1b are identified by a resource index from which the cyclic shift is derived: , In case frequency hopping is enabled, the cyclic shift is determined as described in clause 5.4.2, assuming the condition is fulfilled. In case frequency hopping is disabled, the resource index also indicates the orthogonal sequence index . Both the cyclic shift and the orthogonal sequence index is in this case determined as described in clause 5.4.1. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.4A.2.1 |
4,385 | 11.2.1.3 IPv6 Non Transparent access to an Intranet or ISP | When using IPv6 Address Autoconfiguration, the process of setting up the access to an Intranet or ISP involves two signalling phases. The first signalling phase is done in the control plane and consists of the PDP context activation or initial attach (e.g. create default bearer) for EPC based access, followed by a second signalling phase done in the user plane. The user plane signalling phase shall be stateless. The stateless procedure, which involves only the MS/UE and the GGSN/P-GW, is described in subclause "IPv6 Stateless Address Autoconfiguration". For APNs that are configured for IPv6 address allocation, the GGSN/P-GW shall only use the Prefix part of the IPv6 address for forwarding of mobile terminated IP packets. The size of the prefix shall be according to the maximum prefix length for a global IPv6 address as specified in the IPv6 Addressing Architecture, see RFC 4291 [82]. The GGSN/P-GW indicates to the MS/UE that Stateless Autoconfiguration shall be performed by sending Router Advertisements as described in the corresponding subclause below and according to the principles defined in RFC 4861 [89] and RFC 4862 [83]. For MS/UE having IPv6, IPv6 Stateless Address Autoconfiguration is mandatory. | 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 | 11.2.1.3 |
4,386 | 11.7 IP Multicast access | NOTE: This section is applicable only to GERAN and UTRAN. The Packet Domain could allow access to IP Multicast traffic coming from an external network. The support of IP-Multicast in the Packet Domain is optional. In order for the Packet Core Network to support Multicast traffic that will allow the MS/UE to subscribe to multicast groups from outside the PLMN, the GGSN/P-GW shall support IGMP (IPv4) and/or MLD (IPv6) and one or more Inter-Router Multicast protocols, such as DVMRP, MOSPF, or PIM-SM. IGMP/MLD is an integral part of IP. All hosts wishing to receive IP multicasts are required to implement IGMP (or equivalent) and class-D IPv4 addresses or MLD and IPv6 multicast according to RFC 2710 [48]. IGMP/MLD messages are encapsulated in IP datagrams. To be able to deliver IP-Multicast packets to the appropriate Tes, the GGSN/P-GW may have an IP-Multicast proxy functionality. The IP-Multicast proxy will perform the following tasks: NOTE: In this example it is assumed that IGMP/MLD is used as a Host-Router Multicast protocol. - maintain a list of mobiles that joined one or more Multicast groups. This list is built/updated each time the GGSN/P-GW receives an IGMP Join or MLD Report message from the mobile; - send, based on this maintained list of mobiles, multicast routing information to the routers attached to the Packet Domain, allowing them to route multicast packets; - upon reception by the GGSN/P-GW of multicast packets, make and send a copy as Point-to-Point packets, to each mobile of the group. IP-Multicast traffic can only be handled after an MS/UE has attached to the Packet Domain, and a bearer (e.g. Activated PDP context(s)) (including possibly authentication) pointing to the preferred ISP/external network for this purpose. The Multicast traffic is handled at the application level from a Packet Domain perspective and is sent over UDP/IP. Figure 12 depicts the protocol configuration for handling Multicast traffic (control plane) for the non-EPC based domain case. The Multicast traffic handling affects the GGSN by the introduction of the IP-Multicast proxy and the support for an Inter-Router Multicast protocol and a host-router multicast protocol. If the protocol configuration for handling Multicast traffic (control plane) is applied for Sgi (i.e EPC based packet domain), the P-GW has the functionality of GGSN and Sgi corresponds to the Gi in Figure 12. Figure 12: Protocol configuration for IP-Multicast handling (control plane) | 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 | 11.7 |
4,387 | D.8.6.3 Repeated IEs | If an information element with format T, TV, TLV, or TLV-E is repeated in a message in which repetition of the information element is not specified in subclause D.5, the UE shall handle only the contents of the information element appearing first and shall ignore all subsequent repetitions of the information element. When repetition of information elements is specified, the UE shall handle only the contents of specified repeated information elements. If the limit on repetition of information elements is exceeded, the UE shall handle the contents of information elements appearing first up to the limit of repetitions and shall ignore all subsequent repetitions of the information element. The network should follow the same procedures. | 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 | D.8.6.3 |
4,388 | 4.7.4.1.4 Abnormal cases in the MS | The following abnormal cases can be identified: a) T3321 time-out On the first expiry of the timer, the MS shall retransmit the DETACH REQUEST message and shall reset and restart timer T3321. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3321, the GPRS detach procedure shall be aborted, the MS shall change to state: - MM-NULL if "IMSI detach" was requested; - GMM-REGISTERED.NORMAL-SERVICE if "IMSI Detach" was requested; - GMM-DEREGISTERED if "GPRS detach" was requested; - GMM-DEREGISTERED and MM-NULL if "GPRS/IMSI" detach was requested. b) Lower layer failure before reception of DETACH ACCEPT message The detach procedure is aborted and the MS shall change to one of the following states, except in the following implementation option cases b.1, b.2 and b3: - MM-NULL if "IMSI detach" was requested; - GMM-REGISTERED.NORMAL-SERVICE if "IMSI Detach" was requested; - GMM-DEREGISTERED if "GPRS detach" was requested; - GMM-DEREGISTERED and MM-NULL if "IMSI/GPRS" detach was requested. b.1) Release of PS signalling connection before the completion of the GPRS detach procedure The release of the PS signalling connection before completion of the GPRS detach procedure shall result in the GPRS detach procedure being initiated again, if the following conditions apply: i) The original GPRS detach procedure was initiated over an existing PS signalling connection; and ii) No SECURITY MODE COMMAND message and no Non-Access Stratum (NAS) messages relating to the PS signalling connection (e.g. PS authentication procedure, see subclause 4.7.7) were received after the DETACH REQUEST message was transmitted. b.2) RR release in Iu mode (i.e. RRC connection release) with cause different than "Directed signalling connection re-establishment", for example, "Normal", or"User inactivity" (see 3GPP TS 25.331[ None ] [23c] and 3GPP TS 44.118[ None ] [111]) The GPRS detach procedure shall be initiated again, if the following conditions apply: i) The original GPRS detach procedure was initiated over an exisiting RRC connection; and ii) No SECURITY MODE COMMAND message and no Non-Access Stratum (NAS) messages relating to the PS signalling connection (e.g. PS authentication procedure, see subclause 4.7.7) were received after the DETACH REQUEST message was transmitted. NOTE: The RRC connection release cause different than "Directed signalling connection re-establishment" that triggers the re-initiation of the GPRS detach procedure is implementation specific. b.3) RR release in Iu mode (i.e. RRC connection release) with cause "Directed signalling connection re-establishment" (see 3GPP TS 25.331[ None ] [23c] and 3GPP TS 44.118[ None ] [111]) The routing area updating procedure shall be initiated followed by completion of the GPRS detach procedure if the following conditions apply: i) The original GPRS detach procedure was not due to SIM removal; and ii) The original GPRS detach procedure was not due to a rerun of the procedure due to "Directed signalling connection reestablishment". c) Detach procedure collision GPRS detach containing cause "power off": - If the MS receives a DETACH REQUEST message before the MS initiated GPRS detach procedure has been completed, this message shall be ignored and the MS initiated GPRS detach procedure shall continue. GPRS detach containing other causes than "power off": - If the MS receives a DETACH REQUEST message before the MS initiated GPRS detach procedure has been completed, the MS shall treat the message as specified in subclause 4.7.4.2.2 with the following modifications: - If the DETACH REQUEST message received by the MS contains detach type "re-attach required", and the MS initiated detach procedure is with detach type "GPRS detach" or "Combined GPRS/IMSI detach", the MS need not initiate the GPRS attach or combined GPRS attach procedure. - If the DETACH REQUEST message received by the MS contains detach type "IMSI detach", and the MS initiated detach procedure is with detach type "IMSI detach", the MS in operation mode A or B in network operation mode I need not re-attach to non-GPRS services. - If the DETACH REQUEST message received by the MS contains detach type "IMSI detach", and the MS initiated detach procedure is with detach type "GPRS detach" or "combined GPRS/IMSI detach", the MS shall progress both procedures. The MS in operation mode A or B in network operation mode I need not re-attach to non-GPRS services. d) Detach and GMM common procedure collision GPRS detach containing cause "power off": - If the MS receives a message used in a GMM common procedure before the GPRS detach procedure has been completed, this message shall be ignored and the GPRS detach procedure shall continue. GPRS detach containing other causes than "power off" and containing detach type "IMSI detach": - If the MS receives a message used in a GMM common procedure before the GPRS detach procedure has been completed, both the GMM common procedure and the GPRS detach procedure shall continue. GPRS detach containing other causes than "power off" and containing other detach types than "IMSI detach": - If the MS receives a P-TMSI REALLOCATION COMMAND, a GMM STATUS, or a GMM INFORMATION message before the GPRS detach procedure has been completed, this message shall be ignored and the GPRS detach procedure shall continue. - If the MS receives an AUTHENTICATION AND CIPHERING REQUEST or IDENTITY REQUEST message, before the GPRS detach procedure has been completed, the MS shall respond to it as described in subclauses 4.7.7 and 4.7.8 respectively. e) Change of cell within the same RA (A/Gb mode only) If a cell change occurs within the same RA before a DETACH ACCEPT message has been received, then the cell update procedure shall be performed before completion of the detach procedure. f) Change of cell into a new routing area If a cell change into a new routing area occurs before a DETACH ACCEPT message has been received, the GPRS detach procedure shall be aborted and re-initiated after successfully performing a routing area updating procedure. If the detach procedure is performed due to the removal of the SIM/USIM or the MS is to be switched off, the MS shall abort the detach procedure and enter the state GMM-DEREGISTERED. g) Access barred because of access class control or EAB The signalling procedure for GPRS detach shall not be started. The MS starts the signalling procedure as soon as possible and if still necessary, i.e. when the barred state is removed or because of a cell change, or performs a local detach immediately or after an implementation dependent time. h) Detach and paging for non-GRPS services procedure collision If the MS receives a paging for non-GPRS services before the MS initiated combined GPRS detach procedure with detach type "IMSI detach" or "GPRS/IMSI detach" has been completed, then the paging for non-GPRS services shall be ignored and the MS initiated combined GPRS detach procedure shall continue. Figure 4.7.4/1 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : MS initiated GPRS detach procedure For the cases b and f: - Timer T3321 shall be stopped if still 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 | 4.7.4.1.4 |
4,389 | A.35 Monitoring of RRC connection usage per UE multi-RAT capability | An objective for an operator is to utilize installed network functions as much as possible for efficiency reasons because each additional technology layer constitutes an important portion of total capex expenditures. A generic followed approach is to configure network parameters so that UEs that support both new and old radio access technology layers would camp on and use services from new radio access technology for better cost per bit characteristics. Therefore, it is of utmost importance for an operator to know if new technology capable UEs are served by old radio access technology in geographical areas where new technology is overlayed on top. RRC connection usage per UE multi-RAT capability related measurement is helpful for operators to identify how efficient they utilize their deployed radio access technology layers and perform corrective actions when needed. | 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.35 |
4,390 | 11.1.1 Applicability of requirements | The requirements in this clause are applicable to UEs that support ProSe Direct Discovery. The test case applicability is in according to table 11.1.1-1 depending on set of supported UE capabilities. Table 11.1.1-1: ProSe Direct Discovery test applicability For maximum Sidelink Processes test specified in clause 11.5, the UE is required to only meet the test for the maximum channel bandwidth over the ProSe operating bands supported by the UE. Test case 11.2.3 for 5MHz channel bandwidth is applicable to UEs that support ProSe Direct Communication on Band 31 only. | 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 | 11.1.1 |
4,391 | O.4.1 Personal ME identifier | The purpose of the personal ME identifier is to discriminate between MEs used by the same user (see TS 24.279[ Combining Circuit Switched (CS) and IP Multimedia Subsystem (IMS) services; Stage 3 ] [116], subclause 4.2). NOTE: As the personal ME identifier is generated randomly, it is not guaranteed that it uniquely identifies a specific ME used by the same user. The personal ME identifier has the form PMI-XXXX, where XXXX is a 4-digit hexadecimal number. Only the hexadecimal number XXXX is coded in the personal ME identifier information element. The personal ME identifier information element is coded as shown in figure O.2/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table O.2/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The personal ME identifier is a type 3 information element with 3 octets length. Figure O.2/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Personal ME identifier Table O.2/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Personal ME identifier | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | O.4.1 |
4,392 | 5.30.2.11 UE Mobility support for SNPN | If the UE moves its 3GPP access between SNPN and PLMN, the network selection is performed as specified in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17] and UE performs initial registration as specified in clause 4.2.2.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. NOTE 1: When the UE moves its 3GPP access between SNPN and PLMN, it is up to UE implementation to activate/deactivate SNPN access mode. If the UE moves its 3GPP access between SNPNs, the network selection is performed as specified in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17], then the UE performs initial or mobility registration as specified in clause 4.2.2.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. NOTE 2: When the UE moves its 3GPP access between SNPNs, it is up to UE implementation whether and when to establish again PDU Sessions using existing mechanism. If the UE and network supports equivalent SNPNs, the AMF may provide list of equivalent SNPNs to the UE and NG-RAN. The UE may move its 3GPP access to the SNPN in the list of equivalent SNPNs without performing network selection. A UE supporting equivalent SNPNs gets a new registered SNPN ID during the Registration procedure if serving SNPN is changed. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.30.2.11 |
4,393 | 5.37.4 Network Exposure of 5GS information | 5GS and XR/media services cooperate to provide a better user experience using External Network Exposure. Based on the AF request, the 5GS can expose the following information based on the QoS Monitoring as defined in clause 5.33.3 and/or clause 5.45: - The UL and/or DL congestion information monitoring (see clause 5.45.3). Based on the PCC rule from PCF, the SMF requests the NG-RAN to report the information via GTP-U header to PSA UPF. This NG-RAN reported information is common to support congestion information exposure and to support ECN marking for L4S in PSA UPF as described in clause 5.37.3.3. In the case of congestion information exposure, the PSA UPF exposes the UL and/or DL congestion information via Nupf_EventExposure service or via SMF/PCF/NEF as described in clause 5.8.2.18. It can be applied to a Non-GBR or GBR QoS Flow. - The UL and/or DL Data rate information (see clause 5.45.4). Based on the PCC rule from PCF, the SMF requests the PSA UPF to measure and report the information. They may be exposed to the AF directly by PSA UPF via Nupf_EventExposure service or via SMF/PCF/NEF as described in clause 5.8.2.18. - The round trip delay for two service data flows considering the UL direction of a service data flow and the DL direction of another service data flow. in the same PDU Session. It is determined based on the QoS Monitoring for packet delay of individual QoS Flows as described in clause 5.33.3. The PCF derives the separate QoS monitoring policies for each direction packet delay (see clause 5.33.3) based on AF request and local policy. The PCF provides the two QoS Monitoring policies in the PCC rules for the service data flows. The PSA UPF reports the delay information per QoS Flow to the SMF. The SMF reports to PCF. The PCF derives round trip delay information based on the two direction's packet delay result for the service data flows and exposes the information to the AF directly or via NEF. - The round trip delay for one service data flow. If the service data flow is mapped to two QoS Flows (i.e. the UL traffic and DL traffic of the service data flow are separated into two QoS flows respectively) in the same PDU Session, similarly to the round trip delay for two service data flows over two QoS flows, the PCF triggers QoS Monitoring for each direction packet delay of individual QoS flows respectively and derives round trip delay based on the two direction QoS flows' packet delay monitored result. NOTE: How PCF calculates the requested round trip delay for multiple QoS Flows from delays of individual QoS Flows is not specified in this specification. The AF may provide the Alternative QoS parameter set requirements and Averaging Window to the NEF/PCF for the GBR QoS Flow as specified in clause 4.15.6.6 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.37.4 |
4,394 | 4.2.3.1 Number of E-RABs attempted to modify the QoS parameter | a) This measurement provides the number of E-RABs attempted to modify the QoS parameter. The measurement is split into subcounters per E-RAB QoS level (QCI). b) CC c) On receipt by the eNodeB/RN of an E-RAB MODIFY REQUEST message, each E-RAB attempted to modify the QoS parameter is added to the relevant measurement per QCI, the possible QCIs are included in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]. The sum of all supported per QCI measurements shall equal the total number of E-RABs attempted to modify the QoS parameter. In case only a subset of per QCI measurements is supported, a sum subcounter will be provided first. d) Each measurement is an integer value. The number of measurements is equal to the number of QCIs plus a possible sum value identified by the .sum suffix. e) The measurement name has the form ERAB.ModQoSAttNbr.QCI where QCI identifies the target E-RAB level quality of service class. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.2.3.1 |
4,395 | 5.4.12 Paging Early Indication with Paging Subgrouping Assistance 5.4.12.1 General | The RAN and UE may use a Paging Early Indication with Paging Subgrouping (PEIPS) to reduce the UE's power consumption in RRC_IDLE and RRC_INACTIVE over NR (see TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [50]). The paging subgrouping can be based on either the UE's temporary ID or a Paging Subgroup ID allocated by the AMF. Paging subgrouping based on the UE's temporary ID is implemented within the NG-RAN. For paging subgrouping based on UE's temporary ID, the UE's support is included in the UE Radio Capability for Paging, either derived by the NG-RAN from UE provided UE radio capability (see clause 5.4.4) or based on UE Radio Capability ID if UE radio capability signalling optimisation is used (see clause 5.4.4.1a). The AMF, when determining its paging strategy (see clause 5.4.3), should take into consideration whether a gNB is using Paging subgrouping based on the UE's temporary ID. NOTE: Paging messages sent to that gNB can increase UE power consumption for other UEs that support Paging Subgrouping based on the UE's temporary ID. If paging subgroups are being allocated by the AMF, then all AMFs connected to one gNB (including the AMFs in different PLMNs using 5G MOCN network sharing) shall use a consistent policy in allocating UEs to the paging subgroups. The AMF may configure up to 8 different Paging Subgroup IDs. NOTE: Because the UE uses the AMF allocated paging subgroup across all cells in its TAI-list, and, different, overlapping TAI lists can be allocated to different UEs, then to avoid UE power consumption increasing, it is likely to be necessary that all AMFs with an overlapping coverage area use a consistent policy in allocating UEs to the paging subgroups. The NG-RAN node and the UE determine per cell which paging subgrouping method to use as defined in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [50] and TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.4.12 |
4,396 | 10.14.2 PDU Session Split at UPF during PDU session resource modify (5GC initiated) | The 5GC may provide an additional UL TEID address during PDU Session Resource Modify in order to allow the MN to split the PDU session. The MN may perform the SN Addition or the MN-initiated SN Modification procedure. If the MN decides to split the PDU session, the MN provides a DL TEID address to be applied as the additional DL tunnel address and the QoS flows associated with that tunnel. Figure 10.14.2-1: PDU Session Split at UPF during PDU session resource modify 1. The 5GC provides an additional UL TEID address during PDU Session Resource Modify, to be applied as the additional NG-U tunnel in case the MN decides to split the PDU session. 2. The MN decides to setup two tunnels. If the new tunnel is to be setup at the SN, the MN uses the SN Addition procedure (as described in 10.2.2) or the MN-initiated SN Modification procedure (as described in 10.3.2) up to step 6, or up to step 8 if a QoS flow is moved to the SN and data forwarding applies. 3. The MN provides a DL TEID address to be applied as the additional DL tunnel address on the NG-U interface and the QoS flows associated with that tunnel. | 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.14.2 |
4,397 | 6.3.4.4 PUCCH / PUSCH / SRS time mask for subframe TTI | The PUCCH/PUSCH/SRS time mask defines the observation period between sounding reference symbol (SRS) and an adjacent PUSCH/PUCCH symbol and subsequent sub-frame. The time masks apply for all types of frame structures and their allowed PUCCH/PUSCH/SRS transmissions unless otherwise stated. There are no additional requirements on UE transmit power beyond that which is required in subclause 6.2.2 and subclause 6.6.2.3 Figure 6.3.4.4-1: PUCCH/PUSCH/SRS time mask when there is a transmission before SRS but not after for Frame Structure Type 1 and Frame Structure Type 2 For Frame Structure Type 3 the PUSCH/SRS time mask when there is a transmission before SRS but not after is specified in Figure 6.3.4.4-1A; the OFF power requirement applies 5 s after the end of the last symbol transmitted. Figure 6.3.4.4-1A: PUSCH/SRS time mask when there is a transmission before SRS but not after for Frame Structure Type 3 Figure 6.3.4.4-2: PUCCH/PUSCH/SRS time mask when there is transmission before and after SRS Figure 6.3.4.4-3: PUCCH/PUSCH/SRS time mask when there is a transmission after SRS but not before Figure 6.3.4.4-4: SRS time mask when there is FDD SRS blanking for Frame Structure Type 1 and Frame Structure Type 2 For Frame Structure Type 3 the PUSCH/SRS time mask with transmission after the SRS symbol and the PUSCH starting position modified by in the following subframe (clause 6.3.4.1) is specified in Figure 6.3.4.4-4A when there is SRS blanking. Figure 6.3.4.4-4A: SRS time mask when there is SRS blanking for Frame Structure Type 3 | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.3.4.4 |
4,398 | 4.3.18.2.1 Originating IMS-based MPS Session | IMS based MPS sessions are permitted to be originated from any UE, in addition to MPS-subscribed UEs. The MPS-subscribed UE, based on the MPS IMS subscription information, operator's policy and national/regional regulations, may be given priority treatment for the default bearer and the EPS bearer carrying IMS signalling in the EPS prior to and during IMS-based MPS invocation. Further, priority treatment in the EPS for signalling and media bearers may be modified/established via dynamic PCC based on the session authorization information received from the AF. As the IMS media bearer is established after the IMS session of the MPS service has been established, it can be assigned with correct ARP value when it is established. However IMS signalling related EPS bearer needs to be upgraded if it has not been assigned with an appropriate ARP setting for the MPS service when the IMS session of the MPS service has been initiated. Also to avoid cases where the default bearer may not be allocated resources in the handover case, due to low ARP priority for the PDN connection, it is necessary to assure that the default bearer has an ARP setting appropriate for the MPS service. | 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.18.2.1 |
4,399 | 5.28a Support for TSN enabled Transport Network 5.28a.1 General | When the 5GS supports interworking with IEEE TSN deployed in the transport network, the CUC that is collocated with SMF interworks with the CNC in the transport network (TN CNC) as specified in clause 46.2 of IEEE Std 802.1Q [98]. The SMF/CUC provides the stream requirements on QoS Flow basis (i.e. translated Talker group and Listener group information) via the User/Network-Interface (UNI) to the TN CNC. The TN CNC uses the stream requirements as input to configure respective path(s) and schedules in TN. Based on the results, the TN CNC provides a Status group that contains the end station communication-configuration back to the SMF/CUC. When interworking with TSN deployed in the transport network is applied, the dynamic value for the CN PDB of a Delay-critical GBR 5QI shall be configured in the SMF as described in clause 5.7.3.4. When the SMF setups a new QoS Flow, the SMF signals the dynamic value for the CN PDB and TSCAI for the QoS Flow to NG-RAN on QoS Flow basis. Upon receiving the TSCAI for a QoS Flow from the SMF, if the TSCAI includes a BAT in UL direction, the RAN may determine a dynamic value of 5G-AN PDB in UL direction for the QoS Flow. The NG-RAN provides the dynamic value of 5G-AN PDB to the SMF in a response to the QoS Flow request. The dynamic value of 5G-AN PDB is used to generate EarliestTransmitOffset as described in Annex M. The details of providing End Station related information to generate the stream requirements for the QoS Flow by the SMF/CUC are described in Annex M. If the NG-RAN and UPF support the TSN Talker and Listener functionality (i.e. implement the AN-TL and CN-TL, respectively), the SMF/CUC can communicate with the AN-TL and CN-TL via TL-Container. The TL-Container conveys the data sets defined in IEEE P802.1Qdj [146] between the SMF/CUC and AN-TL and CN-TL. The AN-TL and CN-TL enable the following functions: a) hold and buffer functionality in a case when the TSCAI contains a BAT in UL and/or DL direction. b) support of stream transformation functionality with respective information exchange with SMF/CUC. c) for SMF/CUC to retrieve the InterfaceCapabilities and/or EndStationInterfaces from the AN-TL or CN-TL. d) topology information exchange functionality via LLDP in the TN as described in clause 5.28a.3. NOTE 1: How to realize AN-TL in the base station and CN-TL in UPF is up to implementation. NOTE 2: In this Release of the specification, it is assumed that connected mode mobility is not used in deployments with a TSN enabled TN. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.28a |
4,400 | – VisitedCellInfoList | The IE VisitedCellInfoList includes the mobility history information of maximum of 16 most recently visited primary cells or time spent in any cell selection state and/or camped on any cell state in NR or E-UTRA and, in case of Dual Connectivity, the mobility history information of maxPSCellHistory most recently visited primary secondary cell group cells across all the primary cells included in the VisitedCellInfoList. The most recently visited cell is stored first in the list. The list includes cells visited in RRC_IDLE, RRC_INACTIVE and RRC_CONNECTED states for NR and RRC_IDLE and RRC_CONNECTED for E-UTRA. VisitedCellInfoList information element -- ASN1START -- TAG-VISITEDCELLINFOLIST-START VisitedCellInfoList-r16 ::= SEQUENCE (SIZE (1..maxCellHistory-r16)) OF VisitedCellInfo-r16 VisitedCellInfo-r16 ::= SEQUENCE { visitedCellId-r16 CHOICE { nr-CellId-r16 CHOICE { cgi-Info CGI-Info-Logging-r16, pci-arfcn-r16 PCI-ARFCN-NR-r16 }, eutra-CellId-r16 CHOICE { cellGlobalId-r16 CGI-InfoEUTRA, pci-arfcn-r16 PCI-ARFCN-EUTRA-r16 } } OPTIONAL, timeSpent-r16 INTEGER (0..4095), ..., [[ visitedPSCellInfoListReport-r17 VisitedPSCellInfoList-r17 OPTIONAL ]] } VisitedPSCellInfoList-r17 ::= SEQUENCE (SIZE (1..maxPSCellHistory-r17)) OF VisitedPSCellInfo-r17 VisitedPSCellInfo-r17 ::= SEQUENCE { visitedCellId-r17 CHOICE { nr-CellId-r17 CHOICE { cgi-Info-r17 CGI-Info-Logging-r16, pci-arfcn-r17 PCI-ARFCN-NR-r16 }, eutra-CellId-r17 CHOICE { cellGlobalId-r17 CGI-InfoEUTRALogging, pci-arfcn-r17 PCI-ARFCN-EUTRA-r16 } } OPTIONAL, timeSpent-r17 INTEGER (0..4095), ... } -- TAG-VISITEDCELLINFOLIST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.