Abstract: A method of enhancing IP packet forwarding feature support after interworking is proposed. When a PDU session in 5GS is transferred to a PDN connection in EPS, the UE shall assume the feature is supported after inter-system change from 5GS to EPS. When a PDN connection is established in EPS, the network indicated that the feature is not supported, and the network provided 5GSM parameters for ESM/5GSM interworking for this PDN connection, then UE shall assume the feature is supported after inter-system change from EPS to 5GS, the UE shall also assume the feature is supported after inter-system change from 5GS back to EPS. The IP packet forwarding features include PS data off and local IP address in TFT.

Abstract: A user equipment (UE) in a mobile network is configured to establish a first packet data network (PDN) connection between the UE and an Internet Protocol Multimedia Service (IMS) network of the mobile network via a wireless local area network (WLAN) access point. The first PDN connection is for implementing a voice call. The UE determines that at least one of the UE or the mobile network fails to support Voice over New Radio (VoNR). Responsive to determining that at least one of the UE or the mobile network fails to support Voice over New Radio (VoNR), the UE prevents itself from establishing a connection with a first radio access network (RAN) of the mobile network.

Abstract: In a mobile cellular network, a mobile network operator (MNO) or other entity can specify whether a user equipment (UE) is to utilize either a concealed identifier (e.g., a subscription concealed identifier (SUCI)) calculated by a universal subscriber identity module (USIM) of a universal integrated circuit card (UICC) or a concealed identifier calculated by mobile equipment (ME) of the UE that is separate from the UICC and USIM. In the event that a USIM-calculated concealed identifier is specified for use but the USIM fails in generation of a concealed identifier, the UE can utilize one or more failure recovery procedures to attempt completion of attachment of the UE to the same network or a different network to help ensure that the UE does not remain attached to a network without access to services of the network due to authentication failure.

Abstract: A method of enhanced error handling for 5G QoS operations is proposed. A PDU session defines the association between the UE and the data network that provides a PDU connectivity service. Each PDU session is identified by a PDU session ID, and may include multiple QoS flows and QoS rules. Within a PDU session, there should be one and only one default QoS rule. The default QoS rule indication (DQR) and the QoS flow identifier (QFI) of a signaled QoS rule should not be changed. Two new 5G session management (5GSM) causes are defined: a semantic error in the QoS operation (cause value #83) and a syntactic error (cause value #84) in the QoS operation. The UE should check the QoS rule provided in a PDU session modification command message for different types of QoS rule errors.

Abstract: A method of enhancing IP packet forwarding feature support after interworking is proposed. When a PDU session in 5GS is transferred to a PDN connection in EPS, the UE shall assume the feature is supported after inter-system change from 5GS to EPS. When a PDN connection is established in EPS, the network indicated that the feature is not supported, and the network provided 5GSM parameters for ESM/5GSM interworking for this PDN connection, then UE shall assume the feature is supported after inter-system change from EPS to 5GS, the UE shall also assume the feature is supported after inter-system change from 5GS back to EPS. The IP packet forwarding features include PS data off and local IP address in TFT.

Abstract: A method of enhancing IP packet forwarding feature support after interworking is proposed. When a PDU session in 5GS is transferred to a PDN connection in EPS, the UE shall assume the feature is supported after inter-system change from 5GS to EPS. When a PDN connection is established in EPS, the network indicated that the feature is not supported, and the network provided 5GSM parameters for ESM/5GSM interworking for this PDN connection, then UE shall assume the feature is supported after inter-system change from EPS to 5GS, the UE shall also assume the feature is supported after inter-system change from 5GS back to EPS. The IP packet forwarding features include PS data off and local IP address in TFT.

Abstract: A user equipment (UE) determines that a protocol data unit (PDU) session comprises an adaptable PDU session. The UE determines whether a current energy mode of the UE comprises an energy-saving mode. In response to determining that the current energy mode of the UE comprises the energy-saving mode, the UE establishes the adaptable PDU session in a non-always-on mode; and in response to determining that the current energy mode of the UE does not comprise the energy-saving mode, the UE establishes the adaptable PDU session in an always-on mode. Further, the UE can initially establish a mode of a plurality of adaptable PDU sessions as the non-always-on mode, when connecting to a certain type of network.

Abstract: A method of supporting IMS signaling over EPS bearer or QoS flow upon inter-system change between EPS and 5GS is proposed. When inter-system change from 5GS to EPS occurs, a PDU session is converted to a PDN connection having multiple EPS bearers. The EPS bearer mapped from the QoS flow that is used for IMS signaling in 5GS is the EPS bearer for IMS signaling in EPS. When inter-system change from EPS to 5GS occurs, a PDN connection is converted to a PDU session having multiple QoS flows. The QoS flow that is associated with the default QoS rule is the QoS flow for IMS signaling in 5GS, regardless of which EPS bearer is used for IMS signaling in EPS.

Abstract: A method of managing default QoS rules for PDU session is proposed. A PDU session defines the association between the UE and the data network that provides a PDU connectivity service. Each PDU session is identified by a PDU session ID, and may include multiple QoS flows and QoS rules. There can be more than one QoS rule associated with the same QoS flow. A default QoS rule is required to be sent to the UE for every PDU session establishment and it is associated with a QoS flow. Within a PDU session, there should be one and only one default QoS rule. In one novel aspect, UE behavior and error handling for proper QoS rule management is defined for PDU session establishment and modification procedures to enforce the one and only one default QoS rule policy.

Abstract: A method of managing default QoS rules for PDU session is proposed. A PDU session defines the association between the UE and the data network that provides a PDU connectivity service. Each PDU session is identified by a PDU session ID, and may include multiple QoS flows and QoS rules. There can be more than one QoS rule associated with the same QoS flow. A default QoS rule is required to be sent to the UE for every PDU session establishment and it is associated with a QoS flow. Within a PDU session, there should be one and only one default QoS rule. In one novel aspect, UE behavior and error handling for proper QoS rule management is defined for PDU session establishment and modification procedures to enforce the one and only one default QoS rule policy.

Abstract: A method of enhanced error handling for 5G QoS operations is proposed. A PDU session defines the association between the UE and the data network that provides a PDU connectivity service. Each PDU session is identified by a PDU session ID, and may include multiple QoS flows and QoS rules. Within a PDU session, there should be one and only one default QoS rule. The default QoS rule indication (DQR) and the QoS flow identifier (QFI) of a signaled QoS rule should not be changed. Two new 5G session management (5GSM) causes are defined: a semantic error in the QoS operation (cause value #83) and a syntactic error (cause value #84) in the QoS operation. The UE should check the QoS rule provided in a PDU session modification command message for different types of QoS rule errors.

Abstract: A method of enhanced error handling for 5G QoS operations is proposed. A PDU session defines the association between the UE and the data network that provides a PDU connectivity service. Each PDU session is identified by a PDU session ID, and may include multiple QoS flows and QoS rules. Within a PDU session, there should be one and only one default QoS rule. The default QoS rule indication (DQR) and the QoS flow identifier (QFI) of a signaled QoS rule should not be changed. Two new 5G session management (5GSM) causes are defined: a semantic error in the QoS operation (cause value #83) and a syntactic error (cause value #84) in the QoS operation. The UE should check the QoS rule provided in a PDU session modification command message for different types of QoS rule errors.

Abstract: A method of defining ATtention (AT) commands for 5G session management operations is proposed. In one example, the AT command can be a set command for configuring a PDU session establishment procedure. Additional 5G parameters including PDU session ID, Single-Network Slice Selection Assistance Information (S-NSSAI), Service and Session Continuity (SSC) mode, access type, and Reflective QoS (RQ) indication are defined for AT command +CGDCONT to configure the PDU session. In another example, the AT command can be a read command for querying PDU session and QoS flow parameters. Additional 5G parameters including PDU session ID (PSI), QoS flow ID (QFI), S-NASSI, SSC mode, access type, and RQ timer are defined for AT command +CGCONTRDP or +CGSCONTRDP.

Abstract: A method of supporting IMS signaling over EPS bearer or QoS flow upon inter-system change between EPS and 5GS is proposed. When inter-system change from 5GS to EPS occurs, a PDU session is converted to a PDN connection having multiple EPS bearers. The EPS bearer mapped from the QoS flow that is used for IMS signaling in 5GS is the EPS bearer for IMS signaling in EPS. When inter-system change from EPS to 5GS occurs, a PDN connection is converted to a PDU session having multiple QoS flows. The QoS flow that is associated with the default QoS rule is the QoS flow for IMS signaling in 5GS, regardless of which EPS bearer is used for IMS signaling in EPS.

Abstract: A method of enhancing IP packet forwarding feature support after interworking is proposed. When a PDU session in 5GS is transferred to a PDN connection in EPS, the UE shall assume the feature is supported after inter-system change from 5GS to EPS. When a PDN connection is established in EPS, the network indicated that the feature is not supported, and the network provided 5GSM parameters for ESM/5GSM interworking for this PDN connection, then UE shall assume the feature is supported after inter-system change from EPS to 5GS, the UE shall also assume the feature is supported after inter-system change from 5GS back to EPS. The IP packet forwarding features include PS data off and local IP address in TFT.

Abstract: A method of enhanced error handling for 5G QoS operations is proposed. A PDU session defines the association between the UE and the data network that provides a PDU connectivity service. Each PDU session is identified by a PDU session ID, and may include multiple QoS flows and QoS rules. Within a PDU session, there should be one and only one default QoS rule. The default QoS rule indication (DQR) and the QoS flow identifier (QFI) of a signaled QoS rule should not be changed. Two new 5G session management (5GSM) causes are defined: a semantic error in the QoS operation (cause value #83) and a syntactic error (cause value #84) in the QoS operation. The UE should check the QoS rule provided in a PDU session modification command message for different types of QoS rule errors.

Abstract: A method of modifying PS_Data_Off status via a PDN connection modification procedure and interpreting network PS_Data_Off support feature is proposed. A UE modifies the PS data off status by using a bearer resource modification procedure. The UE receives a response to the modification request and monitors whether the response includes the 3GPP PS_Data_Off Support indication. In one embodiment, if the network does not provide the 3GPP PS_Data_Off Support Indication, the UE thinks that the network does not support PS data off feature regardless whether the network accept or reject the modification request. In another embodiment, if the network does not provide the 3GPP PS_Data_Off Support Indication, then UE thinks that the network supports PS data off feature if it accepts the modification request, and does not support PS data off feature if it rejects the modification request.

Abstract: A method of defining ATtention (AT) commands for 5G session management operations is proposed. In one example, the AT command can be a set command for configuring a PDU session establishment procedure. Additional 5G parameters including PDU session ID, Single-Network Slice Selection Assistance Information (S-NSSAI), Service and Session Continuity (SSC) mode, access type, and Reflective QoS (RQ) indication are defined for AT command +CGDCONT to configure the PDU session. In another example, the AT command can be a read command for querying PDU session and QoS flow parameters. Additional 5G parameters including PDU session ID (PSI), QoS flow ID (QFI), S-NASSI, SSC mode, access type, and RQ timer are defined for AT command +CGCONTRDP or +CGSCONTRDP.

Abstract: A method of managing default QoS rules for PDU session is proposed. A PDU session defines the association between the UE and the data network that provides a PDU connectivity service. Each PDU session is identified by a PDU session ID, and may include multiple QoS flows and QoS rules. There can be more than one QoS rule associated with the same QoS flow. A default QoS rule is required to be sent to the UE for every PDU session establishment and it is associated with a QoS flow. Within a PDU session, there should be one and only one default QoS rule. In one novel aspect, UE behavior and error handling for proper QoS rule management is defined for PDU session establishment and modification procedures to enforce the one and only one default QoS rule policy.

Abstract: A method of managing default QoS rules for PDU session is proposed. A PDU session defines the association between the UE and the data network that provides a PDU connectivity service. Each PDU session is identified by a PDU session ID, and may include multiple QoS flows and QoS rules. There can be more than one QoS rule associated with the same QoS flow. A default QoS rule is required to be sent to the UE for every PDU session establishment and it is associated with a QoS flow. Within a PDU session, there should be one and only one default QoS rule. In one novel aspect, UE behavior and error handling for proper QoS rule management is defined for PDU session establishment and modification procedures to enforce the one and only one default QoS rule policy.