Handling Of Invalid Mandatory Information In Mobile Communications

Abstract

Various examples and schemes pertaining to handling of invalid mandatory information in mobile communications are described. An apparatus (e.g., a user equipment (UE)) receives a 5th Generation session management (5GSM) message from a network node of a wireless network. The apparatus determines that there is an error encountered with a mandatory information element (IE) in the 5GSM message. The apparatus handles the error in a way specific to a protocol data unit (PDU) session procedure corresponding to the 5GSM message.

Description

CROSS REFERENCE TO RELATED PATENT APPLICATION(S)

The present disclosure is part of a non-provisional application claiming the priority benefit of U.S. Patent Application No. 62/742,325, filed on 6 Oct. 2018, the content of which being incorporated by reference in its entirety.

TECHNICAL FIELD

The present disclosure is generally related to mobile communications and, more particularly, to handling of invalid mandatory information in mobile communications.

BACKGROUND

Unless otherwise indicated herein, approaches described in this section are not prior art to the claims listed below and are not admitted as prior art by inclusion in this section.

Under the 3^rd Generation Partnership Project (3GPP) specifications, non-access stratum (NAS) procedures in a 5th Generation system (5GS) can be used for 5GS mobility management between a user equipment (UE) and an Access and Mobility Management Function (AMF) for both 3GPP access and non-3GPP access. The NAS procedures can also be used for 5GS session management between the UE and a Session Management Function (SMF) for both 3GPP access and non-3GPP access. Specifically, the 5G Session Management (5GSM) protocol defined in the 3GPP specifications (e.g., TS 24.301) provides procedures for the handling of 5GS protocol data unit (PDU) session contexts. Together with the bearer control provided by the access stratum (AS), the 5GSM protocol is used for the control of user plane (UP) bearers, as the 5G Session Management Function (SMF) is responsible for interacting with the decoupled data plane, creating, updating and removing PDU sessions and managing session context with the User Plane Function (UPF). Currently, however, it has not been defined as to how errors in non-semantical mandatory information elements should be handled for certain PDU session related procedures.

SUMMARY

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.

In one aspect, a method may involve a processor of an apparatus receiving a 5GSM message from a network node of a wireless network. The method may also involve the processor determining that there is an error encountered with a mandatory information element (IE) in the 5GSM message. The method may further involve the processor handing the error in a way specific to a PDU session procedure corresponding to the 5GSM message.

In one aspect, a method may involve a processor of an apparatus determining that there is an error encountered with a mandatory IE in a 5GSM message from a network node of a wireless network. The method may also involve the processor handling the error in a way depending on to which PDU session procedure the 5GSM message corresponds. The PDU session procedure to which the 5GSM message corresponds may be a PDU session establishment procedure, a PDU session modification procedure, or a PDU session release procedure.

In one aspect, an apparatus may include a transceiver and a processor coupled to the transceiver. The transceiver may be configured to wirelessly communicate with a network node of a wireless network. The processor may be configured to receive, via the transceiver, a 5GSM message from the network node. The processor may be also configured to determine that there is an error encountered with a mandatory IE in the 5GSM message. The processor may be further configured to handle the error in a way specific to a PDU session procedure corresponding to the 5GSM message.

It is noteworthy that, although description provided herein may be in the context of certain radio access technologies, networks and network topologies such as 5G and New Radio (NR), 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, Long-Term Evolution (LTE), LTE-Advanced, LTE-Advanced Pro, narrowband (NB), narrowband Internet of Things (NB-IoT), and any future-developed networks and technologies. Thus, the scope of the present disclosure is not limited to the examples described herein.

BRIEF DESCRIPTION OF THE DRAWINGS

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.

FIG. 1 is a diagram of an example network environment in which various proposed schemes in accordance with the present disclosure may be implemented.

FIG. 2 is a block diagram of an example communication system in accordance with an implementation of the present disclosure.

FIG. 3 is a flowchart of an example process in accordance with an implementation of the present disclosure.

FIG. 4 is a flowchart of an example process in accordance with an implementation of the present disclosure.

DETAILED DESCRIPTION OF PREFERRED IMPLEMENTATIONS

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

Implementations in accordance with the present disclosure relate to various techniques, methods, schemes and/or solutions pertaining to handling of invalid mandatory information 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.

FIG. 1 illustrates an example network environment 100 in which various solutions and schemes in accordance with the present disclosure may be implemented. Referring to FIG. 1, network environment 100 may involve a UE 110 in wireless communication with a wireless network 120 (e.g., a 5G NR mobile network or an NB-IoT network) via a network node 125 (e.g., a base station such as an eNB, a gNB or a transmit-receive point (TRP)). In network environment 100, UE 110 and wireless network 120 may implement various schemes pertaining handling of invalid mandatory information in mobile communications in accordance with the present disclosure.

Under various proposed schemes in accordance with the present disclosure, UE 110 may receive a 5GSM message for a PDU session-related procedure from wireless network 120 via network node 125 and may determine that there is an error encountered with a mandatory IE in the 5GSM message. Accordingly, UE 110 may handle the error in a way specific to the PDU session-related procedure, which may be a PDU session establishment procedure, a PDU session modification procedure, or a PDU session release procedure.

Under a proposed scheme in accordance with the present disclosure, in an event that the 5GSM message corresponds to a PDU SESSION ESTABLISHMENT ACCEPT message, UE 110 may handle the error by initiating a PDU session release procedure. For instance, UE 110 may send a PDU SESSION RELEASE REQUEST message to network node 125 with a 5GSM cause #96 to indicate invalid mandatory information.

Under another proposed scheme in accordance with the present disclosure, in an event that the 5GSM message corresponds to a PDU SESSION MODIFICATION COMMAND message, UE 110 may handle the error by sending a PDU SESSION MODIFICATION COMMAND REJECT message to network node 125 with a 5GSM cause #96 to indicate invalid mandatory information.

Under yet another proposed scheme in accordance with the present disclosure, in an event that the 5GSM message corresponds to a PDU SESSION RELEASE COMMAND message, UE 110 may handle the error by sending a PDU SESSION RELEASE COMPLETE message to network node 125 with a 5GSM cause #96 to indicate invalid mandatory information.

ILLUSTRATIVE IMPLEMENTATIONS

FIG. 2 illustrates an example communication system 200 having 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 invalid mandatory information in mobile communications, including various schemes described above as well as process 400 described below.

Each of apparatus 210 and apparatus 220 may be a part of an electronic apparatus, which may be a UE such as a portable or mobile apparatus, a wearable apparatus, a wireless communication apparatus or a computing apparatus. For instance, each of apparatus 210 and apparatus 220 may be implemented in a smartphone, a smartwatch, a personal digital assistant, 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 or NB-IoT apparatus such as an immobile or a stationary apparatus, a home apparatus, 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. Alternatively, 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. 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. 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 each of apparatus 210 and apparatus 220 are neither shown in FIG. 2 nor described below in the interest of simplicity and brevity.

In some implementations, at least one of apparatus 210 and apparatus 220 may be a part of an electronic apparatus, which may be a network node or base station (e.g., eNB, gNB or TRP), a small cell, a router or a gateway. For instance, at least one of apparatus 210 and apparatus 220 may be implemented in an eNodeB in an LTE, LTE-Advanced or LTE-Advanced Pro network or in a gNB in a 5G, NR, IoT or NB-IoT network. Alternatively, at least one of apparatus 210 and apparatus 220 may be implemented in the form of one or more IC chips such as, for example and without limitation, one or more single-core processors, one or more multi-core processors, or one or more CISC or RISC processors.

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 handling of invalid mandatory information in mobile communications in accordance with various implementations of the present disclosure.

In some implementations, apparatus 210 may also include a transceiver 216, as a communication device, coupled to processor 212 and capable of wirelessly transmitting and receiving data. 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 also include a transceiver 226, as a communication device, coupled to processor 222 and capable of wirelessly transmitting and receiving data. 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. Accordingly, apparatus 210 and apparatus 220 may wirelessly communicate with each other via transceiver 216 and transceiver 226, respectively.

To aid better understanding, the following description of the operations, functionalities and capabilities of each of apparatus 210 and apparatus 220 is provided in the context of an NR communication environment in which apparatus 210 is implemented in or as a UE (e.g., UE 110) and apparatus 220 is implemented in or as a network node (e.g., network node 125) of a wireless network (e.g., wireless network 120).

In one aspect of handling of invalid mandatory information in mobile communications in accordance with the present disclosure, processor 212 of apparatus 210 may receive, via transceiver 216, a 5GSM message from apparatus 220 as a network node of a wireless network. Additionally, processor 212 may determine that there is an error encountered with a mandatory IE in the 5GSM message. Moreover, processor 212 may handle the error in a way specific to a PDU session procedure corresponding to the 5GSM message.

In some implementations, the 5GSM message may include a PDU SESSION ESTABLISHMENT ACCEPT message. In such cases, in handling the error, processor 212 may initiate a PDU session release procedure. In some implementations, in initiating the PDU session release procedure, processor 212 may send, via transceiver 216, a PDU SESSION RELEASE REQUEST message to apparatus 220 with a 5GSM cause #96 to indicate invalid mandatory information.

In some implementations, the 5GSM message may include a PDU SESSION MODIFICATION COMMAND message. In such cases, in handling the error, processor 212 may send, via transceiver 216, a PDU SESSION MODIFICATION COMMAND REJECT message to apparatus 220 with a 5GSM cause #96 to indicate invalid mandatory information.

In some implementations, the 5GSM message may include a PDU SESSION RELEASE COMMAND message. In such cases, in handling the error, processor 212 may send, via transceiver 216, a PDU SESSION RELEASE COMPLETE message to apparatus 220 with a 5GSM cause #96 to indicate invalid mandatory information.

In another aspect of handling of invalid mandatory information in mobile communications in accordance with the present disclosure, processor 212 of apparatus 210 may determine that there is an error encountered with a mandatory IE in a 5GSM message from apparatus 220 as a network node of a wireless network. Furthermore, processor 212 may handle the error in a way depending on to which PDU session procedure the 5GSM message corresponds. In some implementations, the PDU session procedure to which the 5GSM message corresponds may include a PDU session establishment procedure, a PDU session modification procedure, or a PDU session release procedure.

In some implementations, the 5GSM message may include a PDU SESSION ESTABLISHMENT ACCEPT message. In such cases, in handling the error, processor 212 may initiate a PDU session release procedure. In some implementations, in initiating the PDU session release procedure, processor 212 may send, via transceiver 216, a PDU SESSION RELEASE REQUEST message to apparatus 220 with a 5GSM cause #96 to indicate invalid mandatory information.

In some implementations, the 5GSM message may include a PDU SESSION MODIFICATION COMMAND message. In such cases, in handling the error, processor 212 may send, via transceiver 216, a PDU SESSION MODIFICATION COMMAND REJECT message to apparatus 220 with a 5GSM cause #96 to indicate invalid mandatory information.

In some implementations, the 5GSM message may include a PDU SESSION RELEASE COMMAND message. In such cases, in handling the error, processor 212 may send, via transceiver 216, a PDU SESSION RELEASE COMPLETE message to apparatus 220 with a 5GSM cause #96 to indicate invalid mandatory information.

Illustrative Processes

FIG. 3 illustrates an example process 300 in accordance with an implementation of the present disclosure. Process 300 may be an example implementation of the proposed schemes described above with respect to handling of invalid mandatory information in mobile communications in accordance with the present disclosure. Process 300 may represent an aspect of implementation of features of apparatus 210 and apparatus 220. Process 300 may include one or more operations, actions, or functions as illustrated by one or more of blocks 310, 320 and 330. 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 of process 300 may executed in the order shown in FIG. 3 or, alternatively, in a different order. Process 300 may also be repeated partially or entirely. Process 300 may be implemented by apparatus 210, apparatus 220 and/or any suitable wireless communication device, UE, base station or machine type devices. Solely for illustrative purposes and without limitation, process 300 is described below in the context of apparatus 210 in or as a UE and apparatus 220 in or as a network node of a wireless network (e.g., 5G NR mobile network). Process 300 may begin at block 310.

At 310, process 300 may involve processor 212 of apparatus 210 receiving, via transceiver 216, a 5GSM message from apparatus 220 as a network node of a wireless network. Process 300 may proceed from 310 to 320.

At 320, process 300 may involve processor 212 determining that there is an error encountered with a mandatory information element (IE) in the 5GSM message. Process 300 may proceed from 320 to 330.

At 330, process 300 may involve processor 212 handling the error in a way specific to a PDU session procedure corresponding to the 5GSM message.

In some implementations, the 5GSM message may include a PDU SESSION ESTABLISHMENT ACCEPT message. In such cases, in handling the error, process 300 may involve processor 212 initiating a PDU session release procedure. In some implementations, in initiating the PDU session release procedure, process 300 may involve processor 212 sending, via transceiver 216, a PDU SESSION RELEASE REQUEST message to apparatus 220 with a 5GSM cause #96 to indicate invalid mandatory information.

In some implementations, the 5GSM message may include a PDU SESSION MODIFICATION COMMAND message. In such cases, in handling the error, process 300 may involve processor 212 sending, via transceiver 216, a PDU SESSION MODIFICATION COMMAND REJECT message to apparatus 220 with a 5GSM cause #96 to indicate invalid mandatory information.

In some implementations, the 5GSM message may include a PDU SESSION RELEASE COMMAND message. In such cases, in handling the error, process 300 may involve processor 212 sending, via transceiver 216, a PDU SESSION RELEASE COMPLETE message to apparatus 220 with a 5GSM cause #96 to indicate invalid mandatory information.

FIG. 4 illustrates an example process 400 in accordance with an implementation of the present disclosure. Process 400 may be an example implementation of the proposed schemes described above with respect to handling of invalid mandatory information in mobile communications in accordance with the present disclosure. Process 400 may represent an aspect of implementation of features of apparatus 210 and apparatus 220. 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 of process 400 may executed in the order shown in FIG. 4 or, alternatively, in a different order. Process 400 may also be repeated partially or entirely. Process 400 may be implemented by apparatus 210, apparatus 220 and/or any suitable wireless communication device, UE, base station or machine type devices. Solely for illustrative purposes and without limitation, process 400 is described below in the context of apparatus 210 in or as a UE and apparatus 220 in or as a network node of a wireless network (e.g., 5G NR mobile network). Process 400 may begin at block 410.

At 410, process 400 may involve processor 212 of apparatus 210 determining that there is an error encountered with a mandatory IE in a 5GSM message from apparatus 220 as a network node of a wireless network. Process 400 may proceed from 410 to 420.

At 420, process 400 may involve processor 212 handling the error in a way depending on to which PDU session procedure the 5GSM message corresponds.

In some implementations, the PDU session procedure to which the 5GSM message corresponds may include a PDU session establishment procedure, a PDU session modification procedure, or a PDU session release procedure.

In some implementations, the 5GSM message may include a PDU SESSION ESTABLISHMENT ACCEPT message. In such cases, in handling the error, process 400 may involve processor 212 initiating a PDU session release procedure. In some implementations, in initiating the PDU session release procedure, process 400 may involve processor 212 sending, via transceiver 216, a PDU SESSION RELEASE REQUEST message to apparatus 220 with a 5GSM cause #96 to indicate invalid mandatory information.

In some implementations, the 5GSM message may include a PDU SESSION MODIFICATION COMMAND message. In such cases, in handling the error, process 400 may involve processor 212 sending, via transceiver 216, a PDU SESSION MODIFICATION COMMAND REJECT message to apparatus 220 with a 5GSM cause #96 to indicate invalid mandatory information.

In some implementations, the 5GSM message may include a PDU SESSION RELEASE COMMAND message. In such cases, in handling the error, process 400 may involve processor 212 sending, via transceiver 216, a PDU SESSION RELEASE COMPLETE message to apparatus 220 with a 5GSM cause #96 to indicate invalid mandatory information.

ADDITIONAL NOTES

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.

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.

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.”

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, comprising:

receiving, by a processor of an apparatus, a 5th Generation session management (5GSM) message from a network node of a wireless network;

determining, by the processor, that there is an error encountered with a mandatory information element (IE) in the 5GSM message; and

handling, by the processor, the error in a way specific to a protocol data unit (PDU) session procedure corresponding to the 5GSM message.

2. The method of claim 1, wherein the 5GSM message comprises a PDU SESSION ESTABLISHMENT ACCEPT message, and wherein the handling of the error comprises initiating a PDU session release procedure.

3. The method of claim 2, wherein the initiating of the PDU session release procedure comprises sending a PDU SESSION RELEASE REQUEST message to the network node with a 5GSM cause #96 to indicate invalid mandatory information.

4. The method of claim 1, wherein the 5GSM message comprises a PDU SESSION MODIFICATION COMMAND message, and wherein the handling of the error comprises sending a PDU SESSION MODIFICATION COMMAND REJECT message to the network node with a 5GSM cause #96 to indicate invalid mandatory information.

5. The method of claim 1, wherein the 5GSM message comprises a PDU SESSION RELEASE COMMAND message, and wherein the handling of the error comprises sending a PDU SESSION RELEASE COMPLETE message to the network node with a 5GSM cause #96 to indicate invalid mandatory information.

6. A method, comprising:

determining, by a processor of an apparatus, that there is an error encountered with a mandatory information element (IE) in a 5th Generation session management (5GSM) message from a network node of a wireless network; and

handling, by the processor, the error in a way depending on to which protocol data unit (PDU) session procedure the 5GSM message corresponds,

wherein the PDU session procedure to which the 5GSM message corresponds comprises a PDU session establishment procedure, a PDU session modification procedure, or a PDU session release procedure.

7. The method of claim 6, wherein the 5GSM message comprises a PDU SESSION ESTABLISHMENT ACCEPT message, and wherein the handling of the error comprises initiating a PDU session release procedure.

8. The method of claim 7, wherein the initiating of the PDU session release procedure comprises sending a PDU SESSION RELEASE REQUEST message to the network node with a 5GSM cause #96 to indicate invalid mandatory information.

9. The method of claim 6, wherein the 5GSM message comprises a PDU SESSION MODIFICATION COMMAND message, and wherein the handling of the error comprises sending a PDU SESSION MODIFICATION COMMAND REJECT message to the network node with a 5GSM cause #96 to indicate invalid mandatory information.

10. The method of claim 6, wherein the 5GSM message comprises a PDU SESSION RELEASE COMMAND message, and wherein the handling of the error comprises sending a PDU SESSION RELEASE COMPLETE message to the network node with a 5GSM cause #96 to indicate invalid mandatory information.

11. An apparatus, comprising:

a transceiver configured to wirelessly communicate with a network node of a wireless network; and

a processor coupled to the transceiver and configured to perform operations comprising: receiving, via the transceiver, a 5th Generation session management (5GSM) message from the network node; determining that there is an error encountered with a mandatory information element (IE) in the 5GSM message; and handling the error in a way specific to a protocol data unit (PDU) session procedure corresponding to the 5GSM message.

12. The apparatus of claim 11, wherein the 5GSM message comprises a PDU SESSION ESTABLISHMENT ACCEPT message, and wherein, in handling the error, the processor is configured to initiate a PDU session release procedure.

13. The apparatus of claim 12, wherein, in initiating the PDU session release procedure, the processor is configured to send, via the transceiver, a PDU SESSION RELEASE REQUEST message to the network node with a 5GSM cause #96 to indicate invalid mandatory information.

14. The apparatus of claim 11, wherein the 5GSM message comprises a PDU SESSION MODIFICATION COMMAND message, and wherein, in handling the error, the processor is configured to send, via the transceiver, a PDU SESSION MODIFICATION COMMAND REJECT message to the network node with a 5GSM cause #96 to indicate invalid mandatory information.

15. The apparatus of claim 11, wherein the 5GSM message comprises a PDU SESSION RELEASE COMMAND message, and wherein, in handling the error, the processor is configured to send, via the transceiver, a PDU SESSION RELEASE COMPLETE message to the network node with a 5GSM cause #96 to indicate invalid mandatory information.