Methods and apparatus of handling user data when PDU session is inactive in mobile communications
By using cause-indicating messages and local session management, the synchronization issue of inactive PDU sessions in mobile communications is resolved, ensuring efficient user data handling and network alignment.
Patent Information
- Application Number
- PCT/CN2026/089321
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-09-04
- Filing Date
- 2026-04-08
- Publication Date
- 2026-11-12
AI Technical Summary
In mobile communications, when a PDU session is inactive, existing technologies fail to synchronize user data handling between the UE and the network, leading to unsynchronized states and rejection by the network, particularly in cases of unknown or inactive PDU session identities.
Implementing schemes in UE and network apparatuses to handle PDU sessions by transmitting and receiving messages with appropriate causes, such as 5GMM cause #90 or 5GSM cause #43, to indicate inactive sessions, and performing local releases or registration procedures to align UE and network states.
Ensures synchronized handling of user data by aligning UE and network states, preventing unsynchronized conditions and network rejections, thereby maintaining communication efficiency.
Smart Images

Figure CN2026089321_12112026_PF_FP_ABST
Abstract
Description
METHODS AND APPARATUS OF HANDLING USER DATA WHEN PDU SESSION IS INACTIVE IN MOBILE COMMUNICATIONSCROSS REFERENCE TO RELATED PATENT APPLICATION (S)
[0001] The present disclosure claims the priority benefit of India Patent Application Nos. 202521044713 and 202521084239, filed 08 May 2025 and 04 September 2025, respectively, the contents of which herein being incorporated by reference in their entirety.TECHNICAL FIELD
[0002] The present disclosure is generally related to mobile communications and, more particularly, to handling of user data when a protocol data unit (PDU) session is inactive in mobile communications.BACKGROUND
[0003] In wireless communications such as mobile communications under the current 3rd Generation Partnership Project (3GPP) specification, the purpose of the transport of user data via a control plane procedure is to transfer the user data via the control plane in an encapsulated form between a user equipment (UE) and a Mobility Management Entity (MME) of a network. The procedure may be initiated by the UE or the network when the UE is in an Evolved Packet System (EPS) Mobility Management (EMM) connected (EMM-CONNECTED) mode. The procedure may also be initiated by the UE in an EMM idle (EMM-IDLE) mode or while in EMM-IDLE mode with a suspend indication, by including an EPS Session Management (ESM) DATA TRANSPORT message in a CONTROL PLANE SERVICE REQUEST message. However, when the EPS bearer identity provided in the ESM DATA TRANSPORT message indicates an EPS bearer identity value which does not belong to any already-activated EPS bearer context, then network handling is not clearly defined in the 3GPP specifications regarding whether a user data container is to be handled or discarded. Consequently, the UE and network would be unsynchronized when the EPS bearer identity value is activated in UE but not in network.
[0004] With respect to abnormal cases on the network side, if the Payload container type information element (IE) is set to "CIoT user data container" and: (1) if the Access and Mobility Management Function (AMF) of the network does not have a PDU session routing context for the PDU session identification (ID) and the UE; or (2) if the AMF unsuccessfully attempted to forward the user data container and the PDU session ID, then the AMF may send back to the UE the Cellular Internet of Things (CIoT) user data container which was not forwarded as specified in subclause 5.4.5.3.1 case l1 of the 3GPP technical specification (TS) , which pertains to a single uplink CIoT user data container or control plane user data which was not forwarded due to routing failure.
[0005] With respect to a network-initiated non-access stratum (NAS) transport of messages accepted by the UE, in case that the 5th Generation (5G) Mobility Management (5GMM) cause IE is set to the 5GMM cause #22 "Congestion" , the UE passes to the 5G Session Management (5GSM) sublayer an indication that the CIoT user data was not forwarded due to data network name (DNN) -based congestion control along with the CIoT user data from the Payload container IE of the DL NAS TRANSPORT message, and the time value from the Back-off timer value IE. Alternatively, in case that the 5GMM cause IE is set to the 5GMM cause #67 "insufficient resources for specific slice and DNN" , the UE passes to the 5GSM sublayer an indication that the CIoT user data was not forwarded due to single network slice selection assistance information (S-NSSAI) and DNN-based congestion control along with the CIoT user data from the Payload container IE of the DL NAS TRANSPORT message, and the time value from the Back-off timer value IE. Alternatively, in case that the 5GMM cause IE is set to the 5GMM cause #69 "insufficient resources for specific slice" , the UE passes to the 5GSM sublayer an indication that the CIoT user data was not forwarded due to S-NSSAI only based congestion control along with the CIoT user data from the Payload container IE of the downlink (DL) NAS TRANSPORT message, and the time value from the Back-off timer value IE. Alternatively, in case that the 5GMM cause IE is set to the 5GMM cause #90 "payload was not forwarded" , the UE passes to the 5GSM sublayer an indication that the user data container was not forwarded due to routing failure along with the user data container from the Payload container IE and the PDU session ID from the PDU session ID IE of the DL NAS TRANSPORT message.
[0006] With respect to PDU session identity, upon receipt of an uplink (UL) NAS TRANSPORT message, If the Request type IE is set to "initial request" or "initial emergency request" and the message includes a reserved PDU session identity value, the network is to respond with a DL NAS TRANSPORT message with 5GMM cause #90 "payload was not forwarded" . Otherwise, if the message includes an unassigned or reserved PDU session identity value, the network is to respond with a DL NAS TRANSPORT message with 5GMM cause #90 "payload was not forwarded" .
[0007] When the UE sends an UL NAS TRANSPORT message to the network and the Payload container type IE is set to "CIoT user data container" and the message includes an unassigned or reserved PDU session identity value or PDU session identity is active in network, then the network sends a DL NAS TRANSPORT message with 5GMM cause #90 "payload was not forwarded" . However, as the UE would not perform actions, the UE would be unsynchronized with the network (e.g., resulting in the PDU session identity being inactive at UE and inactive at network) . Due to being unsynchronized, the UE would always be reject by the network with a 5GMM cause #90 for a same PDU session identity.
[0008] Therefore, there is a need for a solution of handling of user data when a PDU session is inactive in mobile communications.SUMMARY
[0009] The following summary is illustrative only and is not intended to be limiting in any way. That is, the following summary is provided to introduce concepts, highlights, benefits, and advantages of the novel and non-obvious techniques described herein. Select implementations are further described below in the detailed description. Thus, the following summary is not intended to identify essential features of the claimed subject matter, nor is it intended for use in determining the scope of the claimed subject matter.
[0010] An objective of the present disclosure is to propose solutions or schemes that address the issue (s) described herein. More specifically, various schemes proposed in the present disclosure are believed to provide solutions pertaining to handling of user data when a PDU session is inactive in mobile communications. It is believed that implementations of one or more of the schemes proposed herein may address or otherwise alleviate the issues described above.
[0011] In one aspect, a method may involve a UE transmitting, to a network, an uplink (UL) message with a PDU session identity of a PDU session that is inactive in the network. The method may also involve the UE, responsive to the transmitting, receiving, from the network, a downlink (DL) message with a cause indicating that a payload was not forwarded.
[0012] In another aspect, a method may involve a network receiving, from a UE, an UL message with a PDU session identity of a PDU session that is inactive in the network. The method may also involve the network, responsive to the receiving, transmitting, to the UE, a DL message with a cause indicating that a payload was not forwarded.
[0013] In another aspect, an apparatus implementable in a UE may include a transceiver configured to communicate wirelessly and a processor coupled to the transceiver. The processor may transmit, to a network, an UL message with a PDU session identity of a PDU session that is inactive in the network. The processor may also, responsive to the transmitting, receive, from the network, a DL message with a cause indicating that a payload was not forwarded.
[0014] It is noteworthy that, although the description provided herein may be in the context of certain radio access technologies, networks, and network topologies such as 5th Generation (5G) New Radio (NR) / Beyond Fifth-Generation (B5G) / 6th Generation (6G) mobile communications, the proposed concepts, schemes and any variation (s) / derivative (s) thereof may be implemented in, for and by other types of radio access technologies, networks and network topologies such as, for example and without limitation, 4th Generation (4G) / Long-Term Evolution (LTE) , LTE-Advanced, LTE-Advanced Pro, Internet-of-Things (IoT) , Narrow Band Internet of Things (NB-IoT) , Industrial Internet of Things (IIoT) , vehicle-to-everything (V2X) , and non-terrestrial network (NTN) communications. Thus, the scope of the present disclosure is not limited to the examples described herein.BRIEF DESCRIPTION OF THE DRAWINGS
[0015] The accompanying drawings are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of the present disclosure. The drawings illustrate implementations of the disclosure and, together with the description, serve to explain the principles of the disclosure. It is appreciable that the drawings are not necessarily in scale as some components may be shown to be out of proportion than the size in actual implementation in order to clearly illustrate the concept of the present disclosure.
[0016] FIG. 1 is a diagram of an example network environment in which various solutions and schemes in accordance with the present disclosure may be implemented.
[0017] FIG. 2 is a block diagram of an example communication system under a proposed scheme in accordance with the present disclosure.
[0018] FIG. 3 is a flowchart of an example process under a proposed scheme in accordance with the present disclosure.
[0019] FIG. 4 is a flowchart of an example process under a proposed scheme in accordance with the present disclosure. DETAILED DESCRIPTION OF PREFERRED IMPLEMENTATIONS
[0020] Detailed embodiments and implementations of the claimed subject matters are disclosed herein. However, it shall be understood that the disclosed embodiments and implementations are merely illustrative of the claimed subject matters which may be embodied in various forms. The present disclosure may, however, be embodied in many different forms and should not be construed as limited to the exemplary embodiments and implementations set forth herein. Rather, these exemplary embodiments and implementations are provided so that description of the present disclosure is thorough and complete and will fully convey the scope of the present disclosure to those skilled in the art. In the description below, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations. Overview
[0021] Implementations in accordance with the present disclosure relate to various techniques, methods, schemes and / or solutions pertaining to handling of user data when a PDU session is inactive in mobile communications. According to the present disclosure, a number of possible solutions may be implemented separately or jointly. That is, although these possible solutions may be described below separately, two or more of these possible solutions may be implemented in one combination or another.
[0022] FIG. 1 illustrates an example network environment 100 in which various solutions and schemes in accordance with the present disclosure may be implemented. FIG. 2 ~ FIG. 4 illustrate examples of implementation of various proposed schemes in network environment 100 in accordance with the present disclosure. The following description of various proposed schemes is provided with reference to FIG. 1 ~ FIG. 4.
[0023] Referring to FIG. 1, network environment 100 involves a UE 110 in wireless communication with a wireless network 120 (e.g., a mobile network including an NTN and a TN) via a terrestrial network node 125 (e.g., an evolved Node-B (eNB) , a Next Generation Node-B (gNB) , or a transmission / reception point (TRP) ) and / or a non-terrestrial network node 128 (e.g., a satellite) . For example, the terrestrial network node 125 and / or the non-terrestrial network node 128 may form a non-terrestrial network (NTN) serving cell for wireless communication with the UE 110. In some implementations, the UE 110 may be an IoT device such as an NB-IoT UE or an enhanced machine-type communication (eMTC) UE (e.g., a bandwidth reduced low complexity (BL) UE or a coverage enhancement (CE) UE) . In such communication environment, the UE 110, the network 120, the terrestrial network node 125, and the non-terrestrial network node 128 may implement various schemes pertaining to handling of user data when a PDU session is inactive in accordance with the present disclosure, as described below. It is noteworthy that, while the various proposed schemes may be individually or separately described below, in actual implementations some or all of the proposed schemes may be utilized or otherwise implemented jointly. Of course, each of the proposed schemes may be utilized or otherwise implemented individually or separately.
[0024] Under a proposed scheme in accordance with the present disclosure, in a 4G mobile communication system, when a network (e.g., network 120) receives an ESM DATA TRANSPORT message and / or when the ESM DATA TRANSPORT message indicates an EPS bearer identity value which does not belong to any already-activated EPS bearer context, then the network may perform one or more operations described below. For instance, the network may discard the ESM DATA TRANSPORT message and / or discard the user data container. Alternatively, or additionally, the network may send an ESM status message with a new cause or existing cause (e.g., #43 indicating "invalid EPS bearer identity" ) . Alternatively, or additionally, the network may send an ESM DATA TRANSPORT message or other ESM messages to indicate that the EPS bearer context is deactivated in an EPS bearer context status IE or in a new IE. After receiving the new cause or an existing cause, the UE may stop any related timer. Moreover, the UE may locally release the PDU session indicated in the message from network.
[0025] As an implementational example with respect to unknown EPS bearer context in a 4G mobile communication system, if the EPS bearer identity provided in the ESM DATA TRANSPORT message indicates an EPS bearer identity value which does not belong to any already-activated EPS bearer context, the MME of the network may discard the user data container and reply with an ESM STATUS message with an ESM cause #43 indicating "invalid EPS bearer identity" .
[0026] Under a proposed scheme in accordance with the present disclosure, in a 5G, 6G or next-generation mobile communication system, when the network receives an UL NAS TRANSPORT message and / or when the UL NAS TRANSPORT message is received with a Payload container type IE set to "CIoT user data container" for a PDU session that is inactive in the network, then network may perform one or more operation described below. For instance, the network may discard the UL NAS TRANSPORT message and / or discard the user data container. Alternatively, or additionally, the network may send a 5GSM status message with a new cause or existing cause (e.g., #43 indicating "Invalid PDU session identity" ) . Alternatively, or additionally, the network may send a DL NAS TRANSPORT message or other 5GSM / 5GMM messages to indicate that the PDU session is released in a PDU session status IE or in a new IE. Alternatively, or additionally, the network may send back to a UE (e.g., UE 110) the CIoT user data container which was not forwarded with a new cause or an existing cause (e.g., #43 indicating "Invalid PDU session identity" or cause #90 indicating "payload was not forwarded" ) . After receiving the new cause or an existing cause, the UE may stop any related timer. Moreover, the UE may locally release the PDU session indicated in the message from network.
[0027] As an implementational example with respect to abnormal cases on the network side regarding CIoT user data received for a PDU session ID which is inactive in the network in a 5G or 6G mobile communication system, if an UL NAS TRANSPORT message is received with a Payload container type IE set to "CIoT user data container" for a PDU session that is inactive in the network, the AMF of the network may discard the CIoT user data container. Moreover, the AMF may send to the UE a 5GSM STATUS message with a 5GSM cause #43 indicating “Invalid PDU session identity” .
[0028] As an implementational example with respect to 5GSM status received in the UE, if the 5GSM entity of the UE receives a 5GSM STATUS message, the UE may take different actions depending on the received 5GSM cause value. For instance, if the 5GSM STATUS message includes a cause #43 ( “Invalid PDU session identity” ) , the UE may abort any ongoing 5GSM procedure related to the received PDU session ID, stop any related timer, and locally release a PDU session that is indicated in the 5GSM STATUS message.
[0029] As an implementational example with respect to handling an unknown, erroneous or unforeseen PDU session identity received in the header of a 5GSM message from the UE, if the 5GSM message includes an unassigned PDU session identity value, a reserved PDU session identity value or an assigned PDU session identity value that does not match an existing PDU session, the network may respond to the UE with a DL NAS TRANSPORT message with a 5GMM cause #90 indicating “payload was not forwarded” .
[0030] Under a proposed scheme in accordance with the present disclosure, when: (a) a UE (e.g., UE 110) sends an UL NAS TRANSPORT message to a network (e.g., network 120) and / or (b) a Payload container type IE in the UL NAS TRANSPORT message is set to "CIoT user data container" (e.g., as the UE is sending control plane user data) and / or (c) the UL NAS TRANSPORT message includes an unassigned PDU session identity value or reserved PDU session identity value or PDU session identity value of PDU session that is inactive in the network, then the UE and the network may perform one or more operations described below. For instance, the UE may release an allocated procedure transaction identity (PTI) and / or perform a local release of a PDU session and / or perform a registration procedure for mobility and periodic registration update by sending a REGISTRATION REQUEST message including a PDU session status IE. Alternatively, or additionally, the network may respond to the UE with a 5GSM STATUS message with a 5GSM cause #43 indicating "invalid PDU session identity" and / or ignore a CIoT user data container received in the UL NAS TRANSPORT message and / or include a PDU session status IE in a DL NAS TRANSPORT message that the network sends to the UE.
[0031] As an implementational example with respect to PDU session identity, if a Payload container type IE in a message is set to "CIoT user data container" and the message includes a PDU session ID of a PDU session that is in a 5GSM state of PDU SESSION INACTIVE state in the network or an unassigned or reserved PDU session identity value, the network may respond to the UE with a 5GSM STATUS message with a 5GSM cause #43 indicating "invalid PDU session identity" .
[0032] As an implementational example with respect to abnormal cases in the UE, upon receiving an indication from the network that a CIoT user data container was not forwarded due to routing failure along with a PDU session ID IE being set to the same value as the PDU session ID that was sent by the UE, the UE may release the allocated PTI, perform a local release of the PDU session, and / or perform a registration procedure for mobility and periodic registration update by sending a REGISTRATION REQUEST message to the network including the PDU session status IE over each access that user plane resources have been established.
[0033] As an implementational example with respect to abnormal cases on the network side, if a Payload container type IE in a message is set to "CIoT user data container" and the message includes a PDU session ID of the PDU session that is in 5GSM state PDU SESSION INACTIVE state in the network or an unassigned or reserved PDU session identity value, then the AMF of the network may ignore the CIoT user data container and may respond to the UE with a 5GSM STATUS message with a 5GSM cause #43 indicating "invalid PDU session identity" . Illustrative Implementations
[0034] FIG. 2 illustrates an example communication system 200 having at least an example apparatus 210 and an example apparatus 220 in accordance with an implementation of the present disclosure. Each of apparatus 210 and apparatus 220 may perform various functions to implement schemes, techniques, processes and methods described herein pertaining to handling of user data when a PDU session is inactive in mobile communications, including the various schemes described above with respect to various proposed designs, concepts, schemes, systems and methods described above, including network environment 100, as well as processes described below.
[0035] Each of apparatus 210 and apparatus 220 may be a part of an electronic apparatus, which may be a network apparatus or a UE (e.g., UE 110) , such as a portable or mobile apparatus, a wearable apparatus, a vehicular device or a vehicle, a wireless communication apparatus or a computing apparatus. For instance, each of apparatus 210 and apparatus 220 may be implemented in a smartphone, a smart watch, a personal digital assistant, an electronic control unit (ECU) in a vehicle, a digital camera, or a computing equipment such as a tablet computer, a laptop computer or a notebook computer. Each of apparatus 210 and apparatus 220 may also be a part of a machine type apparatus, which may be an IoT apparatus such as an immobile or a stationary apparatus, a home apparatus, a roadside unit (RSU) , a wire communication apparatus or a computing apparatus. For instance, each of apparatus 210 and apparatus 220 may be implemented in a smart thermostat, a smart fridge, a smart door lock, a wireless speaker or a home control center. When implemented in or as a network apparatus, apparatus 210 and / or apparatus 220 may be implemented in an eNB in an LTE, LTE-Advanced or LTE-Advanced Pro network or in a gNB or TRP in a 5G network, an NR network, or an IoT network.
[0036] In some implementations, each of apparatus 210 and apparatus 220 may be implemented in the form of one or more integrated-circuit (IC) chips such as, for example and without limitation, one or more single-core processors, one or more multi-core processors, one or more complex-instruction-set-computing (CISC) processors, or one or more reduced-instruction-set-computing (RISC) processors. In the various schemes described above, each of apparatus 210 and apparatus 220 may be implemented in or as a network apparatus or a UE. Each of apparatus 210 and apparatus 220 may include at least some of those components shown in FIG. 2 such as a processor 212 and a processor 222, respectively, for example. Each of apparatus 210 and apparatus 220 may further include one or more other components not pertinent to the proposed scheme of the present disclosure (e.g., internal power supply, display device and / or user interface device) , and, thus, such component (s) of apparatus 210 and apparatus 220 are neither shown in FIG. 2 nor described below in the interest of simplicity and brevity.
[0037] In one aspect, each of processor 212 and processor 222 may be implemented in the form of one or more single-core processors, one or more multi-core processors, or one or more CISC or RISC processors. That is, even though a singular term “a processor” is used herein to refer to processor 212 and processor 222, each of processor 212 and processor 222 may include multiple processors in some implementations and a single processor in other implementations in accordance with the present disclosure. In another aspect, each of processor 212 and processor 222 may be implemented in the form of hardware (and, optionally, firmware) with electronic components including, for example and without limitation, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors and / or one or more varactors that are configured and arranged to achieve specific purposes in accordance with the present disclosure. In other words, in at least some implementations, each of processor 212 and processor 222 is a special-purpose machine specifically designed, arranged, and configured to perform specific tasks including those pertaining to handling of user data when a PDU session is inactive in mobile communications in accordance with various implementations of the present disclosure.
[0038] In some implementations, apparatus 210 may also include a transceiver 216 coupled to processor 212. Transceiver 216 may be capable of wirelessly transmitting and receiving data. In some implementations, transceiver 216 may be capable of wirelessly communicating with different types of wireless networks of different radio access technologies (RATs) . In some implementations, transceiver 216 may be equipped with a plurality of antenna ports (not shown) such as, for example, four antenna ports. That is, transceiver 216 may be equipped with multiple transmit antennas and multiple receive antennas for multiple-input multiple-output (MIMO) wireless communications. In some implementations, apparatus 220 may also include a transceiver 226 coupled to processor 222. Transceiver 226 may include a transceiver capable of wirelessly transmitting and receiving data. In some implementations, transceiver 226 may be capable of wirelessly communicating with different types of UEs / wireless networks of different RATs. In some implementations, transceiver 226 may be equipped with a plurality of antenna ports (not shown) such as, for example, four antenna ports. That is, transceiver 226 may be equipped with multiple transmit antennas and multiple receive antennas for MIMO wireless communications.
[0039] In some implementations, apparatus 210 may further include a memory 214 coupled to processor 212 and capable of being accessed by processor 212 and storing data therein. In some implementations, apparatus 220 may further include a memory 224 coupled to processor 222 and capable of being accessed by processor 222 and storing data therein. Each of memory 214 and memory 224 may include a type of random-access memory (RAM) such as dynamic RAM (DRAM) , static RAM (SRAM) , thyristor RAM (T-RAM) and / or zero-capacitor RAM (Z-RAM) . Alternatively, or additionally, each of memory 214 and memory 224 may include a type of read-only memory (ROM) such as mask ROM, programmable ROM (PROM) , erasable programmable ROM (EPROM) and / or electrically erasable programmable ROM (EEPROM) . Alternatively, or additionally, each of memory 214 and memory 224 may include a type of non-volatile random-access memory (NVRAM) such as flash memory, solid-state memory, ferroelectric RAM (FeRAM) , magnetoresistive RAM (MRAM) and / or phase-change memory.
[0040] Each of apparatus 210 and apparatus 220 may be a communication entity capable of communicating with each other using various proposed schemes in accordance with the present disclosure. For illustrative purposes and without limitation, a description of capabilities of apparatus 210, as a UE (e.g., UE 110) , and apparatus 220, as a network node (e.g., network node 125) of a network (e.g., wireless network 120 as a 4G, 5G / NR, 6G or next-generation mobile network) , is provided below in the context of example processes 300 and 400. Illustrative Processes
[0041] FIG. 3 illustrates an example process 300 in accordance with an implementation of the present disclosure. Process 300 may represent an aspect of implementing various proposed designs, concepts, schemes, systems and methods described above. More specifically, process 300 may represent an aspect of the proposed concepts and schemes pertaining to handling of user data when a PDU session is inactive in mobile communications in accordance with the present disclosure. Process 300 may include one or more operations, actions, or functions as illustrated by one or more of blocks 310 and 320. Although illustrated as discrete blocks, various blocks of process 300 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks / sub-blocks of process 300 may be executed in the order shown in FIG. 3 or, alternatively, in a different order. Furthermore, one or more of the blocks / sub-blocks of process 300 may be executed repeatedly or iteratively. Process 300 may be implemented by or in apparatus 210 and apparatus 220 as well as any variations thereof. Solely for illustrative purposes and without limiting the scope, process 300 is described below in the context of apparatus 210 as a UE (e.g., UE 110) and apparatus 220 as a communication entity such as a network node (e.g., non-terrestrial network node 128 or terrestrial network node 125) of a network (e.g., wireless network 120) . Process 300 may begin at block 310.
[0042] At 310, process 300 may involve processor 212 of apparatus 210, as a UE (e.g., UE 110) , transmitting, via transceiver 216, to a network (e.g., network 120 via apparatus 220 as non-terrestrial network node 128 or terrestrial network node 125) an UL message with a PDU session identity of a PDU session that is inactive in the network. Process 300 may proceed from 310 to 320.
[0043] At 320, process 300 may involve processor 212, in response to the transmitting, receiving, via transceiver 216, from the network a DL message with a cause indicating that a payload was not forwarded.
[0044] In some implementations, the UL message may include a UL NAS TRANSPORT message, and the DL message may include a DL NAS TRANSPORT message.
[0045] In some implementations, the cause may include a 5GMM cause #90.
[0046] In some implementations, in transmitting the UL message, process 300 may involve processor 212 transmitting the UL message with a payload container type IE set to CIoT user data container for the PDU session that is inactive in the network.
[0047] In some implementations, responsive to the receiving, process 300 may involve processor 212: (a) stopping any related timer; and (b) locally releasing the PDU session.
[0048] FIG. 4 illustrates an example process 400 in accordance with an implementation of the present disclosure. Process 400 may represent an aspect of implementing various proposed designs, concepts, schemes, systems and methods described above. More specifically, process 400 may represent an aspect of the proposed concepts and schemes pertaining to handling of user data when a PDU session is inactive in mobile communications in accordance with the present disclosure. Process 400 may include one or more operations, actions, or functions as illustrated by one or more of blocks 410 and 420. Although illustrated as discrete blocks, various blocks of process 400 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks / sub-blocks of process 400 may be executed in the order shown in FIG. 4 or, alternatively, in a different order. Furthermore, one or more of the blocks / sub-blocks of process 400 may be executed repeatedly or iteratively. Process 400 may be implemented by or in apparatus 210 and apparatus 220 as well as any variations thereof. Solely for illustrative purposes and without limiting the scope, process 400 is described below in the context of apparatus 210 as a UE (e.g., UE 110) and apparatus 220 as a communication entity such as a network node (e.g., non-terrestrial network node 128 or terrestrial network node 125) of a network (e.g., wireless network 120) . Process 400 may begin at block 410.
[0049] At 410, process 400 may involve processor 222 of apparatus 220, as a network node (e.g., network node 128 or terrestrial network node 125) of a network (e.g., wireless network 120) , receiving, via transceiver 226, from a UE (e.g., apparatus 210) an UL message with a PDU session identity of a PDU session that is inactive in the network. Process 400 may proceed from 410 to 420.
[0050] At 420, process 400 may involve processor 222, in response to the receiving, transmitting, via transceiver 226, to the UE a DL message with a cause indicating that a payload was not forwarded.
[0051] In some implementations, the UL message may include a UL NAS TRANSPORT message, and the DL message may include a DL NAS TRANSPORT message.
[0052] In some implementations, the cause may include a 5GMM cause #90.
[0053] In some implementations, in receiving the UL message, process 400 may involve processor 222 receiving the UL message with a payload container type IE set to CIoT user data container for the PDU session that is inactive in the network.
[0054] In some implementations, responsive to the receiving, process 400 may further involve processor 222 performing either or both of: (a) ignoring a CIoT user data container received in the UL message; and (b) including a PDU session status IE in the DL message. Additional Notes
[0055] The herein-described subject matter sometimes illustrates different components contained within, or connected with, different other components. It is to be understood that such depicted architectures are merely examples, and that in fact many other architectures can be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively "associated" such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as "associated with" each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated can also be viewed as being "operably connected" , or "operably coupled" , to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being "operably couplable" , to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and / or physically interacting components and / or wirelessly interactable and / or wirelessly interacting components and / or logically interacting and / or logically interactable components.
[0056] Further, with respect to the use of substantially any plural and / or singular terms herein, those having skill in the art can translate from the plural to the singular and / or from the singular to the plural as is appropriate to the context and / or application. The various singular / plural permutations may be expressly set forth herein for sake of clarity.
[0057] Moreover, it will be understood by those skilled in the art that, in general, terms used herein, and especially in the appended claims, e.g., bodies of the appended claims, are generally intended as “open” terms, e.g., the term “including” should be interpreted as “including but not limited to, ” the term “having” should be interpreted as “having at least, ” the term “includes” should be interpreted as “includes but is not limited to, ” etc. It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles "a" or "an" limits any particular claim containing such introduced claim recitation to implementations containing only one such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and indefinite articles such as "a" or "an, " e.g., “a” and / or “an” should be interpreted to mean “at least one” or “one or more; ” the same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted to mean at least the recited number, e.g., the bare recitation of "two recitations, " without other modifiers, means at least two recitations, or two or more recitations. Furthermore, in those instances where a convention analogous to “at least one of A, B, and C, etc. ” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention, e.g., “a system having at least one of A, B, and C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc. In those instances where a convention analogous to “at least one of A, B, or C, etc. ” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention, e.g., “a system having at least one of A, B, or C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc. It will be further understood by those within the art that virtually any disjunctive word and / or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase “A or B” will be understood to include the possibilities of “A” or “B” or “A and B. ”
[0058] From the foregoing, it will be appreciated that various implementations of the present disclosure have been described herein for purposes of illustration, and that various modifications may be made without departing from the scope and spirit of the present disclosure. Accordingly, the various implementations disclosed herein are not intended to be limiting, with the true scope and spirit being indicated by the following claims.
Claims
1.A method of handling user data when a protocol data unit (PDU) session is inactive, comprising:transmitting, by a processor of a user equipment (UE) , to a network an uplink (UL) message with a PDU session identity of a PDU session that is inactive in the network; andresponsive to the transmitting, receiving, by the processor, from the network a downlink (DL) message with a cause indicating that a payload was not forwarded.2.The method of Claim 1, wherein the UL message comprises a UL non-access stratum (NAS) TRANSPORT message, and wherein the DL message comprises a DL NAS TRANSPORT message.3.The method of Claim 1, wherein the cause comprises a 5th Generation (5G) Mobility Management (5GMM) cause #90.4.The method of Claim 1, wherein the transmitting of the UL message comprises transmitting the UL message with a payload container type information element (IE) set to Cellular Internet of Things (CIoT) user data container for the PDU session that is inactive in the network.5.The method of Claim 1, responsive to the receiving, further comprising:stopping any related timer; andlocally releasing the PDU session.6.A method of handling user data when a protocol data unit (PDU) session is inactive, comprising:receiving, by a processor of a network node of a network, from a user equipment (UE) an uplink (UL) message with a PDU session identity of a PDU session that is inactive in the network; andresponsive to the receiving, transmitting, by the processor, to the UE a downlink (DL) message with a cause indicating that a payload was not forwarded.7.The method of Claim 6, wherein the UL message comprises a UL non-access stratum (NAS) TRANSPORT message, and wherein the DL message comprises a DL NAS TRANSPORT message.8.The method of Claim 6, wherein the cause comprises a 5th Generation (5G) Mobility Management (5GMM) cause #90.9.The method of Claim 6, wherein the receiving of the UL message comprises receiving the UL message with a payload container type information element (IE) set to Cellular Internet of Things (CIoT) user data container for the PDU session that is inactive in the network.10.The method of Claim 6, responsive to the receiving, further comprising:performing either or both of:ignoring a Cellular Internet of Things (CIoT) user data container received in the UL message; andincluding a PDU session status information element (IE) in the DL message.11.An apparatus implementable in a user equipment (UE) , comprising:a transceiver configured to communicate wirelessly; anda processor coupled to the transceiver and configured to perform operations comprising:transmitting, via the transceiver, to a network an uplink (UL) message with a PDU session identity of a PDU session that is inactive in the network; andresponsive to the transmitting, receiving, via the transceiver, from the network a downlink (DL) message with a cause indicating that a payload was not forwarded.12.The apparatus of Claim 11, wherein the UL message comprises a UL non-access stratum (NAS) TRANSPORT message, and wherein the DL message comprises a DL NAS TRANSPORT message.13.The apparatus of Claim 11, wherein the cause comprises a 5th Generation (5G) Mobility Management (5GMM) cause #90.14.The apparatus of Claim 11, wherein the transmitting of the UL message comprises transmitting the UL message with a payload container type information element (IE) set to Cellular Internet of Things (CIoT) user data container for the PDU session that is inactive in the network.15.The apparatus of Claim 11, responsive to the receiving, the processor is further configured to perform operations comprising:stopping any related timer; andlocally releasing the PDU session.
