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
⌀ |
|---|---|---|---|---|---|---|---|
5,901 | 9.9.4.6 Linked EPS bearer identity | The purpose of the Linked EPS bearer identity IE is to identify the default bearer that is associated with a dedicated EPS bearer or to identify the EPS bearer (default or dedicated) with which one or more packet filters specified in a traffic flow aggregate are associated. The Linked EPS bearer identity information element is coded as shown in figure 9.9.4.6.1 and table 9.9.4.6.1. The Linked EPS bearer identity is a type 1 information element. Figure 9.9.4.6.1: Linked EPS bearer identity information element Table 9.9.4.6.1: Linked EPS bearer identity information element | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.9.4.6 |
5,902 | Annex G (normative): Support of GERAN/UTRAN access by SMF+PGW-C | This annex applies when the SMF+PGW-C is enhanced to support GERAN/UTRAN access via Gn/Gp interface as specified in Annex L of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. NOTE 1: For the interface with the serving node of the UE, the SMF+PGW-C is assumed to behave as the Control Plane of the PGW described in Annex D of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. SMF+PGW-C is selected by the SGSN using existing mechanism as specified in Annex A of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [79]. NOTE 2 If network deployment requires both SMF+PGW-C and legacy PGW, selection of SMF+PGW-C by SGSN can be achieved based on e.g. APN and optionally APN-OI Replacement as specified Annex A of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [79]. When a SMF+PGW-C is used for GERAN/UTRAN access, at PDP context activation, the SMF+PGW-C allocates a PDU Session ID (in the network range) and uses this PDU Session ID over SBI interface (e.g. N7). The following procedures from TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [79] are not supported when SMF+PGW-C is used for GERAN/UTRAN access: - Network requested PDP Context Activation Procedure (clause 9.2.2.2 of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [79]). - Secondary PDP Context Activation Procedure (clause 9.2.2.1.1 of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [79]). - Network Requested Secondary PDP Context Activation Procedure using Gn (clause 9.2.2.1.3 of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [79]). When SMF+PGW-C is used for GERAN/UTRAN access and interacts with PCF, the SMF+PGW-C uses SM policy association procedures as specified in clause 4.11.0a.2 with the following modification: - The SMF+PGW-C performs mapping of QoS parameters as follows: - The SMF+PGW-C maps the Release 99 QoS parameters received from Gn/Gp interface to EPS QoS parameters as specified in Annex E of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13], which is then used to derive QoS parameters over N7 interface as specified in clause 4.11.0a.2. - the SMF+PGW-C uses QoS parameters over N7 interface to derive EPS QoS parameters as specified in clause 4.11.0a.2, which is then mapped to Release 99 QoS parameters for Gn/Gp interface as specified in Annex E of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. - For SM Policy Association Establishment Procedure, the SMF+PGW-C invokes Npcf_SMPolicyControl_Create Service operation taking input from the information elements received in Create PDP Context Request message (specified in TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [79]), including mapping of QoS parameters as mentioned above as well as GERAN/UTRAN location management related information. - For SM Policy Association Modification procedure initiated by the SMF+PGW-C, the SMF+PGW-C invokes Npcf_SMPolicyControl_Update Service operation taking input from the information elements received in Update PDP Context Request message (specified in TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [79]), including mapping of QoS parameters as mentioned above, as well as GERAN/UTRAN location management related information. - For SM Policy Association Modification procedure initiated by the PCF, the SMF+PGW-C may receive PCC Rules and PDU Session Policy Information. The SMF+PGW-C performs mapping of QoS parameters as mentioned above. - For SM Policy Association Termination procedure, the SMF+PGW-C invokes Npcf_SMPolicyControl_Delete service operation (including GERAN/UTRAN location management related information) when receiving Delete PDP Context Request message (specified in TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [79]). - Even though N7 supports Ethernet PDU Session Type, as Ethernet PDN Type is not supported in GERAN/UTRAN, it is assumed that if the UE moves from E-UTRAN to GERAN/UTRAN, Ethernet PDN connections are released and thus no information related with Ethernet PDU Session Type shall be exchanged over N7 when a UE is served by GERAN/UTRAN. - Even though GERAN/UTRAN specifications foresee other alternatives, the Bearer Binding is performed by the SMF+PGW-C acting as a PGW. - Access Network Information reporting with a granularity of GERAN/UTRAN cell is supported over N7 and N5. When the UE moves between E-UTRAN and GERAN/UTRAN, the SMF+PGW-C may invoke SM Policy Association Modification procedure based on the Policy Control Request Triggers as specified in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. NOTE 3: Support for IP address preservation upon indirect mobility between 5GS and GERAN/UTRAN for PDN sessions established in EPC is described in clause 5.17.2.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. IP address preservation is not supported for direct mobility between 5GS and GERAN/UTRAN, nor for indirect mobility cases when the PDN session is established in 5GS or in GERAN/UTRAN. NOTE 4: Usage of SMF+PGW-C to serve a PDP context requires no change to SGSN(s) (and thus to roaming partners in Home Routed roaming) as it is assumed that DNS records are properly configured to map APN to SMF+PGW-C acting as PGW. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | Annex |
5,903 | 4.2.2.7 Distribution of Normally Released Call (QCI1 E-RAB) Duration | a) This measurement provides the histogram result of the samples related to normally released call (QCI1 E-RAB) duration collected during measurement period duration. b) CC c) Each sample is measured from the point in time the QCI1 E-RAB has been successfully established via initial Context setup or additional E-RAB setup procedure or incoming handover till the point in time the E-RAB is released via eNB or EPC initiated release procedure or successful outgoing handover according to 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] due to normal release cause. Triggering is done for the bin the given sample falls in. d) Each measurement is an integer value. e) The measurement name has the form QCI1ERAB.NormCallDurationBinX where X denotes the X-th bin from total number of N configured bins. X-th bin stands for the normal call duration which is within the range from tx-1 to tx. f) Cell g) Valid for packet switched traffic h) EPS i) Each histogram function is represented by the configured number of bins with configured bin width by operator. | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.2.2.7 |
5,904 | 5.8.16.2 NR sidelink U2U Relay UE threshold conditions | A UE capable of NR sidelink U2U Relay UE operation shall: 1> if the threshold conditions for integrated Discovery specified in this clause were previously not met: 2> if the sd-RSRP-Thresh-DiscConfig is not configured, or if the SL-RSRP of the Direct Communication Request message with integrated Discovery received from the Source NR sidelink U2U Remote UE is available and is above sd-RSRP-Thresh-DiscConfig if configured: 3> consider the threshold conditions to be met (entry); 1> else: 2> if the SL-RSRP of the Direct Communication Request message with integrated Discovery received from the Source NR sidelink U2U Remote UE is available and is below sd-RSRP-Thresh-DiscConfig by sd-hystMaxRelay if configured: 3> consider the threshold conditions not to be met (leave); 1> if the threshold conditions for Model B Discovery specified in this clause were previously not met: 2> if the sd-RSRP-Thresh-DiscConfig is not configured, or if the SD-RSRP of the Model B Discovery message received from the Source NR sidelink U2U Remote UE is available and is above sd-RSRP-Thresh-DiscConfig if configured: 3> consider the threshold conditions to be met (entry); 1> else: 2> if the SD-RSRP of the Model B Discovery message received from the Source NR sidelink U2U Remote UE is available and is below sd-RSRP-Thresh-DiscConfig by sd-hystMaxRelay if configured: 3> consider the threshold conditions not to be met (leave); | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.16.2 |
5,905 | 6.4.4 Cipher key and integrity key identification | The key set identifier (KSI) is a number which is associated with the cipher and integrity keys derived during authentication. The key set identifier is allocated by the network and sent with the authentication request message to the mobile station where it is stored together with the calculated cipher key CK and integrity key IK. KSI in UMTS corresponds to CKSN in GSM. The USIM stores one KSI/CKSN for the PS domain key set and one KSI/CKSN for the CS domain key set. The purpose of the key set identifier is to make it possible for the network to identify the cipher key CK and integrity key IK which are stored in the mobile station without invoking the authentication procedure. This is used to allow re-use of the cipher key CK and integrity key IK during subsequent connection set-ups. KSI and CKSN have the same format. The key set identifier is three bits. Seven values are used to identify the key set. A value of '111' is used by the mobile station to indicate that a valid key is not available for use. At deletion of the cipher key and integrity key, the KSI is set to '111'. The value '111' in the other direction from network to mobile station is reserved. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.4.4 |
5,906 | – ReportInterval | The IE ReportInterval indicates the interval between periodical reports. The ReportInterval is applicable if the UE performs periodical reporting (i.e. when reportAmount exceeds 1) when reportType is set to either eventTriggered, periodical, cli-EventTriggered or cli-Periodical. Value ms120 corresponds to 120 ms, value ms240 corresponds to 240 ms and so on, while value min1 corresponds to 1 min, min6 corresponds to 6 min and so on. ReportInterval information element -- ASN1START -- TAG-REPORTINTERVAL-START ReportInterval ::= ENUMERATED {ms120, ms240, ms480, ms640, ms1024, ms2048, ms5120, ms10240, ms20480, ms40960, min1,min6, min12, min30 } -- TAG-REPORTINTERVAL-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,907 | 11.2.2 Features supported by direct peer GTP-C entities | A node shall signal to a direct peer node the list of features it supports by sending the Sending Node Features IE in every Echo Request and Echo Response messages to that node. An exception to this is where the sending node does not support or use any features towards the peer node and is not prepared to accept a message which is constructed by making use of any features. The peer receiving the Sending Node Features IE shall store the list of features supported by the sending node per IP address and only update this list based on the Sending Node Features IE in the Echo Request and Echo Response messages, and it shall only use common supported features to initiate subsequent GTPv2 messages towards this IP address. Receipt of an Echo Request or an Echo Response message without the Sending Node Features IE shall indicate that the sending node does not support any feature specified in Table 8.83-1 on the corresponding interface. | 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 | 11.2.2 |
5,908 | 6.16.2.3 Connection Resume in CM-IDLE with Suspend to a new ng-eNB | When the UE using user plane CIoT 5GS Optimization decides to resume the RRC connection in CM-IDLE with suspend, the UE sends the RRC Resume Request message on SRB0 (i.e. it is not integrity protected). The UE shall include I-RNTI and a ShortResumeMAC-I in RRC Resume Request message. The I-RNTI is used for context identification and its value shall be the same as the I-RNTI that the UE had received from the source ng-eNB in the RRC Release with releaseCause set to rrc-suspend message in the source cell. The ShortResumeMAC-I is a 16-bit message authentication token, the UE shall calculate it using the integrity algorithm (EIA) in the stored AS security context, which was negotiated between the UE and the source ng-eNB and the current KRRCint with the following inputs: - KEY : it shall be set to current KRRCint; - BEARER : all its bits shall be set to 1. - DIRECTION : its bit shall be set to 1; - COUNT : all its bits shall be set to 1; - MESSAGE : it shall be set to VarShortResumeMAC-Input as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [69] for ng-eNB with the following inputs: source C-RNTI, source PCI, resume constant, target Cell-ID. The source PCI and source C-RNTI are associated with the cell where the UE was suspended. The target Cell-ID is the identity of the target cell where the UE sends the RRC Resume Request message. The resume constant allows differentiation of VarShortResumeMAC from VarShortMAC. For protection of all RRC messages except RRC Reject message following the sent RRC Resume Request message, the UE shall derive a KNG-RAN* using the target PCI, target EARFCN-DL and the KgNB/NH based on either a horizontal key derivation or a vertical key derivation as defined in clause 6.9.2.1.1 and Annex A.12. The UE shall further derive KRRCint, KRRCenc, KUPenc (optionally), and KUPint (optionally) from the newly derived KNG-RAN*. Then the UE resets all PDCP COUNTs to 0 and activates the new AS keys in PDCP layer. When the target ng-eNB receives the RRC Resume Request message from the UE, the target ng-eNB extracts the I-RNTI from the RRC Resume Request message. The target ng-eNB contacts the source ng-eNB based on the information in the I-RNTI by sending an Xn-AP Retrieve UE Context Request message with the following included: I-RNTI, ShortResumeMAC-I and target Cell-ID, in order to allow the source ng-eNB to validate the UE request and to retrieve the UE context including the UE 5G AS security context. The source ng-eNB retrieves the stored UE context including the UE 5G AS security context from its database using the I-RNTI. The source ng-eNB verifies the shortResumeMAC-I using the current KRRCint key stored in the retrieved UE 5G AS security context (calculating the shortResumeMAC-I in the same way as described above). If the verification of the shortResumeMAC-I is successful, then the source ng-eNB calculates KNG-RAN* using the target cell PCI, target EARFCN-DL and the KgNB/NH in the current UE 5G AS security context based on either a horizontal key derivation or a vertical key derivation according to whether the source ng-eNB has an unused pair of {NCC, NH} as described in Annex A.12. The source ng-eNB can obtain the target PCI and target EARFCN-DL from a cell configuration database by means of the target Cell-ID which was received from the target ng-eNB. Then the source ng-eNB shall respond with an Xn-AP Retrieve UE Context Response message to the target ng-eNB including the UE context that contains the UE 5G AS security context. The UE 5G AS security context sent to the target ng-eNB shall include the newly derived KNG-RAN*, the NCC associated to the KNG-RAN*, the UE EPS security capabilities, UP security policy, the UP security activation status, and the ciphering and integrity algorithms used by the UE with the source cell. The target ng-eNB shall check if it supports the ciphering and integrity algorithms the UE used with the last source cell. If the target ng-eNB does not support the ciphering and integrity algorithms used in the last source cell or if the target ng-eNB prefers to use different algorithms than the source ng-eNB, then the target ng-eNB shall send an RRC Setup message on SRB0 to the UE in order to proceed with RRC connection establishment as if the UE was in RRC_IDLE (i.e., a fallback procedure). If the target ng-eNB supports the ciphering and integrity algorithms used with the last source cell and these algorithms are the chosen algorithms by the target ng-eNB, the target ng-eNB shall derive new AS keys (RRC integrity key, RRC encryption key and UP keys) using the algorithms the UE used with the source cell and the received KNG-RAN*. The target ng-eNB shall reset all PDCP COUNTs to 0 and activate the new keys in PDCP layer. The target ng-eNB shall respond to the UE with an RRC Resume message on SRB1 which is integrity protected and ciphered in PDCP layer using the new RRC keys. If the UP security activation status can be supported in the target ng-eNB, the target ng-eNB shall use the UP security activations that the UE used at the last source cell. When the UE receives the RRC Resume message, the UE shall decrypt the message using the KRRCenc that was derived based on the newly derived KNG-RAN*. The UE shall also verify the RRC Resume message by verifying the PDCP MAC-I using the KRRCint that was derived from the newly derived KNG-RAN* If verification of the RRC Resume message is successful, the UE shall delete the current KRRCint key and the UE shall save the KRRCint, KRRCenc, KUPenc (optionally), and KUPint (optionally) from the newly derived KNG-RAN* as part of the UE current AS security context. In this case, the UE shall send the RRC Resume Complete message both integrity protected and ciphered to the target ng-eNB on SRB1 using the current KRRCint and KRRCenc. The UE shall use the UP security activations status to protect the UP data. If the UE receives RRC Reject message from the target ng-eNB in response to the RRC Resume Request message, the UE shall delete newly derived AS keys used for connection resumption attempt, including newly derived KNG-RAN*, newly derived RRC integrity key, RRC encryption key and UP keys, and keep the current KRRCint and the KgNB/NH in its current AS context. In that case, for the next resume to any target ng-eNB, the UE shall start with the same AS security context as it had when it was suspended originally, i.e., same KgNB/NH shall act as base key for derivation of new KNG-RAN*. After a successful resume, the target ng-eNB shall perform Path Switch procedure with the AMF as is done in case of X2-handover. The AMF shall verify the UE security capability as described in the clause 6.7.3.1, and the SMF shall verify the UE’s UP security policy as described in the clause 6.6.1. When EDT or PUR feature is used, the UE shall use newly derived KUPenc to encrypt the UL UP data according to the UP security activations before transmitting the RRC Resume Request message, and send the encrypted UL UP data in the PDCP layer with RRC Resume Request message to the target ng-eNB. The target ng-eNB shall use newly derived KUPenc key to get the UL UP data according to the UP security activations after retrieving UE context from the source ng-eNB. The UE and the target eNB shall use the same KUPenc key and UP security activation to protect the DL data (if included) in PDCP layer in the RRC Release or RRC Resume message. NOTE: UP security policy is only applicable for UP ciphering as UP integrity protection is not supported. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.16.2.3 |
5,909 | 4.3.3 PDU Session Modification 4.3.3.1 General | The procedure is used when one or several of the QoS parameters exchanged between the UE and the network are modified and/or to send updated ECS Address Configuration Information as defined in clause 6.5.2 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74] to the UE and/or to send the updated DNS server address as defined in clause 6.2.3.2.3 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74]. NOTE 1: The conditions when to use this procedure for QoS change as well as the QoS parameters exchanged between the UE and the network are defined in clause 5.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. NOTE 2: The conditions when to use this procedure for the exchange of ECS Address Configuration Information are described in clause 6.5.2 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74]. NOTE 3: The conditions when to use this procedure for the update of DNS server address are described in clause 6.2.3.2.3 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.3 |
5,910 | .2 Delete Bearer Request | The direction of this message shall be from PGW to SGW, from SGW to MME/S4-SGSN and from PGW to TWAN/ePDG (see Table 6.1-1). A Delete Bearer Request message shall be sent on the S5/S8 and S4/S11 interfaces as part of the following procedures: - PGW or MME initiated bearer deactivation procedures, - UE requested Bearer Resource Modification, - MS and SGSN Initiated Bearer Deactivation procedure using S4 or - PGW initiated bearer deactivation procedure using S4. In the above cases, this Request is sent by the PGW to the SGW and shall be forwarded to the MME or S4-SGSN. The message shall also be sent on the S4/S11 interface by the SGW to the SGSN/MME to delete the bearer resources on the other ISR associated CN node if the ISRAI flag is not set in the Modify Bearer Request/Modify Access Bearers Request message. The message shall also be sent on the S4/S11 interface by the SGW to the SGSN/MME to delete the bearer resources on the other ISR associated CN node in the TAU/RAU/Handover procedures if the ISR related Cause IE is included in the Delete Session Request message. The message shall also be sent on the S2b interface by the PGW to the ePDG as part of PGW Initiated Bearer Resource Allocation Deactivation procedure with GTP on S2b. The message shall also be sent on the S2a interface by the PGW to the TWAN as part of the PGW Initiated Bearer Resource Allocation Deactivation in WLAN on GTP on S2a procedure. The message may also be sent on the S11/S4 interface by the SGW to the MME/S4 SGSN when the SGW receives the Error Indication from PGW for the default bearer or the ICMP message from a PGW that indicates the UE specific error indication as specified in 3GPP TS 23.007[ Restoration procedures ] [17]. The message shall also be sent on the S5/S8 or S2a/S2b interface by the PGW to the SGW or to the TWAN/ePDG and on the S11/S4 interface by the SGW to the MME/S4-SGSN as part of the Network-initiated IP flow mobility procedure, as specified by 3GPP TS 23.161[ Network-Based IP Flow Mobility (NBIFOM); Stage 2 ] [71]. The message shall also be sent on the S5/S8 interface by the PGW to the SGW, as part of EPS to 5GS mobility without N26 interface, ePDG/EPC to 5GS handover, EPS to 5GC/N3IWF handover, as specified in 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [83]. If the UE uses NB-IoT, WB-EUTRAN or GERAN Extended Coverage with increased NAS transmission delay (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [23] and 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [5]), the MME/SGSN should proceed as specified for a UE in ECM-IDLE state with extended idle mode DRX enabled in clause 5.4.4.1 of 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3]. Possible Cause values are: - "RAT changed from 3GPP to Non-3GPP", - "ISR deactivation", - "Access changed from Non-3GPP to 3GPP", - "Reactivation requested", - "PDN reconnection to this APN disallowed", - "PDN connection inactivity timer expires", - "Local release", - "Multiple accesses to a PDN connection not allowed", - "EPS to 5GS Mobility". Table .2-1 specifies the presence of IEs in this message. Table .2-1: Information Elements in a Delete Bearer Request NOTE: In the case that the procedure was initiated by a UE Requested Bearer Resource Modification Procedure for an E-UTRAN as specified by 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [23], then there will be only one instance of the EPS Bearer IDs IE in the Delete Bearer Request. Table .2-2: Bearer Context within Delete Bearer Request Table 7.2.9.2-3: Load Control Information within Delete Bearer Request Table 7.2.9.2-4: Overload Control Information within Delete Bearer Request Table 7.2.9.2-5: PGW Change Info within Delete Bearer Request | 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 |
5,911 | 4.11.5.3 UE Requested PDU Session Establishment procedure | For PDU Session via 3GPP, the following impacts are applicable to clause 4.3.2.2 (UE Requested PDU Session Establishment procedure) to support interworking with EPS: In clause 4.3.2.2.1 Non-roaming and Roaming with local breakout: - Step 1: In PDU Session Establishment Request message, the UE includes also the UE capability of Ethernet PDN type support in EPS to the SMF (or H-SMF in home routing roaming); - Step 3: The AMF determines that a PDU Session supports EPS interworking with N26 or without N26, based on e.g. 5GMM capability (e.g. "S1 mode supported"), UE subscription data (e.g. Core Network Type Restriction to EPS, EPC interworking support per (S-NSSAI, subscribed DNN)) and network configuration if EPS interworking with N26 or without N26 is supported. The AMF then includes in the Nsmf_PDUSession_CreateSMContext an indication whether the PDU Session supports EPS Interworking and whether EPS Interworking is done with N26 or without N26. For PDU Session with Request Type "initial emergency request", the AMF decides the EPS interworking with N26 or without N26 based on 5GMM capability and local configuration. For PDU Session with Request Type "Existing Emergency PDU Session", the AMF shall use Emergency Information received from HSS+UDM and the S-NSSAI locally configured in Emergency Configuration Data. If the Request Type indicates "Existing PDU Session" the AMF selects the SMF based on SMF-ID or SMF+PGW-C FQDN received from UDM during the Registration or Subscription Profile Update Notification procedure. The case where the AMF does not recognize the PDU Session ID or the subscription context that the AMF received from UDM neither contains an SMF ID nor a SMF+PGW-C FQDN corresponding to the PDU Session ID constitutes as an error case. NOTE 1: If the AMF receives from the UDM, for a PDU Session, both a SMF ID and a SMF+PGW-C FQDN, the SMF ID takes precedence. If the AMF has stored APN Rate Control Status and the PDU Session is considered a new first PDU Session to a DNN that is the same as the APN in stored APN Rate Control Status and interworking with EPC is enabled for this PDU Session, then the AMF sends the APN Rate Control Status to the SMF. The AMF indicates to the SMF whether the UE support User Plane Integrity Protection with EPS and whether the AMF has associated functionality. - Step 4: If the EPS Interworking indication received from AMF indicates that the UE supports EPS interworking and the SMF determines, based on the EPS interworking support indication from the AMF and additional UE subscription data (e.g. whether UP integrity protection of UP Security Enforcement Information is not set to required, EPS interworking is allowed for this DNN and S-NSSAI), that the PDU Session supports EPS interworking, the SMF+PGW-C FQDN for S5/S8 interface is included in the Nudm_UECM_Registration Request. - Step 10a: If APN Rate Control Status is received from the AMF then the SMF provides the configured APN Rate Control Status to the PGW-U+UPF. - Step 13 In PDU Session Establishment Accept message, the SMF also includes indication of Ethernet PDN type supported if the Ethernet PDN type is supported by both the UE and the SMF+PGW-C. The SMF and the UE stores the information if Ethernet PDN type is supported for later use when UE moves from 5GS to EPS. - Step 16c: For PDU Session establishment with Request Type "initial PDU Session", if the SMF+PGW-C selects the same PCF as the PCF ID received from AMF as specified in clause 4.3.2.2.1 and if the PDU Session supports EPC interworking, the SMF provide the selected PCF ID in the UDM using the Nudm_UECM_Registration service operation. NOTE 2: The subscription data "EPS interworking support indication" is used by AMF when determining the EPS interworking support for the PDU Session. Therefore, when the UE establishes the PDU Session via the 3GPP access, the SMF does not need to consider the same subscription data "EPS interworking support indication" again. In clause 4.3.2.2.2 Home-routed Roaming: - Step 3a: Same impact as for step 3 for the non-roaming and roaming with local breakout case above. - Step 5: Same impact as for step 10a for the Non-roaming and Roaming with Local Breakout case above. - Step 6 The V-SMF pass the EPS interworking support indication received from the AMF to the H-SMF in Nsmf_PDUSession_Create. - Step 7: If the EPS interworking indication received from V-SMF indicates that the PDU Session supports EPS interworking and the H-SMF determines, based on the EPS interworking support indication from the AMF and additional information such as UP integrity protection of UP Security Enforcement Information as described in clause 4.11.1.1, that the PDU Session supports EPS interworking, the SMF+PGW-C FQDN for S5/S8 interface is included in the Nudm_UECM_Registration Request. - Step 15: Same impact as in step 13 for the non-roaming and roaming with local breakout case above with the difference that it's the home SMF+PGW-C that includes the indication of Ethernet PDN type supported. For interworking with the N26 interface, if the PDU Session supports interworking with EPS, the SMF+PGW-C invokes EBI allocation as described in clause 4.11.1.4.1. For non-emergency PDU Session via non-3GPP, the AMF determines if EPS interworking is supported and sends the indication to the SMF in the same way as for PDU Session via 3GPP. The SMF makes the final decision on the EPS interworking in the same way as for PDU Session via 3GPP with the following modification: - If the SMF does not receive the interworking indication, the SMF makes its decision based on subscription. For emergency PDU Session via non-3GPP, the AMF determines if EPS interworking is supported and sends the indication to the SMF in the same way as for emergency PDU Session via 3GPP supporting EPS interworking. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.5.3 |
5,912 | 8.17 RAT Type | RAT Type is coded as depicted in Figure 8.17-1. Figure 8.17-1: RAT Type Table 8.17-1: RAT Type values NOTE 1: For S4-SGSN, currently it is only possible to detect the difference between GERAN and UTRAN when GERAN Gb mode is used. If GERAN Iu mode is used, then an S4-SGSN may not be able to detect the difference between GERAN and UTRAN. Across the Gb interface, the SGSN may also not be able to detect the difference between GERAN and GAN. If S4-SGSN cannot detect that the HSPA Evolution 3GPP TR 25.999 [46] network is behind the Iu interface, the S4-SGSN will send the "UTRAN" RAT Type. NOTE 2: For the Iu interface case, if the SGSN detects UTRAN or HSPA, it sets the RAT-Type to "UTRAN". If the SGSN detects HSPA+, it sets the RAT-Type to "HSPA Evolution", otherwise the SGSN will send the "UTRAN" RAT Type. NOTE 3: The MME sets the LTE-M RAT-Type for a UE accessing E-UTRAN and indicating Category M from the eNB or sets the LTE-M Satellite RAT types for a UE accessing satellite E-UTRAN and indicating Category M from the eNB, as specified in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3]. NOTE 4: The MME sets the RAT-Type to WB-E-UTRAN(LEO) / WB-E-UTRAN(MEO) / WB-EUTRAN(GEO) / WB-E-UTRAN(OTHERSAT) for a UE accessing E-UTRAN with satellite access (EUTRAN-LEO, EUTRAN-MEO, EUTRAN-GEO or EUTRAN-OTHERSAT), and without indicating Category M satellite from the eNB. NOTE 5: The MME sets the RAT-Type to EUTRAN-NB-IoT(LEO) / EUTRAN-NB-IoT(MEO) / EUTRAN-NB-IoT(GEO) / EUTRAN-NB-IoT(OTHERSAT) for a UE accessing EUTRAN-NB-IoT with satellite access (NBIoT-LEO, NBIoT-MEO, NBIoT-GEO or NBIoT-OTHERSAT). NOTE 6: The MME sets the RAT-Type to LTE-M(LEO) / LTE-M(MEO) / LTE-M(GEO) / LTE-M(OTHERSAT) for a UE accessing E-UTRAN with satellite access (EUTRAN-LEO, EUTRAN-MEO, EUTRAN-GEO or EUTRAN-OTHERSAT) and indicating Category M satellite from the eNB. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 8.17 |
5,913 | 6.10.3.2 Mapping to resource elements | For antenna port 5, in a physical resource block with frequency-domain index assigned for the corresponding PDSCH transmission, the reference signal sequence shall be mapped to complex-valued modulation symbols with in a subframe according to: Normal cyclic prefix: Extended cyclic prefix: where is the counter of UE-specific reference signal resource elements within a respective OFDM symbol of the PDSCH transmission. The cell-specific frequency shift is given by . The mapping shall be in increasing order of the frequency-domain index of the physical resource blocks assigned for the corresponding PDSCH transmission. The quantity denotes the assigned bandwidth in resource blocks of the corresponding PDSCH transmission. Figure 6.10.3.2-1 illustrates the resource elements used for UE-specific reference signals for normal cyclic prefix for antenna port 5. Figure 6.10.3.2-2 illustrates the resource elements used for UE-specific reference signals for extended cyclic prefix for antenna port 5. The notation is used to denote a resource element used for reference signal transmission on antenna port. Figure 6.10.3.2-1: Mapping of UE-specific reference signals, antenna port 5 (normal cyclic prefix) Figure 6.10.3.2-2: Mapping of UE-specific reference signals, antenna port 5 (extended cyclic prefix) For antenna ports , , , , , , or the antenna ports indicated in Table 6.3.4.4-1 in a physical resource block with frequency-domain index assigned for the corresponding PDSCH transmission, a part of the reference signal sequence shall be mapped to complex-valued modulation symbols in a subframe according to Normal cyclic prefix: where The sequence is given by Table 6.10.3.2-1. Table 6.10.3.2-1: The sequence for normal cyclic prefix Extended cyclic prefix: where The sequence is given by Table 6.10.3.2-2. Table 6.10.3.2-2: The sequence for extended cyclic prefix and for slot/subslot-PDSCH For extended cyclic prefix, UE-specific reference signals are not supported on antenna ports 9 to 14. For slot-PDSCH transmission, the baseline pattern (see 'Baseline' in Figure 6.10.3.2-2A) of UE-specific reference signals is defined as follows. It is applied in MBSFN subframes. where - - - - - - and - if the slot where the PDSCH is transmitted in () fulfils - if the slot where the PDSCH is transmitted in () fulfils The sequence is given by Table 6.10.3.2-2. For slot-PDSCH transmission in normal subframes,is generated as for the baseline slot-PDSCH UE-specific reference signal pattern for the same values of , while is given by and depends on the cell-specific frequency shift as follows (see 'v0', 'v1' and 'v2' in Figure 6.10.3.2-2A for , , and , respectively): - For , , - For , , - For , . Figure 6.10.3.2-2A: Mapping of UE-specific reference signals for slot-PDSCH, antenna ports 7, 8, 9 and 10 (normal cyclic prefix) For subslot-PDSCH transmission, the baseline pattern (see 'Baseline' in Figure 6.10.3.2-2B) of UE-specific reference signals is defined as follows. It is applied if the presence of UE-specific reference signals is indicated in the DCI associated with the subslot-PDSCH (see DMRS position indicator field in TS 36.212[ Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding ] [3]), and in downlink subslots where the baseline pattern, including all the REs associated with if the parameter maxLayersMIMO-STTI is configured with 2 layers, or if the parameter maxLayersMIMO-STTI is configured with 4 layers, has no overlapping resource element with CRS and no overlapping resource element with configured zero-power and non-zero-power CSI reference signals: where The sequence is given by Table 6.10.3.2-2.For subslot-PDSCH transmission in normal subframes, in downlink subslots where the baseline pattern, including all the REs associated with if the parameter maxLayersMIMO-STTI is configured with 2 layers, or if the parameter maxLayersMIMO-STTI is configured with 4 layers, has overlapping resource elements with configured zero-power or non-zero-power CSI reference signals or has overlapping resource elements with CRS, if the presence of UE-specific reference signals is indicated in the DCI associated (see DMRS position indicator field in TS 36.212[ Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding ] [3]) with the subslot-PDSCH, a shifted pattern of UE-specific reference signals is applied. In the shifted pattern,is generated as for the baseline subslot-PDSCH UE-specific reference signal pattern for the same value of , while is given by and depends on the cell-specific frequency shift as follows (see also 'v0','v1' and 'v2' in Figure 6.10.3.2-2B for , , and , respectively): - For , , - For , , - For , , For subslot-PDSCH transmission in MBSFN subframes, in downlink subslots where the baseline pattern, including all the REs associated with if the parameter maxLayersMIMO-STTI is configured with 2 layers, or if the parameter maxLayersMIMO-STTI is configured with 4 layers, has overlapping resource elements with configured zero-power or non-zero-power CSI reference signals, if the presence of UE-specific reference signals is indicated in the DCI associated (see DMRS position indicator field in TS 36.212[ Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding ] [3]) with the subslot-PDSCH, the shifted pattern of UE-specific reference signals for , as defined above, is applied (see 'v0' in Figure 6.10.3.2-2B for ). Figure 6.10.3.2-2B: Mapping of UE-specific reference signals for subslot-PDSCH, antenna ports 7, 8, 9 and 10 (normal cyclic prefix) Resource elements used for transmission of UE-specific reference signals to one UE on any of the antenna ports in the set , where or shall - not be used for transmission of PDSCH on any antenna port in the same slot, and - not be used for UE-specific reference signals to the same UE on any antenna port other than those in in the same slot. Figure 6.10.3.2-3 illustrates the resource elements used for UE-specific reference signals for normal cyclic prefix for antenna ports 7, 8, 9 and 10. Figure 6.10.3.2-4 illustrates the resource elements used for UE-specific reference signals for extended cyclic prefix for antenna ports 7, 8. For BL/CE UEs, if downlink resource reservation is enabled for the UE as specified in [9], and the Resource reservation field in the DCI is set to 1, then in case of PDSCH transmission associated with C-RNTI or SPS C-RNTI using UE-specific MPDCCH search space including PDSCH transmission without a corresponding MPDCCH, - If all OFDM symbols in a PRB are reserved, the demodulation reference signal transmission in that PRB is dropped. Figure 6.10.3.2-3: Mapping of UE-specific reference signals, antenna ports 7, 8, 9 and 10 (normal cyclic prefix) Figure 6.10.3.2-4: Mapping of UE-specific reference signals, antenna ports 7 and 8 (extended cyclic prefix) | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.10.3.2 |
5,914 | 4.5.1.3.3 Paging response in Iu mode (Iu mode only) | The network may initiate the paging procedure for CS services when the MS is IMSI attached for CS services. To initiate the procedure, the MM entity requests the RR sublayer to initiate paging (see 3GPP TS 25.331[ None ] [23c], 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [19c] and 3GPP TS 44.118[ None ] [111]) for CS services. At reception of a paging message, the RR sublayer in the MS shall deliver a paging indication to the MM sublayer if the paging was initiated by the MM entity in the network (see 3GPP TS 25.331[ None ] [23c] and 3GPP TS 44.118[ None ] [111]) and the MS shall stop the timer T3246, if running. The MS shall respond with the PAGING RESPONSE message defined in 3GPP TS 44.018[ None ] [84], subclause 9.1.25. For reasons of backward compatibility the paging response shall use the RR protocol discriminator. If the MS receives a paging request for CS services during an ongoing MM procedure, and the MS has already requested the establishment of a radio connection, the MS shall ignore the paging request and the MS and the network shall continue the MM procedure. | 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.5.1.3.3 |
5,915 | Annex C (informative): I-RNTI Reference Profiles | The I-RNTI provides the new NG-RAN node a reference to the UE context in the old NG-RAN node. How the new NG-RAN node is able to resolve the old NG-RAN ID from the I-RNTI is a matter of proper configuration in the old and new NG-RAN node. Table C-1 below provides some typical partitioning of a 40bit I-RNTI, assuming the following content: - UE specific reference: reference to the UE context within a logical NG-RAN node; - NG-RAN node address index: information to identify the NG-RAN node that has allocated the UE specific part; NOTE: RAT-specific information may be introduced in a later release, containing information to identify the RAT of the cell within which the UE was sent to RRC_INACTIVE. This version of the specification only supports intra-RAT mobility of UEs in RRC_INACTIVE. - PLMN-specific information: information supporting network sharing deployments, providing an index to the PLMN ID part of the Global NG-RAN node identifier. Table C-1: I-RNTI reference profiles | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | Annex |
5,916 | 8.3.1.1A Enhanced Performance Requirement Type A – Single-layer Spatial Multiplexing with TM9 interference model | The requirements are specified in Table 8.3.1.1A-2, with the addition of the parameters in Table 8.3.1.1A-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify closed loop rank one performance on one of the antenna ports 7 or 8 without a simultaneous transmission on the other antenna port in the serving cell when the PDSCH transmission in the serving cell is interfered by PDSCH of one dominant interfering cell applying transmission mode 9 interference model defined in clause B.5.4. In 8.3.1.1A-1, Cell 1 is the serving cell, and Cell 2 is the interfering cell. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1 and Cell 2, respectively. Table 8.3.1.1A-1: Test Parameters for Testing CDM-multiplexed DM RS (single layer) with TM9 interference model Table 8.3.1.1A-2: Enhanced Performance Requirement Type A, CDM-multiplexed DM RS with TM9 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.3.1.1A |
5,917 | 5.3.4.2 Handling of abnormal conditions in UE triggered Service Request | Under certain conditions, the current UE triggered Service Request procedure can cause unnecessary Downlink Packet Notification messages which increase the load of the MME. This can occur when uplink data sent in step 6 causes a response on the downlink which arrives at the Serving GW before the Modify Bearer Request message, step 8. This data cannot be forwarded from the Serving GW to the eNodeB and hence it triggers a Downlink Data Notification message. If the MME receives a Downlink Data Notification after step 2 and before step 9, the MME shall not send S1 interface paging messages. However, across all the UEs on that MME, the MME shall monitor the rate at which these events occur. If the rate becomes significant (as configured by the operator) and the MME's load exceeds an operator configured value, the MME shall indicate "Delay Downlink Packet Notification Request" with parameter D to the Serving Gateway, where D is the requested delay given as an integer multiple of 50 ms, or zero. The Serving GW then uses this delay in between receiving downlink data and sending the Downlink Data Notification message. NOTE 1: A low rate of reception of Downlink Data Notifications between steps 2 and 9 should be considered a normal circumstance, e.g. due to the chance that a UE Terminating call/session is initiated at roughly the same time as the UE triggered Service Request procedure. NOTE 2: It is recommended that this rate is determined over 60 second periods. The MME shall use the step 8 Modify Access Bearers Request or Modify Bearer Request of the UE initiated Service Request procedure to indicate "Delay Downlink Packet Notification Request" to the Serving GW. To determine the amount of delay requested by a given MME, the Serving GW either uses the last Modify Access Bearers Request or Modify Bearer Request message which is part of a Service Request procedure, or, just uses one of the Service Request procedure's Modify Access Bearers Request or Modify Bearer Request messages received within the preceding 30 seconds. The latter mode of operation shall be taken into account when implementing the MME. The MME is responsible for setting the value of D. The exact algorithm for setting the value is implementation dependent, two examples are given below to serve as a guideline: EXAMPLE 1: The MME adaptively increases the value of D when the rate of unnecessary Downlink Data Notifications is too high; and correspondingly it decreases the value when the rate is not too high. EXAMPLE 2: When unnecessary Downlink Data Notifications arrive, the MME measures the average time from the reception of the unnecessary Downlink Data Notification to the reception of the Modify Access Bearers Request or Modify Bearer Response from the Serving GW in the same UE triggered Service Request Procedure. The value of D is calculated from this average, by adding a safety margin. Normally, upon receipt of a downlink data packet for which there is no DL-TEID of the S1 user plane tunnel, the S-GW shall send the Downlink Data Notification message to the MME without delay. If the S-GW determines from the last Modify Access Bearers Request or Modify Bearer Request message which is part of a Service Request procedure that a given MME request delaying of the Downlink Packet Notification by a delay of D, it shall (only for UEs of that MME) buffer the Downlink Data for a period D. If the DL-TEID and eNodeB address for the UE is received before the expiry of the timer, the timer shall be cancelled and the Network triggered Service Request procedure is finished without sending the Downlink Data Notification message to the MME, i.e. DL data are sent to the UE. Otherwise the Downlink Data Notification message is sent to the MME when the timer expires. NOTE 3: The above procedure and indicated time values are intended to ensure that the procedure is "stable"; avoids RAN impacts; and, that the negative impacts of shortening the DRX interval on UE battery life are avoided. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.4.2 |
5,918 | 11.2.3 Mandatory information in inter-node RRC messages | For the AS-Config transferred within the HandoverPreparationInformation: - The source node shall include all fields necessary to reflect the current AS configuration of the UE, except for the fields sourceSCG-NR-Config, sourceSCG-EUTRA-Config and sourceRB-SN-Config, which can be omitted in case the source MN did not receive the latest configuration from the source SN. For RRCReconfiguration included in the field rrcReconfiguration, ReconfigurationWithSync is included with only the mandatory subfields (e.g. newUE-Identity and t304) and ServingCellConfigCommon; - Need codes or conditions specified for subfields according to IEs defined in clause 6 do not apply. I.e. some fields shall be included regardless of the "Need" or "Cond" e.g. discardTimer; - Based on the received AS configuration, the target node can indicate the delta (difference) to the current AS configuration (as included in HandoverCommand)to the UE. The fields newUE-Identity and t304 included in ReconfigurationWithSync are not used for delta configuration purpose. The candidateCellInfoListSN(-EUTRA) in CG-Config and the candidateCellInfoListMN(-EUTRA)/candidateCellInfoListSN(-EUTRA) in CG-ConfigInfo need not be included in procedures that do not involve a change of node. For fields scg-CellGroupConfig, scg-CellGroupConfigEUTRA and scg-RB-Config in CG-Config (sent upon SN initiated SN change or other conditions as specified in field descriptions) and fields mcg-RB-Config, scg-RB-Config and sourceConfigSCG in CG-ConfigInfo (sent upon change of SN): - The source node shall include all fields necessary to reflect the current AS configuration of the UE, unless stated otherwise in the field description. For RRCReconfiguration included in the field scg-CellGroupConfig in CG-Config, ReconfigurationWithSync is included with only the mandatory subfields (e.g. newUE-Identity and t304) and ServingCellConfigCommon; - Need codes or conditions specified for subfields according to IEs defined in clause 6 do not apply; - Based on the received AS configuration, the target node can indicate the delta (difference) as compared to the current AS configuration to the UE. The fields newUE-Identity and t304 in ReconfigurationWithSync are always included by the target node, i.e. they are not used for delta configuration purpose to UE. For fields in CG-Config and CG-ConfigInfo listed below, absence of the field means that the receiver maintains the values informed via the previous message. Note that every time there is a change in the configuration covered by a listed field, the MN or SN shall include the field and it shall provide the full configuration provided by that field unless stated otherwise. Otherwise, if there is no change, the field can be omitted: - configRestrictInfo; - gapPurpose; - measGapConfig (for which delta signaling applies); - measGapConfigFR2 (for which delta signaling applies); - measResultCellListSFTD; - measResultSFTD-EUTRA; - sftdFrequencyList-EUTRA; - sftdFrequencyList-NR; - ue-CapabilityInfo; - servFrequenciesMN-NR. For other fields in CG-Config and CG-ConfigInfo, the sender shall always signal the appropriate value even if same as indicated in the previous inter-node message, unless explicitly stated otherwise. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 11.2.3 |
5,919 | – PUSCH-Config | The IE PUSCH-Config is used to configure the UE specific PUSCH parameters applicable to a particular BWP. PUSCH-Config information element -- ASN1START -- TAG-PUSCH-CONFIG-START PUSCH-Config ::= SEQUENCE { dataScramblingIdentityPUSCH INTEGER (0..1023) OPTIONAL, -- Need S txConfig ENUMERATED {codebook, nonCodebook} OPTIONAL, -- Need S dmrs-UplinkForPUSCH-MappingTypeA SetupRelease { DMRS-UplinkConfig } OPTIONAL, -- Need M dmrs-UplinkForPUSCH-MappingTypeB SetupRelease { DMRS-UplinkConfig } OPTIONAL, -- Need M pusch-PowerControl PUSCH-PowerControl OPTIONAL, -- Need M frequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, -- Need S frequencyHoppingOffsetLists SEQUENCE (SIZE (1..4)) OF INTEGER (1.. maxNrofPhysicalResourceBlocks-1) OPTIONAL, -- Need M resourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch}, pusch-TimeDomainAllocationList SetupRelease { PUSCH-TimeDomainResourceAllocationList } OPTIONAL, -- Need M pusch-AggregationFactor ENUMERATED { n2, n4, n8 } OPTIONAL, -- Need S mcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S mcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S transformPrecoder ENUMERATED {enabled, disabled} OPTIONAL, -- Need S codebookSubset ENUMERATED {fullyAndPartialAndNonCoherent, partialAndNonCoherent,nonCoherent} OPTIONAL, -- Cond codebookBased maxRank INTEGER (1..4) OPTIONAL, -- Cond codebookBased rbg-Size ENUMERATED { config2} OPTIONAL, -- Need S uci-OnPUSCH SetupRelease { UCI-OnPUSCH} OPTIONAL, -- Need M tp-pi2BPSK ENUMERATED {enabled} OPTIONAL, -- Need S ..., [[ minimumSchedulingOffsetK2-r16 SetupRelease { MinSchedulingOffsetK2-Values-r16 } OPTIONAL, -- Need M ul-AccessConfigListDCI-0-1-r16 SetupRelease { UL-AccessConfigListDCI-0-1-r16 } OPTIONAL, -- Need M -- Start of the parameters for DCI format 0_2 introduced in V16.1.0 harq-ProcessNumberSizeDCI-0-2-r16 INTEGER (0..4) OPTIONAL, -- Need R dmrs-SequenceInitializationDCI-0-2-r16 ENUMERATED {enabled} OPTIONAL, -- Need S numberOfBitsForRV-DCI-0-2-r16 INTEGER (0..2) OPTIONAL, -- Need R antennaPortsFieldPresenceDCI-0-2-r16 ENUMERATED {enabled} OPTIONAL, -- Need S dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2-r16 SetupRelease { DMRS-UplinkConfig } OPTIONAL, -- Need M dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2-r16 SetupRelease { DMRS-UplinkConfig } OPTIONAL, -- Need M frequencyHoppingDCI-0-2-r16 CHOICE { pusch-RepTypeA ENUMERATED {intraSlot, interSlot}, pusch-RepTypeB ENUMERATED {interRepetition, interSlot} } OPTIONAL, -- Need S frequencyHoppingOffsetListsDCI-0-2-r16 SetupRelease { FrequencyHoppingOffsetListsDCI-0-2-r16} OPTIONAL, -- Need M codebookSubsetDCI-0-2-r16 ENUMERATED {fullyAndPartialAndNonCoherent, partialAndNonCoherent,nonCoherent} OPTIONAL, -- Cond codebookBased invalidSymbolPatternIndicatorDCI-0-2-r16 ENUMERATED {enabled} OPTIONAL, -- Need S maxRankDCI-0-2-r16 INTEGER (1..4) OPTIONAL, -- Cond codebookBased mcs-TableDCI-0-2-r16 ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S mcs-TableTransformPrecoderDCI-0-2-r16 ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S priorityIndicatorDCI-0-2-r16 ENUMERATED {enabled} OPTIONAL, -- Need S pusch-RepTypeIndicatorDCI-0-2-r16 ENUMERATED { pusch-RepTypeA, pusch-RepTypeB} OPTIONAL, -- Need R resourceAllocationDCI-0-2-r16 ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch} OPTIONAL, -- Need M resourceAllocationType1GranularityDCI-0-2-r16 ENUMERATED { n2,n4,n8,n16 } OPTIONAL, -- Need S uci-OnPUSCH-ListDCI-0-2-r16 SetupRelease { UCI-OnPUSCH-ListDCI-0-2-r16} OPTIONAL, -- Need M pusch-TimeDomainAllocationListDCI-0-2-r16 SetupRelease { PUSCH-TimeDomainResourceAllocationList-r16 } OPTIONAL, -- Need M -- End of the parameters for DCI format 0_2 introduced in V16.1.0 -- Start of the parameters for DCI format 0_1 introduced in V16.1.0 pusch-TimeDomainAllocationListDCI-0-1-r16 SetupRelease { PUSCH-TimeDomainResourceAllocationList-r16 } OPTIONAL, -- Need M invalidSymbolPatternIndicatorDCI-0-1-r16 ENUMERATED {enabled} OPTIONAL, -- Need S priorityIndicatorDCI-0-1-r16 ENUMERATED {enabled} OPTIONAL, -- Need S pusch-RepTypeIndicatorDCI-0-1-r16 ENUMERATED { pusch-RepTypeA, pusch-RepTypeB} OPTIONAL, -- Need R frequencyHoppingDCI-0-1-r16 ENUMERATED {interRepetition, interSlot} OPTIONAL, -- Cond RepTypeB uci-OnPUSCH-ListDCI-0-1-r16 SetupRelease { UCI-OnPUSCH-ListDCI-0-1-r16 } OPTIONAL, -- Need M -- End of the parameters for DCI format 0_1 introduced in V16.1.0 invalidSymbolPattern-r16 InvalidSymbolPattern-r16 OPTIONAL, -- Need S pusch-PowerControl-v1610 SetupRelease {PUSCH-PowerControl-v1610} OPTIONAL, -- Need M ul-FullPowerTransmission-r16 ENUMERATED {fullpower, fullpowerMode1, fullpowerMode2} OPTIONAL, -- Need R pusch-TimeDomainAllocationListForMultiPUSCH-r16 SetupRelease { PUSCH-TimeDomainResourceAllocationList-r16 } OPTIONAL, -- Need M numberOfInvalidSymbolsForDL-UL-Switching-r16 INTEGER (1..4) OPTIONAL -- Cond RepTypeB2 ]], [[ ul-AccessConfigListDCI-0-2-r17 SetupRelease { UL-AccessConfigListDCI-0-2-r17 } OPTIONAL, -- Need M betaOffsetsCrossPri0-r17 SetupRelease { BetaOffsetsCrossPriSel-r17 } OPTIONAL, -- Need M betaOffsetsCrossPri1-r17 SetupRelease { BetaOffsetsCrossPriSel-r17 } OPTIONAL, -- Need M betaOffsetsCrossPri0DCI-0-2-r17 SetupRelease { BetaOffsetsCrossPriSelDCI-0-2-r17 } OPTIONAL, -- Need M betaOffsetsCrossPri1DCI-0-2-r17 SetupRelease { BetaOffsetsCrossPriSelDCI-0-2-r17 } OPTIONAL, -- Need M mappingPattern-r17 ENUMERATED {cyclicMapping, sequentialMapping} OPTIONAL, -- Cond SRSsets secondTPCFieldDCI-0-1-r17 ENUMERATED {enabled} OPTIONAL, -- Need R secondTPCFieldDCI-0-2-r17 ENUMERATED {enabled} OPTIONAL, -- Need R sequenceOffsetForRV-r17 INTEGER (0..3) OPTIONAL, -- Need R ul-AccessConfigListDCI-0-1-r17 SetupRelease { UL-AccessConfigListDCI-0-1-r17 } OPTIONAL, -- Need M minimumSchedulingOffsetK2-r17 SetupRelease { MinSchedulingOffsetK2-Values-r17 } OPTIONAL, -- Need M availableSlotCounting-r17 ENUMERATED { enabled } OPTIONAL, -- Need S dmrs-BundlingPUSCH-Config-r17 SetupRelease { DMRS-BundlingPUSCH-Config-r17 } OPTIONAL, -- Need M harq-ProcessNumberSizeDCI-0-2-v1700 INTEGER (5) OPTIONAL, -- Need R harq-ProcessNumberSizeDCI-0-1-r17 INTEGER (5) OPTIONAL, -- Need R mpe-ResourcePoolToAddModList-r17 SEQUENCE (SIZE(1..maxMPE-Resources-r17)) OF MPE-Resource-r17 OPTIONAL, -- Need N mpe-ResourcePoolToReleaseList-r17 SEQUENCE (SIZE(1..maxMPE-Resources-r17)) OF MPE-ResourceId-r17 OPTIONAL -- Need N ]], [[ maxRank-n8-r18 INTEGER (5..8) OPTIONAL, -- Cond codebookBased sTx-2Panel-r18 ENUMERATED {enabled} OPTIONAL, -- Need R multipanelScheme-r18 CHOICE { sdm-r18 SetupRelease { SDM-Scheme-r18 }, sfn-r18 SetupRelease { SFN-Scheme-r18 } } OPTIONAL, -- Cond SRSsets codebookTypeUL-r18 SetupRelease { CodebookTypeUL-r18 } OPTIONAL, -- Need M applyIndicatedTCI-State-r18 ENUMERATED {first, second} OPTIONAL, -- Need R dynamicTransformPrecoderFieldPresenceDCI-0-1-r18 ENUMERATED {enabled} OPTIONAL, -- Need R dynamicTransformPrecoderFieldPresenceDCI-0-2-r18 ENUMERATED {enabled} OPTIONAL, -- Need R pusch-ConfigDCI-0-3-r18 SetupRelease { PUSCH-ConfigDCI-0-3-r18 } OPTIONAL -- Need M ]] } UCI-OnPUSCH ::= SEQUENCE { betaOffsets CHOICE { dynamic SEQUENCE (SIZE (4)) OF BetaOffsets, semiStatic BetaOffsets } OPTIONAL, -- Need M scaling ENUMERATED { f0p5, f0p65, f0p8, f1 } } MinSchedulingOffsetK2-Values-r16 ::= SEQUENCE (SIZE (1..maxNrOfMinSchedulingOffsetValues-r16)) OF INTEGER (0..maxK2-SchedulingOffset-r16) MinSchedulingOffsetK2-Values-r17 ::= SEQUENCE (SIZE (1..maxNrOfMinSchedulingOffsetValues-r16)) OF INTEGER (0..maxK2-SchedulingOffset-r17) UCI-OnPUSCH-DCI-0-2-r16 ::= SEQUENCE { betaOffsetsDCI-0-2-r16 CHOICE { dynamicDCI-0-2-r16 CHOICE { oneBit-r16 SEQUENCE (SIZE (2)) OF BetaOffsets, twoBits-r16 SEQUENCE (SIZE (4)) OF BetaOffsets }, semiStaticDCI-0-2-r16 BetaOffsets } OPTIONAL, -- Need M scalingDCI-0-2-r16 ENUMERATED { f0p5, f0p65, f0p8, f1 } } FrequencyHoppingOffsetListsDCI-0-2-r16 ::= SEQUENCE (SIZE (1..4)) OF INTEGER (1.. maxNrofPhysicalResourceBlocks-1) UCI-OnPUSCH-ListDCI-0-2-r16 ::= SEQUENCE (SIZE (1..2)) OF UCI-OnPUSCH-DCI-0-2-r16 UCI-OnPUSCH-ListDCI-0-1-r16 ::= SEQUENCE (SIZE (1..2)) OF UCI-OnPUSCH UL-AccessConfigListDCI-0-1-r16 ::= SEQUENCE (SIZE (1..64)) OF INTEGER (0..63) UL-AccessConfigListDCI-0-1-r17 ::= SEQUENCE (SIZE (1..3)) OF INTEGER (0..2) UL-AccessConfigListDCI-0-2-r17 ::= SEQUENCE (SIZE (1..64)) OF INTEGER (0..63) BetaOffsetsCrossPriSel-r17 ::= CHOICE { dynamic-r17 SEQUENCE (SIZE (4)) OF BetaOffsetsCrossPri-r17, semiStatic-r17 BetaOffsetsCrossPri-r17 } BetaOffsetsCrossPriSelDCI-0-2-r17 ::= CHOICE { dynamicDCI-0-2-r17 CHOICE { oneBit-r17 SEQUENCE (SIZE (2)) OF BetaOffsetsCrossPri-r17, twoBits-r17 SEQUENCE (SIZE (4)) OF BetaOffsetsCrossPri-r17 }, semiStaticDCI-0-2-r17 BetaOffsetsCrossPri-r17 } MPE-Resource-r17 ::= SEQUENCE { mpe-ResourceId-r17 MPE-ResourceId-r17, cell-r17 ServCellIndex OPTIONAL, -- Need R additionalPCI-r17 AdditionalPCIIndex-r17 OPTIONAL, -- Need R mpe-ReferenceSignal-r17 CHOICE { csi-RS-Resource-r17 NZP-CSI-RS-ResourceId, ssb-Resource-r17 SSB-Index } } MPE-ResourceId-r17 ::= INTEGER (1..maxMPE-Resources-r17) SDM-Scheme-r18 ::= SEQUENCE { maxRankSDM-r18 INTEGER (1..2) OPTIONAL, -- Need R maxRankSDM-DCI-0-2-r18 INTEGER (1..2) OPTIONAL -- Need R } SFN-Scheme-r18 ::= SEQUENCE { maxRankSFN-r18 INTEGER (1..2) OPTIONAL, -- Need R maxRankSFN-DCI-0-2-r18 INTEGER (1..2) OPTIONAL -- Need R } CodebookTypeUL-r18 ::= CHOICE { codebook1-r18 ENUMERATED {ng1n4n1, ng1n2n2}, codebook2-r18 ENUMERATED {ng2}, codebook3-r18 ENUMERATED {ng4}, codebook4-r18 ENUMERATED {ng8} } PUSCH-ConfigDCI-0-3-r18 ::= SEQUENCE { resourceAllocationDCI-0-3-r18 ENUMERATED {resourceAllocationType0, resourceAllocationType1, dynamicSwitch} OPTIONAL, -- Need M rbg-SizeDCI-0-3-r18 ENUMERATED {config2, config3} OPTIONAL, -- Need S resourceAllocationType1GranularityDCI-0-3-r18 ENUMERATED {n2,n4,n8,n16} OPTIONAL, -- Need S numberOfBitsForRV-DCI-0-3-r18 INTEGER (0..2) OPTIONAL, -- Need R harq-ProcessNumberSizeDCI-0-3-r18 INTEGER (0..5) OPTIONAL, -- Need R uci-OnPUSCH-ListDCI-0-3-r18 SetupRelease { UCI-OnPUSCH-ListDCI-0-1-r16 } OPTIONAL -- Need M } -- TAG-PUSCH-CONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,920 | 4.3.2.4 Change or determination of IMS registration status | Whenever the UE's availability for voice calls in the IMS is determined or changes (e.g. whenever the IMS registration status is determined or changes), the UE dependent on its mode of operation shall execute procedures according to table 4.3.2.4.1, 4.3.2.4.2 or 4.3.2.4.3: a) The UE is operating in PS mode 1 Table 4.3.2.4.1: Change of IMS registration status for a UE in PS mode 1 NOTE 1: If the UE in PS mode 1 transits to CS/PS mode 1 according to table 4.3.2.4.1, then the UE can return to PS mode 1 when the upper layer indicates the status of being available for voice over PS. b) The UE is operating in PS mode 2 Table 4.3.2.4.2: Change of IMS registration status for a UE in PS mode 2 NOTE 2: If the UE in PS mode 2 transits to CS/PS mode 2 according to table 4.3.2.4.2, then the UE can return to PS mode 2 when the upper layer indicates the status of being available for voice over PS. c) The UE is operating in CS/PS mode 1 Table 4.3.2.4.3: Change of IMS registration status for a UE in CS/PS mode 1 | 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 | 4.3.2.4 |
5,921 | F.2.2 Local/Edge CHF deployment | There is an option of distributing CCS functions in a distributed way by making available, a CHF instance and the Edge Enablement Server (EES) is located in the same Service Deployment Cluster. On this case the CHF instance selected may be the one physically closer to the EES. Therefore, the charging events would be generated through the CTF towards the CHF that is available at the Edge. This is depicted in in TS 32.257[ Telecommunication management; Charging management; Edge computing domain charging ] [57] clause 4.2.3. Furthermore, there are other distributed models that can be used, for instance, the availability of NF(CTF), instead of using an EES, in the Service Deployment Cluster. Figure F.2.2-1: Converged charging architecture with CTF, CHF (ABMF / RF) | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | F.2.2 |
5,922 | 9.8.4.1 FDD and half-duplex FDD | The following requirements apply to UE supporting ce-ModeA-r13 and ce-CQI-AlternativeTable-r15. For the parameters specified in Table 9.8.4.1-1, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2, the reported CQI value according to RC.32 FDD in Table A.4-1 shall be in the range of ±1 of the reported median more than 90% of the time. If the PDSCH BLER using the transport format indicated by median CQI is less than or equal to 0.1, the BLER using the transport format indicated by the (median CQI + 1) shall be greater than 0.1. If the PDSCH BLER using the transport format indicated by the median CQI is greater than 0.1, the BLER using transport format indicated by (median CQI – 1) shall be less than or equal to 0.1. Table 9.8.4.1-1: PUCCH 1-0 static test (FDD and half-duplex FDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.8.4.1 |
5,923 | 8.2.3.2.1 Minimum Requirement for FDD PCell | For TDD FDD CA with FDD PCell and 2DL CCs, the requirements are specified in Table 8.2.3.2.1-4 based on single carrier requirement specified in Table 8.2.3.2.1-2 and Table 8.2.3.2.1-3, with the addition of the parameters in Table 8.2.3.2.1-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of large delay CDD with 2 transmitter antennas. For TDD FDD CA with FDD PCell and 3DL CCs, the requirements are specified in Table 8.2.3.2.1-5 based on single carrier requirement specified in Table 8.2.3.2.1-2 and Table 8.2.3.2.1-3, with the addition of the parameters in Table 8.2.3.2.1-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of large delay CDD with 2 transmitter antennas. For TDD FDD CA with FDD PCell and 4DL CCs, the requirements are specified in Table 8.2.3.2.1-6 based on single carrier requirement specified in Table 8.2.3.2.1-2 and Table 8.2.3.2.1-3, with the addition of the parameters in Table 8.2.3.2.1-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of large delay CDD with 2 transmitter antennas. For TDD FDD CA with FDD PCell and 5DL CCs, the requirements are specified in Table 8.2.3.2.1-7 based on single carrier requirement specified in Table 8.2.3.2.1-2 and Table 8.2.3.2.1-3, with the addition of the parameters in Table 8.2.3.2.1-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of large delay CDD with 2 transmitter antennas. For TDD FDD CA with FDD PCell and 6DL CCs, the requirements are specified in Table 8.2.3.2.1-8 based on single carrier requirement specified in Table 8.2.3.2.1-2 and Table 8.2.3.2.1-3, with the addition of the parameters in Table 8.2.3.2.1-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of large delay CDD with 2 transmitter antennas. For TDD FDD CA with FDD PCell and 7DL CCs, the requirements are specified in Table 8.2.3.2.1-9 based on single carrier requirement specified in Table 8.2.3.2.1-2 and Table 8.2.3.2.1-3, with the addition of the parameters in Table 8.2.3.2.1-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of large delay CDD with 2 transmitter antennas. The test coverage for different number of component carriers is defined in 8.1.2.4. Table 8.2.3.2.1-1: Test Parameters for Large Delay CDD (FRC) for CA Table 8.2.3.2.1-2: Single carrier performance with different bandwidths for multiple CA configurations for FDD PCell and SCell (FRC) Table 8.2.3.2.1-3: Single carrier performance with different bandwidths for multiple CA configurations for TDD SCell (FRC) Table 8.2.3.2.1-4: Minimum performance for multiple CA configurations with 2DL CCs (FRC) Table 8.2.3.2.1-5: Minimum performance for multiple CA configurations with 3DL CCs (FRC) Table 8.2.3.2.1-6: Minimum performance for multiple CA configurations with 4DL CCs (FRC) Table 8.2.3.2.1-7: Minimum performance for multiple CA configurations with 5DL CCs (FRC) Table 8.2.3.2.1-8: Minimum performance for multiple CA configurations with 6DL CCs (FRC) Table 8.2.3.2.1-9: Minimum performance for multiple CA configurations with 7DL CCs (FRC) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.3.2.1 |
5,924 | 10.2.6 Narrowband reference signal (NRS) | Before a UE obtains operationModeInfo: - If frame structure type 1 is used, the UE may assume narrowband reference signals (NRSs) are transmitted in subframes #0 and #4 and in subframes #9 not containing NSSS. - If frame structure type 2 is used, the UE may assume narrowband reference signals (NRSs) are transmitted in subframes #9 and in subframes #0 not containing NSSS. On an NB-IoT carrier for which a UE receives higher-layer parameter operationModeInfo indicating guardband or standalone. - If frame structure type 1 is used, before the UE obtains SystemInformationBlockType1-NB, the UE may assume narrowband reference signals are transmitted in subframes #0, #1, #3, #4 and in subframes #9 not containing NSSS. - If frame structure type 2 is used, before the UE obtains SystemInformationBlockType1-NB, the UE may assume narrowband reference signals are transmitted in subframes #9, and in subframes #0 not containing NSSS, and in subframes #4 if subframes #4 is configured for SystemInformationBlockType1-NB transmissions. - If frame structure type 1 is used, after the UE obtains SystemInformationBlockType1-NB, the UE may assume narrowband reference signals are transmitted in subframes #0, #1, #3, #4, subframes #9 not containing NSSS, and in NB-IoT downlink subframes. - If frame structure type 2 is used, after the UE obtains SystemInformationBlockType1-NB, the UE may assume narrowband reference signals are transmitted in subframes #9, subframes #0 not containing NSSS, in subframes #4 if subframes #4 is configured for SystemInformationBlockType1-NB transmissions, and in NB-IoT downlink subframes. On an NB-IoT carrier for SystemInformationBlockType1-NB for which sib1-carrierInfo-NB indicates non-anchor for frame structure type 2, before the UE obtains SystemInformationBlockType1-NB, the UE may assume narrowband reference signals are transmitted in subframes #0 and #5. After the UE obtains SystemInformationBlockType1-NB, the UE may assume narrowband reference signals are transmitted in subframes #0, #5, and in NB-IoT downlink subframes indicated by tdd-SI-SubframesBitmap. On an NB-IoT carrier for which DL-CarrierConfigCommon-NB is present and no inbandCarrierInfo is present. - If frame structure type 1 is used and when an NB-IoT UE is configured by higher layers to decode NPDCCH with CRC scrambled by the P-RNTI and higher-layer indicates nrs-NonAnchorConfig is enabled, the UE first determines the starting subframe of NPDCCH search space associated with NRS transmission according to [10]. - If higher-layer nB is configured as fourT, the UE may assume NRSs are transmitted in the 10th NB-IoT DL subframe before the determined starting subframe of NPDCCH search space. - If higher-layer nB is configured as twoT, the UE may assume NRSs are transmitted in the 9th and 10th NB-IoT DL subframes before the determined starting subframe of NPDCCH search space. - If higher-layer nB is configured as oneT, the UE may assume NRSs are transmitted in the 6th, 7th, 8th, 9th and 10th NB-IoT DL subframes before the determined starting subframe of NPDCCH search space. - For other nB values, the UE may assume NRSs are transmitted in 10 NB-IoT DL subframes before the determined starting subframe of NPDCCH search space. - When an NB-IoT UE is configured by higher layers to decode NPDCCH with CRC scrambled by the P-RNTI, the UE may assume NRSs are transmitted in the NPDCCH candidate where the UE finds a DCI with CRC scrambled by the P-RNTI. The UE may also assume NRSs are transmitted in 10 NB-IoT DL subframes before and in 4 NB-IoT DL subframes after the NPDCCH candidate where the UE finds a DCI with CRC scrambled by the P-RNTI, where NB-IoT DL subframes without NRS are not counted. If the DCI with CRC scrambled by the P-RNTI schedules a NPDSCH, the UE may assume NRSs are transmitted in the NB-IoT DL subframes carrying the NPDSCH as well as in 4 NB-IoT DL subframes before and after the scheduled NPDSCH, where NB-IoT DL subframes without NRS are not counted. - During the window controlled by higher layers where the UE shall attempt to decode the NPDCCH with DCI scrambled by RA-RNTI (see [8], clause 5.1.4), the UE may assume NRSs are transmitted in the Type-2 CSS configured by higher layers, as well as in 10 NB-IoT DL subframes before and in 4 NB-IoT DL subframes after each Type-2 CSS, where NB-IoT DL subframes without NRS are not counted. If a DCI scrambled by the RA-RNTI is detected, the UE may assume NRSs are transmitted in the NPDSCH scheduled by the DCI scrambled by the RA-RNTI, as well as in 4 NB-IoT DL subframes before and after the scheduled NPDSCH, where NB-IoT DL subframes without NRS are not counted. In addition, when the UE attempts to decode a DCI with CRC scrambled by the RA-RNTI as well as receiving the NPDSCH scheduled by the DCI scrambled by the RA-RNTI, the UE may assume NRSs are transmitted in subframes #0, #1, #3, #4 and #9. - During random access procedure, when an NB-IoT UE is configured by higher layers to decode NPDCCH with CRC scrambled by the temporary C-RNTI and/or the C-RNTI, before the DCI scrambled by temporary C-RNTI and/or C-RNTI is detected, the UE may assume NRSs are transmitted in the Type-2 CSS configured by higher layers, as well as in 10 NB-IoT DL subframes before the start of each Type-2 CSS and in 4 NB-IoT DL subframes after the end of each Type-2 CSS until the mac-ContentionResolutionTimer expires, where NB-IoT DL subframes without NRS are not counted. If a DCI scrambled by the temporary C-RNTI or C-RNTI is detected, the UE may assume NRSs are transmitted in the NPDSCH scheduled by the DCI scrambled by the temporary C-RNTI or C-RNTI as well as in 4 NB-IoT DL subframes before and after the scheduled NPDSCH, where NB-IoT DL subframes without NRS are not counted. - An NB-IoT UE may assume NRSs are transmitted in NB-IoT DL subframes that are used for Type1A-NPDCCH common search space, and Type2A-NPDCCH common search space, as well as in 10 NB-IoT DL subframes prior and in 4 NB-IoT DL subframes after each Type1A-NPDCCH common search space and Type2A-NPDCCH common search space. A UE may assume NRSs are transmitted in NB-IoT DL subframes carrying NPDSCH scheduled by DCI CRC scrambled by G-RNTI or SC-RNTI as well as 4 NB-IoT DL subframes prior and after the scheduled NPDSCH, where NB-IoT DL subframes without NRS are not counted. - In other cases, if frame structure typ1 is used, the UE may assume NRSs are transmitted in subframes #0, #1, #3, #4, #9, and in NB-IoT downlink subframes and shall not expect NRSs in other downlink subframes. On an NB-IoT carrier for which a UE receives higher-layer parameter operationModeInfo indicating inband-SamePCI or inband-DifferentPCI. - If frame structure type 1 is used, before the UE obtains SystemInformationBlockType1-NB, the UE may assume narrowband reference signals are transmitted in subframes #0, #4 and in subframes #9 not containing NSSS, and in subframes #3 which contain SystemInformationBlockType1-NB when additionalTransmissionSIB1 is configured as TRUE. - If frame structure type 2 is used, before the UE obtains SystemInformationBlockType1-NB, the UE may assume narrowband reference signals are transmitted in subframes #9, and in subframes #0 not containing NSSS, and in subframes #4 if subframes #4 is configured for SystemInformationBlockType1-NB transmissions. - If frame structure type 1 is used, after the UE obtains SystemInformationBlockType1-NB, the UE may assume narrowband reference signals are transmitted in subframes #0, #4, subframes #9 not containing NSSS, subframes #3 which contain SystemInformationBlockType1-NB when additionalTransmissionSIB1 is configured as TRUE, and in NB-IoT downlink subframes. - If frame structure type 2 is used, after the UE obtains SystemInformationBlockType1-NB, the UE may assume narrowband reference signals are transmitted in subframes #9, subframes #0 not containing NSSS, in subframes #4 if subframes #4 is configured for SystemInformationBlockType1-NB transmissions, and in NB-IoT downlink subframes On an NB-IoT carrier for which DL-CarrierConfigCommon-NB is present and inbandCarrierInfo is present: - If frame structure type 1 is used, when an NB-IoT UE is configured by higher layers to decode NPDCCH with CRC scrambled by the P-RNTI and higher-layer indicates nrs-NonAnchorConfig is enabled, the UE first determines the starting subframe of NPDCCH search space associated with NRS transmission according to [10]. - If higher-layer nB is configured as fourT, the UE may assume NRSs are transmitted in the 10th NB-IoT DL subframe before the determined starting subframe of NPDCCH search space. - If higher-layer nB is configured as twoT, the UE may assume NRSs are transmitted in 9th and 10th NB-IoT DL subframes before the determined starting subframe of NPDCCH search space. - If higher-layer nB is configured as oneT, the UE may assume NRSs are transmitted in 6th, 7th, 8th, 9th and 10th NB-IoT DL subframes before the determined starting subframe of NPDCCH search space. - For other nB values, the UE may assume NRSs are transmitted in 10 NB-IoT DL subframes before the determined starting subframe of NPDCCH search space. - When an NB-IoT UE is configured by higher layers to decode NPDCCH with CRC scrambled by the P-RNTI, the UE may assume NRSs are transmitted in the NPDCCH candidate where the UE finds a DCI with CRC scrambled by the P-RNTI. The UE may also assume NRSs are transmitted in10 NB-IoT DL subframes before and in 4 NB-IoT DL subframes after the NPDCCH candidate, where NB-IoT DL subframes without NRS are not counted. If the DCI with CRC scrambled by the P-RNTI schedules a NPDSCH, the UE may assume NRSs are transmitted in the NB-IoT DL subframes carrying the NPDSCH as well as 4 NB-IoT DL subframes before and after the scheduled NPDSCH, where NB-IoT DL subframes without NRS are not counted. - During the window controlled by higher layers where the UE shall attempt to decode the NPDCCH with DCI scrambled by RA-RNTI (see [8], clause 5.1.4), the UE may assume NRSs are transmitted in the Type-2 CSS configured by higher layers, as well as in 10 NB-IoT DL subframes before and in 4 NB-IoT DL subframes after each Type-2 CSS, where NB-IoT DL subframes without NRS are not counted. If a DCI scrambled by the RA-RNTI is detected, the UE may assume NRSs are transmitted in the NPDSCH scheduled by the DCI scrambled by the RA-RNTI, as well as in 4 NB-IoT DL subframes before and after the scheduled NPDSCH, where NB-IoT DL subframes without NRS are not counted. In addition, when the UE attempts to decode a DCI with CRC scrambled by the RA-RNTI as well as receiving the NPDSCH scheduled by the DCI scrambled by the RA-RNTI, the UE may assume NRSs are transmitted in subframes #0, #4 and #9. - During random access procedure, when an NB-IoT UE is configured by higher layers to decode NPDCCH with CRC scrambled by the temporary C-RNTI and/or the C-RNTI, before the DCI scrambled by temporary C-RNTI and/or C-RNTI, is detected, the UE may assume NRSs are transmitted in the Type-2 CSS configured by higher layers, as well as in 10 NB-IoT DL subframes before the start of each Type-2 CSS and in 4 NB-IoT DL subframes after the end of each Type-2 CSS until the mac-ContentionResolutionTimer expires, where NB-IoT DL subframes without NRS are not counted. If a DCI scrambled by the temporary C-RNTI or C-RNTI is detected, the UE may assume NRSs are transmitted in the NPDSCH scheduled by the DCI scrambled by the temporary C-RNTI or C-RNTI as well as in 4 NB-IoT DL subframes before and after the scheduled NPDSCH, where NB-IoT DL subframes without NRS are not counted. - An NB-IoT UE may assume NRSs are transmitted in NB-IoT DL subframes that are used for Type1A-NPDCCH common search space, and Type2A-NPDCCH common search space, as well as in 10 NB-IoT DL subframes prior and in 4 NB-IoT DL subframes after each Type1A-NPDCCH common search space and Type2A-NPDCCH common search space, where NB-IoT DL subframes without NRS are not counted. A UE may assume NRSs are transmitted in NB-IoT DL subframes carrying NPDSCH scheduled by DCI CRC scrambled by G-RNTI or SC-RNTI as well as in 4 NB-IoT DL subframes prior and after the scheduled NPDSCH, where NB-IoT DL subframes without NRS are not counted. - In other cases, if frame structure type 1 is used, the UE may assume NRSs are transmitted in subframes #0, #4, #9, and in NB-IoT downlink subframes and shall not expect NRSs in other downlink subframes. On an NB-IoT carrier for which DL-CarrierConfigDedicated-NB is present and no inbandCarrierInfo is present: - If frame structure type 1 is used, the UE may assume NRSs are transmitted in subframes #0, #1, #3, #4, #9, and in NB-IoT downlink subframes and shall not expect NRSs in other downlink subframes. On an NB-IoT carrier for which DL-CarrierConfigDedicated-NB is present and inbandCarrierInfo is present: - If frame structure type 1 is used, the UE may assume NRSs are transmitted in subframes #0, #4, #9, and in NB-IoT downlink subframes and shall not expect NRSs in other downlink subframes. An NB-IoT UE may assume NRSs are not transmitted in subframes that are configured by higher layer parameter nprsBitmap for narrowband positioning reference signal transmission. | 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 | 10.2.6 |
5,925 | 5.15.1.1 Resource allocation | In order to transmit MAC PDU(s) on SL-DCH, the MAC entity shall for every discovery period and each MAC PDU: - if the MAC entity is configured by upper layers with a specific grant as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]: - using the specific grant determine the set of subframes in which a transmission of new MAC PDU(s) occur according to clause 14.3.1 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]; - consider the determined set of subframes to be a configured grant for the corresponding discovery period; - for every subframe, if the MAC entity has a configured grant occurring in that subframe, deliver the configured grant and the MAC PDU to the Sidelink HARQ Entity; - clear the configured grant at the end of the corresponding discovery period. NOTE: Mapping between grant and physical resources is specified in clause 9.5.6 of TS 36.211[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation ] [7]. - else if the MAC entity is configured with a single pool of resources by upper layers: - select a random value p1 in the range from 0 to 1, where the random function shall be such that each of the allowed selections can be chosen with equal probability; - if p1 is less than txProbability: - select a random resource from the pool of resources (excluding any resources which are overlapping with PRACH or resources belonging to the subframes of resources already selected for transmissions on SL-DCH in this discovery period), where the random function shall be such that each of the allowed selections (see clause 14.3.1 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]) can be chosen with equal probability; - using the selected resource determine the set of subframes in which the transmission of a MAC PDU can occur according to clause 14.3.1 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2] - consider the determined set of subframes to be a configured grant for the corresponding discovery period; - for every subframe, if the MAC entity has a configured grant occurring in that subframe, deliver the configured grant and the MAC PDU to the Sidelink HARQ Entity; - clear the configured grant at the end of the corresponding discovery period. | 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.15.1.1 |
5,926 | 6.46.8.1 Description | NGSO (MEO/LEO) based satellite access is raising higher demands on the amount of ground stations, and the availability and stability of the connectivity to ground station for UEs to obtain end-to-end network services anytime. S&F (Store and Forward) Satellite operation in some level provides a way to enable autonomously network service to UEs without the satellite always being connected to the ground station, which can extend the service availability for the areas without the connectivity to ground station via feeder link or ISL (e.g. at sea, very remote areas lack of ground-station infrastructures), improve the ground segment affordability with fewer ground stations and allow more robust UE services with the satellite under intermittently/temporarily unavailable feeder link. This is particularly relevant for delay-tolerant communications via NGSO space segment. The requirements below refer to S&F (Store and Forward) Satellite operation. NOTE: For more information on Store and Forward Satellite operation see Annex J. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.46.8.1 |
5,927 | 8.22.4 Intra-DU indirect path addition on top of direct path | The signaling flow for intra-DU indirect path addition is shown in Fig. 8.22.4-1. Figure 8.22.4-1: Signalling procedure of intra-DU indirect path addition on top of direct path 1. If the MP Remote UE is connected with the MP Relay UE using PC5 link, the Uu measurement configuration and measurement report signalling are performed between MP Remote UE and gNB-CU to evaluate relay link measurement and Uu link measurement. The MP Remote UE may report Uu measurement results of neighboring cells and one or multiple candidate MP Relay UE(s). In case that the MP Remote UE is connected with the MP Relay UE using N3C and the MP Relay UE is in RRC_CONNECTED state, the MP Remote UE reports at least the list of the C-RNTI and the cell ID of one or multiple candidate MP Relay UE(s). 2. The gNB-CU decides to add the indirect path via MP Relay UE to MP Remote UE under the same gNB-DU. 3. The reconfiguration to MP Relay UE is performed among MP Relay UE, gNB-DU and gNB-CU if MP Relay UE is in RRC_CONNECTED state. The gNB-CU sends an RRCReconfiguration message to the MP Relay UE. If the MP Relay UE is in RRC_IDLE/INACTIVE state, this step is skipped. 4. The gNB-CU sends the UE CONTEXT MODIFICATION REQUEST message for the MP Remote UE to the gNB-DU, which contains the indirect path addition configuration at least. 5. The gNB-DU responds to the gNB-CU with a UE CONTEXT MODIFICATION RESPONSE message. 6. The gNB-CU sends the DL RRC MESSAGE TRANSFER message for MP Remote UE by including the RRCReconfiguration message to gNB-DU. If the MP Remote UE is connected with the MP Relay UE using the PC5 link, the contents in the RRCReconfiguration message may include at least indirect path addition configuration, PC5 Relay RLC channel configuration for relay traffic, bearer mapping and the associated radio bearer(s). If the MP Remote UE is using N3C, the contents in the RRCReconfiguration message may include at least indirect path addition configuration, bearer mapping and the associated radio bearer(s). 7. The gNB-DU sends the RRCReconfiguration message to the MP Remote UE. 8. If the MP Remote UE is using the PC5 link, the MP Remote UE establishes PC5 connection with the target MP Relay UE. If the MP Remote UE is using N3C, this step is skipped. 9. The MP Remote UE sends the RRCReconfigurationComplete message to the gNB-DU via direct path to complete the indirect path addition procedure. 9a. In case the SRB1 with duplication is configured, the RRCReconfigurationComplete message is also sent to the gNB-DU via indirect path. NOTE: In the case that the target MP Relay UE for indirect path addition is in RRC_IDLE/INACTIVE state, how the MP Remote UE triggers the MP Relay UE to be in RRC_CONNECTED state is specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [2]. 10/10a. The gNB-DU sends the UL RRC MESSAGE TRANSFER message to gNB-CU by including the RRCReconfigurationComplete message. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.22.4 |
5,928 | 5.7a Discontinuous Reception (DRX) for SC-PTM | Each G-RNTI and, for NB-IoT UEs, BL UEs or UEs in enhanced coverage, each SC-RNTI of the MAC entity may be configured by RRC with a DRX functionality that controls the UE's PDCCH monitoring activity for this G-RNTI and SC-RNTI as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]. When in RRC_IDLE or RRC_CONNECTED, if DRX is configured, the MAC entity is allowed to monitor the PDCCH for this G-RNTI or SC-RNTI discontinuously using the DRX operation specified in this clause; otherwise the MAC entity monitors the PDCCH for this G-RNTI or SC-RNTI continuously. For each G-RNTI or SC-RNTI of the MAC entity, RRC controls its DRX operation by configuring the timers onDurationTimerSCPTM, drx-InactivityTimerSCPTM, the SCPTM-SchedulingCycle and the value of the SCPTM-SchedulingOffset for G-RNTI and for SC-RNTI. The DRX operation specified in this clause is performed independently for each G-RNTI and SC-RNTI and independently from the DRX operation specified in subcaluse 5.7. When DRX is configured for a G-RNTI or for SC-RNTI, the Active Time includes the time while: - onDurationTimerSCPTM or drx-InactivityTimerSCPTM is running. When DRX is configured for a G-RNTI or for SC-RNTI as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8], the MAC entity shall for each subframe for this G-RNTI or SC-RNTI: - if [(H-SFN * 10240 + SFN * 10) + subframe number] modulo (SCPTM-SchedulingCycle) = SCPTM-SchedulingOffset: - start onDurationTimerSCPTM. - during the Active Time, for a PDCCH-subframe: - monitor the PDCCH; - if the PDCCH indicates a DL transmission: - if the UE is a BL UE or a UE in enhanced coverage: - start or re-start the drx-InactivityTimerSCPTM in the subframe containing the last repetition of the corresponding PDSCH reception. - if the UE is an NB-IoT UE: - stop onDurationTimerSCPTM; - stop drx-InactivityTimerSCPTM; - start the drx-InactivityTimerSCPTM in the first subframe of the next PDCCH occasion following the subframe containing the last repetition of the corresponding PDSCH reception. - else: - start or restart drx-InactivityTimerSCPTM. NOTE: If H-SFN is not configured its value is set to 0 in the calculation of the starting subframe. | 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.7a |
5,929 | 5.5.4.19 Event Y1 (PCell becomes worse than threshold1 and candidate L2 U2N Relay UE becomes better than threshold2) | The UE shall: 1> consider the entering condition for this event to be satisfied when both condition Y1-1 and condition Y1-2, as specified below, are fulfilled; 1> consider the leaving condition for this event to be satisfied when condition Y1-3 or condition Y1-4, i.e. at least one of the two, as specified below, is fulfilled; Inequality Y1-1 (Entering condition 1) Mp + Hys < Thresh1 Inequality Y1-2 (Entering condition 2) Mr– Hys > Thresh2 Inequality Y1-3 (Leaving condition 1) Mp – Hys > Thresh1 Inequality Y1-4 (Leaving condition 2) Mr + Hys < Thresh2 The variables in the formula are defined as follows: Mp is the measurement result of the PCell, not taking into account any offsets. Mr is the measurement result of the candidate L2 U2N Relay UE, not taking into account any offsets. Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigInterRAT for this event). Thresh1 is the threshold parameter for this event (i.e. y1-Threshold1 as defined within reportConfigInterRAT for this event). Thresh2 is the threshold parameter for this event (i.e. y1-Threshold2-Relay as defined within reportConfigInterRAT for this event). Mp is expressed in dBm in case of RSRP, or in dB in case of RSRQ and SINR. Mr is expressed in dBm or dB, depending on the measurement quantity of candidate L2 U2N Relay UE. Hys are expressed in dB. Thresh1 is expressed in the same unit as Mp. Thresh2 is expressed in the same unit as Mr. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.4.19 |
5,930 | 4.3.1.5.3 Attempted outgoing handovers non-DRX | This measurement provides the number of attempted outgoing handovers, when DRX is not used (for DRX see [12]). CC. Transmission of the RRCConnectionReconfiguration message to UE triggering the handover, indicating the attempt of an outgoing handover when DRX is not used (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]). A single integer value. HO.NoDrxOutAtt. 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.5.3 |
5,931 | 5.3.20 Specific requirements for UE when receiving non-integrity protected reject messages 5.3.20.1 General | This subclause specifies the requirements for a UE that is not configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [17] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]) and receives a REGISTRATION REJECT or SERVICE REJECT message without integrity protection with specific 5GMM causes. NOTE: Additional UE requirements for this case, requirements for other 5GMM causes, and requirements for the case when the UE receives an integrity protected reject message are specified in subclauses 5.5.1 and 5.6.1. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.20 |
5,932 | 4.2.8 Support of non-3GPP access 4.2.8.1A General Concepts to support Wireline Access | Wireline 5G Access Network (W-5GAN) shall be connected to the 5G Core Network via a Wireline Access Gateway Function (W-AGF). The W-AGF interfaces the 5G Core Network CP and UP functions via N2 and N3 interfaces, respectively. For the scenario of 5G-RG connected via NG RAN the specification for UE defined in this TS, TS 23.502[ Procedures for the 5G System (5GS) ] [3] and TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45] are applicable as defined for UE connected to 5GC via NG RAN unless differently specified in this TS and in TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [84]. When a 5G-RG is connected via a NG-RAN and via a W-5GAN, multiple N1 instances shall exist for the 5G-RG i.e. there shall be one N1 instance over NG-RAN and one N1 instance over W-5GAN. A 5G-RG simultaneously connected to the same 5G Core Network of a PLMN over a 3GPP access and a W-5GAN access shall be served by a single AMF in this 5G Core Network. 5G-RG shall maintain the NAS signalling connection with the AMF over the W-5GAN after all the PDU Sessions for the 5G-RG over that access have been released or handed over to 3GPP access. The 5G-RG connected to 5GC via NG-RAN is specified in TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [84]. For the scenario of FN-RG, which is not 5G capable, connected via W-5GAN to 5GC, the W-AGF provides the N1 interface to AMF on behalf of the FN-RG. An UE connected to a 5G-RG or FN-RG can access to the 5GC via the N3IWF or via the TNGF where the combination of 5G-RG/FN-RG, W-AGF and UPF serving the 5G-RG or FN-RG is acting respectively as Untrusted Non-3GPP access network or as a Trusted Non-3GPP access network defined in clause 4.2.8.2; for example a UE is connecting to 5G-RG by means of WLAN radio access and connected to 5GC via N3IWF. The detailed description is specified in TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [84]. The roaming architecture for 5G-BRG, FN-BRG, 5G-CRG and FN-CRG with the W-5GAN is not specified in this Release. The Home Routed roaming scenario is supported for 5G-RG connected via NG RAN, while Local Breakout scenario is not supported. 5G Multi-Operator Core Network (5G MOCN) is supported for 5G-RG connected via NG RAN as defined in clause 5.18 | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.8 |
5,933 | 5.3.5.5.5 MAC entity configuration | The UE shall: 1> if SCG MAC is not part of the current UE configuration (i.e. SCG establishment): 2> create an SCG MAC entity; 1> if any DAPS bearer is configured: 2> reconfigure the MAC main configuration for the target cell group in accordance with the received mac-CellGroupConfig excluding tag-ToReleaseList and tag-ToAddModList; 1> else: 2> reconfigure the MAC main configuration of the cell group in accordance with the received mac-CellGroupConfig excluding tag-ToReleaseList and tag-ToAddModList; 1> if the received mac-CellGroupConfig includes the tag-ToReleaseList: 2> for each TAG-Id value included in the tag-ToReleaseList that is part of the current UE configuration: 3> release the TAG indicated by TAG-Id; 1> if the received mac-CellGroupConfig includes the tag-ToAddModList: 2> for each tag-Id value included in tag-ToAddModList that is not part of the current UE configuration (TAG addition): 3> add the TAG, corresponding to the tag-Id, in accordance with the received timeAlignmentTimer; 2> for each tag-Id value included in tag-ToAddModList that is part of the current UE configuration (TAG modification): 3> reconfigure the TAG, corresponding to the tag-Id, in accordance with the received timeAlignmentTimer. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.5.5 |
5,934 | 5.2.19.2.2 Naf_EventExposure_Subscribe service operation | Service operation name: Naf_EventExposure_Subscribe Description: The consumer NF subscribes the event to collect AF data for UE(s), group of UEs, or any UE, or updates the subscription which is already defined in AF. Input, Required: Target of Event Reporting (either UE ID(s), or UE IPv4 address(es), or UE IPv6 prefix(es), or Internal/External Group Identifier, or indication that any UE is targeted), (set of) Event ID(s), Notification Target Address (+ Notification Correlation ID) and Event Reporting Information as defined in Table 4.15.1-1. NOTE 1: UE ID includes GPSI or SUPI. Input, Optional: NF ID, Event Filter(s) associated with each Event ID, (set of) External Application Identifier(s), Subscription Correlation ID (in the case of modification of the existing subscription), Expiry time. NOTE 2: In the case of untrusted AF, NEF ID is used as NF ID. Output, Required: Operation execution result indication. When the subscription is accepted: Subscription Correlation ID, Expiry time (required if the subscription can be expired based on the local policy). Output, Optional: First corresponding event report is included, if corresponding information is available (see clause 4.15.1). | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.19.2.2 |
5,935 | 4.2.1.4 Number of additional E-RABs attempted to setup | a) This measurement provides the number of additional E-RABs attempted to setup. 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 SETUP REQUEST message, each requested E-RAB in the message 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 additional E-RABs attempted to setup. 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. EstabAddAttNbr.QCI where QCI identifies the E-RAB level quality of service class. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic. h) EPS. i) This measurement is to support the Accessibility KPI “E-RAB Accessibility” defined in [13]. Another usage of this measurement is to support the coverage ratio (CR) calculation for EE coverage area determination in [21]. | 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.1.4 |
5,936 | 8.10.1.2.13 Performance requirements for DCI format 2D and non Quasi Co-located Antenna Ports | 8.10.1.2.13.1 Minimum requirements for QCL Type C and 3 Layers Spatial Multiplexing The requirements are specified in Table 8.10.1.2.13.1-3, with the additional parameters in Table 8.10.1.2.13.1-1 and Table 8.10.1.2.13.1-2. The purpose of this test is to verify the UE capability of supporting non quasi-colocated antenna ports when the UE receives DCI format 2D in a scenario with non-coherent joint transmission from two transmission points. The test verifies that the UE configured with quasi co-location type C performs correct tracking and compensation of the frequency and time difference between two transmission points, channel parameters estimation, channel estimation and rate matching behaviour according to the ‘PDSCH RE Mapping and Quasi-Co-Location Indicator’ signalling defined in [6]. In Table 8.10.1.2.13.1-1, transmission point 1 (TP 1) is the serving cell transmitting PDCCH, synchronization signals, PBCH and PDSCH, and transmission point 2 (TP 2) has different Cell ID and transmits PDSCH. In the test the PDSCH is transmitted from TP 1 and TP 2. The downlink physical channel setup for TP 1 is according to Annex C.3.2 and for TP 2 according to Annex C.3.2. Table 8.10.1.2.13.1-1: Test Parameters Table 8.10.1.2.13.1-2: Configurations of PQI and DL transmission hypothesis for each PQI set Table 8.10.1.2.13.1-3: Performance Requirements 8.10.1.2.13.2 Minimum requirements for QCL Type C and 4 Layers Spatial Multiplexing The requirements are specified in Table 8.10.1.2.13.2-3, with the additional parameters in Table 8.10.1.2.13.2-1 and Table 8.10.1.2.13.2-2. The purpose of this test is to verify the UE capability of supporting non quasi-colocated antenna ports when the UE receives DCI format 2D in a scenario with non-coherent joint transmission from two transmission points. The test verifies that the UE configured with quasi co-location type C performs correct tracking and compensation of the frequency and time difference between two transmission points, channel parameters estimation, channel estimation and rate matching behaviour according to the ‘PDSCH RE Mapping and Quasi-Co-Location Indicator’ signalling defined in [6]. In Table 8.10.1.2.13.2-1, transmission point 1 (TP 1) is the serving cell transmitting PDCCH, synchronization signals, PBCH and PDSCH, and transmission point 2 (TP 2) has different Cell ID and transmits PDSCH. In the test the PDSCH is transmitted from TP 1 and TP 2. The downlink physical channel setup for TP 1 is according to Annex C.3.2 and for TP 2 according to Annex C.3.2. Table 8.10.1.2.13.2-1: Test Parameters Table 8.10.1.2.13.2-2: Configurations of PQI and DL transmission hypothesis for each PQI set Table 8.10.1.2.13.2-3: Performance Requirements | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.10.1.2.13 |
5,937 | 8.9.10.1 IAB-node orderly release | For orderly release, the IAB-donor-CU can remove the F1 interface connection to the IAB-DU without releasing the IAB-MT. If the IAB-MT needs to be released, IAB-MT will perform the deregistration procedure. If both F1 interface and IAB-MT need to be released, the IAB-donor-CU should remove the F1 interface to the IAB-DU before it releases the collocated IAB-MT. The deregistration procedure is the same as the UE deregistration procedure. The IAB-donor-CU hands over the UEs or child IAB-nodes currently connected to the IAB-node’s cell(s) to another cell(s), or releases the UEs and may stop accepting incoming handovers or connections to the IAB-node that is about to be released. The IAB-donor-CU may also update/release the BH RLC channels in the intermediate hops. At this point, the F1 interface will be released and the corresponding SCTP associations will be removed. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.9.10.1 |
5,938 | 9.6.6 Mapping to physical resources | The block of complex-valued symbols shall be multiplied with the amplitude scaling factor in order to conform to the transmit power specified in [4], and mapped in sequence starting with to physical resource blocks on antenna port . The PSBCH shall use the same set of resource blocks as the synchronization signal. The mapping to resource elements corresponding to the physical resource blocks used for the PSBCH and not used for transmission of reference signals or synchronization signals shall be in increasing order of first the index , then the index , starting with the first slot in the subframe. The resource-element index given by Resource elements in the last SC-FDMA symbol within a subframe should be counted in the mapping process but not transmitted. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.6.6 |
5,939 | 5.1.2.4 UE - PDN GW user plane with 3G access via the S12 interface | Legend: - GPRS Tunnelling Protocol for the user plane (GTP-U): This protocol tunnels user data between UTRAN and the S-GW as well as between the S-GW and the P-GW in the backbone network. GTP shall encapsulate all end user IP packets. - UDP/IP: These are the backbone network protocols used for routing user data and control signalling. - Protocols on the Uu interface are described in TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. - SGSN controls the user plane tunnel establishment and establish a Direct Tunnel between UTRAN and S-GW as shown in Figure 5.1.2.4-1. Figure 5.1.2.4-1: User Plane for UTRAN mode and Direct Tunnel on S12 | 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.2.4 |
5,940 | 5.2.21.4.4 Nnsacf_SliceEventExposure_Notify service operation | Service operation name: Nnsacf_SliceEventExposure_Notify Description: This service operation is used by the NSACF to report the current number of UEs registered with a network slice or the current number of PDU Sessions established on a network slice in numbers or in percentage from the maximum allowed numbers, based on threshold or at expiry of periodic timer. Inputs, Required: Event ID, Event Filter, Event Reporting information, Notification Correlation Information. The Event ID parameter defines the type of the reported information, i.e. the number of UEs registered with a network slice or the number of PDUs Sessions established on a network slice. The Event Filter parameter is the S-NSSAI for which the Notification applies. The Event Reporting information parameter provides the network slice status information in terms of the current number of UEs registered with a network slice or the current number of PDU Sessions established on a network slice. If the Notification is threshold based where the threshold is a certain number of UEs registered with a network slice or PDU Sessions established on a network slice or the threshold is a percentage of the maximum number of UEs registered with a network slice or the maximum number of PDU Sessions established on a network slice, the Event Reporting information parameter contains confirmation for reaching this threshold value. If the Notification is periodical, the Event Reporting information parameter provides information for the current number of UEs registered with a network slice (e.g. represented in percentage of the maximum number of the UEs registered with the network slice) or information for the current number of PDU Sessions established on a network slice (e.g. represented in percentage of the maximum number of the PDU Sessions established on the network slice) with periodicity provided during the subscription. For current number of UEs registered with a network slice, the network slice status information may include information to indicate whether this is number of UE with at least one PDU Session/PDN Connection. Outputs, Required: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.21.4.4 |
5,941 | 4.4.4.6 Location updating accepted by the network | If the location updating is accepted by the network a LOCATION UPDATING ACCEPT message is transferred to the mobile station. In case the identity confidentiality service is active (see subclauses 4.3.1 and 4.4.4.4), the TMSI reallocation may be part of the location updating procedure. The TMSI allocated is then contained in the LOCATION UPDATING ACCEPT message together with the location area identifier LAI. The network shall in this case start the supervision timer T3250 as described in subclause 4.3.1. In a shared network, if the MS is a network sharing supporting MS, the network shall indicate in the LAI the PLMN identity of the CN operator that has accepted the location updating; if the MS is a network sharing non-supporting MS, the network shall indicate the PLMN identity of the common PLMN (see 3GPP TS 23.251[ Network sharing; Architecture and functional description ] [109]). In a multi-operator core network (MOCN) with common GERAN, the network shall indicate in the LAI the common PLMN identity (see 3GPP TS 23.251[ Network sharing; Architecture and functional description ] [109]). If the network wishes to prolong the RR connection to allow the mobile station to initiate MM connection establishment (for example if the mobile station has indicated in the LOCATION UPDATING REQUEST that it has a follow-on request pending) the network shall send "follow on proceed" in the LOCATION UPDATING ACCEPT and start timer T3255. If the mobile station has indicated "CS fallback mobile terminating call" in the LOCATION UPDATING REQUEST message, the network shall maintain the RR connection for an implementation dependent duration to allow for mobile terminating call establishment. If the mobile station has also indicated in the LOCATION UPDATING REQUEST message that it has a follow-on request pending, it is implementation dependent whether the network proceeds with the mobile terminating call establishment or allows for a mobile initiated MM connection establishment. The mobile station receiving a LOCATION UPDATING ACCEPT message shall store the received location area identification LAI, stop timer T3210, reset the location update attempt counter and set the update status in the SIM/USIM to UPDATED. If the message contains an IMSI, the mobile station is not allocated any TMSI, and shall delete any TMSI in the SIM/USIM accordingly. If the message contains a TMSI, the mobile station is allocated this TMSI, and shall store this TMSI in the SIM/USIM and a TMSI REALLOCATION COMPLETE shall be returned to the network. If neither IMSI nor TMSI is received in the LOCATION UPDATING ACCEPT message, the old TMSI if any available shall be kept. If the MS has initiated the location updating procedure due to manual CSG selection and receives a LOCATION UPDATING ACCEPT message, and the MS sent the LOCATION UPDATING REQUEST message in a CSG cell, the MS shall check if the CSG ID and associated PLMN identity of the cell are contained in the Allowed CSG list. If not, the MS shall add that CSG ID and associated PLMN identity to the Allowed CSG list and the MS may add the HNB Name (if provided by lower layers) to the Allowed CSG list if the HNB Name is present in neither the Operator CSG list nor the Allowed CSG list. If the LAI or PLMN identity contained in the LOCATION UPDATING ACCEPT message is a member of the list of "forbidden location areas for regional provision of service", the list of "forbidden location areas for roaming" or the "forbidden PLMN list" then such entries shall be deleted. If the MS receives the LOCATION UPDATING ACCEPT message from a PLMN for which a PLMN-specific attempt counter is maintained (see subclause 4.1.1.6A), then the MS shall reset this counter. If the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the MS shall reset this counter. The network may also send a list of "equivalent PLMNs" in the LOCATION UPDATING ACCEPT message. Each entry of the list contains a PLMN code (MCC+MNC). If the location updating procedure is initiated during a CS fallback procedure and the network is configured to support the return to the last registered E-UTRAN PLMN after CS fallback as specified in 3GPP TS 23.272[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ] [133], and the PLMN identity which is provided as part of the RAI contained in the ROUTING AREA UPDATE ACCEPT message differs from the last registered E-UTRAN PLMN identity, the network shall include the last registered E-UTRAN PLMN identity in the list of "equivalent PLMNs" in the LOCATION UPDATING ACCEPT message. NOTE 1: The network can determine a location updating procedure is initiated during a CS fallback procedure as specified in 3GPP TS 23.272[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ] [133]. NOTE 2: The last registered E-UTRAN PLMN identity can be derived by the network as specified in 3GPP TS 23.272[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ] [133]. The mobile station shall store the list, as provided by the network, except that any PLMN code that is already in the "forbidden PLMN list" shall be removed from the "equivalent PLMNs" list before it is stored by the mobile station. If the mobile station is supporting S1 mode, it shall also remove any PLMN code that is already in the list of "forbidden PLMNs for GPRS service" before storing the list. In addition the mobile station shall add to the stored list the PLMN code of the registered PLMN that sent the list. All PLMNs in the stored list shall be regarded as equivalent to each other for PLMN selection, cell selection/re-selection and handover. The stored list in the mobile station shall be replaced on each occurrence of the LOCATION UPDATING ACCEPT message. If no list is contained in the message, then the stored list in the mobile station shall be deleted. The list shall be stored in the mobile station while switched off so that it can be used for PLMN selection after switch on. After that, the mobile station shall act according to the presence of the "Follow-on proceed" information element in the LOCATION UPDATING ACCEPT; if this element is present and the mobile station has a CM application request pending, it shall send a CM SERVICE REQUEST to the network and proceed as in subclause 4.5.1.1. Otherwise, it shall start timer T3240 and enter state WAIT FOR NETWORK COMMAND. Furthermore, the network may grant authorisation for the mobile station to use GSM-Cordless Telephony System (CTS) in the Location Area and its immediate neighbourhood. The mobile should memorise this permission in non-volatile memory. If the "CTS permission" IE is not present in the message, the mobile is not authorised to use GSM-CTS, and shall accordingly delete any memorised permission. NOTE 3: The interaction between CTS and GPRS procedures are not yet defined. The network may also send a Local Emergency Numbers List with local emergency numbers in the LOCATION UPDATING ACCEPT, by including the Emergency Number List IE. The mobile equipment shall store the Local Emergency Numbers List, as provided by the network. The Local Emergency Numbers List stored in the mobile equipment shall be replaced on each receipt of the Emergency Number List IE. The received Local Emergency Numbers List shall be provided to the upper layers. The emergency number(s) received in the Emergency Number List IE are valid only in networks in the same country as the cell on which this IE is received. If no list is contained in the LOCATION UPDATING ACCEPT message, then the stored Local Emergency Numbers List in the mobile equipment shall be kept, except if the mobile equipment has successfully registered to a PLMN in a country different from that of the PLMN that sent the Local Emergency Numbers List. The mobile equipment shall use the stored Local Emergency Numbers Lt of emergency numbers received from the network in addition to the emergency numbers stored on the SIM/USIM or ME to detect that the number dialled is an emergency number. NOTE 4: The mobile equipment may use the Local Emergency Numbers List to assist the end user in determining whether the dialled number is intended for an emergency service or for another destination, e.g. a local directory service. The possible interactions with the end user are implementation specific. NOTE 5: An MS that supports procedures specified in 3GPP TS 24.302[ Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 ] [156], can get additional local emergency numbers through those procedures, which can be used based on operator policy (see 3GPP TS 24.302[ Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 ] [156]) to detect that the number dialled is an emergency number. The Local Emergency Numbers List shall be deleted at switch off and removal of the SIM/USIM. The mobile equipment shall be able to store up to ten local emergency numbers received from the network. | 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.4.4.6 |
5,942 | 4.12b.3 Deregistration procedure | The Deregistration procedure for devices (N5CW devices) that do not support 5G NAS signalling over WLAN access shall be supported as specified in clause 4.12a.3 for the trusted non-3GPP access with the following modifications: - The TNAP is substituted by a trusted WLAN access point (TWAP). - The TNGF is substituted by the Trusted WLAN Interworking Function (TWIF). - The TWIF sends and receives NAS deregistration request/accept messages on behalf of N5CW device. - For both UE/Network-initiated deregistration procedures, the TWIF may initiate the release of Yt' connection between the N5CW device and TWIF. - UE-initiated deregistration procedure can be initiated by the TWIF, when it has lost connectivity to the N5CW device. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.12b.3 |
5,943 | 5.2.3.3.3 Nudm_SDM_Notification service operation | Service or service operation name: Nudm_SDM_Notification Description: The UDM notifies NF consumer of the updates of Subscription Data indicated by the "subscription data Type" input and additional UDM-related parameters. Inputs, Required: Subscription data type(s), Key for each Subscription data type(s). Inputs, Optional: None. Outputs, Required: Result Indication. The UDM invokes this service operation under the following cases: - When the subscription data is updated at the UDM, the updated subscription information is notified to the serving NF that has subscribed for the specific subscription data type to be notified. - When the UDM needs to deliver Steering of Roaming information to a UE. - When the UDM needs to deliver UDM Update Data to a UE (e.g. a new Routing Indicator or Default Configured NSSAI to the UE). If the updated subscription information is related to session management the subscriber data may contain e.g. Allowed PDU Session Type(s), Allowed SSC mode(s), default 5QI/ARP. Outputs, Optional: Redirection information. If the NF consumer is AMF and if the result of the service operation fails, AMF shall set corresponding cause value in result indication which can be used by the UDM for further action. If the related UE is not served by the AMF and the AMF knows which AMF is serving the UE, the AMF provides redirection information which can be used by the UDM to resend UE related message to the AMF that serves the UE. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.3.3.3 |
5,944 | 6.5.1.7 Handling PDN connectivity request for UE configured for dual priority | If a PDN connection exists that was established due to a request including a low priority indicator set to "MS is configured for NAS signalling low priority" and the upper layers of the UE request to establish a PDN connection with the same APN and a low priority indicator set to "MS is not configured for NAS signalling low priority", when initiating the PDN connectivity request procedure, the UE shall: - send a PDN CONNECTIVITY REQUEST message with the same combination of APN and PDN type as the existing PDN connection. If the UE receives a PDN CONNECTIVITY REJECT message with ESM cause #55 "multiple PDN connections for a given APN not allowed", the upper layers are informed of this; or - send a PDN CONNECTIVITY REQUEST message with the same APN after the successful deactivation of the existing PDN connection. NOTE: The above list of options also apply for the case when the existing PDN connection was established due to a request including a low priority indicator set to "MS is not configured for NAS signalling low priority" and the new request to establish a PDN connection with the same APN contains a low priority indicator set to "MS is configured for NAS signalling low priority". As an alternative the upper layers of the UE can request to establish a PDN connection with a different APN. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.5.1.7 |
5,945 | 8.2.1.4.1D Enhanced Performance Requirement Type B - Single-layer Spatial Multiplexing 2 Tx Antenna Port with TM4 interference model | The requirements are specified in Table 8.2.1.4.1D-2, with the addition of the parameters in Table 8.2.1.4.1D-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify the closed loop rank-one performance with wideband precoding with two transmit antennas when the PDSCH transmission in the serving cell is interfered by PDSCH of two interfering cells applying transmission mode 4 interference model defined in clause B.6.3. In Table 8.2.1.4.1D-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.1.4.1D-1: Test Parameters for Single-layer Spatial Multiplexing (FRC) with TM4 interference model Table 8.2.1.4.1D-2: Minimum Performance for Enhanced Performance Requirement Type B, Single-layer Spatial Multiplexing (FRC) with TM4 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.1.4.1D |
5,946 | 5.3.6.6 vSRVCC handover to a circuit-switched multimedia call | Upon vSRVCC handover to a traffic channel suitable for a data call, the MS shall use a single bearer capability IE for multimedia with ITC set to "UDI" and FNUR set to 64 kbit/s for the call. NOTE: After the MS has attached the user connection (see subclause 5.2.4.3), the MS initially uses predefined codecs for voice and video as specified in 3GPP TS 26.111[ Codec for circuit switched multimedia telephony service; Modifications to H.324 ] [80]. Additionally, the MS can perform in-band codec re-negotiation using H.245 signalling according to the procedures defined in 3GPP TS 26.111[ Codec for circuit switched multimedia telephony service; Modifications to H.324 ] [80]. | 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.3.6.6 |
5,947 | 9.3.2.2.1 FDD | For the parameters specified in Table 9.3.2.2.1-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.3.2.2.1-2 and by the following a) a CQI index not in the set {median CQI -1, median CQI, median CQI +1} shall be reported at least % of the time; b) the ratio of the throughput obtained when transmitting the transport format indicated by each reported wideband CQI index and that obtained when transmitting a fixed transport format configured according to the wideband CQI median shall be ≥ ; c) when transmitting the transport format indicated by each reported wideband CQI index, the average BLER for the indicated transport formats shall be greater or equal to 0.02. Table 9.3.2.2.1-1 Fading test for FDD Table 9.3.2.2.1-2 Minimum requirement (FDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.3.2.2.1 |
5,948 | 9.3.1.2 Handover | Inter RAT mobility is characterised by the following: - The Source RAT configures Target RAT measurement and reporting. - The source RAT decides on the preparation initiation and provides the necessary information to the target RAT in the format required by the target RAT: - For handover preparation from E-UTRA to NR, the source RAT issues a handover preparation request message to the target RAT passing a transparent RRC container with necessary information to prepare the handover at the target side. The information for the target RAT is the same type as specified in clause 9.2.3.2.1 including the current QoS flow to DRB mapping applied to the UE and RRM configuration. - The details of RRM configuration are the same type as specified for NR in clause 9.2.3.2.1 including beam measurement information for the listed cells if the measurements are available. - Radio resources are prepared in the target RAT before the handover. - The RRC reconfiguration message from the target RAT is delivered to the source RAT via a transparent container, and is passed to the UE by the source RAT in the handover command: - The inter-RAT handover command message carries the same type of information required to access the target cell as specified for NR baseline handover in clause 9.2.3.2.1. - The in-sequence and lossless handover is supported for the handover between gNB and ng-eNB. - Both Xn and NG based inter-RAT handover between NG-RAN nodes is supported. Whether the handover is over Xn or CN is transparent to the UE. - In order to keep the SDAP and PDCP configurations for in-sequence and lossless inter-RAT handover, delta-configuration for the radio bearer configuration is used. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 9.3.1.2 |
5,949 | 9.2.3.2.1 C-Plane Handling | The intra-NR RAN handover performs the preparation and execution phase of the handover procedure performed without involvement of the 5GC, i.e. preparation messages are directly exchanged between the gNBs. The release of the resources at the source gNB during the handover completion phase is triggered by the target gNB. The figure below depicts the basic handover scenario where neither the AMF nor the UPF changes: Figure 9.2.3.2.1-1: Intra-AMF/UPF Handover 0. The UE context within the source gNB contains information regarding roaming and access restrictions which were provided either at connection establishment or at the last TA update. 1. The source gNB configures the UE measurement procedures and the UE reports according to the measurement configuration. 2. The source gNB decides to handover the UE, based on MeasurementReport and RRM information. 3. The source gNB issues a Handover Request message to the target gNB passing a transparent RRC container with necessary information to prepare the handover at the target side. The information includes at least the target cell ID, KgNB*, the C-RNTI of the UE in the source gNB, RRM-configuration including UE inactive time, basic AS-configuration including antenna Info and DL Carrier Frequency, the current QoS flow to DRB mapping rules applied to the UE, the SIB1 information from source gNB, the UE capabilities for different RATs, PDU session related information, and can include the UE reported measurement information including beam-related information if available. The PDU session related information includes the slice information and QoS flow level QoS profile(s). The source gNB may also request a DAPS handover for one or more DRBs. NOTE 1: After issuing a Handover Request, the source gNB should not reconfigure the UE, including performing Reflective QoS flow to DRB mapping. 4. Admission Control may be performed by the target gNB. Slice-aware admission control shall be performed if the slice information is sent to the target gNB. If the PDU sessions are associated with non-supported slices the target gNB shall reject such PDU Sessions. 5. The target gNB prepares the handover with L1/L2 and sends the HANDOVER REQUEST ACKNOWLEDGE to the source gNB, which includes a transparent container to be sent to the UE as an RRC message to perform the handover. The target gNB also indicates if a DAPS handover is accepted. NOTE 2: As soon as the source gNB receives the HANDOVER REQUEST ACKNOWLEDGE, or as soon as the transmission of the handover command is initiated in the downlink, data forwarding may be initiated. NOTE 3: For DRBs configured with DAPS, downlink PDCP SDUs are forwarded with SN assigned by the source gNB, until SN assignment is handed over to the target gNB in step 8b, for which the normal data forwarding follows as defined in 9.2.3.2.3. 6. The source gNB triggers the Uu handover by sending an RRCReconfiguration message to the UE, containing the information required to access the target cell: at least the target cell ID, the new C-RNTI, the target gNB security algorithm identifiers for the selected security algorithms. It can also include a set of dedicated RACH resources, the association between RACH resources and SSB(s), the association between RACH resources and UE-specific CSI-RS configuration(s), common RACH resources, and system information of the target cell, etc. NOTE 4: For DRBs configured with DAPS, the source gNB does not stop transmitting downlink packets until it receives the HANDOVER SUCCESS message from the target gNB in step 8a. NOTE 4a: CHO cannot be configured simultaneously with DAPS handover. 7a. For DRBs configured with DAPS, the source gNB sends the EARLY STATUS TRANSFER message. The DL COUNT value conveyed in the EARLY STATUS TRANSFER message indicates PDCP SN and HFN of the first PDCP SDU that the source gNB forwards to the target gNB. The source gNB does not stop assigning SNs to downlink PDCP SDUs until it sends the SN STATUS TRANSFER message to the target gNB in step 8b. 7. For DRBs not configured with DAPS, the source gNB sends the SN STATUS TRANSFER message to the target gNB to convey the uplink PDCP SN receiver status and the downlink PDCP SN transmitter status of DRBs for which PDCP status preservation applies (i.e. for RLC AM). The uplink PDCP SN receiver status includes at least the PDCP SN of the first missing UL PDCP SDU and may include a bit map of the receive status of the out of sequence UL PDCP SDUs that the UE needs to retransmit in the target cell, if any. The downlink PDCP SN transmitter status indicates the next PDCP SN that the target gNB shall assign to new PDCP SDUs, not having a PDCP SN yet. NOTE 5: In case of DAPS handover, the uplink PDCP SN receiver status and the downlink PDCP SN transmitter status for a DRB with RLC-AM and not configured with DAPS may be transferred by the SN STATUS TRANSFER message in step 8b instead of step 7. NOTE 6: For DRBs configured with DAPS, the source gNB may additionally send the EARLY STATUS TRANSFER message(s) between step 7 and step 8b, to inform discarding of already forwarded PDCP SDUs. The target gNB does not transmit forwarded downlink PDCP SDUs to the UE, whose COUNT is less than the conveyed DL COUNT value and discards them if transmission has not been attempted already. 8. The UE synchronises to the target cell and completes the RRC handover procedure by sending RRCReconfigurationComplete message to target gNB. In case of DAPS handover, the UE does not detach from the source cell upon receiving the RRCReconfiguration message. The UE releases the source resources and configurations and stops DL/UL reception/transmission with the source upon receiving an explicit release from the target node. NOTE 6a: From RAN point of view, the DAPS handover is considered to only be completed after the UE has released the source cell as explicitly requested from the target node. RRC suspend, a subsequent handover or inter-RAT handover cannot be initiated until the source cell has been released. 8a/b In case of DAPS handover, the target gNB sends the HANDOVER SUCCESS message to the source gNB to inform that the UE has successfully accessed the target cell. In return, the source gNB sends the SN STATUS TRANSFER message for DRBs configured with DAPS for which the description in step 7 applies, and the normal data forwarding follows as defined in 9.2.3.2.3. NOTE 7: The uplink PDCP SN receiver status and the downlink PDCP SN transmitter status are also conveyed for DRBs with RLC-UM in the SN STATUS TRANSFER message in step 8b, if configured with DAPS. NOTE 8: For DRBs configured with DAPS, the source gNB does not stop delivering uplink QoS flows to the UPF until it sends the SN STATUS TRANSFER message in step 8b. The target gNB does not forward QoS flows of the uplink PDCP SDUs successfully received in-sequence to the UPF until it receives the SN STATUS TRANSFER message, in which UL HFN and the first missing SN in the uplink PDCP SN receiver status indicates the start of uplink PDCP SDUs to be delivered to the UPF. The target gNB does not deliver any uplink PDCP SDUs which has an UL COUNT lower than the provided. NOTE 9: Void. 9. The target gNB sends a PATH SWITCH REQUEST message to AMF to trigger 5GC to switch the DL data path towards the target gNB and to establish an NG-C interface instance towards the target gNB. 10. 5GC switches the DL data path towards the target gNB. The UPF sends one or more "end marker" packets on the old path to the source gNB per PDU session/tunnel and then can release any U-plane/TNL resources towards the source gNB. 11. The AMF confirms the PATH SWITCH REQUEST message with the PATH SWITCH REQUEST ACKNOWLEDGE message. 12. Upon reception of the PATH SWITCH REQUEST ACKNOWLEDGE message from the AMF, the target gNB sends the UE CONTEXT RELEASE to inform the source gNB about the success of the handover. The source gNB can then release radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue. The RRM configuration can include both beam measurement information (for layer 3 mobility) associated to SSB(s) and CSI-RS(s) for the reported cell(s) if both types of measurements are available. Also, if CA is configured, the RRM configuration can include the list of best cells on each frequency for which measurement information is available. And the RRM measurement information can also include the beam measurement for the listed cells that belong to the target gNB. The common RACH configuration for beams in the target cell is only associated to the SSB(s). The network can have dedicated RACH configurations associated to the SSB(s) and/or have dedicated RACH configurations associated to CSI-RS(s) within a cell. The target gNB can only include one of the following RACH configurations in the Handover Command to enable the UE to access the target cell: i) Common RACH configuration; ii) Common RACH configuration + Dedicated RACH configuration associated with SSB; iii) Common RACH configuration + Dedicated RACH configuration associated with CSI-RS. The dedicated RACH configuration allocates RACH resource(s) together with a quality threshold to use them. When dedicated RACH resources are provided, they are prioritized by the UE and the UE shall not switch to contention-based RACH resources as long as the quality threshold of those dedicated resources is met. The order to access the dedicated RACH resources is up to UE implementation. Upon receiving a handover command requesting DAPS handover, the UE suspends source cell SRBs, stops sending and receiving any RRC control plane signalling toward the source cell, and establishes SRBs for the target cell. The UE releases the source cell SRBs configuration upon receiving source cell release indication from the target cell after successful DAPS handover execution. When DAPS handover to the target cell fails and if the source cell link is available, then the UE reverts back to the source cell configuration and resumes source cell SRBs for control plane signalling transmission. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 9.2.3.2.1 |
5,950 | 8.70 MBMS Service Area | The MBMS Service Area is defined in 3GPP TS 23.246[ Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description ] [37]. The MBMS Service Area information element indicates the area over which the Multimedia Broadcast Multicast Service is to be distributed. The payload shall be encoded as per the MBMS-Service-Area AVP defined in 3GPP TS 29.061[ Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) ] [38], excluding the AVP Header fields (as defined in IETF RFC 3588 [39], clause 4.1). Figure 8.70-1: MBMS Service Area | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 8.70 |
5,951 | 4.16.12.1.2 UE Policy Association Modification with old PCF during AMF relocation | This procedure addresses the scenario where a UE Policy Association Modification with the old PCF during AMF relocation. Figure 4.16.12.1.2-1: Policy Association Modification with the old PCF during AMF relocation This procedure addresses both roaming and non-roaming scenarios. In the non-roaming case the V-PCF is not involved. In the roaming case, the AMF interacts with the V-PCF and the V-PCF interacts with the H-PCF. 1. [Conditional] When the old AMF and the new AMF belong to the same PLMN, the old AMF transfers to the new AMF the UE Policy Association information including policy control request trigger(s) and the PCF ID(s). For the roaming case, the new AMF receives both V-PCF ID and H-PCF ID. 2. Based on local policies, the new AMF decides to re-use the UE policy association for the UE Context with the (V-)PCF and contacts the (V)-PCF identified by the PCF ID received in step 1. NOTE: The scenario that only the H-PCF is reused by the new AMF but the V-PCF is not reused is not considered in this Release. 3. The new AMF sends Npcf_UEPolicyControl_Update to the (V-)PCF to update the UE policy association with the (V-)PCF. If a Policy Control Request Trigger condition is met, the information matching the trigger condition may also be provided by the new AMF. In the roaming case, step 4 and 5 are executed, otherwise step 6 follows. 4. The V-PCF forwards the information received from new AMF in step 3 to the (H-)PCF. 5. The H-PCF replies to the V-PCF. In non-roaming case, the PCF may subscribe to Analytics from NWDAF as defined in clause 6.1.1.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. 6. The (V-)PCF updates the stored information provided by the old AMF with the information provided by the new AMF. The (V-)PCF sends a Npcf_UEPolicyControl Update Response to the AMF. 7. The (H-)PCF may create the UE policy container including UE policy information as defined in clause 6.6 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. In the case of roaming the H-PCF may include the UE policy container in the Npcf_UEPolicyControl UpdateNotify Request. 8. The V-PCF sends a response to H-PCF using Npcf_UEPolicyControl UpdateNotify Response. Steps 9, 10 and 11 are the same as steps 8, 9 and 10 of procedure UE Policy Association Establishment in clause 4.16.11. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.16.12.1.2 |
5,952 | 5.8.10.2.7 Sidelink reporting configuration addition/modification | The UE shall: 1> for each sl-ReportConfigId included in the received sl-ReportConfigToAddModList: 2> if an entry with the matching sl-ReportConfigId exists in the sl-ReportConfigList within the VarMeasConfigSL, for this entry: 3> reconfigure the entry with the value received for this sl-ReportConfig; 3> for each sl-MeasId associated with this sl-ReportConfigId included in the sl-MeasIdList within the VarMeasConfigSL, if any: 4> remove the measurement reporting entry for this sl-MeasId from the VarMeasReportListSL, if included; 4> stop the periodical reporting timer and reset the associated information (e.g. sl-TimeToTrigger) for this sl-MeasId; 2> else: 3> add a new entry for the received sl-ReportConfig to the sl-ReportConfigList within the VarMeasConfigSL. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.10.2.7 |
5,953 | 5.30.2.4.3 Manual network selection | For manual network selection UEs operating in SNPN access mode provide to the user the list of SNPNs (each is identified by a PLMN ID and NID) and related human-readable names (if available) of the available SNPNs the UE has respective SUPI and credentials for. If the UEs supports access to an SNPN using credentials from a Credentials Holder, the UE also presents available SNPNs which broadcast the "access using credentials from a Credentials Holder is supported" indication and the human-readable names related to the SNPNs (if available). NOTE: The details of manual SNPN selection are defined in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17]. When a UE performs Initial Registration to an SNPN, the UE shall indicate the selected PLMN ID and NID as broadcast by the selected SNPN to NG-RAN. NG-RAN shall inform the AMF of the selected PLMN ID and NID. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.30.2.4.3 |
5,954 | 5.4.1 Dedicated bearer activation | The dedicated bearer activation procedure for a GTP based S5/S8 is depicted in figure 5.4.1-1. This procedure shall not be used when the UE is accessing over NB-IoT (i.e. RAT Type = NB-IoT). Figure 5.4.1-1: Dedicated Bearer Activation Procedure NOTE 1: Steps 3-10 are common for architecture variants with GTP based S5/S8 and PMIP-based S5/S8. For an PMIP-based S5/S8, procedure steps (A) and (B) are defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. Steps 1, 2, 11 and 12 concern GTP based S5/S8. 1. If dynamic PCC is deployed, the PCRF sends a PCC decision provision (QoS policy) message to the PDN GW. This corresponds to the initial steps of the PCRF-Initiated IP-CAN Session Modification procedure or to the PCRF response in the PCEF initiated IP-CAN Session Modification procedure as defined in TS 23.203[ Policy and charging control architecture ] [6], up to the point that the PDN GW requests IP-CAN Bearer Signalling. The PCC decision provision message may indicate that User Location Information and/or UE Time Zone Information is to be provided to the PCRF as defined in TS 23.203[ Policy and charging control architecture ] [6]. If dynamic PCC is not deployed, the PDN GW may apply local QoS policy. 2. The PDN GW uses this QoS policy to assign the EPS Bearer QoS, i.e., it assigns the values to the bearer level QoS parameters QCI, ARP, GBR and MBR; see clause 4.7.3. If this dedicated bearer is created as part of the handover procedure from non-3GPP access with GTP-based S2a/S2b, then the PDN GW applies the Charging Id already in use for the corresponding dedicated bearer while the UE was in non-3GPP access (i.e bearer with the same QCI and ARP as in non-3GPP access). Otherwise, the PDN GW generates a Charging Id for the dedicated bearer. The PDN GW sends a Create Bearer Request message (IMSI, PTI, EPS Bearer QoS, Maximum Packet Loss Rate (UL, DL), TFT, S5/S8 TEID, Charging Id, LBI, Protocol Configuration Options) to the Serving GW, the Linked EPS Bearer Identity (LBI) is the EPS Bearer Identity of the default bearer. The Procedure Transaction Id (PTI) parameter is only used when the procedure was initiated by a UE Requested Bearer Resource Modification Procedure - see clause 5.4.5. Protocol Configuration Options may be used to transfer application level parameters between the UE and the PDN GW (see TS 23.228[ IP Multimedia Subsystem (IMS); Stage 2 ] [52]), and are sent transparently through the MME and the Serving GW. NOTE 2: The PCO is sent in the dedicated bearer activation procedure either in response to a PCO received from the UE, or without the need to send a response to a UE provided PCO e.g. when the network wants the bearer to be dedicated for IMS signalling. For a QCI=1 bearer, the Maximum Packet Loss Rate (UL, DL) may be provided by the PDN GW as described in TS 23.203[ Policy and charging control architecture ] [6]. 3. The Serving GW sends the Create Bearer Request (IMSI, PTI, EPS Bearer QoS, Maximum Packet Loss Rate (UL, DL), TFT, S1-TEID, PDN GW TEID (GTP-based S5/S8), LBI, Protocol Configuration Options) message to the MME. If the UE is in ECM-IDLE state the MME will trigger the Network Triggered Service Request from step 3 (which is specified in clause 5.3.4.3). In that case the following steps 4-7 may be combined into Network Triggered Service Request procedure or be performed stand-alone. The MME checks if the UE can support the establishment of additional user plane radio bearer based on the maximum number of user plane radio bearers indicated by NB-IoT UE in the UE Network Capability IE as defined in clause 5.11.3 and for WB-E-UTRAN in clause 4.12. If the UE is in ECM-IDLE state and extended idle mode DRX is enabled for the UE, the MME will trigger Network Triggered Service Request from step 3 (which is specified in clause 5.3.4.3), and start a timer which is configured to a value smaller than the GTP re-transmission timer. If the MME receives no response from the UE before the timer expires, the MME sends a Create Bearer Response with a rejection cause indicating that the UE is temporarily not reachable due to power saving and, if a Delay Tolerant Connection indication was set for the PDN connection, the MME sets the internal flag Pending Network Initiated PDN Connection Signalling. The rejection is forwarded by the Serving GW to the PDN GW. In this case, the steps 4-11 are skipped. NOTE 3: If ISR is activated and the Serving GW does not have a downlink S1-U and the SGSN has notified the Serving GW that the UE has moved to PMM-IDLE or STANDBY state, the Serving GW sends Downlink Data Notification to trigger MME and SGSN to page the UE (as specified in clause 5.3.4.3) before sending the Create Bearer Request message. 4. The MME selects an EPS Bearer Identity, which has not yet been assigned to the UE. The MME then builds a Session Management Request including the PTI, TFT, EPS Bearer QoS parameters (excluding ARP), Protocol Configuration Options, the EPS Bearer Identity, the Linked EPS Bearer Identity (LBI) and a WLAN offloadability indication. If the UE has UTRAN or GERAN capabilities and the network supports mobility to UTRAN or GERAN, the MME uses the EPS bearer QoS parameters to derive the corresponding PDP context parameters QoS Negotiated (R99 QoS profile), Radio Priority, Packet Flow Id and TI and includes them in the Session Management Request. If the UE indicated in the UE Network Capability it does not support BSS packet flow procedures, then the MME shall not include the Packet Flow Id. The MME then signals the Bearer Setup Request (EPS Bearer Identity, EPS Bearer QoS, Maximum Packet Loss Rate (UL, DL), Session Management Request, S1-TEID) message to the eNodeB. The MME may include an indication whether the traffic of this PDN Connection is allowed to be offloaded to WLAN as described in clause 4.3.23. 5. The eNodeB maps the EPS Bearer QoS to the Radio Bearer QoS. It then signals a RRC Connection Reconfiguration (Radio Bearer QoS, Session Management Request, EPS RB Identity) message to the UE. The UE shall store the QoS Negotiated, Radio Priority, Packet Flow Id and TI, which it received in the Session Management Request, for use when accessing via GERAN or UTRAN. The UE NAS stores the EPS Bearer Identity and links the dedicated bearer to the default bearer indicated by the Linked EPS Bearer Identity (LBI). The UE uses the uplink packet filter (UL TFT) to determine the mapping of traffic flows to the radio bearer. The UE may provide the EPS Bearer QoS parameters to the application handling the traffic flow. The application usage of the EPS Bearer QoS is implementation dependent. The UE shall not reject the RRC Connection Reconfiguration on the basis of the EPS Bearer QoS parameters contained in the Session Management Request. NOTE 4: How the eNodeB uses the Maximum Packet Loss Rate (UL, DL) for handover threshold decision, if provided, is out of scope of 3GPP specifications. NOTE 5: The details of the Radio Bearer QoS are 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]. 6. The UE acknowledges the radio bearer activation to the eNodeB with a RRC Connection Reconfiguration Complete message. 7. The eNodeB acknowledges the bearer activation to the MME with a Bearer Setup Response (EPS Bearer Identity, S1-TEID, PSCell ID) message. The eNodeB indicates whether the requested EPS Bearer QoS could be allocated or not. The MME shall be prepared to receive this message either before or after the Session Management Response message (sent in step 9). The PSCell ID is included if Dual Connectivity is active for the UE in the RAN. 8. The UE NAS layer builds a Session Management Response including EPS Bearer Identity. The UE then sends a Direct Transfer (Session Management Response) message to the eNodeB. 9. The eNodeB sends an Uplink NAS Transport (Session Management Response) message to the MME. 10. Upon reception of the Bearer Setup Response message in step 7 and the Session Management Response message in step 9, the MME acknowledges the bearer activation to the Serving GW by sending a Create Bearer Response (EPS Bearer Identity, S1-TEID, User Location Information (ECGI), PSCell ID) message. 11. The Serving GW acknowledges the bearer activation to the PDN GW by sending a Create Bearer Response (EPS Bearer Identity, S5/S8-TEID, User Location Information (ECGI)) message. 12. If the dedicated bearer activation procedure was triggered by a PCC Decision Provision message from the PCRF, the PDN GW indicates to the PCRF whether the requested PCC decision (QoS policy) could be enforced or not, allowing the completion of the PCRF-Initiated IP-CAN Session Modification procedure or the PCEF initiated IP-CAN Session Modification procedure as defined in TS 23.203[ Policy and charging control architecture ] [6], after the completion of IP-CAN bearer signalling. If requested by the PCRF the PDN GW indicates User Location Information and/or UE Time Zone Information to the PCRF as defined in TS 23.203[ Policy and charging control architecture ] [6]. If the dedicated bearer activation is rejected with a cause indicating that the UE is temporarily not reachable due to power saving, then the PDN GW re-attempts the same procedure after it receives the indication that the is UE available for end to end signalling in the subsequent Modify Bearer Request message. NOTE 6: The exact signalling of step 1 and 12 (e.g. for local break-out) is outside the scope of this specification. This signalling and its interaction with the dedicated bearer activation procedure are to be specified in TS 23.203[ Policy and charging control architecture ] [6]. Steps 1 and 12 are included here only for completeness. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.4.1 |
5,955 | – SCGFailureInformation | The SCGFailureInformation message is used to provide information regarding NR SCG failures detected by the UE. Signalling radio bearer: SRB1 RLC-SAP: AM Logical channel: DCCH Direction: UE to Network SCGFailureInformation message -- ASN1START -- TAG-SCGFAILUREINFORMATION-START SCGFailureInformation ::= SEQUENCE { criticalExtensions CHOICE { scgFailureInformation SCGFailureInformation-IEs, criticalExtensionsFuture SEQUENCE {} } } SCGFailureInformation-IEs ::= SEQUENCE { failureReportSCG FailureReportSCG OPTIONAL, nonCriticalExtension SCGFailureInformation-v1590-IEs OPTIONAL } SCGFailureInformation-v1590-IEs ::= SEQUENCE { lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } FailureReportSCG ::= SEQUENCE { failureType ENUMERATED { t310-Expiry, randomAccessProblem, rlc-MaxNumRetx, synchReconfigFailureSCG, scg-ReconfigFailure, srb3-IntegrityFailure, other-r16, spare1}, measResultFreqList MeasResultFreqList OPTIONAL, measResultSCG-Failure OCTET STRING (CONTAINING MeasResultSCG-Failure) OPTIONAL, ..., [[ locationInfo-r16 LocationInfo-r16 OPTIONAL, failureType-v1610 ENUMERATED {scg-lbtFailure-r16, beamFailureRecoveryFailure-r16, t312-Expiry-r16, bh-RLF-r16, beamFailure-r17, spare3, spare2, spare1} OPTIONAL ]], [[ previousPSCellId-r17 SEQUENCE { physCellId-r17 PhysCellId, carrierFreq-r17 ARFCN-ValueNR } OPTIONAL, failedPSCellId-r17 SEQUENCE { physCellId-r17 PhysCellId, carrierFreq-r17 ARFCN-ValueNR } OPTIONAL, timeSCGFailure-r17 INTEGER (0..1023) OPTIONAL, perRAInfoList-r17 PerRAInfoList-r16 OPTIONAL ]] } MeasResultFreqList ::= SEQUENCE (SIZE (1..maxFreq)) OF MeasResult2NR -- TAG-SCGFAILUREINFORMATION-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,956 | D.3.3 MME to 3G SGSN combined hard handover and SRNS relocation procedure | The MME to 3G Gn/Gp SGSN Combined Hard Handover and SRNS Relocation procedure is illustrated in Figure D.3.3-1. Any steps descriptions that are from inter Gn/Gp SGSNs procedures of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7] are shown as italic text and remain unmodified. In those step descriptions an MS stands for UE, old SGSN for old MME and GGSN for P-GW. The procedure parts between E-UTRAN eNodeB and UE, and between E-UTRAN eNodeB and MME are compliant with the equivalent procedure parts in clause "5.5 Handover". If emergency bearer services are ongoing for the UE, handover to the target RNC is performed independent of the Handover Restriction List. The SGSN checks, as part of the Routing Area Update in the execution phase, if the handover is to a restricted area and if so SGSN deactivate the non-emergency PDP context as specified in TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7], clause 9.2.4.2. Figure D.3.3-1: MME to 3G SGSN combined hard handover and SRNS relocation procedure 1. The source eNodeB decides to initiate a handover to the target access network, UTRAN Iu mode. At this point both uplink and downlink user data is transmitted via the following: Bearer(s) between UE and source eNodeB, GTP tunnel(s) between source eNodeB, Serving GW and PDN GW. 2. The source eNodeB sends a Handover Required (S1AP Cause, Target RNC Identifier, Source to Target Transparent Container) message to the source MME to request the CN to establish resources in the target RNC and the target SGSN. The bearers that will be subject to data forwarding (if any) are identified by the new SGSN in a later step (see step 5 below). 3. The old MME sends a Forward Relocation Request message (IMSI, Tunnel Endpoint Identifier Signalling, MM Context, PDP Context, Target Identification, RAN Transparent Container, RANAP Cause, GCSI) to the new SGSN. For relocation to an area where Intra Domain Connection of RAN Nodes to Multiple CN Nodes is used, the old MME may have multiple new Gn/Gp SGSNs for each relocation target in a pool area, in which case the old MME will select one of them to become the new Gn/Gp SGSN, as specified in TS 23.236[ Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes ] [30]. PDP context contains GGSN Address for User Plane and Uplink TEID for Data (to this GGSN Address and Uplink TEID for Data, the Serving GW and the new SGSN send uplink packets). At the same time a timer is started on the MM and PDP contexts in the old MME (see Routing Area Update procedure in clause "Location Management Procedures (Iu mode)"). The old MME does not set any GCSI flag as the MME has no GPRS CAMEL Subscription Information. The S1AP Cause received from eNodeB is indicated as RANAP Cause. The Source to Target Transparent Container received from eNodeB is indicated as RAN Transparent Container. The MM context includes information on the EPS Bearer context(s). The old MME does not include any EPS Bearer Context information for "Non-IP" bearers, or for any SCEF connection, or for "Ethernet" bearers. If none of the MS's EPS Bearers can be supported by the selected new SGSN, the old MME rejects the handover attempt by sending a Handover Preparation Failure (Cause) message to the Source eNodeB. NOTE 1: If the handover is successful, the old MME will signal to the SGW and/or SCEF to release any non-included EPS Bearers after step 15. The non-included bearers are locally released by the MS following the PDP context status synchronisation that occurs during the Routing Area Update at step 17. NOTE 2: The GGSN user plane address and uplink TEID are the old P-GW user plane address and TEID. The MME maps the EPS bearer parameters to PDP contexts. 4. The new SGSN sends a Relocation Request message (Permanent NAS UE Identity, Cause, CN Domain Indicator, Source RNC To Target RNC Transparent Container, RAB To Be Setup) to the target RNC. For each RAB requested to be established, RABs To Be Setup shall contain information such as RAB ID, RAB parameters, Transport Layer Address, and Iu Transport Association. SGSN shall not establish RABs for PDP contexts with maximum bitrate for uplink and downlink of 0 kbit/s. The list of RABs requested by the new SGSN may differ from list of RABs established in the Source RNC contained in the Source-RNC to target RNC transparent container. The target RNC should not establish the RABs (as identified from the Source-RNC to target RNC transparent container, Service Handover related information) that did not exist in the source RNC prior to the relocation. The RAB ID information element contains the NSAPI value, and the RAB parameters information element gives the QoS profile. The Transport Layer Address is the SGSN Address for user data, and the Iu Transport Association corresponds to the uplink Tunnel Endpoint Identifier Data. The new SGSN may decide to establish Direct Tunnel unless it has received a 'set' GCSI flag from the old SGSN. If the new SGSN decides to establish Direct Tunnel, it provides to the target RNC the GGSN's Address for User Plane and TEID for Uplink data. If the Access Restriction is present in the MM context, the Service Handover related information shall be included by the target SGSN for the Relocation Request message in order for RNC to restrict the UE in connected mode to handover to the RAT prohibited by the Access Restriction. After all the necessary resources for accepted RABs including the Iu user plane are successfully allocated, the target RNC shall send the Relocation Request Acknowledge message (Target RNC To Source RNC Transparent Container, RABs Setup, RABs Failed To Setup) to the new SGSN. Each RAB to be setup is defined by a Transport Layer Address, which is the target RNC Address for user data, and the Iu Transport Association, which corresponds to the downlink Tunnel Endpoint Identifier for user data. The transparent container contains all radio-related information that the MS needs for the handover, i.e. a complete RRC message (e.g., Physical Channel Reconfiguration in UTRAN case, or Handover From UTRAN, or Handover Command in GERAN Iu mode case) to be sent transparently via CN and source SRNC to the MS. For each RAB to be set up, the target RNC may receive simultaneously downlink user packets both from the source SRNC and from the new SGSN. NOTE 3: This step for the new SGSN is unmodified compared to pre-Rel-8. If the new SGSN decides to establish Direct Tunnel, it provides to the target RNC the P-GW Address for User Plane and TEID for Uplink data. The UE acts as the MS; the old eNodeB acts as the source SRNC. 5. When resources for the transmission of user data between target RNC and new SGSN have been allocated and the new SGSN is ready for relocation of SRNS, the Forward Relocation Response (Cause, RAN Transparent Container, RANAP Cause, Target-RNC Information) message is sent from the new SGSN to the old SGSN. This message indicates that the target RNC is ready to receive from source SRNC the forwarded downlink PDUs, i.e., the relocation resource allocation procedure is terminated successfully. RAN transparent container and RANAP Cause are information from the target RNC to be forwarded to the source SRNC. The Target RNC Information, one information element for each RAB to be set up, contains the RNC Tunnel Endpoint Identifier and RNC IP address for data forwarding from the source SRNC to the target RNC. The Forward Relocation Response message is applicable only in the case of inter-SGSN SRNS relocation. NOTE 4: This step is unmodified compared to pre-Rel-8. The old MME acts as the old SGSN, and the source eNodeB as the source SRNC. 6. If 'Indirect Forwarding' applies the source MME sends a Create Indirect Data Forwarding Tunnel Request message (IMSI, MME Tunnel Endpoint Identifier for Control Plane, MME Address for Control plane, Target RNC Address and TEID(s) for DL user plane) to the Serving GW. 7. The Serving GW returns a Create Indirect Data Forwarding Tunnel Response (Cause, Serving GW DL TEID(s)) message to the source MME. If the Serving GW doesn't support data forwarding, an appropriate cause value shall be returned. 8. The source MME completes the preparation phase towards source eNodeB by sending the message Handover Command (Target to Source Transparent Container, Bearers Subject to Data Forwarding List, S1AP Cause). "Bearers Subject to Data forwarding list" may be included in the message and it shall be a list of 'Address(es) and TEID(s) for user traffic data forwarding' received from target side in the preparation phase (Step 5) in the case of direct forwarding or received from the Serving GW in the preparation phase (Step 7) in the case of indirect forwarding. RANAP Cause as received from new SGSN is indicated as S1AP Cause. RAN Transparent Container as received from new SGSN is indicated as Target to Source Transparent Container. 9. The source eNodeB initiates data forwarding for bearers specified in the "Bearers Subject to Data Forwarding List". The data forwarding may go directly to target RNC or alternatively go via the Serving GW if so decided by source MME in the preparation phase. 10. The source eNodeB will give a command to the UE to handover to the target access network via the message HO from E-UTRAN Command. This message includes a transparent container including radio aspect parameters that the target RNC has set-up in the preparation phase. The details of this E-UTRAN specific signalling are described in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. 11. If the PLMN has configured Secondary RAT usage data reporting and the source eNodeB has Secondary RAT usage data to report, the eNodeB sends the RAN data report message (Secondary RAT usage data) to the MME. Since the handover is an inter-RAT handover, the MME continues with the Secondary RAT usage data reporting procedure as in clause 5.7A.3. The reporting procedure in clause 5.7A.3 is only performed if PGW secondary RAT usage reporting is active. NOTE 5: The source eNodeB does not send any RAN contexts towards the target RNC. 12. The target RNC shall send a Relocation Detect message to the new SGSN when the relocation execution trigger is received. For SRNS relocation type "UE Involved", the relocation execution trigger may be received from the Uu interface; i.e., when target RNC detects the MS on the lower layers. When the Relocation Detect message is sent, the target RNC shall start SRNC operation. NOTE 6: This step is unmodified compared to pre-Rel-8. 13. When the MS has reconfigured itself, it sends an RRC message e.g., a Physical Channel Reconfiguration Complete message to the target SRNC. The UE locally deactivates ISR by setting its TIN from "RAT-related TMSI" to "GUTI", if any EPS bearer context activated after the ISR was activated in the UE exists. 14. When the target SRNC receives the appropriate RRC message, e.g. Physical Channel Reconfiguration Complete message or the Radio Bearer Release Complete message in UTRAN case, or the Handover To UTRAN Complete message or Handover Complete message in GERAN case, i.e. the new SRNC-ID + S-RNTI are successfully exchanged with the MS by the radio protocols, the target SRNC shall initiate a Relocation Complete procedure by sending the Relocation Complete message to the new SGSN. The purpose of the Relocation Complete procedure is to indicate by the target SRNC the completion of the relocation of the SRNS to the CN. NOTE 7: This step is unmodified compared to pre-Rel-8. The UE acts as the MS. 15. Upon receipt of Relocation Complete message, if the SRNS Relocation is an inter SGSN SRNS relocation, the new SGSN signals to the old SGSN the completion of the SRNS relocation procedure by sending a Forward Relocation Complete message. A timer in source MME is started to supervise when resources in Source eNodeB and Source Serving GW shall be released. For all bearers that were not included in the Forward Relocation Request message sent in step 3, the MME now releases them by sending a Delete Bearer Command to the SGW, or, the appropriate message to the SCEF. NOTE 8: For the SGSN this step is unmodified compared to pre-Rel-8. The old MME acts as the old SGSN, and the source eNodeB as the source SRNC. 16. Upon receipt of the Relocation Complete message, the CN shall switch the user plane from the source RNC to the target SRNC. If the SRNS Relocation is an inter-SGSN SRNS relocation or if Direct Tunnel was established in intra-SGSN SRNS relocation, the new SGSN sends Update PDP Context Request messages (new SGSN Address, SGSN Tunnel Endpoint Identifier, QoS Negotiated, serving network identity, CGI/SAI, User CSG Information, RAT type, MS Info Change Reporting support indication, NRSN, DTI) to the GGSNs concerned. The SGSN shall send the serving network identity to the GGSN. If Direct Tunnel is established the SGSN provides to GGSN the RNC's Address for User Plane and TEID for Downlink data and shall include the DTI to instruct the GGSN to apply Direct Tunnel specific error handling procedure as described in clause 13.8. NRSN indicates SGSN support of the network requested bearer control. The GGSNs update their PDP context fields and return an Update PDP Context Response (GGSN Tunnel Endpoint Identifier, Prohibit Payload Compression, APN Restriction, MS Info Change Reporting Action, CSG Information Reporting Action, BCM) message. The Prohibit Payload Compression indicates that the SGSN should negotiate no data compression for this PDP context. The PDN GW shall include a Charging Id to be used at the SGSN as the Charging Id for reporting usage for this PDP context. The PDN GW shall include the Charging Id in the offline charging data. NOTE 9: This step is unmodified compared to pre-Rel-8. The P-GW acts as the GGSN. 17. After the MS has finished the reconfiguration procedure and if the new Routing Area Identification is different from the old one or if the MS' TIN indicates "GUTI", the MS initiates the Routing Area Update procedure. See clause "Location Management Procedures (Iu mode)". For a MS supporting CIoT EPS Optimisations, the MS uses the PDP context status information in the RAU Accept to identify any non-transferred bearers that it shall locally release. NOTE 10: It is only a subset of the RA update procedure that is performed, since the MS is in PMM-CONNECTED state. NOTE 11: This step is unmodified compared to pre-Rel-8. The UE acts as the MS. The old EPS bearer information in old MME and Serving GW is removed as part of the Routing Area Update procedure. 18. When the timer started in step 15 expires, the source MME deletes the EPS bearer resources by sending Delete Session Request (Cause, Operation Indication, Secondary RAT usage data) messages to the Serving GW because the new SGSN is a Gn/Gp SGSN, which is derived from using GTPv1 for relocation signalling between new Gn/Gp SGSN and old MME. The new Gn/Gp SGSN does not signal any Serving GW change. The operation Indication flag is not set, that indicates to the Serving GW that the Serving GW shall not initiate a delete procedure towards the PDN GW. Secondary RAT usage data was included if it was received in step 11a. The Source Serving GW acknowledges with Delete Session Response (Cause) messages. If ISR is activated the cause indicates to the old S-GW that the old S-GW shall delete the bearer resources on the other old CN node by sending Delete Bearer Request message(s) to that CN node. If resources for indirect forwarding have been allocated then these are released. When the timer started in step 15 expires, the source MME sends a Release Resources message to the source eNodeB. When the Release Resources message has been received and there is no longer any need for the eNodeB to forward data, the source eNodeB releases its resources. If the SRNS Relocation is inter-SGSN, then the following CAMEL procedure calls shall be performed (see referenced procedures in TS 23.078[ Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2 ] [29]) NOTE 12: The C1 CAMEL procedure call was omitted intentionally from this procedure since EPS does not support CAMEL procedure calls. The other CAMEL procedure calls are unmodified compared to pre-Rel-8. The new SGSN shall determine the Maximum APN restriction based on the received APN Restriction of each PDP context from the GGSN and then store the new Maximum APN restriction value. If the SRNS Relocation is intra-SGSN, then the above mentioned CAMEL procedures calls shall not be performed. If Routing Area Update occurs, the SGSN shall determine whether Direct Tunnel can be used based on the received GPRS CAMEL Subscription Information. If Direct Tunnel can not be maintained the SGSN shall re-establish RABs and initiate the Update PDP Context procedure to update the IP Address and TEID for Uplink and Downlink data. If Routing Area Update occurs, then the following CAMEL procedure calls shall be performed (see referenced procedures in TS 23.078[ Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2 ] [29]): C2) CAMEL_GPRS_Routing_Area_Update_Session and CAMEL_PS_Notification. They are called in the following order: - The CAMEL_GPRS_Routing_Area_Update_Session procedure is called. The procedure returns as result "Continue". - Then the CAMEL_PS_Notification procedure is called. The procedure returns as result "Continue". C3) CAMEL_GPRS_Routing_Area_Update_Context. This procedure is called several times: once per PDP context. It returns as result "Continue". For C2 and C3: refer to Routing Area Update procedure description for detailed message flow. NOTE 13: Handover Reject is performed as defined in clause 5.5.2.1.4, excluding steps 4 and 7. | 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") | D.3.3 |
5,957 | 10.1.5 SC-FDMA baseband signal generation | For , the time-continuous signal in SC-FDMA symbol in a slot is defined by clause 5.6 with the quantity replaced by . For , the time-continuous signal for sub-carrier index in SC-FDMA symbol in an uplink slot is defined by for where parameters for and are given in Table 10.1.5-1, is the modulation value of symbol , and the phase rotation is defined by where is the number of transport blocks defined in 16.5.1 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4]. If >1 and interleaving between codewords is applied according to clause 16.5.1 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4], then the symbol counter is reset at the start of the first NPUSCH codeword transmission and incremented for each symbol during the transmission of the NPUSCH codewords. For other cases, the symbol counter is reset to 0 at the start of each NPUSCH codeword transmission and incremented for each symbol during the transmission of the NPUSCH codeword. Table 10.1.5-1: SC-FDMA parameters for The SC-FDMA symbols in a slot shall be transmitted in increasing order of , starting with , where SC-FDMA symbol starts at time within the slot. For , the remaining in are not transmitted and used for guard period. Only normal CP is supported for Narrowband IoT uplink in this release of the specification. | 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 | 10.1.5 |
5,958 | 6.8.1.3 Key handling for the Registration procedure when registered in NG-RAN | NOTE: This clause applies to both 3GPP access and non-3GPP access. Before the UE can initiate the Registration procedure, the UE needs to transition to CM-CONNECTED state. The UE shall use the current 5G security context to protect the Registration Request and include the corresponding 5G-GUTI and ngKSI value. The Registration Request shall be integrity-protected, but not confidentiality-protected. UE shall use the current 5G security context algorithms to protect the Registration Request message. For the case that this security context is non-current in the AMF, the AMF shall delete any existing current 5G security context and make the used 5G NAS security context the current 5G security context. If "PDU session(s) to be re-activated" is included in the Registration request message or if the AMF chooses to establish radio bearers when there is pending downlink UP data or pending downlink signalling, radio bearers will be established as part of the Registration procedure and a KgNB/KeNB will be derived. If there was no subsequent NAS SMC, the value of the uplink NAS COUNT, associated with the 3GPP access over which the Registration request message was sent from the UE to the AMF, is used as freshness parameter in the KgNB/KeNB derivation using the KDF as specified in clause Annex A.9. In the case a primary authentication is run successfully, the uplink and downlink NAS COUNT shall be set to the start values (i.e. zero). In the case source and target AMF use different NAS algorithms, the target AMF re-derives the NAS keys from KAMF with the new algorithm identities as input and provides the new algorithm identifiers within a NAS SMC. The UE shall assure that the NAS keys used to verify the integrity of the NAS SMC are derived using the algorithm identity specified in the NAS SMC. If there is a NAS Security Mode Command after the Registration Request over 3GPP access, the UE and AMF shall use the value of the uplink NAS COUNT associated with the 3GPP access of the most recent NAS Security Mode Complete and the related KAMF as the parameter in the derivation of the KgNB/KeNB. From this KgNB/KeNB the RRC protection keys and the UP protection keys are derived as described in sub-clause 6.2.3.1. In the case of Registration over non-3GPP access, the UE and AMF shall use the uplink NAS COUNT associated with the non-3GPP access of the most recent NAS Security Mode Complete and the related KAMF as the parameter in the derivation of the KN3IWF. IPsec SA is established between the UE and N3IWF using the KN3IWF as described in sub-clause 7.2.1 of this document. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.1.3 |
5,959 | 8.2.2.9.2 Minimum Requirement for Rel-16 further enhanced HST | The requirements are specified in Table 8.2.2.9.2-2, with the addition of the parameters in Table 8.2.2.9.2-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify UE performance in the HST-SFN-500 and HST-500 scenario. The test for HST-SFN-500 scenario defined in B.3B is applied when highSpeedEnhDemodFlag2-r16 [7] is received. The test for HST-500 scenario defined in B.3C is applied when highSpeedEnhDemodFlag2-r16 [7] is not received. HST-500 test is not applicable to UE that has passed HST-SFN-500 test. Table 8.2.2.9.2-1: Test Parameters for UE performance in HST-SFN-500 and HST-500 scenario (FRC) Table 8.2.2.9.2-2: Minimum performance UE in HST-SFN scenario (FRC) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.2.9.2 |
5,960 | 24.5 Home PLMN ProSe Function Address | The Home PLMN ProSe Function address is in the form of a Fully Qualified Domain Name as defined in IETF RFC 1035 [19] and IETF RFC 1123 [20]. This address consists of six labels. Each label shall consist of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-) in accordance with IETF RFC 1035 [19]. Each label shall begin and end with either an alphabetic character or a digit in accordance with IETF RFC 1123 [20]. The case of alphabetic characters is not significant. For 3GPP systems, if not pre-configured on the UE or provisioned by the network, the UE shall derive the Home PLMN ProSe Function address from the IMSI as described in the following steps: 1. Take the first 5 or 6 digits, depending on whether a 2 or 3-digit MNC is used (see 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [27]) and separate them into MCC and MNC; if the MNC is 2-digit MNC then a zero shall be added at the beginning. 2. Use the MCC and MNC derived in step 1 to create the "mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org" domain name. 3. Add the label "prose-function." to the beginning of the domain. An example of a Home PLMN ProSe Function address is: IMSI in use: 234150999999999; where: - MCC = 234; - MNC = 15; and - MSIN = 0999999999, which gives the following Home PLMN ProSe Function address: "prose-function.mnc015.mcc234.pub.3gppnetwork.org". | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 24.5 |
5,961 | 9.3.5 Additional requirements for enhanced receiver Type A | The purpose of the test is to verify that the reporting of the channel quality is based on the receiver of the enhanced Type A. Performance requirements are specified in terms of the relative increase of the throughput obtained when the transport format is that indicated by the reported CQI subject to an interference model compared to the case with a white Gaussian noise model, and a requirement on the minimum BLER of the transmitted transport formats indicated by the reported CQI subject to an 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 | 9.3.5 |
5,962 | 5.3.15.2 Reception of the RRCReject by the UE | The UE shall: 1> stop timer T300, if running; 1> stop timer T319, if running; 1> stop timer T319a, if running and consider SDT procedure is not ongoing; 1> stop timer T302, if running; 1> reset MAC and release the default MAC Cell Group configuration; 1> if waitTime is configured in the RRCReject: 2> start timer T302, with the timer value set to the waitTime; 1> if RRCReject is received in response to a request from upper layers: 2> inform the upper layer that access barring is applicable for all access categories except categories '0' and '2'; 1> if RRCReject is received in response to an RRCSetupRequest: 2> inform upper layers about the failure to setup the RRC connection, upon which the procedure ends; 1> else if RRCReject is received in response to an RRCResumeRequest or an RRCResumeRequest1: 2> if resume is triggered by upper layers: 3> inform upper layers about the failure to resume the RRC connection; 2> if resume is triggered due to an RNA update; or 2> if resume is triggered for SDT and T380 has expired: 3> set the variable pendingRNA-Update to true; 2> discard the current KgNB key, the KRRCenc key, the KRRCint key, the KUPint key and the KUPenc key derived in accordance with 5.3.13.3; 2> if resume is triggered for SDT: 3> for SRB2, if it is resumed and for SRB1: 4> trigger the PDCP entity to perform SDU discard as specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5]; 4> re-establish the RLC entity as specified in TS 38.322[ NR; Radio Link Control (RLC) protocol specification ] [4]; 3> for each DRB that is not suspended: 4> indicate PDCP suspend to lower layers; 4> re-establish the RLC entity as specified in TS 38.322[ NR; Radio Link Control (RLC) protocol specification ] [4]; 2> suspend SRB1 and the radio bearers configured for SDT, if any; 2> the procedure ends. Upon L2 U2N Relay UE receives RRCReject, it either indicates to upper layers (to trigger PC5 unicast link release) or sends NotificationMessageSidelink message to the connected L2 U2N Remote UE(s) in accordance with 5.8.9.10. The RRC_INACTIVE UE shall continue to monitor paging while the timer T302 is running. NOTE: If timer T331 is running, the UE continues to perform idle/inactive measurements according to 5.7.8. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.15.2 |
5,963 | 14.3 Handling of Bearer Context Mismatch 14.3.1 General | The following requirements should apply: 1) When an EPC entity receives a response message, where one or more dedicated bearer context(s) is associated with the Cause code "Context Not Found" while the PDN connection is known by the peer, the EPC entity shall delete the corresponding bearer context(s); 2) When an SGW receives a Modify Bearer Request, where one or more dedicated bearer context(s) is missing in the request message in comparison to the Bearer Context(s) stored for the UE's PDN connection, the SGW shall accept the Modify Bearer Request message and delete the corresponding bearer context(s) locally. The PGW shall apply the same behavior if the Modify Bearer Request received at the PGW includes the Bearer Contexts to be modified IE; 3) When a SGW receives a Modify Bearer Request, where only one or more dedicated bearer context(s) is unknown, the SGW shall accept the Modify Bearer Request message partially and set the cause code "Context Not Found" for those unknown bearer context(s) at Bearer Context level. The PGW shall apply the same behavior if the Modify Bearer Request received at the PGW includes the Bearer Contexts to be modified IE; 4) When a SGW receives a Modify Access Bearer Request, where one or more dedicated bearer context(s) is missing in the request message in comparison to the Bearer Context(s) stored for all the UE's PDN connections, the SGW shall delete the corresponding bearer context(s) locally; 5) When a SGW receives a Modify Access Bearer Request, where only one or more dedicated bearer context(s) is unknown, the SGW shall accept the Modify Access Bearer Request message partially and set the cause code "Context Not Found" for those unknown bearer context(s) at Bearer Context level. NOTE: It is assumed the PGW can at least use a subsequent Modify Bearer Request to resolve Bearer Context mismatch, so that the SGW need not send explicit message to delete unknown Bearer Context. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 14.3 |
5,964 | 5.5.1.3 Registration procedure for mobility and periodic registration update 5.5.1.3.1 General | This procedure is used by a UE for both mobility and periodic registration update of 5GS services. This procedure, when used for periodic registration update of 5GS services, is performed only in 3GPP access. This procedure used for periodic registration update of 5GS services is controlled in the UE by timer T3512. When timer T3512 expires, the registration procedure for mobility and periodic registration update is started. Start and reset of timer T3512 is described in subclause 10.2. If the MUSIM UE is registered for emergency services and initiates a registration procedure for mobility and periodic registration update, the network shall not indicate the support of: - the NAS signalling connection release; - the paging indication for voice services; - the reject paging request; or - the paging restriction; in 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 | 5.5.1.3 |
5,965 | 5.2.16.2.1 Nnssf_NSSelection_Get service operation | Service operation name: Nnssf_NSSelection_Get Description: This service operation enables Network Slice selection in both the Serving PLMN and HPLMN. It also enables the NSSF to provide to the AMF the Allowed NSSAI and the Configured NSSAI for the Serving PLMN. It allows also to provide the NSAG information which is applicable (clause 5.15.14 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). It may be invoked during Registration procedure, during inter-PLMN mobility procedure, during PDU Session Establishment procedure or during UE Configuration Update procedure. When invoked during Registration procedure it may possibly trigger AMF re-allocation. When invoked during PDU Session Establishment procedure it may be invoked in the VPLMN or in the HPLMN; if invoked in the VPLMN it returns the hNRF selected by the hNSSF and if applicable, the value of the HPLMN NSI ID. When invoked during UE Configuration Update procedure or inter-PLMN mobility procedure it may be invoked in the Serving PLMN. NOTE 1: The list of events, which trigger invoking of the Nnssf_NSSelection_Get service operation, is not exhaustive. NOTE 2: The NSSF can determine the serving network and Access Type from the TAI, as described in TS 29.571[ 5G System; Common Data Types for Service Based Interfaces; Stage 3 ] [70]. Inputs, Required: None. Inputs, Conditional Required: If this service operation is invoked during Registration procedure for Network Slice selection or UE Configuration Update procedure, then the following inputs are required: - Subscribed S-NSSAI(s) with the indication if marked as default S-NSSAI, PLMN ID of the SUPI, TAI, NF type of the NF service consumer, Requester ID. If this service operation is invoked to derive the S-NSSAI for the serving PLMN (as described in clause 4.11.1.3.3), the following inputs are required: - S-NSSAIs for the HPLMN associated with established PDN connection, PLMN ID of the SUPI, NF type of the NF service consumer, Requester ID. If this service operation is invoked by target AMF during inter-PLMN mobility procedure, the following inputs are required: - S-NSSAIs for the HPLMN, PLMN ID of the SUPI, TAI. If this service operation is invoked during PDN Connection Establishment in the Serving PLMN in EPS by a SMF+PGW-C, the following inputs are required: - Subscribed S-NSSAIs for the UE, PLMN ID of the SUPI, NF type of the NF service consumer, Requester ID. If this service operation is invoked during PDU Session Establishment procedure in the Serving PLMN then the following inputs are required: - S-NSSAI, non-roaming/LBO roaming/HR roaming indication, PLMN ID of the SUPI, TAI, NF type of the NF service consumer, Requester ID. Inputs, Optional: If this service operation is invoked during Registration procedure for Network Slice selection or UE Configuration Update procedure, then the following inputs are provided if available: - Requested NSSAI, Mapping Of Requested NSSAI, Default Configured NSSAI Indication, NSSRG Information, UE support of subscription-based restrictions to simultaneous registration of network slice feature Indication, UDM indication to provide all subscribed S-NSSAIs for UEs not indicating support of subscription-based restrictions to simultaneous registration of network slices, Allowed NSSAI for current Access Type, Allowed NSSAI for the other Access Type and the corresponding Mapping Of Allowed NSSAIs for current Access Type and other Access Type, Rejected S-NSSAI(s) for RA, UE support of NSAG Information. If this service operation is invoked during PDU Session Establishment procedure, then the following input is optional: - HPLMN S-NSSAI that maps to the S-NSSAI from the Allowed NSSAI of the Serving PLMN. Outputs, Conditional Required: If this service operation is invoked during Registration procedure for Network Slice selection or UE Configuration Update procedure, then one or more of the following outputs are required: - Allowed NSSAI, Configured NSSAI; Target AMF Set or, based on configuration, the list of candidate AMF(s). If this service operation is invoked during inter-PLMN mobility procedure, then one or more of the following outputs are required: - Allowed NSSAI. If this service operation is invoked to derive the S-NSSAI for the serving PLMN (as described in clause 4.11.1.3.3), the following output is required: - S-NSSAIs for the HPLMN associated with established PDN connection, Mapping of S-NSSAIs associated with established PDN connection in the Serving PLMN. If this service operation is invoked during PDN Connection Establishment in the Serving PLMN in EPS by a SMF+PGW-C, the following outputs are required: - Subscribed S-NSSAIs for the UE, Mapping of S-NSSAIs associated with the subscribed S-NSSAIs for the UE in the Serving PLMN. If this service operation is invoked during PDU Session Establishment procedure, then the following outputs are required: - The NRF to be used to select NFs/services within the selected Network Slice instance. Outputs, conditional Optional: If this service operation is invoked during UE Registration procedure or UE Configuration Update procedure, then one or more of the following outputs are optional: - Mapping Of Allowed NSSAI, Mapping Of Configured NSSAI, NSI ID(s) associated with the Network Slice instances of the Allowed NSSAI, NRF(s) to be used to select NFs/services within the selected Network Slice instance(s) and NRF to be used to determine the list of candidate AMF(s) from the AMF Set, rejected S-NSSAI with cause of rejection, Target NSSAI, the NSAG information (defined in clause 5.15.14 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). If this service operation is invoked during inter-PLMN mobility procedure, then the following output is optional: - Mapping Of Allowed NSSAI. If this service operation is invoked during PDU Session Establishment procedure, then the following output is optional: - NSI ID associated with the S-NSSAI provided in the input. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.16.2.1 |
5,966 | 9.11.4.18 5GSM network feature support | The purpose of the 5GSM network feature support information element is to indicate whether certain session management related features are supported by the network. The 5GSM network feature support information element is coded as shown in figure 9.11.4.18.1 and table 9.11.4.18.1. The 5GSM network feature support is a type 4 information element with a minimum length of 3 octets and a maximum length of 15 octets. Figure 9.11.4.18.1: 5GSM network feature support information element Table 9.11.4.18.1: 5GSM network feature support information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.4.18 |
5,967 | 9.11.3.103 Partial NSSAI | The purpose of the Partial NSSAI information element is to deliver one or more S-NSSAIs in a set of tracking areas of a registration area from the network to the UE. The Partial NSSAI information element is coded as shown in figure 9.11.3.103.1, and table 9.11.3.103.1. The Partial NSSAI information element is a type 6 information element, with a minimum length of 13 octets and a maximum length of 808 octets. Figure 9.11.3.103.1: Partial NSSAI information element Table 9.11.3.103.1: Partial NSSAI 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.103 |
5,968 | H.2 Signalling of ingress time for time synchronization | The ingress timestamp (TSi) of the PTP event (e.g. Sync) message is provided from the ingress TT (NW-TT/UPF or DS-TT/UE) to the egress TT, if supported in the PTP messages as described in clauses 5.27.1.2.2.1 and 5.27.1.2.2.2 using the Suffix field defined in clause 13.4 of IEEE Std 1588 [126]. The structure of the Suffix field follows the recommendation of clause 14.3 of IEEE Std 1588 [126], with an organizationId specific to 3GPP, an organizationSubType referring to an ingress timestamp, and data field that carries the ingress timestamp encoded as specified in clause 5.3.3 of IEEE Std 1588 [126]. TS 24.535[ 5G System (5GS); Device-Side Time Sensitive Networking (TSN) Translator (DS-TT) to Network-Side TSN Translator (NW-TT) protocol aspects; Stage 3 ] [117] specifies the coding of the ingress timestamp in the (g)PTP messages between a DS-TT and a NW-TT. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | H.2 |
5,969 | 5.8.2.8.2 Enforcement of Dynamic PCC Rules | The application detection filters required in the UPF can be configured either in the SMF and provided to the UPF as the service data flow filter, or be configured in the UP function identified by an application identifier. When receiving a dynamic PCC rule from the PCF which contains an application identifier and/or parameters for traffic handling in the UPF: - if the application detection filter is configured in the SMF, the SMF shall provide it in the service data flow filter to the UPF, as well as parameters for traffic handling in the UPF received from the dynamic PCC rule; - otherwise, the application detection filters is configured in UPF, the SMF shall provide to UPF with the application identifier and the parameters for traffic handling in the UPF as required based on the dynamic PCC rule. The SMF shall maintain the mapping between a PCC rule received over Npcf and the flow level PDR(s) used on N4 interface. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.8.2.8.2 |
5,970 | 8.4.3.1.1 FDD Pcell (FDD single carrier) | 8.4.3.1.1.1 Minimum Requirement 2 Tx Antenna Port The average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.4.3.1.1.1-2 for Pcell and in Table 8.4.3.1.1.1-3 for LAA Scell(s), with the addition of the parameters in Table 8.4.3-1, and Table 8.4.3.1.1.1-1. The downlink physical setup is in accordance with Annex C.3.2. Table 8.4.3.1.1.1-1: Test Parameters for LAA Scell(s) Table 8.4.3.1.1.1-2: Single carrier performance for CCs which are not LAA Scells for multiple CA configurations Table 8.4.3.1.1.1-3: Single carrier performance for LAA Scell(s) for multiple CA configurations | 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.4.3.1.1 |
5,971 | 6.1.3.20 Timing Advance Report MAC Control Element | The Timing Advance MAC CE is identified by MAC subheader with LCID as specified in Table 6.2.1-2. It has a fixed size and consists of two octets defined as follows (Figure 6.1.3.20-1): - R: Reserved bit, set to 0; - Timing Advance: The Timing Advance field indicates the least integer number of subframes greater than or equal to the Timing Advance value (see TS 36.211[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation ] [7] clause 8.1). The length of the field is 14 bits. Figure 6.1.3.20-1: Timing Advance MAC CE | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.1.3.20 |
5,972 | – NeedForGapsConfigNR | The IE NeedForGapsConfigNR contains configuration related to the reporting of measurement gap requirement information. NeedForGapsConfigNR information element -- ASN1START -- TAG-NeedForGapsConfigNR-START NeedForGapsConfigNR-r16 ::= SEQUENCE { requestedTargetBandFilterNR-r16 SEQUENCE (SIZE (1..maxBands)) OF FreqBandIndicatorNR OPTIONAL -- Need R } -- TAG-NeedForGapsConfigNR-STOP -- ASN1STOP – NeedForGapsInfoNR The IE NeedForGapsInfoNR indicates whether measurement gap is required for the UE to perform SSB based measurements on an NR target band while NR-DC or NE-DC is not configured. NeedForGapsInfoNR information element -- ASN1START -- TAG-NeedForGapsInfoNR-START NeedForGapsInfoNR-r16 ::= SEQUENCE { intraFreq-needForGap-r16 NeedForGapsIntraFreqList-r16, interFreq-needForGap-r16 NeedForGapsBandListNR-r16 } NeedForGapsIntraFreqList-r16 ::= SEQUENCE (SIZE (1.. maxNrofServingCells)) OF NeedForGapsIntraFreq-r16 NeedForGapsBandListNR-r16 ::= SEQUENCE (SIZE (1..maxBands)) OF NeedForGapsNR-r16 NeedForGapsIntraFreq-r16 ::= SEQUENCE { servCellId-r16 ServCellIndex, gapIndicationIntra-r16 ENUMERATED {gap, no-gap} } NeedForGapsNR-r16 ::= SEQUENCE { bandNR-r16 FreqBandIndicatorNR, gapIndication-r16 ENUMERATED {gap, no-gap} } -- TAG-NeedForGapsInfoNR-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,973 | 9.11.3.104 AUN3 indication | The purpose of the AUN3 indication information element is to indicate to the network that the registration request by the 5G-RG is on behalf of an AUN3 device. The AUN3 indication information element is coded as shown in figure 9.11.3.104.1 and table 9.11.3.104.1. The AUN3 indication is a type 4 information element with a length of 3 octets. Figure 9.11.3.104.1: AUN3 indication information element Table 9.11.3.104.1: AUN3 indication information element 9.11.3.105 Feature authorization indication The purpose of the Feature authorization indication information element is to indicate whether the UE that is authorized to operate certain feature. The Feature authorization indication is a type 4 information element with a minimum length of 3 octets and maximum length of 257 octets. The Feature authorization indication information element is coded as shown in Figure 9.11.3.105.1 and Table 9.11.3.105.1. Figure 9.11.3.105.1: Feature authorization indication information element Table 9.11.3.105.1: Feature authorization indication 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.104 |
5,974 | U.2 Procedure | Figure: U.2-1: Primary authentication using EAP-TTLS and AAA 0. The UE is configured with the trust anchor needed to authenticate the certificate of the EAP-TTLS server running on the AUSF. Further, the UE is configured with the credentials required to authenticate with the AAA server. Steps 1-17 are same as the steps 1-17 in clause B.2.2.1 in Annex B, except in the following steps: 1. The SUPI in the NAI format, i.e., username@realm, is used. 5. EAP-TTLS is selected by the UDM as the authentication method. 6-17. EAP-TTLS phase 1 is executed between the AUSF and the UE. EAP-Type is set to EAP-TTLS and the authentication of the UE using TLS client certificate is skipped. Since TLS client certificate is not used in EAP-TTLS, the UE need not be configured with UE certificate. 18-27. After EAP-TTLS phase 1 is successfully completed, the UE runs EAP-TTLS phase 2 authentication with the AAA as specified in RFC 5281 [99] via NSSAAF. The phase 2 authentication method used is outside the scope of the present document but MS-CHAPv2 is depicted here as an example to show that the Nnssaaf_AIW_Authentication service offered by NSSAAF carries AVPs if the phase 2 authentication method is non-EAP.NOTE: As referenced in section 14.1.11 of RFC 5281 [99], allowing the use of phase 2 (inner) authentication method outside of tunnelled protocol leads to Man-in-the-Middle (MitM) vulnerability. Thus, it is assumed that the UE does not allow the use of phase 2 authentication method outside of TLS tunnel (i.e., the UE does not respond to requests for phase 2 authentication outside of the TLS tunnel). In environments where the use of phase 2 authentication outside of the tunnelled protocol cannot be prevented, EAP-TTLS implementations need to address this vulnerability by using EAP channel binding or cryptographic binding described in RFC 6678 [100]. 28-31. After EAP-TTLS phase 2 authentication is successfully completed, the rest of the procedures are same as steps 18- 21 described in clause B.2.1.1, except that the EAP-Type is set to EAP-TTLS in the EAP Response message from the UE to the AUSF. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | U.2 |
5,975 | 5.7.18 Actions for SRS for Positioning transmission in RRC_INACTIVE in a Validity Area | The UE may be configured or preconfigured with SRS for Positioning in a validity area defined by group of cells. There can be multiple preconfigured SRS for positioning that can be configured to UE where each preconfiguration belongs to different validity area. For each validity area, the UE is preconfigured with only one SRS for positioning configuration. For non-preconfigured SRS for positioning, only one validity area is configured. When the UE is (pre)configured to transmit SRS for positioning in a validity area, the UE shall: 1> if the RS in spatialRelationInfoPos cannot be accurately measured: 2> suspend the transmission of the SRS for positioning resource and monitor the configured RS; 2> if the UE determines that RS in spatialRelationInfoPos being accurately measured: 3> resume the SRS transmission. The UE releases the (pre)configured SRS for positioning with validity area upon receiving RRCRelease message with the indication to release the (pre)configuration. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.18 |
5,976 | 5.8.2.2.3 The procedure of Stateless IPv6 Address Autoconfiguration | If Stateless IPv6 Address Autoconfiguration is used for IPv6 address allocation to the UE, after PDU Session Establishment the UE may send a Router Solicitation message to the SMF to solicit a Router Advertisement message. The SMF sends a Router Advertisement message (solicited or unsolicited) to the UE. The Router Advertisement messages shall contain the IPv6 prefix. After the UE has received the Router Advertisement message, it constructs a full IPv6 address via IPv6 Stateless Address Autoconfiguration in accordance with RFC 4862 [10]. To ensure that the link-local address generated by the UE does not collide with the link-local address of the UPF and the SMF, the SMF shall provide an interface identifier (see RFC 4862 [10]) to the UE and the UE shall use this interface identifier to configure its link-local address. For Stateless Address Autoconfiguration however, the UE can choose any interface identifier to generate IPv6 addresses, other than link-local, without involving the network. However, the UE shall not use any identifiers defined in TS 23.003[ Numbering, addressing and identification ] [19] as the basis for generating the interface identifier. For privacy, the UE may change the interface identifier used to generate full IPv6 address, as defined in TS 23.221[ Architectural requirements ] [23] without involving the network. Any prefix that the SMF advertises to the UE is globally unique. The SMF shall also record the relationship between the UE's identity (SUPI) and the allocated IPv6 prefix. Because any prefix that the SMF advertises to the UE is globally unique, there is no need for the UE to perform Duplicate Address Detection for any IPv6 address configured from the allocated IPv6 prefix. Even if the UE does not need to use Neighbor Solicitation messages for Duplicate Address Detection, the UE may, for example, use them to perform Neighbor Unreachability Detection towards the SMF, as defined in RFC 4861 [54]. Therefore, the SMF shall respond with a Neighbor Advertisement upon receiving a Neighbor Solicitation message from the UE. In IPv6 multi-homing PDU session, SMF shall not allocate an interface identifier when a new IPv6 prefix allocated corresponding to the new PDU Session Anchor. The above IPv6 related messages (e.g. Router Solicitation, Router Advertisement, Neighbor Solicitation, Neighbor Advertisement) are transferred between the SMF and UE via the UPF(s). If the Control Plane CIoT 5GS Optimisation is enabled for a PDU session, the above IPv6 related messages are transferred between the SMF and UE via the AMF after PDU Session Establishment, see clauses 4.3.2.2.1 and 4.3.2.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], using the Mobile Terminated Data Transport in Control Plane CIoT 5GS Optimisation procedures. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.8.2.2.3 |
5,977 | 5.2.5.8.2 Npcf_AMPolicyAuthorization_Create service operation | Service operation name: Npcf_AMPolicyAuthorization_Create Description: Authorizes the request and optionally determines and installs AM influence data according to the information provided by the NF Consumer. Inputs, Required: SUPI. Inputs, Optional: GPSI, Throughput requirements, service coverage requirements, policy duration, subscribed events(s), 5G access stratum time distribution indication (enable, disable), Uu time synchronization error budget, clock quality detail level, clock quality acceptance criteria. The subscribed event includes Event ID as specified in Npcf_AMPolicyAuthorization_Notify service operation, Event Reporting Information defined in Table 4.15.1-1 (only the Event Reporting mode and the immediate reporting flag when applicable), Notification Target Address. Outputs, Required: Success or Failure. Outputs, Optional: Identification of the created application context, the inputs that can be accepted by the PCF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.5.8.2 |
5,978 | 10.5.5.27 E-UTRAN inter RAT information container | The purpose of the E-UTRAN inter RAT information container information element is to supply the network with E-UTRAN related information that needs to be transferred at Inter-RAT PS handover to E-UTRAN (see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [122]). The E-UTRAN inter RAT information container information element is coded as shown in figure 10.5.151/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The E-UTRAN inter RAT information container information element is a type 4 information element with a minimum length of 3 octets and an upper length limit of 257 octets. Figure 10.5.151/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : E-UTRAN inter RAT information container information element The value part of the E-UTRAN inter RAT information container information element is formatted and coded according to the UE-EUTRA-Capability IE defined in 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [129]. | 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.5.27 |
5,979 | 5.5.6.3 Actions related to transmission of LocationMeasurementIndication message | The UE shall set the contents of LocationMeasurementIndication message as follows: 1> if the procedure is initiated to indicate start of location related measurements: 2> if the procedure is initiated for RSTD measurements towards E-UTRA: 3> set the measurementIndication to the eutra-RSTD according to the information received from upper layers; 2> else if the procedure is initiated for positioning measurement towards NR: 3> set the measurementIndication to the nr-PRS-Measurement according to the information received from upper layers; 1> else if the procedure is initiated to indicate stop of location related measurements: 2> set the measurementIndication to the value release; 1> if the procedure is initiated to indicate start of subframe and slot timing detection towards E-UTRA: 2> set the measurementIndication to the value eutra-FineTimingDetection; 1> else if the procedure is initiated to indicate stop of subframe and slot timing detection towards E-UTRA: 2> set the measurementIndication to the value release; 1> submit the LocationMeasurementIndication message to lower layers for transmission, upon which the procedure ends. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.6.3 |
5,980 | 8.10.1.1.5A Single-layer Spatial Multiplexing (User-Specific Reference Symbols) | The requirements are specified in Table 8.10.1.1.5A-2, with the addition of the parameters in Table 8.10.1.1.5A-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify closed loop rank one performance on one of the antenna ports 7 or 8 with a simultaneous transmission on the other antenna port in the serving cell, and to verify rate matching with multiple CSI reference symbol configurations with non-zero and zero transmission power. Table 8.10.1.1.5A-1: Test Parameters for Testing CDM-multiplexed DM RS (single layer) with multiple CSI-RS configurations Table 8.10.1.1.5A-2: Minimum performance for CDM-multiplexed DM RS with interfering simultaneous transmission (FRC) with multiple CSI-RS configurations | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.10.1.1.5A |
5,981 | 8.3.7.12 IP header compression configuration | This IE is included in the message: a) if the UE wishes to re-negotiate IP header compression configuration associated to a PDU session and both the UE and the network supports Control plane CIoT 5GS optimization and IP header compression; or b) to negotiate IP header compression configuration associated to a PDU session after an inter-system change from S1 mode to N1 mode when both the UE and the network support control plane CIoT 5GS optimization and IP header compression, and the UE is operating in single-registration mode in the network supporting N26 interface. | 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.7.12 |
5,982 | 8.2.3.5.1 Minimum Requirement for FDD PCell | For TDD FDD CA with FDD PCell and 2DL CCs, the requirements are specified in Table 8.2.3.5.1-4 based on single carrier requirement specified in Table 8.2.3.5.1-2 and Table 8.2.3.5.1-3, with the addition of the parameters in Table 8.2.3.5.1-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of large delay CDD with 2 transmitter antennas. For TDD FDD CA with FDD PCell and 3DL CCs, the requirements are specified in Table 8.2.3.5.1-5 based on single carrier requirement specified in Table 8.2.3.5.1-2 and Table 8.2.3.5.1-3, with the addition of the parameters in Table 8.2.3.5.1-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of large delay CDD with 2 transmitter antennas. For TDD FDD CA with FDD PCell and 4DL CCs, the requirements are specified in Table 8.2.3.5.1-6 based on single carrier requirement specified in Table 8.2.3.5.1-2 and Table 8.2.3.5.1-3, with the addition of the parameters in Table 8.2.3.5.1-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of large delay CDD with 2 transmitter antennas. For TDD FDD CA with FDD PCell and 5DL CCs, the requirements are specified in Table 8.2.3.5.1-7 based on single carrier requirement specified in Table 8.2.3.5.1-2 and Table 8.2.3.5.1-3, with the addition of the parameters in Table 8.2.3.5.1-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of large delay CDD with 2 transmitter antennas. The test coverage for different number of component carriers is defined in 8.1.2.4. Table 8.2.3.5.1-1: Test Parameters for Large Delay CDD (FRC) for CA Table 8.2.3.5.1-2: Single carrier performance for multiple CA configurations for FDD PCell and SCell (FRC) Table 8.2.3.5.1-3: Single carrier performance for multiple CA configurations for TDD SCell (FRC) Table 8.2.3.5.1-4: Minimum performance for multiple CA configurations with 2DL CCs (FRC) Table 8.2.3.5.1-5: Minimum performance for multiple CA configurations with 3DL CCs (FRC) Table 8.2.3.5.1-6: Minimum performance for multiple CA configurations with 4DL CCs (FRC) Table 8.2.3.5.1-7: Minimum performance for multiple CA configurations with 5DL CCs (FRC) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.3.5.1 |
5,983 | 5.3.7a Specific requirements for UE configured to use timer T3245 | The following requirement applies for an UE that is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]): When the UE adds a PLMN identity to the "forbidden PLMN list", the "forbidden PLMNs for attach in S101 mode" list, or the "forbidden PLMNs for GPRS service" list or sets the USIM as invalid for non-EPS services or EPS services or both, and timer T3245 (see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13]) is not running, the UE shall start timer T3245 as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13], clause 4.1.1.6. Upon expiry of the timer T3245, the UE shall erase the "forbidden PLMN list", the "forbidden PLMNs for GPRS service" list, and the "forbidden PLMNs for attach in S101 mode" list and set the USIM to valid for non-EPS and EPS services. When the lists are erased, the UE performs cell selection according to 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]. If the UE is switched off when the timer T3245 is running, the UE shall behave as follows when the UE is switched on and the USIM in the UE remains the same: - let t1 be the time remaining for T3245 timeout at switch off and let t be the time elapsed between switch off and switch on. If t1 is greater than t, then the timer shall be restarted with the value t1 – t. If t1 is equal to or less than t, then the UE will follow the behaviour as defined in the paragraph above upon expiry of the timer T3245. If the UE is not capable of determining t, then the UE shall restart the timer with the value t1. | 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.7a |
5,984 | 8.2.14.1 Message definition | The DEREGISTRATION REQUEST message is sent by the AMF to the UE. See table 8.2.14.1.1. Message type: DEREGISTRATION REQUEST Significance: dual Direction: network to UE Table 8.2.14.1.1: DEREGISTRATION REQUEST message content NOTE: It is possible for AMFs compliant with version 17.7.0 or 17.8.0 of this specification to send the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" IE with IEI of value "3B" for this message or the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for regional provision of service" IE with IEI of value "3C" for this message. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 8.2.14.1 |
5,985 | 10.5.4.4a.1 Static conditions for the backup bearer capability IE contents | If the information transfer capability field (octet 3) indicates "speech", octets 4, 5, 5a, 5b, 6, 6a, 6b, 6c, 6d, 6e, 6f, 6g and 7 shall not be included. If the information transfer capability field (octet 3) indicates a value different from "speech", octets 4 and 5shall be included, octets 6, 6a, 6b, 6c, 6d, 6e, 6f and 6g are optional. In case octet 6 is included, octets 6a, 6b, and 6c shall also be included. In case octet 6d is included, octets 6e, 6f and 6g may be included. If the information transfer capability field (octet 3) indicates "facsimile group 3" and octet 6c is included, the modem type field (octet 6c) shall indicate "none". If the information transfer capability field (octet 3) indicates "other ITC" or the rate adaption field (octet 5) indicates "other rate adaption", octet 5a shall be included. The modem type field (octet 6c) shall not indicate "autobauding type 1" unless the connection element field (octet 6c) indicates "non transparent". | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.4.4a.1 |
5,986 | 8.13.2.2 Management based MDT Activation in gNB-CU-CP | The signalling flow for Management based MDT Activation in gNB-CU-CP is shown in Figure 8.13.2.2-1. Figure 8.13.2.2-1 Management based MDT Activation in gNB-CU-CP 1. The EM sends a Trace Session activation request to the gNB-CU-CP. This request includes the parameters for configuring UE measurements. 2. The gNB-CU-CP shall select the suitable UEs for MDT data collection. If the UE is not in the specified area or if the serving PLMN is not within the Management Based MDT PLMN List the UE shall not be selected by the gNB-CU-CP for MDT data collection as defined in TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ] [20]. For each selected UE, if the gNB-CU-UP should perform MDT measurement, the gNB-CU-CP sends TRACE START message to the gNB-CU-UP, including MDT configuration parameters. 3. For each selected UE, if the gNB-DU should perform MDT measurement, the gNB-CU-CP sends TRACE START message to the gNB-DU, including MDT configuration parameters. 4. The gNB-CU-CP may send CELL TRAFFIC TRACE message to the AMF for the selected UE, including Trace ID for MDT. The AMF forwards Trace ID and other information to the TCE as specified in TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ] [20]. If the UE reports an indication of measurement pollution, the gNB-CU-CP shall, if supported, include such indication as part of the measurement report to be sent to the TCE so that the TCE is able to correlate and filter the affected measurements. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.13.2.2 |
5,987 | 5.8.1 Description | In most countries, the operation of UAV is limited to the line-of-sight control i.e., the operation of UAV is allowed only when human UAV operators can directly see the UAV. Also, most countries prohibit operation of UAV at night. Recently, Korean government launched a special program which allows UAV operation even when a UAV operator is not in line-of-sight of a UAV or when the UAV operates at night. [2] But, to apply for this special program, there are certain conditions. For example: - UAV is equipped with lights for collision-avoidance purpose. These lights should be visible up to 5 KM away. - UAV is equipped with support for auto-pilot functionality, more than one way of communication channel (e.g. RF + LTE). - Observers who can monitor a UAV should be dispatched, if a UAV operator controls the UAV out of line-of-sight. These conditions will evolve or be relaxed in the future, as alternative approaches and technologies are available or enough tests have been performed to prove safety of NLOS UAV operation. For example: - Observers can be replaced to non-human system which can detect or monitor UAVs. - Light used for collision-avoidance can be replaced to other communication-based method. (e.g. broadcast of identifiers using direct 3GPP communication) - Back-up communication path can be provided even within 3GPP systems. (e.g. using direct/indirect 3GPP communication simultaneously) Figure 5.8.1-1: Identification of NLOS UAV | 3GPP TS 22.825 | Study on Remote Identification of Unmanned Aerial Systems (UAS) | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 5.8.1 |
5,988 | 5.8.1 Generic requirements | The long-term key(s) used for authentication and security association setup purposes shall be protected from physical attacks and shall never leave the secure environment of the UDM/ARPF unprotected. NOTE 1: Security mechanisms for protection of subscription credentials in ARPF are left to implementation. NOTE 2: Security mechanisms for storage of subscription credentials in the UDR and for the transfer of authentication subscription data (as specified in 3GPP TS 29.505[ 5G System; Usage of the Unified Data Repository services for Subscription Data; Stage 3 ] [70]) between UDR and ARPF are left to implementation. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 5.8.1 |
5,989 | 4.13.2.7 Number of attempted reconfigurations of LTE DRB to LWA DRB | a) This measurement provides the number of attempted reconfigurations of LTE DRB to LWA DRB. b) CC c) On transmission of RRCConnectionReconfiguration message which includes the drb-ToAddModList in the radioResourceConfigDedicated information element by the eNB, and the drb-ToAddModList contains at least one drb-Identity that is part of the current UE configuration but not an LWA DRB and the drb-TypeLWA of this DRB set to TRUE (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [18]). d) An integer value e) LWI.LteToLwaDrbReconfAtt f) WLANMobilitySet g) Valid for packet switched traffic h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.13.2.7 |
5,990 | 5.8.12 DFN derivation from GNSS | When the UE selects GNSS as the synchronization reference source, the DFN, the subframe number within a frame and slot number within a frame used for NR sidelink communication/discovery are derived from the current UTC time, by the following formulae: DFN= Floor (0.1*(Tcurrent –Tref–OffsetDFN)) mod 1024 SubframeNumber= Floor (Tcurrent –Tref–OffsetDFN) mod 10 SlotNumber= Floor ((Tcurrent –Tref–OffsetDFN)*2μ) mod (10*2μ) Where: Tcurrent is the current UTC time obtained from GNSS. This value is expressed in milliseconds; Tref is the reference UTC time 00:00:00 on Gregorian calendar date 1 January, 1900 (midnight between Thursday, December 31, 1899 and Friday, January 1, 1900). This value is expressed in milliseconds; OffsetDFN is the value sl-OffsetDFN if configured, otherwise it is zero. This value is expressed in milliseconds. μ=0/1/2/3 corresponding to the 15/30/60/120 kHz of SCS for SL, respectively. NOTE 1: In case of leap second change event, how UE obtains the scheduled time of leap second change to adjust Tcurrent correspondingly is left to UE implementation. How UE handles to avoid the sudden discontinuity of DFN is left to UE implementation. NOTE 2: Void. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.12 |
5,991 | 8.9.4.2.1 Enhanced Downlink Control Channel Performance Requirement Type A - 2 Tx Antenna Port with Non-Colliding CRS Dominant Interferer | The purpose of this test is to verify the Enhanced Downlink Control Channel Performance Requirement Type A for PDCCH/PCFICH with 2 transmit antennas for the case of dominant interferer with the non-colliding CRS pattern and applying interference model defined in clause B.7.1. For the parameters specified in Table 8.4.2-1 and Table 8.9.4.2.1-1, the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.9.4.2.1-2. In Table 8.9.4.2.1-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the agressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is provided and includes Cell 2 and Cell 3. Table 8.9.4.2.1-1: Test Parameters for PDCCH/PCFICH Table 8.9.4.2.1-2: Minimum Performance for PDCCH/PCFICH for Enhanced Downlink Control Channel Performance Requirement Type A | 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.9.4.2.1 |
5,992 | 20.4.4 Session-Termination-Answer Command | The STA command, defined in IETF RFC 6733 (DIAMETER BASE) [111], is indicated by the Command-Code field set to 275 and the ‘R’ bit cleared in the Command Flags field, is sent in response to an STR command. The relevant AVPs that are of use for the SGmb interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for SGmb purposes and should be ignored by the receiver or processed according to the relevant specifications. Message Format: <ST-Answer> ::= < Diameter Header: 275, PXY > < Session-Id > { Result-Code } { Origin-Host } { Origin-Realm } * [ Class ] [ Error-Message ] [ Error-Reporting-Host ] [ Failed-AVP ] [ Origin-State-Id ] * [ Redirect-Host ] [ Redirect-Host-Usage ] [ Redirect-Max-Cache-Time ] * [ Proxy-Info ] [ Restart-Counter ] | 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.4.4 |
5,993 | 10.2 Downlink Scheduling | In the downlink, the gNB can dynamically allocate resources to UEs via the C-RNTI on PDCCH(s). A UE always monitors the PDCCH(s) in order to find possible assignments when its downlink reception is enabled (activity governed by DRX and cell DTX when configured). When CA is configured, the same C-RNTI applies to all serving cells. The gNB may pre-empt an ongoing PDSCH transmission to one UE with a latency-critical transmission to another UE. The gNB can configure UEs to monitor interrupted transmission indications using INT-RNTI on a PDCCH. If a UE receives the interrupted transmission indication, the UE may assume that no useful information to that UE was carried by the resource elements included in the indication, even if some of those resource elements were already scheduled to this UE. In addition, with Semi-Persistent Scheduling (SPS), the gNB can allocate downlink resources for the initial HARQ transmissions to UEs: RRC defines the periodicity of the configured downlink assignments while PDCCH addressed to CS-RNTI can either signal and activate the configured downlink assignment, or deactivate it; i.e. a PDCCH addressed to CS-RNTI indicates that the downlink assignment can be implicitly reused according to the periodicity defined by RRC, until deactivated. NOTE: When required, retransmissions are explicitly scheduled on PDCCH(s). The dynamically allocated downlink reception overrides the configured downlink assignment in the same serving cell, if they overlap in time. Otherwise a downlink reception according to the configured downlink assignment is assumed, if activated. The UE may be configured with up to 8 active configured downlink assignments for a given BWP of a serving cell. When more than one is configured: - The network decides which of these configured downlink assignments are active at a time (including all of them); and - Each configured downlink assignment is activated separately using a DCI command and deactivation of configured downlink assignments is done using a DCI command, which can either deactivate a single configured downlink assignment or multiple configured downlink assignments jointly. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 10.2 |
5,994 | 5.2.2.4.13 Actions upon reception of SIB12 | Upon receiving SIB12, the UE shall: 1> if the UE has stored at least one segment of SIB12 and the value tag of SIB12 has changed since a previous segment was stored: 2> discard all stored segments; 1> store the segment; 1> if all segments have been received: 2> assemble SIB12-IEs from the received segments; 2> if sl-FreqInfoList/sl-FreqInfoListSizeExt is included in SIB12-IEs: 3> if configured to receive NR sidelink communication: 4> use the resource pool(s) indicated by sl-RxPool for NR sidelink communication reception, as specified in 5.8.7; 3> if configured to transmit NR sidelink communication: 4> use the resource pool(s) indicated by sl-TxPoolSelectedNormal, or sl-TxPoolExceptional for NR sidelink communication transmission, as specified in 5.8.8; 4> perform CBR measurement on the transmission resource pool(s) indicated by sl-TxPoolSelectedNormal or sl-TxPoolExceptional for NR sidelink communication transmission, as specified in 5.5.3.1; 4> use the synchronization configuration parameters for NR sidelink communication on frequencies included in sl-FreqInfoList/sl-FreqInfoListSizeExt, as specified in 5.8.5; 3> if configured to receive NR sidelink discovery: 4> use the resource pool(s) indicated by sl-DiscRxPool or sl-RxPool for NR sidelink discovery reception, as specified in 5.8.13.2; 3> if configured to transmit NR sidelink discovery: 4> if the UE is configured by upper layers to transmit NR sidelink L2 U2N relay discovery messages and sl-L2U2N-Relay is included in SIB12; or 4> if the UE is configured by upper layers to transmit NR sidelink L3 U2N relay discovery messages and sl-L3U2N-RelayDiscovery is included in SIB12; or 4> if the UE is configured by upper layers to transmit NR sidelink non-relay discovery messages and sl-NonRelayDiscovery is included in SIB12: 5> use the resource pool(s) indicated by sl-DiscTxPoolSelected, sl-TxPoolExceptional or sl-TxPoolSelectedNormal for NR sidelink discovery transmission, as specified in 5.8.13.3; 5> perform CBR measurement on the transmission resource pool(s) indicated by sl-TxPoolSelectedNormal, sl-DiscTxPoolSelected or sl-TxPoolExceptional for NR sidelink discovery transmission, as specified in 5.5.3.1; 5> use the synchronization configuration parameters for NR sidelink discovery on frequencies included in sl-FreqInfoList, as specified in 5.8.5; 2> if sl-RadioBearerConfigList or sl-RLC-BearerConfigList is included in sl-ConfigCommonNR: 3> perform sidelink DRB addition/modification/release as specified in 5.8.9.1a.1/5.8.9.1a.2; 3> if sl-RLC-BearerConfigListSizeExt is included in SIB12-IEs: 4> perform additional sidelink RLC bearer addition/modification/release as specified in 5.8.9.1a.5/5.8.9.1a.6; 2> if sl-MeasConfigCommon is included in sl-ConfigCommonNR: 3> store the NR sidelink measurement configuration; 2> if sl-DRX-ConfigCommonGC-BC is included in SIB12-IEs: 3> store the NR sidelink DRX configuration and configure lower layers to perform sidelink DRX operation for groupcast and broadcast as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]; 1> if the UE is acting as L2 U2N Remote UE: 2> if the sl-TimersAndConstantsRemoteUE is included in SIB12: 3> use values for timers T300, T301 and T319 as included in the sl-TimersAndConstantsRemoteUE received in SIB12; 2> else: 3> use values for timers T300, T301 and T319 as included in the ue-TimersAndConstants received in SIB1; The UE should discard any stored segments for SIB12 if the complete SIB12 has not been assembled within a period of 3 hours. The UE shall discard any stored segments for SIB12 upon cell (re-)selection. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.2.2.4.13 |
5,995 | 4.26 Support for Personal IoT Network service | The 5GS can support the Personal IoT Network (PIN) service (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]). The PIN enables the Personal IoT Network Elements (PINEs) to communicate with each other via PIN direct communication, PIN indirect communication or PIN-DN communication. For the PIN indirect communication and PIN-DN communication, a UE acting as a PIN Element with Gateway Capability (PEGC) enables the PINEs behind the PEGC to connect to the network and to communicate with other PINEs within the PIN or with the DN via the PDU session established for PIN. A PEGC may serve one or more PINs. The PEGC establishes only one PDU session for each PIN. The PEGC establishes different PDU sessions for different PINs based on different DNNs and S-NSSAIs. The PEGC may establish only one PDU session for multiple PINs if traffic differentiation for multiple PINs is not required in 5GS. NOTE 1: The PIN direct communication is out of the scope of 3GPP. The PIN, PEGC, and PINEs are managed by PIN Element with Management Capability (PEMC) and optionally the corresponding application function. Each PIN contains at least one PEGC and at least one PEMC. The PIN architecture is captured in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]. The 5GS supports the delivery of URSP rules which include the PIN ID to a PEGC registered to 5GS (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] and 3GPP TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [10]). The 5GS is enhanced to support the PDU session management for PIN to ensure the end-to-end QoS requirement. The end-to-end QoS requirement for each PINE over PIN indirect communication and over PIN-DN communication includes: a) the QoS requirement in the 3GPP access network; and b) the QoS requirement in the non-3GPP access network. The N3QAI is introduced to enable a PEGC to perform the QoS differentiation for the PINEs in the non-3GPP access network. If the UE supports receiving the N3QAI, the network may provide the N3QAI associated with the QoS flow during the PDU session establishment procedure as defined in subclause 6.4.1 or during the PDU session modification procedure as defined in subclause 6.4.2. NOTE 2: How the PEGC applies N3QAI is outside the scope of the present document. The non-3GPP delay budget refers to the delay budget between the PEGC and the PINE in the non-3GPP access network. If the UE supports providing the non-3GPP delay budget, the UE may provide the network with the non-3GPP delay budget for the one or more QoS flows associated with the PDU sessions for a PIN during the PDU session modification procedure as defined in subclause 6.4.2. The network takes into account the received non-3GPP delay budget to ensure the end-to-end QoS requirement of a PINE. NOTE 3: The support of a 5G-RG or a FN-RG acting as a PEGC is not specified in this release of specification. NOTE 4: The support of redundant PDU sessions does not apply for PIN. | 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.26 |
5,996 | 4.14.1 RAN Initiated QoS Flow Mobility | This procedure is used to transfer QoS Flows to and from Secondary RAN Node. During this procedure, the SMF and UPF are never re-allocated. The UPF referred in this clause 4.14.1 is the UPF which terminates N3 interface in the 5GC. The presence of IP connectivity between the UPF and the Master RAN node, as well as between the UPF and the Secondary RAN node is assumed. If QoS Flows for multiple PDU Sessions need to be transferred to or from Secondary RAN Node, the procedure shown in the Figure 4.14.1-1 below is repeated for each PDU Session. Figure 4.14.1-1: NG-RAN initiated QoS Flow mobility procedure 1. The Master RAN node sends a N2 QoS Flow mobility Indication (PDU Session ID, QFI(s), AN Tunnel Info, User Location Information) message to the AMF. AN Tunnel Info includes the new RAN tunnel endpoint for the QFI(s) for which the AN Tunnel Info shall be modified. The User Location Information shall include the serving cell's ID and if Dual Connectivity is activated for the UE, the PSCell ID. 2. AMF to SMF: Nsmf_PDUSession_UpdateSMContext reques (N2 QoS Flow mobility Indication message PDU Session ID). 3. The SMF sends an N4 Session Modification Request (PDU Session ID(s), QFI(s), AN Tunnel Info for downlink user plane) message to the UPF. 4. The UPF returns an N4 Session Modification Response (CN Tunnel Info for uplink traffic) message to the SMF after requested QFIs are switched. NOTE: Step 7 can occur any time after receipt of N4 Session Modification Response at the SMF. 5. SMF to AMF: Nsmf_PDUSession_UpdateSMContext response (N2 SM information (CN Tunnel Info for uplink traffic)) for QFIs of the PDU Session which have been switched successfully. If none of the requested QFIs have been switched successfully, the SMF shall send an N2 QoS Flow mobility Failure message. 6. In order to assist the reordering function in the Master RAN node and/or Secondary RAN node, for each affected N3 tunnel the UPF sends one or more "end marker" packets on the old tunnel immediately after switching the tunnel for the QFI. The UPF starts sending downlink packets to the Target NG-RAN. 7. The AMF relays message 5 to the Master RAN node. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.14.1 |
5,997 | 8.2.1.4.1B Enhanced Performance Requirement Type A - Single-Layer Spatial Multiplexing 2 Tx Antenna Port with TM4 interference model | The requirements are specified in Table 8.2.1.4.1B-2, with the addition of the parameters in Table 8.2.1.4.1B-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify the closed loop rank-one performance with wideband precoding with two transmit antennas when the PDSCH transmission in the serving cell is interfered by PDSCH of two dominant interfering cells applying transmission mode 4 interference model defined in clause B.5.3. In Table 8.2.1.4.1B-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.1.4.1B-1: Test Parameters for Single-Layer Spatial Multiplexing (FRC) with TM4 interference model Table 8.2.1.4.1B-2: Enhanced Performance Requirement Type A, Single-Layer Spatial Multiplexing (FRC) with TM4 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.1.4.1B |
5,998 | 9.9.3.36 UE security capability | The UE security capability information element is used by the network to indicate which security algorithms are supported by the UE in S1 mode, Iu mode and Gb mode. Security algorithms supported in S1 mode are supported both for NAS and for AS security. If the UE supports S101 mode, then these security algorithms are also supported for NAS security in S101 mode. The UE security capability information element is coded as shown in figure 9.9.3.36.1 and table 9.9.3.36.1. The UE security capability is a type 4 information element with a minimum length of 4 octets and a maximum length of 7 octets. Octets 5, 6, and 7 are optional. If octet 5 is included, then also octet 6 shall be included and octet 7 may be included. If a UE did not indicate support of any security algorithm for Gb mode, octet 7 shall not be included. If the UE did not indicate support of any security algorithm for Iu mode and Gb mode, octets 5, 6, and 7 shall not be included. If the UE did not indicate support of any security algorithm for Iu mode but indicated support of a security algorithm for Gb mode, octets 5, 6, and 7 shall be included. In this case octets 5 and 6 are filled with the value of zeroes. Figure 9.9.3.36.1: UE security capability information element Table 9.9.3.36.1: UE security capability information element | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.9.3.36 |
5,999 | 5.32 Support for ATSSS 5.32.1 General | The ATSSS feature is an optional feature that may be supported by the UE and the 5GC network. The ATSSS feature enables a multi-access PDU Connectivity Service, which can exchange PDUs between the UE and a data network by simultaneously using one 3GPP access network and one non-3GPP access network and two independent N3/N9 tunnels between the PSA and RAN/AN. The multi-access PDU Connectivity Service is realized by establishing a Multi-Access PDU (MA PDU) Session, i.e. a PDU Session that may have user-plane resources on two access networks. This assumes both 3GPP access and non-3GPP access are allowed for the S-NSSAI of the PDU Session. The UE may request a MA PDU Session when the UE is registered via both 3GPP and non-3GPP accesses, or when the UE is registered via one access only. After the establishment of a MA PDU Session, and when there are user-plane resources on both access networks, the UE applies network-provided policy (i.e. ATSSS rules) and considers local conditions (such as network interface availability, signal loss conditions, user preferences, etc.) for deciding how to distribute the uplink traffic across the two access networks. Similarly, the UPF anchor of the MA PDU Session applies network-provided policy (i.e. N4 rules) and feedback information received from the UE via the user-plane (such as access network Unavailability or Availability) for deciding how to distribute the downlink traffic across the two N3/N9 tunnels and the two access networks. When there are user-plane resources on only one access network, the UE applies the ATSSS rules and considers local conditions for triggering the establishment or activation of the user plane resources over another access. The type of a MA PDU Session may be one of the following types defined in clause 5.6.1: IPv4, IPv6, IPv4v6, and Ethernet. In this release of the specification, the Unstructured type is not supported. The clause 5.32.6.2.1, the clause 5.32.6.2.2 and the clause 5.32.6.3.1 below define what Steering Functionalities can be used for each supported type of a MA PDU Session. The handling of 3GPP PS Data Off feature for MA PDU Session is specified in clause 5.24. The ATSSS feature can be supported over any type of access network, including untrusted and trusted non-3GPP access networks (see clauses 4.2.8 and 5.5), wireline 5G access networks (see clause 4.2.8), etc. as long as a MA PDU Session can be established over this type of access network. In this Release of the specification, a MA PDU Session using IPv6 multi-homing (see clause 5.6.4.3) or UL Classifier (see clause 5.6.4.2) is not specified. In this Release of the specification, support for ATSSS assumes SMF Service Areas covering the whole PLMN or that a MA PDU Session is released over both accesses when the UE moves out of the SMF Service Area. A MA PDU Session does not support LADN. If the AMF receives a request to establish a MA PDU Session for a LADN DNN, the AMF shall reject the request. If the AMF receives a request to establish a PDU Session for a LADN DNN with "MA PDU Network-Upgrade Allowed" indication, the AMF shall not forward "MA PDU Network-Upgrade Allowed" indication to the SMF. If the UE, due to mobility, moves from being served by a source AMF supporting ATSSS to a target AMF not supporting ATSSS, the MA PDU Session is released as described in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. NOTE 1: Deployment of ATSSS that is homogeneous per PLMN, or network slice enables consistent behaviour. In the case of non-homogenous support of ATSSS in a PLMN/slice (i.e. some NFs in a PLMN/slice may not support ATSSS), MA PDU Sessions can be released due to UE mobility. A Multi-Access PDU Session may, for the 3GPP access and/or non-3GPP access, use user-plane resources of an associated PDN Connection in EPC (e.g. one 3GPP access path via EPC and one non-3GPP access path via 5GC or one 3GPP access path via 5GC and one non-3GPP access path via ePDG/EPC). Such use of ATSSS with EPS interworking may apply to Ethernet and IP-based PDU Session and PDN Connection types. NOTE 2: Co-existence with NBIFOM is not defined. It is assumed that NBIFOM and the multi-access connectivity described in this clause are not deployed in the same network. NOTE 3: To the MME and SGW this is a regular PDN Connection and the support for ATSSS is transparent to MME and SGW. For a MA PDU Session established for the Ethernet PDU Session type, if the UE has not indicated support for Ethernet PDN connection type or if the network does not support Ethernet PDN connection type, when the 3GPP access use user-plane resources of an associated PDN Connection, the following takes place: - The SMF+PGW-C considers that the Multi-Access PDU Session is still using the Ethernet PDU Session / PDN Connection type but in a restricted mode where EPS signalling can only refer to non-IP PDN Connection type. - MAR rules in the UPF are still used for distributing DL traffic between 3GPP access and non-3GPP access. - For traffic on 3GPP access, the SMF may update N4 rules and QoS rules/EPS bearer contexts on the UE to take into account that no QoS differentiation is possible over 3GPP access. Support of Multi-Access PDU Sessions using one leg associated with PDN Connection in EPC and one leg associated with PDU Session in 5GC is further defined in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The following clauses specify the functionality that enables ATSSS. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.32 |
6,000 | 6.3.1.2.2 PDU EAP message reliable transport procedure accepted by the UE | The UE shall create a PDU SESSION AUTHENTICATION COMPLETE message when the upper layers provide an EAP-response message responding to the received EAP-request message. The UE shall set the EAP message IE of the PDU SESSION AUTHENTICATION COMPLETE message to the EAP-response message. The UE shall transport the PDU SESSION 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 authentication and authorization procedure initiated by the DN is transparent to the 5GSM layer of the UE. Upon receipt of a PDU SESSION AUTHENTICATION COMPLETE message, the SMF shall stop timer T3590 and provides the EAP message received in the EAP message IE of the PDU SESSION AUTHENTICATION COMPLETE message to the DN or handles it locally. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.3.1.2.2 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.