Method and apparatus for requesting configuration update

Abstract

The present application provides a method and device for requesting configuration update, wherein the method for requesting configuration update comprises: sending, by a processor of a device, a request message to a network to request CUC information; receiving, by the processor, a CUC message including the CUC information from the network; and sending, by the processor, a configuration update completion message to the network. By using the present application, configuration update can be better requested.

Description

Technical Field

[0001] This invention relates generally to mobile communications, and more specifically, to requests for configuration updates by devices and network nodes in mobile communications. Background Technology

[0002] Unless otherwise stated, the methods described in this section are not considered prior art in the claims, nor are they considered prior art by virtue of their inclusion in this section.

[0003] Wireless communication systems can be widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems use multiple access technologies to support communication with multiple users by sharing available system resources. Examples of these multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0004] In traditional communication technologies, the configuration of User Equipment (UE) can be updated by the network at any time through the UE configuration update process. However, the UE is unaware of when the UE configuration update command can be sent, including the time zone or other relevant information such as the Regional Network Identifier Time Zone (NITZ) and Operational Name information. The UE may not know when the AMF command will arrive after the registration process. Therefore, the local time zone or network name may be incorrect for a period of time.

[0005] Accordingly, how to request configuration updates to obtain the correct information becomes an important issue in newly developed wireless communication networks. Therefore, an appropriate scheme needs to be provided for requesting configuration updates. Summary of the Invention

[0006] The following overview is illustrative only and is not intended to be limiting in any way. That is, it is provided to introduce the concept, key points, benefits, and advantages of the novel and non-obvious techniques described in this invention. Selected implementations are further described in the detailed description below. Therefore, the following overview is not intended to identify essential features of the claimed subject matter, nor is it intended to define the scope of the claimed subject matter.

[0007] This invention provides a method for requesting a configuration update, comprising: a processor of a device sending a request message to a network to request CUC information; the processor receiving a CUC message including the CUC information from the network; and the processor sending a configuration update completion message to the network.

[0008] This invention provides a method for requesting a configuration update, comprising: a network node receiving a request message for requesting configuration information (CUC) from a user equipment (UE); the network node sending a CUC message including the CUC information to the UE based on the request message; and the network node receiving a configuration update completion message from the UE.

[0009] This invention provides a device for requesting configuration updates, comprising: a transceiver that wirelessly communicates with a network during operation; and a processor communicatively coupled to the transceiver, such that during operation, the processor performs the following operations: sending a request message to the network via the transceiver to request CUC information; receiving a CUC message including the CUC information from the network via the transceiver; and sending a configuration update complete message to the network via the transceiver.

[0010] It is worth noting that while the descriptions provided herein can be used in the context of certain radio access technologies, networks, and network topologies, such as LTE, LTE Advanced, LTE Advanced Pro, 5G, NR, IoT, NB-IoT, IIoT, B5G, and 6G, the proposed concepts, schemes, and any variations / derivatives thereof can be implemented in, used in, and by other types of radio access technologies, networks, and network topologies. Therefore, the scope of the invention is not limited to the examples described herein. Attached Figure Description

[0011] The accompanying drawings contain information for a further understanding of the invention and are incorporated into and constitute a part of the invention. These drawings illustrate embodiments of the invention and, together with the description, serve to explain the principles of the invention. It is worth noting that the drawings are not necessarily drawn to scale, as some components may be shown out of proportion to their actual size in order to clearly illustrate the concepts of the invention.

[0012] Figure 1 This is an example scenario of a communication environment according to an embodiment of the present invention.

[0013] Figure 2 This is an example scenario of the request configuration for the first proposed scheme of sending a request message in the RM registration state according to an embodiment of the present invention.

[0014] Figure 3 This is an example scenario of request configuration for sending a request message in the RM deregistration state according to an embodiment of the present invention.

[0015] Figure 4 This is an example scenario of the payload container type IE according to an embodiment of the present invention.

[0016] Figure 5 This is an example scenario of requesting a CSC parameter container according to an embodiment of the present invention.

[0017] Figure 6 This is an example scenario of request configuration for a second proposed scheme of sending a request message in the RM registration state according to an embodiment of the present invention.

[0018] Figure 7 This is an example scenario of a configuration update request message according to an embodiment of the present invention.

[0019] Figure 8 This is an example scenario of requesting configuration update parameter information elements according to an embodiment of the present invention.

[0020] Figure 9 This is an example scenario of the request configuration update process according to an embodiment of the present invention.

[0021] Figure 10 This is an example communication system according to an embodiment of the present invention.

[0022] Figure 11 This is an example process according to an embodiment of the present invention.

[0023] Figure 12 This is an example process according to an embodiment of the present invention. Detailed Implementation

[0024] This invention discloses detailed embodiments and implementations of the claimed subject matter. However, it should be understood that the inventive embodiments and implementations are merely illustrative of the claimed subject matter, which can be implemented in various forms. Moreover, the invention can be implemented 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 to make the specification of this invention comprehensive and complete, and to fully convey the scope of the invention to those skilled in the art. In the following description, details of known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations.

[0025] Overview The embodiments of this invention relate to various techniques, methods, schemes, and / or solutions for requesting configuration updates. According to this invention, multiple possible solutions can be implemented individually or in combination. That is, although these possible solutions may be described individually below, two or more of these possible solutions may be implemented in a combination or other combined manner.

[0026] Figure 1This is an example scenario 100 of a communication environment according to an embodiment of the present invention. Scenario 100 involves UE 110 wirelessly communicating with network 120 (e.g., a wireless network including NTN and TN) via terrestrial network node 125 (e.g., an evolved Node B (eNB), a next-generation Node B (gNB), or a transmit / receive point (TRP)) and / or non-terrestrial network node 128 (e.g., a satellite). For example, terrestrial network node 125 and / or non-terrestrial network node 128 may form a non-terrestrial network (NTN) serving cell to wirelessly communicate with UE 110. In some embodiments, UE 110 may be an Internet of Things (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-enhanced (CE) UE). In such a communication environment, UE 110, network 120, terrestrial network node 125, and non-terrestrial network node 128 may implement various schemes of the improved request configuration update process according to the present invention as described below. It is worth noting that although various proposed solutions may be described individually or separately below, in practice, some or all of the proposed solutions may be used or implemented in combination. Of course, each proposed solution may be used or implemented individually or separately.

[0027] According to an embodiment of the present invention, a device (e.g., UE 110) may send a request message to a network (e.g., network 120) (or the network's Access and Mobility Management Function (AMF)) to request Configuration Update Command (CUC) information. The device may receive a CUC message (e.g., UE Configuration Update Command) containing CUC information from the network (or AMF). The device may then send a configuration update complete message (e.g., UE Configuration Complete) to the network (or AMF).

[0028] According to an embodiment of the invention, the request message can be sent in the RM-registered state, while the CUC message can be received in the Mobility Management (MM) registered state (e.g., 5GMM or 6GMM).

[0029] In the first proposal for sending a request message in RM registration status, the request message may include an uplink (UL) non-access stratum (NAS) transport message, and the UL NAS transport message may include a request list requesting Information Element Identifier (IEI) values ​​in the CUC parameter container (e.g., Figure 5 The table shown is shown. In one implementation, the payload container type information element (IE) (e.g., Figure 4The table shown may include a request CUC parameter container. Specifically, the device may send a list of request information in a payload container type set as a request CUC parameter container. The list of IEI value requests specified in the request CUC parameter container may be the same list of information assigned in a configuration update command of a network node (e.g., the network's AMF). If a network node (e.g., the network's AMF) receives a request CUC parameter container in the payload container IE of a UL NAS transmission message while in MM registration state, the network node (e.g., the network's AMF) may send a CUC message (e.g., a UE configuration update command) based on the UL NAS transmission message. That is, the CUC message (e.g., the UE configuration update command) may include the request information from the UL NAS transmission message.

[0030] Figure 2 This is an example scenario 200 of a request configuration for sending a request message in the RM registration state according to an embodiment of the present invention. Scenario 200 involves a device (e.g., UE) and a network node (e.g., a (macro / micro) base station), which can be an AMF of a wireless network (e.g., an LTE network, a 5G / NR network, an IoT network, or a 6G network). Reference Figure 2 In RM registration status, the device can send a UL NAS transport message with a request CUC parameter container. The AMF can then send a CUC message (e.g., a UE configuration update command) based on the UL NAS transport message. In other words, the AMF can resend the requested CUC to the device. The device can then send a configuration update complete message (e.g., UE configuration update complete) to the AMF.

[0031] Figure 3 This is an example scenario 300 of a request configuration for sending a request message in an RM-deregistered state, according to an embodiment of the present invention. Scenario 300 involves a device (e.g., a UE) and a network node (e.g., a (macro / micro) base station), which can be an AMF (Advanced Feature Function) of a wireless network (e.g., an LTE network, a 5G / NR network, an IoT network, or a 6G network). Reference Figure 3 In RM deregistration state, the device can send a registration request message (e.g., registration request or initial registration request) with a request CUC parameter container to the AMF. The AMF can then send a registration acceptance message (e.g., registration accepted) to the device. The device can then send a registration completion message (e.g., registration complete). In RM registration state, the AMF can send a CUC message (e.g., UE configuration update command) based on the registration request message. That is, the AMF can send a requested CUC to the device. The device can then send a configuration update completion message (e.g., UE configuration update complete) to the AMF.

[0032] Figure 4 This is an example scenario 400 of payload container type IE according to an embodiment of the present invention. (Reference) Figure 4 The payload container type IE can include the request CSC parameter container corresponding to the payload container type value (1 1 0 1).

[0033] Figure 5 This is an example scenario 500 of requesting a CSC parameter container according to an embodiment of the present invention. See also Figure 5 The request CSC parameter container can include the length of the request CUC parameter container, which is octet xi+1. The request CSC parameter container can also include the number of IEIs in the list (e.g., request IE 4, IE 3, IE 2, and IE 1 for octet xi+3, and request IE 7, IE 6, IE 5, and IE 4 for octet xi+4). The request CSC parameter container can also include the request IE for the CUC, which is octet y.

[0034] In the second proposed scenario where the request message is sent while the RM is registered, the request message may include a configuration update request message, and the configuration update request message may include a request list of IEI values ​​(e.g., Figure 8 (See the table shown). Specifically, the device can proactively send a configuration update request message (e.g., a UE configuration update request) to obtain information allocated in the configuration update command. The request list of IEI values ​​specified in the configuration update request can be the same list of information allocated in the configuration update command. If the network (e.g., the network's AMF) receives the configuration update request message in MM registration state, the network (e.g., the network's AMF) can send a CUC message (or a UE configuration update command) to the device based on the configuration update request. That is, the configuration update command can include the request information from the configuration update request message.

[0035] Figure 6 This is an example scenario 600 of a request configuration for a second proposal scheme in the RM registration state according to an embodiment of the present invention. Scenario 600 involves a device (e.g., UE) and a network node (e.g., a (macro / micro) base station), which can be an AMF of a wireless network (e.g., an LTE network, a 5G / NR network, an IoT network, or a 6G network). See also Figure 6In RM registration status, the device can send a configuration update request message (e.g., UE configuration update request) to the AMF. The AMF can then send a CUC message (e.g., UE configuration update command) based on the configuration update request message. In other words, the AMF can resend the requested CUC IE to the device. The device can then send a configuration update complete message (e.g., UE configuration update complete) to the AMF.

[0036] Figure 7 This is an example scenario 700 of a configuration update request message according to an embodiment of the present invention. See also Figure 7 The configuration update request message may include the content of the IEI, information elements (e.g., extended protocol discriminator, security header type, spare half-octet, configuration update request message identifier, request configuration update parameters), type / reference (e.g., extended protocol discriminator 9.2, security header type 9.3, spare half-octet 9.5, message type 9.7, request configuration update parameters 9.11.3 AB), presence (e.g., M), format (e.g., V and TLV), and length (e.g., 1, 1 / 2, 1 / 2, 1 and 3-n).

[0037] Figure 8 This is an example scenario 800 of requesting configuration update parameter information elements according to an embodiment of the present invention. See also Figure 8 The request configuration update parameter information element may include the request configuration update parameter IEI (byte 1). The request configuration update parameter information element may also include the length of the request configuration update parameter content (byte 2). The request configuration update parameter information element may also include the number of IEIs in the list (e.g., request IE 4, request IE 3, request IE 2, and request IE 1 (byte 3), and request IE 7, request IE 6, request IE 5, and request IE 4 (byte 4)). The request configuration update parameter information element may also include the request IE of CUC (byte n).

[0038] According to embodiments of the present invention, the request message can be sent in the RM deregistration state, and the CUC message can be received in the MM deregistration state. According to one embodiment of the present invention, the request message may include a registration request message (e.g., a registration request). The registration request message may include a request list of IEI values ​​requested in the CUC parameter container. Specifically, the device may proactively send a registration request message with a request for the CUC parameter container to obtain information allocated in the CUC message (e.g., a UE configuration update command). If the network (e.g., the network's AMF) receives the request for the CUC parameter container in the payload container IE of the registration request message in the MM deregistration state, the network (e.g., the network's AMF) may send a CUC message (e.g., a UE configuration update command) based on the registration request message. That is, the CUC message (e.g., a UE configuration update command) may include the request information from the registration request message.

[0039] Figure 9 This is an example scenario 900 of a request configuration update process according to an embodiment of the present invention. Scenario 900 involves a device (e.g., a UE) and a network node (e.g., a (macro / micro) base station), which may be an AMF (Advanced Configuration Function) of a wireless network (e.g., an LTE network, a 5G / NR network, an IoT network, or a 6G network). See also Figure 9 The UE can request configuration information (i.e., send a request message). In one embodiment, if the UE is in RM registration state, the UE can transmit (or send) a UL NAS transmission message to the AMF to request configuration information. That is, the value of "Request CUC Container IE" is true (i.e., "Request CUC Container IE" = true). The UE can then wait for a UE configuration update command from the AMF. Furthermore, the UE can send a configuration update completion message to the AMF.

[0040] See Figure 9 In another embodiment, if the UE is in RM registration state, the UE can transmit (or send) a UE configuration update request to the AMF to request configuration information. The UE can then wait for a UE configuration update command from the AMF. Furthermore, the UE can send a configuration update completion message to the AMF.

[0041] See Figure 9 In another embodiment, if the UE is in an RM deregistration state, the UE can transmit (or send) an initial registration request to the AMF to request configuration information. That is, the value of "Request CUC Container IE" is true (i.e., "Request CUC Container IE" = true). The UE can then wait for a UE configuration update command from the AMF. Furthermore, the UE can send a configuration update completion message to the AMF.

[0042] Illustrative Implementation Figure 10 This is an example communication system 1000 according to an embodiment of the present invention, including an example communication device 1010 and an example network device 1020. The communication device 1010 and the network device 1020 can perform various functions to implement the schemes, techniques, processes and methods related to requesting configuration updates described herein, including the above-described scenarios / schemes and processes 1000 and 1200 described below.

[0043] The communication device 1010 may be part of an electronic device, which may be a UE (User Equipment), such as a portable or mobile device, a wearable device, a wireless communication device, or a computing device. For example, the communication device 1010 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 notebook computer. The communication device 1010 may also be part of a machine-type device, which may be an IoT, NB-IoT, or IIoT device, such as a fixed or stationary device, a home device, a wired communication device, or a computing device. For example, the communication device 1010 may be implemented in a smart thermostat, smart refrigerator, smart door lock, wireless speaker, or home control center. Alternatively, the communication device 1010 may be implemented in the form of 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 Reduced Instruction Set Computing (RISC) processors, or one or more Complex Instruction Set Computing (CISC) processors. The communication device 1010 may include... Figure 3 At least some components are shown, such as processor 1012. Communication device 1010 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), however, these components of communication device 1010 are not shown in [the original text]. Figure 10 It is shown in the text and not described below, to keep it concise.

[0044] Network device 1020 may be part of an electronic device, which may be a network node, such as a satellite, base station, cell, router, or gateway for an IoT network. For example, network device 1020 may be implemented in an eNB / gNB / TRP in a satellite or 4G / 5G / B5G / 6G, NR, IoT, NB-IoT, or IIoT network. Alternatively, network device 1020 may be implemented as one or more IC chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, or one or more RISC or CISC processors. Network device 1020 may include... Figure 10At least some components are shown, such as processor 1022. Network device 1020 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), however, these components of network device 1020 are not shown in the present invention. Figure 10 It is shown in the text and not described below, to keep it concise.

[0045] In one aspect, processors 1012 and 1022 may be implemented as one or more single-core processors, one or more multi-core processors, or one or more Complex Instruction Set Computer (CISC) processors. That is, although the singular term "processor" is used to refer to processors 1012 and 1022, each of processors 1012 and 1022 may include multiple processors in some implementations of the invention, and may include a single processor in other implementations. In another aspect, each of processors 1012 and 1022 may be implemented in hardware (and optionally, firmware), including, 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, these components being configured and arranged to achieve a specific purpose of the invention. In other words, in at least some implementations, each of processors 1012 and 1022 is a dedicated machine specifically designed, arranged, and configured to perform a specific task, including configuration updates requested according to various implementations of the invention.

[0046] In some embodiments, communication device 1010 may further include a transceiver 1016 coupled to processor 1012, capable of wirelessly transmitting and receiving data. In some embodiments, transceiver 1016 is capable of wireless communication with wireless networks of different types of UEs and / or different Radio Access Technologies (RATs). In some embodiments, transceiver 1016 may be equipped with multiple antenna ports (not shown), such as four antenna ports. That is, transceiver 1016 may be equipped with multiple transmit antennas and multiple receive antennas for multiple-input multiple-output (MIMO) wireless communication. In some embodiments, network device 1020 may further include a transceiver 1026 coupled to processor 1022. Transceiver 1026 may include a transceiver capable of wirelessly transmitting and receiving data. In some embodiments, transceiver 1026 is capable of wireless communication with different types of UEs of different RATs. In some embodiments, transceiver 1026 may be equipped with multiple antenna ports (not shown), such as four antenna ports. That is, transceiver 1026 may be equipped with multiple transmit antennas and multiple receive antennas for MIMO wireless communication.

[0047] In some embodiments, the communication device 1010 may further include a memory 1014 coupled to the processor 1012, which can be accessed by the processor 1012 and stores data. In some embodiments, the network device 1020 may further include a memory 1024 coupled to the processor 1022, which can be accessed by the processor 1022 and stores data. Memory 1014 and memory 1024 may include a random access memory (RAM), such as dynamic RAM (DRAM), static RAM (SRAM), thyristor RAM (T-RAM), and / or zero-capacitance RAM (Z-RAM). Alternatively, memory 1014 and memory 1024 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, memory 1014 and memory 1024 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.

[0048] Each communication device 1010 and network device 1020 can be a communication entity capable of communicating with each other using various proposed schemes of the present invention. For illustrative purposes and without limitation, the capabilities of communication device 1010 as a UE and network device 1020 as a network node (e.g., TRP) are described below in conjunction with procedures 1100 and 1200.

[0049] Explanatory process Figure 11 This is an example process 1000 according to an embodiment of the present invention. Process 1000 may be part or all of the example implementation of the above-described scenario / scheme involving a request for configuration update of the present invention. Process 1000 may represent one aspect of the feature implementation of communication device 1010. Process 1000 may include one or more operations, actions, or functions shown by one or more of blocks 1110 to 1130. Although shown as discrete blocks, the individual blocks of process 1000 may be divided into more blocks, merged into fewer blocks, or eliminated according to the desired implementation. Furthermore, the blocks of process 1000 may be arranged according to Figure 11 The execution may be performed in the order shown, or in a different order. For illustrative purposes only and without limitation, process 1000 is described below in the context of communication device 1010. Process 1000 may begin with block 1110.

[0050] In block 1110, process 1100 may involve the processor 1012 of communication device 1010 sending a request message to the network via transceiver 1016 to request CUC information. Process 1100 can proceed from block 1110 to block 1120.

[0051] In block 1120, process 1100 may involve the processor 1012 of communication device 1010 receiving a CUC message including CUC information from the network via transceiver 1016. Process 1100 may proceed from block 1120 to block 1130.

[0052] In block 1130, process 1100 may involve the processor 1012 of communication device 1010 sending a configuration update completion message to the network via transceiver 1016.

[0053] In some embodiments, the request message can be sent in the RM registered state, and the CUC message can be received in the MM registered state.

[0054] In some embodiments, the request message may include a UL NAS transport message, and the UL NAS transport message may include a list of requests for IEI values ​​in the CUC parameter container.

[0055] In some embodiments, the payload container type IE may include a request CUC parameter container.

[0056] In some embodiments, the request message may include a configuration update request message, and the configuration update request message may include a request list of IEI values.

[0057] In some embodiments, the request message can be sent in the RM deregistered state, and the CUC message can be received in the MM deregistered state.

[0058] In some embodiments, the request message may include a registration request message, and the registration request message may include a list of requests for IEI values ​​in the CUC parameter container.

[0059] Figure 12 This is an example process 1200 according to an embodiment of the present invention. Process 1200 may be part or all of the example implementation of the above-described scenario / scheme involving a configuration update requested by the present invention. Process 1200 may represent one aspect of a feature implementation of network device 1020. Process 1200 may include one or more operations, actions, or functions shown by one or more of blocks 1210 to 1230. Although shown as discrete blocks, the individual blocks of process 1200 may be divided into more blocks, merged into fewer blocks, or omitted, depending on the desired implementation. Furthermore, the blocks of process 1200 may be arranged according to... Figure 12 The execution may be performed in the order shown, or in a different order. For illustrative purposes only and without limitation, process 1200 is described below in the context of network device 1020. Process 1200 may begin at block 1210.

[0060] In block 1210, process 1200 may involve the processor 1022 of network device 1020 receiving a request message requesting CUC information from the UE via transceiver 1026. Process 1200 can proceed from block 1210 to block 1220.

[0061] In block 1220, process 1200 may involve processor 1022 sending a CUC message including CUC information to the UE based on a request message via transceiver 1026. Process 1200 may proceed from block 1220 to block 1230.

[0062] In block 1230, process 1200 may involve processor 1022 receiving a configuration update complete message from UE via transceiver 1026.

[0063] In some embodiments, request messages can be received in the RM registration state, and CUC messages can be sent in the MM registration state.

[0064] In some embodiments, the request message may include a UL NAS transport message, and the UL NAS transport message may include a list of requests for IEI values ​​in the CUC parameter container.

[0065] In some embodiments, the payload container type IE may include a request CUC parameter container.

[0066] In some embodiments, the request message may include a configuration update request message, and the configuration update request message may include a request list of IEI values.

[0067] In some embodiments, the request message can be received in the RM deregistered state, and the CUC message can be sent in the MM deregistered state.

[0068] In some embodiments, the request message may include a registration request message, and the registration request message may include a list of requests for IEI values ​​in the CUC parameter container.

[0069] Additional Notes The subject matter described in this invention sometimes illustrates different components included within or connected to other components. However, it should be understood that these depicted architectures are merely examples, and many other architectures implementing the same functionality can actually be implemented. Conceptually, any arrangement of components implementing the same function is effectively “associated” to enable the desired functionality. Therefore, regardless of architecture or intermediate components, any two components combined in this invention to achieve a specific function can be considered “associated” with each other to enable the desired functionality. Similarly, any two such associated components can also be considered “operationally connected” or “operationally coupled” to each other to achieve the desired functionality, and any two components that can be suchly associated can also be considered “operationally coupled” to each other to achieve the desired functionality. Specific examples of operationally coupled components include, but are not limited to, physically mating and / or physically interacting components and / or wirelessly interacting components and / or logically interacting and / or logically interactable components.

[0070] Furthermore, regarding any plural and / or singular terms used substantially in this invention, those skilled in the art can convert them from plural to singular and / or from singular to plural as appropriate for the content and / or application. For clarity, various singular / plural substitutions may be explicitly stated in this invention.

[0071] Furthermore, those skilled in the art will understand that, generally, the terms used in this invention, and especially in the appended claims (e.g., the body of the appended claims), are generally meant as “open-ended” terms. For example, the term “comprising” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “at least having,” the term “comprising” should be interpreted as “including but not limited to,” and so on. Those skilled in the art will also understand that if a specific number of claims is intentionally listed, this intention will be explicitly listed in the claims, and the absence of such a listing will not indicate this intention. For example, to aid understanding, the appended claims may include the use of the introductory phrases “at least one” and “one or more.” However, the use of such phrases should not be construed as implying that the introduction of the indefinite article “a” or “an” limits any particular claim that includes such an introductory claim to only one embodiment of such a listing, even when the same claim includes the introductory phrases “one or more” or “at least one” and indefinite articles such as “a” or “an,” for example, “a and / or one” should be interpreted as meaning “at least one” or “one or more,” the same applies to the use of definite articles used to introduce claims. Furthermore, even when a specific number of the introduced claims are explicitly listed, those skilled in the art will recognize that such a listing should be interpreted as meaning at least the number listed. For example, in the absence of other modifiers, the basic listing of "two listings" means at least two listings or two or more listings. Additionally, when using conventions such as "at least one of A, B, and C," it generally means, in the sense that those skilled in the art will understand, that a system having at least one of A, B, and C will include, but is not limited to, systems having A alone, having B alone, having C alone, having A and B together, having A and C together, having B and C together, and / or having A, B, and C together. When using conventions such as "at least one of A, B, or C," it generally means, in the sense that those skilled in the art will understand, that a system having at least one of A, B, or C will include, but is not limited to, systems having A alone, having B alone, having C alone, having A and B together, having A and C together, having B and C together, and / or having A, B, and C together. Those skilled in the art will also understand that any transitional words and / or phrases in the specification, claims, or drawings that actually indicate two or more options should be understood to include the possibility of including one, any, or both of these items. For example, the phrase "A or B" will be understood to include the possibility of including "A" or "B" or "A and B".

[0072] As can be seen from the foregoing, it is understood that various embodiments of the present 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 in this invention are not intended to be limiting, and the true scope and spirit are determined by the appended claims.

Claims

1. A method for requesting configuration updates, comprising: The device's processor sends a request message to the network to request configuration update command (CUC) information; The processor receives a CUC message, including the CUC information, from the network; and The processor sends a configuration update completion message to the network.

2. The method for requesting configuration updates as described in claim 1, characterized in that, The request message is sent in the Registration Management (RM) registration state, and the CUC message is received in the Mobility Management (MM) registration state.

3. The method for requesting configuration updates as described in claim 2, characterized in that, The request message includes an uplink UL non-access stratum NAS transport message, and the UL NAS transport message includes a request list requesting the Information Element Identifier (IEI) values ​​in the CUC parameter container.

4. The method for requesting configuration updates as described in claim 3, characterized in that, The payload container type information element (IE) includes the request CUC parameter container.

5. The method for requesting configuration updates as described in claim 2, characterized in that, The request message includes a configuration update request message, which in turn includes a request list of IEI values.

6. The method for requesting configuration updates as described in claim 1, characterized in that, The request message is sent in the RM deregistered state, and the CUC message is received in the MM deregistered state.

7. The method for requesting configuration updates as described in claim 6, characterized in that, The request message includes a registration request message, which in turn includes a list of requests for IEI values ​​in the CUC parameter container.

8. A method for requesting a configuration update, comprising: The network node receives a request message from the user equipment (UE) requesting CUC information. The network node sends a CUC message, including the CUC information, to the UE based on the request message; as well as The network node receives the configuration update complete message from the UE.

9. The method for requesting configuration updates as described in claim 8, characterized in that, The request message is received in the RM registration state, and the CUC message is sent in the MM registration state.

10. The method for requesting configuration updates as described in claim 9, characterized in that, The request message includes a UL NAS transport message, which contains a list of requests for IEI values ​​in the CUC parameter container.

11. The method for requesting configuration updates as described in claim 10, characterized in that, The payload container type IE includes the request CUC parameter container.

12. The method for requesting configuration updates as described in claim 9, characterized in that, The request message includes a configuration update request message, which in turn includes a request list of IEI values.

13. The method for requesting configuration updates as described in claim 8, characterized in that, The request message is received in the RM deregistered state, and the CUC message is sent in the MM deregistered state.

14. The method for requesting configuration updates as described in claim 13, characterized in that, The request message includes a registration request message, which in turn includes a list of requests for IEI values ​​in the CUC parameter container.

15. A device for requesting configuration updates, comprising: A transceiver that communicates wirelessly with a network during operation; as well as A processor, communicatively coupled to the transceiver, enables the processor to perform the following operations during operation: The transceiver sends a request message to the network to request CUC information. Receives a CUC message containing the CUC information from the network via the transceiver; and The transceiver sends a configuration update completion message to the network.

16. The device as claimed in claim 15, characterized in that, The request message is sent while the RM is registered, and the CUC message is received while the MM is registered.

17. The device as claimed in claim 16, characterized in that, The request message includes a UL NAS transport message, which includes a request list of IEI values ​​in the CUC parameter container, and the payload container type IE includes the requested CUC parameter container.

18. The device as claimed in claim 16, characterized in that, The request message includes a configuration update request message, which in turn includes a request list of IEI values.

19. The device as claimed in claim 15, characterized in that, The request message is sent in the RM deregistered state, and the CUC message is received in the MM deregistered state.

20. The method for requesting configuration updates as described in claim 19, characterized in that, The request message includes a registration request message, which in turn includes a list of requests for IEI values ​​in the CUC parameter container.

Images