Search is not available for this dataset
doc_id
int64 1
6.72k
⌀ | Section
stringlengths 5
247
⌀ | Content
stringlengths 501
147k
⌀ | Source
stringclasses 456
values | Document Title
stringclasses 22
values | Working Group
stringclasses 21
values | Series Subject
stringclasses 9
values | Subclause
stringlengths 1
13
⌀ |
|---|---|---|---|---|---|---|---|
4,601 | 7.8.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 wide band intermodulation requirements are defined with the uplink active on the band(s) other than the band whose downlink is being tested. The UE shall meet the requirements specified in subclause 7.8.1.1 for each component carrier while all downlink carriers are active. 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 a component carrier configured in Band 46 or Band 49, the requirements specified in subclause 7.8.1.1 are replaced by the requirements in Table 7.8.1-1A-0. Table 7.8.1.1A-0: Wide band intermodulation 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 wideband intermodulation requirements of subclause 7.8.1A do not apply. For intra-band contiguous carrier aggegation 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 7.8.1A-1 with the uplink configuration set according to Table 7.-1 for the applicable carrier aggreagation 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 Table 7.8.1A-1 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 Table 7.8.1A-1. 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.8.1A-1. Table 7.8.1A-1: Wide band intermodulation For intra-band non-contiguous carrier aggregation with one uplink carrier and two or more downlink sub-blocks, the wide band intermodulation 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.8.1.1 and in this subclause for one component carrier and two or more component carriers per sub-block, respectively. The requirements apply for out-of-gap interferers while all downlink carriers are active. For combinations of intra-band and inter-band carrier aggregation and one uplink carrier 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. For these uplink configurations, the UE shall meet the wide-band intermodulation requirements for intra-band non-contiguous carrier aggregation with RIBNC = 0 dB for all sub-block gaps (Table 7.3.1A-3) for the two or more non-contiguous downlink sub-blocks, the requirements for intra-band contiguous carrier aggregation for the contiguously aggregated downlink carriers and for any remaining component carrier(s) the requirements specified in subclause 7.8.1. For contiguously aggregated component carriers configured in Band 46, the said requirements for intra-band contiguous carrier aggregation of two or more downlink carriers are replaced by requirements in Table 7.8.1A-2. For non-contiguously aggregated component carriers configured in Band 46, the said requirements are applied to each sub-block for out-of-gap interferers. For the sub-block with a single component carrier, the requirement is replaced by Table 7.8.1.1A-0. For the sub-block with two or more contiguous component carriers, the requirement is replaced by Table 7.8.1.1A-2. 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. Table 7.8.1A-2: Wide band intermodulation | 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.8.1A |
4,602 | .1 Delete Session Response | A Delete Session Response message shall be sent on the S11 interface by the SGW to the MME and on the S5/S8 interface by the PGW to the SGW as part of the following procedures: - EUTRAN Initial Attach - UE, HSS or MME Initiated Detach - UE or MME Requested PDN Disconnection It shall also be sent on the S4 interface by the SGW to the SGSN and on the S5/S8 interface by the PGW to the SGW as part of the procedures: - MS, HLR or SGSN initiated detach procedure - Combined GPRS/IMSI Attach - MS and SGSN Initiated Default Bearer Deactivation Procedure using S4 On the S11 interface by the SGW to the MME as part of the procedures: - Tracking Area Update with SGW Change - S1 Based Handover with SGW Change - X2 Based Handover with SGW Relocation - E-UTRAN to UTRAN Iu mode Inter RAT handover with SGW change - E-UTRAN to GERAN A/Gb mode Inter RAT handover with SGW change - Inter RAT handover cancel with SGW change - MME to Gn/Gp SGSN combined hard handover and SRNS relocation procedure - MME to SGSN Routing Area Update - E-UTRAN to Gn/Gp SGSN Inter RAT handover - S1 Based handover cancel with SGW change - Optimised Active Handover: E-UTRAN Access to CDMA2000 HRPD Access - MME triggered Serving GW relocation And on the S4 interface by the SGW to the SGSN as part of the procedures: - Enhanced Serving RNS Relocation with SGW relocation using S4 - Routing Area Update with SGW change - SGSN to MME Tracking Area Update with SGW change - Serving RNS relocation with SGW change - UTRAN Iu mode to E-UTRAN Inter RAT handover with SGW change - GERAN A/Gb mode to E-UTRAN Inter RAT handover with SGW change - S4 SGSN to Gn/Gp SGSN Routeing Area Update - S4 SGSN to Gn/Gp SGSN Serving RNS Relocation Procedures - S4 SGSN to Gn/Gp SGSN PS handover Procedures - S4-SGSN triggered Serving GW relocation The message shall also be sent on the S2b interface by the PGW to the ePDG as part of procedures: - UE/ePDG Initiated Detach with GTP on S2b - UE Requested PDN Disconnection with GTP on S2b - HSS/AAA Initiated Detach with GTP on S2b The message shall also be sent on the S2a interface by the PGW to the TWAN as part of procedures: - UE/TWAN Initiated Detach and UE/TWAN Requested PDN Disconnection in WLAN on GTP S2a - HSS/AAA Initiated Detach in WLAN on GTP S2a This message may also be sent on S5/S8 interface by the PGW to the SGW: - If Downlink Data Notification Acknowledge message with Context not found cause value is received. The sending entity shall include Cause IE in the Delete Session Response message. The IE indicates if the peer has deleted the bearer, or not. Possible Cause values are specified in Table 8.4-1. Message specific cause values are: - "Context not found". - "Invalid peer". Table .1-1 specifies the presence of the IEs in the message. Table .1-1: Information Elements in a Delete Session Response Table 7.2.10.1-2: Load Control Information within Delete Session Response Table 7.2.10.1-3: Overload Control Information within Delete Session Response | 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 | .1 |
4,603 | – PathlossReferenceRS | The IE PathlossReferenceRS is used to configure a Reference Signal (e.g. a CSI-RS config or a SS block) to be used for path loss estimation for PUSCH, PUCCH and SRS for unified TCI state operation. PathlossReferenceRS information element -- ASN1START -- TAG-PATHLOSSREFERENCERS-START PathlossReferenceRS-r17 ::= SEQUENCE { pathlossReferenceRS-Id-r17 PathlossReferenceRS-Id-r17, referenceSignal-r17 CHOICE { ssb-Index SSB-Index, csi-RS-Index NZP-CSI-RS-ResourceId }, additionalPCI-r17 AdditionalPCIIndex-r17 OPTIONAL -- Cond RS-SSB } -- TAG-PATHLOSSREFERENCERS-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,604 | 6.7.3.0 Initial AS security context establishment | This clause provides the details for AS security algorithms negotiation and consideration during the UE initial AS security context establishment. Each gNB/ng-eNB shall be configured via network management with lists of algorithms which are allowed for usage. There shall be one list for integrity algorithms, and one for ciphering algorithms. These lists shall be ordered according to a priority decided by the operator. When AS security context is to be established in the gNB/ng-eNB, the AMF shall send the UE 5G security capabilities to the gNB/ng-eNB. The gNB/ng-eNB shall choose the ciphering algorithm which has the highest priority from its configured list and is also present in the UE 5G security capabilities. The gNB/ng-eNB shall choose the integrity algorithm which has the highest priority from its configured list and is also present in the UE 5G security capabilities. The chosen algorithms shall be indicated to the UE in the AS SMC. The chosen ciphering algorithm is used for ciphering (when activated) of the user plane and RRC traffic. The chosen integrity algorithm is used for integrity protection (when activated) of the user plane and RRC traffic. Activation of ciphering and integrity protection for the RRC traffic shall be done as defined by clause 6.7.4. Activation of ciphering and integrity protection for the user plane traffic shall be done based on the UP security policy received from the SMF as defined by clause 6.6.2. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.7.3.0 |
4,605 | 8 Security of interworking 8.1 General | As described in TS 23.501[ System architecture for the 5G System (5GS) ] [2], in order to interwork with EPC, the UE can operate in Single Registration or Dual Registration mode. When operating in Dual Registration mode, the UE shall independently maintain and use two different security contexts, an EPS security context to interact with the Evolved Packet System and a 5G security context to interact with the 5G System. Therefore, during inter-system mobility, when the target system is EPS, the UE shall take into use the EPS security context and hence all the security mechanisms described in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10] are applicable. In the other direction, i.e. when the target system is the 5GC, the UE shall take into use the 5G security context and hence all the security mechanisms described in the present document are applicable. When operating in Single Registration mode, there are two cases depending on the support of the N26 interface between the AMF and the MME. In both cases the security mechanisms described in all the subsequent sub-clauses are applicable. Upon registration during mobility from EPS to 5GS, the UDM may decide to trigger the procedure defined in clause 6.1.5 based on the local operator authentication policy. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 8 |
4,606 | 6.1.3.1.3 Unsuccessful PDP context activation initiated by the MS 6.1.3.1.3.1 General | Upon receipt of an ACTIVATE PDP CONTEXT REQUEST message the network may reject the MS initiated PDP context activation by sending an ACTIVATE PDP CONTEXT REJECT message to the MS. The message shall contain a cause code that typically indicates one of the following causes: # 8: Operator Determined Barring; # 26: insufficient resources; # 27: missing or unknown APN; # 28: unknown PDP address or PDP type; # 29: user authentication failed; # 30: activation rejected by GGSN, Serving GW or PDN GW; # 31: activation rejected, unspecified; # 32: service option not supported; # 33: requested service option not subscribed; # 34: service option temporarily out of order; # 35: NSAPI already used. The network shall not send this cause code (see note 1); # 50: PDP type IPv4 only allowed; # 51: PDP type IPv6 only allowed; # 57: PDP type IPv4v6 only allowed; # 58: PDP type non IP only allowed; # 65: maximum number of PDP contexts reached; # 66: requested APN not supported in current RAT and PLMN combination; # 95 - 111: protocol errors; #112: APN restriction value incompatible with active PDP context; or #113: Multiple accesses to a PDN connection not allowed. NOTE 1: Pre-R99 network may send this cause code. The network may include a Back-off timer value IE in the ACTIVATE PDP CONTEXT REJECT message. If the SM cause value is #26 "insufficient resources" and if the request type in the ACTIVATE PDP CONTEXT REQUEST was set to "emergency", the network shall not include a Back-off timer value IE. If the Back-off timer value IE is included and the SM cause value is different from #26 "insufficient resources", #50 "PDP type IPv4 only allowed", #51 "PDP type IPv6 only allowed", #57 "PDP type IPv4v6 only allowed", #58 "PDP type non IP only allowed" and #65 "maximum number of PDP contexts reached", the network may include the Re-attempt indicator IE to indicate whether the MS is allowed to attempt a PDN connectivity procedure in the PLMN for the same in S1 mode, and whether another attempt in A/Gb and Iu mode or in S1 mode is allowed in an equivalent PLMN. If the SM cause value is #50 "PDP type IPv4 only allowed", #51 "PDP type IPv6 only allowed", #57 "PDP type IPv4v6 only allowed" or #58 "PDP type non IP only allowed", the network may include the Re-attempt indicator IE without Back-off timer value IE to indicate whether the MS is allowed to attempt a PDP context activation procedure in an equivalent PLMN for the same APN in A/Gb or Iu mode using the same PDP type. If the SM cause value is #66 "requested APN not supported in current RAT and PLMN combination", the network may include the Re-attempt indicator IE without Back-off timer value IE to indicate whether the MS is allowed to attempt a PDP context activation procedure in an equivalent PLMN for the same APN in A/Gb or Iu mode. Upon receipt of an ACTIVATE PDP CONTEXT REJECT message, the MS shall stop timer T3380 and enter/remain in state PDP-INACTIVE. If the ACTIVATE PDP CONTEXT REQUEST message was sent with request type set to "emergency" and the MS receives an ACTIVATE PDP CONTEXT REJECT message, then the MS may inform the upper layers of the failure to establish the emergency bearer. NOTE 2: This can result in the upper layers requesting establishment of a CS emergency call (if not already attempted in the CS domain) or initiating other implementation specific mechanisms, e.g. 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 ] [95] can result in the emergency call being attempted to another IP-CAN. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.1.3.1.3 |
4,607 | A.9 Monitoring of RF performance | RF Performance reflects the cell loading levels and abnormal conditions. In the Downlink, Power Resources are managed by the EUTRAN Cell(RAN). More Power Resources may help in increasing the Capacity of the System. Hence, there the power resources could be effectively used to optimize the Capacity of the System. Hence there is a need to keep monitoring the Power Resource Utilization in % and also in absolute terms. Monitoring of the quality of RF signal in the cell is useful for the purpose of NW planning and overall service quality assessment. Measurements of Channel Quality Indicator (CQI) reported by UEs is a useful metric reflecting RF signal quality and service quality. Timing advance measurements reflect the distance of the UE from the cell antenna. This information reflects the optimality of the cell antenna location with respect to the cell traffic and is useful in the NW planning process. Monitoring interference, both uplink and downlink, is an important aspect of monitoring RF performance. For this purpose, monitoring of UL interference power is useful. Interference signals in a number of different ways, including frequency, frequency band, direction of interfering signals, etc. can also be classified by System internal interference and External interference. By efficient frequency planning and careful Selection of base station locations, the impact of interference signal can be effectively controlled within an acceptable scope.uplink interference disturbs the base station receiver. Once the base station receiver is compromised, it leads to receiving code errors for the whole base station and the site’s entire service area is degraded including its network and service. Of course, customer satisfaction is negatively impacted. So it is very useful to monitor uplink interference of communication system to do network optimization. | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | A.9 |
4,608 | 5.4.13.5 Overload control | The AMF and UE may only use the procedure defined in this clause if both the UE and AMF indicate support for "Unavailability Period Support", see clause 5.4.13.1. A UE indicating support for "Unavailability Period Support" shall support the procedures defined in this clause when leaving coverage and re-gaining coverage for an NR satellite access. In order to avoid a large number of UEs causing excessive signalling load on the network when leaving coverage or re-gaining coverage after being out of coverage, the AMF may determine a Maximum Time Offset controlling when UEs are allowed to initiate NAS signalling with the network, as described in this clause. In this case, the AMF determines this Maximum Time Offset based on network configuration, high priority access and priority service as specified in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17] and TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. The AMF sends this Maximum Time Offset to individual UEs during the Registration procedure or UE Configuration Update procedure. If the UE receives a Maximum Time Offset from the network in a Registration Accept or UE Configuration Update Command message, the UE shall replace any previously received Maximum Time Offset on the same RAT type and PLMN with this one. When the UE knows a later time at which coverage will be lost and when the UE does not send Mobility Registration Update to the AMF in advance (see clause 5.4.13.1), the UE determines a random value up to the minimum of the latest Maximum Time Offset for this PLMN and RAT type and the time until coverage will be lost. The UE shall send the Mobility Registration Update at the time when coverage will be lost less the random value to the AMF indicating the loss of coverage. Upon returning to coverage after being out of coverage due to discontinuous coverage, the UE sets the discontinuous coverage wait timer value to a random value up to and including the latest Maximum Time Offset for this PLMN and RAT type, and starts this timer. The UE shall not initiate any NAS signalling on that RAT Type and PLMN while the discontinuous coverage wait timer is running. The UE shall stop the discontinuous coverage wait timer and initiate NAS signalling if the UE receives paging message, has pending emergency services or when UE enters a TAI outside the registration area. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.4.13.5 |
4,609 | 13.4 Public User Identity | A Public User Identity is any identity used by a user within the IMS subsystem for requesting communication to another user. The Public User Identity shall take the form of either a SIP URI (see IETF RFC 3261 [26]) or a Tel URI (see IETF RFC 3966 [45]). The 3GPP specifications describing the interfaces over which Public User Identities are transferred specify the allowed Public User Identity formats, in particular 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [81] for SIP signalling interfaces, 3GPP TS 29.229[ Cx and Dx interfaces based on the Diameter protocol; Protocol details ] [95] for Cx and Dx interfaces, 3GPP TS 29.329[ Sh interface based on the Diameter protocol; Protocol details ] [96] for Sh interface, 3GPP TS 29.165[ Inter-IMS Network to Network Interface (NNI) ] [97] for II-NNI interface. In the case the user identity is a telephone number, it shall be represented either by a Tel URI or by a SIP URI that includes a "user=phone" URI parameter and a "userinfo" part that shall follow the same format as the Tel URI. According to 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [81], the UE can use either: - a global number as defined in IETF RFC 3966 [45] and following E.164 format, as defined by ITU-T Recommendation E.164 [10] or - a local number, that shall include a "phone-context" parameter that identifies the scope of its validity, as per IETF RFC 3966 [45]. According to 3GPP TS 29.165[ Inter-IMS Network to Network Interface (NNI) ] [97] a global number as defined in IETF RFC 3966 [45] shall be used in a tel-URI or in the user portion of a SIP URI with the user=phone parameter when conveyed via a non-roaming II-NNI except when agreement exists between the operators to also allow other kinds of numbers. According to 3GPP TS 29.229[ Cx and Dx interfaces based on the Diameter protocol; Protocol details ] [95] and 3GPP TS 29.329[ Sh interface based on the Diameter protocol; Protocol details ] [96] the canonical forms of SIP URI and Tel URI shall be used over the corresponding Diameter interfaces. The canonical form of a SIP URI for a Public User Identity shall take the form "sip:username@domain" as specified in IETF RFC 3261 [26], clause 10.3. SIP URI comparisons shall be performed as defined in IETF RFC 3261 [26], clause 19.1.4. The canonical form of a Tel URI for a Public User Identity shall take the form "tel:+<CC><NDC><SN>" (max number of digits is 15), that represents an E.164 number and shall contain a global number without parameters and visual separators (see IETF RFC 3966[45], clause 3). Tel URI comparisons shall be performed as defined in IETF RFC 3966[45], clause 4. Public User Identities are stored in the HSS either as a distinct Public User Identity or as a Wildcarded Public User Identity. A distinct Public User Identity contains the Public User Identity that is used in routing and it is explicitly provisioned in the HSS. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 13.4 |
4,610 | 4.7.3.2.1 Combined GPRS attach procedure initiation | If the MS is in GMM state GMM-DEREGISTERED and in MM state MM IDLE, the MS initiates the combined GPRS attach procedure by sending an ATTACH REQUEST message to the network, starts timer T3310 and enters state GMM-REGISTERED-INITIATED and MM LOCATION UPDATING PENDING. If timer T3302 is currently running, the MS shall stop timer T3302. If timer T3311 is currently running, the MS shall stop timer T3311. The MS shall set the Mobile identity IE, old RAI and P-TMSI signature in the ATTACH REQUEST message as specified in subclause 4.7.3.1.1. Furthermore the MS shall include the TMSI status IE if no valid TMSI is available. If the MS initiates a combined GPRS attach procedure for GPRS services and "SMS-only service", the MS shall indicate "SMS only" in the Additional update type IE. If the MS has stored a valid LAI and the MS supports EMM combined procedures, the MS shall include it in the Old location area identification IE in the ATTACH REQUEST message. If the MS has stored a valid TMSI, the MS shall include the TMSI based NRI container IE in the ATTACH REQUEST message. In Iu mode, if the MS wishes to prolong the established PS signalling connection after the GPRS attach (for example, the MS has any CM application request pending), it may set a follow-on request pending indicator on (see subclause 4.7.13). | 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.3.2.1 |
4,611 | 6.3.7.2 Providing policy requirements that apply to multiple UE and hence to multiple PCF | An authorized Application Function may, via the NEF, provide policy requirements that apply to multiple UE(s) (which, for example, belong to group of UE(s) defined by subscription or to any UE). Such policy requirements shall apply to any existing or future PDU Sessions that match the parameters in the AF request, and they may apply to multiple PCF instance(s). NOTE: Application Function influence on traffic routing described in clause 5.6.7 is an example of such requirement. After relevant validation of the AF request (and possible parameter mapping), the NEF stores this request received from the AF into the selected UDR instance as the Data Subset of the Application data. The possible parameter mapping includes mapping UE (group) identifiers provided by the AF to identifiers used within the 5GC, e.g. from GPSI to SUPI and/or from External Group Identifier to Internal-Group Identifier. Parameter mapping may also include mapping from the identifier of the Application Function towards internal identifiers such as the DNN and/or the S-NSSAI. PCF(s) that need to receive AF requests that targets a DNN (and slice), and/or a group of UEs subscribe to receive notifications from the UDR about such AF request information. The PCF(s) can be configured (e.g. by OAM) to subscribe to receive notification of such AF request information from the UDR(s). The PCF(s) take(s) the received AF request information into account when making policy decisions for existing and future relevant PDU Sessions. In the case of existing PDU Sessions, the policy decision of the PCF instance(s) may trigger a PCC rule(s) change from the PCF to the SMF. The PCF subscription to notifications of AF requests described above may take place during PDU Session Establishment or PDU Session Modification, when the PCF(s) receive request(s) from the SMF for policy information related to the DNN (and slice), and/or the Internal-Group Identifier of UEs. For the PCF(s) that have subscribed to such notifications, the UDR(s) notify the PCF(s) of any AF request update. The NEF associates the AF request with information allowing to later modify or delete the AF request in the UDR; it associates the AF request with: - When the AF request targets PDU Sessions established by "any UE": the DNN, the slicing information target of the AF request, - When the request targets PDU Sessions established by UE(s) belonging to an Internal-Group: the DNN, the slicing information and the Internal-Group Identifier target of the application request. - The AF transaction identifier in the AF request. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.7.2 |
4,612 | 17.6.1 AAR Command | The AAR command, defined in Diameter NASREQ (IETF RFC 7155 [120]), is indicated by the Command-Code field set to 265 and the ‘R’ bit set in the Command Flags field. It, is sent by the GGSN to the BM-SC to request user authorization (authorize the activating UE to receive Data) , to modify an MBMS UE Context in the BM-SC or to register the GGSN for a particular multicast MBMS bearer service. When used for these purposes, the Additional-MBMS-Trace-Info AVP shall not be included. When the AAR command is used by the GGSN to modify an MBMS UE context in the BM-SC, it shall include all the parameters that have been changed according to the triggering Update MBMS Context Request, ref. fig. 35. The inclusion of CGI/SAI in the 3GPP-User-Location-Info AVP shall be according to the rules detailed in subclause 15.1.1a in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [3]). The Called-Station-Id AVP, Calling-Station-Id AVP, Framed-IP-Address AVP, Framed-IPv6-Prefix AVP and Framed-Interface-Id AVP shall not be included, The AAR command is also used when the GGSN needs to activate a Trace Session in the BM-SC. In this case the Called-Station-Id AVP, Calling-Station-Id AVP, Framed-IP-Address AVP, Framed-IPv6-Prefix AVP, Framed-Interface-Id AVP, and RAI AVP shall not be included. For more detailed description of Trace Session activation/deactivation procedures see 3GPP TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ] [69]. The relevant AVPs that are of use for the Gmb interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for Gmb purposes and should be ignored by the receiver or processed according to the relevant specifications. The bold marked AVPs in the message format indicate new optional AVPs for Gmb, or modified existing AVPs. Message Format: <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id > { Auth-Application-Id } { Origin-Host } { Origin-Realm } { Destination-Realm } { Auth-Request-Type } [ Destination-Host ] [ Called-Station-Id ] [ Calling-Station-Id ] [ Framed-IP-Address] [ Framed-IPv6-Prefix ] [ Framed-Interface-Id ] * [ Proxy-Info ] * [ Route-Record ] [ 3GPP-IMSI] [ RAI ] [ 3GPP-IMEISV ] [ 3GPP-RAT-Type ] [ 3GPP-User-Location-Info ] [ 3GPP-MS-TimeZone ] [ Additional-MBMS-Trace-Info ] The GGSN shall allocate a new Session-Id each time an AAR command is sent, except for the case when the AAR is sent to modify an existing MBMS UE Context in the BM-SC. A request for user authorisation for an MBMS bearer service is indicated by the presence of the MSISDN within the Calling-Station-Id AVP and the 3GPP-IMSI. Otherwise the request is for the GGSN to be authorised (i.e. registered) to receive the MBMS bearer service.The Framed-IPv6-Prefix AVP contains the IPv6 prefix of the multicast address identifying the MBMS bearer service. The Framed-Interface-Id AVP contains the IPv6 interface identifier of the multicast address identifying the MBMS bearer service. The Framed-IP-Address AVP contains the IPv4 multicast address identifying the MBMS bearer service. The Called-Station-Id AVP contains the Access Point Name (APN) on which the MBMS bearer service authorisation request was received. | 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.6.1 |
4,613 | 4.4.6.5 Time duration of Scheduled IP Throughput in DL | a) This measurement provides the time duration to transmit a data burst excluding the last piece of data transmitted in the TTI when the buffer is emptied in downlink. For an eNodeB serving one or more RNs, packets transmitted between the E-UTRAN and RNs are excluded, i.e., only packets transmitted between the eNodeB (or RN) and UEs are counted. The measurement is also applicable to RN. b) DER(n=1). c) This measurement is obtained according to the definition in 3GPP TS 36.314[ Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements ] [11] clause 4.1.6 as sum of ThpTimeDl. Separate counters are maintained for each QCI. d) Each measurement is a real value representing active transmission time of a data burst in ms. The number of measurements is equal to the number of QCIs. e) The measurement name has the form DRB.IPTimeDl.QCI where QCI identifies the E-RAB level quality of service class. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic. h) EPS. i) This measurement is to support the Integrity KPI "E-UTRAN IP Throughput" defined in [13]. | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.4.6.5 |
4,614 | 5.8.2.20 SMF Pause of Charging | The SMF Pause of Charging functionality is supported with the purpose that the charging and usage monitoring data in the core network more accurately reflects the downlink traffic actually sent to the (R)AN. When the amount of downlink data incoming at the UPF for a PDU Session that is in deactivated state goes above a pre-configured threshold, the pause of charging functionality ensures that data that dropped in the core network is not included in charging and usage monitoring records. The procedures for SMF Pause of Charging are described in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.8.2.20 |
4,615 | 5.33.3.2 Per QoS Flow per UE QoS Measurement | SMF may activate the end to end UL/DL packet delay measurement between UE and PSA UPF for a QoS Flow during the PDU Session Establishment or Modification procedure. The SMF sends a QoS Monitoring request to the PSA UPF via N4 and NG-RAN via N2 signalling to request the QoS monitoring between PSA UPF and NG-RAN. The QoS Monitoring request may contain monitoring parameters determined by SMF based on the authorized QoS Monitoring policy received from the PCF and/or local configuration. The NG-RAN initiates the RAN part of UL/DL packet delay measurement based on the QoS Monitoring request from SMF. NG-RAN reports the RAN part of UL/DL packet delay result to the PSA UPF in the UL data packet or dummy UL packet. If the NG-RAN and PSA UPF are time synchronised, the one way packet delay monitoring between NG-RAN and PSA UPF is supported. If the NG-RAN and PSA UPF are not time synchronised, it is assumed that the UL packet delay and the DL packet delay between NG-RAN and PSA UPF are the same. For both time synchronised and not time synchronised between NG-RAN and PSA UPF, the PSA UPF creates and sends the monitoring packets to the RAN in a measurement frequency, decided by the PSA UPF, taking the Reporting frequency for QoS Monitoring received from the SMF into account: - The PSA UPF encapsulates in the GTP-U header with QFI, QoS Monitoring Packet (QMP) indicator (which indicates the packet is used for UL/DL packet delay measurement) and the local time T1 when the PSA UPF sends out the DL monitoring packets. - The NG-RAN records the local time T1 received in the GTP-U header and the local time T2 at the reception of the DL monitoring packets. - When receiving an UL packet from UE for that QFI or when the NG-RAN sends a dummy UL packet as monitoring response (in case there is no UL service packet for UL packet delay monitoring), the NG-RAN encapsulates QMP indicator, the RAN part of UL/DL packet delay result, the time T1 received in the GTP-U header, the local time T2 at the reception of the DL monitoring packet and the local time T3 when NG-RAN sends out this monitoring response packet to the UPF via N3 interface, in the GTP-U header of the monitoring response packet. NOTE 1: When the NG-RAN sends the dummy UL packet as monitoring response to PSA UPF depends on NG-RAN's implementation. - The PSA UPF records the local time T4 when receiving the monitoring response packets and calculates the round trip (if not time synchronized) or UL/DL packet delay (if time synchronized) between NG-RAN and anchor PSA UPF based on the time information contained in the GTP-U header of the received monitoring response packet. If the NG-RAN and PSA UPF are not time synchronised, the PSA UPF calculates the UL/DL packet delay between the NG-RAN and the PSA UPF based on the (T2-T1+T4-T3)/2. If the NG-RAN and PSA UPF are time synchronised, the PSA UPF calculates the UL packet delay and DL packet delay between the NG-RAN and the PSA UPF based on (T4-T3) and (T2-T1), respectively. The PSA UPF calculates the UL/DL packet delay between UE and PSA UPF based on the received RAN part of UL/DL packet delay result and the calculated UL/DL packet delay between RAN and PSA UPF. NOTE 2: If the NG-RAN and PSA UPF are not time synchronised, it can cause inaccurate result of UL/DL packet delay. - The PSA UPF reports the QoS Monitoring results as described in clause 5.8.2.18. If the redundant transmission on N3/N9 interfaces is activated, the UPF and NG-RAN performs QoS monitoring for both UP paths. The UPF reports the packet delays of the two UP paths independently to the SMF. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.33.3.2 |
4,616 | 8.3.1.1D Enhanced Performance Requirement Type B – Single-layer Spatial Multiplexing with CRS interference model | The requirements are specified in Table 8.3.1.1D-2, with the addition of the parameters in Table 8.3.1.1D-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify closed loop rank one performance on one of the antenna ports 7 or 8 without a simultaneous transmission on the other antenna port in the serving cell when the PDSCH transmission in the serving cell is interfered by the CRS of the interfering cell, applying the CRS interference model defined in clause B.6.5. In 8.3.1.1D-1, Cell 1 is the serving cell, and Cell 2, 3 are interfering cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. Table 8.3.1.1D-1: Test Parameters for Testing CDM-multiplexed DM RS (Single-layer) with CRS interference model Table 8.3.1.1D-2: Minimum Performance for Enhanced Performance Requirement Type B, CDM-multiplexed DM RS with CRS interference model | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.3.1.1D |
4,617 | 13.2.4.8 Procedure | The following clause illustrates the message flow between the two SEPPs with modifications from cIPX and pIPX. Figure 13.2.4.8-1 Message flow between two SEPPs 1. The cSEPP receives an HTTP request message from a network function. If the message contains a telescopic FQDN, the cSEPP removes its domain name from this FQDN to obtain the original FQDN as described in clause 13.1. 2. The cSEPP shall reformate the HTTP Request message as follows: a. The cSEPP shall generate blocks (JSON objects) for integrity protected data and encrypted data, and protecting them: The cSEPP shall encapsulate the HTTP request into a clearTextEncapsulatedMessage block containing the following child JSON objects: - Pseudo_Headers - HTTP_Headers with one element per header of the original request. - Payload that contains the message body of the original request. For each attribute that require end-to-end encryption between the two SEPPs, the attribute value is copied into a dataToIntegrityProtectAndCipher JSON object and the attribute's value in the clearTextEncapsulatedMessage is replaced by the index of attribute value in the dataToIntegrityProtectAndCipher block. The cSEPP shall create a metadata block that contains the N32-f context ID, message ID generated by the cSEPP for this request/response transaction and next hop identity. The cSEPP shall protect the dataToIntegrityProtect block and the dataToIntegrityProtectAndCipher block as per clause 13.2.4.4. This results in a single JWE object representing the protected HTTP Request message. b. The cSEPP shall generate payload for the SEPP to SEPP HTTP message: The JWE object becomes the payload of the new HTTP message generated by cSEPP. 3. The cSEPP shall use HTTP POST to send the HTTP message to the first Roaming Intermediary. 4. The first Roaming Intermediary (e.g. visited network's IPX provider) shall create a new modifiedDataToIntegrityProtect JSON object with three elements: a. The Operations JSON patch document contains modifications performed by the first Roaming Intermediary as per RFC 6902 [64]. b. The first Roaming Intermediary shall include its own identity in the Identity field of the modifiedDataToIntegrityProtect. c. The first Roaming Intermediary shall copy the "tag" element, present in the JWE object generated by the cSEPP, into the modifiedDataToIntegrityProtect object. This acts as a replay protection for updates made by the first Roaming Intermediary. The Roaming Intermediary shall execute JWS on the modifiedDataToIntegrityProtect JSON object and append the resulting JWS object to the message. 5. The first Roaming Intermediary shall send the modified HTTP message request to the second Roaming Intermediary (e.g. home network's IPX) as in step 3. 6. The second Roaming Intermediary shall perform further modifications as in step 4 if required. The second Roaming Intermediary shall further execute JWS on the modifiedDataToIntegrityProtect JSON object and shall append the resulting JWS object to the message. 7. The second Roaming Intermediary shall send the modified HTTP message to the pSEPP as in step 3. NOTE 1: The behaviour of the Roaming Intermediaries is not normative, but the pSEPP assumes that behaviour for processing the resulting request. 8. The pSEPP receives the message and shall perform the following actions: - The pSEPP extracts the serialized values from the components of the JWE object. - The pSEPP invokes the JWE AEAD algorithm to check the integrity of the message and decrypt the dataToIntegrityProtectAndCipher block. This results in entries in the encrypted block becoming visible in cleartext. - The pSEPP updates the clearTextEncapsulationMessage block in the message by replacing the references to the dataToIntegrityProtectAndCipher block with the referenced decrypted values from the dataToIntegrityProtectAndCipher block. - The pSEPP then verifies IPX provider updates of the attributes in the modificationsArray. It checks whether the modifications performed by the Roaming Intermediaries were permitted by policy. The pSEPP further verifies that the PLMN-ID contained in the message is equal to the "Remote PLMN-ID" in the related N32-f context. - The pSEPP updates the modified values of the attributes in the clearTextEncapsulationMessage in order. The pSEPP shall re-assemble the full HTTP Request from the contents of the clearTextEncapsulationMessage. 9. The pSEPP shall send the HTTP request resulting from step 8 to the home network's NF. 10.-18. These steps are analogous to steps 1.-9. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.2.4.8 |
4,618 | 16.5.2 IMS Emergency call | An IMS Emergency call support indication is provided to inform the UE that emergency bearer services are supported. In normal service state the UE is informed if the PLMN supports emergency services through an Emergency Service Support indicator in the Attach and TAU procedures (see TS 23.501[ System architecture for the 5G System (5GS) ] [3]). In limited service state and for emergency services other than eCall over IMS, a UE is informed about if a cell supports emergency services over NG-RAN from a broadcast indication (ims-EmergencySupport). The broadcast indicator is set to "support" if any AMF in a non-shared environment or at least one of the PLMN's in a shared environment supports IMS emergency bearer services. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.5.2 |
4,619 | 9.10 Security mechanisms for the interface between W-5GAN and 5GC | The W-AGF function in Wireline 5G Access network (W-5GAN) terminates the following interfaces: - N2 interface between the W-5GAN and the AMF. -N3 interface between the W-5GAN and the UPF. The security of the N2 interface between the W-5GAN and the AMF is as defined in clause 9.2 of the present document. The security of the N3 interface between the W-5GAN and the UPF is as defined in clause 9.3 of the present document. On the W-AGF side a SEG may be used to terminate the IPsec tunnels. NOTE: Clauses 9.2 and 9.3 require that the N2 and N3 interfaces are integrity, confidentiality, and replay protected. The same protection can be achieved by placing the AGF in the same trust domain as the AMF and the SMF. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 9.10 |
4,620 | 4.1.1.5 Access class control | The network can restrict the access for certain groups of mobile stations. These groups are also known as access classes. The restriction can apply for access to both domains (common access class control or EAB, depending on EAB configuration) or to one domain only (domain specific access control) (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]). Additionally, the network can alleviate the access restriction in both domains or domain specifically, and allow restricted mobile stations to respond to paging messages or to perform generic location updating, or GPRS attach or routing area updating procedure. A network operator can also restrict some MSs to access the network for location registration, although via common access class control or domain specific access class control the MSs are permitted to access the network for other purposes. Therefore, for each access to the network the mobile station shall determine from the information received via the system information broadcast whether access is allowed or not: - For paging response the mobile station shall evaluate the control information for common access control (as specified in 3GPP TS 44.018[ None ] [84], 3GPP TS 44.060[ None ] [76], and 3GPP TS 25.331[ None ] [23c]), the control information for EAB (as specified in 3GPP TS 44.018[ None ] [84], and 3GPP TS 25.331[ None ] [23c]), domain specific access control (as specified in 3GPP TS 44.018[ None ] [84] and 3GPP TS 25.331[ None ] [23c]), and the specific control information for paging response (as specified in 3GPP TS 25.331[ None ] [23c]; see "Paging Permission with Access Control"). - For generic location updating, GPRS attach and routing area updating procedures the mobile station shall evaluate the control information for: - common access control (as specified in 3GPP TS 44.018[ None ] [84], 3GPP TS 44.060[ None ] [76], and 3GPP TS 25.331[ None ] [23c]); - domain specific access control (as specified in 3GPP TS 44.018[ None ] [84] and 3GPP TS 25.331[ None ] [23c]); - specific control information for location registration (as specified in 3GPP TS 25.331[ None ] [23c]; see "Paging Permission with Access Control"); and - EAB as specified for A/Gb mode in 3GPP TS 44.018[ None ] [84], and for Iu mode in 3GPP TS 25.331[ None ] [23c]. The same control information shall also be taken into account, when the present document requires the mobile station to initiate a generic location updating, or GPRS attach or routing area updating procedure when it detects that a domain changes from barred to unbarred (see e.g. subclauses 4.1.1.2.1 and 4.1.1.2.2). - For GPRS attach and routing area updating procedures in Iu mode, the mobile station shall evaluate the control information for: - ACDC if the mobile station supports ACDC (as specified in 3GPP TS 25.331[ None ] [23c]). The same control information shall also be taken into account, when the present document requires the mobile station to initiate a GPRS attach or routing area updating procedure in Iu mode when it detects that PS domain changes from barred to unbarred (see e.g. subclauses 4.1.1.2.1 and 4.1.1.2.2). - For all other purposes the mobile station shall evaluate the control information for common access control as specified in 3GPP TS 44.018[ None ] [84], 3GPP TS 44.060[ None ] [76], and 3GPP TS 25.331[ None ] [23c], the control information for EAB (as specified in 3GPP TS 44.018[ None ] [84], and 3GPP TS 25.331[ None ] [23c]), domain specific access control (as specified in 3GPP TS 44.018[ None ] [84] and 3GPP TS 25.331[ None ] [23c]) and in Iu mode for PS domain if the mobile station supports ACDC, the control information for ACDC (as specified in 3GPP TS 25.331[ None ] [23c]). | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.1.1.5 |
4,621 | A.34 Monitor of Secondary Node Addition for E-UTRA-NR Dual Connectivity | In the E-UTRA-NR Dual Connectivity scenario, the Secondary Node Addition procedure is initiated by the MN and is used to establish a UE context at the SN to provide radio resources from the SN to the UE. The success or failure of Secondary Node Addition directly impacts the quality level for delivering the service by the networks, and also the feeling of the end user. So the success or failure of Secondary Node Addition needs be monitored, and for the scenarios that the path update is needed during the Secondary Node Addition procedure, the path update related measurements are also needed. | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | A.34 |
4,622 | 5.7A.4 Secondary RAT Periodic Usage Data Reporting Procedure | Periodic reporting of the Secondary RAT usage data is an optional function. When eNodeB, as defined in bullet e) of clause 5.7A.2, is configured with a "time interval for Secondary RAT usage data reporting", the eNodeB shall send a RAN Usage Data Report message for periodic reporting purposes to the MME only when this timer expires for a UE for which Secondary RAT usage data reporting is ongoing. The timer runs from the last usage reporting for the UE. The MME also indicates to SGW if secondary RAT usage data reporting to the PGW is active. The procedures 5.7A.3-1 to 5.7A.3-2 in its entirety is executed to provide periodic reporting of Secondary RAT usage data to the Serving GW and to the PDN GW when PGW secondary RAT usage data reporting is active. At use for periodic usage data reporting, the procedure 5.7A.3-1 uses signalling from eNodeB which does not include a handover flag. | 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.7A.4 |
4,623 | 4.4.4.7 Location updating not accepted by the network | If the location updating cannot be accepted, the network sends a LOCATION UPDATING REJECT message to the mobile station. The mobile station receiving a LOCATION UPDATING REJECT message containing a reject cause other than MM cause value #25 or the message is integrity protected, shall stop the timer T3210, store the reject cause, start the timer T3240, enter state LOCATION UPDATING REJECTED, await the release of the RR connection triggered by the network, and for all causes except #12, #15, #22 and #25 deletes the list of "equivalent PLMNs". If the LOCATION UPDATING REJECT message containing the MM cause value #25 was received without integrity protection, then the MS shall discard the message. If the location updating is rejected due to general NAS level mobility management congestion control, the network shall set the MM cause value to #22 "congestion" and assign a back-off timer T3246 (see 3GPP TS 23.012[ Location management procedures ] [140]). Upon the release of the RR connection, the mobile station shall take the following actions depending on the stored reject cause: # 2: (IMSI unknown in HLR); # 3: (Illegal MS); or # 6: (Illegal ME). The mobile station shall set the update status to ROAMING NOT ALLOWED (and store it in the SIM/USIM according to subclause 4.1.2.2), and delete any TMSI, stored LAI and ciphering key sequence number and shall consider the SIM/USIM as invalid for non-GPRS services until switch-off or the SIM/USIM is removed or the timer T3245 expires as described in subclause 4.1.1.6. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. # 11: (PLMN not allowed); The mobile station shall delete any LAI, TMSI and ciphering key sequence number stored in the SIM/USIM, reset the location update attempt counter, and set the update status to ROAMING NOT ALLOWED (and store it in the SIM/USIM according to subclause 4.1.2.2). The mobile station shall store the PLMN identity in the "forbidden PLMN list" and if the MS is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112]) then the MS shall start timer T3245 and proceed as described in subclause 4.1.1.6. If the message has been successfully integrity checked by the lower layers and the MS maintains a PLMN-specific attempt counter for that PLMN, then the MS shall set this counter to the MS implementation-specific maximum value. The MS shall perform a PLMN selection when back to the MM IDLE state according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. An MS in GAN mode shall request a PLMN list in GAN (see 3GPP TS 44.318[ None ] [76b]) prior to performing a PLMN selection from this list according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. # 12: (Location Area not allowed); The mobile station shall delete any LAI, TMSI and ciphering key sequence number stored in the SIM/USIM, reset the location update attempt counter, and set the update status to ROAMING NOT ALLOWED (and store it in the SIM/USIM according to subclause 4.1.2.2). The mobile station shall store the LAI in the list of "forbidden location areas for regional provision of service". The MS shall perform a cell selection when back to the MM IDLE state according to 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98]. NOTE 1: The cell selection procedure is not applicable for an MS in GAN mode. # 13: (Roaming not allowed in this location area). The mobile station shall reset the location update attempt counter, and set the update status to ROAMING NOT ALLOWED (and store it in the SIM/USIM according to subclause 4.1.2.2). The mobile station shall store the LAI in the list of "forbidden location areas for roaming". The mobile station shall perform a PLMN selection instead of a cell selection when back to the MM IDLE state according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. An MS in GAN mode shall request a PLMN list in GAN (see 3GPP TS 44.318[ None ] [76b]) prior to performing a PLMN selection from this list according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. # 15: (No Suitable Cells In Location Area). The mobile station shall reset the location update attempt counter, set the update status to ROAMING NOT ALLOWED (and store it in the SIM/USIM according to subclause 4.1.2.2). The mobile station shall store the LAI in the list of "forbidden location areas for roaming". The mobile station shall search for a suitable cell in another location area or a tracking area according to 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [121]. NOTE 2: The cell selection procedure is not applicable for an MS in GAN mode. # 22: (Congestion). If the T3246 value IE is present in the LOCATION UPDATING REJECT message and the value indicates that this timer is neither zero nor deactivated, the mobile station shall proceed as described below, otherwise it shall be considered as an abnormal case and the behaviour of the MS for this case is specified in subclause 4.4.4.9. The mobile station shall abort the location updating procedure, reset the location update attempt counter, set the MM update status to U2 NOT UPDATED and change to state MM IDLE sub-state ATTEMPTING TO UPDATE. The MS shall stop timer T3246 if it is running. If the LOCATION UPDATING REJECT message is integrity protected, the mobile station shall start timer T3246 with the value provided in the T3246 value IE. If the LOCATION UPDATING REJECT message is not integrity protected, the mobile station shall start timer T3246 with a random value from the default range specified in table 11.1. The mobile station stays in the current serving cell and applies the normal cell reselection process. The MM connection establishment is started, if still necessary, when timer T3246 expires or is stopped. # 25: (Not authorized for this CSG ). Cause #25 is only applicable in UTRAN Iu mode and when received from a CSG cell. Other cases are considered as abnormal cases and the specification of the mobile station behaviour is given in subclause 4.4.4.9. The MS shall reset the location update attempt counter, and set the update status to ROAMING NOT ALLOWED (and store it in the SIM/USIM according to subclause 4.1.2.2). If the CSG ID and associated PLMN identity of the cell where the MS has sent the LOCATION UPDATING REQUEST message are contained in the Allowed CSG list stored in the MS, the MS shall remove the entry corresponding to this CSG ID and associated PLMN identity from the Allowed CSG list. If the CSG ID and associated PLMN identity of the cell where the MS has sent the LOCATION UPDATING REQUEST message are contained in the Operator CSG list, the MS shall proceed as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14] subclause 3.1A. The MS shall search for a suitable cell according to 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98]. Other values are considered as abnormal cases and the specification of the mobile station behaviour in those cases is given in subclause 4.4.4.9. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.4.4.7 |
4,624 | 6.2.10 Handling of 3GPP PS data off | In case of PLMN, a UE, which supports 3GPP PS data off (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]), 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) ] [17] or in the EF3GPPPSDATAOFF USIM file as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]: a) a list of 3GPP PS data off exempt services to be used in the HPLMN or EHPLMN; and b) 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 is configured at the UE, this list shall be also used in the VPLMN. In case of SNPN, a UE, which supports 3GPP PS data off (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]), can be configured with: a) 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) ] [17] for each subscribed SNPN whose entry exists in the "list of subscriber data": 1) a list of 3GPP PS data off exempt services to be used in the subscribed SNPN; and 2) a list of 3GPP PS data off exempt services to be used in the non-subscribed SNPN; and b) one list of 3GPP PS data off exempt services as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [17] for PLMN subscription: 1) a list of 3GPP PS data off exempt services to be used in the non-subscribed SNPN. If only the list of 3GPP PS data off exempt services to be used in the subscribed SNPN is configured for the selected entry of "list of subscriber data", this list shall be also used in the non-subscribed SNPN. If the UE supports 3GPP PS data off, the UE shall provide the 3GPP PS data off UE status in the Extended protocol configuration options IE during UE-requested PDU session establishment procedure except for the transfer of a PDU session from non-3GPP access to 3GPP access and except for the establishment of user plane resources on the other access for the MA PDU session(see subclause 6.4.1), and during UE-requested PDU session modification procedure (see subclause 6.4.2), regardless of associated access type of the PDU session. If the UE requests a PDU session establishment procedure in order to transfer a PDU session from non-3GPP access to 3GPP access, or in order to establish user plane resources on the other access for the MA PDU session over 3GPP access or non-3GPP access, and: a) if the 3GPP PS data off UE status has changed since the last providing to the network, the UE shall provide the 3GPP PS data off UE status in the Extended protocol configuration options IE; or b) if the 3GPP PS data off UE status has not changed since the last providing to the network, the UE need not provide the 3GPP PS data off UE status. The network shall support of 3GPP PS data off. The UE shall indicate change of the 3GPP PS data off UE status for the PDU session by using the UE-requested PDU session modification procedure as specified in subclause 6.4.2. When the 3GPP PS data off UE status is "activated": a) the UE does not send uplink IP packets via 3GPP access except: 1) for those services indicated in the list of 3GPP PS data off exempt services to be used in the HPLMN or EHPLMN as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [17] when the UE is in its HPLMN or EHPLMN; 2) for those services indicated in the list of 3GPP PS data off exempt services to be used in the subscribed SNPN, configured for the selected entry of "list of subscriber data", as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [17] when the UE is in the subscribed SNPN; 3) for those services indicated in the list of 3GPP PS data off exempt services to be used in the HPLMN or EHPLMN when the UE is in the VPLMN, if only the list of 3GPP PS data off exempt services to be used in the HPLMN or EHPLMN is configured to the UE as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [17]; 4) for those services indicated in the list of 3GPP PS data off exempt services to be used in the subscribed SNPN, configured for the selected entry of "list of subscriber data", when the UE is in a non-subscribed SNPN and only the list of 3GPP PS data off exempt services to be used in the subscribed SNPN is configured for the selected entry of "list of subscriber data" as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [17]; 5) for those services indicated in the list of 3GPP PS data off exempt services to be used in the VPLMN when the UE is in the VPLMN, if the list of 3GPP PS data off exempt services to be used in the VPLMN is configured to the UE as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [17]; 6) for those services indicated in the list of 3GPP PS data off exempt services to be used in the non-subscribed SNPN, configured for the selected entry of "list of subscriber data", when the UE is in a non-subscribed SNPN and the list of 3GPP PS data off exempt services to be used in the non-subscribed SNPN is configured for the selected entry of "list of subscriber data" as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [17]; 7) for those services indicated in the list of 3GPP PS data off exempt services to be used in the non-subscribed SNPN, configured for the selected PLMN subscription, when the UE is in the non-subscribed SNPN and the list of 3GPP PS data off exempt services to be used in the non-subscribed SNPN is configured for the selected PLMN subscription as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [17]; 8) 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 ] [22]; 9) 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 ] [14]; and 10) any uplink traffic due to procedures specified in 3GPP TS 24.623[ Extensible Markup Language (XML) Configuration Access Protocol (XCAP) over the Ut interface for Manipulating Supplementary Services ] [20]; b) the UE does not send uplink Ethernet user data packets via 3GPP access; and c) the UE does not send uplink Unstructured user data packets via 3GPP access. Otherwise the UE sends uplink user data packets without restriction. NOTE: If the UE 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 ] [14] in U.3.1.5. 3GPP PS data off does not restrict sending of uplink user data packets via non-3GPP access of a single access PDU session or an MA PDU session. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.2.10 |
4,625 | D.3.7.2 Preparation phase | Figure D.3.7.2-1: E-UTRAN to GERAN A/Gb Inter RAT HO, preparation phase 1. The source eNodeB decides to initiate an Inter RAT Handover to the target GERAN A/Gb mode (2G) system. At this point both uplink and downlink user data is transmitted via the following: Bearer(s) between UE and Source eNodeB, GTP tunnel(s) between Source eNodeB, Serving GW and PDN GW. If the UE has an ongoing emergency bearer service the source eNodeB shall not initiate PS handover to GERAN. NOTE 1: The process leading to the handover decision is outside of the scope of this specification 2. The source eNodeB sends a Handover Required (Cause, Target System Identifier, Source BSS to Target BSS Transparent Container) message to the Source MME to request the CN to establish resources in the Target BSS, Target SGSN and the Serving GW. The bearers that will be subject to data forwarding (if any) are identified by the new SGSN in a later step (see step 8 below). The 'Target System Identifier' IE contains the identity of the target global cell Id. NOTE 2: This step is unmodified compared to clause 5.5.2.3.2. The target SGSN acts as the new SGSN. 3 The old SGSN determines from the Target Cell Identifier that the type of handover is inter-RAT/mode handover. In the case of Inter-RAT/ mode Inter-SGSN PS handover, the old SGSN initiates the PS Handover resource allocation procedure by sending a Forward Relocation Request (IMSI, Tunnel Endpoint Identifier Control Plane, RANAP Cause, Target Cell Identifier, MM Context, PDP Contexts, Packet Flow ID, SNDCP XID parameters, LLC XID parameters, PDP Context Prioritisation, Source BSS To Target BSS Transparent Container [RN part] in the BSS Container, Source RNC Id, SGSN Address for control plane) message to the new SGSN. If the old SGSN supports PS handover procedures then it has to allocate a valid PFI according to clause 4.4.1 during the PDP Context activation procedure. Each PDP context contains the GGSN Address for User Plane and the Uplink TEID for Data (to this GGSN Address and Uplink TEID for Data the old SGSN and the new SGSN send uplink packets). The MM context includes information on the EPS Bearer context(s). If none of the UE's EPS Bearers can be supported by the selected target SGSN, the old SGSN rejects the handover attempt by sending a Handover Preparation Failure (Cause) message to the Source eNodeB. NOTE 3: If the handover is successful, the old SGSN will signal to the SGW and/or SCEF to release any non-included EPS Bearers after step 8 of the Execution procedure. The non-included bearers are locally released by the MS following the PDP Context Status synchronisation that occurs during the Routing Area Update at step 13 of the Execution procedure. The MM context contains security related information, e.g. supported ciphering algorithms as described in TS 29.060[ General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface ] [14]. The relation between GSM and UMTS security parameters is defined in TS 33.102[ 3G security; Security architecture ] [40], The new SGSN selects the ciphering algorithm to use. This algorithm will be sent transparently from the new SGSN to the MS. The IOV-UI parameter generated in the new SGSN and used, as input to the ciphering procedure will also be transferred transparently from the new SGSN to the MS. When the new SGSN receives the Forward Relocation Request message the required PDP, MM, SNDCP and LLC contexts are established and a new P-TMSI is allocated for the MS. When this message is received by the new SGSN it begins the process of establishing PFCs for all PDP contexts. When the new SGSN receives the Forward Relocation Request message it extracts from the PDP Contexts the NSAPIs and SAPIs and PFIs to be used in the new SGSN. If for a given PDP Context the new SGSN does not receive a PFI from the old SGSN, it shall not request the target BSS to allocate TBF resources corresponding to that PDP Context. If none of the PDP Contexts forwarded from the old SGSN has a valid PFI allocated the new SGSN shall consider this as a failure case and the request for PS handover shall be rejected. In the case when an SAPI and PFI was available at the old SGSN but the new SGSN does not support the same SAPI and PFI for a certain NSAPI as the old SGSN, the new SGSN shall continue the PS handover procedure only for those NSAPIs for which it can support the same PFI and SAPI as the old SGSN. All PDP contexts for which no resources are allocated by the new SGSN or for which it cannot support the same SAPI and PFI (i.e. the corresponding NSAPIs are not addressed in the response message of the target SGSN), are maintained and the related SAPIs and PFIs are kept. These PDP contexts may be modified or deactivated by the new SGSN via explicit SM procedures upon RAU procedure. The old SGSN shall indicate the current XID parameter settings if available (i.e. those negotiated at the old SGSN when the MS was in A/Gb mode or received during a previous inter-SGSN PS handover) to the new SGSN. If the new SGSN can accept all XID parameters as indicated by the old SGSN, the new SGSN shall create a NAS container for PS HO indicating 'Reset to the old XID parameters'. Otherwise, if the new SGSN cannot accept all XID parameters indicated by the old SGSN or if no XID parameters were indicated by the old SGSN, the new SGSN shall create a NAS container for PS HO indicating Reset (i.e. reset to default parameters). NOTE 4: This step is unmodified compared to pre-Rel-8. The Source eNodeB acts as the source RNC, Source MME acts as the old SGSN, and the PDN GW acts as the GGSN. 4. The new SGSN sends a PS Handover Request (Local TLLI, IMSI, Cause, Target Cell Identifier, Source BSS to Target BSS Transparent Container (RN part), PFCs To Be Set Up List, NAS container for PS HO) message to the target BSS. The new SGSN shall not request resources for PFCs associated with PDP contexts with maximum bit rate for uplink and downlink of 0 kbit/s or for which the Activity Status Indicator within the PDP Context indicates that no active RAB exists on the source side. 5. Based upon the ABQP for each PFC the target BSS makes a decision about which PFCs to assign radio resources. The algorithm by which the BSS decides which PFCs that need resources is implementation specific. Due to resource limitations not all downloaded PFCs will necessarily receive resource allocation. The target BSS allocates TBFs for each PFC that it can accommodate. 6. The target BSS shall prepare the Target BSS to Source BSS Transparent Container which contains a PS Handover Command including the CN part (NAS container for PS HO) and the RN part (PS Handover Radio Resources). 7. Target BSS shall send the PS Handover Request Acknowledge message (Local TLLI, List of Set Up PFCs, Target BSS to Source BSS Transparent Container) message to the new SGSN. Upon sending the PS Handover Request Acknowledge message the target BSS shall be prepared to receive downlink LLC PDUs from the new SGSN for the accepted PFCs. Any PDP contexts for which a PFC was not established are maintained in the new SGSN and the related SAPIs and PFIs are kept. These PDP contexts may be modified or deactivated by the new SGSN via explicit SM procedures upon the completion of the routing area update (RAU) procedure. 8. The new SGSN passes the assigned list of TEIDs for each PDP context for which a PFC was assigned in the RAB setup information IE in the Forward Relocation Response (Cause, List of Set Up PFCs, Target BSS to Source BSS Transparent Container) in the BSS Container, Tunnel Endpoint Identifier Control Plane, SGSN Address for User Traffic, Tunnel Endpoint Identifier Data II) message to the old SGSN. The NSAPIs of the active PDP Contexts received in the Forward Relocation Request message for which the PS handover continues, i.e. for which resources are allocated for the PFCs in the target BSS, are indicated in this message. The Tunnel Endpoint Identifier Data II, one information for each PDP context, is the tunnel endpoint of the new SGSN and is used for data forwarding from the Source eNodeB, via the new SGSN, to the target BSS. The new SGSN activates the allocated LLC/SNDCP engines as specified in TS 44.064[ Mobile Station - Serving GPRS Support Node (MS-SGSN); Logical Link Control (LLC) Layer Specification ] [23] for an SGSN originated Reset or 'Reset to the old XID parameters'. When the old SGSN receives the Forward Relocation Response message and it decides to proceed with the handover, the preparation phase is finished and the execution phase will follow. 9. If 'Indirect Forwarding' applies, the source MME sends a Create Indirect Data Forwarding Tunnel Request message (Cause, SGSN Address(es) and TEID(s) for Data Forwarding) to the Serving GW. Cause indicates that the bearer(s) are subject to data forwarding. Indirect forwarding may be performed via a Serving GW which is different from the Serving GW used as the anchor point for the UE. 9a. The Serving GW returns a Create Indirect Data Forwarding Tunnel Response (Cause, Serving GW Address(es) and TEID(s) for Data Forwarding) message to the target MME. If the Serving GW doesn't support data forwarding, an appropriate cause value shall be returned and the Serving GW Address(es) and TEID(s) will not be included in the message. NOTE 5: This step is mostly unmodified compared to pre-Rel-8. The Source MME acts as the old SGSN, and the PDN GW acts as the GGSN. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | D.3.7.2 |
4,626 | – UEAssistanceInformation | The UEAssistanceInformation message is used for the indication of UE assistance information to the network. Signalling radio bearer: SRB1, SRB3 RLC-SAP: AM Logical channel: DCCH Direction: UE to Network UEAssistanceInformation message -- ASN1START -- TAG-UEASSISTANCEINFORMATION-START UEAssistanceInformation ::= SEQUENCE { criticalExtensions CHOICE { ueAssistanceInformation UEAssistanceInformation-IEs, criticalExtensionsFuture SEQUENCE {} } } UEAssistanceInformation-IEs ::= SEQUENCE { delayBudgetReport DelayBudgetReport OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension UEAssistanceInformation-v1540-IEs OPTIONAL } DelayBudgetReport::= CHOICE { type1 ENUMERATED { msMinus1280, msMinus640, msMinus320, msMinus160,msMinus80, msMinus60, msMinus40, msMinus20, ms0, ms20,ms40, ms60, ms80, ms160, ms320, ms640, ms1280}, ... } UEAssistanceInformation-v1540-IEs ::= SEQUENCE { overheatingAssistance OverheatingAssistance OPTIONAL, nonCriticalExtension UEAssistanceInformation-v1610-IEs OPTIONAL } OverheatingAssistance ::= SEQUENCE { reducedMaxCCs ReducedMaxCCs-r16 OPTIONAL, reducedMaxBW-FR1 ReducedMaxBW-FRx-r16 OPTIONAL, reducedMaxBW-FR2 ReducedMaxBW-FRx-r16 OPTIONAL, reducedMaxMIMO-LayersFR1 SEQUENCE { reducedMIMO-LayersFR1-DL MIMO-LayersDL, reducedMIMO-LayersFR1-UL MIMO-LayersUL } OPTIONAL, reducedMaxMIMO-LayersFR2 SEQUENCE { reducedMIMO-LayersFR2-DL MIMO-LayersDL, reducedMIMO-LayersFR2-UL MIMO-LayersUL } OPTIONAL } OverheatingAssistance-r17 ::= SEQUENCE { reducedMaxBW-FR2-2-r17 SEQUENCE { reducedBW-FR2-2-DL-r17 ReducedAggregatedBandwidth-r17, reducedBW-FR2-2-UL-r17 ReducedAggregatedBandwidth-r17 } OPTIONAL, reducedMaxMIMO-LayersFR2-2 SEQUENCE { reducedMIMO-LayersFR2-2-DL MIMO-LayersDL, reducedMIMO-LayersFR2-2-UL MIMO-LayersUL } OPTIONAL } ReducedAggregatedBandwidth ::= ENUMERATED {mhz0, mhz10, mhz20, mhz30, mhz40, mhz50, mhz60, mhz80, mhz100, mhz200, mhz300, mhz400} ReducedAggregatedBandwidth-r17 ::= ENUMERATED {mhz0, mhz100, mhz200, mhz400, mhz800, mhz1200, mhz1600, mhz2000} UEAssistanceInformation-v1610-IEs ::= SEQUENCE { idc-Assistance-r16 IDC-Assistance-r16 OPTIONAL, drx-Preference-r16 DRX-Preference-r16 OPTIONAL, maxBW-Preference-r16 MaxBW-Preference-r16 OPTIONAL, maxCC-Preference-r16 MaxCC-Preference-r16 OPTIONAL, maxMIMO-LayerPreference-r16 MaxMIMO-LayerPreference-r16 OPTIONAL, minSchedulingOffsetPreference-r16 MinSchedulingOffsetPreference-r16 OPTIONAL, releasePreference-r16 ReleasePreference-r16 OPTIONAL, sl-UE-AssistanceInformationNR-r16 SL-UE-AssistanceInformationNR-r16 OPTIONAL, referenceTimeInfoPreference-r16 BOOLEAN OPTIONAL, nonCriticalExtension UEAssistanceInformation-v1700-IEs OPTIONAL } UEAssistanceInformation-v1700-IEs ::= SEQUENCE { ul-GapFR2-Preference-r17 UL-GapFR2-Preference-r17 OPTIONAL, musim-Assistance-r17 MUSIM-Assistance-r17 OPTIONAL, overheatingAssistance-r17 OverheatingAssistance-r17 OPTIONAL, maxBW-PreferenceFR2-2-r17 MaxBW-PreferenceFR2-2-r17 OPTIONAL, maxMIMO-LayerPreferenceFR2-2-r17 MaxMIMO-LayerPreferenceFR2-2-r17 OPTIONAL, minSchedulingOffsetPreferenceExt-r17 MinSchedulingOffsetPreferenceExt-r17 OPTIONAL, rlm-MeasRelaxationState-r17 BOOLEAN OPTIONAL, bfd-MeasRelaxationState-r17 BIT STRING (SIZE (1..maxNrofServingCells)) OPTIONAL, nonSDT-DataIndication-r17 SEQUENCE { resumeCause-r17 ResumeCause OPTIONAL } OPTIONAL, scg-DeactivationPreference-r17 ENUMERATED { scgDeactivationPreferred, noPreference } OPTIONAL, uplinkData-r17 ENUMERATED { true } OPTIONAL, rrm-MeasRelaxationFulfilment-r17 BOOLEAN OPTIONAL, propagationDelayDifference-r17 PropagationDelayDifference-r17 OPTIONAL, nonCriticalExtension UEAssistanceInformation-v1800-IEs OPTIONAL } UEAssistanceInformation-v1800-IEs ::= SEQUENCE { idc-FDM-Assistance-r18 IDC-FDM-Assistance-r18 OPTIONAL, idc-TDM-Assistance-r18 IDC-TDM-Assistance-r18 OPTIONAL, multiRx-PreferenceFR2-r18 ENUMERATED {single} OPTIONAL, musim-Assistance-v1800 MUSIM-Assistance-v1800 OPTIONAL, flightPathInfoAvailable-r18 ENUMERATED {true} OPTIONAL, ul-TrafficInfo-r18 UL-TrafficInfo-r18 OPTIONAL, n3c-RelayUE-InfoList-r18 N3C-RelayUE-InfoList-r18 OPTIONAL, sl-PRS-UE-AssistanceInformationNR-r18 SL-PRS-UE-AssistanceInformationNR-r18 OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } IDC-Assistance-r16 ::= SEQUENCE { affectedCarrierFreqList-r16 AffectedCarrierFreqList-r16 OPTIONAL, affectedCarrierFreqCombList-r16 AffectedCarrierFreqCombList-r16 OPTIONAL, ... } AffectedCarrierFreqList-r16 ::= SEQUENCE (SIZE (1.. maxFreqIDC-r16)) OF AffectedCarrierFreq-r16 AffectedCarrierFreq-r16 ::= SEQUENCE { carrierFreq-r16 ARFCN-ValueNR, interferenceDirection-r16 ENUMERATED {nr, other, both, spare} } AffectedCarrierFreqCombList-r16 ::= SEQUENCE (SIZE (1..maxCombIDC-r16)) OF AffectedCarrierFreqComb-r16 AffectedCarrierFreqComb-r16 ::= SEQUENCE { affectedCarrierFreqComb-r16 SEQUENCE (SIZE (2..maxNrofServingCells)) OF ARFCN-ValueNR OPTIONAL, victimSystemType-r16 VictimSystemType-r16 } VictimSystemType-r16 ::= SEQUENCE { gps-r16 ENUMERATED {true} OPTIONAL, glonass-r16 ENUMERATED {true} OPTIONAL, bds-r16 ENUMERATED {true} OPTIONAL, galileo-r16 ENUMERATED {true} OPTIONAL, navIC-r16 ENUMERATED {true} OPTIONAL, wlan-r16 ENUMERATED {true} OPTIONAL, bluetooth-r16 ENUMERATED {true} OPTIONAL, ..., [[ uwb-r18 ENUMERATED {true} OPTIONAL ]] } DRX-Preference-r16 ::= SEQUENCE { preferredDRX-InactivityTimer-r16 ENUMERATED { ms0, ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, ms80, ms100, ms200, ms300, ms500, ms750, ms1280, ms1920, ms2560, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1} OPTIONAL, preferredDRX-LongCycle-r16 ENUMERATED { ms10, ms20, ms32, ms40, ms60, ms64, ms70, ms80, ms128, ms160, ms256, ms320, ms512, ms640, ms1024, ms1280, ms2048, ms2560, ms5120, ms10240, spare12, spare11, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 } OPTIONAL, preferredDRX-ShortCycle-r16 ENUMERATED { ms2, ms3, ms4, ms5, ms6, ms7, ms8, ms10, ms14, ms16, ms20, ms30, ms32, ms35, ms40, ms64, ms80, ms128, ms160, ms256, ms320, ms512, ms640, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 } OPTIONAL, preferredDRX-ShortCycleTimer-r16 INTEGER (1..16) OPTIONAL } MaxBW-Preference-r16 ::= SEQUENCE { reducedMaxBW-FR1-r16 ReducedMaxBW-FRx-r16 OPTIONAL, reducedMaxBW-FR2-r16 ReducedMaxBW-FRx-r16 OPTIONAL } MaxBW-PreferenceFR2-2-r17 ::= SEQUENCE { reducedMaxBW-FR2-2-r17 SEQUENCE { reducedBW-FR2-2-DL-r17 ReducedAggregatedBandwidth-r17 OPTIONAL, reducedBW-FR2-2-UL-r17 ReducedAggregatedBandwidth-r17 OPTIONAL } OPTIONAL } MaxCC-Preference-r16 ::= SEQUENCE { reducedMaxCCs-r16 ReducedMaxCCs-r16 OPTIONAL } MaxMIMO-LayerPreference-r16 ::= SEQUENCE { reducedMaxMIMO-LayersFR1-r16 SEQUENCE { reducedMIMO-LayersFR1-DL-r16 INTEGER (1..8), reducedMIMO-LayersFR1-UL-r16 INTEGER (1..4) } OPTIONAL, reducedMaxMIMO-LayersFR2-r16 SEQUENCE { reducedMIMO-LayersFR2-DL-r16 INTEGER (1..8), reducedMIMO-LayersFR2-UL-r16 INTEGER (1..4) } OPTIONAL } MaxMIMO-LayerPreferenceFR2-2-r17 ::= SEQUENCE { reducedMaxMIMO-LayersFR2-2-r17 SEQUENCE { reducedMIMO-LayersFR2-2-DL-r17 INTEGER (1..8), reducedMIMO-LayersFR2-2-UL-r17 INTEGER (1..4) } OPTIONAL } MinSchedulingOffsetPreference-r16 ::= SEQUENCE { preferredK0-r16 SEQUENCE { preferredK0-SCS-15kHz-r16 ENUMERATED {sl1, sl2, sl4, sl6} OPTIONAL, preferredK0-SCS-30kHz-r16 ENUMERATED {sl1, sl2, sl4, sl6} OPTIONAL, preferredK0-SCS-60kHz-r16 ENUMERATED {sl2, sl4, sl8, sl12} OPTIONAL, preferredK0-SCS-120kHz-r16 ENUMERATED {sl2, sl4, sl8, sl12} OPTIONAL } OPTIONAL, preferredK2-r16 SEQUENCE { preferredK2-SCS-15kHz-r16 ENUMERATED {sl1, sl2, sl4, sl6} OPTIONAL, preferredK2-SCS-30kHz-r16 ENUMERATED {sl1, sl2, sl4, sl6} OPTIONAL, preferredK2-SCS-60kHz-r16 ENUMERATED {sl2, sl4, sl8, sl12} OPTIONAL, preferredK2-SCS-120kHz-r16 ENUMERATED {sl2, sl4, sl8, sl12} OPTIONAL } OPTIONAL } MinSchedulingOffsetPreferenceExt-r17 ::= SEQUENCE { preferredK0-r17 SEQUENCE { preferredK0-SCS-480kHz-r17 ENUMERATED {sl8, sl16, sl32, sl48} OPTIONAL, preferredK0-SCS-960kHz-r17 ENUMERATED {sl8, sl16, sl32, sl48} OPTIONAL } OPTIONAL, preferredK2-r17 SEQUENCE { preferredK2-SCS-480kHz-r17 ENUMERATED {sl8, sl16, sl32, sl48} OPTIONAL, preferredK2-SCS-960kHz-r17 ENUMERATED {sl8, sl16, sl32, sl48} OPTIONAL } OPTIONAL } MUSIM-Assistance-r17 ::= SEQUENCE { musim-PreferredRRC-State-r17 ENUMERATED {idle, inactive, outOfConnected} OPTIONAL, musim-GapPreferenceList-r17 MUSIM-GapPreferenceList-r17 OPTIONAL } MUSIM-GapPreferenceList-r17 ::= SEQUENCE (SIZE (1..4)) OF MUSIM-GapInfo-r17 MUSIM-Assistance-v1800 ::= SEQUENCE { musim-GapPriorityPreferenceList-r18 MUSIM-GapPriorityPreferenceList-r18 OPTIONAL, musim-GapKeepPreference-r18 ENUMERATED {true} OPTIONAL, musim-CapRestriction-r18 MUSIM-CapRestriction-r18 OPTIONAL, musim-NeedForGapsInfoNR-r18 NeedForGapsInfoNR-r16 OPTIONAL } MUSIM-GapPriorityPreferenceList-r18 ::= SEQUENCE (SIZE (1..3)) OF GapPriority-r17 MUSIM-CapRestriction-r18 ::= SEQUENCE { musim-Cell-SCG-ToRelease-r18 MUSIM-Cell-SCG-ToRelease-r18 OPTIONAL, musim-CellToAffectList-r18 MUSIM-CellToAffectList-r18 OPTIONAL, musim-AffectedBandsList-r18 MUSIM-AffectedBandsList-r18 OPTIONAL, musim-AvoidedBandsList-r18 MUSIM-AvoidedBandsList-r18 OPTIONAL, musim-MaxCC-r18 MUSIM-MaxCC-r18 OPTIONAL } MUSIM-Cell-SCG-ToRelease-r18 ::= SEQUENCE { musim-CellToRelease-r18 MUSIM-CellToRelease-r18 OPTIONAL, scg-ReleasePreference-r18 ENUMERATED { scgReleasePreferred } OPTIONAL } MUSIM-CellToRelease-r18 ::= SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellIndex MUSIM-CellToAffectList-r18::= SEQUENCE (SIZE (1..maxNrofServingCells)) OF MUSIM-CellToAffect-r18 MUSIM-CellToAffect-r18 ::= SEQUENCE { musim-SCellIndex-r18 ServCellIndex, musim-MIMO-Layers-DL-r18 INTEGER (1..8) OPTIONAL, musim-MIMO-Layers-UL-r18 INTEGER (1..4) OPTIONAL, musim-SupportedBandwidth-DL-r18 SupportedBandwidth OPTIONAL, musim-SupportedBandwidth-UL-r18 SupportedBandwidth OPTIONAL } MUSIM-AffectedBandsList-r18 ::= SEQUENCE (SIZE (1..maxBandComb)) OF MUSIM-AffectedBands-r18 MUSIM-AffectedBands-r18 ::= SEQUENCE (SIZE (1..maxSimultaneousBands)) OF MUSIM-CapabilityRestrictedBandParameters MUSIM-CapabilityRestrictedBandParameters ::= SEQUENCE { bandEntryIndex BandEntryIndex, musim-CapabilityRestricted-r18 SEQUENCE { musim-MIMO-Layers-DL-r18 INTEGER (1..8) OPTIONAL, musim-MIMO-Layers-UL-r18 INTEGER (1..4) OPTIONAL, musim-SupportedBandwidth-DL-r18 SupportedBandwidth OPTIONAL, musim-SupportedBandwidth-UL-r18 SupportedBandwidth OPTIONAL } OPTIONAL } MUSIM-AvoidedBandsList-r18 ::= SEQUENCE (SIZE (1..maxBandComb)) OF MUSIM-AvoidedBands-r18 MUSIM-AvoidedBands-r18 ::= SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandEntryIndex BandEntryIndex ::= INTEGER(1.. maxCandidateBandIndex-r18) MUSIM-MaxCC-r18 ::= SEQUENCE { musim-MaxCC-DL-r18 INTEGER (1..32) OPTIONAL, musim-MaxCC-UL-r18 INTEGER (1..32) OPTIONAL } ReleasePreference-r16 ::= SEQUENCE { preferredRRC-State-r16 ENUMERATED {idle, inactive, connected, outOfConnected} } ReducedMaxBW-FRx-r16 ::= SEQUENCE { reducedBW-DL-r16 ReducedAggregatedBandwidth, reducedBW-UL-r16 ReducedAggregatedBandwidth } ReducedMaxCCs-r16 ::= SEQUENCE { reducedCCsDL-r16 INTEGER (0..31), reducedCCsUL-r16 INTEGER (0..31) } SL-UE-AssistanceInformationNR-r16 ::= SEQUENCE (SIZE (1..maxNrofTrafficPattern-r16)) OF SL-TrafficPatternInfo-r16 SL-TrafficPatternInfo-r16::= SEQUENCE { trafficPeriodicity-r16 ENUMERATED {ms20, ms50, ms100, ms200, ms300, ms400, ms500, ms600, ms700, ms800, ms900, ms1000}, timingOffset-r16 INTEGER (0..10239), messageSize-r16 BIT STRING (SIZE (8)), sl-QoS-FlowIdentity-r16 SL-QoS-FlowIdentity-r16 } UL-GapFR2-Preference-r17::= SEQUENCE { ul-GapFR2-PatternPreference-r17 INTEGER (0..3) OPTIONAL } PropagationDelayDifference-r17 ::= SEQUENCE (SIZE (1..4)) OF INTEGER (-270..270) IDC-FDM-Assistance-r18 ::= SEQUENCE { affectedCarrierFreqRangeList-r18 AffectedCarrierFreqRangeList-r18 OPTIONAL, affectedCarrierFreqRangeCombList-r18 AffectedCarrierFreqRangeCombList-r18 OPTIONAL, ... } IDC-TDM-Assistance-r18 ::= SEQUENCE { cycleLength-r18 ENUMERATED {ms2, ms3, ms4, ms5, ms6, ms7, ms8, ms10, ms14, ms16, ms20, ms30, ms32, ms35, ms40, ms60, ms64, ms70, ms80, ms96, ms100, ms128, ms160, ms256, ms320, ms512, ms640, ms1024, ms1280, ms2048, ms2560, ms5120, ms10240}, startOffset-r18 INTEGER (0..10239), slotOffset-r18 INTEGER (0..31), activeDuration-r18 CHOICE { subMilliSeconds INTEGER (1..31), milliSeconds ENUMERATED { ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, ms80, ms100, ms200, ms300, ms400, ms500, ms600, ms800, ms1000, ms1200, ms1600, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 } } } AffectedCarrierFreqRangeList-r18 ::= SEQUENCE (SIZE (1..maxFreqIDC-r16)) OF AffectedCarrierFreqRange-r18 AffectedCarrierFreqRange-r18 ::= SEQUENCE { affectedFreqRange-r18 AffectedFreqRange-r18,interferenceDirection-r18 ENUMERATED {nr, other, both, spare}, victimSystemType-r18 VictimSystemType-r16 OPTIONAL } AffectedCarrierFreqRangeCombList-r18 ::= SEQUENCE (SIZE (1..maxCombIDC-r16)) OF AffectedCarrierFreqRangeComb-r18 AffectedCarrierFreqRangeComb-r18 ::= SEQUENCE { affectedCarrierFreqRangeComb-r18 SEQUENCE (SIZE (2..maxNrofServingCells)) OF AffectedFreqRange-r18, interferenceDirection-r18 ENUMERATED {nr, other, both, spare}, victimSystemType-r18 VictimSystemType-r16 OPTIONAL } AffectedFreqRange-r18 ::= SEQUENCE { centerFreq-r18 ARFCN-ValueNR, affectedBandwidth-r18 ENUMERATED {khz200, khz400, khz600, khz800, mhz1, mhz2, mhz3, mhz4, mhz5, mhz6, mhz8, mhz10, mhz20, mhz30, mhz40, mhz50, mhz60, mhz80, mhz100, mhz200, mhz300, mhz400} } UL-TrafficInfo-r18 ::= SEQUENCE (SIZE (1..maxNrofPDU-Sessions-r17)) OF PDU-SessionUL-TrafficInfo-r18 PDU-SessionUL-TrafficInfo-r18 ::= SEQUENCE { pdu-SessionID-r18 PDU-SessionID, qos-FlowUL-TrafficInfoList-r18 SEQUENCE (SIZE (1..maxNrofQFIs)) OF QOS-FlowUL-TrafficInfo-r18 } QOS-FlowUL-TrafficInfo-r18 ::= SEQUENCE { qfi-r18 INTEGER (0..maxQFI), jitterRange-r18 SEQUENCE { lowerBound-r18 JitterBound-r18, upperBound-r18 JitterBound-r18 } OPTIONAL, burstArrivalTime-r18 CHOICE { referenceTime ReferenceTime-r16, referenceSFN-AndSlot ReferenceSFN-AndSlot-r18 } OPTIONAL, trafficPeriodicity-r18 INTEGER (1..640000) OPTIONAL, pduSetIdentification-r18 BOOLEAN OPTIONAL, ... } ReferenceSFN-AndSlot-r18 ::= SEQUENCE { referenceSFN-r18 INTEGER (0..1023), referenceSlot-r18 INTEGER (0..639) } JitterBound-r18 ::= ENUMERATED {ms0, ms0dot5, ms1, ms1dot5, ms2, ms2dot5, ms3, ms3dot5, ms4, ms4dot5, ms5, ms5dot5, ms6, ms6dot5, ms7, beyondMs7} N3C-RelayUE-InfoList-r18 ::= SEQUENCE (SIZE (0..8)) OF N3C-RelayUE-Info-r18 -- Editor's note: Upper limit 8 is FFS. N3C-RelayUE-Info-r18::= SEQUENCE { n3c-RelayIdentification-r18 SEQUENCE { n3c-CellGlobalId-r18 SEQUENCE { n3c-PLMN-Id-r18 PLMN-Identity, n3c-CellIdentity-r18 CellIdentity }, n3c-C-RNTI-r18 RNTI-Value } } SL-PRS-UE-AssistanceInformationNR-r18 ::= SEQUENCE (SIZE (1..maxNrofSL-PRS-TxConfig-r18)) OF SL-PRS-TxInfo-r18 SL-PRS-TxInfo-r18 ::= SEQUENCE { sl-PRS-Periodicity-r18 ENUMERATED {ms100, ms200, ms300, ms400, ms500, ms600, ms700, ms800, ms900, ms1000, spare6, spare5, spare4, spare3, spare2, spare1}, sl-PRS-Priority-r18 INTEGER (1..8) OPTIONAL, sl-PRS-DelayBudget-r18 INTEGER (0..1023) OPTIONAL } --Editor's Note: sl-PRS-Priority and sl-PRS-DelayBudgetis FFS. -- TAG-UEASSISTANCEINFORMATION-STOP -- ASN1STOP NOTE 1: The field may also indicate the UE's preference on reduced configuration corresponding to the maximum number of SRS ports (i.e. nrofSRS-Ports) of each serving cell operating on the associated frequency range. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,627 | 7.7.1 Minimum requirements | The throughput 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.7.1-1 and 7.7.1-2. For operating bands with an unpaired DL part (as noted in Table 5.5-1), the requirements only apply for carriers assigned in the paired part. Table 7.7.1-1: Spurious response parameters Table 7.7.1-2: Spurious response For the UE which supports inter-band CA configuration in Table 7.3.1-1A, Pinterferer power defined in Table 7.7.1-2 is increased by the amount given by ΔRIB,c in Table 7.3.1-1A. | 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.7.1 |
4,628 | 15.5.2.7 Successful HO | One of the functions of Mobility Robustness Optimization is to detect a sub-optimal successful handover event. The aim is to identify underlying conditions during successful ordinary handovers, successful DAPS handovers, or successful Conditional handovers. For analysis of successful handover, the UE may collect Successful Handover Report (SHR) based on configuration by network, if stored, and makes the SHR available to the network as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]. The UE stores the SHR until it is fetched by the network or for 48 hours after the SHR is recorded. For SHR collected during intra-NR handover, if the target NR node fetches the SHR from the UE and the trigger of SHR is T310/T312, it may forward the information to the source NR node, i.e. the node handling the cell reported as source cell in this SHR, by using the ACCESS AND MOBILITY INDICATION message over Xn or by means of the Uplink RAN configuration transfer procedure and Downlink RAN configuration transfer procedure over NG. If the NG-RAN node that fetches the SHR from the UE is neither the source node nor the target node of the handover, it forwards the information to the node(s) which configured the SHR trigger causing the SHR to be generated, by using the ACCESS AND MOBILITY INDICATION message over Xn or by means of the Uplink RAN configuration transfer procedure and Downlink RAN configuration transfer procedure over NG. In case of failure shortly after successful Handover, the same mobility event may generate both a SHR and a RLF report. In this case, the node(s), which configured the SHR trigger causing the SHR, may take the duplication into account e.g. ignore the SHR. Upon retrieval of an SHR, the receiving node may analyse whether its mobility configuration needs adjustment. The SHR report can be used to detect one case of Intra-system Too Late Handover, namely when DAPS HO is configured but an RLF is detected in the source cell during a successful DAPS HO. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 15.5.2.7 |
4,629 | 18.7 Correlation MSISDN | A Correlation MSISDN (C-MSISDN) is an MSISDN (see clause 3.3) that is used for correlation of sessions at access transfer and to route a call from the IM CN subsystem to the same user in the CS domain. The C-MSISDN is equal to the MSISDN or the basic MSISDN if multinumbering option is used (see 3GPP TS 23.008[ Organization of subscriber data ] [2], clause 2.1.3) of the CS access. Any MSISDN of a user that can be used for TS11 (telephony) in the CS domain which is not shared by more than one IMS Private Identity in an IMS CN subsystem, can serve as the user's C-MSISDN. The C-MSISDN is bound to the IMS Private User Identity and is uniquely assigned per IMSI and IMS Private User Identity. If A-MSISDN is available it shall be used as the C-MSISDN. For the definition of A-MSISDN refer to clause 18.9. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 18.7 |
4,630 | 5.3.4.2.1 Mobile Originating Establishment | The service is requested by the originating mobile station by transferring a SETUP message to the network containing the BC repeat indicator IE, the bearer capability 1 information element, and the bearer capability 2 information element. The first mode of operation ("call mode") shall be indicated by the bearer capability 1 information element and the second call mode by the bearer capability 2 information element. A low layer compatibility may optionally be specified for each call mode in a low layer compatibility I and low layer compatibility II information element. In that case: - the SETUP message shall contain the LLC repeat indicator IE and both low layer compatibility I and low layer compatibility II information elements. The low layer compatibility I information element then corresponds to the bearer capability 1 information element and the low layer compatibility II information element to the bearer capability 2 information element; - if no low layer compatibility specification applies for one of the two call modes, the corresponding low layer compatibility IE (low layer compatibility I or low layer compatibility II) shall indicate "not applicable"; - the LLC repeat indicator shall specify the same repeat indication as the BC repeat indicator IE. Similarly, a high layer compatibility may optionally be specified for each call mode in a high layer compatibility i and high layer compatibility ii information element. In that case: - the SETUP message shall contain the HLC repeat indicator IE and both high layer compatibility i and high layer compatibility ii information elements. The high layer compatibility i information element then corresponds to the bearer capability 1 information element and the high layer compatibility ii information element to the bearer capability 2 information element; - if no high layer compatibility specification applies for one of the two call modes, the corresponding high layer compatibility IE (high layer compatibility i or high layer compatibility ii) shall indicate "not applicable"; - the HLC repeat indicator shall specify the same repeat indication as the BC repeat indicator IE. The receiving entity shall ignore whether the LLC repeat indicator IE or HLC repeat indicator are contained in the message or not; it shall also ignore the repeat indication of an LLC repeat indicator IE or HLC repeat indicator IE. If the low layer compatibility II IE is not contained in the message and the low layer compatibility I IE is contained in the message, the receiving entity shall relate it to a call mode indicated in the message that does not specify speech (if any). If the high layer compatibility ii IE is not contained in the message and the high layer compatibility i IE is contained in the message, the receiving entity shall relate it to a call mode indicated in the message that does not specify speech (if any). The specific part of the network which is sensitive to the call mode shall examine each mode described in the bearer capabilities included in the SETUP message by performing compatibility checking as defined in Annex B. If as a result of this compatibility checking the network decides to reject the call, then the network shall initiate call clearing as specified in subclause 5.4 with the following causes: a) #57 "bearer capability not authorized"; b) #58 "bearer capability not presently available"; c) #65 "bearer service not implemented"; d) #70 "only restricted digital information bearer capability is available". | 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.4.2.1 |
4,631 | 5.10 Security aspects 5.10.1 General | The security features in the 5G System include: - Authentication of the UE by the network and vice versa (mutual authentication between UE and network). - Security context generation and distribution. - User Plane data confidentiality and integrity protection. - Control Plane signalling confidentiality and integrity protection. - User identity confidentiality. - Support of LI requirements as specified in TS 33.126[ Lawful Interception requirements ] [35] subject to regional/national regulatory requirements, including protection of LI data (e.g. target list) that may be stored or transferred by an NF. Detailed security related network functions for 5G are described in TS 33.501[ Security architecture and procedures for 5G System ] [29]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.10 |
4,632 | – Q-OffsetRange | The IE Q-OffsetRange is used to indicate a cell, beam or measurement object specific offset to be applied when evaluating candidates for cell re-selection or when evaluating triggering conditions for measurement reporting. The value is in dB. Value dB-24 corresponds to -24 dB, dB-22 corresponds to -22 dB and so on. Q-OffsetRange information element -- ASN1START -- TAG-Q-OFFSETRANGE-START Q-OffsetRange ::= ENUMERATED { dB-24, dB-22, dB-20, dB-18, dB-16, dB-14, dB-12, dB-10, dB-8, dB-6, dB-5, dB-4, dB-3, dB-2, dB-1, dB0, dB1, dB2, dB3, dB4, dB5, dB6, dB8, dB10, dB12, dB14, dB16, dB18, dB20, dB22, dB24} -- TAG-Q-OFFSETRANGE-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,633 | 5.1.3.2 EMM sublayer states in the UE 5.1.3.2.1 General | In the following clauses, the possible EMM states of an EMM entity in the UE are described. Clause 5.1.3.2.2 summarizes the main states of an EMM entity. The substates that have been defined are described in clause 5.1.3.2.3 and clause 5.1.3.2.4. It should be noted, however, that this clause does not include a description of the detailed behaviour of the UE in the single states and does not cover abnormal cases. A detailed description of the behaviour of the UE is given in clause 5.2. For the behaviour of the UE in abnormal cases refer to the description of the elementary EMM procedures in clauses 5.4, 5.5, 5.6 and 5.7. | 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.1.3.2 |
4,634 | 5.2.6.27.2 Nnef_UEId_Get operation | Service operation name: Nnef_UEId_Get Description: Get the UE identifier. Inputs, Required: GPSI or UE address (i.e. IPv4/IPv6 address or MAC address) or External Group Identifier(s). Inputs, Optional: DNN, S-NSSAI, Port number (e.g. TCP or UDP port), IP domain, Application port ID, MTC Provider Information, AF Identifier. Outputs, Required: Result, AF specific UE Identifier represented as an External Identifier or SUPI or Internal Group Identifier(s). NOTE: SUPI and Internal Group Identifier can only be exposed to roaming partners. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.27.2 |
4,635 | 9.11.4.7 Integrity protection maximum data rate | The purpose of the integrity protection maximum data rate information element is for the UE to indicate to the network the maximum data rate per UE for user-plane integrity protection for uplink and the maximum data rate per UE for user-plane integrity protection for downlink that are supported by the UE. The integrity protection maximum data rate is coded as shown in figure 9.11.4.7.1 and table 9.11.4.7.2. The integrity protection maximum data rate is a type 3 information element with a length of 3 octets. Figure 9.11.4.7.1: Integrity protection maximum data rate information element Table 9.11.4.7.2: Integrity protection maximum data rate information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.4.7 |
4,636 | 5.2.21.2 Nnsacf_NSAC services 5.2.21.2.1 General | Service Description: The Nnsacf_NSAC services control the number of UEs registered with a network slice and the number of PDU Sessions associated with a network slice for the network slices subject to NSAC. The consumer NF (e.g. AMF) can request the NSACF to check whether the number of UEs registered with a network slice has reached the maximum number of UEs per network slice and the consumer NF can also request the NSACF to update the number of UEs registered with a network slice. The SMF can request the NSACF to check whether the number of PDU Sessions established on a network slice has reached the maximum number of PDU Sessions per network slice and the SMF can also request the NSACF to update the number of PDU Sessions established on a network slice. While roaming, for a centralized NSAC architecture and/or a Hierarchical NSAC architecture, the VPLMN Primary (or Central) NSACF can fetch the local maximum number of Registered UEs and/or number of LBO PDU sessions. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.21.2 |
4,637 | 7.4 Security | The 3GPP system shall protect against spoofing attacks of the UAS identities. The 3GPP system shall protect the integrity of the message(s) sent from UAS to a UTM containing the UAS identities. The 3GPP system shall protect the confidentiality of the message(s) sent between UAS to a UTM containing the UAS identities. The 3GPP system shall support non-repudiation of data sent from the UAS to UTM. The 3GPP system shall support the capability to provide different levels of integrity and privacy protection for the different connections between UAS and UTM as well as the data being transferred via those connections. The 3GPP system shall support confidentiality protection of identities related to the UAS and personally identifiable information. The 3GPP system shall enable a UTM to authenticate the identity and authority of the official making a request for UAS identity and information. Data held at the UTM may be subject to local data retention and privacy regulations. It shall be possible to support lawful interception for UAS traffic. | 3GPP TS 22.825 | Study on Remote Identification of Unmanned Aerial Systems (UAS) | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 7.4 |
4,638 | 16.21.2.2 L2 MP Relay using N3C indirect path | For the multi-path relay using N3C indirect path between the Remote UE and Relay UE, the protocol stacks for the user plane and control plane of L2 MP Relay architecture are illustrated in Figure 16.21.2.2-1 and Figure 16.21.2.2-2. The L2 MP Relay UE and the L2 MP Remote UE are connected via a N3C interface. In the multi-path relay using N3C indirect path, the SRAP sublayer does not exist on the protocol stack. Without the SRAP entity between L2 MP Remote UE and L2 MP Relay UE, the Uu SDAP, PDCP, and RRC are terminated at gNB and L2 MP Remote UE. While RLC, MAC, and PHY are terminated in Uu hop. An UL PDCP PDU in the L2 MP Remote UE can be delivered to a Uu RLC entity and an intended PDCP entity or RLC entity in the L2 MP Relay UE. It is supported for more than one RB over the Uu link of the L2 MP Relay UE by configuring 1:1 bearer mapping between the Radio bearer in the L2 MP Remote UE and Uu Relay RLC channel in the L2 MP Relay UE. The Uu Relay RLC channels for the PDU delivery of the L2 MP Relay UE's local traffic and relay traffic are configured differently. Bearer identification except LCID is not needed in L2 PDU over the Uu link. If the split bearer is configured and the PDCP PDU duplication is activated on the PDCP entity, the duplicated PDCP PDUs are delivered via both direct path and indirect path. Figure 16.21.2.2-1: User plane protocol stack for L2 Multi-path Relay using N3C indirect path Figure 16.21.2.2-2: Control plane protocol stack for L2 Multi-path Relay using N3C indirect path | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.21.2.2 |
4,639 | 6.1.3.8.3 Unsuccessful MBMS context activation requested by the network | Upon receipt of the REQUEST MBMS CONTEXT ACTIVATION message, the MS may reject the network requested MBMS context activation by sending the REQUEST MBMS CONTEXT ACTIVATION REJECT message to the network. The sender of the message shall include the same TI as included in the REQUEST MBMS CONTEXT ACTIVATION and an additional cause code that typically indicates one of the following causes: # 26: insufficient resources; # 31: activation rejected, unspecified; # 40: feature not supported; or # 95 - # 111: protocol errors. The network shall stop timer T3385 and enter in state PDP-INACTIVE. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.1.3.8.3 |
4,640 | 5.2.8.2.4 Nsmf_PDUSession_Release service operation | Service operation name: Nsmf_PDUSession_Release. Description: It causes the immediate and unconditional deletion of the resources associated with the PDU Session. This service operation is used by V-SMF to request the H-SMF or used by I-SMF to request the SMF to release the resources related to a PDU Session for the serving network initiated PDU release case (e.g. implicit De-registration of UE in the serving network). Input, Required: SM Context ID. Input, Optional: Secondary RAT Usage Data, N4 information. Output, Required: Result Indication. Output, Optional: Small Data Rate Control Status, APN Rate Control Status. See clause 4.3.4.3 for an example usage of this service operation. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.8.2.4 |
4,641 | 4.4.1.3 N4 Session Modification procedure | The N4 Session Modification procedure is used to update the N4 session context of an existing PDU Session at the UPF, which is executed between SMF and UPF whenever PDU Session related parameters have to be modified. Figure 4.4.1.3-1 N4 Session Modification procedure 1. SMF receives the trigger to modify the existing PDU Session. 2. The SMF sends an N4 session modification request message to the UPF that contains the update for the structured control information which defines how the UPF needs to behave. 3. The UPF identifies the N4 session context to be modified by the N4 Session ID. Then, the UPF updates the parameters of this N4 session context according to the list of parameters sent by the SMF. The UPF responds with an N4 session modification response message containing any information that the UPF has to provide to the SMF in response to the control information received. 4. The SMF interacts with the network entity which triggered this procedure (e.g. AMF or PCF). | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.4.1.3 |
4,642 | 5.27.1.11 Controlling time synchronization service based on the Subscription | The distribution of timing information, 5G access stratum-based time distribution and (g)PTP-based time distribution, for a UE may be controlled based on subscription data stored in the UDM. The (g)PTP-based or 5G access stratum-based time synchronization service may be provided to a UE based on the UE's subscription which is specified in the TS 23.502[ Procedures for the 5G System (5GS) ] [3] clause 5.2.3.3.1. The Access and Mobility Subscription data include for the control of 5G access stratum-based time distribution the following information: - the Access Stratum Time Synchronization Service Authorization, which indicates whether the UE should be provisioned with 5G system internal clock timing information over access stratum as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28]. - optionally, the Uu time synchronization error budget. - optionally, one or more periods of start and stop times defining the times when the UE should be provisioned with 5G system internal clock timing information. - optionally, a Time Synchronization Coverage Area comprising a list of TAs where the UE shall be provisioned with 5G system internal clock timing information. - optionally, a clock quality detail level indicating whether and which clock quality information to provide to the UE. It comprises one of the following values: clock quality metrics or acceptable/not acceptable indication. - optionally, the clock quality acceptance criteria for the UE. It may be defined based on one or more attributes listed in Table 5.27.1.12-1. During the Registration procedure, the AMF retrieves the subscription from UDM. If the AMF receives 5G access stratum-based time synchronization service subscription for the given UE, the AMF controls the 5G access stratum-based time distribution: - If the 5G access stratum-based time synchronization service is allowed for the UE, the AMF provides the 5G access stratum time distribution indication to the NG-RAN so that it can provide 5G timing information to the UE. - The AMF may provide a Uu time synchronization error budget to the NG-RAN (as described in clause 5.27.1.9). If the UE's subscription contains a Uu time synchronization error budget, then AMF sends it to NG-RAN. Otherwise, the AMF uses the pre-configured Uu time synchronization error budget and sends it to NG-RAN. - If the UE's subscription contains Coverage Area (defined as a list of TAs), the AMF configures the NG-RAN to provide the 5G timing information to UE only when the UE is in the Coverage Area as described in clause 5.27.1.10. - If the AMF receives the start and stop times, then the AMF enables and disables the 5G access stratum time distribution indication to the NG-RAN according to the expiry of start and stop times if the UE is in CM-CONNECTED state. If the UE is in CM-IDLE state when a Start time condition is met, the AMF pages the UE and provides the 5G access stratum time distribution indication to NG-RAN as part of the subsequent service request procedure initiated by the UE in the response to the paging. - If the AMF receives the clock quality detail level, then the AMF configures the NG-RAN to provide clock quality detail information reporting to UE as described in clause 5.27.1.12. The AMF may instruct the UE to reconnect to the network when the UE detects that the RAN timing synchronization status has changed while the UE is in RRC_INACTIVE or RRC_IDLE, as described in clause 5.27.1.12. - If the AMF receives the same parameters both in the Access and Mobility Subscription data from UDM and in the AM Policy from PCF, the AMF shall use the value received from the AM policy. The Time Synchronization Subscription data is the subscription data for the control of (g)PTP-based time distribution and 5G access stratum-based time distribution and includes the following information: - the "AF request Authorization", indicating whether the UE is authorized for an AF-requested 5G access stratum-based time distribution and (g)PTP-based time distribution services. The indication is provided separately for each service: - "allowed" or "not allowed" for (g)PTP based time synchronization service (per DNN/S-NSSAI and UE identity), - "allowed" or "not allowed" for ASTI based time synchronization services (per UE identity). - If the "AF request Authorization" is set to "allowed", the Time Synchronization Subscription data may contain additional information for (g)PTP/ASTI based time synchronization services authorized by: - optionally, a list of TA(s) which specifies an area (a so-called Authorized Time Synchronization Coverage Area) in which an AF may request time synchronization services; - optionally, one or more periods of authorized start and stop times, which indicates the allowed time period during which an AF may request time synchronization services; - optionally, authorized Uu time synchronization error budget, which indicates the limit the AF may request. - one or more Subscribed time synchronization service ID(s), each containing the DNN/S-NSSAI and a reference to a PTP instance configuration pre-configured at the TSCTSF (e.g. PTP profile, PTP domain, etc.): - optionally, for each PTP instance configuration, one or more periods of start and stop times defining active times of time synchronization service for the PTP instance. - optionally, for each PTP instance configuration, a Time Synchronization Coverage Area defining a list of TAs where the (g)PTP-based time synchronization is available for the UEs in the PTP instance. - optionally, for each PTP instance configuration, Uu time synchronization error budget. The TSCTSF retrieves the Time Synchronization Subscription data from UDM. If the TSCTSF receives the Time Synchronization Subscription data for a UE, the TSCTSF controls the Time Synchronization Service including (g)PTP-based time distribution and 5G access stratum-based time distribution: - The TSCTSF retrieves the Time Synchronization Subscription data from the UDM when the TSCTSF receives an AF request for the time synchronization service (either ASTI or (g)PTP). According to the "AF request Authorization" in the UE's Time Synchronization Subscription data, the TSCTSF determines whether the UE is authorized for an AF-requested time synchronization service: - If the UE's Time Synchronization Subscription data contains an Authorized Time Synchronization Coverage Area (i.e. a list of TA(s) defining the restricted area for AF request), TSCTSF checks whether the AF requested Coverage Area satisfies the authorized area: If the requested Coverage Area (see clause 5.27.1.10) is within the Authorized Time Synchronization Coverage Area, the TSCTSF uses the requested Coverage Area. If the Authorized Time Synchronization Coverage Area is inside of the requested Coverage Area, the TSCTSF uses the Authorized Time Synchronization Coverage Area. If the requested Coverage Area partly overlaps with the Authorized Time Synchronization Coverage Area, the TSCTSF uses the intersection of them. If there is no overlap between them, the TSCTSF shall reject the AF request. - If the AF requested Coverage Area satisfies the authorized area totally or partly, TSCTSF notifies to AF with the Time Synchronization Service information based on the Authorized Time Synchronization Coverage Area. TSCTSF subscribes to UE's presence in the Area of Interest at the discovered AMF(s), if the UE(s) moves out of the AF requested coverage area, the TSCTSF shall disable Time Synchronization Service and notifies to AF. - If the UE's Time Synchronization Subscription data contains authorized Uu time synchronization error budget, the TSCTSF checks whether the Uu time synchronization error budget derived from AF request satisfies (i.e. equal or larger than) the authorized Uu time synchronization error budget. - If the UE's Time Synchronization Subscription data contains periods of authorized start and stop times, the TSCTSF checks whether the AF requested temporal validity condition satisfies (i.e. within) any of the periods of authorized start and stop times. If such period is found, the TSCTSF uses the start and stop times of the AF request. - If the AF request is authorized, the TSCTSF proceeds as specified in clause 5.27.1.8 and in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. Otherwise, the TSCTSF rejects the AF request. - The TSCTSF retrieves the Time Synchronization Subscription data from the UDM when it receives notification from the PCF that a UE has established a PDU Session that is potentially impacted by (g)PTP-based time synchronization service: - The TSCTSF retrieves the PTP instance configurations referenced from the "Subscribed time synchronization service ID(s)". The PTP instance configurations are stored locally in the TSCTSF. The TSCTSF determines if one or more of the PTP instance configurations match with the DNN/S-NSSAI of the given PDU Session. If no PTP instance exists for the given PTP instance configuration, the TSCTSF initializes the PTP instance in 5GS as described in clause K.2.2. - The TSCTSF configures a PTP port in DS-TT and adds it to the corresponding PTP instance in NW-TT as described in clause K.2.2. - If the PTP instance configuration referenced by UE's Time Synchronization Subscription data contains an Uu time synchronization error budget, then the TSCTSF uses it to derive an Uu time synchronization error budget available for the NG-RAN to provide the 5G access stratum time for the UE as specified in clause 5.27.1.9. - If the PTP instance configuration referenced by the Time Synchronization Subscription data for the UE contains start and stop times, the TSCTSF, upon expiry of start time, creates the PTP instance and adds the PTP port in DS-TT to the PTP instance. Upon expiry of stop time, if this is the last period of start and stop times in the PTP instance configuration, the TSCTSF deletes the PTP instance, otherwise the TSCTSF temporarily disables the PTP instance. - If the PTP instance configuration referenced by the Time Synchronization Subscription data for the UE contains a Time Synchronization Coverage Area, the TSCTSF subscribes to UE's Presence in Area(s) of Interest corresponding to the Time Synchronization Coverage Area at the discovered AMF(s). When the TSCTSF determines that the UE has moved inside or outside of the Time Synchronization Coverage Area, the TSCTSF adds or temporarily removes the PTP port in DS-TT from the corresponding PTP instance. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.27.1.11 |
4,643 | C.2 GPRS Support Nodes | This clause defines a naming convention for GSNs. It shall be possible to refer to a GSN by a logical name which shall then be translated into a physical IP address. This clause proposes a GSN naming convention which would make it possible for an internal GPRS DNS server to make the translation. An example of how a logical name of an SGSN could appear is: sgsnXXXX.mncYYY.mccZZZ.gprs X, shall be Hex coded digits, Y andZz shall be encoded as single digits (in the range 0-9). If there are less than 4 significant digits in XXXX one or more "0" digit(s) is/are inserted at the left side to fill the 4 digits coding. If there are only 2 significant digits in YYY, a "0" digit is inserted at the left side to fill the 3 digit coding. As an example, the logical name for SGSN 1B34, MCC 167 and MNC 92 will be coded in the DNS server as: sgsn1B34. mnc092.mcc167.gprs | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | C.2 |
4,644 | 7.9 Inter-node Resource Coordination | For MR-DC operations, MN and SN may coordinate their UL and DL radio resources in semi-static manner via UE associated signalling. The MN may coordinate its sidelink radio resources with the SN using the same UE associated signalling. In EN-DC, CSI-RS based SgNB change between neighbour en-gNBs is supported by enabling that neighbour en-gNBs can exchange their own CSI-RS configurations and on/off status via the MeNB. In NGEN-DC and NR-DC, CSI-RS based SN change between neighbour gNBs is supported by enabling that neighbour gNBs can exchange their own CSI-RS configurations and on/off status via the MN. | 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 | 7.9 |
4,645 | 6.1.3.12 Handling session management request for MS configured for dual priority | If timer T3396 is running for a specific APN due to one of the following reasons: - an ACTIVATE PDP CONTEXT REQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST, MODIFY PDP CONTEXT REQUEST or ACTIVATE MBMS CONTEXT REQUEST message containing the low priority indicator set to "MS is configured for NAS signalling low priority" was rejected with a timer value for timer T3396 and SM cause value #26 "insufficient resources"; - a DEACTIVATE PDP CONTEXT REQUEST message was received with a timer value for timer T3396 and SM cause value #26 "insufficient resources" for a PDP context established with the low priority indicator set to "MS is configured for NAS signalling low priority", or - because the MS received a DEACTIVATE PDP CONTEXT REQUEST message containing a timer value for timer T3396 and SM cause value #26 "insufficient resources" for a PDP context established with the low priority indicator set to "MS is configured for NAS signalling low priority"; upon request of the upper layers the MS can: - send an ACTIVATE PDP CONTEXT REQUEST or ACTIVATE MBMS CONTEXT REQUEST message to the same APN, with low priority indicator set to "MS is not configured for NAS signalling low priority"; or, - send an ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST message, with low priority indicator set to "MS is not configured for NAS signalling low priority", for an active PDP context established with low priority indicator set to "MS is not configured for NAS signalling low priority" exists. If timer T3396 is running, because any of the following messages containing the low priority indicator set to "MS is configured for NAS signalling low priority" was rejected with a timer value for timer T3396 and SM cause value #26 "insufficient resources": - an ACTIVATE PDP CONTEXT REQUEST without an APN and with request type different from "emergency"; or - an ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST message for a non-emergency PDN connection established without APN sent by the MS, or because the MS received a DEACTIVATE PDP CONTEXT REQUEST message containing a timer value for timer T3396 and SM cause value #26 "insufficient resources" for a non-emergency PDN connection established without an APN and established with the low priority indicator set to "MS is configured for NAS signalling low priority", then upon request of the upper layers the MS can: - send an ACTIVATE PDP CONTEXT REQUEST message without an APN and with low priority indicator set to "MS is not configured for NAS signalling low priority" for establishment an non-emergency PDN connection; or - send an ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST message, with low priority indicator set to "MS is not configured for NAS signalling low priority", for an active non-emergency PDP context established without an APN and with low priority indicator set to "MS is not configured for NAS signalling low priority". For requests with low priority indicator set to "MS is configured for NAS signalling low priority", the MS shall follow the procedures specified in subclause 6.1.3.1.3. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.1.3.12 |
4,646 | 4.17.8 NF/NF service status subscribe/notify across PLMNs | In the case that the NF service consumer intends to subscribe to the status of NF/NF service instance(s) in home PLMN, the NRF in serving PLMN needs to request "NF status subscribe" service from NRF in the home PLMN. The notification is sent from the NRF in the home PLMN to the NF service consumer in the serving PLMN without the involvement of the NRF in the serving PLMN. The procedure is depicted in the figure below: Figure 4.17.8-1: NF/NF service status subscribe/notify across PLMNs NOTE 1: The NRF in the home PLMN communicates with the NRF and the NF consumer in the serving PLMN via the SEPPs in the respective PLMNs. For the sake of clarity, SEPPs are not depicted in the flow. 1. The NF service consumer in the serving PLMN invokes Nnrf_NFManagement_NFStatusSubscribe Request from an appropriate configured NRF in the serving PLMN. 2. The NRF in serving PLMN identifies NRF in home PLMN (hNRF) based on the home PLMN ID and it requests Nnrf_NFManagement_NFStatusSubscribe service from NRF in home PLMN. As the NRF in the serving PLMN triggers the Nnrf_NFManagement_NFStatusSubscribe service on behalf of the NF service consumer, the NRF in the serving PLMN shall not replace the information of the service requester NF, i.e. NF consumer ID, in the status subscribe Request message it sends to the hNRF. 3. The NRF in serving PLMN acknowledges the execution of Nnrf_NFManagement_NFStatusSubscribe Request to the NF consumer in the serving PLMN. 4. NRF in the home PLMN notifies about newly registered/updated/deregistered NF instances along with its NF services to the subscribed NF service consumer in the serving PLMN. NOTE 2: The NF service consumer unsubscribes to receive NF status notifications by invoking Nnrf_NFManagement_NFStatusUnSubscribe service operation. NOTE 3: When the NF or NF service intance becomes unavailable, the NRF in the home PLMN invokes Nnrf_NFManagement_NFStatusNotify service to notify the NF service consumer in the serving PLMN based on the subscription. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.17.8 |
4,647 | 10.2.7.2.2 Mapping to resource elements | The same antenna port shall be used for all symbols of the narrowband secondary synchronization signal within a subframe. The UE shall not assume that the narrowband secondary synchronization signal is transmitted on the same antenna port as any of the downlink reference signals. The UE shall not assume that the transmissions of the narrowband secondary synchronization signal in a given subframe use the same antenna port, or ports, as the narrowband secondary synchronization signal in any other subframe. If indicated by higher layer, a UE may assume different precoders are applied for NSSS transmission in a number of consecutive NSSS occasions signalled by higher layer. The sequence shall be mapped to resource elements in sequence starting with in increasing order of first the index over the 12 assigned subcarriers and then the index over the assigned last symbols of subframe 9 for frame structure type 1 or subframe 0 for frame structure type 2 in radio frames fulfilling , where is given by Table 10.2.7.2.2-1. Table 10.2.7.2.2-1: NSSS number of symbols For resource elements overlapping with resource elements where cell-specific reference signals according to clause 6.10 are transmitted, the corresponding sequence element is not used for the NSSS but counted in the mapping process. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 10.2.7.2.2 |
4,648 | 4.3.2.5 Authentication not accepted by the network | If the authentication response (RES or SRES) is not valid, the network response depends upon the type of identity used by the mobile station in the first message, that is: - the TMSI was used; or - the IMSI was used. If the TMSI has been used, the network may decide to initiate the identification procedure. If the IMSI given by the mobile station then differs from the one the network had associated with the TMSI, the authentication should be restarted with the correct parameters. If the IMSI provided by the MS is the expected one (i.e. authentication has really failed), the network should send an AUTHENTICATION REJECT message to the mobile station. If the IMSI has been used, or the network decides not to try the identification procedure, an AUTHENTICATION REJECT message should be transferred to the mobile station. After having sent this message, all MM connections in progress (if any) are released and the network should initiate the RR connection release procedure described in subclause 3.5.of 3GPP TS 44.018[ None ] [84] (A/Gb mode only), 3GPP TS 25.331[ None ] [23c] (UTRAN Iu mode only), or in 3GPP TS 44.118[ None ] [111] (GERAN Iu mode only). Upon receipt of an AUTHENTICATION REJECT message, a) if the message has been successfully integrity checked by the lower layers, the mobile station shall set the update status in the SIM/USIM to U3 ROAMING NOT ALLOWED, delete from the SIM/USIM the stored TMSI, LAI and ciphering key sequence number. The SIM/USIM shall be considered as invalid until switching off or the SIM/USIM is removed. If the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. If the MS maintains a counter for "SIM/USIM considered invalid for GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. b) if the message is received without integrity protection, then the MS shall start timer T3247 with a random value uniformly drawn from the range between 30 minutes and 60 minutes, if the timer is not running (see subclause 4.1.1.6A). Additionally, the MS shall: - if the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services" events and the counter has a value less than an MS implementation-specific maximum value, proceed as specified in subclause 4.1.1.6A, list item 1.a) for the case a LOCATION UPDATING REJECT message is received without integrity protection. Additionally, if the MS maintains a counter for "SIM/USIM considered invalid for GPRS services", then the MS shall increment this counter; and - otherwise proceed as specified under list item a) above for the case that the message has been successfully checked by the lower layers. List item b) above is also applicable, if the message is received in A/Gb mode. If the AUTHENTICATION REJECT message is received in the state IMSI DETACH INITIATED the mobile station shall follow subclause 4.3.4.3. If the AUTHENTICATION REJECT message is received in any other state the mobile station shall abort any MM specific, MM connection establishment or call re-establishment procedure, stop any of the timers T3210, T3230, T3214 or T3216 (if they were running), release all MM connections (if any), start timer T3240 and enter the state WAIT FOR NETWORK COMMAND, expecting the release of the RR connection. If the RR connection is not released within a given time controlled by the timer T3240, the mobile station shall abort the RR connection. In both cases, either after a RR connection release triggered from the network side or after a RR connection abort requested by the MS-side, the MS enters state MM IDLE, substate NO IMSI. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.3.2.5 |
4,649 | 10.1.4.1.2 Reference signal sequence for | The reference signal sequences for is defined by a cyclic shift of a base sequence according to , where is given by Table 10.1.4.1.2-1 for , Table 10.1.4.1.2-2 for and Table 5.5.1.2-1 for . If group hopping is not enabled, the base sequence index is given by higher layer parameters threeTone-BaseSequence, sixTone-BaseSequence, and twelveTone-BaseSequence for , , and , respectively. If not signalled by higher layers, the base sequence is given by If group hopping is enabled, the base sequence index is given by clause 10.1.4.1.3. The cyclic shift for and is derived from higher layer parameters threeTone-CyclicShift and sixTone-CyclicShift, respectively, as defined in Table 10.1.4.1.2-3. For , if npusch-CyclicShift in PUR-Config-NB is configured for NPUSCH (re)transmission corresponding to preconfigured uplink resource it provides the value of and the cyclic shift in a slot is given as , otherwise . Table 10.1.4.1.2-1: Definition of for Table 10.1.4.1.2-2: Definition of for Table 10.1.4.1.2-3: 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 | 10.1.4.1.2 |
4,650 | 4.11.1.4.2 EPS bearer ID transfer | Following procedures are updated to transfer EPS bearer ID(s) allocation information to target AMF. - step 14d in figure 4.11.1.3.3-1 in EPS to 5GS Idle mode mobility with N26 (clause 4.11.1.3.3). - step 7 in figure 4.11.1.2.2.2-1 in EPS to 5GS handover using N26 interface prepare phase (clause 4.11.1.2.2.2). Figure 4.11.1.4.2-1: Procedures for EPS bearer IDs transfer 1. The AMF sends an Nsmf_PDUSession_CreateSMContext Request message to the SMF in above case; 2. The SMF+PGW-C to AMF: Nsmf_PDUSession_CreateSMContext Response with the allocated EBI information. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.1.4.2 |
4,651 | 6.1.4.1a Linking authentication confirmation to Nudm_UECM_Registration procedure from AMF | The information sent from the AUSF to the UDM that a successful or unsuccessful authentication of a subscriber has occurred, shall be used to link authentication confirmation to subsequent procedures. The AUSF shall send the Nudm_UEAuthentication_ResultConfirmation service operation for this purpose as shown in figure6.1.4.1a-1. Figure 6.1.4.1a-1: Linking increased Home control to subsequent procedures 1. The AUSF shall inform UDM about the result and time of an authentication procedure with a UE using a Nudm_UEAuthentication_ResultConfirmation Request. This shall include the SUPI, a timestamp of the authentication, the authentication type (e.g. EAP method or 5G-AKA), and the serving network name. NOTE: It may be sufficient for the purposes of fraud prevention to send only information about successful authentications, but this is up to operator policy. 2. The UDM shall store the authentication status of the UE (SUPI, authentication result, timestamp, and the serving network name). 3. UDM shall reply to AUSF with a Nudm_UEAuthentication_ResultConfirmation Response. 4. Upon reception of subsequent UE related procedures (e.g. Nudm_UECM_Registration_Request from AMF) UDM may apply actions according to home operator’s policy to detect and achieve protection against certain types of fraud (e.g. as proposed in clause 6.1.4.2). | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.1.4.1a |
4,652 | K.2.2 UE configuration | An IOPS-enabled UE has the dedicated IOPS PLMN identity configured in a separate dedicated USIM application as an HPLMN along with the Access Class status of 11 or 15, subject to regional/national regulatory requirements and operator policy. NOTE: Access Class 15 can be reserved for use by network operator personnel who are responsible for critical recovery operations of the network. An IOPS-enabled UE can display information on available PLMNs, including the IOPS PLMN, assisting the user to activate an appropriate USIM application. Subject to user preferences, e.g. to maintain a group communication, the user can perform a manual USIM application switch at any time. When an authorized IOPS-enabled UE, with the dedicated IOPS USIM application activated, selects an IOPS-mode cell, it selects the dedicated IOPS PLMN identity, attaches to the IOPS PLMN (supported by the Local EPC) and is authenticated using security procedures as specified in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [41] and the security credentials from the active IOPS USIM application. | 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") | K.2.2 |
4,653 | 6.4.1 Description | 5G introduces the opportunity to design a system to be optimized for supporting diverse UEs and services. While support for IoT is provided by EPS, there is room for improvement in efficient resource utilization that can be designed into a 5G system whereas they are not easily retrofitted into an existing system. Some of the underlying principles of the potential service and network operation requirements associated with efficient configuration, deployment, and use of UEs in the 5G network include bulk provisioning, resource efficient access, optimization for UE originated data transfer, and efficiencies based on the reduced needs related to mobility management for stationary UEs and UEs with restricted range of movement. As sensors and monitoring UEs are deployed more extensively, the need to support UEs that send data packages ranging in size from a small status update in a few bits to streaming video increases. A similar need exists for smart phones with widely varying amounts of data. Specifically, to support short data bursts, the network should be able to operate in a mode where there is no need for a lengthy and high overhead signalling procedure before and after small amounts of data are sent. The system will, as a result, avoid both a negative impact to battery life for the UE and wasting signalling resources. For small form factor UEs it will be challenging to have more than 1 antenna due to the inability to get good isolation between multiple antennas. Thus, these UEs need to meet the expected performance in a 5G network with only one antenna. Cloud applications like cloud robotics perform computation in the network rather than in a UE, which requires the system to have high data rate in the uplink and very low round trip latency. Supposed that high density cloud robotics will be deployed in the future, the 5G system need to optimize the resource efficiency for such scenario. Additional resource efficiencies will contribute to meeting the various KPIs defined for 5G. Control plane resource efficiencies can be achieved by optimizing and minimizing signalling overhead, particularly for small data transmissions. Mechanisms for minimizing user plane resources utilization include in-network caching and application in a Service Hosting Environment closer to the end user. These optimization efforts contribute to achieving lower latency and higher reliability. Diverse mobility management related resource efficiencies are covered in clause 6.2. Security related resource efficiencies are covered in clause 8.8. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.4.1 |
4,654 | 1.7.1 Voice Group Call Service (VGCS) and Voice Broadcast Service (VBS) | Voice Group Call Service and Voice Broadcast Service are applicable in A/Gb mode only. For mobile stations supporting the Voice Group Call Service or the Voice Broadcast Service, it is explicitly mentioned throughout the present document if a certain procedure is applicable only for such a service and, if necessary, how mobile stations not supporting such a service shall behave. For VGCS and VBS, the following possible mobile station implementations exist: - support of listening to voice broadcast calls (VBS listening); - support of originating a voice broadcast call (VBS originating); - support of listening to voice group calls (VGCS listening); - support of talking in voice group calls (VGCS talking. This always includes the implementation for VGCS listening); - support of originating a voice group call (VGCS originating. This always includes the implementation for VGCS talking). Apart from the explicitly mentioned combinations, all possible combinations are optional and supported by the present document. The related terms are used in the present document, if information on these implementation options is required. | 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 | 1.7.1 |
4,655 | 4.5.1.5 MM connection establishment for emergency calls | A MM connection for an emergency call may be established in all states of the mobility management sublayer which allow MM connection establishment for a normal originating call. In addition, establishment may be attempted in all service states where a cell is selected (see subclause 4.2.2) but not in the MM CONNECTION ACTIVE state (GROUP TRANSMIT MODE) state. However, as a network dependent option, a MM connection establishment for emergency call may be rejected in some of the states. When a user requests an emergency call establishment the mobile station will send a CM SERVICE REQUEST message to the network with a CM service type information element indicating emergency call establishment. If the network does not accept the emergency call request, e.g., because IMEI was used as identification and this capability is not supported by the network, the network will reject the request by returning a CM SERVICE REJECT message to the mobile station. The reject cause information element indicates the reason for rejection. The following cause values may apply: #3 "Illegal MS" #4 "IMSI unknown in VLR" #5 "IMEI not accepted" #6 " Illegal ME" #17 "Network failure" #22 "Congestion" #25 "Not authorized for this CSG" #32 "Service option not supported" #34 "Service option temporarily out of order" With the above defined exceptions, the procedures described for MM connection establishment in subclauses 4.5.1.1 and 4.5.1.2 shall be followed. NOTE: Normally, the mobile station will be identified by an IMSI or a TMSI. However, if none of these identifiers is available in the mobile station, then the mobile station shall use the IMEI for identification purposes. The network may in that case reject the request by returning a CM SERVICE REJECT message with reject cause: #5 "IMEI not accepted". | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.5.1.5 |
4,656 | 11.2.1.4 Access to Internet, Intranet or ISP with Mobile IPv4 | General A way to allow users to roam from one environment to another, between fixed and mobile, between public and private as well as between different public systems is to use Mobile IP RFC 3344 [30]. Mobile IP (MIP) is a mobility management protocol developed by IETF. The Mobile IP Foreign Agent (FA) RFC 3344 [30] is located in the Core Network in the GGSN. MIP also uses a Home Agent (HA) RFC 3344 [30] which may or may not be located in a PLMN network. Interworking model for MIP A FA is located in the GGSN. The interface between the GGSN and the FA will probably not be standardised as the GGSN/FA is considered being one integrated node. The mapping between these two is a matter of implementation. Each FA must be configured with at least one care-of address. In addition a FA must maintain a list that combines IP addresses with TEIDs of all the visiting MSs that have registered with the FA. IP packets destined for the MS are intercepted by the HA and tunneled to the MS’s care-of address, i.e. the FA. The FA de-tunnels the packets and forwards the packets to the MS. Mobile IP related signalling between the MS and the FA is done in the user plane. MIP registration messages RFC 3344 [30] are sent with UDP. Figure 11c: The protocol stacks for the Gi IP reference point in the MIP signalling plane Figure 11d: Protocol stacks for user access with MIP In figure 11d: "(Tunneling)" is intended to show asymmetric traffic flow. Tunneling (IP-in-IP) is only used in the direction from the ISP towards the MT. Authentication of the user is supported in Mobile IPv4. This authentication mechanism may involve communication with an authentication server (e.g. RADIUS), although this is not shown in figure 11d. Address allocation – at PDP context activation no IP address is allocated to the MS indicated by 0.0.0.0. in the "Requested PDP Address" field. If the MS does not have a static IP address which it could register with the HA, it will acquire a dynamic IP address from the HA RFC 2794 [25]. After completion of the PDP activation the SGSN is informed of the assigned IP address by means of the GGSN initiated PDP Context Modification Procedure. An example of a signalling scheme, shown in figure 11e, is described below. In this example the MS is separated into a TE and MT, with AT commands and PPP used in-between (see 3GPP TS 27.060[ Packet domain; Mobile Station (MS) supporting Packet Switched services ] [10]). The PS attach procedures have been omitted for clarity. Figure 11e: Example of PDP Context activation with Mobile IP registration (the PS attach procedure not included) 1. The AT command carries parameters that the MT needs to request the PDP Context Activation. The important parameter here, is the APN (Access Point Name), see clause A below. The AT command is followed by a setup of the PPP connection between the MT and the TE. 2. As part of the PPP connection, LCP negotiates Maximum-Receive-Unit between the TE and the MT. No PPP authentication is required when using MIPv4. 3. As part of the PPP connection, the TE sends an IPCP Configure Request using the MIPv4 configuration option (see RFC 2290 [37]). The TE sends either its Home Address or a null address (i.e. 0.0.0.0) if the Network Address identifier is used (see RFC 2794 [25]). 4. The MT sends the "Activate PDP Context Request" to the SGSN. The message includes various parameters of which the "APN" (Access Point Name) and the "Requested PDP Address" are of interest here. The TE/MT may use APN to select a reference point to a certain external network or to select a service. APN is a logical name referring to the external packet data network or to a service that the subscriber wishes to connect to. The "Requested PDP Address" should be omitted for all MSs using Mobile IP. This is done irrespective of if the TE has a permanently assigned Mobile IP address from its Mobile IP home network, a previously assigned dynamic home address from its Mobile IP home network or if it wishes the Mobile IP home network to allocate a "new" dynamic home address. A. The SGSN will base the choice of GGSN based on the APN that is given by the MS. 5. The SGSN requests the selected GGSN to set up a PDP Context for the MS. The PDP address and APN fields are the same as in the "Activate PDP Context Request" message. 6. A Create PDP Context Response is sent from the GGSN/FA to the SGSN. If the creation of PDP Context was successful, some parameters will be returned to the SGSN, if not, an error code will be returned. If the GGSN has been configured, by the operator, to use a Foreign Agent for the requested APN, the PDP address returned by the GGSN shall be set to 0.0.0.0. indicating that the PDP address shall be reset by the MS with a Home Agent after the PDP context activation procedure. 7. The Activate PDP Context Accept message is sent by the SGSN to the MT and contains similar information as the Create PDP Context Response message. 8. The MT sends an IPCP Configure Ack to the TE in order to terminate the PPP connection phase. 9. The Agent Advertisement RFC 3344 [30] is an ICMP (Internet Control Message Protocol) Router Advertisement message with a mobility agent advertisement extension. The latter part contains parameters of the FA that the mobile node needs, among those are one or more care-of addresses that the FA offers. This message should be sent, in the Packet Domain user plane, as an IP limited broadcast message, i.e. destination address 255.255.255.255, however only on the TEID for the requesting MS to avoid broadcast over the radio interface. 10. The Mobile IP Registration Request is sent from the mobile node to the GGSN/FA across the Packet Domain backbone as user traffic. The mobile node includes its (permanent) home address as a parameter RFC 3344 [30]. Alternatively, it can request a temporary address assigned by the home network by sending 0.0.0.0 as its home address, and include the Network Access Identifier (NAI) in a Mobile-Node-NAI Extension RFC 2794 [25] and RFC 2486 [31]. 11. The FA forwards the Mobile IP Registration Request to the home network of the mobile node, where a home agent (HA) processes it. Meanwhile, the GGSN/FA needs to store the home address of the mobile node or the NAI and the local link address of the MS, i.e. the TEID (Tunnel Endpoint ID). 12. The Registration Reply is sent from the home network to the FA, which extracts the information it needs and forwards the message to the mobile node in the Packet Domain user plane. As the FA/GGSN knows the TEID and the NAI or home address, it can pass it on to the correct MS. B. The GGSN/FA extracts the home address from the Mobile IP Registration Reply message and updates its GGSN PDP Context. 13. The GGSN triggers a "GGSN initiated PDP Context modification procedure" in order to update the PDP address in the SGSN and in the MT. | 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.4 |
4,657 | 8.3.2.1 Single-layer Spatial Multiplexing | For single-layer transmission on antenna port 5, the requirements are specified in Table 8.3.2.1-2, with the addition of the parameters in Table 8.3.2.1-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the demodulation performance using user-specific reference signals with full RB or single RB allocation. Table 8.3.2.1-1: Test Parameters for Testing DRS Table 8.3.2.1-2: Minimum performance DRS (FRC) For single-layer transmission on antenna ports 7 or 8 upon detection of a PDCCH with DCI format 2B, the requirements are specified in Table 8.3.2.1-4 and 8.3.2.1-5, with the addition of the parameters in Table 8.3.2.1-3 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify rank-1 performance on one of the antenna ports 7 or 8 with and without a simultaneous transmission on the other antenna port. Table 8.3.2.1-3: Test Parameters for Testing CDM-multiplexed DM RS (single layer) Table 8.3.2.1-4: Minimum performance for CDM-multiplexed DM RS without simultaneous transmission (FRC) Table 8.3.2.1-5: Minimum performance for CDM-multiplexed DM RS with interfering simultaneous transmission (FRC) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.3.2.1 |
4,658 | 8.13.2.7 Management based trace activation in MR-DC with 5GC | In the MR-DC with 5GC case, the EM provides the MDT configuration to both MN and SN independently. In Management Based Trace Activation towards a SN, the SN may send the CELL TRAFFIC TRACE message including the Trace ID and privacy indicator to the MN as described in TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ] [20]. Upon reception of the CELL TRAFFIC TRACE message from the SN, the MN will send a CELL TRAFFIC TRACE message including the Trace ID and privacy indicator to the CN for this UE. The CN forwards the Trace ID and other information to the TCE as specified in TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ] [20]. The following shows a flow chart summarizing the functionality in MR-DC when the SN is the SgNB. Figure 8.13.2.7-1 Data anonymization in MR-DC when the SN is the SgNB 0. The gNB-CU-CP, the gNB-CU-UP, the gNB-DU receives the MDT configuration from EM and select the suitable UEs for MDT data collection. The anonymization MDT configuration parameter from the EM is considered to be IMEI-TAC. 1. For the management based MDT activation in gNB-CU-UP and/or in gNB-DU, if the gNB-CU-UP and/or the gNB-DU receive an MDT Configuration including the anonymization parameter set to IMEI-TAC, the gNB-CU-UP and/or gNB-DU send CELL TRAFFIC TRACE message to the gNB-CU-CP for this UE, including Trace ID and privacy indicator. 2. For the management based MDT activation in gNB-CU-CP, upon receiving the CELL TRAFFIC TRACE message from E1/F1, the gNB-CU-CP shall send a CELL TRAFFIC TRACE message to the MN for this UE, including Trace ID and privacy indicator. 3. The MN sends a CELL TRAFFIC TRACE message to the CN for this UE, including Trace ID and privacy indicator. The CN forwards Trace ID and other information to the TCE as specified in TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ] [20]. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.13.2.7 |
4,659 | 8.10 Multiple TNLAs for E1 | NOTE: The general principles and procedures described in this clause also apply to ng-eNB and W1/E1 interface, i.e. W1 interface between ng-eNB-DU and ng-eNB-CU-CP/ng-eNB-CU-UP, E1 interface between ng-eNB-CU-CP and ng-eNB-CU-UP, if not explicitly specified otherwise. In the following, the procedure for managing multiple TNLAs for E1 is described. Figure 8.10-1: Managing multiple TNLAs for E1. 1. Either the gNB-CU-CP or gNB-CU-UP establishes the first SCTP association with the gNB-CU-UP or gNB-CU-CP respectively using a configured TNL address. NOTE: The gNB-CU-UP/gNB-CU-CP may use different source and/or destination IP end point(s) if the TNL establishment towards one IP end point fails. How the gNB-CU-UP/gNB-CU-CP gets the remote IP end point(s) and its own IP address are outside the scope of this specification. 2-3 (A). Once the TNLA (gNB-CU-UP initiated) has been established, the gNB-CU-UP initiates the E1 Setup procedure to exchange application level configuration data. 2-3 (B). Once the TNLA (gNB-CU-CP initiated) has been established, the gNB-CU-CP initiates the E1 Setup procedure to exchange application level configuration data. 4-6. The gNB-CU-CP may add additional SCTP Endpoint(s) to be used for E1 signalling between the gNB-CU-CP and the gNB-CU-UP pair using the gNB-CU-CP Configuration Update procedure. The gNB-CU-CP Configuration Update procedure also allows the gNB-CU-CP to request the gNB-CU-UP to modify or release TNLA(s). 7-9. The gNB-CU-UP may add additional TNL association(s) to be used for E1 signalling using a gNB-CU-CP endpoint already in use for existing TNL associations between the gNB-CU-CP and the gNB-CU-UP pair. The gNB-CU-UP CONFIGURATION UPDATE message including the gNB-CU-UP ID shall be the first E1AP message sent on an additional TNLA of an already setup E1 interface instance after the TNL association has become operational. The E1AP UE TNLA binding is a binding between a E1AP UE association and a specific TNL association for a given UE. After the E1AP UE TNLA binding is created, the gNB-CU-CP can update the UE TNLA binding by sending the E1AP message for the UE to the gNB-CU-UP via a different TNLA. The gNB-CU-UP shall update the E1AP UE TNLA binding with the new TNLA. The gNB-CU-UP Configuration Update procedure also allows the gNB-CU-UP to inform the gNB-CU-CP that the indicated TNLA(s) will be removed by the gNB-CU-UP. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.10 |
4,660 | 5.8.2.4.2 Traffic Detection Information | The SMF controls the traffic detection at the UP function by providing detection information for every PDR. For IPv4 or IPv6 or IPv4v6 PDU Session type, detection information is a combination of: - CN tunnel info. - Network instance. - QFI. - IP Packet Filter Set as defined in clause 5.7.6.2. - Application Identifier: The Application Identifier is an index to a set of application detection rules configured in UPF. - FQDN Filter for DNS Query message. For Ethernet PDU Session type, detection information is a combination of: - CN tunnel info. - Network instance. - QFI. - Ethernet Packet Filter Set as defined in clause 5.7.6.3. In this Release of the specification for Unstructured PDU Session Type, the UPF does not perform-QoS Flow level traffic detection for QoS enforcement. Traffic detection information sent by the SMF to the UPF for a PDU Session may be associated with Network instance for detection and routing of traffic over N6. In the case of IP PDU Session Type, Network Instances can, e.g. be used by the UPF for traffic detection and routing in the case of different IP domains or overlapping IP addresses. In the case of Ethernet PDU Session Type, different Network Instances can e.g. be configured in the UPF with different ways to handle the association between N6 and the PDU Sessions. Based on SMF instructions, UPF may identify the PDU Sets, according to the Protocol Description in PDR, to derive the PDU Set Information for DL traffics and send it to RAN via DL GTP-U header of each PDU identified as belonging to a PDU Set. The PDU Set Information, is described in clause 5.37.5. The PDU Set identification can be done by UPF implementation or by detecting RTP/SRTP header or payload. The details of the RTP/SRTP headers, header extensions and/or payloads used to identify PDU Sets are defined in TS 26.522[ 5G Real-time Media Transport Protocol Configurations ] [179]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.8.2.4.2 |
4,661 | 5.3.5 Triggers for network analytics | Triggers for the AMF to request for or subscribe to the analytics information from the NWDAF are internal logic in the AMF and may include for example: - UE access and mobility related event subscription by other NFs (e.g. SMF, NEF); - locally detected events; - analytics information received. The trigger conditions may depend on operator and implementation policy in the AMF. When a trigger condition happens, the AMF may decide if any analytics information is needed and if so, request for or subscription to the analytics information from the NWDAF. The AMF may, upon detection of certain local events, e.g. frequent mobility re-registration of one or more UEs, subscribe to mobility related abnormal behaviour analytics of the UE(s) as described in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86] in order to trace UE mobility trend and take appropriate actions. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.5 |
4,662 | F.6 5GS DetNet node configuration | The DetNet controller triggers the procedure to provide Deterministic Networking specific parameters to 5GS. Figure F.6-1: Deterministic Networking specific parameter provisioning 1. The DetNet controller provides YANG data model configuration to the TSCTSF. The TSCTSF uses the identifier of the incoming and outgoing interfaces to determine the affected PDU Session(s) and flow direction, whether it is uplink or downlink as described in more detail in clause 5.28.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The TSCTSF also determines if the flow is UE to UE in which case two PDU Sessions will be affected for the flow and the TSCTSF breaks up the requirements to individual requirements for the PDU Sessions. 2. The TSCTSF uses the traffic requirements in the YANG configuration as described in clause 6.1.3.23b of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. The TSCTSF also constructs the TSCAC for each flow description. 3. The TSCTSF provides the mapped parameters and the flow description to the PCF(s) on a per AF Session basis. 4. The PCF authorizes the request from TSCTSF. If the PCF determines that the requirements can't be authorized, it rejects the request. Once the PCF authorizes the request, the PCF updates the SMF with corresponding new PCC rule(s) with PCF initiated SM Policy Association Modification procedure as described in clause 4.16.5.2. The SMF applies the received PCC rules. This can induce creating a new QoS flow to the PDU session and triggers the resource allocation in the RAN. 5. PCF provides response to the TSCTSF. 6. The TSCTSF provides response to the DetNet controller. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | F.6 |
4,663 | 16a.3.2 PPP PDP type | Figure 25b describes the Diameter message flows between a GGSN and a Diameter server for the case where PPP is terminated at the GGSN. The case where PPP is relayed to an LNS is beyond the scope of the present document. NOTE 1: Separate accounting and Authentication servers may be used. NOTE 2: Actual messages depend on the used authentication protocol (e.g. PAP, CHAP). NOTE 3: If some external applications require Diameter Accounting request (Start) information before they can process user packets, then the selected APN (GGSN) may be configured in such a way that the GGSN drops user data until the Accounting Answer (START) is received from the AAA server. The GGSN may delete the PDP context if the Accounting Response (START) is not received. NOTE 4: An LCP termination procedure may be performed. Either the MS or the GGSN may initiate the context deactivation. NOTE 5: The AA-Request message shall be used for primary PDP context only. NOTE 6: Network Initiated deactivation. NOTE 7: User Initiated deactivation. Figure 25b: Diameter message flow for PDP type PPP (successful user authentication case) When a GGSN receives a Create PDP Context Request message for a given APN, the GGSN shall immediately send a Create PDP context response back to the SGSN. After PPP link setup, the authentication phase may take place. During Authentication phase, the GGSN sends a Diameter AA-Request to a Diameter server. The Diameter server authenticates and authorizes the user. If Diameter is also responsible for IP address allocation the Diameter server shall return the allocated IP address or IPv6 prefix in the AA-answer message (if the user was authenticated). If the user is not authenticated, the GGSN shall send a Delete PDP context request to the SGSN. The AA-Request and AA-Answer messages are only used for the primary PDP context. Even if the GGSN was not involved in user authentication (e.g. for PPP no authentication may be selected), it may send a Diameter Accounting-Request (START) message to a Diameter server. If no Diameter session is already open for the user a Diameter session needs to be activated, otherwise the existing Diameter session is used to send the Accounting-Request (START). The NSAPI will identify the particular PDP context this accounting refers to. The Accounting-Request message also indicates to the Diameter server that the user session has started, and the QoS parameters associated to the session. This message contains parameters, e.g. a tuple which includes the user-id, IP address or IPv6 prefix, and the MSISDN to be used by application servers (e.g. WAP gateway) in order to identify the user. If some external applications require Diameter Accounting request (Start) information before they can process user packets, then the selected APN (GGSN) may be configured in such a way that the GGSN drops user data until the Accounting Answer (START) is received from the Diameter server. The GGSN may delete the PDP context if the Accounting Answer (START) is not received. The Authentication and Accounting servers may be separately configured for each APN. When the GGSN receives a Delete PDP Context Request message and providing a Diameter Accounting-Request (START) message was sent previously, the GGSN shall send a Diameter Accounting-Request (STOP) message to the Diameter server, which indicates the termination of this particular user session. The NSAPI will identify the particular PDP context this accounting refers to. The GGSN shall immediately send a Delete PDP context response, without waiting for an Accounting-Answer (STOP) message from the Diameter server. If this was the last PDP context for that PDP address, the GGSN shall additionally send an STR message to the Diameter server. The Diameter server shall reply with an STA and shall deallocate the IP address or IPv6 prefix (if any) initially allocated to the subscriber. | 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.3.2 |
4,664 | 6.3.3.1 Overview | The selection and reselection of the UPF for PDU session establishment, UE mobility or UE traffic offloading are performed by the SMF by considering UPF deployment scenarios such as centrally located UPF and distributed UPF located close to or at the Access Network site. The selection of the UPF shall also enable deployment of UPF with different capabilities, e.g. UPFs supporting no or a subset of optional functionalities. The UPF selection for PDU session establishment in home routed roaming case, the UPF(s) in home PLMN is selected by SMF(s) in HPLMN, and the UPF(s) in the VPLMN is selected by SMF(s) in VPLMN. The exact set of parameters used for the selection mechanism is deployment specific and controlled by the operator configuration. The UPF selection for PDU session establishment, UE mobility or UE traffic offloading involves: - a step of SMF Provisioning of available UPF(s). This step may take place while there is no PDU Session to establish and may be followed by N4 Node Level procedures defined in clause 4.4.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] where the UPF and the SMF may exchange information such as the support of optional functionalities and capabilities. - A step of selection of an UPF for a particular PDU Session; it is followed by N4 session management procedures defined in clause 4.4.1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. To collect the data from the UPF as defined in clause 5.8.2.17, the related dedicated UPF is discovered and selected as following: - When the NF consumer or SCP directly subscribes to the UPF, the NF consumer or SCP queries the NRF including the related discovery parameter. The NRF returns the UPF(s) which meet(s) the discovery request. - When the NF consumer or SCP shall subscribe via the SMF, the NF consumer gets the serving SMF information from the UDM per SUPI, DNN and S-NSSAI. After that, the NF consumer sends a subscription to the indicated SMF and the SMF identifies the related UPF(s) using the parameters of the subscription (e.g. target flow description, AoI, etc.) and transfers the related event subscription information to the identified UPF(s). If the NF consumer does not know the SUPI but only the UE IP address, it may need to invoke the BSF to get the SUPI corresponding to the triplet (IP address, DNN and S-NSSAI). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.3.1 |
4,665 | A.12 KNG-RAN* derivation function for target ng-eNB | When deriving a KNG-RAN* from current KgNB or from fresh NH and the target physical cell ID in the UE and NG-RAN for handover purposes and transition from RRC_INACTIVE to RRC_CONNECTED states the following parameters shall be used to form the input S to the KDF. - FC = 0x71 - P0 = PCI (target physical cell id) - L0 = length of PCI (i.e. 0x00 0x02) - P1 = EARFCN-DL (target physical cell downlink frequency) - L1 = length of EARFCN-DL (i.e. 0x00 0x03) The input key KEY shall be the 256-bit NH when the index NCC in the handover increases, otherwise the current 256-bit KgNB (when source is gNB) or KeNB (when source is ng-eNB). | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | A.12 |
4,666 | 4.4.1.2 Average UL cell PDCP SDU bit-rate | a) This measurement provides the average cell bit-rate of PDCP SDUs on the uplink. This represents successful transmissions of user plane traffic; control signalling and retransmissions are excluded from this measure. The measurement is split into subcounters per E-RAB QoS level (QCI). b) CC c) This measurement is obtained by accumulating the number of bits leaving the eNodeB/RN on the X2 or S1 interface, and then dividing the sum by the measurement period. The measurement is performed at the PDCP SDU level. PDCP SDUs that were not received over the air interface in the cell (but were forwarded from another eNodeB during handover) are excluded from the count. Separate counters are maintained for each QCI. The sum of all supported per QCI measurements shall equal the total UL cell PDCP SDU bit-rate. In case only a subset of per QCI measurements is supported, a sum subcounter will be provided first. d) Each measurement is an integer value representing the bit-rate measured in kbit/s. The number of measurements is equal to the number of QCIs plus a possible sum value identified by the .sum suffix. e) The measurement name has the form DRB. PdcpSduBitrateUl.QCI where QCI identifies the E-RAB level quality of service class. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS i) One usage of this measurement is to support the KPI "E-UTRAN data Energy Efficiency" defined in [13]. | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.4.1.2 |
4,667 | 5.9.3 IMSI and APN information retrieval procedure | This procedure is used by the RCAF to determine the UEs that are served by a congested eNodeB or E-UTRAN cell and the APNs of the active PDN connections of these UEs. This information is used to determine the PCRFs serving these UEs and subsequently report RAN user-plane congestion information (RUCI) to the PCRFs. The decision whether the RCAF requests MME to retrieve the list of UEs on eNodeB or E-UTRAN cell level is up to operator configuration. NOTE 1: The details of congestion reporting to the PCRF are specified in TS 23.203[ Policy and charging control architecture ] [6]. The RCAF determines the MMEs that are serving the congested eNodeB or E-UTRAN cell based on the Tracking Area Identities served by the congested eNodeB or E-UTRAN cell. For further details on the related DNS procedure see TS 29.303[ Domain Name System Procedures; Stage 3 ] [61]. The following steps are applied to all MMEs serving the congested eNodeB or E-UTRAN cell. NOTE 2: In network sharing scenarios the RCAF belongs to the RAN operator. In this case it is up to inter-operator agreements and operator configuration which sharing partner's MMEs the RCAF queries IMSI and APN information from. Figure 5.9.3-1: IMSI and APN information retrieval procedure 1. The RCAF sends an IMSI/APN information request to the MME. The request shall identify whether the request refers to an eNodeB or an E-UTRAN cell and shall contain the related eNodeB ID or ECGI. NOTE 3: The eNodeB ID is defined in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]. 2. The MME sends the IMSI/APN information response to the RCAF. The response shall contain the list of UEs (identified by the IMSIs) served by the eNodeB or E-UTRAN cell and the list of APNs of the active PDN connections of each IMSI. If the RCAF requested the IMSI/APN information on E-UTRAN cell level, then the MME first determines the list of UEs served by that E-UTRAN cell. The MME may achieve this by querying the eNodeB that the E-UTRAN cell belongs to for the exact ECGI for all UEs served by this eNodeB using the Location Reporting procedure (clause 5.9.1). NOTE 4: Applying the Location Reporting feature due to an E-UTRAN cell level RCAF request can increase S1-MME interface signalling load. NOTE 5: In order for RCAF to maintain the list of impacted UEs (identified by the IMSIs) (and related APN information) for a congested cell, the RCAF needs to regularly receive IMSI/APN information updates from the MME. The details of whether the RCAF needs to query the MME regularly or whether the MME updates the RCAF regularly without further explicit requests from the RCAF is specified in Stage 3. | 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.9.3 |
4,668 | 8.9 Data security and privacy | The 5G system shall support data integrity protection and confidentiality methods that serve URLLC, high data rates and energy constrained devices. The 5G system shall support a mechanism to verify the integrity of a message as well as the authenticity of the sender of the message. The 5G system shall support encryption for URLLC services within the requested end-to-end latency. Subject to regulatory requirements, the 5G system shall enable an MNO to provide end-to-end integrity protection, confidentiality, and protection against replay attacks between a UE and third-party application server, such that the 3GPP network is not able to intercept or modify the data transferred between a UE and third-party application server. Subject to regulatory requirements and based on operator policy, the 5G system shall provide a mechanism to support data integrity verification service to assure the integrity of the data exchanged between the 5G network and a third-party service provider. NOTE: This requirement could apply to mechanisms supported over the interface between 5G core network and an external application, with no impact on RAN and UE. Subject to regulatory requirements and based on operator policy, the 5G system shall provide a mechanism to support confidentiality to prevent exposure of data exchanged between the 5G network and a third party service provider. NOTE: This requirement could apply to mechanisms supported over the interface between 5G core network and an external application, with no impact on RAN and UE. Subject to operator’s policies, a 5G system with satellite access supporting S&F Satellite operation shall be able to preserve security of the data stored and forwarded. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 8.9 |
4,669 | C.3.4 ECIES profiles C.3.4.0 General | Unless otherwise stated, the ECIES profiles follow the terminology and processing specified in SECG version 2 [29] and [30]. The profiles shall use "named curves" over prime fields. For generating successive counter blocks from the initial counter block (ICB) in CTR mode, the profiles shall use the standard incrementing function in section B.1 of NIST Special Publication 800-38A [16] with m = 32 bits. The ICB corresponds to T1 in section 6.5 of [16]. The value of the MAC tag in ECIES, shall be the L most significant octets of the output generated by the HMAC function, where L equals to the maclen. Profile A shall use its own standardized processing for key generation (section 6 of RFC 7748 [46]) and shared secret calculation (section 5 of RFC 7748 [46]). The Diffie-Hellman primitive X25519 (section 5 of RFC 7748 [46]) takes two random octet strings as input, decodes them as scalar and coordinate, performs multiplication, and encodes the result as an octet string. The shared secret output octet string from X25519 shall be used as the input Z in the ECIES KDF (section 3.6.1 of [29]). As the point compression is not applied for profile A, the prefix rule for compression type defined in [29] section 5.1.3 shall not be used in profile A, i.e., there shall be no prefix for the ephemeral public key of Profile A. Profile B shall use point compression to save overhead and shall use the Elliptic Curve Cofactor Diffie-Hellman Primitive (section 3.3.2 of [29]) to enable future addition of profiles with cofactor h ≠ 1. For curves with cofactor h = 1 the two primitives (section 3.3.1 and 3.3.2 of [29]) are equal. The profiles shall not use backwards compatibility mode (therefore are not compatible with version 1 of SECG). | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | C.3.4 |
4,670 | 4.4.1.4 Bx | The Bx reference point supports interaction between a CGF and the BD. The information crossing this reference point is comprised of CDR files. A common, standard file transfer protocol (e.g. FTAM, FTP) shall be used, including the transport mechanisms specified for the selected protocol. This interface application is defined in TS 32.297[ Telecommunication management; Charging management; Charging Data Record (CDR) file format and transfer ] [52]. The information contained in the files corresponds to the CDRs defined per domain/subsystem/service, as stated in clause 4.4.1.3. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.4.1.4 |
4,671 | 5.5.4.3 UE-initiated authentication and key agreement procedure initiation | Upon receiving a ProSe direct link establishment request from the 5G ProSe remote UE or the 5G ProSe end UE including the SUCI or the CP-PRUK ID of the 5G ProSe remote UE or the 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] when the security for 5G ProSe communication via 5G ProSe UE-to-network relay or 5G ProSe UE-to-UE relay is performed over control plane as specified in 3GPP TS 33.503[ Security Aspects of Proximity based Services (ProSe) in the 5G System (5GS) ] [56], the UE shall: a) allocate a PRTI value as specified in subclause 5.5.4.2; b) create a RELAY KEY REQUEST message; c) set the PRTI IE of the RELAY KEY REQUEST message to the allocated PRTI value; d) set the relay key request parameters IE of the RELAY KEY REQUEST message with SUCI or the CP-PRUK ID, relay service code, and nonce_1 received from the of the 5G ProSe remote UE or the 5G ProSe end UE; e) send the RELAY KEY REQUEST message; and f) start the timer T3527 upon sending the RELAY KEY REQUEST message. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.4.3 |
4,672 | 5.3.4.1 Service Description | This circuit switched service allows the two users on a point-to-point connection to use the connection between them for different information transfer during the same call, but not at the same time. If the negotiation during call establishment leads to the recognition of the above mentioned services, the in-call modification procedure is allowed to be executed within the current call by changing from one call mode to the other. In some cases the in-call modification procedure makes it necessary to change the channel configuration by allocating a new channel and in other cases to change channel configuration parameters while keeping the previously allocated channel. This change is determined by the network, which initiates either the channel assignment procedure, handover procedure or channel mode modify procedure (see clause 3). The capability and the initial mode desired must be identified by the mobile station by identifying each mode of operation with a separate information element during call establishment. Further the type of change between the modes must be identified by means of the repeat indicator: mode 1 "alternate" mode 2. | 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.4.1 |
4,673 | 6.3.12b Access Network selection for 5G NSWO | In addition to the PLMN lists specified in clause 6.3.12 and in clause 6.3.12a, a WLAN access network may also advertise the following PLMN list: - A PLMN List-5, which includes candidate PLMNs with which "AAA connectivity to 5GC" is supported. A WLAN access network supports "AAA connectivity to 5GC" in a candidate PLMN when it deploys an AAA function that can connect with a NSWOF in this PLMN or can connect with a NSWOF in another PLMN (i.e. HPLMN in roaming case) via AAA proxy. The NSWOF supports "WLAN connection using 5G credentials without 5GS registration", as defined in clause 4.2.15. If the UE selects a PLMN that is neither UE's HPLMN nor EHPLMN through which the NSWO request should be sent towards the HPLMN, the UE shall use the decorated NAI format as specified in clause 4.2.15 and in TS 23.003[ Numbering, addressing and identification ] [19]. For access to SNPN or CH , a WLAN access network may also advertise the following SNPN list: - A SNPN List-5, which includes SNPNs with which "AAA connectivity to 5GC" is supported. The SNPNs are the candidate serving SNPNs that the WLAN access network can connect with. A WLAN access network supports "AAA connectivity to 5GC" in a SNPN when it deploys an AAA function that can connect with a NSWOF in this SNPN or can connect with a NSWOF or AAA server in a CH via AAA Proxy. The SNPN or CH supports "WLAN connection using 5G credentials without 5GS registration", as defined in clause 4.2.15. NOTE: The selected SNPN within the SNPN List-5 is interpreted as serving SNPN when the SNPN does not correspond to UE's subscribed SNPN. When the UE wants to connect to a WLAN access network using the 5G NSWO procedure defined in TS 33.501[ Security architecture and procedures for 5G System ] [29], Annex S, the UE may retrieve the PLMN List-5 or SNPN List-5 advertised by each discovered WLAN access network and may consider this list for selecting the WLAN access network to connect to. For example, if the UE identifies that the HPLMN or CH is included in the PLMN List-5 or SNPN List-5 advertised by a WLAN access network, the UE may select this WLAN access network to connect to using the 5G NSWO procedure. When the UE is configured by HPLMN or CH to use 5G NSWO for connecting to WLAN access networks using its 5G credentials (as defined in TS 33.501[ Security architecture and procedures for 5G System ] [29]), the UE shall attempt to select a WLAN that supports 5G NSWO and shall only use the 5G NSWO procedure for connecting to the selected WLAN. A WLAN access network may also advertise a list of SNPNs which includes SNPNs with which "AAA connectivity to 5GC" is supported. A WLAN access network supports "AAA connectivity to 5GC" in an SNPN when it deploys an AAA function that can connect with a SNPN or CH using any of the architectures defined in clause 4.2.15. When the UE operating in SNPN access mode wants to connect to a WLAN access network using the 5G NSWO procedure defined in Annex S of TS 33.501[ Security architecture and procedures for 5G System ] [29], the UE may retrieve the SNPNs with which "AAA connectivity to 5GC" is supported that are advertised by each discovered WLAN access network and may consider this information for selecting the WLAN access network to which it attempts to connect. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.12b |
4,674 | 5.5.4.15 Event D1 (Distance between UE and referenceLocation1 is above threshold1 and distance between UE and referenceLocation2 is below threshold2) | The UE shall: 1> consider the entering condition for this event to be satisfied when both condition D1-1 and condition D1-2, as specified below, are fulfilled; 1> consider the leaving condition for this event to be satisfied when condition D1-3 or condition D1-4, i.e. at least one of the two, as specified below, are fulfilled; Inequality D1-1 (Entering condition 1) Inequality D1-2 (Entering condition 2) Inequality D1-3 (Leaving condition 1) Inequality D1-4 (Leaving condition 2) The variables in the formula are defined as follows: Ml1 is the distance between UE and a reference location for this event (i.e. referenceLocation1 as defined within reportConfigNR for this event), not taking into account any offsets. Ml2 is the distance between UE and a reference location for this event (i.e. referenceLocation2 as defined within reportConfigNR for this event), not taking into account any offsets. Hys is the hysteresis parameter for this event (i.e. hysteresisLocation as defined within reportConfigNR for this event). Thresh1 is the threshold for this event defined as a distance, configured with parameter distanceThreshFromReference1, from a reference location configured with parameter referenceLocation1 within reportConfigNR for this event. Thresh2 is the threshold for this event defined as a distance, configured with parameter distanceThreshFromReference2, from a reference location configured with parameter referenceLocation2 within reportConfigNR for this event. Ml1 is expressed in meters. Ml2 is expressed in the same unit as Ml1. Hys is expressed in the same unit as Ml1. Thresh1 is expressed in the same unit as Ml1. Thresh2 is expressed in the same unit as Ml1. NOTE: The definition of Event D1 also applies to CondEvent D1. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.4.15 |
4,675 | 6.11B.1 Sequence generation | The MWUS sequence in subframe is defined by where is the actual duration of MWUS as defined in [4]. For a UE not configured with group MWUS, . For a UE configured with group MWUS, for , where is determined by the UE group to which the UE is associated as determined by higher layers [10]. In a resource that is not shared with non-group MWUS, the common MWUS sequence shall be determined by . In a resource that is shared with non-group MWUS, the common MWUS sequence is determined by higher layers [9]. The scrambling sequence is given by clause 7.2, and shall be initialized at the start of the MWUS with where is the first frame of the first PO to which the MWUS is associated, is the first slot of the first PO to which the MWUS is associated and indicates the group MWUS resource to which the UE is associated. For a UE not configured with group MWUS, , whereas for a UE configured with group MWUS, is determined by higher layers [10]. | 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.11B.1 |
4,676 | 8.4.3.1.2 TDD Pcell (TDD single carrier) | 8.4.3.1.2.1 Minimum Requirement 2 Tx Antenna Port The average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.4.3.1.2.1-2 for Pcell and in Table 8.4.3.1.2.1-3 for LAA Scell(s), with the additional of the parameters in Table 8.4.3-1, and Table 8.4.3.1.2.1-1. The downlink physical setup is in accordance with Annex C.3.2. Table 8.4.3.1.2.1-1: Test Parameters for LAA Scell(s) Table 8.4.3.1.2.1-2: Single carrier performance for CCs which are not LAA Scells for multiple CA configurations Table 8.4.3.1.2.1-3: Single carrier performance for LAA Scell(s) for multiple CA configurations | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.4.3.1.2 |
4,677 | 4.5.1.6.1 Call re-establishment, initiation by the mobile station | NOTE: The network is unable to initiate call re-establishment. If at least one request to re-establish an MM connection is received from a CM entity as a response to the indication that the MM connection is interrupted (see subclause 4.5.2.3.) the mobile station initiates the call re-establishment procedure. If several CM entities request re-establishment only one re-establishment procedure is initiated. If any CM entity requests re-establishment, then re-establishment of all transactions belonging to all Protocol Discriminators that permit Call Re-establishment shall be attempted. Upon request of a CM entity to re-establish an MM connection the MM sublayer requests the RR sublayer to establish an RR connection and enters MM sublayer state WAIT FOR REESTABLISH. This request contains an establishment cause and a CM RE-ESTABLISHMENT REQUEST message. When the establishment of an RR connection is indicated by the RR sublayer, the MM sublayer of the mobile station starts timer T3230, gives an indication to all CM entities that are being re-established, and remains in the MM sublayer state WAIT FOR REESTABLISH. The CM RE-ESTABLISHMENT REQUEST message contains the - mobile identity according to subclause 10.5.1.4; - mobile station classmark 2; - ciphering key sequence number. NOTE: Whether or not a CM entity can request re-establishment depends upon the Protocol Discriminator. The specifications for Short Message Service (3GPP TS 24.011[ Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface ] [22]), Call Independent Supplementary Services (3GPP TS 24.010[ Mobile radio interface layer 3; Supplementary services specification; General aspects ] [21]) and Location Services (3GPP TS 44.071[ None ] [23a]) do not currently specify any re-establishment procedures. For a shared GERAN in A/Gb mode, if the MS is a GERAN network sharing supporting MS, the chosen PLMN identity shall be indicated to the GERAN in the CM RE-ESTABLISHMENT REQUEST message using the Skip Indicator IE as specified in subclause 10.3.1. Upon receiving a CM RE-ESTABLISHMENT REQUEST message, the network shall analyse its content. Depending on the type of request, the network may start any of the MM common procedures and RR procedures. The network may initiate the classmark interrogation procedure, for example, to obtain further information on the mobile station's encryption capabilities. The identification procedure (see subclause 4.3.3) may be invoked. The network may invoke the authentication procedure (see subclause 4.3.2). In A/Gb mode, the network decides if the security mode setting procedure shall be invoked (see 3GPP TS 44.018[ None ] [84] subclause 3.4.7). An indication from the RR sublayer that the security mode setting procedure is completed, or reception of a CM SERVICE ACCEPT message, shall be treated as a service acceptance indication by the mobile station. In Iu mode, the network decides if the security mode control procedure shall be invoked (see 3GPP TS 25.331[ None ] [23c] and 3GPP TS 44.118[ None ] [111]). An indication from the RR sublayer that the security mode control procedure is completed, or reception of a CM SERVICE ACCEPT message, shall be treated as a service acceptance indication by the mobile station. The MM connection re-establishment is completed, timer T3230 shall be stopped, all CM entities associated with the re-establishment shall be informed, and MM sublayer state MM CONNECTION ACTIVE is re-entered. All the MM connections are considered to be active. If the network cannot associate the re-establishment request with any existing call for that mobile station, a CM SERVICE REJECT message is returned with the reject cause: #38 "call cannot be identified" If call re-establishment cannot be performed for other reasons, a CM SERVICE REJECT is returned, the appropriate reject cause may be any of the following (see annex G): # 4 "IMSI unknown in VLR"; # 6 "illegal ME"; #17 "network failure"; #22 "congestion"; #25 "not authorized for this CSG"; #32 "service option not supported"; #34 "service option temporarily out of order". If the service request is rejected due to general NAS level mobility management congestion control, the network shall set the MM cause value to #22 "congestion" and assign a back-off timer T3246 (see 3GPP TS 23.012[ Location management procedures ] [140]). Whatever the reject cause a mobile station receiving a CM SERVICE REJECT as a response to the CM RE-ESTABLISHMENT REQUEST shall stop T3230, release all MM connections and proceed as described in subclause 4.5.3.1. In addition: - if cause value #4 is received, the mobile station deletes any TMSI, LAI and ciphering key sequence number in the SIM/USIM, changes the update status to NOT UPDATED (and stores it in the SIM/USIM according to subclause 4.1.2.2), and enters the MM sublayer state WAIT FOR NETWORK COMMAND. If subsequently the RR connection is released or aborted, this will force the mobile station to initiate a normal location updating. The CM re-establishment request shall not be memorized during the location updating procedure. - if cause value #6 is received, the mobile station deletes any TMSI, LAI and ciphering key sequence number in the SIM/USIM, changes the update status to ROAMING NOT ALLOWED (and stores it in the SIM/USIM according to subclause 4.1.2.2), and enters the MM sublayer state WAIT FOR NETWORK COMMAND. The MS shall consider the SIM/USIM as invalid for non-GPRS services until switch-off or the SIM/USIM is removed. - If cause value # 22 is received, the T3246 value IE is present in the CM SERVICE REJECT message and the value indicates that this timer is neither zero nor deactivated, the MS shall abort the re-establishment, release any MM connections, and proceed as specified in subclause 4.5.3.1. The MS shall stop timer T3246 if it is running. If the CM SERVICE REJECT message is integrity protected, the MS shall start timer T3246 with the value provided in the T3246 value IE. If the CM SERVICE REJECT message is not integrity protected, the MS shall start timer T3246 with a random value from the default range specified in table 11.1. The MS stays in the current serving cell and applies the normal cell reselection process. The CM RE-ESTABLISHMENT REQUEST procedure should not be restarted when timer T3246 expires or is stopped. If cause value #22 is received, the T3246 value IE is not present in the CM SERVICE REJECT message or if the value provided in the T3246 value IE indicates that this timer is zero or deactivated, the MS shall abort the re-establishment, release any MM connections, and proceed as specified in subclause 4.5.3.1. - if cause value #25 is received from a CSG cell and the mobile station is in UTRAN Iu mode, the MS shall check whether the CM SERVICE REJECT message with cause #25 is integrity protected. If the message is not integrity protected, the MS shall discard the message. Otherwise, the MS shall remove the entry corresponding to the CSG ID and associated PLMN identity of the cell where the MS has sent the CM SERVICE REQUEST message from the Allowed CSG list if the CSG ID and associated PLMN identity are contained in the Allowed CSG list, and enter the MM sublayer state WAIT FOR NETWORK COMMAND. If the CSG ID and associated PLMN identity of the cell where the MS has sent the CM SERVICE REQUEST message is contained in the Operator CSG list, the MS shall proceed as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14] subclause 3.1A. If cause value #25 is received and the cell is not a CSG cell or the MS is not in UTRAN Iu mode, the MS shall discard the CM SERVICE REJECT message. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.5.1.6.1 |
4,678 | 13a.2.2.3 Creation of a PDP Context/EPS Bearer for IMS Media Flows | For PDP Contexts/EPS bearers used to carry IMS media flows, specific policies may be applied. The policy includes packet filtering, which enables a specific charging for these PDP Contexts/EPS bearers, see 3GPP TS 29.212[ Policy and Charging Control (PCC); Reference points ] [75]. The creation of a PDP Context/EPS bearer to be used to carry media flows involves interaction between the MS/UE and the GGSN/P-GW and between the GGSN/P-GW and the PCRF. The interaction between the GGSN/P-GW and the PCRF, i.e. the Gx interface, is described in detail in 3GPP TS 29.212[ Policy and Charging Control (PCC); Reference points ] [75]. The interaction between the MS/UE and GGSN/P-GW is described in 3GPP TS 29.213[ Policy and charging control signalling flows and Quality of Service (QoS) parameter mapping ] [76]. If Gx is enabled for the APN, the GGSN/P-GW contacts the PCRF selected during the establishment of the APN. | 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 | 13a.2.2.3 |
4,679 | Annex I (informative): Member UE selection without the NEF assistance at the AF | This informative Annex describes an example of the procedure that AF selects the FL members by collecting network exposure information in case that no NEF is present in the 5GS. In this example, QoS Monitoring is used for FL Member UE selection. Network exposure information as described in clause 4.15 of TS 23.502[ Procedures for the 5G System (5GS) ] [4], e.g. UE location reporting from the AMF, user plane information from the UPF and data analytics from NWDAF may be collected and used to assist the AF in application layer Member UE selection e.g. assist in the selection of Member UEs participating in a federating learning operation. Figure I-1: Example of Procedure for Member UE selection without the NEF assistance 1. [Optional] The AF requests the location reporting of the UEs from the AMF by invoking existing Namf_EventExposure_Subscribe (Location Reporting). 2. [Optional] The AF initiates direct notification of QoS Monitoring procedure for delay information for the UEs in the candidate list, as defined in steps 1a-5 of clause 6.4.2.1 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74]. 3. [Optional] The AF requests user plane information, e.g. Throughput UL/DL, Packet transmission, Packet retransmission, for the UEs in the candidate list from UPF. 4. [Optional] The AF requests analytics from NWDAF by invoking the Nnwdaf_AnalyticsSubscription_Subscribe service operation, such as UE Communication, User Data Congestion Analytics, WLAN performance analytics per UE, etc. as defined in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. NOTE 1: In Steps 1-4, the AF maintains the candidate list itself and collects the Member UE selection information directly from the 5GC and includes the Target UE Identifier(s) for the UEs in the candidate list in the request. 5. The AF selects members, e.g. for application layer Member UE selection for FL, based on the information collected in steps 1-4. NOTE 2: What information needs to be collected by the AF to perform Member UE selection is decided by the AF itself. NOTE 3: AF may keep monitoring the information from AMF/UPF/SMF/NWDAF to update the members. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | Annex |
4,680 | 8.10.2.2.4 Enhanced Downlink Control Channel Performance Requirement Type A - 4 Tx Antenna Port with Non-Colliding CRS Dominant Interferer | The purpose of this test is to verify the Enhanced Downlink Control Channel Performance Requirement Type A for PDCCH/PCFICH with 4 transmit antennas for the case of dominant interferer with the non-colliding CRS pattern and applying interference model defined in clause B.7.1. For the parameters specified in Table 8.10.2.2.4-1, the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.10.2.2.4-2. In Table 8.10.2.2.4-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, respectively. Table 8.10.2.2.4-1: Test Parameters for PDCCH/PCFICH Table 8.10.2.1.4-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.10.2.2.4 |
4,681 | G.1 Causes related to MS identification | Cause value = 2 IMSI unknown in HLR This cause is sent to the MS if the MS is not known (registered) in the HLR, or if the MS has packet only subscription (see 3GPP TS 29.272[ Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol ] [150]). This cause code does not affect operation of the GPRS service, although is may be used by a GMM procedure. Cause value = 3 Illegal MS This cause is sent to the MS when the network refuses service to the MS either because an identity of the MS is not acceptable to the network or because the MS does not pass the authentication check, i.e. the SRES received from the MS is different from that generated by the network. When used by an MM procedure, except the authentication procedure, this cause does not affect operation of the GPRS service. Cause value = 4 IMSI unknown in VLR This cause is sent to the MS when the given IMSI is not known at the VLR. Cause value = 5 IMEI not accepted This cause is sent to the MS if the network does not accept emergency call establishment using an IMEI or not accept attach procedure for emergency services using an IMEI. Cause value = 6 Illegal ME This cause is sent to the MS if the ME used is not acceptable to the network, e.g. prohibit listed When used by an MM procedure, this cause does not affect operation of the GPRS service. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | G.1 |
4,682 | 5.30.2.9.2 Credentials Holder using AAA Server for primary authentication and authorization | The AUSF and the UDM in SNPN may support primary authentication and authorization of UEs using credentials from a AAA Server in a Credentials Holder (CH). - Only NSI based SUPI is supported and the SUPI is used to identify the UE during primary authentication and authorization towards the AAA Server. SUPI privacy is achieved according to methods in clause I.5 of TS 33.501[ Security architecture and procedures for 5G System ] [29]. - The AMF discovers and selects the AUSF as described in clause 6.3.4 using the Home Network Identifier (realm part) and Routing Indicator present in the SUCI provided by a UE configured as described in clause 5.30.2.3. - The AMF selects the UDM in the same SNPN, based on local configuration (e.g. using the realm part of the SUCI), or using the NRF procedure defined in clause 4.17.4a of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. - If the UDM decides that the primary authentication is performed by AAA Server in CH based on the UE's SUPI and subscription data. The Home Network Identifier, is derived by UDM from the SUCI received from AUSF. If the SUCI was generated using a privacy protection scheme that requires de-concealment, UDM de-conceal the SUCI as defined in TS 33.501[ Security architecture and procedures for 5G System ] [29]. The UDM then instructs the AUSF that primary authentication by a AAA Server in a CH is required, the AUSF shall discover and select the NSSAAF, and then forward EAP messages to the NSSAAF. The NSSAAF selects AAA Server based on the domain name corresponds to the realm part of the SUPI, relays EAP messages between AUSF and AAA Server (or AAA proxy) and performs related protocol conversion. The AAA Server acts as the EAP Server for the purpose of primary authentication. NOTE 1: The UDM in SNPN, based on SLA between Credentials Holder and SNPN, is pre-configured with information indicating whether the UE needs primary authentication from AAA Server. NOTE 2: It is assumed that the SNPN is configured on per Home Network Identifier basis to determine whether to perform primary authentication with AUSF/UDM or AAA server. - The AMF and SMF shall retrieve the UE subscription data from UDM using SUPI. Figure 5.30.2.9.2-1 depicts the 5G System architecture for SNPN with Credentials Holder using AAA Server for primary authentication and authorization. NOTE 3: The SNPN in Figure 5.30.2.9.2-1 can be the subscribed SNPN for the UE (i.e. NG-RAN broadcasts SNPN ID of the subscribed SNPN). As a deployment option, the SNPN in Figure 5.30.2.9.2-1 can also be another SNPN than the subscribed SNPN for the UE (i.e. none of the SNPN IDs broadcast by NG-RAN matches the SNPN ID corresponding to the subscribed SNPN). In both cases, the AUSF, UDM and NSSAAF are configured to support the HNI of the UE's SUPI/SUCI, SUPI privacy settings (when using privacy protection scheme other than the 'null-scheme' to generate the SUCI as defined in TS 33.501[ Security architecture and procedures for 5G System ] [29]), subscription data of the UE and authentication settings to allow UE authentication with AAA-S in CH. Figure 5.30.2.9.2-1: 5G System architecture with access to SNPN using credentials from Credentials Holder using AAA Server NOTE 4: The NSSAAF deployed in the SNPN can support primary authentication in the SNPN using credentials from Credentials Holder using a AAA Server (as depicted) and/or the NSSAAF can support Network Slice-Specific Authentication and Authorization with a Network Slice-Specific AAA Server (not depicted). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.30.2.9.2 |
4,683 | 4.9.1.3.3 Execution phase | Figure 4.9.1.3.3-1: inter NG-RAN node N2 based handover, execution phase NOTE 1: Registration of serving AMF with the UDM is not shown in the figure for brevity. 1. S-AMF to S-RAN: Handover Command (Target to Source transparent container, List Of PDU Sessions to be handed-over with N2 SM information containing information received from T-RAN during the handover preparation phase, List Of PDU Sessions failed to be setup). Target to Source transparent container is forwarded as received from S-AMF. If DAPS Response information for one or more DRBs is received by S-RAN and indicates that DAPS handover is accepted, the execution phase for DAPS handover procedure as described in clause 4.9.1.3.3a is performed. The SM forwarding info list includes T-RAN SM N3 forwarding info list for direct forwarding or S-UPF SM N3 forwarding info list for indirect data forwarding S-RAN uses the PDU Sessions failed to be setup list and the indicated reason for failure to decide whether to proceed with the N2 Handover procedure. If the S-RAN supports and receives a reference to an Alternative QoS Profile for an accepted QoS Flow, it shall take it into account for deciding whether or not to proceed with the N2 Handover procedure (see TS 23.501[ System architecture for the 5G System (5GS) ] [2]). 2. S-RAN to UE: Handover Command (UE container). UE container is a UE part of the Target to Source transparent container which is sent transparently from T-RAN via AMF to S-RAN and is provided to the UE by the S-RAN. 2a0. If the PLMN has configured secondary RAT usage reporting and the source NG-RAN has Secondary RAT usage data to report, the source NG-RAN node may provide RAN usage data report message (N2 SM Information (Secondary RAT usage data), Handover Flag) as in clause 4.21 to the AMF. The Handover Flag indicates to the AMF that it should buffer the N2 SM Information containing the usage data report before forwarding it. NOTE 2: This step is not shown in this figure but the secondary RAT usage data reporting procedure is shown in figure 4.21-1 in clause 4.21. 2a. - 2c. The S-RAN sends the Uplink RAN Status Transfer message to the S-AMF, as specified in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [46] and TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [9]. The S-RAN may omit sending this message if none of the radio bearers of the UE shall be treated with PDCP status preservation. In the case of time-based handover, the S-RAN sends the Uplink RAN Early Status Transfer message to the S-AMF as specified in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10]. If there is an AMF relocation, the S-AMF sends this information to the T-AMF via the Namf_Communication_N1N2MessageTransfer service operation and the T-AMF acknowledges. The S-AMF or, if the AMF is relocated, the T-AMF, sends the information to the T-RAN via the Downlink RAN Status Transfer message, as specified in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [46] and TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [9]. In the case of time-based handover, the T-AMF sends the Downlink RAN Early Status Transfer message to the T-RAN as specified in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10]. For Inter PLMN handover, if the target AMF has been relocated in Preparation phase, e.g. due to the inter PLMN handover, the S-AMF send this information to the indicated T-AMF, which is derived from the target AMF ID received in step 12 of clause 4.9.1.3.2. 3. Uplink packets are sent from T-RAN to T-UPF and UPF (PSA). Downlink packets are sent from UPF (PSA) to S-RAN via S-UPF. The S-RAN should start forwarding of downlink data from the S-RAN towards the T-RAN for QoS Flows or DRBs subject to data forwarding. This may be either direct (step 3a) or indirect forwarding (step 3b). 4. UE to T-RAN: Handover Confirm. After the UE has successfully synchronized to the target cell, it sends a Handover Confirm message to the T-RAN. Handover is by this message considered as successful by the UE. 5. T-RAN to T-AMF: Handover Notify. Handover is by this message considered as successful in T-RAN. 6a. [Conditional] T-AMF to S-AMF: Namf_Communication_N2InfoNotify. The T-AMF notifies to the S-AMF about the N2 handover notify received from the T-RAN by invoking the Namf_Communication_N2InfoNotify. A timer in S-AMF is started to supervise when resources in S-RAN shall be release. 6b. [Conditional] S-AMF to T-AMF: Namf_Communication_N2InfoNotify ACK (N2 SM Information (Secondary RAT usage data)). The S-AMF acknowledges by sending the Namf_Communication_N2InfoNotify ACK to the T-AMF. The N2 SM Information here is the one buffered at step 2a0 when applicable. 6c. [Conditional] S-AMF to SMF: Nsmf_PDUSession_ReleaseSMContext Request (SM Context ID, N2 SM Information (Secondary RAT Usage Data)). If the PDU Session(s) is not accepted by the T-AMF (e.g. S-NSSAI associated with the PDU Session is not available in the T-AMF), S-AMF triggers PDU Session Release procedure as specified in clause 4.3.4.2 after the S-AMF is notified for the reception of N2 Handover Notify in step 6a. 7. T-AMF to SMF: Nsmf_PDUSession_UpdateSMContext Request (Handover Complete indication for PDU Session ID, UE presence in LADN service area, N2 SM Information (Secondary RAT usage data)). The N2 SM Information here is the one received at step 6b when applicable. Handover Complete indication is sent per each PDU Session to the corresponding SMF to indicate the success of the N2 Handover. When an Nsmf_PDUSession_UpdateSMContext Response message arrived too late during the handover preparation phase (see step 8 of clause 4.9.1.3.2), or the PDU Session with SMF involvement is not accepted by T-RAN, Nsmf_PDUSession_UpdateSMContext Request (SM Context ID, Operation Type) is sent to the corresponding SMF allowing the SMF to deallocate a possibly allocated N3 UP address and Tunnel ID of the selected UPF. A PDU Session handled by that SMF is considered deactivated and handover attempt is terminated for that PDU Session. In the case that the AMF determines that the PDU Session is related to a LADN then the AMF provides the "UE presence in LADN service area". If the AMF does not provide the "UE presence in LADN service area" indication and the SMF determines that the DNN corresponds to a LADN, then the SMF considers that the UE is OUT of the LADN service area. The SMF takes actions for the LADN PDU Session as defined in clause 5.6.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] based on the "UE presence in LADN service area" indication. For each QoS Flow for which the SMF has received a reference to the fulfilled Alternative QoS Profile in step 10 of clause 4.9.1.3.2, the SMF notifies the PCF and the UE as described in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 8a. [Conditional] SMF to T-UPF (intermediate): N4 Session Modification Request. If new T-UPF is inserted or an existing intermediate S-UPF is re-allocated, the SMF shall send N4 Session Modification Request indicating DL AN Tunnel Info of T-RAN to the T-UPF. 8b. [Conditional] T-UPF to SMF: N4 Session Modification Response. The T-UPF acknowledges by sending N4 Session Modification Response message to SMF. 9a. [Conditional] SMF to S-UPF (intermediate): N4 Session Modification Request. If UPF is not re-allocated, the SMF shall send N4 Session Modification Request indicating DL AN Tunnel Info of T-RAN to the S-UPF. 9b. [Conditional] S-UPF to SMF: N4 Session Modification Response. The S-UPF acknowledges by sending N4 Session Modification Response message to SMF. 10a. [Conditional] SMF to UPF (PSA): N4 Session Modification Request. For non-roaming or local breakout roaming scenario, the SMF sends N4 Session Modification Request message to PDU Session Anchor UPF, UPF (PSA), providing N3 AN Tunnel Info of T-RAN or the DL CN Tunnel Info of T-UPF if a new T-UPF is inserted or an existing intermediate S-UPF is re-allocated. If redundant transmission is performed for one or more QoS Flows of the PDU Session, two N3 AN Tunnel Info of T-RAN or two DL CN Tunnel Info of two T-UPFs are provided and the SMF indicates to the UPF (PSA) one of the AN/CN Tunnel Info is used as redundancy tunnel of the PDU Session. If the existing intermediate S-UPF terminating N9 toward the H-UPF (PDU Session Anchor) is re-allocated for the home routed roaming scenario, the V-SMF invokes an Nsmf_PDUSession_Update Request (DL CN Tunnel Info) service operation toward the H-SMF. In the case of the S-UPF acts as a UL CL or BP, the SMF indicates only one of the PDU Session Anchors to send the "end marker" packets. To ensure the "end marker" is the last user plane packet on the old path, the SMF should modify the path on other PDU Session Anchors before it indicates the PDU Session Anchor to send the "end marker" packets. If T-UPF is not inserted or an existing intermediate S-UPF is not re-allocated, step 10a and step 10b are skipped. 10b. [Conditional] UPF (PSA) to SMF: N4 Session Modification Response. The UPF (PSA) sends N4 Session Modification Response message to SMF. In order to assist the reordering function in the T-RAN, the UPF (PSA) sends one or more "end marker" packets for each N3 tunnel on the old path immediately after switching the path, the source NG-RAN shall forward the "end marker" packets to the Target NG-RAN. At this point, UPF (PSA) starts sending downlink packets to the T-RAN, via T-UPF if a new T-UPF is inserted or an existing intermediate S-UPF is re-allocated. In the case of home routed roaming scenario, the H-SMF responds with the Nsmf_PDUSession_Update Response service operation to V-SMF once the H-UPF (PDU Session Anchor) is updated with the UL Tunnel Info of the T-UPF. When there are multiple UPFs(PSA), step 10a and step 10b are performed for each UPFs(PSA). 11. SMF to T-AMF: Nsmf_PDUSession_UpdateSMContext Response (PDU Session ID). SMF confirms reception of Handover Complete. If indirect data forwarding applies, the SMF starts an indirect data forwarding timer, to be used to release the resource of indirect data forwarding tunnel. 12. The UE initiates Mobility Registration Update procedure as described in clause 4.2.2.2.2. The target AMF knows that it is a Handover procedure and therefore the target AMF performs only a subset of the Registration procedure, specifically the steps 4, 5 and 10 in the Registration procedure for the context transfer between source AMF and target AMF are skipped. The target AMF, based on the S-NSSAIs subject to Network Slice-Specific Authentication and Authorization status information from source AMF in step 3 of clause 4.9.1.3.2, may decide to skip step 25 in the Registration procedure (i.e. NSSAA procedure) or whether to perform it if the status is pending. 13a. [Conditional] SMF to S-UPF (intermediate): N4 Session Release Request. If there is a source intermediate UPF, the SMF initiates resource release, after timer in step 6 or indirect data forwarding timer expires, by sending an N4 Session Release Request (Release Cause) to source UPF. This message is also used to release the indirect data forwarding resource in S-UPF. 13b. S-UPF to SMF: N4 Session Release Response. The S-UPF acknowledges with an N4 Session Release Response message to confirm the release of resources. In the case of indirect data forwarding, the resource of indirect data forwarding is also released. 14a. AMF to S-RAN: UE Context Release Command (). After the timer in step 6a expires, the AMF sends UE Context Release Command. 14b. S-RAN to AMF: UE Context Release Complete (). The source NG-RAN releases its resources related to the UE and responds with a UE Context Release Complete () message. 15a. [Conditional] SMF to T-UPF: N4 Session Modification Request. If indirect forwarding applies and UPF is re-allocated, after timer of indirect data forwarding expires, the SMF sends N4 Session Modification Request to T-UPF to release the indirect data forwarding resource. 15b. [Conditional] T-UPF to SMF: N4 Session Modification Response. The T-UPF acknowledges with an N4 Session Modification Response message to confirm the release of indirect data forwarding resources. If the AMF is subscribed to Mobility Event by other NFs, the AMF notifies the event to the corresponding NFs by invoking the Namf_EventExposure_Notify service operation as described in clause 4.15.4.2. Upon reception of the Namf_EventExposure_Notify with an indication that UE is reachable only for regulatory prioritized service, the SMF deactivates the PDU Session if the service of the PDU Session is not regulatory prioritized. For home routed roaming case, the V-SMF triggers the deactivation of the PDU Session, in addition, the H-SMF refrains from sending downlink signalling if the signalling is not related to regulatory prioritized service upon receiving the notification. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.9.1.3.3 |
4,684 | 10.5.4.1 Extensions of codesets | There is a certain number of possible information element identifier values using the formatting rules described in subclause 10.5: 128 from the type 3 & 4 information element format and at least 8 from the type 1 & 2 information element format. One value in the type 1 format is specified for shift operations described below. One other value in both the type 3 & 4 and type 1 format is reserved. This leaves 133 information element identifier values available for assignment. It is possible to expand this structure to eight codesets of 133 information element identifier values each. One common value in the type 1 format is employed in each codeset to facilitate shifting from one codeset to another. The contents of this shift information element identifies the codeset to be used for the next information element or elements. The codeset in use at any given time is referred to as the "active codeset". By convention, codeset 0 is the initially active codeset. Two codeset shifting procedures are supported: locking shift and non-locking shift. Codeset 5 is reserved for information elements reserved for national use. Codeset 6 is reserved for information elements specific to the local network (either public or private). Codeset 7 is reserved for user-specific information elements. The coding rules specified in subclause 10.5 shall apply for information elements belonging to any active codeset. The mobile station and the network shall not apply the "comprehension required" scheme (see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20]) to information elements belonging to codesets different from codeset 0. IEIs with bits 5, 6, 7 and 8 all set to zero should not be allocated for new optional information elements in codesets different from codeset 0, because there are legacy mobile stations that apply the "comprehension required" scheme also to these information elements, e.g. if such a mobile station receives a SETUP message containing an unknown information element from codeset 5 with an IEI with bits 5, 6, 7 and 8 all set to zero, then the mobile station will release the call. Transitions from one active codeset to another (i.e. by means of the locking shift procedure) may only be made to a codeset with a higher numerical value than the codeset being left. An information element belonging to codeset 5, 6 or 7 may appear together with information elements belonging to codeset 0, by using the non-locking shift procedure (see subclause 10.5.4.3). A user or network equipment shall have the capability to recognize a shift information element and to determine the length of the following information element, although the equipment need not be able to interpret and act on the content of the information element. This enables the equipment to determine the start of the subsequent 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.1 |
4,685 | 10.5.3.2.2 Authentication Failure parameter (UMTS and EPS authentication challenge) | The purpose of the Authentication Failure parameter information element is to provide the network with the necessary information to begin a re-authentication procedure (see 3GPP TS 33.102[ 3G security; Security architecture ] [5a]) in the case of a 'Synch failure', following a UMTS or EPS authentication challenge. The Authentication Failure parameter IE is coded as shown in figure 10.5.76.2/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.90.2/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Authentication Failure parameter IE is a type 4 information element with a length of 16 octets. Figure 10.5.76.2/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Authentication Failure parameter information element (UMTS and EPS authentication challenge) Table 10.5.90.2/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Authentication Failure parameter information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.3.2.2 |
4,686 | 5.2.16.3 Nnssf_NSSAIAvailability service 5.2.16.3.1 General | Service description: This service enables to update the AMFs and the NSSF on the availability of S-NSSAIs and NSAGs on a per TA basis. This service also enables updates for Network Slice Replacement and Network Slice Instance Replacement to the NF Service Consumer (e.g. AMF or NSSF in the VPLMN) when the NSSF determines that an S-NSSAI has to be replaced with an Alternative S-NSSAI or a Network Slice instance is replaced as described in clause 5.15.19 [2]. NOTE: The NSSF can determine the serving network and Access Type from the TAI, as described in TS 29.571[ 5G System; Common Data Types for Service Based Interfaces; Stage 3 ] [70]. When this service is used by the NSSF for Network Slice Replacement, i.e. to provide to the NF Service Consumer an Alternative S-NSSAI to the S-NSSAI to be replaced, the following cases are possible: - in non-roaming and in roaming case, NSSF in the Serving PLMN provides to the AMF the Alternative S-NSSAI of the Serving PLMN; or - in roaming case, the NSSF in the HPLMN provides to the NSSF in the VPLMN the Alternative HPLMN S-NSSAI; and the NSSF in the VPLMN provides to the AMF the Alternative HPLMN S-NSSAI. Following NSSF event subscriptions are supported: - NSSAI availability status change; - Network Slice Replacement (see clause 5.15.19 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]); - Network Slice Instance Replacement (see clause 5.15.20 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") | 5.2.16.3 |
4,687 | Create Session Response | The Create Session Response message shall be sent on the S11/S4 interfaces by the SGW to the MME/S4-SGSN, on the S5/S8 interfaces by the PGW to the SGW, on the S2b interface by the PGW to the ePDG, and on the S2a interface by the PGW to the TWAN as part of the procedures listed for the Create Session Request (see clause 7.2.1). A PGW may receive the Create Session Response message sent from another PGW (see clause 7.2.1), the PGW shall forward the Create Session response message to the SGW as received from another PGW but with the following modifications: - the destination IP address and UDP port of the message shall be set to the source IP address and UDP port of the Create Session Request message received from the SGW; - the source IP address and UDP port of the message shall be set to the IP address and port of the forwarding PGW. In some network deployment, e.g. when 5G Network Slice is deployed and the combined PGW-C/SMFs are connected to the UDM, if the MME indicated in the Create Session Request that it supports PGW redirection due to mismatch with network slice subscribed by UE, the source PGW/SMF may select another PGW supporting the network slice for which the UE has a subscription and then reject the Create Session Request with the cause set to "PGW mismatch with network slice subscribed by the UE" and with the FQDN or IP address of the other PGW that the MME should use for establishing the PDN connection. NOTE: This can be used e.g. if there is no GTPv2/UDP/IP connectivity between PGW/SMFs pertaining to different network slices, or if the source PGW/SMF does not support forwarding the request to the target PGW/SMF as specified in clause 7.2.1. If handling of default bearer fails, then cause at the message level shall be a failure cause. Possible Cause values are specified in Table 8.4-1. Message specific cause values are: - "Request accepted". - "Request accepted partially". - "New PDN type due to network preference". - "New PDN type due to single address bearer only". - "Missing or unknown APN". - "GRE key not found". - "Preferred PDN type not supported". - "All dynamic addresses are occupied". - "Remote peer not responding". - "Semantic error in the TFT operation". - "Syntactic error in the TFT operation". - "Semantic errors in packet filter(s)". - "Syntactic errors in packet filter(s)". - "User authentication failed". - "APN access denied – no subscription". - "APN Restriction type incompatibility with currently active PDN Connection". - "Version not supported by next peer". - "Denied in RAT". - "Protocol type not supported". - "APN congestion". - "Multiple PDN connections for a given APN not allowed". - "Multiple accesses to a PDN connection not allowed". - "Context not found". - "UE not authorised by OCS or external AAA Server". - "PGW mismatch with network slice subscribed by the UE". Table -1: Information Elements in a Create Session Response Table -2: Bearer Context Created within Create Session Response Table -3: Bearer Context marked for removal within a Create Session Response Table 7.2.2-4: Load Control Information within Create Session Response Table 7.2.2-5: Overload Control Information within Create Session Response Table 7.2.2-6: PGW Change Info within Create Session Response | 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 | Create |
4,688 | 6.12.2 Requirements | The 5G network shall enable operators to support wireless self-backhaul using NR and E-UTRA. The 5G network shall support flexible and efficient wireless self-backhaul for both indoor and outdoor scenarios. The 5G network shall support flexible partitioning of radio resources between access and backhaul functions. The 5G network shall support autonomous configuration of access and wireless self-backhaul functions. The 5G network shall support multi-hop wireless self-backhauling. NOTE 1: This is to enable flexible extension of range and coverage area. The 5G network shall support autonomous adaptation on wireless self-backhaul network topologies to minimize service disruptions. The 5G network shall support topologically redundant connectivity on the wireless self-backhaul. NOTE 2: This is to enhance reliability and capacity and reduce end-to-end latency. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.12.2 |
4,689 | 8.13.1.4.1 Minimum Requirement Enhanced Performance Requirement Type A – Single-layer Spatial Multiplexing with TM9 interference model (User-Specific Reference Symbols) | The purpose of these tests is to verify closed loop rank one performance on one of the antenna ports 7 or 8 without a simultaneous transmission on the other antenna port in the serving cell when the PDSCH transmission in the serving cell is interfered by PDSCH of one dominant interfering cell applying transmission mode 9 interference model defined in clause B.5.4. In 8.13.1.4.1-1, Cell 1 is the serving cell, and Cell 2 is the interfering cell. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1 and Cell 2, respectively. For CA with 2 DL CCs, the requirements are specified in Table 8.13.1.4.1-3, based on single carrier requirement specified in Table 8.13.1.4.1-2, with the addition of the parameters in Table 8.13.1.4.1-1 and the downlink physical channel setup according to Annex C.3.2. Table 8.13.1.4.1-1: Test Parameters for Testing CDM-multiplexed DM RS (single layer) with TM9 interference model for CA Table 8.13.1.4.1-2: Single carrier performance for multiple CA configurations Enhanced Performance Requirement Type A, CDM-multiplexed DM RS Table 8.13.1.4.1-3: Minimum performance (FRC) based on single carrier performance for CA with 2 DL CCs | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.13.1.4.1 |
4,690 | 4.11.1.5.2 E-UTRAN Initial Attach | The E-UTRAN Initial Attach Procedure specified 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] is impacted as shown in Figure 4.11.1.5.2-1 when interworking with 5GS using N26 interface is supported. Figure 4.11.1.5.2-1: Impacts to E-UTRAN Initial Attach procedure 1. The UE sends an Attach Request message as specified in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] with the following modifications: - If the UE was previously registered in 5GS, the UE provides in Access Stratum signalling a GUMMEI mapped from the 5G-GUTI and indicates it as a native GUMMEI and should in addition indicate it as "Mapped from 5G-GUTI". - If the UE was previously registered in 5GS, the UE provides, in the Attach Request message, an EPS GUTI mapped from 5G-GUTI sent as old Native GUTI and indicates that it is moving from 5GC. The UE integrity protects the Attach Request message using the 5G security context. - A UE that supports 5GC NAS procedures shall indicate its support of 5G NAS as part of its UE Core Network Capability IE. - If the UE includes ESM message container for PDN Connection Establishment and the Request type is "initial request", the UE shall allocate a PDU Session ID and include it in the PCO. The PDU Session ID shall be unique across all other PDN connections of the UE. - MME may steer the UE from EPC by rejecting the Attach request with an appropriate cause value. If the UE supports any of the CIoT 5GS Optimisations included in 5GC Preferred Network Behaviour, then the UE shall include its 5GC Preferred Network Behaviour if it included its EPC Preferred Network Behaviour in the Attach request. The MME should take into account availability of 5GC to the UE and the Preferred and Supported Network Behaviour (see clause 5.31.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) before steering the UE from EPC. 2. The relevant steps of the procedure as specified in the figure above are executed with the following modification: - The HSS/UDM on receiving Update Location Request from MME, de-register any old AMF by sending an Nudm_UECM_DeregistrationNotification service operation to the registered AMF for 3GPP access. - Step 7 and step 10 as specified 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] (i.e. IP-CAN Session Termination) is replaced by SM Policy Association Termination procedure as specified in clause 4.16.6. - Step 14 as specified 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] (i.e. IP-CAN Session Establishment/Modification) are replaced by SM Policy Association Establishment/Modification procedure as specified in clause 4.16.4 and clause 4.16.5. 3. Step 15 as specified 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] with the following modification: - The SMF+PGW-C allocates 5G QoS parameters corresponding to PDN connection, e.g. Session AMBR, QoS rules and QoS Flow level QoS parameters if needed for the QoS Flow associated with the QoS rule(s) and then includes them in PCO. 4. The relevant steps of the procedure as specified in the figure above are executed. 5. Step 18 as specified 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] with the following modification: - The 5G QoS parameters for the PDU session and for the QoS Flow associated with the default QoS rule are stored in the UE. 6. The relevant steps of the procedure as specified in the figure above are executed. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.1.5.2 |
4,691 | 5.2.2.3.3 Call failure procedures | In case of abnormal behaviour the following call failure procedures apply: i. If the network does not receive any response to the SETUP message prior to the expiration of timer T303, then the network shall: initiate clearing procedures towards the calling user with cause #18 "no user responding"; and initiate clearing procedures towards the called mobile station in accordance with subclause 5.4.4 using cause #102 "recovery on timer expiry". ii. If the network has received a CALL CONFIRMED message, but does not receive an ALERTING, CONNECT or DISCONNECT message prior to the expiration of timer T310, then the network shall: - initiate clearing procedures towards the calling user with cause #18 "no user responding"; and - initiate clearing procedures towards the called MS in accordance with subclause 5.4.4 using cause #102 "recovery on timer expiry". iii. If the network has received an ALERTING message, but does not receive a CONNECT or DISCONNECT message prior to the expiry of timer T301 (or a corresponding internal alerting supervision timing function), then the network shall: initiate clearing procedures towards the calling user with cause #19 "user alerting, no answer"; and initiate clearing procedures towards the called mobile station in accordance with subclause 5.4.4, using cause #102 "recovery on timer expiry" or using cause #31 "normal, unspecified". NOTE: The choice between cause #31 and cause #102 may have consequences on indications generated by the mobile station, see 3GPP TS 22.001[ Principles of circuit telecommunication services supported by a Public Land Mobile Network (PLMN) ] [8a]. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.2.2.3.3 |
4,692 | B.2 Computation of CD for an IMEI | Computation of CD from the IMEI proceeds as follows: Step 1: Double the values of the odd labelled digits D1, D3, D5 ... D13 of the IMEI. Step 2: Add together the individual digits of all the seven numbers obtained in Step 1, and then add this sum to the sum of all the even labelled digits D2, D4, D6 ... D14 of the IMEI. Step 3: If the number obtained in Step 2 ends in 0, then set CD to be 0. If the number obtained in Step 2 does not end in 0, then set CD to be that number subtracted from the next higher number which does end in 0. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | B.2 |
4,693 | 9.1 Overview | Within the protocols defined in the present document, every message, except the SERVICE REQUEST message, is a standard L3 message as defined in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [12]. This means that the message consists of the following parts: 1) if the message is a plain NAS message: a) protocol discriminator; b) EPS bearer identity or security header type; c) procedure transaction identity; d) message type; e) other information elements, as required. 2) if the message is a security protected NAS message: a) protocol discriminator; b) security header type; c) message authentication code; d) sequence number; e) plain NAS message, as defined in item 1. The organization of a plain NAS message is illustrated in the example shown in figure 9.1.1. Figure 9.1.1: General message organization example for a plain NAS message The organization of a security protected NAS message is illustrated in the example shown in figure 9.1.2. Figure 9.1.2: General message organization example for a security protected NAS message The EPS bearer identity and the procedure transaction identity are only used in messages with protocol discriminator EPS session management. Octet 1a with the procedure transaction identity shall only be included in these messages. Unless specified otherwise in the message descriptions of clause 8, a particular information element shall not be present more than once in a given message. When a field extends over more than one octet, the order of bit values progressively decreases as the octet number increases. The most significant bit of the field is represented by the highest numbered bit of the lowest numbered octet of the field. The least significant bit of the field is represented by the lowest numbered bit of the highest numbered octet of the field. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.1 |
4,694 | 16.21 Multi-path Relay 16.21.1 General | In multi-path relay scenario, a MP Remote UE is connected to a single gNB via one direct path and one indirect path while the MP Remote UE is in RRC_CONNECTED state. For the indirect path, both L2 and L3 MP Relay architectures are supported. The L3 MP Relay architecture is transparent to the serving NG-RAN of the MP Relay UE, except for controlling sidelink resources. In the case of MP Remote UE using SL indirect path, mode 1 resource allocation is supported only for intra-DU case, with the SR/BSR and grant sent on the direct path. In multi-path relay, the interface between MP Remote UE and MP Relay UE can be either PC5 or N3C. When the interface between MP Remote UE and MP Relay UE is N3C interface, the relationship of MP Remote UE and MP Relay UE is pre-configured or static, and it is up to implementation how to pre-configure or make it static. Multi-path relay supports MP Remote UE and MP Relay UE when they are in the intra-gNB, and PCell is always on the direct path. Multi-path relay is supported in the following cell deployment scenarios: - The MP Relay UE and MP Remote UE are served by the same cell; - The MP Relay UE and MP Remote UE are served by different intra-frequency cells of the same gNB; - The MP Relay UE and MP Remote UE are served by different inter-frequency cells of the same gNB. Multi-path relay is supported in the following sidelink scenarios: - Sidelink TX/RX and Uu link share the same carrier at the MP Remote UE; - Sidelink TX/RX and Uu link use different carriers at the MP Remote UE; - Sidelink TX/RX and Uu link share the same carrier at the MP Relay UE; - Sidelink TX/RX and Uu link use different carriers at the MP Relay UE. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.21 |
4,695 | 9.9.1.3.2 TDD | The following requirements apply to UE Category ≥5. For the parameters specified in table 9.9.1.3.2-1, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2, the reported offset level of the wideband spatial differential CQI for codeword #1 (Table 7.2-2 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6]) shall be used to determine the wideband CQI index for codeword #1 as wideband CQI1 = wideband CQI0 – Codeword 1 offset level The wideband CQI1 shall be within the set {median CQI1 -1, median CQI1, median CQI1 +1} for more than 90% of the time, where the resulting wideband values CQI1 shall be used to determine the median CQI values for codeword #1. For both codewords #0 and #1, the PDSCH BLER using the transport format indicated by the respective median CQI0 – 1 and median CQI1 – 1 shall be less than or equal to 0.1. Furthermore, for both codewords #0 and #1, the PDSCH BLER using the transport format indicated by the respective median CQI0 + 1 and median CQI1 + 1 shall be greater than or equal to 0.1. Table 9.9.1.3.2-1: PUCCH 1-1 static test (TDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.9.1.3.2 |
4,696 | 6.7.2 NAS security mode command procedure | The NAS SMC shown in Figure 6.7.2-1 shall be used to establish NAS Security context between the UE and the AMF. This procedure consists of a roundtrip of messages between the AMF and the UE. The AMF sends the NAS Security Mode Command message to the UE and the UE replies with the NAS Security Mode Complete message. NOTE 1: The NAS SMC procedure is designed such that it protects the Registration Request against a man-in-the-middle attack where the attacker modifies the IEs containing the UE security capabilities provided by the UE in the Registration Request. It works as follows: if the method completes successfully, the UE is attached to the network knowing that no bidding down attack has happened. In case a bidding down attack was attempted, the verification of the NAS SMC will fail and the UE replies with a reject message meaning that the UE will not attach to the network. Figure 6.7.2-1: NAS Security Mode Command procedure 1a. The AMF activates the NAS integrity protection before sending the NAS Security Mode Command message. 1b. The AMF sends the NAS Security Mode Command message to the UE. The NAS Security Mode Command message shall contain: the replayed UE security capabilities, the selected NAS algorithms, and the ngKSI for identifying the KAMF. The NAS Security Mode Command message may contain: K_AMF_change_flag (carried in the additional 5G security parameters IE specified in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [35]) to indicate a new KAMF is calculated, a flag requesting the complete initial NAS message (see subclause 6.4.6), Anti-Bidding down Between Architectures (ABBA) parameter. In the case of horizontal derivation of KAMF during mobility registration update or during multiple registration in same PLMN, K_AMF_change_flag shall be included in the NAS Security Mode Command message as described in clause 6.9.3. This message shall be integrity protected (but not ciphered) with NAS integrity key based on the KAMF indicated by the ngKSI in the NAS Security Mode Command message (see Figure 6.7.2-1). NOTE 2: Void. In case the network supports interworking using the N26 interface between MME and AMF, the AMF shall also include the selected EPS NAS algorithms (defined in Annex B of TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10]) to be used after mobility to EPS in the NAS Security Mode Command message (see clause 8.5.2). The UE shall store the algorithms for use after mobility to EPS using the N26 interface between MME and AMF. The AMF shall store the selected EPS NAS algorithms in the UE security context. NOTE 2a: When AMF change happens either due to N2-handover or idle mode mobility, the selected EPS NAS algorithms is always included in the 5G UE security context and provided to the target AMF as part of the 5G UE security context. 1c. The AMF activates NAS uplink deciphering after sending the NAS Security Mode Command message. 2a. The UE shall verify the NAS Security Mode Command message. This includes checking that the UE security capabilities sent by the AMF match the ones stored in the UE to ensure that these were not modified by an attacker and verifying the integrity protection using the indicated NAS integrity algorithm and the NAS integrity key based on the KAMF indicated by the ngKSI. In case the NAS Security Mode Command message includes a K_AMF_change_flag, the UE shall derive a new KAMF as described in Annex A.13 and set the NAS COUNTs to zero. If the verification of the integrity of the NAS Security Mode Command message is successful, the UE shall start NAS integrity protection and ciphering/deciphering with the security context indicated by the ngKSI. 2b. The UE sends the NAS Security Mode Complete message to the AMF ciphered and integrity protected. The NAS Security Mode Complete message shall include PEI in case AMF requested it in the NAS Security Mode Command message. The AMF shall set the NAS COUNTs to zero if horizontal derivation of KAMF is performed. The UE may include the complete initial NAS message (see subclause 6.4.6 for details). If the verification of the NAS Security Mode Command message is not successful in the UE, it shall reply with a NAS Security Mode Reject message (see TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [35]). The NAS Security Mode Reject message and all subsequent NAS messages shall be protected with the previous, if any, 5G NAS security context, i.e., the 5G NAS security context used prior to the failed NAS Security Mode Command message. If no 5G NAS security context existed prior to the NAS Security Mode Command message, the NAS Security Mode Reject message shall remain unprotected. NOTE 2b: Void. The AMF shall de-cipher and check the integrity protection on the NAS Security Mode Complete message using the key and algorithm indicated in the NAS Security Mode Command message. NAS downlink ciphering at the AMF with this security context shall start after receiving the NAS Security Mode Complete message. 1d. The AMF activates NAS downlink ciphering. NOTE 3: If the uplink NAS COUNT will wrap around by sending the NAS Security Mode Reject message, the UE releases the NAS connection instead of sending the NAS Security Mode Reject message. NOTE 4: If the AMF successfully validated the NAS SMC Complete message, the AMF has successfully confirmed the SUPI received from the home network and the SUPI used by the UE match (as required in clause 5.5.3). However, integrity check failure of the NAS SMC Complete message at the AMF could have other causes than a mismatch of the SUPIs. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.7.2 |
4,697 | 6.1.3.3.3a Network initiated PDP Context Modification not accepted by the MS | Upon receipt of a MODIFY PDP CONTEXT REQUEST message, if the MS does not accept the new QoS due to resource reasons or the indicated LLC SAPI, the MS shall initiate the PDP context deactivation procedure for the PDP context - the reject cause IE value of the DEACTIVATE PDP CONTEXT REQUEST message shall indicate "QoS not accepted". The MS may reject the network initiated PDP context modification request by sending a MODIFY PDP CONTEXT REJECT message to the network. The message shall contain a cause code that typically indicates one of the following: # 41: semantic error in the TFT operation; # 42: syntactical error in the TFT operation; # 44: semantic errors in packet filter(s); # 45: syntactical errors in packet filter(s); # 48: request rejected, Bearer Control Mode violation; or # 95 - 111: protocol errors. The MS shall reply with a MODIFY PDP CONTEXT REJECT message with cause "request rejected, Bearer Control Mode violation", if the selected Bearer Control Mode is 'MS only' and the network requests to modify or delete a TFT If a TFT modification was requested and the network requests to modify or delete packet filters which were added by the MS, then the MODIFY PDP CONTEXT REJECT message shall be sent. The TFT in the request message is checked by the MS for different types of TFT IE errors as specified in subclause 6.1.3.3.4. Upon receipt of a MODIFY PDP CONTEXT REJECT message, the network shall stop timer T3386 and enter the state PDP-ACTIVE. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.1.3.3.3a |
4,698 | 4.15.4.5 Exposure of Events from UPF for UPF Data Collection 4.15.4.5.1 General | This clause contains the detailed description and the procedures for how the UPF event exposure service (see clause 5.2.26.2) is used for UPF data collection. The list of NF consumer which may receive UPF event notifications is defined in clause 5.8.2.17 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. To get exposure data from UPF, NF consumer may subscribe to the UPF directly or indirectly via SMF. This is further defined in clause 5.8.2.17 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The UPF event exposure events are described in clause 5.2.26.2. In this Release of the specification, the following events are used for UPF Data collection: - QoS Monitoring. This event provides QoS Flow performance information. - UserDataUsageMeasures. This event provides information of user data usage of the User PDU Session. - UserDataUsageTrends. This event provides statistics related to user data usage of the User PDU Session. A consumer of UPF event exposure can subscribe to QoS monitoring event via SMF only and UPF sends the QoS Flow Performance information directly to this consumer. For this event, the interaction between SMF and UPF is over PFCP (TS 29.244[ Interface between the Control Plane and the User Plane nodes ] [69]). TS 23.501[ System architecture for the 5G System (5GS) ] [2] describes the QoS parameters that can be measured by means of QoS monitoring and how to enable the measurements for QoS flows. When the Subscription request for QoS monitoring event indicates that it is for the QoS Flow associated with the default QoS rule, based on local configuration the subscription request may trigger SMF to enable QoS monitoring. NOTE 1: Packets from multiple applications may share the QoS Flow associated with the default QoS Rule which may diminish the relevance of some measurements like data rate. The subscription to QoS monitoring event can target the QoS flows bound to an application by including an Application Identifier. In this case, at subscription request and/or when the PCC rules change, SMF identifies the active PCC Rule that includes a DataCollection_ApplicationIdentifier matching that Application Identifier. SMF enables this consumer (e.g. NWDAF) to receive the QoS Monitoring reports enabled by that PCC Rule. The consumer may indicate that it can receive QoS Flow Performance information for the QoS Flow associated with the default QoS rule if there are no measurements available for the Application Identifier (that is, if no PCC rule is identified). In this case the SMF may instruct the UPF to perform QoS monitoring for the QoS Flow associated with the default QoS rule and include the Indication of QoS Flow associated with the default QoS Rule (see clause 5.8.2.18 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). The UPF will then include the Indication of QoS Flow associated with the default QoS Rule in the Nupf_EventExposure_Notify service operation when sending reports. Otherwise, the SMF may accept the request and indicate in the response that reporting will be activated when the measurements are enabled by a PCC rule or the SMF may reject the subscription request for that Application Identifier. NOTE 2: Extensive usage of QoS Monitoring has significant impact on load and signalling. A consumer of UPF event exposure such as NWDAF can subscribe to User Data Usage events directly to UPF or via SMF and UPF sends the event notifications directly to this consumer. For this event, the interaction between SMF and UPF is over SBI. For User Data Usage events, the subscription request may target specific service data flows (e.g. a specific application traffic) by including a traffic description (e.g. an Application Id). Else, the scope of the subscription is all the traffic in the PDU Session. The subscription request may indicate the granularity requested, that is whether the measurement reports should be provided per service data flow, application, or the whole PDU Session. If the event notification can be delayed, i.e. delay tolerant, Reporting suggestion information is included. The Reporting suggestion information includes Report urgency and Reporting time information. Reporting urgency information indicates whether this event report can be delay tolerant, i.e. the event report can be delayed. If the Reporting urgency information indicates "delay tolerant", the Reporting time is also provided, which defines the last valid reporting time and UPF shall report the detected event before the last valid time. Table 4.15.4.5.1-1: Input parameters in subscription to UPF event Exposure events | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.4.5 |
4,699 | – RRCResumeRequest1 | The RRCResumeRequest1 message is used to request the resumption of a suspended RRC connection or perform an RNA update. Signalling radio bearer: SRB0 RLC-SAP: TM Logical channel: CCCH1 Direction: UE to Network RRCResumeRequest1 message -- ASN1START -- TAG-RRCRESUMEREQUEST1-START RRCResumeRequest1 ::= SEQUENCE { rrcResumeRequest1 RRCResumeRequest1-IEs } RRCResumeRequest1-IEs ::= SEQUENCE { resumeIdentity I-RNTI-Value, resumeMAC-I BIT STRING (SIZE (16)), resumeCause ResumeCause, spare BIT STRING (SIZE (1)) } -- TAG-RRCRESUMEREQUEST1-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,700 | 6.1.4.1 Coordination between 5GSM and ESM with N26 interface | Interworking with EPS is supported for a PDU session, if the PDU session includes the mapped EPS bearer context(s) or has association(s) between QoS flow and mapped EPS bearer after inter-system change from S1 mode to N1 mode. The SMF shall not include any mapped EPS bearer contexts associated with a PDU session for LADN and with a PDU session which is a multi-homed IPv6 PDU session. If the UE receives any mapped EPS bearer context for a PDU session for LADN or for a multi-homed IPv6 PDU session, the UE may locally delete the mapped EPS bearer context. See coding of the Mapped EPS bearer contexts IE in subclause 9.11.4.8. In an MA PDU session, the UE shall have one set of the mapped EPS bearer contexts. The network can provide the set of the mapped EPS bearer contexts of the MA PDU session via either access of the MA PDU session. In an MA PDU session, the UE shall support modification or deletion via an access of a mapped EPS bearer context of the MA PDU session created via the same or the other access. Upon inter-system change from N1 mode to S1 mode, the UE shall create the default EPS bearer context and the dedicated EPS bearer context(s) based on the parameters of the mapped EPS bearer contexts or the associations between QoS flow and mapped EPS bearer in the PDU session, if available. The EPS bearer identity assigned for the QoS flow of the default QoS rule becomes the EPS bearer identity of the default bearer in the corresponding PDN connection. If there is no EPS bearer identity assigned to the QoS flow of the default QoS rule of a PDU session associated with 3GPP access, or if there is no corresponding mapped EPS bearer contexts associated with the EPS bearer identity assigned to the QoS flow of the default QoS rule of a PDU session associated with 3GPP access: a) the PDU session is not an MA PDU session established over both 3GPP access and non-3GPP access, the UE shall perform a local release of the PDU session; or b) the PDU session is an MA PDU session established over both 3GPP access and non-3GPP access, the UE shall perform a local release of the PDU session over 3GPP access and consider that the MA PDU session is established over non-3GPP access only. If there is no EPS bearer identity assigned to the QoS flow(s) of a PDU session associated with 3GPP access which is not associated with the default QoS rule, or if there is no corresponding mapped EPS bearer contexts associated with the EPS bearer identity assigned to the QoS flow of the non-default QoS rule of a PDU session associated with 3GPP access, unless the PDU session is an MA PDU session established over 3GPP access and over non-3GPP access, the UE shall locally delete the QoS rules and the QoS flow description(s). The UE uses the parameters from each PDU session for which interworking with EPS is supported to create corresponding default EPS bearer context and optionally dedicated EPS bearer context(s) as follows: a) the PDU session type of the PDU session shall be mapped to the PDN type of the default EPS bearer context as follows: 1) the PDN type shall be set to "non-IP" if the PDU session type is "Unstructured"; 2) the PDN type shall be set to "IPv4" if the PDU session type is "IPv4"; 3) the PDN type shall be set to "IPv6" if the PDU session type is "IPv6"; 4) the PDN type shall be set to "IPv4v6" if the PDU session type is "IPv4v6"; 5) the PDN type shall be set to "non-IP" if the PDU session type is "Ethernet", and the UE, the network or both of them do not support Ethernet PDN type in S1 mode; and 6) the PDN type shall be set to "Ethernet" if the PDU session type is "Ethernet" and the UE and the network support Ethernet PDN type in S1 mode; b) the PDU address of the PDU session shall be mapped to the PDN address of the default EPS bearer context as follows: 1) the PDN address of the default EPS bearer context is set to the PDU address of the PDU session, if the PDU session type is "IPv4", "IPv6" or "IPv4v6"; and 2) the PDN address of the default EPS bearer context is set to zero, if the PDU session type is "Ethernet" or "Unstructured"; c) the DNN of the PDU session shall be mapped to the APN of the default EPS bearer context, unless the PDU session is an emergency PDU session; d) the APN-AMBR and extended APN-AMBR received in the parameters of the default EPS bearer context of the mapped EPS bearer contexts shall be mapped to the APN-AMBR and extended APN-AMBR of the default EPS bearer context; e) for each PDU session in state PDU SESSION ACTIVE, PDU SESSION MODIFICATION PENDING or PDU SESSION INACTIVE PENDING: 1) if the UE is performing an inter-system change from N1 mode to WB-S1 mode, the UE shall set the state of the mapped EPS bearer context(s) to BEARER CONTEXT ACTIVE; or 2) if the UE is performing an inter-system change from N1 mode to NB-S1 mode, for the mapped EPS bearer context corresponding to the default EPS bearer, the UE shall set the state of the mapped EPS bearer context to BEARER CONTEXT ACTIVE. Additionally, if the UE is performing an inter-system change from WB-N1 mode to NB-S1 mode, for the mapped EPS bearer context corresponding to a dedicated EPS bearer, if any, the UE shall set the state of the mapped EPS bearer context to BEARER CONTEXT INACTIVE; and f) for any other PDU session the UE shall set the state of the mapped EPS bearer context(s) to BEARER CONTEXT INACTIVE. Additionally, for each mapped EPS bearer context or the association between QoS flow and mapped EPS bearer in the PDU session: a) the EPS bearer identity shall be set to the EPS bearer identity received in the mapped EPS bearer context, or the EPS bearer identity associated with the QoS flow; b) the EPS QoS parameters shall be set to the mapped EPS QoS parameters of the EPS bearer received in the mapped EPS bearer context, or the EPS QoS parameters associated with the QoS flow; c) the extended EPS QoS parameters shall be set to the mapped extended EPS QoS parameters of the EPS bearer received in the mapped EPS bearer context, or the extended EPS QoS parameters associated with the QoS flow; and d) the traffic flow template shall be set to the mapped traffic flow template of the EPS bearer received in the mapped EPS bearer context, or the stored traffic flow template associated with the QoS flow, if available. After inter-system change from N1 mode to S1 mode, the UE shall associate the PDU session identity, the S-NSSAI, and the session-AMBR with the default EPS bearer context, and for each EPS bearer context mapped from one or more QoS flows, associate the QoS rule(s) for the QoS flow(s) and the QoS flow description(s) for the QoS flow(s) with the EPS bearer context. If the PDU session is associated with the control plane only indication and supports interworking with EPS, after inter-system change from N1 mode to S1 mode, the UE shall associate the EPS bearer context(s) of the PDN connection corresponding to the PDU session with the control plane only indication. If the PDU session is associated with a PDU session pair ID, after inter-system change from N1 mode to S1 mode, the UE shall associate the default EPS bearer context of the PDN connection corresponding to the PDU session with the PDU session pair ID. If the PDU session is associated with an RSN, after inter-system change from N1 mode to S1 mode, the UE shall associate the default EPS bearer context of the PDN connection corresponding to the PDU session with the RSN. After inter-system change from N1 mode to S1 mode, the UE and the SMF shall maintain the PDU session type of the PDU session until the PDN connection corresponding to the PDU session is released if the UE supports non-IP PDN type and the PDU session type is "Ethernet" or "Unstructured". After inter-system change from N1 mode to S1 mode, the UE and the SMF shall maintain the following 5GSM attributions and capabilities associated with the PDU session until the PDN connection corresponding to the PDU session is released: a) the always-on PDU session indication; b) the maximum number of supported packet filters; c) the support of reflective QoS; d) the maximum data rate per UE for user-plane integrity protection supported by the UE for uplink and the maximum data rate per UE for user-plane integrity protection supported by the UE for downlink; e) the support of multi-homed IPv6 PDU session; and f) if the PDU session is an MA PDU session established over 3GPP access, the PDN connection of the default EPS bearer corresponding to the MA PDU session shall be considered as a user-plane resource of the MA PDU session. After inter-system change from N1 mode to S1 mode, the UE operating in single-registration mode in a network supporting N26 interface shall deem that the following features are supported by the network on the PDN connection corresponding to the PDU session: a) PS data off; and b) Local address in TFT. If there is a QoS flow used for IMS signalling, after inter-system change from N1 mode to S1 mode, the EPS bearer associated with the QoS flow for IMS signalling becomes the EPS bearer for IMS signalling. When the UE is provided with a new session-AMBR in the Protocol configuration options IE or Extended protocol configuration options IE in the MODIFY EPS BEARER CONTEXT REQUEST message, the UE shall discard the corresponding association and associate the new valuewith the default EPS bearer context. The network may provide the UE with one or more QoS rules by including either one QoS rules parameter, or one QoS rules with the length of two octets parameter, but not both, in the Protocol configuration options IE or Extended protocol configuration options IE in the MODIFY EPS BEARER CONTEXT REQUEST message. The network may provide the UE with one or more QoS flow descriptions corresponding to the EPS bearer context being modified, by including either one QoS flow descriptions parameter, or one QoS flow descriptions with the length of two octets parameter, but not both, in the Protocol configuration options IE or Extended protocol configuration options IE in the MODIFY EPS BEARER CONTEXT REQUEST message. When the UE is provided with one or more QoS flow descriptions or the EPS bearer identity of an existing QoS flow description is modified in the Protocol configuration options IE or Extended protocol configuration options IE in the MODIFY EPS BEARER CONTEXT REQUEST message, the UE shall check the EPS bearer identity included in the QoS flow description; and: a) if the EPS bearer identity corresponds to the EPS bearer context being modified or the EPS bearer identity is not included, the UE shall store the QoS flow description and all the associated QoS rules, if any, for the EPS bearer context being modified for use during inter-system change from S1 mode to N1 mode; and b) otherwise the UE shall locally delete the QoS flow description and all the associated QoS rules, if any, and include a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause parameter set to 5GSM cause #84 "syntactical error in the QoS operation" in the MODIFY EPS BEARER CONTEXT ACCEPT message. When the UE is provided with one or more QoS rules, or one or more QoS flow descriptions in the Protocol configuration options IE or Extended protocol configuration options IE in the MODIFY EPS BEARER CONTEXT REQUEST message, the UE shall process the QoS rules sequentially starting with the first QoS rule and shall process the QoS flow descriptions sequentially starting with the first QoS flow description. The UE shall check the QoS rules and QoS flow descriptions for different types of errors as follows: NOTE 1: If an error is detected in a QoS rule or a QoS flow description which requires sending a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause value, then the QoS rules parameter, the QoS rules with the length of two octets parameter, the QoS flow descriptions parameter and the QoS flow descriptions with the length of two octets parameter included in the Protocol configuration options IE or Extended protocol configuration options IE in the MODIFY EPS BEARER CONTEXT REQUEST message are discarded, if any. NOTE 2: If the EPS bearer context modification procedure is rejected, then the QoS rules parameter, the QoS rules with the length of two octets parameter, the QoS flow descriptions parameter and the QoS flow descriptions with the length of two octets parameter included in the Protocol configuration options IE or Extended protocol configuration options IE in the MODIFY EPS BEARER CONTEXT REQUEST message are discarded, if any. a) Semantic errors in QoS operations: 1) When the rule operation is "Modify existing QoS rule and add packet filters", "Modify existing QoS rule and replace all packet filters", "Modify existing QoS rule and delete packet filters" or "Modify existing QoS rule without modifying packet filters" on the default QoS rule and the DQR bit is set to "the QoS rule is not the default QoS rule". 2) When the rule operation is "Modify existing QoS rule and add packet filters", "Modify existing QoS rule and replace all packet filters", "Modify existing QoS rule and delete packet filters" or "Modify existing QoS rule without modifying packet filters" on a QoS rule which is not the default QoS rule and the DQR bit is set to "the QoS rule is the default QoS rule". 3) When the rule operation is "Create new QoS rule" and the DQR bit is set to "the QoS rule is the default QoS rule" when there's already a default QoS rule with different QoS rule identifier. 4) When the rule operation is "Delete existing QoS rule" on the default QoS rule. 5) When the rule operation is "Create new QoS rule", "Modify existing QoS rule and add packet filters", "Modify existing QoS rule and replace all packet filters", "Modify existing QoS rule and delete packet filters", or "Modify existing QoS rule without modifying packet filters" and two or more QoS rules associated with this PDU session would have identical precedence values. 6) When the rule operation is "Modify existing QoS rule and delete packet filters", the QoS rule is a QoS rule of a PDU session of IPv4, IPv6, IPv4v6 or Ethernet PDU session type, and the packet filter list in the resultant QoS rule is empty. 7) When the rule operation is "Create new QoS rule", and there is already an existing QoS rule with the same QoS rule identifier and the existing QoS rule is associated with a QoS flow description stored for the EPS bearer context being modified or the existing QoS rule is not associated with any QoS flow description. 8) When the rule operation is "Modify existing QoS rule and add packet filters", "Modify existing QoS rule and replace all packet filters", "Modify existing QoS rule and delete packet filters", or "Modify existing QoS rule without modifying packet filters" and there is no existing QoS rule with the same QoS rule identifier associated with a QoS flow description stored for the EPS bearer context being modified. 9) When the rule operation is "Delete existing QoS rule" and there is no existing QoS rule with the same QoS rule identifier associated with a QoS flow description stored for the EPS bearer context being modified. 10) When the flow description operation is "Create new QoS flow description" and there is already an existing QoS flow description with the same QoS flow identifier stored for the EPS bearer context being modified. 11) When the flow description operation is "Modify existing QoS flow description" and there is no existing QoS flow description with the same QoS flow identifier stored for the EPS bearer context being modified. 12) When the flow description operation is "Delete existing QoS flow description" and there is no existing QoS flow description with the same QoS flow identifier stored for the EPS bearer context being modified. 13) When the UE determines that: i) the default EPS bearer context is associated with one or more QoS flows but the default EPS bearer context is not associated with the default QoS rule. ii) a dedicated EPS bearer context is associated with one or more QoS flows but the dedicated EPS bearer context is associated with the default QoS rule. 14) When the rule operation is "Create new QoS rule" and there is already an existing QoS rule with the same QoS rule identifier associated with a QoS flow description stored for an EPS bearer context different from the EPS bearer context being modified and belonging to the same PDN connection as the EPS bearer context being modified. 15) When the flow description operation is "Create new QoS flow description", and there is already an existing QoS flow description with the same QoS flow identifier stored for an EPS bearer context different from the EPS bearer context being modified and belonging to the same PDN connection as the EPS bearer context being modified. 16) When the rule operation is "Create new QoS rule", "Modify existing QoS rule and add packet filters", "Modify existing QoS rule and replace all packet filters", "Modify existing QoS rule and delete packet filters", or "Modify existing QoS rule without modifying packet filters" and the resultant QoS rule is associated with a QoS flow description stored for an EPS bearer context different from the EPS bearer context being modified. 17) When the rule operation is "Create new QoS rule", the DQR bit is set to "the QoS rule is not the default QoS rule", the QoS rule is provided for a PDN connection of PDN type "non-IP" and there is locally available information associated with the PDN connection that is set to "Unstructured". 18) When the flow description operation is "Create new QoS flow description" or "Modify existing QoS flow description", the QFI associated with the QoS flow description is not the same as the QFI of the default QoS rule, the QoS flow description is provided for a PDN connection of PDN type "non-IP" and there is locally available information associated with the PDN connection that is set to "Unstructured". 19) When the rule operation is "Modify existing QoS rule and add packet filters", the "packet filter list" field contains a match-all packet filter, the resultant QoS rule is the default QoS rule and there is already an existing match-all packet filter associated with the default QoS rule. 20) When the rule operation is "Create new QoS rule" and the DQR bit is set to "the QoS rule is not the default QoS rule", or the rule operation is "Modify existing QoS rule and add packet filters" on a QoS rule which is not the default QoS rule or "Modify existing QoS rule and replace all packet filters" on a QoS rule which is not the default QoS rule, and one match-all packet filter is to be associated with the resultant QoS rule. In case 5, if the old QoS rule (i.e. the QoS rule that existed before the MODIFY EPS BEARER CONTEXT REQUEST message was received) is not the default QoS rule and the old QoS rule is associated with a QoS flow description stored for the EPS bearer context being modified, the UE shall not diagnose an error, shall further process the new request and, if it was processed successfully, shall delete the old QoS rule which has identical precedence value. Otherwise, the UE shall include a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause parameter set to 5GSM cause #83 "semantic error in the QoS operation" in the MODIFY EPS BEARER CONTEXT ACCEPT message. In case 6, if the QoS rule is not the default QoS rule, the UE shall delete the QoS rule. If the QoS rule is the default QoS rule, the UE shall include a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause parameter set to 5GSM cause #83 "semantic error in the QoS operation" in the MODIFY EPS BEARER CONTEXT ACCEPT message. In case 7, if the existing QoS rule is not the default QoS rule and the DQR bit of the new QoS rule is set to "the QoS rule is not the default QoS rule", the UE shall not diagnose an error, further process the create request and, if it was processed successfully, delete the old QoS rule (i.e. the QoS rule that existed when case 7 was detected). If the existing QoS rule is the default QoS rule or the DQR bit of the new QoS rule is set to "the QoS rule is the default QoS rule", the UE shall include a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause parameter set to 5GSM cause #83 "semantic error in the QoS operation" in the MODIFY EPS BEARER CONTEXT ACCEPT message. In case 9, the UE shall not diagnose an error, further process the delete request and, if it was processed successfully, consider the respective QoS rule as successfully deleted. In case 10, the UE shall not diagnose an error, further process the create request and, if it was processed successfully, delete the old QoS flow description (i.e. the QoS flow description that existed when case 10 was detected. In case 12, the UE shall not diagnose an error, further process the delete request and, if it was processed successfully, consider the respective QoS flow description as successfully deleted. Otherwise, the UE shall include a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause parameter set to 5GSM cause #83 "semantic error in the QoS operation" in the MODIFY EPS BEARER CONTEXT ACCEPT message. b) Syntactical errors in QoS operations: 1) When the rule operation is "Create new QoS rule", "Modify existing QoS rule and add packet filters", "Modify existing QoS rule and replace all packet filters" or "Modify existing QoS rule and delete packet filters", the packet filter list in the QoS rule is empty, and the QoS rule is provided for a PDN connection of PDN type IPv4, IPv6, IPv4v6 or Ethernet, or for a PDN connection of PDN type "non-IP" and there is locally available information associated with the PDN connection that is set to "Ethernet". 2) When the rule operation is "Delete existing QoS rule" or "Modify existing QoS rule without modifying packet filters" with a non-empty packet filter list in the QoS rule. 3) When the rule operation is "Modify existing QoS rule and delete packet filters" and the packet filter to be deleted does not exist in the original QoS rule. 4) Void. 5) When there are other types of syntactical errors in the coding of the QoS rules parameter, the QoS rules with the length of two octets parameter, the QoS flow descriptions parameter or the QoS flow descriptions with the length of two octets parameter, such as a mismatch between the number of packet filters subfield, and the number of packet filters in the packet filter list when the rule operation is "delete existing QoS rule" or "create new QoS rule", or the number of packet filters subfield is larger than the maximum possible number of packet filters in the packet filter list (i.e., there is no QoS rule precedence subfield included in the QoS rule IE), the QoS Rule Identifier is set to "no QoS rule identifier assigned" when the rule operation is not "delete existing QoS rule", or the QoS flow identifier is set to "no QoS flow identifier assigned" when the flow description operation is not "Delete existing QoS flow description". 6) When, the A) rule operation is "Create new QoS rule", "Modify existing QoS rule and add packet filters", "Modify existing QoS rule and replace all packet filters", "Modify existing QoS rule and delete packet filters" or "Modify existing QoS rule without modifying packet filters", the UE determines, by using the QoS rule’s QFI as the 5QI, that there is a resulting QoS rule for a GBR QoS flow (as described in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] table 5.7.4-1), and there is no QoS flow description with a QFI corresponding to the QFI of the resulting QoS rule. B) flow description operation is "Delete existing QoS flow description", and the UE determines, by using the QoS rule’s QFI as the 5QI, that there is a resulting QoS rule for a GBR QoS flow (as described in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] table 5.7.4-1) with a QFI corresponding to the QFI of the QoS flow description that is deleted (i.e. there is no associated QoS flow description with the same QFI). 7) When the flow description operation is "Create new QoS flow description" or "Modify existing QoS flow description", and the UE determines that there is a QoS flow description of a GBR QoS flow (as described in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] table 5.7.4-1) which lacks at least one of the mandatory parameters (i.e., GFBR uplink, GFBR downlink, MFBR uplink and MFBR downlink). If the QoS flow description does not include a 5QI, the UE determines this by using the QFI as the 5QI. 8) When the rule operation is "Create new QoS rule", "Modify existing QoS rule and add packet filters" or "Modify existing QoS rule and replace all packet filters" with a non-empty packet filter list in the QoS rule, and the DQR bit is set to "the QoS rule is the default QoS rule", the QoS rule is provided for a PDN connection of PDN type "non-IP" and there is locally available information associated with the PDN connection that is set to "Unstructured". In case 3 the UE shall not diagnose an error, further process the deletion request and, if no error according to items c and d was detected, consider the respective packet filter as successfully deleted. Otherwise the UE shall include a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause parameter set to 5GSM cause #84 "syntactical error in the QoS operation" in the MODIFY EPS BEARER CONTEXT ACCEPT message. NOTE 3: It is not considered an error if the UE determines that after processing all QoS operations on QoS rules and QoS flow descriptions there is a QoS flow description that is not associated with any QoS rule and the UE is not in NB-N1 mode. NOTE 3a: An implementation that strictly follows QoS rule operation as defined in subclause 9.11.4.13 might not detect case 2). 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. The UE shall include a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause parameter set to 5GSM cause #44 "semantic errors in packet filter(s)" in the MODIFY EPS BEARER CONTEXT ACCEPT message. d) Syntactical errors in packet filters: 1) When the rule operation is "Modify existing QoS rule and add packet filters" or "Modify existing QoS rule and replace all packet filters", and two or more packet filters in the resultant QoS rule would have identical packet filter identifiers. 2) When the rule operation is "Create new QoS rule", and two or more packet filters in the resultant QoS rule would have identical packet filter identifiers. 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. 4) Void. In case 1, if two or more packet filters with identical packet filter identifiers are contained in the MODIFY EPS BEARER CONTEXT REQUEST message, the UE shall include a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause parameter set to 5GSM cause #45 "syntactical error in packet filter(s)" in the MODIFY EPS BEARER CONTEXT ACCEPT message. Otherwise, the UE shall not diagnose an error, further process the MODIFY EPS BEARER CONTEXT REQUEST message and, if it was processed successfully, delete the old packet filters which have the identical packet filter identifiers. Otherwise the UE shall include a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause parameter set to 5GSM cause #45 "syntactical error in packet filter(s)" in the MODIFY EPS BEARER CONTEXT ACCEPT message. If the UE detects different errors in the QoS rules and QoS flow descriptions as described in this subclause which requires sending a 5GSM cause parameter in the MODIFY EPS BEARER CONTEXT ACCEPT message, the UE shall include a single 5GSM cause parameter in the MODIFY EPS BEARER CONTEXT ACCEPT message. NOTE 4: The 5GSM cause to use cannot be different from #44 "semantic error in packet filter(s)", #45 "syntactical errors in packet filter(s)", #83 "semantic error in the QoS operation" or #84 "syntactical error in the QoS operation". The selection of a 5GSM cause is up to UE implementation. Upon successful completion of an EPS attach procedure or tracking area updating procedure after inter-system change from N1 mode to S1 mode (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]), unless the PDU session is an MA PDU session established over 3GPP access and over non-3GPP access both connected to 5GCN, a) the UE shall delete any UE derived QoS rules of each PDU session which has been transferred to EPS; b) the UE and the SMF shall perform a local release of the PDU session(s) associated with 3GPP access which have not been transferred to EPS; and c) the UE and the SMF shall perform a local release of QoS flow(s) which have not been transferred to EPS, of the PDU session(s) which have been transferred to EPS. The UE and the SMF shall also perform a local release of any QoS flow description not associated with any QoS rule and not associated with any mapped EPS bearer context. If there is a QoS flow description not associated with any QoS rule, but associated with a mapped EPS bearer context, and after the inter-system change from N1 mode to S1 mode the respective EPS bearer context is active, then the UE shall associate the QoS flow description with the EPS bearer context. For PDU session(s) associated with non-3GPP access in 5GS, if present, the UE may: a) keep some or all of these PDU sessions still associated with non-3GPP access in 5GS, if supported; b) release some or all of these PDU sessions explicitly by initiating the UE requested PDU session release procedure(s); or c) attempt to transfer some or all of these PDU sessions from N1 mode to S1 mode by initiating the UE requested PDN connectivity procedure(s) with the PDN CONNECTIVITY REQUEST message created as follows: 1) if the PDU session is an emergency PDU session, the request type shall be set to "handover of emergency bearer services". Otherwise the request type shall be set to "handover"; 2) the PDU session type of the PDU session shall be mapped to the PDN type of the default EPS bearer context as follows: i) the PDN type shall be set to "non-IP" if the PDU session type is "Unstructured"; ii) the PDN type shall be set to "IPv4" if the PDU session type is "IPv4"; iii) the PDN type shall be set to "IPv6" if the PDU session type is "IPv6"; iv) the PDN type shall be set to "IPv4v6" if the PDU session type is "IPv4v6"; v) the PDN type shall be set to "non-IP" if the PDU session type is "Ethernet" and the UE, the network or both of them do not support Ethernet PDN type in S1 mode; and vi) the PDN type shall be set to "Ethernet" if the PDU session type is "Ethernet" and the UE and the network support Ethernet PDN type in S1 mode; 3) the DNN of the PDU session shall be mapped to the APN of the default EPS bearer context, unless the PDN connection is an emergency PDN connection; and 4) the PDU session ID parameter in the Protocol configuration options IE or the Extended protocol configuration options IE shall be set to the PDU session identity of the PDU session. If a PDU session associated with non-3GPP access is transferred to EPS, the UE shall associate the PDU session identity with the default EPS bearer context and shall delete any UE derived QoS rules of such PDU session. Interworking to 5GS is supported for a PDN connection, if the corresponding default EPS bearer context includes a PDU session identity, an S-NSSAI, if the PDN connection is a non-emergency PDN connection, session AMBR and one or more QoS flow descriptions received in the Protocol configuration options IE or Extended protocol configuration options IE (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]), or the default EPS bearer context has association with the PDU session identity, the S-NSSAI, if the PDU session is a non-emergency PDU session, the session-AMBR and one or more QoS flow descriptions after inter-system change from N1 mode to S1 mode. For a PDN connection established in S1 mode, to enable the UE to attempt to transfer the PDN connection from S1 mode to N1 mode in case of inter-system change, the UE shall allocate a PDU session identity, indicate the allocated PDU session identity in the PDU session ID parameter in the Protocol configuration options IE of the PDN CONNECTIVITY REQUEST message and associate the allocated PDU session identity with the default EPS bearer context of the PDN connection. If an N5CW device supporting 3GPP access establishes a new PDN connection in S1 mode, the N5CW device supporting 3GPP access shall refrain from allocating "PDU session identity value 15". For a PDN connection established in S1 mode, the SMF assigning the QoS rules shall consider that the UE supports 16 packet filters for the corresponding PDU session until the UE indicates a higher number (as specified in subclause 6.4.2.2). The network may provide the UE with one or more QoS rules by including either one QoS rules parameter, or one QoS rules with the length of two octets parameter, but not both, in the Protocol configuration options IE or Extended protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST or ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message. The network may provide the UE with one or more QoS flow descriptions corresponding to the EPS bearer context being activated, by including either one QoS flow descriptions parameter, or one QoS flow descriptions with the length of two octets parameter, but not both, in the Protocol configuration options IE or Extended protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST or ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message. When the UE is provided with one or more QoS flow descriptions in the Protocol configuration options IE or Extended protocol configuration options IE of the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST or ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, the UE shall check the EPS bearer identity included in the QoS flow description; and: a) if the EPS bearer identity corresponds to the EPS bearer context being activated or the EPS bearer identity is not included, the UE shall store the QoS flow description and all the associated QoS rules, if any, for the EPS bearer context being activated for use during inter-system change from S1 mode to N1 mode; and b) otherwise the UE shall locally delete the QoS flow description and all the associated QoS rules, if any, and include a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause parameter set to 5GSM cause #84 "syntactical error in the QoS operation" in the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT or ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message. When the UE is provided with one or more QoS rules, or one or more QoS flow descriptions in the Protocol configuration options IE or Extended protocol configuration options IE of the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST or ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, the UE shall process the QoS rules sequentially starting with the first QoS rule and shall process the QoS flow descriptions sequentially starting with the first QoS flow description. The UE shall check QoS rules and QoS flow descriptions for different types of errors as follows: NOTE 5: If an error is detected in a QoS rule or a QoS flow description which requires sending a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause value, then the QoS rules parameter, the QoS rules with the length of two octets parameter, the QoS flow descriptions parameter and the QoS flow descriptions with the length of two octets parameter included in the Protocol configuration options IE or Extended protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST or ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message are discarded, if any. NOTE 6: If the default EPS bearer context activation procedure or the dedicated EPS bearer context activation procedure is rejected, then the QoS rules parameter, the QoS rules with the length of two octets parameter, the QoS flow descriptions parameter and the QoS flow descriptions with the length of two octets parameter included in the Protocol configuration options IE or Extended protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST or ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message are discarded, if any. a) Semantic errors in QoS operations: 1) When the rule operation is "Create new QoS rule" and the DQR bit is set to "the QoS rule is the default QoS rule" when there's already a default QoS rule. 2) When the rule operation is received in an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message, the rule operation is "Create new QoS rule", and there is no rule with the DQR bit set to "the QoS rule is the default QoS rule". 3) When the rule operation is "Create new QoS rule" and two or more QoS rules associated with this PDU session would have identical precedence values. 4) When the rule operation is an operation other than "Create new QoS rule". 5) When the flow description operation is an operation other than "Create new QoS flow description". 6) When the UE determines that: i) the default EPS bearer context is associated with one or more QoS flows but the default EPS bearer context is not associated with the default QoS rules. ii) a dedicated EPS bearer context is associated with one or more QoS flows but the dedicated EPS bearer context is associated with the default QoS rule. 7) When the flow description operation is received in an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, the flow description operation is "Create new QoS flow description" and there is already an existing QoS flow description with the same QoS flow identifier stored for an EPS bearer context different from the EPS bearer context being activated and belonging to the same PDN connection as the EPS bearer context being activated. 8) When the rule operation is received in an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, the rule operation is "Create new QoS rule" and there is already an existing QoS rule with the same QoS rule identifier stored for an EPS bearer context different from the EPS bearer context being activated and belonging to the same PDN connection as the EPS bearer context being activated. 9) When the rule operation is received in an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, the rule operation is "Create new QoS rule" and the resultant QoS rule is associated with a QoS flow description stored for an EPS bearer context different from the EPS bearer context being activated and belonging to the same PDN connection as the EPS bearer context being activated. 10) When the rule operation is "Create new QoS rule" and the DQR bit is set to "the QoS rule is not the default QoS rule" and one match-all packet filter is to be associated with the QoS rule. 11) When the flow description operation is "Create new QoS flow description" and there is already an existing QoS flow description with the same QoS flow identifier stored for the EPS bearer context being activated. 12) When the rule operation is "Create new QoS rule", and there is already an existing QoS rule with the same QoS rule identifier and the existing QoS rule is associated with a QoS flow description stored for the EPS bearer context being activated or the existing QoS rule is not associated with any QoS flow description. In case 4, if the rule operation is for a non-default QoS rule, the UE shall delete the QoS rule. If the QoS rule is the default QoS rule, the UE shall include a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause parameter set to 5GSM cause #83 "semantic error in the QoS operation" in the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT or ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message. In case 11, the UE shall not diagnose an error, further process the create request and, if it was processed successfully, delete the old QoS flow description (i.e. the QoS flow description that existed when case 11 was detected). In case 12, if the existing QoS rule is not the default QoS rule and the DQR bit of the new QoS rule is set to "the QoS rule is not the default QoS rule", the UE shall not diagnose an error, further process the create request and, if it was processed successfully, delete the old QoS rule (i.e. the QoS rule that existed when case 12 was detected). If the existing QoS rule is the default QoS rule or the DQR bit of the new QoS rule is set to "the QoS rule is the default QoS rule", the UE shall include a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause parameter set to 5GSM cause #83 "semantic error in the QoS operation" in the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT or ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message. Otherwise for all the cases above, the UE shall include a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause parameter set to 5GSM cause #83 "semantic error in the QoS operation" in the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT or ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message. b) Syntactical errors in QoS operations: 1) When the rule operation is "Create new QoS rule", the packet filter list in the QoS rule is empty, and the QoS rule is provided for a PDN connection of PDN type IPv4, IPv6, IPv4v6 or Ethernet, or for a PDN connection of PDN type "non-IP" and there is locally available information associated with the PDN connection that is set to "Ethernet". 2) Void. 3) When there are other types of syntactical errors in the coding of the QoS rules parameter, the QoS rules with the length of two octets parameter, the QoS flow descriptions parameter or the QoS flow descriptions with the length of two octets parameter, such as a mismatch between the number of packet filters subfield, and the number of packet filters in the packet filter list when the rule operation is "delete existing QoS rule" or "create new QoS rule", or the number of packet filters subfield is larger than the maximum possible number of packet filters in the packet filter list (i.e., there is no QoS rule precedence subfield included in the QoS rule IE), the QoS Rule Identifier is set to "no QoS rule identifier assigned", or the QoS flow identifier is set to "no QoS flow identifier assigned. 4) When, the A) rule operation is "Create new QoS rule", the UE determines, by using the QoS rule’s QFI as the 5QI, that there is a resulting QoS rule for a GBR QoS flow (as described in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] table 5.7.4-1), and there is no QoS flow description with a QFI corresponding to the QFI of the resulting QoS rule. 5) When the flow description operation is "Create new QoS flow description", and the UE determines that there is a QoS flow description of a GBR QoS flow (as described in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] table 5.7.4-1) which lacks at least one of the mandatory parameters (i.e., GFBR uplink, GFBR downlink, MFBR uplink and MFBR downlink). If the QoS flow description does not include a 5QI, the UE determines this by using the QFI as the 5QI. The UE shall include a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause parameter set to 5GSM cause #84 "syntactical error in the QoS operation" in the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT or ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message. NOTE 7: It is not considered an error if the UE determines that after processing all QoS operations on QoS rules and QoS flow descriptions there is a QoS flow description that is not associated with any QoS rule and the UE is not in NB-N1 mode. 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. The UE shall include a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause parameter set to 5GSM cause #44 "semantic errors in packet filter(s)" in the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT or ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message. d) Syntactical errors in packet filters: 1) When the rule operation is "Create new QoS rule" and two or more packet filters in the resultant QoS rule would have identical packet filter identifiers. 2) 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. The UE shall delete the QoS rule and include a Protocol configuration options IE or Extended protocol configuration options IE with a 5GSM cause parameter set to 5GSM cause #45 "syntactical error in packet filter(s)" in the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT or ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message. If the UE detects different errors in the QoS rules and QoS flow descriptions as described in this subclause which requires sending a 5GSM cause parameter in the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT or ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message, the UE shall include a single 5GSM cause parameter in the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT or ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message. NOTE 8: The 5GSM cause to use cannot be different from #44 "semantic error in packet filter(s)", #45 "syntactical errors in packet filter(s)", #83 "semantic error in the QoS operation" or #84 "syntactical error in the QoS operation". The selection of a 5GSM cause is up to UE implementation. Upon inter-system change from S1 mode to N1 mode, the UE uses the parameters from the default EPS bearer context of each PDN connection for which interworking to 5GS is supported to create a corresponding PDU session associated with 3GPP access as follows, unless the PDN connection is a user-plane resource of an MA PDU session: a) the PDN type of the default EPS bearer context shall be mapped to the PDU session type of the PDU session as follows: 1) if the PDN type is "non-IP": - the PDU session type is set to the locally available information associated with the PDN connection (either "Ethernet" or "Unstructured"), if available; or - otherwise, the PDU session type is set to "Unstructured"; 2) if the PDN type is "IPv4" the PDU session type is set to "IPv4"; 3) if the PDN type is "IPv6", the PDU session type is set to "IPv6"; 4) if the PDN type is "IPv4v6", the PDU session type is set to "IPv4v6"; and 5) if the PDN type is "Ethernet", the PDU session type is "Ethernet"; b) the PDN address of the default EPS bearer context shall be mapped to PDU address of the PDU session, if the PDN type is "IPv4", "IPv6" or "IPv4v6"; c) the APN of the default EPS bearer context shall be mapped to the DNN of the PDU session, unless the PDN connection is an emergency PDN connection; d) for each default EPS bearer context in state BEARER CONTEXT ACTIVE the UE shall set the state of the mapped PDU session to PDU SESSION ACTIVE; and e) for any other default EPS bearer context the UE shall set the state of the mapped PDU session to PDU SESSION INACTIVE. Additionally, the UE shall set: a) the PDU session identity of the PDU session to the PDU session identity included by the UE in the Protocol configuration options IE or Extended protocol configuration options IE in the PDN CONNECTIVITY REQUEST message, or the PDU session identity associated with the default EPS bearer context; b) the S-NSSAI of the PDU session to the S-NSSAI included by the network in the Protocol configuration options IE or Extended protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER REQUEST message, or the S-NSSAI associated with the default EPS bearer context, if the PDN connection is a non-emergency PDN connection; c) the session-AMBR of the PDU session to the session-AMBR included by the network in the Protocol configuration options IE or Extended protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER REQUEST message or the MODIFY EPS BEARER CONTEXT REQUEST message, or the session-AMBR associated with the default EPS bearer context; d) the SSC mode of the PDU session to "SSC mode 1"; and e) the always-on PDU session indication to the always-on PDU session indication maintained in the UE, if any. Upon inter-system change from S1 mode to N1 mode, the UE shall locally release the PDN connection(s) for which interworking to 5GS is not supported. Upon inter-system change from S1 mode to N1 mode, for each PDN connection which is a user-plane resource of MA PDU session and for which interworking to 5GS is supported, the UE shall consider that the MA PDU session is established over 3GPP access and, unless the MA PDU session is established over non-3GPP access too, the UE shall set the session-AMBR of the PDU session to the session-AMBR included by the network in the Protocol configuration options IE or Extended protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER REQUEST message or the MODIFY EPS BEARER CONTEXT REQUEST message, or the session-AMBR associated with the default EPS bearer context of the PDN connection. Additionally, for each EPS bearer context of the PDN connection, the UE shall create QoS flow(s) each of which is associated with the QoS flow description received in the Protocol configuration options IE or Extended protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER REQUEST message, ACTIVATE DEDICATED EPS BEARER REQUEST message, or MODIFY EPS BEARER REQUEST message (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]), or the QoS flow description associated with EPS bearer context, unless: a) the PDU session is an MA PDU session which: 1) is established over non-3GPP access; and 2) has a PDN connection as a user-plane resource; and b) the QoS flow already exists over the non-3GPP access. Additionally, for each EPS bearer context of the PDN connection, the UE shall create QoS rules(s), if any, each of which is associated with the QoS rule received in the Protocol configuration options IE or Extended protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER REQUEST message, ACTIVATE DEDICATED EPS BEARER REQUEST message, or MODIFY EPS BEARER CONTEXT REQUEST message (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]), or the QoS rules associated with EPS bearer context, unless: a) the PDU session is an MA PDU session which: 1) is established over non-3GPP access; and 2) has a PDN connection as a user-plane resource; and b) the QoS rule already exists over the non-3GPP access. NOTE 9: For a QoS rule which does not exist over non-3GPP access, the UE does not create the QoS rule if the QoS rule is the default QoS rule, or the precedence value of the QoS rule equals to the precedence value of a QoS rule exists over the non-3GPP access. Additionally, for each PDU session which was created at inter-system change from S1 mode to N1 mode from a corresponding PDN connection of the "Ethernet" PDN type, the UE shall consider that Ethernet PDN type in S1 mode is supported by the network and the SMF shall consider that Ethernet PDN type in S1 mode is supported by the UE. The UE and the network shall locally release the PDN connection(s) and EPS bearer context(s) associated with the 3GPP access which have not been transferred to 5GS. After inter-system change from S1 mode to N1 mode, for each QoS flow mapped from an EPS bearer context the UE shall associate the EPS bearer identity, the EPS QoS parameters, the extended EPS QoS parameters, and the traffic flow template, if available, of the EPS bearer context with the QoS flow. After inter-system change from S1 mode to N1 mode, for each QoS flow of an MA PDU session which: a) is established over non-3GPP access; and b) has a PDN connection as a user-plane resource; such that the QoS flow was received in the Protocol configuration options IE or Extended protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER REQUEST message, ACTIVATE DEDICATED EPS BEARER REQUEST message, MODIFY EPS BEARER CONTEXT REQUEST message, (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]), or associated with EPS bearer context, the UE shall associate the EPS bearer identity, the EPS QoS parameters, the extended EPS QoS parameters, and the traffic flow template, if available, of the EPS bearer context with the QoS flow. If the EPS bearer context(s) of the PDN connection are associated with the control plane only indication, and the PDN connection supports interworking to 5GS, after inter-system change from S1 mode to N1 mode, the UE shall associate the PDU session corresponding to the PDN connection with the control plane only indication. If the default EPS bearer context of the PDN connection is associated with the PDU session pair ID, and the PDN connection supports interworking to 5GS, after inter-system change from S1 mode to N1 mode, the UE shall associate the PDU session corresponding to the PDN connection with the PDU session pair ID. If the default EPS bearer context of the PDN connection is associated with the RSN, and the PDN connection supports interworking to 5GS, after inter-system change from S1 mode to N1 mode, the UE shall associate the PDU session corresponding to the PDN connection with the RSN. If there is an EPS bearer used for IMS signalling, after inter-system change from S1 mode to N1 mode, the QoS flow of the default QoS rule in the corresponding PDU session is used for IMS signalling. For a PDN connection established when in S1 mode, upon an inter-system change from S1 mode to N1 mode, if a UE-requested PDU session modification procedure has not been successfully performed yet,the SMF shall determine the always-on PDU session indication as specified in subclause 6.3.2.2. When the UE is provided with one or more mapped EPS bearer contexts in the Mapped EPS bearer contexts IE of the PDU SESSION MODIFICATION COMMAND message, the UE shall process the mapped EPS bearer contexts sequentially starting with the first mapped EPS bearer context. When the UE is provided with a new EPS bearer identity, a new EPS QoS parameters, a new extended EPS QoS parameters, a new APN-AMBR or a new extended APN-AMBR in the Mapped EPS bearer context IE of the PDU SESSION MODIFICATION COMMAND message for a QoS flow, the UE shall discard the corresponding association(s) and associate the new value(s) with the QoS flow. When the UE is provided with a new traffic flow template in the Mapped EPS bearer contexts IE of the PDU SESSION MODIFICATION COMMAND message for a QoS flow, the UE shall check the traffic flow template for different types of TFT IE errors as specified in subclause 6.3.2.3. When a QoS flow is deleted, the associated EPS bearer context information that are mapped from the deleted QoS flow shall be deleted from the UE and the network if there is no other existing QoS flow associated with this EPS bearer context. When the EPS bearer identity of a QoS flow is deleted, the associated EPS bearer context information that are mapped from the deleted EPS bearer identity shall be deleted from the UE and the network if there is no other existing QoS flow associated with this EPS bearer context. When an EPS bearer is released, all the associated QoS flow descriptions and QoS rules that are mapped from the released EPS bearer shall be deleted from the UE and the network. NOTE 10: If T3584 is running or deactivated for the S-NSSAI and optionally the DNN combination, the UE is allowed to initate ESM procedures in EPS with or without APN corresponding to that DNN, and if the APN is congested in EPS, the MME can send a back-off timer for the APN to the UE as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]. Upon inter-system change from N1 mode to S1 mode, if the UE has any PDU sessions associated with one or more multicast MBS sessions, the UE shall locally leave the associated multicast MBS sessions and the network shall consider the UE as removed from the associated MBS sessions. For the case of handover of an existing PDU session from 3GPP access to non-3GPP access, - upon receipt of the PDU SESSION ESTABLISHMENT ACCEPT message, the UE locally deletes the EPS bearer identities for the PDU session, if any (see subclause 6.4.1.3); and - after successful handover, the network shall locally delete the EPS bearer identities for the PDU session, if any. | 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.1.4.1 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.