A communication method and apparatus

Abstract

This application relates to a communication method and apparatus. A second network device receives a first message requesting a change in the affiliation of a first IoT device to a first service requester. Before changing the affiliation of the first IoT device to the first service requester, the first IoT device is affiliated with a second service requester. If the affiliation of the first IoT device is changed to the first service requester, the second network device stores first information indicating that the first IoT device belongs to the first service requester. Embodiments of this application can reasonably manage IoT devices, thereby determining the service requester to which the IoT device belongs. Furthermore, embodiments of this application can store the first information, enabling the network to clearly identify the current service requester to which the first IoT device belongs.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0002] With the development of communication technology, the 3rd Generation Partnership Project (3GPP) defined the Ambient Internet of Things (A-IoT) technology. In AIoT scenarios, the service requester to which the same AIoT device belongs may change. How to manage the service requester to which an AIoT device belongs is a problem that needs to be solved. Summary of the Invention

[0003] This application provides a communication method and apparatus for managing service requesters belonging to Internet of Things (IoT) devices.

[0004] Firstly, a first communication method is provided, which is applied to a network device. That is, the method can be executed by a network device. This network device is, for example, a network equipment, or a device including network device functions (e.g., a network device), or a chip system (or chip) or other functional module capable of implementing the functions of a network device, and is, for example, disposed within a network equipment. Hereinafter, the method is taken as being executed by a network device. This network device is, for example, a second network device. The second network device includes, for example, a core network device, such as a network element capable of storing IoT service-related data, such as a UDM, UDR, or AIoTF. The method includes: receiving a first message, the first message requesting a change in the affiliation of a first IoT device to a first service requester, wherein, before changing the affiliation of the first IoT device to a first service requester, the first IoT device is affiliated to a second service requester; if the affiliation of the first IoT device is changed to a first service requester, storing first information, the first information indicating that the first IoT device is affiliated to the first service requester.

[0005] In this embodiment, the business requester to which the first IoT device belongs can change. For example, the first IoT device may be transported from one enterprise to another, thus changing the enterprise or business requester to which the first IoT device belongs. This embodiment supports such changes. Therefore, this embodiment can reasonably manage IoT devices, thereby determining the business requester to which the IoT device belongs. Furthermore, this embodiment can store first information, enabling the network to clearly identify the current business requester to which the first IoT device belongs.

[0006] In an optional implementation, the method further includes: if the first message is rejected, then maintaining the dependency relationship of the first IoT device unchanged. If the first message is rejected, the dependency relationship of the first IoT device may remain unchanged; for example, the second network device may store the original dependency relationship of the first IoT device.

[0007] In one optional implementation, the first message may further include one or more of the following: the identifier of the first IoT device; the identifier of the first service requester; or, the identifier of the second service requester.

[0008] In an optional implementation, the first message further indicates: M service requesters, where M is a positive integer, and these M service requesters are those from which the first IoT device can continue to change its affiliation; and / or, whether the affiliation of the first IoT device can continue to change. For example, after the affiliation of the first IoT device changes to be subordinate to the first service requester, the affiliation of the first IoT device may still change, or it may no longer be possible to change it further; the first message can indicate this. If the affiliation of the first IoT device can still be changed, the first message can also indicate the M service requesters that can be changed. This makes the information obtained by the second network device more complete.

[0009] In one optional implementation, the M service requesters are service requesters to which the first IoT device can change its affiliation when the first IoT device is changed to be subordinate to the first service requester.

[0010] In one optional implementation, the first message further includes a first network identifier, which indicates a first network. This first network is the network that the first IoT device preferentially accesses when it is changed to belong to the first service requester. For example, the first network is the network corresponding to the first service requester. If the first IoT device is not connected to the first network, the first service requester may be unable to control the first IoT device. Therefore, the first message can indicate the first network identifier; for example, a second network device can trigger the first IoT device to access the first network, thereby enabling the first service requester to control the first IoT device.

[0011] In one optional implementation, the network that the first IoT device preferentially accesses is the network corresponding to the first service requester. For example, the network corresponding to the first service requester is the network where the first service requester is located, or the network to which the first service requester has a contract, or the network with which the first service requester has a protocol relationship, or the network through which the first service requester can communicate.

[0012] In an optional implementation, the method further includes: if the first network is different from the network currently accessed by the first IoT device, sending a second message, the second message being used to trigger the first IoT device to select the first network. If the network currently accessed by the first IoT device is not the first network, the second network device can trigger the first IoT device to select the first network, enabling the second network device to control the first IoT device. However, if the network currently accessed by the first IoT device is the first network, the second network device does not need to trigger the first IoT device to select a network.

[0013] In one optional implementation, the second message further includes: second information indicating the dwell time of the first IoT device on the first network; and / or, third information indicating a first location and indicating that the first IoT device selects the first network when located at the first location. The second and / or third information enables the first IoT device to access the first network at an appropriate time and / or location.

[0014] In an optional implementation, the method further includes: receiving fourth information from the first IoT device, the fourth information indicating that the first IoT device has connected to the first network, or indicating that the first IoT device has failed to connect to the first network. The first IoT device may report the result of successful or failed connection to the first network to a second network device, for example, the second network device may use this information to determine whether to change the affiliation of the first IoT device.

[0015] In an optional implementation, before receiving the first message, the method further includes: receiving a third message from the second service requester, wherein the third message indicates that the first IoT device belongs to the second service requester and indicates whether the affiliation of the first IoT device can be changed. The first IoT device originally belongs to the second service requester, and the second service requester can send this information to the second network device in advance. Therefore, when the first service requester requests to change the affiliation of the first IoT device, the second network device can determine whether the affiliation of the first IoT device can be changed based on locally stored information, resulting in higher efficiency.

[0016] In an optional implementation, the method further includes: determining, based on the third message, whether the first IoT device can be changed to be subordinate to the first service requester.

[0017] In one optional implementation, the third message indicates that the affiliation of the first IoT device can be changed, and further indicates that the affiliation of the first IoT device can be changed to belong to N service requesters, where the N service requesters include the first service requester, and N is a positive integer. The third message can indicate the specific service requesters whose affiliation the first IoT device can change to, and the second network device can make a determination accordingly.

[0018] In an optional implementation, after receiving the first message, the method further includes: sending a fourth message to the second service requester, the fourth message querying whether the first IoT device can be changed to belong to the first service requester; and receiving a fifth message, the fifth message indicating whether the first IoT device can be changed to belong to the first service requester. When the first service requester requests to change the affiliation of the first IoT device, the second network device can query the second service requester to determine whether the affiliation of the first IoT device can be changed. In this implementation, the second network device does not need to pre-store information, but can query the original service requester (e.g., the second service requester) to see if the affiliation of the corresponding IoT device can be changed, which helps save storage space for the second network device.

[0019] In one alternative implementation, the fifth message indicates that the first IoT device cannot be changed to be subordinate to the first service requester, and also indicates the reason why it cannot be changed.

[0020] In an optional implementation, the method further includes: receiving a sixth message from a first network device, the sixth message requesting the determination of a service requester to which the first IoT device belongs; and sending a seventh message to the first network device, the seventh message indicating that the first IoT device belongs to the first service requester. For example, if the first network device receives information from a first IoT device that needs to be forwarded to a service requester to which the first IoT device belongs, the first network device can query a second network device to determine the service requester to which the first IoT device belongs, thus ensuring the correct transmission of the information.

[0021] In one alternative implementation, the first network device is an AIoTF.

[0022] In one optional implementation, the method is performed by an AIoTF, and the method further includes: receiving an identifier of a first IoT device and first data; and sending the first data to the first service requester. If the second network device is an AIoTF, for example, if the AIoTF receives the first data from the first IoT device, and the AIoTF can determine that the first IoT device belongs to the first service requester based on stored information, then the first network device can send the first data to the first service requester.

[0023] In one alternative implementation, the first service requester is a first AF, and the second service requester is a second AF.

[0024] Secondly, a second communication method is provided, which is applied to the network device side. That is, the method can be executed by a network device. This network device is, for example, a network equipment, or a device including network device functions (e.g., a network device), or a chip system (or chip) or other functional module capable of implementing the network device functions, and is, for example, located within the network equipment. In the following text, the method being executed by a network device is taken as an example. This network device includes, for example, a service requester. The service requester is, for example, a first service requester. The method includes: sending a first message to a second network device, the first message requesting a change in the affiliation of a first IoT device to that of the first service requester, wherein, prior to the change in the affiliation of the first IoT device to that of the first service requester, the first IoT device is subordinate to the first service requester; receiving a ninth message, the ninth message indicating that the affiliation of the first IoT device has been changed to that of the first service requester, or indicating a refusal to change the affiliation of the first IoT device.

[0025] In one optional implementation, the first message may further include one or more of the following: the identifier of the first IoT device; the identifier of the first service requester; or, the identifier of the second service requester.

[0026] In an optional implementation, the first message further indicates: M service requesters, wherein the M service requesters are service requesters for which the first IoT device can continue to change its affiliation, and M is a positive integer; and / or whether the affiliation of the first IoT device can continue to change.

[0027] In an optional implementation, when the first network is different from the network currently accessed by the first IoT device, the first message further includes a first network identifier, which indicates the first network, wherein the first network is the network that the first IoT device preferentially accesses when the first IoT device is changed to belong to the first service requester.

[0028] In one optional implementation, the M service requesters are service requesters to which the first IoT device can change its affiliation when the first IoT device is changed to be subordinate to the first service requester.

[0029] In one alternative implementation, the first message further includes: second information indicating the dwell time of the first IoT device in the first network; and / or, third information indicating a first location and indicating that the first IoT device selects the first network when it is located in the first location.

[0030] For the technical effects of the second aspect or various alternative implementation methods, please refer to the introduction of the technical effects of the first aspect or corresponding implementation methods.

[0031] Thirdly, a third communication method is provided, which is applied to the network device side. That is, the method can be executed by the network device. This network device is, for example, a network equipment, or a device including network device functions (e.g., a network device), or a chip system (or chip) or other functional module capable of implementing the network device functions, and is, for example, housed within the network equipment. In the following description, the method being executed by the network device is taken as an example. This network device may include, for example, a service requester. The service requester may be, for example, a second service requester. The method includes: sending a third message to the second network device, the third message indicating that the first IoT device is subordinate to the second service requester, and indicating whether the subordinate relationship of the first IoT device can be changed.

[0032] In one alternative implementation, the third message indicates that the affiliation of the first IoT device can be changed, and also indicates that the affiliation of the first IoT device can be changed to be subordinate to N service requesters, the N service requesters including the first service requester, where N is a positive integer.

[0033] In an optional implementation, the method further includes: sending a tenth message to a first network device, the tenth message being used to request the execution of a first operation on the first IoT device; and receiving a first rejection message, the first rejection message being used to reject the second request.

[0034] In one optional implementation, the first rejection information further includes a rejection reason, wherein the rejection reason is that the first IoT device has changed to belong to the first service requester.

[0035] For information on the technical effects of the third aspect or various alternative implementation methods, please refer to the description of the technical effects of the first aspect or corresponding implementation methods.

[0036] Fourthly, a fourth communication method is provided, which is applied to the network device side. That is, the method can be executed by the network device. This network device is, for example, a network equipment, or a device including network device functions (e.g., a network device), or a chip system (or chip) or other functional module capable of implementing the network device functions, and is, for example, housed within the network equipment. In the following text, the method being executed by the network device is taken as an example. This network device may include, for example, a service requester. The service requester may be, for example, a second service requester. The method includes: receiving a fourth message, the fourth message querying whether it is possible to change the first IoT device to belong to the first service requester; and sending a fifth message, the fifth message indicating whether it is possible to change the first IoT device to belong to the first service requester.

[0037] In one alternative implementation, based on fifth information, it is determined whether the first IoT device can be changed to be subordinate to the first service requester, wherein the fifth information indicates that the first IoT device is subordinate to the second service requester, and indicates whether the subordinate relationship of the first IoT device can be changed.

[0038] In one optional implementation, the fifth information indicates that the affiliation of the first IoT device can be changed, and also indicates that the affiliation of the first IoT device can be changed to be subordinate to N service requesters, the N service requesters including the first service requester, where N is a positive integer.

[0039] In one alternative implementation, the fifth message indicates that the first IoT device cannot be changed to be subordinate to the first service requester, and also indicates the reason why it cannot be changed.

[0040] For the technical effects of the fourth aspect or various alternative implementation methods, please refer to the introduction of the technical effects of the first aspect or corresponding implementation methods.

[0041] Fifthly, a fifth communication method is provided, which is applied to the network device side. That is, the method can be executed by a network device. This network device is, for example, a network device, or a device including network device functions (e.g., a network device), or a chip system (or chip) or other functional module capable of implementing the network device functions, and is, for example, disposed within a network device. In the following description, the method being executed by a network device is taken as an example. This network device is, for example, a first network device. The first network device includes, for example, AIoTF, etc. The method includes: receiving the identifier of a first IoT device and first data; sending the first data to a first service requester, wherein the first service requester is a service requester to which the first IoT device belongs.

[0042] In an optional implementation, the method further includes: sending a sixth message to a second network device, the sixth message being used to request determination of the service requester to which the first IoT device belongs; and receiving a seventh message from the second network device, the seventh message being used to indicate that the first IoT device belongs to the first service requester.

[0043] For the technical effects of the fifth aspect or various alternative implementations, please refer to the introduction of the technical effects of the first aspect or corresponding implementations.

[0044] Sixthly, a communication device is provided. The communication device can implement the functions of the network device described in any one of the first to fifth aspects. The communication device possesses the functions of the aforementioned network device. The communication device may be, for example, a first network device, or another device including the functions of a first network device, or a system-on-a-chip (or chip) or other functional module capable of implementing the functions of the first network device, and the system-on-a-chip or functional module may be, for example, disposed in the first network device. Alternatively, the communication device may be, for example, a second network device, or another device including the functions of a second network device, or a system-on-a-chip (or chip) or other functional module capable of implementing the functions of the second network device, and the system-on-a-chip or functional module may be, for example, disposed in the second network device. Alternatively, the communication device may be, for example, a first service requester, or another device including the functions of a first service requester, or a system-on-a-chip (or chip) or other functional module capable of implementing the functions of a first service requester, and the system-on-a-chip or functional module may be, for example, disposed in the first service requester. Alternatively, the communication device may be, for example, a second service requester, or other equipment including the functions of a second service requester, or a chip system (or chip) or other functional module capable of implementing the functions of a first service requester, and such chip system or functional module may be disposed, for example, in the second service requester. In one optional implementation, the communication device includes a baseband device and a radio frequency device. In another optional implementation, the communication device includes a processing unit (sometimes also called a processing module) and a transceiver unit (sometimes also called a transceiver module). The transceiver unit is capable of transmitting and receiving functions. When the transceiver unit performs the transmitting function, it may be called a transmitting unit (sometimes also called a transmitting module), and when the transceiver unit performs the receiving function, it may be called a receiving unit (sometimes also called a receiving module). The transmitting unit and the receiving unit may be the same functional module, which is called the transceiver unit and can perform both transmitting and receiving functions; or, the transmitting unit and the receiving unit may be different functional modules, and the transceiver unit is a collective term for these functional modules.

[0045] In one optional implementation, the transceiver unit (or the receiving unit) is configured to receive a first message requesting a change in the affiliation of the first IoT device to that of a first service requester, wherein, prior to changing the affiliation of the first IoT device to that of the first service requester, the first IoT device is subordinate to a second service requester; the processing unit is configured to, if the affiliation of the first IoT device is changed to that of the first service requester, store first information indicating that the first IoT device is subordinate to the first service requester.

[0046] In one optional implementation, the transceiver unit (or the sending unit) is configured to send a first message to a second network device, the first message requesting a change in the affiliation of the first IoT device to that of a first service requester, wherein the first IoT device is affiliated to the first service requester before the affiliation of the first IoT device is changed to that of the first service requester; the transceiver unit (or the receiving unit) is configured to receive a ninth message, the ninth message indicating that the affiliation of the first IoT device has been changed to that of the first service requester, or indicating that the change in the affiliation of the first IoT device is refused.

[0047] In one optional implementation, the transceiver unit (or the sending unit) is configured to send a third message to the second network device, the third message indicating that the first IoT device is subordinate to the second service requester, and indicating whether the subordinate relationship of the first IoT device can be changed.

[0048] In one optional implementation, the transceiver unit (or the receiving unit) is configured to receive a fourth message, the fourth message querying whether the first IoT device can be changed to belong to the first service requester; the transceiver unit (or the sending unit) is configured to send a fifth message, the fifth message indicating whether the first IoT device can be changed to belong to the first service requester.

[0049] In one optional implementation, the transceiver unit (or the receiving unit) is configured to receive the identifier of the first IoT device and first data; the transceiver unit (or the sending unit) is configured to send the first data to a first service requester, wherein the first service requester is a service requester to which the first IoT device belongs.

[0050] In an alternative embodiment, the communication device further includes a storage unit (sometimes also called a storage module), and the processing unit is configured to couple with the storage unit and execute programs or instructions in the storage unit to enable the communication device to perform the functions of the network device described in any one of the first to fifth aspects above.

[0051] A seventh aspect provides a communication device. The communication device may be a network device, or a chip or chip system for use in a network device. The communication device includes a processor configured to perform the methods executed by the network device in the aforementioned aspects. Optionally, the processor is coupled to a memory, which, when reading the computer program or instructions, causes the communication device to perform the methods executed by the network device in the aforementioned aspects. The memory is used to store the computer program or instructions and may be included in the communication device or disposed externally. Optionally, the communication device further includes a communication interface from which the processor calls and runs the computer program or instructions.

[0052] Eighthly, a communication system is provided, including a second network device. The second network device is used to perform the method described in the first aspect, which is executed by the first network device. For example, the first network device can be implemented using the communication apparatus described in the sixth or seventh aspect.

[0053] Optionally, the communication system may further include a first service requester. The first service requester is used to execute the method described in the second aspect above. For example, the first service requester can be implemented using the communication apparatus described in the sixth or seventh aspect.

[0054] Optionally, the communication system may further include a second service requester. The second service requester is used to perform the methods described in the third or fourth aspect above. For example, the second service requester can be implemented using the communication apparatus described in the sixth or seventh aspect.

[0055] Optionally, the communication system may further include a first network device. The first network device is used to perform the method described in the fifth aspect above. For example, the first network device can be implemented using the communication apparatus described in the sixth or seventh aspect.

[0056] Ninthly, a computer-readable storage medium is provided for storing a computer program or instructions that, when executed, cause the methods performed by the network apparatus in the preceding aspects to be implemented.

[0057] In a tenth aspect, a computer program product containing instructions is provided, which, when the computer program or instructions are run on a computer, causes the methods described in the above aspects to be implemented. Attached Figure Description

[0058] Figure 1 and Figure 2 These are schematic diagrams of two different structures of the access network equipment in the embodiments of this application;

[0059] Figure 3 A schematic diagram illustrating how readers and AIoT devices work.

[0060] Figure 4 This is a schematic diagram of a communication system applicable to an embodiment of this application;

[0061] Figures 5-7 Flowcharts of several communication methods provided in the embodiments of this application;

[0062] Figure 8 A schematic diagram of an apparatus provided in an embodiment of this application;

[0063] Figure 9 This is a schematic diagram of another device provided in an embodiment of this application. Detailed Implementation

[0064] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the embodiments of this application will be further described in detail below with reference to the accompanying drawings.

[0065] In this application embodiment, the number of nouns, unless otherwise specified, refers to "singular nouns or plural nouns," that is, "one or more." "At least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. For example, A / B means: A or B. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c means: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, and c can be single or multiple.

[0066] The ordinal numbers such as "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects, and are not used to limit the size, content, order, timing, priority, or importance of the multiple objects. Furthermore, the numbering of steps in the various embodiments described in this application is only to distinguish different steps and is not used to limit the order in which the steps are performed.

[0067] The following explanations of some terms or concepts used in the embodiments of this application are provided to facilitate understanding by those skilled in the art.

[0068] (1) In this application embodiment, the terminal device is a device with wireless transceiver function, which may be a fixed device, a mobile device, a handheld device (e.g., a mobile phone), a wearable device, an in-vehicle device, or a wireless device (e.g., a communication module, a modem, or a chip system, etc.) built into the above devices. The terminal devices are used to connect people, objects, and machines, and can be widely used in various scenarios, including but not limited to the following: sensing scenarios, cellular communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine / machine-type (M2M / MTC) communication, Internet of Things (IoT), virtual reality (VR), augmented reality (AR), industrial control, self-driving, remote medical care, smart grid, smart furniture, smart office, smart wearables, smart transportation, smart city, drones, robots, and terminal devices in indoor commercial scenarios (such as mobile phone screen mirroring, file sharing, and mobile phone to VR glasses). When the terminal equipment is applied to V2X, it can also be called a V2X device, such as a smart car, digital car, unmanned car, driverless car, pilotless car, or automobile, self-driving car, or autonomous car, pure electric vehicle (EV), hybrid electric vehicle (HEV), range-extended electric vehicle (REEV), plug-in hybrid electric vehicle (PHEV), new energy vehicle, or roadside unit (RSU). The terminal equipment can also be a device used in D2D communication, such as an electricity meter or water meter.

[0069] Furthermore, in this embodiment of the application, the terminal device can also be a terminal device in an Internet of Things (IoT) system. IoT is an important component of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection.

[0070] The various terminal devices described above, if located in a vehicle (e.g., placed inside or installed inside a vehicle), can all be considered in-vehicle terminal devices, also known as on-board units (OBUs). The terminal device of this application can also be an in-vehicle module, in-vehicle component, in-vehicle chip, or in-vehicle unit built into a vehicle as one or more components or units. The vehicle can implement the methods of this application through the built-in in-vehicle module, in-vehicle component, in-vehicle chip, or in-vehicle unit.

[0071] The terminal equipment may sometimes be referred to as UE, terminal, access station, UE station, remote station, wireless communication equipment, or user equipment, etc.

[0072] In this application embodiment, the device for implementing the terminal device function can be a terminal device, which can be a terminal device or a device capable of supporting the terminal device in implementing the function, such as a chip system. This device can be installed in the terminal device. In the technical solutions provided in this application embodiment, the example of a terminal device being used to implement the terminal device function is used to describe the technical solutions provided in this application embodiment.

[0073] (2) The network devices in this application embodiment include, for example, access network devices (or access network elements) and / or core network devices (or core network elements). The access network device is a device with wireless transceiver capabilities, used to communicate with the terminal device. The access network device includes, but is not limited to, base stations (base transceiver stations (BTS), Node B, evolved Node B (eNodeB) / eNB, or the next generation Node B (gNodeB) / gNB), transmission reception points (TRPs), base stations evolved from the 3rd generation partnership project (3GPP), access nodes in wireless fidelity (Wi-Fi) systems, wireless relay nodes, wireless backhaul nodes, etc. The base station can be: macro base station, micro base station, pico base station, small cell, relay station, etc. Multiple base stations can support networks using the same access technology or networks using different access technologies. A base station can contain one or more co-located or non-co-located transmission and reception points. The access network equipment can also be a radio controller, centralized unit (CU), and / or distributed unit (DU) in a cloud radio access network (CRAN) scenario. The access network equipment can also be a server, etc. For example, the network equipment in V2X technology can be a roadside unit (RSU). The following description uses a base station as an example to illustrate the access network equipment. A base station can communicate with a terminal device, or it can communicate with a terminal device through a relay station. A terminal device can communicate with multiple base stations in different access technologies. The core network equipment is used to implement functions such as mobility management, data processing, session management, policy and billing. The names of the equipment implementing core network functions may differ in systems using different access technologies; this application does not limit this.Taking the 5th generation (5G) mobile communication technology system as an example, the core network equipment includes, for example, access and mobility management function (AMF), session management function (SMF), policy control function (PCF), or user plane function (UPF), etc.

[0074] In a CU-DU architecture, or in an open RAN (ORAN) system, access network equipment may include one or more logical network elements such as a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). CUs and DUs can be separate entities or included in the same network element, such as a baseband unit (BBU). RUs may be included in radio equipment or radio units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs). One possible structure for access network equipment can be found in [reference needed]. Figure 1 Among them, core network equipment and access network equipment can communicate through backhaul links; within access network equipment, CU and DU can communicate through midhaul links, and DU and RU can communicate through fronthaul links.

[0075] Alternatively, another architecture for the access network equipment can be referenced. Figure 2 , Figure 2Taking access network equipment implemented through chips as an example, such as a RAN chip, the RAN chip may include a CU, DU, and RU. The CU can perform L2 and L3 functions, etc.; the DU can perform L1 functions and some L2 functions, etc.; and the RU can perform L1 computing and radio frequency (RF) digital functions, etc. The CU communicates with the core network equipment through a backhaul interface, which carries the traffic between the CU and the core network equipment. The CU may include a central processing unit (CPU) based on x86 or ARM architecture, as well as field programmable gate arrays (FPGAs), graphics processing units (GPUs), or other accelerators, etc. The CPU can communicate with the FPGA, GPU, or other accelerators through a peripheral component interconnect express (PCIe) interface.

[0076] The CU and DU communicate via a midhaul interface, which carries the traffic between the CU and DU. The DU may include an x86 or ARM architecture CPU, as well as FPGAs, GPUs, or other accelerators, which can communicate with the FPGA, GPU, or other accelerators via a PCIe interface.

[0077] The DU and RU communicate via a fronthaul interface, which carries the traffic between the DU and RU. If the access network equipment uses an integrated DU, the integrated DU can include the functions of both the DU and RU, and the RAN may no longer need to include a separate RU. The RU may include a RAN fronthaul processing unit, a digital processing unit, and an RF processing unit. The RAN fronthaul processing unit is implemented, for example, using an FPGA or an application-specific integrated circuit (ASIC). The digital processing unit is implemented, for example, using an FPGA or an ASIC.

[0078] The RU can be connected to an antenna to communicate with the UE via the antenna.

[0079] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called an open CU (O-CU), DU can also be called an open DU (O-DU), CU-CP can also be called an open CU-CP (O-CU-CP), CU-UP can also be called an open CU-UP (O-CU-CP), and RU can also be called an open RU (O-RU). For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples in its embodiments. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in the embodiments of this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.

[0080] The CU and DU can be configured according to the protocol layer functions of the wireless network they implement. For example, the CU can be configured to implement the functions of the Packet Data Convergence Protocol (PDCP) layer and above (such as the Radio Resource Control (RRC) layer and / or the Service Data Adaptation Protocol (SDAP) layer); the DU can be configured to implement the functions of protocol layers below the PDCP layer (such as one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, or Physical (PHY) layer). Alternatively, the CU can be configured to implement the functions of protocol layers above the PDCP layer (such as the RRC and / or SDAP layers), and the DU can be configured to implement the functions of protocol layers below the PDCP layer (such as one or more of the RLC, MAC, or PHY layers).

[0081] The above CU and DU configurations are merely examples; the functions of the CU and DU can be configured as needed. For instance, the CU or DU can be configured to have more protocol layer functions, or only some protocol layer processing functions. For example, some RLC layer functions and protocol layer functions above the RLC layer can be placed in the CU, while the remaining RLC layer functions and protocol layer functions below the RLC layer can be placed in the DU. Furthermore, the functions of the CU or DU can be divided according to service type or other system requirements, such as by latency. Functions that require low latency can be placed in the DU, while functions that do not require low latency can be placed in the CU.

[0082] DU and RU can cooperate to implement the functions of the PHY layer. A DU can be connected to one or more RUs. The functions of DU and RU can be configured in various ways depending on the design. For example, a DU can be configured to implement baseband functions, and an RU can be configured to implement mid-RF functions. Another example is that a DU can be configured to implement higher-level functions in the PHY layer, and an RU can be configured to implement lower-level functions in the PHY layer, or to implement both lower-level and RF functions. Higher-level functions in the physical layer can include a portion of the physical layer's functions that are closer to the MAC layer, while lower-level functions in the physical layer can include another portion of the physical layer's functions that are closer to the mid-RF side.

[0083] In this application embodiment, the apparatus for implementing the functions of a network device can be referred to as a network apparatus. This network apparatus can be a network element, a network device, or an apparatus capable of supporting the network device or network element in implementing the function, such as a chip system. This apparatus can be installed within the network device. In the technical solutions provided in this application embodiment, the apparatus for implementing the functions of a network device is described as a network apparatus (for example, an apparatus for implementing the functions of an access network apparatus is an access network apparatus, and an apparatus for implementing the functions of a core network apparatus is a core network apparatus).

[0084] (3) Devices in the Internet of Things (IoT) system.

[0085] Currently, IoT is receiving significant attention. For IoT scenarios, reducing device size and complexity is expected to increase the number of devices that can be accommodated in the IoT ecosystem. These IoT devices can include AIoT devices. For example, the peak power consumption of AIoT devices can range from 1μW to several hundred μW; the uplink signal of an AIoT device can be generated internally, or the AIoT device needs to perform backscattering based on an externally provided carrier wave to achieve uplink transmission. In some implementations, an AIoT device with a peak power consumption of approximately 1μW (referred to as device1) does not have uplink or downlink amplification capabilities; an AIoT device with a peak power consumption of several hundred μW (referred to as device2) has uplink and / or downlink amplification capabilities.

[0086] AIoT devices can perform business with corresponding devices. In this case, the AIoT device can be called an AIoT device. The corresponding device can be called a reader, such as a network device or a UE. Here, "device" can also be replaced with IoT devices such as UE, tag, or AIoT tag; and "reader" can also be replaced with network devices or UEs such as an interrogator.

[0087] A tag can also be called an electronic tag or a tag device. For example, a tag implemented through an AIoT device can also be called an AIoT tag. In this embodiment, the tag can communicate with network devices as a terminal device. Here, "tag" is just an optional name, and the name may change; for example, "AIoT tag" may be changed to other names. This embodiment does not limit the name. For ease of description, the term "tag" will continue to be used as an example below.

[0088] AIoT can be applied to a variety of scenarios. For example, in logistics and warehousing, tags (such as AIoT tags) can be used for inventory and tracking of goods, and to monitor the status of goods during transportation. In industrial manufacturing, tags can be used to monitor the status of the environment and equipment. Furthermore, AIoT can be considered for other consumer-facing businesses, such as managing user assets. By locating tags through inventory processes or other similar processes, users can determine whether their items are lost and in what area, thereby enabling AIoT-based item retrieval.

[0089] When the application server operates on the tag, it can send operation instructions through the core network. These instructions may include, but are not limited to, one or more of the following: operations for obtaining tag information, inventory operations (or storage operations), read operations, write operations, invalidation operations, or operations for interacting with the tag. These instructions may include area location information, tag identifiers, etc. The reader sends an access instruction to the tag. After the tag successfully connects randomly, the reader sends instructions to the tag (the reader can forward instructions from the core network to the tag). The tag obtains or sends corresponding information according to the instructions. For example, when the instruction is an inventory instruction or an inventory operation, the tag sends its identifier; when the instruction is a read instruction or a read operation, the tag sends the data stored in its storage area; when the instruction is a write instruction or a write operation, the tag stores the data to be written to the tag, as included in the instruction, in its storage area. The reader sends (or forwards) the tag's information to the core network; the core network then sends this information to the application server.

[0090] In this implementation, the application server can send operation commands through the control plane channel. For example, the application server can send operation commands to the AIoTF. In this case, the application server can be an application function (AF) entity, an application server (AS), or an ambient internet of things (A-IoT) AF / P-IoT AF, etc. In one possible implementation, the A-IoT AF can send operation commands to the ambient internet of things (AIoTMF) management function, which in turn sends the operation commands to the AMF. In another possible implementation, the A-IoT AF can send operation commands to the AIoTMF through a control plane device. This control plane device can be a network exposure function (NEF), a session management function (SMF), a policy control function (PCF), a unified data management function (UDM), or a network slice-specific and SNPN authentication and authorization function (NSSAAF). Alternatively, the application server can send operation commands through the user plane channel. In one possible implementation, the application server can send commands to the reader through the user plane function (UPF). In another possible implementation, the application server can send operation commands to the AIoTMF through user plane equipment (e.g., UPF) and SMF, and the AIoTMF can then send the operation commands to the tag through the access network equipment. In yet another possible implementation, the server sends operation commands to the reader through user plane equipment (e.g., UPF) and access network equipment (e.g., radio access network (RAN)), where the reader can be a UE.

[0091] AIoTMF, also known as ambient internet of things function (AIoTF), can process business requests from business requesters (such as application servers) and execute corresponding business operations (such as instructing a reader to perform device inventory procedures) and transmit instructions (such as read operations, write operations, and deactivation operations). Furthermore, AIoTF can manage IoT devices and perform security authentication processes.

[0092] In AIoT, AIoT devices (such as tags) can communicate with readers; for more information, please refer to [link / reference]. Figure 3 Through communication between the AIoT device and the reader, the AIoT device and the reader can perform at least one of the following operations: inventory operation, read operation, write operation, kill or disable operation, or lock operation.

[0093] Inventory operations, also known as inventory checks, are used to retrieve tag identifiers. For example, a reader and / or the core network and / or the service requester can obtain tag identifiers using query and acknowledged (ACK) commands. Inventory operations can be used to confirm whether a tag is currently within the inventory area. For instance, to facilitate tag inventory, tags can include four session identifiers (S0 to S3), each corresponding to two inventory states, A and B, indicated by inventory flags. When a reader selects a tag, the select command sent to that tag can carry a session identifier, which the tag can store. When the reader performs an inventory operation on that tag, the query command sent to the tag will include the session identifier, at which point the tag can flip the inventory state corresponding to that session identifier from A to B. If the reader sends a query command to perform an inventory operation again, the label will not respond to the reader because the inventory status in the label is B, thus avoiding the same label being inventoryed multiple times in one inventory cycle.

[0094] Read operations can read the electronic product code (EPC) or tag identifier (TID) in the tag's storage area, or read the content stored in the tag's reserved area or the content stored in the user's storage area, etc.

[0095] The write operation allows writing to the tag's storage area.

[0096] The inactivation operation can render the label permanently unusable.

[0097] Locking operations can lock the information of a tag to prevent read or write operations on that tag. Alternatively, locking operations can also lock the tag's storage area to prohibit read or write operations on that storage area.

[0098] The above are just examples. Other operations can be performed between tags and readers, which will not be illustrated here.

[0099] In some scenarios, AIoT devices can move, for example, being transported from one company to another. Each company can correspond to a business requester, and different companies may have the same or different business requesters. For instance, a product is manufactured by a manufacturer, who can assign an identifier to the product, making it an AIoT device. This identifier serves as the device's identifier. The product may then be transported to a retailer for sale. This retailer is a different company than the manufacturer, but the product's identifier remains the same. Here, the manufacturer corresponds to business requester 1, and the retailer corresponds to business requester 2; these two business requesters may be the same or different. Therefore, the business requester to which the AIoT device belongs may change. Figure 4 This is a schematic diagram of a mobile scenario for an AIoT device. For example, an AIoT device is transported from company A to company B. Company A is, for example, the manufacturer of the AIoT device, and company B is, for example, the distributor of the AIoT device. Company A corresponds to network A, and company B corresponds to network B. Network A corresponds to service requester A, and network B corresponds to service requester B. Network A and network B can be the same network, in which case service requester A and service requester B can be the same service requester or different service requesters; alternatively, network A and network B can be different networks, in which case service requester A and service requester B can be different service requesters.

[0100] How to manage the business requesters associated with AIoT devices is a problem that needs to be solved.

[0101] Therefore, in this embodiment, the business requester to which the first IoT device belongs can change. For example, the first IoT device may be transported from one enterprise to another, thus changing the enterprise or business requester to which the first IoT device belongs. This embodiment supports such changes. It is evident that this embodiment can reasonably manage IoT devices, thereby determining the business requester to which the IoT device belongs. Furthermore, this embodiment can store first information, enabling the network to clearly identify the current business requester to which the first IoT device belongs.

[0102] The communication method provided in this application can be applied to fourth-generation (4G) communication systems, such as long-term evolution (LTE) communication systems, as well as fifth-generation (5G) communication systems, such as 5G new radio (NR) communication systems, or various communication systems evolving after 5G, such as future communication systems. The method provided in this application can also be applied to Bluetooth systems, wireless fidelity (Wi-Fi) systems, long-range radio (LoRa) systems, or vehicle-to-everything (V2X) systems. The method provided in this application can also be applied to terrestrial networks (TN) and non-terrestrial networks (NTN), such as satellite communication systems. For example, it can be applied to transparent satellite architectures, backhaul satellite architectures, or regenerative satellite architectures, etc., without limitation.

[0103] Figure 4 A schematic diagram of a communication system applicable to an embodiment of this application is shown. For example... Figure 4 As shown, the communication system includes an AIoT device, access network equipment, a UDM, an AIoTF, a NEF, and two AFs, namely AF A and AF B. Among them, Figure 4 If the access network device is a reader, or the reader can also be a UE, then the access network device can communicate with the UE acting as a reader, and the reader can then communicate with the AIoT device.

[0104] The network architecture and communication process described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0105] The method provided in the embodiments of this application is described below with reference to the accompanying drawings. In the accompanying drawings corresponding to the various embodiments of this application, all steps indicated by dashed lines are optional steps. In the various embodiments of this application, the AIoT service includes, for example, one or more of the following: inventory operation (or inventory service), read operation (or read service), write operation (or write service), deactivation operation (or deactivation service), or locking operation (or locking service). In the various embodiments of this application, "subordinate" can also be understood as "belonging," "execution," or "control authority," etc. For example, an AIoT device subordinate to a service requester can be understood as the AIoT device belonging to the service requester, or the service requester can instruct the AIoT device to perform corresponding operations, or the service requester has the execution right of the AIoT device, or the service requester has execution authority or control authority over the AIoT device, etc.

[0106] In various embodiments of this application, the subject of the service requester may be, for example, an AF, an AIoT AF, or a passive IoT (P-IoT) AF, or an owner, or an enterprise, or a credential holder, or the Internet Protocol (IP) address of the AF, A-IoT AF, P-IoT AF, owner, enterprise, or credential holder, or the port number of the AF, A-IoT AF, P-IoT AF, owner, enterprise, or credential holder, etc. Alternatively, it can be understood that the information identifying the service requester can be replaced by the aforementioned identifiers. Or, it can be understood that the service requester information identifiable by the core network can be replaced by the aforementioned identifiers. The following text primarily uses the example of a service requester whose subject is an AF (e.g., the subject of the first service requester is AF B, and the subject of the second service requester is AF A).

[0107] In various embodiments of this application, the Internet of Things (IoT) device is, for example, an AIoT device, or other types of IoT devices. The terms "IoT device" or "AIoT device" can also have other names; for example, "IoT" or "AIoT" can be replaced with other names without limitation. This document uses "IoT device" or "AIoT device" as an example. Furthermore, in this embodiment, the IoT device is described as an AIoT device; for example, "AIoT device" as used below can be replaced with "IoT device". In various embodiments of this application, "reader" can be called a reader, a read / write device, or a reader. In various embodiments of this application, "subordinate relationship" can also be replaced with "belonging relationship" or "corresponding relationship".

[0108] Terms such as "affiliation," "usability relationship," "can be used relationship," or "subordinate relationship" are used without restriction on the name; the following text will use "subordinate relationship" as an example. In meaning, an AIoT device having a subordinate relationship with a service requester (e.g., the AIoT device is subordinate to the service requester) means one or more of the following: the AIoT device can be used by the service requester; the service requester can modify the subordinate relationship of the AIoT device; the service requester has the right to use the AIoT device to perform services; or the service requester has the right to manage the relevant permissions of the AIoT device, etc.

[0109] The various embodiments of this application can be applied to Figure 4 The network architecture shown. For example, the first AIoT device described in various embodiments of this application may be... Figure 4 The AIoT device shown; the subject of the first service requester described in various embodiments of this application is, for example, the AIoT device shown. Figure 4 As shown in AF B; the subject of the second service requester described in various embodiments of this application is, for example, AF B. Figure 4 The first network device described in various embodiments of this application is, for example, AF A. Figure 4 The AIoTF shown; the second network device described in various embodiments of this application is, for example, the AIoTF. Figure 4 The UDM shown may be any other network element capable of storing IoT service-related data, such as a unified data repository (UDR) or AIoTF, etc. The following text uses the UDM as an example. In the accompanying drawings corresponding to the various embodiments of this application, all steps indicated by dashed lines are optional.

[0110] In various embodiments of this application, the subject of the first service requester is AF B (or the first service requester is AF B), the subject of the second service requester is AF A (or the second service requester is AF A), the first network device is AIoTF, and the second network device is UDM. That is, in various embodiments of this application, "AF B" can be replaced with "first service requester" or "subject of the first service requester", "AF A" can be replaced with "second service requester" or "subject of the second service requester", "AIoTF" can be replaced with the first network device, and "UDM" can be replaced with the second network device.

[0111] This application provides a communication method, please refer to the embodiments therein. Figure 5 . Figure 5 This is a flowchart of the method.

[0112] S501 and AF B send the first message to UDM. UDM then receives this first message.

[0113] The first message can request a change in the affiliation of the first AIoT device to AF B. For example, if the first AIoT device originally belonged to AF A, this can be understood as the first AIoT device belonging to AF A before the affiliation is changed to AF B. AF B may be unaware of the AF to which the first AIoT device originally belonged, or AF B may be aware that the first AIoT device originally belonged to AF A. For instance, if company A, corresponding to AF A, manufactures the first AIoT device, and the first AIoT device is currently subordinate to AF A; later, when the first AIoT device is shipped to a retailer (e.g., company B) for sale, AF B, corresponding to company B, can send a first message to the UDM to request a change in the affiliation of the first AIoT device to AF B, so that AF B can control the first AIoT device.

[0114] Optionally, the first message may also include one or more of the following: the identifier of the first AIoT device, the identifier of AF A, or the identifier of AF B. The identifier of the first AIoT device enables the UDM to determine which AIoT device the first message is addressed to. The identifier of AF A enables the UDM to determine the AF to which the first AIoT device originally belonged. The identifier of AF B enables the UDM to determine which AF the first message specifically requests to change the first AIoT device's affiliation.

[0115] Optionally, the first message may also indicate the M business requesters and / or whether the affiliation of the first AIoT device can continue to change. M is a positive integer. Whether the affiliation of the first AIoT device can continue to change can be understood as whether the affiliation of the first AIoT device can continue to change when its affiliation is changed to be subordinate to AF B.

[0116] If the affiliation of the first AIoT device to AF B can be changed, then the M service requesters are service requesters that can be changed; that is, the first AIoT device can be changed to be affiliated with any one of the M service requesters. Alternatively, the M service requesters can also be understood as service requesters to whom the first AIoT device can change its affiliation even when its affiliation to AF B is changed.

[0117] Alternatively, the first message may not indicate the M service requesters and / or whether the affiliation of the first AIoT device can continue to change. Optionally, AF B may indicate the M service requesters and / or whether the affiliation of the first AIoT device can continue to change through other messages. For example, if the first AIoT device changes to be affiliated with AF B, AF B may then send a message to UDM to indicate the M service requesters and / or whether the affiliation of the first AIoT device can continue to change.

[0118] S502, UDM changes the dependency of the first AIoT device to be dependent on AF B, or UDM rejects the first message.

[0119] UDM can determine whether the affiliation of the first AIoT device can be changed to affiliation with AFB in a corresponding manner.

[0120] Optionally, the UDM can determine whether the first AIoT device can be changed to be subordinate to AF B based on the third message. If the subordinate relationship of the first AIoT device can be changed to be subordinate to AF B, the UDM can change the subordinate relationship of the first AIoT device to be subordinate to AF B. Optionally, the UDM can store first information indicating that the first AIoT device is subordinate to AF B. Optionally, the UDM can store the first information after changing the subordinate relationship of the first AIoT device to be subordinate to AF B. Optionally, the UDM can also send a ninth message to AF B, which can indicate that the subordinate relationship of the first AIoT device has been changed to be subordinate to AF B. For example, the ninth message may include the identifier of the first AIoT device and a success indication. Optionally, the first information may be stored in the context of the first AIoT device, or in the context of AF B, or in the subscription information of the first AIoT device or AF B, or in a special storage container, without limitation. For example, the UDM may store the first information according to the identifier of the first AIoT device, and / or according to the identifier of AF B.

[0121] If the third message determines that the affiliation of the first AIoT device cannot be changed to be subordinate to AF B, the UDM can reject the first message. For example, the UDM can send a ninth message to AF B, which can indicate rejection of the first message, rejection of changing the affiliation of the first AIoT device to be subordinate to AF B, or rejection of changing the affiliation of the first AIoT device. For example, the ninth message may include the identifier of the first AIoT device and a failure indication. Optionally, the ninth message may also include a cause value for rejection.

[0122] The third message may include dependency information for K AIoT devices, where K is a positive integer. These K AIoT devices may be some or all of the AIoT devices belonging to AF A. These K AIoT devices may include the first AIoT device. For example, the dependency information for the K AIoT devices may include: whether the dependency of each of the K AIoT devices can be changed, and / or at least one service requester to which each AIoT device can change its dependency. For example, for the first AIoT device, the third message may indicate whether the dependency of the first AIoT device can be changed; if it can be changed, optionally, the third message may also indicate that the dependency of the first AIoT device can be changed to belong to N service requesters, where N is a positive integer. Alternatively, the third message may indicate whether the dependency of the first AIoT device can be changed without indicating the service requesters to whom the dependency of the first AIoT device can be changed; if the third message indicates whether the dependency of the first AIoT device can be changed, there may also be other messages (e.g., message A) indicating that the dependency of the first AIoT device can be changed to belong to N service requesters. Optionally, the N service requesters may include AF B. Among them, different AIoT devices can change the same or different business requesters in terms of their subordinate relationships.

[0123] For example, the K AIoT devices include AIoT device 1, AIoT device 2, and AIoT device 3. The third message can indicate that the affiliation of AIoT device 1 can be changed, and that AIoT device 1 can be changed to be affiliated with AF B and AF C. The third message can also indicate that the affiliation of AIoT device 2 cannot be changed. The third message can also indicate that the affiliation of AIoT device 3 can be changed, but does not indicate that AIoT device 3 can change the AF to which it is affiliated. For example, there is also message A indicating that AIoT device 3 can be changed to be affiliated with T AFs, where T is a positive integer.

[0124] Optionally, the third message originates from AF A. For example, the method may further include S503, whereby AF A sends a third message to UDM, and correspondingly, UDM receives the third message. Optionally, S503 may occur before S502, and / or before S501. Figure 5 Take S503 occurring before S501 as an example.

[0125] Alternatively, third-party messages can be pre-configured by the operator or obtained based on implementation, such as based on the service agreement between AF B and AF A.

[0126] Optionally, the type of the third message may be, for example, the type defined in the embodiments of this application, such as an AIoT status notification, or it may be other types. This type may indicate whether the AIoT device can change its affiliation, or indicate the affiliation of the AIoT device.

[0127] Alternatively, the third message type can also be an existing message type, such as an AIoT command. There are no restrictions on the implementation method of the third message.

[0128] The UDM receives a third message and can store its content. Optionally, the UDM can receive at least one message from at least one AF, where each AF's message indicates the dependency information of AIoT devices belonging to that AF, and the UDM can store this information uniformly. The third message can be one of these at least one messages; the following description uses the third message as an example. For example, the content of the third message can be stored in the context of the first AIoT device, or in the context of the first service requester, or in the subscription information of the first AIoT device or the first service requester, or in a special storage container, without specific limitations. For example, the UDM can store the information according to the identifier of the AIoT device, and / or according to the identifier of the service requester. Taking the storage of information according to the identifier of the AIoT device as an example, refer to Table 1, which shows the dependency information of an AIoT device stored by the UDM. Table 1 corresponds to the identifier of the AIoT device.

[0129] Table 1

[0130]

[0131] As shown in Table 1, the AIoT device is currently subordinate to AF A. The subordinate relationship of the AIoT device can be changed, specifically, it can be changed to be subordinate to AF B or AF C.

[0132] For example, UDM can store information based on the identifier of the service requester. Referring to Table 2, the UDM stores the dependency information between a service requester (e.g., AF) and AIoT devices. Table 2 corresponds to the identifier of the service requester, for example, AF A. This service requester can be a service requester currently dependent on corresponding AIoT devices. The information stored in the UDM can indicate whether these AIoT devices can change their dependency relationship and / or which service requesters they can become dependent on.

[0133] Table 2

[0134]

[0135] As shown in Table 3, AIoT device 1, AIoT device 2, and AIoT device 3 are currently subordinate to the service requester. The subordinate relationship of AIoT device 1 can be changed, and AIoT device 1 can be changed to be subordinate to AF B or AF C; the subordinate relationship of AIoT device 2 cannot be changed; the subordinate relationship of AIoT device 3 can be changed, but it is not specified whether AIoT device 3 can change its subordinate AF.

[0136] Continuing with the example of UDM storing information based on the identifier of the service requester, Table 3 shows the affiliation information between a service requester (e.g., AF) and AIoT devices stored in the UDM. Table 3 corresponds to the identifier of the service requester, for example, AF B. The service requester can be one requesting a change in affiliation. The information stored in the UDM can indicate one or more of the following: which AIoT devices the service requester requests to change their affiliation, whether the affiliation of the AIoT devices can be changed, which service requesters the AIoT devices can change their affiliation to, or the service requester to which the AIoT device currently belongs.

[0137] Table 3

[0138]

[0139] As shown in Table 3, AF B requests to change the affiliation of AIoT device 1 to AF B. AIoT device 1 was originally subordinate to AIoT A. The affiliation of AIoT device 1 can be changed, and it can be changed to be subordinate to AF B or AF C.

[0140] In addition to the storage methods mentioned above, UDM can also use other methods to store the content of third messages without restriction.

[0141] If an AF requests a change to the dependency of a corresponding AIoT device, the UDM can determine whether the change can be executed based on a third message (e.g., the content of a third message stored in the UDM). For example, if AF B requests a change to the dependency of the first AIoT device, the UDM can determine whether the dependency of the first AIoT device can be changed based on the third message.

[0142] For example, if the third message indicates that the dependency of the first AIoT device cannot be changed, then the UDM can reject the first message.

[0143] For example, if the third message indicates that the affiliation of the first AIoT device can be changed, and the third message also indicates the business requester whose affiliation of the first AIoT device can be changed, such as the business requester not including AFB, then UDM can reject the first message.

[0144] For example, if the third message indicates that the dependency of the first AIoT device can be changed, and the third message also indicates the business requester that the dependency of the first AIoT device can be changed, such as the business requester including AF B, then UDM can change the first AIoT device to be dependent on AF B.

[0145] For example, if the third message indicates that the affiliation of the first AIoT device can be changed, and the third message does not indicate the business requester that the affiliation of the first AIoT device can be changed, then UDM can change the first AIoT device to be subordinate to AF B.

[0146] Optionally, the method may also include S504 to S507.

[0147] S504, AF A sends the tenth message to AIoTF. Correspondingly, AIoTF receives the tenth message.

[0148] Message A may request to perform a first operation on the first AIoT device, or request to control the first AIoT device, etc.

[0149] S505 and AIoTF send message A to UDM. Correspondingly, UDM receives message A.

[0150] Message A may request or query whether AF A can perform a first operation on the first AIoT device, or request or query whether AF A can perform an operation on the first AIoT device, or request or query whether AF A can control the first AIoT device, or request or query the subordinate relationship of the first AIoT device, etc.

[0151] Optionally, message A may be, for example, an AIoT command request. Message A may include, for example, the identifier of the first AIoT device and the identifier of AIoT.

[0152] S506, UDM sends message B to AIoTF. Correspondingly, AIoTF receives message B.

[0153] Message B may instruct AF A not to perform the first operation on the first AIoT device, or instruct AF A not to perform an operation on the first AIoT device, or instruct AF A not to control the first AIoT device, or instruct the first AIoT device to currently belong to AF B, or instruct the first AIoT device to currently not belong to AF A, etc.

[0154] S507, AIoTF sends a first rejection message to AFA. Correspondingly, AFA receives the first rejection message. The first rejection message may have other names; this embodiment does not limit the name of the message.

[0155] The first rejection message can be used to reject the tenth message. For example, the first rejection message can instruct AF A not to perform the first operation on the first AIoT device, or instruct AF A not to perform an operation on the first AIoT device, or instruct AF A not to control the first AIoT device, etc. Optionally, the first rejection message may also include a rejection reason, such as the first AIoT device currently belonging to AF B or the first AIoT device currently not belonging to AF A.

[0156] Optionally, the first rejection information may be included in the AIoT command response. The first rejection information may include, for example, the identifier of the first AIoT device, and optionally, a reason for rejection.

[0157] It is evident that when the affiliation of an AIoT device changes, the original business requester to which the AIoT device belonged can no longer control the AIoT device, thus allowing the control authority of the AIoT device to belong to the current business requester, thereby reducing the probability of the AIoT device's state becoming chaotic.

[0158] Optionally, the method may also include S508 to S513.

[0159] S508. The first AIoT device sends the sixth information. Correspondingly, the access network device receives the sixth information. This embodiment uses the access network device as a reader as an example. If the access network device is not a reader, the first AIoT device can send the sixth information to the reader, and the reader can send the sixth information to the access network device.

[0160] The sixth information may include first data or first signaling, where the first data is, for example, uplink data initiated by the first AIoT device, and the first signaling is, for example, uplink signaling initiated by the first AIoT device. Optionally, the sixth information may also include the identifier of the first AIoT device. Optionally, the sixth information may be, for example, a device-to-reader (D2R) message, or the sixth information may be included in a D2R message.

[0161] S509: The access network device sends the seventh information to the AIoTF. Correspondingly, the AIoTF receives the seventh information.

[0162] For example, an access network device sends an N2 message to the AIoTF. This N2 message may include first data, the identifier of the first AIoT device, or it may include seventh information. Optionally, the first data and the identifier of the first AIoT device may be included in an AIoT container within the N2 message. The access network device may send the seventh information to the AIoTF directly or via other network elements.

[0163] The S510 and AIoTF send the sixth message to the UDM. The UDM then receives the sixth message.

[0164] The sixth message may request the determination of the affiliation of the first AIoT device, or request the determination of the business requesting party to which the first AIoT device belongs. For example, the sixth message may include the identifier of the first AIoT device.

[0165] S511, UDM sends the seventh message to AIoTF. Correspondingly, AIoTF receives the seventh message.

[0166] The seventh message may indicate the dependency of the first AIoT device, such as indicating that the first AIoT device belongs to AF B. For example, the seventh message may include the identifier of AF B.

[0167] S512, AIoTF sends the first data to AF B. Correspondingly, AF B receives the first data.

[0168] The AIoTF can directly send the first data to AF B without the need for relaying from other network elements; alternatively, the AIoTF can also send the first data to AF B through relaying from other network elements. For example, the AIoTF sends the first data to the NEF, and the NEF then sends the first data to AF B. Optionally, the AIoTF can send an AIoT data report, in which the first data can be included. Optionally, the AIoT data report may also include the identifier of the first AIoT device and / or the identifier of AF B.

[0169] As can be seen, since the UDM stores the dependency relationships of AIoT devices, if an AIoT device initiates uplink data, the AIoTF can request the dependency relationship of the AIoT device from the UDM. In this way, the AIoTF can send the uplink data to the service requester to which the AIoT device is currently dependent, thereby improving the data transmission accuracy.

[0170] This embodiment of the application uses a UDM as an example of a second network device. Alternatively, the second network device can also be an AIoTF. If the second network device is an AIoTF, the AIoTF stores the dependency relationships of AIoT devices. Then, after S504, the AIoTF can determine whether AFA can perform the first operation on the first AIoT device based on the stored information, thereby rejecting AFA's request in S507. That is, S505 and S506 do not need to be executed.

[0171] If the second network device is AIoTF, then after S509, AIoTF can determine the subordinate relationship of the first AIoT device as belonging to AF B based on the stored information, thereby executing S512. That is, S510 and S511 do not need to be executed.

[0172] In summary, in this embodiment, the business requester to which the first AIoT device belongs can change. For example, the first AIoT device may be transported from one enterprise to another, thus changing the enterprise or business requester to which it belongs. This embodiment supports such changes. Therefore, this embodiment can reasonably manage AIoT devices, thereby determining the business requester to which the AIoT device belongs. Furthermore, this embodiment can store first information, enabling the network to clearly identify the current business requester to which the first IoT device belongs. Since network elements such as the UDM in this embodiment can determine the business requester to which the AIoT device belongs, when the AIoT device initiates uplink data, the network can send the uplink data to the current business requester to which the AIoT device belongs, thereby improving the accuracy of data transmission and reducing the probability of sending uplink data to the wrong network element. Moreover, in this embodiment, the UDM can pre-store the affiliation information of the AIoT device (e.g., storing first information). When a business requester requests to change the affiliation of the AIoT device, the UDM can determine whether the affiliation of the AIoT device can be changed based on local information, without needing to query other network elements, thus improving communication efficiency.

[0173] This application provides another communication method, please refer to the embodiments therein. Figure 6 Here is a flowchart of the method.

[0174] S601 and AF B send the first message to UDM. UDM then receives the first message.

[0175] For more information about the S601, please refer to [link / reference]. Figure 5 S501 of the illustrated embodiment.

[0176] S602, UDM changes the first AIoT device to be subordinate to AF B, or UDM rejects the first message.

[0177] Optionally, the UDM can determine whether the affiliation of the first AIoT device can be changed by sending a request to the service requester (e.g., AFA) to which the first AIoT device originally belonged. For example, the method may also include S603 and S604. Optionally, S603 and S604 can occur before S602.

[0178] S603, UDM sends the fourth message to AF A. Correspondingly, AF A receives the fourth message.

[0179] For example, AF A was the service requester to which the first AIoT device originally belonged; that is, before the affiliation of the first AIoT device was changed to belong to AF B, the first AIoT device belonged to AF A. The fourth message may query or inquire whether it is possible to change the affiliation of the first AIoT device to belong to the first service requester. For example, the fourth message may include the identifier of the first AIoT device and / or the identifier of AF B.

[0180] S604, AF A sends a fifth message to UDM. Correspondingly, UDM receives the fifth message. The fifth message may indicate whether the first AIoT device can be changed to be subordinate to AF B. For example, the fifth message may include the identifier of the first AIoT device, and a first indication that may indicate whether the first AIoT device can be changed to be subordinate to AF B, or indicate that the first AIoT device cannot be changed to be subordinate to AF B.

[0181] Optionally, AFA can determine whether it can change the first AIoT device to be subordinate to AFB based on the third message. For details on this determination method, please refer to [link / reference]. Figure 5 S502 of the illustrated embodiment.

[0182] If the fifth message indicates that the first AIoT device can be changed to be subordinate to AF B, then the UDM can change the first AIoT device to be subordinate to AF B. Optionally, the UDM can store first information indicating that the first AIoT device is subordinate to AF B. Optionally, the UDM can also send a ninth message to AF B, which can indicate that the first AIoT device has been changed to be subordinate to AF B. For example, the ninth message may include the identifier of the first AIoT device and a success indication.

[0183] Alternatively, if the fifth message indicates that the first AIoT device cannot be changed to be subordinate to AF B, the UDM can reject the first message. For example, the UDM can send a ninth message to AF B, which can indicate rejection of the first message or rejection of changing the first AIoT device to be subordinate to AF B. For example, the ninth message may include the identifier of the first AIoT device and a failure indication. Optionally, the UDM can store first information, which can indicate that the first AIoT device is subordinate to AF A. This can be understood as the UDM storing the subordinate relationship of the first AIoT device, such as subordinate to AF A or AF B, regardless of whether the subordinate relationship of the first AIoT device can be changed. Thus, if another business requester requests to change the subordinate relationship of the first AIoT device or inquires about the subordinate relationship of the first AIoT device, the UDM does not need to inquire with AF A or AF B again, but can make its own decision.

[0184] Optionally, the method may also include S605 to S608. For details regarding S605 to S608, please refer to... Figure 5 Examples S504 to S507 of the illustrated embodiment.

[0185] Optionally, the method may also include S609 to S614. For details regarding S609 to S614, please refer to... Figure 5 S508 to S513 of the illustrated embodiment.

[0186] In this embodiment, the business requester to which the first AIoT device belongs can change. For example, the first AIoT device may be transported from one enterprise to another, thus changing the enterprise or business requester to which it belongs. This embodiment supports such changes. Therefore, this embodiment can manage AIoT devices reasonably, thereby determining the business requester to which the AIoT device belongs. Furthermore, this embodiment can store first information, enabling the network to clearly identify the current business requester to which the first IoT device belongs. Since network elements such as the UDM in this embodiment can determine the business requester to which the AIoT device belongs, when the AIoT device initiates uplink data, the network can send the uplink data to the current business requester to which the AIoT device belongs, thereby improving the accuracy of data transmission and reducing the probability of sending uplink data to the wrong network element. Moreover, in this embodiment, the UDM does not need to pre-store the AIoT device's affiliation information; when a business requester requests a change in the AIoT device's affiliation, the UDM can query the corresponding business requester, thus saving UDM storage space.

[0187] This application provides yet another communication method; please refer to [reference needed]. Figure 7 . Figure 7 This is a flowchart of the method.

[0188] S701 and AF B send the first message to UDM. UDM then receives the first message.

[0189] The first message may request a change in the affiliation of the first AIoT device to AF B. Optionally, the first message may also include one or more of the following: the identifier of the first AIoT device, the identifier of AF A, or the identifier of AF B. Optionally, the first message may also indicate the M requesting parties and / or indicate whether the affiliation of the first AIoT device can continue to be changed. For more information, please refer to [link / reference needed]. Figure 5 S501 of the illustrated embodiment.

[0190] Optional, except Figure 5 In addition to the content described in S501 of the illustrated embodiment, in this application embodiment, the first message may also include a first network identifier. The first network identifier indicates a first network, which may be the network that the first AIoT device preferentially accesses when it is changed to belong to AF B. For example, the first network is the network corresponding to AF B. The network corresponding to AF B may be, for example, the network where AF B is located, or a network with a service agreement with AF B, or a network that AF B has signed a contract with, etc. The first network identifier may be the identifier of the first network, such as the identifier of the public land mobile network (PLMN) corresponding to AF B, or the network identity number (NID) corresponding to AF B, etc. This application embodiment does not impose any formal limitations.

[0191] For example, when AF B requests to change the affiliation of the first AIoT device to AF B, if it determines that AF B corresponds to a different network than AF A, or determines that the network corresponding to AF B is different from the network where the first AIoT device is located, then the first message may include a first network identifier. Optionally, if AF A is the service requester to which the first AIoT device originally belonged, then the network where the first AIoT device is located may be the network corresponding to AF A. In this case, AF B can determine whether the networks corresponding to AF B and AF A are different, or determine whether the network corresponding to AF B is different from the network where the first AIoT device is located. The service requester to which the first AIoT device originally belonged may be, for example, the service requester that produced the first AIoT device. The network where the first AIoT device is located can be understood or replaced as the network currently accessed by the first AIoT device, the highest priority network in the network selection list of the first AIoT device, or the network that the first AIoT device preferentially accesses.

[0192] Alternatively, if AF A is not the original service requester to which the first AIoT device belonged, then the network where the first AIoT device is located may or may not be the network corresponding to AF A. In this case, AF B can determine whether the network corresponding to AF B is different from the network where the first AIoT device is located.

[0193] If the network where the first AIoT device is located is different from the network corresponding to AF B, even if the first AIoT device is changed to belong to AF B, AF B may still be unable to control the first AIoT device because the first AIoT device may not receive the messages sent by AF B. Therefore, if the network where the first AIoT device is located is different from the network corresponding to AF B, the first message may include a first network identifier, enabling the first AIoT device to reselect a network to access the network indicated by the first network identifier.

[0194] For example, AF B may not need to determine whether the networks corresponding to AF B and AF A are the same, or whether the network corresponding to AF B is the same as the network where the first AIoT device is located. Instead, the UDM determines whether the networks corresponding to AF B and AF A are the same, or whether the network corresponding to AF B is the same as the network where the first AIoT device is located. For instance, when AF B requests to change the affiliation of the first AIoT device to be subordinate to AF B, it can send the first network identifier at the same time (e.g., the first network identifier is included in the first message). This can be understood as AF B not needing to determine whether the networks corresponding to AF B and AF A are the same, but can instead send the first network identifier to the UDM. Optionally, the UDM, upon receiving the first network identifier, can use it to determine whether the networks corresponding to AF B and AF A are the same, or whether the network corresponding to AF B is the same as the network where the first AIoT device is located.

[0195] Alternatively, AF B may not send the first network identifier; UDM can obtain the first network identifier through other means, such as through other network elements within the first network. Optionally, AF B can send the first network identifier to other network elements, and these other network elements can send the first network identifier to UDM.

[0196] S702, UDM changes the first AIoT device to be subordinate to AF B, or UDM rejects the first message.

[0197] For more information about the S702, please refer to [link / reference]. Figure 5 The illustrated embodiments or Figure 6 The illustrated embodiment. That is, in the embodiments of this application, the UDM determines whether the subordinate relationship can be changed, which can be achieved by... Figure 5The embodiments shown provide the method, or adopt the following approach. Figure 6 The illustrated embodiments provide the following approach.

[0198] Optionally, embodiments of this application may also include S703. For example, S703 may be executed if UDM determines that it can change the first AIoT device to be subordinate to AF B, or if UDM has already changed the first AIoT device to be subordinate to AF B.

[0199] S703 and UDM send a second message.

[0200] The second message can trigger or request the first AIoT device to select or access the first network. Specifically, the UDM can send the second message to the AMF serving the first AIoT device, which in turn sends the first network identifier to the first AIoT device. Figure 7 Taking this as an example, the second message could be a network selection information notification, or some other message.

[0201] For example, if AF B sends the first network identifier after determining that the network corresponding to AF B is different from that corresponding to AF A, then if UDM receives the first network identifier, it can execute S703. However, if UDM does not receive the first network identifier, then it does not need to execute S703.

[0202] For example, whether AF B corresponds to the same network as AF A is determined by the UDM. The UDM can obtain the first network identifier from AF B or other network elements, and based on this, the UDM can determine whether AF B corresponds to the same network as AF A, or whether the network corresponding to AF B is the same as the network where the first AIoT device is located (or, the network currently accessed by the first AIoT device; or, the network with the highest priority in the network selection list of the first AIoT device; or, the network that the first AIoT device preferentially accesses). If the networks corresponding to AF B and AF A are different, or the network corresponding to AF B is different from the network where the first AIoT device is located, the UDM can execute S703. However, if the networks corresponding to AF B and AF A are the same, or the network corresponding to AF B is the same as the network where the first AIoT device is located, the UDM may not execute S703.

[0203] The AMF sends the first network identifier to the first AIoT device, for example, through a corresponding procedure. This procedure could be a UE configuration update procedure, or other procedures, such as the registration procedure of the first AIoT device, the procedure for sending downlink data to the first AIoT device, or the procedure for paging the first AIoT device, etc., without limitation. The purpose of sending the first network identifier could be to update the network selection list of the first AIoT device, so the first network identifier could be included in the new network selection list; or it could be that a new network selection list is not sent, but an implicit or explicit instruction is used to make the first AIoT device set the first network identifier as the highest priority in the network selection list of the first AIoT device.

[0204] The second message may include a first network identifier to trigger or request the first AIoT device to select the first network. Optionally, the second message may also include second and / or third information. The second information may also be referred to as time information, or may have other names. The second information may indicate the dwell time of the first AIoT device on the network indicated by the first network identifier. For example, the second information indicates one or more time periods during which the first AIoT device may reside on the first network. If the current time exceeds the time period, the first AIoT device may continue to reside on the first network or may reselect a network. Optionally, the first AIoT device may access the first network at the start time of the time period.

[0205] Alternatively, the second information indicates one or more time points at which the first AIoT device can access the first network.

[0206] The third information may also be called location information, or may have other names. The third information may indicate the first location, and may also indicate that the first AIoT device accesses the network indicated by the first network identifier when it is located at the first location. The third information may include, for example, at least one tracking area code (TAC), closed access group (CAG), or cell identifier.

[0207] If the second message also includes second information and / or third information, then in addition to sending the first network identifier to the first AIoT device, the AMF can also send the second information and / or the third information to the first AIoT device, so that the first AIoT device can select a network according to the requirements of the second message.

[0208] The first AIoT device receives a first network identifier and can preferentially access the first network. Optionally, if the first AIoT device also receives second information, the first AIoT device can access the first network within the time specified by the first information. If the first AIoT device also receives third information, the first AIoT device can access the network indicated by the first network identifier at a first location.

[0209] Optionally, the first AIoT device can also send a fourth message to the UDM. This fourth message can indicate whether the first AIoT device successfully or unsuccessfully selected a network, or whether the first AIoT device successfully or unsuccessfully accessed the first network. For example, the first AIoT device can send the fourth message to the AMF, which in turn sends the fourth message to the UDM. Alternatively, the first AIoT device can also send the fourth message to the UDM through other paths.

[0210] Optionally, upon receiving the fourth message, the UDM may, according to the instructions in the fourth message, change the first AIoT device to be subordinate to AF B, or reject the first message. For example, if the fourth message indicates that the first AIoT device has successfully selected a network, or indicates that the first AIoT device has successfully accessed the first network, then the UDM may change the first AIoT device to be subordinate to AF B; while if the first response message indicates that the first AIoT device has failed to select a network, or indicates that the first AIoT device has failed to access the first network, then the UDM may reject the first message.

[0211] Alternatively, UDM can change the dependency relationship without relying on the fourth piece of information. For example, UDM based on... Figure 5 The illustrated embodiments or Figure 6 In the illustrated embodiment, the first AIoT device is changed to be subordinate to AF B, or the first message is rejected. In this case, the UDM may receive the fourth message, or may not receive the fourth message, and the fourth message may not affect the UDM's decision on whether to change the subordinate relationship.

[0212] Optionally, AIoT can also request to control the first AIoT device; for details, please refer to [link / reference needed]. Figure 5 Examples S504 to S507 of the illustrated embodiment.

[0213] Optionally, when the first AIoT device initiates uplink data, the network can send the uplink data to the service requester (e.g., AFB) to which the first AIoT device currently belongs. For related information, please refer to [link to relevant documentation]. Figure 5 S508 to S513 of the illustrated embodiment.

[0214] This application embodiment can trigger AIoT device network selection to select the network corresponding to the service requester to which the AIoT device currently belongs, so that the service requester can control the AIoT device.

[0215] Figure 8 A schematic diagram of a communication device according to an embodiment of this application is provided. The communication device 800 may be... Figures 5-7 The first AIoT device or its circuitry, as shown in any of the accompanying drawings, is used to implement the method corresponding to the first AIoT device in the above method embodiments. Alternatively, the communication device 800 may be... Figures 5-7 The AIoTF or its circuitry, as shown in any of the accompanying drawings, is used to implement the method corresponding to the AIoTF in the above method embodiments. Alternatively, the communication device 800 may be... Figures 5-7 The UDM or its circuitry, as shown in any of the accompanying drawings, is used to implement the method corresponding to the UDM in the above method embodiments. Alternatively, the communication device 800 may be... Figures 5-7 The AF B or its circuit system, as shown in any of the accompanying drawings, is used to implement the method corresponding to the AF B in the above method embodiments. Alternatively, the communication device 800 may be... Figures 5-7 The AF A or its circuit system, as shown in any of the accompanying drawings, is used to implement the method corresponding to AF A in the above method embodiments. Alternatively, the communication device 800 may be... Figure 7 The AMF or circuit system of the illustrated embodiment is used to implement the method corresponding to the AMF in the above method embodiments. For example, one type of circuit system is a chip system.

[0216] The communication device 800 includes at least one processor 801. The processor 801 can be used for internal processing within the device to implement certain control processing functions. Optionally, the processor 801 includes instructions. Optionally, the processor 801 can store data. Optionally, different processors can be independent devices, located in different physical locations, or located on different integrated circuits. Optionally, different processors can be integrated into one or more processors, for example, integrated on one or more integrated circuits.

[0217] Optionally, the communication device 800 includes one or more memories 803 for storing instructions. Optionally, the memories 803 may also store data. The processor and the memories may be separate or integrated together.

[0218] Optionally, the communication device 800 includes a communication line 802 and at least one communication interface 804. Since the memory 803, communication line 802, and communication interface 804 are all optional, therefore... Figure 8 All are represented by dashed lines.

[0219] Optionally, the communication device 800 may further include a transceiver and / or an antenna. The transceiver can be used to send information to or receive information from other devices. The transceiver may be referred to as a transceiver unit, transceiver circuit, input / output interface, etc., and is used to realize the transmission and reception functions of the communication device 800 via the antenna. Optionally, the transceiver includes a transmitter and a receiver. For example, the transmitter can be used to generate a radio frequency (RF) signal from a baseband signal, and the receiver can be used to convert the RF signal back into a baseband signal.

[0220] The processor 801 may include a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of programs according to the present application.

[0221] Communication line 802 may include a path for transmitting information between the aforementioned components.

[0222] The communication interface 804 uses any transceiver-like device for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area network (WLAN), wired access network, etc.

[0223] The memory 803 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory 803 may exist independently and be connected to the processor 801 via communication line 802. Alternatively, the memory 803 may be integrated with the processor 801.

[0224] The memory 803 stores computer execution instructions for implementing the scheme of this application, and its execution is controlled by the processor 801. The processor 801 executes the computer execution instructions stored in the memory 803 to achieve one or more of the following: Figures 5-7 The steps performed by the first AIoT device in any of the embodiments shown in the accompanying drawings, Figures 5-7 The steps performed by AIoTF as described in any of the embodiments shown in the accompanying drawings. Figure 7 The steps performed by the AMF as described in the illustrated embodiment, Figures 5-7 The steps performed by AF B as described in any of the embodiments shown in the accompanying drawings, Figures 5-7 The steps performed by the UDM as described in any of the embodiments shown in the accompanying drawings, or, Figures 5-7 The steps performed by AF A as described in any of the embodiments shown in the accompanying drawings.

[0225] Optionally, the computer execution instructions in the embodiments of this application may also be referred to as application code, and the embodiments of this application do not specifically limit this.

[0226] In a specific implementation, as an example, processor 801 may include one or more CPUs, for example... Figure 8 CPU0 and CPU1 in the CPU.

[0227] In a specific implementation, as an example, the communication device 800 may include multiple processors, such as... Figure 8 Processors 801 and 805 are mentioned. Each of these processors can be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor here can refer to one or more devices, circuits, and / or processing cores used to process data (e.g., program instructions).

[0228] when Figure 8 When the device shown is a chip, such as the chip of a first AIoT device, a UDM chip, an AFB chip, an AFA chip, an AMF chip, or an AIoTF chip, then the chip includes a processor 801 (and may also include a processor 805), a communication line 802, and a communication interface 804. Optionally, it may include a memory 803. Specifically, the communication interface 804 may be an input interface, pins, or circuits, etc. The memory 803 may be a register, cache, etc. The processor 801 and processor 805 may be a general-purpose CPU, microprocessor, ASIC, or one or more integrated circuits for controlling the execution of a program that controls the communication method of any of the above embodiments.

[0229] This application embodiment can divide the device into functional modules according to the above method example. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware or as software functional modules. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. For example, when dividing the device into functional modules according to each function, Figure 9 This is a schematic diagram of an apparatus. The apparatus 900 may be the first AIoT device, AIoTF, AMF, AF B, AF A, or UDM involved in the above-described method embodiments, or a chip in the first AIoT device, AIoTF, AMF, AF B, AF A, or UDM. The apparatus 900 includes a processing unit 902 and a transceiver unit 901.

[0230] It should be understood that the device 900 can be used to implement the steps performed by the first AIoT device and / or AIoTF and / or AMF and / or AF B and / or AF A and / or UDM in the communication method of the embodiments of this application, and the relevant features can be referred to above. Figures 5-7 The embodiments shown in the figure will not be described in detail here.

[0231] Optional, Figure 9 The functions / implementation process of the transceiver unit 901 and the processing unit 902 can be obtained through Figure 8 The processor 801 in the memory calls computer execution instructions stored in memory 803 to implement the function. Alternatively, Figure 9 The function / implementation process of the processing unit 902 in the middle can be achieved through Figure 8 The processor 801 in the memory calls computer execution instructions stored in the memory 803 to implement this. Figure 9 The function / implementation process of the transceiver unit 901 in the middle can be obtained through Figure 8 It is implemented using the 804 communication interface.

[0232] Optionally, when the device 900 is a chip or circuit, the function / implementation process of the transceiver unit 901 can also be implemented through pins or circuits. Optionally, the transceiver unit 901 may include a transmitting unit and / or a receiving unit, whereby the transmitting unit implements the transmitting function and the receiving unit implements the receiving function; or, the transceiver unit 901 may be an integral module capable of implementing both transmitting and / or receiving functions. Optionally, the transceiver unit 901 can be implemented using a transceiver.

[0233] This application also provides a computer-readable storage medium storing a computer program or instructions that, when executed, implement the methods performed by the first AIoT device and / or AIoTF and / or AMF and / or AF B and / or AF A and / or UDM in the aforementioned method embodiments. Thus, the functions described in the above embodiments can be implemented as software functional units and sold or used as independent products. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to it, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0234] This application also provides a computer program product comprising: computer program code, which, when executed on a communication device, causes the communication device to perform the method executed by the first AIoT device and / or AIoTF and / or AMF and / or NEF and / or AF in any of the foregoing method embodiments.

[0235] This application also provides a processing apparatus, including a processor and an interface; the processor is used to execute the methods performed by the first AIoT device and / or AIoTF and / or AMF and / or AF B and / or AF A and / or UDM involved in any of the above method embodiments.

[0236] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0237] The various illustrative logic units and circuits described in the embodiments of this application can be implemented or operate the described functions using a general-purpose processor, digital signal processor (DSP), ASIC, field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. The general-purpose processor can be a microprocessor; alternatively, it can be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented using a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other similar configuration.

[0238] The steps of the methods or algorithms described in the embodiments of this application can be directly embedded in hardware, software units executed by a processor, or a combination of both. The software units can be stored in RAM, flash memory, ROM, erasable programmable read-only memory (EPROM), EEPROM, registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium in the art. Exemplarily, the storage medium can be connected to the processor so that the processor can read information from the storage medium and write information to the storage medium. Optionally, the storage medium can also be integrated into the processor. The processor and storage medium can be disposed in an ASIC, which can be disposed in the terminal device. Optionally, the processor and storage medium can also be disposed in different components of the terminal device.

[0239] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0240] The contents of the various embodiments of this application can be referenced to each other. Unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0241] It is understood that in the embodiments of this application, the first AIoT device and / or AIoTF and / or AMF and / or AF B and / or AF A and / or UDM can perform some or all of the steps in the embodiments of this application. These steps or operations are merely examples. In the embodiments of this application, other operations or variations of various operations can also be performed. Furthermore, the steps can be performed in different orders as presented in the embodiments of this application, and it is not necessary to perform all the operations in the embodiments of this application.

Claims

1. A communication method characterized by comprising: The method includes: Receive a first message, the first message requesting to change the affiliation of the first IoT device to affiliation with the first business requester, wherein, before changing the affiliation of the first IoT device to affiliation with the first business requester, the first IoT device is affiliation with the second business requester; If the affiliation of the first IoT device is changed to be subordinate to the first service requester, first information is stored, and the first information indicates that the first IoT device is subordinate to the first service requester.

2. The method of claim 1, wherein, The first message also includes one or more of the following: The identifier of the first Internet of Things device; The identifier of the first service requester; or, The identifier of the second service requester.

3. The method according to claim 1 or 2, characterized in that, The first message also includes a first network identifier, which indicates a first network, which is the network that the first IoT device preferentially accesses when the first IoT device is changed to be subordinate to the first service requester.

4. The method of claim 3, wherein, The method further includes: If the first network is different from the network currently accessed by the first IoT device, a second message is sent, which triggers the first IoT device to select the first network.

5. The method of claim 4, wherein, The second message also includes: The second information indicates the dwell time of the first IoT device on the first network; and / or The third information indicates a first location and indicates that the first IoT device selects the first network when it is located at the first location.

6. The method according to any one of claims 1 to 5, characterized in that, Before receiving the first message, the method further includes: Receive a third message from the second service requester, wherein the third message indicates that the first IoT device belongs to the second service requester and indicates whether the affiliation of the first IoT device can be changed.

7. The method of claim 6, wherein, The method further includes: Based on the third message, it is determined whether the first IoT device can be changed to be subordinate to the first service requester.

8. The method according to claim 6 or 7, characterized in that, The third message indicates that the affiliation of the first IoT device can be changed, and also indicates that the affiliation of the first IoT device can be changed to belong to N service requesters, where the N service requesters include the first service requester and N is a positive integer.

9. The method according to any one of claims 1 to 5, characterized in that, After receiving the first message, the method further includes: A fourth message is sent to the second service requester, the fourth message querying whether the first IoT device can be changed to belong to the first service requester; A fifth message is received, indicating whether the first IoT device can be changed to be subordinate to the first service requester.

10. The method of claim 9, wherein, The fifth message indicates that the first IoT device cannot be changed to be subordinate to the first service requester, and also indicates the reason why it cannot be changed.

11. The method according to any one of claims 1 to 10, characterized in that, The method further includes: Receive a sixth message from the first network device, the sixth message requesting the identification of the service requester to which the first IoT device belongs; A seventh message is sent to the first network device, the seventh message being used to indicate that the first IoT device belongs to the first service requester.

12. The method of claim 11, wherein, The first network device is an Environmental Internet of Things (AIoTF) device.

13. The method according to any one of claims 1 to 12, characterized in that, The method is executed by AIoTF, and the method further includes: Receive the identifier of the first IoT device and the first data; Send the first data to the first service requester.

14. The method according to any one of claims 1 to 13, characterized in that, The first service requester is the first application function (AF), and the second service requester is the second application function (AF).

15. A method of communication, comprising: The method includes: Send a first message to the second network device, the first message requesting to change the affiliation of the first IoT device to that of the first service requester, wherein the first IoT device was affiliated with the first service requester before the affiliation of the first IoT device was changed to that of the first service requester; A ninth message is received, which indicates that the affiliation of the first IoT device has been changed to be subordinate to the first service requester, or indicates that the affiliation of the first IoT device is refused.

16. The method of claim 15, wherein, The first message also includes one or more of the following: The identifier of the first IoT device; The identifier of the first service requester; or, The identifier of the second service requester.

17. The method according to claim 15 or 16, characterized in that, When the first network is different from the network currently accessed by the first IoT device, the first message also includes a first network identifier, which indicates the first network, wherein the first network is the network that the first IoT device preferentially accesses when the first IoT device is changed to belong to the first service requester.

18. The method according to any one of claims 15 to 17, characterized in that, The first message also includes: The second information indicates the dwell time of the first IoT device on the first network; and / or The third information indicates a first location and indicates that the first IoT device selects a first network when it is located at the first location.

19. A communications device, characterized by The communication device includes a module for performing the method as described in any one of claims 1 to 14, or includes a module for performing the method as described in any one of claims 15 to 18.

20. A communications device, characterized by The communication device includes a processor, which is configured to perform the method as described in any one of claims 1 to 14, or the method as described in any one of claims 15 to 18.

21. A computer-readable storage medium, characterized in that, The computer-readable storage medium is stored in the communication device, and the computer-readable storage medium stores a computer program that, when the computer program is run by the communication device, causes the method as described in any one of claims 1 to 14 to be performed, or causes the method as described in any one of claims 15 to 18 to be performed.

22. A computer program product, characterised in that, The computer program product includes a computer program that, when run on a communication device, causes the method as described in any one of claims 1 to 14 to be executed, or causes the method as described in any one of claims 15 to 18 to be executed.

Images