Communication method and device

Abstract

The present application relates to a communication method and a device. A first ambient Internet of Things device transmits a first message, the first message comprising a second identifier, the second identifier being used for identifying the first ambient Internet of Things device, and the first ambient Internet of Things device being an active ambient Internet of Things device; the first ambient Internet of Things device receives a random number; and the first ambient Internet of Things device generates a first identifier on the basis of the random number and the second identifier, the first identifier being used for temporarily identifying the first ambient Internet of Things device. Before transmitting the first message, the first ambient Internet of Things device has not received a paging message from a first reader, wherein the first reader is a reader that has established a communication connection with the first ambient Internet of Things device. When needing to transmit the identifier of the first ambient Internet of Things device to a network, the first ambient Internet of Things device can transmit the first identifier without transmitting the second identifier, thereby reducing the probability of exposing the second identifier at an ambient Internet of Things interface, and thus improving the communication security.

Description

A communication method and apparatus

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202510380581.4, filed on March 26, 2025, entitled "A Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

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

[0004] With the development of communication technology, the 3rd Generation Partnership Project (3GPP) defined the Ambient Internet of Things (A-IoT) technology. The devices involved in AIoT technology include readers and AIoT devices. Data transmission can be performed between readers and AIoT devices; for example, an AIoT device can send its device ID to a reader.

[0005] Exposing the device ID of an AIoT device in the AIoT interface reduces communication security. Summary of the Invention

[0006] This application provides a communication method and apparatus to improve communication security.

[0007] Firstly, a first communication method is provided. This method can be applied to a first device. The first device is, for example, a terminal-side device, also referred to as a terminal device or a terminal. The terminal device is, for example, a terminal equipment, or other equipment including terminal equipment functions, or a circuit, or a system-on-a-chip (or, a chip, such as a modem chip, also known as a baseband chip, or a system-on-a-chip (SoC) chip containing a modem core, or a system-in-package (SIP) chip) or other functional module, which is capable of implementing the functions of the terminal equipment, and which is, for example, disposed in the terminal equipment. Optionally, the terminal device is, for example, an environmental IoT device, and may be referred to as a first environmental IoT device. The method includes: sending a first message, the first message including a second identifier, the second identifier being used to identify a first environmental IoT device, the first environmental IoT device being an active environmental IoT device; receiving a random number; generating a first identifier based on the random number and the second identifier, the first identifier being used to temporarily identify the first environmental IoT device; wherein, before sending the first message, the first environmental IoT device has not received a paging message from a first reader / writer, the first reader / writer being a reader / writer that has established a communication connection with the first environmental IoT device.

[0008] The first environmental IoT device in this embodiment can receive a random number from the network, thereby generating a first identifier. The first identifier can be used to temporarily identify the first environmental IoT device. Therefore, when the first environmental IoT device needs to send its identifier to the network, it can send the first identifier instead of the second identifier, reducing the probability of exposing the second identifier to the AIoT interface and improving communication security.

[0009] In one optional implementation, the first IoT device is an active environmental IoT device. Optionally, the active environmental IoT device may be, for example, device C or device 2b. It can be understood that the embodiments of this application provide a method for such environmental IoT devices to obtain temporary identifiers.

[0010] In one alternative implementation, the first reader / writer is an access network device or a terminal device.

[0011] Secondly, a second communication method is provided. This method can be applied to a second device. The second device is, for example, a network-side device, also referred to as a network device. The network device is, for example, a network equipment, or other equipment including network equipment functions, or a circuit, or a chip system (or chip) or other functional module, which can implement the functions of the network equipment, and is, for example, disposed in the network equipment. The network equipment is, for example, an access network equipment or a core network equipment. Optionally, the first device is, for example, an AIoTF or AMF, etc. The method includes: receiving a first message, the first message being from a first environmental IoT device, the first message including a second identifier of the first environmental IoT device, the second identifier being used to identify the first environmental IoT device; in response to receiving the first message, sending a random number to the first environmental IoT device; wherein, before receiving the first message, the first core network device has not sent a service request to a first reader / writer, the first reader / writer being a reader / writer that has established a communication connection with the first environmental IoT device.

[0012] In one alternative implementation, the first IoT device is an active environmental IoT device, and the first core network device is an AIoTF or an AMF.

[0013] In one alternative implementation, the first reader / writer is an access network device or a terminal device.

[0014] 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.

[0015] Thirdly, a third communication method is provided. This method can be applied to a third device. The third device is, for example, a terminal-side device, also referred to as a terminal device or a terminal. This terminal device is, for example, a terminal equipment, or other equipment including terminal equipment functions, or a circuit, or a system-on-a-chip (or, a chip, such as a modem chip, also known as a baseband chip, or a system-on-a-chip (SoC) chip containing a modem core, or a system-in-package (SIP) chip) or other functional module, which can realize the functions of the terminal equipment, and which is, for example, disposed in the terminal equipment. Optionally, the terminal device is, for example, an environmental IoT device, which can be referred to as a first environmental IoT device. Optionally, the third device and the first device can be the same device. The method includes: sending a second message, the second message including a second identifier, the second identifier being used to identify a first environmental IoT device; receiving a first identifier, the first identifier being used to temporarily identify the first environmental IoT device, the first identifier being determined based on the second identifier and a third identifier, the third identifier being an identifier of an AIoTF, or an identifier of a set to which the AIoTF belongs, or an identifier of a region where the AIoTF is located, the AIoTF being an AIoTF serving the first environmental IoT device.

[0016] In this embodiment, the network assigns a first identifier to the first AIoT device. For example, the network can assign different identifiers to different AIoT devices, so that one identifier can uniquely identify one AIoT device, reducing collisions. Since the first identifier is assigned to the first AIoT device, the first AIoT device can send the first identifier instead of the second identifier when it needs to send its own identifier, which improves communication security and reduces signaling overhead.

[0017] In one optional implementation, the first identifier is determined based on the second identifier and the third identifier, including: the first identifier is determined based on the second identifier, the third identifier, and the identifier of the AMF, wherein the AMF is the AMF serving the IoT device in the first environment. The first identifier can be determined based on the third identifier, or based on the third identifier and the identifier of the AMF, thereby improving transmission reliability by routing based on the first identifier during transmission.

[0018] In one alternative implementation, the second message is an initial registration request message. Alternatively, the second message can be other messages, such as messages for transmitting data; there is no limitation on the type of the second message.

[0019] Fourthly, a fourth communication method is provided. This method can be applied to a fourth device. The fourth device is, for example, a network-side device, also referred to as a network device. The network device is, for example, a network equipment, or other equipment including network equipment functions, or a circuit, or a chip system (or chip) or other functional module capable of implementing the functions of the network equipment, and the chip system or functional module is, for example, disposed in the network equipment. The network equipment is, for example, an access network equipment or a core network equipment. Optionally, the fourth device is, for example, an AIoTF or AMF, etc. Optionally, the fourth device and the second device can be the same device. The method includes: receiving a second identifier, the second identifier being used to identify a first environment IoT device; determining a first identifier based on the second identifier and a third identifier, the first identifier being used to temporarily identify the first environment IoT device, the third identifier being an identifier of a first core network device, or an identifier of a set to which the first core network device belongs, or an identifier of the area where the first core network device is located, the first core network device being a core network device serving the first environment IoT device; and sending the first identifier.

[0020] In one optional implementation, determining the first identifier based on the second identifier and the third identifier includes: determining the first identifier based on the second identifier, the third identifier, and the identifier of the second core network device.

[0021] In one alternative implementation, receiving a second identifier of a first environmental IoT device includes receiving a second message, the second message including the second identifier.

[0022] In one alternative implementation, the second message is an initial registration request message.

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

[0024] Fifthly, a communication device is provided. The communication device may be the first device described in the first aspect or the third device described in the third aspect. The communication device possesses the functions of the first or third device. For example, the communication device may implement the functions described in the first or third aspect, such as including modules, units, or means corresponding to performing the operations involved in the first or third aspect. These modules, units, or means may be implemented in software, hardware, or a combination of software and hardware. The communication device may be, for example, a terminal device, or other device including terminal device functions, or a chip system (or chip or circuit) or other functional module capable of implementing the functions of a terminal device, and may be, for example, disposed in a terminal device. 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). A transceiver unit can perform both sending and receiving functions. When the transceiver unit performs the sending function, it can be called a sending unit (sometimes also called a sending module), and when it performs the receiving function, it can be called a receiving unit (sometimes also called a receiving module). The sending unit and the receiving unit can be the same functional module, which is called the transceiver unit and can perform both sending and receiving functions; or, the sending unit and the receiving unit can be different functional modules, and the transceiver unit is a collective term for these functional modules.

[0025] In one optional implementation, the transceiver unit (or the sending unit) is configured to send a first message, the first message including a second identifier, the second identifier being used to identify the first environmental IoT device, the first environmental IoT device being an active environmental IoT device; the transceiver unit (or the receiving unit) is configured to receive a random number; the processing unit is configured to generate a first identifier based on the random number and the second identifier, the first identifier being used to temporarily identify the first environmental IoT device; wherein, before sending the first message, the first device (or the transceiver unit) has not received a paging message from a first reader / writer, the first reader / writer being a reader / writer that has established a communication connection with the first device.

[0026] In one optional implementation, the transceiver unit (or the sending unit) is configured to send a second message, the second message including a second identifier, the second identifier being used to identify a first environmental IoT device; the transceiver unit (or the receiving unit) is configured to receive a first identifier, the first identifier being used to temporarily identify the first environmental IoT device, the first identifier being determined based on the second identifier and a third identifier, the third identifier being an identifier of an AIoTF, or an identifier of a set to which the AIoTF belongs, or an identifier of the region where the AIoTF is located, the AIoTF being an AIoTF serving the first environmental IoT device.

[0027] In an alternative embodiment, the communication device further includes a storage unit (sometimes also called a storage module), and a 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 first device described in the first aspect or the third device described in the third aspect.

[0028] Sixthly, a communication device is provided. The communication device may be the second device described in the second aspect or the fourth device described in the fourth aspect. The communication device possesses the functions of the second or fourth device. For example, the communication device is capable of implementing the functions described in the second or fourth aspect. For instance, the communication device includes modules, units, or means corresponding to performing the operations involved in the second or fourth aspect. These modules, units, or means can be implemented through software, hardware, or a combination of software and hardware. The communication device may be, for example, a network device, or other device including network device functions, or a chip system (or chip or circuit) or other functional module capable of implementing the functions of a network device. This chip system or functional module may be, for example, disposed within a network device. 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). For details on the implementation of the transceiver unit, please refer to the description in the fifth aspect.

[0029] In one optional implementation, the transceiver unit (or the receiving unit) is configured to receive a first message, the first message being from a first environmental IoT device, the first message including a second identifier of the first environmental IoT device, the second identifier being used to identify the first environmental IoT device; the transceiver unit (or the sending unit) is configured to send a random number to the first environmental IoT device in response to receiving the first message; wherein, prior to receiving the first message, the first core network device (or the transceiver unit; or the second device) has not sent a service request to the first reader / writer, the first reader / writer being a reader / writer that has established a communication connection with the first environmental IoT device.

[0030] In one optional implementation, the transceiver unit (or the receiving unit) is configured to receive a second identifier, the second identifier being used to identify a first environmental IoT device; the processing unit is configured to determine a first identifier based on the second identifier and a third identifier, the first identifier being used to temporarily identify the first environmental IoT device, the third identifier being an identifier of a first core network device (or the fourth device), or an identifier of a set to which the first core network device belongs, or an identifier of the region where the first core network device is located, the first core network device being a core network device serving the first environmental IoT device; the transceiver unit (or the sending unit) is configured to send the first identifier.

[0031] 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 second device described in the second aspect above, or to enable the communication device to perform the functions of the fourth device described in the fourth aspect above.

[0032] A seventh aspect provides an apparatus comprising a memory and one or more processors. The memory is used to store part or all of a computer program or instructions necessary for implementing the functions described in the first or third aspect above. The one or more processors are executable to carry out the computer program or instructions, such that, when executed, the apparatus implements the methods in any possible design or implementation of the first or third aspect above.

[0033] In one possible design, the device may further include interface circuitry, wherein the processor is configured to communicate with other devices or components via the interface circuitry.

[0034] In one possible design, the device may also include the memory.

[0035] The aforementioned device may be a terminal, or a communication module in the terminal, or a chip in the terminal responsible for communication functions such as a modem chip (also known as a baseband chip) or a SoC or SIP chip containing a modem module.

[0036] Eighthly, an apparatus is provided, the apparatus comprising a memory and one or more processors. The memory is used to store part or all of a computer program or instructions necessary for implementing the functions involved in the second or fourth aspect described above. The one or more processors are executable to carry out the computer program or instructions, such that, when executed, the apparatus implements the methods in any possible design or implementation of the second or fourth aspect described above.

[0037] In one possible design, the device may further include interface circuitry, wherein the processor is configured to communicate with other devices or components via the interface circuitry.

[0038] In one possible design, the device may also include the memory.

[0039] The aforementioned device may be a network device, a communication module in a network device, or a chip in a network device that is responsible for communication functions, such as a modem chip (also known as a baseband chip) or a SoC or SIP chip that contains a modem module.

[0040] A ninth aspect provides a communication system including a first core network device. The first core network device is used to perform the method described in the second aspect, which is executed by the second apparatus. For example, the first core network device can be implemented using the apparatus described in the sixth or eighth aspect.

[0041] Optionally, the communication system further includes a first environmental IoT device, wherein the first environmental IoT device is used to perform the method executed by the first device as described in the first aspect. For example, the first environmental IoT device can be implemented using the device described in the fifth or seventh aspect.

[0042] In a tenth aspect, another communication system is provided, including a first core network device. The first core network device is used to perform the method executed by the fourth apparatus as described in the fourth aspect above. For example, the first core network device can be implemented using the apparatus described in the sixth or eighth aspect.

[0043] Optionally, the communication system further includes a first environmental IoT device, wherein the first environmental IoT device is used to perform the method performed by the first device as described in the third aspect above. For example, the first environmental IoT device can be implemented using the device described in the fifth or seventh aspect.

[0044] Eleventhly, a computer-readable storage medium is provided for storing a computer program or instructions that, when executed, cause the method performed by the first, second, third, or fourth means described above to be implemented.

[0045] In a twelfth 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.

[0046] In a thirteenth aspect, a chip system is provided, including a processor and an interface, the processor being configured to call and execute instructions from the interface to enable the chip system to implement the methods described above. Attached Figure Description

[0047] Figures 1 and 2 are schematic diagrams of two structures of the access network device in the embodiments of this application;

[0048] Figure 3 is a schematic diagram of the working mode of the reader and AIoT device;

[0049] Figure 4 is an AS flow diagram between the AIoT device and the reader / writer;

[0050] Figure 5 is a flowchart of the AIoT random access process;

[0051] Figures 6 to 10 are schematic diagrams of several network architectures applicable to the embodiments of this application;

[0052] Figure 11 is a schematic diagram of the logical system architecture of Topology 1;

[0053] Figure 12 is a schematic diagram of the AIoT-related processes defined under Topology 1;

[0054] Figure 13 is a schematic diagram of the direct connection between AIoT RAN and AIoTF under Topology 1;

[0055] Figure 14 is a schematic diagram of the non-direct connection between AIoT RAN and AIoTF under Topology 1;

[0056] Figure 15 is a schematic diagram of the logical system architecture of Topology 2;

[0057] Figure 16 is a schematic diagram of a protocol stack corresponding to Topology 2;

[0058] Figure 17 is a schematic diagram of direct connection between AIoT-enabled gNB and AIoTF in topology 2;

[0059] Figure 18 is a schematic diagram of the non-direct connection between AIoT-enabled gNB and AIoTF under topology 2;

[0060] Figure 19 is a schematic diagram of another protocol stack corresponding to Topology 2;

[0061] Figure 20 is a schematic diagram of another protocol stack corresponding to Topology 2;

[0062] Figures 21 to 24 are flowcharts of several communication methods provided in the embodiments of this application;

[0063] Figure 25 is a schematic diagram of an apparatus provided in an embodiment of this application;

[0064] Figure 26 is a schematic diagram of another device provided in an embodiment of this application. Detailed Implementation

[0065] 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.

[0066] 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 preceding and following related objects 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.

[0067] 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.

[0068] 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.

[0069] (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, things, 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.

[0070] 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.

[0071] 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.

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

[0073] 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.

[0074] (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 functionality, 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.

[0075] In a CU-DU architecture, or in an open RAN (ORAN) system, access network equipment can 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 can 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 is shown in Figure 1. In this structure, core network equipment and access network equipment can communicate via a backhaul link; within the access network equipment, CUs and DUs can communicate via a midhaul link, and DUs and RUs can communicate via a fronthaul link.

[0076] Alternatively, another architecture for the access network device can be seen in Figure 2, which illustrates an access network device implemented using a chip, 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 computation and radio frequency (RF) digital functions, etc. The CU communicates with the core network device through a backhaul interface, which carries the traffic between the CU and the core network device. The CU may include a central processing unit (CPU) based on x86 or ARM architecture, and may include a field-programmable gate array (FPGA), graphics processing unit (GPU), or other accelerators. The CPU can communicate with the FPGA, GPU, or other accelerators via a peripheral component interconnect express (PCIe) interface.

[0077] 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.

[0078] 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.

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

[0080] 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.

[0081] 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). As another example, 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).

[0082] 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.

[0083] 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.

[0084] 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).

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

[0086] 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.

[0087] AIoT devices can perform business with corresponding devices. In this case, the AIoT device can be called a device, such as 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.

[0088] 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.

[0089] 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.

[0090] In AIoT, AIoT devices (such as tags) and readers can communicate, as shown in 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.

[0091] AIoT technology can include network devices and first-type terminal devices, or, an AIoT-based communication system can include network devices and first-type terminal devices. The first-type terminal devices can be devices with AIoT terminal device functionality. In this case, both the reader / writer and the AIoT terminal device can be implemented based on cellular network infrastructure. In other words, both the reader / writer and the AIoT terminal device can be devices within a cellular network. The AIoT terminal device can also be referred to as an AIoT device.

[0092] For example, the functionality of a reader / writer can be implemented by network devices, such as base stations. AIoT terminal devices can be implemented by terminal devices in cellular networks, such as ultra-low power, ultra-low complexity IoT terminal devices, i.e., the first type of terminal devices. Network devices can perform contactless data communication with the first type of terminal devices, thereby reading information from the first type of terminal devices and / or writing information that needs to be stored into the first type of terminal devices. AIoT technology can be used to implement one or more of the following services: inventory, positioning, sensing, or command. It can be understood that command services can be services that implement write or lock processes. In terms of application scope, AIoT technology can be applied to scenarios such as logistics, warehousing, industrial manufacturing, identity recognition, or environmental monitoring.

[0093] The 3rd Generation Partnership Project (3GPP) plenary meeting defined an extremely low-power, low-complexity Internet of Things (IoT) technology, which can be understood as an extension of radio frequency identification (RFID) within 3GPP. While this IoT technology shares some principles with RFID, such as similar inventory management processes, it will introduce more value-added scenarios within 3GPP.

[0094] AIoT is based on cellular network communication infrastructure and consists of readers (such as base stations) and passive / semi-passive / active AIoT terminal devices (AIoT terminal devices are terminal devices in the cellular network, which can be understood as extremely low-power, extremely low-complexity IoT terminal devices). Its main functions include inventory management, positioning, sensing, or command functions, among others. Typical application scenarios include logistics, warehousing, industrial manufacturing, identity recognition, and environmental monitoring.

[0095] The following examples illustrate various AIoT services.

[0096] Inventory management involves using a reader (which can be a base station or a terminal) to connect A-IoT devices within the coverage area. Successfully connected AIoT devices need to send their unique identifier to the reader. Inventory management, also known as a checklist operation, is used to obtain the identifiers of AIoT devices.

[0097] Location services utilize positioning signals to pinpoint the location of AIoT devices.

[0098] In the sensing business, AIoT devices can report sensing data to the base station, such as temperature data.

[0099] Command operations can be a series of operational instructions. For example, command operations can include at least one of the following: read, write, disable, enable, kill, or lock operations.

[0100] The read function can read the electronic product code (EPC), tag identifier (TID) in the storage area of ​​the AIoT device, the content stored in the reserved area of ​​the AIoT device, or the content stored in the user storage area.

[0101] The write operation allows for writing to the storage area of ​​an AIoT device. For example, a base station can send a write command (or write request) and data, instructing the AIoT device to write the data into its storage area.

[0102] Disable service: Request AIoT devices to permanently or temporarily disable their radio frequency (RF) transmission capabilities.

[0103] Enable service, requesting the activation of temporarily disabled AIoT devices.

[0104] The kill function can make AIoT devices permanently unusable.

[0105] Locking services can lock the information of an AIoT device, preventing read or write operations on that device. Alternatively, locking services can also lock a storage area, preventing or allowing read or write operations on that storage area.

[0106] The above are just examples. AIoT devices and readers can also perform other services or operations, which will not be listed here.

[0107] In AIoT, AIoT devices can be divided into three categories: Device A, Device B, and Device C.

[0108] Device A (similar to a passive tag) has no energy storage, cannot generate signals independently, and can transmit signals using backscattering.

[0109] Device B (similar to a semi-passive tag) has energy storage but cannot generate signals independently. It can transmit signals using backscattering, and the energy stored in Device B can amplify the reflected signal.

[0110] Device C (similar to an active tag) has energy storage, can generate signals independently, and has active radio frequency components for transmission.

[0111] In addition, the RAN1#116 meeting further defined the following three categories of AIoT devices: Device 1, Device 2a, and Device 2b.

[0112] Device 1 has a peak power consumption of approximately 1 μW and features energy storage. Its initial sampling frequency offset (SFO) reaches 10 x ppm, and it cannot amplify downlink (DL) or uplink (UL) signals. It requires an external carrier signal for backscatter communication to enable uplink transmission.

[0113] Device 2a has a peak power consumption of less than or equal to several hundred μW, has energy storage capabilities, and an SFO of 10. X ppm can amplify DL and / or UL signals. An external carrier signal is required for backscatter communication in order to perform uplink transmission.

[0114] Device 2b has a peak power consumption of less than or equal to several hundred μW, has energy storage capabilities, and an SFO of 10. X ppm, capable of DL and / or UL signal amplification. The device can perform uplink transmission without relying on an externally provided carrier.

[0115] The following describes the access stratum (AS) process between the AIoT device and the reader / writer. Please refer to Figure 4.

[0116] Step A: AIoT Paging. Based on the service request, the reader sends an A-IoT paging message, indicating the AIoT device that needs to respond.

[0117] The term "AIoT paging message" can be replaced with "(initial) trigger message" or any other name. For simplicity, no restrictions are imposed.

[0118] Step B: D2R Data Transmission. The triggered AIoT device performs AIoT device ID transmission via or without the AIoT random access procedure (e.g., contention-free resolution). For example, the AIoT device sends its ID to the reader.

[0119] Step C1: Possible R2D data transmission (e.g., for sending commands, such as read, write, lock, deactivate, sensor, etc.).

[0120] Step C2: Possible D2R data transfer (e.g., responses to commands, such as data read by a read command, success / failure feedback for a write command, etc.).

[0121] The process shown in Figure 4 above can support inventory and command application scenarios in the following ways:

[0122] For the "inventory-only" scenario, the baseline solution may include steps A and B as described above.

[0123] For the "inventory and command" scenario, the baseline scheme may include steps A, B, C1 and C2 as described above.

[0124] For the "command-only" scenario, a solution that includes steps A, B, C1, and C2 as a baseline can also be supported. Furthermore, another candidate solution supporting this scenario is as follows:

[0125] Step A': AIoT Paging. The reader sends an AIoT paging message containing commands based on the service request, instructing the AIoT device to process / respond to the commands.

[0126] Step C2: Perform possible D2R data transmission (e.g., transmit the ID of the AIoT device or a corresponding response to a command) with or without the AIoT random access procedure.

[0127] The AIoT random access procedure is described below. The A-IoT random access procedure can be used for AIoT devices to access the network for data transmission.

[0128] The AIoT random access process can be triggered by a reader / writer, which can send an AIoT paging message (refer to S401 in Figure 4) to page the corresponding AIoT device. Upon receiving the AIoT paging message, the AIoT device can execute the process shown in Figure 5.

[0129] S501, the AIoT device determines the random access type and random access resources.

[0130] The AIoT device can be the AIoT device being paged. For example, the AIoT paging message may include the identifier of the AIoT device, or the AIoT paging message may include the identifier of the group to which the AIoT device belongs, or the AIoT paging message may not include the identifier of any AIoT device, and the AIoT device receives the AIoT paging message.

[0131] Random access resources may include, for example, random access occasions. For instance, an AIoT paging message may include random access resources scheduled for the AIoT device to be paged, so that the paged AIoT device can determine the random access resources based on the AIoT paging message.

[0132] The random access type is, for example, contention-free access or contention-based random access. If it is contention-free access, S502 and S503 can be omitted, and S504 can be executed instead; if it is contention-based access, S502 can be executed.

[0133] S502, the AIoT device sends message 1 (Msg1) to the reader. Correspondingly, the reader receives Msg1.

[0134] When the AIoT device determines that the random access timing of the AIoT device has started, the AIoT device can send Msg1 to the reader.

[0135] There are two options for the content included in Msg1. In option 1, Msg1 can include a random number (RN), for example, called random number A. This random number A can be generated by the AIoT device. There are no restrictions on how the AIoT device generates the random number A; for example, it can be generated randomly, or it can be generated based on the ID of the AIoT device. There are also no restrictions on the size of the random number A; for example, it can be 16 bits, or it can be any other size.

[0136] In scheme 2, Msg1 may include upper-layer data. This upper-layer data may include the identifier of the AIoT device and / or other upper-layer data. Optionally, in scheme 2, Msg1 may include a random number, for example, referred to as random number C; or it may not include a random number.

[0137] S503, the reader sends message 2 (Msg2) to the AIoT device. Correspondingly, the AIoT device receives Msg2.

[0138] If Msg1 uses scheme 1, that is, Msg1 includes a random number (e.g., random number A), then Msg2 includes that random number, for example, referred to as random number B. If the AIoT device receives Msg2 containing random number B, and random number B is the same as random number A, then the AIoT device considers the contention resolution successful or the access successful.

[0139] If Msg1 uses scheme 2, Msg2 may include one or more of the following: a random number C, part or all of the identifier of the AIoT device, or an acknowledgment (ACK). If the AIoT device receives Msg2, the race condition is considered resolved successfully.

[0140] Alternatively, if Msg1 uses Scheme 2, S503 can be omitted; that is, the reader does not send Msg2, which can also be understood as the reader not sending a response to Msg1. If the AIoT device does not receive a signal indicating failure, reconnection, or retransmission, it is considered that the contention resolution was successful or the access / data transmission / service was successful.

[0141] S504, Data transmission.

[0142] This data transmission may include D2R data transmission and / or R2D data transmission. For example, if the AIoT device considers the contention resolved successfully, or if the AIoT device is using contention-free access, the AIoT device may send data to the reader. This data may include, for example, upper-layer data, which may include the AIoT device's identifier and / or other upper-layer data. Optionally, the reader may also send data to the AIoT device, such as sending commands, without limitation.

[0143] The above process involves the AIoT device sending its ID to the reader. Currently, AIoT devices send their device IDs. However, exposing the AIoT device's device ID in the AIoT interface reduces communication security.

[0144] Therefore, the environmental IoT device in this application embodiment can receive a random number from the network, thereby generating a first identifier, which is used to temporarily identify the first environmental IoT device. Thus, when the first environmental IoT device needs to send its identifier to the network, it can send the first identifier instead of the second identifier, reducing the probability of exposing the second identifier to the AIoT interface and improving communication security. Optionally, the first environmental IoT device may be, for example, an active environmental IoT device, or device C or device 2b. It can be understood that this application embodiment provides a method for such environmental IoT devices to obtain a temporary identifier.

[0145] 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.

[0146] Figures 6 to 10 are schematic diagrams of several communication systems applicable to embodiments of this application, which are also several network topologies of AIoT technology.

[0147] Figure 6 shows topology 1. In topology 1, AIoT devices communicate directly and bidirectionally with network devices. Communication between network devices and AIoT devices includes the transmission of AIoT data and / or signaling. The network device can act as a reader / writer.

[0148] Figure 7 shows Topology 2. In Topology 2, an intermediate node exists between the AIoT device and the network device. The AIoT device and the network device can communicate bidirectionally through this intermediate node, which can transmit AIoT data and / or signaling between the network device and the AIoT device. In Topology 2, the intermediate node can be a repeater, an integrated access and backhaul (IAB) node, a UE, or other devices, enabling AIoT technology implementation. This intermediate node can also function as a reader / writer.

[0149] Figures 8 and 9 both illustrate Topology 3. In Topology 3, the AIoT device sends AIoT data and / or signaling to the network device and can receive AIoT data and / or signaling from the auxiliary node, as shown in Figure 8; alternatively, the AIoT device can receive AIoT data and / or signaling from the network device and can send AIoT data and / or signaling to the auxiliary node, as shown in Figure 9. In Topology 3, the auxiliary node can be a repeater, IAB node, UE, or other devices capable of implementing AIoT technology. The network device can function as a reader / writer.

[0150] Figure 10 shows topology 4. In topology 4, the AIoT device and the UE communicate bidirectionally. The communication between the UE and the AIoT device includes AIoT data and / or signaling. The UE can act as a reader / writer.

[0151] In Figures 6 through 9, the network device shown is, for example, an access network device, such as a base station.

[0152] Please refer to Figure 11, which is a schematic diagram of the logical system architecture of Topology 1. As shown in Figure 11, the xx interface is the next generation (NG) interface, and XXAP is the control plane protocol of the XX interface (NG interface). One possible implementation of "XXAP" is to include AIoTF information / cells in NGAP, and another possible implementation is to carry a newly defined protocol layer on top of the NGAP protocol.

[0153] The AIoT-related processes are defined on the XXAP layer as shown in Figure 12. Figure 12 includes the protocol stack between the AIoT device, the AIoT radio access network (RAN), and the AIoT core network (CN). In Figure 12, the xx interface can be an NG interface. For example, in various embodiments of this application, the interface between the access network device and the core network device can be an NG interface, as exemplified in Figures 11 and 12. The AIoT device communicates with the AIoT RAN's AIoT radio protocol layer through the AIoT radio protocol layers. The XXAP layer of the AIoT RAN communicates with the XXAP layer of the AIoT CN, the Stream Control Transmission Protocol (SCTP) layer of the AIoT RAN communicates with the SCTP layer of the AIoT CN, the Internet Protocol (IP) layer of the AIoT RAN communicates with the IP layer of the AIoT CN, the layer 2 (L2) of the AIoT RAN communicates with the L2 of the AIoT CN, and the L1 of the AIoT RAN communicates with the L1 of the AIoT CN.

[0154] In Topology 1, there are two scenarios between AIoT RAN and AIoTF: direct connection and indirect path via AMF. Figure 13 shows the direct connection scenario, and Figure 14 shows the indirect connection scenario.

[0155] Optionally, for Topology 1, whether in a direct or indirect connection scenario, "AIoT RAN" (e.g., the AIoT RAN shown in Figure 13 or Figure 14) or "AIoT RAN node" can be replaced with "access network device", such as "gNB".

[0156] Please refer to Figure 15, which is a schematic diagram of the logical system architecture of Topology 2. In Topology 2, the xx interface between the AIoT-enabled gNB (the AIoT-enabled base station in Figure 15) and the A-IoT CN is the NG interface. The AIoT-enabled UE (the AIoT-enabled UE in Figure 15) and the AIoT device (the AIoT device in Figure 15) communicate through the AIoT interface (e.g., AIoT radio).

[0157] AIoT-enabled gNB includes the AIoT RAN node function, and AIoT-enabled UE includes the common reader function. The common reader function refers to the ability to communicate with A-IoT devices through an AIoT interface (e.g., A-IoT radio); the AIoT RAN node function includes the ability to control AIoT radio resources.

[0158] Topology 2 supports three approaches: a radio resource control (RRC) based solution, a non-access stratum (NAS) based solution, and a user plane (UP) based solution.

[0159] solution1:RRC based solution.

[0160] The basic idea is that after the access network device (e.g., a base station) receives an AIoT service-related request from the AIoT CN via XXAP, the base station further sends the relevant information to the A-IoT-enabled UE via RRC messages. When the base station receives AIoT service-related data or signaling from the A-IoT-enabled UE via RRC, the base station transmits the relevant information to the AIoT CN via XXAP / NGAP.

[0161] For an RRC-based solution, a possible protocol stack can be found in Figure 16. Figure 16 shows the protocol stack between the AIoT device, the AIoT RAN, and the AIoT CN. The AIoT device communicates with the AIoT RAN's AIoT radio protocol layer through AIoT radio protocol layers. The RRC layer of the AIoT-enabled UE communicates with the RRC layer of the AIoT-enabled gNB, the PDCP layer of the AIoT-enabled UE communicates with the PDCP layer of the AIoT-enabled gNB, the radio link control (RLC) layer of the AIoT-enabled UE communicates with the RLC layer of the AIoT-enabled gNB, the media access control (MAC) layer of the AIoT-enabled UE communicates with the MAC layer of the AIoT-enabled gNB, and the physical (PHY) layer of the AIoT-enabled UE communicates with the physical layer of the AIoT-enabled gNB. The XXAP layer of the AIoT-enabled gNB communicates with the XXAP layer of the AIoT CN, the SCTP layer of the AIoT-enabled gNB communicates with the SCTP layer of the AIoT CN, the IP layer of the AIoT-enabled gNB communicates with the IP layer of the AIoT CN, the layer 2 (L2) of the AIoT-enabled gNB communicates with the L2 of the AIoT CN, and the L1 of the AIoT-enabled gNB communicates with the L1 of the AIoT CN.

[0162] Among them, the xx interface is the NG-C interface (i.e., the NG control plane interface). One possible implementation of "XXAP" is to include AIoTF information / cells in the NGAP, and another possible implementation is to carry a newly defined protocol layer on the NGAP protocol.

[0163] For RRC-based solutions, there are two scenarios between AIoT-enabled gNBs and AIoTFs: direct connection and indirect connection (indirect path via AMF).

[0164] (1) A direct connection diagram between AIoT-enabled gNB and AIoTF is shown in Figure 17 (in Figure 17, AIoTF can be replaced with A-IoT CN, and Nx / XX is the NG interface).

[0165] (2) The indirect path via AMF between AIoT-enabled gNB and AIoTF is shown in Figure 18. That is, the AIoT data / signaling transmitted between AIoTF and AIoT-enabled gNB is carried on NGAP. Optionally, "N2" in Figure 18 can also be replaced with "NG".

[0166] solution 2: NAS based solution.

[0167] The basic idea is that the access network equipment (such as the base station) cannot see the AIoT-related processes. The AIoT CN and the AIoT-enabled UE transmit AIoT-related data / signaling through the DL / UL NAS packets of the AIoT-enabled UE (transparent transmission of AIoT-enabled gNB). The base station can use the DL NAS transport process and the UL NAS transport process on the NGAP to process the DL / UL NAS packets of the AIoT-enabled UE.

[0168] Figure 19 shows a possible protocol stack for a NAS-based solution.

[0169] solution 3: UP based solution.

[0170] The basic idea is that access network devices (such as base stations) can not see the AIoT-related processes. AIoT service-related data / signaling between the AIoT CN and the -IoT-enabled UE are transmitted on the PDU Session of the AIoT-enabled UE (transparent transmission to the AIoT-enabled gNB). The gNB processes the user plane data of the AIoT-enabled UE through the NG-U GTP-U channel.

[0171] Figure 20 illustrates a possible protocol stack for an UP-based solution.

[0172] Optionally, for topology 3, “AIoT-enabled UE” (e.g., the AIoT-enabled UE shown in Figure 15) can also be replaced with “UE reader”, “intermediate UE”, or “intermediate node”, etc.

[0173] 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.

[0174] The following describes some signaling or information involved in the embodiments of this application.

[0175] The Select message can also be replaced with a Paging message, an (initial) trigger message, an (initial) DL trigger message, or an Indication message, etc. There are no restrictions on the name.

[0176] The Query message can also be replaced with an access round trigger or indication message, etc., and there are no restrictions on the name.

[0177] The QueryRep message can also be replaced with the (next)access occasion trigger message or the / Indication message, etc., and there are no restrictions on the name.

[0178] The random number (RN) can also be replaced with a random access ID or random ID, etc. There are no restrictions on the name.

[0179] Msg2 or ACK can also be replaced with access ID response, access response, or UE / device contention resolution identity, etc. There are no restrictions on the name.

[0180] EPC can also be replaced with uplink data (UL data) or device ID, etc., and there are no restrictions on the name.

[0181] One or more of the above signaling can be carried in the media access control (MAC) layer, for example, in a MAC control element (CE), a MAC service data unit (SDU), or a MAC protocol data unit (PDU). Optionally, "MAC layer" can also be replaced with "AIoT access stratum (AS)".

[0182] A query can trigger or indicate at least one access opportunity. For example, it can directly or indirectly indicate the total number of access opportunities, and / or trigger the first access opportunity.

[0183] QueyRep can trigger or indicate the next access opportunity. It can also be understood as QueyRep indicating or associating the boundary (start or end) of an access opportunity.

[0184] Optionally, the aforementioned "access opportunity" can also be referred to as access timing or access slot, etc. Each access opportunity may allow the AIoT device to send one or more of the following messages: access (request), contention resolution, or data.

[0185] Paging can instruct AIoT devices to access the reader / writer. For example, when the reader / writer is an access network device, paging can instruct the AIoT device to access the network; or, for example, when the reader / writer is a UE, paging can instruct the AIoT device to access the UE. Optionally, if the reader / writer is an access network device, the AIoT device can access the network through the corresponding UE.

[0186] Paging can also trigger or instruct AIoT devices to send data, or trigger, instruct, or request AIoT devices to perform corresponding services. These services can include at least one of the following: paging services, inventory services, command services (such as read, write, deactivate, lock, etc.), location services, or sensing services. Paging can be triggered by a reader / writer.

[0187] RN can be used for contention resolution or to distinguish different AIoT devices during random access or contention resolution.

[0188] ACK can indicate whether contention resolution was successful. Optionally, ACK can carry a contention resolution identifier to be associated with the corresponding AIoT device.

[0189] 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 lock operation (or lock service).

[0190] In various embodiments of this application, the environmental IoT device is, for example, an AIoT device, or may have other names. For example, "AIoT" can be replaced with other names without limitation; this document uses "AIoT device" as an example. Taking a first AIoT device as an example, the first AIoT device can store energy, and therefore can independently generate and transmit signals. For example, the first AIoT device does not need to rely on reflecting signals from other devices to obtain energy, but can store energy itself, thus enabling the first AIoT device to actively transmit signals. For example, the first AIoT device can be an active AIoT device, or device C, or device 2b.

[0191] In various embodiments of this application, the reader may be referred to as a reader-writer or a reader; in this paper, a reader-writer is used as an example.

[0192] In various embodiments of this application, the first identifier can be used to temporarily identify the first AIoT device; or, the first identifier can be used to identify the first AIoT device for a period of time, and the first identifier may no longer be used to identify the first AIoT device at the end of the period. For example, the first identifier is a temporary identifier (temporary ID) of the first AIoT device.

[0193] In various embodiments of this application, the second identifier can be used to identify the first AIoT device. For example, the second identifier can be used to permanently identify the first AIoT device, without time limitations. For example, the second identifier is the device ID of the first AIoT device.

[0194] The various embodiments of this application can be applied to the network architecture shown in any of the figures 6 to 10. For example, the first AIoT device described in the various embodiments of this application can be any of the AIoT devices shown in figures 6 to 10; the reader / writer described in the various embodiments of this application is, for example, the network device shown in Figure 6, Figure 8, or Figure 9, or the intermediate node shown in Figure 7, or the UE shown in Figure 10; the first core network device described in the various embodiments of this application is, for example, a core network device capable of communicating with the network devices shown in Figures 6, 8, and 9 (not shown in Figures 6, 8, and 9), or the network device shown in Figure 7, or a core network device capable of communicating with the network device shown in Figure 10 (not shown in Figure 10); the second core network device described in the various embodiments of this application is, for example, a core network device not shown in Figures 6 to 10. Optionally, the first core network device is, for example, an AMF or an ambient IoT function (AIoTF). Optionally, the second core network device is, for example, an AMF. For example, the reader can communicate with the first core network device (e.g., AIoTF) via the second core network device, or the reader can communicate directly with the first core network device (e.g., AIoTF) without going through the second core network device.

[0195] The various embodiments of this application can be applied to various topologies as described above. If the various embodiments of this application are applied to Topology 1 as described above, optionally, the "first reader / writer" described in the various embodiments of this application can be replaced with an "access network device" or a "gNB". Alternatively, it can be understood that in Topology 1, the "first reader / writer" described in the various embodiments of this application is implemented through an access network device or a gNB. In this case, the communication process between the first reader / writer and the access network device described below may not be performed.

[0196] This application provides a communication method, please refer to Figure 21, which is a flowchart of the method.

[0197] S2101, The first AIoT device sends the first message. Correspondingly, the first core network device receives the first message.

[0198] The first message may be uplink data, an initial registration request message, or other messages. The first message may include a second identifier.

[0199] In this system, the first AIoT device can send a first message to the first reader / writer, which then sends the first message to the first core network device, as illustrated in Figure 21. The first reader / writer can be a reader / writer that serves the first AIoT device, or it can be a reader / writer that has established a communication connection with the first AIoT device.

[0200] The first reader / writer can be an access network device or a UE. If the first reader / writer is an access network device, it can send a first message to the first core network device. Alternatively, if the first reader / writer is a UE, it can send a first message to the access network device, which then sends a first message to the first core network device.

[0201] The first core network device is, for example, an AIoTF or an AMF. If the first core network device is an AIoTF, the first reader (or access network device) can communicate directly with the AIoTF, for example, by directly sending a first message to the AIoTF; or, the first reader (or access network device) can also communicate with the AIoTF through a second core network device, for example, the first reader can send a first message to the second core network device, which then sends a first message to the AIoTF. The second core network device is, for example, an AMF. Alternatively, if the first core network device is an AMF, the first reader (or access network device) can send a first message to the AMF, which then sends a first message to the AIoTF. In short, the first reader (or access network device) can communicate directly with the AIoTF, or it can communicate with the AIoTF through an AMF.

[0202] For the first core network device, although it receives the first message from the first reader, the second core network device, or the access network device, the first message actually originates from the first AIoT device.

[0203] Optionally, the first AIoT device has not received a paging message from the first reader / writer before sending the first message. Alternatively, this can be understood as the first AIoT device not sending the first message only upon being triggered by the first reader / writer, but rather actively sending the first message.

[0204] S2102, The first core network device sends a random number. Correspondingly, the first AIoT device receives the random number. Optionally, the random number can be used to generate a first identifier. For example, the random number and a second identifier can be used to generate the first identifier.

[0205] For example, the first core network device can send a random number to the first reader in response to the first message. Optionally, the first core network device can include the random number in a response to the first message. The first reader receives the random number and then retransmits it. Optionally, the random number sent by the first reader can be included in an acknowledgment (ACK) message. Thus, the first AIoT device can receive the random number, as illustrated in Figure 21.

[0206] The first reader / writer can be an access network device or a UE. If the first reader / writer is an access network device, the first core network device can send a random number to the first reader / writer, which then sends the random number. Alternatively, if the first reader / writer is a UE, the first core network device can send a random number to the access network device serving the first reader / writer, which then sends the random number to the first reader / writer, which then sends the random number.

[0207] The first core network device is, for example, an AIoTF or an AMF. If the first core network device is an AIoTF, the AIoTF can communicate directly with the first reader (or access network device), for example, the AIoTF can directly send a random number to the first reader or access network device; or, the AIoTF can also communicate with the first reader or access network device through a second core network device, for example, the AIoTF can send a random number to the second core network device, the second core network device sends the random number to the first reader or access network device, and the first reader or access network device then sends the random number. The second core network device is, for example, an AMF. Alternatively, if the first core network device is an AMF, the AIoTF first sends the random number to the AMF (for example, in S2101, the AMF sends the first message to the AIoTF, and the AIoTF can send the random number in response to the first message), the AMF can send the random number to the first reader or access network device, and the first reader or access network device then sends the random number.

[0208] In the following text, whenever information interaction is involved between the first AIoT device and the first core network device, the interaction process is similar. Please refer to the introduction of S2101 or S2102.

[0209] For example, the first core network device sends a random number (RN) or a fresh number in response to the first message; this embodiment uses a random number as an example. Optionally, before receiving the first message, the first core network device (e.g., AIoTF) or the AIoTF (e.g., the first core network device is an AMF) has not sent a service request to the first reader, or the first core network device has not sent a service request related to the first AIoT device, or the first core network device has not requested the first AIoT device to perform a service, or the first core network device and the first AIoT device have not performed a service, etc. Alternatively, it can be understood that the first message is not sent under the trigger of the first core network device, but rather actively sent by the first AIoT device.

[0210] S2103. The first AIoT device generates a first identifier based on the random number and the second identifier.

[0211] Optionally, the first AIoT device can generate a first identifier based on the random number, the second identifier, and the key. The key can be predefined by the protocol, configured by the network device (e.g., the first core network device), or determined through negotiation between the first AIoT device and the network device (e.g., the first core network device).

[0212] If the first identifier is generated entirely by the first AIoT device itself, without referencing information from the network (such as the random number), different AIoT devices may generate the same identifier, leading to collisions. However, in this embodiment, a first core network device assigns random numbers to each AIoT device. For example, the first core network device can assign different random numbers to different AIoT devices. Each AIoT device can generate its first identifier based on the received random number, thereby reducing the probability of different AIoT devices generating the same identifier, minimizing collisions, and ensuring that the identifier generated by the AIoT device can be used to uniquely identify the AIoT device.

[0213] Optionally, the method may further include S2104, whereby the first AIoT device sends a first identifier, and correspondingly, the first core network device receives the first identifier. In this way, the first core network device effectively obtains both the first and second identifiers of the first AIoT device. Subsequently, if the first AIoT device needs to send its own identifier to the first core network device, it can send the first identifier without sending the second identifier, thereby reducing the probability of exposing the second identifier to the AIoT interface and improving communication security. Optionally, the number of bits occupied by the first identifier can be less than the number of bits occupied by the second identifier; therefore, the first AIoT device sending the first identifier without sending the second identifier can also reduce signaling overhead.

[0214] This application provides a second communication method, as shown in Figure 22, which is a flowchart of the method. In this application embodiment, the first core network device is, for example, an AMF.

[0215] S2201, The first AIoT device sends the second identifier. Correspondingly, the AMF receives the second identifier.

[0216] Optionally, the second identifier may be included in the second message. For a description of the second message, please refer to the second message in S2101 of the embodiment shown in FIG21. For more details about S2201, such as how message passing is performed between the first AIoT device and the AMF, please refer to S2101 of the embodiment shown in FIG21.

[0217] Optionally, the method may also include S2202 and S2203.

[0218] S2202, AMF sends the second identifier to AIoTF. Correspondingly, AIoTF receives the second identifier.

[0219] Taking the second identifier included in the second message as an example, if the AMF receives the second message, it can also send a second message to the AIoTF.

[0220] S2203, AIoTF sends a third identifier to AMF. Correspondingly, AMF receives the third identifier.

[0221] Optionally, the third identifier may be, for example, the identifier of the AIoTF, or the identifier of the set to which the AIoTF belongs (e.g., AIoTF set ID), or the identifier of the region to which the AIoTF belongs (e.g., AIoTF region ID).

[0222] S2204, AMF determines the first identifier based on the second identifier and the third identifier.

[0223] For example, the first identifier determined by the AMF based on the second identifier may include the third identifier.

[0224] Optionally, the AMF determines the first identifier based on the second identifier and the third identifier. Alternatively, the AMF may determine the first identifier based on the second identifier, the third identifier, and its own identifier. For example, the first identifier determined by the AMF based on the second identifier may include the third identifier and the AMF's identifier. Wherein, the first identifier includes the third identifier and can be used by the reader, access network device, or AMF to determine the AIoTF; the first identifier includes the AMF's identifier and can be used by the reader or access network device to determine the AMF.

[0225] S2205, AMF sends the first identifier. Correspondingly, the first AIoT device receives the first identifier.

[0226] For example, the AMF sends a first identifier to the first reader; or the AMF sends a first identifier to an access network device, which then sends the first identifier back to the first reader. Once the first reader receives the first identifier, it can send the first identifier back, allowing the first AIoT device to receive it. Optionally, the first identifier sent by the first reader may be carried in an ACK, which could be a response to a second message.

[0227] Optionally, the method may also include S2206.

[0228] S2206, The first AIoT device sends the first identifier. Correspondingly, the AIoTF receives the first identifier.

[0229] The first reader / writer can be an access network device or a UE. If the first reader / writer is an access network device, it can send a first identifier to the AIoTF. Alternatively, if the first reader / writer is a UE, it can send the first identifier to the access network device, which then sends a second message to the AIoTF.

[0230] The first reader (or access network device) can communicate directly with the AIoTF, for example, by directly sending a first identifier to the AIoTF. Optionally, the first reader can determine the AIoTF based on a third identifier included in the first identifier. For example, if the third identifier is the identifier of the AIoTF, the first reader can send the first identifier to that AIoTF. Alternatively, if the third identifier is an AIoTF set ID, the first reader can send the first identifier to each AIoTF in all or part of the set indicated by the AIoTF set ID. Alternatively, if the third identifier is an AIoTF region ID, the first reader can send the first identifier to each AIoTF in all or part of the region indicated by the AIoTF region ID.

[0231] Alternatively, the first reader (or access network device) can also communicate with the AIoTF via the AMF. For example, the first reader can send a first identifier to the AMF, and the AMF can then send the first identifier to the AIoTF. Optionally, the first reader can determine the AMF based on the AMF's identifier included in the first identifier. Optionally, the AMF can determine the AIoTF based on a third identifier included in the first identifier. For example, if the third identifier is the AIoTF's identifier, the AMF can send the first identifier to that AIoTF. Alternatively, if the third identifier is an AIoTF set ID, the AMF can send the first identifier to each AIoTF in all or part of the set indicated by the AIoTF set ID. Alternatively, if the third identifier is an AIoTF region ID, the AMF can send the first identifier to each AIoTF in all or part of the region indicated by the AIoTF region ID.

[0232] In summary, the first reader (or access network device) can communicate directly with the AIoTF, or it can communicate with the AIoTF through the AMF.

[0233] In this embodiment, the network assigns a first identifier to the first AIoT device. For example, the network can assign different identifiers to different AIoT devices, so that one identifier can uniquely identify one AIoT device, reducing collisions. Since a first identifier is assigned to the first AIoT device, the first AIoT device can send the first identifier instead of the second identifier when it needs to send its own identifier, improving communication security and reducing signaling overhead. Furthermore, the first identifier can be determined based on a third identifier, or based on the third identifier and the identifier of the AMF (Advanced Feature Controller), thereby allowing routing based on the first identifier during transmission, improving transmission reliability.

[0234] This application provides a third communication method, as shown in Figure 23, which is a flowchart of the method. In this application embodiment, the first core network device is, for example, an AIoTF.

[0235] S2301, The first AIoT device sends the second identifier. Correspondingly, the AIoTF receives the second identifier.

[0236] Optionally, the second identifier may be included in the second message. For a description of the second message, refer to the first message in S2101 of the embodiment shown in FIG21. For more details about S2201, such as how message passing is performed between the first AIoT device and the AIoTF, refer to S2101 of the embodiment shown in FIG21. FIG23 illustrates communication between the first reader / writer or access network device and the AIoTF via the AMF as an example.

[0237] S2302, AIoTF determines the first identifier based on the second identifier and the third identifier.

[0238] For example, the first identifier determined by the AMF based on the second identifier may include the third identifier.

[0239] Optionally, the AIoTF determines the first identifier based on the second identifier and the third identifier. This may further include the AIoTF determining the first identifier based on the second identifier, the third identifier, and the identifier of the second core network device. For example, if the first reader or access network device communicates with the AIoTF through the second core network device, the AIoTF can determine the first identifier based on the second identifier, the third identifier, and the identifier of the second core network device. The second core network device is, for example, an AMF or other device; in the following embodiments of this application, the AMF will be used as an example. For example, the first identifier determined by the AIoTF based on the second identifier may include the third identifier and the identifier of the AMF. Wherein, the first identifier includes the third identifier, which can be used by the reader, access network device, or AMF to determine the AIoTF; the first identifier includes the identifier of the AMF, which can be used by the reader or access network device to determine the AMF.

[0240] In this process, for the AIoTF to determine the first identifier based on the AMF's identifier, it first needs to obtain the AMF's identifier. For example, if the first reader or access network device communicates with the AIoTF through the AMF, then in S2301, the AIoTF receives the second identifier from the AMF. Optionally, in addition to sending the second identifier to the AIoTF, the AMF also sends its own identifier to the AIoTF, enabling the AIoTF to obtain the AMF's identifier.

[0241] S2303, AIoTF sends the first identifier to AMF. Correspondingly, AMF receives the first identifier.

[0242] Optionally, if the first identifier is determined based on the second and third identifiers, or if the first identifier is not determined based on the identifier of the AMF, then the AMF, upon receiving the first identifier, can also obtain a new first identifier based on the first identifier and the identifier of the AMF. For example, the new first identifier may include the third identifier and the identifier of the AMF. For distinction, the first identifier sent by the AIoTF can be referred to as first identifier A, and the first identifier sent by the AMF can be referred to as first identifier B.

[0243] The first identifier A and the first identifier B can be the same identifier, or the first identifier A and the first identifier B can be different. For example, the first identifier A is determined based on the second identifier and the third identifier, and the first identifier B is determined based on the first identifier A and the identifier of the AMF (or the first identifier B is determined based on the second identifier, the third identifier and the representation of the AMF).

[0244] S2304, AMF sends the first identifier B. Correspondingly, the first AIoT device receives the first identifier B.

[0245] For example, the AMF sends the first identifier B to the first reader; or the AMF sends the first identifier B to the access network device, which then sends the first identifier B back to the first reader. Once the first reader receives the first identifier B, it can send the first identifier B, thus enabling the first AIoT device to receive the first identifier B. Optionally, the first identifier B sent by the first reader may be carried in an ACK, which could be a response to a second message.

[0246] Optionally, the method may also include S2305.

[0247] S2305, The first AIoT device sends the first identifier. Correspondingly, the AIoTF receives the first identifier.

[0248] For more information on S2305, please refer to S2206 of the embodiment shown in FIG22.

[0249] In this embodiment, the network assigns a first identifier to the first AIoT device. For example, the network can assign different identifiers to different AIoT devices, so that one identifier can uniquely identify one AIoT device, reducing collisions. Since a first identifier is assigned to the first AIoT device, the first AIoT device can send the first identifier instead of the second identifier when it needs to send its own identifier, improving communication security and reducing signaling overhead. Furthermore, the first identifier can be determined based on a third identifier, or based on the third identifier and the identifier of the AMF (Advanced Feature Controller), thereby allowing routing based on the first identifier during transmission, improving transmission reliability.

[0250] This application provides a fourth communication method. Please refer to Figure 24, which is a flowchart of the method.

[0251] S2401, the first AIoT device sends a fourth message. Correspondingly, the first core network device receives the fourth message. In this embodiment, the first core network device is, for example, an AIoTF.

[0252] The fourth message may be, for example, uplink data, an initial registration request message, or other messages. The fourth message may include the first identifier or the second identifier.

[0253] For more details on S2401, such as how message passing is performed between the first AIoT device and the AIoTF, please refer to S2101 of the embodiment shown in FIG21.

[0254] S2402, the first core network device sends the fifth message to the third core network device. Correspondingly, the third core network device receives the fifth message.

[0255] The fifth message may include either a first identifier or a second identifier. For example, if the fourth message includes a first identifier, then the fifth message may include the first identifier; or if the fourth message includes a second identifier, then the fifth message may include the second identifier.

[0256] If the fifth message includes the first identifier, then the fifth message can be used to request the second identifier, or to request the association between the first identifier and the second identifier. Alternatively, if the fifth message includes the second identifier, then the fifth message can be used to request the first identifier, or to request the association between the first identifier and the second identifier.

[0257] For example, the fourth message includes a second identifier, but the first core network device may not have stored the corresponding first identifier. During the execution of AIoT services, the first AIoT device can send an identifier to the first core network device, thus the first AIoT device may send the first identifier. If the first core network device does not store the first identifier, or does not store the association relationship, it cannot recognize the first identifier and therefore cannot identify the first AIoT device based on the first identifier. Therefore, the first core network device can send a fifth message to the third core network device to request the first identifier or the association relationship.

[0258] For example, the fourth message may include a first identifier, but the first core network device cannot recognize the first identifier. This could be because the first core network device does not store the corresponding second identifier or the association, or although it stores the second identifier, it is unaware of the association. Therefore, the first core network device can send a fifth message to the third core network device to request the second identifier or the association.

[0259] The third core network device can be, for example, an AIoTF, or other network devices. Taking an example where both the first and second core network devices are AIoTFs, for distinction, the AIoTF acting as the first core network device will be called AIoTF1, and the AIoTF acting as the third core network device will be called AIoTF2. For instance, in one scenario, when AIoTF2 serves the first AIoT device, AIoTF2 stores the association relationship. Later, the first AIoT device moves, and AIoTF2 no longer serves the first AIoT device; instead, AIoTF1 takes over serving the first AIoT device. Since AIoTF1 did not store the association relationship, it can request the association relationship from AIoTF2, or request a first identifier or a second identifier.

[0260] S2403, the second core network device sends the sixth message to the first core network device. Correspondingly, the first core network device receives the sixth message.

[0261] For example, if the fifth message requests a first identifier or requests the association, then the sixth message may include the first identifier or the association, thus the first core network device obtains the first identifier or the association. As another example, if the fifth message requests a second identifier or requests the association, then the sixth message may include the second identifier or the association, thus the first core network device obtains the second identifier or the association. In this case, the sixth message can be the response to the fifth message.

[0262] Optionally, the method may also include S2404 to S2407.

[0263] S2404, The first core network device sends the seventh message. Correspondingly, the first reader / writer receives the seventh message.

[0264] Optionally, the seventh message may include the first identifier, or it may not include the first identifier.

[0265] S2405, the first reader / writer sends the eighth message. Correspondingly, the first AIoT device receives the eighth message.

[0266] Once the reader receives the seventh message, it can send the eighth message. If the seventh message includes the first identifier, the eighth message can also include the first identifier; alternatively, if the seventh message does not include the first identifier, the eighth message may also omit the first identifier. The eighth message can be, for example, a response to the fourth message.

[0267] S2406, The first AIoT device sends a first identifier to the first reader / writer. Correspondingly, the first reader / writer receives the first identifier.

[0268] When the first AIoT device needs to send its own identifier, it can send the first identifier instead of the second identifier, thereby improving communication security and reducing signaling overhead.

[0269] S2407, The first reader / writer sends the first identifier to the first core network device. Correspondingly, the first core network device receives the first identifier. For the first core network device, although the first identifier is sent by the first reader / writer, the first data comes from the first AIoT device.

[0270] In this embodiment, if the first core network device does not store the first identifier, the second identifier, or the association relationship, the first core network device can request the first identifier, the second identifier, or the association relationship from other core network devices. Thus, the first AIoT device can send the first identifier to the first core network device without sending the second identifier, thereby improving communication security and reducing signaling overhead.

[0271] Optionally, the various embodiments of this application can be applied independently, or some or all of the embodiments can be applied in combination. For example, the embodiment shown in FIG24 can be applied in combination with the embodiments shown in any of FIG21, FIG22 or FIG23. For example, one combination is that when an AIoTF serves a first AIoT device, the first AIoT device obtains a first identifier according to the embodiment shown in any of FIG21, FIG22 or FIG23. Later, the first AIoT device moves, and the AIoTF no longer serves the first AIoT device, but switches to another AIoTF serving the first AIoT device. If the other AIoTF does not store the association between the first identifier and the second identifier, or does not store the first identifier or the second identifier, then the other AIoTF can obtain the first identifier, the second identifier or the association according to the embodiment shown in FIG24.

[0272] Figure 25 shows a schematic diagram of the structure of a device provided in an embodiment of this application. The communication device 2500 can be the first AIoT device or its circuit system as described in any of the embodiments shown in Figures 21 to 24, used to implement the method corresponding to the first AIoT device in the above method embodiments. Alternatively, the communication device 2500 can be the first reader / writer or its circuit system as described in any of the embodiments shown in Figures 21 to 24, used to implement the method corresponding to the first reader / writer in the above method embodiments. Alternatively, the communication device 2500 can be the first core network device or its circuit system as described in any of the embodiments shown in Figures 21 to 24, used to implement the method corresponding to the first core network device in the above method embodiments. For example, one type of circuit system is a chip system.

[0273] The communication device 2500 includes at least one processor 2501. The processor 2501 can be used for internal processing within the device to implement certain control processing functions. Optionally, the processor 2501 includes instructions. Optionally, the processor 2501 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 onto one or more integrated circuits.

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

[0275] Optionally, the communication device 2500 includes a communication line 2502 and at least one communication interface 2504. Since the memory 2503, communication line 2502, and communication interface 2504 are all optional, they are all represented by dashed lines in Figure 25.

[0276] Optionally, the communication device 2500 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 2500 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.

[0277] Processor 2501 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.

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

[0279] The communication interface 2504 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.

[0280] The memory 2503 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 2503 may exist independently and be connected to the processor 2501 via communication line 2502. Alternatively, the memory 2503 may be integrated with the processor 2501.

[0281] The memory 2503 stores computer execution instructions for implementing the scheme of this application, and the processor 2501 controls the execution of these instructions. The processor 2501 executes the computer execution instructions stored in the memory 2503 to implement the steps performed by the first AIoT device, the first reader / writer, or the first core network device as shown in any of the figures 21 to 24.

[0282] 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.

[0283] In a specific implementation, as one example, processor 2501 may include one or more CPUs, such as CPU0 and CPU1 in FIG25.

[0284] In a specific implementation, as one embodiment, the communication device 2500 may include multiple processors, such as processors 2501 and 2505 in FIG. 25. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. Here, a processor may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0285] When the device shown in Figure 25 is a chip, such as the chip of a first AIoT device, a chip of a first reader / writer, or a chip of a first core network device, the chip includes a processor 2501 (and may also include a processor 2505), a communication line 2502, and a communication interface 2504. Optionally, it may include a memory 2503. Specifically, the communication interface 2504 may be an input interface, pins, or circuits, etc. The memory 2503 may be a register, cache, etc. The processor 2501 and processor 2505 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.

[0286] This application embodiment can divide the device into functional modules according to the above method examples. 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 software functional modules. The module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may exist in actual implementation. For example, in the case of dividing each functional module according to its own function, Figure 26 is a schematic diagram of a device. This device 2600 can be the first AIoT device, the first reader / writer, or the first core network device involved in the above method embodiments, or it can be a chip in the first AIoT device, the first reader / writer, or the first core network device. The device 2600 includes a processing unit 2602 and a transceiver unit 2601.

[0287] It should be understood that the device 2600 can be used to implement the steps performed by the first AIoT device, the first reader, or the first core network device in the communication method of the embodiments of this application. The relevant features can be referred to the embodiments shown in any of the figures 21 to 24 above, and will not be repeated here.

[0288] Optionally, the functions / implementation processes of the transceiver unit 2601 and processing unit 2602 in Figure 26 can be implemented by the processor 2501 in Figure 25 calling computer execution instructions stored in memory 2503. Alternatively, the functions / implementation processes of the processing unit 2602 in Figure 26 can be implemented by the processor 2501 in Figure 25 calling computer execution instructions stored in memory 2503, and the functions / implementation processes of the transceiver unit 2601 in Figure 26 can be implemented by the communication interface 2504 in Figure 25.

[0289] Optionally, when the device 2600 is a chip or circuit, the function / implementation process of the transceiver unit 2601 can also be implemented through pins or circuits, etc. Optionally, the transceiver unit 2601 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 2601 may be an integral module capable of implementing both transmitting and / or receiving functions. Optionally, the transceiver unit 2601 can be implemented using a transceiver.

[0290] 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 reader / writer and / or the first AIoT device and / or the first core network device 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.

[0291] This application also provides a computer program product comprising: computer program code, which, when run on a computer, causes the computer to perform the method executed by the first reader and / or the first AIoT device and / or the first core network device in any of the foregoing method embodiments.

[0292] 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 reader and / or the first AIoT device and / or the first core network device involved in any of the above method embodiments.

[0293] 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)).

[0294] 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.

[0295] 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.

[0296] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

[0297] 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.

[0298] It is understood that in the embodiments of this application, the first reader and / or the first AIoT device and / or the first core network device may 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 may also be performed. Furthermore, the various steps may be performed in different orders as presented in the embodiments of this application, and it is not necessarily necessary to perform all the operations in the embodiments of this application.

Claims

1. A communication method, characterized in that, The method includes: Send a first message, the first message including a second identifier, the second identifier being used to identify the first environmental IoT device, the first environmental IoT device being an active environmental IoT device; Receive random numbers; A first identifier is generated based on the random number and the second identifier, and the first identifier is used to temporarily identify the first environmental IoT device; Prior to sending the first message, the first environmental IoT device did not receive a paging message from the first reader / writer, which is a reader / writer that has established a communication connection with the first environmental IoT device.

2. The method according to claim 1, characterized in that, The first IoT device is an active environmental IoT device.

3. The method according to claim 1 or 2, characterized in that, The first reader / writer is an access network device or a terminal device.

4. A communication method, characterized in that, The method includes: (1) A chip applied to a first core network device or a chip in a first core network device. Receive a first message, the first message comes from a first environmental IoT device, the first message includes a second identifier of the first environmental IoT device, the second identifier is used to identify the first environmental IoT device; In response to receiving the first message, a random number is sent to the first environmental IoT device; Prior to receiving the first message, the first core network device did not send a service request to the first reader / writer, which is a reader / writer that has established a communication connection with the first environmental IoT device.

5. The method according to claim 4, characterized in that, The first IoT device is an active environmental IoT device, and the first core network device is an Environmental IoT Function (AIoTF) or an Access and Mobility Management Function (AMF).

6. The method according to claim 4 or 5, characterized in that, The first reader / writer is an access network device or a terminal device.

7. A communication method, characterized in that, The method includes: Send a second message, the second message including a second identifier, the second identifier being used to identify the first environmental IoT device; Receive a first identifier, which is used to temporarily identify the first environmental IoT device. The first identifier is determined based on a second identifier and a third identifier. The third identifier is the identifier of the AIoTF, or the identifier of the set to which the AIoTF belongs, or the identifier of the region where the AIoTF is located. The AIoTF is the AIoTF that serves the first environmental IoT device.

8. The method according to claim 7, characterized in that, The first identifier is determined based on the second identifier and the third identifier, including: The first identifier is determined based on the second identifier, the third identifier, and the identifier of the AMF, wherein the AMF is the AMF that serves the IoT device in the first environment.

9. The method according to claim 7 or 8, characterized in that, The second message is the initial registration request message.

10. A communication method, characterized in that, The method includes: Receive a second identifier, which is used to identify the first environmental IoT device; The first identifier is determined based on the second identifier and the third identifier. The first identifier is used to temporarily identify the first environmental IoT device. The third identifier is the identifier of the first core network device, or the identifier of the set to which the first core network device belongs, or the identifier of the area where the first core network device is located. The first core network device is the core network device that serves the first environmental IoT device. Send the first identifier.

11. The method according to claim 10, characterized in that, Determining the first identifier based on the second identifier and the third identifier includes: The first identifier is determined based on the second identifier, the third identifier, and the identifier of the second core network device.

12. The method according to claim 10 or 11, characterized in that, Receive the second identifier of the IoT device in the first environment, including: Receive a second message, the second message including the second identifier.

13. The method according to claim 12, characterized in that, The second message is the initial registration request message.

14. A communication device, characterized in that, The communication device includes a module for performing the method as described in any one of claims 1 to 3, or includes a module for performing the method as described in any one of claims 4 to 6, or includes a module for performing the method as described in any one of claims 7 to 9, or includes a module for performing the method as described in any one of claims 10 to 13.

15. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program that, when run on a reader or a chip in a reader, causes the method as described in any one of claims 1 to 3 to be executed, or causes the method as described in any one of claims 7 to 9 to be executed.

16. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program that, when run on a first environment IoT device or a chip in the first environment IoT device, causes the method as described in any one of claims 4 to 6 to be executed, or causes the method as described in any one of claims 10 to 13 to be executed.

17. A computer program product, characterized in that, The computer program product includes a computer program that, when run on a reader or a chip in a reader, causes the method as described in any one of claims 1 to 3 to be performed, or causes the method as described in any one of claims 7 to 9 to be performed.

18. A computer program product, characterized in that, The computer program product includes a computer program that, when run on a first environmental IoT device or a chip in the first environmental IoT device, causes the method as described in any one of claims 4 to 6 to be executed, or causes the method as described in any one of claims 10 to 13 to be executed.

Images