Search is not available for this dataset
doc_id
int64 1
6.72k
⌀ | Section
stringlengths 5
247
⌀ | Content
stringlengths 501
147k
⌀ | Source
stringclasses 456
values | Document Title
stringclasses 22
values | Working Group
stringclasses 21
values | Series Subject
stringclasses 9
values | Subclause
stringlengths 1
13
⌀ |
|---|---|---|---|---|---|---|---|
3,801 | 9.4 Satellite Access | In a 5G system with satellite access, charging data records associated with satellite access(es) shall include the location of the associated UE(s) with satellite access. NOTE: The precision of the location of the UE can be based on the capabilities of the UE or of the network. A 5G system with satellite access supporting S&F Satellite operation shall be able to collect charging information per UE or per application (e.g., number of UEs, data volume, duration, involved satellites). A 5G system with satellite access shall be able to collect charging information for a UE registered to a HPLMN or a VPLMN, for UE-Satellite-UE communication. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 9.4 |
3,802 | 19.7.2 External Identifier | An External Identifier identifies a subscription associated to an IMSI. A subscription associated to an IMSI may have one or several External Identifier(s). The External Identifier shall have the form username@realm as specified in clause 2.1 of IETF RFC 4282 [53]. The username part format of the External Identifier shall contain a Local Identifier as specified in 3GPP TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [98]. The realm part format of the External Identifier shall contain a Domain Identifier as specified in 3GPP TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [98]. As specified in clause 4 of IETF RFC 4282 [53], the Domain Identifier shall be a duly registered Internet domain name. The combination of Local Identifier and Domain Identifier makes the External Identifier globally unique. The result of the External Identifier form is: "<Local Identifier>@<Domain Identifier>" An example of an External Identifier is: Local Identifier in use: "123456789"; Domain Identifier = "domain.com"; Which gives the External Identifier as: [email protected] | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 19.7.2 |
3,803 | 6.2.5A Configured transmitted power for CA | For uplink carrier aggregation the UE is allowed to set its configured maximum output power PCMAX,c for serving cell c and its total configured maximum output power PCMAX. The configured maximum output power PCMAX,c on serving cell c shall be set as specified in subclause 6.2.5. For uplink inter-band carrier aggregation, MPRc and A-MPRc apply per serving cell c and are specified in subclause 6.2.3 and subclause 6.2.4, respectively. P-MPR c accounts for power management for serving cell c. PCMAX,c is calculated under the assumption that the transmit power is increased independently on all component carriers. For uplink intra-band contiguous and non-contiguous carrier aggregation, MPRc = MPR and A-MPRc = A-MPR with MPR and A-MPR specified in subclause 6.2.3A and subclause 6.2.4A respectively. There is one power management term for the UE, denoted P-MPR, and P-MPR c = P-MPR. PCMAX,c is calculated under the assumption that the transmit power is increased by the same amount in dB on all component carriers. The total configured maximum output power PCMAX shall be set within the following bounds: PCMAX_L ≤ PCMAX ≤ PCMAX_H For uplink inter-band carrier aggregation with one serving cell c per operating band when same TTI pattern is used in all aggregated serving cells, PCMAX_L = MIN {10log10∑ MIN [ pEMAX,c/ (tC,c), pPowerClass/(mprc·a-mprc·tC,c ·tIB,c·tProSe) , pPowerClass/pmprc], PPowerClass} PCMAX_H = MIN{10 log10 ∑ pEMAX,c , PPowerClass} where - pEMAX,c is the linear value of PEMAX, c which is given by IE P-Max for serving cell c in [7]; - PPowerClass is the maximum UE power specified in Table 6.2.2A-1 without taking into account the tolerance specified in the Table 6.2.2A-1; pPowerClass is the linear value of PPowerClass; - mpr c and a-mpr c are the linear values of MPR c and A-MPR c as specified in subclause 6.2.3 and subclause 6.2.4, respectively; - pmprc is the linear value of P-MPR c; - tC,c is the linear value of TC,ctC,c = 1.41 when NOTE 2 in Table 6.2.2-1 applies for a serving cell c, otherwise tC,c = 1; - tIB,c is the linear value of the inter-band relaxation term TIB,c of the serving cell c as specified in Table 6.2.5-2; otherwise tIB,c - tProSe is the linear value of TProSe and applies as specified in subclause 6.2.5. For uplink intra-band contiguous and non-contiguous carrier aggregation when same TTI pattern is used in all aggregated serving cells, PCMAX_L = MIN{10 log10 ∑ pEMAX,c - TC , (PPowerClass – ΔPPowerClass) – MAX(MPR + A-MPR + ΔTIB,c + TC + TProSe, P-MPR ) } PCMAX_H = MIN{10 log10 ∑ pEMAX,c , PPowerClass} where - pEMAX,c is the linear value of PEMAX,c which is given by IE P-Max for serving cell c in [7]; - PPowerClass is the maximum UE power specified in Table 6.2.2A-1 without taking into account the tolerance specified in the Table 6.2.2A-1; ΔPPowerClass = 3 dB for a power class 2 capable UE operating in Band 41, when P-max of 23 dBm or lower is indicated or if the uplink/downlink configuration is 0 or 6 in the cell; otherwise, ΔPPowerClass = 0 dB - MPR and A-MPR are specified in subclause 6.2.3A and subclause 6.2.4A respectively; - TIB,c is the additional tolerance for serving cell c as specified in Table 6.2.5-2; - P-MPR is the power management term for the UE; - TC is the highest value TC,c among all serving cells c in the TREF over all Teval durations. TC,c = 1.5 dB when NOTE 2 in Table 6.2.2A-1 applies to the serving cell c, otherwise TC,c = 0 dB; - TProSe applies as specified in subclause 6.2.5. For uplink inter-band carrier aggregation with one serving cell c per operating band when at least one different TTI patterns is used in aggregated cells, the UE is allowed to set its configured maximum output power PCMAX,c(i),i for serving cell c(i) of TTI length i, i = 1,2,3 and its total configured maximum output power PCMAX. The configured maximum output power PCMAX,c(i),i (p) in TTI p of serving cell c(i) on TTI length i shall be set within the following bounds: PCMAX_L,c(i),i (p) ≤ PCMAX,c(i), i (p) ≤ PCMAX_H,c(i),i (p) where PCMAX_L,c(i),i (p) and PCMAX_H,c(i),i (p) are the limits for a serving cell c(i) of TTI length i as specified in subclause 6.2.5. The total UE configured maximum output power PCMAX (p,q,k) in a TTI p of TTI length 1 , a TTI q of TTI length 2 and a TTI k of TTI length 3 that overlap in time shall be set within the following bounds unless stated otherwise: PCMAX_L(p,q,k) ≤ PCMAX (p,q,k) ≤ PCMAX_H (p,q,k) When p, q, k are of different lengths and belong to different cells: PCMAX_L (p,q,k) = MIN {10 log10 [pCMAX_L,c(1),1 (p) + pCMAX_L,c(2),2 (q)+ + pCMAX_L,c(3),3 (k)], PPowerClass} PCMAX_H (p,q,k) = MIN {10 log10 [pCMAX_H,c(1),1 (p) + pCMAX_H,c(2),2 (q) + pCMAX_H,c(3),3 (k)], PPowerClass} where pCMAX_L,c(i),i and pCMAX_H,c(i),i are the respective limits PCMAX_L,c(i),iand PCMAX_H,c(i),i expressed in linear scale. For combinations of intra-band and inter-band carrier aggregation with UE configured for transmission on three serving cells (up to two contiguously aggregated carriers per operating band), For the case when p and q belong to the same band and k belongs to a different band but p, q and k are of the same TTI pattern. PCMAX_L = MIN {10log10∑(pCMAX_L, Bi), PPowerClass} PCMAX_H = MIN{10 log10 ∑ pEMAX,c , PPowerClass} For the case when p and q belong to the same band and are of the same TTI pattern while k belong to a different band and is of different TTI pattern then: PCMAX_L (p,q,k) = MIN {10 log10 [pCMAX_L,Bi(p) + pCMAX_L,c(3),3 (k)], PPowerClass} PCMAX_H (p,q,k) = MIN {10 log10 [pCMAX_H,Bi (p) + pCMAX_H,c(3),3 (k)], PPowerClass} where - pEMAX,c is the linear value of PEMAX, c which is given by IE P-Max for serving cell c in [7]; - PPowerClass is the maximum UE power specified in Table 6.2.2A-0 without taking into account the tolerance specified in the Table 6.2.2A-0; pPowerClass is the linear value of PPowerClass; - pCMAX_L, Bi is the linear values of PCMAX_L as specified in corresponding operating band. PCMAX_L,c specified for single carrier in subclause 6.2.5 applies for operating band supporting one serving cell. PCMAX_L specified for uplink intra-band contiguous carrier aggregation in subclause 6.2.5A applies for operating band supporting two contiguous serving cells. - intra-band carriers use the same TTI patterns. TREF and Teval are specified in Table 6.2.5A-0 when same and different TTI patterns are used in aggregated carriers. For each TREF, the PCMAX_L is evaluated per Teval and given by the minimum value taken over the transmission(s) within the Teval; the minimum PCMAX_L over the one or more Teval is then applied for the entire TREF. PPowerClass shall not be exceeded by the UE during any period of time. Table 6.2.5A-0: PCMAX evaluation window for different TTI patterns If the UE is configured with multiple TAGs and transmissions of the UE on TTI i for any serving cell in one TAG overlap some portion of the first symbol of the transmission on TTI i +1 for a different serving cell in another TAG, the UE minimum of PCMAX_L for TTIs i and i + 1 applies for any overlapping portion of TTIs i and i + 1. PPowerClass shall not be exceeded by the UE during any period of time. In case PC2 and uplink intra-band contiguous CA capable UE receives pEMAX,c in Scell then that applies both to Scell and Pcell once the Scell is activated. The measured maximum output power PUMAX over all serving cells with same TTI pattern shall be within the following range: PCMAX_L – MAX{TL, TLOW(PCMAX_L) } ≤ PUMAX ≤ PCMAX_H + THIGH(PCMAX_H) PUMAX = 10 log10 ∑ pUMAX,c where pUMAX,c denotes the measured maximum output power for serving cell c expressed in linear scale. The tolerances TLOW(PCMAX) and THIGH(PCMAX) for applicable values of PCMAX are specified in Table 6.2.5A-1 and Table 6.2.5A-2 for inter-band carrier aggregation and intra-band carrier aggregation, respectively. The tolerance TL is the absolute value of the lower tolerance for applicable E-UTRA CA configuration as specified in Table 6.2.2A-0, Table 6.2.2A-1 and Table 6.2.2A-2 for inter-band carrier aggregation, intra-band contiguous carrier aggregation and intra-band non-contiguous carrier aggregation, respectively. The measured maximum output power PUMAX over all serving cells, when atleast one TTI has a different TTI pattern, shall be within the following range: P’CMAX_L– MAX{TL, TLOW (P’CMAX_L)} ≤ P’UMAX ≤ P’CMAX_H + THIGH (P’CMAX_H) P’UMAX = 10 log10 ∑ p’UMAX,c where p’UMAX,c denotes the average measured maximum output power for serving cell c expressed in linear scale over TREF. The tolerances TLOW(P’CMAX) and THIGH(P’CMAX) for applicable values of P’CMAX are specified in Table 6.2.5A-1 and Table 6.2.5A-2 for inter-band carrier aggregation and intra-band carrier aggregation, respectively. The tolerance TL is the absolute value of the lower tolerance for applicable E-UTRA CA configuration as specified in Table 6.2.2A-0, Table 6.2.2A-1 and Table 6.2.2A-2 for inter-band carrier aggregation, intra-band contiguous carrier aggregation and intra-band non-contiguous carrier aggregation, respectively. where: P’CMAX_L = MIN{ MIN {10log10∑(pCMAX_L, Bi), PPowerClass} over all overlapping TTIs in TREF} P’CMAX_H = MAX{ MIN{10 log10 ∑ pEMAX,c , PPowerClass} over all overlapping TTIs in TREF} Table 6.2.5A-1: PCMAX tolerance for uplink inter-band CA (two bands) Table 6.2.5A-2: PCMAX tolerance for uplink intra-band CA | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.2.5A |
3,804 | 7.1.2 Echo Response | Table 7.1.2-1 specifies the information elements included in the Echo Response message. The Recovery information element contains the local Restart Counter, which is specified in 3GPP TS 23.007[ Restoration procedures ] [17]) The optional Private Extension contains vendor or operator specific information. Table 7.1.2-1: Information Elements in Echo Response NOTE: Having no Cause IE in the Echo Response message is an exceptional case for a triggered message. Hence, a GTP entity that detects a GTP protocol error, e.g Mandatory IE missing, in the Echo Request message, ignores the IE(s) that are in error and sends Echo Response. In addition it can log the error. | 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.1.2 |
3,805 | 4.11.2.4.1 E-UTRAN Attach | Impact on clause 5.3.2.1 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] from adding support for the optional network functionality dual registration mode: - Step 1: The UE constructs the Attach Request message according to the following principles: - If UE operates in single-registration mode, the UE indicates that it is moving from 5GC and provides a native 4G-GUTI or a 4G-GUTI mapped from 5G GUTI (indicated as native GUTI), if available, otherwise the IMSI, or - If the UE operates in dual-registration mode, the UE indicates that it is moving from 5GC and provides native 4G-GUTI, or - If the UE sent a TAU in step 2 and it was rejected because the MME could not derive the UE identity, the UE provides IMSI. If the UE wants to transfer a PDU Session to EPC as part of the Attach procedure, it includes a PDN CONNECTIVITY Request message in the Attach Request and provides a Request type "Handover", DNN/APN and PDU Session ID of the PDU Session (clause 5.3.2.1 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]). The UE provides the PDU Session ID in PCO as described in clause 4.11.1.1. For PDU Session of Ethernet Type, if the UE and the network support Ethernet PDN Type in EPS which is negotiated during PDU Session Establishment as described in clause 4.11.5, the UE includes PDN Type Ethernet in PDN CONNECTIVITY Request message. If the UE supports URSP provisioning in EPS, the UE also includes the "Indication of URSP Provisioning Support in EPS" in the PCO or in the ePCO in the first PDN CONNECTIVITY Request or during Initial Attach procedure. The PDN CONNECTIVITY Request is sent together with Initial Attach request as described in clause 5.17.8 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the TAU was rejected in step 2 the IP address preservation is not provided. In this case the UE provides IMSI in the Attach Request and does not provide a Request Type "Handover" in the PDN CONNECTIVITY Request if included in the Attach Request. The UE provides an EPS bearer ID for all mapped EPS bearers in the EPS bearer status. For the initial Attach Request the EPS bearer status is empty. NOTE 1: The UE is aware the network is configured to support 5GS-EPS interworking without N26 procedure. The UE does not include the EPS bearer IDs corresponding to the 5G QoS flows to the EPS bearer status. If the UE supports 5GC NAS procedures (see clause 5.17.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), then the UE shall indicate its support of 5G NAS in a NAS indicator. - Step 3: If the UE provided a 4G-GUTI mapped from 5G-GUTI and the MME is configured to support 5GS-EPS interworking without N26 procedure, the MME does not perform step 3, Identification Request to old MME/SGSN/AMF in clause 5.3.2.1 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. NOTE 2: As the 4G-GUTI mapped from 5G-GUTI is unknown identity to the MME, the MME sends an Identity Request to the UE to request the IMSI. The UE responds with Identity Response (IMSI). - Step 8: If the UE indicates that it is moving from 5GC (Attach Request) and the MME is configured to support 5GS-EPS interworking without N26 procedure, the MME sends an Update Location Request message to the HSS+UDM indicating that registration of an AMF at the HSS+UDM, if any, shall not be cancelled. The HSS+UDM does not send Nudm_UECM_DeregistrationNotification to the old AMF. NOTE 3: If the UE does not maintain registration in 5GC, upon reachability time-out, the AMF can implicitly detach the UE and release the possible remaining PDU Sessions in 5GC. - Step 11: The HSS+UDM selects one of the SMF+PGW-C FQDN for one APN based on operator's policy. The HSS+UDM sends selected SMF+PGW-C FQDN along with APN to the MME for the UE. - Step 12: The MME determines the SMF+PGW-C address for the Create Session Request based on the APN received from the UE and the subscription profile received from the HSS+UDM. - Step 13: The SMF+PGW-C uses the PDU Session ID received from the UE in PCO to correlate the transferred PDN connection with the PDU Session in 5GC. In this release, if the Handover Indication is present in the Create Session Request and the SMF+PGW-C detects it corresponds to a PDU Session for a LADN in 5GC, the SMF+PGW-C rejects the request. - Step 14: IP-CAN Session Modification procedure is replaced by SM Policy Association Modification Procedure as described in clause 4.16.5. - Step 17: If the UE indicated support for 5GC NAS procedures (see clause 5.11.3) and the MME supports procedures for interworking with 5GC without N26, the MME may indicate in the Attach Accept, that interworking without N26 is supported. UE handling of this indicator is defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - Step 23a: As a result of the procedure the PGW-U+UPF starts routing DL data packets to the Serving GW for the default and any dedicated EPS bearers established for this PDN connection. - Step 25: Notify Request is sent to HSS/UDM if the network supports the procedures for 5GC interworking without N26 and that the UE is allowed to access 5GC (condition that is identified based on the subscription data). For emergency attach, Notify Request is sent to HSS/UDM if the network supports the procedures for 5GC interworking without N26 and operator policy allows handover of emergency session to 5GS. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.2.4.1 |
3,806 | 4.9.1.3.2 Preparation phase | Figure 4.9.1.3.2-1: Inter NG-RAN node N2 based handover, Preparation phase 1. S-RAN to S-AMF: Handover Required (Target ID, Source to Target transparent container, SM N2 info list, PDU Session IDs, intra system handover indication). NOTE 1: When applicable the message includes the selected NID, see TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10] for the IE that includes the selected NID. The T-AMF, ensures that the selected NID is forwarded to SMF. Source to Target transparent container includes NG-RAN information created by S-RAN to be used by T-RAN and is transparent to 5GC. It also contains for each PDU session the corresponding QoS flows/DRBs information subject to data forwarding. It may also contain DAPS Information if DAPS handover is supported by S-RAN and S-AMF and DAPS handover is requested for one or more DRBs as described in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [9]. It may also contain the time-based handover parameters when time-based trigger condition is used. All PDU Sessions handled by S-RAN (i.e. all existing PDU Sessions with active UP connections) shall be included in the Handover Required message, indicating which of those PDU Session(s) are requested by S-RAN to handover. The SM N2 info includes Direct Forwarding Path Availability if direct data forwarding is available. Direct Forwarding Path Availability indicates whether direct forwarding is available from the S-RAN to the T-RAN. This indication from S-RAN can be based on e.g. the presence of IP connectivity and security association(s) between the S-RAN and the T-RAN. If the source NG RAN and target NG RAN support RACS as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2], the Source to Target transparent container need not carry the UE radio access capabilities (instead the UE Radio Capability ID is supplied from the CN to the T-RAN). However, if the source NG-RAN has knowledge that the target NG-RAN might not have a local copy of the Radio Capability corresponding to the UE Radio Capability ID (i.e. because the source NG-RAN had itself to retrieve the UE's Radio Capability from the AMF) then the source NG-RAN may also send some (or all) of the UE's Radio Capability to the target NG-RAN (the size limit based on local configuration). In the case of inter-PLMN handover, when the source and target NG-RAN support RACS as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2] and the source NG-RAN determines based on local configuration that the target PLMN does not support the UE Radio Capability ID assigned by the source PLMN, then the source NG-RAN includes the UE radio access capabilities in the Source to Target transparent container. 2. T-AMF Selection: When the S-AMF can't serve the UE anymore, the S-AMF selects the T-AMF as described in clause 6.3.5 on "AMF Selection Function" in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 3. [Conditional] S-AMF to T-AMF: Namf_Communication_CreateUEContext Request (N2 Information (Target ID, Source to Target transparent container, SM N2 information list, PDU Session IDs), UE context information (SUPI, Service area restriction, Allowed NSSAI for each Access Type and Partially Allowed NSSAI if available, Tracing Requirements, LTE M Indication, the list of PDU Session IDs along with the corresponding SMF information and the corresponding S-NSSAI(s), PCF ID(s), DNN, UE Radio Capability ID and UE Radio Capability Information, N2 Notify URI). If the subscription information includes Tracing Requirements, the old AMF provides the target AMF with Tracing Requirements. If the old AMF was a consumer of UE related NWDAF services, the old AMF includes information about active analytics subscriptions, i.e. the Subscription Correlation ID(s), NWDAF identifier(s) (i.e. Instance ID or Set ID), Analytics ID(s) and associated Analytics specific data in the Namf_Communication_UEContextTransfer request. Usage of the analytics information by the new AMF is specified in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. In inter PLMN handover case, UE context information includes HPLMN S-NSSAIs corresponding to the Allowed NSSAI for each Access Type and Partially Allowed NSSAI, without Allowed NSSAI and Partially Allowed NSSAI of source PLMN. The target AMF may determine the Allowed NSSAI and Partially Allowed NSSAI based on the HPLMN S-NSSAIs received in step 3, or else the target AMF queries the NSSF by invoking Nnssf_NSSelection_Get service operation with the HPLMN S-NSSAIs and PLMN ID of SUPI. Based on the query result returned from the NSSF, the target AMF determines whether the AMF re-allocation need be triggered and if needed reselects another target AMF. In this case the target AMF selected by the S-AMF is the Initial AMF. And another reselected target AMF is the final target AMF (i.e. T-AMF). The S-AMF initiates Handover resource allocation procedure by invoking the Namf_Communication_CreateUEContext service operation towards the target AMF. When the S-AMF can still serve the UE, this step and step 12 are not needed. If target AMF re-allocation is needed, e.g. due to the inter PLMN handover, the initial AMF invokes Namf_Communication_CreateUEContext request (SUPI, Target 5GAN Node ID, Source to Target Transparent Container, 5GS MM Context, PDU Session ID and its associated S-NSSAI of the VPLMN value for each PDU Session, the corresponding S-NSSAI of HPLMN value for home routed PDU Session(s), Allowed NSSAI, N2 Notify URI) to the selected final target AMF. The N2 Notify URI is the N2 Notify URI of the source AMF, which is used by the T-AMF to send N2 handover notify to the S-AMF. If the information about active analytics subscriptions are received from S-AMF, it is also included them in the Namf_Communication_CreateUEContext request. If Service area restrictions are available in the S-AMF, they may be forwarded to the T-AMF as described in clause 5.3.4.1.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If both Home and Visited PCF ID(s) are provided by the S-AMF, the T-AMF contacts the (V-) PCF identified by the (V-)PCF ID. If the (V-)PCF identified by the (V-)PCF ID is not used or there are no PCF ID(s) received from the S-AMF, the T-AMF may select the PCF(s) as described in clause 6.3.7.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and according to the V-NRF to H-NRF interaction described in clause 4.3.2.2.3.3. The T-AMF informs the S-AMF that the PCF ID is not used, as defined in step 12 and then the S-AMF terminates the AM Policy Association with the PCF identified by the PCF ID. 4. [Conditional] T-AMF to SMF: Nsmf_PDUSession_UpdateSMContext (PDU Session ID, Target ID, T-AMF ID, N2 SM Information). For each PDU Session indicated by S-RAN, the AMF invokes the Nsmf_PDUSession_UpdateSMContext Request to the associated SMF. However, if the S-NSSAI associated with PDU Session is not available in the T-AMF, the T-AMF does not invoke Nsmf_PDUSession_UpdateSMContext for this PDU Session. PDU Session ID indicates a PDU Session candidate for N2 Handover. Target ID corresponds to Target ID provided by S-RAN in step 1. SM N2 Info includes the Direct Forwarding Path Availability if the direct data forwarding is available between the S-RAN and the T-RAN and has been inserted by the S-RAN. If the (T-)AMF detects that the UE moves into a non-allowed area based on Service area restrictions, the (T-)AMF notifies each NF consumer which has subscribed for UE reachability event (e.g. SMFs corresponding to the list of PDU Sessions received in UE Context from (S-)AMF via Namf_EventExposure_Notify that the UE is only reachable for regulatory prioritized services. 5. [Conditional] SMF checks if the Target ID is within the service area of the UPF connecting to NG-RAN. If UE has moved out of the service area of the UPF connecting to NG-RAN, SMF selects a new intermediate UPF according to clause 6.3.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], if available. If redundant transmission is performed for one or more QoS Flows of the PDU Session, the SMF selects two new Intermediate UPFs to support the redundant transmission based on two N3 and N9 tunnels between the T-RAN and the UPF (PSA) as described in clause 5.33.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. In this case, step 6c and 6d are performed between SMF and each T-UPF. 6a. [Conditional] SMF to UPF (PSA): N4 Session Modification Request. If the SMF selects a new UPF to act as intermediate UPF for the PDU Session and the different CN Tunnel Info need be used, the SMF sends N4 Session Modification Request message to UPF (PSA). The SMF provides the CN Tunnel Info (on N9) if the CN Tunnel Info is allocated by the SMF and UL Packet detection rules associate the CN Tunnel Info (on N9) to be installed on the UPF (PSA). If redundant transmission is performed for one or more QoS Flows of the PDU Session and the different CN Tunnel Info need be used, the SMF provides two CN Tunnel Info (on N9) to the UPF (PSA) if the CN Tunnel Info is allocated by the SMF and indicates to the UPF (PSA) one of the CN Tunnel Info is used as redundancy tunnel of the PDU Session. 6b. [Conditional] UPF (PSA) to SMF: N4 Session Modification Response. The UPF (PSA) sends an N4 Session Modification Response message to the SMF. If the UPF (PSA) allocates CN Tunnel Info (on N9) of UPF (PSA), it provides CN Tunnel Info (on N9) to the SMF. If redundant transmission is performed for one or more QoS Flows of the PDU Session, the UPF (PSA) provides two CN Tunnel Info (on N9) of UPF (PSA) to the SMF and indicates the SMF that one CN Tunnel Info is used as redundancy tunnel of the PDU Session as described in in clause 5.33.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The UPF (PSA) associate the CN Tunnel Info (on N9) with UL Packet detection rules provided by the SMF. 6c. [Conditional] SMF to T-UPF (intermediate): N4 Session Establishment Request. If the SMF selects a new intermediate UPF, i.e. the target UPF (T-UPF), for the PDU Session and if CN Tunnel Info is allocated by the T-UPF, an N4 Session Establishment Request message is sent to the T-UPF, providing Packet detection, enforcement and reporting rules to be installed on the T-UPF. The CN Tunnel Info (on N9) of UPF (PSA) for this PDU Session, which is used to setup N9 tunnel, is also provided to the T-UPF. 6d. T-UPF (intermediate) to SMF: N4 Session Establishment Response. The T-UPF sends an N4 Session Establishment Response message to the SMF with DL CN Tunnel Info and UL CN Tunnel Info (i.e. N3 tunnel info). The SMF starts a timer to release the resource of S-UPF, which is to be used in step 13a of the Execution Phase. 7. SMF to T-AMF: Nsmf_PDUSession_UpdateSMContext Response (PDU Session ID, N2 SM Information, Reason for non-acceptance). If at step 5 the SMF has determined that the UPF connecting to NG-RAN can still be used after the handover or has selected a new intermediate UPF, the SMF includes in the Nsmf_PDUSession_UpdateSMContext response the N2 SM Information containing the N3 UP address and the UL CN Tunnel ID of the UPF, the QoS parameters, TSCAI and the User Plane Security Enforcement information for the Target NG-RAN. If redundant transmission is performed for one or more QoS Flows of the PDU Session, two UL CN Tunnel Info are included in the N2 SM Information. If the N2 SM information received at step 4 does not include the Direct Forwarding Path Availability and the SMF knows that there is no indirect data forwarding connectivity between source and target, the N2 SM Information includes a Data forwarding not possible indication. If the SMF indicated that Direct Forwarding is available in step 4, the SMF should further include a "Direct Forwarding Path Availability" indication in the N2 SM information container. The SMF sends the Alternative QoS Profiles, QoS monitoring configuration for congestion information or ECN marking for L4S indicator for QoS Flow (see TS 23.501[ System architecture for the 5G System (5GS) ] [2]) to the Target NG-RAN on a per QoS Flow basis, if available. If the SMF failed to find a suitable I-UPF at step 5, the SMF does not include any N2 SM Information regarding the PDU Session to avoid establishment of radio resources at the target NG-RAN. Instead of that, the SMF provides a reason for non-acceptance. The SMF decides to (based on local policies) either: - trigger re-establishment of PDU Session. After handover procedure, SMF sends N1 message to the UE via the AMF by invoking Namf_Communication_N1N2MessageTransfer containing the cause indicating PDU Session re-establishment is required for the UE; or - keep the PDU Session (the User Plane connection being deactivated); or - release the PDU Session after handover procedure. If the SMF has received notification from (T-)AMF that the UE is only reachable for regulatory prioritized services, the SMF does not include any N2 SM info regarding the PDU Session for non-regulatory prioritized services to avoid establishment of radio resources at the target NG-RAN. If the SMF receives notification from (T-)AMF that UE is only reachable for regulatory prioritized service after this step via Namf_EventExposure_Notify, the SMF deactivates the PDU Session after handover procedure finish if the PDU Session is not for regulatory prioritized services. 8. AMF supervises the Nsmf_PDUSession_UpdateSMContext Response messages from the involved SMFs. The lowest value of the Max delay indications for the PDU Sessions that are candidates for handover gives the maximum time AMF may wait for Nsmf_PDUSession_UpdateSMContext Response messages before continuing with the N2 Handover procedure. At expiry of the maximum wait time or when all Nsmf_PDUSession_UpdateSMContext Response messages are received, AMF continues with the N2 Handover procedure (Handover Request message in step 9). NOTE 2: The delay value for each PDU Session is locally configured in the AMF and implementation specific. 9. T-AMF to T-RAN: Handover Request (Source to Target transparent container, N2 MM Information, N2 SM Information list, Tracing Requirements, UE Radio Capability ID). If the subscription information includes Tracing Requirements, the target AMF provides the target RAN with Tracing Requirements in the Handover Request. T-AMF determines T-RAN based on Target ID. T-AMF may allocate a 5G-GUTI valid for the UE in the AMF and target TAI. Source to Target transparent container is forwarded as received from S-RAN. N2 MM Information includes e.g. security information and Mobility Restriction List if available in the T-AMF. N2 SM Information list includes N2 SM Information received from SMFs for the T-RAN in the Nsmf_PDUSession_UpdateSMContext Response messages received within allowed max delay supervised by the T-AMF mentioned in step 8. T-AMF provides the UE Radio Capability ID to T-RAN if RACS is supported. If the UE Radio Capability ID is included in the Handover Request message and no UE radio access capabilities are provided in the Source to Target transparent container, when there is no corresponding UE radio capabilities set for UE Radio Capability ID at T-RAN, T-RAN shall request the T-AMF to provide the UE radio capabilities set corresponding to UE Radio Capability ID to the T-RAN. If the Source to Target transparent container contains the UE radio access capabilities and the T-RAN did not receive the UE Radio Capability ID from the T-AMF, NG-RAN shall proceed with handover using the received UE radio access capabilities. If the T-RAN received both the UE radio access capabilities and the UE Radio Capability ID, then the T-RAN shall use any locally stored UE radio access capability information corresponding to the UE Radio Capability ID. If none are stored locally, the T-RAN may request the full UE radio access capability information from the core network. If the full UE radio access capability information is not promptly received from the core network, or the T-RAN chooses not to request them, then the T-RAN shall proceed with the UE radio access capabilities sent by the source RAN node. The T-RAN shall not use the UE radio access capability information received from the source RAN node for any other UE with the same the UE Radio Capability ID. 10. T-RAN to T-AMF: Handover Request Acknowledge (Target to Source transparent container, List of PDU Sessions to Hand-over with N2 SM information, List of PDU Sessions that failed to be established with the failure cause given in the N2 SM information element, PDU Set Based Handling Support Indication included in the N2 SM information). Target to Source transparent container includes a UE container with an access stratum part and a NAS part. The UE container is sent transparently via T-AMF, S-AMF and S-RAN to the UE. If DAPS handover is supported by the T-RAN and T-AMF and the DAPS Information for one or more DRBs had been received in the Source to Target Transparent Container, the T-RAN includes the DAPS Response information in the Target to Source Transparent Container as described in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [9]. T-RAN creates List Of PDU Sessions failed to be setup and reason for failure (e.g. T-RAN decision, S-NSSAI is not available, unable to fulfil User Plane Security Enforcement) based on T-RAN determination. The information is provided to the S-RAN. The N2 SM information in the List Of PDU Sessions to Hand-over, contains per each PDU Session ID T-RAN N3 addressing information i.e. N3 UP address and Tunnel ID of T-RAN for the PDU Session. If redundant transmission is performed for one or more QoS Flows of the PDU Session, the T-RAN provides two AN Tunnel Info for the PDU Session in the N2 SM information. The T-RAN indicates to the SMF one of the AN Tunnel Info is used as the redundancy tunnel of the PDU session as described in clause 5.33.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If only one AN Tunnel Info is provided by the Target NG-RAN for the PDU session, the SMF may release these QoS Flows by triggering PDU Session Modification procedure as specified in clause 4.3.3 after the handover procedure. The N2 SM information may also include: - an Indication whether UP integrity protection is performed or not on the PDU Session based on User Plane Security Enforcement information received in N2 SM information in step 9. - if the PDU Session has at least one QoS Flow subject for data forwarding, N3 UP address and Tunnel ID of T-RAN for receiving forwarded data. The T-RAN provides data forwarding addresses for each data forwarding tunnel which it decided to setup. - For each QoS Flow accepted with an Alternative QoS Profile (see TS 23.501[ System architecture for the 5G System (5GS) ] [2]), the Target NG-RAN shall include a reference to the fulfilled Alternative QoS Profile. - For each accepted QoS Flow, QoS Flows status (active/not active) for QoS monitoring configuration for congestion information, established QoS Flows status (active/not active) for ECN marking for L4S. - PDU Set Based Handling Support Indication as described in clause 5.37.5.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 11a. AMF to SMF: Nsmf_PDUSession_UpdateSMContext Request (PDU Session ID, N2 SM response received from T-RAN in step 10). For each N2 SM response received from the T-RAN (N2 SM information included in Handover Request Acknowledge), AMF sends the received N2 SM response to the SMF indicated by the respective PDU Session ID. If no new T-UPF is selected, SMF stores the N3 tunnel info of T-RAN from the N2 SM response if N2 handover is accepted by T-RAN. The SMF/UPF allocates the N3 UP address and Tunnel IDs for indirect data forwarding corresponding to the data forwarding tunnel endpoints established by T-RAN. If a PDU Session is indicated as a rejected PDU Session by the Target NG-RAN with an indication that the PDU session was rejected because User Plane Security Enforcement is not supported in the Target NG-RAN and the User Plane Enforcement Policy indicates "Required" as described in clause 5.10.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the SMF triggers the release of this PDU Session. In all other cases of PDU Session rejection, the SMF can decide whether to release the PDU Session (possibly triggering the re-establishment of the PDU Session as described in step 5) or to deactivate the UP connection of this PDU Session. If some of the QoS Flows of a PDU Session are not accepted by the Target NG-RAN, the SMF shall initiate the PDU Session Modification procedure to remove the non-accepted QoS Flows from the PDU Session(s) after the handover procedure is completed. 11b. [Conditional] SMF to T-UPF: N4 Session Modification Request (T-RAN SM N3 forwarding Information list, indication to allocate DL forwarding tunnel(s) for indirect forwarding) If the SMF selected a T-UPF in step 6a, the SMF updates the T-UPF by providing the T-RAN SM N3 forwarding information list by sending a N4 Session Modification Request to the T-UPF. If indirect forwarding applies based on indication from the S-RAN and the UPF is re-allocated and if the SMF decides to setup the indirect forwarding tunnel on the same T-UPF, the SMF also requests in the N4 Session Modification Request message to the T-UPF, to allocate DL forwarding tunnel(s) for indirect forwarding. Indirect forwarding may be performed via a UPF which is different from the T-UPF, in which case the SMF selects a T-UPF for indirect forwarding. 11c. [Conditional] T-UPF to SMF: N4 Session Modification Response (T-UPF SM N3 forwarding Information list). The T-UPF allocates Tunnel Info and returns an N4 Session Modification Response message to the SMF. The T-UPF SM N3 forwarding info list includes T-UPF N3 address, T-UPF N3 Tunnel identifiers for forwarding data 11d. [Conditional] SMF to S-UPF: N4 Session Modification Request (T-RAN SM N3 forwarding Information list or T-UPF SM N3 forwarding Information list, indication to allocate DL forwarding tunnel(s) for indirect forwarding). If the UPF is re-allocated, this message includes the T-UPF SM N3 forwarding info list. If the UPF is not re-allocated, this message includes the T-RAN SM N3 forwarding info list. If indirect forwarding applies based on indication from NG-RAN and UPF allocates tunnel identities, the SMF indicates in the N4 Session Modification Request message to the S-UPF to allocate DL forwarding tunnel(s) for indirect forwarding. Indirect forwarding may be performed via a UPF which is different from the S-UPF. 11e. [Conditional] S-UPF to SMF: N4 Session Modification Response (S-UPF SM N3 forwarding Information list). The S-UPF allocates Tunnel Info and returns an N4 Session establishment Response message to the SMF. The S-UPF SM N3 forwarding Information list includes S-UPF N3 address, S-UPF N3 Tunnel identifiers for DL data forwarding. 11f. SMF to T-AMF: Nsmf_PDUSession_UpdateSMContext Response (N2 SM Information). The SMF sends an Nsmf_PDUSession_UpdateSMContext Response message per PDU Session to T-AMF. The SMF creates an N2 SM information containing the DL forwarding Tunnel Info to be sent to the S-RAN by the AMF. The SMF includes this information in the Nsmf_PDUSession_UpdateSMContext response. The DL forwarding Tunnel Info can be one of the following information: - If direct forwarding applies, then the SMF includes the T-RAN N3 forwarding information the SMF received in step 11a. - If the indirect forwarding tunnel is setup in step 11b or 11d, then the SMF includes the T-UPF or S-UPF DL forwarding information containing the N3 UP address and the DL Tunnel ID of the UPF. 12. [Conditional] T-AMF to S-AMF: Namf_Communication_CreateUEContext Response (N2 information necessary for S-AMF to send Handover Command to S-RAN including Target to Source transparent container, PDU Sessions failed to be setup list, N2 SM information (N3 DL forwarding Information, PCF ID), [Target AMF ID]). T-AMF supervises the Nsmf_PDUSession_UpdateSMContext Response message from the involved SMFs. At expiry of the maximum wait time or when all Nsmf_PDUSession_UpdateSMContext Response messages are received, T-AMF sends the Namf_Communication_CreateUEContext Response to the S-AMF. The PDU Sessions failed to be setup list includes the List Of PDU Sessions failed to be setup received from target RAN in step 10 and the Non-accepted PDU session List generated by the T-AMF. Non-accepted PDU Session List includes following PDU Session(s) with proper cause value: - Non-accepted PDU Session(s) by the SMF(s); - Non-accepted PDU Session(s) by the AMF due to no response from the SMF within maximum wait time; and - Non-accepted PDU Session(s) by the AMF due to non-available S-NSSAI in the T-AMF, which is decided at step 4. The Target to Source transport container is received from the T-RAN. The N2 SM Information is received from the SMF in step 11f. If target AMF re-allocation is executed in step 3, the selected final target AMF, i.e. T-AMF, invoke Namf_Communication_CreateUEContext Response (Cause, N2 information necessary for S-AMF to send Handover Command to S-RAN including Target to Source transparent container, N2 SM information (PDU Sessions failed to setup list, N3 DL forwarding Information), PCF ID, PCF reselected indication, target AMF ID) to the initial AMF. The cause indicates whether the Relocate UE Context (hand-Over) succeeded or failed. If the target NG RAN has rejected the Handover Request in step 10, the cause indicates a failure due to RAN rejection. The target AMF ID is used for S-AMF to transfer RAN Status to T-AMF directly. Based on the receiving Namf_Communication_CreateUEContext Response, the initial AMF invokes Namf_Communication_CreateUEContext Response towards S-AMF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.9.1.3.2 |
3,807 | 5.7.1 HSS | IMSI is the prime key to the data stored in the HSS. The data held in the HSS is defined in Table 5.7.1-1 here below. The table below is applicable to E-UTRAN in stand-alone operation only. Table 5.7.1-1: HSS data NOTE 1: IMEI and SVN are stored in HSS when the Automatic Device Detection feature is supported, see clause 15.5 of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. NOTE 2: The 'EPS subscribed QoS profile' stored in HSS is complementary to the legacy 'GPRS subscribed QoS profile'. NOTE 3: Void. NOTE 4: How to indicate which of the PDN subscription contexts stored in the HSS is the default one for the UE is defined in stage 3. NOTE 5: To help with the selection of a co-located or topologically appropriate PDN GW and Serving GW, the PDN GW identity shall be in the form of an FQDN. NOTE 6: The "Access Point Name (APN)" field in the table above contains the APN-NI part of the APN. NOTE 7: In this specification, the values "prohibited for SIPTO" and " allowed for SIPTO excluding SIPTO at the local network" correspond to the pre Rel-12 values "prohibited for SIPTO" and "allowed for SIPTO". Actual coding of these values belongs to Stage 3 domain. NOTE 8: There may be at most three default APNs for a given user. One default APN can belong to either of the three PDN types of "IPv4", "IPv6", or "IPv4v6", one default APN can belong to PDN type of "Non-IP" and another default APN can belong to PDN type of "Ethernet". An expired CSG subscription should not be removed from the HSS subscription data before it is removed from the UE's Allowed CSG list or Operator CSG list. When a CSG subscription is cancelled it should be handled as an expired subscription in HSS subscription data to allow for removing it from UE's Allowed CSG list or Operator CSG list first. One (and only one) of the PDN subscription contexts stored in the HSS may contain a wild card APN (see TS 23.003[ Numbering, addressing and identification ] [9]) in the Access Point Name field. The PDN subscription context marked as the default one shall not contain a wild card APN. The PDN subscription context with a wildcard APN shall not contain a statically allocated PDN GW. If the LIPA permission and SIPTO permission flags are both included for a particular APN, they shall be set in a consistent manner, e.g. if the LIPA permission is set to LIPA-only or LIPA-conditional, the SIPTO permission shall be set to SIPTO-prohibited. Conversely, if the SIPTO permission indicates the APN is a SIPTO-allowed APN, the LIPA permission shall be set to LIPA-prohibited. A SIPTO-allowed APN is an APN for which the SIPTO permission is set to allowed for SIPTO excluding SIPTO at the local network, allowed for SIPTO including SIPTO at the local network or allowed for SIPTO at the local network only. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7.1 |
3,808 | 5.5.1 Registration procedure 5.5.1.1 General | The registration procedure is always initiated by the UE and used for initial registration as specified in subclause 5.5.1.2.2 or mobility and periodic registration update as specified in subclause 5.5.1.3.2. When the UE needs to initiate registration over both 3GPP access and non-3GPP access in the same PLMN (e.g. the 3GPP access and the selected N3IWF are located in the same PLMN), the UE: a) in 5GMM-REGISTERED-INITIATED over 3GPP access shall not initiate registration over non-3GPP access; or b) in 5GMM-REGISTERED-INITIATED over non-3GPP access shall not initiate registration over 3GPP access. NOTE 1: To which access (i.e. 3GPP access or non-3GPP access) the UE initiates registration first is up to UE implementation. When the UE is registered with a PLMN over a non-3GPP access, the AMF and the UE maintain: a) registration state and state machine over non-3GPP access; b) 5G NAS security context; c) 5G-GUTI; d) registration area for non-3GPP access, which is associated with a single TAI; and e) non-3GPP de-registration timer in the UE and non-3GPP implicit de-registration timer in the AMF. A registration attempt counter is used to limit the number of subsequently rejected registration attempts. The registration attempt counter shall be incremented as specified in subclause 5.5.1.2.7 or subclause 5.5.1.3.7. Depending on the value of the registration attempt counter, specific actions shall be performed. The registration attempt counter shall be reset when: - the UE is powered on; - a USIM is inserted; - a registration procedure is successfully completed; - an EPS attach, combined EPS attach procedure, a normal or periodic tracking area updating or a combined tracking area updating procedure is successfully completed in S1 mode and the UE is operating in single-registration mode. In this case, the UE shall reset the registration attempt counter for 3GPP access; NOTE 2: The registration attempt counter for non-3GPP access is not impacted by the EPS attach and the combined EPS attach procedure. - a registration procedure is rejected with cause #11, #12, #13, #15, #27, #31, #62, #72, #73, #74, #75, #76, #77 or #78; - a registration procedure is rejected with cause #3, #6 or #7, the REGISTRATION REJECT message is received without integrity protection and the counter for "SIM/USIM considered invalid for GPRS services" events has a value less than a UE implementation-specific maximum value. - a network initiated de-registration procedure is completed with cause #11, #12, #13, #15, #27; #62, #72, #74, #75, #76, #77 or #78; or - a new PLMN or SNPN is selected. Additionally, the registration attempt counter shall be reset when the UE is in substate 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION or 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE, and: - the current TAI is changed; - timer T3502 expires; or - timer T3346 is started. When the registration attempt counter is reset, the UE shall stop timer T3519 if running, and delete any stored SUCI. The lower layers indicate to NAS whether the network supports emergency services for the UE in limited service state (see 3GPP TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [30]). This information is taken into account when deciding whether to initiate an initial registration for emergency services. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.1 |
3,809 | 5.4.4.1.2 Clearing when tones/announcements not provided | When in-band tones and announcements are not provided, the call control entity of the network shall initiate call clearing by stopping all running call control timers, sending a DISCONNECT message without progress indicator, starting timer T305 and entering the "disconnect indication" state. 5.4.4.1.2.1 Receipt of a DISCONNECT message without progress indicator or with progress indicator different from #8 from the network The call control entity of the mobile station in any state except the "null" state, the "disconnect indication" state, and the "release request" state, shall, upon the receipt of a DISCONNECT message without progress indicator information element or with progress indicator different from #8: - stop all running call control timers; - send a RELEASE message; - start timer T308; and - enter the "release request" state. 5.4.4.1.2.2 Receipt of a RELEASE message from the mobile station The call control entity of the network in any state except the "null" state and the "release request" state, shall, upon receipt of a RELEASE message: stop all running call control timers; send a RELEASE COMPLETE message; release the MM connection; and return to the "null" state. 5.4.4.1.2.3 Abnormal cases The call control entity of the network, having entered the "disconnect indication" state after sending a DISCONNECT message without progress indicator or with progress indicator different from #8, shall upon expiry of timer T305: send a RELEASE message to the mobile station with the cause number originally contained in the DISCONNECT message; start timer T308; and enter the "release request" state. In addition to the original clearing cause, the RELEASE message may contain a second cause information element with cause #102 "recovery on timer expiry". | 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.4.4.1.2 |
3,810 | 4.11.5.7 UE or Network Requested PDU Session Release procedure | The following impacts are applicable to clause 4.3.4.2 (UE or network requested PDU Session Release for Non-Roaming and Roaming with Local Breakout) to support interworking with EPS: - Step 2b: If the released PDU Session used APN Rate Control in EPC then the PGW-U+UPF provides the APN Rate Control Status to the SMF if the released PDU Session supported interworking with EPC and it is the last PDU Session to the DNN that is the same as the APN identified in the APN Rate Control Status. - Step 3: If the PGW-U+UPF provided APN Rate Control Status to the SMF then the SMF provides the APN Rate Control Status to the AMF. The following impacts are applicable to clause 4.3.4.3 (UE or network requested PDU Session Release for Home-routed Roaming) to support interworking with EPS: - Step 2b: Same impact as for step 2b for the Non-roaming and Roaming with Local Breakout case above. - Step 3: Same impact as for step 3 for the Non-roaming and Roaming with Local Breakout case above. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.5.7 |
3,811 | 4.7.1.10 Handling of 3GPP PS data off | An MS, which supports 3GPP PS data off (see 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74]), can be configured with up to two lists of 3GPP PS data off exempt services as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] or in the EF3GPPPSDATAOFF USIM file as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112]: - a list of 3GPP PS data off exempt services to be used in the HPLMN or EHPLMN (if the EHPLMN list is present); and - a list of 3GPP PS data off exempt services to be used in the VPLMN. If only the list of 3GPP PS data off exempt services to be used in the HPLMN or EHPLMN (if the EHPLMN list is present) is configured at the MS, this list shall be also used in the VPLMN. If the MS supports 3GPP PS data off, the MS shall provide the 3GPP PS data off UE status in the protocol configuration options IE during PDP context activation procedure (see subclause 6.1.3.1). The network informs the MS about the support of 3GPP PS data off during PDP context activation procedure as specified in subclause 6.1.3.1. If 3GPP data off support is not indicated in the protocol configuration options IE in the ACTIVATE PDP CONTEXT ACCEPT message, the MS shall not indicate any change of 3GPP PS data off UE status for the PDN connection established by the PDP context activation procedure; otherwise the MS shall indicate change of the 3GPP PS data off UE status for the PDN connection by using the PDP context modification procedure as specified in subclause 6.1.3.3. If the network does not provide indication of support of 3GPP PS data off during PDP context activation procedure, the MS behaviour for non-exempt service requests from the network is implementation dependent. When the 3GPP PS data off UE status is "activated": a) the MS does not send uplink IP packets except: - for those services indicated in the list of 3GPP PS data off exempt services to be used in the HPLMN or EHPLMN (if the EHPLMN list is present) as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] when the MS is in its HPLMN or EHPLMN (if the EHPLMN list is present); - for those services indicated in the list of 3GPP PS data off exempt services to be used in the HPLMN or EHPLMN (if the EHPLMN list is present) when the MS is in the VPLMN, if only the list of 3GPP PS data off exempt services to be used in the HPLMN or EHPLMN (if the EHPLMN list is present) is configured to the MS as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135]; - for those services indicated in the list of 3GPP PS data off exempt services to be used in the VPLMN when the MS is in the VPLMN, if the list of 3GPP PS data off exempt services to be used in the VPLMN is configured to the MS as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135]; - for those services indicated in the EF3GPPPSDATAOFF USIM file as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112]; and - any uplink traffic due to procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [13D]; and b) the MS does not send uplink non-IP user data packets. Otherwise the MS sends uplink user data packets without restriction. NOTE: If the MS supports 3GPP PS data off, uplink IP packets are filtered as specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [13D] in subclause B.3.1.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.7.1.10 |
3,812 | 6.3.5 Re-synchronisation procedure | A VLR/SGSN may send two types of authentication data requests to the HE/AuC, the (regular) one described in subsection 6.3.2 and one used in case of synchronisation failures, described in this subsection. Upon receiving a synchronisation failure message from the user, the VLR/SGSN sends an authentication data request with a "synchronisation failure indication" to the HE/AuC, together with the parameters: - sent to the MS in the preceding user authentication request, and - AUTS received by the VLR/SGSN in the response to that request, as described in subsection 6.3.3. An VLR/SGSN will not react to unsolicited "synchronisation failure indication" messages from the MS. The VLR/SGSN does not send new user authentication requests to the user before having received the response to its authentication data request from the HE/AuC (or before it is timed out). When the HE/AuC receives an authentication data request with a "synchronisation failure indication" it acts as follows: 1. The HE/AuC retrieves SQNMS from Conc(SQNMS) by computing Conc(SQNMS) Å f5*K(RAND). 2. The HE/AuC checks if SQNHE is in the correct range, i.e. if the next sequence number generated SQNHE using would be accepted by the USIM. 3. If SQNHE is in the correct range then the HE/AuC continues with step (6), otherwise it continues with step (4). 4. The HE/AuC verifies AUTS (cf. subsection 6.3.3). 5. If the verification is successful the HE/AuC resets the value of the counter SQNHE to SQNMS. 6. The HE/AuC sends an authentication data response with a new batch of authentication vectors to the VLR/SGSN. If the counter SQNHE was not reset then these authentication vectors can be taken from storage, otherwise they are newly generated after resetting SQNHE. In order to reduce the real-time computation burden on the HE/AuC, the HE/AuC may also send only a single authentication vector in the latter case. Whenever the VLR/SGSN receives a new batch of authentication vectors from the HE/AuC in an authentication data response to an authentication data request with synchronisation failure indication it deletes the old ones for that user in the VLR/SGSN. The user may now be authenticated based on a new authentication vector from the HE/AuC. Figure 12 shows how re-synchronisation is achieved by combining a user authentication request answered by a synchronisation failure message (as described in section 6.3.3) with an authentication data request with synchronisation failure indication answered by an authentication data response (as described in this section). Figure 12: Resynchronisation mechanism | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.3.5 |
3,813 | 5.2.6.25.2 Nnef_TimeSynchronization_ConfigCreate operation | Service operation name: Nnef_TimeSynchronization_ConfigCreate Description: The consumer requests to create a time synchronization configuration and activate the time synchronization service with the configuration, for which the NEF authorizes the request and invokes the corresponding service operation with TSCTSF (clause 5.2.27.2.2). Inputs, Required: As specified in clause 5.2.27.2.2. Inputs, Optional: As specified in clause 5.2.27.2.2. Outputs, Required: Operation execution result indication and in the case of successful operation, any outputs as specified in clause 5.2.27.2.2. Outputs, Optional: As specified in clause 5.2.27.2.2. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.25.2 |
3,814 | 6.4.2.4 Dedicated EPS bearer context activation not accepted by the UE | Upon receipt of the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, the UE may reject the request from the MME by sending an ACTIVATE DEDICATED EPS BEARER CONTEXT REJECT message. The message shall include the EPS bearer identity and an ESM cause value indicating the reason for rejecting the dedicated EPS bearer context activation request. The ACTIVATE DEDICATED EPS BEARER CONTEXT REJECT message contains an ESM cause that typically indicates one of the following ESM cause values: #26: insufficient resources; #31: request rejected, unspecified; #41: semantic error in the TFT operation; #42: syntactical error in the TFT operation; #43: invalid EPS bearer identity; #44: semantic error(s) in packet filter(s); #45: syntactical error(s) in packet filter(s); or #95 – 111: protocol errors. The UE shall check the TFT in the request message for different types of TFT IE errors as follows: a) Semantic errors in TFT operations: 1) When the TFT operation is an operation other than "Create a new TFT" The UE shall reject the activation request with ESM cause #41 "semantic error in the TFT operation". b) Syntactical errors in TFT operations: 1) When the TFT operation = "Create a new TFT" and the packet filter list in the TFT IE is empty. 2) When there are other types of syntactical errors in the coding of the TFT IE, such as a mismatch between the number of packet filters subfield, and the number of packet filters in the packet filter list. The UE shall reject the activation request with ESM cause #42 "syntactical error in the TFT operation". c) Semantic errors in packet filters: 1) When a packet filter consists of conflicting packet filter components which would render the packet filter ineffective, i.e. no IP packet will ever fit this packet filter. How the UE determines a semantic error in a packet filter is outside the scope of the present document. 2) When the resulting TFT does not contain any packet filter which applicable for the uplink direction. The UE shall reject the activation request with ESM cause #44 "semantic errors in packet filter(s)". d) Syntactical errors in packet filters: 1) When the TFT operation = "Create a new TFT" and two or more packet filters in the resultant TFT would have identical packet filter identifiers. 2) When the TFT operation = "Create a new TFT" and two or more packet filters in all TFTs associated with this PDN connection would have identical packet filter precedence values. 3) When there are other types of syntactical errors in the coding of packet filters, such as the use of a reserved value for a packet filter component identifier. In case 2, if the old packet filters do not belong to the default EPS bearer context, the UE shall not diagnose an error, shall further process the new activation request and, if it was processed successfully, shall delete the old packet filters which have identical filter precedence values. Furthermore, by means of explicit peer-to-peer signalling between the network and the UE, the UE shall perform a UE requested bearer resource modification procedure to delete the packet filters in the network corresponding to the packet filters it has deleted on the UE side. In case 2, if one or more old packet filters belong to the default EPS bearer context, the UE shall release the relevant PDN connection. If the relevant PDN connection is the last one that the UE has and EMM-REGISTERED without PDN connection is not supported by the UE or the MME, the UE shall detach and re-attach to the network. In cases 1 and 3 the UE shall reject the activation request with ESM cause #45 "syntactical errors in packet filter(s)". Upon receipt of the ACTIVATE DEDICATED EPS BEARER CONTEXT REJECT message in state BEARER CONTEXT ACTIVE PENDING, the MME shall stop the timer T3485, enter the state BEARER CONTEXT INACTIVE and abort the dedicated EPS bearer context activation procedure. The MME also requests the lower layer to release the radio resources that were established during the dedicated EPS bearer context activation procedure. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.4.2.4 |
3,815 | 10.9 IAB Resource Configuration | If the IAB-DU and the IAB-MT of an IAB-node are subject to a half-duplex constraint, correct transmission/reception by one cannot be guaranteed during transmission/reception by the other and vice versa, e.g., when collocated and operating in the same frequency. If an IAB-node supports enhanced frequency or spatial multiplexing capabilities, additional multiplexing modes can be supported, i.e., simultaneous operation of IAB-MT Rx / IAB-DU Rx, IAB-MT Tx / IAB-DU Tx, IAB-MT Rx / IAB-DU Tx, IAB-MT Tx / IAB-DU Rx. An IAB-node can report its duplexing constraints between the IAB-MT and the collocated IAB-DU via F1AP. An IAB-node can indicate via F1AP whether or not FDM is required for an enhanced multiplexing operation. The scheduler on an IAB-DU or IAB-donor-DU complies with the gNB-DU resource configuration received via F1AP, which defines the usage of scheduling resources to account for the aforementioned duplexing constraint. The resource configuration assigns an attribute of hard, soft or unavailable to each symbol of each DU cell. Transmission/reception can occur for symbols configured as hard, whereas scheduling cannot occur, except for some special cases, for symbols configures as unavailable. For symbols configured as soft, scheduling can occur conditionally on an explicit indication of availability by the parent node via DCI format 2_5, or on an implicit determination of availability by the IAB-node. The implicit determination of availability is determined by the IAB-node depending on whether or not the operation of the IAB-DU would have an impact on the collocated IAB-MT. The resource configuration can be shared among neighbouring IAB-nodes and IAB-donors to facilitate interference management, dual connectivity, and enhanced multiplexing. To facilitate transitioning from IAB-MT to IAB-DU operation and vice versa, guard symbols can be used to overcome potentially misaligned symbol boundaries between the IAB-MT operation and the IAB-DU operation (e.g., IAB-MT Rx boundaries are not aligned with the IAB-DU Tx boundaries). Specifically, an IAB-node can indicate to a parent node a number of desired guard symbols, while the parent node can indicate to the IAB-node the number of actually provided guard symbols for specific transitions. An IAB-node supporting enhanced multiplexing capabilities, i.e., IAB-MT Rx / IAB-DU Rx, IAB-MT Tx / IAB-DU Tx, IAB-MT Rx / IAB-DU Tx, IAB-MT Tx / IAB-DU Rx, can provide via MAC-CE to a parent node information to facilitate scheduling for enhanced multiplexing operation by the IAB-node, specifically: - recommended IAB-MT's Tx/Rx beams; - desired IAB-MT Tx PSD range; - desired parent node's IAB-DU Tx power adjustment; - required IAB-MT's uplink transmission timing mode. Correspondingly, the parent node can provide information via MAC-CE to the IAB-node to facilitate enhanced multiplexing at the IAB-node and/or at the parent node: - restricted IAB-DU Tx beams; - actual parent node's IAB-DU Tx power adjustment; - IAB-MT's uplink transmission timing mode. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 10.9 |
3,816 | 6.4 Permanent Equipment Identifier (PEI) | In 5GS, the Permanent Equipment Identifier (PEI) identifies a UE. The PEI is defined as: - a PEI type: in this release of the specification, it may indicate an IMEI or IMEISV, a MAC address or an IEEE Extended Unique Identifier (EUI-64); and - dependent on the value of the PEI type: - an IMEI as defined in clause 6.2.1; or - an IMEISV as defined in clause 6.2.2; or - a MAC address (48-bit MAC identifier, as defined in IETF RFC 7042 [132]); or - an IEEE Extended Unique Identifier (EUI-64), for UEs not supporting any 3GPP access technologies, as defined in IEEE "Guidelines for Use of Extended Unique Identifier (EUI), Organizationally Unique Identifier (OUI), and Company ID (CID)" [136]. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.4 |
3,817 | 10.5.4.5 Bearer capability | The purpose of the bearer capability information element is to describe a bearer service. The use of the bearer capability information element in relation to compatibility checking is described in annex B. The bearer capability information element is coded as shown in figure 10.5.88/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and tables 10.5.102/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] to 10.5.115/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The bearer capability is a type 4 information element with a minimum length of 3 octets and a maximum length of 16 octets. Figure 10.5.88/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Bearer capability information element NOTE 1: The coding of the octets of the bearer capability information element is not conforming to ITU Recommendation Q.931 [53]. An MS shall encode the Bearer Capability infomation element according to A/Gb mode call control requirements also if it is requesting for a service in Iu mode, with the following exceptions: 1. A mobile station not supporting A/Gb mode and GERAN Iu mode for the requested bearer service shall set the following parameters to the value "0": - Maximum number of traffic channels (octet 6e, bits 1-3) - Acceptable Channel coding(s) (octet 6e, bits 4, 5 and 7) 2. Furthermore, a mobile station not supporting A/Gb mode and GERAN Iu mode for the requested bearer service shall also set the following parameters to the value "0", if the respective octets have to be included in the bearer capability information element according to subclause 10.5.4.5.1 and 3GPP TS 27.001[ General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS) ] [36]: - UIMI, User initiated modification indication (octet 6f, bits 5-7) - Acceptable Channel Codings extended (octet 6g, bits 5-7) For UTRAN Iu mode the following parameters are irrelevant for specifying the radio access bearer, because multiple traffic channels (multislot) are not deployed, see 3GPP TS 23.034[ High Speed Circuit Switched Data (HSCSD); Stage 2 ] [104]. However, the parameters if received, shall be stored in the MSC, and used for handover to A/Gb or GERAN Iu mode: - Maximum number of traffic channels (octet 6e, bits 1-3) - Acceptable Channel coding(s) (octet 6e, bits 4, 5 and 7) - UIMI, User initiated modification indication (octet 6f, bits 5-7) - Acceptable Channel Codings extended (octet 6g, bits 5-7) NOTE 2: The following parameters are relevant in UTRAN Iu mode for non transparent data calls for deciding which RLP version to negotiate in order to avoid renegotiation of RLP version in case of inter-system handover from UTRAN Iu mode to A/Gb or GERAN Iu mode, see 3GPP TS 24.022[ Radio Link Protocol (RLP) for circuit switched bearer and teleservices ] [141]: - Maximum number of traffic channels (octet 6e, bits 1-3) - Wanted air interface user rate (octet 6f, bits 1- 4) - UIMI, User initiated modification indication (octet 6f, bits 5-7). Table 10.5.102/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Bearer capability information element (continued...) Table 10.5.102/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Bearer capability information element (continued) Table 10.5.103/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Bearer capability information element Table 10.5.104/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Bearer capability information element Table 10.5.105/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Bearer capability information element Table 10.5.106/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Bearer capability information element Table 10.5.107/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Bearer capability information element Table 10.5.108/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Bearer capability information element Table 10.5.109/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Bearer capability information element Table 10.5.110/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Bearer capability information element Table 10.5.111/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Bearer capability information element Table 10.5.112/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Bearer capability information element Table 10.5.113/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Bearer capability information element Table 10.5.114/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Bearer capability information element Table 10.5.115/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Bearer capability information element Table 10.5.115a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Bearer capability 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.5 |
3,818 | 4.6 EPS Mobility Management and Connection Management states 4.6.1 General | The EPS Mobility Management (EMM) states describe the Mobility Management states that result from the mobility management procedures e.g. Attach and Tracking Area Update procedures. Two EMM states are described in this document: - EMM-DEREGISTERED. - EMM-REGISTERED. NOTE 1: Other specifications may define more detailed EMM states (see e.g. TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [46]). The EPS Connection Management (ECM) states describe the signalling connectivity between the UE and the EPC. Two ECM states are described in this document: - ECM-IDLE. - ECM-CONNECTED. NOTE 2: The ECM-CONNECTED and ECM-IDLE states used in this document correspond respectively to the EMM-CONNECTED and EMM-IDLE modes defined in TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [46]. In general, the ECM and EMM states are independent of each other. Transition from EMM-REGISTERED to EMM-DEREGISTERED can occur regardless of the ECM state, e.g. by explicit detach signalling in ECM-CONNECTED or by implicit detach locally in the MME during ECM-IDLE. However there are some relations, e.g. to transition from EMM-DEREGISTERED to EMM-REGISTERED the UE has to be in the ECM-CONNECTED state. | 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.6 |
3,819 | 6.5.1F Frequency error for UE category NB1 and NB2 | For UE category NB1 and NB2, the UE modulated carrier frequency shall be accurate to within the following limits Table 6.5.1F-1: Frequency error requirement for UE category NB1 and NB2 Observed over a period of one time slot (0.5 ms for 15 kHz sub-carrier spacing and 2 ms excluding the 2304Ts gap for 3.75 kHz sub-carrier spacing) and averaged over 72/LCtone slots (where LCtone = {1, 3, 6, 12} is the number of sub-carriers used for the transmission), compared to the carrier frequency received from the E-UTRA Node B. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.5.1F |
3,820 | 6.5.2A.1 Error Vector Magnitude | For the intra-band contiguous and non-contiguous carrier aggregation, the Error Vector Magnitude requirement should be defined for each component carrier. Requirements only apply with PRB allocation in one of the component carriers. Similar transmitter impairment removal procedures are applied for CA waveform before EVM calculation as is specified for non-CA waveform in sub-section 6.5.2.1. When a single component carrier is configured Table 6.5.2.1.1-1 apply. The EVM requirements are according to Table 6.5.2A.1-1 if CA is configured in uplink with the parameters defined in Table 6.5.2.1.1-2. Table 6.5.2A.1-1: Minimum requirements for Error Vector Magnitude | 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.5.2A.1 |
3,821 | B.3.1 Compatibility checking with addressing information | If an incoming SETUP message is offered to the MS with addressing information (i.e. sub-address or called party number) the following shall occur: a) if the MS has a DDI number or a sub-address, then the information in any Called Party BCD Number or any Called Party subaddress information elements of the incoming SETUP message shall be checked by the MS against the corresponding part of the number assigned to the user (e.g. for DDI) or the user's own sub-address. In the cases of a mismatch, the MS shall release the call. In the case of a match, the compatibility checking described in B.3.2 and B.3.3 shall be performed. b) if the MS has no DDI number and no sub-address, then the Called Party BCD Number and Called Party Sub-address information element shall be ignored for the purposes of compatibility checking. The compatibility checking described in B.3.2 and B.3.3 shall be performed. NOTE: According to the user's requirements, compatibility checking can be performed in various ways from the viewpoint of execution order and information to be checked, e.g. first DDI number/sub-address and then bearer capability or vice versa. | 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 | B.3.1 |
3,822 | 4.11.0a.10 UE requested bearer resource modification procedure | To support URSP Provisioning in EPS, the following enhancement to clause 5.4.5 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] applies: - Steps 1, if the UE received the Indication of URSP Provisioning Support in eEPS in ePCO from SMF+PGW-C in the PDN Connectivity Accept message (as described in clause 4.11.0a.5), the UE includes the UE Policy Container ePCO in the Request Bearer Resource Modification message. - Step 4 (replaced by SM Policy Association Modification procedure as described in clause 4.11.0a.2a.2.1), SMF+PGW-C forwards the UE Policy Container received from the UE to the PCF for the PDU Session, which triggers UE Policy Association establishment as specified in clause 4.11.0a.2a.5. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.0a.10 |
3,823 | 4.22.5A Suspend and Resume Traffic Duplication | After the MA PDU session is established and the Redundant steering mode is active, the UPF may suspend traffic duplication by sending PMF-Suspend Duplication Request to the UE via the user plane of any available access of the MA PDU session as described in clause 5.32.5.6 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The UPF may resume traffic duplication for a UE by sending PMF-Resume Duplication Request via the user plane of any available access of the MA PDU session as described in clause 5.32.5.6 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.22.5A |
3,824 | 15.4.3 O&M requirements | Operators should be able to configure the energy saving function. The configured information should include: - The ability of an NG-RAN node to perform autonomous cell switch-off; - The ability of an NG-RAN node to request the re-activation of a configured list of inactive cells owned by a peer NG-RAN node. O&M may also configure: - policies used by the NG-RAN node for cell switch-off decision; - policies used by peer NG-RAN nodes for requesting the re-activation of an inactive cell; - The minimum time an NG-RAN node's cell should remain activated upon reception of a re-activation request from an eNB. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 15.4.3 |
3,825 | 4.22.2 Authentication and authorization of UAV | The 5GS supports the USS UAV Authorization and Authentication (UUAA) procedure for a UE supporting UAS services. Depending on operator policy or regulatory requirements, the UUAA-MM procedure can be performed by the UE and the AMF at a registration procedure as specified in subclause 5.5.1.2 or the UUAA-SM procedure can be performed by the UE and the SMF at a PDU session establishment procedure as specified in subclause 6.4.1.2. The UE shall support UUAA-MM and UUAA-SM, and the network shall support UUAA-SM and may optionally support UUAA-MM. The UUAA procedure needs to be performed by 5GS with USS successfully before the connectivity for UAS services is established. During the registration procedure as described in subclause 5.5.1.2, the UE supporting UAS services provides CAA-level UAV ID to the AMF, and the AMF may trigger the UUAA-MM procedure. If the UE supporting UAS services does not provide CAA-level UAV ID to the AMF and the network is configured to perform UUAA-MM at registration procedure, the AMF may accept the registration request and shall mark in the UE's 5GMM context that the UE is not allowed to request UAS services. If the UE wants to use the UAS services by providing the CAA-Level UAV ID later on, the UE shall perform the registration procedure for mobility and periodic registration update. When a UE supporting UAS services requests to establish a PDU session as described in subclause 6.4.1.2 for USS communication, the UE provides CAA-level UAV ID to the network, and the SMF may trigger the UUAA-SM procedure based on the DNN and S-NSSAI combination for aerial services according to the user's subscription data and the CAA-level UAV ID provided by the UE. If the UE does not provide CAA-level UAV ID and the user’s subscription data for the UE requires the UUAA-SM, the network rejects the UE-requested PDU session establishment procedure for the UAS services. The UE supporting UAS services shall not provide CAA-level UAV ID to the network over non-3GPP access, and the network shall not perform UUAA procedure for non-3GPP access and shall ensure that the UE is not allowed to access any aerial services in non-3GPP access. If provided by the upper layers, the UE supporting UAS services provides to the network the USS address during the registration procedure or PDU session establishment procedure so that the network uses the information to discover the USS. NOTE: The parameters (e.g., CAA-level UAV ID or USS address) sent by a UE supporting UAS services to the network for UAS services are included in the Service-level-AA container IE which is a non-cleartext IE. After successful UUAA procedure, either the AMF or the SMF may initiate re-authentication of the UAV when required by the USS. If UUAA-MM fails during a re-authentication and there are PDU sessions established using UAS services, the AMF shall request the SMF to perform the release of these PDU sessions and may trigger a network-initiated de-registration procedure based on operator policy. If UUAA-SM fails during a re-authentication, the SMF shall release the PDU session related to re-authentication. If the UUAA is revoked, the PDU session related to the UAS services shall be released by the SMF. Based on operator policy, the AMF may decide to keep the UE registered or trigger a de-registration procedure. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.22.2 |
3,826 | – SL-SDAP-Config | The IE SL-SDAP-Config is used to set the configurable SDAP parameters for a Sidelink DRB. SL-SDAP-Config information element -- ASN1START -- TAG-SL-SDAP-CONFIG-START SL-SDAP-Config-r16 ::= SEQUENCE { sl-SDAP-Header-r16 ENUMERATED {present, absent}, sl-DefaultRB-r16 BOOLEAN, sl-MappedQoS-Flows-r16 CHOICE { sl-MappedQoS-FlowsList-r16 SEQUENCE (SIZE (1..maxNrofSL-QFIs-r16)) OF SL-QoS-Profile-r16, sl-MappedQoS-FlowsListDedicated-r16 SL-MappedQoS-FlowsListDedicated-r16 } OPTIONAL, -- Need M sl-CastType-r16 ENUMERATED {broadcast, groupcast, unicast, spare1} OPTIONAL, -- Need M ... } SL-MappedQoS-FlowsListDedicated-r16 ::= SEQUENCE { sl-MappedQoS-FlowsToAddList-r16 SEQUENCE (SIZE (1..maxNrofSL-QFIs-r16)) OF SL-QoS-FlowIdentity-r16 OPTIONAL, -- Need N sl-MappedQoS-FlowsToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofSL-QFIs-r16)) OF SL-QoS-FlowIdentity-r16 OPTIONAL -- Need N } -- TAG-SL-SDAP-CONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,827 | 5.5.2 Measurement configuration 5.5.2.1 General | The network applies the procedure as follows: - to ensure that, whenever the UE has a measConfig associated with a CG, it includes a measObject for the SpCell and for each NR SCell of the CG to be measured; - to configure at most one measurement identity across all CGs using a reporting configuration with the reportType set to reportCGI; - to configure at most one measurement identity per the node hosting PDCP entity using a reporting configuration with the ul-DelayValueConfig; - to configure at most one measurement identity per the node hosting PDCP entity using a reporting configuration with the ul-ExcessDelayConfig; - to ensure that, in the measConfig associated with a CG: - for all SSB based measurements there is at most one measurement object with the same ssbFrequency; - an smtc1 included in any measurement object with the same ssbFrequency has the same value and that an smtc2 included in any measurement object with the same ssbFrequency has the same value and that an smtc3list included in any measurement object with the same ssbFrequency has the same value and that an smtc4list included in any measurement object with the same ssbFrequency has the same value; - to ensure that all measurement objects configured in this specification and in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] with the same ssbFrequency have the same ssbSubcarrierSpacing; - to ensure that, if a measurement object associated with the MCG has the same ssbFrequency as a measurement object associated with the SCG: - for that ssbFrequency, the measurement window according to the smtc1 configured by the MCG includes the measurement window according to the smtc1 configured by the SCG, or vice-versa, with an accuracy of the maximum receive timing difference specified in TS 38.133[ NR; Requirements for support of radio resource management ] [14]. - if both measurement objects are used for RSSI measurements, bits in measurementSlots in both objects corresponding to the same slot are set to the same value. Also, the endSymbol is the same in both objects. - to ensure that, if a measurement object has the same ssbFrequency as a measurement object configured in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]: - for that ssbFrequency, the measurement window according to the smtc configured in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] includes the measurement window according to the smtc1 configured in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] , or vice-versa, with an accuracy of the maximum receive timing difference specified in TS 38.133[ NR; Requirements for support of radio resource management ] [14]. - if both measurement objects are used for RSSI measurements, bits in measurementSlots in both objects corresponding to the same slot are set to the same value. Also, the endSymbol is the same in both objects. - when the UE is in NE-DC, NR-DC, or NR standalone, to configure at most one measurement identity across all CGs using a reporting configuration with the reportType set to reportSFTD; For CSI-RS resources, the network applies the procedure as follows: - to ensure that all CSI-RS resources configured in each measurement object have the same center frequency, (startPRB+floor(nrofPRBs/2)) - to ensure that the total number of CSI-RS resources configured in each measurement object does not exceed the maximum number specified in TS 38.214[ NR; Physical layer procedures for data ] [19]. The UE shall: 1> if the received measConfig includes the measObjectToRemoveList: 2> perform the measurement object removal procedure as specified in 5.5.2.4; 1> if the received measConfig includes the measObjectToAddModList: 2> perform the measurement object addition/modification procedure as specified in 5.5.2.5; 1> if the received measConfig includes the reportConfigToRemoveList: 2> perform the reporting configuration removal procedure as specified in 5.5.2.6; 1> if the received measConfig includes the reportConfigToAddModList: 2> perform the reporting configuration addition/modification procedure as specified in 5.5.2.7; 1> if the received measConfig includes the quantityConfig: 2> perform the quantity configuration procedure as specified in 5.5.2.8; 1> if the received measConfig includes the measIdToRemoveList: 2> perform the measurement identity removal procedure as specified in 5.5.2.2; 1> if the received measConfig includes the measIdToAddModList: 2> perform the measurement identity addition/modification procedure as specified in 5.5.2.3; 1> if the received measConfig includes the measGapConfig: 2> perform the measurement gap configuration procedure as specified in 5.5.2.9; 1> if the received measConfig includes the measGapSharingConfig: 2> perform the measurement gap sharing configuration procedure as specified in 5.5.2.11; 1> if the received measConfig includes the s-MeasureConfig: 2> if s-MeasureConfig is set to ssb-RSRP, set parameter ssb-RSRP of s-MeasureConfig within VarMeasConfig to the threshold value of the RSRP indicated by the received value of s-MeasureConfig which is derived as specified in 6.3.2; 2> else, set parameter csi-RSRP of s-MeasureConfig within VarMeasConfig to the threshold value of the RSRP indicated by the received value of s-MeasureConfig which is derived as specified in 6.3.2. 1> if the received measConfig includes the effectiveMeasWindowConfig: 2> perform the effective measurement window configuration as specified in 5.5.2.12; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.2 |
3,828 | 5.2.21.2.3 Nnsacf_NSAC_EACNotify service operation | Service Operation name: Nnsacf_NSAC_EACNotify Description: The NSACF is configured with the information about which network slices are subject to NSAC. The NSACF may trigger notification to the consumer NF (e.g. AMF) to indicate the activation of the Early Admission Control (EAC) mode for a certain network slice which is subject to NSAC when the number of the UEs registered with the network slice is above certain operator defined threshold (e.g. a percentage of the maximum number of UEs allowed to register with the network slice) and the deactivation of the EAC mode when the number of the UEs registered with the network slice is below certain operator defined threshold which may be same or different from the activation threshold. Inputs, Required: S-NSSAI(s), EAC flag(s). The S-NSSAI input parameter is the network slice for which the NSACF activates or deactivates the EAC mode. The EAC flag input parameter indicates whether the Slice EAC mode is activated or deactivated. Inputs, Optional: None. Output, Required: None. Output, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.21.2.3 |
3,829 | 8.3.7.2 5GSM capability | This IE is included in the message: 1) for a PDN connection established when in S1 mode, after an inter-system change from S1 mode to N1 mode, if the UE is a UE operating in single-registration mode in a network supporting N26 interface, the UE has not previously successfully performed the UE-requested PDU session modification to provide this capability, and: a) if the PDU session is of "IPv4", "IPv6", "IPv4v6" or "Ethernet" PDU session type, and the UE supports reflective QoS; or b) if the PDU session is of "IPv6" or "IPv4v6" PDU session type, and the UE supports multi-homed IPv6 PDU session; or 2) if the UE needs to revoke the previously indicated support of reflective QoS. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 8.3.7.2 |
3,830 | 5.28.1 5GS bridge management for TSN | 5GS acts as a Layer 2 Ethernet Bridge. When integrated with IEEE TSN network, 5GS functions acts as one or more TSN Bridges of the TSN network. The 5GS Bridge is composed of the ports on a single UPF (i.e. PSA) side, the user plane tunnel between the UE and UPF, and the ports on the DS-TT side. For each 5GS Bridge of a TSN network, the port on NW-TT support the connectivity to the TSN network, the ports on DS-TT side are associated to the PDU Session providing connectivity to the TSN network. The granularity of the 5GS TSN bridge is per UPF for each network instance or DNN/S-NSSAI. The bridge ID of the 5GS TSN bridge is bound to the UPF ID of the UPF as identified in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The TSN AF stores the binding relationship between a port on UE/DS-TT side and a PDU Session during reporting of 5GS TSN bridge information. The TSN AF also stores the information about ports on the UPF/NW-TT side. The UPF/NW-TT forwards traffic to the appropriate egress port based on the traffic forwarding information. From the TSN AF point of view, a 5GS TSN bridge has a single NW-TT entity within UPF and the NW-TT may have multiple ports that are used for traffic forwarding. NOTE 1: How to realize single NW-TT entity within UPF is up to implementation. NOTE 2: Ethernet PDU Session type in this release of the specification may be subject to the constraint that it supports a single N6 interface in a UPF associated with the N6 Network Instance. There is only one PDU Session per DS-TT port for a given UPF. All PDU Sessions which connect to the same TSN network via a specific UPF are grouped into a single 5GS bridge. The capabilities of each port on UE/DS-TT side and UPF/NW-TT side are integrated as part of the configuration of the 5GS Bridge and are notified to TSN AF and delivered to CNC for TSN bridge registration and modification. NOTE 3: It is assumed that all PDU Sessions which connect to the same TSN network via a specific UPF are handled by the same TSN AF. Figure 5.28.1-1: Per UPF based 5GS bridge NOTE 4: If a UE establishes multiple PDU Sessions terminating in different UPFs, then the UE is represented by multiple 5GS TSN bridges. In order to support IEEE 802.1Q features related to TSN, including TSN scheduled traffic (clause 8.6.8.4 in IEEE Std 802.1Q [98]) over 5GS Bridge, the 5GS supports the following functions: - Configure the bridge information in 5GS. - Report the bridge information of 5GS Bridge to TSN network after PDU Session establishment. - Receiving the configuration from TSN network as defined in clause 5.28.2. - Map the configuration information obtained from TSN network into 5GS QoS information (e.g. 5QI, TSC Assistance Information) of a QoS Flow in corresponding PDU Session for efficient time-aware scheduling, as defined at clause 5.28.2. The bridge information of 5GS Bridge is used by the TSN network to make appropriate management configuration for the 5GS Bridge. The bridge information of 5GS Bridge includes at least the following: - Information for 5GS Bridge: - Bridge ID Bridge ID is to distinguish between bridge instances within 5GS. The Bridge ID can be derived from the unique bridge MAC address as described in IEEE Std 802.1Q [98], or set by implementation specific means ensuring that unique values are used within 5GS; - Number of Ports; - list of port numbers. - Capabilities of 5GS Bridge as defined in IEEE Std 802.1Q [98]: - 5GS Bridge delay per port pair per traffic class, including 5GS Bridge delay (dependent and independent of frame size, and their maximum and minimum values: independentDelayMax, independentDelayMin, dependentDelayMax, dependentDelayMin), ingress port number, egress port number and traffic class. - Propagation delay per port (txPropagationDelay), including transmission propagation delay, egress port number. - VLAN Configuration Information. NOTE 5: This Release of the specification does not support the modification of VLAN Configuration Information at the TSN AF. - Topology of 5GS Bridge as defined in IEEE Std 802.1AB [97]: - LLDP Configuration Information. - Chassis ID subtype and Chassis ID of the 5GS Bridge. - LLDP Discovery Information for each discovered neighbor of each NW-TT port and DS-TT port. - Traffic classes and their priorities per port as defined in IEEE Std 802.1Q [98]. - Stream Parameters as defined in clause 12.31.1 in IEEE Std 802.1Q [98], in order to support PSFP: - MaxStreamFilterInstances: The maximum number of Stream Filter instances supported by the bridge; - MaxStreamGateInstances: The maximum number of Stream Gate instances supported by the bridge; - MaxFlowMeterInstances: The maximum number of Flow Meter instances supported by the bridge (optional); - SupportedListMax: The maximum value supported by the bridge of the AdminControlListLength and OperControlListLength parameters. The following parameters: independentDelayMax and independentDelayMin, how to calculate them is left to implementation and not defined in this specification. DS-TT and NW-TT report txPropagationDelay to the TSN AF relative to the time base of the TSN GM clock (identified by the TSN time domain number received in PMIC). If the TSN AF has subscribed for notifications on txPropagationDelay and if the difference to the previously reported txPropagationDelay is larger than the txPropagationDelayDeltaThreshold received in PMIC, the corresponding DS-TT or NW-TT informs the TSN AF about the updated txPropagationDelay using PMIC signalling. NOTE 6: Configuration of TSN time domain number and txPropagationDelayDeltaThreshold via PMIC is optional for NW-TT. NW-TT can instead be pre-configured with the threshold and the single time domain that is used by the CNC for bridge configuration and reporting. Bridge ID of the 5GS Bridge, port number(s) of the Ethernet port(s) in NW-TT could be preconfigured on the UPF. The UPF is selected for a PDU Session serving TSC as described in clause 6.3.3.3. This release of the specification requires that each DS-TT port is assigned with a globally unique MAC address. NOTE 7: The MAC address of the DS-TT port must not be used in user data traffic; it is used for identification of the PDU Session and the associated bridge port within the 3GPP system. When there are multiple network instances within a UPF, each network instance is considered logically separate. The network instance for the N6 interface (clause 5.6.12) may be indicated by the SMF to the UPF for a given PDU Session during PDU Session establishment. UPF allocates resources based on the Network Instance and S-NSSAI and it is supported according to TS 29.244[ Interface between the Control Plane and the User Plane nodes ] [65]. DNN/S-NSSAI may be indicated by the SMF together with the network instance to the UPF for a given PDU Session during PDU Session establishment procedure. The TSN AF is responsible to receive the bridge information of 5GS Bridge from 5GS, as well as register or update this information to the CNC. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.28.1 |
3,831 | 5.21.4 Network Function/NF Service Context Transfer 5.21.4.1 General | Network Function/NF Service Context Transfer Procedures allow transfer of Service Context of a NF/NF Service from a Source NF/NF Service Instance to the Target NF/NF Service Instance e.g. before the Source NF/NF Service can gracefully close its NF/NF Service. Service Context Transfer procedures are supported as specified in clause 4.26 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. Source NF / OA&M system determines when Source NF needs to transfer UE contexts to an NF in another NF set. Source NF should initiate this only for UE(s) that are not active in order to limit and avoid impacting services offered to corresponding UE(s). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.21.4 |
3,832 | 4.22.5 Reporting of Access Availability | After the MA PDU session is established, if Reporting of Access Availability is required by network, the UE performs detection of the unavailability and availability of an access as described in clause 5.32.5.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. To report the availability/unavailability of the access, the UE sends the PMF-Access Report to the UPF via the user plane of any available access of the MA PDU session. The UPF shall use this report to decide which access can be used to deliver the downlink packets. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.22.5 |
3,833 | 5.14.1.4 Buffer Status Reporting | The sidelink Buffer Status reporting procedure is used to provide the serving eNB with information about the amount of sidelink data available for transmission in the SL buffers associated with the MAC entity. RRC controls BSR reporting for the sidelink by configuring the two timers periodic-BSR-TimerSL and retx-BSR-TimerSL. Each sidelink logical channel belongs to a ProSe Destination. Each sidelink logical channel is allocated to an LCG depending on the priority and optionally the PPPR of the sidelink logical channel, and the mapping between LCG ID and priority and optionally the mapping between LCG ID and PPPR which are provided by upper layers in logicalChGroupInfoList, as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]. LCG is defined per ProSe Destination. A sidelink Buffer Status Report (BSR) shall be triggered if any of the following events occur: - if the MAC entity has a configured SL-RNTI or a configured SL-V-RNTI: - SL data, for a sidelink logical channel of a ProSe Destination, 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] respectively) and either the data belongs to a sidelink logical channel with higher priority than the priorities of the sidelink logical channels which belong to any LCG belonging to the same ProSe Destination and for which data is already available for transmission, or there is currently no data available for transmission for any of the sidelink logical channels belonging to the same ProSe Destination, in which case the Sidelink BSR is referred below to as "Regular Sidelink BSR"; - UL resources are allocated and number of padding bits remaining after a Padding BSR has been triggered is equal to or larger than the size of the Sidelink BSR MAC control element containing the buffer status for at least one LCG of a ProSe Destination plus its subheader, in which case the Sidelink BSR is referred below to as "Padding Sidelink BSR"; - retx-BSR-TimerSL expires and the MAC entity has data available for transmission for any of the sidelink logical channels, in which case the Sidelink BSR is referred below to as "Regular Sidelink BSR"; - periodic-BSR-TimerSL expires, in which case the Sidelink BSR is referred below to as "Periodic Sidelink BSR"; - else: - An SL-RNTI or an SL-V-RNTI is configured by upper layers and SL data is 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] respectively), in which case the Sidelink BSR is referred below to as "Regular Sidelink BSR". For Regular and Periodic Sidelink BSR: - if the number of bits in the UL grant is equal to or larger than the size of a Sidelink BSR containing buffer status for all LCGs having data available for transmission plus its subheader: - report Sidelink BSR containing buffer status for all LCGs having data available for transmission; - else report Truncated Sidelink BSR containing buffer status for as many LCGs having data available for transmission as possible, taking the number of bits in the UL grant into consideration. For Padding Sidelink BSR: - if the number of padding bits remaining after a Padding BSR has been triggered is equal to or larger than the size of a Sidelink BSR containing buffer status for all LCGs having data available for transmission plus its subheader: - report Sidelink BSR containing buffer status for all LCGs having data available for transmission; - else report Truncated Sidelink BSR containing buffer status for as many LCGs having data available for transmission as possible, taking the number of bits in the UL grant into consideration. If the Buffer Status reporting procedure determines that at least one Sidelink BSR has been triggered and not cancelled: - if the MAC entity has UL resources allocated for new transmission for this TTI and the allocated UL resources can accommodate a Sidelink BSR MAC control element plus its subheader as a result of logical channel prioritization: - instruct the Multiplexing and Assembly procedure to generate the Sidelink BSR MAC control element(s); - start or restart periodic-BSR-TimerSL except when all the generated Sidelink BSRs are Truncated Sidelink BSRs; - start or restart retx-BSR-TimerSL; - else if a Regular Sidelink BSR has been triggered: - if an uplink grant is not configured: - a Scheduling Request shall be triggered. A MAC PDU shall contain at most one Sidelink BSR MAC control element, even when multiple events trigger a Sidelink BSR by the time a Sidelink BSR can be transmitted in which case the Regular Sidelink BSR and the Periodic Sidelink BSR shall have precedence over the padding Sidelink BSR. The MAC entity shall restart retx-BSR-TimerSL upon reception of an SL grant. All triggered regular Sidelink BSRs shall be cancelled in case the remaining configured SL grant(s) valid for this SC Period can accommodate all pending data available for transmission in sidelink communication or in case the remaining configured SL grant(s) valid can accommodate all pending data available for transmission in V2X sidelink communication. All triggered Sidelink BSRs shall be cancelled in case the MAC entity has no data available for transmission for any of the sidelink logical channels. All triggered Sidelink BSRs shall be cancelled when a Sidelink BSR (except for Truncated Sidelink BSR) is included in a MAC PDU for transmission. All triggered Sidelink BSRs shall be cancelled, and retx-BSR-TimerSL and periodic-BSR-TimerSL shall be stopped, when upper layers configure autonomous resource selection. The MAC entity shall transmit at most one Regular/Periodic Sidelink BSR in a TTI. If the MAC entity is requested to transmit multiple MAC PDUs in a TTI, it may include a padding Sidelink BSR in any of the MAC PDUs which do not contain a Regular/Periodic Sidelink BSR. All Sidelink 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 Sidelink BSRs reporting buffer status for this LCG. NOTE: A Padding Sidelink BSR is not allowed to cancel a triggered Regular/Periodic Sidelink BSR. A Padding Sidelink BSR is triggered for a specific MAC PDU only and the trigger is cancelled when this MAC PDU has been built. | 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.4 |
3,834 | 5.5.1.2 Alternate party charging for IMS | This applies to the alternate charged party in charged party principles defined in TS 22.115[ Service aspects; Charging and billing ] [101]. In IMS offline and online charging as an alternative it is possible that neither calling nor called party can be charged for the IMS session. The alternate charged party need not be registered at the time that the charges are made. It is required however, that the alternate charged party be a verifiable charged party. Selection and verification is done through internal actions in the SIP-AS. The Subscription Identification contains the identity of alternate charged party. The IMS session is then processed in the normal manner. NOTE: The method for verifying the alternate charged party is not covered in the present document. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 5.5.1.2 |
3,835 | 5.3.2.1 E-UTRAN Initial Attach | A UE/user needs to register with the network to receive services that require registration. This registration is described as Network Attachment. The always-on connectivity for UE/users of the EPS may be enabled by establishing a default EPS bearer during Network Attachment. The PCC rules applied to the default EPS bearer may be predefined in the PDN GW and activated in the attachment by the PDN GW itself. The Attach procedure may trigger one or multiple Dedicated Bearer Establishment procedures to establish dedicated EPS bearer(s) for that UE. During the attach procedure, the UE may request for an IP address allocation. Terminals utilising only IETF based mechanisms for IP address allocation are also supported. During the Initial Attach procedure the Mobile Equipment Identity is obtained from the UE. The MME operator may check the ME Identity with an EIR. The MME passes the ME Identity (IMEISV) to the HSS and to the PDN GW. During the Initial Attach procedure, if the MME supports SRVCC and if any of the conditions described in step 8 in Figure 5.3.2.1-1 are satisfied, the MME informs the HSS with the UE SRVCC capability e.g. for further IMS registration. The E-UTRAN Initial Attach procedure is used for Emergency Attach by UEs that need to perform emergency services but cannot gain normal services from the network. These UEs are in limited service state as defined in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [10]. Also UEs that had attached for normal services and do not have emergency bearers established and are camped on a cell in limited service state (e.g. restricted Tracking Area or not allowed CSG) shall initiate the Attach procedures indicating that the attach is to receive emergency services. UEs that camp normally on a cell, i.e. UEs that are not in limited service state, should initiate normal initial attach when not already attached and shall initiate the UE Requested PDN Connectivity procedure to receive emergency EPS bearer services. The E-UTRAN Initial Attach procedure is used for RLOS Attach by UEs in limited service state as defined in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [10], as well as UEs attached for normal services but moved to a cell in limited service state (e.g. restricted Tracking Area or not allowed CSG). NOTE 1: A UE that is emergency or RLOS attached performs initial attach procedure before being able to obtain normal services. In order to limit load on the network, only when performing an E-UTRAN Attach with a new PLMN (i.e. not the registered PLMN or an equivalent PLMN of the registered PLMN), a UE configured to perform Attach with IMSI at PLMN change (see TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [69]) shall identify itself by its IMSI instead of any stored temporary identifier. This procedure is also used to establish the first PDN connection over E-UTRAN when the UE already has active PDN connections over a non-3GPP access network and wants to establish simultaneous PDN connections to different APNs over multiple accesses. During the Attach procedure, a Multi-USIM UE may indicate to the MME a Requested IMSI Offset, as described in clause 4.3.33, with the aim of modifying the timing of the Paging Occasions to avoid paging collisions. NOTE 2: As an exception, during the Attach procedure a Multi-USIM UE implementation can decide to indicate to the MME a Requested IMSI Offset even if it does not know whether the MME supports it. Figure 5.3.2.1-1: Attach procedure NOTE 3: For a PMIP-based S5/S8, procedure steps (A), (B), and (C) are defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. Steps 7, 10, 13, 14, 15 and 23a/b concern GTP based S5/S8. NOTE 4: The Serving GWs and PDN GWs involved in steps 7 and/or 10 may be different to those in steps 13-15. NOTE 5: The steps in (D) are executed only upon handover from non-3GPP access or if Presence Reporting Area Information is received from the MME. NOTE 6: More detail on procedure steps (E) is defined in the procedure steps (B) in clause 5.3.8.3. NOTE 7: More detail on procedure steps (F) is defined in the procedure steps (B) in clause 5.3.8.4. 1. A UE, camping on an E-UTRAN cell reads the related System Information Broadcast. An E-UTRAN cell for a PLMN that supports CIoT enhancements shall broadcast: For the NB-IoT case: - Whether it can connect to an MME which supports EPS Attach without PDN Connectivity. For the WB-E-UTRAN case: - Whether it supports Control Plane CIoT EPS Optimisation and it can connect to an MME which supports Control Plane CIoT EPS Optimisation. - Whether it supports User Plane CIoT EPS Optimisation and it can connect to an MME which supports User Plane CIoT EPS Optimisation. - Whether it can connect to an MME which supports EPS Attach without PDN Connectivity. If the PLMN does not advertise support of EPS attach without PDN connectivity and the UE can only attach without PDN connectivity, then the UE shall not attach to the PLMN in this cell and shall proceed as specified in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [10]. In the case of WB-E-UTRAN, if the PLMN does not support Control Plane CIoT EPS Optimisation, and the UE only supports Control Plane CIoT EPS Optimisation and cannot otherwise attach, then the UE shall not proceed with the Attach to the PLMN in this cell and shall proceed as specified in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [10]. An E-UTRAN cell for a PLMN that supports Restricted Local Operator Service shall broadcast: - Whether it supports Restricted Local Operator Service. If the PLMN does not advertise support for Restricted Local Operator Services, the UE shall not proceed with the Attach with indication that the attach is to receive Restricted Local Operator Services to the PLMN in this cell. If a Service Gap timer is running in the UE (see clause 4.3.17.9) and the Attach Type is not Emergency Attach and it is not an Attach without PDN connectivity, then the UE shall not send Attach Requests to this PLMN or any other PLMN as long as the timer is running. If the UE can proceed to attach, it initiates the Attach procedure by the transmission, to the eNodeB, of an Attach Request (IMSI or old GUTI, Old GUTI type, last visited TAI (if available), UE Core Network Capability, UE Specific DRX parameters, extended idle mode DRX parameters, UE paging probability information, Attach Type, ESM message container (Request Type, PDN Type, Protocol Configuration Options, Ciphered Options Transfer Flag, Header Compression Configuration), KSIASME, NAS sequence number, NAS-MAC, additional GUTI, P-TMSI signature, Voice domain preference and UE's usage setting, Preferred Network behaviour, MS Network Capability, Support for restriction of use of Enhanced Coverage, UE has UE Radio Capability ID assigned for the selected PLMN, Requested IMSI Offset) message together with RRC parameters indicating the Selected Network and the old GUMMEI. In the RRC connection establishment signalling associated with the Attach Request, the UE indicates its support of the CIoT EPS Optimisations, relevant for MME selection. The UE shall also include an IAB-Indication in the RRC connection establishment signalling, if the UE is an IAB-node, as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37]. If the UE identifies itself with the old GUTI, the UE shall set the Old GUTI Type to indicate whether the Old GUTI is a native GUTI or is mapped from a P-TMSI and RAI. The old GUTI may be derived from a P-TMSI and RAI. IMSI shall be included if the UE does not have a valid GUTI or a valid P-TMSI available, or if the UE is configured to perform Attach with IMSI at PLMN change and is accessing a new PLMN. The UE stores the TIN in detached state. If the UE's TIN indicates "GUTI" or "RAT-related TMSI" and the UE holds a valid GUTI then the old GUTI indicates this valid GUTI. If the UE's TIN indicates "P-TMSI" and the UE holds a valid P-TMSI and related RAI then these two elements are indicated as the old GUTI. Mapping a P-TMSI and RAI to a GUTI is specified in TS 23.003[ Numbering, addressing and identification ] [9]. If the UE holds a valid GUTI and the old GUTI indicates a GUTI mapped from a P-TMSI and RAI, then the UE indicates the GUTI as additional GUTI. If the old GUTI indicates a GUTI mapped from a P-TMSI and RAI and the UE has a valid P-TMSI signature associated to it, the P-TMSI signature shall be included. The UE sets the voice domain preference and UE's usage setting according to its configuration, as described in clause 4.3.5.9. Alternatively, when a UE only supports E-UTRAN, if the UE has a GUTI available and the UE is accessing the same PLMN (or ePLMN), then it identifies itself with the old GUTI and sets the Old GUTI Type to 'native', otherwise the UE configuration determines whether the UE identifies itself with its IMSI or the Old GUTI. The UE includes the extended idle mode DRX parameters information element if the UE needs to enable extended idle mode DRX. The UE may include UE paging probability information if it supports the assignment of WUS Assistance Information from the MME to assist the eNodeB's Wake-Up Signal (WUS) group decision (see TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]). If available, the last visited TAI shall be included in order to help the MME produce a good list of TAIs for any subsequent Attach Accept message. Selected Network indicates the PLMN that is selected for network sharing purposes. The RRC parameter "old GUMMEI" takes its value from the "old GUTI" contained in the Attach Request. UE Network Capability is described in UE capabilities, see clause 5.11. If the UE has valid security parameters, the Attach Request message shall be integrity protected by the NAS-MAC in order to allow validation of the UE by the MME. KSIASME, NAS sequence number and NAS-MAC are included if the UE has valid EPS security parameters. NAS sequence number indicates the sequential number of the NAS message. If the UE does not have a valid EPS security association, then the Attach Request message is not integrity protected. In this case the security association is established in step 5a. The UE network capabilities indicate also the supported NAS and AS security algorithms. PDN type indicates the requested IP version (IPv4, IPv4/IPv6, IPv6). For a UE that support CIoT EPS Optimisations, the PDN type may also be "Non-IP". PDN type may also indicate Ethernet. Protocol Configuration Options (PCO) are used to transfer parameters between the UE and the PDN GW, and sent transparently through the MME and the Serving GW. The Protocol Configuration Options may include the Address Allocation Preference indicating that the UE prefers to obtain an IPv4 address only after the default bearer activation by means of DHCPv4. If the UE intends to send PCO which require ciphering (e.g., PAP/CHAP usernames and passwords) or send an APN, or both, the UE shall set the Ciphered Options Transfer Flag and send PCO or APN or both only after authentication and NAS security setup have been completed (see below). NOTE 8: External network operators wanting to use PAP for authentication are warned that PAP is an obsolete protocol from a security point of view. CHAP provides stronger security than PAP. If the UE supports 3GPP PS Data Off, it shall include in the PCO the 3GPP PS Data Off UE Status, which indicates whether the user has activated or deactivated 3GPP PS Data Off. If the UE has UTRAN or GERAN capabilities, it shall send the NRSU in the PCO to indicate the support of the network requested bearer control in UTRAN/GERAN. The UE sends the ETFTU in the PCO to indicate the support of the extended TFT filter format. Request Type is included in the ESM message container and indicates "Handover" when the UE has already an activated PDN GW/HA due to mobility with non-3GPP accesses. If a UE indicates support of CIoT EPS Optimisations in the RRC message, it may omit the ESM message container. If the ESM message container is omitted the MME shall not establish a PDN connection as part of the Attach procedure. In this case steps 6, 12 to 16 and 23 to 26 are not executed. In addition, for the case of UEs attaching with Control Plane CIoT EPS Optimisation with no user plane establishment, steps 17 to 22 are replaced by S1 AP NAS Transport and RRC Direct Transfer messages that just transport the NAS Attach Accept and NAS Attach Complete messages. Attach Type indicates whether it is an EPS attach or a combined EPS/IMSI attach or an Emergency Attach or an RLOS Attach. Emergency Attach and RLOS Attach shall not be indicated when the UE is using NB-IoT. When using CIoT EPS Optimisations, the UE may indicate EPS attach and request SMS by setting the "SMS transfer without Combined Attach" flag in the Preferred Network Behaviour IE. If a UE includes a Preferred Network Behaviour, this defines the Network Behaviour the UE is expecting to be available in the network as defined in clause 4.3.5.10. If a UE indicated Control Plane CIoT EPS Optimisation supported in Preferred Network Behaviour, and the UE included the ESM message container, and the PDN type was IPv4 or IPv6 or IPv4v6, and the UE supports header compression, it shall include the Header Compression Configuration. The Header Compression Configuration includes the information necessary for the ROHC channel setup. Optionally, the Header Compression Configuration may include additional header compression context setup parameters if the UE already has the application traffic information, e.g. the target server IP address. For an Emergency Attach the UE shall set both the Attach Type and the Request Type to "Emergency" and the IMSI shall be included if the UE does not have a valid GUTI or a valid P-TMSI available. The IMEI shall be included when the UE has no IMSI, no valid GUTI and no valid P-TMSI. For RLOS attach, the UE shall set the Attach Type to "RLOS" and the Request Type to "RLOS", the IMSI shall be included if available and if the UE does not have a valid GUTI or a valid P-TMSI available. The IMEI shall be included when the UE has no IMSI, no valid GUTI and no valid P-TMSI. If the UE supports RACS as defined in clause 5.11.3a, and if the UE is provisioned with a UE Radio Capability ID for use in the selected PLMN (i.e.PLMN-assigned for the specific PLMN or UE manufacturer-assigned), the UE includes a flag that indicates it has an assigned UE Radio Capability ID for use in the selected PLMN but the actual UE Radio Capability ID is provided to MME after security context is established in step 5a (see below). If a Multi-USIM UE needs to modify the Paging Occasions in order to avoid paging collisions, it sends a Requested IMSI Offset to the MME, in order to signal an alternative IMSI as described in clause 4.3.33. 2. The eNodeB derives the MME address from the RRC parameters carrying the old GUMMEI, the indicated Selected Network and the RAT (NB-IoT or WB-E-UTRAN). If that MME is not associated with the eNodeB or the old GUMMEI is not available, the eNodeB selects an MME as described in clause 4.3.8.3 on "MME selection function". The eNodeB forwards the Attach Request message in a S1-MME control message (Initial UE message) together with the Selected Network, CSG access mode, CSG ID, L-GW address, TAI+ECGI of the cell from where it received the message to the new MME. CSG ID is provided if the UE attaches via a CSG cell or hybrid cell. CSG access mode is provided if the UE attaches via a hybrid cell. If the CSG access mode is not provided but the CSG ID is provided, the MME shall consider the cell as a CSG cell. If the eNodeB has a collocated L-GW, it includes the L-GW address in the Initial UE message to the MME. If the IAB-Indication is received from the UE in step 1, the eNodeB selects an MME that supports IAB operation and includes the IAB-Indication in the Initial UE message to the MME. If the MME is not configured to support Emergency Attach the MME shall reject any Attach Request that indicates Attach Type "Emergency". If the MME is not configured to support RLOS Attach, the MME shall reject any Attach Request that indicates Attach Type "RLOS". If the UE has included the Preferred Network Behaviour, and what the UE indicated it supports in Preferred Network Behaviour is incompatible with the network support e.g. the UE indicated support only for Control Plane CIoT EPS Optimisation and the MME only supports User Plane CIoT EPS Optimisation, the MME shall reject the Attach Request with an appropriate cause value (e.g. one that avoids retries on this PLMN). To assist Location Services, the eNodeB indicates the UE's Coverage Level to the MME. If the UE supports MT-EDT as indicated in the UE Network Capability, the MME shall consider this parameter to provide the MT-EDT indication towards Serving GW during PDN Connection establishment or mobility procedures, and handle the data size information that the MME may receive during Downlink Data Notification procedures as defined in clause 5.3.4B.6, and clause 5.3.5B. In the case of satellite access for Cellular IoT, the MME may verify the UE location and determine whether the PLMN is allowed to operate at the UE location, as described in clause 4.13.4. If the UE receives an Attach Reject message with cause value indicating that the selected PLMN is not allowed to operate at the present UE location, the UE shall attempt to select a PLMN as specified in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [10]. 3. If the UE identifies itself with GUTI and the MME has changed since detach, the new MME determines the type of the old node, i.e. MME or SGSN, as specified in clause 4.3.19, uses the GUTI received from the UE to derive the old MME/SGSN address, and sends an Identification Request (old GUTI, complete Attach Request message) to the old MME/SGSN to request the IMSI. If the request is sent to an old MME, the old MME first verifies the Attach Request message by NAS MAC and then responds with Identification Response (IMSI, MM Context). If the request is sent to an old SGSN, the old SGSN first verifies the Attach Request message by the P-TMSI signature and then responds with Identification Response (MM Context). If the UE is not known in the old MME/SGSN or if the integrity check or P-TMSI signature check for the Attach Request message fails, the old MME/SGSN responds with an appropriate error cause. The MM context contains security related information as well as other parameters (including IMSI) as described in clause 5.7.2 (Information Storage for MME). The additional GUTI in the Attach Request message allows the new MME to find any already existing UE context stored in the new MME when the old GUTI indicates a GUTI mapped from a P-TMSI and RAI. For an Emergency Attach or a RLOS Attach, if the UE identifies itself with a temporary identity that is not known to the MME the MME immediately requests the IMSI from the UE. If the UE identifies itself with IMEI, the IMSI request shall be skipped. During inter PLMN mobility, the new MME shall delete the UE Radio Capability ID received from the old MME, unless the operator policy indicates that all UE Radio Capability IDs used in the old PLMN are also valid in the new PLMN. NOTE 9: A SGSN always responds with the UMTS security parameters and the MME may store it for later use. 4. If the UE is unknown in both the old MME/SGSN and new MME, the new MME sends an Identity Request to the UE to request the IMSI. The UE responds with Identity Response (IMSI). 5a If no UE context for the UE exists anywhere in the network, if the Attach Request (sent in step 1) was not integrity protected, or if the check of the integrity failed, then authentication and NAS security setup to activate integrity protection and NAS ciphering are mandatory. Otherwise it is optional. If NAS security algorithm is to be changed, the NAS security setup is performed in this step. The authentication and NAS security setup functions are defined in clause 5.3.10 on "Security Function". If the UE supports RACS as indicated in the UE Network Capability, and if the UE indicated that it has UE Radio Capability ID assigned for use in the selected PLMN in step 1, then authentication and NAS security setup to activate integrity protection and NAS ciphering are mandatory and the MME shall request the UE to provide the UE Radio Capability ID in Security Mode Command and the UE shall include the UE Radio Capability ID in Security Mode Command Accept for the supported UE radio capabilities. If the MME is configured to support Emergency Attach for unauthenticated IMSIs and the UE indicated Attach Type "Emergency" the MME skips the authentication and security setup or the MME accepts that the authentication may fail and continues the attach procedure. If the MME is configured to support RLOS Attach and the UE indicated Attach Type "RLOS", based on local regulation and operator policy, the MME may skip the authentication and security setup, or the MME may perform authentication if security information is available or obtainable from HSS and continues the attach procedure regardless of the authentication result. After step 5a, all NAS messages shall be protected by the NAS security functions (integrity and ciphering) indicated by the MME unless the UE is emergency or RLOS attached and not successfully authenticated. 5b. The ME Identity (IMEISV) shall be retrieved from the UE. The ME identity shall be transferred encrypted unless the UE performs Emergency Attach or RLOS Attach and cannot be authenticated. For an Emergency Attach or RLOS Attach, the UE may have included the IMEI in the Emergency Attach or RLOS Attach. If so, the ME Identity retrieval is skipped. In order to minimise signalling delays, the retrieval of the ME Identity may be combined with NAS security setup in step 5a. The MME may send the ME Identity Check Request (ME Identity, IMSI) to the EIR. The EIR shall respond with ME Identity Check Ack (Result). Dependent upon the Result, the MME decides whether to continue with this Attach procedure or to reject the UE. For an Emergency Attach or RLOS Attach, the IMEI check to the EIR may be performed. If the IMEI is blocked, operator policies determine whether the Emergency Attach or RLOS Attach procedure continues or is stopped. If the UE supports RACS, as indicated in the UE Core Network Capability IE, the MME shall use the IMEI of the UE to obtain the IMEI/TAC for the purpose of RACS operation. 6. If the UE has set the Ciphered Options Transfer Flag in the Attach Request message, the Ciphered Options i.e. PCO or APN or both, shall now be retrieved from the UE. In order to handle situations where the UE may have subscriptions to multiple PDNs, if the Protocol Configuration Options contains user credentials (e.g. user name/password within PAP or CHAP parameters) then the UE should also send the APN to the MME. 7. If there are active bearer contexts in the new MME for this particular UE (i.e. the UE re-attaches to the same MME without having properly detached before), the new MME deletes these bearer contexts by sending Delete Session Request (LBI) messages to the GWs involved. The GWs acknowledge with Delete Session Response (Cause) message. If a PCRF is deployed, the PDN GW employs an IP-CAN Session Termination procedure to indicate that resources have been released. 8. If the MME has changed since the last detach, or if there is no valid subscription context for the UE in the MME, or if the UE provides an IMSI or the UE provides an old GUTI which doesn't refer to a valid context in the MME, or for some network sharing scenario (e.g. GWCN) if the PLMN-ID of the TAI supplied by the eNodeB is different from that of the GUTI in the UE's context, the MME sends an Update Location Request (MME Identity, IMSI, ME Identity (IMEISV), MME Capabilities, ULR-Flags, Homogeneous Support of IMS Voice over PS Sessions, UE SRVCC capability, equivalent PLMN list) message to the HSS. The MME capabilities indicate the MME's support for regional access restrictions functionality. ULR-Flags indicates "Initial-Attach-Indicator" as this is an Attach procedure. The inclusion of the equivalent PLMN list indicates that the MME supports the inter-PLMN handover to a CSG cell in an equivalent PLMN using the subscription information of the target PLMN. The "Homogenous Support of IMS Voice over PS Sessions" indication (see clause 4.3.5.8A) shall not be included unless the MME has completed its evaluation of the support of "IMS Voice over PS Session" as specified in clause 4.3.5.8. NOTE 10: At this step, the MME may not have all the information needed to determine the setting of the IMS Voice over PS Session Supported indication for this UE (see clause 4.3.5.8). Hence the MME can send the "Homogenous Support of IMS Voice over PS Sessions" later on in this procedure. If the UE performs Initial or Handover Attach in a VPLMN supporting Autonomous CSG Roaming and the HPLMN has enabled Autonomous CSG Roaming in the VPLMN (via Service Level Agreement) and the MME needs to retrieve the CSG subscription information of the UE from the CSS, the MME initiates the Update CSG Location Procedure with CSS as described in clause 5.3.12. If the MME determines that only the UE SRVCC capability has changed, the MME sends a Notify Request to the HSS to inform about the changed UE SRVCC capability. If there is a valid subscription context for the UE in the MME with a Service Gap timer running and the Attach Type is not Emergency Attach and it is not an Attach without PDN connectivity, the MME rejects the Attach Request from the UE with an appropriate cause value. In addition, MME may also provide a UE with a Mobility Management Back-off Timer set to the remaining value of the Service Gap timer. For an Emergency Attach in which the UE was not successfully authenticated, the MME shall not send an Update Location Request to the HSS. For an RLOS Attach the MME shall not send an Update Location Request to the HSS. 9. The HSS sends Cancel Location (IMSI, Cancellation Type) to the old MME. The old MME acknowledges with Cancel Location Ack (IMSI) and removes the MM and bearer contexts. If the ULR-Flags indicates "Initial-Attach-Indicator" and the HSS has the SGSN registration, then the HSS sends Cancel Location (IMSI, Cancellation Type) to the old SGSN. The Cancellation Type indicates the old MME/SGSN to release the old Serving GW resource. 10. If there are active bearer contexts in the old MME/SGSN for this particular UE, the old MME/SGSN deletes these bearer contexts by sending Delete Session Request (LBI) messages to the GWs involved. The GWs return Delete Session Response (Cause) message to the old MME/SGSN. If a PCRF is deployed, the PDN GW employs an IP-CAN Session Termination procedure as defined in TS 23.203[ Policy and charging control architecture ] [6] to indicate that resources have been released. 11. The HSS acknowledges the Update Location message by sending an Update Location Ack (IMSI, Subscription data) message to the new MME. The Subscription Data contain one or more PDN subscription contexts. Each PDN subscription context contains an 'EPS subscribed QoS profile' and the subscribed APN-AMBR (see clause 4.7.3) and the WLAN offloadability indication (see clause 4.3.23). The new MME validates the UE's presence in the (new) TA. If due to regional subscription restrictions or access restrictions (e.g. CSG restrictions) the UE is not allowed to attach in the TA or due to subscription checking fails for other reasons, the new MME rejects the Attach Request with an appropriate cause. If all checks are successful then the new MME constructs a context for the UE. If the APN provided by the UE is not allowed by subscription, based on operator policy, the MME may reject the Attach Request from the UE with an appropriate cause, or accept the Attach Request by replacing the UE requested APN with a network supported APN. The MME uses that network supported APN for the remainder of this procedure, except that the MME provides to the UE the same APN that the UE requested. If the Update Location is rejected by the HSS, the new MME rejects the Attach Request from the UE with an appropriate cause. The Subscription Data may contain CSG subscription information for the registered PLMN and for the equivalent PLMN list requested by MME in step 8. The Subscription Data may contain the IAB-Operation Allowed indication the IAB operation. The MME shall use the IAB-Opeation Allowed indication to authorize the UE's IAB operation. The subscription data may contain Enhanced Coverage Restricted parameter. If received from the HSS, MME stores this Enhanced Coverage Restricted parameter in the MME MM context. The subscription data may contain Service Gap Time parameter. If received from the HSS, MME stores this Service Gap Time in the MME MM context and passes it to the UE in the Attach Accept message. The subscription data may contain Subscribed Paging Time Window parameter that applies to the UEs on a specific RAT, e.g. NB-IoT. If received from the HSS, MME stores this Subscribed Paging Time Window parameter in the MME MM context. If the UE provided APN is authorized for LIPA according to the user subscription, the MME shall use the CSG Subscription Data to authorize the connection. For an Emergency Attach or RLOS Attach, the MME shall not check for access restrictions, regional restrictions or subscription restrictions (e.g. CSG restrictions). For an Emergency Attach, the MME shall ignore any unsuccessful Update Location Response from HSS and continue with the Attach procedure. 12. If an ESM container was not included in the Attach Request, steps 12, 13,14,15,16 are skipped. If the attach type is not set to "Emergency" or "RLOS", and the ESM container was included in the Attach Request, and the UE has indicated support for Attach without PDN Connectivity, and the network supports Attach without PDN Connectivity, and the PDN Connection Restriction is set in the subscriber data, then the new MME shall not establish PDN connection, and steps 12, 13, 14, 15 and 16 are skipped. For an Emergency Attach the MME applies the parameters from MME Emergency Configuration Data for the emergency bearer establishment performed in this step and any potentially stored IMSI related subscription data are ignored by the MME. For a RLOS Attach, the MME applies the parameters from MME RLOS Configuration Data for the RLOS default bearer establishment performed in this step and any potentially stored IMSI related subscription data are ignored by the MME. If the UE performs Initial or Handover Attach via a CSG cell and there is no subscription for that CSG or the CSG subscription is expired the MME shall reject the Attach Request with an appropriate cause. If the UE has this CSG ID and associated PLMN on its Allowed CSG list the UE shall remove the CSG ID and associated PLMN from the list when receiving this reject cause. If a subscribed PDN address is allocated for the UE for this APN, the PDN subscription context contains the UE's IPv4 address and/or the IPv6 prefix and optionally the PDN GW identity. If the PDN subscription context contains a subscribed IPv4 address and/or IPv6 prefix, the MME indicates it in the PDN address. For Request Type indicating "Initial request", if the UE does not provide an APN, the MME shall use the PDN GW corresponding to the default APN for default bearer activation. If the UE provides an APN, this APN shall be employed for default bearer activation. For Request Type indicating "Handover", if the UE provides an APN, the MME shall use the PDN GW corresponding to the provided APN for default bearer activation, If the UE does not provide an APN, and the subscription context from HSS contains a PDN GW identity corresponding to the default APN, the MME shall use the PDN GW corresponding to the default APN for default bearer activation. The case where the Request Type indicates "Handover" and the UE does not provide an APN, and the subscription context from HSS does not contain a PDN GW identity corresponding to the default APN constitutes an error case. If the Request Type indicates "Initial request" and the selected PDN subscription context contains no PDN GW identity the new MME selects a PDN GW as described in clause 4.3.8.1 on PDN GW selection function (3GPP accesses). If the PDN subscription context contains a dynamically allocated PDN GW identity and the Request Type does not indicate "Handover" the MME may select a new PDN GW as described in clause PDN GW selection function, e.g. to allocate a PDN GW that allows for more efficient routing. For initial and handover Emergency Attach the MME uses the PDN GW Selection function defined in clause 4.3.12.4 to select a PDN GW. For initial RLOS Attach, the MME uses the PDN GW Selection function defined in clause 4.3.12a.4 to select a PDN GW. If the subscription context does not indicate that the APN is for a PDN connection to an SCEF, the new MME selects a Serving GW as described in clause 4.3.8.2 on Serving GW selection function and allocates an EPS Bearer Identity for the Default Bearer associated with the UE. Then it sends a Create Session Request (IMSI, MSISDN, MME TEID for control plane, PDN GW address, PDN Address, APN, RAT type, LTE-M RAT type reporting to PGW flag, Default EPS Bearer QoS, PDN Type, APN-AMBR, EPS Bearer Identity, Protocol Configuration Options, Handover Indication, ME Identity (IMEISV), User Location Information (ECGI and TAI), UE Time Zone, User CSG Information, MS Info Change Reporting support indication, Selection Mode, Charging Characteristics, Trace Reference, Trace Type, Trigger Id, OMC Identity, Maximum APN Restriction, Dual Address Bearer Flag, the Protocol Type over S5/S8, Serving Network, APN Rate Control Status) message to the selected Serving GW. If Control Plane CIoT EPS Optimisation applies, then the MME shall also indicate S11-U tunnelling of NAS user data and send its own S11-U IP address and MME DL TEID for DL data forwarding by the SGW. User CSG Information includes CSG ID, access mode and CSG membership indication. For PDN type "non-IP" when Control Plane CIoT EPS Optimisations are enabled for the UE, if APN subscription data indicate a SCEF connection needs to be used, then the MME allocates an EPS Bearer Identity for the Default Bearer associated with the UE and establishes a connection to the SCEF address indicated in subscription data as per TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74] and the steps 12,13,14,15,16 are not executed. The rest of the interactions with the UE apply as specified below. If the MME determines the PDN connection shall only use the Control Plane CIoT EPS Optimisation, the MME shall include a Control Plane Only PDN Connection Indicator in Create Session Request. If the Request Type indicates "Emergency" or "RLOS", Maximum APN restriction control shall not be performed. For emergency attached or RLOS attached UEs IMSI is included if available and if the IMSI cannot be authenticated then the IMSI shall be marked as unauthenticated. The RAT type is provided in this message for the later PCC decision. The RAT type shall distinguish between NB-IoT, LTE-M and WB-E-UTRA RAT types as specified in clause 4.3.5.3. The subscribed APN-AMBR for the APN is also provided in this message. The MSISDN is included if provided in the subscription data from the HSS. Handover Indication is included if the Request Type indicates handover. Selection Mode indicates whether a subscribed APN was selected, or a non-subscribed APN sent by the UE was selected. Charging Characteristics indicates which kind of charging the bearer context is liable for. The MME may change the requested PDN type according to the subscription data for this APN as described in clause 5.3.1.1. The MME shall set the Dual Address Bearer Flag when the PDN type is set to IPv4v6 and all SGSNs which the UE may be handed over to are Release 8 or above supporting dual addressing, which is determined based on node pre-configuration by the operator. The Protocol Type over S5/S8 is provided to Serving GW which protocol should be used over S5/S8 interface. The charging characteristics for the PS subscription and individually subscribed APNs as well as the way of handling Charging Characteristics and whether to send them or not to the P-GW is defined in TS 32.251[ Telecommunication management;Charging management;Packet Switched (PS) domain charging ] [44]. The MME shall include Trace Reference, Trace Type, Trigger Id, and OMC Identity if S-GW and/or P-GW trace is activated. The MME shall copy Trace Reference, Trace Type, and OMC Identity from the trace information received from the HLR or OMC. The Maximum APN Restriction denotes the most stringent restriction as required by any already active bearer context. If there are no already active bearer contexts, this value is set to the least restrictive type (see clause 15.4 of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]). If the P-GW receives the Maximum APN Restriction, then the P-GW shall check if the Maximum APN Restriction value does not conflict with the APN Restriction value associated with this bearer context request. If there is no conflict the request shall be allowed, otherwise the request shall be rejected with sending an appropriate error cause to the UE. If the MME requires the eNodeB to check whether the UE radio capabilities are compatible with the network configuration (e.g. whether the SRVCC or frequency support by the UE matches that of the network) to be able to set the IMS voice over PS Session Supported Indication (see clause 4.3.5.8), then the MME may send a UE Radio Capability Match Request to the eNodeB as defined in clause 5.3.14. The MME includes the latest APN Rate Control status if it has stored it. Based on UE and Serving GW capability of supporting MT-EDT, Communication Pattern parameters or local policy, the MME may indicate to Serving GW that MT-EDT is applicable for the PDN connection. 13. The Serving GW creates a new entry in its EPS Bearer table and sends a Create Session Request (IMSI, MSISDN, APN, Serving GW Address for the user plane, Serving GW TEID of the user plane, Serving GW TEID of the control plane, RAT type, Default EPS Bearer QoS, PDN Type, PDN Address, subscribed APN-AMBR, EPS Bearer Identity, Protocol Configuration Options, Handover Indication, ME Identity, User Location Information (ECGI), UE Time Zone, User CSG Information, MS Info Change Reporting support indication, PDN Charging Pause Support indication, Selection Mode, Charging Characteristics, Trace Reference, Trace Type, Trigger Id, OMC Identity, Maximum APN Restriction, Dual Address Bearer Flag, Serving Network, APN Rate Control Status) message to the PDN GW indicated by the PDN GW address received in the previous step. After this step, the Serving GW buffers any downlink packets it may receive from the PDN GW without sending a Downlink Data Notification message to the MME until it receives the Modify Bearer Request message in step 23 below. The MSISDN is included if received from the MME. If the Serving GW has received the Control Plane Only PDN Connection Indicator in step 12, the Serving GW informs the PDN GW this information in Create Session Request. The Serving GW and PDN GW shall indicate the use of CP only on their CDRs. PDN GWs shall not perform any checks of Maximum APN Restriction if Create Session Request includes the emergency APN or RLOS APN. For emergency attached or RLOS attached UEs IMSI is included if available and if the IMSI cannot be authenticated then the IMSI shall be marked as unauthenticated. In the case of handover attach, and if the PDN GW detects that the 3GPP PS Data Off UE Status is active, the PDN GW shall indicate this status to the charging system for offline and online charging. 14. If dynamic PCC is deployed and the Handover Indication is not present, the PDN GW performs an IP-CAN Session Establishment procedure as defined in TS 23.203[ Policy and charging control architecture ] [6], and thereby obtains the default PCC rules for the UE. If the UE is accessing over WB-E-UTRA, this may lead to the establishment of a number of dedicated bearers following the procedures defined in clause 5.4.1 in association with the establishment of the default bearer, which is described in Annex F. The IMSI, APN, UE IP address, User Location Information (ECGI), UE Time Zone, Serving Network, RAT type, APN-AMBR, Default EPS Bearer QoS, ETFTU (if ETFTU is not provided it means UE and/or the PDN GW does not support the extended TFT filter format) are provided to the PCRF by the PDN GW if received by the previous message. The User Location Information and UE Time Zone are used for location based charging. For emergency attached or RLOS attached UEs which are unauthenticated the PDN GW provides the IMEI as the UE Identity instead of IMSI, to the PCRF. If the PCRF decides that the PDN connection may use the extended TFT filter format, it shall return the ETFTN indicator to the PDN GW for inclusion in the protocol Configuration Options returned to the UE. The PCRF may modify the APN-AMBR and the QoS parameters (QCI and ARP) associated with the default bearer in the response to the PDN GW as defined in TS 23.203[ Policy and charging control architecture ] [6]. If the PCC is configured to support emergency services and if dynamic PCC is deployed, the PCRF, based on the emergency APN, sets the ARP of the PCC rules to a value that is reserved for emergency services and the authorization of dynamic PCC rules as described in of TS 23.203[ Policy and charging control architecture ] [6]. If dynamic PCC is not deployed, the PDN GW uses the ARP of the default emergency EPS bearer for any potentially initiated dedicated emergency EPS bearer. The P-GW determines that emergency services are requested based on the emergency APN received in Create Session Request message. If the PCC is configured to support Restricted Local Operator Services and if dynamic PCC is deployed, the PCRF, based on the RLOS APN, sets the ARP of the PCC rules to a value based on operator policy and the authorization of dynamic PCC rules as described in of TS 23.203[ Policy and charging control architecture ] [6]. NOTE 11: While the PDN GW/PCEF may be configured to activate predefined PCC rules for the default bearer, the interaction with the PCRF is still required to provide e.g. the UE IP address information to the PCRF. NOTE 12: If the IP address is not available when the PDN GW performs the IP-CAN Session Establishment procedure with the PCRF, the PDN GW initiates an IP-CAN Session Modification procedure to inform the PCRF about an allocated IP address as soon as the address is available. In this version of the specification, this is applicable only to IPv4 address allocation. If dynamic PCC is deployed and the Handover Indication is present, the PDN GW executes a PCEF Initiated IP-CAN Session Modification procedure with the PCRF as specified in TS 23.203[ Policy and charging control architecture ] [6] to report the new IP-CAN type. Depending on the active PCC rules, the establishment of dedicated bearers for the UE may be required. The establishment of those bearers shall take place in combination with the default bearer activation as described in Annex F. This procedure can continue without waiting for a PCRF response. If changes to the active PCC rules are required, the PCRF may provide them after the handover procedure is finished. In both cases (Handover Indication is present or not), if dynamic PCC is not deployed, the PDN GW may apply local QoS policy. If the UE is accessing over WB-E-UTRA, this may lead to the establishment of a number of dedicated bearers for the UE following the procedures defined in clause 5.4.1 in combination with the establishment of the default bearer, which is described in Annex F. If the CSG information reporting triggers are received from the PCRF, the PDN GW should set the CSG Information Reporting Action IE accordingly. If 3GPP PS Data Off status is received in the PCO from the UE and PDN GW supports 3GPP PS Data Off, the PDN GW shall provide the 3GPP PS Data Off status to the PCRF. If the PCRF supports 3GPP PS Data Off, it shall return 3GPP PS Data Off support to the PDN GW for inclusion in the PCO returned to the UE. The additional behaviour of the PDN GW for 3GPP PS Data Off is defined in TS 23.203[ Policy and charging control architecture ] [6]. If received, the PDN GW may take the APN Rate Control Status into account when encoding the APN Rate Control parameters in Protocol Configuration Options and when enforcing the APN Rate Control as described in clause 4.7.7.3. 15. The P-GW creates a new entry in its EPS bearer context table and generates a Charging Id for the Default Bearer. The new entry allows the P-GW to route user plane PDUs between the S-GW and the packet data network, and to start charging. The way the P-GW handles Charging Characteristics that it may have received is defined in TS 32.251[ Telecommunication management;Charging management;Packet Switched (PS) domain charging ] [44]. The PDN GW returns a Create Session Response (PDN GW Address for the user plane, PDN GW TEID of the user plane, PDN GW TEID of the control plane, PDN Type, PDN Address, EPS Bearer Identity, EPS Bearer QoS, Protocol Configuration Options, Charging Id, Prohibit Payload Compression, APN Restriction, Cause, MS Info Change Reporting Action (Start) (if the PDN GW decides to receive UE's location information during the session), CSG Information Reporting Action (Start) (if the PDN GW decides to receive UE's User CSG information during the session), Presence Reporting Area Action (if the PDN GW decides to receive notifications about a change of UE presence in Presence Reporting Area), PDN Charging Pause Enabled indication (if PDN GW has chosen to enable the function), APN-AMBR, Delay Tolerant Connection) message to the Serving GW. The PDN GW takes into account the received PDN type, the Dual Address Bearer Flag and the policies of operator when the PDN GW selects the PDN type to be used as follows. If the received PDN type is IPv4v6 and both IPv4 and IPv6 addressing is possible in the PDN but the Dual Address Bearer Flag is not set, or only single IP version addressing for this APN is possible in the PDN, the PDN GW selects a single IP version (either IPv4 or IPv6). If the received PDN type is IPv4 or IPv6 or "Non-IP" or "Ethernet", the PDN GW uses the received PDN type if it is supported in the PDN, otherwise an appropriate error cause will be returned. For IPv4, IPv6 and IPv4v6, the PDN GW allocates a PDN Address according to the selected PDN type. If the PDN GW has selected a PDN type different from the received PDN Type, the PDN GW indicates together with the PDN type IE a reason cause to the UE why the PDN type has been modified, as described in clause 5.3.1.1. The PDN GW shall either accept or reject (but not modify) the PDN type if the PDN type is set to "Non-IP" or "Ethernet". PDN Address may contain an IPv4 address for IPv4 and/or an IPv6 prefix and an Interface Identifier, or be omitted for PDN types "Non-IP" and "Ethernet". If the PDN has been configured by the operator so that the PDN addresses for the requested APN shall be allocated by usage of DHCPv4 only, or if the PDN GW allows the UE to use DHCPv4 for address allocation according to the Address Allocation Preference received from the UE, the PDN Address shall be set to 0.0.0.0, indicating that the IPv4 PDN address shall be negotiated by the UE with DHCPv4 after completion of the Default Bearer Activation procedure. For external PDN addressing for IPv6, the PDN GW obtains the IPv6 prefix from the external PDN using either RADIUS or Diameter client function. In the PDN Address field of the Create Session Response, the PDN GW includes the Interface Identifier and IPv6 prefix. The PDN GW sends Router Advertisement to the UE after default bearer establishment with the IPv6 prefix information for all cases. If the PDN address is contained in the Create Session Request, the PDN GW shall allocate the IPv4 address and/or IPv6 prefix contained in the PDN address to the UE. The IP address allocation details are described in clause 5.3.1 on "IP Address Allocation". The PDN GW derives the BCM based on the NRSU and operator policy. The PDN GW derives whether the extended TFT filter format is to be used based on the ETFTU, ETFTN received from the PCRF and operator policy. Protocol Configuration Options contains the BCM, ETFTN as well as optional PDN parameters that the P-GW may transfer to the UE. These optional PDN parameters may be requested by the UE, or may be sent unsolicited by the P-GW. Protocol Configuration Options are sent transparently through the MME. The PDN GW includes a Delay Tolerant Connection indication if the PDN GW supports receiving a rejection cause from the SGW indicating that the UE is temporarily not reachable due to power saving and holding mobile terminated procedures, until the PDN GW receives a message indicating that the UE is available for end to end signalling. When the Handover Indication is present, the PDN GW does not yet send downlink packets to the S-GW; the downlink path is to be switched at step 23a. If the PDN GW is an L-GW, it does not forward downlink packets to the S-GW. The packets will only be forwarded to the HeNB at step 20 via the direct user plane path. If the 3GPP PS Data Off UE Status was present in the Create Session Request PCO and the network supports 3GPP PS Data Off feature, the PDN GW shall include the 3GPP PS Data Off Support Indication in the Create Session Response PCO. 16. The Serving GW returns a Create Session Response (PDN Type, PDN Address, Serving GW address for User Plane, Serving GW TEID User Plane, Serving GW TEID for control plane, EPS Bearer Identity, EPS Bearer QoS, PDN GW addresses and TEIDs (GTP-based S5/S8) or GRE keys (PMIP-based S5/S8) at the PDN GW(s) for uplink traffic, Protocol Configuration Options, Prohibit Payload Compression, APN Restriction, Cause, MS Info Change Reporting Action (Start), Presence Reporting Area Action, CSG Information Reporting Action (Start), APN-AMBR, Delay Tolerant Connection) message to the new MME. If Control Plane CIoT EPS Optimisation applies, and if the MME does not include Control Plane Only PDN Connection Indicator in the Create Session Request: - If separation of S11-U from S1-U is required, the Serving GW shall include the Serving GW IP address and TEID for S11-U and additionally the Serving GW IP address and TEID for S1-U in Create Session Response. - Otherwise, if separation of S11-U from S1-U is not required, the Serving GW includes the Serving GW IP address and TEID for S11-U in Create Session Response. 17. If an APN Restriction is received, then the MME shall store this value for the Bearer Context and the MME shall check this received value with the stored value for the Maximum APN Restriction to ensure there are no conflicts between values. If the Bearer Context is accepted, the MME shall determine a (new) value for the Maximum APN Restriction. If there is no previously stored value for Maximum APN Restriction, then the Maximum APN Restriction shall be set to the value of the received APN Restriction. MME shall not deactivate bearer(s) with emergency ARP, if present, to maintain valid APN restriction combination. The P-GW shall ignore Maximum APN restriction if the request includes the Emergency APN. If the MS Info Change Reporting Action (Start) and/or the CSG Information Reporting Action (Start) are received for this bearer context, then the MME shall store this for the bearer context and the MME shall report to that P-GW via the S-GW whenever a UE's location and/or User CSG information change occurs that meets the P-GW request, as described in clause 15.1.1a of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. If Presence Reporting Area Action is received for this bearer context, the MME shall store this information for the bearer context and shall report to that P-GW via the S-GW whenever a change of UE presence in a Presence Reporting Area is detected, as described in clause 5.9.2.2. The MME determines the UE AMBR to be used by the eNodeB based on the subscribed UE-AMBR and the APN-AMBR for the default APN, see clause 4.7.3. For emergency attach or RLOS attach the MME determines the UE-AMBR to be used by the eNodeB from the APN AMBR received from the S-GW. If new MME hasn't received, from Step 12, Voice Support Match Indicator for the UE from the eNodeB then, based on implementation, the MME may set IMS Voice over PS session supported Indication and update it at a later stage. The new MME sends an Attach Accept (GUTI, TAI List, Session Management Request (APN, PDN Type, PDN Address, EPS Bearer Identity, Protocol Configuration Options, Header Compression Configuration, Control Plane Only Indicator, Connection Release Supported, Paging Cause Indication for Voice Service Supported, Reject Paging Request Supported, Paging Restriction Supported, Paging Timing Collision Control Supported), NAS sequence number, NAS-MAC, IMS Voice over PS session supported Indication, Emergency Service Support indicator, LCS Support Indication, Supported Network Behaviour, Service Gap Time, Enhanced Coverage Restricted, Indication for support of 15 EPS bearers per UE, PLMN-assigned UE Radio Capability ID, indication for PLMN-assigned UE Radio Capability ID deletion, Accepted IMSI Offset, Forbidden TAI(s), Enhanced Discontinuous Coverage Support, Return To Coverage Notification Not Required, Maximum Time Offset) message to the eNodeB. GUTI is included if the new MME allocates a new GUTI. PDN Type and PDN Address are omitted if the Attach Request (step 1) did not contain an ESM message container. The MME indicates the CIoT EPS Optimisations it accepts in the Supported Network Behaviour information as defined in clause 4.3.5.10. Service Gap Time is included if Service Gap Time is present in the subscription information (step 11) and the UE has indicated UE Service Gap Control Capability. This message is contained in an S1_MME control message Initial Context Setup Request, unless the MME has selected to use the Control Plane CIoT EPS Optimisation, or, the UE did not include the ESM message container in the Attach Request (step 1), in which case an S1-AP Downlink NAS transport message is used. The S1-AP Initial Context Setup Request message also includes the AS security context information for the UE, the Handover Restriction List, the EPS Bearer QoS, the UE-AMBR, EPS Bearer Identity, as well as the TEID at the Serving GW used for user plane and the address of the Serving GW for user plane and whether User Plane CIoT EPS Optimisation is allowed for the UE. If the PDN type is set to "Non-IP" the MME includes it in the S1-AP Initial Context Setup Request so that the eNodeB disables header compression. If the PDN type is set to "Ethernet" the MME includes it in the S1-AP Initial Context Setup Request so that any eNodeB header compression functionality can act appropriately. In addition, if the PDN connection is established for Local IP Access, the corresponding S1 Initial Context Setup Request message includes a Correlation ID for enabling the direct user plane path between the HeNB and the L-GW. If the PDN connection is established for SIPTO at the Local Network with L-GW function collocated with the (H)eNB, the corresponding S1-AP Initial Context Setup Request message includes a SIPTO Correlation ID for enabling the direct user plane path between the (H)eNB and the L-GW. LIPA and SIPTO do not apply to Control Plane CIoT EPS Optimisation. NOTE 13: In this release of the 3GPP specification the Correlation ID and SIPTO Correlation ID is set equal to the user plane PDN GW TEID (GTP-based S5) or GRE key (PMIP-based S5) that the MME has received in step 16. If Control Plane CIoT EPS Optimisation applies for an IP PDN connection, and the UE has sent in the Attach Request the Header Compression Configuration, and the MME supports the header compression parameters, the MME shall include the Header Compression Configuration in the PDN Connectivity Accept message. The MME also binds the uplink and downlink ROHC channels to support header compression feedback signalling. If the UE has included header compression context setup parameters in Header Compression Configuration in the Attach Request, the MME may acknowledge the header compression context setup parameters. If the ROHC context is not established during the attach procedure for the PDN connection, before using the compressed format for sending the data, the UE and the MME need to establish the ROHC context with ROHC IR packet based on Header Compression Configuration. If the MME based on local policy determines the PDN connection shall only use the Control Plane CIoT EPS Optimisation, the MME shall include a Control Plane Only Indicator in the Session Management Request. For PDN connections with an SCEF, the MME shall always include the Control Plane Only Indicator. A UE receiving the Control Plane Only Indicator, for a PDN connection shall only use the Control Plane CIoT EPS Optimisation for this PDN connection. If the ESM container was not included in the Attach Request in step 1, then the Attach Accept message shall not include PDN related parameters, and the Downlink NAS transfer S1-AP message shall not include Access stratum context related information but may include CSG related information. If the attach type is not set to "Emergency", and the ESM container was included in Attach Request in step 1, and the UE indicated support of Attach without PDN Connection in the Attach Request, and the MME supports Attach without PDN Connection, and PDN connection restriction is set in subscriber data, then the MME shall discard the ESM container in the Attach Request message, and shall not include PDN related parameters in the Attach Accept, but may include CSG related information. In the Attach Accept message, the MME does not include the IPv6 prefix within the PDN Address. The MME includes the EPS Bearer QoS parameter QCI and APN-AMBR into the Session Management Request. Furthermore, if the UE has UTRAN or GERAN capabilities and the network supports mobility to UTRAN or GERAN, the MME uses the EPS bearer QoS information to derive the corresponding PDP context parameters QoS Negotiated (R99 QoS profile), Radio Priority, Packet Flow Id and TI and includes them in the Session Management Request. If the UE indicated in the UE Network Capability it does not support BSS packet flow procedures, then the MME shall not include the Packet Flow Id. Handover Restriction List is described in clause 4.3.5.7 "Mobility Restrictions". The MME sets the IMS Voice over PS session supported Indication as described in clause 4.3.5.8. LCS Support Indication indicates whether the network supports the EPC-MO-LR and/or CS-MO-LR as described in TS 23.271[ Functional stage 2 description of Location Services (LCS) ] [57]. The MME may include an indication whether the traffic of this PDN Connection is allowed to be offloaded to WLAN, as described in clause 4.3.23. Indication for support of 15 EPS bearers per UE indicates the network support for up to 15 EPS bearers per UE as defined in clause 4.12. If the UE initiates the Attach procedure at a hybrid cell, the MME shall check whether the CSG ID is contained in the CSG subscription and is not expired. The MME shall send an indication whether the UE is a CSG member to the RAN along with the S1-MME control message. Based on this information, the RAN may perform differentiated treatment for CSG and non-CSG members. If the MME or PDN GW has changed the PDN Type, an appropriate reason cause shall be returned to the UE as described in clause 5.3.1.1. If the UE has indicated PDN type "Non-IP" or "Ethernet", the MME and PDN GW shall not change PDN type. For an emergency attached UE, i.e. for UEs that have only emergency EPS bearers established, there is no AS security context information included in the S1 control messages and there is no NAS level security when the UE cannot be authenticated. The Emergency Service Support indicator informs the UE that Emergency bearer services are supported, i.e. the UE is allowed to request PDN connectivity for emergency services. For RLOS attached UEs, i.e. for UEs that have only RLOS PDN connection established, there is no AS security context information included in the S1 control messages and there is no NAS level security when the UE cannot be successfully authenticated. If the UE included extended idle mode DRX parameters information element, the MME includes extended idle mode DRX parameters information element if it decides to enable extended idle mode DRX with Paging Time Window length assigned considering Subscribed Paging Time Window (if available) and the local policy. Additionally, for a UE using an eNodeB that provides discontinuous coverage (e.g. for satellite access with discontinuous coverage), the MME may consider this as described in clause 4.13.8.2 when determining extended idle mode DRX parameters. If the UE provided the UE paging probability information in Step 1, the MME takes it into account when generating the WUS Assistance Information. If the MME has determined WUS Assistance Information for the UE, the MME shall send the WUS Assistance Information to 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 ] [5]). If the UE included support for restriction of use of Enhanced Coverage in step 1, the MME sends Enhanced Coverage Restricted parameter to the eNodeB in S1-AP Initial Context Set-up Request message. MME also sends Enhanced Coverage Restricted parameter to the UE in the Attach Accept message. If the UE has indicated support for dual connectivity with NR in the Attach Request and the UE is not allowed to use NR as Secondary RAT, the MME indicates that to the UE in the Attach Accept message. If RACS is supported in the MME and MME has received UE Radio Capability ID earlier in this procedure, it signals the UE Radio Capability ID to the eNodeB in S1-AP Initial Context Set-up Request message. If the eNodeB does not have mapping between the specific UE Radio Capability ID and the UE radio capabilities, it shall use the procedure described in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36] to retrieve the mapping from the MME. When the UE supports RACS, and the MME needs to configure the UE with a UE Radio Capability ID, and the MME already has the UE radio capabilities for the UE, the MME may provide the UE with the UE Radio Capability ID for the UE radio capabilities the UCMF returns to the MME for this UE. If MME has authorized the UE's IAB operation in step 11 based on the IAB-Operation Allowed indication, it shall include an "IAB Authorized" indication in the S1-AP Initial Context Set-up Request message to the eNodeB. If the UE had included a UE Specific DRX parameter for NB-IoT in the Attach Request, the MME includes the Accepted NB-IoT DRX parameter. If the UE provided a Requested IMSI Offset in step 1, but the network prefers a different value, the MME provides the UE with an Accepted IMSI Offset different from the one provided in step 1. Otherwise the value of the Accepted IMSI Offset the MME sends is the value of the Requested IMSI Offset sent by the UE in step 1. The MME stores the value of the alternative IMSI derived from the Accepted IMSI Offset (see clause 4.3.33) provided to the UE in the UE context. If a Multi-USIM mode UE does not provide a Requested IMSI Offset in step 1, the MME erases any Alternative IMSI value in the UE context. If the Multi-USIM UE has indicated one or more Multi-USIM specific capabilities are supported in the UE Core Network Capability in step 1, the MME shall indicate whether the corresponding one or more Multi-USIM specific features described in clause 4.3.33 are supported based on network capability and preference by the network (i.e. based on local network policy) by providing one or more of the Connection Release Supported, Paging Cause Indication for Voice Service Supported, Reject Paging Request Supported, Paging Restriction Supported and Paging Timing Collision Control Supported indications. The MME shall only indicate Paging Restriction Supported together with either Connection Release Supported or Reject Paging Request Supported. The UE shall only use Multi-USIM specific features that the MME indicated as being supported. In the case of Emergency Attach, the MME shall not indicate support for any Multi-USIM feature to the UE. If the MME receives multiple TAIs from E-UTRAN in step 2 and determines that some, but not all, TAIs in the received list of TAIs are forbidden by subscription or by operator policy, the MME shall include the forbidden TAI(s) in the Attach Accept message. If both UE and network support discontinuous coverage, the MME provides the Enhanced Discontinuous Coverage Support indication as described in clause 4.13.8.1. For a UE using a eNodeB that provides discontinuous coverage (e.g. for satellite access with discontinuous coverage), the MME may provide Return To Coverage Notification Not Required, which requests the UE in ECM_IDLE state to not perform the TAU procedure when it returns to coverage as described in clause 4.13.8.2. The MME may also provide a Maximum Time Offset as described in clause 4.13.8.6. 18. If the eNodeB received an S1-AP Initial Context Setup Request the eNodeB sends the RRC Connection Reconfiguration message including the EPS Radio Bearer Identity to the UE, and the Attach Accept message will be sent along to the UE. If the eNodeB received an S1-AP Downlink NAS Transport message (e.g. containing the Attach Accept message), the eNode B sends a RRC Direct Transfer message to the UE. The UE shall store the QoS Negotiated, Radio Priority, Packet Flow Id and TI, which it received in the Session Management Request, for use when accessing via GERAN or UTRAN. The APN is provided to the UE to notify it of the APN for which the activated default bearer is associated. For further details, see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37]. The UE may provide EPS Bearer QoS parameters to the application handling the traffic flow(s). The application usage of the EPS Bearer QoS is implementation dependent. The UE shall not reject the RRC Connection Reconfiguration on the basis of the EPS Bearer QoS parameters contained in the Session Management Request. If the UE receives Enhanced Coverage Restricted parameter in the Attach Accept message, UE shall store this information and shall use the value of Enhanced Coverage Restricted parameter to determine if enhanced coverage feature should be used or not. If the UE receives a Service Gap Time in the Attach Accept message, the UE shall store this parameter and apply Service Gap Control (see clause 4.3.17.9). If the attach procedure is initiated by manual CSG selection and occurs via a CSG cell, the UE upon receiving the Attach accept shall check if the CSG ID and associated PLMN of the cell where the UE has sent the Attach Request message is contained in its Allowed CSG list. If the CSG ID and associated PLMN is not in the UE's Allowed CSG list, the UE shall add the CSG ID and associated PLMN to its Allowed CSG list. Manual CSG selection is not supported when an emergency service has been initiated. NOTE 14: If the UE receives an Attach Accept message via a hybrid cell, the UE does not add the corresponding CSG ID and associated PLMN to its Allowed CSG list. Adding a CSG ID and associated PLMN to the UE's local Allowed CSG list for a hybrid cell is performed only by OTA or OMA DM procedures. When receiving the Attach Accept message the UE shall set its TIN to "GUTI" as no ISR Activated is indicated. If the UE receives an IPv4 address set to 0.0.0.0, it may negotiate the IPv4 address with DHCPv4 as specified in TS 29.061[ Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) ] [38]. If the UE receives an IPv6 interface identifier, it may wait for the Router Advertisement from the network with the IPv6 prefix information or it may send a Router Solicitation if necessary. NOTE 15: The IP address allocation details are described in clause 5.3.1 on "IP Address Allocation". If Control Plane CIoT EPS Optimisation applies or the UE has not included the ESM message container in the Attach Request in step 1, then the steps 19 and 20 are not executed. 19. The UE sends the RRC Connection Reconfiguration Complete message to the eNodeB. For further details, see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37]. 20. The eNodeB sends the Initial Context Response message to the new MME. This Initial Context Response message includes the TEID of the eNodeB and the address of the eNodeB used for downlink traffic on the S1_U reference point. The MME shall be prepared to receive this message either before or after the Attach Complete message (sent in step 22). If the Correlation ID or SIPTO Correlation ID was included in the Initial Context Setup Request message, the eNodeB shall use the included information to establish direct user plane path with the L-GW and forward uplink data for Local IP Access or SIPTO at the Local Network with L-GW function collocated with the (H)eNB accordingly. 21. The UE sends a Direct Transfer message to the eNodeB, which includes the Attach Complete (EPS Bearer Identity, NAS sequence number, NAS-MAC) message. If the UE omitted the ESM message container from the Attach Request message in step 1, then the EPS Bearer Identity is omitted from the Attach Complete message. 22. The eNodeB forwards the Attach Complete message to the new MME in an Uplink NAS Transport message. If the ESM message container was included in step 1, after the Attach Accept message and once the UE has obtained (if applicable to the PDN type) a PDN Address, the UE can then send uplink packets towards the eNodeB which will then be tunnelled to the Serving GW and PDN GW. If Control Plane CIoT EPS Optimisations apply, UL data is sent as specified in clause 5.3.4B. If the UE requested for a dual address PDN type (IPv4v6) to a given APN and was granted a single address PDN type (IPv4 or IPv6) by the network with a reason cause indicating that only single IP version per PDN connection is allowed sent together with the PDN type, the UE should request for the activation of a parallel PDN connection to the same APN with a single address PDN type (IPv4 or IPv6) other than the one already activated. If the UE receives no reason cause in step 18 in response to an IPv4v6 PDN type and it receives an IPv6 Interface Identifier apart from the IPv4 address or 0.0.0.0 in the PDN Address field, it considers that the request for a dual address PDN was successful. It can wait for the Router Advertisement from the network with the IPv6 prefix information or it may send Router Solicitation if necessary. 23. Upon reception of both, the Initial Context Response message in step 20 and the Attach Complete message in step 22, the new MME sends a Modify Bearer Request (EPS Bearer Identity, eNodeB address, eNodeB TEID, Handover Indication, Presence Reporting Area Information, RAT type, LTE-M RAT type reporting to PGW) message to the Serving GW. If the Control Plane CIoT EPS Optimisation applies and the PDN connection is not served by a SCEF and if the MME does not need to report a change of UE presence in Presence Reporting Area, sending of Modify Bearer Request and steps 23a, 23b and 24 are skipped; otherwise if the PDN connection is served by SCEF, steps 23,24, 25, and 26 are not executed. If the MME has been requested to report a change of UE presence in Presence Reporting Area, the MME includes in this message the Presence Reporting Area Information comprising the PRA identifier(s) and indication(s) on whether the UE is inside or outside the area(s). When receiving the request for reporting change of UE presence in Presence Reporting Area, and the MME decides not to activate reporting UE presence in one or more of the received Presence Reporting Area(s), the MME reports also the inactive Presence Reporting Area(s) in this message. The RAT type information element is included if the UE is using the LTE-M RAT type. If PDN GW expects the LTE-M RAT type reporting as specified in clause 5.11.5, the MME also includes the LTE-M RAT type reporting to PGW flag to indicate that the Serving GW needs to forward the LTE-M RAT type to the PGW. 23a. If the Handover Indication is included in step 23, the Serving GW sends a Modify Bearer Request (Handover Indication) message to the PDN GW to prompt the PDN GW to tunnel packets from non 3GPP IP access to 3GPP access system and immediately start routing packets to the Serving GW for the default and any dedicated EPS bearers established. If Presence Reporting Area Information is included in step 23, the Serving GW sends a Modify Bearer Request (Presence Reporting Area Information) message to the PDN GW. If the LTE-M RAT type and the LTE-M RAT type reporting to PGW flag were received at step 23, the Serving GW shall include the LTE-M RAT type in the Modify Bearer Request message to the PGW. Otherwise the Serving GW includes RAT type WB-E-UTRAN. NOTE 16: The PDN GW is expected to handle the uplink packets sent by the UE via 3GPP access after step 22, even if they arrive before path switch in step 23. NOTE 17: The PDN GW forwards the Presence Reporting Area Information to the PCRF, to the OCS or to both as defined in TS 23.203[ Policy and charging control architecture ] [6]. 23b. The PDN GW acknowledges by sending Modify Bearer Response to the Serving GW. 24. The Serving GW acknowledges by sending Modify Bearer Response (EPS Bearer Identity) message to the new MME. The Serving GW can then send its buffered downlink packets. If there is a "Availability after DDN Failure" monitoring event or a "UE Reachability" monitoring event configured for the UE in the EMM Context of the MME, the MME sends an event notification (see TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74] for further information). 25. After the MME receives Modify Bearer Response (EPS Bearer Identity) message, if Request Type does not indicate handover and an EPS bearer was established and the subscription data indicates that the user is allowed to perform handover to non-3GPP accesses, and if the MME selected a PDN GW that is different from the PDN GW identity which was indicated by the HSS in the PDN subscription context, the MME shall send a Notify Request including the APN and PDN GW identity to the HSS for mobility with non-3GPP accesses. The message shall include information that identifies the PLMN in which the PDN GW is located. If the ME identity of the UE has changed and step 8 has not been performed, the MME sends a Notify Request (ME Identity) message to inform the HSS of the updated ME identity. For an unauthenticated or roaming UE, if the Request Type of the UE requested connectivity procedure indicates "Emergency", the MME shall not send any Notify Request to an HSS. For a non-roaming authenticated UE, based on operator configuration (e.g. on whether Voice over WLAN is supported or not by the operator, on whether the operator uses a fixed PDN GW for emergency calls, etc.), if the Request Type indicates "Emergency", the MME may send a Notify Request to the HSS including the "PDN GW currently in use for emergency services", which comprises the PDN GW address and an indication that the PDN connection is for emergency services. The HSS shall store it as part of the UE context for emergency services. For any UEs, if Request Type of the UE requested connectivity procedure indicates "RLOS", the MME shall not send any Notify Request to an HSS. After step 8, and in parallel to any of the preceding steps, the MME shall send a Notify Request (Homogeneous Support of IMS Voice over PS Sessions) message to the HSS: - If the MME has evaluated the support of IMS Voice over PS Sessions, see clause 4.3.5.8, and - If the MME determines that it needs to update the Homogeneous Support of IMS Voice over PS Sessions, see clause 4.3.5.8A. 26. In the case of non-emergency services, the HSS stores the APN and PDN GW identity pair. In the case of emergency services, the HSS stores the "PDN GW currently in use for emergency services". The HSS then sends a Notify Response to the MME. NOTE 18: For handover from non-3GPP access, the PDN GW initiates resource allocation deactivation procedure in the trusted/untrusted non-3GPP IP access as specified in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.2.1 |
3,836 | 17 Usage of Diameter on Gmb interface | Signalling between GGSN and BM-SC is exchanged at Gmb reference point. BM-SC functions for different MBMS bearer services may be provided by different physical network elements. To allow this distribution of BM-SC functions, the Gmb protocol must support the use of proxies to correctly route the different signalling interactions in a manner which is transparent to the GGSN. The GGSN uses the Gmb interface - to request authorisation/deactivation of a user for a multicast MBMS service, - to register/de-register the GGSN for receiving a multicast MBMS service. - to receive indication of session start, session update and session stop messages, which shall cause the GGSN, SGSN and RAN to set up/tear down the appropriate resources for the service. For further details, see 3GPP TS 23.246[ Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description ] [65]. - to receive indication if IP multicast distribution to UTRAN should be used for the MBMS user plane data. The support of Gmb within the GGSN is optional, and needed for MBMS. The Gmb application is defined as an IETF vendor specific Diameter application, where the vendor is 3GPP. The vendor identifier assigned by IANA to 3GPP (http://www.iana.org/assignments/enterprise-numbers) is 10415. The Gmb application identifier value assigned by IANA is 16777223. The Gmb application identifier value shall be included in the Auth-Application-Id AVP. The BM-SC and the GGSN shall advertise the support of the Gmb application by including the value of the application identifier in the Auth-Application-Id AVP and the value of the 3GPP (10415) in the Vendor-Id AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands as specified in IETF RFC 6733 [111], i.e. as part of the Vendor-Specific-Application-Id AVP. The Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands are specified in the Diameter Base Protocol. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 17 |
3,837 | 9.3.1 Frequency-selective scheduling mode | The accuracy of sub-band channel quality indicator (CQI) reporting under frequency selective fading conditions is determined by a double-sided percentile of the reported differential CQI offset level 0 per sub-band, and the relative increase of the throughput obtained when transmitting on a randomly selected sub-band among the sub-bands with the highest reported differential CQI offset level the corresponding transport format compared to the case for which a fixed format is transmitted on any sub-band in set S of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6]. The purpose is to verify that preferred sub-bands can be used for frequently-selective scheduling. To account for sensitivity of the input SNR the sub-band CQI reporting under frequency selective fading conditions is considered to be verified if the reporting accuracy is met for at least one of two SNR levels separated by an offset of 1 dB. | 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.1 |
3,838 | 6.8B.5 Mapping to resource elements | Mapping to resource elements shall be done according to Clause 6.8A.5 with the following exceptions: - The term EPDCCH shall be replaced by MPDCCH. - The mapping shall be repeated across each of the BL/CE DL subframes. - is the number of ECCEs used for this MPDCCH in the first of the subframes. - For an MPDCCH associated with a 2+4 PRB set as defined in [4], the mapping to resource elements on antenna port shall be in increasing order of first the index and then the index over the 6 PRBs for MPDCCH format 5 and over the 2 or 4 PRBs for the other MPDCCH formats. - For localized transmission and MPDCCH format 5, the single antenna port to use is given by Table 6.8A.5-1 with where equals the C-RNTI. - Resource elements occupied by CSI reference signals shall be counted in the MPDCCH mapping but not used for transmission of the MPDCCH. - PRB pairs occupied by RSS shall be counted in the MPDCCH mapping but not used for transmission of the MPDCCH. - Resource elements belonging to PRBs in which PRS is transmitted (including PRS muted subframes) shall be counted in the MPDCCH mapping but not used for transmission of the MPDCCH. - A BL/CE UE not configured with higher layer parameter ce-pdsch-maxBandwidth-config and not configured with higher layer parameter ce-PDSCH-FlexibleStartPRB-AllocConfig may assume there is no MPDCCH transmission which uses overlapping sets of subframes as PDSCH transmissions to that UE, where the MPDCCH is located at a different narrowband than the PDSCH. - A BL/CE UE configured with higher layer parameter ce-pdsch-maxBandwidth-config may assume that there is no MPDCCH transmission which uses overlapping sets of subframes as PDSCH transmissions to that UE, where the MPDCCH transmission and PDSCH transmission in any of the overlapping subframes span a PRB region larger than X contiguous PRBs where X=25 if ce-pdsch-maxBandwidth-config is set to 5 MHz and X=100 if ce-pdsch-maxBandwidth-config is set to 20 MHz. - A BL/CE UE configured with higher layer parameter ce-PDSCH-FlexibleStartPRB-AllocConfig may assume there is no MPDCCH transmission in MPDCCH candidates not fully contained within the tuning narrowband defined for PDSCH in Clause 6.2.8. - For BL/CE UEs in CEModeB, in MBSFN subframe(s), resource elements that correspond to the positions of cell-specific reference signals as in subframe #0 shall not be counted in the MPDCCH mapping and not used for transmission of the MPDCCH. - Resource elements belonging to synchronization signals, the core part of PBCH, PBCH repetitions, or resource elements reserved for reference signals in the mapping operation of PBCH but not used for transmission of reference signals, shall be counted in the MPDCCH mapping but not used for transmission of the MPDCCH. - If MPDCCH transmission in the LTE control region is configured by the higher layer parameter transmissionInControlChRegion, - For frame structure type 1 and frame structure type 2 except special subframe configuration 9 or 10, - Symbols used for transmission of MPDCCH or demodulation signals associated with MPDCCH and mapped to resource element in the second slot, where , shall additionally be mapped to resource element in the first slot. - For frame structure type 2 and special subframe configuration 9 or 10, - Symbols used for transmission of MPDCCH or demodulation signals associated with MPDCCH and mapped to resource element in the first slot, where , shall additionally be mapped to resource element in the first slot, if resource element in the first slot is not used for cell-specific reference signals. - In the subframes where an MPDCCH or its associated PDSCH is transmitted in response to a physical random access transmission initiated by a PDCCH order, the UE shall receive the MPDCCH or its associated PDSCH, and assume no other UE-specific reception is needed. - For MPDCCH transmission associated with C-RNTI or TPC-PUCCH-RNTI or TPC-PUSCH-RNTI or SPS C-RNTI that are not configured to use the Type2-MPDCCH common search space, frequency hopping of the MPDCCH is enabled when higher layer parameter mpdcch-pdsch-HoppingConfig is set. - For MPDCCH transmission associated with PUR-RNTI using UE-specific MPDCCH search space, frequency hopping of the MPDCCH is enabled when mpdcch-FreqHopping in higher layer parameter PUR-MPDCCH-Config is set. - For MPDCCH transmission associated with Type2-MPDCCH common search space, frequency hopping of the MPDCCH is enabled when higher layer parameter rar-HoppingConfig is set. Further - if PRACH CE level 0 or 1 is used for the last PRACH attempt, is set to the higher layer parameter interval-DlHoppingConfigCommonModeA; - if PRACH CE level 2 or 3 is used for the last PRACH attempt, is set to the higher layer parameter interval-DlHoppingConfigCommonModeB. - For MPDCCH transmission associated with SC-RNTI, frequency hopping of the MPDCCH is enabled when higher layer parameter mpdcch-pdsch-HoppingConfig-SC-MCCH is set. Further - if mpdcch-pdsch-HoppingConfig-SC-MCCH is set to CEModeA, is set to the higher layer parameter interval-DlHoppingConfigCommonModeA; - if mpdcch-pdsch-HoppingConfig-SC-MCCH is set to CEModeB, is set to the higher layer parameter interval-DlHoppingConfigCommonModeB. - For MPDCCH transmission associated with G-RNTI, frequency hopping of the MPDCCH is enabled when higher layer parameter mpdcch-pdsch-HoppingConfig-SC-MTCH is set. Further - if mpdcch-pdsch-CEmodeConfig-SC-MTCH is set to CEModeA, is set to the higher layer parameter interval-DlHoppingConfigCommonModeA; - if mpdcch-pdsch-CEmodeConfig-SC-MTCH is set to CEModeB, is set to the higher layer parameter interval-DlHoppingConfigCommonModeB. - The narrowband for MPDCCH transmission in the first subframe of MPDCCH search space is provided by higher layers. Starting subframe configuration of a search space where UE monitors an MPDCCH is also provided by higher layers. The MPDCCH search space uses subframes, spanning consecutive subframes, including subframes that are not BL/CE DL subframes where the MPDCCH transmission is postponed. - If downlink resource reservation is enabled for the UE as specified in [9], then in case of MPDCCH transmission associated with C-RNTI or SPS C-RNTI using UE-specific MPDCCH search space, - In a subframe that is fully reserved as defined in clause 7.1 in [4], the MPDCCH transmission is postponed until the next BL/CE downlink subframe that is not fully reserved. - In a subframe that is partially reserved, the reserved resource elements shall be counted in the MPDCCH mapping but not used for transmission of the MPDCCH. - If frequency hopping is not enabled for MPDCCH, the repetitions of an MPDCCH candidate are located at the same PRB resources in the same narrowband , and - if frequency hopping is enabled for MPDCCH, an MPDCCH candidate shall be transmitted in absolute subframe using the same PRB resources within each narrowband where is the absolute subframe number of the first downlink subframe of MPDCCH search space, and , and are cell-specific higher-layer parameters. The UE shall not expect MPDCCH transmission in absolute subframe if it is not a BL/CE DL subframe. - The UE may assume the same precoding matrix being used for a PRB across a block of consecutive subframes for MPDCCH, where the subframe number of the first subframe in each block of consecutive subframes, denoted as , satisfies . - If crs-ChEstMPDCCH-ConfigCommon or crs-ChEstMPDCCH-ConfigDedicated is configured by higher layers, the relation between the MPDCCH and CRS antenna ports is defined as follows: - When one CRS port is configured by the eNB, the antenna port(s) used for MPDCCH transmission are equivalent to CRS port 0. - For distributed transmission and when two CRS ports are configured by the eNB, the relation between the symbols transmitted on the antenna ports used for MPDCCH transmission and CRS ports 0 – 1 is defined by the precoder matrix for single-layer transmission in Table 6.3.4.2.3-1 using codebook index for antenna port 107 and codebook index for antenna port 109. - For distributed transmission and when four CRS ports are configured by the eNB, in absolute subframe and resource block index within one or two MPDCCH PRB sets where UE monitors an MPDCCH, the relation between the symbols transmitted on the antenna ports used for MPDCCH transmission and CRS ports 0 – 3 is defined by the precoder matrix for single-layer transmission in Table 6.3.4.2.3-2 using codebook index for antenna port 107 and codebook index for antenna port 109, where - For localized transmission, when two CRS ports are configured by the eNB and predefined mapping type is used, in absolute subframe and resource block index within one or two MPDCCH PRB sets where UE monitors an MPDCCH, the relation between the symbols transmitted on the antenna port used for MPDCCH transmission and CRS ports 0 – 1 is defined by the precoder matrix for single-layer transmission in Table 6.3.4.2.3-1, with codebook index , where - For localized transmission, when four CRS ports are configured by the eNB and predefined mapping type is used, in absolute subframe and resource block index within one or two MPDCCH PRB sets where UE monitors an MPDCCH, the relation between the symbols transmitted on the antenna port used for MPDCCH transmission and CRS ports 0 – 3 is given by the precoder matrix for single-layer transmission in Table 6.3.4.2.3-2 using codebook index where - For localized transmission and when CSI-based or reciprocity-based mapping type is used, the relation between the symbols transmitted on the antenna port used for MPDCCH transmission and the CRS ports is given in [4]. When it is indicated in [4] that the antenna port is changed for an MPDCCH candidate with aggregation level 2, the antenna port shall be replaced by the antenna port determined for an MPDCCH candidate with aggregation level 4 in the same search space. - NOTE: , with for and otherwise, where the ordering of PRBs within the PRB set(s) is in increasing order of PRB index. The UE may assume that an MPDCCH associated with the P-RNTI is transmitted on the set of narrowbands where is defined in Clause 6.4.1. For a UE monitoring an MPDCCH associated with the P-RNTI, the first MPDCCH narrowband is given by where , is the Paging Narrowband (PN) obtained according to [10], and is the higher-layer parameter paging-narrowBands. - If the higher-layer parameter si-HoppingConfigCommon disables frequency hopping for an MPDCCH associated with P-RNTI, each MPDCCH candidate shall be located in the same PRB in narrowband where . - If the higher-layer parameter si-HoppingConfigCommon enables frequency hopping for an MPDCCH with P-RNTI, an MPDCCH candidate shall be located in narrowband in absolute subframe using the same PRB resources within each narrowband where where is the absolute subframe number of the first downlink subframe of MPDCCH search space according to locations of paging opportunity subframes, and , and are cell-specific higher-layer parameters. For MPDCCH associated with P-RNTI, if interval-DlHoppingConfigCommonModeB is signalled in SIB1-BR, then the frequency hopping granularity is set to interval-DlHoppingConfigCommonModeB; otherwise, is set to interval-DlHoppingConfigCommonModeA signalled in SIB1-BR. The UE shall not expect MPDCCH transmission in absolute subframe if it is not a BL/CE DL subframe. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.8B.5 |
3,839 | 6.3.1.0 Principles for Binding, Selection and Reselection | Binding can be used to indicate suitable target NF producer instance(s) for NF service instance selection, reselection and routing of subsequent requests associated with a specific NF producer resource (context) and NF service. This allows the NF producer to indicate that the NF consumer, for a particular context, should be bound to an NF service instance, NF instance, NF service set or NF set depending on local policies and other criteria (e.g. at what point it is in the middle of a certain procedure, considering performance aspects etc). Binding can also be used by the NF consumer to indicate suitable NF consumer instance(s) for notification target instance reselection and routing of subsequent notification requests associated with a specific notification subscription and for providing Binding Indication for service(s) that the NF consumer produces for the same data context and the NF service producer is subsequently likely to invoke. The Binding Indication contains the information in Table 6.3.1.0-1. The Routing Binding Indication may be included in Request, Subscribe or Notification messages (see clause 7.1.2). It may be used in the case of indirect communication by the SCP to route the message. The Routing Binding Indication is a copy of the information in the Binding Indication and also contains the information in Table 6.3.1.0-1. NOTE 1: Subscription request messages can contain both a Binding Indication and a Routing Binding Indication. The NF service producer may provide a Binding Indication to the NF service consumer as part of the Direct or Indirect Communication procedures, to be used in subsequent related service requests. The level of Binding Indication provided by the NF service producer to the NF consumer indicates if the resource in the NF service producer is either bound to NF service instance, NF instance, NF Service Set or NF set as specified in Table 6.3.1.0-1. The Binding Indication may include NF Service Set ID, NF Set ID, NF instance ID, or NF service instance ID, for use by the NF consumer or SCP for NF Service Producer (re-)selection. If the resource is created in the NF Service Producer, the NF Service Producer provides resource information which includes the endpoint address of the NF service producer. For indirect communication, the NF service consumer copies the Binding Indication into the Routing Binding Indication in Request or Subscribe message, unless the NF service consumer performs a reselection for indirect communication without delegated discovery. During explicit or implicit notification subscription, a Binding Indication may be provided by the NF service consumer to NF service producer; the NF service consumer will also provide a Notification Endpoint. The NF service consumer may also provide a Binding Indication in response to notification requests. The level of Binding Indication provided by the NF service consumer to the NF service provider indicates if the Notification Endpoint is either bound to NF service instance, NF instance, NF Service Set or NF set as specified in Table 6.3.1.0-1. The Binding Indication shall include at least one of NF Set ID, NF instance ID, NF Service Set ID and/or NF service instance ID, and may also include the service name. The NF Service Set ID, NF service instance ID, and service name relate to the service of the NF service consumer that will handle the notification. NOTE 2: The NF service can either be a standardised service as per this specification or a custom service. The custom service can be used for the sole purpose of registering endpoint address(es) to receive notifications at the NRF. The Binding Indication is used by the NF service producer as notification sender to reselect an endpoint address and construct the Notification Endpoint, i.e. the URI where the notification is to be sent, e.g. if the provided Notification Endpoint of the NF service consumer included in the subscription cannot be reached, according to the following: - If the service name in the Binding Indication is omitted and the binding for notification is on NF Set or NF Instance level, the endpoint address registered in the NRF at NF Profile level of the NF(s) selected according to the Binding Indication shall be used to construct a new Notification Endpoint. - If the service name is included in the Binding Indication, an endpoint address registered in the NRF for that service in the NF profile(s) selected according to the Binding Indication shall be used to construct a new Notification Endpoint. For indirect communication, the NF service producer copies the Binding Indication into the Routing Binding Indication that is included in the Notification request, to be used by the SCP to discover an alternative endpoint address and construct a Notification Endpoint e.g. if the Notification Endpoint that the request targets cannot be reached, according to the following: - If the service name in the Routing Binding Indication is omitted and the binding for notification is on NF Set or NF Instance level, the endpoint address registered in the NRF at NF Profile level of the NF(s) selected according to the Binding Indication shall be used to construct a new Notification Endpoint. - If the service name is included in the Routing Binding Indication, an endpoint address registered in the NRF for that service in the NF profile(s) selected according to the Binding Indication shall be used to construct a new Notification Endpoint. For subscription to notifications via another network function, a separate Binding Indication for subscription related events may be provided by the NF service consumer (see clause 4.17.12.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]) and if provided shall be associated with an applicability indicating notification for subscription related events. If the NF as an NF consumer provides a Binding Indication for services that the NF produces in service requests, the Binding Indication shall be associated with an applicability indicating other service and may contain the related service name(s), in addition to the other parameters listed in Table 6.3.1.0-1. If no service name(s) are provided, the Binding Indication relates to all services that the NF produces. For NF Set or NF Instance level of binding, a Binding Indication for notifications and other services may be combined if it relates to the same service, and that combined Binding Indication shall then be associated with an applicability indicating all scenarios that the Binding Indication relates to (For this purpose, the applicability can indicate a combination of values). If no applicability is indicated in a request or subscribe messages, a Binding Indication in that messages is applicable for notification to all events except for the subscription related event (see clause 4.17.12.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]). NOTE 3: Such a request message can be used for implicit subscription. NOTE 4: Request messages can contain both the Binding Indications for services and for notifications, and in addition, the Routing Binding Indication in the case of indirect communication. A Binding Indication may be shared by a group of resources (e.g. contexts) identified by a group identifier. This enables a NF Service consumer or producer to update the binding indication for this group of resources in a single request or notification towards a given peer NF service instance, e.g. when a group of resources need to be taken over by a different NF within an NF set. See clause 6.12.1 of TS 29.500[ 5G System; Technical Realization of Service Based Architecture; Stage 3 ] [49]. Table 6.3.1.0-1 defines the selection and reselection behaviour of NF services consumers and SCPs depending on the Binding Indication provided by an NF service producer. The detailed procedures refer to clause 4.17.11 and 4.17.12 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. Table 6.3.1.0-1: Binding, selection and reselection | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.1.0 |
3,840 | 5.28.5.2 5GS DetNet node reporting | The TSCTSF may provide exposure information to the DetNet controller using information collected from the 5GS entities. The exposure information can be used by the DetNet controller to build up the network topology information. The exposure may be based on IETF RFC 8343 [151] and IETF RFC 8344 [152]. The TSCTSF may collect the information from the UPF/NW-TT via parameters in PMIC as defined in clause 5.28.3.1. For the device side ports, the TSCTSF collects information using parameters provided from SMF to TSCTSF via PCF as described in clause 6.1.3.23b of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. When the MTU size for IPv4 or IPv6 is not provided to TSCTSF for a port, the TSCTSF may use a pre-configured default value for IPv4 or IPv6. In the case of network side ports, the TSCTSF may collect information on the type of the interface (defined in IETF RFC 8343 [151], with values defined in IETF RFC 7224 [153]) associated with the port. In the case of device side ports, which correspond to the PDU Sessions that are reported to the TSCTSF, the default value of "3GPP WWAN" (wwanPP) for the interface type is assumed. The TSCTSF can differentiate network side ports as they are reported from the NW-TT within UMIC/PMIC, while device side ports correspond to the PDU Sessions, reported to the TSCTSF in the associated AF sessions. For device side ports also information on IP addresses or IP prefixes not directly assigned to the port but reachable via the port may be provided. On the device side ports, these are related to Framed Routes, i.e. a range of IPv4 addresses or IPv6 prefixes reachable over a single PDU Session, as defined in clause 5.6.14, or prefixes delegated by IPv6 prefix delegation as defined in clause 5.8.2.2. This additional information helps both the TSCTSF and the DetNet controller to map flows to the correct UE address as described in clause 5.28.5.3. For the network side ports, the TSCTSF may also collect information on the link layer address and neighbor IP nodes. The ports are identified by the port number within the 3GPP system. The port number may also be used to generate interface identifiers towards the DetNet controller that are unique within the 5GS node. NOTE 1: One possibility to generate unique interface identifiers towards the DetNet controller is to use the port number as the if-Index as defined in IETF RFC 8343 [151]. Based on the if-Index, an interface name is generated, e.g. by using the if-Index as a string, possibly adding a substring prefix or postfix based on configuration. The if-Index and the name of the interface contain essentially the same information, but both can be provided, since the name is used as the key in the YANG model, while if-Index is usually considered as the basis for interface management of IP nodes. The TSCTSF may use the user-plane node ID provided by the UPF to generate an identifier of the 5GS node that is provided to the DetNet controller. NOTE 2: The 5GS node identification can be realized by providing an identifier of the 5GS node to the DetNet controller, or the TSCTSF can use different termination points (addresses) for the signalling between the DetNet controller and the TSCTSF. For network side ports, the information is transferred in PMIC between the NW-TT and the TSCTSF. For device side ports, the information is transferred without relying on PMIC, using parameters from the SMF via the PCF to the TSCTSF. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.28.5.2 |
3,841 | 9.5.15b Request Secondary PDP Context Activation Reject | This message is sent by the MS to the network to reject the request of a secondary PDP context activation. See table 9.5.15b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: request SECONDARY PDP context ACTIVATION reject Significance: global Direction: MS to network Table 9.5.15b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : request SECONDARY PDP context ACTIVATION reject 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.5.15b |
3,842 | 7.6.2.1A Minimum requirements for CA | For inter-band carrier aggregation with one component carrier per operating band and the uplink assigned to one E-UTRA band, the out-of-band blocking requirements are defined with the uplink active on the band(s) other than the band whose downlink is being tested. The throughput in the downlink measured shall be ≥ 95% of the maximum throughput of the reference measurement channels as specified in Annexes A.2.2, A.2.3 and A.3.2 (with one sided dynamic OCNG Pattern OP.1 FDD/TDD for the DL-signal as described in Annex A.5.1.1/A.5.2.1) with parameters specified in Tables 7.6.2.1-1 and 7.6.2.1A-0. For E-UTRA CA configurations including an operating band without uplink operation (as noted in Table 5.5-1), the requirements for all downlinks shall be met with the uplink active in the band(s) capable of UL operation. For the E-UTRA CA configurations with band 46 or Band 49, the parameters specified in Table 7.6.2.1A-0 are replaced by those specified in Table 7.6.2.1A-0a. The UE shall meet these requirements for each component carrier while all downlink carriers are active. For inter-band carrier aggregation with one component carrier per operating band and the uplink active in two E-UTRA bands, the out-of-band blocking requirements specified above shall be met with the transmitter power for the uplink set to 7 dB below PCMAX_L,c for each serving cell c. For E-UTRA CA configurations including an operating band without uplink band or an operating band with an unpaired DL part (as noted in Table 5.5-1), the requirements for all downlinks shall be met with the single uplink carrier active in each band capable of UL operation. For E-UTRA CA configurations listed in Table 7.3.1A-0a under conditions for which reference sensitivity for the operating band being tested is N/A, the out-of-band blocking requirements of subclause 7.6.2.1A do not apply. Table 7.6.2.1A-0: out-of-band blocking for inter-band carrier aggregation Table 7.6.2.1A-0a: out-of-band blocking for inter-band carrier aggregation with band 46 or Band 49 and with one active uplink For Table 7.6.2.1A-0 and Table 7.6.2.1A-0b in frequency ranges 1, 2 and 3, up to exceptions per downlink are allowed for spurious response frequencies for one active uplink when measured using a step size of 1 MHz. For Table 7.6.2.1A-0 in frequency ranges 1, 2 and 3, up to 2∙ exceptions per downlink are allowed for spurious response frequencies for two active uplinks when measured using a step size of 1 MHz. For these exceptions the requirements in clause 7.7.1A apply. For intra-band contiguous carrier aggreagations the downlink SCC(s) shall be configured at nominal channel spacing to the PCC. For FDD, the PCC shall be configured closest to the uplink band. All downlink carriers shall be active throughout the test. The uplink output power shall be set as specified in Table .1A-1 with the uplink configuration set according to Table 7.-1 for the applicable carrier aggregation configuration. For UE(s) supporting one uplink carrier, the uplink configuration of the PCC shall be in accordance with Table 7.3.1-2. The UE shall fulfil the minimum requirement in presence of an interfering signal specified in Tables .1A-1 and Tables 7.6.-2 being on either side of the aggregated signal. The throughput of each carrier shall be ≥ 95% of the maximum throughput of the reference measurement channels as specified in Annexes , A.2.3 and A.3.2 (with one sided dynamic OCNG Pattern OP.1 FDD/TDD for the DL-signal as described in Annex /A.5.2.1) with parameters specified in Tables 7.6.2.1A-1 and 7.6.2.1A-2. For operating bands with an unpaired DL part (as noted in Table 5.5-1), the requirements also apply for an SCC assigned in the unpaired part with parameters specified in Tables 7.6.2.1A-1 and 7.6.2.1A-2. For Table .1A frequency range 1, 2 and 3, up to exceptions are allowed for spurious response frequencies in each assigned frequency channel when measured using a 1MHz step size. For these exceptions the requirements of subclause 7.7 Spurious response are applicable. Table .1A-1: Out-of-band blocking parameters Table .1A-2: Out of band blocking For intra-band non-contiguous carrier aggregation with one uplink carrier and two or more downlink sub-blocks, the out-of-band blocking requirements are defined with the uplink configuration in accordance with table 7.3.1A-3. For this uplink configuration, the UE shall meet the requirements for each sub-block as specified in subclauses 7.6.2.1 and 7.6.2.1A for one component carrier and two or more component carriers per sub-block, respectively. The requirements apply with all downlink carriers active. For Table 7.6.2.1-2 in frequency range 1, 2 and 3, up to exceptions per assigned E-UTRA channel per sub-block of the E-UTRA CA configuration are allowed for spurious response frequencies for one active uplink when measured using a 1MHz step size. For these exceptions the requirements of subclause 7.7 spurious response are applicable. For Table 7.6.2.1-2 in frequency range 4, up to exceptions per assigned E-UTRA channel per sub-block of the E-UTRA CA configuration are allowed for spurious response frequencies for one active uplink when measured using a 1MHz step size. For these exceptions the requirements of clause 7.7 spurious response are applicable. For intra-band non-contiguous carrier aggregation with two uplink carriers and two or more downlink carriers, the out-of-band blocking requirements are defined with the uplink configuration of the PCC and SCC being in accordance with Table 7.3.1A-4 and powers of both carriers set to PCMAX_L,c – 7 dBm. The UE shall meet the requirements specified in subclause 7.6.2.1 for each component carrier while both downlink carriers are active. For Table 7.6.2.1-2 in frequency range 1, 2 and 3, up to 2∙ exceptions per assigned E-UTRA channel per sub-block of the E-UTRA CA configuration are allowed for spurious response frequencies for two active uplinks in the same operating band when measured using a 1MHz step size. For these exceptions the requirements of subclause 7.7 spurious response are applicable. For Table 7.6.2.1-2 in frequency range 4, up to 2∙ exceptions per assigned E-UTRA channel per sub-block of the E-UTRA CA configuration are allowed for spurious response frequencies for two active uplinks in the same operating band when measured using a 1MHz step size. For these exceptions the requirements of clause 7.7 spurious response are applicable. For combinations of intra-band and inter-band carrier aggregation and the uplink assigned to one E-UTRA band, the requirement is defined with the uplink active in a band other than that supporting the downlink(s) under test. The uplink configuration shall be in accordance with Table 7.3.1A-3 when the uplink is active in the band supporting two or more non-contiguous component carriers, Table 7.3.1A-1 when the uplink is active in a band supporting two contiguous component carriers and in accordance with Table 7.3.1-2 when the uplink is active in a band supporting one carrier per band. The downlink PCC shall be configured closer to the uplink operating band than the downlink SCC(s) when the uplink is active in band(s) supporting contiguous aggregation. For the two or more non-contiguous component carriers within the same band, Pwanted in Table 7.6.2.1A-0 is set using RIBNC = 0 dB for all sub-block gaps (Table 7.3.1A-3) while a band supporting contiguously aggregated carriers the out-of-band blocking parameters in Table 7.6.2.1-1 are replaced by those specified in Table 7.6.2.1A-1. For each downlink the UE shall meet the out-of-band blocking requirements applicable for inter-band carrier aggregation with one component carrier per operating band with the following exception. For each component carrier of the E-UTRA CA Configurations with band 46 or band 49, the requirements specified in Table 7.6.2.1A-0 are replaced by those in Table 7.6.2.1A-0a. All downlink carriers shall be active throughout the tests and the requirements for the downlinks shall be met with the single uplink carrier active in each band capable of UL operation. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 7.6.2.1A |
3,843 | 5.6.1.6A Service request procedure for an emergency services fallback not accepted by the network | If the service request for initiating an emergency services fallback cannot be accepted by the network, the UE shall perform the procedures as described in subclause 5.6.1.5, if the service request for initiating an emergency services fallback fails due to receiving the AUTHENTICATION REJECT message, the UE shall perform the procedures as described in subclauses 5.4.1.2.2.11, 5.4.1.2.3.1, 5.4.1.2.3A.1 or 5.4.1.3.5, and if the UE does not attempt to select an E-UTRA cell connected to EPC or 5GCN as described in subclause 5.6.1.5 and is camped on NR or E-UTRA cell connected to 5GCN in the same PLMN where the last service request was attempted, the UE shall inform the upper layers of the failure of the procedure. NOTE 1: This can result in the upper layers requesting another emergency call attempt using domain selection as specified in 3GPP TS 23.167[ IP Multimedia Subsystem (IMS) emergency sessions ] [6]. If the service request for initiating an emergency services fallback fails due to abnormal cases a) in subclause 5.6.1.7, the UE shall inform the upper layers of the failure of the emergency services fallback. NOTE 2: This can result in the upper layers requesting another emergency call attempt using domain selection as specified in 3GPP TS 23.167[ IP Multimedia Subsystem (IMS) emergency sessions ] [6]. If the service request procedure for initiating an emergency services fallback fails due to abnormal cases other than a) in subclause 5.6.1.7, the UE may abort the service request procedure, if not aborted already and attempt to select an E-UTRA cell connected to EPC or 5GCN according to the domain priority and selection rules specified in 3GPP TS 23.167[ IP Multimedia Subsystem (IMS) emergency sessions ] [6]. If the UE finds a suitable E-UTRA cell, it then proceeds with the appropriate EMM or 5GMM procedures. If the UE operating in single-registration mode has changed to S1 mode, it shall disable the N1 mode capability for 3GPP access. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.6.1.6A |
3,844 | – Phy-Parameters | The IE Phy-Parameters is used to convey the physical layer capabilities. Phy-Parameters information element -- ASN1START -- TAG-PHY-PARAMETERS-START Phy-Parameters ::= SEQUENCE { phy-ParametersCommon Phy-ParametersCommon OPTIONAL, phy-ParametersXDD-Diff Phy-ParametersXDD-Diff OPTIONAL, phy-ParametersFRX-Diff Phy-ParametersFRX-Diff OPTIONAL, phy-ParametersFR1 Phy-ParametersFR1 OPTIONAL, phy-ParametersFR2 Phy-ParametersFR2 OPTIONAL } Phy-Parameters-v16a0 ::= SEQUENCE { phy-ParametersCommon-v16a0 Phy-ParametersCommon-v16a0 OPTIONAL } Phy-ParametersCommon ::= SEQUENCE { csi-RS-CFRA-ForHO ENUMERATED {supported} OPTIONAL, dynamicPRB-BundlingDL ENUMERATED {supported} OPTIONAL, sp-CSI-ReportPUCCH ENUMERATED {supported} OPTIONAL, sp-CSI-ReportPUSCH ENUMERATED {supported} OPTIONAL, nzp-CSI-RS-IntefMgmt ENUMERATED {supported} OPTIONAL, type2-SP-CSI-Feedback-LongPUCCH ENUMERATED {supported} OPTIONAL, precoderGranularityCORESET ENUMERATED {supported} OPTIONAL, dynamicHARQ-ACK-Codebook ENUMERATED {supported} OPTIONAL, semiStaticHARQ-ACK-Codebook ENUMERATED {supported} OPTIONAL, spatialBundlingHARQ-ACK ENUMERATED {supported} OPTIONAL, dynamicBetaOffsetInd-HARQ-ACK-CSI ENUMERATED {supported} OPTIONAL, pucch-Repetition-F1-3-4 ENUMERATED {supported} OPTIONAL, ra-Type0-PUSCH ENUMERATED {supported} OPTIONAL, dynamicSwitchRA-Type0-1-PDSCH ENUMERATED {supported} OPTIONAL, dynamicSwitchRA-Type0-1-PUSCH ENUMERATED {supported} OPTIONAL, pdsch-MappingTypeA ENUMERATED {supported} OPTIONAL, pdsch-MappingTypeB ENUMERATED {supported} OPTIONAL, interleavingVRB-ToPRB-PDSCH ENUMERATED {supported} OPTIONAL, interSlotFreqHopping-PUSCH ENUMERATED {supported} OPTIONAL, type1-PUSCH-RepetitionMultiSlots ENUMERATED {supported} OPTIONAL, type2-PUSCH-RepetitionMultiSlots ENUMERATED {supported} OPTIONAL, pusch-RepetitionMultiSlots ENUMERATED {supported} OPTIONAL, pdsch-RepetitionMultiSlots ENUMERATED {supported} OPTIONAL, downlinkSPS ENUMERATED {supported} OPTIONAL, configuredUL-GrantType1 ENUMERATED {supported} OPTIONAL, configuredUL-GrantType2 ENUMERATED {supported} OPTIONAL, pre-EmptIndication-DL ENUMERATED {supported} OPTIONAL, cbg-TransIndication-DL ENUMERATED {supported} OPTIONAL, cbg-TransIndication-UL ENUMERATED {supported} OPTIONAL, cbg-FlushIndication-DL ENUMERATED {supported} OPTIONAL, dynamicHARQ-ACK-CodeB-CBG-Retx-DL ENUMERATED {supported} OPTIONAL, rateMatchingResrcSetSemi-Static ENUMERATED {supported} OPTIONAL, rateMatchingResrcSetDynamic ENUMERATED {supported} OPTIONAL, bwp-SwitchingDelay ENUMERATED {type1, type2} OPTIONAL, ..., [[ dummy ENUMERATED {supported} OPTIONAL ]], [[ maxNumberSearchSpaces ENUMERATED {n10} OPTIONAL, rateMatchingCtrlResrcSetDynamic ENUMERATED {supported} OPTIONAL, maxLayersMIMO-Indication ENUMERATED {supported} OPTIONAL ]], [[ spCellPlacement CarrierAggregationVariant OPTIONAL ]], [[ -- R1 9-1: Basic channel structure and procedure of 2-step RACH twoStepRACH-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-1: Monitoring DCI format 1_2 and DCI format 0_2 dci-Format1-2And0-2-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-1a: Monitoring both DCI format 0_1/1_1 and DCI format 0_2/1_2 in the same search space monitoringDCI-SameSearchSpace-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-10: Type 2 configured grant release by DCI format 0_1 type2-CG-ReleaseDCI-0-1-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-11: Type 2 configured grant release by DCI format 0_2 type2-CG-ReleaseDCI-0-2-r16 ENUMERATED {supported} OPTIONAL, -- R1 12-3: SPS release by DCI format 1_1 sps-ReleaseDCI-1-1-r16 ENUMERATED {supported} OPTIONAL, -- R1 12-3a: SPS release by DCI format 1_2 sps-ReleaseDCI-1-2-r16 ENUMERATED {supported} OPTIONAL, -- R1 14-8: CSI trigger states containing non-active BWP csi-TriggerStateNon-ActiveBWP-r16 ENUMERATED {supported} OPTIONAL, -- R1 20-2: Support up to 4 SMTCs configured for an IAB node MT per frequency location, including IAB-specific SMTC window periodicities separateSMTC-InterIAB-Support-r16 ENUMERATED {supported} OPTIONAL, -- R1 20-3: Support RACH configuration separately from the RACH configuration for UE access, including new IAB-specific offset and scaling factors separateRACH-IAB-Support-r16 ENUMERATED {supported} OPTIONAL, -- R1 20-5a: Support semi-static configuration/indication of UL-Flexible-DL slot formats for IAB-MT resources ul-flexibleDL-SlotFormatSemiStatic-IAB-r16 ENUMERATED {supported} OPTIONAL, -- R1 20-5b: Support dynamic indication of UL-Flexible-DL slot formats for IAB-MT resources ul-flexibleDL-SlotFormatDynamics-IAB-r16 ENUMERATED {supported} OPTIONAL, dft-S-OFDM-WaveformUL-IAB-r16 ENUMERATED {supported} OPTIONAL, -- R1 20-6: Support DCI Format 2_5 based indication of soft resource availability to an IAB node dci-25-AI-RNTI-Support-IAB-r16 ENUMERATED {supported} OPTIONAL, -- R1 20-7: Support T_delta reception. t-DeltaReceptionSupport-IAB-r16 ENUMERATED {supported} OPTIONAL, -- R1 20-8: Support of Desired guard symbol reporting and provided guard symbok reception. guardSymbolReportReception-IAB-r16 ENUMERATED {supported} OPTIONAL, -- R1 18-8 HARQ-ACK codebook type and spatial bundling per PUCCH group harqACK-CB-SpatialBundlingPUCCH-Group-r16 ENUMERATED {supported} OPTIONAL, -- R1 19-2: Cross Slot Scheduling crossSlotScheduling-r16 SEQUENCE { non-SharedSpectrumChAccess-r16 ENUMERATED {supported} OPTIONAL, sharedSpectrumChAccess-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL, maxNumberSRS-PosPathLossEstimateAllServingCells-r16 ENUMERATED {n1, n4, n8, n16} OPTIONAL, extendedCG-Periodicities-r16 ENUMERATED {supported} OPTIONAL, extendedSPS-Periodicities-r16 ENUMERATED {supported} OPTIONAL, codebookVariantsList-r16 CodebookVariantsList-r16 OPTIONAL, -- R1 11-6: PUSCH repetition Type A pusch-RepetitionTypeA-r16 SEQUENCE { sharedSpectrumChAccess-r16 ENUMERATED {supported} OPTIONAL, non-SharedSpectrumChAccess-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL, -- R1 11-4b: DL priority indication in DCI with mixed DCI formats dci-DL-PriorityIndicator-r16 ENUMERATED {supported} OPTIONAL, -- R1 12-1a: UL priority indication in DCI with mixed DCI formats dci-UL-PriorityIndicator-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-1e: Maximum number of configured pathloss reference RSs for PUSCH/PUCCH/SRS by RRC for MAC-CE based pathloss reference RS update maxNumberPathlossRS-Update-r16 ENUMERATED {n4, n8, n16, n32, n64} OPTIONAL, -- R1 18-9: Usage of the PDSCH starting time for HARQ-ACK type 2 codebook type2-HARQ-ACK-Codebook-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-1g-1: Resources for beam management, pathloss measurement, BFD, RLM and new beam identification across frequency ranges maxTotalResourcesForAcrossFreqRanges-r16 SEQUENCE { maxNumberResWithinSlotAcrossCC-AcrossFR-r16 ENUMERATED {n2, n4, n8, n12, n16, n32, n64, n128} OPTIONAL, maxNumberResAcrossCC-AcrossFR-r16 ENUMERATED {n2, n4, n8, n12, n16, n32, n40, n48, n64, n72, n80, n96, n128, n256} OPTIONAL } OPTIONAL, -- R1 16-2a-4: HARQ-ACK for multi-DCI based multi-TRP - separate harqACK-separateMultiDCI-MultiTRP-r16 SEQUENCE { maxNumberLongPUCCHs-r16 ENUMERATED {longAndLong, longAndShort, shortAndShort} OPTIONAL } OPTIONAL, -- R1 16-2a-4: HARQ-ACK for multi-DCI based multi-TRP - joint harqACK-jointMultiDCI-MultiTRP-r16 ENUMERATED {supported} OPTIONAL, -- R4 9-1: BWP switching on multiple CCs RRM requirements bwp-SwitchingMultiCCs-r16 CHOICE { type1-r16 ENUMERATED {us100, us200}, type2-r16 ENUMERATED {us200, us400, us800, us1000} } OPTIONAL ]], [[ targetSMTC-SCG-r16 ENUMERATED {supported} OPTIONAL, supportRepetitionZeroOffsetRV-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-12: in-order CBG-based re-transmission cbg-TransInOrderPUSCH-UL-r16 ENUMERATED {supported} OPTIONAL ]], [[ -- R4 6-3: Dormant BWP switching on multiple CCs RRM requirements bwp-SwitchingMultiDormancyCCs-r16 CHOICE { type1-r16 ENUMERATED {us100, us200}, type2-r16 ENUMERATED {us200, us400, us800, us1000} } OPTIONAL, -- R1 16-2a-8: Indicates that retransmission scheduled by a different CORESETPoolIndex for multi-DCI multi-TRP is not supported. supportRetx-Diff-CoresetPool-Multi-DCI-TRP-r16 ENUMERATED {notSupported} OPTIONAL, -- R1 22-10: Support of pdcch-MonitoringAnyOccasionsWithSpanGap in case of cross-carrier scheduling with different SCSs pdcch-MonitoringAnyOccasionsWithSpanGapCrossCarrierSch-r16 ENUMERATED {mode2, mode3} OPTIONAL ]], [[ -- R1 16-1j-1: Support of 2 port CSI-RS for new beam identification newBeamIdentifications2PortCSI-RS-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-1j-2: Support of 2 port CSI-RS for pathloss estimation pathlossEstimation2PortCSI-RS-r16 ENUMERATED {supported} OPTIONAL ]], [[ mux-HARQ-ACK-withoutPUCCH-onPUSCH-r16 ENUMERATED {supported} OPTIONAL ]], [[ -- R1 31-1: Support of Desired Guard Symbol reporting and provided guard symbol reception. guardSymbolReportReception-IAB-r17 ENUMERATED {supported} OPTIONAL, -- R1 31-2: support of restricted IAB-DU beam reception restricted-IAB-DU-BeamReception-r17 ENUMERATED {supported} OPTIONAL, -- R1 31-3: support of recommended IAB-MT beam transmission for DL and UL beam recommended-IAB-MT-BeamTransmission-r17 ENUMERATED {supported} OPTIONAL, -- R1 31-4: support of case 6 timing alignment indication reception case6-TimingAlignmentReception-IAB-r17 ENUMERATED {supported} OPTIONAL, -- R1 31-5: support of case 7 timing offset indication reception and case 7 timing at parent-node indication reception case7-TimingAlignmentReception-IAB-r17 ENUMERATED {supported} OPTIONAL, -- R1 31-6: support of desired DL Tx power adjustment reporting and DL Tx power adjustment reception dl-tx-PowerAdjustment-IAB-r17 ENUMERATED {supported} OPTIONAL, -- R1 31-7: support of desired IAB-MT PSD range reporting desired-ul-tx-PowerAdjustment-r17 ENUMERATED {supported} OPTIONAL, -- R1 31-8: support of monitoring DCI Format 2_5 scrambled by AI-RNTI for indication of FDM soft resource availability to an IAB node fdm-SoftResourceAvailability-DynamicIndication-r17 ENUMERATED{supported} OPTIONAL, -- R1 31-10: Support of updated T_delta range reception updated-T-DeltaRangeReception-r17 ENUMERATED{supported} OPTIONAL, -- R1 30-5: Support slot based dynamic PUCCH repetition indication for PUCCH formats 0/1/2/3/4 slotBasedDynamicPUCCH-Rep-r17 ENUMERATED {supported} OPTIONAL, -- R1 25-1: Support of HARQ-ACK deferral in case of TDD collision sps-HARQ-ACK-Deferral-r17 SEQUENCE { non-SharedSpectrumChAccess-r17 ENUMERATED {supported} OPTIONAL, sharedSpectrumChAccess-r17 ENUMERATED {supported} OPTIONAL } OPTIONAL, -- R1 23-1-1k Maximum number of configured CC lists (per UE) unifiedJointTCI-commonUpdate-r17 INTEGER (1..4) OPTIONAL, -- R1 23-2-1c PDCCH repetition with a single span of three contiguous OFDM symbols that is within the first four OFDM symbols in a slot mTRP-PDCCH-singleSpan-r17 ENUMERATED {supported} OPTIONAL, -- R1 27-23: Support of more than one activated PRS processing windows across all active DL BWPs supportedActivatedPRS-ProcessingWindow-r17 ENUMERATED {n2, n3, n4} OPTIONAL, cg-TimeDomainAllocationExtension-r17 ENUMERATED {supported} OPTIONAL ]], [[ -- R1 25-20: Propagation delay compensation based on Rel-15 TA procedure for TN and licensed ta-BasedPDC-TN-NonSharedSpectrumChAccess-r17 ENUMERATED {supported} OPTIONAL, -- R1 31-11: Directional Collision Handling in DC operation directionalCollisionDC-IAB-r17 ENUMERATED {supported} OPTIONAL ]], [[ dummy1 ENUMERATED {supported} OPTIONAL, dummy2 ENUMERATED {supported} OPTIONAL, dummy3 ENUMERATED {supported} OPTIONAL, dummy4 ENUMERATED {supported} OPTIONAL, srs-AdditionalRepetition-r17 ENUMERATED {supported} OPTIONAL, pusch-Repetition-CG-SDT-r17 ENUMERATED {supported} OPTIONAL ]], [[ multiPDSCH-PerSlotType1-CB-Support-r17 ENUMERATED {supported} OPTIONAL ]], [[ supportedCSI-RS-ReportSettingList-r18 SupportedCSI-RS-ReportSettingList-r18 OPTIONAL, -- R1 43-3: Aperiodic beam indication for access link ncr-AperiodicBeamInd-AccessLink-r18 SEQUENCE { scs-15kHz-r18 INTEGER (0..1) OPTIONAL, scs-30kHz-r18 INTEGER (0..1) OPTIONAL, scs-60kHz-r18 INTEGER (0..2) OPTIONAL, scs-120kHz-r18 INTEGER (0..2) OPTIONAL } OPTIONAL, -- R1 43-4: Semi-persistent beam indication for access link ncr-Semi-PersistentBeamInd-AccessLink-r18 ENUMERATED {supported} OPTIONAL, -- R1 43-5: Simulatenous UL transmission of backhaul link and C-Link ncr-SimultaneousUL-BackhaulAndC-Link-r18 ENUMERATED {supported} OPTIONAL, -- R1 43-6: Dedicated signalling for backhaul link beam indication ncr-BackhaulBeamInd-r18 ENUMERATED {nonUnifiedTCI, unifiedTCI, both} OPTIONAL, -- R1 43-8: Adaptive beam for NCR backhaul link/C-link ncr-AdaptiveBeamBackhaulAndC-Link-r18 ENUMERATED {nonUnifiedTCI, unifiedTCI, both} OPTIONAL, -- R1 49-4a: Nominal RBG size of Configuration 3 for FDRA type 0 for DCI format 1_3 nominalRBG-SizeOfConfig-3-FDRA-Type-0-DCI-1-3-r18 ENUMERATED {supported} OPTIONAL, -- R1 49-4b: Nominal RBG size of Configuration 3 for FDRA type 0 for DCI format 0_3 nominalRBG-SizeOfConfig-3-FDRA-Type-0-DCI-0-3-r18 ENUMERATED {supported} OPTIONAL, -- R1 49-4c: Configurable Type-1A fields for DCI format 0_3/1_3 configurableType-1A-FieldsForDCI-0-3-And-1-3-r18 ENUMERATED {supported} OPTIONAL, -- R1 49-4d: FDRA Type 1 granularity of 2, 4, 8, or 16 consecutive RBs based RIV for DCI format 1_3/0_3 fdra-Type-1-Gty-2-4-8-16-RBs-RIV-DCI-1-3-And-0-3-r18 ENUMERATED {supported} OPTIONAL, -- R1 51-3: Support 5 MHz channel bandwidth with 20 PRB CORESET0 support-5MHz-ChannelBW-20PRB-CORESET0-r18 ENUMERATED {supported} OPTIONAL, -- R1 55-1: Additional SR periodicities additionalSR-Periodicities-r18 SEQUENCE { scs-30kHz-r18 ENUMERATED {supported} OPTIONAL, scs-120kHz-r18 ENUMERATED {supported} OPTIONAL } OPTIONAL, -- R1 55-5: Enable MAC CE based pathloss RS updates for Type 1 CG-PUSCH pathlossRS-UpdateForType1CG-PUSCH-r18 ENUMERATED {supported} OPTIONAL ]] } Phy-ParametersCommon-v16a0 ::= SEQUENCE { srs-PeriodicityAndOffsetExt-r16 ENUMERATED {supported} OPTIONAL } Phy-ParametersXDD-Diff ::= SEQUENCE { dynamicSFI ENUMERATED {supported} OPTIONAL, twoPUCCH-F0-2-ConsecSymbols ENUMERATED {supported} OPTIONAL, twoDifferentTPC-Loop-PUSCH ENUMERATED {supported} OPTIONAL, twoDifferentTPC-Loop-PUCCH ENUMERATED {supported} OPTIONAL, ..., [[ dl-SchedulingOffset-PDSCH-TypeA ENUMERATED {supported} OPTIONAL, dl-SchedulingOffset-PDSCH-TypeB ENUMERATED {supported} OPTIONAL, ul-SchedulingOffset ENUMERATED {supported} OPTIONAL ]] } Phy-ParametersFRX-Diff ::= SEQUENCE { dynamicSFI ENUMERATED {supported} OPTIONAL, dummy1 BIT STRING (SIZE (2)) OPTIONAL, twoFL-DMRS BIT STRING (SIZE (2)) OPTIONAL, dummy2 BIT STRING (SIZE (2)) OPTIONAL, dummy3 BIT STRING (SIZE (2)) OPTIONAL, supportedDMRS-TypeDL ENUMERATED {type1, type1And2} OPTIONAL, supportedDMRS-TypeUL ENUMERATED {type1, type1And2} OPTIONAL, semiOpenLoopCSI ENUMERATED {supported} OPTIONAL, csi-ReportWithoutPMI ENUMERATED {supported} OPTIONAL, csi-ReportWithoutCQI ENUMERATED {supported} OPTIONAL, onePortsPTRS BIT STRING (SIZE (2)) OPTIONAL, twoPUCCH-F0-2-ConsecSymbols ENUMERATED {supported} OPTIONAL, pucch-F2-WithFH ENUMERATED {supported} OPTIONAL, pucch-F3-WithFH ENUMERATED {supported} OPTIONAL, pucch-F4-WithFH ENUMERATED {supported} OPTIONAL, pucch-F0-2WithoutFH ENUMERATED {notSupported} OPTIONAL, pucch-F1-3-4WithoutFH ENUMERATED {notSupported} OPTIONAL, mux-SR-HARQ-ACK-CSI-PUCCH-MultiPerSlot ENUMERATED {supported} OPTIONAL, uci-CodeBlockSegmentation ENUMERATED {supported} OPTIONAL, onePUCCH-LongAndShortFormat ENUMERATED {supported} OPTIONAL, twoPUCCH-AnyOthersInSlot ENUMERATED {supported} OPTIONAL, intraSlotFreqHopping-PUSCH ENUMERATED {supported} OPTIONAL, pusch-LBRM ENUMERATED {supported} OPTIONAL, pdcch-BlindDetectionCA INTEGER (4..16) OPTIONAL, tpc-PUSCH-RNTI ENUMERATED {supported} OPTIONAL, tpc-PUCCH-RNTI ENUMERATED {supported} OPTIONAL, tpc-SRS-RNTI ENUMERATED {supported} OPTIONAL, absoluteTPC-Command ENUMERATED {supported} OPTIONAL, twoDifferentTPC-Loop-PUSCH ENUMERATED {supported} OPTIONAL, twoDifferentTPC-Loop-PUCCH ENUMERATED {supported} OPTIONAL, pusch-HalfPi-BPSK ENUMERATED {supported} OPTIONAL, pucch-F3-4-HalfPi-BPSK ENUMERATED {supported} OPTIONAL, almostContiguousCP-OFDM-UL ENUMERATED {supported} OPTIONAL, sp-CSI-RS ENUMERATED {supported} OPTIONAL, sp-CSI-IM ENUMERATED {supported} OPTIONAL, tdd-MultiDL-UL-SwitchPerSlot ENUMERATED {supported} OPTIONAL, multipleCORESET ENUMERATED {supported} OPTIONAL, ..., [[ csi-RS-IM-ReceptionForFeedback CSI-RS-IM-ReceptionForFeedback OPTIONAL, csi-RS-ProcFrameworkForSRS CSI-RS-ProcFrameworkForSRS OPTIONAL, csi-ReportFramework CSI-ReportFramework OPTIONAL, mux-SR-HARQ-ACK-CSI-PUCCH-OncePerSlot SEQUENCE { sameSymbol ENUMERATED {supported} OPTIONAL, diffSymbol ENUMERATED {supported} OPTIONAL } OPTIONAL, mux-SR-HARQ-ACK-PUCCH ENUMERATED {supported} OPTIONAL, mux-MultipleGroupCtrlCH-Overlap ENUMERATED {supported} OPTIONAL, dl-SchedulingOffset-PDSCH-TypeA ENUMERATED {supported} OPTIONAL, dl-SchedulingOffset-PDSCH-TypeB ENUMERATED {supported} OPTIONAL, ul-SchedulingOffset ENUMERATED {supported} OPTIONAL, dl-64QAM-MCS-TableAlt ENUMERATED {supported} OPTIONAL, ul-64QAM-MCS-TableAlt ENUMERATED {supported} OPTIONAL, cqi-TableAlt ENUMERATED {supported} OPTIONAL, oneFL-DMRS-TwoAdditionalDMRS-UL ENUMERATED {supported} OPTIONAL, twoFL-DMRS-TwoAdditionalDMRS-UL ENUMERATED {supported} OPTIONAL, oneFL-DMRS-ThreeAdditionalDMRS-UL ENUMERATED {supported} OPTIONAL ]], [[ pdcch-BlindDetectionNRDC SEQUENCE { pdcch-BlindDetectionMCG-UE INTEGER (1..15), pdcch-BlindDetectionSCG-UE INTEGER (1..15) } OPTIONAL, mux-HARQ-ACK-PUSCH-DiffSymbol ENUMERATED {supported} OPTIONAL ]], [[ -- R1 11-1b: Type 1 HARQ-ACK codebook support for relative TDRA for DL type1-HARQ-ACK-Codebook-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-8: Enhanced UL power control scheme enhancedPowerControl-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-1b-1: TCI state activation across multiple CCs simultaneousTCI-ActMultipleCC-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-1b-2: Spatial relation update across multiple CCs simultaneousSpatialRelationMultipleCC-r16 ENUMERATED {supported} OPTIONAL, cli-RSSI-FDM-DL-r16 ENUMERATED {supported} OPTIONAL, cli-SRS-RSRP-FDM-DL-r16 ENUMERATED {supported} OPTIONAL, -- R1 19-3: Maximum MIMO Layer Adaptation maxLayersMIMO-Adaptation-r16 ENUMERATED {supported} OPTIONAL, -- R1 12-5: Configuration of aggregation factor per SPS configuration aggregationFactorSPS-DL-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-1g: Resources for beam management, pathloss measurement, BFD, RLM and new beam identification maxTotalResourcesForOneFreqRange-r16 SEQUENCE { maxNumberResWithinSlotAcrossCC-OneFR-r16 ENUMERATED {n2, n4, n8, n12, n16, n32, n64, n128} OPTIONAL, maxNumberResAcrossCC-OneFR-r16 ENUMERATED {n2, n4, n8, n12, n16, n32, n40, n48, n64, n72, n80, n96, n128, n256} OPTIONAL } OPTIONAL, -- R1 16-7: Extension of the maximum number of configured aperiodic CSI report settings csi-ReportFrameworkExt-r16 CSI-ReportFrameworkExt-r16 OPTIONAL ]], [[ twoTCI-Act-servingCellInCC-List-r16 ENUMERATED {supported} OPTIONAL ]], [[ -- R1 22-11: Support of 'cri-RI-CQI' report without non-PMI-PortIndication cri-RI-CQI-WithoutNon-PMI-PortInd-r16 ENUMERATED {supported} OPTIONAL ]], [[ -- R1 25-11: 4-bits subband CQI for TN and licensed cqi-4-BitsSubbandTN-NonSharedSpectrumChAccess-r17 ENUMERATED {supported} OPTIONAL ]], [[ multipleCORESET-RedCap-r17 ENUMERATED {supported} OPTIONAL ]] } Phy-ParametersFR1 ::= SEQUENCE { pdcch-MonitoringSingleOccasion ENUMERATED {supported} OPTIONAL, scs-60kHz ENUMERATED {supported} OPTIONAL, pdsch-256QAM-FR1 ENUMERATED {supported} OPTIONAL, pdsch-RE-MappingFR1-PerSymbol ENUMERATED {n10, n20} OPTIONAL, ..., [[ pdsch-RE-MappingFR1-PerSlot ENUMERATED {n16, n32, n48, n64, n80, n96, n112, n128, n144, n160, n176, n192, n208, n224, n240, n256} OPTIONAL ]], [[ -- R1 22-12: PDCCH monitoring with a single span of three contiguous OFDM symbols that is within the first four OFDM symbols in a -- slot pdcch-MonitoringSingleSpanFirst4Sym-r16 ENUMERATED {supported} OPTIONAL ]], [[ -- similar to NTN R1 26-10: K1 range extension defined for ATG as well k1-RangeExtensionATG-r18 ENUMERATED {supported} OPTIONAL, -- similar to NTN R1 26-5: Increasing the number of HARQ processes defined for ATG as well maxHARQ-ProcessNumberATG-r18 ENUMERATED {u16d32, u32d16, u32d32} OPTIONAL, -- similar to NTN R1 26-1: Uplink Time and Frequency pre-compensation and timing relationship enhancements defined for ATG as well uplinkPreCompensationATG-r18 ENUMERATED {supported} OPTIONAL ]] } Phy-ParametersFR2 ::= SEQUENCE { dummy ENUMERATED {supported} OPTIONAL, pdsch-RE-MappingFR2-PerSymbol ENUMERATED {n6, n20} OPTIONAL, ..., [[ pCell-FR2 ENUMERATED {supported} OPTIONAL, pdsch-RE-MappingFR2-PerSlot ENUMERATED {n16, n32, n48, n64, n80, n96, n112, n128, n144, n160, n176, n192, n208, n224, n240, n256} OPTIONAL ]], [[ -- R1 16-1c: Support of default spatial relation and pathloss reference RS for dedicated-PUCCH/SRS and PUSCH defaultSpatialRelationPathlossRS-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-1d: Support of spatial relation update for AP-SRS via MAC CE spatialRelationUpdateAP-SRS-r16 ENUMERATED {supported} OPTIONAL, maxNumberSRS-PosSpatialRelationsAllServingCells-r16 ENUMERATED {n0, n1, n2, n4, n8, n16} OPTIONAL ]] } -- TAG-PHY-PARAMETERS-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,845 | 12.3.9.2.1 Description | An overloaded GTP-C entity shall ask its peers to reduce the number of requests they would ordinarily send by signalling Overload Control Information including the requested traffic reduction, as a percentage, within the "Overload-Reduction-Metric", as specified in clause 12.3.5.1.2.1. The recipients of the "Overload-Reduction-Metric" shall reduce the number of requests sent by that percentage, either by redirecting them to an alternate destination if possible (e.g. the Create Session Request message may be redirected to an alternate SGW/PGW), or by failing the request and treating it as if it was rejected by the destination GTP-C entity. For example, if a sender requests another peer to reduce the traffic it is sending by 10%, then that peer shall throttle 10% of the traffic that would have otherwise been sent to this GTP-C entity. The overloaded GTP-C entity should periodically adjust the requested traffic reduction based e.g. on the traffic reduction factor that is currently in use, the current system utilization (i.e. the overload level) and the desired system utilization (i.e. the target load level), and/or the rate of the current overall received traffic. Annex D.3.1 provides an (informative) example of a possible implementation of the "Loss" algorithm, amongst other possible methods. NOTE 1: This algorithm does not guarantee that the future traffic towards the overloaded GTP-C entity will be less than the past traffic but it ensures that the total traffic sent towards the overloaded GTP-C entity is less than what would have been sent without any throttling in place. If after requesting a certain reduction in traffic, the overloaded GTP-C entity receives more traffic than in the past, whilst still in overload, leading to the worsening rather than an improvement in the overload level, then the overloaded GTP-C entity can request for more reduction in traffic. Thus, by periodically adjusting the requested traffic reduction, the overloaded node can ensure that it receives, approximately, the amount of traffic which it can handle. NOTE 2: Since the reduction is requested as a percentage, and not as an absolute amount, this algorithm achieves a good useful throughput towards the overloaded node when the traffic conditions vary at the source nodes (depending upon the events generated towards these source nodes by other entities in the network), as a potential increase of traffic from some source nodes can possibly be compensated by a potential decrease of traffic from other source nodes. | 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 | 12.3.9.2.1 |
3,846 | 8.40 PDU Numbers | The PDU Numbers information element contains the sequence number status corresponding to a Bearer context in the old SGSN. This information element shall be sent only when acknowledged peer-to-peer LLC operation is used for the Bearer context or when the "delivery order" QoS attribute is set in the Bearer context QoS profile. NSAPI identifies the Bearer context for which the PDU Number IE is intended. DL GTP-U Sequence Number is the number for the next downlink GTP-U T-PDU to be sent to the UE when "delivery order" is set. UL GTP-U Sequence Number is the number for the next uplink GTP-U T-PDU to be tunnelled to the S-GW when "delivery order" is set. The Send N-PDU Number is used only when acknowledged peer-to-peer LLC operation is used for the Bearer context. Send N-PDU Number is the N-PDU number to be assigned by SNDCP to the next down link N-PDU received from the S-GW. The Receive N-PDU Number is used only when acknowledged peer-to-peer LLC operation is used for the Bearer context. The Receive N-PDU Number is the N-PDU number expected by SNDCP from the next up link N-PDU to be received from the UE. The PDU Number IE will be repeated for each Bearer Context for which this IE is required. PDU Numbers IE is coded as depicted in Figure 8.40-1. Figure 8.40-1: PDU Numbers | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 8.40 |
3,847 | – ControlResourceSet | The IE ControlResourceSet is used to configure a time/frequency control resource set (CORESET) in which to search for downlink control information (see TS 38.213[ NR; Physical layer procedures for control ] [13], clause 10.1). For the UE not supporting multipleCORESET in FR1, in order to receive MBS multicast in CFR within the UE's active BWP, if a CORESET is not configured within the PDCCH-ConfigMulticast, the CORESET other than CORESET#0 configured within the UE's active BWP for scheduling unicast can be used for scheduling MBS multicast, and the CORESET is expected to be included completely within the CFR and the parameters configured in the CORESET are expected to be supported by the UE for MBS multicast. ControlResourceSet information element -- ASN1START -- TAG-CONTROLRESOURCESET-START ControlResourceSet ::= SEQUENCE { controlResourceSetId ControlResourceSetId, frequencyDomainResources BIT STRING (SIZE (45)), duration INTEGER (1..maxCoReSetDuration), cce-REG-MappingType CHOICE { interleaved SEQUENCE { reg-BundleSize ENUMERATED {n2, n3, n6}, interleaverSize ENUMERATED {n2, n3, n6}, shiftIndex INTEGER(0..maxNrofPhysicalResourceBlocks-1) OPTIONAL -- Need S }, nonInterleaved NULL }, precoderGranularity ENUMERATED {sameAsREG-bundle, allContiguousRBs}, tci-StatesPDCCH-ToAddList SEQUENCE(SIZE (1..maxNrofTCI-StatesPDCCH)) OF TCI-StateId OPTIONAL, -- Cond NotSIB-initialBWP tci-StatesPDCCH-ToReleaseList SEQUENCE(SIZE (1..maxNrofTCI-StatesPDCCH)) OF TCI-StateId OPTIONAL, -- Cond NotSIB-initialBWP tci-PresentInDCI ENUMERATED {enabled} OPTIONAL, -- Need S pdcch-DMRS-ScramblingID INTEGER (0..65535) OPTIONAL, -- Need S ..., [[ rb-Offset-r16 INTEGER (0..5) OPTIONAL, -- Need S tci-PresentDCI-1-2-r16 INTEGER (1..3) OPTIONAL, -- Need S coresetPoolIndex-r16 INTEGER (0..1) OPTIONAL, -- Need S controlResourceSetId-v1610 ControlResourceSetId-v1610 OPTIONAL -- Need S ]], [[ followUnifiedTCI-State-r17 ENUMERATED {enabled} OPTIONAL -- Need R ]], [[ applyIndicatedTCI-State-r18 ENUMERATED {first, second, both, none} OPTIONAL -- Cond FollowUTCI ]] } -- TAG-CONTROLRESOURCESET-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,848 | 11.2.2 Timers of GPRS mobility management | Table 11.3/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : GPRS Mobility management timers - MS side Table 11.3a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : GPRS Mobility management timers – MS side Table 11.4/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : GPRS Mobility management timers - network side Table 11.4a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : GPRS Mobility management timers - network side | 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 | 11.2.2 |
3,849 | 4.1 GTP Tunnel | GTP tunnels are used between two nodes communicating over a GTP based interface, to separate traffic into different communication flows. A GTP tunnel is identified in each node with a TEID, an IP address and a UDP port number. The receiving end side of a GTP tunnel locally assigns the TEID value the transmitting side has to use. The TEID value shall be assigned in a non-predictable manner for PGW S5/S8/S2a/S2b interfaces (see 3GPP TS 33.250[ Security assurance specification for the PGW network product class ] [85]). The TEID values are exchanged between tunnel endpoints using GTP-C or S1-MME or Iu-PS messages. The GTPv2 entity communicates to the peer GTPv2 entity the TEID value at which it expects to receive all subsequent control plane messages related to that GTP tunnel via the: - "Sender F-TEID for Control Plane" IE, - "PGW S5/S8/S2a/S2b F-TEID for PMIP based interface or for GTP based Control Plane interface" IE, - "MSC Server Sv TEID for Control Plane" IE, - "S3/S16/S10 Address and TEID for Control Plane" IE, or - "MME/SGSN Sv TEID for Control Plane" IE. The criteria defining when the same or different GTP tunnels shall be used between the two nodes differs between the control and the user plane, and also between interfaces. For the control plane, for each end-point of a GTP-C tunnel: - The TEID-C shall be unique per PDN-Connection on GTP based S2a, S2b, S5 and S8 interfaces. The same tunnel shall be shared for the control messages related to all bearers associated to the PDN-Connection. A TEID-C on the S2a/S2b/S5/S8 interface shall be released after all its associated EPS bearers are deleted. - There shall be only one pair of TEID-Cs per UE on each of the S3, S10, S16 and N26 interfaces. The same tunnel shall be shared for the control messages related to the same UE operation. A TEID-C on the S3/S10/S16/N26 interface shall be released after its associated UE context is removed or the UE is detached. For the S3 interface, when ISR is active for the UE, during I-RAT handover between the ISR associated nodes, the existing S3 TEID-C may be re-used or new S3 TEID-C may be allocated. During this scenario, if the node decides to allocate new S3 TEID-C, it shall release its own old S3 TEID-C. - There shall be only one pair of TEID-C per UE over the S11 and the S4 interfaces. The same tunnel shall be shared for the control messages related to the same UE operation. A TEID-C on the S11/S4 interface shall be released after all its associated EPS bearers are deleted. - There shall be only one pair of TEID-C per MBMS Bearer Service (i.e. per TMGI and MBMS Flow Identifier, if the MBMS Flow Identifier is provided; or per TMGI, if the MBMS Flow Identifier is not provided) over the Sm and Sn interfaces respectively. The same tunnel shall be shared for the control messages related to the same MBMS Bearer Service. A TEID-C on the Sm/Sn interface shall be released after the MBMS Bearer Session is stopped. For GTP-U, a TEID-U is used according to 3GPP TS 29.281[ General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U) ] [13]. NOTE: GTP-U is based on GTP version 1 (GTPv1). | 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 | 4.1 |
3,850 | 5.3.14A List of equivalent SNPNs | The UE may support equivalent SNPNs. If the UE supports equivalent SNPNs, the ME shall store a list of equivalent SNPNs: - per entry of "list of subscriber data"; or - per the PLMN subscription, if the UE supports access to an SNPN using credentials from a credentials holder. SNPNs in the list of equivalent SNPNs associated with the selected entry of "list of subscriber data" or the selected PLMN subscription shall be regarded by the UE as equivalent to each other for SNPN selection, cell selection and cell re-selection. The list of equivalent SNPNs associated with the selected entry of "list of subscriber data" or the selected PLMN subscription is created, replaced or deleted at the end of each registration procedure. The stored list consists of a list of equivalent SNPNs as provided by the network plus the SNPN identity of the registered SNPN that provided the list. When the UE is switched off, the UE shall keep the stored list(s) so that they can be used for SNPN selection after switch on. The UE shall delete the stored list associated with an entry of "list of subscriber data" or the PLMN subscription, when the USIM is removed, the associated entry of "list of subscriber data" is updated, or the UE registered for emergency services enters the state 5GMM-DEREGISTERED. The maximum number of possible entries in each stored list is 16. NOTE 1: To enable UE mobility between the registered SNPN and an equivalent SNPN, the SNPN identity of the registered SNPN providing a list of equivalent SNPNs and the SNPN identity(ies) in the list of equivalent SNPNs are assumed to be globally-unique SNPN identities. NOTE 2: The MS can provide the list of equivalent SNPNs associated with the selected entry of "list of subscriber data" or the selected PLMN subscription to the lower layers. If the UE supports equivalent SNPNs and registers to different SNPNs over 3GPP and non-3GPP accesses, the UE shall store an additional list of equivalent SNPNs associated with non-3GPP access. The UE manages the two lists of equivalent SNPNs per access type independently. | 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.14A |
3,851 | 9.9.2.1.2 TDD | For the parameters specified in Table 9.9.2.1.2-1, and using the downlink physical channels specified in Annex C, the minimum requirements are specified in 9.9.2.1.2-2 and by the following a) the ratio of the throughput obtained when transmitting the transport format indicated by each reported wideband CQI index subject to an interference source with specified DIP and that obtained when transmitting the transport format indicated by each reported wideband CQI index subject to a white Gaussian noise source shall be ≥ ; b) when transmitting the transport format indicated by each reported wideband CQI index subject to an interference source with specified DIP, the average BLER for the indicated transport formats shall be greater than or equal to 2%. Table 9.9.2.1.2-1 Fading test for single antenna (TDD) Table 9.3.5.1.2-2 Minimum requirement (TDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.9.2.1.2 |
3,852 | 5.6.1.7 Abnormal cases on the network side | The following abnormal cases can be identified: a) Lower layer failure If a lower layer failure occurs before a SERVICE REJECT message has been sent to the UE or the service request procedure has been completed by the network, the network enters/stays in EMM-IDLE. b) Protocol error If the SERVICE REQUEST, EXTENDED SERVICE REQUEST or the CONTROL PLANE SERVICE REQUEST message is received with a protocol error, the network shall return a SERVICE REJECT message with one of the following EMM cause values: #96: invalid mandatory information; #99: information element non-existent or not implemented; #100: conditional IE error; or #111: protocol error, unspecified. The network stays in the current EMM mode. c) More than one SERVICE REQUEST, EXTENDED SERVICE REQUEST or CONTROL PLANE SERVICE REQUEST received before the procedure has been completed (i.e., before SERVICE REJECT message has been sent or service request procedure has been completed) - If one or more of the information elements in the SERVICE REQUEST message, CONTROL PLANE SERVICE REQUEST or EXTENDED SERVICE REQUEST for packet services differs from the ones received within the previous SERVICE REQUEST, CONTROL PLANE SERVICE REQUEST or EXTENDED SERVICE REQUEST message for packet services, the previously initiated service request procedure shall be aborted and the new service request procedure shall be progressed; NOTE: The network actions are implementation dependent for the case that more than one EXTENDED SERVICE REQUEST messages for CS fallback or 1xCS fallback are received and their information elements differ. - If the information elements do not differ, then the network shall continue with the previous service request procedure and shall not treat any further this SERVICE REQUEST, EXTENDED SERVICE REQUEST or CONTROL PLANE SERVICE REQUEST message. d) ATTACH REQUEST received before a SERVICE REJECT message has been sent or the service request procedure has been completed If an ATTACH REQUEST message is received and the service request procedure has not been completed or a SERVICE REJECT message has not been sent, the network may initiate the EMM common procedures, e.g. the EMM authentication procedure. The network may e.g. after a successful EMM authentication procedure execution, abort the service request procedure, delete the EMM context, EPS bearer contexts, if any, and progress the new ATTACH REQUEST. e) TRACKING AREA UPDATE REQUEST message received before the service request procedure has been completed or a SERVICE REJECT message has been sent If a TRACKING AREA UPDATE REQUEST message is received and the service request procedure has not been completed or a SERVICE REJECT message has not been sent, the network may initiate the EMM common procedures, e.g. the EMM authentication procedure. The network may e.g. after a successful EMM authentication procedure execution, abort the service request procedure and progress the tracking area updating procedure. f) Default or dedicated bearer set up failure If the lower layers indicate a failure to set up a radio or S1 bearer, the MME shall locally deactivate the EPS bearer as described in clause 6.4.4.6. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.6.1.7 |
3,853 | 4.24.1 UPF anchored Mobile Originated Data Transport in Control Plane CIoT 5GS Optimisation | This clause describes the procedures for Mobile Originated Transport in Control Plane CIoT 5GS Optimisation where the PDU Session is terminated at a UPF. Figure 4.24.1-1: UPF anchored Mobile Originated Data Transport in Control Plane CIoT 5GS Optimisation 1. If the UE is CM-CONNECTED it sends a NAS message carrying the ciphered PDU session ID and ciphered uplink data as payload. If the UE is in CM-IDLE, the UE first establishes an RRC connection or sends the RRCEarlyDataRequest message and sends a NAS message as part of this. The UE may also send NAS Release Assistance Information (NAS RAI) included in the NAS message. NAS RAI indicates that no further Uplink and Downlink Data transmissions are expected, or that only a single Downlink data transmission (e.g. Acknowledgement or response to Uplink data) subsequent to this Uplink Data transmission is expected. 1a. In the NB-IoT case, during step 1 the NG-RAN, based on configuration, may retrieve the NB-IoT UE Priority and the Expected UE Behaviour Parameters from the AMF, if not previously retrieved. Based on such parameters, the NG-RAN may apply prioritisation between requests from different UEs before triggering step 2 and throughout the RRC connection. The NG-RAN may retrieve additional parameters (e.g. UE Radio Capabilities). 2. NG-RAN forwards the NAS message to the AMF using the Initial NAS message procedure (if the UE was in CM-IDLE before step 1) or using the Uplink NAS transport procedure (if the UE was in CM-CONNECTED before step 1). If RRCEarlyDataRequest message was received in step 1, the NG-RAN includes "EDT Session" indication in the N2 Initial UE message. The RAI signalled by MAC based on the Buffer Status Report (BSR), see TS 36.321[ Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification ] [56], shall not be used when using Control Plane CIoT 5GS Optimisations. 3. AMF checks the integrity of the incoming NAS message and deciphers the PDU session ID and uplink data. If a NAS RAI is received from the UE and it conflicts with the Expected UE Behaviour, the NAS RAI takes precedence. 3a. If the AMF received "EDT Session" indication from the NG-RAN in step 2, the AMF sends an N2 message to the NG-RAN. a) In the case of NAS RAI with Uplink data and it indicated that Downlink data was not expected and the AMF does not expect any other signalling with the UE, the AMF shall - either send a NAS service accept in the N2 Downlink NAS Transport message and include End Indication to indicate that no further data or signalling is expected with the UE; or - alternatively, the AMF sends an N2 Connection Establishment Indication message including End Indication to indicate that no further data or signalling is expected with the UE. b) If the AMF determines more data or signalling may be pending, the AMF sends an N2 Downlink NAS Transport message or Initial Context Setup Request message without End Indication. 3b. If 3a was executed, the NG-RAN completes the RRC early data procedure as follows. a) For the case of 3a.a) the NG-RAN proceeds with RRCEarlyDataComplete message. The procedure is completed in step 5. b) For the case of 3a.b) the NG-RAN proceeds with RRC connection establishment procedure. In that case, all steps up to step 13 apply. 4. AMF determines the (V-)SMF handling the PDU session based on the PDU session ID contained in the NAS message and passes the PDU Session ID and the data to the (V-)SMF by invoking Nsmf_PDUSession_SendMOData service operation. If NG-RAN forwarded the NAS message to the AMF using the Initial NAS message procedure in step 2 and the UE is accessing via NB-IoT RAT then the AMF may inform the (H-)SMFs whether the RRC establishment cause is set to "MO exception data", as described in clause 5.31.14.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The AMF may immediately send the MO Exception Data Counter to the (H-)SMF. If no Downlink Data is expected based on the NAS RAI from the UE in step 1 and if the AMF is not aware of pending MT traffic, then AMF does not wait for step 7 and continues with step 12. 5. The (V-)SMF decompresses the header if header compression applies to the PDU session and forwards the data to the UPF. The UPF forwards the data to the DN based on data forwarding rule, e.g. in the case of unstructured data, tunnelling may be applied according to clause 5.6.10.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 6. [Conditional] In the non-roaming and LBO case, the UPF forwards available downlink data to the (V-)SMF, in the home-routed roaming case, the H-UPF forwards the data to the V-UPF then to the V-SMF. 7. [Conditional] The (V-)SMF compresses the header if header compression applies to the PDU session. The (V-)SMF forwards the downlink data and the PDU session ID to the AMF using the Namf_Communication_N1N2MessageTransfer service operation. 8. [Conditional] The AMF creates a DL NAS transport message with the PDU session ID and the downlink data. The AMF ciphers and integrity protects the NAS transport message 9. [Conditional] The AMF sends the DL NAS transport message to NG-RAN. If NAS RAI indicated for single uplink and single downlink packets (e.g. acknowledgment expected) and AMF has determined the data transmission is for single uplink and single downlink packets, the AMF includes an End Indication in the DL NAS transport message to indicate that no further data or signalling is expected with the UE. 10. [Conditional] NG-RAN delivers the NAS payload over RRC to the UE. 11. If no further data or signalling is pending and AMF received NAS RAI indicating single downlink data transmission, then AMF triggers the AN release procedure (clause 4.2.6) and the procedure stops after this step. 12. [Conditional] If no further activity is detected by NG-RAN, then NG-RAN triggers the AN release procedure. 13. [Conditional] The UE's logical NG-AP signalling connection and RRC signalling connection are released according to clause 4.2.6. NOTE: The details of the NGAP messages to be used for this procedure are specified in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.24.1 |
3,854 | 8.2.1.4 Intra-gNB-DU LTM | This procedure is used for the case when the UE moves within the same gNB-DU during NR operation for LTM. Figure 8.2.1.4-1 shows the intra-gNB-DU LTM procedure for intra-NR. Figure 8.2.1.4-1: Intra-gNB-DU LTM 1. The UE sends a MeasurementReport message (L3 measurement result) to the gNB-DU containing measurements of neighbouring cells. The gNB-DU sends an UL RRC MESSAGE TRANSFER message conveying the received MeasurementReport message to the gNB-CU. 2. The gNB-CU determines to initiate LTM configuration. 3. The gNB-CU sends a UE CONTEXT MODIFICATION REQUEST message to the gNB-DU containing one target candidate cell ID, the LTM configuration ID of the candidate cell, and LTM configuration ID mapping list, the CSI resource configuration. The gNB-CU requests PRACH resources from the gNB-DU. The gNB-CU may request the gNB-DU to provide the lower layer configuration for the purpose of generating the reference configuration. 4. If the gNB-DU accepts the request of LTM configuration, it responds with a UE CONTEXT MODIFICATION RESPONSE message including the generated lower layer RRC configurations (e.g., TCI state configuration, RACH configuration, and the CSI report configuration) for the accepted target candidate cell. NOTE 1: Steps 3 and 4 may be initiated multiple times for LTM candidate cell preparation of multiple cells including the source cell. 5. The gNB-CU sends a UE CONTEXT MODIFICATION REQUEST message to the source gNB-DU including the collected TCI state configurations and the gNB-CU may send the CSI report configuration for all the accepted target candidate cells. 6. The source gNB-DU responds with a UE CONTEXT MODIFICATION RESPONSE message which includes an updated lower layer configuration, e.g., containing the CSI report configuration of the source cell. NOTE 2: In case of subsequent LTM, the CU-initiated UE Context Modification procedure may be invoked per each candidate cell to transfer to the candidate gNB-DU the CSI report configuration, TCI state information, RACH configuration, and the LTM configuration IDs of the candidate cells. 7. The gNB-CU sends a DL RRC MESSAGE TRANSFER message to the gNB-DU, which includes the generated RRCReconfiguration message with the LTM configuration. 8. The gNB-DU forwards the received RRCReconfiguration message to the UE. 9. The UE responds to the gNB-DU with an RRCReconfigurationComplete message. 10. The gNB-DU forwards the RRCReconfigurationComplete message to the gNB-CU via an UL RRC MESSAGE TRANSFER message. 11. Early synchronization may be performed as specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [2]. 12. The UE sends the L1 measurement result to the gNB-DU. The gNB-DU decides to execute LTM. 13. The gNB-DU sends the Cell Switch command to the UE. 14. The gNB-DU sends the DU-CU CELL CHANGE NOTIFICATION message to the gNB-CU to indicate the initiation of the Cell Switch command to the UE including the target cell ID and the TCI state ID. 15. The gNB-DU detects the UE access as specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [2]. 16. The target gNB-DU sends the ACCESS SUCCESS message to the gNB-CU with the target cell ID. 17. The UE sends an RRCReconfigurationComplete message to the gNB-DU. 18. The gNB-DU forwards the RRCReconfigurationComplete message to the gNB-CU via an UL RRC MESSAGE TRANSFER message. 19. The gNB-CU may send the UE CONTEXT MODIFICATION REQUEST message to the gNB-DU to release the resources of prepared cells. 20. The gNB-DU responds with a UE CONTEXT MODIFICATION RESPONSE message. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.2.1.4 |
3,855 | 8.4.2.2.5 Enhanced Downlink Control Channel Performance Requirement Type A - 2 Tx Antenna Port with Colliding CRS Dominant Interferer | The purpose of this test is to verify the Enhanced Downlink Control Channel Performance Requirement Type A for PDCCH/PCFICH with 2 transmit antennas for the case of dominant interferer with the colliding CRS pattern and applying interference model defined in clause B.7.1. For the parameters specified in Table 8.4.2-1 and Table 8.4.2.2.5-1, the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.4.2.2.5-2. In Table 8.4.2.2.5-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is provided and includes Cell 2 and Cell 3. Table 8.4.2.2.5-1: Test Parameters for PDCCH/PCFICH Table 8.4.2.2.5-2: Minimum Performance for PDCCH/PCFICH for Enhanced Downlink Control Channel Performance Requirement Type A | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.4.2.2.5 |
3,856 | 4.2.10.2 SMF triggered N3 data transfer establishment procedure | If UE and AMF successfully negotiate N3 data transfer in addition to Control Plane CIoT 5GS Optimisation based on the Preferred and Supported Network Behaviour as defined in clause 5.31.2, then the SMF may, e.g. based on the amount of data to be transferred or due to congestion, initiate N3 data transfer establishment procedure for any PDU session for which Control Plane Only Indicator was not included. The SMF triggered N3 data transfer establishment procedure may be initiated by the SMF while the UE is in CM-IDLE or CM-CONNECTED state and follows the Network Triggered Service Request procedure defined in clause 4.2.3.3 with the following differences: Step 3a. The SMF request the activation of Data Radio Bearer and N3 tunnel for the PDU session in Namf_Communication_N1N2MessageTransfer. Step 3b. If the RAT type is NB-IoT and the UE already has 2 PDU Sessions with active user plane resources, the AMF shall not proceed with the rest of the procedure and instead the AMF shall respond with Namf_Communication_N1N2MessageTransfer Response with appropriate failure message. Step 6. The UE triggered N3 data transfer establishment procedure defined in clause 4.2.10.1 is applied instead of Service Request procedure from clause 4.2.3.2. Step 7. When the N3 data transfer is set up for a PDU session, the UE and the network shall only use user plane radio bearers to transfer data PDUs on that PDU Session. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.10.2 |
3,857 | 5.15.13 Support of data rate limitation per Network Slice for a UE | A UE subscription information may include an optional Slice Maximum Bit Rate for the UE (Subscribed UE-Slice-MBR) for an S-NSSAI, which applies for 3GPP access type only. The Subscribed UE-Slice-MBR includes a UL and a DL value. If a Subscribed UE-Slice-MBR is associated to an S-NSSAI in the subscription information, it is provided by the AMF to the NG-RAN when the AMF provides the Allowed NSSAI for the UE to the NG-RAN as UE-Slice-MBR QoS parameter. The UE-Slice-MBR QoS parameter is defined in clause 5.7.2.6. If the Subscribed UE-Slice-MBR for a UE changes, the AMF updates UE-Slice-MBR in the NG-RAN accordingly. In roaming case, the UE-Slice-MBR is provided for the S-NSSAI of the VPLMN which maps to the S-NSSAI of the HPLMN and the AMF may first interact with the PCF for authorization of the Subscribed UE-Slice-MBR. If the AMF interacts with the PCF, the PCF may provide the Authorized UE-Slice-MBR that is used as UE-Slice-MBR by the AMF as described in clause 6.1.2.1 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. For a roaming UE, the S-NSSAI of the VPLMN maps to only one S-NSSAI of the HPLMN for which an UE-Slice-MBR is applied. The enforcement of the UE-Slice-MBR value, if present in the UE context in the NG-RAN for an S-NSSAI, is described in clause 5.7.1.10. NOTE: The PCF for the PDU Session may in addition be configured to monitor the data rate per Network Slice for a UE and to strengthen or relax the traffic restrictions for individual PDU Sessions or PCC rules accordingly, as described in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45] clause 6.2.1.9. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.13 |
3,858 | 6.11.3.1 Sequence generation | The resynchronization signal (RSS) is transmitted in subframes numbered , where the RSS duration is configured by higher layers. The sequence used for the th RSS subframe is generated according to where the pseudo-random sequence is defined in clause 7.2. The pseudo-random sequence generator shall be initialised each subframe with , where u equals the value of the higher-layer parameter systemInfoUnchanged-BR-r15 as set in subframe . is given by Table 6.11.3.1-1. Table 6.11.3.1-1: Definition of . | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.11.3.1 |
3,859 | 16a.1 Diameter Authentication and Authorization | Diameter Authentication and Authorization shall be used according to RFC 7155 [120]. The GGSN/P-GW and the Diameter server shall advertise the support of the Diameter NASREQ Application by including the value of the appropriate application identifier in the Capability-Exchange-Request and Capability-Exchange-Answer commands as specified in IETF RFC 6733 [111]. The Diameter client function may reside in a GGSN/P-GW. When the GGSN/P-GW receives an initial attach (e.g. Create PDP Context) request message the Diameter client function may send the authentication information to an authentication server, which is identified during the APN provisioning. The authentication server checks that the user can be accepted. The response (when positive) may contain network information, such as an IPv4 address and/or IPv6 prefix for the user when the GGSN/P-GW is interworking with the AAA server. The information delivered during the Diameter authentication can be used to automatically correlate the users identity (the MSISDN or IMSI) to the IPv4 address and/or IPv6 prefix, if applicable, assigned/confirmed by the GGSN/P-GW or the authentication server respectively. The same procedure applies, in case of sending the authentication to a ‘proxy’ authentication server. Diameter Authentication is applicable to the initial access (e.g. primary PDP context or the default bearer). When the GGSN/P-GW receives a positive response from the authentication server it shall complete the initial access (e.g. PDP context activation) procedure. If a failure or no response is received, the GGSN/P-GW shall reject the initial access (e.g. PDP Context Activation) attempt with a suitable cause code, e.g. User Authentication failed. The GGSN may also use the Diameter re-authorization procedure for the purpose of IPv4 address allocation to the UE for PDP type of IPv4v6 after establishment of a PDN connection. For EPS, the P-GW may also use the Diameter re-authorization procedure for the purpose of IPv4 address allocation to the UE for PDN type of IPv4v6 after establishment of a PDN connection. The use cases that may lead this procedure are: - Deferred IPv4 address allocation via DHCPv4 procedure after successful attach on 3GPP accesses. - Deferred IPv4 address allocation after successful attach in trusted non-3GPP IP access on S2a. - Deferred IPv4 home address allocation via DSMIPv6 Re-Registration procedure via S2c. | 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.1 |
3,860 | 16.14.6 AMF (Re-)Selection | The gNB implements the NAS Node Selection Function specified in TS 38.410[ NG-RAN; NG general aspects and principles ] [16]. For an RRC_CONNECTED UE, when the gNB is configured to ensure that the UE connects to an AMF that serves the country in which the UE is located, if the gNB detects that the UE is in a different country to that served by the serving AMF, then it should perform an NG handover to change to an appropriate AMF, or initiate an UE Context Release Request procedure towards the serving AMF (in which case the AMF may decide to de-register the UE). For the purpose of selecting an appropriate AMF, the 5GC may verify the UE location according to TS 23.501[ System architecture for the 5G System (5GS) ] [3] and TS 38.305[ NG Radio Access Network (NG-RAN); Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN ] [42] after the UE has attached to the network. NOTE: UE location verification for AMF selection should not be necessary if NTN cell(s) do not extend across countries. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.14.6 |
3,861 | 6.11.2 Requirements | The 5G system shall support network resource utilization efficiently and network optimization based on system information, including:- network conditions, such as network load and congestion information; - information on served UEs such as access information (e.g. 3GPP access, non-3GPP access), cell type (e.g. macro cell, small cell), user experienced data rate; - application's characteristics (e.g. expected traffic over time); - information on prioritized communication such as user subscription profile and priority level, priority services (e.g. MPS, Emergency, and Public Safety), application used for priority communications (e.g. voice, video, and data) and traffic associated with priority communications (signalling and media); - subject to user consent, enhanced traffic characteristic of UE (e.g. Mobility information (e.g. no mobility, nomadic, spatially restricted mobility, full mobility), location, sensor-level information (e.g. direction, speed, power status, display status, other sensor information installed in the UE), application-level information (e.g. foreground applications, running background application, and user settings). The 5G system shall support mechanisms to collect system information for network optimization within an operator configured time scale. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.11.2 |
3,862 | 11.1 Roaming and Access Restrictions | The principles for conveying roaming and access restriction info for EN-DC 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 ] [2]. For MR-DC with 5GC, SCG (re)selection at the SN is based on roaming and access restriction information in SN. If roaming and access restriction information is not available at the SN, the SN shall consider that there is no restriction for SCG (re)selection. Therefore, the MN needs to convey the latest roaming and access restriction information as received from the Core Network or another NG-RAN node to the SN via XnAP messages. | 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 | 11.1 |
3,863 | 10.10.1 EN-DC | The RRC Transfer procedure is used to deliver an RRC message, encapsulated in a PDCP PDU between the MN and the SN (and vice versa) so that it may be forwarded to/from the UE using split SRB. The RRC transfer procedure is also used for: - providing an NR measurement report, NR failure information, NR UE assistance information or intra-SN CPC execution completion from the UE to the SN via the MN. If UE is IAB-MT, providing NR IAB other information from the IAB-MT to the SN via the MN; - providing MCG failure information from the UE to the MN via the SN and an RRC reconfiguration, or release, or an inter-RAT handover command from the MN to the UE via the SN. Additional details of the RRC transfer procedure are defined in TS 36.423[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP) ] [9]. Split SRB: Figure 10.10.1-1: RRC Transfer procedure for the split SRB (DL operation) Figure 10.10.1-1 shows an example signaling flow for the DL RRC Transfer in case of the split SRB: 1. The MN, when it decides to use the split SRBs, starts the procedure by initiating the RRC Transfer procedure. The MN encapsulates the RRC message in a PDCP-C PDU and ciphers with own keys. NOTE: The usage of the split SRBs shall be indicated in the Secondary Node Addition procedure or Modification procedure. 2. The SN forwards the RRC message to the UE. 3. The SN may send PDCP delivery acknowledgement of the RRC message forwarded in step 2. Figure 10.10.1-2: RRC Transfer procedure for the split SRB (UL operation) Figure 10.10.1-2 shows an example signaling flow for the UL RRC Transfer in case of the split SRB: 1. When the UE provides response to the RRC message, it sends it to the SN. 2. The SN initiates the RRC Transfer procedure, in which it transfers the received PDCP-C PDU with encapsulated RRC message. NR measurement report, NR failure information, NR UE assistance information, NR IAB other information or intra-SN CPC execution completion: Figure 10.10.1-3: RRC Transfer procedure for NR measurement report, NR failure information, NR UE assistance information, NR IAB other information or intra-SN CPC execution completion Figure 10.10.1-3 shows an example signaling flow for RRC Transfer in case of the forwarding of the NR measurement report, NR failure information, NR IAB other information from the UE, NR UE assistance information or intra-SN CPC execution completion: 1. When the UE sends a measurement report, NR failure information, NR UE assistance information, NR IAB other information or intra-SN CPC execution completion, it sends it to the MN in a container within ULInformationTransferMRDC message as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]. 2. The MN initiates the RRC Transfer procedure, in which it transfers the received NR measurement report, NR failure information, NR UE assistance information, NR IAB other information or intra-SN CPC execution completion as an octet string. MCG failure information and RRC Reconfiguration / RRC Release / inter-RAT handover command over SRB3: Figure 10.10.1-4: RRC Transfer procedure for MCG failure information Figure 10.10.1-4 shows an example signaling flow for RRC Transfer in case of the forwarding of the MCG failure information from the UE: 1. When the UE sends EUTRA MCGFailureInformation message over SRB3, it sends it to the SN in a container within ULInformationTransferMRDC message as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [4]. 2. The SN initiates the RRC Transfer procedure, in which it transfers the received EUTRA MCGFailureInformation message as an octet string. 3. The MN initiates the RRC Transfer procedure, in which it transfers the EUTRA RRCConnectionReconfiguration message, or EUTRA RRCConnectionRelease message, or MobilityFromEUTRACommand message as an octet string. 4. The SN sends the received EUTRA RRC message to the UE over SRB3 in a container within DLInformationTransferMRDC, message as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [4]. | 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.10.1 |
3,864 | 4.3.32.2 System enhancements to support IAB | In IAB operation, the IAB-UE interacts with the EPC using procedures defined for UE. The IAB-node gNB-DU only interacts with the IAB-donor-CU and follows the CU/DU design defined in TS 38.401[ NG-RAN; Architecture description ] [90]. For the IAB-UE operation, the existing UE authentication methods as defined in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [41] apply. For EPC, only USIM based methods are allowed. The following aspects of EPS are enhanced to support the IAB operation: - the Attach procedure as defined in clause 5.3.2 is enhanced to indicate IAB-node's capability to the MME: - the IAB-node provides an IAB-indication to the eNodeB when the IAB-node establishes the RRC connection. If the IAB-indication is received, the eNodeB selects an MME that supports IAB, and includes the IAB-indication in the INITIAL UE MESSAGE so that the MME can perform IAB authorization; - the UE Subscription data as defined in clause 5.7.1 is enhanced to include the authorization information for the IAB operation; - Authorization procedure during the UE attach procedure is enhanced to perform verification of IAB subscription information; - If the IAB operation is not authorized, the MME may reject the IAB-UE's attach request or detach the IAB-UE, or the MME may initiate UE Context setup/Modification procedure by providing IAB authorized indication with the value set to "not authorized" to the eNodeB, but the IAB-UE is in the EMM-REGISTERED state. - If the IAB operation is authorized, UE Context setup/modification procedure is enhanced to provide IAB authorized indication with the value set to "authorized" to eNodeB and IAB-donor gNB. After attached or registered, the IAB-node remains in ECM-CONNECTED state if the IAB operation is authorized. In the case of radio link failure, the IAB-UE uses existing UE procedure to restore the connection with the network. The IAB-UE uses the Detach procedure defined in clause 5.3.8 to disconnect from the network. | 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.32.2 |
3,865 | 8.10.1.2.11 Closed loop spatial multiplexing performance - Single-Layer Spatial Multiplexing 4 Tx Antenna Port with CRS assistance information (Cell-Specific Reference Symbols) | The requirements are specified in Table 8.10.1.2.11-2, with the addition of parameters in Table 8.10.1.2.11-1. In Table 8.10.1.2.11-1, Cell 1 is the serving cell, and Cell 2 is the aggressor cell. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1 and Cell 2, respectively. The CRS assistance information [7] is provided to the UE and includes information on Cell 2. The purpose of the test is to verify the closed loop single layer TM4 performance under assumption that UE applies CRS interference mitigation in the scenario with 4 CRS antenna ports in the serving and aggressor cell. Table 8.10.1.2.11-1: Test Parameters Table 8.10.1.2.11-2: Minimum Performance for PDSCH | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.10.1.2.11 |
3,866 | I.10.2.1 Untrusted non-3GPP access support in SNPN without CH | Procedures for untrusted non-3GPP access authentication are described in clause 7.2.1. For SNPN the procedures are modified as follows: Steps 1-4 are performed as described in clause 7.2.1. In step 5, the SUCI can be an onboarding SUCI. Further in step 5, the SUCI can be of type anonymous SUCI if the construction of SUCI as described in clause 6.12 cannot be used and if the employed EAP method supports SUPI privacy. Step 6 is performed as described in clause 7.2.1. In step 7 of clause 7.2.1, in case the AUSF receives an onboarding indication, the AUSF shall perform steps 6-10 and 14-17 as described in Annex I.2.2.2. In the selection of UE authentication method in step 7 of clause 7.2.1, 5G AKA, EAP-AKA’, or any other key-generating EAP authentication method apply. When the "username" part of the SUPI is "anonymous" or omitted, the UDM may select an authentication method based on the "realm" part of the SUPI or on the UDM local policy. In case the AUSF received an anonymous SUCI in step 7 (but no onboarding indication was received) the AUSF shall perform steps 11-13 of Annex I.2.2.2 after a successful authentication to inform the UDM of the actual SUPI. In case anonymous SUCI and onboarding indication was received in step 7, steps 11-13 of Annex I.2.2.2 can be skipped. In step 8 of clause 7.2.1 in case an EAP method is used for primary authentication, the AMF shall encapsulate the EAP-Success received from AUSF within the SMC message. Steps 9-16 are performed as described in clause 7.2.1. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | I.10.2.1 |
3,867 | 5.15.7.2 Idle mode aspects | In addition to the interworking principles documented in clause 5.17.2 the following applies for interworking with N26: - When UE moves from 5GS to EPS, the UE context information sent by AMF to MME includes the UE Usage type, which is retrieved from UDM by AMF as part of subscription data. - When UE moves from EPS to 5GS, then the UE includes the S-NSSAIs (with values for the Serving PLMN of the target 5GS, if available) associated with the established PDN connections in the Requested NSSAI in RRC Connection Establishment (subject to the conditions set out in clause 5.15.9) and NAS. The UE also provides to the AMF in the Registration Request message the mapping information as described in clause 5.15.6. The UE derives the S-NSSAIs values for the Serving PLMN by using the latest available information from EPS (if received in PCO) and from 5GS (e.g. based on URSP, Configured NSSAI, Allowed NSSAI). In the home-routed roaming case, the AMF selects default V-SMFs. The SMF+PGW-C sends PDU Session IDs and related S-NSSAIs to AMF. The AMF derives S-NSSAI values for the Serving PLMN as described in clause 5.15.5.2.1 and determines whether the AMF is the appropriate AMF to serve the UE. If not, the AMF reallocation may need be triggered. For each PDU Session the AMF determines whether the V-SMF need be reselected based on the associated S-NSSAI value for the Serving PLMN. If the V-SMF need be reallocated, i.e. change from the default V-SMF to another V-SMF, the AMF trigger the V-SMF reallocation as described in clause 4.23.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. In addition to the interworking principles documented in clause 5.17.2 the following applies for interworking without N26: - When the UE initiates the Registration procedure, and subject to the conditions set out in clause 5.15.9, the UE includes the S-NSSAI (with values for the Serving PLMN of the target 5GS) associated with the established PDN connections in the Requested NSSAI in the RRC Connection Establishment. - The UE includes the S-NSSAIs (with values for the Serving PLMN of the target 5GS, if available) and the HPLMN S-NSSAI received in the PCO for the PDN connections as mapping information when moving PDN connections to 5GC using PDU Session Establishment Request message. The UE derives the S-NSSAIs values for the Serving PLMN by using, the latest available information from EPS (if received in PCO) and from 5GS (e.g. based on URSP, Configured NSSAI, Allowed NSSAI). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.7.2 |
3,868 | 5.9.3.5 Requirements for Network Functions (NF) | The NF that sends a signalling message (service/subscription request or notification message) shall include its PLMN-ID in the 3gpp-Sbi-Originating-Network-Id header. If an NF supports multiple PLMN-IDs, the sending NF shall include the PLMN ID in the 3gpp-Sbi-Originating-Network-Id header on behalf of which the message is sent. The handling of the PLMN-ID in the 3gpp-Sbi-Originating-Network-Id header at the receiving NF is up to configuration and deployment. NOTE: A misconfigured PLMN-ID in the 3gpp-Sbi-Originating-Network-Id header can lead to service interruption. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 5.9.3.5 |
3,869 | 5.8.17.4 Actions related to selection and reselection of NR sidelink U2U Relay UE | A UE capable of NR sidelink U2U Remote UE operation shall: 1> perform NR sidelink discovery procedure as specified in clause 5.8.13 in order to search for candidate NR sidelink U2U Relay UEs; 2> when evaluating the one or more detected NR sidelink U2U Relay UEs, apply layer 3 filtering as specified in 5.5.3.2 across measurements that concern the same U2U Relay UE ID and using the sd-FilterCoefficientU2U in SIB12 (if in RRC_IDLE/INACTIVE), the sd-FilterCoefficientU2U in sl-ConfigDedicatedNR (if in RRC_CONNECTED) or the preconfigured sd-FilterCoefficientU2U as defined in 9.3 (out of coverage), before using the SD-RSRP measurement results; 2> consider a candidate NR sidelink U2U Relay UE for which SD-RSRP exceeds sd-RSRP-ThreshU2U has met the AS criteria; 1> if the UE detects any suitable NR sidelink U2U Relay UE(s): 2> consider one of the available suitable NR sidelink U2U Relay UE(s) can be selected; 1> else: 2> consider no NR sidelink U2U Relay UE to be selected; 1> if the UE is performing U2U Relay Communication with integrated Discovery as specified in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [65] and has received Direct Communication Request message(s) from one or multiple NR sidelink U2U Relay UEs: 2> when evaluating the NR sidelink U2U Relay UE(s), apply layer 3 filtering as specified in 5.5.3.2 across measurements that concern the same U2U Relay UE ID and using the sd-FilterCoefficientU2U in SIB12 (if in RRC_IDLE/INACTIVE), the sd-FilterCoefficientU2U in sl-ConfigDedicatedNR (if in RRC_CONNECTED) or the preconfigured sd-FilterCoefficientU2U as defined in 9.3 (out of coverage), before using the SD-RSRP measurement results; 2> consider a candidate NR sidelink U2U Relay UE for which SL-RSRP exceeds sd-RSRP-ThreshU2U has met the AS criteria; 2> if the UE detects any suitable NR sidelink U2U Relay UE(s): 3> consider one of the available suitable NR sidelink U2U Relay UE(s) can be selected; 2> else: 3> consider no NR sidelink U2U Relay UE to be selected. NOTE: A candidate NR sidelink U2U Relay UE which meets all AS layer criteria defined in 5.8.17.4 and higher layer criteria defined in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [65] can be regarded as suitable NR sidelink U2U Relay UE by the NR sidelink U2U Remote UE. If multiple suitable NR sidelink U2U Relay UEs are available, it is up to Remote UE implementation to choose one NR sidelink U2U Relay UE. The details of the interaction with upper layers are up to UE implementation. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.17.4 |
3,870 | 5.2.6.33.5 Nnef_AF_request_for_QoS_Update service operation | Service operation name: Nnef_AF_request_for_QoS Update Description: The consumer requests the network to update the Service Requirement(s) and/or additional Alternative Service Requirement(s) for a UE or a group of UEs. Inputs, Required: Transaction Reference ID. Inputs, Optional: Flow description information (as described in clause 6.1.3.6 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]), QoS reference or individual QoS parameters as described in clause 6.1.3.22 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], time period, traffic volume, Alternative Service Requirements (containing one or more QoS reference parameters or Requested Alternative QoS Parameter Sets in a prioritized order), QoS parameter(s) to be measured, Reporting frequency, Target of reporting and optional an indication of local event notification as described in clause 6.1.3.21 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], traffic characteristics as described in clause 6.1.3.23 or 6.1.3.23a of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. Outputs, Required: Result. Output (optional): None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.33.5 |
3,871 | 8.5.2.2.3 Minimum Requirement 2 Tx Antenna Port (demodulation subframe overlaps with aggressor cell ABS) | For the parameters specified in Table 8.5.2-1 and Table 8.5.2.2.3-1, the average probability of a miss-detecting ACK for NACK (Pm-an) shall be below the specified value in Table 8.5.2.2.3-2. The downlink physical setup is in accordance with Annex C.3.2 and Annex C.3.3, In Table 8.5.2.2.3-1, Cell 1 is the serving cell, and Cell 2 is the aggressor cell. The downlink physical channel setup for Cell 1 is according to Annex C.3.2 and for Cell 2 is according to Annex C.3.3, respectively. Table 8.5.2.2.3-1: Test Parameters for PHICH Table 8.5.2.2.3-2: Minimum performance PHICH | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.5.2.2.3 |
3,872 | 4.3.17.4 UE configuration and usage of indicators | A subscriber can by agreement with its operator be required to use UEs that are configured (see TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [69]) to support one or more of the following options: - UE configured for low access priority; and/or - UE configured with a permission for overriding low access priority, which is only applicable for a UE that is also configured for low access priority; and/or - UE configured to perform Attach with IMSI at PLMN change; and/or - UE configured with a long minimum periodic PLMN search time limit; and/or - UE configured for specific handling of the invalid USIM state, the "forbidden PLMN list", the "forbidden PLMNs for attach in S1mode list" and the "forbidden PLMNs for GPRS service list"; and/or - UE configured for Extended Access Barring; and/or - UE configured with a permission for overriding Extended Access Barring, which is only applicable for a UE that is also configured for Extended Access Barring. NOTE 1: When a UE is accessing the network with low access priority, then the UE may be subject for longer backoff timers at overload and consequently need to be designed to be tolerant to delays when accessing the network. UEs can be configured for one or more of the above options with the following restrictions: - in this Release of the specification, a UE that is configured for low access priority shall also be configured for Extended Access Barring; and - in this Release of the specification, a UE that is configured for Extended Access Barring shall be configured for low access priority. - in this Release of the specification, a UE that is configured for overriding low access priority shall also be configured for overriding Extended Access Barring; and - in this Release of the specification, a UE that is configured for overriding Extended Access Barring shall also be configured for overriding low access priority. UEs can be configured for one or more of the above options. Post-manufacturing configuration of these options in the UE can be performed only by OMA DM or (U)SIM OTA procedures. UEs capable of the above options should support configuration of these options by both OMA DM and (U)SIM OTA procedures. A UE configured for low access priority shall transmit the low access priority indicator to the MME during the appropriate NAS signalling procedures and transmit the corresponding low access priority to the E-UTRAN during RRC connection establishment procedures. NOTE 2: The low access priority indicator in NAS signalling and the corresponding low access priority for RRC connection establishment are used by the network to decide whether to accept the NAS request or the setup of the RRC connection respectively. Low access priority shall not be applicable in the following situations: - for all procedures related to an emergency PDN connection; used for IMS Emergency sessions that are to be prioritized as per the requirements for IMS Emergency session procedures (see clause 4.3.12). When an emergency PDN connection gets established, the MME may, based on MME configuration, initiate the deactivation of any non-emergency PDN connection using the MME requested PDN disconnection procedure described in clause 5.10.3; - for all procedures when preferential access to the network is provided to the UE by the Access Class 11-15 mechanism according to TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37] and TS 22.011[ Service accessibility ] [67] e.g. for Multimedia Priority Services as described in clause 4.3.18; NOTE 3: The configuration of a UE for low access priority and Access Class 11-15 are configured independently of each other. However, the home operator can take care to prevent a subscription for Access Class 11-15 from being used in a UE configured for low access priority. - for RRC connection establishment procedures when responding to paging; - for a UE configured with a permission for overriding low access priority under conditions described by bullet o in clause 4.3.17.2; or - other specific situations described in TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [46]. If the NAS session management request message used to establish a new PDN connection contains a low access priority indication, the MME shall forward the low access priority indication in the Create Session Request message to the S-GW/P-GW. The low priority indication gets associated with a PDN connection when it is established and it shall not change until the PDN connection is deactivated. The low access priority indication may be included in charging records by the visited and home networks. In order to permit the S-GW to include the low access priority indicator in the charging records, the low access priority indicator should be stored in the MME EPS Bearer contexts and should be passed as part of these contexts to other SGSN/MME or S-GW nodes in mobility management procedures. NOTE 4: In this release there is no other usage of storing the low access priority indicator in EPS Bearer contexts other than for the purpose to include it in charging records. Particularly, the low access priority indicator in EPS Bearer contexts is not used by the network to make overload control decisions. A network node may invoke one or more of the following mechanisms based on the indicators received in signalling from UEs or forwarded by other network nodes: - based on the low access priority indicator in NAS request messages, bullets e, h, i, k and l as defined in clause 4.3.17.2; and/or - based on the low access priority for RRC connection establishment, bullets b, c and q as defined in clause 4.3.17.2. A UE shall invoke one or more of the following mechanisms based on the configuration and capabilities of the UE: - when UE is configured with a long minimum periodic PLMN search time limit, the UE invokes actions as described in bullet f in clause 4.3.17.2; and/or - when UE is configured to perform Attach with IMSI at PLMN change, the UE invokes actions as described in bullet g in clause 4.3.17.2; and/or - when a UE is configured for low access priority, the UE invokes actions as described in bullets b and h in clause 4.3.17.2; and/or - when UE is configured for specific handling of the invalid USIM state, the "forbidden PLMN list", the "forbidden PLMNs for attach in S1mode list" and the "forbidden PLMNs for GPRS service list", the UE invokes actions as defined in bullet n in clause 4.3.17.2; and/or - when UE is configured for Extended Access Barring, the UE invokes actions as defined in bullet d in clause 4.3.17.2; and/or - when a UE is configured with a permission for overriding low access priority and configured with a permission for overriding Extended Access Barring, the UE invokes actions as described in bullets o) and p) in clause 4.3.17.2. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.17.4 |
3,873 | 4.3.5.4 Addition of additional PDU Session Anchor and Branching Point or UL CL | Clause 4.3.5.4 describes a procedure to add a PDU Session Anchor and a Branching Point or UL CL for an established PDU Session. Figure 4.3.5.4-1: Addition of additional PDU Session Anchor and Branching Point or UL CL 1. UE has an established PDU Session with a UPF including the PDU Session Anchor 1 (PSA1 in Figure 4.3.5.4-1). The PDU Session User Plane involves at least the (R)AN and the PDU Session Anchor 1. 2. At some point the SMF decides to establish a new PDU Session Anchor e.g. due to UE mobility, new flow detection. The SMF selects a UPF and using N4 establish the new PDU Session Anchor 2 (PSA2 in Figure 4.3.5.4-1) of the PDU Session. In the case of IPv6 multi-homing PDU Session, the SMF also ensures that a new IPv6 prefix corresponding to PSA2 is allocated and if the PCF has subscribed to the IP allocation/release event, the SMF performs the Session Management Policy Modification procedure as defined in clause 4.16.5 to provide the new allocated IPv6 prefix to the PCF. If the runtime coordination between 5GC and AF is enabled based on local configuration, according to the indication of "AF acknowledgment to be expected" is included in AF subscription to SMF events, the SMF sends an early notification to the AF after new PSA (PSA2 in Figure 4.3.5.4-1) is selected and waits for a notification response from the AF before configuring the new PSA. If the SMF receives a negative notification response from the AF, the SMF may stop the procedure. 3. The SMF selects a UPF and using N4 establish the Branching Point (in the case of IPv6 multi-homing) or a UL CL for the PDU Session. It provides the necessary uplink forwarding rules towards PSA1 and PSA2 including the PSA1 CN Tunnel Info and the PSA2 CN Tunnel Info. In addition, the AN Tunnel Info is provided for downlink forwarding. In the case of IPv6 multi-homing, the SMF also provides traffic filters for the IPv6 prefixes corresponding to PSA1 and PSA2 indicating what traffic shall be forwarded towards PSA1 and PSA2 respectively. In the case of UL CL, the SMF provides traffic filters indicating what traffic shall be forwarded towards PSA1 and PSA2 respectively. If the runtime coordination between 5GC and AF is enabled based on local configuration, according to the indication of "AF acknowledgment to be expected" is included in AF subscription to SMF events, the SMF sends a late notification to the AF and waits for a notification response from the AF before configuring the UL CL. If the SMF receives a negative notification response from the AF, the SMF may stop the procedure. NOTE 1: If the Branching Point or UL CL and the PSA2 are co-located in a single UPF then steps 2 and 3 can be merged. If a Branching Point is already allocated, step 3 is skipped. 4. The SMF updates the PSA1 via N4. It provides the Branching Point or UL CL CN Tunnel Info for the downlink traffic. NOTE 2: If the Branching Point or UL CL and the PSA1 are co-located in a single UPF then steps 3 and 4 can be merged. 5. The SMF updates PSA2 via N4. It provides the Branching Point or UL CL CN Tunnel Info for down-link traffic. NOTE 3: If the Branching Point or UL CL and the PSA2 are co-located in a single UPF then step 5 is not needed. 6. The SMF updates (R)AN via N2 SM information over N11. It provides the new CN Tunnel Info corresponding to the UPF (Branching Point or UL CL). In the case of UL CL, if there is an existing UPF between the (R)AN and new inserted UL CL, the SMF updates the existing UPF via N4 instead of updating the (R)AN. 7. In the case of IPv6 multi-homing, the SMF notifies the UE of the availability of the new IP prefix @ PSA2. This is performed using an IPv6 Router Advertisement message (RFC 4861 [6]). Also, the SMF sends IPv6 multi-homed routing rule along with the IPv6 prefix to the UE using an IPv6 Router Advertisement message (RFC 4191 [21]) as described in clause 5.8.2.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the runtime coordination between 5GC and AF is enabled based on local configuration, according to the indication of "AF acknowledgment to be expected" included in AF subscription to SMF events, the SMF sends a late notification to the AF and waits for a notification response from the AF before sending the new IP prefix to the UE. If the SMF receives a negative notification response from the AF, the SMF may stop the procedure. 8. In the case of IPv6 multi-homing, the SMF may re-configure the UE for the original IP prefix @ PSA1,i.e. SMF sends IPv6 multi-homed routing rule along with the IPv6 prefix to the UE using an IPv6 Router Advertisement message (RFC 4191 [21]) as described in clause 5.8.2.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.5.4 |
3,874 | 5.4.3.6 Abnormal cases in the UE | The following abnormal cases can be identified: a) Transmission failure of SECURITY MODE COMPLETE message or SECURITY MODE REJECT message indication from lower layers (if the security mode control procedure is triggered by a tracking area updating procedure or an attach procedure) The UE shall abort the security mode control procedure and re-initiate the tracking area updating procedure if the security mode control procedure is triggered by a tracking area updating procedure. The UE shall abort the security mode control procedure and re-initiate the attach procedure if the security mode control procedure is triggered by an attach procedure. b) Transmission failure of SECURITY MODE COMPLETE message or SECURITY MODE REJECT message indication with TAI change from lower layers (if the security mode control procedure is triggered by a service request procedure) If the current TAI is not in the TAI list, the security mode control procedure shall be aborted and a tracking area updating procedure shall be initiated. If the current TAI is still part of the TAI list, the security mode control procedure shall be aborted and it is up to the UE implementation how to re-run the ongoing procedure that triggered the security mode control procedure. c) Transmission failure of SECURITY MODE COMPLETE message or SECURITY MODE REJECT message indication without TAI change from lower layers (if the security mode control procedure is triggered by a service request procedure) The security mode control procedure shall be aborted and it is up to the UE implementation how to re-run the ongoing procedure that triggered the security mode control procedure. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.3.6 |
3,875 | 5.9 MBS Broadcast 5.9.1.1 General | UE receiving or interested to receive MBS broadcast service(s) applies MBS broadcast procedures described in this clause as well as the MBS Interest Indication procedure as specified in clause 5.9.4. MBS broadcast configuration information, except CFR configuration for MCCH/MTCH, is provided on MCCH logical channel. MCCH carries the MBSBroadcastConfiguration message which indicates the MBS broadcast sessions that are provided in the cell as well as the corresponding scheduling related information for these sessions. Optionally, the MBSBroadcastConfiguration message may also contain a list of neighbour cells providing the same broadcast MBS service(s) as provided in the current cell. The configuration information required by the UE to receive MCCH is provided in SIB1 and SIB20. Additionally, System Information may provide information related to service continuity of MBS broadcast in SIB21. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.9 |
3,876 | 5.3.5.1 Initiation of service level up- and downgrading | The procedure is initiated by the mobile station in the "active" state of the call. It shall: - send a MODIFY message including the wanted value of the "maximum number of traffic channels" and/or the "wanted air interface user rate" parameters; - not change any of the other, possibly negotiated, parameters of the bearer capability information element; - start timer T323; and - enter the "mobile originating modify" state. Any internal resources necessary to support the next service parameters shall be reserved. If a dual service was negotiated at call setup, the mobile station shall initiate the service level up- or down-grading only during the data phase of the dual service. Upon receipt of the MODIFY message, the network shall check if the indicated maximum number of traffic channels can be supported and enter the "mobile originating modify" state. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.5.1 |
3,877 | 6.3.3.3 Network-requested PDU session release procedure accepted by the UE | For a single access PDU session, upon receipt of a PDU SESSION RELEASE COMMAND message and a PDU session ID, using the NAS transport procedure as specified in subclause 5.4.5, the UE considers the PDU session as released and the UE shall create a PDU SESSION RELEASE COMPLETE message. For an MA PDU session, upon receipt of the PDU SESSION RELEASE COMMAND message, the UE shall behave as follows: a) if the PDU SESSION RELEASE COMMAND message includes the Access type IE and the MA PDU session has user-plane resources established on both 3GPP access and non-3GPP access, the UE shall consider the user-plane resources on the access indicated in the Access type IE as released and shall create a PDU SESSION RELEASE COMPLETE message. If the Access type IE indicates "3GPP access" and there is one or more multicast MBS sessions associated with the MA PDU session, the UE shall locally leave these associated multicast MBS sessions; b) if the PDU SESSION RELEASE COMMAND message includes the Access type IE and the MA PDU session has user-plane resources established on only the access indicated in the Access type IE, the UE shall consider the MA PDU session as released and shall create a PDU SESSION RELEASE COMPLETE message; and c) if the PDU SESSION RELEASE COMMAND message does not include the Access type IE, the UE shall consider the MA PDU session as released and shall create a PDU SESSION RELEASE COMPLETE message. If the UE supports network slice usage control: a) all PDU session associated with an on-demand S-NSSAI are released and there is no MA PDU session associated with this on-demand S-NSSAI, the UE shall start the slice deregistration inactivity timer for this on-demand S-NSSAI over the corresponding access type; b) all MA PDU session associated with an on-demand S-NSSAI are released and there is no PDU session associated with this on-demand S-NSSAI, the UE shall start the slice deregistration inactivity timer for this on-demand S-NSSAI over both 3GPP access and non-3GPP access; or c) all PDU session and all MA PDU session associated with an on-demand S-NSSAI are released, the UE shall start the slice deregistration inactivity timer for this on-demand S-NSSAI over both 3GPP access and non-3GPP access. If there is one or more multicast MBS sessions associated with the PDU session the UE considers as released, the UE shall locally leave these associated multicast MBS sessions. If the PDU SESSION RELEASE COMMAND message contains the PTI value allocated in the UE-requested PDU session release procedure, the UE shall stop the timer T3582. The UE should ensure that the PTI value assigned to this procedure is not released immediately. NOTE 1: The way to achieve this is implementation dependent. For example, the UE can ensure that the PTI value assigned to this procedure is not released during the time equal to or greater than the default value of timer T3592. While the PTI value is not released, the UE regards any received PDU SESSION RELEASE COMMAND message with the same PTI value as a network retransmission (see subclause 7.3.1). If the PDU SESSION RELEASE COMMAND message includes 5GSM cause #39 "reactivation requested", then after completion of the network-requested PDU session release procedure, the UE should re-initiate the UE-requested PDU session establishment procedure as specified in subclause 6.4.1 for: a) the PDU session type associated with the released PDU session; b) the SSC mode associated with the released PDU session; c) the DNN associated with the released PDU session; and d) the S-NSSAI associated with (if available in roaming scenarios) a mapped S-NSSAI if provided in the UE-requested PDU session establishment procedure of the released PDU session. If the PDU SESSION RELEASE COMMAND message contains the Alternative S-NSSAI IE, the UE shall include both the S-NSSAI to be replaced and the alternative S-NSSAI during the UE-requested PDU session establishment procedure. NOTE 2: User interaction is necessary in some cases when the UE cannot re-initiate the UE-requested PDU session establishment procedure automatically. If the PDU SESSION RELEASE COMMAND message is received without the Back-off timer value IE or includes 5GSM cause #39 "reactivation requested", and the UE provided an S-NSSAI during the PDU session establishment, the UE shall stop timer T3585 if it is running for the S-NSSAI of the PDU session. If the UE did not provide an S-NSSAI during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop the timer T3585 associated with no S-NSSAI if it is running. If the PDU SESSION RELEASE COMMAND message was received for an emergency PDU session, the UE shall not stop the timer T3585 associated with no S-NSSAI if it is running. The timer T3585 to be stopped includes: a) in a PLMN: 1) the timer T3585 applied for all the PLMNs and for the access over which the PDU SESSION RELEASE COMMAND is received, if running; 2) the timer T3585 applied for all the PLMNs and for both 3GPP access type and non-3GPP access type, if running; 3) the timer T3585 applied for the registered PLMN and for the access over which the PDU SESSION RELEASE COMMAND is received, if running; and 4) the timer T3585 applied for the registered PLMN and for both 3GPP access type and non-3GPP access type, if running; or b) in an SNPN: 1) the timer T3585 applied for all the equivalent SNPNs and for the access over which the PDU SESSION AUTHENTICATION COMMAND message is received, associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; 2) the timer T3585 applied for all the equivalent SNPNs and for both 3GPP access type and non-3GPP access type, associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; 3) the timer T3585 applied for the registered SNPN and for the access over which the PDU SESSION AUTHENTICATION COMMAND message is received, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and 4) the timer T3585 applied for the registered PLMN and for both 3GPP access type and non-3GPP access type, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. If the PDU SESSION RELEASE COMMAND message is received without the Back-off timer value IE or includes 5GSM cause #39 "reactivation requested", and the UE provided a DNN during the PDU session establishment, the UE shall stop timer T3396 if it is running for the DNN provided by the UE. If the UE did not provide a DNN during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop the timer T3396 associated with no DNN if it is running. If the PDU SESSION RELEASE COMMAND message was received for an emergency PDU session, the UE shall not stop the timer T3396 associated with no DNN if it is running. In an SNPN, the timer T3396 to be stopped includes: a) the timer T3396 applied for all the equivalent SNPNs, associated with the RSNPN or an equivalent SNPN, and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and b) the timer T3396 applied for the registered SNPN, associated with the RSNPN, and, if the UE supports access to an SNPN using credentials from a credentials holder, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. If the PDU SESSION RELEASE COMMAND message is received without the Back-off timer value IE or includes 5GSM cause #39 "reactivation requested", and the UE provided an S-NSSAI and a DNN during the PDU session establishment, the UE shall stop timer T3584 if it is running for the [S-NSSAI of the PDU session, DNN] combination provided by the UE. If the UE did not provide an S-NSSAI during the PDU session establishment, the UE shall stop the timer T3584 associated with [no S-NSSAI, DNN] if it is running. If the UE did not provide a DNN during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop the timer T3584 associated with [S-NSSAI of the PDU session, no DNN] combination, if it is running. If the PDU SESSION RELEASE COMMAND message was received for an emergency PDU session, the UE shall not stop the timer T3584 associated with [S-NSSAI of the PDU session, no DNN] if it is running. If the UE provided neither a DNN nor an S-NSSAI during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop the timer T3584 associated with [no S-NSSAI, no DNN] if it is running. If the PDU SESSION RELEASE COMMAND message was received for an emergency PDU session, the UE shall not stop the timer T3584 associated with [no S-NSSAI, no DNN] if it is running. The timer T3584 to be stopped includes: a) in a PLMN: 1) the timer T3584 applied for all the PLMNs, if running; and 2) the timer T3584 applied for the registered PLMN, if running; or b) in an SNPN: 1) the timer T3584 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and 2) the timer T3584 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. NOTE 3: If the PDU SESSION RELEASE COMMAND message is received without the Back-off timer value IE or includes 5GSM cause #39 "reactivation requested" for a PDU session, the UE provided a DNN (or no DNN) and an S-NSSAI (or no S-NSSAI) when the PDU session is established, timer T3396 associated with the DNN (or no DNN, if no DNN was provided by the UE) is running, and timer T3584 associated with the DNN (or no DNN, if no DNN was provided by the UE) and the S-NSSAI of the PDU session (or no S-NSSAI, if no S-NSSAI was provided by the UE) is running, then the UE stops both the timer T3396 and the timer T3584. NOTE 4: If the PDU SESSION RELEASE COMMAND message is received without the Back-off timer value IE or includes 5GSM cause #39 "reactivation requested" for a PDU session, the UE provided a DNN (or no DNN) and an S-NSSAI of the PDU session (or no S-NSSAI) when the PDU session is established, timer T3585 associated with the S-NSSAI of the PDU session (or no S-NSSAI, if no S-NSSAI was provided by the UE) is running, and timer T3584 associated with the DNN (or no DNN, if no DNN was provided by the UE) and the S-NSSAI of the PDU session (or no S-NSSAI, if no S-NSSAI was provided by the UE) is running, then the UE stops both the timer T3585 and the timer T3584. If the PDU SESSION RELEASE COMMAND message includes 5GSM cause #26 "insufficient resources" and the Back-off timer value IE, the UE shall ignore the 5GSM congestion re-attempt indicator IE provided by the network, if any, and the UE shall take different actions depending on the timer value received for timer T3396 in the Back-off timer value: a) If the timer value indicates neither zero nor deactivated and a DNN was provided during the PDU session establishment, the UE shall stop timer T3396 associated with the corresponding DNN, if it is running. If the timer value indicates neither zero nor deactivated and no DNN was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop timer T3396 associated with no DNN if it is running. In an SNPN, the timer T3396 to be stopped includes: 1) the timer T3396 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and 2) the timer T3396 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE shall then start timer T3396 with the value provided in the Back-off timer value IE and: 1) shall not send a PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the same DNN that was sent by the UE, until timer T3396 expires or timer T3396 is stopped; and 2) shall not send a PDU SESSION ESTABLISHMENT REQUEST message without an DNN and with request type different from "initial emergency request" and different from "existing emergency PDU session", or a PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for a non-emergency PDU session established without an DNN provided by the UE, if no DNN was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", until timer T3396 expires or timer T3396 is stopped. The UE shall not stop timer T3396 upon a PLMN change, SNPN change, or inter-system change; b) if the timer value indicates that this timer is deactivated and a DNN was provided during the PDU session establishment, the UE shall stop timer T3396 associated with the corresponding DNN, if it is running. If the timer value indicates that this timer is deactivated and no DNN was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop timer T3396 associated with no DNN if it is running. In an SNPN, the timer T3396 to be stopped includes: 1) the timer T3396 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and 2) the timer T3396 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE: 1) shall not send a PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the same DNN until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated, or the UE receives a PDU SESSION MODIFICATION COMMAND message for the same DNN from the network, or a PDU SESSION AUTHENTICATION COMMAND message for the same DNN, or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE or including 5GSM cause #39 "reactivation requested" for the same DNN from the network; and 2) shall not send a PDU SESSION ESTABLISHMENT REQUEST message without a DNN and with request type different from "initial emergency request" and different from "existing emergency PDU session", or a PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for a non-emergency PDU session established without a DNN provided by the UE, if no DNN was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated, or the UE receives a PDU SESSION MODIFICATION COMMAND message for a non-emergency PDU session established without an DNN provided by the UE, or a PDU SESSION AUTHENTICATION COMMAND message for a non-emergency PDU session established without a DNN provided by the UE, or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE or including 5GSM cause #39 "reactivation requested" for a non-emergency PDU session established without a DNN provided by the UE. The timer T3396 remains deactivated upon a PLMN change, SNPN change, or inter-system change; and c) if the timer value indicates zero, the UE: 1) shall stop timer T3396 associated with the corresponding DNN, if running. In an SNPN, the timer T3396 to be stopped includes: i) the timer T3396 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and ii) the timer T3396 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE may send a PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message for the same DNN; and 2) if no DNN was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop timer T3396 associated with no DNN, if running. In an SNPN, the timer T3396 to be stopped includes: i) the timer T3396 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and ii) the timer T3396 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE may send a PDU SESSION ESTABLISHMENT REQUEST message without a DNN, or a PDU SESSION MODIFICATION REQUEST message without an DNN provided by the UE. In an SNPN, if the UE supports equivalent SNPNs, then the UE shall apply the timer T3396 for all the equivalent SNPNs. Otherwise, the UE shall apply the timer T3396 for the registered SNPN. If the PDU SESSION RELEASE COMMAND message includes 5GSM cause #26 "insufficient resources" and the Back-off timer value IE is not included, then the UE may send a PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message for the same DNN or without a DNN. When the timer T3396 is running or the timer is deactivated, the UE is allowed to initiate a PDU session establishment procedure for emergency services. If the timer T3396 is running when the UE enters state 5GMM-DEREGISTERED, the UE remains switched on, and the USIM in the UE (if any) remains the same and the entry in the "list of subscriber data" for the SNPN to which timer T3396 is associated (if any) is not updated, then timer T3396 is kept running until it expires or it is stopped. If the UE is switched off when the timer T3396 is running, and if the USIM in the UE (if any) remains the same and the entry in the "list of subscriber data" for the SNPN to which timer T3396 is associated (if any) is not updated when the UE is switched on, the UE shall behave 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 UE is not capable of determining t, then the UE shall restart the timer with the value t1. If the 5GSM cause value is #39 "reactivation requested", the UE shall ignore the Back-off timer value IE provided by the network, if any. If the 5GSM cause value is #67 "insufficient resources for specific slice and DNN" and the Back-off timer value IE is included, the UE shall take different actions depending on the timer value received for timer T3584 in the Back-off timer value: a) If the timer value indicates neither zero nor deactivated, and both an S-NSSAI and a DNN were provided by the UE during the PDU session establishment the UE shall stop timer T3584 associated with the [S-NSSAI of the PDU session, DNN] combination, if it is running. If the timer value indicates neither zero nor deactivated, an S-NSSAI and no DNN was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop timer T3584 associated with [S-NSSAI of the PDU session, no DNN] combination, if it is running. If the timer value indicates neither zero nor deactivated, no S-NSSAI and a DNN was provided during the PDU session establishment, the UE shall stop timer T3584 associated with the [no S-NSSAI, DNN] combination, if it is running. If the timer value indicates neither zero nor deactivated and neither S-NSSAI nor DNN was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop timer T3584 associated with the [no S-NSSAI, no DNN] combination, if it is running. The timer T3584 to be stopped includes: 1) in a PLMN: i) the timer T3584 applied for all the PLMNs, if running; and ii) the timer T3584 applied for the registered PLMN, if running; or 2) in an SNPN: i) the timer T3584 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and ii) the timer T3584 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE shall then start timer T3584 with the value provided in the Back-off timer value IE. 1) The UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message with request type different from "initial emergency request" and different from "existing emergency PDU session", or PDU SESSION MODIFICATION REQUEST message with the exception of those identified in subclause 6.4.2.1, for the [S-NSSAI of the PDU session, DNN] combination, until timer T3584 expires or timer T3584 is stopped; 2) shall not send another PDU SESSION ESTABLISHMENT REQUEST message with request type different from "initial emergency request" and different from "existing emergency PDU session", or another PDU SESSION MODIFICATION REQUEST message with the exception of those identified in subclause 6.4.2.1, for the [S-NSSAI of the PDU session, no DNN] combination, if no DNN was provided during the PDU session establishment, until timer T3584 expires or timer T3584 is stopped; 3) shall not send another PDU SESSION ESTABLISHMENT REQUEST message, or another PDU SESSION MODIFICATION REQUEST message with the exception of those identified in subclause 6.4.2.1, for the same [no S-NSSAI, DNN] combination, if no S-NSSAI was provided during the PDU session establishment, until timer T3584 expires or timer T3584 is stopped; and 4) shall not send another PDU SESSION ESTABLISHMENT REQUEST message with request type different from "initial emergency request" and different from "existing emergency PDU session", or another PDU SESSION MODIFICATION REQUEST message with the exception of those identified in subclause 6.4.2.1, for the same [no S-NSSAI, no DNN] combination, if neither S-NSSAI nor DNN was provided during the PDU session establishment, until timer T3584 expires or timer T3584 is stopped. The UE shall not stop timer T3584 upon a PLMN change, SNPN change, or inter-system change; b) if the timer value indicates that this timer is deactivated: 1) if both S-NSSAI and DNN were provided by the UE during the PDU session establishment, the UE shall stop timer T3584 associated with the [S-NSSAI of the PDU session, DNN] combination, if running. The timer T3584 to be stopped includes: i) in a PLMN: A) the timer T3584 applied for all the PLMNs, if running; and B) the timer T3584 applied for the registered PLMN, if running; or ii) in an SNPN: A) the timer T3584 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and B) the timer T3584 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message with request type different from "initial emergency request" and different from "existing emergency PDU session", or PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the [S-NSSAI of the PDU session, DNN] combination that was sent by the UE, until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated, or the UE receives a PDU SESSION MODIFICATION COMMAND message for the [S-NSSAI of the PDU session, DNN] combination from the network, or a PDU SESSION AUTHENTICATION COMMAND message for the [S-NSSAI of the PDU session, DNN] combination from the network, or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE or including 5GSM cause #39 "reactivation requested" for the [S-NSSAI of the PDU session, DNN] combination from the network; 2) if an S-NSSAI was provided but a DNN was not provided by the UE during the PDU session establishment, the UE shall stop timer T3584 associated with the [S-NSSAI of the PDU session, no DNN] combination, if running. The timer T3584 to be stopped includes: i) in a PLMN: A) the timer T3584 applied for all the PLMNs, if running; and B) the timer T3584 applied for the registered PLMN, if running; or ii) in an SNPN: A) the timer T3584 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and B) the timer T3584 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE shall not send a PDU SESSION ESTABLISHMENT REQUEST message with request type different from "initial emergency request" and different from "existing emergency PDU session", or a PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the [S-NSSAI of the PDU session, no DNN] combination, if no DNN was provided during the PDU session establishment, until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated, or the UE receives an PDU SESSION MODIFICATION COMMAND message for a non-emergency PDU session established for the [S-NSSAI of the PDU session, no DNN] combination from the network, or a PDU SESSION AUTHENTICATION COMMAND message for a non-emergency PDU session established the [S-NSSAI of the PDU session, DNN] combination from the network, or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE or including 5GSM cause #39 "reactivation requested" for a non-emergency PDU session established for the [S-NSSAI of the PDU session, no DNN] combination from the network; 3) if an S-NSSAI was not provided but a DNN was provided by the UE during the PDU session establishment, the UE shall stop timer T3584 associated with the [no S-NSSAI, DNN] combination, if running. The timer T3584 to be stopped includes: i) in a PLMN: A) the timer T3584 applied for all the PLMNs, if running; and B) the timer T3584 applied for the registered PLMN, if running; or ii) in an SNPN: A) the timer T3584 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and B) the timer T3584 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE shall not send a PDU SESSION ESTABLISHMENT REQUEST message, or a PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the [no S-NSSAI, DNN], if no S-NSSAI was provided during the PDU session establishment, until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated, or the UE receives an PDU SESSION MODIFICATION COMMAND message for the [no S-NSSAI, DNN] combination from the network, or a PDU SESSION AUTHENTICATION COMMAND message for the [no S-NSSAI, DNN] combination from the network, or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE or including 5GSM cause #39 "reactivation requested" for the same [no S-NSSAI, DNN] combination from the network; and 4) if neither S-NSSAI nor DNN were provided by the UE during the PDU session establishment, the UE shall stop timer T3584 associated with the [no S-NSSAI, no DNN] combination, if running. The timer T3584 to be stopped includes: i) in a PLMN: A) the timer T3584 applied for all the PLMNs, if running; and B) the timer T3584 applied for the registered PLMN, if running; or ii) in an SNPN: A) the timer T3584 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and B) the timer T3584 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE shall not send a PDU SESSION ESTABLISHMENT REQUEST message with request type different from "initial emergency request" and different from "existing emergency PDU session", or a PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the [no S-NSSAI, no DNN] combination, if neither S-NSSAI nor DNN was provided during the PDU session establishment, until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated, or the UE receives an PDU SESSION MODIFICATION COMMAND message for a non-emergency PDU session established for the [no S-NSSAI, no DNN] combination from the network, or a PDU SESSION AUTHENTICATION COMMAND message for a non-emergency PDU session established for the [no S-NSSAI, no DNN] combination from the network or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE or including 5GSM cause #39 "reactivation requested" for a non-emergency PDU session established for the [no S-NSSAI, no DNN] combination from the network. The timer T3584 remains deactivated upon a PLMN change, SNPN change, or inter-system change; and c) if the timer value indicates zero: 1) if both S-NSSAI and DNN were provided by the UE during the PDU session establishment, the UE shall stop timer T3584 associated with the [S-NSSAI of the PDU session, DNN] combination, if running. The timer T3584 to be stopped includes: i) in a PLMN: A) the timer T3584 applied for all the PLMNs, if running; and B) the timer T3584 applied for the registered PLMN, if running; or ii) in an SNPN: A) the timer T3584 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and B) the timer T3584 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE may send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message for the [S-NSSAI of the PDU session, DNN] combination; 2) if an S-NSSAI was provided but a DNN was not provided by the UE during the PDU session establishment, the UE shall stop timer T3584 associated with the [S-NSSAI of the PDU session, no DNN] combination, if running. The timer T3584 to be stopped includes: i) in a PLMN: A) the timer T3584 applied for all the PLMNs, if running; and B) the timer T3584 applied for the registered PLMN, if running; or ii) in an SNPN: A) the timer T3584 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and B) the timer T3584 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE may send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message for the [S-NSSAI of the PDU session, no DNN] combination if the request type was different from "initial emergency request" and different from "existing emergency PDU session"; 3) if an S-NSSAI was not provided but a DNN was provided by the UE during the PDU session establishment, the UE shall stop timer T3584 associated with the [no S-NSSAI, DNN] combination, if running. The timer T3584 to be stopped includes: i) in a PLMN: A) the timer T3584 applied for all the PLMNs, if running; and B) the timer T3584 applied for the registered PLMN, if running; or ii) in an SNPN: A) the timer T3584 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and B) the timer T3584 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE may send another PDU SESSION ESTABLISHMENT REQUEST message, or PDU SESSION MODIFICATION REQUEST message for the [no S-NSSAI, DNN] combination; and 4) if neither S-NSSAI nor DNN were provided by the UE during the PDU session establishment, the UE shall stop timer T3584 associated with the [no S-NSSAI, no DNN] combination, if running. The timer T3584 to be stopped includes: i) in a PLMN: A) the timer T3584 applied for all the PLMNs, if running; and B) the timer T3584 applied for the registered PLMN, if running; or ii) in an SNPN: A) the timer T3584 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and B) the timer T3584 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE may send another PDU SESSION ESTABLISHMENT REQUEST message, or PDU SESSION MODIFICATION REQUEST message for the [no S-NSSAI, no DNN] combination if the request type was different from "initial emergency request" and different from "existing emergency PDU session". If the 5GSM congestion re-attempt indicator IE with the ABO bit set to "The back-off timer is applied in all PLMNs or all equivalent SNPNs " is included in the PDU SESSION RELEASE COMMAND message with the 5GSM cause value #67 "insufficient resources for specific slice and DNN", then the UE shall apply the timer T3584 for all the PLMNs or all the equivalent SNPNs. Otherwise, the UE shall apply the timer T3584 for the registered PLMN or the registered SNPN. If the 5GSM cause value is #67 "insufficient resources for specific slice and DNN" and the Back-off timer value IE is not included, then the UE may send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message for the same [S-NSSAI, DNN] combination. When the timer T3584 is running or the timer is deactivated, the UE is allowed to initiate a PDU session establishment procedure for emergency services. If the timer T3584 is running when the UE enters state 5GMM-DEREGISTERED, the UE remains switched on, and the USIM in the UE (if any) remains the same and the entry in the "list of subscriber data" for the SNPN to which timer T3584 is associated (if any) is not updated, then timer T3584 is kept running until it expires or it is stopped. If the UE is switched off when the timer T3584 is running, and if the USIM in the UE (if any) remains the same and the entry in the "list of subscriber data" for the SNPN to which timer T3584 is associated (if any) is not updated when the UE is switched on, the UE shall behave as follows: - let t1 be the time remaining for T3584 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 UE is not capable of determining t, then the UE shall restart the timer with the value t1. If the 5GSM cause value is #69 "insufficient resources for specific slice" and the Back-off timer value IE is included, the UE shall take different actions depending on the timer value received for timer T3585 in the Back-off timer value: a) If the timer value indicates neither zero nor deactivated and an S-NSSAI was provided during the PDU session establishment, the UE shall stop timer T3585 associated with the S-NSSAI of the PDU session, if it is running. If the timer value indicates neither zero nor deactivated and no S-NSSAI was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop timer T3585 associated with no S-NSSAI if it is running. The timer T3585 to be stopped includes: 1) in a PLMN: i) the timer T3585 applied for all the PLMNs and for the access over which the PDU SESSION RELEASE COMMAND is received, if running; ii) the timer T3585 applied for all the PLMNs and for both 3GPP access type and non-3GPP access type, if running; iii) the timer T3585 applied for the registered PLMN and for the access over which the PDU SESSION RELEASE COMMAND is received, if running; and iv) the timer T3585 applied for the registered PLMN and for both 3GPP access type and non-3GPP access type, if running; or 2) in an SNPN: i) the timer T3585 applied for all the equivalent SNPNs and for the access over which the PDU SESSION AUTHENTICATION COMMAND message is received, associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; ii) the timer T3585 applied for all the equivalent SNPNs and for both 3GPP access type and non-3GPP access type, associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; iii) the timer T3585 applied for the registered SNPN and for the access over which the PDU SESSION AUTHENTICATION COMMAND message is received, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and iv) the timer T3585 applied for the registered PLMN and for both 3GPP access type and non-3GPP access type, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE shall then start timer T3585 with the value provided in the Back-off timer value IE and: 1) if an S-NSSAI was provided by the UE during the PDU session establishment, the UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message, or PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the S-NSSAI of the PDU session, until timer T3585 expires or timer T3585 is stopped; and 2) if the request type was different from "initial emergency request" and from "existing emergency PDU session", and an S-NSSAI was not provided by the UE during the PDU session establishment, the UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message without an S-NSSAI and with request type different from "initial emergency request" and different from "existing emergency PDU session", or another PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for a non-emergency PDU session established without an S-NSSAI provided by the UE, until timer T3585 expires or timer T3585 is stopped. The UE shall not stop timer T3585 upon a PLMN change, SNPN change, or inter-system change; b) if the timer value indicates that this timer is deactivated and an S-NSSAI was provided during the PDU session establishment, the UE shall stop timer T3585 associated with the S-NSSAI of the PDU session, if it is running. If the timer value indicates that this timer is deactivated and no S-NSSAI was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop timer T3585 associated with no S-NSSAI if it is running. The timer T3585 to be stopped includes: 1) in a PLMN: i) the timer T3585 applied for all the PLMNs and for the access over which the PDU SESSION RELEASE COMMAND is received, if running; ii) the timer T3585 applied for all the PLMNs and for both 3GPP access type and non-3GPP access type, if running; iii) the timer T3585 applied for the registered PLMN and for current access type or both 3GPP access type and non-3GPP access type, if running; and iv) the timer T3585 applied for the registered PLMN and for both 3GPP access type and non-3GPP access type, if running; or 2) in an SNPN: i) the timer T3585 applied for all the equivalent SNPNs and for the access over which the PDU SESSION AUTHENTICATION COMMAND message is received, associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; ii) the timer T3585 applied for all the equivalent SNPNs and for both 3GPP access type and non-3GPP access type, associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; iii) the timer T3585 applied for the registered SNPN and for the access over which the PDU SESSION AUTHENTICATION COMMAND message is received, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and iv) the timer T3585 applied for the registered PLMN and for both 3GPP access type and non-3GPP access type, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. In addition: 1) if an S-NSSAI was provided by the UE during the PDU session establishment, the UE shall not send another PDU SESSION ESTABLISHMENT REQUEST, or PDU SESSION MODIFICATION REQUEST with exception of those identified in subclause 6.4.2.1, for the S-NSSAI of the PDU session until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated, or a PDU SESSION MODIFICATION COMMAND message for the S-NSSAI of the PDU session from the network, or a PDU SESSION AUTHENTICATION COMMAND message for the S-NSSAI of the PDU session from the network, or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE or including 5GSM cause #39 "reactivation requested" for the S-NSSAI of the PDU session from the network; and 2) if the request type was different from "initial emergency request" and from "existing emergency PDU session", and an S-NSSAI was not provided by the UE during the PDU session establishment, the UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message without an S-NSSAI and with request type different from "initial emergency request" and different from "existing emergency PDU session", or another PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for a non-emergency PDU session established without an S-NSSAI provided by the UE, until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated, or a PDU SESSION MODIFICATION COMMAND message for a non-emergency PDU session established without an S-NSSAI provided by the UE, or a PDU SESSION AUTHENTICATION COMMAND message for a non-emergency PDU session established without an S-NSSAI provided by the UE, or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE or including 5GSM cause #39 "reactivation requested" for a non-emergency PDU session established without an S-NSSAI provided by the UE. The timer T3585 remains deactivated upon a PLMN change, SNPN change, or inter-system change; and c) if the timer value indicates zero: 1) if an S-NSSAI was provided by the UE during the PDU session establishment, the UE shall stop timer T3585 associated with the S-NSSAI of the PDU session, if running. The timer T3585 to be stopped includes: i) in a PLMN: A) the timer T3585 applied for all the PLMNs and for the access over which the PDU SESSION RELEASE COMMAND is received, if running; B) the timer T3585 applied for all the PLMNs and for the access over which the PDU SESSION RELEASE COMMAND is received, if running; C) the timer T3585 applied for the registered PLMN and for current access type or both 3GPP access type and non-3GPP access type, if running; and D) the timer T3585 applied for the registered PLMN and for both 3GPP access type and non-3GPP access type, if running; or ii) in an SNPN: A) the timer T3585 applied for all the equivalent SNPNs and for the access over which the PDU SESSION AUTHENTICATION COMMAND message is received, associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; B) the timer T3585 applied for all the equivalent SNPNs and for both 3GPP access type and non-3GPP access type, associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; C) the timer T3585 applied for the registered SNPN and for the access over which the PDU SESSION AUTHENTICATION COMMAND message is received, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and D) the timer T3585 applied for the registered PLMN and for both 3GPP access type and non-3GPP access type, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE may send another PDU SESSION ESTABLISHMENT REQUEST, or PDU SESSION MODIFICATION REQUEST message for the S-NSSAI of the PDU session; and 2) if no S-NSSAI was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop timer T3585 associated with no S-NSSAI i) in a PLMN: A) the timer T3585 applied for all the PLMNs and for the access over which the PDU SESSION RELEASE COMMAND is received, if running,; B) the timer T3585 applied for all the PLMNs and for the access over which the PDU SESSION RELEASE COMMAND is received, if running; C) the timer T3585 applied for the registered PLMN and for current access type or both 3GPP access type and non-3GPP access type, if running; and D) the timer T3585 applied for the registered PLMN and for both 3GPP access type and non-3GPP access type, if running; or ii) in an SNPN: A) the timer T3585 applied for all the equivalent SNPNs and for the access over which the PDU SESSION AUTHENTICATION COMMAND message is received, associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; B) the timer T3585 applied for all the equivalent SNPNs and for both 3GPP access type and non-3GPP access type, associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; C) the timer T3585 applied for the registered SNPN and for the access over which the PDU SESSION AUTHENTICATION COMMAND message is received, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and D) the timer T3585 applied for the registered PLMN and for both 3GPP access type and non-3GPP access type, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE may send another PDU SESSION ESTABLISHMENT REQUEST message without an S-NSSAI, or another PDU SESSION MODIFICATION REQUEST message without an S-NSSAI provided by the UE. If the 5GSM congestion re-attempt indicator IE with the ABO bit set to "The back-off timer is applied in all PLMNs or all equivalent SNPNs " is included in the PDU SESSION RELEASE COMMAND message with the 5GSM cause value #69 "insufficient resources for specific slice", then the UE shall apply the timer T3585 for all the PLMNs or all the equivalent SNPNs. Otherwise, the UE shall apply the timer T3585 for the registered PLMN or the registered SNPN. If the 5GSM cause value is #69 "insufficient resources for specific slice" and the Back-off timer value IE is not included, then the UE may send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message for the same S-NSSAI or without an S-NSSAI. When the timer T3585 is running or the timer is deactivated, the UE is allowed to initiate a PDU session establishment procedure for emergency services. If the timer T3585 is running when the UE enters state 5GMM-DEREGISTERED, the UE remains switched on, and the USIM in the UE (if any) remains the same and the entry in the "list of subscriber data" for the SNPN to which timer T3585 is associated (if any) is not updated, then timer T3585 is kept running until it expires or it is stopped. If the UE is switched off when the timer T3585 is running, and if the USIM in the UE (if any) remains the same and the entry in the "list of subscriber data" for the SNPN to which timer T3585 is associated (if any) is not updated when the UE is switched on, the UE shall behave as follows: - let t1 be the time remaining for T3585 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 UE is not capable of determining t, then the UE shall restart the timer with the value t1. NOTE 5: As described in this subclause, upon PLMN change, SNPN change or inter-system change, the UE does not stop the timer T3584 or T3585. This means the timer T3584 or T3585 can still be running or be deactivated for the given 5GSM procedure, the PLMN or SNPN, the S-NSSAI and optionally the DNN combination when the UE returns to the PLMN or SNPN or when it performs inter-system change back from S1 mode to N1 mode. Thus the UE can still be prevented from sending another PDU SESSION ESTABLISHMENT REQUEST or PDU SESSION MODIFICATION REQUEST message in the PLMN for the same S-NSSAI and optionally the same DNN. Upon PLMN change or SNPN change, if T3584 applied for the registered PLMN or the registered SNPN is running or is deactivated for an S-NSSAI, a DNN, and old PLMN or old SNPN, but T3584 is not running and is not deactivated for the S-NSSAI, the DNN, and new PLMN or new SNPN, then the UE is allowed to send a PDU SESSION ESTABLISHMENT REQUEST message for the same S-NSSAI and the same DNN in the new PLMN or new SNPN. Upon PLMN change or SNPN change, if T3585 applied for the registered PLMN or the registered SNPN is running or is deactivated for an S-NSSAI and old PLMN or old SNPN, but T3585 is not running and is not deactivated for the S-NSSAI and new PLMN or new SNPN, then the UE is allowed to send a PDU SESSION ESTABLISHMENT REQUEST message for the same S-NSSAI in the new PLMN or new SNPN. Upon SNPN change, if T3584 applied for all the equivalent SNPNs is running or is deactivated for an S-NSSAI, a DNN, and old SNPN, but T3584 is not running and is not deactivated for the S-NSSAI, the DNN, and new non-equivalent SNPN, then the UE is allowed to send a PDU SESSION ESTABLISHMENT REQUEST message for the same S-NSSAI and the same DNN in the new SNPN. Upon SNPN change, if T3585 applied for all the equivalent SNPNs is running or is deactivated for an S-NSSAI and old SNPN, but T3585 is not running and is not deactivated for the S-NSSAI and new non-equivalent SNPN, then the UE is allowed to send a PDU SESSION ESTABLISHMENT REQUEST message for the same S-NSSAI in the new SNPN. If the PDU SESSION RELEASE COMMAND message includes 5GSM cause #29 "user authentication or authorization failed" and the Back-off timer value IE, the UE shall behave as follows: a) if the timer value indicates neither zero nor deactivated and: 1) if the UE provided a DNN and S-NSSAI to the network during the PDU session establishment, the UE shall start the back-off timer with the value provided in the Back-off timer value IE for the PDU session establishment procedure and: i) in a PLMN, [PLMN, DNN, (mapped) HPLMN S-NSSAI] combination. The UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for the same DNN and (mapped) HPLMN S-NSSAI in the current PLMN, until the back-off timer expires, the UE is switched off, or the USIM is removed; or ii) in an SNPN, [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, (mapped) subscribed SNPN S-NSSAI] combination. The UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for the same DNN and (mapped) subscribed SNPN S-NSSAI in the current SNPN using the selected entry of the "list of subscriber data" or selected PLMN subscription, until the back-off timer expires, the UE is switched off, the USIM is removed, or the selected entry of the "list of subscriber data" is updated; 2) if the UE provided a DNN to the network during the PDU session establishment, the UE shall start the back-off timer with the value provided in the Back-off timer value IE for the PDU session establishment procedure and: i) in a PLMN, [PLMN, DNN] combination. The UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for the same DNN in the current PLMN, until the back-off timer expires, the UE is switched off, or the USIM is removed; or ii) in an SNPN, [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN] combination. The UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for the same DNN in the current PLMN using the selected entry of the "list of subscriber data" or selected PLMN subscription, until the back-off timer expires, the UE is switched off, the USIM is removed or the selected entry of the "list of subscriber data" is updated; 3) if the UE did not provide a DNN or S-NSSAI or any of the two parameters to the network during the PDU session establishment, it shall start the back-off timer accordingly for the PDU session establishment procedure and: i) in a PLMN, the [PLMN, DNN, no S-NSSAI], [PLMN, no DNN, (mapped) HPLMN S-NSSAI] or [PLMN, no DNN, no S-NSSAI] combination. Dependent on the combination, the UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for the same [PLMN, DNN, no S-NSSAI], [PLMN, no DNN, (mapped) HPLMN S-NSSAI] or [PLMN, no DNN, no S-NSSAI] combination in the current PLMN, until the back-off timer expires, the UE is switched off, or the USIM is removed; or ii) in an SNPN, [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, no S-NSSAI], [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, (mapped) subscribed SNPN S-NSSAI] or [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, no S-NSSAI] combination. Dependent on the combination, the UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for the same [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, no S-NSSAI], [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, (mapped) subscribed SNPN S-NSSAI] or [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, no S-NSSAI] combination in the current PLMN using the selected entry of the "list of subscriber data" or selected PLMN subscription, until the back-off timer expires, the UE is switched off, the USIM is removed or the selected entry of the "list of subscriber data" is updated; or 4) if the UE did not provide a DNN to the network during the PDU session establishment, it shall start the back-off timer accordingly for the PDU session establishment procedure and: i) in a PLMN, the [PLMN, no DNN] combination. The UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for the same [PLMN, no DNN] in the current PLMN, until the back-off timer expires, the UE is switched off, or the USIM is removed; or ii) in an SNPN, [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN] combination. The UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for the same [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN] in the current SNPN using the selected entry of the "list of subscriber data" or selected PLMN subscription, until the back-off timer expires, the UE is switched off, the USIM is removed, or the selected entry of the "list of subscriber data" is updated; b) if the timer value indicates that this timer is deactivated and: 1) if the UE provided a DNN and S-NSSAI to the network during the PDU session establishment, the UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for: i) in a PLMN, the same DNN and (mapped) HPLMN S-NSSAI in the current PLMN, until the UE is switched off, or the USIM is removed; or ii) in an SNPN, the same DNN and (mapped) subscribed SNPN S-NSSAI in the current SNPN using the selected entry of the "list of subscriber data" or selected PLMN subscription, until the UE is switched off, or the USIM is removed, or the selected entry of the "list of subscriber data" is updated; 2) if the UE provided a DNN to the network during the PDU session establishment, the UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for: i) in a PLMN, the same DNN in the current PLMN, until the UE is switched off, or the USIM is removed; or ii) in an SNPN, the same DNN in the current SNPN using the selected entry of the "list of subscriber data" or selected PLMN subscription, until the UE is switched off, or the USIM is removed, or the selected entry of the "list of subscriber data" is updated; 3) if the UE did not provide a DNN or S-NSSAI or any of the two parameters to the network during the PDU session establishment, the UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for: i) in a PLMN, the same [PLMN, DNN, no S-NSSAI], [PLMN, no DNN, (mapped) HPLMN S-NSSAI] or [PLMN, no DNN, no S-NSSAI] combination in the current PLMN, until the UE is switched off, or the USIM is removed; or ii) in an SNPN, the same [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, no S-NSSAI], [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, (mapped) subscribed SNPN S-NSSAI] or [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, no S-NSSAI] combination in the current SNPN using the selected entry of the "list of subscriber data" or selected PLMN subscription, until the UE is switched off, or the USIM is removed, or the selected entry of the "list of subscriber data" is updated; or 4) if the UE did not provide a DNN to the network during the PDU session establishment, the UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for: i) in a PLMN, the same [PLMN, no DNN] in the current PLMN, until the UE is switched off, or the USIM is removed; or ii) in an SNPN, the same [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN] combination in the current SNPN using the selected entry of the "list of subscriber data" or selected PLMN subscription, until the UE is switched off, or the USIM is removed, or the selected entry of the "list of subscriber data" is updated; and c) if the timer value indicates zero, the UE may send another PDU SESSION ESTABLISHMENT REQUEST message: 1) in a PLMN, for the same combination of [PLMN, DNN, (mapped) HPLMN S-NSSAI], [PLMN, DNN, no S-NSSAI], [PLMN, no DNN, (mapped) HPLMN S-NSSAI], or [PLMN, no DNN, no S-NSSAI] in the current PLMN; or 2) in an SNPN, for the same combination of [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, (mapped) subscribed SNPN S-NSSAI], [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, no S-NSSAI], [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, (mapped) subscribed SNPN S-NSSAI], or [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, no S-NSSAI] in the current SNPN. The UE shall not stop any back-off timer: a) upon a PLMN or SNPN change; b) upon an inter-system change; or c) upon registration over another access type. If the PDU SESSION RELEASE COMMAND message includes: a) 5GSM cause #29 "user authentication or authorization failed"; and b) the service-level-AA response in the Service-level-AA container IE with the SLAR field set to the value of "Service level authentication and authorization was not successful or service level authorization is revoked", the UE shall forward the service-level-AA response to the upper layers, so the UUAA authorization data is deleted as specified in 3GPP TS 33.256[ Security aspects of Uncrewed Aerial Systems (UAS) ] [24B]. The UE shall transport the PDU SESSION RELEASE COMPLETE message and the PDU session ID, using the NAS transport procedure as specified in subclause 5.4.5. Upon receipt of a PDU SESSION RELEASE COMPLETE message, the SMF shall stop timer T3592 and shall consider the PDU session as released. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.3.3.3 |
3,878 | G.4.1 Service Registration and Service Discovery | Service registration can be done in several ways. One option is that ready 5GC Service Functions may register themselves with their service profile via the Nnrf interface. The registration request is forwarded to the internal Registry as well as forwarded to the operator's NRF. The internal registration is used to store the address to identifier relationship and the Service Deployment Cluster location. The external registration (NRF) is used to expose the Service Functionality to Services outside the depicted SCP. Service discovery entails Function A requesting a resolvable identifier for Functionality B. This resolve request is received by the Service Router which performs the task with the help of the SCP. After the resolve is done, the 5GC Functionalities may communicate either directly without any further interaction through the SCP, when the targeted address is resolved within the same Service Deployment Cluster; or via the Service Router when the Functionality resides outside of the originator's Service Deployment Cluster. The Service Router then acts as gateway towards the underlying SCP platform. Figure G.4.1-1: Registering 5GC Functionalities in the SCP | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | G.4.1 |
3,879 | 4.15.9.2 Exposure of UE availability for Time Synchronization service | The procedure is used by the AF to subscribe to notifications and to explicitly cancel a previous subscription for UE availability for time synchronization service. Cancelling is done by sending Nnef_TimeSynchronization_CapsUnsubscribe request identifying the subscription to cancel with Subscription Correlation ID. Figure 4.15.9.2-1: Procedure for exposing 5GS and/or UE availability and capabilities for Time Synchronization services 1. Upon PDU Session establishment, the PCF determines if the PDU Session is potentially impacted by time synchronization service (based on local configuration or 5GS Bridge/Router information event from SMF as described in SM Policy Association Establishment procedure in clause 4.16.4). In this case the PCF invokes Npcf_PolicyAuthorization_Notify service operation to the TSCTSF discovered and selected as described in clause 6.3.24 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The Npcf_PolicyAuthorization_Notify service operation includes the UE address of the PDU Session and DNN/S-NSSAI. NOTE: In the case of private IPv4 address being used for the UE, the DNN and S-NSSAI are required for session binding in the PCF. The PCF registers to BSF as described in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. TSCTSF invokes a Npcf_PolicyAuthorization_Create request message to the PCF and stores the DNN, S-NSSAI and IP address as received from PCF and SUPI as received from BSF and associates them with the AF-session. If PMIC/UMIC information from the DS-TT or NW-TT is available at the PCF, the PCF reports it to the TSCTSF invoking Npcf_PolicyAuthorization_Notify. 2. The AF subscribes to the UE availability for time synchronization service and provides the associated Notification Target Address of the AF by sending Nnef_TimeSynchronization_CapsSubscribe request. Report Type defines the type of reporting requested (e.g. one-time reporting, periodic reporting or event based reporting). The request may include DNN and slicing information (S-NSSAI) and shall include an AF-Service-Identifier. If the DNN and S-NSSAI are omitted in the request, the NEF uses the AF-Service-Identifier to determine the target DNN and slicing information (S-NSSAI). The Event Filter may include a list of UE identities (GPSIs) or Groups of UEs identified by an External Group Identifier that further define the subset of the target UEs. If the request does not include UE identities nor External Group Identifier, the request is targeted to any UE with a PDU Session using the DNN and S-NSSAI. The NEF forwards the GPSIs or the External Group Identifier to the TSCTSF by including them/it inside the Ntsctsf_TimeSynchronization_CapsSubscribe request. Additionally, the Event Filter may include one or more of the requested PTP instance type, requested transport protocol for PTP, or requested PTP Profile as described in Table 5.2.6.25.6-1. When the NEF processes the AF request the AF-Service-Identifier may be used to authorize the AF request. Depending on the AF-Service-Identifier and/or DNN/S-NSSAI, the NEF may reject the request if the list of UE identities or External Group Identifier is not included in the request. To unsubscribe to the UE availability for time synchronization for a list of UE(s), the AF invokes Nnef_TimeSynchronization_CapsUnsubscribe service operation and provides the Subscription Correlation ID. 3. (In the case of Ntsctsf_TimeSynchronization_CapsSubscribe): The NEF discovers the TSCTSF as described in clause 6.3.24 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The NEF invokes the Ntsctsf_TimeSynchronization_CapsSubscribe request service operation to the selected TSCTSF. (In the case of Ntsctsf_TimeSynchronization_CapsUnsubscribe): The NEF uses the Subscription Correlation ID to determine the TSCTSF and interacts with the TSCTSF by triggering a Ntsctsf_TimeSynchronization_CapsUnsubscribe request message. The AF that is part of operator's trust domain may invoke the services directly with TSCTSF. 4. If the Event Filter includes GPSI(s), an External Group Identifier or an Internal Group Identifier, the TSCTSF uses the Nudm_SDM_Get request to retrieve the subscription information (SUPI(s)) from the UDM using each GPSI or the External Group Identifier as received from the NEF or an Internal Group Identifier as provided directly by the AF (in the case when the AF is within the operator's domain). The TSCTSF requests the Time Synchronization Subscription data from the UDM. The TSCTSF may also use stored Time Synchronization Subscription data which it retrieved from the UDM when the UE established PDU session, see clause 4.28.3.1. 5. The UDM provides the Nudm_SDM_Get response containing SUPI that are mapped from each received GPSI or a list of SUPIs mapped from the External/Internal Group Identifier and identify UEs targeted by the AF request. 6. (in the case of Ntsctsf_TimeSynchronization_CapsSubscribe): The TSCTSF uses the parameters received in step 3 and step 5 (i.e. DNN, S-NSSAI and the list of SUPIs if present) to find matching AF-session(s). If the Time Synchronization Subscription data is available, the subscription data returned by the UDM includes the AF request authorization that indicates whether the AF is allowed to request (g)PTP-based time distribution for DNN/S-NSSAI. If the subscription data indicates that the AF is not allowed to request (g)PTP-based time synchronization, the AF-session is excluded from the list of matching AF-sessions. For any such matching AF-session, the TSCTSF interacts with the PCF by triggering a Npcf_PolicyAuthorization_Update request message. (in the case of Ntsctsf_TimeSynchronization_CapsUnsubscribe): The TSCTSF uses the Subscription Correlation ID to determine the AF sessions and interacts with the PCF(s) by triggering a Npcf_PolicyAuthorization_Delete request message. Steps 10-15 are skipped. 7. TSCTSF acknowledges the execution of Ntsctsf_TimeSynchronization_CapsSubscribe to the requester that initiated the request. The acknowledgement contains a Subscription Correlation ID that the requester can use to cancel or modify the subscription. 8. NEF acknowledges the execution of Nnef_TimeSynchronization_CapsSubscribe to the requester that initiated the request. The acknowledgement contains a Subscription Correlation ID that the AF can use to cancel or modify the subscription. 9. As part of Npcf_PolicyAuthorization_Update request, the TSCTSF uses the procedures as described in clause K.2.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] to determine the (g)PTP capabilities from the DS-TT. If the TSCTSF has not determined the (g)PTP capabilities from the NW-TT, the TSCTSF determines the capabilities using the procedures as described in clause K.2.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The TSCTSF composes the time synchronization capabilities for the DS-TT/UE(s) connected to the NW-TT based on the capability information received from the DS-TT(s) and NW-TT. If the Ntsctsf_TimeSynchronization_CapsSubscribe request include an Event Filter with one or more of the requested PTP instance type, requested transport protocol for PTP, or requested PTP Profile, the TSCTSF considers only the DS-TT(s) and NW-TT(s) with these capabilities as part of the time synchronization capability set that is reported to the NEF (or AF). The TSCTSF maintains association between the user-plane Node ID, the time synchronization capabilities, the reference to the capabilities (as identified by the Subscription Correlation ID), the Event Filter (if available), the NEF or AF Notification Target Address and list of the AF sessions with PCFs with this user-plane Node ID. If the Ntsctsf_TimeSynchronization_CapsSubscribe request includes one or more Event Filter(s), the TSCTSF considers only the matching UE identities and the DS-TT(s) and NW-TT(s) with the matching capabilities to be included in the associated AF sessions. 10. The TSCTSF sends Ntsctsf_TimeSynchronization_CapsNotify (as described in clause 5.2.27.2.8) to the NEF. The message includes the time synchronization capabilities as composed in step 9. The message contains one or more user-plane Node ID(s) and a list of UE identities associated to each user-plane Node ID and time synchronization capabilities for each set of DS-TTs connected to given user-plane Node ID, as described in Table 5.2.6.25.8-1. The user-plane Node ID identifies the NW-TT to where the UE/DS-TT(s) are connected to. 11. The NEF sends Nnef_TimeSynchronization_CapsNotify with Time Synchronization capability event (as described in Table 5.2.6.25.8-1) to the AF. 12-13. Upon PDU Session Establishment as defined clause 4.3.2.2.1, steps 1, 9, 10 and 11 are repeated for the new PDU Session. 14. If necessary, e.g. upon PDU Session establishment or release, the TSCTSF may update the time synchronization capabilities for the DS-TT/UE(s) connected to the NW-TT(s). The TSCTSF sends Ntsctsf_TimeSynchronization_CapsNotify with Time Synchronization capability event (as described in Table 5.2.6.25.8-1) containing the updated capabilities to the NEF. 15. The NEF sends Nnef_TimeSynchronization_CapsNotify containing the updated capabilities to the AF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.9.2 |
3,880 | 10.5.4.10 Calling party subaddress | The purpose of the Calling party subaddress is to identify a subaddress associated with the origin of a call. For the definition of a subaddress see ITU-T Rec. I.330 [48]. The Calling party subaddress information element is coded as shown in figure 10.5.94/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 calling 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.94/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Calling party subaddress Table 10.5.121/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Calling party subaddress | 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.10 |
3,881 | 5.6G.1 Channel bandwidths per operating band for V2X Communication | E-UTRA V2X Communication channel bandwidths and operating band is shown in Table 5.6G.1-1. The same (symmetrical) channel bandwidth is specified for both the TX and RX path. Table 5.6G.1-1: V2X Communciation channel bandwidth For V2X inter-band con-current operation, the V2X Communication channel bandwidths for each operating band is specified in Table 5.6G.1-2. Table 5.6G.1-2: Inter-band con-current V2X configurations and bandwidth combination sets V2X Bandwidth Class is specified in Table 5.6G.1-3 for V2X intra-band contiguous multi-carrier operation. Table 5.6G.1-3: V2X bandwidth classes and corresponding nominal guard bands For V2X intra-band multi-carrier operation, the V2X communication channel bandwidths for each operating band is specified in Table 5.6G.1-4. Table 5.6G.1-4: V2X intra-band multi-carrier configurations | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.6G.1 |
3,882 | 5.5.2.2.7 Abnormal cases in the network side | The following abnormal cases can be identified: a) De-registration request received in a cell belonging to an SNPN with a non-globally-unique SNPN identity for which the UE has no valid subscription If the UE initiates a de-registration procedure in a cell belonging to an SNPN with a non-globally-unique SNPN identity for which the UE has no valid subscription, and the de-registration procedure is not due to "switch off", the network shall initiate the de-registration procedure. The AMF shall send a DEREGISTRATION REQUEST message including the 5GMM cause #74 "Temporarily not authorized for this SNPN". b) De-registration request received in a cell belonging to an SNPN with a globally-unique SNPN identity for which the UE has no valid subscription If the UE initiates a de-registration procedure in a cell belonging to an SNPN with a globally-unique SNPN identity for which the UE has no valid subscription, and the de-registration procedure is not due to "switch off", the network shall initiate the de-registration procedure. The AMF shall send a DEREGISTRATION REQUEST message including the 5GMM cause #75 "Permanently not authorized for this SNPN". c) De-registration request received in a CAG cell and none of the CAG ID broadcasted by the CAG cell is authorized based on the UE's "allowed CAG list" for the current PLMN If the UE initiates a de-registration procedure in a CAG cell and none of the CAG ID broadcasted by the CAG cell is authorized based on the UE's "allowed CAG list" for the current PLMN and the de-registration procedure is not due to "switch off", the AMF shall initiate the de-registration procedure. The AMF shall send a DEREGISTRATION REQUEST message including the 5GMM cause #76 "Not authorized for this CAG or authorized for CAG cells only" if the UE supports CAG. Otherwise, the network shall operate as described in bullet g) of subclause 5.5.2.3.5. d) De-registration request received in a non-CAG cell from a UE whose "CAG information list" includes an entry associated with the current PLMN, where the entry contains an "indication that the UE is only allowed to access 5GS via CAG cells" If the UE initiates a de-registration procedure in a non-CAG cell from a UE whose "CAG information list" includes an entry associated with the current PLMN, where the entry contains an "indication that the UE is only allowed to access 5GS via CAG cells" and the de-registration procedure is not due to "switch off", the AMF shall initiate the de-registration procedure. The AMF shall send a DEREGISTRATION REQUEST message including the 5GMM cause #76 "Not authorized for this CAG or authorized for CAG cells only" if the UE supports CAG. Otherwise, the network shall operate as described in bullet g) of subclause 5.5.2.3.5. e) De-registration and registration procedure for initial registration collision If the network receives a REGISTRATION REQUEST message indicating either "initial registration" or "emergency registration" in the 5GS registration type IE from the UE before the UE-initiated de-registration procedure, which is not due to switch off, has been completed, the network shall abort the de-registration procedure and the registration procedure 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.5.2.2.7 |
3,883 | 9.3.12 Hold Reject | This message is sent by the network to indicate the denial of a request to hold a call. See table 9.62e/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] for the content of the HOLD REJECT message. For the use of this message, see 3GPP TS 24.010[ Mobile radio interface layer 3; Supplementary services specification; General aspects ] [21]. Message type: HOLD REJECT Significance: local Direction: network to mobile station Table 9.62e/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : HOLD REJECT 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.12 |
3,884 | 5.5.4.2 ProSe relay transaction identity (PRTI) | Upon receiving a ProSe direct link establishment request from a 5G ProSe remote UE or a 5G ProSe end UE for establishing a secure PC5 unicast link as specified in 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E], the UE shall allocate an available PRTI value for the authentication and key agreement procedure for 5G ProSe UE-to-network relay or 5G ProSe UE-to-UE relay and associate this PRTI value with the 5G ProSe remote UE or the 5G ProSe end UE. The UE shall release the PRTI value allocated to the authentication and key agreement procedure for 5G ProSe UE-to-network relay or 5G ProSe UE-to-UE relay when the authentication and key agreement procedure for 5G ProSe UE-to-network relay or 5G ProSe UE-to-UE relay completes or is aborted. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.4.2 |
3,885 | 5.34.5 Usage of IPv6 multi-homing for a PDU Session controlled by I-SMF | This clause applies only in the case of non-roaming or LBO roaming as control of UL CL/BP in VPLMN is not supported in HR case. When I-SMF is involved for a PDU Session, it is possible that the BP controlled by I-SMF is inserted into the data path of the PDU Session. The usage of a BP controlled by I-SMF in the data path of a PDU Session is depicted in Figure 5.34.5-1. Figure 5.34.5-1: Multi-homed PDU Session: Branching Point controlled by I-SMF The I-SMF determines whether BP will be inserted based on information received from SMF, and the I-SMF selects the UPFs acting as BP and/or PDU Session Anchor providing local access to the Data Network. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.34.5 |
3,886 | 11.2.1.2.1 non-EPC based IPv4 Non Transparent access | In this case: - the MS is given an address belonging to the Intranet/ISP addressing space. The address is given either at subscription in which case it is a static address or at PDP context activation in which case it is a dynamic address. This address is used for packet forwarding within the GGSN and for packet forwarding on the Intranet/ISP. This requires a link between the GGSN and an address allocation server, like AAA, DHCP, …, belonging to the Intranet/ISP; - the MS shall send an authentication request at PDP context activation and the GGSN requests user authentication from a server, like AAA, DHCP, …, belonging to the Intranet/ISP; - the protocol configuration options are retrieved (if requested by the MS at PDP context activation) from some server (AAA or DHCP, …) belonging to the Intranet/ISP; - the communication between the Packet Domain and the Intranet/ISP may be performed over any network, even an insecure e.g. the Internet. In case of an insecure connection between the GGSN and the Intranet/ISP there may be a specific security protocol in between. This security protocol is defined by mutual agreement between PLMN operator and Intranet/ISP administrator. Figure 11a: Signalling plane of non transparent case NOTE: The transport protocol UDP is used for DHCP and RADIUS, and TCP or SCTP are used for Diameter. The following description bullet items describe the signal flow. 1) The TE sends an AT-command to the MT to set up parameters and enter PPP mode. The MT responds with an AT-response. 2) LCP negotiates Maximum-Receive-Unit and authentication protocol. The negotiated authentication protocol is, either CHAP, PAP or ‘none’. The MT shall try to negotiate for CHAP as first priority. 3) If the negotiated authentication protocol is either of CHAP or PAP, the TE authenticates itself towards the MT by means of that protocol. The MT stores the necessary authentication data and sends a forced positive acknowledgement of the authentication to the TE. 4) The TE requests IP configuration by sending the IPCP Configure-Request message to the MT indicating either the static IP address that shall be used or that an IP-address shall be dynamically allocated. 5) The MT sends the Activate PDP context request message to the SGSN, including the Protocol Configuration Options. The SGSN sends the Create PDP context req message to the chosen GGSN including the unmodified Protocol Configuration Options. 6) The GGSN deduces from the APN: - the server(s) to be used for address allocation, authentication and protocol configuration options retrieval; - the protocol like RADIUS, DHCP, … to be used with this / those server(s); - the communication and security feature needed to dialogue with this / those server(s) e.g. tunnel, IPSec security association, dial-up connection (using possibly PPP), … As an example the GGSN may use one of the following options: - RADIUS for authentication and IP-address allocation. The AAA server responds with either an Access-Accept or an Access-Reject to the RADIUS client in the GGSN; - RADIUS for authentication and DHCP for host configuration and address allocation. The AAA server responds with either an Access-Accept or an Access-Reject to the RADIUS client in the GGSN. After a successful authentication, the DHCP client discovers the DHCP server(s) in the ISP/Intranet and receives host configuration data. - If the received Protocol Configurations Options IE contains a PPP IPCP Configure-Request packet, the GGSN shall analyse all the contained IPCP options and their requested values. In accordance with the relevant PPP RFC 1661 [21a] and RFC 1662 [21b] the GGSN shall respond with the following messages: - zero or one PPP IPCP Configure-Reject packet containing options not supported and options which values cannot be returned; - zero or one PPP IPCP Configure-Nak packet containing options that are supported but has requested values that are incorrect/unsupported; and - zero or one PPP IPCP Configure-Ack packet containing options that are supported and has requested values that are correct/supported. Any returned PPP IPCP packets shall be contained in the Protocol Configurations Options IE. 7) The GGSN sends back to the SGSN a Create PDP Context Response message, containing the Protocol Configuration Options IE. The cause value shall be set according to the outcome of the host –authentication and –configuration. A PDP context activation shall not be rejected solely due to the presence of unsupported or incorrect PPP IPCP options or option values, received from the MS in the Protocol Configurations Options IE. The MS may however later decide to immediately deactivate the activated PDP context due to the information received in the Protocol Configurations Options IE received from the network. 8) Depending on the cause value received in the Create PDP Context Response the SGSN sends either an Activate PDP Context Accept or an Activate PDP Context Reject, to the MS. If Protocol Configuration Options are received from the GGSN, the SGSN shall relay those to the MS. The MT sends either the configuration-ack packet (e.g. IPCP Configure Ack in PPP case), the configure-nack packet in case of dynamic address allocation (e.g. IPCP Configure Nack in PPP case), or a link Terminate request (LCP Terminate-Request in PPP case) back to the TE. In the case where a configure-nack packet was sent by the MT, a local negotiation may take place at the R reference point (i.e. the TE proposes the new value to the MT), after which a configuration-ack packet is sent to the TE. 9) In case a configuration-ack packet was sent to the TE, the link from the TE to the external ISP/Intranet is established and IP packets may be exchanged. In case a link terminate request packet was sent to the TE, the TE and MT negotiates for link termination. The MT may then send a final AT-response to inform the TE about the rejected PDP Context activation. A link terminate request packet (such as LCP Terminate-request in PPP case) causes a PDP context deactivation. EXAMPLE: In the following example PPP is used as layer 2 protocol over the R reference point. The MT acts as a PPP server and translates Protocol Configuration Options into SM message Ies. GTP-C carries this information unchanged to the GGSN which uses the information e.g. for DHCP or RADIUS authentication and host configuration. The result of the host authentication and configuration is carried via GTP-C to the SGSN which relays the information to the MT. The MT sends an IPCP Configure-Ack to the TE with the appropriate options included. Figure 11b: PDP Context Activation for the IPv4 Non-transparent case | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 11.2.1.2.1 |
3,887 | – SSB-PositionQCL-Relation | The IE SSB-PositionQCL-Relation is used to indicate the QCL relationship between SSB positions on the frequency indicated by ssbFrequency (see TS 38.213[ NR; Physical layer procedures for control ] [13], clause 4.1) for operation with shared spectrum channel access. Value n1 corresponds to 1, value n2 corresponds to 2 and so on. SSB-PositionQCL-Relation information element -- ASN1START -- TAG-SSB-POSITIONQCL-RELATION-START SSB-PositionQCL-Relation-r16 ::= ENUMERATED {n1,n2,n4,n8} SSB-PositionQCL-Relation-r17 ::= ENUMERATED {n32, n64} -- TAG-SSB-POSITIONQCL-RELATION-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,888 | 5.6.10.4 Maximum Transfer Unit size considerations | In order to avoid data packet fragmentation between the UE and the UPF acting as PSA, the link MTU size in the UE should be set to the value provided by the network as part of the IP configuration. The link MTU size for IPv4 is sent to the UE by including it in the PCO (see TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]). The link MTU size for IPv6 is sent to the UE by including it in the IPv6 Router Advertisement message (see RFC 4861 [54]). NOTE 1: Ideally the network configuration ensures that for PDU Session type IPv4v6 the link MTU values provided to the UE via PCO and in the IPv6 Router Advertisement message are the same. In cases where this condition cannot be met, the MTU size selected by the UE is unspecified. When using a PDU Session type Unstructured, the maximum uplink packet size, and when using Ethernet, the Ethernet frames' payload, that the UE should use may be provided by the network as a part of the session management configuration by encoding it within the PCO (see TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]). When using a PDU Session type Unstructured, to provide a consistent environment for application developers, the network shall use a maximum packet size of at least 128 octets (this applies to both uplink and downlink). When the MT and the TE are separated, the TE may either be pre-configured to use a specific default MTU size or the TE may use an MTU size provided by the network via the MT. Thus, it is not always possible to set the MTU value by means of information provided by the network. NOTE 2: In network deployments that have MTU size of 1500 octets in the transport network, providing a link MTU value of 1358 octets (as shown in Figure J-1) to the UE as part of the IP configuration information from the network will prevent the IP layer fragmentation within the transport network between the UE and the UPF. For network deployments that uniformly support transport with larger MTU size than 1500 octets (for example with ethernet jumbo frames of MTU size up to 9216 octets), providing a link MTU value of MTU minus 142 octets to the UE as part of the IP configuration information from the network will prevent the IP layer fragmentation within the transport network between the UE and the UPF. Link MTU considerations are discussed further in Annex J. NOTE 3: As the link MTU value is provided as a part of the session management configuration information, a link MTU value can be provided during each PDU Session establishment. In this release, dynamic adjustment of link MTU for scenarios where MTU is not uniform across transport are not addressed. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.6.10.4 |
3,889 | 4.4.3.4 Ciphering and deciphering | The sender shall use its locally stored NAS COUNT as input to the ciphering algorithm. The receiver shall use the NAS sequence number included in the received message (or estimated from the 5 bits of the NAS sequence number received in the message) and an estimate for the NAS overflow counter as defined in clause 4.4.3.1 to form the NAS COUNT input to the deciphering algorithm. The input parameters to the NAS ciphering algorithm are the constant BEARER ID, DIRECTION bit, NAS COUNT, NAS encryption key and the length of the key stream to be generated by the encryption algorithm. When an initial plain NAS message for transport of user data via control plane (i.e. CONTROL PLANE SERVICE REQUEST message) is to be partially ciphered, the length of the key stream is set to the length of the part of the initial plain NAS message (i.e. the value part of the ESM message container IE or the value part of the NAS message container) that is to be ciphered. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.4.3.4 |
3,890 | 9.9.1.1.1 FDD | The following requirements apply to UE Category ≥1. For the parameters specified in Table 9.9.1.1.1-1, using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2, the reported CQI value according to RC.1 FDD / RC.4 FDD in Table A.4-1 shall be in the range of ±1 of the reported median more than 90% of the time. If the PDSCH BLER using the transport format indicated by median CQI is less than or equal to 0.1, the BLER using the transport format indicated by the (median CQI + 1) shall be greater than 0.1. If the PDSCH BLER using the transport format indicated by the median CQI is greater than 0.1, the BLER using transport format indicated by (median CQI – 1) shall be less than or equal to 0.1. Table 9.9.1.1.1-1: PUCCH 1-0 static test (FDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.9.1.1.1 |
3,891 | 6.3.14 NEF Discovery | The NF consumers may utilize the NRF to discover NEF instance(s) unless NEF information is available by other means, e.g. locally configured in NF consumers. The NRF provides NF profile(s) of NEF instance(s) to the NF consumers. The IP address(es)/port(s) of the NEF or L-NEF may be locally configured in the AF, or the AF may discover the FQDN or IP address(es)/port(s) of the NEF/L-NEF by performing a DNS query using the External Identifier of an individual UE or using the External Group Identifier of a group of UEs or using EDNS Client Subnet, or, if the AF is trusted by the operator, the AF may utilize the NRF to discover the FQDN or IP address(es)/port(s) of the NEF or L-NEF. NOTE 1: When the AF discovers the FQDN or IP address(es)/port(s) of the NEF/L-NEF by performing a DNS query, the AF can add in its DNS request an EDNS Client Subnet option in order to help the DNS determine a local NEF directly. The use of a DNS query for the selection of a L-NEF is only supported for AF and not internal network functions. NOTE 2: The EDNS Client Subnet may be derived by the AF based on factors that are considered for NEF selection. Whether and which factors are considered for NEF/L-NEF selection may depend on whether the AF performs an initial NEF discovery or a NEF discovery due to L-PSA relocation. NOTE 3: The NEF discovery and selection procedures described in this clause are intended to be applied by NF consumers deployed within the operator's domain. NOTE 4: The NEF supporting the capabilities can be configured in the AF or discovered by AF with the assistance of NRF. The following factors may be considered for NEF selection: - S-NSSAI(s); - S-NSSAI and DNN corresponding to an untrusted AF; - Event ID(s) supported by an AF (see clause 6.2.6, clause 6.2.2.3 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86] and clause 5.2.19 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]); - AF Instance ID, Application Identifier; - External Identifier, External Group Identifier, or domain name; - A request for local NEF selection; - Location (see locality in clause 6.1.6.2.2 of TS 29.510[ 5G System; Network function repository services; Stage 3 ] [58]); - (for local NEF selection) List of supported TAI; - (for local NEF selection) List of supported DNAI; - Capability of NEF to support UAS NF functionality for UUAA procedures; - Capability of NEF to support Multi-member AF session with required QoS for a set of UEs identified by a list of UE addresses; - Capability of NEF to support member UE selection assistance functionality. Local NEF instance(s) can be deployed close to UE access. For local NEF selection, the location of the local NEF instance (e.g. geographical location, data centre) may be used in conjunction with the location of L-PSA UPF or AF. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.14 |
3,892 | 8.22.1 Inter-DU direct path addition on top of indirect path | The signalling flow for inter-DU direct path addition is shown in Figure 8.22.1-1. This procedure is only applicable to the MP Remote UE using PC5 link. Figure 8.22.1-1: Signalling procedure of inter-DU direct path addition on top of indirect path 1. The Uu measurement configuration and measurement report signalling are performed between MP Remote UE and the gNB-CU to evaluate both relay link measurement and Uu link measurement. The MP Remote UE may report Uu measurement results of neighboring cells and one or multiple candidate MP Relay UE(s). 2. The gNB-CU decides to add the direct path to MP Remote UE under a different gNB-DU (i.e., gNB-DU1). NOTE: Mode 1 resource configuration cannot be configured for MP Remote UE in inter-gNB-DU multi-path relay in this release. 3. The gNB-CU sends the UE CONTEXT SETUP REQUEST message for the MP Remote UE to the gNB-DU1, which contains at least the direct path configuration. 4. The gNB-DU1 responds to the gNB-CU with a UE CONTEXT SETUP RESPONSE message. 5. The gNB-CU sends an RRCReconfiguration message to the MP Relay UE to update the indirect path configuration if necessary. 6. The gNB-CU sends the UE CONTEXT MODIFICATION REQUEST message for MP Remote UE by including the direct path addition information and the RRCReconfiguration message to the gNB-DU2. The gNB-DU2 may update the stored UE context for MP Remote UE. The contents in the RRCReconfiguration message may include at least direct path addition configuration, RLC channel configuration, bearer mapping and the associated radio bearer(s). 7. The gNB-DU2 sends the RRCReconfiguration message to the MP Remote UE. 8. The gNB-DU2 sends the UE CONTEXT MODIFICATION RESPONSE message to the gNB-CU. 9. The MP Remote UE performs random access procedure at the gNB-DU1. 10. The MP Remote UE sends the RRCReconfigurationComplete message to the gNB-DU1 via direct path in order to complete the direct path addition procedure. 10a. In case the SRB1 with duplication is configured, the MP Remote UE also sends the RRCReconfigurationComplete message to the gNB-DU2 via indirect path. 11. The gNB-DU1 sends the UL RRC MESSAGE TRANSFER message to gNB-CU by including the RRCReconfigurationComplete message received in step 10. 11a. In case the SRB1 with duplication is configured, the gNB-DU2 also sends the UL RRC MESSAGE TRANSFER message to gNB-CU by including the RRCReconfigurationComplete message received in step 10a. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.22.1 |
3,893 | 5.30.2.8 Access to stand-alone non-public network services via PLMN | To access SNPN services, a UE that has successfully registered with a PLMN over 3GPP access may perform another registration via the PLMN User Plane with an SNPN (using the credentials of that SNPN) following the same architectural principles as specified in clause 4.2.8 (including the optional support for PDU Session continuity between PLMN and SNPN using the Handover of a PDU Session procedures in clauses 4.9.2.1 and 4.9.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]) and the PLMN taking the role of "Untrusted non-3GPP access" of the SNPN, i.e. using the procedures for Untrusted non-3GPP access in clause 4.12.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. Annex D, clause D.3 provides additional details. The case where UE that has successfully registered with a PLMN over non-3GPP access to access SNPN services is not specified in this Release. NOTE: QoS differentiation in the PLMN can be provided on per-IPsec Child Security Association basis by using the UE or network requested PDU Session Modification procedure described in clause 4.3.3.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. In the SNPN, N3IWF determines the IPsec child SAs as defined in clause 4.12 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The N3IWF is preconfigured by SNPN to allocate different IPsec child SAs for QoS Flows with different QoS profiles. To support QoS differentiation in the PLMN with network-initiated QoS, the mapping rules between the PLMN and the SNPN are assumed to be governed by an SLA including: 1) mapping between the DSCP markings for the IPsec child SAs on NWu and the corresponding QoS, which is the QoS requirement of the SNPN and is expected to be provided by the PLMN, and 2) N3IWF IP address(es) in the SNPN. The non-alteration of the DSCP field on NWu is also assumed to be governed by an SLA and by transport-level arrangements that are outside of 3GPP scope. The packet detection filters in the PLMN can be based on the N3IWF IP address and the DSCP markings on NWu. To support QoS differentiation in the PLMN with UE-requested QoS, the UE can request for an IPsec SA the same 5QI from the PLMN as the 5QI provided by the SNPN. It is assumed that UE-requested QoS is used only when the 5QIs used by the SNPN are from the range of standardized 5QIs. The packet filters in the requested QoS rule can be based on the N3IWF IP address and the SPI associated with the IPsec SA. Refer to clause D.7 for details on how to support QoS differentiation. When the UE accesses the SNPN over NWu via a PLMN, the AMF in the SNPN shall send an indication toward the UE during the Registration procedure to indicate whether an IMS voice over PS session is supported or not. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.30.2.8 |
3,894 | 10.17.1 MR-DC with 5GC | Inter-MN RRC Resume without MN initiated SN change is used to transfer UE context data from a source MN to a target MN while the UE context at the SN is kept. During the procedure, the target MN may decide not to keep the SN. Figure 10.17.1-1: Inter-MN RRC Resume without MN initiated SN change procedure Figure 10.17.1-1 shows an example signalling flow for inter-MN RRC Resume without MN initiated SN change: 1. The UE resumes from RRC_INACTIVE, providing the I-RNTI, allocated by the source MN, i.e., the last serving NG-RAN node. 2. The target MN, if able to resolve the NG-RAN node identity contained in the I-RNTI, requests the source MN to provide UE Context by initiating the Xn Retrieve UE Context procedure. 3. If the verification is successful, the source MN provides UE context data. The source MN includes the SN UE XnAP ID, SN ID and the UE context in the SN in the Retrieve UE Context Response message. NOTE 1: The source MN may trigger the MN-initiated SN Modification procedure (to the SN) to retrieve the current SCG configuration and to allow provision of data forwarding related information before step 3.4a. If the target MN decides to keep the SN, the target MN sends SN Addition Request to the SN including the SN UE XnAP ID as a reference to the UE context in the SN that was established by the source MN. 4b. The SN replies with SN Addition Request Acknowledge message. 4c. For SN terminated bearers using MCG resources, the target MN provides Xn-U DL TNL address information in the Xn-U Address Indication message. 5/6. The target MN and UE complete the resumption of the RRC connection. 7. If configured with bearers requiring SCG radio resources, the UE synchronizes to the SN. NOTE 2: The order the UE sends the RRCResumeComplete message towards the target MN (step 6) and performs the Random Access procedure towards the SN (step 7) is not defined. 8. If the RRC connection reconfiguration procedure was successful, the target MN informs the SN via SN Reconfiguration Complete message. 9. If the RRC connection reconfiguration procedure was successful, the target MN initiates the Xn Retrieve UE Context Confirm procedure and indicates to the source MN whether the UE context in the SN is kept or not. 10. The Xn-U Address Indication procedure may be invoked by the target MN to provide forwarding address information if loss of DL user data buffered in the source side needs to be avoided. 11a/11b. The source MN sends SN Release Request message to the SN including a Cause indicating MCG mobility. The SN acknowledges the release request. The source MN indicates to the SN that the UE context in the SN is kept, if it receives the indication from the target MN. If the indication as the UE context kept in the SN is included, the SN keeps the UE context. 11c. If received in step 10, the source MN sends the Xn-U Address Indication message to the SN to transfer data forwarding information. More than one data forwarding addresses may be provided if the PDU session is split in the target side. 12. If applicable, data forwarding takes place from the source side. If the SN is kept, data forwarding may be omitted for SN terminated bearers or QoS flows kept in the SN. 13-16. The target MN initiates the Path Switch procedure. If the target MN includes multiple DL TEIDs for one PDU session in the Path Switch Request message, multiple UL TEID of the UPF for the PDU session should be included in the Path Switch Ack message in case there is TEID update in UPF. NOTE 3: If new UL TEIDs of the UPF for SN terminated bearers are included, the target MN performs MN initiated SN Modification procedure to provide them to the SN. 17. The target MN initiates the UE Context Release procedure towards the source MN. 18. Upon reception of the UE Context Release message from source MN, the SN releases C-plane related resources associated to the UE context towards the source MN. Any ongoing data forwarding may continue. The SN shall not release the UE context associated with the target MN if the UE context kept indication was included in the SN Release Request message in step 11. | 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.17.1 |
3,895 | 5.15.10 Network Slice-Specific Authentication and Authorization | A serving PLMN or SNPN shall perform Network Slice-Specific Authentication and Authorization for the S-NSSAIs of the HPLMN or SNPN which are subject to it based on subscription information. The UE shall indicate in the Registration Request message in the UE 5GMM Core Network Capability whether it supports NSSAA feature. If the UE does not support NSSAA feature and if the UE requests any of these S-NSSAIs that are subject to Network Slice-Specific Authentication and Authorization, the AMF shall not trigger this procedure for the UE and they are rejected for the PLMN or SNPN. If the UE supports NSSAA feature and if the UE requests any of these S-NSSAIs that are subject to Network Slice-Specific Authentication and Authorization, they are included in the list of Pending NSSAI for the PLMN or SNPN, as described in clause 5.15.5.2.1. If a UE is configured with S-NSSAIs, which are subject to Network Slice-Specific Authentication and Authorization, the UE stores an association between the S-NSSAI and corresponding credentials for the Network Slice-Specific Authentication and Authorization. NOTE 1: How the UE is aware that an S-NSSAI is subject to Network Slice-Specific Authentication and Authorization (e.g. based on local configuration) is out of scope of this specification. The UE may support remote provisioning of credentials for NSSAA, specified in clause 5.39. A UE that supports to be provisioned with the credentials used for NSSAA over UP remote provisioning shall use connectivity over an S-NSSAI/DNN which can access the provisioning server to establish a PDU session for remote provisioning as defined in clause 5.39. NOTE 2: The credentials for Network Slice-Specific Authentication and Authorization are not specified. To perform the Network Slice-Specific Authentication and Authorization for an S-NSSAI, the AMF invokes an EAP- based Network Slice-Specific authorization procedure documented in clause 4.2.9 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] (see also TS 33.501[ Security architecture and procedures for 5G System ] [29]) for the S-NSSAI. When an NSSAA procedure is started and is ongoing for an S-NSSAI, the AMF stores the NSSAA status of the S-NSSAI as pending and when the NSSAA is completed the S-NSSAI becomes either part of the Allowed NSSAI or a Rejected S-NSSAI. The NSSAA status of each S-NSSAI, if any is stored, is transferred when the AMF changes. This procedure can be invoked for a supporting UE by an AMF at any time, e.g. when: a. The UE registers with the AMF and one of the S-NSSAIs of the HPLMN or SNPN which maps to an S-NSSAI in the Requested NSSAI is requiring Network Slice-Specific Authentication and Authorization (see clause 5.15.5.2.1 for details), and the S-NSSAI in the Requested NSSAI can be added to the Allowed NSSAI by the AMF once the Network Slice-Specific Authentication and Authorization for the HPLMN or SNPN S-NSSAI succeeds; or b. The Network Slice-Specific AAA Server triggers a UE re-authentication and re-authorization for an S-NSSAI; or c. The AMF, based on operator policy or a subscription change, decides to initiate the Network Slice-Specific Authentication and Authorization procedure for a certain S-NSSAI which was previously authorized. In the case of re-authentication and re-authorization (b. and c. above) the following applies: - If S-NSSAIs that are requiring Network Slice-Specific Authentication and Authorization map to S-NSSAIs that are included in the Allowed NSSAI for each Access Type, AMF selects an Access Type to be used to perform the Network Slice Specific Authentication and Authorization procedure based on network policies. - If the Network Slice-Specific Authentication and Authorization for some S-NSSAIs mapped to some S-NSSAIs in the Allowed NSSAI is unsuccessful, the AMF shall update the Allowed NSSAI for each Access Type to the UE via UE Configuration Update procedure. - If the Network Slice-Specific Authentication and Authorization fails for all S-NSSAIs mapped to all S-NSSAIs in the Allowed NSSAI, the AMF determines a new Allowed NSSAI including default S-NSSAI(s). If no default S-NSSAI(s) could be added, the AMF shall execute the Network-initiated Deregistration procedure described in clause 4.2.2.3.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] and shall include in the explicit De-Registration Request message the list of Rejected S-NSSAIs, each of them with the appropriate rejection cause value. After a successful or unsuccessful UE Network Slice-Specific Authentication and Authorization, the UE context in the AMF shall retain the authentication and authorization status for the UE for the related specific S-NSSAI of the HPLMN or SNPN while the UE remains RM-REGISTERED in the PLMN or SNPN, so that the AMF is not required to execute a Network Slice-Specific Authentication and Authorization for a UE at every Periodic Registration Update or Mobility Registration procedure with the PLMN or SNPN. A Network Slice-Specific AAA server may revoke the authorization or challenge the authentication and authorization of a UE at any time. When authorization is revoked for an S-NSSAI that maps to an S-NSSAI in the current Allowed NSSAI for an Access Type, the AMF shall provide a new Allowed NSSAI to the UE and trigger the release of all PDU sessions associated with the S-NSSAI, for this Access Type. The AMF provides the GPSI of the UE related to the S-NSSAI to the AAA Server to allow the AAA server to initiate the Network Slice-Specific Authentication and Authorization, or the Authorization revocation procedure, where the current AMF serving the UE needs to be identified by the system, so the UE authorization status can be challenged or revoked. The Network Slice-Specific Authentication and Authorization requires that the UE Primary Authentication and Authorization of the SUPI has successfully completed. If the SUPI authorization is revoked, then also the Network Slice-Specific authorization is revoked. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.10 |
3,896 | 6.6.1 UP security policy | The SMF shall provide UP security policy for a PDU session to the ng-eNB/gNB during the PDU session establishment procedure as specified in TS 23.502[ Procedures for the 5G System (5GS) ] [8]. The UP security policy shall indicate whether UP confidentiality and/or UP integrity protection shall be activated or not for all DRBs belonging to that PDU session. The UP security policy shall be used to activate UP confidentiality and/or UP integrity for all DRBs belonging to the PDU session. The ng-eNB/gNB shall activate UP confidentiality and/or UP integrity protection per each DRB, according to the received UP security policy, using RRC signalling as defined in clause 6.6.2. If the user plane security policy indicates "Required" or "Not needed", the ng-eNB/gNB shall not overrule the UP security policy provided by the SMF. If the ng-eNB/gNB cannot activate UP confidentiality and/or UP integrity protection when the received UP security policy is "Required", the ng-eNB/gNB shall reject establishment of UP resources for the PDU Session and indicate reject-cause to the SMF. If the received UP security policy is "Not needed ", then the establishment of the PDU Session shall proceed as described in TS 23.502[ Procedures for the 5G System (5GS) ] [8]. Only if the UE indicates that it supports use of integrity protection with ng-eNB, the ng-eNB can activate UP integrity protection. NOTE 1: Local SMF can override the confidentiality option in the UP security policy received from the home SMF based on its local policy, roaming agreement and/or regulatory requirements. At an Xn-handover from the source ng-eNB/gNB to the target ng-eNB/gNB, the source ng-eNB/gNB shall include in the HANDOVER REQUEST message, the UE's UP security policy. If the UP security policy is ‘Required’, the target ng-eNB/gNB shall reject all PDU sessions for which it cannot comply with the corresponding received UP security policy and indicate the reject-cause to the SMF. For the accepted PDU sessions, the target ng-eNB/gNB shall activate UP confidentiality and/or UP integrity protection per DRB according to the received UE's UP security policy and shall indicate that to the UE in the HANDOVER COMMAND by the source ng-eNB/gNB. Only if the UE indicates that it supports use of integrity protection with ng-eNB, the target ng-eNB can activate UP integrity protection. If the UE receives an indication in the HANDOVER COMMAND that UP integrity protection and/or UP encryption for a PDU session is enabled at the target ng-eNB/gNB, the UE shall generate or update the UP encryption key and/or UP integrity protection key and shall activate UP encryption and/or UP integrity protection for the respective PDU session. NOTE 2: If the security policy is ‘Preferred’, it is possible to have a change in activation or deactivation of UP integrity after the handover. Further, in the Path-Switch message, the target ng-eNB/gNB shall send the UE's UP security policy and corresponding PDU session ID received from the source ng-eNB/gNB to the SMF. The SMF shall verify that the UE's UP security policy received from the target ng-eNB/gNB is the same as the UE's UP security policy that the SMF has locally stored. If there is a mismatch, the SMF shall send its locally stored UE's UP security policy of the corresponding PDU sessions to the target ng-eNB/gNB. This UP security policy information, if included by the SMF, is delivered to the target ng-eNB/gNB in the Path-Switch Acknowledge message. The SMF shall support logging capabilities for this event and may take additional measures, such as raising an alarm. If the target ng-eNB/gNB receives UE's UP security policy from the SMF in the Path-Switch Acknowledge message, the target ng-eNB/gNB shall update the UE's UP security policy with the received UE's UP security policy. If UE's current UP confidentiality and/or UP integrity protection activation is different from the received UE's UP security policy, then the target ng-eNB/gNB shall initiate intra-cell handover procedure which includes RRC Connection Reconfiguration procedure to reconfigure the DRBs to activate or de-activate the UP integrity/confidentiality as per the received policy from SMF. In case of the target ng-eNB/gNB receives both UE security capability and UP security policy, then ng-eNB/gNB initiates the intra-cell handover procedure which contains selected algorithm and an NCC to the UE. New UP keys shall be derived and used at both the UE and the target ng-eNB/gNB. At an N2-handover the SMF shall send the UE's UP security policy to the target ng-eNB/gNB via the target AMF. The target ng-eNB/gNB shall reject all PDU sessions for which it cannot comply with the corresponding received UP security policy and indicate the reject-cause to the SMF via the target AMF. For all other PDU sessions, the target ng-eNB/gNB shall activate UP confidentiality and/or UP integrity protection per DRB according to the received UE's UP security policy. Only if the UE indicates that it supports use of integrity protection with ng-eNB, the target ng-eNB can activate UP integrity protection. At interworking-handover from EPS to 5GS, the SMF+PGW-C provides the UE's UP security policy to the target ng-eNB/gNB via the target AMF. The target ng-eNB shall determine from the UP security policy received from the AMF together with the UE indication that it supports user plane integrity protection with ng-eNB in UE EPS security capabilities (i.e. bit EIA7), whether to activate user plane integrity protection with the UE or not. The target ng-eNB/gNB shall reject all DRBs for which it cannot comply with the corresponding UP integrity protection policy in the UP security policy and indicate the reject-cause to the source MME via the target AMF. For all other DRBs, the target ng-eNB/gNB shall activate UP integrity protection per DRB according to the used UP security policy. Only if the UE indicates that it supports use of user plane integrity protection with ng-eNB, the target ng-eNB can activate UP integrity protection. If the target AMF detects in a Registration procedure following interworking-handover from EPS to 5GS, and becomes aware of that there is a mismatch between the UE EPS security capabilities received from the source MME and the one received from the UE, and that the target ng-eNB may not have the UE capability indicating UP IP support in UE EPS security capabilities, then the AMF shall send an N2 CONTEXT MODIFICATION REQUEST message to inform the target ng-eNB about the correct UE EPS security capabilities and target ng-eNB shall take the new UE EPS security capabilities into account. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.6.1 |
3,897 | – ReportConfigNR | The IE ReportConfigNR specifies criteria for triggering of an NR measurement reporting event or of a CHO, CPA or CPC event or of an L2 U2N relay measurement reporting event. For events labelled AN with N equal to 1, 2 and so on, measurement reporting events and CHO, CPA or CPC events are based on cell measurement results, which can either be derived based on SS/PBCH block or CSI-RS. Event A1: Serving becomes better than absolute threshold; Event A2: Serving becomes worse than absolute threshold; Event A3: Neighbour becomes amount of offset better than PCell/PSCell; Event A4: Neighbour becomes better than absolute threshold; Event A5: PCell/PSCell becomes worse than absolute threshold1 AND Neighbour/SCell becomes better than another absolute threshold2; Event A6: Neighbour becomes amount of offset better than SCell; Event D1: Distance between UE and a reference location referenceLocation1 becomes larger than configured threshold distanceThreshFromReference1 and distance between UE and a reference location referenceLocation2 becomes shorter than configured threshold distanceThreshFromReference2; CondEvent A3: Conditional reconfiguration candidate becomes amount of offset better than PCell/PSCell; CondEvent A4: Conditional reconfiguration candidate becomes better than absolute threshold where condEventA4 can also be used for current PSCell (i.e., in case it is configured as candidate PSCell for CondEvent A4 evaluation) for CHO with candidate SCG(s) case; CondEvent A5: PCell/PSCell becomes worse than absolute threshold1 AND Conditional reconfiguration candidate becomes better than another absolute threshold2; CondEvent D1: Distance between UE and a reference location referenceLocation1 becomes larger than configured threshold distanceThreshFromReference1 and distance between UE and a reference location referenceLocation2 of conditional reconfiguration candidate becomes shorter than configured threshold distanceThreshFromReference2; CondEvent D2: Distance between UE and a moving reference location determined based on referenceLocation1 becomes larger than configured threshold distanceThreshFromReference1 and distance between UE and a moving reference location determined based on referenceLocation2 of conditional reconfiguration candidate becomes shorter than configured threshold distanceThreshFromReference2; CondEvent T1: Time measured at UE becomes more than configured threshold t1-Threshold but is less than t1-Threshold + duration; Event X1: Serving L2 U2N Relay UE becomes worse than absolute threshold1 AND NR Cell becomes better than another absolute threshold2; Event X2: Serving L2 U2N Relay UE becomes worse than absolute threshold; For event I1, measurement reporting event is based on CLI measurement results, which can either be derived based on SRS-RSRP or CLI-RSSI. Event I1: Interference becomes higher than absolute threshold. The reporting events concerning Aerial UE altitude are labelled HN with N equal to 1 and 2. Additionally, the reporting events concerning Aerial UE altitude and the neighboring cell measurements simultaneously are labelled AMHN with M equal to 3, 4, 5 and N equal to 1, 2. Event H1: Aerial UE altitude becomes higher than a threshold; Event H2: Aerial UE altitude becomes lower than a threshold. Event A3H1: Neighbour becomes offset better than SpCell and the Aerial UE altitude becomes higher than a threshold. Event A3H2: Neighbour becomes offset better than SpCell and the Aerial UE altitude becomes lower than a threshold. Event A4H1: Neighbour becomes better than threshold1 and the Aerial UE altitude becomes higher than a threshold2. Event A4H2: Neighbour becomes better than threshold1 and the Aerial UE altitude becomes lower than a threshold2. Event A5H1: SpCell becomes worse than threshold1 and neighbour becomes better than threshold2 and the Aerial UE altitude becomes higher than a threshold3. Event A5H2: SpCell becomes worse than threshold1 and neighbour becomes better than threshold2 and the Aerial UE altitude becomes lower than a threshold3. ReportConfigNR information element -- ASN1START -- TAG-REPORTCONFIGNR-START ReportConfigNR ::= SEQUENCE { reportType CHOICE { periodical PeriodicalReportConfig, eventTriggered EventTriggerConfig, ..., reportCGI ReportCGI, reportSFTD ReportSFTD-NR, condTriggerConfig-r16 CondTriggerConfig-r16, cli-Periodical-r16 CLI-PeriodicalReportConfig-r16, cli-EventTriggered-r16 CLI-EventTriggerConfig-r16, rxTxPeriodical-r17 RxTxPeriodical-r17, reportOnScellActivation-r18 ReportOnScellActivation-r18 } } ReportCGI ::= SEQUENCE { cellForWhichToReportCGI PhysCellId, ..., [[ useAutonomousGaps-r16 ENUMERATED {setup} OPTIONAL -- Need R ]] } ReportSFTD-NR ::= SEQUENCE { reportSFTD-Meas BOOLEAN, reportRSRP BOOLEAN, ..., [[ reportSFTD-NeighMeas ENUMERATED {true} OPTIONAL, -- Need R drx-SFTD-NeighMeas ENUMERATED {true} OPTIONAL, -- Need R cellsForWhichToReportSFTD SEQUENCE (SIZE (1..maxCellSFTD)) OF PhysCellId OPTIONAL -- Need R ]] } CondTriggerConfig-r16 ::= SEQUENCE { condEventId CHOICE { condEventA3 SEQUENCE { a3-Offset MeasTriggerQuantityOffset, hysteresis Hysteresis, timeToTrigger TimeToTrigger }, condEventA5 SEQUENCE { a5-Threshold1 MeasTriggerQuantity, a5-Threshold2 MeasTriggerQuantity, hysteresis Hysteresis, timeToTrigger TimeToTrigger }, ..., condEventA4-r17 SEQUENCE { a4-Threshold-r17 MeasTriggerQuantity, hysteresis-r17 Hysteresis, timeToTrigger-r17 TimeToTrigger }, condEventD1-r17 SEQUENCE { distanceThreshFromReference1-r17 INTEGER(0.. 65525), distanceThreshFromReference2-r17 INTEGER(0.. 65525), referenceLocation1-r17 ReferenceLocation-r17, referenceLocation2-r17 ReferenceLocation-r17, hysteresisLocation-r17 HysteresisLocation-r17, timeToTrigger-r17 TimeToTrigger }, condEventT1-r17 SEQUENCE { t1-Threshold-r17 INTEGER (0..549755813887), duration-r17 INTEGER (1..6000) }, condEventD2-r18 SEQUENCE { distanceThreshFromReference1-r18 INTEGER(0.. 65525), distanceThreshFromReference2-r18 INTEGER(0.. 65525), referenceLocation1-r18 ReferenceLocation-r17, referenceLocation2-r18 ReferenceLocation-r17, hysteresisLocation-r18 HysteresisLocation-r17, timeToTrigger-r18 TimeToTrigger } }, rsType-r16 NR-RS-Type, ..., [[ nesEvent-r18 ENUMERATED {true} OPTIONAL -- Need R ]] } EventTriggerConfig::= SEQUENCE { eventId CHOICE { eventA1 SEQUENCE { a1-Threshold MeasTriggerQuantity, reportOnLeave BOOLEAN, hysteresis Hysteresis, timeToTrigger TimeToTrigger }, eventA2 SEQUENCE { a2-Threshold MeasTriggerQuantity, reportOnLeave BOOLEAN, hysteresis Hysteresis, timeToTrigger TimeToTrigger }, eventA3 SEQUENCE { a3-Offset MeasTriggerQuantityOffset, reportOnLeave BOOLEAN, hysteresis Hysteresis, timeToTrigger TimeToTrigger, useAllowedCellList BOOLEAN }, eventA4 SEQUENCE { a4-Threshold MeasTriggerQuantity, reportOnLeave BOOLEAN, hysteresis Hysteresis, timeToTrigger TimeToTrigger, useAllowedCellList BOOLEAN }, eventA5 SEQUENCE { a5-Threshold1 MeasTriggerQuantity, a5-Threshold2 MeasTriggerQuantity, reportOnLeave BOOLEAN, hysteresis Hysteresis, timeToTrigger TimeToTrigger, useAllowedCellList BOOLEAN }, eventA6 SEQUENCE { a6-Offset MeasTriggerQuantityOffset, reportOnLeave BOOLEAN, hysteresis Hysteresis, timeToTrigger TimeToTrigger, useAllowedCellList BOOLEAN }, ..., [[ eventX1-r17 SEQUENCE { x1-Threshold1-Relay-r17 SL-MeasTriggerQuantity-r16, x1-Threshold2-r17 MeasTriggerQuantity, reportOnLeave-r17 BOOLEAN, hysteresis-r17 Hysteresis, timeToTrigger-r17 TimeToTrigger, useAllowedCellList-r17 BOOLEAN }, eventX2-r17 SEQUENCE { x2-Threshold-Relay-r17 SL-MeasTriggerQuantity-r16, reportOnLeave-r17 BOOLEAN, hysteresis-r17 Hysteresis, timeToTrigger-r17 TimeToTrigger }, eventD1-r17 SEQUENCE { distanceThreshFromReference1-r17 INTEGER(1.. 65525), distanceThreshFromReference2-r17 INTEGER(1.. 65525), referenceLocation1-r17 ReferenceLocation-r17, referenceLocation2-r17 ReferenceLocation-r17, reportOnLeave-r17 BOOLEAN, hysteresisLocation-r17 HysteresisLocation-r17, timeToTrigger-r17 TimeToTrigger } ]], [[ eventH1-r18 SEQUENCE { h1-Threshold-r18 Altitude-r18, h1-Hysteresis-r18 HysteresisAltitude-r18, reportOnLeave-r18 BOOLEAN, timeToTrigger-r18 TimeToTrigger, includeAltitudeUE-r18 BOOLEAN, simulMultiTriggerSingleMeasReport-r18 BOOLEAN }, eventH2-r18 SEQUENCE { h2-Threshold-r18 Altitude-r18, h2-Hysteresis-r18 HysteresisAltitude-r18, reportOnLeave-r18 BOOLEAN, timeToTrigger-r18 TimeToTrigger, includeAltitudeUE-r18 BOOLEAN, simulMultiTriggerSingleMeasReport-r18 BOOLEAN }, eventA3H1-r18 SEQUENCE { a3-Offset-r18 MeasTriggerQuantityOffset, reportOnLeave-r18 BOOLEAN, a3-Hysteresis-r18 Hysteresis, timeToTrigger-r18 TimeToTrigger, useAllowedCellList-r18 BOOLEAN, h1-Threshold-r18 Altitude-r18, h1-Hysteresis-r18 HysteresisAltitude-r18, includeAltitudeUE-r18 BOOLEAN, simulMultiTriggerSingleMeasReport-r18 BOOLEAN }, eventA3H2-r18 SEQUENCE { a3-Offset-r18 MeasTriggerQuantityOffset, reportOnLeave-r18 BOOLEAN, a3-Hysteresis-r18 Hysteresis, timeToTrigger-r18 TimeToTrigger, useAllowedCellList-r18 BOOLEAN, h2-Threshold-r18 Altitude-r18, h2-Hysteresis-r18 HysteresisAltitude-r18, includeAltitudeUE-r18 BOOLEAN, simulMultiTriggerSingleMeasReport-r18 BOOLEAN }, eventA4H1-r18 SEQUENCE { a4-Threshold-r18 MeasTriggerQuantity, reportOnLeave-r18 BOOLEAN, a4-Hysteresis-r18 Hysteresis, timeToTrigger-r18 TimeToTrigger, useAllowedCellList-r18 BOOLEAN, h1-Threshold-r18 Altitude-r18, h1-Hysteresis-r18 HysteresisAltitude-r18, includeAltitudeUE-r18 BOOLEAN, simulMultiTriggerSingleMeasReport-r18 BOOLEAN }, eventA4H2-r18 SEQUENCE { a4-Threshold-r18 MeasTriggerQuantity, reportOnLeave-r18 BOOLEAN, a4-Hysteresis-r18 Hysteresis, timeToTrigger-r18 TimeToTrigger, useAllowedCellList-r18 BOOLEAN, h2-Threshold-r18 Altitude-r18, h2-Hysteresis-r18 HysteresisAltitude-r18, includeAltitudeUE-r18 BOOLEAN, simulMultiTriggerSingleMeasReport-r18 BOOLEAN }, eventA5H1-r18 SEQUENCE { a5-Threshold1-r18 MeasTriggerQuantity, a5-Threshold2-r18 MeasTriggerQuantity, reportOnLeave-r18 BOOLEAN, a5-Hysteresis-r18 Hysteresis, timeToTrigger-r18 TimeToTrigger, useAllowedCellList-r18 BOOLEAN, h1-Threshold-r18 Altitude-r18, h1-Hysteresis-r18 HysteresisAltitude-r18, includeAltitudeUE-r18 BOOLEAN, simulMultiTriggerSingleMeasReport-r18 BOOLEAN }, eventA5H2-r18 SEQUENCE { a5-Threshold1-r18 MeasTriggerQuantity, a5-Threshold2-r18 MeasTriggerQuantity, reportOnLeave-r18 BOOLEAN, a5-Hysteresis-r18 Hysteresis, timeToTrigger-r18 TimeToTrigger, useAllowedCellList-r18 BOOLEAN, h2-Threshold-r18 Altitude-r18, h2-Hysteresis-r18 HysteresisAltitude-r18, includeAltitudeUE-r18 BOOLEAN, simulMultiTriggerSingleMeasReport-r18 BOOLEAN } ]] }, rsType NR-RS-Type, reportInterval ReportInterval, reportAmount ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity}, reportQuantityCell MeasReportQuantity, maxReportCells INTEGER (1..maxCellReport), reportQuantityRS-Indexes MeasReportQuantity OPTIONAL, -- Need R maxNrofRS-IndexesToReport INTEGER (1..maxNrofIndexesToReport) OPTIONAL, -- Need R includeBeamMeasurements BOOLEAN, reportAddNeighMeas ENUMERATED {setup} OPTIONAL, -- Need R ..., [[ measRSSI-ReportConfig-r16 MeasRSSI-ReportConfig-r16 OPTIONAL, -- Need R useT312-r16 BOOLEAN OPTIONAL, -- Need M includeCommonLocationInfo-r16 ENUMERATED {true} OPTIONAL, -- Need R includeBT-Meas-r16 SetupRelease {BT-NameList-r16} OPTIONAL, -- Need M includeWLAN-Meas-r16 SetupRelease {WLAN-NameList-r16} OPTIONAL, -- Need M includeSensor-Meas-r16 SetupRelease {Sensor-NameList-r16} OPTIONAL -- Need M ]], [[ coarseLocationRequest-r17 ENUMERATED {true} OPTIONAL, -- Need R reportQuantityRelay-r17 SL-MeasReportQuantity-r16 OPTIONAL -- Need R ]], [[ numberOfTriggeringCells-r18 INTEGER (2..maxCellReport) OPTIONAL, -- Need R cellIndividualOffsetList-r18 SEQUENCE (SIZE (1..maxNrofCellMeas)) OF CellIndividualOffsetList-r18 OPTIONAL -- Need R ]] } PeriodicalReportConfig ::= SEQUENCE { rsType NR-RS-Type, reportInterval ReportInterval, reportAmount ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity}, reportQuantityCell MeasReportQuantity, maxReportCells INTEGER (1..maxCellReport), reportQuantityRS-Indexes MeasReportQuantity OPTIONAL, -- Need R maxNrofRS-IndexesToReport INTEGER (1..maxNrofIndexesToReport) OPTIONAL, -- Need R includeBeamMeasurements BOOLEAN, useAllowedCellList BOOLEAN, ..., [[ measRSSI-ReportConfig-r16 MeasRSSI-ReportConfig-r16 OPTIONAL, -- Need R includeCommonLocationInfo-r16 ENUMERATED {true} OPTIONAL, -- Need R includeBT-Meas-r16 SetupRelease {BT-NameList-r16} OPTIONAL, -- Need M includeWLAN-Meas-r16 SetupRelease {WLAN-NameList-r16} OPTIONAL, -- Need M includeSensor-Meas-r16 SetupRelease {Sensor-NameList-r16} OPTIONAL, -- Need M ul-DelayValueConfig-r16 SetupRelease { UL-DelayValueConfig-r16 } OPTIONAL, -- Need M reportAddNeighMeas-r16 ENUMERATED {setup} OPTIONAL -- Need R ]], [[ ul-ExcessDelayConfig-r17 SetupRelease { UL-ExcessDelayConfig-r17 } OPTIONAL, -- Need M coarseLocationRequest-r17 ENUMERATED {true} OPTIONAL, -- Need R reportQuantityRelay-r17 SL-MeasReportQuantity-r16 OPTIONAL -- Need R ]] } NR-RS-Type ::= ENUMERATED {ssb, csi-rs} MeasTriggerQuantity ::= CHOICE { rsrp RSRP-Range, rsrq RSRQ-Range, sinr SINR-Range } MeasTriggerQuantityOffset ::= CHOICE { rsrp INTEGER (-30..30), rsrq INTEGER (-30..30), sinr INTEGER (-30..30) } MeasReportQuantity ::= SEQUENCE { rsrp BOOLEAN, rsrq BOOLEAN, sinr BOOLEAN } MeasRSSI-ReportConfig-r16 ::= SEQUENCE { channelOccupancyThreshold-r16 RSSI-Range-r16 OPTIONAL -- Need R } CLI-EventTriggerConfig-r16 ::= SEQUENCE { eventId-r16 CHOICE { eventI1-r16 SEQUENCE { i1-Threshold-r16 MeasTriggerQuantityCLI-r16, reportOnLeave-r16 BOOLEAN, hysteresis-r16 Hysteresis, timeToTrigger-r16 TimeToTrigger }, ... }, reportInterval-r16 ReportInterval, reportAmount-r16 ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity}, maxReportCLI-r16 INTEGER (1..maxCLI-Report-r16), ... } CLI-PeriodicalReportConfig-r16 ::= SEQUENCE { reportInterval-r16 ReportInterval, reportAmount-r16 ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity}, reportQuantityCLI-r16 MeasReportQuantityCLI-r16, maxReportCLI-r16 INTEGER (1..maxCLI-Report-r16), ... } RxTxPeriodical-r17 ::= SEQUENCE { rxTxReportInterval-r17 RxTxReportInterval-r17 OPTIONAL, -- Need R reportAmount-r17 ENUMERATED {r1, infinity, spare6, spare5, spare4, spare3, spare2, spare1}, ... } RxTxReportInterval-r17 ::= ENUMERATED {ms80,ms120,ms160,ms240,ms320,ms480,ms640,ms1024,ms1280,ms2048,ms2560,ms5120,spare4,spare3,spare2,spare1} MeasTriggerQuantityCLI-r16 ::= CHOICE { srs-RSRP-r16 SRS-RSRP-Range-r16, cli-RSSI-r16 CLI-RSSI-Range-r16 } MeasReportQuantityCLI-r16 ::= ENUMERATED {srs-rsrp, cli-rssi} ReportOnScellActivation-r18 ::= SEQUENCE { rsType NR-RS-Type, reportQuantityRS-Indexes MeasReportQuantity, maxNrofRS-IndexesToReport INTEGER (1..maxNrofIndexesToReport), includeBeamMeasurements BOOLEAN } CellIndividualOffsetList-r18 ::= SEQUENCE { physCellId-r18 PhysCellId, cellIndividualOffset-r18 Q-OffsetRangeList } -- TAG-REPORTCONFIGNR-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,898 | 5.3.7.7 T301 expiry or selected cell/L2 U2N Relay UE no longer suitable | The UE shall: 1> if timer T301 expires; or 1> if the selected cell becomes no longer suitable according to the cell selection criteria as specified in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]; or 1> if the (re)selected L2 U2N Relay UE becomes unsuitable; or 1> upon reception of NotificationMessageSidelink indicating relayUE-HO or relayUE-CellReselection; or 1> upon PC5 unicast link release indicated by upper layer at L2 U2N Remote UE: 2> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with release cause 'RRC connection failure'. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.7.7 |
3,899 | O.3 A PDU Session targeting a predefined group formed of multiple sub-groups | In the case when the UE Application uses IP or Ethernet multicast, 5GS allows UE to simultaneously send data to different groups with different QoS policy via the following: - UE establishes a PDU Session to a DNN and S-NSSAI, which can be a special DNN and S-NSSAI configured by the operator for e.g. an electrical system. The DNN and S-NSSAI is associated with a 5GVN group, which is defined as a combination of multiple sub-groups (IP or Ethernet multicast groups). - The 5G VN group and each sub-group is associated with a separate multicast address and QoS, the QoS for a 5G VN group is set to refer to the QoS of the sub-group that has the strictest QoS requirements among all the sub-group groups. When a UE belongs to multiple groups, the QoS provisioning for the groups needs to be done in the order that enables the the strictest QoS profile to be selected for the UE. For each group, its members, multicast address, corresponding QoS information, associated DNN and S-NSSAI are provisioned as part of the AF requested QoS information as described in clause 6.1.3.28 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. - The application sends traffic to a multicast address depending on which group(s) it wants to target. For example, an application sends traffic to the multicast address associated with the 5G VN group. This allows an application to send a single packet reaching multiple destinations and also multiple groups. Figure O.3-1 shows a PDU Session targeting a predefined group formed of multiple sub-groups as an example. - Group1 (G1): a group of multicast address 1 with members UE1 and UE2 is associated with / mapped to 5GVN.1 group. The QoS for the group is set to QoS1. For G1, its members, multicast address 1, corresponding QoS1, DNN and S-NSSAI are provisioned as part of the AF requested QoS information for 5GVN.1 group as described in clause 6.1.3.28 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. - Group2 (G2): a group of multicast address 2 with members UE1 and UE3 is associated with / mapped to 5GVN.2 group. The QoS for the group is set to QoS2. For G2, its members, multicast address 2 and corresponding QoS2, DNN and S-NSSAI are provisioned as part of the AF requested QoS information for 5GVN.2 group as described in clause 6.1.3.28 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. - GroupA (GA): a group of multicast address A with members UE1, UE2 and UE3 is associated with 5GVN.A group. G1 and G2 are combined to form the GA. The QoS for the 5GVN.A group is indicated to refer to the strictest QoS among other groups the UE belongs to. For GA, its members, multicast address A and corresponding QoS indication, DNN and S-NSSAI are provisioned as part of the AF requested QoS information for 5GVN.A group as described in clause 6.1.3.28 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. - During establishment or modification procedure for PDU Sessions targeting to the DNN and S-NSSAI, or upon detection of the UE joining a multicast address, the SMF and PCF can jointly use the AF requested QoS information to set up the QoS flow in respective member's PDU Session. As a result: - There will have two QoS flows in UE1's PDU Session targeting to DNN and S-NSSAI, one QoS flow is used to carry data destined to multicast address 1 with QoS1, the other one is used to carry data destined to multicast address 2 with QoS2. With the QoS indication for GA, the higher QoS between QoS1 of G1 and QoS2 of G2 is selected for UE1 since the UE1 belongs to both the G1 and G2, then the QoS flow with higher QoS requirements (QoS Flow 1) is also used to carry data destined to multicast address A. - There will have one QoS flow in UE2's PDU Session targeting to DNN and S-NSSAI, this QoS flow (QoS Flow 2) is used to carry data destined to multicast address 1 with QoS1. With the QoS indication for GA, the QoS1 of G1 is selected for UE1 since the UE2 only belongs to G1, then the same QoS flow is also used to carry data destined to multicast address A. - There will have one QoS flow in UE3's PDU Session targeting to DNN and S-NSSAI, this QoS flow (QoS Flow 3) is used to carry data destined to multicast address 2 with QoS2. With the QoS indication for GA, the QoS2 of G2 is selected for UE3 since the UE3 only belongs to G2, then the same QoS flow is also used to carry data destined to multicast address A. - UE1 sends data with multicast address A (MA.A) to a UPF via QoS Flow 1 of UE1's PDU Session for 5GVN.A group. The UPF forwards the packet to UE2 as it is a member of multicast group represented by multicast address A (MA.A) via the QoS Flow 2 of UE2's PDU Session and forwards the packet to UE3 as it is a member of the multicast group represented by multicast address A (MA.A) via the QoS Flow 3 of UE3's PDU Session. Figure O.3-1: A PDU Session targeting a predefined group formed of multiple sub-groups | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | O.3 |
3,900 | 4.15.13.6.2 Member UE Selection assistance with end-to-end data volume transfer time related filtering criteria | Figure 4.15.13.6.2-1: Assistance to member UE selection for end-to-end data volume transfer time related filtering criteria 1. AF subscribes to the member UE selection assistance functionality by invoking Nnef_MemberUESelectionAssistance_subscribe request including the Application ID, DNN/S NSSAI, AoI, and the end-to-end data volume transfer time related filtering criteria including the average end-to-end data volume transfer time and/or the variance of the transfer time. 2. NEF verifies the authorization of the AF Request and identifies which information needs to be collected and executed based on the end-to-end data volume transfer time related filtering criteria provided by the AF. 3. S-NSSAI/DNN are not included in the request from the AF, the NEF derives the S-NSSAI and DNN which this Application has access to. NEF discovers and selects the NWDAF(s) by invoking Nudm_UECM_Get or Nnrf_NFDiscovery_Request including Analytics ID = E2E data volume transfer time, AoI, S-NSSAI, etc. 4. NEF sends an Analytics request/subscribe to NWDAF by invoking Nnwdaf_AnalyticsSubscription_Subscribe / Nnwdaf_AnalyticsInfo_Request including Analytics ID = E2E data volume transfer time, Application ID, DNN, S-NSSAI, AoI, and target UEs based on the initial UE list obtained from the AF. 5. The NWDAF collects data from multiple sources for end-to-end data volume transfer time analytics as specified in clause 6.18.2 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. 6. The NWDAF provides the required output analytics to the consumer NF as specified in clause 6.18.4 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50] by means of either Nnwdaf_AnalyticsInfo_Request response or Nnwdaf_AnalyticsSubscription_Notify, depending on the service used in step 4. 7. Based on the analytics received from the NWDAF, the NEF consolidates results and derives the list(s) of candidate UE(s) that fulfil the filtering criteria requested by the AF. The NEF may use the average end-to-end data volume transfer time of specific volumes of data and/or the variance to derive the list(s) of candidate UEs that meet the requirements from the AF. 8. NEF sends a Nnef_MemberUESelectionAssistance_Notify request to the AF including the list(s) of candidate UE(s) and additional information. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.13.6.2 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.