Handling of asynchronous reconfiguration complete message and pdu session modification complete message in mobile communication

Abstract

This disclosure describes techniques related to reconfiguration complete messages and protocol data unit (PDU) session modification complete messages in mobile communications. A user equipment (UE) receives a reconfiguration message with an addition or modification indication from a network. In response, the UE sends a reconfiguration complete message to the network, which contains one or more non-access stratum (NAS) messages.

Description

[0001] Cross-references

[0002] This invention claims priority to U.S. Patent Application No. 63 / 691,400, filed September 6, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This invention generally relates to mobile communications, and more specifically, to processing asynchronous reconfiguration completion messages and protocol data unit (PDU) session modification completion messages in mobile communications. Background Technology

[0004] In wireless communications (such as mobile communications) under the current 3rd Generation Partnership Project (3GPP) specifications, radio resource control (RRC) reconfiguration is used to add data radio bearers (DRBs). For example, the radio access network (RAN) can send an RRC reconfiguration message to the user equipment (UE) to add a DRB in the radio bearer configuration information element (IE). This IE can configure the DRB identifier, packet data convergence protocol (PDCP) configuration (PDCP-Config), service data adaptation protocol (SDAP-Config), etc. On the other hand, session management (SM) is used to modify protocol data unit (PDU) sessions to add new quality of service (QoS) streams. For example, the core network (CN) can send a PDU session modification command to add a new QoS flow and configure it with authorized QoS flow description IEs and related packet filters through authorized QoS rules IEs.

[0005] There is a possibility that a PDU session modification command may be piggybacked during RRC reconfiguration. For example, the network may send an RRC reconfiguration message to add a QoS flow and DRB, and include a PDU session modification command in the dedicated non-access stratum (NAS) message list to add the QoS flow. Therefore, the UE can only send the RRC reconfiguration complete message and the PDU session modification complete message separately. That is, the PDU session modification acceptance message is included in the uplink (UL) NAS transport, which is then included in the ULInformationTransfer IE.

[0006] Therefore, there is a technical issue where the UE can only send the RRC reconfiguration complete message and the NAS PDU session modification complete message in separate messages. Typically, the UE sends the NAS complete message after the RRC complete message. If the NAS message fails in over-the-air (OTA) transmission but the RRC message succeeds, and the UE sends data with the new configuration, the core network may not yet be ready to receive it with the updated QoS flow configuration. This could be due to unreliable links between network nodes (e.g., gNB) and the CN or between the UE and the gNB, causing the NAS message to fail to reach the UE. The core network can retransmit the NAS command message using timer T3590. However, the core network can retransmit the NAS PDU session modification command message to create a QoS flow, even though the gNB has already added the corresponding DRB. This introduces some processing complexity at the gNB end, which is undesirable.

[0007] Therefore, a solution is needed in mobile communications for reconfiguration completion messages and PDU session modification completion messages. Summary of the Invention

[0008] The following abstract is for illustrative purposes only and is not intended to be limiting in any way. That is, the following abstract aims to introduce the concepts, key points, benefits, and advantages of the novel and non-obvious techniques described in this invention. Some embodiments will be further set forth in the detailed description below. Therefore, the following abstract is not intended to identify the essential features of the claimed subject matter, nor is it intended to determine the scope of the claimed subject matter.

[0009] The purpose of this invention is to propose solutions or strategies to address the problems described herein. More specifically, the various solutions proposed in this invention are believed to provide solutions related to reconfiguration completion messages and PDU session modification completion messages in mobile communications. It is believed that implementing one or more solutions proposed in this invention can solve or alleviate the aforementioned problems.

[0010] In one aspect, a method may involve a UE receiving a reconfiguration message from a network with an indication of addition or modification. The method may also involve the UE responding to the network by sending a reconfiguration completion message containing one or more NAS messages.

[0011] In another aspect, one method may involve a network node of the network sending a reconfiguration message with an indication of addition or modification to the UE. The method may also involve the network node receiving a reconfiguration completion message containing one or more NAS messages from the UE in response to sending the reconfiguration message.

[0012] It is worth noting that although the content described in this invention may be carried out in the context of certain wireless access technologies, networks, and network topologies, such as 5th Generation (5G) New Radio (NR), Beyond Fifth-Generation (B5G), and 6th Generation (6G) mobile communications, the proposed concepts, schemes, and any variations / derivatives thereof can be implemented, used, and implemented by other types of wireless access technologies, networks, and network topologies, such as, but not limited to, 4th Generation (4G) / Long-Term Evolution (LTE), LTE-Advanced, LTE-AdvancedPro, 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. Therefore, the scope of this invention is not limited to the examples described herein. Attached Figure Description

[0013] The accompanying drawings are intended to further understand the invention and are incorporated into and constitute a part of this invention. The drawings illustrate embodiments of the invention and, together with the description, serve to explain the principles of the invention. It will be understood that the drawings are not necessarily drawn to scale, as some components may be shown out of proportion to their actual dimensions for clarity in illustrating the concepts of the invention.

[0014] Figure 1 This is a schematic diagram of an example network environment in which various solutions and schemes conforming to the content of this invention can be implemented.

[0015] Figure 2 This is an example design schematic diagram under a proposed solution that conforms to the content of this invention.

[0016] Figure 3 This is an example design schematic diagram under a proposed solution that conforms to the content of this invention.

[0017] Figure 4 This is a sample communication system block diagram under a proposed solution that conforms to the content of this invention.

[0018] Figure 5 This is an example flowchart of a proposed solution that conforms to the content of this invention.

[0019] Figure 6 This is an example flowchart of a proposed solution that conforms to the content of this invention. Detailed Implementation

[0020] Detailed embodiments and implementations of the subject matter of the claims are disclosed herein. However, it should be understood that the disclosed embodiments and implementations are merely illustrative of the subject matter and may be implemented in various forms. The invention can take many different forms and should not be construed as limited to the exemplary embodiments and implementations listed herein. Rather, these exemplary embodiments and implementations are provided to make the description of the invention exhaustive and complete, and to fully convey the scope of the invention to those skilled in the art. In the following description, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations.

[0021] Overview

[0022] According to the present invention, various techniques, methods, schemes, and / or solutions related to reconfiguration completion messages and PDU session modification completion messages in mobile communications are involved. According to the present invention, multiple possible solutions can be implemented individually or in combination. That is, although these possible solutions are described separately below, two or more of them can be implemented in some combination.

[0023] Figure 1 An example network environment 100 is shown, in which various solutions and schemes of the present invention can be implemented. Figures 2 to 6 Examples of implementations of various proposed solutions in network environment 100 according to the present invention are shown. The following descriptions of the various proposed solutions are combined with… Figures 1 to 6 Please provide an explanation.

[0024] See Figure 1 Network environment 100 involves a UE 110 wirelessly communicating with a wireless network 120 (e.g., a 6G mobile network comprising a non-terrestrial network (NTN) and a terrestrial network (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 an NTN serving cell for wireless communication with the UE 110. In some implementations, the UE 110 may be a smartphone, wearable device, 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 this communication environment, UE 110, network 120, terrestrial network node 125 and non-terrestrial network node 128 can implement various schemes related to reconfiguration completion messages and PDU session modification completion messages, as described below.

[0025] It is worth noting that although the various proposed solutions may be described separately or individually below, in actual implementation, some or all of the proposed solutions may be used in combination or implemented in other ways. Of course, each proposed solution may also be used or implemented individually or separately. In addition, as used in this invention, each proposed solution may refer to the SM layer above the Mobility Management (MM) layer above the RRC layer, as well as the PDCP layer, radio link control (RLC) layer, medium access control (MAC) layer, physical (PHY) layer, etc.

[0026] Figure 2 An example design 200 according to the proposed scheme of the present invention is illustrated. Under this proposed scheme, a new dedicated NAS-MessageList field can be added or included in the RRC reconfiguration completion message to piggyback one or more NAS messages. Thus, the UE (e.g., UE 110) can use a single RRC message to simultaneously send access stratum (AS) and non-access stratum (NAS) completion messages to achieve synchronization transactions. See also Figure 2 The network (e.g., wireless network 120) may send an RRC reconfiguration message to the UE (e.g., UE 110) containing a PDU session modification command, which may be piggybacked or included in the RRC reconfiguration message. Upon completion, the UE may reply to the network with an RRC reconfiguration completion message containing an MM uplink NAS transport message (MM UL NAS TRANSPORT) and an acceptance of the PDU session modification (PDUSESSION MODIFICATION ACCEPT).

[0027] Figure 3 An example design 300 according to a proposed solution of the present invention is illustrated. Design 300 may involve at least a portion of an RRC reconfiguration completion message. Under this proposed solution, if the triggered RRC reconfiguration includes NAS messages and is a non-handover scenario, then a list of NAS messages may be included in the RRC reconfiguration completion message. For example, if the RRC reconfiguration message indicates adding or modifying the DRB by piggybacking the required SM messages, then the dedicatedNAS-MessageList field may appear in the RRC reconfiguration completion message.

[0028] In view of the above, according to various proposed embodiments of the present invention, a method for including a NAS message in an RRC message in a wireless communication network (e.g., network 120) may involve a UE (e.g., UE 110) receiving an RRC message from a network node (e.g., terrestrial network node 125 or non-terrestrial network node 128) containing an Add DRB indication and one or more NAS command messages to add one or more QoS flows. The method may also involve the UE responding by sending an RRC completion message to the network node. The RRC completion message may contain one or more NAS completion or acceptance messages.

[0029] Exemplary Implementation

[0030] Figure 4An example communication system 400 is illustrated, comprising at least one example device 410 and one example device 420, according to an implementation of the present invention. Both device 410 and device 420 can perform various functions to implement the schemes, techniques, processes, and methods described in this invention related to reconfiguration completion messages and PDU session modification completion messages in mobile communications, including the aforementioned schemes regarding various proposed designs, concepts, schemes, systems, and methods, including network environment 100, and the processes described below.

[0031] Each device 410 and device 420 may be part of an electronic device, which may be a network device or UE (e.g., UE 110), such as a portable or mobile device, a wearable device, an in-vehicle device or vehicle, a wireless communication device, or a computing device. For example, each device 410 and device 420 may be implemented in a smartphone, smartwatch, personal digital assistant, electronic control unit (ECU) in a vehicle, digital camera, or computing device such as a tablet, laptop, or mobile phone. Each device 410 and device 420 may also be part of a machine-type device, which may be an IoT device, such as a non-movable or fixed device, a home device, a roadside unit (RSU), a wired communication device, or a computing device. For example, each device 410 and device 420 may be implemented in a smart thermostat, a smart refrigerator, a smart door lock, a wireless speaker, or a home control center. When implemented as a network device, device 410 and / or device 420 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 / 6G network or IoT network.

[0032] In some embodiments, each device 410 and device 420 may be implemented as one or more integrated circuit (IC) chips, such as, but not limited to, 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 embodiments described above, each device 410 and device 420 may be implemented in a network device or a UE. Each device 410 and device 420 may include... Figure 4The components shown include, for example, processors 412 and 422, respectively. Each device 410 and device 420 may also include one or more other components unrelated to the proposed solution (e.g., internal power supply, display device, and / or user interface device). Therefore, for the sake of brevity, these components of devices 410 and 420 are not listed in the table below. Figure 4 It is shown in the text and is not described in the following text.

[0033] In one aspect, each processor 412 and processor 422 may be implemented as one or more single-core processors, one or more multi-core processors, or one or more CISC or RISC processors. That is, although the singular term "processor" is used herein to refer to processor 412 and processor 422, in some embodiments of the invention, each processor 412 and processor 422 may include multiple processors, and in other embodiments may include a single processor. In another aspect, each processor 412 and processor 422 may be implemented in hardware (and optionally firmware) and include electronic components, such as, but not limited to, 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 varactor diodes, which are configured and arranged to achieve a specific purpose of the invention. In other words, in at least some embodiments, each processor 412 and processor 422 is a dedicated machine specifically designed, arranged, and configured to perform specific tasks, including tasks related to reconfiguration completion messages and PDU session modification completion messages in mobile communications, according to various embodiments of the invention.

[0034] In some embodiments, device 410 may further include a transceiver 416 coupled to processor 412. Transceiver 416 is capable of wirelessly transmitting and receiving data. In some embodiments, transceiver 416 is capable of wireless communication with different types of wireless networks using different radio access technologies (RATs). In some embodiments, transceiver 416 may be equipped with multiple antenna ports (not shown), such as four antenna ports. That is, transceiver 416 may be equipped with multiple transmit antennas and multiple receive antennas for multiple-input multiple-output (MIMO) wireless communication. In some embodiments, device 420 may further include a transceiver 426 coupled to processor 422. Transceiver 426 may include a transceiver capable of wirelessly transmitting and receiving data. In some embodiments, transceiver 426 is capable of wireless communication with different types of UE / wireless networks using different RATs. In some embodiments, transceiver 426 may be equipped with multiple antenna ports (not shown), such as four antenna ports. In other words, transceiver 426 can be equipped with multiple transmit antennas and multiple receive antennas for MIMO wireless communication.

[0035] In some embodiments, device 410 may further include a memory 414 coupled to processor 412 and capable of being accessed and storing data by processor 412. In some embodiments, device 420 may further include a memory 424 coupled to processor 422 and capable of being accessed and storing data by processor 422. Each memory 414 and memory 424 may include a 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 memory 414 and memory 424 may include a read-only memory (ROM), such as a mask ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), and / or electrically erasable programmable ROM (EEPROM). Alternatively, each memory 414 and memory 424 may include a non-volatile random-access memory (NVRAM), such as flash memory, solid-state memory, ferroelectric RAM (FeRAM), magnetoresistive RAM (MRAM), and / or phase-change memory.

[0036] Each device 410 and device 420 can be a communication entity capable of communicating with each other according to various proposed embodiments of the present invention. For illustrative purposes and without limitation, the following describes the capabilities of device 410 as a UE (e.g., UE 110) and device 420 as a network node (e.g., terrestrial network node 125 or non-terrestrial network node 128) in a network (e.g., a wireless network 120 as a 5G / NR mobile network) within the context of example flows 500 and 600.

[0037] Example Process

[0038] Figure 5An example flow 500 according to an embodiment of the present invention is illustrated. Flow 500 may represent one aspect of implementing the various proposed designs, concepts, schemes, systems, and methods described above. More specifically, flow 500 may represent one aspect of proposed concepts and schemes related to the present invention regarding reconfiguration completion messages and PDU session modification completion messages in mobile communications. Flow 500 may include one or more operations, actions, or functions as shown in one or more modules. Although shown in discrete module form, the various modules of flow 500 may be divided into more modules, merged into fewer modules, or omitted according to desired implementation. Furthermore, the modules / submodules of flow 500 may be arranged according to... Figure 5 The process can be executed in the order shown, or in a different order. Furthermore, one or more modules / submodules of process 500 can be executed repeatedly or iteratively. Process 500 can be implemented by devices 410 and 420, and any variations thereof. For illustrative purposes only and without limitation, the following process 500 is described with device 410 as a UE (e.g., UE 110) and device 420 as a network node (e.g., non-terrestrial network node 128 or terrestrial network node 125) of a communication entity (e.g., a network (e.g., wireless network 120)). Process 500 can begin at module 510.

[0039] At 510, process 500 may involve the processor 412 of device 410 (as a UE (e.g., UE 110)) receiving a reconfiguration message with an add or modify instruction from a network (e.g., a wireless network 120 via device 420 as a terrestrial network node 125 or a non-terrestrial network node 128) via transceiver 416. Process 500 may continue from 510 to 520.

[0040] At 520, process 500 may involve processor 412 responding to the network via transceiver 416 by sending a reconfiguration completion message containing one or more NAS messages.

[0041] In some embodiments, the indication for adding or modifying may include a PDU session modification command.

[0042] In some embodiments, the indication for adding or modifying may include an indication to add a DRB and one or more NAS command messages to add one or more QoS flows.

[0043] In some embodiments, when responding to the reconfiguration complete message, process 500 may involve processor 412 sending the reconfiguration complete message with a dedicated NAS message list IE to include the one or more NAS messages.

[0044] In some embodiments, when responding to the reconfiguration complete message, process 500 may involve processor 412 sending the reconfiguration complete message with the one or more NAS messages and one or more AS messages.

[0045] In some embodiments, the reconfiguration message may include an RRC reconfiguration message. In some embodiments, the reconfiguration complete message may include an RRC reconfiguration complete message. In some embodiments, the RRC reconfiguration complete message may include one or more NAS complete or accept messages.

[0046] Figure 6 An example flow 600 according to an embodiment of the present invention is illustrated. Flow 600 may represent one aspect of implementing the various proposed designs, concepts, schemes, systems, and methods described above. More specifically, flow 600 may represent one aspect of proposed concepts and schemes related to the present invention regarding reconfiguration completion messages and PDU session modification completion messages in mobile communications. Flow 600 may include one or more operations, actions, or functions as shown in one or more modules. Although shown in discrete module form, the various modules of flow 600 may be divided into more modules, merged into fewer modules, or omitted according to desired implementation. Furthermore, the modules / submodules of flow 600 may be arranged according to... Figure 6 The process can be executed in the order shown, or in a different order. Furthermore, one or more modules / submodules of process 600 can be executed repeatedly or iteratively. Process 600 can be implemented by devices 410 and 420, and any variations thereof. For illustrative purposes only and without limitation, the following process 600 is described with device 410 as a UE (e.g., UE 110) and device 420 as a network node (e.g., non-terrestrial network node 128 or terrestrial network node 125) of a communication entity (e.g., a network (e.g., wireless network 120)). Process 600 can begin at module 610.

[0047] At 610, process 600 may involve the processor 422 of device 420 (as a network node (e.g., terrestrial network node 125 or non-terrestrial network node 128) of a network (e.g., wireless network 120) sending a reconfiguration message with an add or modify instruction to the UE (e.g., device 410) via transceiver 426. Process 600 may continue from 610 to 620.

[0048] At 620, process 600 may involve processor 422 receiving a reconfiguration complete message containing one or more NAS messages from the UE via transceiver 426 in response to sending the reconfiguration message.

[0049] In some embodiments, the indication for adding or modifying may include a PDU session modification command.

[0050] In some embodiments, the indication for adding or modifying may include an indication to add a DRB and one or more NAS command messages to add one or more QoS flows.

[0051] In some embodiments, when the reconfiguration complete message is received, process 600 may involve processor 422 receiving the reconfiguration complete message with a dedicated NAS message list IE to include the one or more NAS messages.

[0052] In some embodiments, when receiving the reconfiguration complete message, process 600 may involve processor 422 receiving the reconfiguration complete message along with one or more NAS messages and one or more AS messages.

[0053] In some embodiments, the reconfiguration message may include an RRC reconfiguration message. In some embodiments, the reconfiguration complete message may include an RRC reconfiguration complete message. In some embodiments, the RRC reconfiguration complete message may include one or more NAS complete or accept messages.

[0054] Additional notes

[0055] The subject matter of this invention sometimes illustrates different components contained within or connected to different other components. It should be understood that these illustrated architectures are merely examples, and many other architectures can actually be implemented to achieve the same functionality. Conceptually, any arrangement of components to achieve the same function is effectively “associated” to achieve the desired functionality. Therefore, any two components combined in this invention to achieve a specific function can be considered “associated with each other” to achieve the desired function, regardless of the architecture or intermediate components. Similarly, any two such associated components can also be considered “operably connected” or “operably coupled” to achieve the desired function, and any two components that can be suchly associated can also be considered “operably coupled” to achieve the desired function. Specific examples of being operablely coupled include, but are not limited to, physically matable and / or physically interactive components and / or wirelessly interactive and / or logically interactive components.

[0056] Furthermore, regarding the use of virtually any plural and / or singular terms in this invention, those skilled in the art can appropriately convert plural to singular and / or singular to plural depending on the context and / or application. Various singular / plural arrangements can be explicitly listed in this invention for clarity.

[0057] Furthermore, those skilled in the art will understand that the terminology commonly used in this invention, particularly in appended claims, such as the body portion of appended claims, is generally intended as “open-ended” terms. For example, the word “comprising” should be interpreted as “including but not limited to,” the word “having” should be interpreted as “at least having,” and the word “including” should be interpreted as “including but not limited to,” etc. Those skilled in the art will also further understand that if a specific quantity introduced in a claim has an explicit intent, that intent will be explicitly stated in the claim; if no such statement is made, then the intent does not exist. For example, to aid understanding, the following appended claims may contain the use of the introductory phrases “at least one” and “one or more” to introduce the claim recitation. However, the use of these phrases should not be construed as limiting any particular claim containing such a recitation to containing only one such recitation, even if the same claim contains the introductory phrases “one or more” or “at least one” and indefinite articles such as “one” or “one,” for example, “one” and / or “one” should be interpreted as “at least one” or “one or more”; the use of definite articles to introduce the claim recitation also applies. Furthermore, even if a specific quantity is explicitly stated in the claims, those skilled in the art will recognize that the statement should be interpreted as at least the stated quantity. For example, the phrase "two statements" alone, without any other modifiers, means at least two statements, or two or more statements. Additionally, when using conventions such as "at least one of A, B, and C," this structure is generally intended to be interpreted in the way that those skilled in the art would understand the convention. For example, "a system having at least one of A, B, and C" includes, but is not limited to, systems having only A, only B, only C, both A and B, both A and C, both B and C, and systems having both A, B, and C. When using conventions such as "at least one of A, B, and C," this structure is generally intended to be interpreted in the way that those skilled in the art would understand the convention. For example, "a system having at least one of A, B, and C" includes, but is not limited to, systems having only A, only B, only C, both A and B, both A and C, both B and C, and systems having both A, B, and C. Those skilled in the art will further understand that virtually any separable term and / or phrase presenting two or more alternative terms, whether in the specification, claims, or drawings, should be understood to include the possibility of including only one term, either one term, or both terms simultaneously. For example, the phrase "A or B" would be understood to include the possibility of including "A" or "B" or "A and B".

[0058] As can be understood from the foregoing, various embodiments of the invention have been described for illustrative purposes, and various modifications can be made without departing from the scope and spirit of the invention. Therefore, the various embodiments disclosed herein are not intended to be limiting, and the true scope and spirit are indicated by the following claims.

Claims

1. A method comprising: The user equipment (UE) processor receives a reconfiguration message with an addition or modification indication from the network; as well as The processor responds to the network by sending a reconfiguration complete message containing one or more Non-Access Stratum (NAS) messages.

2. The method according to claim 1, wherein, The instructions for adding or modifying include Protocol Data Unit (PDU) session modification commands.

3. The method according to claim 1, wherein, The instructions for adding or modifying include instructions for adding a Data Radio Bearer (DRB) and one or more NAS command messages to add one or more Quality of Service (QoS) streams.

4. The method according to claim 1, wherein, Responding via the reconfiguration complete message includes sending the reconfiguration complete message with a dedicated NAS message list information element (IE) to include the one or more NAS messages.

5. The method according to claim 1, wherein, Responding via the reconfiguration complete message includes sending the reconfiguration complete message along with the one or more NAS messages.

6. The method according to claim 1, wherein, This reconfiguration message includes a Radio Resource Control (RRC) reconfiguration message.

7. The method according to claim 6, wherein, The reconfiguration completion message includes the RRC reconfiguration completion message.

8. The method according to claim 7, wherein, The RRC reconfiguration complete message includes one or more NAS complete or accepted messages.

9. A method comprising: The processor of the network node sends a reconfiguration message with an indication of addition or modification to the user equipment (UE); as well as The processor receives a reconfiguration complete message from the UE containing one or more Non-Access Stratum (NAS) messages in response to sending the reconfiguration message.

10. The method according to claim 9, wherein, The instructions for adding or modifying include Protocol Data Unit (PDU) session modification commands.

11. The method according to claim 9, wherein, The instructions for adding or modifying include instructions for adding a Data Radio Bearer (DRB) and one or more NAS command messages to add one or more Quality of Service (QoS) streams.

12. The method according to claim 9, wherein, Receiving the reconfiguration complete message includes receiving the reconfiguration complete message with a dedicated NAS message list information element (IE) to include the one or more NAS messages.

13. The method according to claim 9, wherein, Receiving the reconfiguration complete message includes receiving the reconfiguration complete message along with the one or more NAS messages.

14. The method according to claim 9, wherein, This reconfiguration message includes a Radio Resource Control (RRC) reconfiguration message.

15. The method according to claim 14, wherein, The reconfiguration completion message includes the RRC reconfiguration completion message.

16. The method according to claim 15, wherein, The RRC reconfiguration complete message includes one or more NAS complete or accepted messages.

17. An apparatus that can be implemented in a user equipment (UE), comprising: A transceiver configured for wireless communication; as well as The processor coupled to the transceiver and configured to perform the following operations: This transceiver receives reconfiguration messages with addition or modification instructions from the network; and The transceiver responds to the network by sending a reconfiguration completion message containing one or more Non-Access Stratum (NAS) messages.

18. The apparatus according to claim 17, wherein, The addition or modification instructions include Protocol Data Unit (PDU) session modification commands for adding a Data Radio Bearer (DRB) and one or more NAS command messages to add one or more Quality of Service (QoS) streams.

19. The apparatus according to claim 17, wherein, Responding via the reconfiguration complete message includes sending the reconfiguration complete message with a dedicated NAS message list information element (IE) to include the one or more NAS messages.

20. The apparatus according to claim 17, wherein, Responding via the reconfiguration complete message includes sending the reconfiguration complete message along with the one or more NAS messages.

Images