Search is not available for this dataset
doc_id
int64 1
6.72k
β | Section
stringlengths 5
247
β | Content
stringlengths 501
147k
β | Source
stringclasses 456
values | Document Title
stringclasses 22
values | Working Group
stringclasses 21
values | Series Subject
stringclasses 9
values | Subclause
stringlengths 1
13
β |
|---|---|---|---|---|---|---|---|
6,201 | 28.3.2.2.5 Replacement field used in DNS-based Discovery of regulatory requirements | 28.3.2.2.5.1 General If the visited country mandates the selection of an N3IWF in this country, the NAPTR record(s) associated to the Visited Country FQDN shall be provisioned with the replacement field containing the identity of the PLMN(s) in the visited country which may be used for N3IWF selection. The replacement field shall take the form of an Operator Identifier based N3IWF FQDN as specified in clause 28.3.2.2.2. For countries with multiple MCC, the NAPTR records returned by the DNS may contain a different MCC than the MCC indicated in the Visited Country FQDN. As an example, the NAPTR records associated to the Visited Country FQDN for MCC 345, and for MNC 012, 013 and 014, are provisioned in the DNS as: n3iwf.5gc.mcc345.visited-country.pub.3gppnetwork.org ; IN NAPTR order pref. flag service regexp replacement IN NAPTR 100 999 "" "" n3iwf.5gc.mnc012.mcc345.pub.3gppnetwork.org IN NAPTR 100 999 "" "" n3iwf.5gc.mnc013.mcc345.pub.3gppnetwork.org IN NAPTR 100 999 "" "" n3iwf.5gc.mnc014.mcc345.pub.3gppnetwork.org 28.3.2.2.5.2 Replacement field used in DNS-based Discovery of regulatory requirements for emergency services via N3IWF The NAPTR record(s) associated to the Visited Country Emergency N3IWF FQDN shall be provisioned with the replacement field containing the identity of the PLMN(s) in the visited country supporting emergency services in non-3GPP access via N3IWF. The replacement field shall take the form of an operator identifier based N3IWF FQDN as specified clause 28.3.2.2.2, with the addition of the label "sos" before the labels "n3iwf.5gc". As an example, the NAPTR records associated to the Visited Country Emergency N3IWF FQDN for MCC 345, and for MNC 012, 013 and 014, are provisioned in the DNS as: sos.n3iwf.5gc.mcc345.visited-country.pub.3gppnetwork.org ; IN NAPTR order pref. flag service regexp replacement IN NAPTR 100 999 "" "" sos.n3iwf.5gc.mnc012.mcc345.pub.3gppnetwork.org IN NAPTR 100 999 "" "" sos.n3iwf.5gc.mnc013.mcc345.pub.3gppnetwork.org IN NAPTR 100 999 "" "" sos.n3iwf.5gc.mnc014.mcc345.pub.3gppnetwork.org 28.3.2.2.5.3 Replacement field used in DNS-based Discovery of N3IWF supporting Onboarding If the visited country mandates the selection of an N3IWF supporting onboarding in this country, the NAPTR record(s) associated to the Visited Country FQDN for N3IWF supporting Onboarding shall be provisioned with the replacement field containing the Operator Identifier based Onboarding FQDN for N3IWF located in the visited country. When UE sends the DNS query to the DNS server containing the Visited Country Onboarding FQDN for N3IWF (see clause 28.3.2.2.4.3), the DNS response should contain the Operator Identifier based Onboarding FQDN for N3IWF containing the identity of the PLMN(s) in the visited country which may be used for N3IWF selection in the visited country supporting Untrusted non-3GPP access for UE Onboarding via N3IWF. If the UE has selected an PLMN for onboarding, the UE sends DNS query to the DNS server containing the Operator Identifier based Onboarding FQDN for N3IWF to query the identifier of the N3IWF supporting Onboarding, the DNS response should contain the identifier of the N3IWF supporting the onboarding in the PLMN identified by the PLMN ID. The replacement field shall take the form of Operator Identifier based Onboarding FQDN for N3IWF as below: "onboarding.n3iwf.5gc.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org" For countries with multiple MCC, the NAPTR records returned by the DNS may contain a different MCC than the MCC indicated in the Visited Country FQDN for N3IWF supporting Onboarding. As an example, the NAPTR records associated to the Visited Country FQDN for N3IWF supporting Onboarding for MCC 345, and for MNC 012, 013 and 014, are provisioned in the DNS as: onboarding.n3iwf.5gc.mcc345.visited-country.pub.3gppnetwork.org ; IN NAPTR order pref. flag service regexp replacement IN NAPTR 100 999 "" "" onboarding.n3iwf.5gc.mnc012.mcc345.pub.3gppnetwork.org IN NAPTR 100 999 "" "" onboarding.n3iwf.5gc.mnc013.mcc345.pub.3gppnetwork.org IN NAPTR 100 999 "" "" onboarding.n3iwf.5gc.mnc014.mcc345.pub.3gppnetwork.org | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.3.2.2.5 |
6,202 | 5.28.3.2 Transfer of port or user plane node management information | Port management information is transferred transparently via 5GS between TSN AF or TSCTSF and DS-TT or NW-TT, respectively, inside a Port Management Information Container (PMIC). User plane node management information is transferred transparently via 5GS between TSN AF or TSCTSF and NW-TT inside a user plane node Management Information Container (UMIC). The transfer of port or user plane node management information is as follows: - To convey port management information from DS-TT or NW-TT to TSN AF or TSCTSF: - DS-TT provides a PMIC and the DS-TT port MAC address (if available) to the UE, which includes the PMIC as an optional Information Element of an N1 SM container and triggers the UE requested PDU Session Establishment procedure or PDU Session Modification procedure to forward the PMIC to the SMF. SMF forwards the PMIC and the port number of the related DS-TT port to TSN AF or TSCTSF as described in clauses 4.3.2.2 and 4.3.3.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]; - NW-TT provides PMIC(s) and/or UMIC to the UPF, which may trigger the N4 Session Level Reporting Procedure to forward the PMIC(s) and/or UMIC to SMF. UPF selects an N4 session corresponding to any of the N4 sessions for this NW-TT. SMF in turn forwards the PMIC(s) and the port number(s) of the related NW-TT port(s), or the UMIC, to TSN AF or TSCTSF as described in clause 4.16.5.1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. - NW-TT may provide PMIC(s) and/or UMIC to the UPF, which may trigger UPF Event Exposure Notification to forward the PMIC(s) and/or UMIC to TSN AF or TSCTSF. UPF directly reports TSC management information event via Nupf_EventExposure_Notify service operation as described in clause 5.2.26.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. NOTE 1: There has to be at least one established PDU session for DS-TT port before the UPF can report PMIC/UMIC information towards the TSN AF or TSCTSF. - To convey port management information from TSN AF or TSCTSF to DS-TT: - TSN AF or TSCTSF provides a PMIC, DS-TT port MAC address or UE IP address (applicable for TSCTSF only) reported for a PDU Session (i.e. MAC address of the DS-TT port or IP address related to the PDU session) and the port number of the DS-TT port to manage to the PCF by using the AF Session level Procedure, which forwards the information to SMF based on the MAC or IP address using the PCF initiated SM Policy Association Modification procedure as described in clause 4.16.5.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. SMF determines that the port number relates to a DS-TT port and based on this forwards the PMIC to DS-TT using the network requested PDU Session Modification procedure as described in clause 4.3.3.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. - To convey port or user plane node management information from TSN AF or TSCTSF to NW-TT: - TSN AF or TSCTSF selects a PCF-AF session corresponding to any of the DS-TT MAC or IP addresses (applicable for TSCTSF only) for the related PDU sessions of this bridge or router and provides a PMIC(s) and the related NW-TT port number(s) and/or UMIC to the PCF. The PCF uses the PCF initiated SM Policy Association Modification procedure to forward the information received from TSN AF or TSCTSF to SMF as described in clause 4.16.5.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. SMF determines that the included information needs to be delivered to the NW-TT either by determining that the port number(s) relate(s) to a NW-TT port(s) or based on the presence of UMIC, and forwards the container(s) and/or related port number(s) to NW-TT using the N4 Session Modification procedure described in clause 4.4.1.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.28.3.2 |
6,203 | 6.2.14 Handling of Serving PLMN rate control | Serving PLMN rate control is applicable only for PDU sessions established for control plane CIoT 5GS optimization. Serving PLMN rate control protect its AMF from the load generated by user data over control plane. The SMF can inform the UE of any local serving PLMN rate control during the PDU session establishment procedure (see subclause 6.4.1) or the PDU session modification procedure (see subclause 6.4.2). If serving PLMN rate control is enabled, the SMF shall start the serving PLMN rate control for the PDU session when the first control plane user data is received over the PDU session.The UE shall limit the rate at which it generates uplink control plane user data to comply with the serving PLMN policy provided by the network. The indicated rate in a NAS procedure applies to the PDU session the NAS procedure corresponds to, and the indicated rate is valid until the PDU session is released. Any Serving PLMN rate control information provided by the network to the UE is only applicable for the PLMN which provided this information. This serving PLMN rate control information shall be discarded when the UE successfully registers to another PLMN. NOTE: The serving PLMN can discard or delay control plane user data that exceed the limit provided for Serving PLMN rate control. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.2.14 |
6,204 | 8.5 Identity management | The 5G system shall provide a mechanism for an operator to allow access from a UE using a temporary identifier that hides its subscriber identity. The 5G system shall provide a mechanism for an operator to allow access from a UE connected in an indirect network connection using a temporary identifier that hides its subscriber identity. The HPLMN shall be able to associate a temporary identifier to a UE's subscriber identity. The 5G system shall be able to protect subscriber identity and other user identifying information from passive attacks. Subject to regional or national regulatory requirements, the 5G system shall be able to protect subscriber identity and other user identifying information from active attacks. The 5G system shall be able to allow the equipment identifier to be collected by legitimate entity regardless of UE's user interface, when required. The 5G system shall be able to support identification of subscriptions independently of identification of equipment. The 5G system shall support a secure mechanism to collect system information while ensuring end-user and application privacy (e.g. application level information is not to be related to an individual user identity or subscriber identity and UE information is not to be related to an individual subscriber identity). Subject to regional or national regulatory requirements, the 5G system shall be able to provide the 5G positioning services while ensuring the protection of the privacy of the UE's user or owner, including the respect of his consent to the positioning services. NOTE 1: this includes the ability for the 5G system to provide the positioning services on demand without having to track continuously the position of the involved UE. NOTE 2: the respect of the user's consent to some positioning services could abide by different rules in case of emergency (for example, rules that would also receive consent from the user, but well before the emergency occurs). For a private network using 5G technology, the 5G system shall support network access using identities, credentials, and authentication methods provided and managed by a third-party and supported by 3GPP. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 8.5 |
6,205 | 2.10.2.1.2 Mapping in the UE | When a UE moves from 5GS to an E-UTRAN, the UE needs to map the 5G-GUTI to a GUTI. The mapping of the 5G-GUTI to a GUTI shall be done as follows: 5GS <MCC> maps to E-UTRAN <MCC> 5GS <MNC> maps to E-UTRAN <MNC> 5GS <AMF Region ID> and 5GS <AMF Set ID> map to E-UTRAN <MME Group ID> and part of E-UTRAN <MME Code> as follows: - 8 bits of the 5GS <AMF Region ID> starting at bit 7 and down to bit 0 are mapped into bit 15 and down to bit 8 of the E-UTRAN <MME Group ID>; - 8 bits of the 5GS <AMF Set ID> starting at bit 9 and down to bit 2 are mapped into bit 7 and down to bit 0 of the E-UTRAN <MME Group ID>; - 2 bits of the 5GS <AMF Set ID> starting at bit 1 and down to bit 0 are mapped into bit 7 and down to bit 6 of the E-UTRAN <MME Code>; 5GS <AMF Pointer> maps to part of E-UTRAN <MME Code> as follows: - 6 bits of the 5GS <AMF Pointer> starting at bit 5 and down to bit 0 are mapped into bit 5 and down to bit 0 of the E-UTRAN <MME Code>. 5GS <5G-TMSI> maps to to E-UTRAN <M-TMSI> | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 2.10.2.1.2 |
6,206 | 16.6.2 Mobility 16.6.2.1 General | The same principles as described in 9.2 apply to SNPN except for what is described below. UEs operating in SNPN access mode only (re)select cells within the selected/registered SNPN or within equivalent SNPNs and a cell can only be considered as suitable if the PLMN and NID broadcast by the cell matches the selected/registered SNPN or an equivalent SNPN. In addition, manual selection of SNPN(s) is supported, for which HRNN(s) can be optionally provided. The roaming and access restrictions applicable to SNPN are described in clause 9.4. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.6.2 |
6,207 | 5.7.4.4 Relaxed measurement criterion for a stationary (e)RedCap UE | The relaxed measurement criterion for a stationary UE is met when: - (SS-RSRPRefStationaryConnected β SS-RSRP) < SSearchDeltaP-StationaryConnected, Where: - SS-RSRP = current L3 RSRP measurement of the PCell based on SSB (dB). - SS-RSRPRefStationaryConnected = reference SS-RSRP value of the PCell (dB), set as follows: - at the end of RRC reconfiguration procedure as specified in 5.3.5.3, when rrm-MeasRelaxationReportingConfig is included in the RRCReconfiguration message; or - after MAC successfully completes a Random Access procedure after applying a reconfigurationWithSync in spCellConfig while stationary criterion is configured; or - if (SS-RSRP β SS-RSRPRefStationaryConnected) > 0; or - if the relaxed measurement criterion has not been met for TSearchDeltaP-StationaryConnected: - UE shall set the value of SS-RSRPRefStationaryConnected to the current SS-RSRP value of the serving cell. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.4.4 |
6,208 | D.6.2 UE policy section management list | The purpose of the UE policy section management list information element is to transfer from the PCF to the UE a list of instructions to be performed at the UE for management of UE policy section stored at the UE. The UE policy section management list information element is coded as shown in figure D.6.2.1, figure D.6.2.2, figure D.6.2.3, figure D.6.2.4, figure D.6.2.5, figure D.6.2.6, figure D.6.2.7 and table D.6.2.1. The UE policy section management list information element has a minimum length of 12 octets and a maximum length of 65534 octets. Figure D.6.2.1: UE policy section management list information element Figure D.6.2.2: UE policy section management list contents Figure D.6.2.3: UE policy section management sublist Figure D.6.2.4: UE policy section management sublist contents Figure D.6.2.5: Instruction Figure D.6.2.6: UE policy section contents Figure D.6.2.7: UE policy part Table D.6.2.1: UE policy section management list information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | D.6.2 |
6,209 | 5.3.5.9a MUSIM gap configuration | The UE shall: 1> if musim-GapConfig is set to setup: 2> for each musim-GapId included in the received musim-GapToReleaseList: 3> release the periodic MUSIM gap configuration associated with the musim-GapId; 2> for each MUSIM-Gap included in the received musim-GapToAddModList: 3> setup periodic MUSIM gap configuration indicated by the MUSIM-Gap in accordance with the received musim-GapRepetitionAndOffset (providing musim-GapRepetition and Offset value for the following condition) i.e. the first subframe of each periodic MUSIM gap occurs at an SFN and subframe of the NR PCell meeting the following condition: SFN mod T = FLOOR(Offset/10); subframe = Offset mod 10; with T = musim-GapRepetition/10; 3> set the MUSIM gap priority configuration indicated by musim-GapPriorityToAddModList, if configured, for each periodic MUSIM gap; 3> set the musim-GapKeep, if all collided MUSIM gaps are configured to be kept; NOTE: If network does not retain the relative priorities among MUSIM gaps, UE behaviour is not specified. 2> if musim-AperiodicGap is included: 3> setup aperiodic MUSIM gap configuration indicated by the musim-AperiodicGap in accordance with the received musim-Starting-SFN-AndSubframe, i.e. the first subframe of aperiodic MUSIM gap occurs at an SFN and subframe of the NR PCell meeting the following condition: SFN = starting-SFN; subframe = startingSubframe; 1> else if musim-GapConfig is set to release: 2> release the MUSIM gap configuration. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.9a |
6,210 | 5.31.6 Reliable Data Service | The Reliable Data Service (RDS) may be used between the UE and NEF or UPF when using a PDU Session of PDU Type 'Unstructured'. The service provides a mechanism for the NEF or UPF to determine if the data was successfully delivered to the UE and for the UE to determine if the data was successfully delivered to the NEF or UPF. When a requested acknowledgement is not received, the Reliable Data Service retransmits the packet. The service is enabled or disabled based on DNN and NSSAI Configuration per SLA. When the service is enabled, a protocol is used between the end-points of the unstructured PDU Session. The protocol uses a packet header to identify if the packet requires no acknowledgement, requires an acknowledgement, or is an acknowledgment and to allow detection and elimination of duplicate PDUs at the receiving endpoint. RDS supports both single and multiple applications within the UE. Port Numbers in the header are used to identify the application on the originator and to identify the application on the receiver. The UE, NEF and the UPF may support reservation of the source and destination port numbers for their use and subsequent release of the reserved port numbers. Reliable Data Service protocol (as defined in TS 24.250[ Protocol for Reliable Data Service; Stage 3 ] [80]) also enables applications to query their peer entities to determine which port numbers are reserved and which are available for use at any given time. The header is configured based on Reliable Data Service Configuration information which is obtained in the NIDD configuration, MT NIDD, and MO NIDD procedures with the AF as specified in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. During NIDD Configuration, the AF may indicate which serialization formats it supports for mobile originated and mobile terminated traffic in the Reliable Data Server Configuration. When port numbers are reserved by the UE, the serialization format that will be used by the application may be indicated to the NEF. When port numbers are reserved by the NEF, the serialization format that will be used by the application may be indicated to the UE. If the receiver does not support the indicated serialization format, it rejects the port number reservation request and the sender may re-attempt to reserve the port number with a different serialization format. If, during NIDD Configuration, the AF indicated that it supports multiple serialization formats, the NEF determines the serialization format that it will indicate to the UE based on local policies and previous negotiations with the UE (e.g. the NEF may indicate the same serialization format that was indicated by the UE or avoid indicating a serialization format that was previously rejected by the UE). When serialization formats are configured for reserved port numbers, the NEF stores the serialization formats as part of the Reliable Data Service Configuration and provides the updated Reliable Data Service Configuration to the AF. NOTE: Whether the UE Application or AF supports a given serialization format is outside the scope of 3GPP specifications. The UE indicates its capability of supporting RDS in the Protocol Configuration Options (PCO) and the SMF negotiates RDS support with the NEF or UPF. If the NEF or UPF supports and accepts RDS then the SMF indicates to the UE, in the PCO, that the RDS shall be used if enabled in the DNN and NSSAI configuration. In order to prevent situations where an RDS instance needs to interface to both the user and control plane, RDS may only be used with PDU Sessions for which the "Control Plane CIoT 5GS Optimisation" indication is set or with PDU sessions using the Control Plane CIoT 5GS Optimisation when the AMF does not move the PDU session to the user plane. Reliable Data Service protocol is defined in TS 24.250[ Protocol for Reliable Data Service; Stage 3 ] [80]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.31.6 |
6,211 | 5.9.4.2 Initiation | An MBS capable UE in RRC_CONNECTED may initiate the procedure in several cases including upon successful connection establishment/resume, upon entering or leaving the broadcast service area, upon MBS broadcast session start or stop, upon change of interest, upon change of priority between MBS broadcast reception and unicast/multicast reception, upon change to a PCell providing SIB21 (i.e. where the SIB1 scheduling information contains SIB21), upon receiving SIB20 of an SCell via dedicated signalling, upon handover, and upon RRC connection re-establishment, upon change to a PCell providing nonServingCellMII in SIB1, upon starting or stopping reception of MBS broadcast service on a non-serving cell, upon change of CFR information or subcarrier spacing for MBS broadcast reception on a non-serving cell. If the UE does not have the CFR information and subcarrier spacing for MBS broadcast reception on a non-serving cell at the time it sends the MBS Interest Indication, the UE sends an MBS Interest Indication after it has acquired those information from the non-serving cell. Upon initiating the procedure, the UE shall: 1> if SIB21 is provided by the PCell; or 1> if nonServingCellMII is provided in SIB1 by the PCell: 2> ensure having a valid version of SIB21 for the PCell, if present; 2> if the UE did not transmit MBS Interest Indication since last entering RRC_CONNECTED state; or 2> if since the last time the UE transmitted an MBS Interest Indication, the UE connected to a PCell, neither providing SIB21 nor including nonServingCellMII in SIB1: 3> if the set of MBS broadcast frequencies of interest, determined in accordance with 5.9.4.3, is not empty: 4> set the contents of MBS Interest Indication according to 5.9.4.5 and initiate transmission of the MBSInterestIndication message; 2> else: 3> if the set of MBS broadcast frequencies of interest, determined in accordance with 5.9.4.3, is different from mbs-FreqList included in the last transmission of the MBS Interest Indication; or 3> if the set of MBS broadcast frequencies of interest for MBS broadcast reception on non-serving cell, determined in accordance with 5.9.4.3, is different from the list of MBS broadcast frequencies of interest for MBS broadcast reception on non-serving cell included in the last transmission of the MBS Interest Indication; or 3> if any of the subcarrier spacing and the CFR information for MBS broadcast reception on non-serving cell has changed since the last transmission of the MBS Interest Indication; or 3> if the subcarrier spacing and the CFR information for MBS broadcast reception on non-serving cell have been acquired from the non-serving cell which were not reported in the previous MBS Interest Indication; or 3> if the prioritisation of reception of all indicated MBS broadcast frequencies compared to reception of any of the established unicast bearers and multicast MRBs has changed since the last transmission of the MBS Interest Indication: 4> set the contents of MBS Interest Indication according to 5.9.4.5 and initiate transmission of the MBSInterestIndication message; NOTE: The UE may send MBS Interest Indication even when it is able to receive the MBS services it is interested in, i.e. to avoid that the network allocates a configuration inhibiting MBS broadcast reception. 3> else if SIB20 is provided for the PCell or for the SCell: 4> if since the last time the UE transmitted the MBS Interest Indication, the UE connected to a PCell not providing SIB20 and the UE was not provided with SIB20 for an SCell; or 4> if the set of MBS broadcast services of interest determined in accordance with 5.9.4.4 is different from mbs-ServiceList included in the last transmission of the MBS Interest Indication: 5> set the contents of MBS Interest Indication according to 5.9.4.5 and initiate the transmission of MBSInterestIndication message. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.9.4.2 |
6,212 | β NCR-PeriodicityAndOffset | The IE NCR-PeriodicityAndOffset is used to indicate the periodicity (in slot or ms) and offset (in slot) for periodic forwarding resource and semi-persistent forwarding resource. NCR-PeriodicityAndOffset information element -- ASN1START -- TAG-NCR-PERIODICITYANDOFFSET-START NCR-PeriodicityAndOffset-r18 ::= CHOICE { slot NCR-SlotPeriodicityAndSlotOffset-r18, ms NCR-MsPeriodicityAndSlotOffset-r18 } NCR-SlotPeriodicityAndSlotOffset-r18 ::= CHOICE { sl1 NULL, sl2 INTEGER(0..1), sl4 INTEGER(0..3), sl5 INTEGER(0..4), sl8 INTEGER(0..7), sl10 INTEGER(0..9), sl16 INTEGER(0..15), sl20 INTEGER(0..19), sl32 INTEGER(0..31), sl40 INTEGER(0..39), sl64 INTEGER(0..63), sl80 INTEGER(0..79), sl128 INTEGER(0..127), sl160 INTEGER(0..159), sl256 INTEGER(0..255), sl320 INTEGER(0..319), sl512 INTEGER(0..511), sl640 INTEGER(0..639), sl1024 INTEGER(0..1023), sl1280 INTEGER(0..1279), sl2560 INTEGER(0..2559), sl5120 INTEGER(0..5119), sl10240 INTEGER(0..10239), ... } NCR-MsPeriodicityAndSlotOffset-r18 ::= CHOICE { ms1 INTEGER(0..15), ms2 INTEGER(0..31), ms4 INTEGER(0..63), ms5 INTEGER(0..79), ms8 INTEGER(0..127), ms10 INTEGER(0..159), ms16 INTEGER(0..255), ms20 INTEGER(0..319), ms32 INTEGER(0..511), ms40 INTEGER(0..639), ms64 INTEGER(0..1023), ms80 INTEGER(0..1279), ms128 INTEGER(0..2047), ms160 INTEGER(0..2559), ms256 INTEGER(0..4095), ms320 INTEGER(0..5119), ms512 INTEGER(0..8191), ms640 INTEGER(0..10239), ms1024 INTEGER(0..16383), ms1280 INTEGER(0..20479), ms2560 INTEGER(0..40959), ms5120 INTEGER(0..81919), ms10240 INTEGER(0..163839), ... } -- TAG-NCR-PERIODICITYANDOFFSET-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
6,213 | 8.1 QoS aspects | In EN-DC, the E-UTRAN QoS framework defined in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [2] applies: - An S1-U bearer is established between the EPC and the SN for SN terminated bearers; - An X2-U bearer is established between the MN and the SN for split bearers, MN terminated SCG bearers and SN terminated MCG bearers; - MN terminated and SN terminated bearers may have either MCG or SCG radio resources or both, MCG and SCG radio resources, established; In MR-DC with 5GC: - The NG-RAN QoS framework defined in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [3] applies; - QoS flows belonging to the same PDU session may be mapped to different bearer types (see clause 4.2.2) and as a result there may be two different SDAP entities for the same PDU session: one at the MN and another one at the SN, in which case the MN decides which QoS flows are assigned to the SDAP entity in the SN. If the SN decides that its SDAP entity cannot host a given QoS flow any longer, the SN informs the MN and the MN cannot reject the request. If the MN decides that its SDAP entity can host a given QoS flow which has already been relocated to SN, the MN informs the SN; - The MN or SN node that hosts the SDAP entity for a given QoS flow decides how to map the QoS flow to DRBs; - If the SDAP entity for a given QoS flow is hosted by the MN and the MN decides that SCG resources are to be configured it provides to the SN - DRB QoS flow level QoS parameters, which the SN may reject, and - QoS flow to DRB mapping information and the respective per QoS flow information; - If the SDAP entity for a given QoS flow is hosted by the SN and the SN configures MCG resources, based on offered MCG resource information from the MN, the SN provides to the MN - DRB QoS flow level QoS parameters, which the MN may reject, and - QoS flow to DRB mapping information and the respective per QoS flow information. - If the SDAP entity for a given QoS flow is hosted by the SN, the MN provides sufficient QoS related information to enable the SN to configure appropriate SCG resources and to request the configuration of appropriate MCG resources. The MN may offer MCG resources to the SN and may indicate for GBR QoS flows the amount offered to the SN on a per QoS flow level. Otherwise, the SN can only use SCG resources for the concerned QoS flow. The SN may request the MN to release QoS flows from the SDAP entity hosted by the SN that the MN cannot reject. The MN may also offer MCG resources per PDU Session for all DRBs to which non-GBR QoS flows contained in the PDU Session are mapped. - MN decides the DL PDU session AMBR and UL PDU session AMBR limits to be assigned to the SN, and indicates these to the SN: - The PDCP entity at the SN applies the received DL PDU session AMBR limi t to the set of all bearers for which the SN hosts PDCP for the UE; - The MAC entity at the SN applies the received UL PDU session AMBR limit to the scheduled uplink radio traffic at the SN for the UE. - The MN can decide to reallocate one or more QoS flows from the MN to the SN. In such case, the SN decides which DRBs the offloaded QoS flows are mapped to. It is possible to avoid/ minimise loss and ensure in-order delivery when reallocating all QoS flows mapped to a given DRB in the MN by keeping the QoS flows mapped to the same DRB in the SN. To achieve this, the SN should behave similar to what is specified for the target NG-RAN node upon handover, see TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] clause 9.2.3.2.2 [3]. The corresponding behaviour applies when QoS flows are re-allocated from the SN to the MN. - The MN decides the DL UE Slice MBR and UL UE Slice MBR limits to be assigned to the SN, and indicates these to the SN: - The PDCP entity at the SN applies the received DL UE Slice MBR limit to the set of all bearers for which the SN hosts PDCP for the concerned Slice, as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [11]; - The MAC entity at the SN applies the received UL UE Slice MBR limit to the scheduled uplink radio traffic at the SN for the concerned Slice, as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [11]. In all MR-DC cases: - The MN decides the DL UE AMBR and UL UE AMBR limits to be assigned to the SN, and indicates these to the SN: - The PDCP entity at the SN applies the received DL UE AMBR limit to the set of all bearers for which the SN hosts PDCP for the UE; - The MAC entity at the SN applies the received UL UE AMBR limit to the scheduled uplink radio traffic at the SN for the UE. To support PDU sessions mapped to different bearer types, MR-DC with 5GC provides the possibility for the MN to request the 5GC: - For some PDU sessions of a UE: Direct the User Plane traffic of the whole PDU session either to the MN or to the SN. In that case, there is a single NG-U tunnel termination at the NG-RAN for such PDU session. - The MN may request to change this assignment during the life time of the PDU session. - For some other PDU sessions of a UE: Direct the User Plane traffic of a subset of the QoS flows of the PDU session to the SN (respectively MN) while the rest of the QoS flows of the PDU session is directed to the MN (respectively SN). In that case, there are two NG-U tunnel terminations at the NG-RAN for such PDU session. - The MN may request to change this assignment during the life time of the PDU session. To support notification control indication for GBR QoS flows along the QoS framework specified in 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [3] for MR-DC with 5GC, SN and MN may mutually indicate whenever QoS requirements for GBR QoS flows cannot be fulfilled anymore or can be fulfilled again. When indicating that GBR QoS flows cannot be fulfilled anymore, SN or MN may additionally indicate the reference to the QoS Parameter Set which it can currently fulfil. | 3GPP TS 37.340 | Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 | RAN2 | 3GPP Series : 37 , Multiple radio access technology aspects | 8.1 |
6,214 | 9.11.3.1 5GMM capability | The purpose of the 5GMM capability information element is to provide the network with information concerning aspects of the UE related to the 5GCN or interworking with the EPS. The contents might affect the manner in which the network handles the operation of the UE. The 5GMM capability information element is coded as shown in figure 9.11.3.1.1 and table 9.11.3.1.1. The 5GMM capability is a type 4 information element with a minimum length of 3 octets and a maximum length of 15 octets. Figure 9.11.3.1.1: 5GMM capability information element Table 9.11.3.1.1: 5GMM capability 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.1 |
6,215 | 6.2 IP address allocation 6.2.1 General | The UE can configure an IPv4 address during the establishment of a default EPS bearer context. The UE can obtain an IPv4 address or an IPv6 prefix or both via an IETF-based IP address allocation mechanism once the default bearer is established. The following IETF-based IP address/prefix allocation methods are specified for EPS (the corresponding procedures are specified in 3GPP TS 29.061[ Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) ] [16]): a) /64 IPv6 default prefix allocation via IPv6 stateless address autoconfiguration. Optionally, allocation of additional IPv6 prefix(es) with length /64 or shorter via stateful DHCPv6 Prefix Delegation (see IETF RFC 3633 [24A]); b) IPv4 address allocation and IPv4 parameter configuration via DHCPv4; c) IPv6 parameter configuration via stateless DHCPv6. NOTE: From the perspective of the UE, the procedure used to allocate a static IP address via NAS signalling is the same as the procedure used to allocate a dynamic IP address specified in clause 6.2.2. Upon deactivation of the default bearer of a PDN connection, the UE shall locally release any IPv4 address or IPv6 prefix allocated to the UE for the corresponding PDN connection. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.2 |
6,216 | 10.14.3 PDU Session Split at UPF (RAN initiated QoS flows offloading from MN to SN) | When some QoS flows are offloaded from the MN to the SN, the MN may decide to split the PDU session served by the MN into more than one NG-U tunnels. The MN sends the SN Addition/Modification Request message including UPF UL TEID address used at the MN. Later on, if the MN receives a new UL TEID in the PDU Session Resource Modify Confirm message, the MN may provide the new UL TEID to the SN. Figure 10.14.3-1: PDU Session Split at UPF during RAN initiated PDU session resource modify (QoS flows offloading from MN to SN) 1-2. If the MN decides to split a PDU session, it uses the SN Addition procedure or the MN-initiated SN Modification procedure, including current UPF UL NG-U tunnel used at the MN. If in-order delivery is required for some QoS flows, an UL forwarding tunnel may be setup for the PDU session at this stage. NOTE 1: In case the MN offloads some QoS flows to the SN within a PDU session already split between the MN and the SN, the MN initiated SN Modification procedure is used. 3-6d. If in-order delivery is required, the SN buffers the first packets received from the UE for a certain QoS flow until it receives an GTP-U end marker packet over the UL forwarding tunnel indicating that the MN has delivered all UL packets from the source side to UPF for that QoS flow. Then the SN starts delivering UL packets to UPF for that QoS flow using the UPF UL TEID address used at the MN received at step 1. 7-8. The MN uses the PDU Session Resource Modify Indication message to inform 5GC that the PDU session is split into two tunnels and indicate which QoS flows are associated with which DL tunnel. The 5GC triggers the sending of DL End Marker packets without QFI tag at step 7a and confirms with the PDU Session Resource Modify Confirm message and allocates corresponding uplink tunnels. After receiving the End Marker packet(s) from UPF at step 7a, the MN determines that the End Marker packets only work on the offloaded QoS flows, and may stop delivering and discard DL packets of the offloaded QoS flows, and the MN shall continue transmiting DL packets for the not offloaded QoS flows, if any. 7a./7b. After receiving the DL end marker from 5GC at step 7a, the MN may generate at step 7b DL End Marker packets without QFI tag towards the SN. 9-10. If the MN receives a new UL TEID in the PDU Session Resource Modify Confirm message for itself, the MN will use it to deliver UL packets to UPF. If the MN receives a new UL TEID for the SN, then the MN-initiated SN Modification procedure (i.e., step 9 and step 10) is used to provide the new UL TEID to the SN and then the SN switches to use the new UL TEID to deliver UL packets. 10.14.4 PDU Session Split at UPF (RAN initiates QoS flows offloading from SN to MN) When some QoS flows are offloaded from the SN to the MN, the MN may decide to split the PDU session served by the SN into more than one NG-U tunnels. If the MN requests to offload, the MN sends the SN Modification Request message to the SN. In case the SN requests to offload, the SN sends the SN Modification Required message to the MN. Figure 10.14.4-1: PDU Session Split at UPF during RAN initiated PDU session resource modify (QoS flows offloading from SN to MN) 1a-1c. When the MN requests to offload some QoS flows from the SN to the MN for a PDU session, it sends the SN Modification Request message. If in-order delivery is required for some of the QoS flows, an UL forwarding tunnel may be setup for the PDU session at this stage and the MN provides the UL forwarding tunnel address information in the Xn-U Address Indication message. 2a-2b. When the SN requests to offload some QoS flows to the MN for a PDU session, the SN sends the SN Modification Required message. If in-order delivery is required for some of the QoS flows, an UL forwarding tunnel may be setup for the PDU session at this stage and the MN provides the UL forwarding tunnel address information in the SN Modification Confirm message. 3-6d. If in-order delivery is required, the MN buffers the first packets received from the UE for a certain QoS flow until it receives an GTP-U end marker packet over the UL forwarding tunnel indicating that the SN has delivered all UL packets from the source side to UPF for that QoS flow. 7-8. The MN uses the PDU Session Resource Modify Indication message to inform 5GC that the PDU session is split into two tunnels and indicate which QoS flows are associated with which DL tunnel. The 5GC triggers the sending of DL End Marker packets without QFI tag at step 7a and confirms with the PDU Session Resource Modify Confirm message and allocates corresponding uplink tunnels. After receiving the End Marker packet(s) from UPF at step 7a, the SN determines that the End Marker packets only work on the offloaded QoS flows, and may stop delivering and discard DL packets of the offloaded QoS flows, and the SN shall continue transmiting DL packets for the not offloaded QoS flows, if any. 7a./7b. After receiving the DL end marker from 5GC at step 7a, the SN may generate at step 7b DL End Marker packets without QFI tag towards the MN. 9-10. If the MN receives a new UL TEID in the PDU Session Resource Modify Confirm message for itself, the MN will use it to deliver UL packets to UPF. If the MN receives a new UL TEID for the SN, then the MN-initiated SN Modification procedure (i.e., the step 9 and step 10) is used to provide the new UL TEID to the SN and then the SN switches to use the new UL TEID to deliver UL packets. | 3GPP TS 37.340 | Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 | RAN2 | 3GPP Series : 37 , Multiple radio access technology aspects | 10.14.3 |
6,217 | 5.5.2.2.2 UE initiated detach procedure completion for EPS services only | When the DETACH REQUEST message is received by the network, the network shall send a DETACH ACCEPT message to the UE, if the Detach type IE does not indicate "switch off". Otherwise, the procedure is completed when the network receives the DETACH REQUEST message. The network and the UE shall deactivate the EPS bearer context(s), if any, for this UE locally without peer-to-peer signalling between the UE and the MME. The UE is marked as inactive in the network for EPS services. The network shall enter the state EMM-DEREGISTERED. The UE, when receiving the DETACH ACCEPT message, shall stop timer T3421. Furthermore, if the UE is operating in PS mode of operation, or is operating in CS/PS mode of operation and supports S1 mode only then: - If the detach procedure was performed due to disabling of EPS services, then the UE shall enter the EMM-NULL state. - Otherwise, the UE shall enter the EMM-DEREGISTERED state. The UE operating in CS/PS mode 1 or CS/PS mode 2 of operation, and supporting A/Gb mode or Iu mode, shall further set the update status to U2 NOT UPDATED, disable the E-UTRA capability (see clause 4.5) and attempt to select GERAN or UTRAN access technology. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.2.2.2 |
6,218 | 5.2.6.37 Nnef_ECSAddress service 5.2.6.37.1 General | Service description: The ECS Address service in the V-NEF provides functions for ECS Address Configuration Information provision for a group of UE or any UE from AF and for subscribing and retrieving ECS Address Configuration Information and providing ECS Address Configuration Information to the V-SMF to support. For related procedures see clauses 6.5.2.6.2 and 6.5.2.6.3 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74]. This procedure is defined only for the support of HR-SBO, i.e. where the ECS Address is not associated with the subscription of an user of the PLMN operating the V-NEF and V-SMF. NOTE: There is thus no conflict with the usage of External Parameter Provisioning procedure to configure ECS Address Configuration Information for users of the PLMN operating the NEF and SMF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.37 |
6,219 | 4.7.1.8a Establishment of the PS signalling connection (Iu mode only) | In order to route the NAS message to an appropriate SGSN, the MS NAS provides the lower layers with the routing parameter according to the following rules: a) if the TIN indicates "P-TMSI" or "RAT-related TMSI", and the MS holds a valid P-TMSI, the MS NAS shall provide the lower layers with the P-TMSI; b) if the TIN indicates "GUTI" and the MS holds a valid GUTI allocated by an MME, the MS NAS shall provide the lower layers with the P-TMSI mapped from the GUTI (see 3GPP TS 23.003[ Numbering, addressing and identification ] [10]); c) if the TIN is not available and the MS holds a valid P-TMSI, the MS NAS shall provide the lower layers with the P-TMSI; or d) if the TIN is not available and the MS holds a valid GUTI allocated by an MME, but no valid P-TMSI, the MS NAS shall provide the lower layers with the P-TMSI mapped from the GUTI (see 3GPP TS 23.003[ Numbering, addressing and identification ] [10]). When an ATTACH REQUEST message, or a ROUTING AREA UPDATE REQUEST message after a routing area change, is sent to establish a PS signalling connection, the MS NAS also provides the lower layers with the DCN-ID according to the following rules: a) if a DCN-ID for the PLMN code of the selected PLMN is available in the MS, this DCN-ID the MS NAS shall provide this DCN-ID to the lower layers; or b) if no DCN-ID for the PLMN code of the selected PLMN is available but a Default_DCN_ID value is available in the MS, as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] or in USIM file NASCONFIG as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112], the Default_DCN_ID value MS NAS shall provide the Default_DCN_ID value to the lower layers. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.1.8a |
6,220 | 5.8.3.2 Initiation | A UE capable of NR sidelink communication or NR sidelink discovery or NR sidelink U2N relay operation or NR sidelink U2U relay operation or NR sidelink positioning that is in RRC_CONNECTED may initiate the procedure to indicate it is (interested in) receiving or transmitting NR sidelink communication or NR sidelink discovery or NR sidelink U2N relay operation or NR sidelink U2U relay operation or SL-PRS transmission/reception in several cases including upon successful connection establishment or resuming, upon change of interest, upon changing QoS profile(s), upon receiving UECapabilityInformationSidelink from the associated peer UE, upon RLC mode information updated from the associated peer UE or upon change to a PCell providing SIB12 including sl-ConfigCommonNR, or upon change to a PCell providing SIB23 including sl-PosConfigCommonNR. A UE capable of NR sidelink communication may initiate the procedure to request assignment of dedicated sidelink DRB configuration and transmission resources for NR sidelink communication transmission. A UE capable of NR sidelink communication may initiate the procedure to report to the network that a sidelink radio link failure, sidelink RRC reconfiguration failure or sidelink carrier failure has been declared. A UE capable of NR sidelink discovery may initiate the procedure to request assignment of dedicated resources for NR sidelink discovery transmission or NR sidelink discovery reception. A UE capable of U2N relay operation may initiate the procedure to report/update parameters for acting as U2N Relay UE or U2N Remote UE (including L2 Remote UE's source L2 ID). A UE capable of U2U relay operation may initiate the procedure to report/update parameters for acting as U2U Relay UE or U2U Remote UE. A UE capable of NR sidelink positioning may initiate the procedure to request it is interested or no longer interested in either transmitting SL-PRS or receiving sidelink control information for SL-PRS. A UE capable of NR sidelink operation that is in RRC_CONNECTED may initiate the procedure to report the sidelink DRX configuration received from the associated peer UE for NR sidelink unicast reception, upon accepting the sidelink DRX configuration from the associated peer UE. A UE capable of NR sidelink communication that is configured with sl-ScheduledConfig and is performing sidelink unicast transmission may initiate the procedure to report the sidelink DRX assistance information or the sidelink DRX configuration reject information received from the associated peer UE, upon receiving either of them from the associated peer UE. A UE capable of NR sidelink communication that is configured with sl-ScheduledConfig and is performing sidelink groupcast transmission may initiate the procedure to report the sidelink DRX on/off indication for the associated Destination Layer-2 ID. A UE capable of NR sidelink operation that is in RRC_CONNECTED may initiate the procedure to report the Destination Layer-2 ID and QoS profile(s) associated with its interested service(s) that sidelink DRX is applied, for NR sidelink groupcast or broadcast reception. Upon initiating this procedure, the UE shall: 1> if SIB12 including sl-ConfigCommonNR is provided by the PCell: 2> ensure having a valid version of SIB12 for the PCell; 2> if configured by upper layers to receive NR sidelink communication on the frequency included in sl-FreqInfoList/sl-FreqInfoListSizeExt in SIB12 of the PCell: 3> if the UE did not transmit a SidelinkUEInformationNR message since last entering RRC_CONNECTED state; or 3> if since the last time the UE transmitted a SidelinkUEInformationNR message the UE connected to a PCell not providing SIB12 including sl-ConfigCommonNR; or 3> if the last transmission of the SidelinkUEInformationNR message did not include sl-RxInterestedFreqList; or if the frequency configured by upper layers to receive NR sidelink communication on has changed since the last transmission of the SidelinkUEInformationNR message: 4> initiate transmission of the SidelinkUEInformationNR message to indicate the NR sidelink communication reception frequency of interest in accordance with 5.8.3.3; 2> else: 3> if the last transmission of the SidelinkUEInformationNR message included sl-RxInterestedFreqList: 4> initiate transmission of the SidelinkUEInformationNR message to indicate it is no longer interested in NR sidelink communication reception in accordance with 5.8.3.3; 2> if configured by upper layers to transmit non-relay NR sidelink communication on the frequency included in sl-FreqInfoList/sl-FreqInfoListSizeExt in SIB12 of the PCell; or 2> if configured by upper layer to transmit NR sidelink L3 U2U relay communication on the frequency included in sl-FreqInfoList in SIB12 of the PCell including [FFS gNB capability indication]: 3> if the UE did not transmit a SidelinkUEInformationNR message since last entering RRC_CONNECTED state; or 3> if since the last time the UE transmitted a SidelinkUEInformationNR message the UE connected to a PCell not providing SIB12 including sl-ConfigCommonNR; or 3> if the last transmission of the SidelinkUEInformationNR message did not include sl-TxResourceReqList; or if the information carried by the sl-TxResourceReqList has changed since the last transmission of the SidelinkUEInformationNR message: 4> initiate transmission of the SidelinkUEInformationNR message to indicate the NR sidelink communication transmission resources required by the UE in accordance with 5.8.3.3; 2> else: 3> if the last transmission of the SidelinkUEInformationNR message included sl-TxResourceReqList: 4> initiate transmission of the SidelinkUEInformationNR message to indicate it no longer requires NR sidelink communication transmission resources in accordance with 5.8.3.3; 2> if configured by upper layer to receive NR sidelink non-relay discovery messages on the frequency included in sl-FreqInfoList in SIB12 of the PCell including sl-NonRelayDiscovery: 3> if the UE did not transmit a SidelinkUEInformationNR message since last entering RRC_CONNECTED state; or 3> if since the last time the UE transmitted a SidelinkUEInformationNR message the UE connected to a PCell not providing SIB12 including sl-ConfigCommonNR or connected to a PCell providing SIB12 but not including sl-NonRelayDiscovery; or 3> if the last transmission of the SidelinkUEInformationNR message did not include sl-RxInterestedFreqListDisc; or if the frequency configured by upper layers to receive NR sidelink non-relay discovery messages on has changed since the last transmission of the SidelinkUEInformationNR message: 4> initiate transmission of the SidelinkUEInformationNR message to indicate the NR sidelink discovery reception frequency of interest in accordance with 5.8.3.3; 2> else: 3> if the last transmission of the SidelinkUEInformationNR message included sl-RxInterestedFreqListDisc: 4> initiate transmission of the SidelinkUEInformationNR message to indicate it is no longer interested in NR sidelink non-relay discovery messages reception in accordance with 5.8.3.3; 2> if configured by upper layer to receive NR sidelink L2 U2N relay discovery messages on the frequency included in sl-FreqInfoList in SIB12 of the PCell including sl-L2U2N-Relay; or if configured by upper layer to receive NR sidelink L3 U2N relay discovery messages on the frequency included in sl-FreqInfoList in SIB12 of the PCell including sl-L3U2N-RelayDiscovery; 2> or if configured by upper layer to receive NR sidelink U2U relay discovery messages on the frequency included in sl-FreqInfoList in SIB12 of the PCell including [FFS gNB capability indication]: 3> if the UE did not transmit a SidelinkUEInformationNR message since last entering RRC_CONNECTED state; or 3> if since the last time the UE transmitted a SidelinkUEInformationNR message the UE connected to a PCell not providing SIB12 including sl-ConfigCommonNR; or connected to a PCell providing SIB12 but not including sl-L2U2N-Relay in case of L2 U2N relay operation; or connected to a PCell providing SIB12 but not including sl-L3U2N-RelayDiscovery in case of L3 U2N relay operation; or 3> if since the last time the UE transmitted a SidelinkUEInformationNR message the UE connected to a PCell providing SIB12 but not including [FFS gNB capability indication] in case of U2U relay operation; or 3> if the last transmission of the SidelinkUEInformationNR message did not include sl-RxInterestedFreqListDisc; or if the frequency configured by upper layers to receive NR sidelink discovery messages on has changed since the last transmission of the SidelinkUEInformationNR message: 4> if the UE is capable of U2N Relay UE, and if SIB12 includes sl-RelayUE-ConfigCommon; or 4> if the UE is selecting a U2N Relay UE / has a selected U2N Relay UE, and if SIB12 includes sl-RemoteUE-ConfigCommon; or 4> if the UE is capable of U2U Relay UE, and if SIB12 includes sl-RelayUE-ConfigCommonU2U; or 4> if the UE is selecting a U2U Relay UE / has a selected U2U Relay UE, and if SIB12 includes sl-RemoteUE-ConfigCommonU2U: 5> initiate transmission of the SidelinkUEInformationNR message to indicate the NR relay sidelink discovery reception frequency of interest in accordance with 5.8.3.3; 2> else: 3> if the last transmission of the SidelinkUEInformationNR message included sl-RxInterestedFreqListDisc: 4> initiate transmission of the SidelinkUEInformationNR message to indicate it is no longer interested in NR relay sidelink discovery messages reception in accordance with 5.8.3.3; 2> if configured by upper layer to transmit NR sidelink non-relay discovery messages on the frequency included in sl-FreqInfoList in SIB12 of the PCell including sl-NonRelayDiscovery: 3> if the UE did not transmit a SidelinkUEInformationNR message since last entering RRC_CONNECTED state; or 3> if since the last time the UE transmitted a SidelinkUEInformationNR message the UE connected to a PCell not providing SIB12 including sl-ConfigCommonNR or connected to a PCell providing SIB12 but not including sl-NonRelayDiscovery; or 3> if the last transmission of the SidelinkUEInformationNR message did not include sl-TxResourceReqListDisc; or if the information carried by the sl-TxResourceReqListDisc has changed since the last transmission of the SidelinkUEInformationNR message: 4> initiate transmission of the SidelinkUEInformationNR message to indicate the NR sidelink non-relay discovery messages resources required by the UE in accordance with 5.8.3.3; 2> else: 3> if the last transmission of the SidelinkUEInformationNR message included sl-TxResourceReqListDisc: 4> initiate transmission of the SidelinkUEInformationNR message to indicate it no longer requires NR sidelink non-relay discovery messages resources in accordance with 5.8.3.3; 2> if configured by upper layer to transmit NR sidelink L2 U2N relay discovery messages on the frequency included in sl-FreqInfoList in SIB12 of the PCell including sl-L2U2N-Relay; or if configured by upper layer to transmit NR sidelink L3 U2N relay discovery messages on the frequency included in sl-FreqInfoList in SIB12 of the PCell including sl-L3U2N-RelayDiscovery; or 2> if configured by upper layer to transmit NR sidelink U2U relay discovery messages on the frequency included in sl-FreqInfoList in SIB12 of the PCell including [FFS gNB capability indication]: 3> if the UE did not transmit a SidelinkUEInformationNR message since last entering RRC_CONNECTED state; or 3> if since the last time the UE transmitted a SidelinkUEInformationNR message the UE connected to a PCell not providing SIB12 including sl-ConfigCommonNR; or connected to a PCell providing SIB12 but not including sl-L2U2N-Relay in case of L2 U2N relay operation; or connected to a PCell providing SIB12 but not including sl-L3U2N-RelayDiscovery in case of L3 U2N relay operation; or 3> if since the last time the UE transmitted a SidelinkUEInformationNR message the UE connected to a PCell providing SIB12 but not including [FFS gNB capability indication] in case of U2U relay operation; or 3> if the last transmission of the SidelinkUEInformationNR message did not include sl-TxResourceReqListDisc; or if the information carried by the sl-TxResourceReqListDisc has changed since the last transmission of the SidelinkUEInformationNR message: 4> if the UE is capable of U2N Relay UE, and if SIB12 includes sl-RelayUE-ConfigCommon, and if the U2N Relay UE threshold conditions as specified in 5.8.14.2 are met; or 4> if the UE is selecting a U2N Relay UE / has a selected U2N Relay UE/ configured with measurement object associated to L2 U2N Relay UEs, and if SIB12 includes sl-RemoteUE-ConfigCommon, and if the U2N Remote UE threshold conditions as specified in 5.8.15.2 are met; or 4> if the UE is capable of U2U Relay UE, and if SIB12 includes sl-RelayUE-ConfigCommonU2U, and if the U2U Relay UE threshold conditions as specified in 5.8.16.2 are met; or 4> if the UE is selecting a U2U Relay UE / has a selected U2U Relay UE, and if SIB12 includes sl-RemoteUE-ConfigCommonU2U, and if the U2N Remote UE threshold conditions as specified in 5.8.17.2 are met: 5> initiate transmission of the SidelinkUEInformationNR message to indicate the NR sidelink relay discovery messages resources required by the UE in accordance with 5.8.3.3; 2> else: 3> if the last transmission of the SidelinkUEInformationNR message included sl-TxResourceReqListDisc: 4> initiate transmission of the SidelinkUEInformationNR message to indicate it no longer requires NR sidelink relay discovery messages resources in accordance with 5.8.3.3; 2> if configured by upper layer to transmit NR sidelink L2 U2N relay communication on the frequency included in sl-FreqInfoList in SIB12 of the PCell including sl-L2U2N-Relay; or if configured by upper layer to transmit NR sidelink L3 U2N relay communication on the frequency included in sl-FreqInfoList in SIB12 of the PCell including sl-L3U2N-RelayDiscovery; or 2> if configured by upper layer to transmit NR sidelink L2 U2U relay communication on the frequency included in sl-FreqInfoList in SIB12 of the PCell including [FFS gNB capability indication]: 3> if the UE did not transmit a SidelinkUEInformationNR message since last entering RRC_CONNECTED state; or 3> if since the last time the UE transmitted a SidelinkUEInformationNR message the UE connected to a PCell not providing SIB12 including sl-ConfigCommonNR; or connected to a PCell providing SIB12 but not including sl-L2U2N-Relay in case of L2 U2N relay operation; or connected to a PCell providing SIB12 but not including sl-L3U2N-RelayDiscovery in case of L3 U2N relay operation; or 3> if since the last time the UE transmitted a SidelinkUEInformationNR message the UE connected to a PCell providing SIB12 but not including [FFS gNB capability indication] in case of L2 U2U relay operation; or 3> if the last transmission of the SidelinkUEInformationNR message did not include sl-TxResourceReqL2U2N-Relay; or if the information carried by the sl-TxResourceReqL2U2N-Relay has changed since the last transmission of the SidelinkUEInformationNR message; or if the last transmission of the SidelinkUEInformationNR message did not include sl-TxResourceReqL3U2N-Relay; or if the information carried by the sl-TxResourceReqL3U2N-Relay has changed since the last transmission of the SidelinkUEInformationNR message; or 3> if the last transmission of the SidelinkUEInformationNR message did not include sl-TxResourceReqL2U2U-Relay; or if the information carried by the sl-TxResourceReqL2U2U-Relay has changed since the last transmission of the SidelinkUEInformationNR message; or 3> if configured by upper layers not to transmit either NR sidelink L2 U2N relay communication or NR sidelink L3 U2N relay communication, and if the last transmission of the SidelinkUEInformationNR message includes both sl-TxResourceReqL2U2N-Relay and sl-TxResourceReqL3U2N-Relay: 4> if the UE is capable of U2N Relay UE, and if SIB12 includes sl-RelayUE-ConfigCommon, and if the U2N Relay UE threshold conditions as specified in 5.8.14.2 are met; or 4> if the UE is selecting a U2N Relay UE / has a selected U2N Relay UE, and if SIB12 includes sl-RemoteUE-ConfigCommon, and if the U2N Remote UE threshold conditions as specified in 5.8.15.2 are met; or 4> if the UE is capable of L2 U2U Relay UE, and if SIB12 includes sl-RelayUE-ConfigCommonU2U, and if the U2U Relay UE threshold conditions as specified in 5.8.16.2 are met; or 4> if the UE is selecting a L2 U2U Relay UE / has a selected U2U Relay UE, and if SIB12 includes sl-RemoteUE-ConfigCommonU2U, and if the U2N Remote UE threshold conditions as specified in 5.8.17.2 are met: 5> initiate transmission of the SidelinkUEInformationNR message to indicate the NR sidelink relay communication transmission resources required by the UE in accordance with 5.8.3.3; 2> else: 3> if the last transmission of the SidelinkUEInformationNR message included sl-TxResourceReqL2U2N-Relay or sl-TxResourceReqL3U2N-Relay: 4> initiate transmission of the SidelinkUEInformationNR message to indicate it no longer requires NR sidelink relay communication transmission resources in accordance with 5.8.3.3; 2> if configured by upper layers to perform NR sidelink reception on the frequency included in sl-FreqInfoList/sl-FreqInfoListSizeExt in SIB12 of the PCell and if sl-DRX-ConfigCommonGC-BC is included in SIB12-IEs: 3> if the UE received a sidelink DRX configuration in the RRCReconfigurationSidelink message for NR sidelink unicast reception from the associated peer UE and the UE accepted the sidelink DRX configuration: 4> if the UE did not transmit a SidelinkUEInformationNR message since last entering RRC_CONNECTED state; or 4> if since the last time the UE transmitted a SidelinkUEInformationNR message the UE connected to a PCell not providing SIB12 including sl-DRX-ConfigCommonGC-BC; or 4> if the last transmission of the SidelinkUEInformationNR message did not include sl-RxDRX-ReportList; or if the information carried by sl-RxDRX-ReportList has changed since the last transmission of the SidelinkUEInformationNR message: 5> initiate transmission of the SidelinkUEInformationNR message to report the sidelink DRX configuration in accordance with 5.8.3.3; 3> else: 4> if the last transmission of the SidelinkUEInformationNR message included sl-RxDRX-ReportList: 5> initiate transmission of the SidelinkUEInformationNR message to indicate the sidelink DRX configuration is no longer used in accordance with 5.8.3.3; 3> if the UE is performing NR sidelink groupcast or broadcast reception and is interested in a service that sidelink DRX is applied: 4> if the UE did not transmit a SidelinkUEInformationNR message since last entering RRC_CONNECTED state; or 4> if since the last time the UE transmitted a SidelinkUEInformationNR message the UE connected to a PCell not providing SIB12 including sl-DRX-ConfigCommonGC-BC; or 4> if the last transmission of the SidelinkUEInformationNR message did not include sl-RxInterestedGC-BC-DestList; or if the information carried by sl-RxInterestedGC-BC-DestList has changed since the last transmission of the SidelinkUEInformationNR message: 5> initiate transmission of the SidelinkUEInformationNR message to report the Destination Layer-2 ID and QoS profile(s) associated with the service(s) in accordance with 5.8.3.3; 3> else: 4> if the last transmission of the SidelinkUEInformationNR message included sl-RxInterestedGC-BC-DestList: 5> initiate transmission of the SidelinkUEInformationNR message to indicate it is no longer interested in the service that sidelink DRX is applied in accordance with 5.8.3.3; 2> if configured by upper layers to perform NR sidelink transmission on the frequency included in sl-FreqInfoList in SIB12 of the PCell and if sl-DRX-ConfigCommonGC-BC is included in SIB12-IEs and if the UE is configured with sl-ScheduledConfig: 3> if the UE received a sidelink DRX assistance information or a sidelink DRX configuration reject information from the associated peer UE for NR sidelink unicast transmission: 4> if the UE did not transmit a SidelinkUEInformationNR message since last entering RRC_CONNECTED state; or 4> if since the last time the UE transmitted a SidelinkUEInformationNR message the UE connected to a PCell not providing SIB12 including sl-DRX-ConfigCommonGC-BC; or 4> if the last transmission of the SidelinkUEInformationNR message did not include sl-DRX-InfoFromRxList, sl-FailureList or sl-CarrierFailureList; or if the information carried by sl-DRX-InfoFromRxList, sl-FailureList or sl-CarrierFailureList has changed since the last transmission of the SidelinkUEInformationNR message: 5> initiate transmission of the SidelinkUEInformationNR message to report the sidelink DRX assistance information or the sidelink DRX configuration reject information in accordance with 5.8.3.3; NOTE: After including the SL-DRX reject information in sl-FailureList in the last transmission of the SidelinkUEInformationNR message, it is up to UE implementation to consider another sidelink DRX rejection of a new SL DRX configuration from the same associated peer UE as "change" of sl-FailureList. 3> if the UE is performing NR sidelink groupcast transmission: 4> if the UE did not transmit a SidelinkUEInformationNR message since last entering RRC_CONNECTED state; or 4> if since the last time the UE transmitted a SidelinkUEInformationNR message the UE connected to a PCell not providing SIB12 including sl-DRX-ConfigCommonGC-BC; or 4> if the last transmission of the SidelinkUEInformationNR message did not include sl-DRX-Indication; or if the information carried by sl-DRX-Indication has changed since the last transmission of the SidelinkUEInformationNR message: 5> initiate transmission of the SidelinkUEInformationNR message to report sidelink DRX on/off indication for the corresponding destination in accordance with 5.8.3.3; 1> if SIB23 including sl-PosConfigCommonNR is provided by the PCell: 2> if configured to receive sidelink control information for SL-PRS on the frequency included in sl-FreqInfoList in SIB23 of the PCell: 3> if the UE did not transmit a SidelinkUEInformationNR message since last entering RRC_CONNECTED state; or 3> if since the last time the UE transmitted a SidelinkUEInformationNR message the UE connected to a PCell not providing SIB23 including sl-PosConfigCommonNR; or 3> if the last transmission of the SidelinkUEInformationNR message did not include sl-PosRxInterestedFreqList; or if the frequency configured to receive sidelink control information for SL-PRS has changed since the last transmission of the SidelinkUEInformationNR message: 4> initiate transmission of the SidelinkUEInformationNR message to indicate the frequency of interest for SL-PRS transmission in accordance with 5.8.3.3 and to request configured grant; 2> else: 3> if the last transmission of the SidelinkUEInformationNR message included sl-PosRxInterestedFreqList: 4> initiate transmission of the SidelinkUEInformationNR message to indicate it is no longer interested in SL-PRS reception in accordance with 5.8.3.3; 2> if configured to transmit SL-PRS on the frequency included in sl-FreqInfoList in SIB23 of the PCell: 3> if the UE did not transmit a SidelinkUEInformationNR message since last entering RRC_CONNECTED state; or 3> if since the last time the UE transmitted a SidelinkUEInformationNR message the UE connected to a PCell not providing SIB23 including sl-PosConfigCommonNR; or 3> if the last transmission of the SidelinkUEInformationNR message did not include sl-PosTxResourceReqList; or if the information carried by the sl-PosTxResourceReqList has changed since the last transmission of the SidelinkUEInformationNR message: 4> initiate transmission of the SidelinkUEInformationNR message to indicate the NR sidelink positioning transmission resources required by the UE in accordance with 5.8.3.3; 2> else: 3> if the last transmission of the SidelinkUEInformationNR message included sl-PosTxResourceReqList: 4> initiate transmission of the SidelinkUEInformationNR message to indicate it no longer requires NR sidelink positioning transmission resources in accordance with 5.8.3.3; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.3.2 |
6,221 | 4.7.1.2a.5 Optional establishment of integrity protection in the user plane | If an MS supports integrity protection of user plane data, then the MS shall indicate in the MS network capability IE to the network that it supports integrity protection of user plane data when it sends an ATTACH REQUEST message or a ROUTING AREA UPDATE REQUEST message. If the network supports integrity protection of the user plane data, then the network shall indicate in the ATTACH ACCEPT message or the ROUTING AREA UPDATE ACCEPT message to the MS that integrity protection of user plane data shall be used. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.1.2a.5 |
6,222 | 10.5.4.12 Congestion level | The purpose of the congestion level information element is to describe the congestion status of the call. The congestion level information element is coded as shown in figure 10.5.98/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.124/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The congestion level is a type 1 information element. Figure 10.5.98/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Congestion level information element Table 10.5.124/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Congestion level information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.4.12 |
6,223 | β BandCombinationListSL-Discovery | The IE BandCombinationListSL-Discovery contains a list of NR Sidelink discovery band combinations. BandCombinationListSidelinkSL-Discovery information element -- ASN1START -- TAG-BANDCOMBINATIONLISTSLDISCOVERY-START BandCombinationListSL-Discovery-r17 ::= SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandParametersSidelinkDiscovery-r17 BandParametersSidelinkDiscovery-r17 ::= SEQUENCE { sl-CrossCarrierScheduling-r17 ENUMERATED {supported} OPTIONAL, --R1 32-4: Transmitting NR sidelink mode 2 with partial sensing sl-TransmissionMode2-PartialSensing-r17 SEQUENCE { harq-TxProcessModeTwoSidelink-r17 ENUMERATED {n8, n16}, scs-CP-PatternTxSidelinkModeTwo-r17 CHOICE { fr1-r17 SEQUENCE { scs-15kHz-r17 BIT STRING (SIZE (16)) OPTIONAL, scs-30kHz-r17 BIT STRING (SIZE (16)) OPTIONAL, scs-60kHz-r17 BIT STRING (SIZE (16)) OPTIONAL }, fr2-r17 SEQUENCE { scs-60kHz-r17 BIT STRING (SIZE (16)) OPTIONAL, scs-120kHz-r17 BIT STRING (SIZE (16)) OPTIONAL } } OPTIONAL, extendedCP-Mode2PartialSensing-r17 ENUMERATED {supported} OPTIONAL, dl-openLoopPC-Sidelink-r17 ENUMERATED {supported} OPTIONAL } OPTIONAL, --R1 32-5a-1: Transmitting Inter-UE coordination scheme 1 in NR sidelink mode 2 tx-IUC-Scheme1-Mode2Sidelink-r17 ENUMERATED {supported} OPTIONAL } -- TAG-BANDCOMBINATIONLISTSLDISCOVERY-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
6,224 | 9.9.4.9 PDN address | The PDN address information element can assign an IPv4 address to the UE associated with a packet data network and provide the UE with an interface identifier to be used to build the IPv6 link local address. The PDN address information element is coded as shown in figure 9.9.4.9.1 and table 9.9.4.9.1. The PDN address is a type 4 information element with minimum length of 7 octets and a maximum length of 15 octets. Figure 9.9.4.9.1: PDN address information element Table 9.9.4.9.1: PDN address 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.9 |
6,225 | 6.6.4.4 Abnormal cases in the UE | The following abnormal case can be identified: a) T3396 is running The UE shall not send an ESM DATA TRANSPORT message unless - the UE is a UE configured to use AC11 β 15 in selected PLMN; or - the ESM DATA TRANSPORT message is used for an exception data reporting and the UE is allowed to use exception data reporting (see the ExceptionDataReportingAllowed leaf of the NAS configuration MO in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or the USIM file EFNASCONFIG in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]). The ESM DATA TRANSPORT message can be sent, if still necessary, when timer T3396 expires or is stopped. b) Transmission failure of the ESM DATA TRANSPORT message indication from lower layers If lower layers indicate a TAI change and the current TAI is not in the TAI list, the transport of user data via the control plane procedure shall be aborted and re-initiated after successfully performing a tracking area updating procedure if the control plane CIoT EPS optimisation is still used and the user data exists. The "signalling active" flag shall be set in the TRACKING AREA UPDATE REQUEST message. If lower layers indicate a TAI change, but the current TAI is still part of the TAI list, or the TAI has not changed, the transport of user data via the control plane procedure shall be re-initiated immediately if the user data still exists by including the ESM DATA TRANSPORT message in a CONTROL PLANE SERVICE REQUEST message. NOTE: How the ESM sublayer handles the retransmission of user data via the control plane is up to the UE implementation. c) NAS MAC calculation indication from lower layers If lower layers indicate to calculate an NAS MAC, the UE shall calculate an NAS MAC as specified in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19] and then provide the calculated NAS MAC and 5 least significant bits of the uplink NAS COUNT used to calculate the NAS MAC to lower layers (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]). The UE shall increase the uplink NAS COUNT by one after the calculation of the NAS MAC. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.6.4.4 |
6,226 | 6.46 Satellite access 6.46.2 General | A 5G system with satellite access shall support different configurations where the radio access network is either a satellite NG-RAN or a non-3GPP satellite access network, or both. A UE supporting satellite access shall be able to provide or assist in providing its location to the 5G network. A 5G system with satellite access shall be able to determine a UE's location in order to provide service (e.g. route traffic, support emergency calls) in accordance with the governing national or regional regulatory requirements applicable to that UE. NOTE: This is also applicable for UE using only satellite access. The determination of a UEβs location can be based on 3GPP and/or non-3GPP positioning technologies subject to operatorβs policies. A 5G system with satellite access shall be able to support low power MIoT type of communications. Subject to the regulatory requirements and operatorβs policy, a 5G system with satellite access shall be able to provide services to an authorized UE independently of the UEβs GNSS capability. Subject to regulatory requirements and operatorβs policies, a 5G system with satellite access shall be able to support collection of information on usage statistics and location of the UEs that are connected to the satellite. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.46 |
6,227 | 4.1.1.2.2 GPRS MS operating in mode A or B in a network that operates in mode II | If the network operates in mode II, a GPRS MS that operates in mode A or B and wishes to be or is simultaneously IMSI attached for GPRS and non-GPRS services, shall use the MM specific procedures listed in subclauses 4.3 and 4.4 and the GMM specific procedures listed in subclauses 4.7.3, 4.7.4 and 4.7.5. The applicability of periodic location updating is further specified in subclause 4.4.2 and the periodic routing area updating is specified in subclause 4.7.2.2. If the GPRS MS, which operates in mode A or B, wishes to be IMSI attached for GPRS and "SMS-only service"or is simultaneously IMSI attached for GPRS and non-GPRS services in order to obtain GPRS services and "SMS-only service", then the GPRS MS shall first complete the GMM specific procedure before performing the MM specific procedures. If this GPRS MS receives in the ATTACH ACCEPT or ROUTING AREA UPDATE ACCEPT message the Additional network feature support IE indicating "SMS via GPRS supported", then the GPRS MS shall not perform the MM specific procedure until a new ATTACH ACCEPT or ROUTING AREA UPDATE ACCEPT message indicating "SMS via GPRS not supported" or the GPRS MS does not wish to be IMSI attached only for GPRS and "SMS-only service". If the authentication procedure is performed by MM and the authentication is rejected by the network (i.e upon receive of AUTHENTICATION REJECT), the MS shall in addition set the GPRS update status to GU3 ROAMING NOT ALLOWED and shall, if available, delete the P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number stored. The SIM/USIM shall be considered as invalid for GPRS and non-GPRS services until switching off or the SIM/USIM is removed. The MS shall abort any GMM procedure and shall enter state GMM-DEREGISTERED. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EPS update status, GUTI, last visited registered TAI, TAI list and KSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the EPS authentication is not accepted by the network. If the PS or CS domain is barred because of domain specific access control, a GPRS MS operating in mode A or B in a network that operates in mode II shall use the MM specific procedures or GMM specific procedures, respectively, in the domain which is unbarred. If the MS detects that a domain changes from barred to unbarred, it shall behave as specified in subclauses 4.3.4.4, 4.4.4.9, 4.5.1.2, 4.7.3.1.5, 4.7.4.1.4, 4.7.5.1.5, and 4.7.13.5. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.1.1.2.2 |
6,228 | 4.3.1.3.2 Successful outgoing handovers per handover cause | This measurement provides the number of successful outgoing handovers per handover cause and LTE target cell specific. CC. Receipt of a RRC message RRCConnectionReconfigurationComplete sent from the UE to the target (=source) eNB, indicating a successful outgoing intra-eNB handover (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]), or receipt at the source eNB of UE CONTEXT RELEASE [10] over the X2 from the target eNB following a successful inter-eNB handover, or if handover is performed via S1, receipt of UE CONTEXT RELEASE COMMAND[9] at the source eNB following a successful inter-eNB handover. Each RRCConnectionReconfigurationComplete, X2AP UE CONTEXT RELEASE message or S1AP UE CONTEXT RELEASE COMMAND message received is added to the relevant per handover cause measurement, the possible causes are included in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9] . In case of CA, this succesful handover is only added to same the neighbour cell relation that the corresponding attempted handover is counted at (i.e., the same neighbour cell relation that the measurement defined in subcluse 4.3.1.3.1 is counted at). The sum of all supported per cause measurements shall equal the total number of outgoing intra-RAT handover events. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first. Each measurement is an integer value. The number of measurements is equal to the number of causes supported plus a possible sum value identified by the .sum suffix. HO.OutSuccTarget.Cause where Cause identifies the cause for handover. EUtranRelation 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.3.2 |
6,229 | β TCI-UL-State | The IE TCI-UL-State indicates the TCI state information for UL transmission. TCI-UL-State information element -- ASN1START -- TAG-TCI-UL-STATE-START TCI-UL-State-r17 ::= SEQUENCE { tci-UL-StateId-r17 TCI-UL-StateId-r17, servingCellId-r17 ServCellIndex OPTIONAL, -- Need R bwp-Id-r17 BWP-Id OPTIONAL, -- Cond CSI-RSorSRS-Indicated referenceSignal-r17 CHOICE { ssb-Index-r17 SSB-Index, csi-RS-Index-r17 NZP-CSI-RS-ResourceId, srs-r17 SRS-ResourceId }, additionalPCI-r17 AdditionalPCIIndex-r17 OPTIONAL, -- Need R ul-powerControl-r17 Uplink-powerControlId-r17 OPTIONAL, -- Need R pathlossReferenceRS-Id-r17 PathlossReferenceRS-Id-r17 OPTIONAL, -- Cond Mandatory ..., [[ tag-Id-ptr-r18 ENUMERATED {n0,n1} OPTIONAL -- Cond 2TA ]] } -- TAG-TCI-UL-STATE-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
6,230 | 5.2.16.3.5 Nnssf_NSSAIAvailability_Unsubscribe service operation | Service operation name: Nnssf_NSSAIAvailability_Unsubscribe Description: This service operation enables a NF Service Consumer (e.g. AMF) to unsubscribe to a notification of any previously subscribed changes to the NSSAI availability information. This service operation also enables the NF Service Consumer (e.g. AMF, NSSF) to unsubscribe to a notification for Network Slice Replacement or for Network Slice Instance Replacement. Inputs, Required: Subscription Correlation ID. Inputs, Optional: None. Outputs, Required: None. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.16.3.5 |
6,231 | 6.1.2 Overall architecture for separation of gNB-CU-CP and gNB-CU-UP | The overall architecture for separation of gNB-CU-CP and gNB-CU-UP is depicted in Figure 6.1.2-1. NOTE: NG-RAN could also consist of a set of ng-eNBs, an ng-eNB may consist of an ng-eNB-CU-CP, one or more ng-eNB-CU-UP(s), and one or more ng-eNB-DU(s). An ng-eNB-CU-CP and an ng-eNB-CU-UP is connected via the E1 interface. An ng-eNB-DU is connected to an ng-eNB-CU-CP via the W1-C interface, and to an ng-eNB-CU-UP via the W1-U interface. The general principle described in this clause also applies to ng-eNB and its corresponding E1 and W1 interfaces, if not explicitly specified otherwise. Figure 6.1.2-1. Overall architecture for separation of gNB-CU-CP and gNB-CU-UP - A gNB may consist of a gNB-CU-CP, multiple gNB-CU-UPs and multiple gNB-DUs; - The gNB-CU-CP is connected to the gNB-DU through the F1-C interface; - The gNB-CU-UP is connected to the gNB-DU through the F1-U interface; - The gNB-CU-UP is connected to the gNB-CU-CP through the E1 interface; - One gNB-DU is connected to only one gNB-CU-CP; - One gNB-CU-UP is connected to only one gNB-CU-CP; NOTE 1: For resiliency, a gNB-DU and/or a gNB-CU-UP may be connected to multiple gNB-CU-CPs by appropriate implementation. - One gNB-DU can be connected to multiple gNB-CU-UPs under the control of the same gNB-CU-CP; - One gNB-CU-UP can be connected to multiple DUs under the control of the same gNB-CU-CP; NOTE 2: The connectivity between a gNB-CU-UP and a gNB-DU is established by the gNB-CU-CP using Bearer Context Management functions. NOTE 3: The gNB-CU-CP selects the appropriate gNB-CU-UP(s) for the requested services for the UE. In case of multiple CU-UPs they belong to same security domain as defined in TS 33.210[ Network Domain Security (NDS); IP network layer security ] [18]. NOTE 4: Data forwarding between gNB-CU-UPs during intra-gNB-CU-CP handover within a gNB may be supported by Xn-U. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 6.1.2 |
6,232 | 16.18.6 Flight Path Information Reporting for Aerial UE Communication | Following an indication from the Aerial UE that flight path information is available, NG-RAN can request the Aerial UE to report flight path information consisting of a number of waypoints defined as 3D locations, as defined in TS 37.355[ LTE Positioning Protocol (LPP) ] [43]. Aerial UE reports up to a configured number of waypoints if flight path information is available at the UE. The report can also contain a time stamp per waypoint if configured by the NG-RAN and if available at the UE. The flight path information can be also provided by the source gNB to the target gNB during handover. If configured by the NG-RAN and if the associated distance- or time-based condition (see flightPathUpdateDistanceThr and flightPathUpdateTimeThr in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12], respectively) for indication reporting are met for any of the waypoints, the Aerial UE indicates the availability of the updated flight path information. The Aerial UE can also indicate the availability of the updated flight path information if a new waypoint has been added or if a future waypoint has been removed from the flight path information. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.18.6 |
6,233 | 5.2.1 Mobile originating call establishment | The call control entity of the mobile station initiates establishment of a CC connection by requesting the MM sublayer to establish a mobile originating MM connection and entering the "MM connection pending" state. There are two kinds of a mobile originating call: basic call and emergency call. The request to establish an MM connection shall contain a parameter to specify whether the call is a basic or an emergency call. This information may lead to specific qualities of services to be provided by the MM sublayers. Timer T303 is started when the CM SERVICE REQUEST message is sent. For mobile stations supporting eMLPP basic calls may optionally have an associated priority level as defined in 3GPP TS 23.067[ enhanced Multi-Level Precedence and Pre-emption Service (eMLPP); Stage 2 ] [88]. This information may also lead to specified qualities of service to be provided by the MM sublayers. While being in the "MM connection pending" state, the call entity of the mobile station may cancel the call prior to sending the first call control message according to the rules given in subclause 4.5.1.7. The mobile station supporting multicall that is initiating an emergency call shall release one or more existing call to ensure the emergency call can be established if the multicall supported information stored in the mobile station described in subclauses 5.2.1.2 and 5.2.2.1 indicates the network does not support multicall and some ongoing calls exists. Having entered the "MM connection pending" state, upon MM connection establishment, the call control entity of the mobile station sends a setup message to its peer entity. This setup message is: - a SETUP message, if the call to be established is a basic call, and - an EMERGENCY SETUP message, if the call to be established is an emergency call. NOTE 1: The Extended Local Emergency Numbers List (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120]) does not apply in this specification. The mobile station then enters the "call initiated" state. Timer T303 is not stopped. The setup message shall contain all the information required by the network to process the call. In particular, the: - SETUP message shall contain the called party address information; - EMERGENCY SETUP message shall contain the emergency category, if the emergency category is available at the MS. If the mobile station supports multicall, it shall include the Stream Identifier (SI) information element. For the first call i.e. when there are no other ongoing calls the SI value shall be 1. For speech calls the mobile station shall indicate all codecs that it supports for UTRAN in the Supported Codec List information element. Codecs for GERAN shall be indicated in the Bearer Capability information element, if this information element is included. Additionally, if the mobile station supports codecs for GERAN and UTRAN, it shall indicate the codecs for GERAN also in the Supported Codec List information element. If the call is a redial attempt to switch from speech to multimedia or vice-versa, the SETUP message shall include the Redial information element. NOTE 2: Redial attempt is defined in 3GPP TR 23.903: "Redial solution for voice-video switching"[115]. If the MS supports the enhanced network-initiated in-call modification procedure as specified in subclause 5.3.4.3, the MS shall indicate this in the Call Control Capabilities IE in the SETUP message. If timer T303 elapses in the "MM connection pending" state, the MM connection in progress shall be aborted and the user shall be informed about the rejection of the call. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.2.1 |
6,234 | B.2 Multiple SSBs in a carrier | For a UE in RRC_CONNECTED, the BWPs configured by a serving cell may overlap in the frequency domain with the BWPs configured for other UEs by other cells within a carrier. Multiple SSBs may also be transmitted within the frequency span of a carrier used by the serving cell. However, from the UE perspective, each serving cell is associated to at most a single SSB. Figure B.2-1 below describes a scenario with multiple SSBs in a carrier, identifying two different cells (NCGI = 5, associated to SSB1, and NCGI = 6, associated to SSB3) with overlapping BWPs, and where RRM measurements can be configured to be performed by the UE on each of the available SSBs, i.e. SSB1, SSB2, SSB3 and SSB4. Figure B.2-1: Example of multiple SSBs in a carrier | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | B.2 |
6,235 | 16.18.8 BRID and DAA Support via A2X Communication | The Aerial UE supports A2X communication which is broadcasting of BRID and DAA messages using NR sidelink. DAA can also be provided via unicast transmissions in NR sidelink. BRID and DAA message transmission is supported in both in-coverage and out-of-coverage scenarios and relies only on UE autonomous resource selection for NR sidelink communication. BRID and DAA follow the QoS framework defined for NR sidelink and dedicated A2X PQI values are stored in table 6.2.4.1-1 of TS 23.256[ Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2 ] [60]. The NG-RAN can configure a separate SL Tx resource pool for BRID and DAA. The SL Tx pool selection for A2X is described in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [6], clause 5.22. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.18.8 |
6,236 | 4.3.18.2.2 Terminating IMS-based MPS Session | The terminating network identifies the priority of the IMS-based MPS session and applies priority treatment to ensure that the call is delivered with priority to the terminating user (either a Service User or normal user). If the existing ARP of the default or dedicated EPS bearer that is used to transport IMS signalling are not appropriate for the MPS service, then PCRF updates to the appropriate settings. S-GW triggers a new priority paging towards MME if the ongoing paging is lower priority than the incoming data received in the S-GW for IMS terminating session. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.18.2.2 |
6,237 | 10.5.4.18 Low layer compatibility | The purpose of the low layer compatibility information element is to provide a means which should be used for compatibility checking by an addressed entity (e.g., a remote user or an interworking unit or a high layer function network node addressed by the calling user). The low layer compatibility information element is transferred transparently by a PLMN between the call originating entity (e.g. the calling user) and the addressed entity. Except for the information element identifier, the low layer compatibility information element is coded as in ITU recommendation Q.931. For backward compatibility reasons coding of the modem type field according to ETS 300 102-1 (12-90) shall also be supported. The low layer compatibility is a type 4 information element with a minimum length of 2 octets and a maximum length of 18 octets. Figure 10.5.104/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Low layer compatibility information element If the value part of the IE is empty, the IE indicates "not applicable". | 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.18 |
6,238 | C.3.2 Processing on UE side | The ECIES scheme shall be implemented such that for computing a fresh SUCI, the UE shall use the provisioned public key of the home network and freshly generated ECC (elliptic curve cryptography) ephemeral public/private key pair according to the ECIES parameters provisioned by home network. The processing on UE side shall be done according to the encryption operation defined in [29]. with the following changes to Section 3.8 and step 5 and 6 of Section 5.1.3. - generate keying data K of length enckeylen + icblen + mackeylen. - Parse the leftmost enckeylen octets of K as an encryption key EK, the middle icblen octets of K as an ICB, and the rightmost mackeylen octets of K as a MAC key MK. The final output shall be the concatenation of the ECC ephemeral public key, the ciphertext value, the MAC tag value, and any other parameters, if applicable. NOTE: The reason for mentioning "any other parameter, if applicable" in the final output is to allow cases, e.g. to enable the sender to send additional sign indication when point compression is used. The Figure C.3.2-1 illustrates the UE's steps. Figure C.3.2-1: Encryption based on ECIES at UE | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | C.3.2 |
6,239 | β MeasurementTimingConfiguration | The MeasurementTimingConfiguration message is used to convey assistance information for measurement timing. Direction: en-gNB to eNB, eNB to en-gNB, gNB to gNB, ng-eNB to gNB, gNB to ng-eNB, ng-eNB to ng-eNB, gNB DU to gNB CU, and gNB CU to gNB DU. MeasurementTimingConfiguration message -- ASN1START -- TAG-MEASUREMENT-TIMING-CONFIGURATION-START MeasurementTimingConfiguration ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE{ measTimingConf MeasurementTimingConfiguration-IEs, spare3 NULL, spare2 NULL, spare1 NULL }, criticalExtensionsFuture SEQUENCE {} } } MeasurementTimingConfiguration-IEs ::= SEQUENCE { measTiming MeasTimingList OPTIONAL, nonCriticalExtension MeasurementTimingConfiguration-v1550-IEs OPTIONAL } MeasurementTimingConfiguration-v1550-IEs ::= SEQUENCE { campOnFirstSSB BOOLEAN, psCellOnlyOnFirstSSB BOOLEAN, nonCriticalExtension MeasurementTimingConfiguration-v1610-IEs OPTIONAL } MeasurementTimingConfiguration-v1610-IEs ::= SEQUENCE { csi-RS-Config-r16 SEQUENCE { csi-RS-SubcarrierSpacing-r16 SubcarrierSpacing, csi-RS-CellMobility-r16 CSI-RS-CellMobility, refSSBFreq-r16 ARFCN-ValueNR }, nonCriticalExtension SEQUENCE {} OPTIONAL } MeasTimingList ::= SEQUENCE (SIZE (1..maxMeasFreqsMN)) OF MeasTiming MeasTiming ::= SEQUENCE { frequencyAndTiming SEQUENCE { carrierFreq ARFCN-ValueNR, ssbSubcarrierSpacing SubcarrierSpacing, ssb-MeasurementTimingConfiguration SSB-MTC, ss-RSSI-Measurement SS-RSSI-Measurement OPTIONAL } OPTIONAL, ..., [[ ssb-ToMeasure SSB-ToMeasure OPTIONAL, physCellId PhysCellId OPTIONAL ]] } -- TAG-MEASUREMENT-TIMING-CONFIGURATION-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
6,240 | 6.5.3.4.3 Handling of network rejection due to ESM cause other than ESM cause #26 | If the ESM cause value is different from #26 "insufficient resources" and #65 "maximum number of EPS bearers reached", and the Back-off timer value IE is included, the UE shall behave as follows depending on the timer value received in the Back-off timer value IE (if the UE is a UE configured to use AC11 β 15 in selected PLMN, exceptions are specified in clause 6.3.6): - if the timer value indicates neither zero nor deactivated, the UE shall start the back-off timer with the value provided in the Back-off timer value IE for the bearer resource allocation procedure and PLMN and combination and not send another BEARER RESOURCE ALLOCATION REQUEST message in the PLMN for the same until the back-off timer expires, the UE is switched off or the USIM is removed; - if the timer value indicates that this timer is deactivated, the UE shall not send another BEARER RESOURCE ALLOCATION REQUEST message in the PLMN for the same until the UE is switched off or the USIM is removed; and - if the timer value indicates zero, the UE may send another BEARER RESOURCE ALLOCATION REQUEST message in the PLMN for the same . If the Back-off timer value IE is not included, then the UE shall ignore the Re-attempt Indicator IE provided by the network, if any. 1) Additionally, if the ESM cause value is #32 "service option not supported", or #33 "requested service option not subscribed", the UE shall proceed as follows: - if the UE is registered in the HPLMN or in a PLMN that is within the EHPLMN list (if the EHPLMN list is present), the UE shall behave as described above in the present clause, using the configured SM_RetryWaitTime value as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or in USIM file NASCONFIG as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17], if available, as back-off timer value; and NOTE 0: The way to choose one of the configured SM_RetryWaitTime values for back-off timer value is up to UE implementation if the UE is configured with: - an SM_RetryWaitTime value in ME as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A]; and - an SM_RetryWaitTime value in USIM file NASCONFIG as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]. - otherwise, if the UE is not registered in its HPLMN or a PLMN that is within the EHPLMN list (if the EHPLMN list is present) or the SM_RetryWaitTime value is not configured, the UE shall behave as described above in the present clause, using the default value of 12 minutes for the back-off timer. 2) For ESM cause values different from #32 "service option not supported", or #33 "requested service option not subscribed", the UE behaviour regarding the start of a back-off timer is unspecified. The UE shall not stop any back-off timer upon a PLMN change or inter-system change. If the network indicates that a back-off timer for the bearer resource allocation procedure and PLMN and APN combination is deactivated, then it remains deactivated upon a PLMN change or inter-system change. NOTE 1: This means the back-off timer can still be running or be deactivated for the given ESM procedure and PLMN and APN combination when the UE returns to the PLMN or when it performs inter-system change back from A/Gb or Iu mode or N1 mode to S1 mode. Thus the UE can still be prevented from sending another BEARER RESOURCE ALLOCATION REQUEST message in the PLMN for the same APN. If the back-off timer is started upon receipt of BEARER RESOURCE ALLOCATION REJECT (i.e. the timer value was provided by the network, a configured value is available or the default value is used as explained above) or the back-off timer is deactivated, the UE behaves as follows: 1) after a PLMN change the UE may send a BEARER RESOURCE ALLOCATION REQUEST message for the same APN in the new PLMN, if the back-off timer is not running and is not deactivated for the bearer resource allocation procedure and the combination of new PLMN and APN. Furthermore as an implementation option, for the ESM cause values #32 "service option not supported" or #33 "requested service option not subscribed", if the network does not include a Re-attempt indicator IE, the UE may decide not to automatically send another BEARER RESOURCE ALLOCATION REQUEST message for the same APN that was sent by the UE, if the UE is registered to a new PLMN which is in the list of equivalent PLMNs; 2) if the network does not include the Re-attempt indicator IE to indicate whether re-attempt in A/Gb or Iu mode or N1 mode is allowed, or the UE ignores the Re-attempt indicator IE, e.g. because the Back-off timer value IE is not included, then: - if the UE is registered in its HPLMN or in a PLMN that is within the EHPLMN list (if the EHPLMN list is present), the UE shall apply the configured SM_RetryAtRATChange value as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or in USIM file NASCONFIG as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17], if available, to determine whether the UE may attempt a secondary PDP context activation procedure for the same PLMN and APN combination in A/Gb or Iu mode or a PDU session modification procedure for the same PLMN and APN combination in N1 mode; and NOTE 2: The way to choose one of the configured SM_RetryAtRATChange values for back-off timer value is up to UE implementation if the UE is configured with: - an SM_RetryAtRATChange value in ME as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A]; and - an SM_RetryAtRATChange value in USIM file NASCONFIG as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]. - if the UE is not registered in its HPLMN or in a PLMN that is within the EHPLMN list (if the EHPLMN list is present), or if the NAS configuration MO as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] is not available and the value for inter-system change is not configured in the USIM file NASCONFIG, then the UE behaviour regarding a secondary PDP context activation procedure for the same PLMN and APN combination in A/Gb or Iu mode and a PDU session modification procedure for the same PLMN and APN combination in N1 mode are unspecified; and 3) if the network includes the Re-attempt indicator IE indicating that re-attempt in an equivalent PLMN is not allowed, then depending on the timer value received in the Back-off timer value IE, for each combination of a PLMN from the equivalent PLMN list and the APN the UE shall start a back-off timer for the bearer resource allocation procedure with the value provided by the network, or deactivate the respective back-off timer as follows: - if the Re-attempt indicator IE additionally indicates that re-attempt in A/Gb or Iu mode or N1 mode is allowed, the UE shall start or deactivate the back-off timer for S1 mode only; and - otherwise the UE shall start or deactivate the back-off timer for A/Gb, Iu, S1 and N1 mode. If the back-off timer for a PLMN and APN combination was started or deactivated in A/Gb or Iu mode upon receipt of an ACTIVATE SECONDARY PDP CONTEXT REJECT message (see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13]) and the network indicated that re-attempt in S1 mode is allowed, then this back-off timer does not prevent the UE from sending a BEARER RESOURCE ALLOCATION REQUEST message in this PLMN for the same APN after inter-system change to S1 mode. If the network indicated that re-attempt in S1 mode is not allowed, the UE shall not send any BEARER RESOURCE ALLOCATION REQUEST message in this PLMN for the same APN after inter-system change to S1 mode until the timer expires, the UE is switched off or the USIM is removed. If a back-off timer for a PLMN and APN combination, in combination with any S-NSSAI or without S-NSSAI (see 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54]) was started or deactivated in N1 mode upon receipt of a PDU SESSION MODIFICATION REJECT message (see 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54]) and the network indicated that re-attempt in S1 mode is allowed, then this back-off timer does not prevent the UE from sending a BEARER RESOURCE ALLOCATION REQUEST message in this PLMN for the same APN after inter-system change to S1 mode. If the network indicated that re-attempt in S1 mode is not allowed, the UE shall not send any BEARER RESOURCE ALLOCATION REQUEST message in this PLMN for the same APN after inter-system change to S1 mode until the timer expires, the UE is switched off or the USIM is removed. If more than one back-off timer for the same PLMN and APN combination was started in N1 mode with an indication from the network that re-attempt in S1 mode is not allowed and no back-off timer for the same PLMN and APN combination was deactivated in N1 mode, the UE shall not send any BEARER RESOURCE ALLOCATION REQUEST message in this PLMN for the same APN after inter-system change to S1 mode until all timers have expired. If at least one back-off timer for the same PLMN and APN combination was deactivated in N1 mode, the UE shall not send any BEARER RESOURCE ALLOCATION REQUEST message in this PLMN for the same APN until the UE is switched off or the USIM is removed. NOTE 3: The back-off timer is used to describe a logical model of the required UE behaviour. This model does not imply any specific implementation, e.g. as a timer or timestamp. NOTE 4: Reference to back-off timer in this section can either refer to use of timer T3396 or to use of a different packet system specific timer within the UE. Whether the UE uses T3396 as a back-off timer or it uses different packet system specific timers as back-off timers is left up to UE implementation. This back-off timer is stopped when the UE is switched off or the USIM is removed. If the ESM cause value is #65 "maximum number of EPS bearers reached", the UE shall determine the PLMN's maximum number of EPS bearer contexts in S1 mode (see clause 6.5.0) as the number of active EPS bearer contexts it has. The UE shall ignore the Back-off timer value IE and Re-attempt indicator IE provided by the network, if any. NOTE 5: In some situations, when attempting to establish multiple EPS bearer contexts, the number of active EPS bearer contexts in the UE when cause #65 is received is not equal to the maximum number of EPS bearer contexts reached in the network. The PLMN's maximum number of EPS bearer contexts in S1 mode applies to the PLMN in which the ESM cause #65 "maximum number of EPS bearers reached" is received. When the UE is switched off or when the USIM is removed, the UE shall clear all previous determinations representing any PLMN's maximum number of EPS bearer contexts in S1 mode. Upon successful registration with a new PLMN, the UE may clear previous determinations representing any PLMN's maximum number of EPS bearer contexts in S1 mode. The further actions to be performed by the UE are implementation dependent as part of upper layers responsibility. | 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.3.4.3 |
6,241 | 19.4.2.5 Routing Area Identity (RAI) - EPC | The Routing Area Identity (RAI) consists of a RAC, LAC, MNC and MCC. A subdomain name for use by core network nodes based on RAI shall be derived from the MNC and MCC by adding the label "rac" to the beginning of the Home Network Realm/Domain (see clause 19.2). The RAI FQDN shall be constructed as: rac<RAC>.lac<LAC>.rac.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org <RAC> and <LAC> shall be Hex coded digits representing the LAC and RAC codes respectively. If there are less than 4 significant digits in <RAC> or <LAC>, one or more "0" digit(s) is/are inserted at the left side to fill the 4 digit coding. Note: Above subdomain is for release 8 core network nodes to allow DNS records other than A/AAAA records. The subdomain name in Annex C.2 are still used for existing A/AAAA records for pre-Release 8 nodes and are also still used for backward compatibility. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 19.4.2.5 |
6,242 | 9.2.4.2A TDD (With interferenceMeasRestriction configured) | The following requirements apply to UE Category β₯2. For the parameters specified in table 9.2.4.2A-1, and using the downlink physical channels specified in Tables C.3.4-1 and C.3.4-2, the reported offset level of the wideband spatial differential CQI for codeword #1 (Table 7.2-2 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6]) shall be used to determine the wideband CQI index for codeword #1 as wideband CQI1 = wideband CQI0 β Codeword 1 offset level The wideband CQI1 shall be within the set {median CQI1 -1, median CQI1, median CQI1 +1} for more than 90% of the time, where the resulting wideband values CQI1 shall be used to determine the median CQI values for codeword #1. For both codewords #0 and #1, the PDSCH BLER using the transport format indicated by the respective median CQI0 β 1 and median CQI1 β 1 shall be less than or equal to 0.1. Furthermore, for both codewords #0 and #1, the PDSCH BLER using the transport format indicated by the respective median CQI0 + 1 and median CQI1 + 1 shall be greater than or equal to 0.1. Table 9.2.4.2A-1: PUCCH 1-1 static test (TDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.2.4.2A |
6,243 | 9.3.6.2 TDD | For the parameters specified in Table .2-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.3.6.2-2 and by the following a) a sub-band differential CQI offset level of 0 shall be reported at leastο ο‘ % of the time but less than ο’ο % for each sub-band for CSI process 1, 2, or 3; b) a CQI index not in the set {median CQI -1, median CQI, median CQI +1} shall be reported at least ο€ο % of the time for CSI process 0; c) the difference of the median CQIs of the reported wideband CQI for configurated CSI processes shall be greater or equal to the values as in Table .2-3; d) the ratio of the throughput obtained when transmitting on a randomly selected sub-band among the sub-bands with the highest differential CQI offset level the corresponding TBS and that obtained when transmitting the TBS indicated by the reported wideband CQI median on a randomly selected sub-band in set S shall be β₯ ο§; e) when transmitting on a randomly selected sub-band among the sub-bands with the highest differential CQI offset level the corresponding TBS, the average BLER for the indicated transport formats shall be greater or equal to 0.02. The requirements only apply for sub-bands of full size and the random scheduling across the sub-bands is done by selecting a new sub-band in each TTI for FDD, each available downlink transmission instance for TDD. Sub-bands of a size smaller than full size are excluded from the test. Table .2-1: Fading test for TDD Table .2-2: Minimum requirement (TDD) Table .2-3: Minimum median CQI difference between configured CSI processes (TDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.3.6.2 |
6,244 | 13.7 Unavailable User Identity | The Unavailable User Identity shall take the form of a SIP URI (see IETF RFC 3261 [26]). A SIP URI for an Unavailable User Identity shall take the form "sip:user@domain". The user part shall be the string "unavailable" and the domain part shall be the string "unknown.invalid". The full SIP URI for Unavailable User Identity is thus: "sip:[email protected]" For more information on the Unavailable User Identity and when it is used, see 3GPP TS 29.163[ Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks ] [63]. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 13.7 |
6,245 | β SL-L2RelayUE-Config | The IE SL-L2RelayUE-Config is used to configure L2 U2N relay operation related configurations used by L2 U2N Relay UE, or L2 U2U relay operation related configurations used by L2 U2U Relay UE. SL-L2RelayUE-Config information element -- ASN1START -- TAG-SL-L2RELAYUE-CONFIG-START SL-L2RelayUE-Config-r17 ::= SEQUENCE { sl-RemoteUE-ToAddModList-r17 SEQUENCE (SIZE (1..maxNrofRemoteUE-r17)) OF SL-RemoteUE-ToAddMod-r17 OPTIONAL, -- Need N sl-RemoteUE-ToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofRemoteUE-r17)) OF SL-DestinationIdentity-r16 OPTIONAL, -- Need N ..., [[ sl-U2U-RemoteUE-ToAddModList-r18 SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-U2U-RemoteUE-ToAddMod-r18 OPTIONAL, -- Need N sl-U2U-RemoteUE-ToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-DestinationIdentity-r16 OPTIONAL -- Need N ]] } SL-RemoteUE-ToAddMod-r17 ::= SEQUENCE { sl-L2IdentityRemote-r17 SL-DestinationIdentity-r16, sl-SRAP-ConfigRelay-r17 SL-SRAP-Config-r17 OPTIONAL, -- Need M ... } SL-U2U-RemoteUE-ToAddMod-r18 ::= SEQUENCE { sl-L2IdentityRemote-r18 SL-DestinationIdentity-r16, sl-SourceRemoteUE-ToAddModList-r18 SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-SourceRemoteUE-ToAddMod-r18 OPTIONAL, -- Need N sl-SourceRemoteUE-ToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-SourceIdentity-r17 OPTIONAL, -- Need N ... } SL-SourceRemoteUE-ToAddMod-r18 ::= SEQUENCE { sl-SourceUE-Identity-r18 SL-SourceIdentity-r17, sl-SRAP-ConfigU2U-r18 SL-SRAP-ConfigU2U-r18, ... } -- TAG-SL-L2RELAYUE-CONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
6,246 | β UplinkTxDirectCurrentTwoCarrierList | The IE UplinkTxDirectCurrentTwoCarrierList indicates the Tx Direct Current locations when uplink intra-band CA with two carriers is configured, based on the configured carriers and BWP numerology and the associated carrier bandwidth of the carriers. The UE does not report the uplink Direct Current location information for SUL carrier(s). UplinkTxDirectCurrentTwoCarrierList information element -- ASN1START -- TAG-UPLINKTXDIRECTCURRENTTWOCARRIERLIST-START UplinkTxDirectCurrentTwoCarrierList-r16 ::= SEQUENCE (SIZE (1..maxNrofTxDC-TwoCarrier-r16)) OF UplinkTxDirectCurrentTwoCarrier-r16 UplinkTxDirectCurrentTwoCarrier-r16 ::= SEQUENCE { carrierOneInfo-r16 UplinkTxDirectCurrentCarrierInfo-r16, carrierTwoInfo-r16 UplinkTxDirectCurrentCarrierInfo-r16, singlePA-TxDirectCurrent-r16 UplinkTxDirectCurrentTwoCarrierInfo-r16, secondPA-TxDirectCurrent-r16 UplinkTxDirectCurrentTwoCarrierInfo-r16 OPTIONAL } UplinkTxDirectCurrentCarrierInfo-r16 ::= SEQUENCE { servCellIndex-r16 ServCellIndex, servCellInfo-r16 CHOICE { bwp-Id-r16 BWP-Id, deactivatedCarrier-r16 ENUMERATED {deactivated} } } UplinkTxDirectCurrentTwoCarrierInfo-r16 ::= SEQUENCE { referenceCarrierIndex-r16 ServCellIndex, shift7dot5kHz-r16 BOOLEAN, txDirectCurrentLocation-r16 INTEGER (0..3301) } -- TAG-UPLINKTXDIRECTCURRENTTWOCARRIERLIST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
6,247 | 6.1.3.3.3.2 Handling of network rejection due to SM cause #26 | If the SM cause value is #26 and the Back-off timer value IE is included, the MS shall ignore the Re-attempt indicator IE provided by the network, if any, and take different actions depending on the timer value received for timer T3396 in the Back-off timer value IE (if the MS is configured for dual priority, exceptions are specified in subclause 6.1.3.12; if the MS is an MS configured to use AC11 β 15 in selected PLMN, exceptions are specified in subclause 6.1.3.11): i) if the timer value indicates neither zero nor deactivated, the MS shall stop timer T3396 associated with the corresponding APN, if it is running. The MS shall then start timer T3396 with the value provided in the Back-off timer value IE and not send another ACTIVATE PDP CONTEXT REQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST message with exception of those identified in subclause 6.1.3.3, for the same APN until timer T3396 expires or timer T3396 is stopped. If the MS did not send an APN for the establishment of the PDN connection and the request type was different from "emergency", the MS shall stop timer T3396 associated with no APN, if it is running. The MS shall then start timer T3396 with the value provided in the Back-off timer value IE and not send another ACTIVATE PDP CONTEXT REQUEST without an APN and with request type different from "emergency", or another ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST message with exception of those identified in subclause 6.1.3.3, for a non-emergency PDN connection established without an APN sent by the MS, until timer T3396 expires or timer T3396 is stopped. The MS shall not stop timer T3396 upon a PLMN change or inter-system change; ii) if the timer value indicates that this timer is deactivated, the MS shall not send another ACTIVATE PDP CONTEXT REQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST message with exception of those identified in subclause 6.1.3.3, for the same APN until the MS is switched off or the SIM/USIM is removed or the MS receives REQUEST PDP CONTEXT ACTIVATION, REQUEST SECONDARY PDP CONTEXT ACTIVATION or MODIFY PDP CONTEXT REQUEST message for the same APN or a DEACTIVATE PDP CONTEXT REQUEST message including SM cause #39 "reactivation requested" for a PDP context which was activated by the MS for the same APN from the network. If the MS did not send an APN for the establishment of the PDN connection and the request type was different from "emergency", the MS shall not send another ACTIVATE PDP CONTEXT REQUEST without an APN and with request type different from "emergency", or another ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST with exception of those identified in subclause 6.1.3.3, for a non-emergency PDN connection established without APN sent by the MS, until the MS is switched off or the SIM/USIM is removed or the MS receives any of the following messages: a REQUEST PDP CONTEXT ACTIVATION without an APN, a REQUEST SECONDARY PDP CONTEXT ACTIVATION or MODIFY PDP CONTEXT REQUEST message for a non-emergency PDN connection established without an APN sent by the MS, or a DEACTIVATE PDP CONTEXT REQUEST message including SM cause #39 "reactivation requested" for a PDP context which was activated by the MS for a non-emergency PDN connection established without an APN sent by the MS. The timer T3396 remains deactivated upon a PLMN change or inter-system change; or iii) if the timer value indicates that this timer is zero, the MS: - shall stop timer T3396 associated with the corresponding APN, if running, and may send an ACTIVATE PDP CONTEXT REQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST message for the same APN; and - if the MS did not send an APN for the establishment of the PDN connection and the request type was different from "emergency", the MS shall stop timer T3396 associated with no APN, if running, and may send an ACTIVATE PDP CONTEXT REQUEST message without an APN, or another ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST message for a non-emergency PDN connection established without an APN sent by the MS. If the Back-off timer value IE is not included, the MS may send an ACTIVATE PDP CONTEXT REQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST message for the same APN. If the timer T3396 is running when the MS enters state GMM-DEREGISTERED, the MS remains switched on, and the SIM/USIM in the MS remains the same, then timer T3396 is kept running until it expires or it is stopped. If the MS is switched off when the timer T3396 is running, and if the SIM/USIM in the MS remains the same when the MS is switched on, the MS behaves as follows: - let t1 be the time remaining for T3396 timeout at switch off and let t be the time elapsed between switch off and switch on. If t1 is greater than t, then the timer shall be restarted with the value t1 β t. If t1 is equal to or less than t, then the timer need not be restarted. If the MS is not capable of determining t, then the MS shall restart the timer with the value t1; and - if prior to switch off, timer T3396 was running because an ACTIVATE PDP CONTEXT REQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST, MODIFY PDP CONTEXT REQUEST or ACTIVATE MBMS CONTEXT REQUEST message containing the low priority indicator set to "MS is configured for NAS signalling low priority" was rejected with a timer value for timer T3396, and if timer T3396 is restarted at switch on, then the MS configured for dual priority shall handle session management requests as indicated in subclause 6.1.3.12. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.1.3.3.3.2 |
6,248 | 5.4.5 Buffer Status Reporting | The Buffer Status reporting procedure is used to provide the serving eNB with information about the amount of data available for transmission in the UL buffers associated with the MAC entity. RRC controls BSR reporting by configuring the three timers periodicBSR-Timer, retxBSR-Timer and logicalChannelSR-ProhibitTimer and by, for each logical channel, optionally signalling logicalChannelGroup which allocates the logical channel to an LCG, as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]. For the Buffer Status reporting procedure, the MAC entity shall consider all radio bearers which are not suspended and may consider radio bearers which are suspended. For NB-IoT the Long BSR is not supported and all logical channels belong to one LCG. A Buffer Status Report (BSR) shall be triggered if any of the following events occur: - UL data, for a logical channel which belongs to a LCG, becomes available for transmission in the RLC entity or in the PDCP entity (the definition of what data shall be considered as available for transmission is specified in TS 36.322[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Link Control (RLC) protocol specification ] [3] and TS 36.323[ Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) specification ] [4] or TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [17] respectively) and either the data belongs to a logical channel with higher priority than the priorities of the logical channels which belong to any LCG and for which data is already available for transmission, or there is no data available for transmission for any of the logical channels which belong to a LCG, in which case the BSR is referred below to as "Regular BSR"; - UL resources are allocated and number of padding bits is equal to or larger than the size of the Buffer Status Report MAC control element plus its subheader, in which case the BSR is referred below to as "Padding BSR"; - retxBSR-Timer expires and the MAC entity has data available for transmission for any of the logical channels which belong to a LCG, in which case the BSR is referred below to as "Regular BSR"; - periodicBSR-Timer expires, in which case the BSR is referred below to as "Periodic BSR". For Regular BSR: - if the BSR is triggered due to data becoming available for transmission for a logical channel for which logicalChannelSR-Prohibit is configured by upper layers: - start or restart the logicalChannelSR-ProhibitTimer; - else: - if running, stop the logicalChannelSR-ProhibitTimer. For Regular and Periodic BSR: - if more than one LCG has data available for transmission in the TTI where the BSR is transmitted: report Long BSR; - else report Short BSR. For Padding BSR: - if the number of padding bits is equal to or larger than the size of the Short BSR plus its subheader but smaller than the size of the Long BSR plus its subheader: - if more than one LCG has data available for transmission in the TTI where the BSR is transmitted: report Truncated BSR of the LCG with the highest priority logical channel with data available for transmission; - else report Short BSR. - else if the number of padding bits is equal to or larger than the size of the Long BSR plus its subheader, report Long BSR. For NB-IoT or BL UEs: - if rai-Activation is configured, and a buffer size of zero bytes has been triggered for the BSR, and the UE may have more data to send or receive in the near future: - cancel any pending BSR. If the Buffer Status reporting procedure determines that at least one BSR has been triggered and not cancelled: - if the MAC entity has UL resources allocated for new transmission for this TTI: - instruct the Multiplexing and Assembly procedure to generate the BSR MAC control element(s); - start or restart periodicBSR-Timer except when all the generated BSRs are Truncated BSRs; - start or restart retxBSR-Timer. - else if a Regular BSR has been triggered and logicalChannelSR-ProhibitTimer is not running: - if an uplink grant is not configured or the Regular BSR was not triggered due to data becoming available for transmission for a logical channel for which logical channel SR masking (logicalChannelSR-Mask) is setup by upper layers; or - if sr-WithHARQ-ACK-Config is configured and there is valid resource for SR together with acknowledgement of the data in this TTI: - a Scheduling Request shall be triggered. A MAC PDU shall contain at most one MAC BSR control element, even when multiple events trigger a BSR by the time a BSR can be transmitted in which case the Regular BSR and the Periodic BSR shall have precedence over the padding BSR. For EDT, the MAC entity shall not generate a BSR MAC control element if new transmission is for Msg3. For CP-PUR, the MAC entity shall not generate a BSR MAC control element if new transmission is intended for preconfigured uplink grant. The MAC entity shall restart retxBSR-Timer upon indication of a grant for transmission of new data on any UL-SCH. All triggered BSRs shall be cancelled in case the UL grant(s) in this TTI can accommodate all pending data available for transmission but is not sufficient to additionally accommodate the BSR MAC control element plus its subheader. All triggered BSRs shall be cancelled when a BSR is included in a MAC PDU for transmission. The MAC entity shall transmit at most one Regular/Periodic BSR in a TTI. If the MAC entity is requested to transmit multiple MAC PDUs in a TTI, it may include a padding BSR in any of the MAC PDUs which do not contain a Regular/Periodic BSR. All BSRs transmitted in a TTI always reflect the buffer status after all MAC PDUs have been built for this TTI. Each LCG shall report at the most one buffer status value per TTI and this value shall be reported in all BSRs reporting buffer status for this LCG. NOTE 1: A Padding BSR is not allowed to cancel a triggered Regular/Periodic BSR, except for NB-IoT. A Padding BSR is triggered for a specific MAC PDU only and the trigger is cancelled when this MAC PDU has been built. NOTE 2: If UL HARQ operation is autonomous for the HARQ entity and if the BSR is already included in a MAC PDU for transmission by this HARQ entity, but not yet transmitted by lower layers, it is up to UE implementation how to handle the BSR content. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.4.5 |
6,249 | 10.5.5.35 DCN-ID | The purpose of the DCN-ID information element is to provide a DCN-ID for the registered PLMN to the MS. The DCN-ID is a type 4 information element with 4 octets length. The DCN-ID information element is coded as shown in figure 10.5.5.35-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.5.35-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.5.35-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : DCN-ID information element Table 10.5.5.35-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : DCN-ID information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.5.35 |
6,250 | 10.5.4.21c Redirecting party subaddress | The purpose of the Redirecting party subaddress is to identify a subaddress associated with the redirecting party. For the definition of a subaddress see Rec. ITU-T I.330. The Redirecting party subaddress information element is coded as shown in figure 10.5.108b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.121/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Redirecting party subaddress is a type 4 information element with a minimum length of 2 octets and a maximum length of 23 octets. Figure 10.5.108b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Redirecting party subaddress information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.4.21c |
6,251 | 5.2.6.16.2 Nnef_AnalyticsExposure_Subscribe operation | Service operation name: Nnef_AnalyticsExposure_Subscribe Description: The NF consumer subscribes or modifies an existing subscription on analytics information. Inputs, Required: (Set of) Analytics ID(s), Analytic Filter Information, Target of Analytic Reporting (UEs (e.g. GPSI), External Group Identifier, any UEs), Analytic Reporting Information, Notification Target Address (+ Notification Correlation ID). These input parameters are detailed in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. Inputs, Optional: Subscription Correlation ID (in the case of modification of the analytics subscription), Expiry time, slice specific information, Geographical area, Analytics feedback information. NOTE 1: When the Analytics ID is set to "User Data Congestion", the input parameters are defined in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. NOTE 2: The Geographical area could be provided as e.g. shapes (e.g. polygons, circles, etc.) or civic addresses (e.g. streets, districts, etc.) as referenced by OMA Presence API. NOTE 3: The Analytics feedback information only can be included in modification request for the existing analytics subscription as described in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. Outputs, Required: When the subscription is accepted: Subscription Correlation ID, Expiry time (required if the subscription can be expired based on the operator's policy). Outputs, Optional: First corresponding analytics report is included, if available. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.16.2 |
6,252 | 5.4.9.2 Group Wake Up Signal | To support the Wake Up Signal (WUS), the WUS Assistance Information is used by the ng-eNB to help determine the WUS group used when paging the UE (see TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [30]). The content of the WUS Assistance Information consists of the paging probability information. The paging probability information provides a metric on the probability of a UE receiving a paging message based on, e.g. statistical information. The UE may in the Registration Request message provide its capability to support receiving WUS Assistance Information. If WUS Assistance Information is supported by the UE, then the UE in the Registration Request message may provide the additional UE paging probability information. The AMF may use the UE provided paging probability, local configuration and/or previous statistical information for the UE, when determining the WUS Assistance Information. If the UE supports WUS Assistance Information, the AMF may assign WUS Assistance Information to the UE, even when the UE has not provided the additional UE paging probability information. If the AMF has determined WUS Assistance Information for the UE, the AMF provides it to the UE in every Registration Accept message. The AMF stores the WUS Assistance Information parameter in the MM context and provides it to the ng-eNB when paging the UE. UE and AMF shall not signal WUS Assistance Information in Registration Request, Registration Accept messages when the UE has an active emergency PDU session. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.4.9.2 |
6,253 | 6.2 Considerations on security | The 3GPP system shall support confidentiality protection of identities related to the UAS and personally identifiable information. The 3GPP system shall support the capability to provide different levels of integrity and privacy protection for the different connections between UAS and UTM as well as the data being transferred via those connections. The 3GPP system shall support non-repudiation of data sent from the UAS to UTM. Data held at the UTM may be subject to local data retention and privacy regulations. | 3GPP TS 22.825 | Study on Remote Identification of Unmanned Aerial Systems (UAS) | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.2 |
6,254 | 4.3.20 Relaying function 4.3.20.1 General | The relaying function enables an operator to improve and extend the coverage area by having a Relay Node (RN) wirelessly connected to an eNodeB serving the RN, called Donor eNodeB (DeNB), via a modified version of the E-UTRA radio interface called the Un interface as specified in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. The relaying function and use of RN/DeNB entities in a network is transparent to the operations of the UEs connected to it and associated core network entities (e.g. MME, S/P-GW, PCRF etc.) for the UEs. The relaying architecture is shown in figure 4.3.20.1-1. Figure 4.3.20.1-1: Relaying Architecture NOTE 1: Impact to core network elements from the introduction of RNs and DeNB is minimized by reusing the existing nodes and protocols when interacting with the core network. NOTE 2: Functions of the MME for the RN and MME for the UE may be collocated in a single MME. The RN supports the eNodeB functionality like termination of the radio protocols of the E-UTRA radio interface and the S1 and X2 interfaces. The RN also supports a subset of the UE functionality and protocols to wirelessly connect to the DeNB. In addition to supporting eNodeB functionality, the DeNB also embeds and provides the S-GW/P-GW-like functions needed for the RN operation. This includes creating a session for the RN and managing EPS bearers for the RN as shown in clause 4.3.20.3, as well as terminating the S1-AP and S11 interfaces towards the MME serving the RN. Due to the proxy functionality, the DeNB appears as an MME (for S1), an eNodeB (for X2) and an S-GW to the RN. The RN and DeNB also perform mapping of signalling and data packets onto EPS bearers that are setup for the RN. The mapping is based on existing QoS mechanisms defined for the UE and the P-GW and 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]. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.20 |
6,255 | 4.2.2 Common architecture β reference points | Figure 4.2.2.1 provides an overview of the logical ubiquitous charging architecture and the information flows for offline and online charging in reference points variant for non-5G systems. NOTE: this was formerly figure 4.2.1. Figure 4.2.2.1: Logical ubiquitous charging architecture and information flows for non-5G systemsβ reference points NOTE 0: The Service-NE are defined in the 3GPP specification range of TS 32.27[ None ] x. Figure 4.2.2.1 includes all network elements / systems (top to bottom: CS-NE all the way through to the PCEF) for which charging is defined within 3GPP standards. The arrows indicate logical information flows on the Rf, Ga, Bx, ISC, Ro, CAP, Gy and Gyn reference points. No inference should be drawn from the figure 4.2.2.1 with respect to the physical implementation of interfaces and charging functions. NOTE 1: On the PCEF embedded in PGW, TS 23.203[ Policy and charging control architecture ] [208] specifies the Gy reference point for online flow based bearer charging and the Gz reference point for offline flow based bearer charging. However, from the charging architecture perspective, Gy is functionally equivalent to the Ro reference point. Gz is functionally equivalent to the Ga reference point for the Legacy PS domain, and to one of Ga or Rf reference points for the Evolved PS domain. Therefore, throughout the present document, Ga or Rf are used for offline, and Ro for online are also used in conjunction with PCEF charging. This simplification ensures a consistent architectural view, as specified below, for all PCEF related online and offline charging architectural aspects. Refer to clause 5.3.1.2 for a description of flow based bearer charging. NOTE 2: Void. NOTE 3: Only SMS Charging is defined for MME, as specified in TS 23.272[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ] [213]. NOTE 4: As specified in TS 23.203[ Policy and charging control architecture ] [208], the TDF uses the Gyn reference point for online application based charging and the Gzn reference point for offline application based charging. However, from the charging architecture perspective Gyn is functionally equivalent to the Ro reference point and Gzn is functionally equivalent to one of Ga or Rf reference points in the PS domain. Therefore, throughout the present document, Ga or Rf for offline, and Ro for online are also used in conjunction with TDF charging. This simplification ensures a consistent architectural view, as specified below, for all TDF related online and offline charging architectural aspects. The logical ubiquitous charging architecture and the information flows for offline and online charging applied to the convergent scenario (i.e. both the Fixed Broadband Access network and Evolved Packet Core (EPC) owned by a single operator) with PCEF located in Fixed Broadband Access is defined in annex C, clause C.4.2. To implement roaming unbundling for EU roaming regulation III, an architectural solution known as the Single IMSI architecture has been defined in EU Roaming regulation III; Structural Solutions; High Level Technical Specifications [298]. This architecture is based on the introduction of specific Service-NE (known as a Proxy Function) which uses the Ro reference point for online charging. The details of this architecture are defined in annex B. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.2.2 |
6,256 | 10.5.3.1 Authentication parameter RAND | The purpose of the Authentication Parameter RAND information element is to provide the mobile station with a non-predictable number to be used to calculate the authentication response signature SRES and the ciphering key Kc (for a GSM authentication challenge), or the response RES and both the ciphering key CK and integrity key IK (for a UMTS authentication challenge). The Authentication Parameter RAND information element is coded as shown in figure 10.5.75/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.89/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Authentication Parameter RAND is a type 3 information element with 17 octets length. Figure 10.5.75/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Authentication Parameter RAND information element Table 10.5.89/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Authentication Parameter RAND information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.3.1 |
6,257 | 8.2.1.2.4 Enhanced Performance Requirement Type A - 2 Tx Antenna Ports with TM3 interference model | The requirements are specified in Table 8.2.1.2.4-2, with the addition of parameters in Table 8.2.1.2.4-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of transmit diversity (SFBC) with 2 transmit antennas when the PDSCH transmission in the serving cell is interfered by PDSCH of two dominant interfering cells applying transmission mode 3 interference model defined in clause B.5.2. In Table 8.2.1.2.4-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.2.4-1: Test Parameters for Transmit diversity Performance (FRC) with TM3 interference model Table 8.2.1.2.4-2: Enhanced Performance Requirement Type A, Transmit Diversity (FRC) with TM3 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.2.4 |
6,258 | 9.11.3.88 ProSe relay transaction identity | The purpose of the ProSe relay transaction identity (PRTI) information element is to uniquely identify an authentication and key agreement procedure for 5G ProSe UE-to-network relay or 5G ProSe UE-to-UE relay. The PRTI allows distinguishing up to 254 different bi-directional messages. The ProSe relay transaction identity information element is coded as shown in figure 9.11.3.88.1 and table 9.11.3.88.1. The ProSe relay transaction identity is a type 3 information element with a length of 2 octets. Figure 9.11.3.88.1: ProSe relay transaction identity information element Table 9.11.3.88.1: ProSe relay transaction identity 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.88 |
6,259 | 5.5.2.3.2 Network initiated detach procedure completion by the UE | When receiving the DETACH REQUEST message and the detach type indicates "re-attach required", the UE shall deactivate the EPS bearer context(s), if any, including the default EPS bearer context locally without peer-to-peer signalling between the UE and the MME. The UE shall stop the timer T3346, if it is running. The UE shall also stop timer(s) T3396 and ESM back-off timer(s) not related to congestion control (see clause 6.3.6), if running. If the UE is operating in single-registration mode, the UE shall also stop 5GSM back-off timer(s) not related to congestion control (see clause 6.2.12 in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54]), if running. The UE shall send a DETACH ACCEPT message to the network and enter the state EMM-DEREGISTERED. Furthermore, the UE shall, after the completion of the detach procedure, and the release of the existing NAS signalling connection, initiate an attach or combined attach procedure. The UE shall enable N1 mode capability for 3GPP access if it was previously disabled (see 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54]) and the UE is configured with the "Re_enable_N1_upon_reattach" leaf of the NAS configuration MO which indicates the "re-enabling N1 mode capability when performing re-attach" is enabled (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A]). The UE should also re-establish any previously established PDN connection(s). NOTE 1: When the detach type indicates "re-attach required", user interaction is necessary in some cases when the UE cannot re-activate the EPS bearer(s), if any, automatically. A UE which receives a DETACH REQUEST message with detach type indicating "re-attach required" or "re-attach not required" and no EMM cause IE, is detached only for EPS services. When receiving the DETACH REQUEST message and the detach type indicates "IMSI detach", the UE shall not deactivate the EPS bearer context(s) including the default EPS bearer context. The UE shall set the MM update status to U2 NOT UPDATED. A UE may send a DETACH ACCEPT message to the network, and shall re-attach to non-EPS services by performing the combined tracking area updating procedure according to clause 5.5.3.3, sending a TRACKING AREA UPDATE REQUEST message with EPS update type IE indicating "combined TA/LA updating with IMSI attach". If the UE is attached for EPS and non-EPS services, then the UE shall set the update status to U2 NOT UPDATED if: - the Detach type IE indicates "re-attach required"; or - the Detach type IE indicates "re-attach not required" and no EMM cause IE is included. When receiving the DETACH REQUEST message and the detach type indicates "re-attach not required" and no EMM cause IE, or "re-attach not required" and the EMM cause value is not #2 "IMSI unknown in HSS", the UE shall deactivate the EPS bearer context(s), if any, including the default EPS bearer context locally without peer-to-peer signalling between the UE and the MME. The UE shall then send a DETACH ACCEPT message to the network and enter state EMM-DEREGISTERED. Regardless of the EMM cause value received in the DEREGISTRATION REQUEST message via satellite E-UTRAN, - if the UE receives the Forbidden TAI(s) for the list of "forbidden tracking areas for roaming" IE in the DETACH REQUEST message, the UE shall store the TAI(s) included in the IE which are belonging to the serving PLMN or equivalent PLMN(s), if not already stored, into the list of "forbidden tracking areas for roaming" and ignore the TAI(s) which do not belong to the serving PLMN or equivalent PLMN(s); and - if the UE receives the Forbidden TAI(s) for the list of "forbidden tracking areas for regional provision of service" IE in the DETACH REQUEST message, the UE shall store the TAI(s) included in the IE which are belonging to the serving PLMN or equivalent PLMN(s), if not already stored, into the list of "forbidden tracking areas for regional provision of service" and ignore the TAI(s) which do not belong to the serving PLMN or equivalent PLMN(s). If the detach type indicates "IMSI detach" or "re-attach required", then the UE shall ignore the EMM cause IE if received. If the detach type indicates "re-attach not required", the UE shall take the following actions depending on the received EMM cause value: #2 (IMSI unknown in HSS); The UE shall handle the MM parameters update status, TMSI, LAI and ciphering key sequence number as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when a DETACH REQUEST is received with the GMM cause with the same value and with detach type set to "re-attach not required". The USIM shall be considered as invalid for non-EPS services until switching off or the UICC containing the USIM is removed or the timer T3245 expires as described in clause 5.3.7a. If the UE maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the UE shall set this counter to UE implementation-specific maximum value. The UE is still attached for EPS services in the network. #3 (Illegal UE); #6 (Illegal ME); or #8 (EPS services and non-EPS services not allowed); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and KSI. The UE shall consider the USIM as invalid for EPS services until switching off or the UICC containing the USIM is removed or the timer T3245 expires as described in clause 5.3.7a. The UE shall delete the list of equivalent PLMNs and shall enter the state EMM-DEREGISTERED.NO-IMSI. If the UE maintains a counter for "SIM/USIM considered invalid for GPRS services", then the UE shall set this counter to UE implementation-specific maximum value. If the UE maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the UE shall set this counter to UE implementation-specific maximum value. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the MM parameters update status, TMSI, LAI and ciphering key sequence number and the GMM parameters GMM state, RAI, P-TMSI, P-TMSI signature, GPRS ciphering key sequence number and GPRS update status as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when a DETACH REQUEST is received with the GMM cause with the same value and with detach type set to "re-attach not required". The USIM shall also be considered as invalid for non-EPS services until switching off or the UICC containing the USIM is removed or the timer T3245 expires as described in clause 5.3.7a. For the EMM cause value #3 or #6, if the UE is operating in single-registration mode, the UE shall handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list and ngKSI as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when a DEREGISTRATION REQUEST is received over 3GPP access with the 5GMM cause with the same value, with de-registration type set to "re-registration not required" and with access type set to "3GPP access". For the EMM cause value #8, if the UE is operating in single-registration mode, the UE shall in addition set the 5GMM state to 5GMM-DEREGISTERED, 5GS update status to 5U3 ROAMING NOT ALLOWED, and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. NOTE 2: The possibility to configure a UE so that the radio transceiver for a specific radio access technology is not active, although it is implemented in the UE, is out of scope of the present specification. #7 (EPS services not allowed); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and KSI. The UE shall consider the USIM as invalid for EPS services until switching off or the UICC containing the USIM is removed or the timer T3245 expires as described in clause 5.3.7a. The UE shall enter the state EMM-DEREGISTERED. If the UE maintains a counter for "SIM/USIM considered invalid for GPRS services", then the UE shall set this counter to UE implementation-specific maximum value. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM parameters GMM state, RAI, P-TMSI, P-TMSI signature, GPRS ciphering key sequence number and GPRS update status as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when a DETACH REQUEST is received with the GMM cause with the same value and with detach type set to "re-attach not required". A UE operating in CS/PS mode 1 or CS/PS mode 2 of operation which is IMSI attached for non-EPS services is still IMSI attached for non-EPS services in the network. The UE operating in CS/PS mode 1 or CS/PS mode 2 of operation shall set the update status to U2 NOT UPDATED, shall attempt to select GERAN or UTRAN access technology and shall proceed with the appropriate MM specific procedure according to the MM service state. The UE shall not reselect E-UTRAN radio access technology until switching off or the UICC containing the USIM is removed. If the UE is operating in single-registration mode, the UE shall handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list and ngKSI as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when a DEREGISTRATION REQUEST is received over 3GPP access with the 5GMM cause with the same value, with de-registration type set to "re-registration not required" and with access type set to "3GPP access". #11 (PLMN not allowed); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and KSI. The UE shall delete the list of equivalent PLMNs, shall reset the attach attempt counter and enter the state EMM-DEREGISTERED.PLMN-SEARCH. The UE shall store the PLMN identity in the "forbidden PLMN list" and if the UE is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) then the UE shall start timer T3245 and proceed as described in clause 5.3.7a. If the message has been successfully integrity checked by the NAS and the UE maintains a PLMN-specific attempt counter for that PLMN, then the UE shall set this counter to the UE implementation-specific maximum value. The UE shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the MM parameters update status, TMSI, LAI and ciphering key sequence number and the GMM parameters GMM state, RAI, P-TMSI, P-TMSI signature, GPRS ciphering key sequence number, GPRS update status and GPRS attach attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when a DETACH REQUEST is received with the GMM cause with the same value and with detach type set to "re-attach not required". If the UE is operating in single-registration mode, the UE shall handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list, ngKSI and registration attempt counter as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when a DEREGISTRATION REQUEST is received over 3GPP access with the 5GMM cause with the same value, with de-registration type set to "re-registration not required" and with access type set to "3GPP access". #12 (Tracking area not allowed); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and KSI. The UE shall reset the attach attempt counter and shall enter the state EMM-DEREGISTERED.LIMITED-SERVICE. The UE shall store the current TAI in the list of "forbidden tracking areas for regional provision of service". If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM parameters GMM state, RAI, P-TMSI, P-TMSI signature, GPRS ciphering key sequence number, GPRS update status and GPRS attach attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when a DETACH REQUEST is received with the GMM cause with the same value and with detach type set to "re-attach not required". If the UE is IMSI attached for non-EPS services, the UE shall in addition handle the MM parameters update status, TMSI, LAI, ciphering key sequence number and location update attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when a DETACH REQUEST is received with the GMM cause with the same value and with detach type set to "re-attach not required". If the UE is operating in single-registration mode, the UE shall handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list and ngKSI as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when a DEREGISTRATION REQUEST is received over 3GPP access with the 5GMM cause with the same value, with de-registration type set to "re-registration not required" and with access type set to "3GPP access". #13 (Roaming not allowed in this tracking area); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and KSI. The UE shall delete the list of equivalent PLMNs, reset the attach attempt counter and shall change to state EMM-DEREGISTERED.PLMN-SEARCH. The UE shall store the current TAI in the list of "forbidden tracking areas for roaming". The UE shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6] If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM parameters GMM state, RAI, P-TMSI, P-TMSI signature, GPRS ciphering key sequence number, GPRS update status and GPRS attach attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when a DETACH REQUEST is received with the GMM cause with the same value and with detach type set to "re-attach not required". If the UE is IMSI attached for non-EPS services, the UE shall in addition handle the MM parameters update status, TMSI, LAI, ciphering key sequence number and location update attempt counter and as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when a DETACH REQUEST is received with the GMM cause with the same value and with detach type set to "re-attach not required". If the UE is operating in single-registration mode, the UE shall handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list, ngKSI and registration attempt counter as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when a DEREGISTRATION REQUEST is received over 3GPP access with the 5GMM cause with the same value, with de-registration type set to "re-registration not required" and with access type set to "3GPP access". #14 (EPS services not allowed in this PLMN); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3). Furthermore, the UE shall delete any GUTI, last visited registered TAI, TAI list and KSI. The UE shall reset the attach attempt counter and shall enter the state EMM-DEREGISTERED.PLMN-SEARCH. The UE shall store the PLMN identity in the "forbidden PLMNs for GPRS service" list and if the UE is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) then the UE shall start timer T3245 and proceed as described in clause 5.3.7a. If the message has been successfully integrity checked by the NAS and the UE maintains a PLMN-specific PS-attempt counter for that PLMN, then the UE shall set this counter to the UE implementation-specific maximum value. A UE in PS mode 1 or PS mode 2 of operation shall delete the list of equivalent PLMNs and perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. A UE operating in CS/PS mode 1 or CS/PS mode 2 of operation which is IMSI attached for non-EPS services is still IMSI attached for non-EPS services and shall set the update status to U2 NOT UPDATED. A UE operating in CS/PS mode 1 of operation and supporting A/Gb mode or Iu mode may select GERAN or UTRAN radio access technology and proceed with the appropriate MM specific procedure according to the MM service state. In this case, the UE shall disable the E-UTRA capability (see clause 4.5). A UE operating in CS/PS mode 1 of operation and supporting A/Gb mode or Iu mode may perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. A UE operating in CS/PS mode 1 of operation and supporting S1 mode only or operating in CS/PS mode 2 of operation shall delete the list of equivalent PLMNs and shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM parameters GMM state, GPRS update status, RAI, P-TMSI, P-TMSI signature, GPRS ciphering key sequence number and GPRS attach attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when a DETACH REQUEST is received with the GMM cause with the same value and with detach type set to "re-attach not required". If the UE is operating in single-registration mode, the UE shall in addition set the 5GMM state to 5GMM-DEREGISTERED, 5GS update status to 5U3 ROAMING NOT ALLOWED, and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. Additionally, the UE shall reset the registration attempt counter. #15 (No suitable cells in tracking area); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and KSI. The UE shall reset the attach attempt counter and shall enter the state EMM-DEREGISTERED.LIMITED-SERVICE. The UE shall store the current TAI in the list of "forbidden tracking areas for roaming". The UE shall search for a suitable cell in another tracking area or in another location area according to 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM parameters GMM state, RAI, P-TMSI, P-TMSI signature, GPRS ciphering key sequence number, GPRS update status and GPRS attach attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when a DETACH REQUEST is received with the GMM cause with the same value and with detach type set to "re-attach not required". If the UE is IMSI attached for non-EPS services, the UE shall in addition handle the MM parameters update status, TMSI, LAI, ciphering key sequence number and location update attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when a DETACH REQUEST is received with the GMM cause with the same value and with detach type set to "re-attach not required". If the UE is operating in single-registration mode, the UE shall handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list, ngKSI and registration attempt counter as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when a DEREGISTRATION REQUEST is received over 3GPP access with the 5GMM cause with the same value, with de-registration type set to "re-registration not required" and with access type set to "3GPP access". #25 (Not authorized for this CSG); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3). The UE shall reset the attach attempt counter and shall enter the state EMM-DEREGISTERED.LIMITED-SERVICE. If the cell where the UE has received the DETACH REQUEST message is a CSG cell and the CSG ID and associated PLMN identity of the cell are contained in the Allowed CSG list, the UE shall remove the entry corresponding to this CSG ID and associated PLMN identity from the Allowed CSG list. If the cell where the UE has received the DETACH REQUEST message is a CSG cell and the CSG ID and associated PLMN identity of the cell are contained in the Operator CSG list, the UE shall apply the procedures defined in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6] clause 3.1A. The UE shall search for a suitable cell according to 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM parameters GMM state, GPRS update status and GPRS attach attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when a DETACH REQUEST is received with GMM cause with the same value and with detach type set to "re-attach not required". If the UE is IMSI attached for non-EPS services, the UE shall in addition handle the MM parameters update status and location update attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when a DETACH REQUEST is received with the GMM cause with the same value and with detach type set to "re-attach not required". If the UE is operating in single-registration mode, the UE shall in addition set the 5GMM state to 5GMM-DEREGISTERED and set the 5GS update status to 5U3 ROAMING NOT ALLOWED and reset the registration attempt counter. #78 (PLMN not allowed to operate at the present UE location). This cause value received from a non-satellite E-UTRA cell is considered as an abnormal case and the behaviour of the UE is specified in clause 5.5.2.3.4. The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. Additionally, the UE shall reset the registration attempt counter. The UE shall store the PLMN identity and, if it is known, the current geographical location in the list of "PLMNs not allowed to operate at the present UE location", start a corresponding timer instance (see clause 4.11.2), enter state EMM-DEREGISTERED.PLMN-SEARCH and perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. If the UE is operating in single-registration mode, the UE shall in addition set the 5GMM state to 5GMM-DEREGISTERED, 5GS update status to 5U3 ROAMING NOT ALLOWED, and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. Additionally, the UE shall reset the registration attempt counter. #36 (IAB-node operation not authorized); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. The UE shall delete the list of equivalent PLMNs and enter the state EMM-DEREGISTERED.PLMN-SEARCH. The UE shall store the PLMN identity in the "forbidden PLMN list" and if the UE is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) then the UE shall start timer T3245 and proceed as described in subclause 5.3.7a. If the message has been successfully integrity checked by the NAS and the UE maintains a PLMN-specific attempt counter for that PLMN, then the UE shall set this counter to the UE implementation-specific maximum value. The UE shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list and ngKSI as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when a DEREGISTRATION REQUEST over 3GPP access is received with the 5GMM cause with the same value , with de-registration type set to "re-registration not required" and with access type set to "3GPP access". Other EMM cause values or if no EMM cause IE is included is considered as abnormal cases. The behaviour of the UE in those cases is described in clause 5.5.2.3.4. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.2.3.2 |
6,260 | 9.3.27 Status | This message is sent by the mobile station or the network at any time during a call to report certain error conditions listed in clause 8. It shall also be sent in response to a STATUS ENQUIRY message. See table 9.74/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: STATUS Significance: local Direction: both Table 9.74/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : STATUS message content | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.3.27 |
6,261 | 4.6.3.6 Session management for partial network slice | If the S-NSSAI is included in the partially allowed NSSAI and: a) if the current TAI is in the list of TAs for which the S-NSSAI is allowed, the UE can initiate the UE-requested PDU session establishment procedure for the S-NSSAI; or b) if the current TAI is not in the list of TAs for which the S-NSSAI is allowed, the UE shall not initiate the UE-requested PDU session establishment procedure for the S-NSSAI. If an existing PDU session is established for the S-NSSAI included in the partially allowed NSSAI and: a) if the current TAI is changed and the current TAI is in the list of TAs for which the S-NSSAI is allowed, the UE can initiate the service request procedure to re-establish the user plane resources for the established PDU session or the UE can initiate UL NAS TRANSPORT messages carrying control plane user data or the SMF can send control plane user data to the UE; or b) if the current TAI is changed and the current TAI is not in the list of TAs for which the S-NSSAI is allowed, the SMF and the UE shall maintain the 5GSM contexts for the established PDU session. The UE shall not initiate UL NAS TRANSPORT messages carrying control plane user data and the SMF shall not send control plane user data to the UE. The session management for partial network slice is not applicable to the PDU session established for onboarding services in SNPN. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.6.3.6 |
6,262 | 5.10.1.2 Multicast MCCH scheduling | The multicast MCCH information (i.e. information transmitted in messages sent over multicast MCCH) is transmitted periodically, using a configurable repetition period and within a configured transmission window. MCCH transmissions (and the associated radio resources and MCS) are indicated via the PDCCH addressed to Multicast MCCH-RNTI. PDCCH monitoring occasion(s) for the multicast MCCH transmission are determined according to the common search space indicated by searchspaceMulticastMCCH. If searchspaceMulticastMCCH is set to zero, PDCCH monitoring occasions for the multicast MCCH message reception in the multicast MCCH transmission window are the same as PDCCH monitoring occasions for SIB1 where the mapping between PDCCH monitoring occasions and SSBs is specified in TS 38.213[ NR; Physical layer procedures for control ] [13]. If searchspaceMulticastMCCH is not set to zero, PDCCH monitoring occasions for the multicast MCCH message are determined based on search space indicated by searchspaceMulticastMCCH. PDCCH monitoring occasions for the multicast MCCH message which are not overlapping with UL symbols (determined according to tdd-UL-DL-ConfigurationCommon) are sequentially numbered from one in the multicast MCCH transmission window. The [xΓN+K]th PDCCH monitoring occasion for the multicast MCCH message in the multicast MCCH transmission window corresponds to the Kth transmitted SSB, where x = 0, 1, ...X-1, K = 1, 2, β¦N, N is the number of actual transmitted SSBs determined according to ssb-PositionsInBurst in SIB1 and X is equal to CEIL(number of PDCCH monitoring occasions in multicast MCCH transmission window/N). The actual transmitted SSBs are sequentially numbered from one in ascending order of their SSB indexes. The UE assumes that, in the multicast MCCH transmission window, PDCCH for a multicast MCCH message is transmitted in at least one PDCCH monitoring occasion corresponding to each transmitted SSB and thus the selection of SSB for the reception multicast MCCH messages is up to UE implementation. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.10.1.2 |
6,263 | β PDSCH-Config | The PDSCH-Config IE is used to configure the UE specific PDSCH parameters. If this IE is used for MBS CFR, the following fields shall be absent: tci-StatesToAddModList, tci-StatesToReleaseList, zp-CSI-RS-ResourceToAddModList, minimumSchedulingOffsetK0, antennaPortsFieldPresenceDCI-1-2, aperiodicZP-CSI-RS-ResourceSetsToAddModListDCI-1-2, aperiodicZP-CSI-RS-ResourceSetsToReleaseListDCI-1-2, dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2, dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2, dmrs-SequenceInitializationDCI-1-2, harq-ProcessNumberSizeDCI-1-2, mcs-TableDCI-1-2, numberOfBitsForRV-DCI-1-2, pdsch-AggregationFactor, pdsch-TimeDomainAllocationListDCI-1-2, prb-BundlingTypeDCI-1-2, priorityIndicatorDCI-1-2, rateMatchPatternGroup1DCI-1-2, rateMatchPatternGroup2DCI-1-2, resourceAllocationType1GranularityDCI-1-2, vrb-ToPRB-InterleaverDCI-1-2, referenceOfSLIVDCI-1-2, resourceAllocationDCI-1-2, dataScramblingIdentityPDSCH2-r16, repetitionSchemeConfig, pdsch-ConfigDCI-1-3. PDSCH-Config information element -- ASN1START -- TAG-PDSCH-CONFIG-START PDSCH-Config ::= SEQUENCE { dataScramblingIdentityPDSCH INTEGER (0..1023) OPTIONAL, -- Need S dmrs-DownlinkForPDSCH-MappingTypeA SetupRelease { DMRS-DownlinkConfig } OPTIONAL, -- Need M dmrs-DownlinkForPDSCH-MappingTypeB SetupRelease { DMRS-DownlinkConfig } OPTIONAL, -- Need M tci-StatesToAddModList SEQUENCE (SIZE(1..maxNrofTCI-States)) OF TCI-State OPTIONAL, -- Need N tci-StatesToReleaseList SEQUENCE (SIZE(1..maxNrofTCI-States)) OF TCI-StateId OPTIONAL, -- Need N vrb-ToPRB-Interleaver ENUMERATED {n2, n4} OPTIONAL, -- Need S resourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch}, pdsch-TimeDomainAllocationList SetupRelease { PDSCH-TimeDomainResourceAllocationList } OPTIONAL, -- Need M pdsch-AggregationFactor ENUMERATED { n2, n4, n8 } OPTIONAL, -- Need S rateMatchPatternToAddModList SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPattern OPTIONAL, -- Need N rateMatchPatternToReleaseList SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPatternId OPTIONAL, -- Need N rateMatchPatternGroup1 RateMatchPatternGroup OPTIONAL, -- Need R rateMatchPatternGroup2 RateMatchPatternGroup OPTIONAL, -- Need R rbg-Size ENUMERATED {config1, config2}, mcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S maxNrofCodeWordsScheduledByDCI ENUMERATED {n1, n2} OPTIONAL, -- Need R prb-BundlingType CHOICE { staticBundling SEQUENCE { bundleSize ENUMERATED { n4, wideband } OPTIONAL -- Need S }, dynamicBundling SEQUENCE { bundleSizeSet1 ENUMERATED { n4, wideband, n2-wideband, n4-wideband } OPTIONAL, -- Need S bundleSizeSet2 ENUMERATED { n4, wideband } OPTIONAL -- Need S } }, zp-CSI-RS-ResourceToAddModList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-Resources)) OF ZP-CSI-RS-Resource OPTIONAL, -- Need N zp-CSI-RS-ResourceToReleaseList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-Resources)) OF ZP-CSI-RS-ResourceId OPTIONAL, -- Need N aperiodic-ZP-CSI-RS-ResourceSetsToAddModList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSet OPTIONAL, -- Need N aperiodic-ZP-CSI-RS-ResourceSetsToReleaseList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSetId OPTIONAL, -- Need N sp-ZP-CSI-RS-ResourceSetsToAddModList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSet OPTIONAL, -- Need N sp-ZP-CSI-RS-ResourceSetsToReleaseList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSetId OPTIONAL, -- Need N p-ZP-CSI-RS-ResourceSet SetupRelease { ZP-CSI-RS-ResourceSet } OPTIONAL, -- Need M ..., [[ maxMIMO-Layers-r16 SetupRelease { MaxMIMO-LayersDL-r16 } OPTIONAL, -- Need M minimumSchedulingOffsetK0-r16 SetupRelease { MinSchedulingOffsetK0-Values-r16 } OPTIONAL, -- Need M -- Start of the parameters for DCI format 1_2 introduced in V16.1.0 antennaPortsFieldPresenceDCI-1-2-r16 ENUMERATED {enabled} OPTIONAL, -- Need S aperiodicZP-CSI-RS-ResourceSetsToAddModListDCI-1-2-r16 SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSet OPTIONAL, -- Need N aperiodicZP-CSI-RS-ResourceSetsToReleaseListDCI-1-2-r16 SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSetId OPTIONAL, -- Need N dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2-r16 SetupRelease { DMRS-DownlinkConfig } OPTIONAL, -- Need M dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2-r16 SetupRelease { DMRS-DownlinkConfig } OPTIONAL, -- Need M dmrs-SequenceInitializationDCI-1-2-r16 ENUMERATED {enabled} OPTIONAL, -- Need S harq-ProcessNumberSizeDCI-1-2-r16 INTEGER (0..4) OPTIONAL, -- Need R mcs-TableDCI-1-2-r16 ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S numberOfBitsForRV-DCI-1-2-r16 INTEGER (0..2) OPTIONAL, -- Need R pdsch-TimeDomainAllocationListDCI-1-2-r16 SetupRelease { PDSCH-TimeDomainResourceAllocationList-r16 } OPTIONAL, -- Need M prb-BundlingTypeDCI-1-2-r16 CHOICE { staticBundling-r16 SEQUENCE { bundleSize-r16 ENUMERATED { n4, wideband } OPTIONAL -- Need S }, dynamicBundling-r16 SEQUENCE { bundleSizeSet1-r16 ENUMERATED { n4, wideband, n2-wideband, n4-wideband } OPTIONAL, -- Need S bundleSizeSet2-r16 ENUMERATED { n4, wideband } OPTIONAL -- Need S } } OPTIONAL, -- Need R priorityIndicatorDCI-1-2-r16 ENUMERATED {enabled} OPTIONAL, -- Need S rateMatchPatternGroup1DCI-1-2-r16 RateMatchPatternGroup OPTIONAL, -- Need R rateMatchPatternGroup2DCI-1-2-r16 RateMatchPatternGroup OPTIONAL, -- Need R resourceAllocationType1GranularityDCI-1-2-r16 ENUMERATED {n2,n4,n8,n16} OPTIONAL, -- Need S vrb-ToPRB-InterleaverDCI-1-2-r16 ENUMERATED {n2, n4} OPTIONAL, -- Need S referenceOfSLIVDCI-1-2-r16 ENUMERATED {enabled} OPTIONAL, -- Need S resourceAllocationDCI-1-2-r16 ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch} OPTIONAL, -- Need M -- End of the parameters for DCI format 1_2 introduced in V16.1.0 priorityIndicatorDCI-1-1-r16 ENUMERATED {enabled} OPTIONAL, -- Need S dataScramblingIdentityPDSCH2-r16 INTEGER (0..1023) OPTIONAL, -- Need R pdsch-TimeDomainAllocationList-r16 SetupRelease { PDSCH-TimeDomainResourceAllocationList-r16 } OPTIONAL, -- Need M repetitionSchemeConfig-r16 SetupRelease { RepetitionSchemeConfig-r16} OPTIONAL -- Need M ]], [[ repetitionSchemeConfig-v1630 SetupRelease { RepetitionSchemeConfig-v1630} OPTIONAL -- Need M ]], [[ pdsch-HARQ-ACK-OneShotFeedbackDCI-1-2-r17 ENUMERATED {enabled} OPTIONAL, -- Need R pdsch-HARQ-ACK-EnhType3DCI-1-2-r17 ENUMERATED {enabled} OPTIONAL, -- Need R pdsch-HARQ-ACK-EnhType3DCI-Field-1-2-r17 ENUMERATED {enabled} OPTIONAL, -- Need R pdsch-HARQ-ACK-RetxDCI-1-2-r17 ENUMERATED {enabled} OPTIONAL, -- Need R pucch-sSCellDynDCI-1-2-r17 ENUMERATED {enabled} OPTIONAL, -- Need R dl-OrJointTCI-StateList-r17 CHOICE { explicitlist SEQUENCE { dl-OrJointTCI-StateToAddModList-r17 SEQUENCE (SIZE (1..maxNrofTCI-States)) OF TCI-State OPTIONAL, -- Need N dl-OrJointTCI-StateToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofTCI-States)) OF TCI-StateId OPTIONAL -- Need N }, unifiedTCI-StateRef-r17 ServingCellAndBWP-Id-r17 } OPTIONAL, -- Need R beamAppTime-r17 ENUMERATED {n1, n2, n4, n7, n14, n28, n42, n56, n70, n84, n98, n112, n224, n336, spare2, spare1} OPTIONAL, -- Need R dummy SetupRelease { Dummy-TDRA-List } OPTIONAL, -- Need M dmrs-FD-OCC-DisabledForRank1-PDSCH-r17 ENUMERATED {true} OPTIONAL, -- Need R minimumSchedulingOffsetK0-r17 SetupRelease { MinSchedulingOffsetK0-Values-r17 } OPTIONAL, -- Need M harq-ProcessNumberSizeDCI-1-2-v1700 INTEGER (0..5) OPTIONAL, -- Need R harq-ProcessNumberSizeDCI-1-1-r17 INTEGER (5) OPTIONAL, -- Need R mcs-Table-r17 ENUMERATED {qam1024} OPTIONAL, -- Need R mcs-TableDCI-1-2-r17 ENUMERATED {qam1024} OPTIONAL, -- Need R xOverheadMulticast-r17 ENUMERATED {xOh6, xOh12, xOh18} OPTIONAL, -- Need S priorityIndicatorDCI-4-2-r17 ENUMERATED {enabled} OPTIONAL, -- Need S sizeDCI-4-2-r17 INTEGER (20..maxDCI-4-2-Size-r17) OPTIONAL -- Need R ]], [[ pdsch-TimeDomainAllocationListForMultiPDSCH-r17 SetupRelease { MultiPDSCH-TDRA-List-r17 } OPTIONAL -- Need M ]], [[ advancedReceiver-MU-MIMO-r18 SetupRelease { AdvancedReceiver-MU-MIMO-r18 } OPTIONAL, -- Need M pdsch-ConfigDCI-1-3-r18 SetupRelease { PDSCH-ConfigDCI-1-3-r18 } OPTIONAL -- Need M ]] } RateMatchPatternGroup ::= SEQUENCE (SIZE (1..maxNrofRateMatchPatternsPerGroup)) OF CHOICE { cellLevel RateMatchPatternId, bwpLevel RateMatchPatternId } MinSchedulingOffsetK0-Values-r16 ::= SEQUENCE (SIZE (1..maxNrOfMinSchedulingOffsetValues-r16)) OF INTEGER (0..maxK0-SchedulingOffset-r16) MinSchedulingOffsetK0-Values-r17 ::= SEQUENCE (SIZE (1..maxNrOfMinSchedulingOffsetValues-r16)) OF INTEGER (0..maxK0-SchedulingOffset-r17) MaxMIMO-LayersDL-r16 ::= INTEGER (1..8) PDSCH-ConfigDCI-1-3-r18 ::= SEQUENCE { resourceAllocationDCI-1-3-r18 ENUMERATED {resourceAllocationType0, resourceAllocationType1, dynamicSwitch} OPTIONAL, -- Need M rbg-SizeDCI-1-3-r18 ENUMERATED {config1, config2, config3} OPTIONAL, -- Cond DCI-1-3 resourceAllocationType1GranularityDCI-1-3-r18 ENUMERATED {n2,n4,n8,n16} OPTIONAL, -- Need S numberOfBitsForRV-DCI-1-3-r18 INTEGER (0..2) OPTIONAL, -- Need R harq-ProcessNumberSizeDCI-1-3-r18 INTEGER (0..5) OPTIONAL -- Need R } -- TAG-PDSCH-CONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
6,264 | 4.15.6.13.4 Procedure for Revoking a Multi-member AF session with required QoS | Figure 4.15.6.13.4-1: Procedure for revoking a Multi-member AF session with required QoS 1. The AF sends a request to revoke the allocated resources for the traffic flows for the communication between a set of UEs and an AF, using Nnef_AFsessionWithQoS_Revoke request message (Transaction Reference ID). 2. The NEF authorizes the AF request. Steps 3-5 apply for each UE address in the list of UE addresses associated with the Transaction Reference ID: 3. The NEF sends the Npcf_PolicyAuthorization_Delete request as described in clause 5.2.5.3.4 to the PCF. 4. The PCF proceeds with the SM Policy Association Modifications procedure as defined in clause 4.16.5.2. If the NEF has subscribed to notifications (e.g. on resource allocation status, QoS Monitoring of UL and/or DL data rate) for the UE address in the Multi-member AF session, the subscription is also removed. 5. The PCF sends the Npcf_PolicyAuthorization_Delete response message to the NEF. 6. The NEF sends the Nnef_AFsessionWithQoS_Revoke response message (Transaction Reference ID) to the AF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.6.13.4 |
6,265 | 4.5.1.3.4 Paging response for CS fallback | The network may initiate the paging procedure for CS services when the MS is IMSI attached for CS services via EMM combined procedures, as described in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120]. At reception of an indication of paging for CS services from EMM, the MS shall stop timer T3246, if it is running. The MM sublayer in the MS requests EMM to perform the service request procedure for CS fallback. After the MS changes to a GERAN or UTRAN cell, the MS shall: - In A/Gb mode: ask for the establishment of an RR connection and proceed as if a paging has been received in the lower layers; - In Iu mode: ask for the establishment of an RRC connection and 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 determines, before sending the response to paging, that it is in a different location area than the stored location area, the MS shall initiate a normal location updating procedure first, regardless of Network Mode of Operation. Additionally the MS performs routing area updating as specified in subclause 4.7.5. If the location area of the current cell is not available, the MS may initiate a normal location updating procedure directly. When initiating the location updating procedure, the MS shall indicate "CS fallback mobile terminating call" in the Additional update parameters IE and the MS shall not include the MS network feature support IE. The MM connection establishment is delayed until successful completion of the normal location updating procedure. After the completion of the normal location updating procedure, the MS shall not send the PAGING RESPONSE message. NOTE: For the race condition when the mobile station has a CM application request pending, the mobile station also indicates that it has a follow-on request pending. | 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.4 |
6,266 | A.4.3.4 Typical examples of non critical extension at the end of a message | The following example illustrates the use of non-critical extensions at the end of the message or at the end of a field that is contained in a BIT or OCTET STRING i.e. when an empty sequence is used. -- /example/ ASN1START RRCMessage-r8-IEs ::= SEQUENCE { field1 InformationElement1, field2 InformationElement2, field3 InformationElement3 OPTIONAL, -- Need N nonCriticalExtension RRCMessage-v860-IEs OPTIONAL } RRCMessage-v860-IEs ::= SEQUENCE { field4-v860 InformationElement4 OPTIONAL, -- Need S field5-v860 BOOLEAN OPTIONAL, -- Cond C54 nonCriticalExtension RRCMessage-v940-IEs OPTIONAL } RRCMessage-v940-IEs ::= SEQUENCE { field6-v940 InformationElement6-r9 OPTIONAL, -- Need R nonCriticalExtensions SEQUENCE {} OPTIONAL } -- ASN1STOP Some remarks regarding the extensions shown in the above example: β The InformationElement4 is introduced in the original version of the protocol (release 8) and hence no suffix is used. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | A.4.3.4 |
6,267 | 6.6.2F.3 Adjacent Channel Leakage Ratio for category NB1 and NB2 | Adjacent Channel Leakage power Ratio is the ratio of the filtered mean power centred on the assigned channel frequency to the filtered mean power centred on an adjacent channel frequency. The assigned category NB1or NB2 channel power and adjacent channel power are measured with filters and measurement bandwidths specified in Table 6.6.2F.3-1. If the measured adjacent channel power is greater than β50dBm then the category NB1 or NB2 UE ACLR shall be higher than the value specified in Table 6.6.2F.3-1. GSMACLR requirement is intended for protection of GSM system. UTRAACLR requirement is intended for protection of UTRA and E-UTRA systems. Table 6.6.2F.3-1: category NB1 and NB2 UE ACLR 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 | 6.6.2F.3 |
6,268 | Annex H (normative): Usage of the AMF | The 16 bits in the AMF are numbered from "0" to "15" where bit "0" is the most significant bit and bit "15" is the least significant bit (see subclause 3.4) Bit "0" is called the "AMF separation bit". It is used for the purposes of EPS (Evolved Packet System) and is specified in - TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [28] for E-UTRAN access to EPS; - TS 33.402[ 3GPP System Architecture Evolution (SAE); Security aspects of non-3GPP accesses ] [29] for non-3GPP access to EPS; - TS 33.501[ Security architecture and procedures for 5G System ] [42] for 5G-RAN access to 5G System. Bits "1" to "7" are reserved for future standardization use. Bits "1" to "7" shall be set to 0 while not yet specified for a particular use. Bits "8" to "15" can be used for proprietary purposes. See Annex F for examples usages. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | Annex |
6,269 | 5.7.2.2 ARP | The QoS parameter ARP contains information about the priority level, the pre-emption capability and the pre-emption vulnerability. This allows deciding whether a QoS Flow establishment/modification/handover may be accepted or needs to be rejected in the case of resource limitations (typically used for admission control of GBR traffic). It may also be used to decide which existing QoS Flow to pre-empt during resource limitations, i.e. which QoS Flow to release to free up resources. The ARP priority level defines the relative importance of a QoS Flow. The range of the ARP priority level is 1 to 15 with 1 as the highest priority. The ARP priority levels 1-8 should only be assigned to QoS Flows for services that are authorized to receive prioritized treatment within an operator domain (i.e. that are authorized by the serving network). The ARP priority levels 9-15 may be assigned to QoS Flows for services that are authorized by the home network and thus applicable when a UE is roaming. NOTE: This ensures that future releases may use ARP priority level 1-8 to indicate e.g. emergency and other priority services within an operator domain in a backward compatible manner. This does not prevent the use of ARP priority level 1-8 in roaming situation in the case that appropriate roaming agreements exist that ensure a compatible use of these priority levels. The ARP pre-emption capability defines whether a QoS Flow may get resources that were already assigned to another QoS Flow with a lower priority. The ARP pre-emption vulnerability defines whether a QoS Flow may lose the resources assigned to it in order to admit a QoS Flow with higher priority. The ARP pre-emption capability and the ARP pre-emption vulnerability shall be either set to 'enabled' or 'disabled'. The ARP pre-emption vulnerability of the QoS Flow which the default QoS rule is associated with should be set appropriately to minimize the risk of a release of this QoS Flow. The details of how the SMF sets the ARP for a QoS Flow are further described in clause 5.7.2.7. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7.2.2 |
6,270 | 4.11.4.2 Handover from 5GS to EPC/ePDG | Figure 4.11.4.2-1: Handover from 5GS to EPC/ePDG NOTE: In step 2, the UE can also trigger this procedure when 5G NAS (i.e. N1 mode) capability is disabled while the UE is in 5GS. 0. Initial status: one or more PDU Sessions have been established between the UE and the SMF/UPF via NG-RAN. 1. The UE connects to an untrusted non-3GPP access and the N3IWF-ePDG selection process results in selecting an ePDG. 2. The UE initiates a Handover procedure as described in clause 8.6.2.1 of TS 23.402[ Architecture enhancements for non-3GPP accesses ] [26], except step 11 of referenced figure 8.2.3-1 that corresponds to the release of resources in source system. 3. The combined PGW+SMF/UPF initiates a network requested PDU Session Release via 3GPP access according to Figure 4.3.4.2-1 steps 3b to 7b, step 11 or Figure 4.3.4.3-1 steps 3a-16b to release the 5GC and NG-RAN resources with the following exception: - For non-roaming or local breakout in clause 4.3.4.2, the SMF does not include N1 SM Container in Namf_Communication_N1N2MessageTransfer service operation. - For home routing roaming in clause 4.3.4.3, the H-SMF indicates in the Nsmf_PDUSession_Update Request that the UE shall not be notified. This shall result in the V-SMF not sending the N1 SM Container (PDU Session Release Command) to the UE. - Nsmf_PDUSession_StatusNotify service operation invoked by H-SMF to V-SMF and Nsmf_PDUSession_SMContexStatusNotify service operation invoked by the (V-)SMF to the AMF indicate that the PDU Session is moved to a different system. - The Npcf_SMPolicyControl_Delete service operation to PCF shall not be performed. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.4.2 |
6,271 | 8.7.9 FDD (4 Rx) | The parameters specified in Table 8.7.9-1 are valid for all FDD tests for 4Rx capable UEs unless otherwise stated. Table 8.7.9-1: Common Test Parameters (FDD) For UE not supporting 256QAM, the TB success rate shall be higher than 85% when PDSCH are scheduled with FRC in Table 8.7.9-2 with the downlink physical channel setup according to Annex C.3.2. For UE supporting 256QAM, the TB success rate shall be higher than 85% when PDSCH are scheduled with FRC in Table 8.7.9-3 with the downlink physical channel setup according to Annex C.3.2. For UE supporting 256QAM, the requirement with 64QAM is not applicable. The TB success rate is defined as 100%*NDL_correct_rx/ (NDL_newtx + NDL_retx), where NDL_newtx is the number of newly transmitted DL transport blocks, NDL_retx is the number of retransmitted DL transport blocks, and NDL_correct_rx is the number of correctly received DL transport blocks. The TB success rate shall be sustained during at least 300 frames. Table 8.7.9-2: Per-CC FRC for SDR test (FDD 64QAM) Table 8.7.9-3: Per-CC FRC for SDR test (FDD 256QAM) CA configuration, bandwidth combination and MIMO layer on each CC is determined by following procedure. - Select one CA bandwidth combination among all supported CA configurations with bandwidth combination and MIMO layer on each CC that leads to largest equivalent aggregated bandwidth among all CA bandwidth combinations supported by UE. Equivalent aggregated bandwidth is defined as where is number of CCs, and is MIMO layer and bandwidth of CC . - When there are multiple sets of {CA configuration, bandwidth combination, MIMO layer} with same largest aggregated bandwidth, select one among sets with largest number of 4 layer CCs. - The procedure applies also for single carrier using operating band instead of CA configuration, and bandwidth instead of bandwidth combination. Table 8.7.9-4: Void Table 8.7.9-5: Void | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.7.9 |
6,272 | 9.8.1.2 TDD | The following requirements apply to UE supporting coverage enhancement. For the parameters specified in Table 9.7.3.2-1, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2, the reported CQI value according to RC.23 TDD in Table A.4-1 shall be in the range of Β±1 of the reported median more than 90% of the time. If the PDSCH BLER using the transport format indicated by median CQI is less than or equal to 0.1, the BLER using the transport format indicated by the (median CQI + 1) shall be greater than 0.1. If the PDSCH BLER using the transport format indicated by the median CQI is greater than 0.1, the BLER using transport format indicated by (median CQI β 1) shall be less than or equal to 0.1. Table 9.8.1.2-1: PUCCH 1-0 static test (TDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.8.1.2 |
6,273 | I.2.3.2 Credentials holder using AAA server for primary authentication | When running primary authentication towards an external Credentials holder using AAA server for authentication as specified in clause I.2.2.2 the derivation of KAUSF is based on the EAP-method credentials in the UE and AAA-S and shall be done as shown in Figure I.2.3.2-1. Figure I.2.3.2-1: KAUSF derivation for primary authentication towards an external Credentials holder using AAA server KAUSF shall be derived by the AUSF and UE from the MSK derived during the EAP authentication as specified in clause I.2.2.2.1. All of figures 6.2.1-1, 6.2.2.1-1 and 6.2.2.2.2-1 from the KAUSF downwards are used without modification. Similarly, text relating to the key hierarchy, key derivation and key distribution in clauses 6.2.1, 6.2.2.1 and 6.2.2.2 for keys derived from KAUSF (e.g. KSEAF, KAMF, KgNB etc) apply without modification. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | I.2.3.2 |
6,274 | 5.4.7.2.3 Abnormal cases on the network side | The following abnormal cases can be identified: a) T3575 expiry The AMF shall, on the first expiry of the timer T3575, retransmit the NETWORK SLICE-SPECIFIC AUTHENTICATION COMMAND message and shall reset and start timer T3575. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3575, the AMF shall abort the network slice-specific authentication and authorization procedure for the S-NSSAI. The AMF shall consider that the network slice-specific authentication and authorization procedure for the S-NSSAI is completed as a failure. b) Lower layers indication of non-delivered NAS PDU due to handover If the NETWORK SLICE-SPECIFIC AUTHENTICATION COMMAND message could not be delivered due to an intra AMF handover and the target TAI is included in the TAI list, then upon successful completion of the intra AMF handover the AMF shall retransmit the NETWORK SLICE-SPECIFIC AUTHENTICATION COMMAND message. If a failure of handover procedure is reported by the lower layer and the N1 NAS signalling connection exists, the AMF shall retransmit the NETWORK SLICE-SPECIFIC AUTHENTICATION COMMAND message. c) Network slice-specific authentication and authorization procedure and de-registration procedure collision If the network receives a DEREGISTRATION REQUEST message before the ongoing network slice-specific authentication and authorization procedure has been completed and the access type included in the DEREGISTRATION REQUEST message is the same as the one for which the network slice-specific authentication and authorization procedure is ongoing, the network shall abort the network slice-specific authentication and authorization procedure and shall progress the UE-initiated de-registration procedure. The AMF may initiate the network slice-specific authentication and authorization procedure for the S-NSSAI which is completed as a failure, if available. If the access type included in the DEREGISTRATION REQUEST message is different from the one for which the network slice-specific authentication and authorization procedure is ongoing, the network shall proceed with both procedures. d) Network slice-specific authentication and authorization procedure and service request procedure collision If the network receives a SERVICE REQUEST message before the ongoing network slice-specific authentication and authorization procedure has been completed and the SERVICE REQUEST message includes the UE request type IE with the Request type value set to "NAS signalling connection release", the network shall abort the network slice-specific authentication and authorization procedure and shall progress the service request procedure. If the network receives a SERVICE REQUEST message before the ongoing network slice-specific authentication and authorization procedure has been completed and the SERVICE REQUEST message does not include UE request type IE with the Request type value set to "NAS signalling connection release", both procedures shall be progressed. e) Network slice-specific authentication and authorization procedure and registration procedure for mobility and periodic registration update collision If the network receives a REGISTRATION REQUEST message before the ongoing network slice-specific authentication and authorization procedure has been completed and the REGISTRATION REQUEST message includes the Unavailability information IE, the network shall abort the network slice-specific authentication and authorization procedure and shall progress the registration procedure for mobility and periodic registration update procedure. If the network receives a REGISTRATION REQUEST message before the ongoing network slice-specific authentication and authorization procedure has been completed and the REGISTRATION REQUEST message does not include the Unavailability information IE, both procedures shall be progressed. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.7.2.3 |
6,275 | 7.8 Messages with semantically incorrect contents | When a message with semantically incorrect contents is received, the UE shall perform the foreseen reactions of the procedural part of the present document (i.e. of clauses 4, 5 and 6). If however no such reactions are specified, the UE shall ignore the message except that it shall return a status message (EMM STATUS or ESM STATUS depending on the PD) with cause #95 "semantically incorrect message". The network should follow the same procedure except that a status message is not normally transmitted. | 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 | 7.8 |
6,276 | 5.14.1.2.1 Sidelink HARQ Entity | The MAC entity is configured by upper layers to transmit using pool(s) of resources on one or multiple carriers as indicated in clause 5.10.13.1 of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]. For each carrier, there is one Sidelink HARQ Entity at the MAC entity for transmission on SL-SCH, which maintains a number of parallel Sidelink processes. For sidelink communication, the number of transmitting Sidelink processes associated with the Sidelink HARQ Entity is defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]. For V2X sidelink communication, the maximum number of transmitting Sidelink processes associated with each Sidelink HARQ Entity is 8. A sidelink process may be configured for transmissions of multiple MAC PDUs. For transmissions of multiple MAC PDUs, the maximum number of transmitting Sidelink processes associated with each Sidelink HARQ Entity is 2. A delivered and configured sidelink grant and its associated HARQ information are associated with a Sidelink process. For each subframe of the SL-SCH and each Sidelink process, the Sidelink HARQ Entity shall: - if a sidelink grant corresponding to a new transmission opportunity has been indicated for this Sidelink process and there is SL data, for sidelink logical channels of ProSe destination associated with this sidelink grant, available for transmission: - obtain the MAC PDU from the "Multiplexing and assembly" entity; - deliver the MAC PDU and the sidelink grant and the HARQ information to this Sidelink process; - instruct this Sidelink process to trigger a new transmission. - else, if this subframe corresponds to retransmission opportunity for this Sidelink process: - instruct this Sidelink process to trigger a retransmission. NOTE: The resources for retransmission opportunities are specified in clause 14.2.1 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2] unless specified in clause 5.14.1.1. | 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.14.1.2.1 |
6,277 | 5.7.2.4.3 Usage of Notification control with Alternative QoS Profiles during QoS Flow establishment and modification | During QoS Flow establishment and modification, a prioritized list of Alternative QoS Profile(s) can be provided to the NG-RAN for the QoS Flow in addition to the QoS profile. If the NG-RAN is not able to guarantee the GFBR, the PDB and the PER included in the QoS profile and if Alternative QoS Profiles are provided to the NG-RAN and the NG-RAN supports Alternative QoS Profiles, the NG-RAN shall check whether the GFBR, the PDB and the PER values that it can fulfil match at least one of the Alternative QoS Profile(s) taking the priority order into account. If there is a match between one of the Alternative QoS Profiles and the GFBR, the PDB and if available, associated MDBV and the PER values that the NG-RAN can fulfil, the NG-RAN shall accept the QoS Flow and indicate the reference to that Alternative QoS Profile to the SMF. If there is no match to any Alternative QoS Profile, the NG-RAN shall reject the QoS Flow establishment or modification. After a successful QoS Flow establishment or modification during which the NG-RAN indicated that the currently fulfilled QoS matches one of the Alternative QoS Profiles, the NG-RAN shall treat this QoS Flow in the same way as if it had sent a notification that the "GFBR can no longer be guaranteed" with a reference to that Alternative QoS Profile to the SMF (as described in clause 5.7.2.4.1b). If the SMF has received a reference to an Alternative QoS Profile during QoS Flow establishment and modification the SMF may inform the PCF about it (as described in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]). If the PCF has not indicated differently, the SMF shall use NAS signalling (that is sent transparently through the RAN) to inform the UE about the QoS parameters (i.e. 5QI, GFBR, MFBR) corresponding to the referenced Alternative QoS Profile. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7.2.4.3 |
6,278 | 5.3.3.6 Cell re-selection or cell selection or relay (re)selection while T390, T300 or T302 is running (UE in RRC_IDLE) | The UE shall: 1> if cell reselection occurs while T300 or T302 is running; or 1> if relay reselection occurs while T300 is running; or 1> if cell changes due to relay reselection while T302 is running: 2> perform the actions upon going to RRC_IDLE as specified in 5.3.11 with release cause 'RRC connection failure'; 1> else: 2> if cell selection or reselection occurs while T390 is running; or 2> cell change due to relay selection or reselection occurs while T390 is running: 3> stop T390 for all access categories; 3> perform the actions as specified in 5.3.14.4. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.3.6 |
6,279 | 4.11.1.4.1 EPS bearer ID allocation | Following procedures are updated to allocate EPS bearer ID(s) towards EPS bearer(s) mapped from QoS flow(s) and provide the EPS bearer ID(s) to the NG-RAN: - UE requested PDU Session Establishment (Non-roaming and Roaming with Local Breakout (clause 4.3.2.2.1) including Request Types "Initial Request", "Existing PDU Session", "Initial emergency request" and "Existing emergency PDU session". - UE requested PDU Session Establishment (Home-routed Roaming (clause 4.3.2.2.2) including Request Types "Initial Request" and "Existing PDU Session". - UE or network requested PDU Session Modification (non-roaming and roaming with local breakout) (clause 4.3.3.2). - UE or network requested PDU Session Modification (home-routed roaming) (clause 4.3.3.3). - UE Triggered Service Request (clause 4.2.3.2) to move PDU Session(s) from non-3GPP access to 3GPP access EBI allocation shall apply to PDU Session via 3GPP access supporting EPS interworking with N26. EBI allocation shall not apply to PDU Session via 3GPP access supporting EPS interworking without N26 and shall not apply to PDU Session via non-3GPP access supporting EPS interworking. Figure 4.11.1.4.1-1: Procedures for EPS bearer ID allocation 1. Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. 2. If the SMF+PGW-C (or H-SMF in the case of home routed case), determines, based on the indication of EPS interworking support with N26 as defined in clauses 4.11.5.2, 4.11.5.3 and 4.11.5.4 and operator policies e.g. User Plane Security Enforcement information, Access Type, that EPS bearer ID(s) needs to be assigned to the QoS flow(s) in the PDU Session, SMF+PGW-C invokes Namf_Communication_EBIAssignment Request (PDU Session ID, ARP list) (via V-SMF Nsmf_PDUSession_Update in the case of home routed case). When V-SMF receives Nsmf_PDUSession_Update request from H-SMF for EPS bearer ID allocation request, V-SMF needs to invoke Namf_Communication_EBIAssignment Request (PDU Session ID, ARP list). If the SMF+PGW-C (or H-SMF in the case of home-routed roaming) serves multiple PDU sessions for the same DNN but different S-NSSAIs for a UE, then the SMF shall only request EBIs for PDU sessions served by a common UPF (PSA). If different UPF (PSA) are serving those PDU sessions, then the SMF chooses one of the UPF (PSA) for this determination based on operator policy. When the PDU session is established via non-3GPP access, the SMF+PGW-C shall not trigger EBI allocation procedure. Steps 3 to 6 apply only when AMF needs to revoke EBI previously allocated for an UE in order to serve a new SMF request of EBI for the same UE. 3. [Conditional] If the AMF has no available EBIs, the AMF may revoke an EBI that was assigned to QoS flow(s) based on the ARP(s) and S-NSSAI stored during PDU Session establishment, EBIs information in the UE context and local policies. If an assigned EBI is to be revoked, the AMF takes the ARP pre-emption vulnerability and the ARP priority level into consideration and revokes EBIs with a higher value of the ARP priority level first. The AMF invokes Nsmf_PDUSession_UpdateSMContext (EBI(s) to be revoked) to request the related SMF (called "SMF serving the released resources") to release the mapped EPS QoS parameters corresponding to the EBI to be revoked. The AMF stores the association of the assigned EBI, ARP pair to the corresponding PDU Session ID and SMF address. 4. The "SMF serving the released resources" that receives the request in step 3 shall evaluate if any of the revoked EBI(s) corresponds to the QoS Flow associated with the default QoS rule. If the revoked EBI corresponds to the QoS Flow associated with the default QoS rule, the SMF shall release the EBI(s) corresponding to all other QoS Flows of the PDU Session and update the AMF of this release by sending Namf_Communication_EBIAssignment Request (PDU Session ID, Released EBI List). Next, the SMF shall invoke Namf_Communication_N1N2Message Transfer (N2 SM information (PDU Session ID, EBI(s) to be revoked), N1 SM container (PDU Session Modification Command (PDU Session ID, EBI(s) to be revoked))) to inform the (R)AN and the UE to remove the mapped EPS QoS parameters corresponding to the EBI(s) to be revoked. In home routed roaming scenario, the H-SMF includes EBI(s) to be revoked to V-SMF to inform V-SMF to remove the mapped EPS bearer context corresponding to the EBI(s) to be revoked. NOTE 1: The SMF can also decide to remove the QoS flow if it is not acceptable to continue the service when no corresponding EPS QoS parameters can be assigned. For home routed roaming scenario, the "SMF serving the released resources" sends an N4 Session Modification Request to request the PGW-U+UPF to release N4 Session corresponding to the revoked EBI(s). In home routed roaming case, the V-SMF starts a VPLMN initiated QoS modification for the PDU Session and the Namf_Communication_N1N2Message Transfer is invoked by the V-SMF based on the corresponding QoS modification message received from H-SMF. 5. If the UE is in CM-CONNECTED state, the AMF sends N2 PDU Session Resource Modify Request (N2 SM information received from SMF, NAS message (PDU Session ID, N1 SM container (PDU Session Modification Command))) Message to the (R)AN. If the UE is in CM-IDLE state and an ATC is activated, the AMF updates and stores the UE context based on the Namf_Communication_N1N2MessageTransfer and step 5-6 are skipped. When the UE is reachable, e.g. when the UE enters CM-CONNECTED state, the AMF forwards the N1 message to synchronize the UE context with the UE. 6. The rest steps of the procedure are executed as specified in the figure above. 7 If the AMF successfully assigns EBI(s), it responds with the assigned EBI(s). Otherwise, it responds with a cause indicating EBI assignment failure. If the PDU Session is associated to an S-NSSAI subject for Network Slice-Specific Authentication and Authorization the AMF should indicate EBI assignment failure. If a PDU Session from another SMF already exists towards the same DNN, the AMF either rejects the EBI assignment request, or revokes the EBI(s) from the existing PDU Session(s) to the same DNN but different SMFs if the AMF makes the decision based on the operator policy, that the existing PDU Session cannot support EPS interworking N26. The AMF stores the DNN and SMF+PGW-C in which the PDU Session(s) support EPS interworking to UDM in clause 4.11.1.6. NOTE 2: The above applies only when the S-NSSAI(s) for the PDU Sessions are different, otherwise the same SMF is selected for PDU Sessions to the same DNN. 8. The SMF+PGW-C sends an N4 Session Establishment/Modification Request to the PGW-U+UPF. For home routed roaming scenario, if the EBI is assigned successfully, the SMF+PGW-C prepares the CN Tunnel Info for each EPS bearer. For non roaming and LBO scenario, if the EBI is assigned successfully, the SMF+PGW-C may prepare the CN Tunnel Info for each EPS bearer. The PGW-U+UPF allocates the PGW-U tunnel info for the EPS bearer and sends it to the SMF+PGW-C. The PGW-U+UPF is ready to receive uplink packets from E-UTRAN. NOTE 3: In the home routed roaming scenario the SMF+PGW-C prepares the CN Tunnel Info for each EPS bearer and provide it to V-SMF. Thus when the UE move to EPC network, the V-SMF does not need interact with the SMF+PGW-C to get the EPS bearer context(s). 9. If the SMF+PGW-C receives any EBI(s) from the AMF, it adds the received EBI(s) into the mapped EPS bearer context(s). In home routed roaming scenario, the SMF+PGW-C generates EPS bearer context which includes per EPS bearer PGW-U tunnel information. In addition, if the default EPS bearer is generated for the corresponding PDN Connection of PDU Session (i.e. during the PDU Session establishment procedure), the SMF+PGW-C generates the PGW-C tunnel information of the PDN connection and include it in UE EPS PDN connection. 9a. [Conditional] In non-roaming or LBO scenario, the SMF+PGW-C includes the mapped EPS bearer context(s) and the corresponding QoS Flow(s) to be sent to the UE in the N1 SM container. SMF+PGW-C also indicates the mapping between the QoS Flow(s) and mapped EPS bearer context(s) in the N1 SM container. SMF+PGW-C also includes the mapping between the received EBI(s) and QFI(s) into the N2 SM information to be sent to the NG-RAN. The SMF+PGW-C sends the N1 SM container and N2 SM information to AMF via the Nsmf_PDUSession_UpdateSMContext Response in the case of the PDU Session Modification procedure triggered by UE or AN, or UE Triggered Service Request procedure that results in session transfer from N3GPP to 3GPP, otherwise, via the Namf_Communication_N1N2MessageTransfer. 9b [Conditional] In home routed roaming scenario, the SMF+PGW-C sends mapped EPS bearer context(s), the mapping between the received EBI(s) and QFI(s), linked EBI and EPS bearer context(s) to V-SMF via Nsmf_PDUSession_Create Response in the case of PDU Session Establishment, or via Nsmf_PDUSession_Update Request in the case of PDU Session Modification. The V-SMF stores the EPS bearer context(s) and generates N1 SM container and N2 SM information and forwards them to AMF via the Nsmf_PDUSession_UpdateSMContext Response in the case of the PDU Session Modification procedure triggered by UE or AN, or UE Triggered Service Request procedure that results in session transfer from N3GPP to 3GPP, otherwise, via the Namf_Communication_N1N2MessageTransfer. 10. The N1 SM container and N2 SM information are sent to the UE and NG-RAN respectively. The relevant steps of the procedure as specified in the figure above are executed. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.1.4.1 |
6,280 | 5.3.1.5 Suspend and resume of the N1 NAS signalling connection | Suspend of the N1 NAS signalling connection can be initiated by the network in 5GMM-CONNECTED mode when user plane CIoT 5GS optimization is used. Resume of the suspended N1 NAS signalling connection is initiated by the UE. In the UE, when user plane CIoT 5GS optimization is used: - Upon idle suspend indication from the lower layers, the UE shall enter 5GMM-IDLE mode with suspend indication, shall not consider the N1 NAS signalling connection released and shall not consider the secure exchange of NAS messages terminated (see subclause 4.4.2.5 and 4.4.5). - Upon trigger of a procedure using an initial NAS message when in 5GMM-IDLE mode with suspend indication, the UE shall: i) if the initial NAS message is a REGISTRATION REQUEST message with the NG-RAN-RCU bit of the 5GS update type IE set to "UE radio capability update needed", enter 5GMM-IDLE mode without suspend indication and proceed with the registration procedure; or ii) otherwise, request the lower layer to resume the RRC connection. NOTE 1: In NB-N1 mode, in the request to the lower layer the data volume information of the initial NAS message is provided to the lower layers. Interactions between the NAS and the lower layers in order to obtain the data volume information of the initial NAS message (see 3GPP TS 36.321[ Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification ] [25E], 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [25A]) is left to implementations. - Upon indication from the lower layers that the RRC connection has been resumed when in 5GMM-IDLE mode with suspend indication, the UE shall enter 5GMM-CONNECTED mode. If the pending NAS message is: i) a SERVICE REQUEST message, the service type IE is not set to "emergency services fallback", and the UE did not include the NAS message container IE in the SERVICE REQUEST message; or ii) a CONTROL PLANE SERVICE REQUEST message, and the UE did not include the CIoT small data container IE or the NAS message container IE in the CONTROL PLANE SERVICE REQUEST message, the message shall not be sent. Otherwise the UE shall cipher the message as specified in subclause 4.4.5 and send the pending initial NAS message upon entering 5GMM-CONNECTED mode; NOTE 2: If a NAS message is discarded and not sent to the network, the uplink NAS COUNT value corresponding to that message is reused for the next uplink NAS message to be sent. - Upon fallback indication from the lower layers at RRC connection resume when in 5GMM-IDLE mode with suspend indication, the UE shall enter 5GMM-IDLE mode without suspend indication, send any pending initial NAS message and proceed as if RRC connection establishment had been requested; - Upon indication from the lower layers that the RRC connection resume has failed and indication from the lower layers that the RRC connection is suspended, the UE shall enter 5GMM-IDLE mode with suspend indication and restart the ongoing NAS procedure if required; and - Upon indication from the lower layers that the RRC connection resume has failed and indication from the lower layers that the RRC connection is not idle suspended, the UE shall enter 5GMM-IDLE mode without suspend indication and restart the ongoing NAS procedure if required. In the network, when user plane CIoT 5GS optimization is used: - Upon idle suspend indication from the lower layers, the network shall enter 5GMM-IDLE mode with suspend indication, shall not consider the N1 NAS signalling connection released and shall not consider the secure exchange of NAS messages terminated; and - Upon indication from the lower layers that it has received the NGAP UE context resume request message as specified in 3GPP TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [31] when in 5GMM-IDLE mode with suspend indication, the network shall enter 5GMM-CONNECTED mode. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.1.5 |
6,281 | 4.5.1.9 MM connection establishment due to Dual Radio Voice Call Continuity (DRVCC) access transfer | The MM Connection establishment procedures for a dual radio voice call continuity (DRVCC) access transfer follow the procedures described in subclause 4.5.1.1 with the following additions: Upon request from the upper layers to set up a DRVCC call, the MS shall initiate the MM connection establishment and send a CM SERVICE REQUEST message. The MS shall include the Additional update parameters information element indicating "DRVCC call". If the MS determines that it is in a different location area than the stored location area, the MS shall first initiate a normal location updating procedure regardless of Network Mode of Operation. The MS shall indicate "follow-on request pending", shall include the Additional update parameters information element indicating "DRVCC call", and shall not include the MS network feature support information element in the LOCATION UPDATING REQUEST message. The network may use the "DRVCC call" indication to decide whether to initiate any of the MM common procedures. If the MS and the network have an established GSM security context or UMTS security context, the MS and the network may take the key(s) of the established security context into use as specified in subclause 4.3.2.7a. | 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.9 |
6,282 | 6.3.4G ON/OFF time mask for V2X Communication | For V2X Communications, additional requirements on ON/OFF time masks for V2X physical channels and signals are specified in this clause. The General ON/OFF time mask in subclause 6.3.4D.1 and PSSS/SSSS time mask in subcluse 6.3.4D.2 are applied for E-UTRA V2X sidelink UE. When UE is configured for simultaneous E-UTRA V2X sidelink and E-UTRA uplink transmissions for inter-band E-UTRA V2X / E-UTRA bands specified in Table 5.5G-2, the requirements in subclause 6.3.4G apply for the V2X sidelink transmission and the requirements in subclause 6.3.4 apply for the E-UTRA uplink transmission. For intra-band contiguous multi-carrier operation the general ON/OFF time mask is applicable for each component carrier during the ON power period and the transient periods. The OFF period shall only be applicable for each component carrier when all the component carriers are OFF. For V2X UE supporting Transmit Diversity, the ON/OFF time mask requirements apply at each transmit antenna connector. If the UE transmits on two antenna connectorsat the same time, the general ON/OFF time mask requirements apply to each transmit antenna connector. If the UE transmits on one antenna connector at a time, the general ON/OFF time mask requirements apply to the active antenna connector. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.3.4G |
6,283 | β NeedForGapNCSG-InfoEUTRA | The IE NeedForGapNCSG-InfoEUTRA indicates whether measurement gap or NCSG is required for the UE to perform measurements on an E-UTRA target band while NR-DC or NE-DC is not configured. NeedForGapNCSG-InfoEUTRA information element -- ASN1START -- TAG-NEEDFORGAPNCSG-INFOEUTRA-START NeedForGapNCSG-InfoEUTRA-r17 ::= SEQUENCE { needForNCSG-EUTRA-r17 SEQUENCE (SIZE (1..maxBandsEUTRA)) OF NeedForNCSG-EUTRA-r17 } NeedForNCSG-EUTRA-r17 ::= SEQUENCE { bandEUTRA-r17 FreqBandIndicatorEUTRA, gapIndication-r17 ENUMERATED {gap, ncsg, nogap-noncsg} } -- TAG-NEEDFORGAPNCSG-INFOEUTRA-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
6,284 | 16a.4.3 ACR Command | The ACR command, defined in IETF RFC 6733 (Diameter Base) [111], is indicated by the Command-Code field set to 271 and the βRβ bit set in the Command Flags field. It is sent by the GGSN/P-GW to the Diameter server to report accounting information for a certain IP-CAN bearer (e.g. PDP context) or an IP-CAN session of a certain user. The relevant AVPs that are of use for the Gi/Sgi interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for Gi/Sgi purposes and should be ignored by the receiver or processed according to the relevant specifications. The bold marked AVPs in the message format indicate optional AVPs for Gi/Sgi, or modified existing AVPs. For Sgi, some of the optional 3GPP vendor-specific AVPs listed in the message format below are not applicable. See table 9a in subclause 16a.5 to see the ones that are applicable. Message Format: <AC-Request> ::= < Diameter Header: 271, REQ, PXY > < Session-Id > { Origin-Host } { Origin-Realm } { Destination-Realm } { Accounting-Record-Type } { Accounting-Record-Number } [ Acct-Application-Id ] [ User-Name ] [ Origin-State-Id ] [ Destination-Host ] [ Event-Timestamp ] [ Acct-Delay-Time ] [ NAS-Identifier ] [ NAS-IP-Address ] [ NAS-IPv6-Address ] [ NAS-Port ] [ NAS-Port-Id ] [ NAS-Port-Type ] * [ Class ] [ Service-Type ] [ Accounting-Input-Octets ] [ Accounting-Input-Packets ] [ Accounting-Output-Octets ] [ Accounting-Output-Packets ] [ Acct-Authentic ] [ Accounting-Auth-Method ] [ Acct-Session-Time ] [ Acct-Tunnel-Connection ] [ Acct-Tunnel-Packets-Lost ] [ Callback-Id ] [ Callback-Number ] [ Called-Station-Id ] [ Calling-Station-Id ] * [ Connection-Info ] [ Originating-Line-Info ] [ Authorization-Lifetime ] [ Session-Timeout ] [ Idle-Timeout ] [ Port-Limit ] [ Accounting-Realtime-Required ] [ Acct-Interim-Interval ] * [ Filter-Id ] * [ NAS-Filter-Rule ] * [ Qos-Filter-Rule ] [ Framed-Compression ] [ Framed-Interface-Id ] [ Framed-IP-Address ] [ Framed-IP-Netmask ] * [ Framed-IPv6-Prefix ] [ Framed-IPv6-Pool ] * [ Framed-IPv6-Route ] * [ Delegated-IPv6-Prefix ] [ Framed-IPX-Network ] [ Framed-MTU ] [ Framed-Pool ] [ Framed-Protocol ] * [ Framed-Route ] [ Framed-Routing ] * [ Login-IP-Host ] * [ Login-IPv6-Host ] [ Login-LAT-Group ] [ Login-LAT-Node ] [ Login-LAT-Port ] [ Login-LAT-Service ] [ Login-Service ] [ Login-TCP-Port ] * [ Tunneling ] * [ Proxy-Info ] * [ Route-Record ] [ 3GPP-IMSI] [ External-Identifier] [ 3GPP-Charging-ID ] [ 3GPP-PDP-Type ] [ 3GPP-CG-Address ] [ 3GPP-GPRS-Negotiated-QoS-Profile ] [ 3GPP-SGSN-Address ] [ 3GPP-GGSN-Address ] [ 3GPP-IMSI-MCC-MNC ] [ 3GPP-GGSN-MCC-MNC ] [ 3GPP-NSAPI ] [ 3GPP-Selection-Mode ] [ 3GPP-Charging-Characteristics ] [ 3GPP-CG-IPv6-Address ] [ 3GPP-SGSN-IPv6-Address ] [ 3GPP-GGSN-IPv6-Address ] [ 3GPP-SGSN-MCC-MNC ] [ 3GPP-IMEISV ] [ 3GPP-RAT-Type ] [ 3GPP-User-Location-Info ] [ 3GPP-MS-Time-Zone ] [ 3GPP-CAMEL-Charging-Info ] [ 3GPP-Packet-Filter ] [ 3GPP-Negotiated-DSCP ] [ TWAN-Identifier ] [ 3GPP-User-Location-Info-Time ] * [ 3GPP-Secondary-RAT-Usage ] [ 3GPP-UE-Local-IP-Address ] [ 3GPP-UE-Source-Port ] * [ AVP ] | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 16a.4.3 |
6,285 | 4.23.12.8.5 Inter NG-RAN node N2 based handover with I-SMF insertion/change/removal | The following impact is applicable for Inter NG-RAN node N2 based handover with I-SMF insertion in clause 4.23.7.3.2: - In step 7c, at I-SMF insertion, if EBI(s) have been allocated before but the SMF+PGW-C has not prepared the CN Tunnel Info for each EPS bearer, the SMF+PGW-C requests the PGW-U+UPF to allocate the CN Tunnel for each EPS bearer for PDU Session(s). PGW-U+UPF allocates the PGW-U tunnel info for the EPS bearer and sends it to the SMF+PGW-C. - In step 7f, the SMF+PGW-C provides also the CN Tunnel Info for each EPS bearer to the I-SMF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.12.8.5 |
6,286 | 15.5.2.4 Inter-system Ping-pong | One of the functions of Mobility Robustness Optimization is to detect ping-pongs that occur in inter-system environment. The problem is defined as follows: - A UE is handed over from a cell in a source system (e.g. 5GS) to a cell in a target system different from the source system (e.g. EPS), then within a predefined limited time the UE is handed over back to a cell in the source system, while the coverage of the source system was sufficient for the service used by the UE. The event may occur more than once. The solution for the problem may consist of the following steps: 1) Statistics regarding inter-system ping-pong occurrences are collected by the responsible node; 2) Coverage verification is performed to check if the mobility to other system was inevitable. The statistics regarding ping-pong occurrence may be based on evaluation of the UE History Information IE in the HANDOVER REQUIRED message. If the evaluation indicates a potential ping-pong case and the source NG_RAN node of the 1st inter-system handover is different than the target NG-RAN node of the 2nd inter-system handover, the target NG-RAN node may use the HANDOVER REPORT message or the UPLINK RAN CONFIGURATION TRANSFER message to indicate the occurrence of potential ping-pong cases to the source NG-RAN node. If NG-RAN coverage during the potential ping-pong event needs to be verified for the purpose of determining corrective measures, the Unnecessary HO to another system procedure may be used. NOTE: Inter-system mobility triggered by Voice Fallback is not considered as inter-system ping-pong. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 15.5.2.4 |
6,287 | 4.7.4 GPRS detach procedure 4.7.4.0 General | The GPRS detach procedure is used: - to detach the IMSI for GPRS services only. Independent of the network operation mode, this procedure is used by all kind of GPRS MSs; - as a combined GPRS detach procedure used by GPRS MSs operating in MS operation mode A or B to detach the IMSI for GPRS and non-GPRS services or for non-GPRS services only, if the network operates in network operation mode I and no circuit-switched transaction is ongoing; - in the case of a network failure condition to indicate to the MS that a re-attach with successive activation of previously active PDP contexts shall be performed. In this case, the MS may also perform the procedures needed in order to activate any previously active multicast service(s); or - to detach the IMSI or IMEI for emergency bearer services. After completion of a GPRS detach procedure or combined GPRS detach procedure for GPRS and non-GPRS services the GMM context is released. An eCall only mobile station that is not capable of eCall over IMS shall not perform any kind of GPRS detach procedure. The GPRS detach procedure shall be invoked by the MS if the MS is switched off, the SIM/USIM card is removed from the MS or if the GPRS or non-GPRS capability of the MS is disabled. The procedure may be invoked by the network to detach the IMSI for GPRS services. The GPRS detach procedure causes the MS to be marked as inactive in the network for GPRS services, non-GPRS services or both services. If the detach procedure is triggered due to SIM/USIM removal, the MS shall indicate "switch off" in the detach type IE. If a detach is requested by the HLR for an MS that has a PDP context for emergency services, the SGSN shall not send a DETACH REQUEST message to the MS, and shall follow the procedure described in subclause 6.1.3.4.2 for an MS that has PDP contexts for emergency bearer services. When upper layers indicates that emergency bearer services are no longer required, the MS if still attached for emergency bearer services, may perform a detach followed by a re-attach to regain normal services, if the MS is in or moves to a suitable cell. In A/Gb mode, if the GPRS detach procedure is performed, the PDP contexts and the MBMS contexts, if any, are deactivated locally without peer to peer signalling between the SM and LLC entities in the MS and the network. In Iu mode, if the GPRS detach procedure is performed, the PDP contexts and the MBMS contexts, if any, are deactivated locally without peer to peer signalling between the SM entities in the MS and the network. If the MS supports S1 mode, the MS shall store the TIN in the non-volatile memory in the ME, as described in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120], annex C, for a subsequent attach procedure. The MS is allowed to initiate the GPRS detach procedure even if the timer T3346 is running. The network proceeds with the GPRS detach procedure even if NAS level mobility management congestion control is active. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.4 |
6,288 | 5.5.4.28 Event A5H2 (SpCell becomes worse than threshold1 and neighbour becomes better than threshold2 and the Aerial UE altitude becomes lower than a threshold3) | The UE shall: 1> consider the entering condition for this event to be satisfied when all of condition A5H2-1 and condition A5H2-2 and condition A5H2-3, as specified below, are fulfilled; 1> consider the leaving condition for this event to be satisfied when condition A5H2-4 or condition A5H2-5 or condition A5H2-6, i.e. at least one of the three, as specified below, is fulfilled; 1> use the SpCell for Mp. NOTE: The parameters of the reference signal(s) of the cell(s) that triggers the event are indicated in the measObjectNR associated to the event which may be different from the measObjectNR of the NR SpCell. Inequality A5H2-1 (Entering condition 1) Mp + Hys1 < Thresh1 Inequality A5H2-2 (Entering condition 2) Mn + Ofn + Ocn β Hys1 > Thresh2 Inequality A5H2-3 (Entering condition 3) Ms + Hys2 < Thresh3 Inequality A5H2-4 (Leaving condition 1) Mp β Hys1 > Thresh1 Inequality A5H2-5 (Leaving condition 2) Mn + Ofn + Ocn + Hys1 < Thresh2 Inequality A5H2-6 (Leaving condition 3) Ms β Hys2 > Thresh3 The variables in the formula are defined as follows: Mp is the measurement result of the NR SpCell, not taking into account any offsets. Mn is the measurement result of the neighbouring cell, not taking into account any offsets. Ofn is the measurement object specific offset of the neighbour cell (i.e. offsetMO as defined within measObjectNR corresponding to the neighbour cell). Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectNR corresponding to the neighbour cell), and set to zero if not configured for the neighbour cell. Hys1 is the hysteresis parameter for this event (i.e. a5-Hysteresis as defined within reportConfigNR for this event). Thresh1 is the threshold parameter for this event (i.e. a5-Threshold1 as defined within reportConfigNR for this event). Thresh2 is the threshold parameter for this event (i.e. a5-Threshold2 as defined within reportConfigNR for this event). Ms is the Aerial UE altitude relative to the sea level. Hys2 is the hysteresis parameter for this event (i.e. h2-Hysteresis as defined within reportConfigNR for this event). Thresh3 is the threshold parameter for this event (i.e. h2-Threshold as defined within reportConfigNR for this event). Mn, Mp are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR. Ofn, Ocn, Hys are expressed in dB. Thresh1 is expressed in the same unit as Mp. Thresh2 is expressed in the same unit as Mn. Ms, Hys2, Thresh3 are expressed in meters. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.4.28 |
6,289 | 6.8.4 Intersystem handover for CS Services β from UTRAN to GSM BSS | If ciphering has been started when an intersystem handover occurs from UTRAN to GSM BSS, the necessary information (e.g. Kc, supported/allowed GSM ciphering algorithms) is transmitted within the system infrastructure before the actual handover is executed to enable the communication to proceed from the old RNC to the new GSM BSS, and to continue the communication in ciphered mode. The RNC may request the MS to send the MS Classmarks 2 and 3 which include information on the GSM ciphering algorithm capabilities of the MS. This is necessary only if the MS Classmarks 2 and 3 were not transmitted from UE to UTRAN during the RRC Connection Establishment. The intersystem handover will imply a change of ciphering algorithm from a UEA to a GSM A5. The GSM BSS includes the selected GSM ciphering mode in the handover command message sent to the MS via the RNC. The integrity protection of signalling messages is stopped at handover to GSM BSS. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.4 |
6,290 | β AvailabilityCombinationsPerCell | The IE AvailabilityCombinationsPerCell is used to configure the AvailabilityCombinations applicable for a cell of the IAB DU (see TS 38.213[ NR; Physical layer procedures for control ] [13], clause 14). Note that the IE AvailabilityCombinationsPerCellIndex can only be configured up to 511. AvailabilityCombinationsPerCell information element -- ASN1START -- TAG-AVAILABILITYCOMBINATIONSPERCELL-START AvailabilityCombinationsPerCell-r16 ::= SEQUENCE { availabilityCombinationsPerCellIndex-r16 AvailabilityCombinationsPerCellIndex-r16, iab-DU-CellIdentity-r16 CellIdentity, positionInDCI-AI-r16 INTEGER(0..maxAI-DCI-PayloadSize-1-r16) OPTIONAL, -- Need M availabilityCombinations-r16 SEQUENCE (SIZE (1..maxNrofAvailabilityCombinationsPerSet-r16)) OF AvailabilityCombination-r16, ..., [[ availabilityCombinationsRB-Groups-r17 SEQUENCE (SIZE (1..maxNrofAvailabilityCombinationsPerSet-r16)) OF AvailabilityCombinationRB-Groups-r17 OPTIONAL -- Need M ]], [[ positionInDCI-AI-RBGroups-v1720 INTEGER(0..maxAI-DCI-PayloadSize-1-r16) OPTIONAL -- Need M ]] } AvailabilityCombinationsPerCellIndex-r16 ::= INTEGER(0..maxNrofDUCells-r16) AvailabilityCombination-r16 ::= SEQUENCE { availabilityCombinationId-r16 AvailabilityCombinationId-r16, resourceAvailability-r16 SEQUENCE (SIZE (1..maxNrofResourceAvailabilityPerCombination-r16)) OF INTEGER (0..7) } AvailabilityCombinationId-r16 ::= INTEGER (0..maxNrofAvailabilityCombinationsPerSet-1-r16) AvailabilityCombinationRB-Groups-r17 ::= SEQUENCE { availabilityCombinationId-r17 AvailabilityCombinationId-r16, rb-SetGroups-r17 SEQUENCE (SIZE (1..maxNrofRB-SetGroups-r17)) OF RB-SetGroup-r17 OPTIONAL, -- Need R resourceAvailability-r17 SEQUENCE (SIZE (1..maxNrofResourceAvailabilityPerCombination-r16)) OF INTEGER (0..7) OPTIONAL -- Need R } RB-SetGroup-r17 ::= SEQUENCE { resourceAvailability-r17 SEQUENCE (SIZE (1..maxNrofResourceAvailabilityPerCombination-r16)) OF INTEGER (0..7) OPTIONAL, -- Need R rb-Sets-r17 SEQUENCE (SIZE (1..maxNrofRB-Sets-r17)) OF INTEGER (0..7) OPTIONAL -- Need R } -- TAG-AVAILABILITYCOMBINATIONSPERCELL-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
6,291 | 5.5.1.3.4.3 Combined attach successful for EPS services only | Apart from the actions on the tracking area updating attempt counter, the description for attach for EPS services as specified in clause 5.5.1.2.4 shall be followed. In addition, the following description for attach for non-EPS services applies. If, due to emergency services fallback (see 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [59], clause 4.13.4), there is a request for emergency services pending and the emergency bearer services indicator in the EPS network feature support IE indicates "emergency bearer services in S1 mode not supported", then the UE shall skip the requirements defined below in the present clause for the receipt of an ATTACH ACCEPT message including an EMM cause value, attempt to select GERAN or UTRAN radio access technology, select a setup message as defined in clause 5.3.7, proceed with appropriate MM specific procedures, and send the setup message. The UE receiving the ATTACH ACCEPT message takes one of the following actions depending on the EMM cause value: #2 (IMSI unknown in HSS) The UE shall stop T3410 if still running and shall reset the tracking area updating attempt counter. The UE shall set the update status to U3 ROAMING NOT ALLOWED and shall delete any TMSI, LAI and ciphering key sequence number. The UE shall enter state EMM-REGISTERED.NORMAL-SERVICE. The new MM state is MM IDLE. The USIM shall be considered as invalid for non-EPS services until the UE is switched off, the UICC containing the USIM is removed or the timer T3245 expires as described in clause 5.3.7a. If the UE maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the UE shall set this counter to UE implementation-specific maximum value. If, due to emergency services fallback (see 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [59]), there is a request for CS fallback call pending (see clause 5.3.7), the UE shall attempt to select GERAN or UTRAN radio access technology and attempt emergency call setup. A UE operating in CS/PS mode 1 of operation with "IMS voice not available" shall disable the E-UTRA capability (see clause 4.5). #16 (MSC temporarily not reachable); or #17 (Network failure) The UE shall stop timer T3410 if still running, and shall enter state MM IDLE. The tracking area updating attempt counter shall be incremented, unless it was already set to 5. If the tracking area updating attempt counter is less than 5: - the UE shall start timer T3411, shall set the EPS update status to EU1 UPDATED and shall enter state EMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM. When timer T3411 expires the combined tracking area updating procedure indicating "combined TA/LA updating with IMSI attach" is triggered. If the tracking area updating attempt counter is equal to 5: - a UE operating in CS/PS mode 2 of operation and a UE operating in CS/PS mode 1 of operation with "IMS voice available" shall start timer T3402, shall set the EPS update status to EU1 UPDATED and shall enter state EMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM. When timer T3402 expires the combined tracking area updating procedure indicating "combined TA/LA updating with IMSI attach" is triggered; - a UE operating in CS/PS mode 1 of operation with "IMS voice not available" shall attempt to select GERAN or UTRAN radio access technology and proceed with appropriate MM or GMM specific procedures and disable the E-UTRA capability (see clause 4.5). #18 (CS domain not available) The UE shall stop timer T3410 if still running, shall reset the tracking area updating attempt counter, shall set the EPS update status to EU1 UPDATED and shall enter state EMM-REGISTERED.NORMAL-SERVICE. The UE shall enter state MM IDLE and shall set the update status to U2 NOT UPDATED. A UE in CS/PS mode 1 of operation with "IMS voice not available" shall attempt to select GERAN or UTRAN radio access technology and disable the E-UTRA capability (see clause 4.5). A UE in CS/PS mode 2 of operation and a UE operating in CS/PS mode 1 of operation with "IMS voice available" may provide a notification to the user or the upper layers that the CS domain is not available. The UE shall not attempt combined attach or combined tracking area updating procedures with current PLMN until switching off the UE or the UICC containing the USIM is removed. #22 (Congestion) The UE shall stop the timer T3410 if still running. The tracking area updating attempt counter shall be set to 5. The UE shall start the timer T3402, shall set the EPS update status to EU1 UPDATED, shall enter state EMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM, and shall enter state MM IDLE. Other EMM cause values and the case that no EMM cause IE was received are considered as abnormal cases. The combined attach procedure shall be considered as failed for non-EPS services. The behaviour of the UE in those cases is specified in clause 5.5.1.3.6. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.1.3.4.3 |
6,292 | 28.3.2.2.7 Replacement field used in DNS-based Discovery of SNPN N3IWF for regulatory requirements | 28.3.2.2.7.1 General If the visited country mandates the selection of an N3IWF in this country, the NAPTR record(s) associated to the Visited Country FQDN shall be provisioned with the replacement field containing FQDNs of SNPN N3IWFs located in the visited country. NOTE: If the visited country mandates the selection of the N3IWF in this country and the SNPN does not have an N3IWF in this country, the NAPTR record(s) associated to the Visited Country FQDN are provisioned with the replacement field containing an FQDN that cannot be resolved to an IP address. 28.3.2.2.7.2 Replacement field used in DNS-based Discovery of SNPN N3IWF supporting Onboarding If the visited country mandates the selection of an SNPN N3IWF supporting onboarding in this country, the NAPTR record(s) associated to the Visited Country FQDN for SNPN N3IWF supporting Onboarding shall be provisioned with the replacement field containing Operator Identifier based Onboarding FQDN for SNPN N3IWF located in the visited country. When UE sends the DNS query to the DNS server containing the Visited Country Onboarding FQDN for SNPN N3IWF (see clause 28.3.2.2.6.2), the DNS response should contain the Operator Identifier based Onboarding FQDN for SNPN N3IWF with the identity of an SNPN in the visited country supporting Untrusted non-3GPP access for UE Onboarding via N3IWF. If the UE has selected an SNPN for onboarding, the UE sends DNS query to the DNS server containing the Operator Identifier based Onboarding FQDN for SNPN N3IWF to query the identifier of the N3IWF supporting Onboarding, the DNS response should contain the identifier of the N3IWF supporting the onboarding in the SNPN identified by the SNPN ID. The replacement field shall take the form of Operator Identifier based Onboarding FQDN for SNPN N3IWF as below: "onboarding.n3iwf.5gc.snpnid<SNPNID>.mcc<MCC>.pub.3gppnetwork.org" As an example, the NAPTR records associated to the Visited Country Emergency SNPN FQDN for MCC 345, and for a) SNPN MCC 999, MNC 123, and NID 456789ABCDE; b) SNPN MCC 999, MNC 013, and NID 345678BCDEF, are provisioned in the DNS as: onboarding.n3iwf.snpn-5gc.mcc345.visited-country.pub.3gppnetwork.org ; IN NAPTR order pref. flag service regexp replacement IN NAPTR 100 999 "" "" onboarding.n3iwf.5gc.snpnid999123456789ABCDE.mcc345.pub.3gppnetwork.org IN NAPTR 100 999 "" "" onboarding.n3iwf.5gc.snpnid999013345678BCDEF.mcc345.pub.3gppnetwork.org | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.3.2.2.7 |
6,293 | β DLInformationTransfer | The DLInformationTransfer message is used for the downlink transfer of NAS dedicated information, timing information for the 5G internal system clock, or IAB-DU specific F1-C related information. Signalling radio bearer: SRB2 or SRB1 (only if SRB2 not established yet). If SRB2 is suspended, the network does not send this message until SRB2 is resumed. If only dedicatedInfoF1c is included, SRB2 is used. RLC-SAP: AM Logical channel: DCCH Direction: Network to UE DLInformationTransfer message -- ASN1START -- TAG-DLINFORMATIONTRANSFER-START DLInformationTransfer ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { dlInformationTransfer DLInformationTransfer-IEs, criticalExtensionsFuture SEQUENCE {} } } DLInformationTransfer-IEs ::= SEQUENCE { dedicatedNAS-Message DedicatedNAS-Message OPTIONAL, -- Need N lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension DLInformationTransfer-v1610-IEs OPTIONAL } DLInformationTransfer-v1610-IEs ::= SEQUENCE { referenceTimeInfo-r16 ReferenceTimeInfo-r16 OPTIONAL, -- Need N nonCriticalExtension DLInformationTransfer-v1700-IEs OPTIONAL } DLInformationTransfer-v1700-IEs ::= SEQUENCE { dedicatedInfoF1c-r17 DedicatedInfoF1c-r17 OPTIONAL, -- Need N rxTxTimeDiff-gNB-r17 RxTxTimeDiff-r17 OPTIONAL, -- Need N ta-PDC-r17 ENUMERATED {activate,deactivate} OPTIONAL, -- Need N sib9Fallback-r17 ENUMERATED {true} OPTIONAL, -- Need N nonCriticalExtension DLInformationTransfer-v1800-IEs OPTIONAL } DLInformationTransfer-v1800-IEs ::= SEQUENCE { eventID-TSS-r18 INTEGER(0..63) OPTIONAL, -- Cond clockQualityDetailsLevel clockQualityDetailsLevel-r18 CHOICE { clockQualityMetrics-r18 ClockQualityMetrics-r18, clockQualityAcceptanceStatus-r18 ENUMERATED {acceptable, notAcceptable} } OPTIONAL, -- Need N nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-DLINFORMATIONTRANSFER-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
6,294 | 6.5.5 Handling session management request for UE configured for dual priority | If timer T3396 is running for a specific APN due to one of the following reasons: - a PDN CONNECTIVITY REQUEST, BEARER RESOURCE MODIFICATION REQUEST or BEARER RESOURCE ALLOCATION REQUEST message containing the low priority indicator set to "MS is configured for NAS signalling low priority" was rejected with a timer value for timer T3396 and ESM cause value #26 "insufficient resources"; - a DEACTIVATE EPS BEARER CONTEXT REQUEST message was received with a timer value for timer T3396 and ESM cause value #26 "insufficient resources" for a PDN connection established with low priority indicator set to "MS is configured for NAS signalling low priority", or - because the UE received a DEACTIVATE EPS BEARER CONTEXT REQUEST message containing a timer value for timer T3396 and ESM cause value #26 "insufficient resources" for a PDN connection established with low priority indicator set to "MS is configured for NAS signalling low priority", upon request of the upper layers the UE can: - send a PDN CONNECTIVITY REQUEST message to the same APN, with low priority indicator set to "MS is not configured for NAS signalling low priority"; or, - send a BEARER RESOURCE MODIFICATION REQUEST or BEARER RESOURCE ALLOCATION REQUEST message, with low priority indicator set to "MS is not configured for NAS signalling low priority", for a PDN connection established with low priority indicator set to "MS is not configured for NAS signalling low priority" exists. If timer T3396 is running, because any of the following messages containing the low priority indicator set to "MS is configured for NAS signalling low priority" was rejected with a timer value for timer T3396 and ESM cause value #26 "insufficient resources": - a PDN CONNECTIVITY REQUEST without APN and with request type different from "emergency" and from "handover of emergency bearer services", sent together with an ATTACH REQUEST message; - a stand-alone PDN CONNECTIVITY REQUEST message without APN and with request type different from "emergency" and from "handover of emergency bearer services"; or - a BEARER RESOURCE MODIFICATION REQUEST or BEARER RESOURCE ALLOCATION REQUEST message sent for a non-emergency PDN connection established without APN provided by the UE, or because the UE received a DEACTIVATE EPS BEARER CONTEXT REQUEST message containing a timer value for timer T3396 and ESM cause value #26 "insufficient resources" for a non-emergency PDN connection established without APN provided by the UE and established with low priority indicator set to "MS is configured for NAS signalling low priority", then upon request of the upper layers the UE can initiate a new attach procedure or stand-alone PDN CONNECTIVITY REQUEST procedure without APN and with request type different from "emergency" and from "handover of emergency bearer services", with low priority indicator set to "MS is not configured for NAS signalling low priority". For requests with low priority indicator set to "MS is configured for NAS signalling low priority", the UE shall follow the procedures specified in clause 6.5.1.4. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.5.5 |
6,295 | 5.5.2.3.4 Abnormal cases in the UE | The following abnormal cases can be identified: a) Transmission failure of DETACH ACCEPT message indication from lower layers The detach procedure shall be progressed and the UE shall send the DETACH ACCEPT message. b) DETACH REQUEST, other EMM cause values than those treated in clause 5.5.2.3.2 or no EMM cause IE is included, and the Detach type IE indicates "re-attach not required" The UE shall delete any GUTI, TAI list, last visited registered TAI, list of equivalent PLMNs, KSI, shall set the update status to EU2 NOT UPDATED and shall start timer T3402. A UE operating in CS/PS mode 1 or CS/PS mode 2 of operation which is IMSI attached for non-EPS services is still IMSI attached for non-EPS services and shall set the update status to U2 NOT UPDATED. A UE not supporting any of A/Gb mode, Iu mode or N1 mode may enter the state EMM-DEREGISTERED.PLMN-SEARCH in order to perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]; otherwise the UE shall enter the state EMM-DEREGISTERED.ATTEMPTING-TO-ATTACH. A UE supporting A/Gb mode, Iu mode or N1 mode shall - enter the state EMM-DEREGISTERED and attempt to select GERAN, UTRAN, or NR radio access technology and proceed with the appropriate MM, GMM or 5GMM specific procedures. In this case, the UE may disable the E-UTRA capability (see clause 4.5); - enter the state EMM-DEREGISTERED.PLMN-SEARCH in order to perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]; or - enter the state EMM-DEREGISTERED.ATTEMPTING-TO-ATTACH. If A/Gb mode or Iu mode is supported by the UE, the UE shall set the GPRS update status to GU2 NOT UPDATED and shall delete the GMM parameters P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number and shall enter the state GMM-DEREGISTERED. If the UE is operating in single-registration mode, the UE shall in addition set the 5GMM state to 5GMM-DEREGISTERED, 5GS update status to 5U2 NOT UPDATED, and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.2.3.4 |
6,296 | 6.16.1.2 Security procedures for RRCConnectionRe-establishment Procedure in Control Plane CIoT 5GS Optimization | If the UE experience a RLF when using Control Plane CIoT 5GS optimisation only, the AS layer of the UE may trigger an RRCConnectionReestablishment procedure. As there is no AS security available, this procedure can not be protected as described in subclause 6.11. In order to protect the the re-establishment procedure, the AS part of the UE triggers the NAS part of the UE to provide the UL_NAS_MAC and XDL_NAS_MAC. These parameter are used to show that the UE is requesting the re-establishment and that the UE is talking to a genuine network respectively. The UE calculates a UL_NAS_MAC and XDL_NAS_MAC by using the curently used NAS integrity algorithm with the following inputs, KNASint as the key, the uplink NAS COUNT that would be used for the next uplink NAS message, the DIRECTION bit set to 0 and the target Cell-ID as the message to be protected to calculate NAS-MAC (see Annex D.3.1). The uplink NAS COUNT is increased by the UE in exactly the same way as if it had sent a NAS message. The first 16 bits of NAS-MAC form UL_NAS_MAC and the last 16 bits form XDL_NAS_MAC, which is stored by the UE. The UE shall send the RRCConnectionRestablishmentRequest message to the target ng-eNB and shall include the Truncated 5G-S-TMSI (as described in TS 23.501[ System architecture for the 5G System (5GS) ] [2], TS 23.003[ Numbering, addressing and identification ] [19] and TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [69]), the 5 least significant bits (LSB) of the NAS COUNT that was used to calculate NAS-MAC and UL_NAS_MAC in the message. The target ng-eNB recognises the RRCConnectionRestablishmentRequest message sent by a UE relates to the Control Plane CIoT 5GS optimisation based on the presence of the Truncated 5G-S-TMSI in the message. The target ng-eNB shall recreate the 5G-S-TMSI from the Truncated 5G-S-TMSI (as described in TS 23.501[ System architecture for the 5G System (5GS) ] [2], TS 23.003[ Numbering, addressing and identification ] [19] and TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [69]). The target ng-eNB shall send the 5G-S-TMSI, LSB of NAS COUNT, UL_NAS_MAC and target Cell-ID in the CP Relocation Indication message to the AMF that is serving the UE (this can be deteremined by the S-TMSI). The AMF uses LSB of NAS COUNT to estimate the full uplink NAS COUNT and calculates XNAS-MAC (see Annex D.3.1) using the same inputs (i.e. estimated uplink NAS COUNT, DIRECTION bit set to 0 and the target Cell-ID as the message) as the UE used for calculating NAS-MAC. The AMF then compares the received UL_NAS_MAC with the first 16 bits of XNAS-MAC and if these are equal the network is sure that the geniune UE sent the RRCConnectionRestablishmentRequest message. The stored uplink NAS COUNT in the AMF is set as though the AMF received a sucessfully protected NAS message using that NAS COUNT. The AMF shall set DL_NAS_MAC to the last 16 bits of already calculated XNAS-MAC and send DL_NAS_MAC to the target ng-eNB in the Connection Establishment Indication message. The target ng-eNB shall send the DL_NAS_MAC to the UE in the RRCConnectionReestablisment message. The UE shall check that the received DL_NAS_MAC equal to the stored XDL_NAS_MAC. If so, the UE shall complete the re-establishment procedure. 6.16.2 Security handling in User Plane CIoT 5GS Optimization | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.16.1.2 |
6,297 | 7.4.5 CS Paging Indication | The CS Paging Indication shall be sent on the S3 interface by the MME to the associated SGSN when ISR is activated as part of mobile terminated CS services. The MME gets the related information from SGsAP-PAGING-REQUEST message as specified in 3GPP TS29.118 [21].Table -1 specifies the presence requirements and the conditions of the IEs in the message. NOTE: The SS code received on the SGs interface is not transferred to the SGSN because it is not used by the SGSN. Table -1: Information Element in CS Paging Indication | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 7.4.5 |
6,298 | 8.3.6.9 Protocol configuration options | This IE is included in the message when the network wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the UE and the extended protocol configuration options is not supported by the UE or the network end-to-end for the PDN connection (see clause 6.6.1.1). This IE shall be included if the network supports Local IP address in the traffic flow aggregate description and TFT filter, the PDN Type is different from Non-IP and Ethernet, and the extended protocol configuration options is not supported by the UE or the network end-to-end for the PDN connection (see clause 6.6.1.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 | 8.3.6.9 |
6,299 | 4.7.4.1.1 MS initiated GPRS detach procedure initiation | The GPRS detach procedure is initiated by the MS by sending a DETACH REQUEST message. The detach type information element may indicate "GPRS detach with switching off", "GPRS detach without switching off", "IMSI detach", "GPRS/IMSI detach with switching off" or "GPRS/IMSI detach without switching off". If the MS has a valid P-TMSI, the MS shall include the P-TMSI in the DETACH REQUEST message. The MS shall also include a valid P-TMSI signature, if available. If the MS is not switched off and the MS is in the state GMM_REGISTERED, timer T3321 shall be started after the DETACH REQUEST message has been sent. If the detach type information element value indicates "IMSI Detach" the MS shall enter GMM-REGISTERED.IMSI-DETACH_INITIATED, otherwise the MS shall enter the state GMM-DEREGISTERED-INITIATED. If the detach type information element value indicates "IMSI Detach" or "GPRS/IMSI Detach", state MM IMSI DETACH PENDING is entered. If the MS to be switched off is not a MS using any of the coverage classes of EC-GSM-IoT, the MS shall try for a period of 5 seconds to send the DETACH REQUEST message. If the MS to be switched off is a MS using any of the coverage classes of EC-GSM-IoT, that MS should try for at least a period of 10 seconds to send the DETACH REQUEST message. If the MS is able to send the DETACH REQUEST message during this time the MS may be switched off. If the detach type information element value indicates "GPRS detach without switching off " and the MS is attached for GPRS and non-GPRS services and the network operates in network operation mode I, then if in the MS the timer T3212 is not already running, the timer T3212 shall be set to its initial value and restarted after the DETACH REQUEST message has been sent. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.4.1.1 |
6,300 | 7.3.1 Forward Relocation Request | A Forward Relocation Request message shall be sent from: - the source MME to the target MME over the S10 interface as part of an S1-based handover relocation procedure; - the source MME to the target SGSN, or from the source SGSN to the target MME over the S3 interface as part of an Inter RAT handover and combined hard handover and SRNS relocation procedures; - the source SGSN to the target SGSN over the S16 interface as part of an SRNS Relocation and PS handover procedures; - the source MME to the target SGSN over the S3 interface as part of an SRVCC from E-UTRAN to UTRAN or GERAN with DTM HO support procedures and from the source SGSN to the target SGSN over the S16 interface as part of SRVCC from UTRAN (HSPA) to UTRAN or GERAN with DTM HO support; - the source MME to the target AMF, or from the source AMF to the target MME over the N26 interface as part of the EPS to 5GS handover and 5GS to EPS handover procedures. - the source AMF to the target MME_SRVCC over the N26 interface as part of the 5G-SRVCC from NG-RAN to UTRAN procedure. A source MME/SGSN which supports CIoT knows whether the target MME/SGSN pool or target AMF (5GS) supports some CIoT optimisations either by using DNS procedures enhanced for DCNs or by local configuration, as specified in clause 5.9 of 3GPP TS 29.303[ Domain Name System Procedures; Stage 3 ] [32]. A source AMF knows whether the target MME pool supports SGi Non-IP or Ethernet PDN connections either by using DNS procedures enhanced for DCNs or by local configuration, as specified in clause 5.9 and 5.13 of 3GPP TS 29.303[ Domain Name System Procedures; Stage 3 ] [32]. The target MME/SGSN may forward the Forward Relocation Request to another MME/SGSN in the target MME/SGSN pool which is more suitable to serve the UE, based on the information received in the Forward Relocation Request message, e.g. required CIoT EPS optimisation(s) applicable to the given UE's attachment. NOTE 1: The source MME/SGSN/AMF does not need to know each individual CIoT feature the target MME/SGSN pool or target AMF (5GS) supports. The source MME/SGSN/AMF can behave as if the target MME/SGSN/AMF pool supports all CIoT features when the target MME/SGSN pool is known to support CIoT; the source MME/SGSN/AMF determines then which bearer contexts were successfully transferred as specified in sunclause 7.3.2. NOTE 2: Among the CIoT optimization features, only the support of SCEF Non-IP PDN connection and the support of SGi Non-IP PDN connection are applicable to a SGSN. NOTE 3: 5GS supports Attach without PDU session. 5GS can also support Unstructured and Ethernet PDU session types, which are assimilated to "SGi Non-IP PDN connections" over N26. Forward Relocation procedure across S10 interface (when KASME is taken into use) shall be performed according to the Rules on Concurrent Running of Security Procedures, which are specified in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [12]. When the source MME/SGSN supports one or more of the CIoT optimization features as specified in clause 8.125, the source MME/SGSN shall transfer EPS bearer context(s) for SGi Non-IP PDN connections or for PDN connections to a SCEF only if the target serving node is known to support SGi Non-IP PDN connections or SCEF Non-IP PDN connections respectively, as specified in clause 5.5.1.2.1 and 5.5.2 of 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3]. Likewise, a source AMF shall transfer EPS bearer context(s) for SGi Non-IP PDN connections only if the target MME is known to support SGi Non-IP PDN connections. The source MME/SGSN/AMF shall not proceed with the Forward Relocation Request procedure if the UE does not have any EPS bearer context(s) for SGi IP or Non-IP PDN connections that can be transferred to the target serving node, i.e. under the following conditions: - If the UE is attached to the source MME/SGSN with only the PDN connection(s) of PDN type "non-IP" through the SGW and the PGW, with or without SCEF PDN connections, and the target serving node is known to not support SGi Non-IP PDN Connection (as specified in clause 4.3.17.8.3.3 of 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3] and in clause 5.3.13.8 of 3GPP TS 23 060 [35]); or - If the UE is attached to the source AMF (5GS) with only PDU session(s) of type "Ethernet" or "Unstructured", and the target MME is known to not support SGi Non-IP and Ethernet PDN Connection. The source MME shall transfer the EPS bearer context(s) for the Ethernet PDN connection only if the target serving node is known to support the Ethernet PDN connection, as specified in clause 5.3.3.1 of 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3]. The source MME shall not proceed with the Forward Relocation Request procedure if the UE does not have any EPS bearer context(s) that can be transferred to the target serving node, i.e. under the following conditions: - If the UE is attached to the source MME with only the PDN connection(s) of PDN type "Ethernet" through the SGW and the PGW, and the target serving node is known to not support the Ethernet PDN connection. Table 7.3.1-1 specifies the presence requirements and conditions of the IEs in the message. Table 7.3.1-1: Information Elements in a Forward Relocation Request The PDN Connection grouped IE shall be coded as depicted in Table 7.3.1-2. Table 7.3.1-2: MME/SGSN/AMF UE EPS PDN Connections within Forward Relocation Request The Bearer Context grouped IE shall be coded as depicted in Table 7.3.1-3. Table 7.3.1-3: Bearer Context within MME/SGSN/AMF UE EPS PDN Connections within Forward Relocation Request Table 7.3.1-4: Remote UE Context Connected within MME/SGSN UE EPS PDN Connections within Forward Relocation Request Table 7.3.1-5: MME UE SCEF PDN Connections within Forward Relocation Request Table 7.3.1-6: Subscribed V2X Information within Forward Relocation Request Table 7.3.1-7: PC5 QoS Parameters within Forward Relocation Request Table 7.3.1-8: PGW Change Info with Forward Relocation 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 | 7.3.1 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.