Abstract:
Various examples and schemes pertaining to synchronization of quality of service (QoS) flows and rulesin mobile communications are described. An apparatus establishes one or more protocol data unit (PDU) sessions with a wireless network. The apparatus then transmits a message to the wireless network to result in synchronization of status of at least one or more aspects related to QoS rules or QoS flows with respect to the one or more PDU sessions.
Abstract:
A PDU session and QoS flow handling mechanism is proposed when a QoS flow of a PDU session does not have a mapping DRB after a handover or a service request procedure. If the QoS flow is associated with a default QoS rule, the UE can locally release the PDU session, initiate a PDU session release procedure, send a 5GSM status message with proper cause, or assume the PDU session is not reactivated. On the other hand, if the QoS flow is not associated with a default QoS rule, the UE can locally delete the QoS flow, delete the QoS flow by using a PDU session modification procedure, or send a 5GSM status message with proper cause.
Abstract:
A method can include receiving a non-access stratum (NAS) message for establishing or modifying a protocol data unit (PDU) session at a user equipment (UE) from a core network, determining whether there is a quality of service (QoS) flow description resulting from the establishment or modification of the PDU session that is associated with a guaranteed bit rate (GBR) QoS flow of the PDU session, and invalid, and when it is determined that there is the invalid QoS flow description associated with the GBR QoS flow of the PDU session, performing an error handling operation.
Abstract:
Various examples and schemes pertaining to error handling on missing configuration for inter-system change in mobile communications are described. An apparatus performs a protocol data unit (PDU) -related procedure with a wireless network. The apparatus detects whether there is an error in the PDU-related procedure and the apparatus handles the error in response to detecting the error in the PDU-related procedure.
Abstract:
Methods and apparatus are provided for inter-RAT bearer change for the 3GPP network. In one novel aspect, a bearer termination procedure is performed upon detecting one or more triggering events for the inter-RAT bearer modification. In one embodiment, the UE established the 4G EPS bearer. The UE successfully performs a bearer change from 4G to 3G. Subsequently, the UE detects missing mandatory parameters during inter-RAT bearer change from 3G to 2G in an idle state. The UE performs bearer termination by releasing the PDP context. In one embodiment, the PDP context is locally released. In other embodiments, the UE explicitly releases bearer using the PDP context deactivation procedure. The locally released procedure can be triggered by the UE, or by the network, or by both the UE and the network. The explicitly PDP context release procedure can be triggered by the UE, or by the network, or by both the UE and the network.
Abstract:
A method of handling QoS flow descriptions with invalid EPS bearer context is proposed. During an EPS bearer activation or modification procedure, a UE may receive an ePCO/PCO IE for creating a new QoS flow description or modifying an existing QoS flow description. if UE detects that the to be created/modified QoS flow descriptions are associated with invalid EPS bearer context, then UE does not create/modify the QoS flow descriptions. Instead, UE locally deletes the QoS flow descriptions provided by the network. In addition, UE indicates a 5GSM cause to the network via PCO/ePCO. As a result, when inter-system change from EPS to 5GS happens, UE no longer needs to handle the QoS flow descriptions with invalid EPS bearer context.
Abstract:
A method of handling mapped Evolved Packet System (EPS) bearer context for invalid QoS flow description is proposed. During a PDU session establishment procedure or a PDU session modification procedure, a UE may receive a mapped EPS bearer context IE for creating a new mapped EPS bearer of a PDU session. If there is no corresponding QoS flow description associated to the new mapped EPS bearer, e.g., if there is no corresponding authorized QoS flow description IE in the PDU session establishment accept message or in the PDU session modification command message, then the UE should send another PDU session modification request message to the network to delete the new mapped EPS bearer context.
Abstract:
A method of 5G session management (5GSM) state mapping is proposed when interworking. For each PDU session in 5GSM state of PDU session active, PDU session modification pending, or PDU session inactive pending, UE maps the PDU session to a PDN connection in 4G ESM state bearer context active. For any other PDU session in 5GSM state of PDU session inactive, or PDU session active pending, UE maps the PDU session to a PDN connection in 4G ESM state bearer context inactive.
Abstract:
A method for Procedure Transaction Identity (PTI) exception handling on protocol data unit (PDU) session modification and establishment procedure is proposed. If a UE receives a PDU SESSION MODIFICATION COMMAND message in which the PTI value is an assigned value that does not match any PTI in use, the UE stays in the current 5GSM state and sends a 5GSM STATUS message including 5GSM cause #47 "PTI mismatch", and the network will send another COMMAND message with the correct PTI value. If the UE receives a PDU SESSION ESTABLISHMENT ACCEPT or REJECT message in which the PTI value is an assigned value that does not match any PTI in use, the UE responds with a 5GSM STATUS message including 5GSM cause #47 "PTI mismatch", and the network will send another ACCEPT or REJECT message with the correct PTI value.
Abstract:
A method of handling mapped EPS bearer context with duplicate EPS bearer ID (EBI) for 5GS to EPS inter-system change enhancement is proposed. UE is provided with a mapped EPS bearer context IE by the network to create a new mapped EPS bearer associated with a PDU session. UE detects collision of the new mapped EPS bearer –it has the same EBI as an existing EPS bearer. Upon successfully process the create request, UE either replaces the existing EPS bearer with the new mapped EPS bearer, or deletes the EPS bearer with duplicate EBI by explicit signaling to the network. As a result, when inter-system change from 5G to EPS happens, there is no EPS collision.