Multi-user communication in environmental IoT systems

Abstract

Techniques for enabling multi-user communication in Internet of Things (IoT) systems are described. An example wireless communication method includes network functions associated with network nodes and wireless devices performing at least one of the following functions: configuring and maintaining an interface with the network node; managing a registration process for the wireless device; managing connections between the network function and the wireless device; providing the network node with location-related information and services for the wireless device; managing connections between the wireless device and a server; providing authentication services, data security services, billing services, or group communication services for the wireless device; or maintaining information associated with the capabilities, identity, or location of the wireless device.

Description

Technical Field

[0001] This disclosure generally relates to digital wireless communications. Background Technology

[0002] Mobile telecommunications technologies are driving the world toward an increasingly connected and networked society. Compared to existing wireless networks, next-generation systems and wireless communication technologies will need to support a wider range of use case characteristics and provide more complex and granular access requirements and flexibility.

[0003] LTE (Long Term Evolution) is a wireless communication standard for mobile devices and data terminals developed by the 3rd Generation Partnership Project (3GPP). LTE Advanced (LTE-A) is a wireless communication standard that enhances the LTE standard. The fifth-generation wireless system (known as 5G) advances the LTE and LTE-A wireless standards and aims to support higher data rates, massive connectivity, ultra-low latency, high reliability, and other emerging service requirements. Summary of the Invention

[0004] Methods, systems, and devices for implementing multi-user communication in ambient Internet-of-Things (AIoT) systems are described. AIoT systems can be characterized by harsh communication environments, extremely small terminal form factors, and extremely low-cost IoT communication requirements. Embodiments of the disclosed technology provide functionalities and protocols for achieving robust and efficient multi-user communication in ambient IoT systems.

[0005] In one example, a network function associated with a network node and a wireless device performs at least one of the following functions: configuring and maintaining an interface with the network node; managing the registration process for the wireless device; managing the connection between the network function and the wireless device; providing the network node with location-related information and services for the wireless device; managing the connection between the wireless device and a server; providing authentication services, data security services, accounting services, or group communication services for the wireless device; or maintaining information associated with the capabilities, identity, or location of the wireless device.

[0006] In another example, the methods described above are embodied in processor-executable code and stored in a non-transitory computer-readable storage medium. When executed by a processor, the code included in the computer-readable storage medium causes the processor to implement the methods described in this patent document.

[0007] In yet another example, a device configured or operable to perform the methods described above is disclosed.

[0008] The above and other aspects, as well as their embodiments, are described in more detail in the accompanying drawings, specification, and claims. Attached Figure Description

[0009] Figure 1 and Figure 2 A timing diagram is shown for an example inventory or paging process.

[0010] Figures 3 to 10 A timing diagram for the example group communication process is shown.

[0011] Figure 11 A flowchart of an example wireless communication method is shown.

[0012] Figure 12 An example block diagram of a hardware platform that may be part of a network device or communication device is shown.

[0013] Figure 13 Examples of wireless communication including a base station (BS) and a user equipment (UE) based on some implementations of the disclosed technology are shown. Detailed Implementation

[0014] While existing Internet of Things (IoT) technologies, such as Machine Type Communication (MTC), Narrowband (NB)-IoT, and others, have enabled low-cost, low-power, and massive connectivity for IoT terminals, thus meeting the IoT communication needs in many scenarios, there are still many IoT scenarios where existing technologies cannot meet network communication requirements. These scenarios include harsh communication environments, extremely small terminal form factors, and extremely low-cost IoT communication needs.

[0015] Environmental IoT refers to a wireless communication system that includes a device that uses backscattering and environmental energy harvesting techniques to convert available signals and energy around the device into electrical energy capable of driving its own circuitry. Environmental IoT devices use a communication mode centered on backscattering to achieve transmission to target nodes. Furthermore, environmental IoT devices rely on energy harvesting as one of the key mechanisms for powering themselves and enabling the technology. Energy harvesting utilizes power from ambient radio waves to power tiny computing devices. This is very similar to how solar panels collect visible sunlight to power electrical equipment. Therefore, the most significant characteristics of environmental IoT are extremely low power consumption and low cost. The disclosed embodiments can be widely used in various IoT scenarios and represent a key communication technology for the future development of environmental IoT systems.

[0016] The example headings for the various sections below are intended to facilitate understanding of the disclosed subject matter and do not in any way limit the scope of the claimed subject matter. Therefore, one or more features of one example section may be combined with one or more features of another example section. Furthermore, for clarity, the terms 5G and Ambient IoT are used; however, the technologies disclosed in this document are not limited to 5G and Ambient IoT technologies and can be used in wireless systems implementing other protocols.

[0017] For example, the described embodiments and techniques are applied to backscatter communication, which utilizes reflected or backscattered signals to transmit data, wherein the backscattered signal can be a reflection of an ambient radio frequency (RF) signal, an RF signal from a dedicated carrier transmitter, or a signal photon in a non-classical quantum entangled pair, etc. For example, the system and implementation are described in “An Overview on Backscatter Communications” by Niu et al., IEEE Journal of Communications and Information Networks, Vol. 4, No. 2 (2019). In this context, the disclosed embodiments provide various features and aspects of wireless devices operating in an Ambient IoT system (referred to as Ambient IoT (AIoT) User Equipment (UE), or simply UE).

[0018] In the described embodiments, network management functions configured to support multi-user (MU) communication in an IoT system are further detailed through various examples and aspects. As will be described, this network management function can be a new network function or an existing network function, such as a Network Exposure Function (NEF), which has been configured to support AIoT system communication for multiple users. Such a network management function (or simply network function) supporting MU AIoT is referred to as "MF" and, in the examples, is formed by a combination of small software code snippets called microservices, which are configured to provide their services to other NFs via an application programming interface (API).

[0019] Example 1 (Functional Example)

[0020] In some embodiments, in the core network (CN), a network management function, represented as MF, is configured to support environmental IoT functionality. This MF can be a NEF, a different existing network function (NF), or a new network function. An MF, which can be implemented based on the described embodiments, supports one or more of the following functionalities:

[0021] - Termination of the Radio Access Network (RAN) Control Plane (CP) interface for AIoT, where the RAN can connect to the MF via the interface, and the MF supports the transmission of interface messages and the management of the interface, such as establishment, release and modification operations.

[0022] - For AIoT registration management, AIoT UEs that need to register or update their registration can connect to MF to receive the services that need to be registered.

[0023] - Connectivity management for AIoT includes the ability to establish and release control plane (CP) signaling connections between the AIoT UE and the MF.

[0024] - For AIoT reachability management, the MF (Member Provider) is responsible for detecting whether an AIoT UE is reachable and providing the network with the AIoT UE's location (e.g., access node) to reach the AIoT UE. Furthermore, the MF can trigger an inventory process to detect the AIoT UE's location.

[0025] - Provides the transmission of AIoT messages between the UE and the server by delivering messages between the server and the AIoT UE.

[0026] - Access authentication for AIoT is based on subscriptions (such as Operator-Determined Barring (ODB), UE type, access type, and currently used RAT type) and determines whether the AIoT UE is allowed to access.

[0027] - Security for AIoT includes ciphertext and integrity protection for messages and data.

[0028] - Support for billing.

[0029] - Group communication with AIoT UEs, which includes the network communicating with a group of AIoT UEs simultaneously.

[0030] - Maintain location information about AIoT UEs, such as AMF address, gNB address, and area addresses accessed by the UE.

[0031] - Maintain information about AIoT UEs, such as UE identifiers, UE capabilities, etc.

[0032] - Maintain the status of the terminal, such as whether the terminal has been stored in memory, whether the terminal has completed the access process, etc.

[0033] Example 2 (Inventory Process Example)

[0034] In some embodiments, MF triggers an example inventory or paging process, such as Figure 1 As shown. In this example, the inventory or paging process includes the following steps.

[0035] Step 1. The MF triggers an inventory or paging process. The MF transmits a message to the Access and Mobility Management Function (AMF) carrying one or more of the following: a list of UE IDs (e.g., a list of UE IDs with the same group ID within the UE list or associated with location information), a group ID (e.g., associated with multiple AIoT UEs), UE capabilities (e.g., UE type, supported physical technologies, supported communication times, etc.), access formation information (e.g., identity or address associated with one or more gNBs, one or more AMFs, one or more tracking areas, one or more physical areas, etc.), or an AIoT indication (e.g., indicating that a particular communication is an AIoT communication).

[0036] Step 2. AMF triggers an inventory or paging process for the base station (e.g., NB). Here, the inventory or paging message carries one or more of the following: selected UE information (e.g., a list of UE IDs), group ID (e.g., a group ID may be associated with multiple AIoT UEs), or AIoT indication (e.g., indicating that a particular communication is AIoT communication).

[0037] Step 3. The base station (NB) triggers an inventory or paging process.

[0038] Step 4. The UE sends its UE ID back to the NB. In the example, the UE can be the selected UE for a paging or inventory process, in which case the UE will successfully complete the paging or inventory process. Alternatively, the UE may simply send its UE ID to the NB in ​​its response if it is not the selected UE for a paging or inventory process.

[0039] Step 5. The NB reports the UE ID (or a list of UE IDs) to the AMF. In some cases, the NB can collect information for multiple UEs before reporting information to the AMF in a single instance.

[0040] Step 6. The AMF sends a message to the MF, which includes a group ID (e.g., associated with multiple AIoT UEs) and / or a list of UEs (e.g., a list of UE IDs, or a portion of a UE ID).

[0041] In some embodiments, MF triggers an example inventory or paging process, such as Figure 2 As shown. In this example, the inventory or paging process includes the following steps.

[0042] Step 1. The MF triggers an inventory or paging process. The MF transmits a message to the base station (NB) carrying one or more of the following: a list of UE IDs (e.g., a list of UE IDs with the same group ID that are within the UE list or associated with location information), a group ID (e.g., associated with multiple AIoT UEs), or an AIoT indication (e.g., indicating that a particular communication is an AIoT communication).

[0043] Step 2. The base station (NB) triggers an inventory or paging process.

[0044] Step 3. The UE sends its UE ID back to the NB. In the example, the UE can be the selected UE for a paging or inventory process, in which case the UE will successfully complete the paging or inventory process. Alternatively, the UE may simply send its UE ID to the NB in ​​its response if it is not the selected UE for a paging or inventory process.

[0045] Step 4. The NB feeds back the UE ID (or a list of UE IDs) to the MF. In some cases, the NB may collect this information for multiple UEs before feeding it back to the MF in a single instance. The message fed back may include a group ID (e.g., associated with multiple AIoT UEs) and / or a list of UEs (e.g., a list of UE IDs, or a portion of a UE ID).

[0046] Example 3 (Group Communication Example)

[0047] In some embodiments, it provides Figure 3 The example group communication procedure is shown. In this example, the group communication procedure includes the following steps.

[0048] Step 1. The Application Function (AF) or the server sends a request message to the MF. This message carries one or more of the following: a group ID (e.g., associated with multiple AIoT UEs, and the MF can use the same group ID to communicate with each of the multiple AIoT UEs), a list of UEs (e.g., a list of UE IDs, or portions of UE IDs), location information (e.g., an identity or address associated with one or more gNBs, one or more AMFs, one or more tracking areas, one or more physical areas, etc.), data or a list of data (e.g., one or more application layer messages), or an AIoT indication (e.g., indicating that a particular communication is an AIoT communication).

[0049] Step 2. The MF sends a request message to the Unified Data Management (UDM) (this request message is requesting UE information). Here, the request message carries one or more of the following: a group ID (e.g., associated with multiple AIoT UEs, and the MF can use the same group ID to communicate with each of the multiple AIoT UEs), a UE list (e.g., a list of UE IDs, or a portion of UE IDs), location information (e.g., an identity or address associated with one or more gNBs, one or more AMFs, one or more tracking areas, one or more physical areas, etc.), or an AIoT indication (e.g., indicating that a particular communication is an AIoT communication).

[0050] Step 3. The UDM sends a response message back to the MF, which includes UE information, including a list of UE IDs (e.g., a list or portion of UE IDs that are within the same group ID and associated with location information), UE capability information (e.g., UE type, supported physical technologies, supported communication times, etc.), and access formation information (e.g., identity or address associated with one or more gNBs, one or more AMFs, etc.).

[0051] Step 4. The MF is configured to locate the corresponding AMF based on information from the UDM and deliver a message to it. This message includes a list of UE IDs (e.g., a list of UE IDs with the same group ID within the UE list or related to location information), a group ID (e.g., associated with multiple AIoT UEs), UE capabilities (e.g., UE type, supported physical technologies, supported communication times, etc.), access formation information (e.g., identity or address associated with one or more gNBs or one or more AMFs), data or a data list (e.g., one or more application layer messages), or an AIoT indication (e.g., indicating that a particular communication is an AIoT communication).

[0052] Step 5. The AMF triggers an inventory or paging process for the NB. Here, the inventory or paging message carries one or more of the following: selected UE information (e.g., a list of UE IDs), group ID (e.g., a group ID may be associated with multiple AIoT UEs), or AIoT indication (e.g., indicating that a particular communication is an AIoT communication).

[0053] Step 6. The base station (NB) triggers an inventory or paging process.

[0054] Step 7. The UE sends its UE ID back to the NB. In the example, the UE can be the selected UE for a paging or inventory process, in which case the UE will successfully complete the paging or inventory process. Alternatively, the UE may simply send its UE ID to the NB in ​​its response if it is not the selected UE for a paging or inventory process.

[0055] Step 8. The NB reports the UE ID (or a list of UE IDs) to the AMF. In some cases, the NB may collect this information for multiple UEs before reporting it to the AMF in a single instance.

[0056] Step 9. The AMF transmits data to the NB. For example, based on data from the MF, the AMF generates a NAS PDU for the UE (or a list of NAS PDUs for multiple UEs) and transmits it to the NB via an NG message. Here, each NAS PDU corresponds to a UE.

[0057] Step 10. The NB transmits data to the UE. This data can be a NAS PDU.

[0058] Step 11. The UE transmits data to the NB. This data can be a NAS PDU.

[0059] Step 12. The NB transmits this data to the AMF. In some cases, the NB can collect NAS PDU information for multiple UEs before feeding back information to the AMF in a single instance.

[0060] Step 13. The AMF, based on the data from the NB, passes the data to the MF. The AMF is configured to pass data for one UE from a list of multiple UEs to the MF, where each NAS PDU corresponds to a single UE.

[0061] Step 14. The MF sends a response message to the AF or the server, wherein the message carries one or more of the following: group ID (e.g., associated with multiple AIoT UEs), UE list (e.g., a list of UE IDs, or a portion of UE IDs), data (e.g., application layer messages), or a list of data (e.g., each data item is an application layer message associated with a UE list or group ID).

[0062] In some embodiments, the MF can maintain information about the AIoT UE, such as Figure 4 As shown, the maintenance information includes the following steps.

[0063] Step 1. The Application Function (AF) or the server sends a request message to the MF. This message carries one or more of the following: a group ID (e.g., associated with multiple AIoT UEs, and the MF can use the same group ID to communicate with each of the multiple AIoT UEs), a list of UEs (e.g., a list of UE IDs, or portions of UE IDs), location information (e.g., an identity or address associated with one or more gNBs, one or more AMFs, one or more tracking areas, one or more physical areas, etc.), data or a list of data (e.g., one or more application layer messages), or an AIoT indication (e.g., indicating that a particular communication is an AIoT communication).

[0064] Step 2. The MF is configured to locate the corresponding AMF based on the information stored in the MF and deliver a message to it. This message includes a list of UE IDs (e.g., a list of UE IDs with the same group ID within the UE list or related to location information), a group ID (e.g., associated with multiple AIoT UEs), UE capabilities (e.g., UE type, supported physical technologies, supported communication times, etc.), data or a list of data (e.g., one or more application layer messages), or an AIoT indication (e.g., indicating that a particular communication is an AIoT communication).

[0065] Step 3. The AMF triggers an inventory or paging process for the NB. Here, the inventory or paging message carries one or more of the following: selected UE information (e.g., a list of UE IDs), group ID (e.g., a group ID may be associated with multiple AIoT UEs), or AIoT indication (e.g., indicating that a particular communication is an AIoT communication).

[0066] Step 4. The base station (NB) triggers an inventory or paging process.

[0067] Step 5. The UE sends its UE ID back to the NB. In the example, the UE can be the selected UE for a paging or inventory process, in which case the UE will successfully complete the paging or inventory process. Alternatively, the UE may simply send its UE ID to the NB in ​​its response if it is not the selected UE for a paging or inventory process.

[0068] Step 6. The NB reports the UE ID (or a list of UE IDs) to the AMF. In some cases, the NB may collect this information for multiple UEs before reporting it to the AMF in a single instance.

[0069] Step 7. The AMF transmits data to the NB. For example, based on data from the MF, the AMF generates a NAS PDU for the UE (or a list of NAS PDUs for multiple UEs) and transmits it to the NB via an NG message. Here, each NAS PDU corresponds to a UE.

[0070] Step 8. The NB transmits data to the UE. This data can be a NAS PDU.

[0071] Step 9. The UE transmits data to the NB. This data can be a NAS PDU.

[0072] Step 10. The NB transmits this data to the AMF. In some cases, the NB can collect NAS PDU information for multiple UEs before feeding back information to the AMF in a single instance.

[0073] Step 11. The AMF, based on the data from the NB, passes the data to the MF. The AMF is configured to pass data for one UE from a list of multiple UEs to the MF, where each NAS PDU corresponds to a single UE.

[0074] Step 12. The MF sends a response message to the AF or the server, wherein the message carries one or more of the following: a group ID (e.g., associated with multiple AIoT UEs), a list of UEs (e.g., a list of UE IDs, or a portion of a UE ID), data (e.g., an application layer message), or a list of data (e.g., each data item is an application layer message associated with a list of UEs or a group ID).

[0075] In some embodiments, the MF can maintain information about the AIoT UE and has termination for the RAN CP interface for AIoT, such as... Figure 5 As shown. The maintenance information, and the RAN CP interface termination, includes the following steps.

[0076] Step 1. The Application Function (AF) or the server sends a request message to the MF. This message carries one or more of the following: a group ID (e.g., associated with multiple AIoT UEs, and the MF can use the same group ID to communicate with each of the multiple AIoT UEs), a list of UEs (e.g., a list of UE IDs, or portions of UE IDs), location information (e.g., an identity or address associated with one or more gNBs, one or more AMFs, one or more tracking areas, one or more physical areas, etc.), data or a list of data (e.g., one or more application layer messages), or an AIoT indication (e.g., indicating that a particular communication is an AIoT communication).

[0077] Step 2. The MF triggers a paging or inventory process. The MF is configured to locate the appropriate NB based on information stored in the MF and deliver a paging or inventory message to it. The paging or inventory message carries one or more of the following: selected UE information (e.g., a list of UE IDs), a group ID (e.g., a group ID may be associated with multiple AIoT UEs), or an AIoT indication (e.g., indicating that a particular communication is AIoT communication).

[0078] Step 3. The base station (NB) triggers an inventory or paging process.

[0079] Step 4. The UE sends its UE ID back to the NB. In the example, the UE can be the selected UE for a paging or inventory process, in which case the UE will successfully complete the paging or inventory process. Alternatively, the UE may simply send its UE ID to the NB in ​​its response if it is not the selected UE for a paging or inventory process.

[0080] Step 5. The NB reports the UE ID (or a list of UE IDs) to the MF. In some cases, the NB may collect this information for multiple UEs before reporting it to the MF in a single instance.

[0081] Step 6. The MF transmits data to the NB. For example, the MF generates a NAS PDU for the UE (or a list of NAS PDUs for multiple UEs) and transmits it to the NB via a message. Here, each NAS PDU corresponds to a UE.

[0082] Step 7. The NB transmits data to the UE. This data can be a NAS PDU.

[0083] Step 8. The UE transmits data to the NB. This data can be a NAS PDU.

[0084] Step 9. The NB transmits this data to the MF. In some cases, the NB can collect NAS PDU information for multiple UEs before feeding back information to the MF in a single instance.

[0085] Step 10. The MF sends a response message to the AF or the server, wherein the message carries one or more of the following: group ID (e.g., associated with multiple AIoT UEs), UE list (e.g., a list of UE IDs, or a portion of UE IDs), data (e.g., application layer messages), or a list of data (e.g., each data item is an application layer message associated with a UE list or group ID).

[0086] In some embodiments, it provides Figure 6 Another example group communication procedure is shown. In this example, the group communication procedure includes the following steps.

[0087] Step 1. The Application Function (AF) or the server sends a request message to the MF. This message carries one or more of the following: a group ID (e.g., associated with multiple AIoT UEs, and the MF can use the same group ID to communicate with each of the multiple AIoT UEs), a list of UEs (e.g., a list of UE IDs, or portions of UE IDs), location information (e.g., an identity or address associated with one or more gNBs, one or more AMFs, one or more tracking areas, one or more physical areas, etc.), data or a list of data (e.g., one or more application layer messages), or an AIoT indication (e.g., indicating that a particular communication is an AIoT communication).

[0088] Step 2. The MF sends a request message to the Unified Data Management (UDM) (this request message requests UE information). Here, the request message carries one or more of the following: a group ID (e.g., associated with multiple AIoT UEs, and the MF can use the same group ID to communicate with each of the multiple AIoT UEs), a UE list (e.g., a list of UE IDs, or a portion of UE IDs), location information (e.g., an identity or address associated with one or more gNBs, one or more AMFs, one or more tracking areas, one or more physical areas, etc.), or an AIoT indication (e.g., indicating that a particular communication is an AIoT communication).

[0089] Step 3. The UDM sends a response message back to the MF, which includes UE information, including a list of UE IDs (e.g., a list or portion of UE IDs that are within the same group ID and associated with location information), UE capability information (e.g., UE type, supported physical technologies, supported communication times, etc.), and access formation information (e.g., identity or address associated with one or more gNBs, one or more AMFs, etc.).

[0090] Step 4. The MF is configured to locate the appropriate AMF and deliver a paging or inventory message to it. The paging or inventory message carries one or more of the following: selected UE information (e.g., a list of UE IDs), group ID (e.g., a group ID may be associated with multiple AIoT UEs), AIoT indication (e.g., indicating that a particular communication is AIoT communication), or access formation information (e.g., identity or address associated with one or more gNBs, one or more AMFs, etc.).

[0091] Step 5. The AMF triggers an inventory or paging process for the NB. Here, the inventory or paging message carries one or more of the following: selected UE information (e.g., a list of UE IDs), group ID (e.g., a group ID may be associated with multiple AIoT UEs), or AIoT indication (e.g., indicating that a particular communication is an AIoT communication).

[0092] Step 6. The base station (NB) triggers an inventory or paging process.

[0093] Step 7. The UE sends its UE ID back to the NB. In the example, the UE can be the selected UE for a paging or inventory process, in which case the UE will successfully complete the paging or inventory process. Alternatively, the UE may simply send its UE ID to the NB in ​​its response if it is not the selected UE for a paging or inventory process.

[0094] Step 8. The NB reports the UE ID (or a list of UE IDs) to the AMF. In some cases, the NB may collect this information for multiple UEs before reporting it to the AMF in a single instance.

[0095] Step 9. The AMF sends the UE ID (or a list of UE IDs) back to the MF.

[0096] Step 10. The MF transmits a message to the AMF, and the message carries one or more of the following: a list of UE IDs (e.g., a list of UE IDs with the same group ID within the UE list or related to location information), a group ID (e.g., associated with multiple AIoT UEs), UE capabilities (e.g., UE type, supported physical technologies, supported communication times, etc.), access formation information (e.g., identity or address associated with one or more gNBs, one or more AMFs, one or more tracking areas, one or more physical areas, etc.), data or a list of data (e.g., one or more application layer messages), or an AIoT indication (e.g., indicating that a particular communication is an AIoT communication).

[0097] Step 11. The AMF transmits data to the NB. For example, based on data from the MF, the AMF generates a NAS PDU for the UE (or a list of NAS PDUs for multiple UEs) and transmits it to the NB via an NG message. Here, each NAS PDU corresponds to a UE.

[0098] Step 12. The NB transmits data to the UE. This data can be a NAS PDU.

[0099] Step 13. The UE transmits data to the NB. This data can be a NAS PDU.

[0100] Step 14. The NB transmits this data to the AMF. In some cases, the NB can collect NAS PDU information for multiple UEs before feeding back information to the AMF in a single instance.

[0101] Step 15. The AMF, based on the data from the NB, passes the data to the MF. The AMF is configured to pass data for one UE from a list of multiple UEs to the MF, where each NAS PDU corresponds to a single UE.

[0102] Step 16. The MF sends a response message to the AF or the server, wherein the message carries one or more of the following: group ID (e.g., associated with multiple AIoT UEs), UE list (e.g., a list of UE IDs, or a portion of UE IDs), data (e.g., application layer messages), or a list of data (e.g., each data item is an application layer message associated with a UE list or group ID).

[0103] In some embodiments, the MF can maintain information about the AIoT UE, such as Figure 7 As shown, the maintenance information includes the following steps.

[0104] Step 1. The Application Function (AF) or the server sends a request message to the MF. This message carries one or more of the following: a group ID (e.g., associated with multiple AIoT UEs, and the MF can use the same group ID to communicate with each of the multiple AIoT UEs), a list of UEs (e.g., a list of UE IDs, or portions of UE IDs), location information (e.g., an identity or address associated with one or more gNBs, one or more AMFs, one or more tracking areas, one or more physical areas, etc.), data or a list of data (e.g., one or more application layer messages), or an AIoT indication (e.g., indicating that a particular communication is an AIoT communication).

[0105] Step 2. The MF is configured to locate the corresponding AMF based on the information stored in the MF and deliver a paging or inventory message to it. The paging or inventory message carries one or more of the following: selected UE information (e.g., a list of UE IDs), group ID (e.g., a group ID may be associated with multiple AIoT UEs), AIoT indication (e.g., indicating that a particular communication is AIoT communication), or access formation information (e.g., identity or address associated with one or more gNBs, one or more AMFs, etc.).

[0106] Step 3. The AMF triggers an inventory or paging process for the NB. Here, the inventory or paging message carries one or more of the following: selected UE information (e.g., a list of UE IDs), group ID (e.g., a group ID may be associated with multiple AIoT UEs), or AIoT indication (e.g., indicating that a particular communication is an AIoT communication).

[0107] Step 4. The base station (NB) triggers an inventory or paging process.

[0108] Step 5. The UE sends its UE ID back to the NB. In the example, the UE can be the selected UE for a paging or inventory process, in which case the UE will successfully complete the paging or inventory process. Alternatively, the UE may simply send its UE ID to the NB in ​​its response if it is not the selected UE for a paging or inventory process.

[0109] Step 6. The NB reports the UE ID (or a list of UE IDs) to the AMF. In some cases, the NB may collect this information for multiple UEs before reporting it to the AMF in a single instance.

[0110] Step 7. AMF sends the UE ID (or a list of UE IDs) back to MF.

[0111] Step 8. The MF transmits a message to the AMF, and the message carries one or more of the following: a list of UE IDs (e.g., a list of UE IDs with the same group ID within the UE list or related to location information), a group ID (e.g., associated with multiple AIoT UEs), UE capabilities (e.g., UE type, supported physical technologies, supported communication times, etc.), access formation information (e.g., identity or address associated with one or more gNBs, one or more AMFs, one or more tracking areas, one or more physical areas, etc.), data or a list of data (e.g., one or more application layer messages), or an AIoT indication (e.g., indicating that a particular communication is an AIoT communication).

[0112] Step 9. The AMF transmits data to the NB. For example, based on data from the MF, the AMF generates a NAS PDU for the UE (or a list of NAS PDUs for multiple UEs) and transmits it to the NB via an NG message. Here, each NAS PDU corresponds to a UE.

[0113] Step 10. The NB transmits data to the UE. This data can be a NAS PDU.

[0114] Step 11. The UE transmits data to the NB. This data can be a NAS PDU.

[0115] Step 12. The NB transmits this data to the AMF. In some cases, the NB can collect NAS PDU information for multiple UEs before feeding back information to the AMF in a single instance.

[0116] Step 13. The AMF, based on the data from the NB, passes the data to the MF. The AMF is configured to pass data for one UE from a list of multiple UEs to the MF, where each NAS PDU corresponds to a single UE.

[0117] Step 14. The MF sends a response message to the AF or the server, wherein the message carries one or more of the following: group ID (e.g., associated with multiple AIoT UEs), UE list (e.g., a list of UE IDs, or a portion of UE IDs), data (e.g., application layer messages), or a list of data (e.g., each data item is an application layer message associated with a UE list or group ID).

[0118] Example 4 (Group Communication Example)

[0119] In some embodiments, it provides Figure 8 This is yet another example of a group communication procedure. In this example, the group communication procedure includes the following steps.

[0120] Step 1. The Application Function (AF) or the server sends a request message to the MF. This message carries one or more of the following: a group ID (e.g., associated with multiple AIoT UEs, and the MF can use the same group ID to communicate with each of the multiple AIoT UEs), a list of UEs (e.g., a list of UE IDs, or portions of UE IDs), location information (e.g., an identity or address associated with one or more gNBs, one or more AMFs, one or more tracking areas, one or more physical areas, etc.), data or a list of data (e.g., one or more application layer messages), or an AIoT indication (e.g., indicating that a particular communication is an AIoT communication).

[0121] Step 2. The MF sends a request message to the Unified Data Management (UDM) (this request message is requesting UE information). Here, the request message carries one or more of the following: a group ID (e.g., associated with multiple AIoT UEs, and the MF can use the same group ID to communicate with each of the multiple AIoT UEs), a UE list (e.g., a list of UE IDs, or a portion of UE IDs), location information (e.g., an identity or address associated with one or more gNBs, one or more AMFs, one or more tracking areas, one or more physical areas, etc.), or an AIoT indication (e.g., indicating that a particular communication is an AIoT communication).

[0122] Step 3. The UDM sends a response message back to the MF, which includes UE information, including a list of UE IDs (e.g., a list or portion of UE IDs that are within the same group ID and associated with location information), UE capability information (e.g., UE type, supported physical technologies, supported communication times, etc.), and access formation information (e.g., identity or address associated with one or more gNBs, one or more AMFs, etc.).

[0123] Step 4. The MF is configured to locate the corresponding AMF based on information from the UDM and deliver a message to it. This message includes a list of UE IDs (e.g., a list of UE IDs with the same group ID within the UE list or related to location information), a group ID (e.g., associated with multiple AIoT UEs), UE capabilities (e.g., UE type, supported physical technologies, supported communication times, etc.), access formation information (e.g., identity or address associated with one or more gNBs, one or more AMFs, etc.), data (e.g., application layer messages), or an AIoT indication (e.g., indicating that a particular communication is an AIoT communication).

[0124] Step 5. The AMF triggers an inventory or paging process for the NB. Here, the inventory or paging message carries one or more of the following: selected UE information (e.g., a list of UE IDs), group ID (e.g., a group ID may be associated with multiple AIoT UEs), data (e.g., a NAS PDU, which may be delivered to the UE that matches the selected UE information), or an AIoT indication (e.g., indicating that a particular communication is an AIoT communication).

[0125] Step 6. The base station (NB) triggers an inventory or paging process. The inventory or paging message includes a NAS PDU, which can be delivered to the UE that matches the selected UE information.

[0126] Step 7. The UE transmits data to the NB. This data can be a NAS PDU.

[0127] Step 8. The NB transmits this data to the AMF. In some cases, the NB can collect NAS PDU information for multiple UEs before feeding back information to the AMF in a single instance.

[0128] Step 9. The AMF, based on the data from the NB, passes the data to the MF. The AMF is configured to pass data for one UE from a list of multiple UEs to the MF, where each NAS PDU corresponds to a single UE.

[0129] Step 10. The MF sends a response message to the AF or the server, wherein the message carries one or more of the following: group ID (e.g., associated with multiple AIoT UEs), UE list (e.g., a list of UE IDs, or a portion of UE IDs), data (e.g., application layer messages), or a list of data (e.g., each data item is an application layer message associated with a UE list or group ID).

[0130] In some embodiments, the MF can maintain information about the AIoT UE, such as Figure 9 As shown, the maintenance information includes the following steps.

[0131] Step 1. The Application Function (AF) or server sends a request message to the MF. This message carries one or more of the following: a group ID (e.g., associated with multiple AIoT UEs, and the MF can use the same group ID to communicate with each of the multiple AIoT UEs), a UE list (e.g., a list of UE IDs, or portions of UE IDs), location information (e.g., an identity or address associated with one or more gNBs, one or more AMFs, one or more tracking areas, one or more physical areas, etc.), data (e.g., an application layer message that can be delivered to one or more UEs based on the group ID, UE list, and / or location information), or an AIoT indication (e.g., indicating that a particular communication is an AIoT communication).

[0132] Step 2. The MF is configured to locate the corresponding AMF based on the information stored in the MF and deliver a message to it. This message includes a list of UE IDs (e.g., a list of UE IDs with the same group ID within the UE list or related to location information), a group ID (e.g., associated with multiple AIoT UEs), UE capabilities (e.g., UE type, supported physical technologies, supported communication times, etc.), data (e.g., application layer messages that can be delivered to one or more UEs based on the group ID, UE list, and / or location information), or an AIoT indication (e.g., indicating that a particular communication is an AIoT communication).

[0133] Step 3. The AMF triggers an inventory or paging procedure for the NB. Here, the inventory or paging message carries one or more of the following: selected UE information (e.g., a list of UE IDs), group ID (e.g., a group ID may be associated with multiple AIoT UEs), data (e.g., data that may be delivered to the NAS PDU of the UE that matches the selected UE information), or an AIoT indication (e.g., indicating that a particular communication is an AIoT communication).

[0134] Step 4. The base station (NB) triggers an inventory or paging procedure. The inventory or paging message carries a NAS PDU, and the NB is configured to deliver it to the UE that matches the selected UE information.

[0135] Step 5. The UE transmits data to the NB. This data can be a NAS PDU.

[0136] Step 6. The NB transmits this data to the AMF. In some cases, the NB can collect NAS PDU information for multiple UEs before feeding back information to the AMF in a single instance.

[0137] Step 7. The AMF, based on the data from the NB, passes the data to the MF. The AMF is configured to pass data for one UE from a list of multiple UEs to the MF, where each NAS PDU corresponds to a single UE.

[0138] Step 8. The MF sends a response message to the AF or the server, wherein the message carries one or more of the following: group ID (e.g., associated with multiple AIoT UEs), UE list (e.g., a list of UE IDs, or a portion of UE IDs), data (e.g., application layer messages), or a list of data (e.g., each data item is an application layer message associated with a UE list or group ID).

[0139] In some embodiments, the MF can maintain information about the AIoT UE and has termination for the RAN CP interface for AIoT, such as... Figure 10 As shown. The maintenance information, and the RAN CP interface termination, includes the following steps.

[0140] Step 1. The Application Function (AF) or server sends a request message to the MF. This message carries one or more of the following: a group ID (e.g., associated with multiple AIoT UEs, and the MF can use the same group ID to communicate with each of the multiple AIoT UEs), a UE list (e.g., a list of UE IDs, or portions of UE IDs), location information (e.g., an identity or address associated with one or more gNBs, one or more AMFs, one or more tracking areas, one or more physical areas, etc.), data (e.g., an application layer message that can be delivered to one or more UEs based on the group ID, UE list, and / or location information), or an AIoT indication (e.g., indicating that a particular communication is an AIoT communication).

[0141] Step 2. The MF triggers an inventory or paging process. The MF is configured to locate the appropriate NB based on the information stored in the MF and deliver a paging or inventory message to it. The paging or inventory message carries one or more of the following: selected UE information (e.g., a list of UE IDs), group ID (e.g., a group ID can be associated with multiple AIoT UEs), data (e.g., a NAS PDU, which can be delivered to the UE that matches the selected UE information), or an AIoT indication (e.g., indicating that a particular communication is AIoT communication).

[0142] Step 3. The base station (NB) triggers an inventory or paging procedure. The inventory or paging message carries a NAS PDU, and the NB is configured to deliver it to the UE that matches the selected UE information.

[0143] Step 4. The UE transmits data to the NB. This data can be a NAS PDU.

[0144] Step 5. The NB transmits this data to the MF. In some cases, the NB can collect NAS PDU information for multiple UEs before feeding back information to the MF in a single instance.

[0145] Step 6. The MF sends a response message to the AF or the server, wherein the message carries one or more of the following: group ID (e.g., associated with multiple AIoT UEs), UE list (e.g., a list of UE IDs, or a portion of UE IDs), data (e.g., application layer messages), or a list of data (e.g., each data item is an application layer message associated with a UE list or group ID).

[0146] Example 5 (Registration Example)

[0147] In some embodiments, the MF triggers a process that enables the UE to initiate a registration process. The MF may send a message to the AMF or NB, and the message includes location information (e.g., an identity or address associated with one or more gNBs, one or more AMFs or MFs, one or more tracking areas, one or more physical areas, etc.) and a registration indication (e.g., an indication that the message is part of a registration process or a region update process).

[0148] In some embodiments, and after the AMF locates the corresponding NB based on the location information, the AMF sends a message to the NB. This message carries a registration indication (e.g., an indication that the message is part of a registration process or a zone update process).

[0149] In some embodiments, the NB can trigger an inventory or paging procedure, and the inventory or paging message may include a registration indication (e.g., an indication that the message is part of a registration procedure or a region update procedure). If the UE receives the message, it performs the registration procedure or the region update procedure. It can then respond to the inventory or paging message to complete the inventory or paging procedure (if it is the selected UE) or to complete its identification with the network (if it is not the selected UE).

[0150] In some embodiments, the UE may send its UE ID back to the NB and may also send a NAS PDU to the NB. This NAS PDU carries NAS messages, such as registration requests or area update requests. The NAS message may also include one or more of the following: UE ID, UE capabilities, and / or subscription information.

[0151] If the MF receives a NAS message from the UE, the MF can send a NAS message back to the UE, such that the NAS message includes a registration acceptance response or an area update response. The NAS message also includes one or more of the following: the UE ID used in the core network (CN), the area information that the UE has accessed, the group ID, and / or network information (e.g., a Public Land Mobile Network (PLMN) identifier).

[0152] Example methods and implementations of the disclosed technology

[0153] Figure 11 A flowchart of an example wireless communication method 1100 is shown. Method 1100 includes, at operation 1110, at least one of the following performed by a network function associated with a network node and a wireless device: configuring and maintaining an interface with the network node; managing a registration process for the wireless device; managing connections between the network function and the wireless device; providing the network node with location-related information and services for the wireless device; managing connections between the wireless device and a server; providing authentication services, data security services, accounting services, or group communication services to the wireless device; or maintaining information associated with the capabilities, identity, or location of the wireless device.

[0154] The described features can be implemented to further provide one or more of the following technical solutions:

[0155] 1. A wireless communication method comprising: performing at least one of the following functions by network functions associated with a network node and a wireless device: configuring and maintaining an interface with the network node; managing a registration process for the wireless device; managing a connection between the network function and the wireless device; providing the network node with location-related information and services of the wireless device; managing a connection between the wireless device and a server; providing the wireless device with authentication services, data security services, billing services, or group communication services; or maintaining information associated with the capabilities of the wireless device, the identity of the wireless device, or the location of the wireless device.

[0156] 2. The method according to Solution 1, wherein the network function is configured to trigger a paging process or an inventory process by transmitting a message including a list or group identifier associated with the wireless device, or an identifier associated with the network node. In some embodiments, the paging process or inventory process is as described in Embodiment 2.

[0157] 3. The method according to Solution 1, wherein the network function is configured to: determine the address or identifier of the access management service based on information from the data management service; and transmit a message to the access management service based on the address or the identifier, wherein the message includes at least one of the following: a list of identifiers associated with the wireless device, a group identifier associated with the wireless device, an identifier associated with the network node, or one or more application layer messages. In some embodiments, the address or the identifier is determined as described in Embodiment 3.

[0158] 4. The method according to Solution 3, wherein the data management service is Unified Data Management (UDM) and the access management service is Access and Mobility Management Function (AMF).

[0159] 5. The method according to Solution 1, wherein the network function is configured to trigger a paging process or an inventory process for the network node.

[0160] 6. The method according to Solution 1, wherein the network function is configured to: determine the address or identifier of the access management service; and trigger a paging process or inventory process for the access management service based on the address or the identifier.

[0161] 7. The method according to Solution 6, wherein the information stored by the network function includes the address or identifier of the access management service.

[0162] 8. The method according to solution 6 or 7, wherein the access management service is an access and mobility management function (AMF).

[0163] 9. The method according to Solution 1, wherein the network function is configured to: determine the address or identifier of the access management service based on information from the data management service; and transmit a message to the access management service based on the address or the identifier, wherein the message includes an application layer message. In some embodiments, the address or the identifier is determined as described in Embodiment 4.

[0164] 10. The method according to Solution 9, wherein the data management service is Unified Data Management (UDM) and the access management service is Access and Mobility Management Function (AMF).

[0165] 11. The method according to Solution 1, wherein the network function is configured to: determine the address or identifier of the access management service based on information stored by the network function; and transmit a message to the access management service based on the address or the identifier.

[0166] 12. The method according to solution 11, wherein the access management service is an access and mobility management function (AMF).

[0167] 13. The method according to Solution 1, wherein the network function is configured to: determine the address or identifier of the network node based on information stored by the network function; and trigger a paging process or inventory process for the network node based on the address or the identifier.

[0168] 14. The method according to Solution 1, wherein the network function is configured to: transmit a message to the wireless device enabling the wireless device to initiate the registration process; and transmit a message to the network node or access management service, the message including: location information associated with the network node or the access management service, or an indication indicating whether the message is related to the registration process or the area update process. In some embodiments, the registration process is as described in Embodiment 5.

[0169] 15. The method according to solution 14, wherein the access management service is an access and mobility management function (AMF).

[0170] 16. The method according to Solution 1, wherein the network node is configured to trigger a paging process or an inventory process.

[0171] 17. An apparatus for wireless communication, comprising a processor configured to implement the method according to one or more of solutions 1 to 16.

[0172] 18. A non-transitory computer-readable program storage medium having code stored thereon, which, when executed by a processor, causes the processor to perform the method according to one or more of solutions 1 to 16.

[0173] Figure 12 An example block diagram of a hardware platform 1200 is shown, which may be part of a network device (e.g., a base station) or a communication device (e.g., a user equipment (UE)). The hardware platform 1200 includes at least one processor 1210 and a memory 1205 storing instructions thereon. These instructions, when executed by the processor 1210, configure the hardware platform 1200 to perform... Figure 11 The operations described herein and the operations in the various embodiments described in this patent document. Transmitter 1215 transmits or sends information or data to another device. For example, a network device transmitter can send a message to a user equipment. Receiver 1220 receives information or data transmitted or sent by another device. For example, a user equipment can receive a message from a network device.

[0174] The implementation methods discussed above are applicable to wireless communication. Figure 13 An example of a wireless communication system (e.g., a 5G or NR cellular network) is illustrated, comprising a base station 1320 and one or more user equipments (UEs) 1311, 1312, and 1313. In some embodiments, the UE accesses the BS (e.g., the network) using a communication link to the network (sometimes referred to as the uplink direction, as depicted by dashed arrows 1331, 1332, and 1333), which then enables subsequent communication from the BS to the UE (e.g., the direction from the network to the UE, sometimes referred to as the downlink direction, as depicted by arrows 1341, 1342, and 1343). In some embodiments, the BS sends information to the UE (sometimes referred to as the downlink direction, as depicted by arrows 1341, 1342, and 1343), which then enables subsequent communication from the UE to the BS (e.g., the direction from the UE to the BS, sometimes referred to as the uplink direction, as depicted by dashed arrows 1331, 1332, and 1333). The UE can be, for example, a smartphone, tablet, mobile computer, machine-to-machine (M2M) device, Internet of Things (IoT) device, etc.

[0175] Some embodiments described herein are described in the general context of methods or processes that may be implemented in one embodiment by a computer program product embodied in a computer-readable medium, including computer-executable instructions, such as program code executable by a computer in a networked environment. The computer-readable medium may include removable and non-removable storage devices, including but not limited to read-only memory (ROM), random access memory (RAM), optical disc (CD), digital versatile optical disc (DVD), etc. Therefore, the computer-readable medium may include non-transitory storage media. Typically, program modules may include routines, programs, objects, components, data structures, etc., that perform specific tasks or implement specific abstract data types. Computer or processor-executable instructions, associated data structures, and program modules represent examples of program code for performing the method steps disclosed herein. Specific sequences of such executable instructions or associated data structures represent examples of corresponding actions for implementing the functionality described in such steps or processes.

[0176] Some of the disclosed embodiments can be implemented as devices or modules using hardware circuitry, software, or combinations thereof. For example, hardware circuitry implementations may include discrete analog and / or digital components, which may be integrated, for example, as part of a printed circuit board. Alternatively or additionally, the disclosed components or modules may be implemented as application-specific integrated circuits (ASICs) and / or field-programmable gate arrays (FPGAs). Some implementations may additionally or alternatively include digital signal processors (DSPs), which are dedicated microprocessors with an architecture optimized for the operational requirements of digital signal processing associated with the disclosed functions of this application. Similarly, various components or sub-components within each module may be implemented in software, hardware, or firmware. Connectivity between modules and / or between components within a module may be provided using any of the connectivity methods and media known in the art, including but not limited to communication over the Internet, wired, or wireless networks using appropriate protocols.

[0177] While this document contains numerous details, these should not be construed as limiting the scope of the claimed invention or the scope that may be claimed, but rather as descriptions of features specific to particular embodiments. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented separately or in any suitable sub-combination in multiple embodiments. Furthermore, although features may be described above as operating in certain combinations, or even initially claimed in this way, one or more features from a claimed combination may be removed from that combination in some cases, and the claimed combination may involve sub-combinations or variations thereof. Similarly, although operations are depicted in a specific order in the drawings, this should not be construed as requiring the performance of such operations in the specific order shown or in sequential order, or requiring the performance of all shown operations to achieve the desired result.

[0178] Only a few implementations and examples have been described, and other implementations, enhancements and variations may be made based on what is described and shown in this disclosure.

Claims

1. A wireless communication method, comprising: At least one of the following functions is performed by network functions associated with network nodes and wireless devices: Configure and maintain the interface with the network nodes. Manage the registration process for the wireless device. Manage the connection between the network function and the wireless device. Provide the network nodes with location-related information and services for the wireless device. Manage the connection between the wireless device and the server. Provide authentication services, data security services, billing services, or group communication services to the wireless device, or Maintain information associated with the capabilities of the wireless device, the identity of the wireless device, or the location of the wireless device.

2. The method of claim 1, wherein, The network function is configured to trigger a paging or inventory process by transmitting messages, the messages including a list or group of identifiers associated with the wireless device, or an identifier associated with the network node.

3. The method of claim 1, wherein, The network function is configured as follows: Based on information from the data management service, determine the address or identifier for accessing the management service; and Based on the address or the identifier, a message is transmitted to the access management service, wherein the message includes at least one of the following: a list of identifiers associated with the wireless device, a group identifier associated with the wireless device, an identifier associated with the network node, or one or more application layer messages.

4. The method of claim 3, wherein, The data management service is Unified Data Management (UDM), and the access management service is Access and Mobility Management Function (AMF).

5. The method of claim 1, wherein, The network function is configured to trigger a paging process or an inventory process for the network node.

6. The method according to claim 1, wherein, The network function is configured as follows: Determine the address or identifier of the access management service; and Based on the address or the identifier, a paging process or inventory process for the access management service is triggered.

7. The method according to claim 6, wherein, The information stored by the network function includes the address or identifier of the access management service.

8. The method according to claim 6 or 7, wherein, The access management service is the Access and Mobility Management Function (AMF).

9. The method according to claim 1, wherein, The network function is configured as follows: Based on information from the data management service, determine the address or identifier for accessing the management service; and Based on the address or the identifier, a message is transmitted to the access management service, wherein the message includes application layer messages.

10. The method according to claim 9, wherein, The data management service is Unified Data Management (UDM), and the access management service is Access and Mobility Management Function (AMF).

11. The method according to claim 1, wherein, The network function is configured as follows: Based on the information stored by the network functions, the address or identifier of the access management service is determined; and Based on the address or the identifier, a message is transmitted to the access management service.

12. The method according to claim 11, wherein, The access management service is the Access and Mobility Management Function (AMF).

13. The method according to claim 1, wherein, The network function is configured as follows: Based on the information stored by the network function, the address or identifier of the network node is determined; and Based on the address or the identifier, a paging process or inventory process for the network node is triggered.

14. The method according to claim 1, wherein, The network function is configured as follows: A message is sent to the wireless device, the message enabling the wireless device to initiate the registration process; and A message is transmitted to the network node or access management service, the message including: location information associated with the network node or the access management service, or an indication of whether the message is related to the registration process or the area update process.

15. The method according to claim 14, wherein, The access management service is the Access and Mobility Management Function (AMF).

16. The method according to claim 1, wherein, The network node is configured to trigger a paging process or an inventory process.

17. An apparatus for wireless communication, comprising a processor configured to implement the method according to one or more of claims 1 to 16.

18. A non-transitory computer-readable program storage medium having code stored thereon, which, when executed by a processor, causes the processor to perform the method according to one or more of claims 1 to 16.

Images