Communication method and apparatus

Abstract

A communication method and an apparatus. The method comprises: a first core network element allocates a first identifier to a first service, and sends the first identifier to an access network device; when executing the first service (for example, an inventory service), the access network device can acquire a device identifier of at least one first device; when reporting the device identifier of the at least one first device to the first core network element, the access network device further reports the identifier of the corresponding first service to the first core network element, so that the first core network element can determine the correspondence between the device identifier of the at least one first device and the first service, facilitating management of the device identifier by the first core network element.

Description

Communication method and device

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of the People's Republic of China on April 3, 2024, with application number 202410417218.0 and application name "A Communication Method and Device", the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a communication method and device. Background Art

[0004] With the development of communication technology, the 3rd Generation Partnership Project (3GPP) has defined the ambient internet of things (A-IoT) technology. A-IoT technology is based on the cellular network communication infrastructure and consists of readers (such as access network devices) and tags (for example, devices in the cellular network, which can be understood as extremely low-power, extremely low-complexity IoT devices). The main services include: inventory services, positioning services, sensing services, or command services, etc. Typical application scenarios include logistics, warehousing, industrial manufacturing, identity recognition and environmental monitoring, etc. In A-IoT technology, the core network network element can send a service request for a certain service to the access network device. The access network device can perform the corresponding task according to the service request of the service, and the access network device can report the information of the acquired tag device to the core network network element. On the interface between the access network device and the core network network element, how to identify the service or service request corresponding to the information reported by the access network device is a problem to be solved in the embodiments of this application. Summary of the Invention

[0005] In a first aspect, a communication method is provided, which is applied to an access network device. The execution subject of the method can be the access network device, or a module in the access network device (for example, a chip or circuit, etc.), including: receiving a first identifier and a first group identifier of a first service from a first core network network element; sending the first group identifier, which is used to trigger at least one first device to report a device identifier; receiving a device identifier from the at least one first device; and sending the device identifier and the second identifier of the first service to the first core network network element.

[0006] Through the above design, the first core network network element assigns a first identifier to the first service and sends the first identifier to the access network device. When the access network device executes the first service (for example, an inventory service), it can obtain the device identifier of at least one first device. When the access network device reports the device identifier of at least one first device to the first core network network element, it also reports the identifier of the corresponding first service to the first core network network element, so that the first core network network element can determine the correspondence between the device identifier of at least one first device and the first service, which facilitates the first core network network element to manage the device identifier.

[0007] In a possible implementation manner, the first identifier of the first service is the same as the second identifier of the first service.

[0008] In one possible implementation, the first identifier of the first service includes a third identifier allocated by the first core network element to the first service, and the second identifier of the first service includes the third identifier and a fourth identifier allocated by the access network device to the first service.

[0009] In a possible implementation manner, the method further includes: sending the fourth identifier to the first core network element.

[0010] In a possible implementation, it also includes: sending a fifth identifier to the first core network network element, where the fifth identifier is an identifier assigned by the access network device to the first device, and the fifth identifier is used by the access network device to identify the first device on the interface between the access network device and the first core network element.

[0011] With the above design, a corresponding identifier is assigned to the first device at the interface between the access network device and the first core network element. The command message sent by the first core network element to the access network device includes the identifier of the device that is to execute the command message. Because the access network device can recognize the identifier at the interface between the access network device and the first core network element, the access network device can forward the command message to the corresponding device for execution based on the identifier, thereby accurately forwarding the command message to the corresponding device.

[0012] In a possible implementation, it also includes: receiving a sixth identifier from the first core network network element, the sixth identifier is an identifier assigned by the first core network network element to the first device, and the sixth identifier is used by the first core network network element to identify the first device on the interface between the access network device and the first core network element.

[0013] In a possible implementation, the sixth identifier is carried in the command message.

[0014] In a possible implementation manner, the command message also includes the fifth identifier.

[0015] In a possible implementation, the sixth identifier is carried in a first message, and the first message is used to instruct the first device to stop monitoring command messages.

[0016] In a possible implementation manner, the first message also includes the fifth identifier.

[0017] In a possible implementation, it also includes: receiving a first indication from the first core network element, where the first indication is used to indicate the number of times the first device receives the command message; and sending the first indication to the first device.

[0018] With the above design, since the first device does not know how many times it has received command messages, after the relevant process for a command message ends, the first device will continue to wait for the access network device to send another command message. In the above design, the access network device notifies the first device of the number of command messages it has received. After receiving the relevant number of command messages, the first device no longer monitors for command messages, thereby reducing the time the first device spends monitoring command messages.

[0019] The second aspect is a contralateral method of the first aspect. For beneficial effects, please refer to the description of the first aspect. A communication method is provided, which is applied to a first core network network element. The execution subject of the method can be the first core network network element, or a module (chip or circuit, etc.) applied to the first core network network element, including: sending a first identifier and a first group identifier of a first service to an access network device, wherein the first group identifier is used to trigger at least one first device to report a device identifier; receiving the device identifier of the at least one first device and the second identifier of the first service from the access network device.

[0020] In a possible implementation manner, the first identifier of the first service is the same as the second identifier of the first service.

[0021] In one possible implementation, the first identifier of the first service includes a third identifier allocated by the first core network element to the first service, and the second identifier of the first service includes the third identifier and a fourth identifier allocated by the access network device to the first service.

[0022] In a possible implementation manner, the method further includes: receiving the fourth identifier from the access network device.

[0023] In a possible implementation, it also includes: receiving a fifth identifier from the access network device, where the fifth identifier is an identifier assigned by the access network device to the first device, and the fifth identifier is used by the access network device to identify the first device on the interface between the access network device and the first core network network element.

[0024] In a possible implementation, it also includes: sending a sixth identifier to the access network device, where the sixth identifier is an identifier assigned by the first core network network element to the first device, and the sixth identifier is used by the first core network network element to identify the first device on the interface between the access network device and the first core network network element.

[0025] In a possible implementation, the sixth identifier is carried in the command message.

[0026] In a possible implementation manner, the command message also includes the fifth identifier.

[0027] In a possible implementation, the sixth identifier is carried in a first message, and the first message is used to instruct the first device to stop monitoring command messages.

[0028] In a possible implementation manner, the first message further includes the fifth identifier.

[0029] In a possible implementation, the method further includes: sending a first indication to the access network device, where the first indication is used to indicate the number of times the first device receives the command message.

[0030] According to a third aspect, a communication method is provided, which is applied to a distributed unit DU, and the execution subject of the method is the DU, or a module (chip or circuit, etc.) applied in the DU, including: receiving a first identifier and a first group identifier of a first service from a centralized unit CU; sending the first group identifier, which is used to trigger at least one first device to report a device identifier; receiving a device identifier from the at least one first device; and sending the device identifier and the second identifier of the first service to the CU.

[0031] Through the above design, when the CU receives an inventory service request from the core network, it can send multiple inventory service requests to one or more DUs. Each DU can obtain a device identification list through one inventory. Therefore, when the DU only reports the device identification list to the CU, the CU cannot know which inventory service request the device identification list in the inventory is for, which is inconvenient for the CU to manage the device identification list. In this fourth embodiment, the CU can assign a corresponding identifier to an inventory service request and notify the DU of the identifier. When the DU reports the device identification list to the CU, it reports the identifier corresponding to the device identification list to the CU, so that the CU can know which inventory service request the device identification list reported at this time is for, thereby facilitating the CU's management of the device identification list.

[0032] In a possible implementation manner, the first identifier of the first service is the same as the second identifier of the first service.

[0033] In a possible implementation, the first identifier of the first service includes a third identifier allocated by the CU for the first service, and the second identifier of the first service includes the third identifier and a fourth identifier allocated by the DU for the first service.

[0034] In a possible implementation manner, the method further includes: sending the fourth identifier to the CU.

[0035] In a possible implementation, the method further includes: sending a fifth identifier to the CU, where the fifth identifier is an identifier assigned by the DU to the first device, and the fifth identifier is used by the DU to identify the first device on the interface between the DU and the CU.

[0036] Through the above design, an identifier is assigned to the first device at the interface between the CU and the DU. When the CU needs one or more first devices to execute a corresponding command, the CU can carry the corresponding identifier in the command message sent to the DU. Of course, the identifier is the identifier of the device on the interface between the CU and the DU. The DU can determine the one or more first devices that execute the command message based on the identifier, and send a corresponding command indication to the corresponding first device, thereby identifying the first device on the interface between the CU and the DU.

[0037] In a possible implementation, it also includes: receiving a sixth identifier from the CU, where the sixth identifier is an identifier assigned by the CU to the first device, and the sixth identifier is used by the CU to identify the first device on the interface between the DU and the CU.

[0038] In a possible implementation, the sixth identifier is carried in the command message.

[0039] In a possible implementation manner, the command message also includes the fifth identifier.

[0040] In a possible implementation, the sixth identifier is carried in a first message, and the first message is used to instruct the first device to stop monitoring command messages.

[0041] In a possible implementation manner, the first message also includes the fifth identifier.

[0042] In a possible implementation, the method further includes: receiving a first indication from the CU, where the first indication is used to indicate the number of times the first device receives the command message; and sending the first indication to the first device.

[0043] Through the above design, when the first device receives the first indication, it stops monitoring the command message, thereby reducing the time the first device monitors the command message.

[0044] The fourth aspect is a contralateral method of the third aspect. For the beneficial effects, please refer to the description of the third description. A communication method is provided. The method is applied to a centralized unit CU. The execution subject of the method is the CU, or a module (chip or circuit, etc.) applied to the CU, including: sending a first identifier and a first group identifier of a first service to a distributed unit DU, wherein the first group identifier is used to trigger at least one first device to report a device identifier; receiving the device identifier of the at least one first device and the second identifier of the first service from the DU.

[0045] In a possible implementation manner, the first identifier of the first service is the same as the second identifier of the first service.

[0046] In a possible implementation, the first identifier of the first service includes a third identifier allocated by the CU for the first service, and the second identifier of the first service includes the third identifier and a fourth identifier allocated by the DU for the first service.

[0047] In a possible implementation manner, the method further includes: receiving the fourth identifier from the DU.

[0048] In a possible implementation, it further includes: receiving a fifth identifier from the DU, where the fifth identifier is an identifier assigned by the DU to the first device, and the fifth identifier is used by the DU to identify the first device on the interface between the DU and the CU.

[0049] In a possible implementation, the method further includes: sending a sixth identifier to the DU, where the sixth identifier is an identifier assigned by the CU to the first device, and the sixth identifier is used by the CU to identify the first device on the interface between the DU and the CU.

[0050] In a possible implementation, the sixth identifier is carried in the command message.

[0051] In a possible implementation manner, the command message also includes the fifth identifier.

[0052] In a possible implementation, the sixth identifier is carried in a first message, and the first message is used to instruct the first device to stop monitoring command messages.

[0053] In a possible implementation manner, the first message further includes the fifth identifier.

[0054] In a possible implementation, the method further includes: sending a first indication to the DU, where the first indication is used to indicate the number of times the first device receives the command message.

[0055] In a fifth aspect, a communication device is provided, which can implement the method of the first aspect or the third aspect. For example, the device includes means for executing the corresponding method of the first aspect or the third aspect. The device can be implemented through hardware, software, or hardware executing the corresponding software implementation.

[0056] In one possible design, the device includes a unit that performs the first aspect or the third aspect described above.

[0057] In one possible design, the device includes a processor, which is used to execute the method of the first aspect or the third aspect mentioned above.

[0058] In one possible design, the device includes a processor and an interface circuit, the interface circuit is used to receive signals from other devices outside the device and transmit them to the processor or send signals from the processor to other devices outside the device, and the processor is used to implement the method in the first or third aspect above through logic circuits or executing code instructions.

[0059] In one possible design, the device includes a processor and a memory, and the processor is used to execute a computer program or instruction stored in the memory, so that the device implements the method of the first aspect or the third aspect mentioned above.

[0060] Optionally, the device may be a first device, or a module or unit (for example, a chip, or a chip system, or a circuit) in the first device that corresponds one-to-one to executing the method / operation / step / action described in the first aspect or the third aspect, or may be capable of being used in combination with a second device.

[0061] In a sixth aspect, a communication device is provided, which can implement the method of the second aspect or the fourth aspect. For example, the device includes means for executing the corresponding method of the second aspect or the fourth aspect. The device can be implemented through hardware, software, or hardware executing the corresponding software implementation.

[0062] In one possible design, the device includes a unit that performs the second aspect or the fourth aspect described above.

[0063] In one possible design, the device includes a processor, which is used to execute the method of the second aspect or the fourth aspect above.

[0064] In one possible design, the device includes a processor and an interface circuit, the interface circuit is used to receive signals from other devices outside the device and transmit them to the processor or send signals from the processor to other devices outside the device, and the processor is used to implement the method in the second or fourth aspect above through logic circuits or execution code instructions.

[0065] In one possible design, the device includes a processor and a memory, and the processor is used to execute a computer program or instruction stored in the memory, so that the device implements the method of the second aspect or the fourth aspect above.

[0066] Optionally, the device may be a second device, or a module or unit (for example, a chip, or a chip system, or a circuit) in the second device that corresponds one-to-one to executing the method / operation / step / action described in the second aspect or the fourth aspect, or may be capable of being used in combination with the second device.

[0067] In the seventh aspect, a computer-readable storage medium is provided, which stores a computer program or instruction. When the computer program or instruction is executed on a computer, the computer implements the method of any one of the first to fourth aspects above.

[0068] In an eighth aspect, a computer program product is provided, comprising a computer program or instructions, which enables the method of any one of the above-mentioned first to fourth aspects to be executed when the computer program or instructions are executed by a computer.

[0069] In the ninth aspect, a chip is provided, comprising a processor, wherein the processor is coupled to a memory and is used to execute a computer program or instruction stored in the memory, so that the chip implements the method of any one of the first to fourth aspects above.

[0070] In the tenth aspect, a communication system is provided, comprising: a first communication device and a second communication device; wherein the first communication device is used to implement the method of the first aspect above, and the second communication device is used to implement the method of the second aspect above; or, the first communication device is used to implement the method of the second aspect above, and the second communication device is used to implement the method of the third aspect above. BRIEF DESCRIPTION OF THE DRAWINGS

[0071] FIG1 is a schematic diagram of a communication system provided in an embodiment of the present application;

[0072] Figures 2a, 2b, and 2c are schematic diagrams of the topological structure of communication between an access network device and an AIoT device provided in an embodiment of the present application;

[0073] Figures 3, 4 and 5 are flowcharts of a communication method according to an embodiment of the present application;

[0074] FIG6 is a schematic diagram of a data structure provided in an embodiment of the present application;

[0075] 7 and 8 are flowcharts of a communication method according to an embodiment of the present application;

[0076] FIG9 is a schematic diagram of an access network device according to an embodiment of the present application adopting an O-RAN architecture;

[0077] Figures 10, 11 and 12 are flowcharts of a communication method according to an embodiment of the present application;

[0078] 13 and 14 are schematic diagrams of the structure of the device provided in the embodiments of the present application. DETAILED DESCRIPTION

[0079] In order to make the purpose, technical solutions and advantages of this application more clear, the following will further describe the embodiments of this application in detail with reference to the accompanying drawings. The specific operation methods and functional descriptions in the method embodiments can also be applied to the device embodiments or system embodiments.

[0080] FIG1 shows a possible, non-limiting system schematic diagram. As shown in FIG1 , a communication system 10 includes a terminal 100 , a radio access network (RAN) 200 , and a core network (CN) 300 .

[0081] Among them, the terminal 100 can also be referred to as a terminal device, device, user equipment (UE), mobile station, mobile device, etc. The terminal can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, etc. The device can be a mobile phone, tablet computer, computer with wireless transceiver function, wearable device, vehicle, drone, helicopter, airplane, ship, robot, robotic arm, smart home device, etc. The embodiments of the present application do not limit the device form of the terminal.

[0082] RAN 200 includes at least one RAN node. Terminal 100 can be connected to the RAN node wirelessly. The RAN node is connected to core network 300 wirelessly or via a wired connection. The core network equipment in core network 300 and the RAN nodes in RAN 200 can be separate physical devices, or they can be a single physical device that integrates the logical functions of the core network device and the logical functions of a wireless access device.

[0083] RAN 200 may be a cellular system related to the Third Generation Partnership Project (3GPP), such as a fourth-generation (4G) mobile communication system, a fifth-generation (5G) mobile communication system, or a future-oriented evolutionary system, such as a sixth-generation (6G) mobile communication system. RAN 200 may also be an open access network (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system. RAN 200 may also be a communication system that integrates two or more of the above systems.

[0084] In one possible scenario, the RAN node may be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next generation NodeB (gNB), a next generation base station in a 6G mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system. The RAN node may be a macro base station, a micro base station or an indoor station, a relay node or a donor node, or a wireless controller in a CRAN scenario. Optionally, the RAN node may also be a server, a wearable device, a vehicle or an on-board device, etc. For example, the access network device in the vehicle to everything (V2X) technology may be a road side unit (RSU). All or part of the functions of the RAN node in the embodiment of the present application may also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (e.g., a cloud platform). The RAN node in the embodiment of the present application may also be a logical node, a logical module, or software that can implement all or part of the functions of the RAN node.

[0085] In another possible scenario, multiple RAN nodes collaborate to assist the device in achieving wireless access, and different RAN nodes respectively implement part of the functions of the base station. For example, the RAN node can be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU can be set separately, or they can be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0086] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, CU may also be called O-CU (Open CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU. For the convenience of description, this application uses CU, CU-CP, CU-UP, DU and RU as examples for description. Any unit of CU (or CU-CP, CU-UP), DU and RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0087] RAN nodes, sometimes also referred to as access network equipment, RAN entities, or access nodes, constitute part of a communication system and are used to help terminals achieve wireless access. In the subsequent description of this application, unless otherwise specified, "access network equipment" is used for description. The multiple RAN nodes in RAN 200 can be nodes of the same type or different types. In the access network service-oriented architecture, "access network equipment" can also be replaced by access network function (ANF) network elements.

[0088] The core network 300 includes at least one core network element. For example, it includes at least one of a tag management function (TMF) network element, an access and mobility management function (AMF) network element, or an ambient IoT management function (AIoTMF) network element. Optionally, in this embodiment of the present application, the AMF network element can be replaced with an access management function network element or a registration management function network element.

[0089] It is understandable that the names of the various network elements in the core network 300 are not limited. For example, in the 5G communication system, the network element that implements the signaling processing part is called the AMF network element. In the 6G communication system, the network element that implements the above functions can also be called other names, etc., without limitation. In the subsequent description, the names of the various network elements in 5G are mainly used as examples to describe the solutions of the embodiments of the present application. Optionally, the core network 300 may also include other network elements of control plane functions and entities. For example, a user plane function (UPF) network element, a session management function (SMF) network element, or a policy control function (PCF) network element, etc.

[0090] It can be understood that access network equipment, terminals and network elements in the core network can be called communication devices. For example, access network equipment can be understood as communication devices with base station functions, terminals can be understood as communication devices with terminal functions, and network elements in the core network, such as TMF, can be understood as communication devices with TMF functions.

[0091] With the development of communication technology, 3GPP has defined the ambient internet of things (A-IoT, or AIoT) technology. A-IoT technology includes readers and tags. Readers and tags can be implemented by devices in a cellular network. For example, the functions of the reader can be implemented by an access network device in the cellular network. For example, the access network device can be RAN200 of the communication system 10 shown in Figure 1. Tags can be implemented by terminals in the cellular network, such as extremely low-power, extremely low-complexity IoT devices in the cellular network. For example, the device can be terminal 100 of the communication system 10 shown in Figure 1. The reader and tag communicate contactlessly. For example, the reader can read information from the tag and / or write information to be stored to the tag. A-IoT technology can implement one or more of the following services: inventory, positioning, sensing, or command. Optionally, the command service can include at least one of a read service, a write service, a lock service, or a kill service. In terms of application scope, A-IoT technology can be applied to scenarios such as logistics, warehousing, industrial manufacturing, identity recognition, or environmental monitoring.

[0092] It can be understood that in the embodiments of the present application, the access network device may have the function of a reader / writer; the terminal may have a tag function, or the terminal may be a terminal in an AIoT or IoT system.

[0093] In one classification method, tags can be divided into passive tags, semi-passive tags, and active tags. Passive tags and semi-passive tags can use a backscatter-based communication method, while active tags use an actively generated carrier communication method.

[0094] In another classification, tags can be divided into the following three types:

[0095] Device A is similar to a passive tag in a radio frequency identification (RFID) system: it lacks energy storage capabilities, cannot independently generate uplink signals, and uses backscattering to transmit uplink information. For example, device A lacks the ability to generate uplink signals. For example, an access network device, auxiliary node, or intermediate node can send a carrier signal to device A. Device A can then reflect the signal based on the received carrier signal, thereby enabling uplink transmission for device A. Furthermore, because device A lacks energy storage capabilities, it does not support amplification of reflected signals and / or downlink signals.

[0096] Device B is similar to a semi-passive tag in an RFID system: it has energy storage capabilities, cannot independently generate uplink signals, and uses backscatter to transmit uplink information. Unlike device A, device B's energy storage capability allows it to amplify reflected and / or downlink signals.

[0097] Device C is similar to an active tag in an RFID system: it has energy storage capabilities and can independently generate uplink signals. Device C is capable of generating uplink signals. Device C can use the independently generated uplink signals to transmit uplink information, or it can transmit uplink information using backscatter. Furthermore, because device C has energy storage capabilities, the stored energy can be used to amplify uplink signals, reflected signals, and / or downlink signals. Optionally, device C is equipped with radio frequency components for uplink transmission.

[0098] In the description of the embodiments of this application, a tag may be referred to as an electronic tag, an RFID tag, or a tag device. Alternatively, a tag may also be referred to as an AIoT terminal or an AIoT device. In the description of the embodiments of this application, a tag is described as a device. For example, in the subsequent description, a tag is described as an AIoT device or a first device as an example.

[0099] In the embodiment of the present application, the access network device in the cellular network implements the function of a reader / writer, and the topological structure of the communication between the access network device and the AIoT device includes:

[0100] 1. Topology 1, access network equipment AIoT devices.

[0101] As shown in Figure 2a, the access network device and the AIoT device communicate bidirectionally to exchange signaling and / or data of AIoT services. For example, during downlink transmission: the access network device can send downlink information to the AIoT device, and the downlink information includes signaling and / or data of the AIoT service. During uplink transmission: the AIoT device can send uplink information to the access network device, and the uplink information includes signaling and / or data of the AIoT service. It can be understood that in topology 2a, the type of AIoT device can be a third type of AIoT device.

[0102] 2. Topology 2, access network equipment intermediate node AIoT devices.

[0103] As shown in Figure 2b, there is an intermediate node between the access network device and the AIoT device, and the access network device communicates bidirectionally with the AIoT device through the intermediate node. For example, the access network device is located outdoors, and the access network device can communicate with the AIoT device through a movable intermediate node. Optionally, the intermediate node can be a relay node, an integrated access and backhaul (IAB) node, or a terminal. For example, during downlink transmission: the access network device sends a downlink signal to the intermediate node, and the intermediate node can forward the downlink signal to the AIoT device. Alternatively, the intermediate node can parse the downlink signal sent by the access network device to obtain downlink information, and the intermediate node can send downlink information to the AIoT device. During uplink transmission: the AIoT device can generate an uplink signal, send the uplink signal to the intermediate node, and the intermediate node forwards the uplink signal to the access network device. Alternatively, the intermediate node can parse the uplink signal sent by the AIoT device to obtain uplink information, and the intermediate node can send uplink information to the access network device. Alternatively, the access network device can send an instruction to the intermediate node, which can generate a carrier signal based on the instruction. The intermediate node then sends the carrier signal to the AIoT device. The AIoT device uses the carrier signal to reflect the signal to the intermediate node, and the intermediate node forwards the received reflected signal to the access network device. It can be understood that in topology 2b, the AIoT device can be a first type AIoT device, a second type AIoT device, or a third type AIoT device.

[0104] 3. Topology 3, access network equipment Secondary nodes AIoT devices Access network equipment.

[0105] As shown in Figure 2c, in downlink transmission, the access network device sends a downlink signal to the AIoT device, and the AIoT device receives the downlink signal from the access network device. In uplink transmission, the access network device can send an instruction to the auxiliary node, and the auxiliary node sends a carrier signal to the AIoT device based on the instruction. The AIoT device reflects the received carrier signal to generate a reflected signal. The AIoT device sends the reflected signal to the access network device. It can be understood that in topology 2c, the AIoT device can be a first type AIoT device, a second type AIoT device, or a third type AIoT device.

[0106] It should be noted that the main difference between auxiliary nodes and intermediate nodes is that intermediate nodes can act as readers and writers, or are said to have read and write capabilities. However, auxiliary nodes do not have these capabilities. For example, auxiliary nodes only support sending carrier signals to AIoT devices and do not support receiving reflected signals. Intermediate nodes support both sending carrier signals to AIoT devices and receiving reflected signals.

[0107] In the inventory service scenario, the core network network element can send an inventory (Inventory) service request to the access network device, and the access network device can inventory the AIoT devices within its coverage area based on the inventory service request. For example, the access network device accesses the AIoT device within its coverage area, and the AIoT device that has successfully accessed can report its own device identification to the access network device, and the access network device can forward the device identification of the AIoT device that has successfully accessed to the core network network element. Optionally, the inventory service can also be called an inventory operation, which obtains the device identification information of the AIoT device to realize the inventory of the goods corresponding to the AIoT device. For example, as shown in Figure 3, an embodiment of the present application provides a process diagram of inventory, including:

[0108] Optionally, step 300a: the server sends an inventory service request to the first core network network element, and the first core network network element receives the inventory service request from the server, where the inventory service request is used to instruct an inventory service to be performed on the AIoT device.

[0109] Step 300b: The first core network element sends a service inventory request to the access network device, and the access network device receives the service inventory request from the first core network element.

[0110] Optionally, step 300c: the access network device sends a response message to the first core network network element, and the first core network network element receives the response message from the access network device.

[0111] It can be understood that the response message is a response message to the inventory service request in step 300b.

[0112] Step 310: The access network device sends a paging or selection message to the AIoT device, and the AIoT device receives the paging or selection message from the access network device.

[0113] For example, the paging or selection message includes information such as session, action, and mask. When the AIoT device receives a paging or selection message, it can obtain information such as session, action, and mask in the message. The above-mentioned session information is used to indicate a session, and the action information is used to indicate that the session flag position of the above-mentioned session is a specified value. For example, the indication value can be A or B. Assume that the session indicated by the session information is S0 and the action information is 0. For the AIoT device, if the mask information of the AIoT device is consistent with or matches the mask information in the above-mentioned paging or selection message, the AIoT device sets the flag position of session S0 to A.

[0114] Step 320: The access network device sends a query command to the AIoT device, and the AIoT device receives the query command from the access network device.

[0115] The query command is used to initialize an inventory cycle. For example, the query command carries the Q value, inventory session, and flag. For example, the session carried in the query command is S0 and the flag is A. The AIoT device determines whether the flag of its own session S0 is A; if it is A, it is considered that the two match; the AIoT device can respond to the query command. Furthermore, the AIoT device can generate [0,2 Q -1], the AIoT device uses this random number as the initial value of the counter. For example, if Q = 3, the random number generated by the AIoT device is one of the values ​​in the range [0, 15]. For example, if the random number generated by the AIoT device is 10, the initial value of the counter is 10.

[0116] The AIoT device can determine whether the initial value of the counter is 0; if the initial value of the counter is 0, the AIoT device can send a 16-bit random number (random number 16, RN16) to the access network device. The 16-bit random number is used to trigger the random access process and can be used as a random access request message. Alternatively, if the initial value of the counter is not 0, the AIoT device may not send RN16 to the access network device. Correspondingly, if the access network device does not receive the RN16 sent by the AIoT device within the preset time after sending the query command, the access network device continues to send a repeat query (Query Rep) command to the AIoT device. When the AIoT device receives the repeat query command, it subtracts 1 from the current value of the counter, that is, the AIoT device executes: counter = counter - 1; if after the above process, the value of the counter is still not 0, the AIoT device may not send RN16 to the access network device, and the access network device continues to send repeat query commands to the AIoT device until the value of the counter is 0; when the value of the counter is 0, the AIoT device can send RN16 to the access network device.

[0117] Step 330: The AIoT device sends a first random access request message to the access network device, and the access network device receives the first random access request message from the AIoT device.

[0118] For example, the first random access request message may be the RN16 generated by the AIoT device mentioned above. Alternatively, the AIoT device may also generate a random number of other lengths, such as a random number of length 8. In the description of this application, the example of the terminal generating a 16-bit random number RN16 is mainly described.

[0119] Step 340: The access network device sends an acknowledgement (ACK) to the AIoT device, and the AIoT device receives the ACK from the access network device.

[0120] For example, the AIoT device can use the first time-frequency resource to send RN16 to the access network device. The access network device can determine whether only one RN16 is received on the first time-frequency resource; if one RN16 is received, it can be considered that no collision has occurred, and the access network device sends an ACK to the AIoT device, which includes the above-mentioned RN16. The above-mentioned ACK can also be called a random access response message or a conflict resolution message, etc. Alternatively, the access network device receives multiple RN16s on the first time-frequency resource, and it can be considered that a collision has occurred, and the access network device no longer sends an ACK to the AIoT device. Accordingly, when the AIoT device receives ACK, it can obtain RN16 in the ACK; the AIoT device can determine whether the RN16 is the same as the sent RN16; if they are the same, the access is considered successful; execute step 330; otherwise, the AIoT device can continue to access.

[0121] Step 350: The AIoT device sends uplink data to the access network device, and the access network device receives the uplink data from the AIoT device.

[0122] For example, the uplink data includes business data related to the inventory business. For example, the uplink data includes at least one of the following: the electronic product coding (EPC) of the AIoT device, the device ID, the sensor data collected by the AIoT device, or the storage area data of the AIoT device, etc., which are not limited in this application. In the subsequent description of this application, the example in which the uplink data includes the device ID is mainly used for description. It can be understood that the AIoT device can send multiple uplink data to the access network device. In the description of this application, the example in which the AIoT device sends one uplink data is used for description, and the embodiment of this application does not limit the number of uplink data sent by the AIoT device.

[0123] Step 360: The access network device sends a repeat query command to the AIoT device, and the AIoT device receives the repeat query command from the access network device.

[0124] For example, when the AIoT device sends uplink data to the access network device and receives a repeated query command, it means that the data transmission of the AIoT device is successful. At this time, the AIoT device can flip the flag bit of the corresponding session from A to B. For example, the repeated query command includes a session identifier, such as session S0. When the AIoT device receives the repeated query command, it can flip the flag bit of session S0 in the AIoT device from A to B. The purpose of such an operation is that in one round of inventory, the access network device may send query commands multiple times to perform inventory services. After step 350, if the access network device sends a query command again to perform inventory services, since the flag bit of the corresponding session of the AIoT device is B, the AIoT device will no longer respond to the query command of the access network device, thereby avoiding the same AIoT device being inventoried multiple times in one inventory cycle.

[0125] Step 370: The access network device sends device uplink data to the first core network network element, and the first core network network element receives the uplink data from the access network device.

[0126] For example, the uplink data includes the device ID of one or more AIoT devices. It can be understood that the access network device can inventory one or more AIoT devices through a single inventory. The one or more AIoT devices may all meet the conditions in steps 310 to 340 above. The AIoT device reports its device ID to the access network device through uplink data in step 350. The access network device reports the device ID of the one or more AIoT devices received to the first core network network element. The first core network network element can use the device ID included in the device ID list as the inventory result corresponding to the inventory service request sent in step 300b.

[0127] In the process of Figure 3, it can be seen that the first core network element sends an inventory service request to the access network device. The access network device takes inventory of the AIoT devices based on the inventory service request and reports the device identifiers of the inventoried AIoT devices to the first core network element. Because the first core network element may send multiple inventory service requests to the same or different access network devices, in the scheme of the process of Figure 3, the access network device may receive multiple sets of device identifier lists, each set of device identifier lists corresponding to an inventory service request. The access network device cannot determine the inventory service request corresponding to each set of device identifier lists, which makes it difficult for the first core network element to manage the device identifiers.

[0128] In view of the above, an embodiment of the present application provides a communication method, including: a first core network network element assigns a first identifier to a first service, and sends the first identifier to an access network device. When the access network device executes the first service (for example, an inventory service), it can obtain the device identifier of at least one first device. When the access network device reports the device identifier of at least one first device to the first core network network element, it also reports the identifier of the corresponding first service to the first core network network element, so that the first core network network element can determine the correspondence between the device identifier of at least one first device and the first service, which facilitates the first core network network element to manage the device identifier.

[0129] [Example 1]

[0130] As shown in FIG4 , the embodiment of the present application provides a flow chart, including:

[0131] Step 410: The first core network element sends the first identifier and the first group identifier of the first service to the access network device, and the access network device receives the first identifier and the first group identifier of the first service from the first core network element.

[0132] For example, the first core network network element sends an inventory service request to the access network device, and the access network device receives the inventory service request from the first core network network element, where the inventory service request includes a first group identifier and a first identifier of the first service. Optionally, the first group identifier can be a mask, and for details about the mask, please refer to the description in FIG3 . Optionally, the first core network network element can be a TMF network element, an AMF network element, or an AIoTMF network element, or other network element that supports AIoT, and this embodiment of the present application does not limit this.

[0133] Step 420: The access network device sends a first group identifier, and at least one first device receives the first group identifier.

[0134] For example, the access network device may broadcast a first group identifier. For example, the access network device may broadcast a paging or selection message, the paging or selection message including the first group identifier. The first group identifier is used to trigger at least one first device to report its device identifier, or to trigger at least one first device to access, or to trigger at least one first device to access and report its device identifier. For example, if the first group identifier is a mask, devices within the coverage area of ​​the access network device may receive the paging or selection message broadcast by the access network device. Upon receiving the paging or selection message, a device (e.g., the first device) may obtain the mask from the paging or selection message and compare the obtained mask with its own mask. If the two are identical, the first device executes step 430 and reports the first device's device ID to the access network device. Optionally, the first device's device identifier may be an identifier such as the first device's EPC. It is understood that the process of the access network device paging or selecting the first device may also include setting a flag bit and contention resolution. For details, please refer to the description in FIG. 3 and will not be further described here. It is understandable that within the coverage area of ​​the access network device, one or more devices may have masks that match the mask broadcast by the access network device. Therefore, in this embodiment of the present application, in step 430, one or more first devices report their device identities to the access network device. In step 430, the one or more first devices are described as at least one first device.

[0135] Step 430: At least one first device sends a device identification to the access network device, and the access network device receives the device identification from the at least one first device.

[0136] For example, the first device may send uplink data (UL data) to the access network device, and the access network device receives the uplink data from the first device, where the uplink data includes the device identifier of the first device.

[0137] Step 440: The access network device sends the device identifier of at least one first device and the second identifier of the first service to the first core network network element, and the first core network network element receives the device identifier of at least one first device and the second identifier of the first service from the access network device.

[0138] For example, the first service may be an inventory service. For the inventory service, the first core network element may initiate at least one inventory service request. For each inventory service request, the identifier assigned by the first core network element may be different. For example, the first core network element assigns the identifier 00 to the first inventory service request. The first identifier of the first service carried in the first inventory service request sent by the first core network element to the access network device may be 00. The first core network element assigns the identifier 01 to the second inventory service request. The identifier of the first service carried in the second inventory service request sent by the first core network element to the access network device may be 01. The access network device inventories at least one first device based on the inventory service request. The access network device reports the device identifier of the at least one first device and the second identifier of the first service to the first core network element. There is an association between the second identifier of the first service and the first identifier of the first service. For details on the association, please refer to the following description. The first core network element establishes an association between the device identifier of at least one first device and the second identifier of the first service, so that the first core network element can determine the device identifier of at least one first device and its associated inventory service request, thereby facilitating the first core network element to manage the device identifier.

[0139] In one possible implementation, the first identifier of the first service and the second identifier of the first service are the same. For example, the first identifier of the first service and the second identifier of the first service may be a task identifier (task ID). For example, a first core network element assigns a task identifier to a service inventory request, and the service inventory request sent by the first core network element to an access network device includes the task identifier. Based on the service inventory request, the access network device may initiate an inventory operation and obtain the device identifier of at least one first device. The access network device sends the device identifier and the task identifier of the at least one first device to the first core network element. The first core network element may establish an association between the device identifier of the at least one first device and the task identifier. It is understood that the task identifier can be used to identify an inventory service request. That is, the first core network element can obtain the association between the device identifier of the at least one first device and the inventory service request. The first core network element can determine which inventory service request the first device's device identifier is for, thereby facilitating the first core network element's management of device identifiers.

[0140] In another possible implementation, the first identifier of the first service includes a third identifier assigned by the first core network element to the first service, and the second identifier of the first service includes the third identifier and a fourth identifier assigned by the access network device to the first service. For example, the third identifier assigned by the first core network element to the first service may be a non-device association next generation application protocol (NGAP) identifier (non-device association NGAP ID), for example, the non-device association NGAP identifier may be an AIoT association NGAP ID. The fourth identifier assigned by the access network device to the first service may be a non-device association NGAP ID. The third identifier and the fourth identifier form an identifier pair, which is used to identify the first task on the interface between the access network device and the first core network element. Specifically, the third identifier is used by the first core network element to identify the first service on the interface between the first core network element and the access network device, and the fourth identifier is used by the access network device to identify the first service on the interface between the first core network element and the access network device. Optionally, the interface between the first core network element and the access network device may be the first interface. For example, when the first core network element is AMF, the interface between AMF and the access network device is a next generation (NG) interface, that is, the first interface can be an NG interface. Alternatively, when the first core network element is TMF, or other network elements that support AIOT such as AIOTMF, the first interface can be an NG interface, or the first interface can be an interface other than the first interface. Furthermore, an application layer protocol can be applied in the first interface. For example, when the first interface is an NG interface, the application layer protocol can be an NGAP protocol. Alternatively, when the first interface is an interface other than an NG interface, the application layer protocol can be a protocol other than the NGAP protocol. For example, the protocol can be called an application layer protocol (application protocol, AP).

[0141] For example, the first core network network element sends an inventory service request to the access network device. The inventory service request includes a mask and a third identifier. The third identifier can be an identifier assigned by the first core network network element to the current inventory service request. The third identifier is used by the first core network network element to identify the current inventory service request on the interface between the first core network network element and the access network device. The access network device inventories the devices according to the inventory service request and obtains the device identifier of at least one first device. The access network device assigns a fourth identifier to the current inventory service request. The fourth identifier is used by the access network device to identify the current inventory service request on the interface between the first core network network element and the access network device. The access network device reports the following information to the first core network network element: the device identifier of at least one first device + the third identifier + the fourth identifier.

[0142] It is understandable that the two possible implementations described above can be combined. For example, the first core network element assigns a task identifier and a third identifier to the current inventory service request, and the access network device assigns a fourth request to the current inventory service request. The access network device reports the following information to the first core network element: the device identifier of at least one first device + the task identifier + the third identifier + the fourth identifier. Optionally, the device identifier of at least one first device can form a device ID list (device ID list), i.e., the device ID list includes the device identifier of at least one first device.

[0143] Optionally, when the access network device assigns a fourth identifier to the current inventory service request, it also includes: the access network device sends the fourth identifier to the first core network network element, and the first core network network element receives the fourth identifier from the access network device. In one possible implementation, the response message to the inventory service request carries the fourth identifier. The access network device sends a response message to the inventory service request to the first core network network element, which can be performed after step 410 or after step 440, without limitation. When performed after step 440, the information reported by the access network device in step 440 to the first core network network element includes the following: the device identifier of at least one first device + [task identifier and / or third identifier], because at this time the access network device has not yet assigned the fourth identifier to the first task.

[0144] It is understandable that in the embodiments of the present application, the example of "the first service is an inventory service" is mainly used for explanation. In addition to the inventory service, the first service may also be other services. For example, the first service may be a positioning service, a sensing service, or a command service. In the positioning service, at least one first device may report location information to the access network device. The access network device reports the location information and the identifier of the positioning service to the first core network network element. The first core network network element establishes an association between the location information and the identifier of the positioning service. In the sensing service, at least one first device may report sensor data to the access network device. For example, the sensor data may be temperature data. The access network device reports the sensor data and the identifier of the sensing task to the first core network network element. The first core network network element establishes an association between the sensor data and the identifier of the sensing task. Command services mainly include services corresponding to some operation instructions. For example, command services include at least one of a read service, a write service, a kill service, or a lock service. Taking the reading service as an example, at least one first device reports its reading information to the access network device, the access network device reports the reading information and the identifier of the reading service to the first core network network element, and the first core network network element establishes an association relationship between the reading information and the identifier of the reading service. In step 440, the information reported by the access network device to the first core network network element can be replaced with: at least one uplink data + the second identifier of the first service. When the first service is an inventory service, the at least one uplink data includes the device identifier of the at least one first device. Alternatively, when the first service is a service other than the inventory service, the at least one uplink data can be replaced with the corresponding information.

[0145] As shown in FIG5 , taking the inventory business as an example, the embodiment of the present application provides a flow chart, including:

[0146] Step 500a: The first core network element sends a service inventory request to the access network device, and the access network device receives the service inventory request from the first core network element.

[0147] For example, for the current inventory service request of the inventory service, the first core network network element can assign a task identifier and / or a third identifier to it. It can be understood that the task identifier is assigned by the first core network network element, and the interaction between the first core network network element and the access network device uses the third identifier to identify a task, or is called identifying an inventory service request. The third identifier is assigned by the first core network network element, and the third identifier is used by the first core network network element to identify a task or an inventory service request on the interface between the first core network network element and the access network device. For example, the message sent by the access network device to the first core network network element can carry the third identifier, so that the first core network network element can determine a certain task or a certain inventory service request corresponding to the message based on the third identifier. The inventory service request in step 500a includes the first group identifier, the task identifier and / or the third identifier.

[0148] Optionally, step 500b: the access network device sends a response message to the first core network network element, and the first core network network element receives the response message from the access network device.

[0149] For example, the response message is used to respond to a service inventory request and can be a response message to the service inventory request. For example, when the access network device receives the service inventory request and obtains the third identifier in the request, the access network device can assign a fourth identifier to the current service inventory request. The third identifier and the fourth identifier can form an identifier pair (pair ID), which is used to identify an inventory task or an inventory service request on the interface between the access network device and the first core network element. The response message in step 500b above can carry the fourth identifier. When the first core network element receives the response message, it can obtain the fourth identifier in the response message. Further, the first core network element can form an identifier pair with the third identifier. It is understood that the fourth identifier is assigned by the access network device and is used by the access network device to identify a task or an inventory service request on the interface between the access network device and the first core network element. For example, the message sent by the first core network element to the access network device can carry the fourth identifier, and the access network device can determine the inventory task or inventory service request corresponding to the message based on the fourth identifier.

[0150] Step 510: The access network device sends a paging or selection message, and the first device receives the paging or selection message.

[0151] For example, when the access network device receives an inventory service request, it can obtain the first group identifier, the task identifier and / or the third identifier in the inventory service request. The access network device can broadcast a paging or selection message, which includes the first group identifier. For example, the first group identifier can be a mask. A first device located within the coverage area of ​​the access network device can receive the paging or selection message broadcast by the access network device. The first device obtains the mask in the received paging or selection message and compares the obtained mask with the mask of the first device; if the two are consistent, the first device determines that the access network device is paging or selecting itself, that is, the first device is selected or paged.

[0152] Step 520: The access network device sends a query command to the first device, and the first device receives the query command from the access network device. Furthermore, the access network device may send a repeated query command to the first device, and the first device receives the repeated query command from the access network device.

[0153] For example, the paged or selected first device may receive a query command that is used to initialize an inventory cycle. The first device may determine the initial value of the counter based on the Q value carried in the query command. If the initial value of the counter is 0, the first device may execute step 530 to report RN16 to the access network device. Alternatively, if the initial value of the counter is greater than 1, the first device may receive repeated query commands from the access network device, and each time the first device receives a repeated query command, it decrements the counter by 1 until the counter reaches 0, at which point the first device executes step 530 to send RN16 to the access network device.

[0154] Step 530: The first device sends a first random access request message (eg, RN16) to the access network device, and the access network device receives the first random access request message (eg, RN16) from the first device.

[0155] For example, the first device can use the first time-frequency resource to send RN16 to the access network device; if the access network device detects an RN16 on the first time-frequency resource, it is considered that there is no collision, and the first device can execute step 540 to send an ACK to the access network device, which carries RN16.

[0156] Step 540: The access network device sends an ACK, and the first device receives the ACK.

[0157] For example, the access network device may broadcast an ACK, and a first device within the access network device's coverage area may receive the ACK. The first device obtains the RN16 in the ACK and compares the RN16 with the RN16 sent by the first device to see if it is identical. If they are identical, the first device successfully accesses the network, and step 550 is executed. It is understood that a device that fails to access the network can retry access. If access is unsuccessful within the maximum number of retransmissions, the access network device may send an indication to the device, instructing it to wait for the next inventory cycle.

[0158] Step 550: The first device sends uplink data to the access network device, and the access network device receives the uplink data from the first device.

[0159] For example, the uplink data carries the device identifier of the first device. Optionally, the device identifier of the first device sent by the first device can be carried in a non-access stratum (NAS) message, and the access network device can transparently transmit the NAS message to the first core network network element. For example, in step 550, the access network device sends the following information to the first core network network element: a device identifier list + a task identifier and / or an identifier pair consisting of a third identifier and a fourth identifier. The device identifier list includes n device identifiers, where n is an integer greater than or equal to 1: in a possible implementation, the access network device sends a message to the first core network network element, the message including n NAS messages + a task identifier and / or an identifier pair consisting of a third identifier and a fourth identifier, and each of the n NAS messages includes a corresponding device identifier. Alternatively, in a possible implementation, the access network device sends n messages to the first core network network element, each message including a corresponding NAS message + a task identifier and / or an identifier pair consisting of a third identifier and a fourth identifier, and each NAS message includes a corresponding device identifier.

[0160] Step 560: The access network device sends a device identification list + [identification pair consisting of task identification and / or third identification and fourth identification] to the first core network network element, and the first core network network element receives the device identification list + [identification pair consisting of task identification and / or third identification and fourth identification] from the access network device.

[0161] In one possible implementation, the device identifier list in step 560 includes multiple device identifiers, and the information sent by the access network device to the first core network element is as follows: multiple device identifiers + [a task identifier and / or an identifier pair consisting of a third identifier and a fourth identifier]. Alternatively, in step 560, the information reported by the access network device to the first core network element may be replaced by: a single device identifier + [a task identifier and / or an identifier pair consisting of a third identifier and a fourth identifier].

[0162] For example, the access network device sends a device identification list + [the format of the identification pair consisting of the task identification and / or the third identification and the fourth identification] to the first core network network element, as shown in Figure 6. In the example of Figure 6, the device identification list includes the device identifications of n devices, and the device identifications of the n devices can be carried in: uplink data 1 to uplink data n, respectively. It can be understood that the access network device can report through one message: the device identification list + the identification pair consisting of the task identification and / or the third identification and the fourth identification. For example, the access network device sends a message to the first core network network element, and the message includes: the device identification list + [the identification pair consisting of the task identification and / or the third identification and the fourth identification]. For example, the one message can be an NGAP message. Alternatively, the access network device can report the information in step 560 through multiple messages. For example, take the example of the device identification list including the device identifications of n devices. The access network device sends n messages to the first core network network element, where one message i among the n messages includes: a device identifier of device i + [a task identifier and / or an identifier pair consisting of a third identifier and a fourth identifier], where i is an integer greater than zero and less than or equal to n, and n is an integer greater than 1. For example, the n messages may be n NGAP messages.

[0163] Optionally, in the flowchart of Figure 5, step 500b may also be performed after step 550. If step 500b is performed after step 550: since the access network device allocates the fourth identifier in step 500b, in step 550, the information reported by the access network device to the first core network network element may be replaced by: device identifier list + [task identifier and / or third identifier].

[0164] Through the above design, when the first core network network element triggers the access network device to execute the first service, the first core network device also sends the first identifier corresponding to the first service allocation to the access network device. When the access network device reports the information obtained by executing the first service, it also reports the identifier of the first service corresponding to the information to the first core network network element, so that the first core network network element can know which service the information reported by the access network device is associated with, which facilitates the first core network network element to manage the information reported by the access network device.

[0165] [Example 2]

[0166] This second embodiment can be implemented based on the first embodiment. In the second embodiment, a corresponding identifier is assigned to each device, and the identifier is used to identify the device at the interface between the access network device and the first core network element. Optionally, the interface between the access network device and the first core network element can be a first interface, for example, the first interface can be an NG interface.

[0167] For example, the access network device may assign a fifth identifier to the first device, where the fifth identifier is used by the access network device to identify the first device on an interface between the access network device and the first core network element. The access network device may report the fifth identifier to the first core network element. For example, the access network device sends the fifth identifier to the first core network element, and the first core network element receives the fifth identifier from the access network device.

[0168] In one possible implementation, the fifth identifier may be a tag identifier (tag ID). Alternatively, the fifth identifier may be a non-device association NGAP ID. Further: the first core network network element may assign a sixth identifier to the first device, and the sixth identifier is used by the first core network network element to identify the first device on the interface between the access network device and the first core network network element. For example, the sixth identifier may be a non-device association NGAP identifier, and the fifth identifier and the sixth identifier may form an identifier pair (pair ID). The first core network network element may notify the access network device of the sixth identifier. For example, the first core network network element sends the sixth identifier to the access network device, and the access network device receives the sixth identifier from the first core network network element. Optionally, the first core network network element may send the sixth identifier to the access network device in a command message. For example, the command message sent by the first core network network element to the access network device carries the sixth identifier. Further, the command message also includes the fifth identifier.

[0169] Optionally, it also includes: the first core network network element sends a first indication to the access network device, and the access network device receives the first indication from the first core network network element, where the first indication is used to indicate the number of times the first device receives the command message. The access network device sends the first indication to the first device, and the first device receives the first indication from the access network device. The beneficial effects are as follows: since the first device does not know the number of times the command message is received, after the relevant process of a command message is completed, the first device will continue to wait for the access network device to send the command message again. In the above design, the access network device notifies the first device of the number of times the first device receives the command message. After the number of times the first device receives the command message reaches the number indicated by the first indication, the first device will no longer continue to monitor the command message, thereby reducing the time the first device monitors the command message.

[0170] As shown in FIG7 , the embodiment of the present application provides a flow chart, including:

[0171] Step 700a: The first core network element sends a service inventory request to the access network device, and the access network device receives the service inventory request from the first core network element.

[0172] Step 700b: The access network device sends a response message to the first core network network element, and the first core network network element receives the response message from the access network device.

[0173] Step 710: The access network device sends a paging or selection message, and the first device receives the paging or selection message.

[0174] Step 720: The access network device sends a query command to the first device, and the first device receives the query command from the access network device. Furthermore, the access network device may send a repeated query command to the first device, and the first device receives the repeated query command from the access network device.

[0175] Step 730: The first device sends a first random access request message (eg, RN16) to the access network device, and the access network device receives the first random access request message (eg, RN16) from the first device.

[0176] Step 740: The access network device sends an ACK, and the first device receives the ACK.

[0177] Step 750: The first device sends uplink data to the access network device, and the access network device receives the uplink data from the first device.

[0178] For example, the uplink data carries the device identifier of the first device.

[0179] The implementation process of steps 700a to 750 can be found in the description of steps 600a to 650 in FIG6 , and will not be described in detail.

[0180] Different from the first embodiment, in the second embodiment, the "inventory service request" in step 700a can be replaced by a "command service request". For example, the command service request may specifically be a service request such as a read command, a write command, a lock command, or a deactivate command. Furthermore, the "inventory service request" in step 700a may include a first indication, and the first indication is used to indicate the number of times the first device receives the command message. When the access network device receives the inventory service request, it can obtain the first indication in the inventory service request and send the first indication to the first device. For example, the access network device sends the first indication to the first device through the paging or selection message in step 710. For example, the paging or selection message in step 710 carries the first indication.

[0181] Step 760: The access network device sends the identifier of the first device + (the task identifier and / or the identifier pair consisting of the third identifier and the fourth identifier) ​​+ (the label identifier and / or the fifth identifier) ​​to the first core network network element, and the first core network network element receives the identifier of the first device + (the task identifier and / or the identifier pair consisting of the third identifier and the fourth identifier) ​​+ (the label identifier and / or the fifth identifier) ​​from the access network device.

[0182] Due to the above inventory process, the access network device can obtain the device identification of at least one first device. In a possible implementation, for each first device, the access network device sends a message to the first core network network element, and the message includes: the identification of the first device + (the task identification and / or the identification pair consisting of the third identification and the fourth identification) + (the label identification and / or the fifth identification). In this process, the access network device reports the corresponding information for each device, and this process is called per tag reporting. Alternatively, for all first devices, the access network device reports a message to the first core network network element, and the message includes: a device identification list + (the identification pair consisting of the task identification and / or the third identification and the fourth identification) + (the label identification and / or the fifth identification), and the device identification list includes the device identification of at least one first device. It can be understood that when the first core network network element is an AMF, the interface between the access network device and the first core network network element is an NGAP interface, and the message sent by the access network device to the first core network network element is called an NGAP message.

[0183] For information on the task identifier, as well as the third and fourth identifiers, please refer to the description in Example 1. This Example 2 focuses on the process of tag identification and the fifth identifier. It is understood that before executing step 760, the access network device may assign an identifier to the first device, which may be a tag ID. It is understood that all interactions between the access network device and the first core network element utilize this tag ID. And / or, this identifier may be implemented by assigning an identifier to each of the access network device and the first core network element. For example, before step 760, the access network device assigns a fifth identifier to the first device, which may be a non-device-associated NGAP identifier. This fifth identifier is primarily used by the access network device to identify the first device on the interface between the access network device and the first core network element. For example, a message sent by the first core network element to the access network device includes at least the fifth identifier. In Example 2, before step 770, the first core network element may assign a sixth identifier to the first device. For example, this sixth identifier may be a non-device-associated NGAP identifier. This sixth identifier is primarily used by the first core network element to identify the first device on the interface between the access network device and the first core network element. For example, the sixth identifier may be included in a message sent by the access network device to the first core network element. Optionally, the first core network element may notify the access network device of the sixth identifier via the command message in step 770. For example, the command message in step 770 may include at least the sixth identifier.

[0184] It is understandable that step 700b may also occur after step 760. If step 700b is performed after step 760, the message sent by the access network device to the first core network element carries the third identifier and no longer carries the fourth identifier. For example, the information reported by the access network device to the first core network element may be replaced by: the identifier of the first device + (the task identifier and / or the third identifier) ​​+ (the tag identifier and / or the fifth identifier).

[0185] Step 770: The first core network element sends a command message to the access network device, and the access network device receives the command message from the first core network element.

[0186] In this embodiment of the present application, the command message in step 770 includes: a device identifier list + (a task identifier and / or an identifier pair consisting of a third identifier and a fourth identifier) ​​+ (a tag identifier and / or an identifier pair consisting of a fifth identifier and a sixth identifier). It will be understood that the device identifier carried in the command message in step 770 is the identifier of the device that will execute the command. Through the aforementioned process, the access network device inventories at least one first device and reports the device identifier of the at least one first device to the first core network element. The first core network element may determine that all or some of the at least one first device will execute the command message. For example, the command message may be a read command, a write command, a lock command, or a deactivate command. The "device identifier" carried in the command message in step 770 may be the identifier of the device determined by the first core network element to execute the command message. For example, the access network device inventories five first devices and reports the device identifiers of the five first devices to the first core network element. The first core network element may determine that three of the five first devices will execute the command message. Then in step 770, the device identifier in the command message sent by the first core network network element to the access network device includes: device identifiers of three first devices.

[0187] In one possible implementation, the device identifier can be carried in a NAS message, which is carried in a command message. That is, the command message sent by the first core network element to the access network device includes the NAS message + (a task identifier and / or an identifier pair consisting of a third identifier and a fourth identifier) ​​+ (an identifier pair consisting of a label identifier and / or a fifth identifier and a sixth identifier), and the NAS message includes the device identifier. Because the access network device cannot parse the NAS message, the access network device cannot obtain the device identifier of the device executing the command message. In an embodiment of the present application, the access network device can parse the command message to obtain (an identifier pair consisting of a task identifier and / or a third identifier and a fourth identifier) ​​+ (an identifier pair consisting of a label identifier and / or a fifth identifier and a sixth identifier). The access network device can determine a service inventory request using (an identifier pair consisting of a task identifier and / or a third identifier and a fourth identifier) ​​and further obtain at least one first device inventoried based on the service inventory request. Furthermore, the access network device can determine one or more first devices in at least one first device using (an identifier pair consisting of a label identifier and / or a fifth identifier and a sixth identifier). The access network device may trigger the one or more first devices to execute the command process, for example, to execute steps 780 and 790 .

[0188] Step 780: The access network device sends downlink data (DL data) to the first device, and the first device receives the downlink data from the access network device.

[0189] For example, the downlink data carries a command indication. When the first device receives the downlink data, it can obtain the command indication in the downlink data. The first device performs a corresponding operation according to the command indication, such as a read operation, a write operation, a lock operation, or a deactivation operation.

[0190] Step 790: The first device sends uplink data to the first core network network element through the access network device, and the first core network network element receives the uplink data from the first device through the access network device.

[0191] Optionally, the uplink data includes information obtained by the first device executing the command instruction. For example, when the command instruction is used to indicate a read operation, the uplink data may carry information read by the first device.

[0192] It should be noted that, in the above description, the example in which the access network device allocates the fifth identifier to the first device in step 760 is described. In one possible implementation, the access network device may allocate the fifth identifier to the first device after step 770. For example, in step 790, the access network device allocates the fifth identifier to the first device, and sends the fifth identifier to the first core network network element through the uplink data in step 790. At this time, in step 770, the information sent by the first core network network element to the access network device can be replaced by: device identifier + (task identifier and / or identifier pair consisting of the third identifier and the fourth identifier) ​​+ (label identifier and / or fifth identifier).

[0193] With the above design, a corresponding identifier is assigned to the first device at the interface between the access network device and the first core network element. The command message sent by the first core network element to the access network device includes the identifier of the device that is to execute the command message. Because the access network device can recognize the identifier at the interface between the access network device and the first core network element, the access network device can forward the command message to the corresponding device for execution based on the identifier, thereby accurately forwarding the command message to the corresponding device.

[0194] [Example 3]

[0195] The difference between Example 3 and Example 2 is that after the access network device reports the inventory device identifier to the first core network element, the first core network element may send a first message to the access network device. The access network device receives the first message from the first core network element, and the first message is used to instruct the first device to stop listening for command messages. Based on the first message, the access network device sends a second message to the first device. Upon receiving the second message, the first device stops listening for command messages.

[0196] As shown in FIG8 , the embodiment of the present application provides a flow chart, including:

[0197] Step 800a: The first core network element sends a service inventory request to the access network device, and the access network device receives the service inventory request from the first core network element.

[0198] Optionally, step 800b: the access network device sends a response message to the first core network network element, and the first core network network element receives the response message from the access network device.

[0199] Step 810: The access network device sends a paging or selection message, and the first device receives the paging or selection message.

[0200] Step 820: The access network device sends a query command to the first device, and the first device receives the query command from the access network device. Furthermore, the access network device may also send a repeated query command to the first device, and the first device receives the repeated query command from the access network device.

[0201] Step 830: The first device sends a first random access request message (eg, RN16) to the access network device, and the access network device receives the first random access request message (eg, RN16) from the first device.

[0202] Step 840: The access network device sends an ACK, and the first device receives the ACK.

[0203] Step 850: The first device sends uplink data to the access network device, and the access network device receives the uplink data from the first device.

[0204] For example, the uplink data carries the device identifier of the first device.

[0205] Step 860: The access network device sends a device identification list + (task identification and / or an identification pair consisting of a third identification and a fourth identification) + (label identification and / or a fifth identification) to the first core network network element, and the first core network network element receives the device identification list + (task identification and / or an identification pair consisting of a third identification and a fourth identification) + (label identification and / or a fifth identification) from the access network device.

[0206] The implementation process of step 800a to step 860 can refer to the implementation process of step 700a to step 760, which will not be repeated here.

[0207] Step 870: The first core network element sends a first message to the access network device, and the access network device receives the first message from the first core network element.

[0208] For example, the first message may also be referred to as a first signaling, and the first message is used to instruct the first device to stop listening for command messages. The first message may explicitly or implicitly indicate that the first device has stopped listening for command messages. For example, the first message carries an indication that instructs the first device to stop listening for command messages. Alternatively, the first message may implicitly indicate that the first device has stopped listening for command messages. For example, the name of the first message may be "Command Cancel Indication," "Context Release Request," or "Next Tag Indication Request." Based on the name of the first message, the access network device may implicitly determine that the first device has stopped listening for paging messages.

[0209] It is understood that in the second embodiment, in step 870, the first core network element notifies the access network device of the sixth identifier via a command message. The sixth identifier is assigned by the first core network element to the first device to identify the first device on the interface between the first core network element and the access network device. In this third embodiment, the sixth identifier can be notified to the access network device via the first message in step 870. For example, the first message includes the sixth identifier. Furthermore, the first message also includes the fifth identifier, which the access network device reported to the first core network element in step 860.

[0210] In one possible implementation, the first message in step 870 includes: a list of device identifiers + (a task identifier and / or an identifier pair consisting of a third identifier and a fourth identifier) ​​+ (a tag identifier and / or an identifier pair consisting of a fifth identifier and a sixth identifier). It is understood that the "device identifier" included in the first message may be the identifier of the device that stops listening for command messages. The device that stops listening for command messages may be all or part of the device identifiers reported in step 860. In other words, the first core network element may instruct all or part of the inventoried devices to stop listening for command messages.

[0211] Step 880: The access network device sends a second message to the first device, and the first device receives the second message from the access network device.

[0212] In one possible implementation, the access network device may determine whether it has received a first message from the first core network network element. If the access network device receives the first message from the first core network network element, step 880 is executed, and the access network device sends a second message to the first device. Optionally, the second message may be referred to as a second signaling. The second message may be a message other than a command message. For example, the second message may be a selection or paging message, a query command, an access round trigger, an access round indicator, a query Rep, an access occasion trigger, or an access occasion indicator. The principle is as follows: when the first device receives the above-mentioned second message, since the second message is a message other than a command message. When the first device receives the above-mentioned second message, it can directly execute the second message without listening to the command message.

[0213] Through the above design, the first core network element sends a first message to the access network device, and the access network device sends a second message to the first device based on the first message. When the first device receives the second message, it stops listening to the command message, thereby reducing the time the first device listens to the command message.

[0214] [Example 4]

[0215] As shown in Figure 9, the access network equipment in this embodiment can adopt an O-RAN architecture: the access network equipment communicates with the CN via a backhaul link and communicates with the terminal via an air interface. The core network includes at least one core network element.

[0216] For example, the BBU in an access network device communicates with the core network via a backhaul link, and the RU in the access network device communicates with at least one terminal via an air interface. The BBU communicates with at least one RU via a fronthaul link. The BBU and RU may or may not be co-located. The BBU includes at least one CU and at least one DU. At least one CU can communicate with at least one DU via a midhaul link. The interface between the CU and DU is the F1 interface.

[0217] The difference between the fourth embodiment and the first embodiment is that: in the first embodiment, a task is identified on the interface between the access network device and the first core network element. In the fourth embodiment, a task is identified on the F1 interface between the CU and the DU.

[0218] In the scheme of Example 4: A first core network element sends a service request for a first task to a CU. The CU receives the service request for the first task from the first core network element, where the service request includes a first group identifier. The CU assigns a first identifier to the first task. The CU sends the first group identifier and the first identifier of the first task to a DU. The DU receives the first group identifier and the first identifier of the first task from the CU. The DU broadcasts the first group identifier, which is used to trigger at least one first device to report its device identifier. Upon receiving the first group identifier, the at least one first device sends the device identifier of the at least one first device to the DU. The DU sends the device identifier of the at least one first device and the second identifier of the first task to the CU. Optionally, the first identifier of the first task and the second identifier of the first task may be the same, for example, both the first identifier of the first task and the second identifier of the first task are task identifiers (task IDs). Alternatively, the second identifier of the first task may include the first identifier of the first task. For example, the first identifier of the first task includes the third identifier assigned by the CU for the first service, and the second identifier of the first service includes the third identifier and a fourth identifier assigned by the DU for the first service. See the following description for details.

[0219] Taking the first business as an inventory business as an example, as shown in FIG10 , an embodiment of the present application provides a flow chart, including:

[0220] Step 1000: A first core network element sends a service inventory request to a CU, and the CU receives the service inventory request from the first core network element.

[0221] For example, an inventory service request includes a first set of identifiers, which may be referred to as a mask.

[0222] Step 1010a: The CU sends an inventory service request to the DU, and the DU receives the inventory service request from the CU.

[0223] For example, the CU may assign an identifier to an inventory task or an inventory service request, and the identifier may be called a task identifier. The interaction between the CU and the DU uses the task identifier to identify an inventory task or an inventory service request. And / or, the CU may assign an identifier to an inventory task or an inventory service request, and the identifier may be a third identifier, which is used by the CU to identify a task or an inventory service request on the interface between the CU and the DU. For example, the third identifier may be a non-device association F1 interface identifier (non-device association F1AP ID), for example, the non-device association F1 interface identifier may be an AIoT associated F1AP identifier (AIoT association F1AP ID). The inventory service request in step 1010a includes a first group identifier, a task identifier and / or a third identifier.

[0224] Step 1010b: The DU sends a response message to the CU, and the CU receives the response message from the DU.

[0225] The DU may assign an identifier for an inventory task or an inventory service request, which is called a fourth identifier. The fourth identifier is used by the DU to identify an inventory task or an inventory service request on the interface between the CU and the DU. For example, the fourth identifier may be a non-device association F1 interface identifier (non-device association F1AP ID). It is understood that the third identifier and the fourth identifier may form an identifier pair, and this pair of identifiers is used to identify an inventory task or an inventory service request on the interface between the CU and the DU. The DU may notify the CU of the fourth identifier through a response message, for example, the response message includes the fourth identifier.

[0226] Step 1020: The DU sends a paging or selection message to the first device, and the first device receives the paging or selection message from the DU.

[0227] Step 1030: The DU sends a query command to the first device, and the first device receives the query command from the DU. Furthermore, the DU may also send a repeated query command to the first device, and the first device receives the repeated query command from the DU.

[0228] Step 1040: The first device sends a first random access request message (eg, RN16) to the DU, and the DU receives the first random access request message (eg, RN16) from the first device.

[0229] Step 1050: The DU sends an ACK, and the first device receives the ACK.

[0230] Step 1060: The first device sends uplink data to the DU, and the DU receives the uplink data from the first device.

[0231] For example, the uplink data carries the device identifier of the first device.

[0232] Step 1070: The DU sends the device identification list + [task identification and / or identification pair consisting of the third identification and the fourth identification] to the CU, and the CU receives the device identification list + [task identification and / or identification pair consisting of the third identification and the fourth identification] from the DU.

[0233] For example, the device identification list includes the device identifications of n first devices. That is to say, the DU takes inventory of n first devices through the above inventory process. In step 1070, the DU may send a message to the CU, and the CU receives a message from the DU, the message including: device identification list + [identification pair consisting of task identification and / or third identification and fourth identification], the device identification list including the device identifications of n first devices. For example, as shown in FIG6 , a message sent by the DU to the CU includes the following content: identification pair consisting of task identification and / or third identification and fourth identification, and n uplink data. The n uplink data include the device identifications of the n first devices.

[0234] Alternatively, the DU may send n messages to the CU, and the CU receives n messages from the DU. Each of the n messages includes: a corresponding device identification list + [a task identification and / or an identification pair consisting of a third identification and a fourth identification]. This process is called per tag reporting.

[0235] It is understandable that step 1010b may also occur after step 1070, that is, step 1010b is executed after step 1070. In this case, when step 1070 is executed, the CU has not yet allocated the fourth identifier. Therefore, in step 1070, the information sent by the DU to the CU may be replaced by: device identifier + [task identifier and / or third identifier].

[0236] Through the above design, when the CU receives an inventory service request from the core network, it can send multiple inventory service requests to one or more DUs. Each DU can obtain a device identification list through one inventory. Therefore, when the DU only reports the device identification list to the CU, the CU cannot know which inventory service request the device identification list in the inventory is for, which is inconvenient for the CU to manage the device identification list. In this fourth embodiment, the CU can assign a corresponding identifier to an inventory service request and notify the DU of the identifier. When the DU reports the device identification list to the CU, it reports the identifier corresponding to the device identification list to the CU, so that the CU can know which inventory service request the device identification list reported at this time is for, thereby facilitating the CU's management of the device identification list.

[0237] [Example 5]

[0238] The difference between the fifth embodiment and the second embodiment is that in the second embodiment, a device is identified on the interface between the access network device and the first core network element, while in the fifth embodiment, a device is identified on the F1 interface between the CU and the DU.

[0239] For example, the DU may assign a fifth identifier to the first device, and the fifth identifier is used to identify the first device on the interface between the DU and the CU. The DU may notify the CU of the fifth identifier. For example, the DU sends the fifth identifier to the CU, and the CU receives the fifth identifier from the DU. For example, the fifth identifier may be a tag ID, and all interactions between the DU and the CU regarding the first device use the tag to identify the first device. Alternatively, the fifth identifier may be a non-device association F1AP ID, and the fifth identifier is used by the DU to identify the first device on the interface between the DU and the CU. For example, a message sent by the CU to the DU carries the fifth identifier so that the DU can know that the message is for the first device. Further, the CU may also assign a sixth identifier to the first device, and the sixth identifier is used by the CU to identify the first device on the interface between the CU and the DU. For example, a message sent by the DU to the CU may carry the sixth identifier so that the CU can know that the message is for the first device. For example, the sixth identifier may be a non-device association F1AP ID. Further, the CU may notify the DU of the sixth identifier. For example, the CU sends the sixth identifier to the DU, and the DU receives the sixth identifier from the CU, etc.

[0240] Furthermore, in embodiment five, the CU may send a first indication to the DU, and the DU receives the first indication from the CU, where the first indication is used to indicate the number of times the first device receives the command message. For example, the first indication may be carried in an inventory service request sent by the CU to the DU. The DU sends the first indication to the first device, and the first device receives the first indication from the DU. For example, the first indication may be carried in a paging or selection message sent by the DU to the first device. When the first device receives the first indication, it stops monitoring the command message, thereby reducing the time the first device monitors the command message.

[0241] As shown in Figure 11. This embodiment of the application provides a flow chart, including:

[0242] Step 1110a: The CU sends an inventory service request to the DU, and the DU receives the inventory service request from the CU.

[0243] For example, the inventory service request includes the first group identifier and (the task identifier and / or the third identifier).

[0244] Optionally, step 1110b: the DU sends a response message to the CU, and the CU receives the response message from the DU.

[0245] For example, the response message includes the fourth identifier, and the third identifier and the fourth identifier form an identifier pair. For example, the third identifier and the fourth identifier may be non-device-associated F1AP identifiers.

[0246] Step 1120: The DU sends a paging or selection message to the first device, and the first device receives the paging or selection message from the DU.

[0247] For example, the paging or selection message includes a first group identifier, i.e., a mask. The first device that receives the paging or selection message compares the mask in the paging or selection message with its own mask. If the two match, it considers itself to have been paged or selected and continues to receive query commands. Otherwise, it continues to monitor.

[0248] Step 1130: The DU sends a query command to the first device, and the first device receives the query command from the DU. Furthermore, the DU may send a repeated query command to the first device, and the first device may receive a repeated query command from the DU.

[0249] Step 1140: The first device sends a first random access request message (eg, RN16) to the DU, and the DU receives the first random access request message (eg, RN16) from the first device.

[0250] Step 1150: The DU sends an ACK to the first device, and the first device receives the ACK from the DU.

[0251] Step 1160: The first device sends uplink data to the DU, and the DU receives the uplink data from the first device.

[0252] For example, the uplink data includes the device identifier of the first device.

[0253] The implementation process of steps 1110a to 1160 can refer to the description of steps 1010a to 1060 in Figure 10 of Example 4, and will not be repeated here. Different from Example 4, in Example 5, the "inventory service request" in step 1110a can be replaced by "command service request". For example, the command service request can be specifically a service request such as a read command, a write command, a lock command or a deactivate command. Further, the "inventory service request" in step 1110a may include a first indication, and the first indication is used to indicate the number of times the first device receives the command message. When receiving the inventory service request, the DU can obtain the first indication in the inventory service request and send the first indication to the first device. For example, the DU sends the first indication to the first device through the paging or selection message in step 1120. For example, the paging or selection message in step 1120 carries the first indication.

[0254] Step 1170: DU sends the device identification list + [task identification and / or identification pair consisting of the third identification and the fourth identification] + [label identification and / or the fifth identification] to CU, and CU receives the device identification list + [task identification and / or identification pair consisting of the third identification and the fourth identification] + [label identification and / or the fifth identification] from DU.

[0255] For example, the device identification list includes n identifications of the first devices, where n is an integer greater than 1. The DU may send a message to the CU, which includes the device identification list + [identification pair consisting of the task identification and / or the third identification and the fourth identification] + [identification pair consisting of the label identification and / or the fifth identification and the sixth identification]. It can be understood that at this time, the "label identification" includes the label identifications of n first devices, and the "identification pair consisting of the fifth identification and the sixth identification" includes n identification pairs, each identification corresponding to a first device. Optionally, the one message may be referred to as an F1AP message. Alternatively, the DU may send n messages to the CU, which include the device identification corresponding to the first device + [identification pair consisting of the task identification and / or the third identification and the fourth identification] + [identification pair consisting of the label identification and the fifth identification and the sixth identification]. Optionally, the n messages may be referred to as n F1AP messages.

[0256] It is understandable that the aforementioned step 1110b may occur after step 1170. If step 1110b is performed after step 1170, since the access network device assigns the fourth identifier to the inventory task or inventory service request in step 1110b, the fourth identifier does not exist in step 1170. In this case, in step 1170, the content reported by the DU to the CU can be replaced by: device identifier list + [task identifier and / or third identifier] + [tag identifier and fifth identifier].

[0257] Step 1180: The CU sends a command message to the DU, and the DU receives the command message from the CU.

[0258] For example, when the CU receives the information reported by the DU through step 1170, the CU may assign an identifier to the inventory task or inventory service request, which may be referred to as the sixth identifier. The CU may send the sixth identifier to the DU so that the DU may obtain the sixth identifier. For example, in step 1180, the command message sent by the CU to the DU may include the sixth identifier, that is, the CU may notify the DU of the sixth identifier through the command message. Furthermore, the command message also includes the fifth identifier. It can be understood that the fifth identifier and the sixth identifier may form an identifier pair for identifying the first device.

[0259] In one possible implementation, the command message includes: a device identification list + [a task identification and / or an identification pair consisting of a third identification and a fourth identification] + [an identification pair consisting of a label identification and / or a fifth identification and a sixth identification]. It can be understood that the CU sends a command message to the DU so that all or part of the n first devices in the inventory execute the corresponding command. The device identification included in the command message in step 1180 may be the device identification of some or all of the above-mentioned n first devices. When the device identification included in the command message in step 1180 is the device identification of multiple first devices, the label identification included in the command message may be the identification of multiple first devices, and each specific first device corresponds to a device identification. Similarly, the identification pair consisting of the fifth identification and the sixth identification included in the command message may be the identification of multiple first devices, and each specific first device corresponds to an identification pair.

[0260] Step 1190: The DU sends downlink data to the first device, and the first device receives the downlink data from the DU.

[0261] For example, the downlink data includes a command indication. When the first device receives the downlink data, it can obtain the command indication from the downlink data, and the first device performs a corresponding operation according to the command indication.

[0262] Step 11100: The first device sends uplink data to the DU, and the DU receives the uplink data from the first device.

[0263] Optionally, the uplink data includes information obtained by the first device executing a command instruction. For example, when the command instruction is used to indicate a read operation, the uplink data may carry information read by the first device.

[0264] Step 11110: The DU sends uplink data to the CU, and the CU receives uplink data from the DU.

[0265] Through the above design, an identifier is assigned to the first device at the interface between the CU and the DU. When the CU needs one or more first devices to execute a corresponding command, the CU can carry the corresponding identifier in the command message sent to the DU. Of course, the identifier is the identifier of the device on the interface between the CU and the DU. The DU can determine the one or more first devices that execute the command message based on the identifier, and send a corresponding command indication to the corresponding first device, thereby identifying the first device on the interface between the CU and the DU.

[0266] [Example 6]

[0267] The difference between Example 6 and Example 3 is that: in Example 3, the first core network element sends a first message to the access network device. When the access network device receives the first message, it sends a second message to the first device. When the first device receives the second message, it stops monitoring the command message, thereby reducing the time the first device monitors the command message. In Example 6, the CU sends a first message to the DU. When the DU receives the first message, it sends a second message to the first device. When the first device receives the second message, it stops monitoring the paging message, thereby reducing the time the first device monitors the paging message.

[0268] As shown in FIG12 , a flow chart is provided, including:

[0269] Step 1210a: The CU sends an inventory service request to the DU, and the DU receives the inventory service request from the CU.

[0270] Step 1210b: The DU sends a response message to the CU, and the CU receives the response message from the DU.

[0271] Step 1220: The DU sends a paging or selection message to the first device, and the first device receives the paging or selection message from the DU.

[0272] Step 1230: The DU sends a query command to the first device, and the first device receives the query command from the DU. Furthermore, the DU can also send a repeated query command to the first device, and the first device receives the repeated query command from the DU.

[0273] Step 1240: The first device sends a first random access request message (eg, RN16) to the DU, and the DU receives the first random access request message (eg, RN16) from the first device.

[0274] Step 1250: The DU sends an ACK to the first device, and the first device receives the ACK from the DU.

[0275] Step 1260: The first device sends uplink data to the DU, and the DU receives the uplink data from the first device.

[0276] For example, the uplink data includes the device identifier of the first device.

[0277] Step 1270: DU sends the device identification list + [task identification and / or identification pair consisting of the third identification and the fourth identification] + [label identification and / or the fifth identification] to CU, and CU receives the device identification list + [task identification and / or identification pair consisting of the third identification and the fourth identification] + [label identification and / or the fifth identification] from DU.

[0278] Step 1280: The CU sends a first message to the DU, and the DU receives the first message from the CU.

[0279] For example, the first message may also be referred to as a first signaling, and the first message is used to instruct the first device to stop listening for command messages. The first message may explicitly or implicitly indicate that the first device has stopped listening for command messages. For example, the first message may carry an indication that instructs the first device to stop listening for command messages. Alternatively, the first message may implicitly indicate that the first device has stopped listening for command messages. For example, the name of the first message may be "Command Cancel Indication," "Context Release Request," or "Next Tag Indication Request." Based on the name of the first message, the DU may implicitly determine that the first device has stopped listening for paging messages.

[0280] It is understandable that the CU can assign a sixth identifier to the first device, and the sixth identifier is used by the CU to identify the first device on the interface between the CU and the DU, and the CU can send the sixth identifier to the DU to notify the DU of the sixth identifier. In one possible implementation, the CU can notify the DU of the sixth identifier through the first message in step 1280. For example, the first message in step 1280 includes the sixth identifier. Furthermore, the first message in step 1280 also includes the fifth identifier.

[0281] In one possible implementation, the first message sent by the CU to the DU includes: a device identification list + (a task identification and / or an identification pair consisting of a third identification and a fourth identification) + (a tag identification and / or an identification pair consisting of a fifth identification and a sixth identification). It is understood that the "device identification" included in the first message is actually the device identification of the first device that stopped listening for command messages. This "device identification" can be all or part of the device identifications in the "device identification list" that the DU has inventoried, without limitation.

[0282] Step 1290: The DU sends a second message to the first device, and the first device receives the second message from the DU.

[0283] For the second message, please refer to the description in step 980 in embodiment 3, which will not be repeated here.

[0284] Through the above design, CU sends a first message to DU. When DU receives the first message from CU, DU sends a second message to the first device. When the first device receives the second message from DU, the first device stops listening to the command message, thereby reducing the time the first device listens to the command message.

[0285] It is understood that in the embodiments of the present application, the order of different steps in each process is not limited. In each process, it can include fewer steps or more steps than the flowchart or text description, without limitation. The descriptions of different embodiments can refer to each other, and different embodiments can be combined. The newly combined embodiments are also within the scope of protection of the embodiments of the present application.

[0286] In the embodiments provided in the present application, the methods provided in the embodiments of the present application are introduced from the perspective of the interaction between the first core network element, the access network device and the first device. In order to implement the various functions in the methods provided in the embodiments of the present application, the first core network element or the access network device, etc., may include a hardware structure and / or a software module, and implement the above functions in the form of a hardware structure, a software module, or a hardware structure plus a software module. Whether a certain function among the above functions is executed in the form of a hardware structure, a software module, or a hardware structure plus a software module depends on the design constraints of the specific application of the technical solution.

[0287] Figures 13 and 14 are schematic diagrams of possible devices provided by embodiments of the present application. These communication devices can implement the functions of the access network device or the first core network element in the above-mentioned method embodiments, or implement the functions of the CU or DU. Therefore, it is possible to achieve the beneficial effects of the above-mentioned method embodiments.

[0288] As shown in FIG. 13 , the communication device 1300 includes a processing unit 1310 and a transceiver unit 1320 .

[0289] For example, the processing unit 1310 may also be referred to as a processor, a processing board, a processing module, a processing device, etc. The transceiver unit 1320 may also be referred to as a transceiver, a transceiver, a transceiver module, a transceiver device, a communication unit, etc. Furthermore, the transceiver unit 1320 may include at least one of a transmitting unit and a receiving unit. The transmitting unit and the receiving unit may be integrated together or two independent units.

[0290] In one design, communication apparatus 1300 is configured to implement the functionality of the access network device or the first core network element in FIG. 4 , FIG. 5 , FIG. 7 , or FIG. 8 :

[0291] For example, when the communication device 1300 is used to implement the function of the access network device in Figure 4, Figure 5, Figure 7 or Figure 8: the transceiver unit 1320 is used to receive the first identifier and the first group identifier of the first service from the first core network network element; the transceiver unit 1320 is also used to send the first group identifier, and the first group identifier is used to trigger at least one first device to report the device identifier; the transceiver unit 1320 is also used to receive the device identifier from the at least one first device; the processing unit 1310 is used to determine the second identifier of the first service; the transceiver unit 1320 is also used to send the device identifier and the second identifier of the first service to the first core network network element.

[0292] In a possible implementation manner, the first identifier of the first service is the same as the second identifier of the first service.

[0293] In one possible implementation, the first identifier of the first service includes a third identifier allocated by the first core network element to the first service, and the second identifier of the first service includes the third identifier and a fourth identifier allocated by the access network device to the first service.

[0294] In a possible implementation, the transceiver unit 1320 is further configured to send the fourth identifier to the first core network element.

[0295] In one possible implementation, the transceiver unit 1320 is also used to send a fifth identifier to the first core network network element, where the fifth identifier is an identifier assigned by the access network device to the first device, and the fifth identifier is used by the access network device to identify the first device on the interface between the access network device and the first core network network element.

[0296] In one possible implementation, the transceiver unit 1320 is also used to receive a sixth identifier from the first core network network element, where the sixth identifier is an identifier assigned by the first core network network element to the first device, and the sixth identifier is used by the first core network element to identify the first device on the interface between the access network device and the first core network element.

[0297] In a possible implementation, the sixth identifier is carried in the command message.

[0298] In a possible implementation manner, the command message also includes the fifth identifier.

[0299] In a possible implementation, the sixth identifier is carried in a first message, and the first message is used to instruct the first device to stop monitoring command messages.

[0300] In a possible implementation manner, the first message also includes the fifth identifier.

[0301] In one possible implementation, the transceiver unit 1320 is further used to receive a first indication from the first core network element, where the first indication is used to indicate the number of times the first device receives the command message; and to send the first indication to the first device.

[0302] For example, when the communication device 1300 is used to implement the function of the first core network network element in Figure 4, Figure 5, Figure 7 or Figure 8: the transceiver unit 1320 is used to send the first identifier and the first group identifier of the first service to the access network device, and the first group identifier is used to trigger at least one first device to report the device identifier; the transceiver unit 1320 is also used to receive the device identifier of the at least one first device and the second identifier of the first service from the access network device; the processing unit 1310 is used to process the device identifier of the at least one first device and the second identifier of the first service.

[0303] In a possible implementation manner, the first identifier of the first service is the same as the second identifier of the first service.

[0304] In one possible implementation, the first identifier of the first service includes a third identifier allocated by the first core network element to the first service, and the second identifier of the first service includes the third identifier and a fourth identifier allocated by the access network device to the first service.

[0305] In a possible implementation, the transceiver unit 1320 is further configured to receive the fourth identifier from the access network device.

[0306] In one possible implementation, the transceiver unit 1320 is also used to receive a fifth identifier from the access network device, where the fifth identifier is an identifier assigned by the access network device to the first device, and the fifth identifier is used by the access network device to identify the first device on the interface between the access network device and the first core network network element.

[0307] In one possible implementation, the transceiver unit 1320 is also used to send a sixth identifier to the access network device, where the sixth identifier is an identifier assigned by the first core network network element to the first device, and the sixth identifier is used by the first core network network element to identify the first device on the interface between the access network device and the first core network network element.

[0308] In a possible implementation, the sixth identifier is carried in the command message.

[0309] In a possible implementation manner, the command message also includes the fifth identifier.

[0310] In a possible implementation, the sixth identifier is carried in a first message, and the first message is used to instruct the first device to stop monitoring command messages.

[0311] In a possible implementation manner, the first message further includes the fifth identifier.

[0312] In a possible implementation, the transceiver unit 1320 is further configured to send a first indication to the access network device, where the first indication is used to indicate the number of times the first device receives the command message.

[0313] In one design, communication apparatus 1300 is configured to implement the functionality of the CU or DU in FIG. 10 , FIG. 11 , or FIG. 12 :

[0314] For example, when the communication device is used to implement the function of DU in Figure 10, Figure 11 or Figure 12: the transceiver unit 1320 is used to receive a first identifier and a first group identifier of a first service from a centralized unit CU; send the first group identifier, the first group identifier is used to trigger at least one first device to report a device identifier; receive a device identifier from the at least one first device; and send the device identifier and the second identifier of the first service to the CU.

[0315] In a possible implementation manner, the first identifier of the first service is the same as the second identifier of the first service.

[0316] In a possible implementation, the first identifier of the first service includes a third identifier allocated by the CU for the first service, and the second identifier of the first service includes the third identifier and a fourth identifier allocated by the DU for the first service.

[0317] In a possible implementation, the transceiver unit 1320 is further configured to send the fourth identifier to the CU.

[0318] In one possible implementation, the transceiver unit 1320 is further used to send a fifth identifier to the CU, where the fifth identifier is an identifier assigned by the DU to the first device, and the fifth identifier is used by the DU to identify the first device on the interface between the DU and the CU.

[0319] In one possible implementation, the transceiver unit 1320 is further used to receive a sixth identifier from the CU, where the sixth identifier is an identifier assigned by the CU to the first device, and the sixth identifier is used by the CU to identify the first device on the interface between the DU and the CU.

[0320] In a possible implementation, the sixth identifier is carried in the command message.

[0321] In a possible implementation manner, the command message also includes the fifth identifier.

[0322] In a possible implementation, the sixth identifier is carried in a first message, and the first message is used to instruct the first device to stop monitoring command messages.

[0323] In a possible implementation manner, the first message also includes the fifth identifier.

[0324] In a possible implementation, the transceiver unit 1320 is further configured to receive a first indication from the CU, where the first indication is used to indicate the number of times the first device receives the command message; and send the first indication to the first device.

[0325] For example, when the communication device is used to implement the functions of the CU in FIG. 10 , FIG. 11 , or FIG. 12 :

[0326] The transceiver unit 1320 is used to send a first identifier and a first group identifier of a first service to the distributed unit DU, where the first group identifier is used to trigger at least one first device to report a device identifier; and to receive the device identifier of the at least one first device and the second identifier of the first service from the DU; the processing unit 1310 is used to process the device identifier of the at least one first device and the second identifier of the first service.

[0327] In a possible implementation manner, the first identifier of the first service is the same as the second identifier of the first service.

[0328] In a possible implementation, the first identifier of the first service includes a third identifier allocated by the CU for the first service, and the second identifier of the first service includes the third identifier and a fourth identifier allocated by the DU for the first service.

[0329] In a possible implementation, the transceiver unit 1320 is further configured to receive the fourth identifier from the DU.

[0330] In one possible implementation, the transceiver unit 1320 is further used to receive a fifth identifier from the DU, where the fifth identifier is an identifier assigned by the DU to the first device, and the fifth identifier is used by the DU to identify the first device on the interface between the DU and the CU.

[0331] In a possible implementation, the transceiver unit 1320 is further used to send a sixth identifier to the DU, where the sixth identifier is an identifier assigned by the CU to the first device, and the sixth identifier is used by the CU to identify the first device on the interface between the DU and the CU.

[0332] In a possible implementation, the sixth identifier is carried in the command message.

[0333] In a possible implementation manner, the command message also includes the fifth identifier.

[0334] In a possible implementation, the sixth identifier is carried in a first message, and the first message is used to instruct the first device to stop monitoring command messages.

[0335] In a possible implementation manner, the first message further includes the fifth identifier.

[0336] In a possible implementation, the transceiver unit 1320 is further configured to send a first indication to the DU, where the first indication is used to indicate the number of times the first device receives the command message.

[0337] For a more detailed description of the processing unit 1310 and the transceiver unit 1320, reference may be made to the description in the above method embodiment, which will not be repeated here.

[0338] It is understood that the division of units in the embodiments of the present application is schematic and is only a logical functional division. In actual implementation, there may be other division methods. In addition, the various functional units in the embodiments of the present application can be integrated into a physical device (for example, a processor), or each functional unit can be a separate physical device, or two or more units can be integrated into a unit for implementation. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional modules.

[0339] Figure 14 shows another schematic diagram of the structure of a communication device 1400 provided in an embodiment of the present application. For example, the communication device 1400 shown in Figure 14 can be a hardware circuit implementation of the communication device 1300 shown in Figure 13. For ease of illustration, Figure 14 only shows the main parts of the communication device.

[0340] As shown in Figure 14, the communication device 1400 includes a processor 1410 and an interface circuit 1420. The processor 1410 and the interface circuit 1420 are coupled to each other.

[0341] For example, the processor 1410 may be a central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor. The interface circuit 1420 may be a transceiver or input / output circuit, etc.

[0342] Optionally, the communication device 1400 may further include a memory 1430 for storing instructions executed by the processor 1410, or storing input data required by the processor 1410 to execute instructions, or storing data generated after the processor 1410 executes instructions. For example, instructions may also be referred to as computer programs, or computer program codes, etc.

[0343] For example, the memory 1430 can be a random access memory (RAM), a flash memory, a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a register, a hard disk, a mobile hard disk, a CD-ROM, or any other form of storage medium known in the art.

[0344] When the communication device 1400 is used to implement the method of the access network device or the first core network network element in Figure 4, Figure 5, Figure 7 or Figure 8, or when the communication device is used to implement the method of DU or CU in Figure 10, Figure 11 or Figure 12: the processor 1410 is used to implement the function of the processing unit 1310, and the interface circuit 1420 is used to implement the function of the transceiver unit 1320.

[0345] In one design, the interface circuit 1420 is used to receive signals from other communication devices outside the communication device 1400 and transmit them to the processor 1410, or to send signals from the processor 1410 to other communication devices outside the communication device. The processor 1410 uses logic circuits or executes code instructions to implement the functions of the access network device or the first core network network element in Figures 4, 5, 7 or 8, or to implement the functions of the DU or CU in Figures 10, 11 or 12.

[0346] An embodiment of the present application also provides a communications device, comprising a processor and a memory, the processor and memory being coupled together. The processor is configured to implement the functions of the access network device or first core network element in Figures 4, 5, 7, or 8, or the functions of the DU or CU in Figures 10, 11, or 12. For example, the processor may execute instructions in the memory to cause the communications device to implement one or more functions in the aforementioned method embodiments, such as the functions implemented by the access network device or first core network element in Figures 4, 5, 7, or 8, or the functions implemented by the DU or CU in Figures 10, 11, or 12. In one exemplary embodiment, a storage medium is coupled to the processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium may also be a component of the processor. The processor and storage medium may be located in an ASIC. Alternatively, the ASIC may be located in the access network device or first core network element in Figures 4, 5, 7, or 8, or in the DU or CU in Figures 10, 11, or 12. The processor and storage medium may also exist as discrete components in the access network device or the first core network element in Figure 4, Figure 5, Figure 7 or Figure 8, or in the DU or CU in Figure 10, Figure 11 or Figure 12.

[0347] An embodiment of the present application also provides a communication device, which includes a processor, and the processor is used to implement the functions of the access network device or the first core network network element in Figure 4, Figure 5, Figure 7 or Figure 8, or to implement the functions of the DU or CU in Figure 10, Figure 11 or Figure 12.

[0348] The present application also provides a computer-readable storage medium storing instructions, which may also be referred to as computer programs, computer program codes, etc. The instructions are executed on a computer, causing the computer to execute the functions of the access network device or the first core network element in FIG. 4 , FIG. 5 , FIG. 7 , or FIG. 8 in the above method embodiments, or to execute the functions of the DU or CU in FIG. 10 , FIG. 11 , or FIG. 12 in the above method embodiments.

[0349] Optionally, the computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable device. The computer program or instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program or instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired or wireless method. The computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; an optical medium, such as a digital video disc; or a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both volatile and non-volatile types of storage media.

[0350] The embodiment of the present application also provides a computer program product, including a computer program or an instruction. When the computer program or instruction is run on a computer, the method of the access network device or the first core network element in Figure 4, Figure 5, Figure 7 or Figure 8 is executed, or the method of the DU or CU in Figure 10, Figure 11 or Figure 12 is executed. For example, the computer program product includes one or more computer programs or instructions. When the computer program or instruction is loaded and executed on the computer, the process or function of the access network device or the first core network element in Figure 4, Figure 5, Figure 7 or Figure 8 of the embodiment of the present application is executed in whole or in part, or the function of the DU or CU in Figure 10, Figure 11 or Figure 12 of the embodiment of the present application is executed.

[0351] It is understood that the methods in the embodiments of the present application can be implemented in whole or in part by software, hardware, firmware, or any other combination. When implemented by software, they can be implemented in whole or in part in the form of a computer program product.

[0352] An embodiment of the present application also provides a chip, which includes a processor, which is coupled to a memory, and the processor is used to execute a computer program or instruction stored in the memory, so that the chip implements the function of the access network device or the first core network element in Figure 4, Figure 5, Figure 7 or Figure 8, or enables the chip to implement the function of the DU or CU in Figure 10, Figure 11 or Figure 12. For example, taking the chip implementing the function of the access network device as an example, the chip can receive information from other modules of the access network device (such as radio frequency or antenna, etc.), and the information can be sent by the terminal to the access network device. Alternatively, the chip can send information to other modules in the access network device (such as radio frequency or antenna, etc.), and the information is sent by the access network device to the terminal, etc.

[0353] An embodiment of the present application further provides a communication system, including: a first communication device and a second communication device.

[0354] Among them, the first communication device can implement the functions of the access network device in Figures 4, 5, 7, or 8 above; the second communication device can implement the functions of the first core network network element in Figures 4, 5, 7, or 8 above; or the first communication device can implement the functions of the DU in Figures 10, 11, or 12 above; the second communication device can implement the functions of the CU in Figures 10, 11, or 12 above. For the specific structure of the first communication device or the second communication device, please refer to the previous description, such as the structural description in Figures 13 or 14.

[0355] In the description of this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. In the text description of this application, the character " / " generally indicates that the previous and next associated objects are in an "or" relationship; "including at least one of A, B or C" can mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B and C.

[0356] The various numbers used in the embodiments of this application are for ease of description and are not intended to limit the scope of the embodiments of this application. The order of the sequence numbers of the above processes does not necessarily indicate the order in which they are executed. The order in which the processes are executed should be determined by their functions and internal logic.

[0357] Obviously, those skilled in the art may make various changes and modifications to the present application without departing from the scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include these modifications and variations.

Claims

1. A communication method, characterized in that: The method is applied to an access network device, comprising: Receiving a first identifier and a first group identifier of a first service from a first core network network element; Sending the first group identifier, where the first group identifier is used to trigger at least one first device to report a device identifier; receiving a device identification from the at least one first device; Send the device identifier and the second identifier of the first service to the first core network element.

2. The method according to claim 1, wherein The first identifier of the first service is the same as the second identifier of the first service.

3. The method according to claim 1, wherein The first identifier of the first service includes a third identifier allocated by the first core network element to the first service, and the second identifier of the first service includes the third identifier and a fourth identifier allocated by the access network device to the first service.

4. The method according to claim 3, wherein Also includes: Send the fourth identifier to the first core network element.

5. The method according to any one of claims 1 to 4, characterized in that Also includes: A fifth identifier is sent to the first core network network element, where the fifth identifier is an identifier assigned by the access network device to the first device, and the fifth identifier is used by the access network device to identify the first device on the interface between the access network device and the first core network network element.

6. The method according to any one of claims 1 to 5, characterized in that Also includes: Receive the sixth identifier from the first core network network element, where the sixth identifier is the identifier assigned by the first core network network element to the first device, and the sixth identifier is used by the first core network network element to identify the first device on the interface between the access network device and the first core network network element.

7. The method according to claim 6, wherein The sixth identifier is carried in the command message.

8. The method according to claim 7, wherein The command message also includes the fifth identifier.

9. The method according to claim 6, wherein The sixth identifier is carried in the first message, and the first message is used to instruct the first device to stop monitoring command messages.

10. The method according to claim 9, wherein The first message also includes the fifth identifier.

11. The method according to any one of claims 1 to 10, characterized in that Also includes: receiving a first indication from the first core network element, where the first indication is used to indicate a number of times the first device receives the command message; Send the first indication to the first device.

12. A communication method, characterized in that: The method is applied to a first core network element, including: Sending a first identifier and a first group identifier of a first service to an access network device, where the first group identifier is used to trigger at least one first device to report a device identifier; Receive a device identifier of the at least one first device and a second identifier of the first service from the access network device.

13. The method according to claim 12, wherein: The first identifier of the first service is the same as the second identifier of the first service.

14. The method according to claim 12, wherein: The first identifier of the first service includes a third identifier allocated by the first core network element to the first service, and the second identifier of the first service includes the third identifier and a fourth identifier allocated by the access network device to the first service.

15. The method according to claim 14, wherein Also includes: Receive the fourth identifier from the access network device.

16. The method according to any one of claims 12 to 15, characterized in that Also includes: Receive a fifth identifier from the access network device, where the fifth identifier is an identifier assigned by the access network device to the first device, and the fifth identifier is used by the access network device to identify the first device on the interface between the access network device and the first core network network element.

17. The method according to any one of claims 12 to 16, characterized in that Also includes: A sixth identifier is sent to the access network device, where the sixth identifier is an identifier assigned by the first core network network element to the first device, and the sixth identifier is used by the first core network network element to identify the first device on the interface between the access network device and the first core network network element.

18. The method according to claim 17, wherein The sixth identifier is carried in the command message.

19. The method according to claim 18, wherein The command message also includes the fifth identifier.

20. The method of claim 17, wherein: The sixth identifier is carried in the first message, and the first message is used to instruct the first device to stop monitoring command messages.

21. The method according to claim 20, wherein The first message also includes the fifth identifier.

22. The method according to any one of claims 12 to 21, characterized in that Also includes: A first indication is sent to the access network device, where the first indication is used to indicate the number of times the first device receives the command message.

23. A communication device, characterized in that: Comprising means for performing the method according to any one of claims 1 to 11.

24. A communication device, characterized in that: The communication device comprises a processor and a memory, wherein the processor is coupled to the memory, and the processor is configured to execute a computer program or instruction in the memory, so that the communication device implements the method according to any one of claims 1 to 11.

25. A communication device, characterized in that: The method comprises a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, and the processor is used to implement the method according to any one of claims 1 to 11 through a logic circuit or executing code instructions.

26. A communication device, characterized in that: Comprising means for performing the method of any one of claims 12 to 22.

27. A communication device, characterized in that: The communication device comprises a processor and a memory, wherein the processor is coupled to the memory, and the processor is configured to execute a computer program or instruction in the memory, so that the communication device implements the method according to any one of claims 12 to 22.

28. A communication device, characterized in that: It includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, and the processor is used to implement the method as described in any one of claims 12 to 22 through a logic circuit or executing code instructions.

29. A computer-readable storage medium, characterized in that The computer-readable storage medium stores instructions, which, when executed on a computer, enable the computer to execute the method according to any one of claims 1 to 11 or the method according to any one of claims 12 to 22.

30. A computer program product, characterized in that The method comprises a computer program or instructions for executing the method according to any one of claims 1 to 11, or a computer program or instructions for executing the method according to any one of claims 12 to 22.

31. A chip, characterized in that The chip comprises a processor coupled to a memory, wherein the processor is configured to execute a computer program or instruction stored in the memory, so that the chip implements the method according to any one of claims 1 to 11, or implements the method according to any one of claims 12 to 22.

32. A communication system, characterized in that: include: a first communication device and a second communication device; The first communication device is configured to implement the method according to any one of claims 1 to 11; The second communication device is used to implement the method according to any one of claims 12 to 22.

Images