Communication method and communication apparatus

Abstract

The present application provides a communication method and a communication apparatus. The method comprises: receiving first information, wherein the first information comprises a first identifier, the first identifier corresponds to M tags, the first information instructs to perform a first operation on the first identifier, M is greater than or equal to 2, and M is an integer; sending second information to M1 tags among the M tags, wherein the second information instructs to perform the first operation on the M1 tags, M1 is smaller than or equal to M, and M1 is an integer; receiving third information from each tag among N tags, wherein the third information indicates that the first operation is successfully performed on the tag, the N tags fall within the M1 tags, N is smaller than or equal to M1, and N is an integer; and sending fourth information, wherein the fourth information indicates that the first operation is successfully performed on the first identifier. In this way, apparatuses can exchange instructions for instructing to perform the first operation on the first identifier, thereby avoiding frequent exchange of instructions between the apparatuses for instructing to perform the first operation on each tag among the M tags.

Description

A communication method and communication device

[0001] This application claims priority to Chinese Patent Application No. 202510072500.4, filed on January 16, 2025, entitled "A Communication Method and Communication Device", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of wireless communication, and more particularly to a communication method and a communication device. Background Technology

[0003] With the development of communication technology, the 3rd Generation Partnership Project (3GPP) defined the Ambient Internet of Things (AIoT) technology. In AIoT and other related technologies, the communication system can include readers and tags. Tags can be IoT terminals, such as passive / semi-passive / active tags. AIoT technology is mainly used to achieve the following services: inventory management, positioning, sensing, and commands; typical application scenarios of AIoT technology include logistics, warehousing, industrial manufacturing, identity recognition, and environmental monitoring.

[0004] With technological advancements and environmental regulations, the Internet of Things (IoT) will have a much larger application deployment prospect, predicted to cover hundreds of billions of devices in the future. Based on this, the number of tags in the network will increase significantly. If readers and each tag perform one or more processes such as reading, writing, inventorying, or disabling, and simultaneously require tags to respond to the reader's operation requests in real time, this will lead to excessive signaling interactions on the network side. Summary of the Invention

[0005] To address the aforementioned technical problems, this application provides a communication method and communication device, which defines an identifier corresponding to multiple tags and indexes multiple tags using the newly defined identifier when triggering read, write, inventory, or disable processes on the network side, thereby reducing signaling interactions on the network side.

[0006] Firstly, a communication method is provided, which can be executed by a first device, which can be replaced by a tag management functional entity or a component of a tag management functional entity (e.g., a chip, a chip system, a circuit, or a communication module). For ease of understanding, the following description uses execution by a first device as an example. In this case, the first device can also be referred to as a communication device.

[0007] For example, the method includes:

[0008] Receive first information, which includes a first identifier, which corresponds to M tags, and the first information indicates that a first operation should be performed on the first identifier; M≥2, where M is an integer.

[0009] Send a second message to M1 out of M tags. The second message indicates that the first operation should be performed on the M1 tags, where M1 ≤ M and M1 is an integer.

[0010] Receive third information from each of the N tags, indicating that the first operation on the tag was successfully performed; the N tags belong to M1 tags, N≤M1, and N is an integer;

[0011] Send a fourth message indicating that the first operation was successfully performed against the first identifier.

[0012] Based on the above technical solution, by mapping M tags to a first identifier, the devices can interact to instruct each other to perform a first operation on the first identifier, thereby avoiding frequent interaction between the devices to instruct each of the M tags to perform a first operation on each of the M tags.

[0013] For example, M tags correspond to the first terminal; or, M tags correspond to P terminals, and any two tags among the M tags are of the same type, where P is an integer greater than 1.

[0014] Here, the first terminal refers to a single terminal.

[0015] For example, the first identifier is determined based on the identifiers of one or more of the M tags, and the tag identifiers include one or more of the following: tag identifier, electronic product code, or user identifier.

[0016] For example, the first identifier corresponds to M predefined tags.

[0017] In conjunction with the first aspect, in certain implementations of the first aspect, a fourth message is sent, including:

[0018] If the quantity of the third information meets the first condition, then the fourth information is sent.

[0019] The first condition includes one or more of the following: the number of third information is not less than the first threshold; the ratio between the number of third information and M is not less than the second threshold; the number of third information is equal to M; and the ratio between the number of third information received in the first time period and M is not less than the third threshold.

[0020] Based on the above technical solutions, enterprises or operators can define different first conditions for different needs, thereby minimizing the signaling interaction process required to perform the first operation while meeting the requirement. For example, in a warehouse inventory scenario, if multiple tags on a terminal (or an object) are mapped to a single identifier, the first condition can be determined to include the first item mentioned above, thus reducing the signaling interaction required for inventory. As another example, in a location tracking scenario, the first condition can be determined to include the second item mentioned above, thereby ensuring the accuracy of the location tracking.

[0021] In conjunction with the first aspect, in some implementations of the first aspect, the first information also indicates the first condition.

[0022] In conjunction with the first aspect, in some implementations of the first aspect, before sending the second information, the method further includes:

[0023] Send the fifth message, which includes the first identifier. The fifth message is used to request the first tag information of M tags. The first tag information of any one of the M tags is used to determine the tag.

[0024] Receive the sixth message, which includes the first tag information of M tags.

[0025] Based on the above technical solution, the first device can obtain the first tag information of the M tags corresponding to the first identifier, thereby determining the M tags based on the first tag information of the M tags, which is conducive to the first device sending instructions to the M tags to perform the first operation.

[0026] In conjunction with the first aspect, in some implementations of the first aspect, before sending the second information, the method further includes:

[0027] Send the fifth message, which includes the first identifier and is used to request the correspondence between the first identifier and the M tags;

[0028] Receive the sixth information, which includes the correspondence between M tags and the first identifier;

[0029] M labels are determined based on the correspondence.

[0030] Based on the above technical solution, the first device can obtain the correspondence between the first identifier and M tags, thereby determining the M tags according to the correspondence, which is conducive to the first device sending instructions to the M tags to perform the first operation.

[0031] In conjunction with the first aspect, in some implementations of the first aspect, before receiving the first information, the method further includes:

[0032] Receive the seventh message;

[0033] The seventh piece of information includes a first identifier and the first tag information of M tags, wherein the first tag information of any one of the M tags is used to determine the tag; or,

[0034] The seventh piece of information includes the correspondence between the first identifier and the M tags, which is used to determine the M tags.

[0035] Based on the above technical solution, the first device can obtain the first tag information of the M tags corresponding to the first identifier, or obtain the correspondence between the first identifier and the M tags, which is conducive to the first device determining the M tags. Then, after the first device receives the first information, it is conducive to the first device sending instructions to the M tags to perform the first operation.

[0036] In conjunction with the first aspect, in some implementations of the first aspect, the sixth information also includes a first flag indicating that the first identifier is not disabled.

[0037] In conjunction with the first aspect, in some implementations of the first aspect, the first operation includes reading, and the first tag information of the first tag among the M tags includes a second flag with a value of a first value, the second flag with a value of a first value indicating that a write operation was successfully performed on the first tag.

[0038] Based on the above technical solution, the first device can determine whether each of the M tags has successfully performed a write operation. In the case that the first operation includes reading, it is beneficial for the first device to send read instructions only to the tags that have successfully performed a write operation, thereby avoiding the first device sending read instructions to tags that are currently performing a write operation, which could lead to read-write inconsistency or read failure.

[0039] In conjunction with the first aspect, in some implementations of the first aspect, the first operation includes reading, and M1 tags are tags among M tags that have successfully performed a write operation.

[0040] Based on the above technical solution, the first device only sends read commands to tags that have successfully performed write operations, thereby avoiding inconsistency between read and write operations or read failure caused by the first device sending read commands to tags that are currently performing write operations.

[0041] In conjunction with the first aspect, in some implementations of the first aspect, the first operation includes inventory. If the validity of any of the N tags is not verified, then before sending the fourth information, the method further includes:

[0042] Perform a validity check on one of N tags.

[0043] Optionally, if the validity of one of the N tags has already been verified, the first device will not verify the validity of the other tags.

[0044] Based on the above technical solution, the security of the inventory process is guaranteed. Furthermore, when M tags correspond to the first identifier, if any one of the M tags passes the validity check, then all M tags can be considered to have passed the validity check. Therefore, when the first device performs validity checks on at least one of the M tags, it achieves the purpose of validating all M tags while avoiding the frequent signaling interactions that would result from validating all M tags.

[0045] In conjunction with the first aspect, in some implementations of the first aspect, the fourth information also indicates whether the first operation was successfully performed on each of the M tags.

[0046] Based on the above technical solution, it is beneficial for other devices to determine whether each of the M tags has successfully performed the first operation.

[0047] In conjunction with the first aspect, in some implementations of the first aspect, the first operation includes disabling or writing; the fourth information includes second tag information of M tags, the second tag information of the fourth tag among the M tags includes a third flag with a second value, and the second tag information of the fifth tag among the M tags includes a third flag with a third value; wherein, the third flag with a second value indicates that the first operation is to be performed on the fourth tag, and the third flag with a third value indicates that the first operation was successfully performed on the fifth tag.

[0048] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes:

[0049] Receive the eighth message, which includes the fourth identifier, which corresponds to a tag, and the eighth message indicates that the second operation should be performed for the fourth identifier;

[0050] Send the ninth message to the tag corresponding to the fourth identifier. The ninth message indicates that the second operation should be performed on the tag corresponding to the fourth identifier.

[0051] Receive the tenth information from the tag corresponding to the fourth identifier. The tenth information indicates whether the second operation was successfully performed on the tag corresponding to the fourth identifier.

[0052] Send the eleventh message, which indicates whether the second operation was successfully performed against the fourth identifier.

[0053] For example, the fourth identifier corresponds to a predefined label.

[0054] Based on the above technical solution, it is beneficial for enterprises or operators to customize the number of tags corresponding to the identifier according to different needs.

[0055] Secondly, a communication method is provided, which can be executed by a second device. The second device can be replaced by a data management network element or a component of a data management network element (e.g., a chip, chip system, circuit, or communication module), or it can be replaced by an application function or a component of an application function (e.g., a chip, chip system, circuit, or communication module). For ease of understanding, the following description uses execution by a second device as an example. In this case, the second device can also be referred to as a communication device.

[0056] For example, the method includes:

[0057] Receive the twelfth message, which includes a first identifier, which corresponds to M tags, and the twelfth message indicates that a first operation should be performed on the first identifier; M≥2, where M is an integer;

[0058] Send a first message, the first message including a first identifier, the first message indicating to perform a first operation for the first identifier;

[0059] Receive a fourth message indicating that the first operation was successfully performed against the first identifier.

[0060] Based on the above technical solution, by mapping M tags to a first identifier, the devices can interact to instruct each other to perform a first operation on the first identifier, thereby avoiding frequent interaction between the devices to instruct each of the M tags to perform a first operation on each of the M tags.

[0061] For example, M tags correspond to the first terminal; or, M tags correspond to P terminals, and any two tags among the M tags are of the same type, where P is an integer greater than 1.

[0062] Here, the first terminal refers to a single terminal.

[0063] For example, the first identifier is determined based on the identifiers of one or more of the M tags, and the tag identifiers include one or more of the following: tag identifier, electronic product code, or user identifier.

[0064] In conjunction with the second aspect, in some implementations of the second aspect, the fourth information also indicates whether the first operation was successfully performed on each of the M tags.

[0065] Based on the above technical solution, it is beneficial for the second device to determine whether each of the M tags has successfully performed the first operation.

[0066] In conjunction with the second aspect, in some implementations of the second aspect, the first operation includes disabling or writing, the fourth information includes the second tag information of M tags, the second tag information of the fourth tag among the M tags includes a third flag with a value of a second value, and the second tag information of the fifth tag among the M tags includes a third flag with a value of a third value; wherein, the third flag with a value of a second value indicates that the first operation is to be performed on the fourth tag, and the third flag with a value of a third value indicates that the first operation was successfully performed on the fifth tag.

[0067] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes:

[0068] Send the thirteenth message, which indicates that the first operation was successfully performed against the first identifier.

[0069] In conjunction with the second aspect, in some implementations of the second aspect, before receiving the fourth information, the method further includes:

[0070] Send the seventh message;

[0071] The seventh piece of information includes a first identifier and the first tag information of M tags, wherein the first tag information of any one of the M tags is used to determine the tag; or,

[0072] The seventh piece of information includes the correspondence between the M tags and the first identifier, and the correspondence is used to determine the M tags.

[0073] Based on the above technical solution, the first device can obtain the first tag information of the M tags corresponding to the first identifier, or obtain the correspondence between the first identifier and the M tags, which is conducive to the first device determining the M tags. Then, after the first device receives the first information, it is conducive to the first device sending instructions to the M tags to perform the first operation.

[0074] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes, before receiving the twelfth message:

[0075] Receive the fourteenth message, which indicates the determination of the first identifier;

[0076] Identify and save the first identifier.

[0077] Based on the above technical solution, the second device can determine the first identifier based on the fourteenth information, and the first identifier corresponds to multiple tags. Then, different network elements can interact to instruct each other to perform the first operation on the multiple tags corresponding to the first identifier, thereby avoiding frequent interaction between different network elements to instruct each tag to perform the first operation.

[0078] For example, the fourteenth information also indicates how the first identifier is determined based on the identifier of one or more of the M tags.

[0079] In conjunction with the second aspect, in certain implementations of the second aspect, the first identifier is stored, including:

[0080] Store the association between the first identifier and the M tags; or,

[0081] Store the first identifier in the contract information of each of the M tags.

[0082] Thirdly, a communication device is provided. This communication device may include functional modules corresponding to the methods / operations / steps / actions described in any possible implementation of the first aspect, or may include functional modules corresponding to the methods / operations / steps / actions described in any aspect of the second aspect. The module may be a hardware circuit, software, or a combination of hardware circuitry and software implementation.

[0083] In one design, the communication device may include a processing module and a communication module. The communication module is used to perform the sending and receiving actions performed by the first device in the method described in the first aspect above, while the processing module is used to perform processing-related actions performed by the first device in the method described in the first aspect above.

[0084] In one design, the communication device can be a tag management function entity, or a device, module, circuit, or chip configured in the tag management function entity, or a device that can be used in conjunction with the tag management function entity, such as an intelligent network element with a radio access network (RAN) intelligent controller (RIC), an over-the-top (OTT) server, or a cloud server.

[0085] In one design, the communication device may include a processing module and a communication module. The communication module is used to perform the sending and receiving actions performed by the second device in the method described in the second aspect above, while the processing module is used to perform processing-related actions performed by the second device in the method described in the second aspect above.

[0086] In one design, the communication device can be a data management network element or application function, or it can be a device, module, circuit or chip configured in the data management network element or application function, or a device that can be used in conjunction with the data management network element or application function, such as a smart network element, an OTT server or a cloud server.

[0087] Fourthly, a communication device is provided, including a processor and a storage medium storing instructions that, when executed by the processor, cause a method as described in the first aspect or any possible implementation thereof to be implemented, or cause a method as described in the second aspect or any possible implementation thereof to be implemented.

[0088] Fifthly, a communication apparatus is provided, including a processing circuit for processing data and / or information to enable the implementation of a method as described in the first aspect or any possible implementation thereof, or to enable the implementation of a method as described in the second aspect or any possible implementation thereof.

[0089] The processing circuit may include one or more processors, or all or part of the circuitry in one or more processors used for control or processing functions.

[0090] Optionally, the communication device may further include a memory for storing programs or instructions, and the processor for running the programs or instructions to implement the methods as described in the first aspect or any possible implementation thereof, or to implement the methods as described in the second aspect or any possible implementation thereof.

[0091] Optionally, the communication device may further include the transceiver circuit, or an input / output interface.

[0092] In a sixth aspect, a chip is provided, including processing circuitry for running a program or instructions to cause the method as described in the first aspect or any possible implementation thereof to be implemented, or to cause the method as described in the second aspect or any possible implementation thereof to be implemented.

[0093] Optionally, the chip may further include a memory for storing programs or instructions.

[0094] Optionally, the chip may also include transceiver circuitry, or input / output interfaces.

[0095] A seventh aspect provides a computer-readable storage medium. The computer-readable storage medium is included in a communication device, the computer-readable storage medium including instructions that, when executed by a processor, cause a method as described in the first aspect or any possible implementation thereof to be implemented, or cause a method as described in the second aspect or any possible implementation thereof to be implemented.

[0096] Eighthly, a computer program product is provided. The computer program product includes computer program code or instructions that, when executed on a communication device, cause the methods of the first aspect and any possible implementation thereof to be implemented, or cause the methods of the second aspect and any possible implementation thereof to be implemented.

[0097] Ninth aspect, a communication system is provided, the communication system including means for performing the first aspect and any possible implementation thereof, or including means for performing the second aspect and any possible implementation thereof.

[0098] It should be understood that the third to ninth aspects of this application correspond to the technical solutions of the first to second aspects of this application, and the beneficial effects obtained by each aspect and the corresponding feasible implementation are similar, and will not be repeated here. Attached Figure Description

[0099] Figure 1 is a schematic diagram of a communication system applicable to the communication method of this application embodiment;

[0100] Figure 2 is a schematic flowchart of the communication method provided in an embodiment of this application;

[0101] Figure 3 is a schematic flowchart of the communication method provided in an embodiment of this application;

[0102] Figure 4 is a schematic flowchart of the communication method provided in an embodiment of this application;

[0103] Figure 5 is a schematic flowchart of the communication method provided in an embodiment of this application;

[0104] Figure 6 is a schematic flowchart of the communication method provided in an embodiment of this application;

[0105] Figure 7 is a schematic flowchart of the communication method provided in an embodiment of this application;

[0106] Figure 8 is a schematic block diagram of a communication device provided in an embodiment of this application;

[0107] Figure 9 is another schematic block diagram of the communication device provided in the embodiments of this application. Detailed Implementation

[0108] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0109] The technical solutions provided in this application can be applied to various communication systems, such as: 5th generation (5G) or new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, wireless local area network (WLAN) systems, satellite communication systems, future communication systems, or integrated systems of multiple systems. The technical solutions provided in this application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and Internet of Things (IoT) communication systems or other communication systems.

[0110] The technical solutions provided in this application can also be applied to non-terrestrial network (NTN) systems such as inter-satellite communication and satellite communication. As an example, a satellite communication system includes a satellite base station and terminal equipment. The satellite base station provides communication services to the terminal equipment. The satellite base station can also communicate with other base stations. A satellite can act as a base station or as a terminal device. Here, "satellite" can refer to unmanned aerial vehicles (UAVs), hot air balloons, low-Earth orbit (LEO) satellites, medium-Earth orbit (MEO) satellites, high-Earth orbit (HEO) satellites, etc. "Satellite" can also refer to non-terrestrial base stations or non-terrestrial equipment, etc.

[0111] In a communication system, a device can send signals to or receive signals from another device. These signals can include information, signaling, or data. The device can also be replaced by an entity, network entity, communication device, mobile device, network element, communication module, node, communication node, communication apparatus, etc. This disclosure uses a device as an example. For instance, a communication system can include at least one terminal device and at least one network device. The network device can send downlink signals to the terminal device, and / or the terminal device can send uplink signals to the network device. It is understood that the terminal device in this disclosure can be replaced by a first communication device, and the network device can be replaced by a second communication device, both performing the corresponding communication methods described in this disclosure. Alternatively, the corresponding communication methods in this disclosure can be applied between network devices or between terminal devices, without limitation herein.

[0112] The network device in this application embodiment can be a device or module with corresponding communication functions. The network device can be a device used to communicate with terminal devices; it can also be called an access network device or a wireless access network device, such as a base station. In this application embodiment, the network device can refer to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitter point, master station, auxiliary station, motor slide retainer (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or a combination thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center, a device that performs base station functions in D2D, V2X, and M2M communications, or a device that performs base station functions in future communication systems. A base station can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.

[0113] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0114] In some deployments, the network devices mentioned in the embodiments of this application may be devices including CU, DU, or CU and DU, or devices with control plane CU nodes (central unit-control plane (CU-CP)) and user plane CU nodes (central unit-user plane (CU-UP)) and DU nodes. For example, the network devices may include gNB-CU-CP, gNB-CU-UP, and gNB-DU.

[0115] In some deployments, multiple RAN nodes collaborate to assist terminals in achieving wireless access, with different RAN nodes each implementing some of the base station's functions. For example, RAN nodes can be CUs, DUs, CU-CPs, CU-UPs, or RUs. CUs and DUs can be configured separately or included in the same network element, such as a BBU. RUs can be included in radio frequency equipment or radio frequency units, such as RRUs, AAUs, or RRHs.

[0116] In some deployments, the CU (Core Unit) is a logical node that carries the Radio Resource Control (RRC) layer, Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, and other control functions of the access network equipment. The CU connects to network nodes such as the core network through interfaces, which may be E2 interfaces, etc. Optionally, the CU possesses some core network functions. The CU (e.g., the PDCP layer and higher layers) connects to the DU (e.g., the Radio Link Control (RLC) layer and lower layers) through interfaces, which may be F1 interfaces, etc. In some examples, these interfaces (e.g., the F1 interface) can provide control plane (C-Plane) and user plane (U-Plane) functions (e.g., interface management, system information management, UE context management, RRC message transmission, etc.). The F1 application protocol (F1AP) is the application protocol for the F1 interface, and in some examples, it defines the F1 signaling procedures. The F1 interface supports both the control plane (F1-C) and the user plane (F1-U).

[0117] In some deployments, the CU can be split into CU-CP and CU-UP. CU-CP is a logical node carrying the RRC layer and the control plane part of PDCP (PDCP-C) layer, used to implement the CU's control plane functions. CU-CP can interact with network elements in the core network used to implement control plane functions. These network elements in the core network can be access and mobility function network elements. CU-UP is a logical node carrying the SDAP layer and the user plane part of PDCP (PDCP-U) layer, used to implement the CU's user plane functions. CU-UP can interact with network elements in the core network used to implement user plane functions. The above CU and DU configurations are merely examples; the functions of CU and DU can be configured as needed. For example, CU or DU can be configured to have more protocol layer functions, or CU or DU can be configured to have only partial protocol layer processing functions. For example, some functions of the RLC layer and the functions of the protocol layer above the RLC layer can be placed in the CU, while the remaining functions of the RLC layer and the functions of the protocol layer below the RLC layer can be placed in the DU. Another example is that the functions of the CU or DU can be divided according to service type or other system requirements. For instance, based on latency, functions that need to meet low latency requirements can be placed in the DU, while functions that do not need to meet such latency requirements can be placed in the CU.

[0118] In some deployments, the DU (Distributed Unit) is a logical node that carries the RLC (Real-Time Control) layer, the medium access control (MAC) layer, the higher physical layer (Higher PHY) layer, and other functions. In some examples, the DU can control at least one RU (Remote Root). The DU connects to the RU through interfaces, which can be fronthaul interfaces. In some examples, the Higher PHY layer includes the PHY layer processing, such as forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation.

[0119] In some deployments, the RU is a logical node that carries both lower physical layer (PHY) and radio frequency (RF) processing. In some examples, the RU can be a TRP, RRH, or other similar entity. In some examples, the Low-PHY includes portions of the PHY processing, such as Fast Fourier Transform (FFT), Inverse Fast Fourier Transform (IFFT), digital beamforming, and filtering. The RU communicates with one or more UEs via a radio link.

[0120] The DU and RU can be co-located or not. The DU and RU exchange control plane and user plane information via a fronthaul link through a lower-layer split-control, user, and synchronization (LLS-CUS) interface. LLS-CUS may include interfaces providing control and user planes respectively. In some examples, the control plane refers to real-time control between the DU and RU. The DU and RU exchange management information via a fronthaul link interface (such as an LLS-M interface), and the management plane (M-Plane) refers to non-real-time management operations between the DU and RU.

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

[0122] In one possible design, the processing unit in the BBU used to implement baseband functions is called the baseband high (BBH) unit, and the processing unit in the RRU / AAU / RRH used to implement baseband functions is called the baseband low (BBL) unit.

[0123] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, a radio access network can also be an open radio access network (O-RAN) architecture. In an O-RAN system, CU can also be called an open CU (open CU, O-CU), DU can also be called an open DU (open DU, O-DU), CU-CP can also be called an open CU-CP (O-CU-CP), CU-UP can also be called an open CU-UP (O-CU-UP), and RU can also be called an open RU (open RU, O-RU). Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.

[0124] In this embodiment, the device for implementing the functions of a network device can be a network device itself, or a device capable of supporting the network device in implementing those functions, such as a chip system, chip, circuit, or communication module (i.e., a communication module that performs communication functions). This communication device can be installed within the network device. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices. Furthermore, the communication device can be configured with program instructions for performing corresponding communication functions. This embodiment only uses a network device as an example to illustrate the device for implementing the functions of a network device, and does not limit the solution of this embodiment.

[0125] Network devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network device is located. Furthermore, a network device can be a hardware device, or a software function running on dedicated hardware, or a software function running on general-purpose hardware, such as a virtualization function instantiated on a platform (e.g., a cloud platform), or an entity that includes dedicated or general-purpose hardware devices and software functions. This application does not limit the specific form of the terminal device or network device.

[0126] First, a brief introduction to the communication system applicable to the embodiments of this application is given below.

[0127] Figure 1 is a schematic diagram of a communication system 100 applicable to this application. As shown in Figure 1, the communication system 100 includes one or more of the following: a tag, an access network device (RAN), a tag management function (TMF) entity, a unified data management (UDM) network element, an application function (AF), and an operator's business and operation support system (BOSS). Optionally, the communication system 100 also includes a network exposure function (NEF).

[0128] The following describes each network element involved in Figure 1.

[0129] 1. Tag: A tag is also known as a transponder, electronic tag, radio frequency identification (RFID) tag, radio frequency tag, transponder, data carrier, recording medium, RFID card, AIoT device, AIoT terminal, IoT device, IoT terminal, etc. For ease of description, this application will uniformly refer to it as a tag. Each tag has a unique electronic code, such as a tag identifier (TID), and each tag also has an electronic product code (EPC). Tags can be attached to objects or devices to identify target objects.

[0130] The tag's storage area can be divided into a reserved storage area, an EPC storage area, a TID storage area, and a user storage area. The reserved storage area is mainly used to store kill passwords, access passwords, etc. The EPC storage area is mainly used to store the tag's EPC information. The TID storage area is mainly used to store the tag's TID. The user storage area is mainly used to store user-defined data.

[0131] Tags can include: active tags (also known as C-type tags), semi-active tags (also known as B-type tags), and passive tags (also known as A-type tags).

[0132] Active tags, also known as active tags, are powered by an internal battery. The battery's energy can also be converted into radio frequency energy required for communication between the tag and the reader.

[0133] Semi-passive tags are tags that have batteries but do not actively transmit radio frequency signals; they receive and respond to radio frequency signals from readers.

[0134] Passive tags, also known as passive tags, do not have an internal battery. When the tag is outside the reader's reading range, it is in a passive state. When the tag is within the reader's reading range, it extracts the energy required for its operation from the radio frequency energy emitted by the reader.

[0135] 2. The access network device has the capability to inventory tags, and can conduct inventory checks on tags in the passive Internet of Things (IoT) after stimulating them using air interface wireless technology. The access network device can be a device used to communicate with terminals (as shown in Figure 1), or it can be a device that connects terminals to a wireless network. For more details on the access network device, please refer to the description of network devices above.

[0136] The embodiments of this application do not limit the specific technologies, equipment forms, or names used in the access network equipment.

[0137] 3. The TMF is responsible for tag management. The TMF can be an independent network element. The TMF can also be co-located with other network elements, such as with the Access and Mobility Management Function (AMF) as shown in Figure 1. The TMF can also be a function possessed by other network elements, or it can be understood as an improvement to other network elements to enable them to perform the functions handled by the TMF. For example, improving the AMF to enable it to perform TMF functions means that the AMF can possess the functions of managing user registration, reachability detection, session management function (SMF) node selection, and mobility state transition management, while also having the functions of the TMF.

[0138] Optionally, TMF can be replaced with one of the following: ambient IoT management function (AIoTMF), ambient IoT function (AIoTF), AIoT aware core network (AIoT aware CN), or other core network elements / nodes / devices that support or enable AIoT.

[0139] 4. AF primarily supports interaction with the 3GPP core network to provide services, such as influencing data routing decisions, policy control functions, or providing third-party services to the network. AF can be an AF deployed within the operator's network itself, or it can be a third-party AF.

[0140] 5. NEF is primarily used to securely open services and capabilities provided by 3GPP network functions, supporting secure interaction between 3GPP networks and third-party applications.

[0141] 6. UDM is used to generate 3GPP authentication and key agreement (AKA) authentication certificates, process user IDs, and uniformly manage data related to functions such as access authorization based on subscription information, service network function (NF) registration management, and subscription information management.

[0142] 7. BOSS is a crucial software platform supporting operators in network operation, management, and maintenance. BOSS undertakes important functions such as billing, customer management, data collection and analysis, marketing decision-making, and network operation and maintenance. Through billing and authentication for different services and customers, maintaining customer relationships, mining marketing strategies, and monitoring and managing the quality of basic network operation, BOSS provides operators with comprehensive network operation and management support.

[0143] It should be understood that in the network architecture shown in Figure 1, the network elements can communicate with each other through interfaces. The interfaces between the network elements can be point-to-point interfaces or service-oriented interfaces, and this application does not impose any restrictions.

[0144] It should be understood that the network architecture shown above is merely an illustrative example, and the network architecture applicable to the embodiments of this application is not limited thereto. Any network architecture capable of realizing the functions of the above-described network elements is applicable to the embodiments of this application.

[0145] It should also be understood that the AMF, TMF, NEF, AF, and other functions or network elements shown in Figure 1 can be understood as network elements used to implement different functions, such as network slices that can be combined as needed. These network elements can be independent devices or integrated into the same device to implement different functions. They can also be network components in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (e.g., a cloud platform). This application does not limit the specific form of the above-mentioned network elements.

[0146] It should also be understood that the above naming is defined only for the convenience of distinguishing different functions and should not constitute any limitation on this application. This application does not preclude the possibility of using other names in other networks.

[0147] With technological advancements and environmental regulations, the Internet of Things (IoT) will have a much larger application deployment prospect, predicted to cover hundreds of billions of devices in the future. Based on this, the number of tags in the network will increase significantly. If readers and each tag perform one or more processes such as reading, writing, inventorying, or disabling, and simultaneously require tags to respond to the reader's operation requests in real time, this will lead to excessive signaling interactions on the network side.

[0148] In view of this, embodiments of this application provide a communication method and apparatus, which defines an identifier corresponding to multiple tags, and when a read, write, inventory or disable process is triggered on the network side, the newly defined identifier indexes multiple tags, thereby helping to reduce signaling interaction on the network side.

[0149] Before introducing the scheme of this application, the following points should be noted.

[0150] (1) In this application, “instruction” may include direct instruction, indirect instruction, explicit instruction, and implicit instruction. When describing a certain instruction information for the purpose of instructing A, it can be understood that the instruction information carries A, directly instructs A, or indirectly instructs A.

[0151] In this application, the information indicated by the instruction information is called the information to be instructed. In specific implementations, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly indicate the information to be instructed by indicating other information, where there is a relationship between the other information and the information to be instructed. It can also indicate only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent. Furthermore, the information to be instructed can be sent as a whole or divided into multiple sub-information pieces, and the sending period and / or timing of these sub-information pieces can be the same or different.

[0152] (2) In this application, "send" and "receive" indicate the direction of signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, which may include direct transmission via the air interface or indirect transmission via the air interface by other units or modules. "Receive information from YY" can be understood as the source of the information being YY, which may include direct reception from YY via the air interface or indirect reception from YY via the air interface by other units or modules. "Send" can also be understood as the "output" of the chip interface, and "receive" can also be understood as the "input" of the chip interface. In other words, sending and receiving can occur between devices, such as between network devices and terminal devices, or within a device, such as between components, modules, chips, software modules, or hardware modules within the device via a bus, wiring, or interface.

[0153] (3) In the various embodiments of this application, unless otherwise specified or logically conflicting, the terms and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0154] (4) In this application, "first" and "second" are used for descriptive convenience only to distinguish objects and are not intended to limit the scope of the embodiments of this application. They are not used to describe the order or sequence of features. It should be understood that the objects described in this way can be interchanged where appropriate so as to describe solutions other than those in the embodiments of this application.

[0155] (5) In this application, “predefined” may mean a standard protocol predefined, or it may mean that the devices have agreed or negotiated in advance.

[0156] (6) In this application, the words “exemplary,” “for example,” etc., are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as an “example” in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the word “example” is intended to present the concept in a concrete manner. In the embodiments of this application, “of,” “corresponding, relevant,” and “corresponding” may sometimes be used interchangeably, and it should be noted that their intended meanings are consistent unless their distinction is emphasized.

[0157] (7) In this document, "at least one" means one or more. "More than one" means two or more. "And / or" describes the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates that the related objects before and after are in an "or" relationship; in the formula of this application, the character " / " indicates that the related objects before and after are in a "division" relationship. "Including at least one of A, B and 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.

[0158] The method provided by the embodiments of this application will be described in detail below with reference to the accompanying drawings. The embodiments provided by this application can be applied to the communication system shown in FIG2 above, and are not limited thereto.

[0159] It should be noted that the following description uses the interaction between the first device, the second device, and the third device as an example to illustrate the method provided in this application embodiment. The first device can be replaced by a tag management function entity or a component of a tag management function entity (e.g., a chip, a chip system, a circuit, or a communication module). The tag management network element can be replaced by one of the following: AIoTMF, AIoTF, AIoT aware CN, or other core network elements / nodes / devices that support or enable AIoT. The second device can be replaced by a data management network element (e.g., the UDM mentioned above) or a component of a data management network element (e.g., a chip, a chip system, a circuit, or a communication module), or the second device can be replaced by an application function (e.g., the AF mentioned above) or a component of an application function (e.g., a chip, a chip system, a circuit, or a communication module). The third device can be replaced by a network development function (such as the NEF mentioned above) or a component of the network development function (such as a chip, chip system, circuit, or communication module). Alternatively, the third device can be replaced by an operator's business operation support system (such as the BOSS mentioned above) or a component of the operator's business operation support system (such as a chip, chip system, circuit, or communication module).

[0160] Furthermore, the steps described below as being performed by a single execution entity can also be divided into being performed by multiple execution entities, which may be logically and / or physically separate.

[0161] Figure 2 is a schematic diagram of a communication method 200 provided in an embodiment of this application. As shown in Figure 2, method 200 may include the following steps.

[0162] S201, the third device registers the first identifier in the second device.

[0163] A detailed description of the third device registering the first identifier in the second device can be found in method 300 below, but for the sake of brevity, it will not be described in detail here.

[0164] S202, the second device sends the seventh message.

[0165] Correspondingly, the first device receives the seventh message.

[0166] In one possible implementation, the seventh information includes a first identifier and first tag information for M tags, where the first tag information of any one of the M tags is used to determine the tag. Here, M ≥ 2, and M is a positive integer.

[0167] For example, the first identifier in this application embodiment can be replaced with a logical label, and the M labels in this application embodiment can be replaced with M physical labels.

[0168] The first tag information of a tag may include one or more of the following: the tag's identifier or a second flag with a first value. The tag's identifier may include one or more of the following: TID, EPC, or User ID. The second flag with a first value indicates that the tag has successfully performed a write operation. For example, if the first tag information of any tag #a among M tags includes a second flag with a first value, then tag #a can be called the first tag.

[0169] The first identifier corresponds to M tags. It should be understood that when the first device receives the first identifier and the first tag information of the M tags, the first device can determine the M tags based on the first tag information of the M tags, and determine that the first identifier corresponds to the M tags.

[0170] For example, M tags correspond to the first terminal. It should be understood that the first terminal refers to a single terminal.

[0171] For example, there are M tags to P terminals, and any two tags among the M tags are of the same type. P is an integer greater than 1.

[0172] This application does not limit the correspondence between the M tags and the first identifier. For example, the first identifier is determined based on the identifiers of one or more of the M tags. As another example, the first identifier can be a randomly generated random number corresponding to the M tags.

[0173] For example, the correspondence between the M tags and the first identifier is predefined by the enterprise or operator. In other words, the correspondence between the first identifier and the M tags is defined by the enterprise or operator.

[0174] This application does not limit the method of determining the first identifier based on the identification of one or more of the M tags.

[0175] For example, if the Xth to Yth bits of the EPC of any two tags out of the M tags are the same, then the first identifier can be determined based on the X1th to Y1th bits of the EPC of any one of the M tags. Here, X1≥X, Y1≤Y, and X, Y, X1, and Y1 are all integers greater than or equal to 0.

[0176] For example, the first identifier can be composed of the identifiers of M tags, or the first identifier can be composed of the Zth bit of the identifier of each of the M tags, where Z is an integer greater than or equal to 0.

[0177] In one possible implementation, the seventh information includes the correspondence between the first identifier and the M tags, which is used to determine the M tags.

[0178] It should be understood that when the first device receives the seventh information, if the first device has stored the subscription information of at least one tag, then the first device can determine the M tags based on the subscription information of at least one tag and the correspondence between the first identifier and the M tags. For example, if the correspondence between the first identifier and the M tags indicates that the X1 to Y1 bits of the EPC of each of the M tags can form the first identifier, then the first device determines that the X1 to Y1 bits of the EPC of any two tags among the M tags are the same, and the first identifier is composed of the X1 to Y1 bits of the EPC of any one of the M tags. Furthermore, the first device can, based on the stored subscription information of at least one tag, determine the tags with the same X1 to Y1 bits of the EPC among the at least one tag as the M tags, and determine the first identifier as the X1 to Y1 bits of the EPC of any one of the M tags.

[0179] For example, the tag's contract information may include the tag's identifier, such as one or more of TID, EPC, or User ID.

[0180] For example, the correspondence between the first identifier and the M tags can be replaced by a method of determining the first identifier based on the M tags, or by a rule for creating the first identifier, or by a rule for creating logical tags, or by a mapping rule between logical tags and the M physical tags.

[0181] Optionally, the seventh information also includes a second identifier, which corresponds to a plurality of third identifiers, each of the plurality of third identifiers corresponding to at least one tag, and the plurality of third identifiers including the first identifier.

[0182] Optionally, if the third identifiers corresponding to the second identifier include identifier #a in addition to the first identifier, and the second device is used to provide services for at least one tag corresponding to identifier #a, in other words, the second device can communicate with at least one tag corresponding to identifier #a, then the seventh information may also include the first tag information of identifier #a and at least one tag corresponding to identifier #a, or include the correspondence between identifier #a and at least one tag corresponding to identifier #a.

[0183] Optionally, if the multiple third identifiers corresponding to the second identifier also include the aforementioned identifier #a, then method 200 further includes: the second device sending information #a to the first device, wherein information #a includes the second identifier, identifier #a, and first tag information of at least one tag corresponding to identifier #a; or, information #a includes the second identifier and a correspondence between identifier #a and at least one tag corresponding to identifier #a. The second device may simultaneously send the seventh information and information #a to the first device, or send the seventh information to the first device first, and then send information #a to the first device, or send information #a to the first device first, and then send the seventh information to the first device.

[0184] It should be noted that step S202 is optional. For example, after the third device registers the first identifier with the second device, if the second device determines that the M tags corresponding to the first identifier have not been registered with the first device, then method 200 may not execute step S202. As another example, if the first device has not subscribed to the change notifications of the subscription information for the M tags, then method 200 may not execute step S202.

[0185] Furthermore, method 200 includes the step of the first device receiving first information. For example, if the first device receives first information from a third device, then method 200 continues to execute S203a. Also for example, if the first device receives first information from a second device, then method 200 continues to execute S203b1 and S203b3.

[0186] S203a, the third device sends the first information.

[0187] Accordingly, the first device receives the first information.

[0188] The first information includes the first identifier, and further description of the first identifier can be found in S202 above.

[0189] The first information indicates that a first operation should be performed on the first identifier. For example, the first operation may be disable, inventory, read, or write. For instance, the first information may include a 2-bit field #1. If the value of field #1 is "00", it indicates that the first information indicates that an inventory should be performed on the first identifier; if the value of field #1 is "01", it indicates that the first information indicates that an inventory should be performed on the first identifier; if the value of field #1 is "10", it indicates that the first information indicates that a read should be performed on the first identifier; and if the value of field #1 is "11", it indicates that the first information indicates that a write should be performed on the first identifier.

[0190] Optionally, the first information may also indicate a first condition, which is used by the first device to determine whether the first operation was successfully performed for the first identifier.

[0191] For example, the first condition includes one or more of the following: the number of tags that successfully performed the first operation among the M tags is not less than a first threshold (hereinafter referred to as condition #1); the ratio between the number of tags that successfully performed the first operation among the M tags and M is not less than a second threshold; the number of tags that successfully performed the first operation among the M tags is equal to M (hereinafter referred to as condition #2); the ratio between the number of tags that successfully performed the first operation among the M tags in the first time period and M is not less than a third threshold.

[0192] Wherein, one or more of the first threshold, second threshold, third threshold, or first time period are predefined or preconfigured, or are indicated by the third device to the first device, this application does not limit this. For example, one or more of the first threshold, second threshold, third threshold, or first time period may be predefined or preconfigured by an enterprise or operator.

[0193] For example, if the first operation is inventory counting, and M tags correspond to the first terminal, then the first condition can include the aforementioned condition #1, and the first threshold is 1. As another example, if the first operation is inventory counting for location purposes, then the first condition can include the aforementioned condition #2.

[0194] Optionally, if the third device does not register the first identifier in the second device, the first information further includes information #1, which includes the first identifier and first tag information of M tags, or information #1 includes the correspondence between the first identifier and the M tags. Further description of information #1 can be found in the description of the seventh information in S202 above.

[0195] Optionally, the first information also includes information for permission checking, which is used by the first device to determine whether the third device has permission to instruct the third device to perform the first operation on the first identifier. For example, the information for permission checking may include information about the third device. Accordingly, the first device can determine whether the third device has permission to instruct the third device to perform the first operation on the first identifier based on the information about the third device.

[0196] In one possible implementation, the first identifier included in the first information can be replaced with the second identifier mentioned in S202 above.

[0197] It should be understood that if the first information includes the second identifier, then method 200 further includes: the first device determining at least one of a plurality of third identifiers corresponding to the second identifier.

[0198] For example, if method 200 executes S202, and the seventh information includes at least one third identifier from a plurality of third identifiers corresponding to the second identifier, then the first device can determine at least one third identifier from the plurality of third identifiers corresponding to the second identifier based on the seventh information. It should be understood that the first device can provide services for tags corresponding to each of the at least one third identifier. For example, if the at least one third identifier includes the first identifier and the identifier #a mentioned in S202 above, then the first device can provide services for M tags and at least one tag corresponding to identifier #a.

[0199] For example, if method 200 does not execute S202, the first device can obtain at least one of the plurality of third identifiers corresponding to the second identifier through S205 to S206 mentioned below.

[0200] For example, the first information sent by the third device is a message.

[0201] Optionally, after S203a1, method 200 further includes: the first device sending response information #1 to the third device. Response information #1 indicates that the first device has received the first information.

[0202] S203b1, the third device sends the twelfth message.

[0203] Correspondingly, the second device receives the twelfth message.

[0204] The twelfth information includes a first identifier, which indicates that a first operation should be performed on the first identifier. For example, the twelfth information may include a 2-bit field #2. Different values ​​of field #2 indicate different first operations to be performed on the first identifier. For more details on field #2, please refer to the description of field #1 in S203a.

[0205] Optionally, the twelfth message also indicates the first condition. Further description of the first condition can be found in the description in S203a above.

[0206] Optionally, if the third device does not register the first identifier in the second device, the twelfth information may also include information #1, which includes the first identifier and the first tag information of M tags, or information #1 includes the correspondence between the first identifier and the M tags. Further description of information #1 can be found in the description of the seventh information in S202 above.

[0207] Optionally, the twelfth piece of information also includes information for permission checking, which is used by the second device to determine whether the third device has permission to instruct the third device to perform the first operation on the first identifier. For example, the information for permission checking may include information about the third device. Accordingly, the second device can determine whether the third device has permission to instruct the third device to perform the first operation on the first identifier based on the information about the third device.

[0208] In one possible implementation, the first identifier included in the twelfth information can be replaced with the second identifier mentioned in S202 above.

[0209] For example, the twelfth message sent by the third device is a message.

[0210] Optionally, after S203b1, method 200 further includes: the second device sending response information #2 to the third device. Response information #2 indicates that the second device has received the twelfth information.

[0211] Optionally, if the first identifier included in the first information is replaced by a second identifier, and the second identifier corresponds to multiple third identifiers, then the response information #2 indicates whether the second device has received an instruction instructing each of the multiple third identifiers to perform a first operation. For example, if the second identifier corresponds to third identifier #1 and third identifier #2, then the response information #2 indicates whether the second device has received an instruction instructing the first operation to be performed for third identifier #1, and / or indicates whether the second device has received an instruction instructing the first operation to be performed for third identifier #2.

[0212] Optionally, if response information #2 indicates whether the second device has received an instruction to perform the first operation on the third identifier, the second device may, if it is determined that the third device has the authority to perform the first operation on the third identifier, indicate through response information #2 that the second device has received an instruction to perform the first operation on the third identifier; or, if it is determined that the third device does not have the authority to perform the first operation on the third identifier, the second device may, through response information #2, indicate that the second device has not received an instruction to perform the first operation on the third identifier.

[0213] Optionally, if the first information includes a second identifier, then method 200 further includes: the second device determining a plurality of third identifiers corresponding to the second identifier. It should be understood that if method 200 executes S201, and in S201, the third device registers the second identifier, a plurality of third identifiers, and the correspondence between the second identifier and the plurality of third identifiers with the second device, then the second device can determine the plurality of third identifiers corresponding to the second identifier.

[0214] Optionally, if the second device determines a plurality of third identifiers corresponding to the second identifier, then method 200 further includes S203b2.

[0215] S203b2, set the value of flag #a to #a1.

[0216] The flag #a corresponds to the first identifier. A flag #a with a value of #a1 indicates that a first operation is to be performed on the first identifier. The second device setting the flag #a to a value of #a1 is equivalent to the second device setting a flag for the first identifier to be used for the first operation. For example, if the first operation is to disable, it is equivalent to the second device setting a flag for the first identifier to be disabled; that is, a flag #a with a value of #a1 can be called a flag to be disabled. As another example, if the first operation is to write, it is equivalent to the second device setting a flag for the first identifier to be written; that is, a flag #a with a value of #a1 can be called a flag to be written.

[0217] Optionally, the flag #a, which takes the value #a1, is stored in the non-volatile memory area corresponding to the second device.

[0218] Optionally, if the second device determines that the third device has the authority to instruct the first operation to be performed against the first identifier, it executes S203b2.

[0219] Optionally, in S203b2, the second device may also set a flag for performing the first operation for other flags among a plurality of third flags.

[0220] It should be noted that S203b2 is an optional step. For example, if the first operation includes writing or disabling, then method 200 may execute S203b2; if the first operation includes reading or inventory counting, then method 200 may not execute S203b2.

[0221] S203b3, the second device sends the first information.

[0222] Accordingly, the first device receives the first information.

[0223] After receiving the twelfth information from the third device, the second device can send the first information to the first device based on the twelfth information.

[0224] The first information includes a first identifier, and the first information indicates that a first operation should be performed on the first identifier.

[0225] Optionally, if the twelfth message indicates the first condition, then the first message also indicates the first condition.

[0226] Optionally, the first information may also include information #1. For example, if the twelfth information includes information #1, then the first information may include information #1. As another example, if the third device has registered the first identifier in the second device, but method 200 does not execute S202, then the first information may include information #1.

[0227] For a more detailed description of the first information, please refer to the description of the first information in S203a above.

[0228] In one possible implementation, the first identifier included in the first information can be replaced with the second identifier mentioned in S202 above.

[0229] It should be understood that if the first information includes the second identifier, then method 200 further includes: the first device determining at least one of a plurality of third identifiers corresponding to the second identifier. The method by which the second device determines at least one third identifier can be referred to the description in S203a above.

[0230] Optionally, after S203b2, method 200 further includes: the first device sending response information #3 to the second device. Response information #3 indicates that the second device has received the first information.

[0231] S204, set the value of flag #a to #a1.

[0232] The flag #a corresponds to the first identifier. A flag #a with a value of #a1 indicates that a first operation is to be performed on the first identifier. When the first device sets the flag #a to the value #a1, it is equivalent to the first device setting a flag for the first identifier to perform a first operation.

[0233] Optionally, the flag #a, which takes the value #a1, is stored in the context corresponding to the first identifier.

[0234] Optionally, if the first device determines that the third device has the authority to instruct the first operation to be performed against the first identifier, it executes S204.

[0235] Optionally, if the second device receives the second identifier and determines that the second identifier corresponds to at least one third identifier, in S204, the second device may also set a flag for performing the first operation for the at least one third identifier other than the first identifier.

[0236] It should be noted that step S204 is optional. For example, if the first operation includes writing or disabling, then method 200 may execute step S204; if the first operation includes reading or inventory, then method 200 may not execute step S204. As another example, if the first device has saved the context corresponding to the first identifier, then method 200 executes step S204; if the first device has not saved the context corresponding to the first identifier, then method 200 does not execute step S204.

[0237] Optionally, method 200 may also include S205 and S206.

[0238] S205, the first device sends the fifth message.

[0239] Correspondingly, the second device receives the fifth message.

[0240] In one possible implementation, the fifth information includes a first identifier, which is used to request the first tag information of the M tags corresponding to the first identifier. The first tag information can be referred to the description in S202 above.

[0241] In one possible implementation, the fifth information includes a first identifier, which is used to request the correspondence between the first identifier and the M tags. The correspondence between the first identifier and the M tags can be referred to the description in S202 above.

[0242] In one possible implementation, if the first information received by the first device includes a second identifier, then the fifth information includes the second identifier. The fifth information is used to request at least one third identifier corresponding to the second identifier, and first tag information for a tag corresponding to each of the at least one third identifier. Alternatively, the fifth information is used to request at least one third identifier corresponding to the second identifier, and the correspondence between each of the at least one third identifier and the tag corresponding to that third identifier. Wherein, the at least one third identifier includes the first identifier, and the first device is used to provide services for the tags corresponding to each of the at least one third identifier.

[0243] S206, the second device sends the sixth message.

[0244] Correspondingly, the first device receives the sixth information.

[0245] In one possible implementation, the sixth information includes the first tag information of M tags.

[0246] In one possible implementation, the sixth piece of information includes the correspondence between the first identifier and the M tags.

[0247] In one possible implementation, the sixth information includes at least one third identifier and first tag information of the tag corresponding to each of the at least one third identifier.

[0248] In one possible implementation, the sixth information includes at least one third identifier, and the correspondence between each third identifier and the corresponding tag.

[0249] Optionally, the sixth information may also include a first flag indicating that the first identifier is not disabled.

[0250] It should be understood that when the first device receives the sixth information, it can determine the M tags corresponding to the first identifier based on the sixth information. For example, the first device determines the M tags based on the first tag information of the M tags, or the first device determines the M tags based on the correspondence between the first identifier and the M tags.

[0251] It should be noted that steps S205 and S206 are optional. For example, if method 200 executes S202, then method 200 may not execute S205 or S206. As another example, if the first information received by the first device includes information #1 mentioned in S203a above, then method 200 may not execute S205 or S206.

[0252] S207, the first device sends the second information.

[0253] Correspondingly, the tag receives the second information.

[0254] For example, in S207, the first device sends second information to M1 of the M tags, the second information instructing the first operation to be performed on each of the M1 tags. Where M1 ≤ M, and M1 is an integer.

[0255] For example, the second information may include a 2-bit field #3. Different values ​​of field #3 indicate different first operations performed on the M1 tags. For more details on field #3, please refer to the description of field #1 in S203a.

[0256] In one possible implementation, if the first operation includes reading, and the first device obtains the first tag information of M tags based on the sixth and / or seventh information, then before S207, method 200 further includes: the first device determining the first tag among the M tags based on the first tag information of the M tags. The first tag information of the first tag includes a second flag with a second value; in other words, the first tag among the M tags is a tag that has successfully performed a write operation. Then, in S207, the first device sends the second information to all the first tags among the M tags; in other words, the M1 tags include all tags among the M tags that have successfully performed a write operation.

[0257] For example, in S207, the first device can send second information to M1 tags via a reader / writer. For instance, the first device sends message #1 to the reader / writer, message #1 including the second information and the identifiers of the M1 tags; correspondingly, the reader / writer identifies the M1 tags based on the identifiers of the M1 tags and sends the second information to the M1 tags.

[0258] S208, the tag sends third-party information.

[0259] Correspondingly, the first device receives the third information.

[0260] For example, in S208, each of the N tags sends a third message to the first device, the third message indicating that the first operation on the tag was successfully performed.

[0261] Among them, N labels belong to M1 labels, N≤M1, and N is an integer.

[0262] Optionally, in S208, each of the N1 tags sends a third message #a to the first device, the third message #a indicating that the first operation on the tag failed.

[0263] In this set of N1 labels, N1 belongs to M1 labels, where N1 ≤ M1 and N1 is an integer. Each of the N1 labels is different from any of the N labels.

[0264] For example, in S208, the tag can send third information or third information #a to the first device via the reader. For instance, the tag sends message #2 to the reader, message #2 including third information or third information #a; correspondingly, the reader sends third information or third information #a to the first device.

[0265] It should be understood that in S208, because the tag is not connected to the network or is not powered, the first device may not be able to receive the third information or third information #a from each of the M1 tags.

[0266] Optionally, if the first operation includes inventory counting, and after the first device receives the third information from tag #n among the N tags, if no legality verification has been performed on any of the N tags, then method 200 further includes: performing legality verification on one of the N tags (e.g., tag #n). It should be understood that if the first device has already performed legality verification on one of the N tags after receiving the third information from tag #n among the N tags, then the first device will not perform legality verification on tag #n again.

[0267] Optionally, method 200 also includes S209.

[0268] S209, set the value of flag #a to #a2.

[0269] The flag #a corresponds to the first identifier. A flag #a with a value of #a2 indicates that the first operation was successfully performed on the first identifier. The first device setting the flag #a to a value of #a2 is equivalent to the first device setting a flag indicating successful execution of the first operation on the first identifier. For example, if the first operation is disabled, it is equivalent to the first device setting a disabled flag on the first identifier; that is, a flag #a with a value of #a2 can be called a disabled flag. Similarly, if the first operation is written, it is equivalent to the first device setting a written flag on the first identifier; that is, a flag #a with a value of #a2 can be called a written flag.

[0270] Optionally, the flag #a, which takes the value #a2, is stored in the context corresponding to the first identifier.

[0271] In one possible implementation, the first device may execute S209 upon receiving at least one third piece of information.

[0272] In one possible implementation, the first device may execute S209 if the number of received third messages satisfies a first condition. It should be understood that since the third messages indicate successful execution of the first operation on the tag, the number of third messages received by the first device is equal to the number of tags out of M that successfully performed the first operation. Based on this, the first condition described in S203a above may include one or more of the following: the number of third messages is not less than a first threshold; the ratio between the number of third messages and M is not less than a second threshold; the number of third messages is equal to M; the ratio between the number of third messages received within a first time period and M is not less than a third threshold. Further description of the first condition can be found in S203a above.

[0273] Optionally, if the number of third information received by the first device does not meet the first condition, the first device may continue to wait for the tag that has not fed back the third information or the third information #a to feed back the third information or the third information #a. Alternatively, the first device may send the second information again to the tags that have not fed back the third information and the third information #a among the M tags, as well as the tags that have fed back the third information #a, until the number of third information received by the first device meets the first condition, and then the first device executes S209.

[0274] It should be noted that step S209 is optional. For example, if the first operation includes writing or disabling, then method 200 may execute S209; if the first operation includes reading or inventory, then method 200 may not execute S209. As another example, if the first device has saved the context corresponding to the first identifier, then method 200 executes S209; if the first device has not saved the context corresponding to the first identifier, then method 200 does not execute S209.

[0275] It should also be noted that if method 200 executes S205 and S206, and the sixth information received by the first device includes the first flag, then method 200 may execute S209; if the sixth information received by the first device does not include the first flag, or includes a flag indicating that the first flag has been disabled (or has been disabled), then method 200 does not execute S209.

[0276] Furthermore, method 200 includes the step of the first device sending fourth information. For example, if the first device sends fourth information to a third device, then method 200 continues to execute S210a. Also for example, if the first device sends first information to a second device, then method 200 continues to execute S210b1.

[0277] S210a, the first device sends the fourth message.

[0278] Correspondingly, the third device receives the fourth information.

[0279] S210b1, the first device sends the fourth message.

[0280] Correspondingly, the second device receives the fourth information.

[0281] The fourth message indicates that the first operation was successfully performed against the first identifier.

[0282] Optionally, the fourth information also indicates whether the first operation was successfully performed on each of the M tags.

[0283] For example, if the first operation includes disabling or writing, then the fourth information includes second tag information for M tags. The second tag information for the fourth tag among the M tags includes a third flag with a second value, and the second tag information for the fifth tag among the M tags includes a third flag with a third value. The third flag with a second value indicates that the first operation is pending on the fourth tag, and the third flag with a third value indicates that the first operation was successfully performed on the fifth tag. For example, if the first operation includes disabling, then the third flag with a second value can be called a pending disabling flag, and the third flag with a third value can be called a disabled flag. As another example, if the first operation includes writing, then the third flag with a second value can be called a pending writing flag, and the third flag with a third value can be called a written flag.

[0284] In one possible implementation, the first device may execute S210a or S210b1 upon receiving at least one third piece of information.

[0285] In one possible implementation, the first device may execute S210a or S210b1 if the number of received third messages satisfies a first condition. Further description of the first condition can be found in S203a and S209 above.

[0286] Optionally, if the number of third messages received by the first device does not meet the first condition, the first device may continue to wait for the tags that have not fed back the third message or the third message #a to feed back the third message or the third message #a. Alternatively, the first device may send the second message again to the tags that have not fed back the third message and the third message #a among the M tags, as well as the tags that have fed back the third message #a, until the number of third messages received by the first device meets the first condition, and then the first device executes S210a or S210b1.

[0287] Optionally, if the number of third messages received by the first device within a second time period after the first device sends the second message still does not meet the first condition, the first device may send a fourth message #a to the third device or the second device. The fourth message #a indicates that the first operation against the first identifier failed. The duration of the second time period is predefined or preconfigured; for example, the duration of the second time period may be predefined by the enterprise or operator. The start time of the second time period is the moment the first device sends the second message, or the start time of the second time period is the moment the first device first receives the third message; this application does not limit this.

[0288] It should be noted that if method 200 executes S205 and S206, and the sixth information received by the first device includes the first flag, then method 200 can execute S210a or S210b1; if the sixth information received by the first device does not include the first flag, or includes a flag indicating that the first identifier has been disabled (or disabled), then for each third message or third message #a received, the first device sends a fourth message #b to the second or third device, indicating whether the first operation on the tag was successfully performed. For example, if the first device receives third information from tag #m, then the first device sends fourth information #b to the second or third device, indicating that the first operation on tag #m was successfully performed. As another example, if the first device receives third information #a from tag #n, then the first device sends fourth information #b to the second or third device, indicating that the first operation on tag #n failed.

[0289] Optionally, if method 200 performs S210b1, then method 200 may also include S210b2 and / or S210b3.

[0290] S210b2, set the value of flag #a to #a2.

[0291] The flag #a corresponds to the first identifier, and a value of #a2 indicates that the first operation was successfully performed on the first identifier. The second device sets the value of flag #a2, which is equivalent to the second device setting a flag indicating that the first operation was successfully performed on the first identifier.

[0292] Optionally, the flag #a, which takes the value #a2, is stored in the non-volatile memory area corresponding to the second device.

[0293] It should be noted that S210b2 is an optional step. For example, if the first operation includes writing or disabling, then method 200 may execute S210b2; if the first operation includes reading or inventory counting, then method 200 may not execute S210b2.

[0294] S210b3, the second device sends the thirteenth message.

[0295] Correspondingly, the third device receives the thirteenth message.

[0296] If the second device receives the fourth information, the second device sends a thirteenth information to the third device based on the fourth information to indicate that the first operation was successfully performed on the first identifier.

[0297] If the second device receives the fourth information #a, the second device sends the thirteenth information #a to the third device based on the fourth information #a. The thirteenth information #a indicates that the first operation against the first identifier failed.

[0298] If the second device receives the fourth information #b, the second device sends the thirteenth information #b to the third device based on the fourth information #b. The thirteenth information #b indicates whether the first operation was successfully performed on a certain tag (such as the tag #m or tag #n mentioned above).

[0299] In this embodiment of the application, by mapping M tags to a first identifier, the first device, the second device and the third device can interact to instruct each other to perform a first operation on the M tags, thereby avoiding frequent interaction between the first device, the second device and the third device to instruct each of the M tags to perform a first operation.

[0300] Optionally, if the first device executes S210a or 210b1 when the number of received third information is less than M, then after executing S210a or 210b1, the first device may continue to send second information to the tags (e.g., denoted as tag #t) among the M tags that have not successfully performed the first operation, so that tag #t can continue to try to perform the first operation.

[0301] Optionally, if the first device receives the third information from tag #t, the first device may send the fourth information #b to the second or third device, thereby instructing the second or third device that tag #t has successfully performed the first operation.

[0302] Optionally, method 200 may also include the following steps.

[0303] Step 1: The first device receives eighth information, which includes a fourth identifier corresponding to a tag. The eighth information indicates that a second operation should be performed on the fourth tag. For example, the second operation includes disabling, inventorying, reading, or writing.

[0304] Optionally, the fourth identifier corresponding to a tag may be predefined or preconfigured. For example, the fourth identifier corresponding to a tag may be predefined by the enterprise or operator.

[0305] Step 2: The first device sends the ninth information to the tag corresponding to the fourth identifier, and the ninth information instructs the tag corresponding to the fourth identifier to perform the second operation.

[0306] Step 3: The first device receives the tenth information from the tag corresponding to the fourth identifier. The tenth information indicates whether the second operation was successfully performed on the tag corresponding to the fourth identifier.

[0307] Step 4: The first device sends the eleventh message, which indicates whether the first operation was successfully performed on the fourth identifier.

[0308] For further description of steps 1 to 4 above, please refer to the descriptions in S203a (or S203b1 and S203b3), S207, S208 and S201a (or S210b) above.

[0309] Based on the above scheme, it is clear that this application does not limit the number of tags corresponding to the identifiers mentioned in this application (such as the first identifier, the third identifier, or the fourth identifier). For example, enterprises or operators can define the number of tags corresponding to different identifiers according to their needs.

[0310] The method provided in this application embodiment will be described below with reference to Figures 3 to 7, taking the first device as TMF, the second device as UDM, and the third device as NEF / BOSS as an example. For example, in the following embodiments, the logical label corresponds to the identifier (such as the first identifier, the third identifier, or the fourth identifier) ​​corresponding to the label in the above embodiments, and the physical label in the following embodiments corresponds to the label in the above embodiments.

[0311] Figure 3 is a schematic diagram of a communication method 300 provided in an embodiment of this application. As shown in Figure 3, method 300 may include the following steps.

[0312] S301, Physical Tag Information Contract.

[0313] UDM's account opening information includes the signing information of at least one physical tag.

[0314] S302, NEF / BOSS sends a logical tag registration request (example of information fourteen).

[0315] Accordingly, UDM receives logical tag registration requests.

[0316] A logical tag registration request is used to request the registration of a single logical tag, or to request the registration of a group of logical tags. Each logical tag corresponds to at least one physical tag.

[0317] Optionally, if the logical tag registration request is used to request the registration of a logical tag, the logical tag registration request may include a logical tag creation rule.

[0318] Optionally, if a logical tag registration request is used to request the registration of a set of logical tags, the logical tag registration request may include a set of logical tag creation rules.

[0319] Taking logical label creation rule #a as an example, logical label creation rule #a indicates the way to map at least one physical label #a to a logical label #a. In other words, logical label creation rule #a indicates the way to determine logical label #a based on at least one physical label #a.

[0320] For example, the logical label creation rule #a is at least one of the following.

[0321] (1) Map the X1 to Y1 bits of the EPC of any physical tag #a to a logical tag #a. Optionally, X1 and Y1, or the difference between X1 and Y1 and X1, are predefined by the enterprise or operator. Wherein, X1 and Y1 are non-negative integers.

[0322] (2) The enterprise or operator customizes the logical tag #a based on the User ID of at least one physical tag #a.

[0323] (3) A logical label #a is equivalent to at least one physical label #a.

[0324] Optionally, if the logical tag registration request is used to request the registration of a group of logical tags, the logical tag registration request may further indicate the method for determining the logical tag group identifier, or the logical tag registration request may include a logical tag group identifier. The logical tag group identifier corresponds to the group of logical tags that the logical tag registration request requests to register.

[0325] For example, suppose that the logical tag registration request requests the registration of at least one logical tag including logical tag #1 (corresponding to the first identifier in method 200), and logical tag #1 corresponds to M physical tags #1 (corresponding to the M tags in method 200). M is an integer greater than 1.

[0326] Optionally, method 300 also includes S303.

[0327] S303, UDM queries the saved logical label creation rules.

[0328] Upon receiving a logical tag registration request, the UDM first queries the saved logical tag creation rules. If the UDM finds that it has saved logical tag creation rules corresponding to at least one logical tag requested in the request, it does not process the request. If the UDM does not have saved logical tag creation rules corresponding to at least one logical tag requested in the request, it maps the logical tag requested in the request to the logical tag registration request and saves the mapped logical tag and its corresponding logical tag creation rules.

[0329] For example, if the logical tag registration request received by UDM is for requesting the registration of multiple logical tags, UDM may have already saved the logical tag creation rules corresponding to some of the multiple logical tags. In this case, UDM only registers the remaining logical tags, that is, maps out the logical tags, and saves the mapped logical tags and the logical tag creation rules corresponding to the logical tags.

[0330] S304, UDM obtains the logical tag and saves it.

[0331] UDM can map logical tags to rules based on the logical tags included in the logical tag registration request, and save the mapped logical tags and the corresponding logical tag rules.

[0332] For example, assuming that the logical tag registration request requests at least one logical tag including logical tag #1, then in S304, UDM maps logical tag #1 from M physical tags #1 according to logical tag creation rule #1 corresponding to logical tag #1, and saves logical tag #1 and logical tag creation rule #1.

[0333] Optionally, if the logical tag registration request does not include logical tag creation rules, the UDM can map logical tags according to predefined logical tag creation rules and save the logical tags and predefined logical tag creation rules.

[0334] This application does not limit the way UDM saves logical tags and logical tag creation rules.

[0335] For example, logical tags are signed independently and associated with their corresponding physical tags. In other words, the UDM independently stores logical tags and their creation rules, and maintains (or saves) the association between logical tags and their corresponding physical tags.

[0336] For example, UDM stores logical tags and logical tag creation rules in the contract information of the physical tags corresponding to the logical tags.

[0337] S305, UDM sends a logical tag registration response.

[0338] Correspondingly, NEF / BOSS receives the logical tag registration response.

[0339] The Logical Tag Registration response indicates that UDM has registered at least one logical tag requested by the Logical Tag Registration Request.

[0340] Optionally, the logical tag registration response may also include at least one logical tag that the logical tag registration request requested to be registered.

[0341] Optionally, method 300 also includes S306 and S307.

[0342] S306, UDM sends logical tag creation rules.

[0343] Correspondingly, TMF receive logical tag creation rules.

[0344] For example, after the UDM maps at least one logical tag based on the logical tag registration request, if the UDM stores information about the TMF used to provide services for the physical tags corresponding to one or more of the logical tags, the UDM can send the logical tags and logical tag creation rules to the TMF.

[0345] Taking logical label rule #a as an example, logical label rule #a corresponds to logical label #a. If UDM stores information about TMF #a used to provide services for the physical label corresponding to logical label #a, then in S306, UDM can send logical label creation rule #a and logical label #a to TMF #a.

[0346] Optionally, if the logical tag registration request is used to request the registration of multiple logical tags, there may be multiple TMFs that provide services for the physical tags corresponding to at least one of the multiple logical tags. In S306, the UDM sends the logical tags corresponding to the physical tags served by the TMFs and the logical tag creation rules to the multiple TMFs respectively.

[0347] For example, UDM can send the logical labels and logical label creation rules corresponding to the physical labels of TMF services to multiple TMFs simultaneously.

[0348] For example, UDM can send the logical label and logical label creation rule corresponding to the physical label of the TMF service to each of the multiple TMFs in sequence.

[0349] For example, if a UDM sends multiple logical tags and their corresponding logical tag creation rules to the same TMF, the UDM can send the multiple logical tags and their corresponding logical tag creation rules to the TMF simultaneously, or send each of the multiple logical tags and their corresponding logical tag creation rules to the TMF sequentially.

[0350] For example, if the UDM stores logical tag creation rule #1 corresponding to logical tag #1, logical tag creation rule #2 corresponding to logical tag #2, and logical tag creation rule #3, and also stores information about TMF #1 used to provide services for M physical tags #1, and information about TMF #2 used to provide services for the physical tags corresponding to logical tag #2 and the physical tags corresponding to logical tag #3, then the UDM can execute steps a and b simultaneously, or the UDM can execute step a first and then step b, or the UDM can execute step b first and then step a. Step a involves sending logical tag #1 and logical tag rule #1 to TMF #1. Step b includes steps b1 and b2, where step b2 involves sending logical tag #2 and logical tag creation rule #2 to TMF #2, and step b3 involves sending logical tag #3 and logical tag creation rule #3 to TMF #2.

[0351] Optionally, during the execution of step b by UDM, steps b1 and b2 can be executed simultaneously, or step b1 can be executed first and then step b2, or step b2 can be executed first and then step b1.

[0352] S307, TMF sends a logical tag creation rule response.

[0353] Correspondingly, UDM receives the logical label creation rule response.

[0354] The logical tag creation rule response indicates that the TMF has received the logical tag and logical tag creation rule from the UDM.

[0355] It should be noted that the embodiments in this application are only illustrated by the example of logical tags being registered in the UDM, and this application does not limit this. For example, logical tags can also be registered in the AF.

[0356] In this embodiment of the application, NEF / BOSS can register logical tags in UDM, and each logical tag corresponds to one or more physical tags. In the case where a logical tag corresponds to multiple physical tags, different network elements can perform the first operation on multiple physical tags corresponding to the logical tag by exchanging instructions to perform the first operation on the logical tag. This can avoid frequent exchanges between different network elements to perform the first operation on each of the multiple physical tags.

[0357] The method provided in this application embodiment will be described below with reference to Figure 4, taking the first operation including disabling as an example.

[0358] Figure 4 is a schematic diagram of a communication method 400 provided in an embodiment of this application. As shown in Figure 4, method 400 may include the following steps.

[0359] S401, NEF / BOSS sends a request to disable logical labels (example of message number 12).

[0360] Accordingly, UDM receives requests to disable logical labels.

[0361] The Disable Logical Label Request Instruction indicates that a single logical label may be disabled, or a group of logical labels may be disabled. For ease of description, the logical label indicated by the Disable Logical Label Request Instruction will be denoted as logical label #x below.

[0362] For example, suppose the request to disable a logical tag instructs that logical tag #1 be disabled, or instructs that logical tag group #1 be disabled. Logical tag group #1 includes logical tag #1. Logical tag #1 (corresponding to the first identifier in method 200) corresponds to M physical tags #1 (corresponding to the M tags in method 200), where M is an integer greater than 1.

[0363] Optionally, the request to disable a logical label can also carry information for permission checks. For example, in S401, when the NEF sends a request to disable a logical label to the UDM, the request can also carry information about the AF, which triggers the NEF to send the request to the UDM. Accordingly, the UDM can determine whether the AF has the permission to disable a logical label based on the information in the AF.

[0364] Optionally, the request to disable a logical label may also include at least one disabling rule (corresponding to the first condition in method 200), each disabling rule corresponding to a logical label #x, and each disabling rule being used to determine whether the logical label #x corresponding to the disabling rule is successfully disabled.

[0365] For example, the disabling rules include one or more of the following: Disabling rule #1, if disabling one physical tag corresponding to a logical tag is successful, then the logical tag is successfully disabled; Disabling rule #2, if disabling all physical tags corresponding to a logical tag is successful, then the logical tag is successfully disabled; Disabling rule #3, if the ratio of the number of successfully disabled physical tags to the number of all physical tags corresponding to a logical tag is not less than threshold #1 (corresponding to the second threshold in method 200), then the logical tag is successfully disabled; Disabling rule #4, if the ratio of the number of successfully disabled physical tags to the number of all physical tags corresponding to a logical tag within time period #1 (corresponding to the first time period in method 200) is not less than threshold #2 (corresponding to the third threshold in method 200), then the logical tag is successfully disabled. The disabling rules can be customized by the enterprise or operator.

[0366] S402, UDM sets the logical label to be disabled.

[0367] UDM sets the logical label #x to be disabled.

[0368] For example, suppose UDM sets the flag to be disabled for logical tag #1 (corresponding to the flag #a with the value #a1 in method 200), or UDM sets the flag to be disabled for at least one logical tag in logical tag group #1.

[0369] Optionally, UDM stores the flag to be disabled for logical label #x in non-volatile storage.

[0370] Optionally, if the logical label #x has been registered in the UDM, then method 400 executes S402.

[0371] Optionally, if UDM determines that AF / NEN / BOSS has the permission to disable logical label #x, then UDM sets the logical label #x to be disabled.

[0372] It should be noted that S402 is an optional step.

[0373] S403, UDM sends a response to disable logical labels.

[0374] Correspondingly, NEF / BOSS receives a response with the disabled logic tag.

[0375] The Disable Logical Labels response indicates that UDM has successfully received the Disable Logical Labels request.

[0376] Optionally, if the Disable Logical Label Request indicates that multiple logical labels #x be disabled, then the Disable Logical Label Response indicates whether the UDM has received an instruction to disable each of the multiple logical labels #x. For example, if the Disable Logical Label Request indicates that logical labels #1 and #2 be disabled, then the Disable Logical Label Response indicates whether the UDM has received an instruction to disable logical label #1, and / or whether the UDM has received an instruction to disable logical label #2.

[0377] S404, UDM sends a notification to disable logical tags.

[0378] Correspondingly, TMF receives a notification to disable logical tags.

[0379] For example, in S404, the UDM sends a notification to the TMF that provides services for the physical tag corresponding to the logical tag #x, to disable the logical tag.

[0380] Optionally, if the disable logical label request indicates multiple logical labels #x, then there may be multiple TMFs that provide services for the physical labels corresponding to at least one of the multiple logical labels #x. In this case, in S404, the UDM sends a disable notification for the logical label corresponding to the physical label served by the TMF to each of the multiple TMFs. The method by which the UDM sends the disable logical label notification to multiple TMFs can be referred to the method by which the UDM sends logical label creation rules to multiple TMFs in S306 above.

[0381] Optionally, if the request to disable a logical label also includes at least one disabling rule, then in S404, the UDM also sends the disabling rule for the logical label corresponding to the physical label of the TMF service to the TMF.

[0382] For example, suppose in S404, the UDM sends a notification to disable the logical tag (corresponding to the first information in method 200) to the TMF that provides services for logical tag #1. Optionally, the UDM also sends the disabling rule corresponding to logical tag #1 to the TMF that provides services for logical tag #1.

[0383] The remaining steps of method 400 are described below, taking the TMF in Figure 4 as an example for providing services to logical tag #1.

[0384] Optionally, if the TMF stores the context of logical tag #1, then method 400 also includes S405.

[0385] S405, TMF to logical tag pending disable flag.

[0386] For example, in S405, TMF sets the logic tag #1 to be disabled.

[0387] S406, TMF sends notification response #1.

[0388] Accordingly, UDM received notification response #1.

[0389] Notification response #1 indicates that the TMF has received a notification that logical tag #1 is disabled.

[0390] S407, TMF inventory or paging physical tags.

[0391] For example, in S407, there are M physical tags #1 corresponding to TMF inventory or paging logic tag #1.

[0392] For example, the TMF can initiate paging to active tags (such as Class C tags) among the M physical tags #1, and / or, the TMF can initiate an inventory of passive tags (such as Class A tags or Class B tags) among the M physical tags #1, to trigger the M physical tags #1 to access the network.

[0393] It should be understood that, in conjunction with method 300 above, if the UDM sends logical tag #1 and the corresponding logical tag creation rule to the TMF before executing method 400, then before executing S407, the TMF can determine M physical tags #1 based on the logical tag creation rule corresponding to logical tag #1. If the UDM does not send logical tag #1 and the corresponding logical tag creation rule to the TMF, then before S407, the TMF can request the logical tag creation rule corresponding to logical tag #1 from the UDM. For example, the TMF can send request information #a (corresponding to the fifth information in method 200) to the UDM. Request information #a includes logical tag #1 and is used to request the logical tag creation rule corresponding to logical tag #1. Then, the UDM sends the logical tag creation rule corresponding to logical tag #1 to the TMF based on request information #a (corresponding to the sixth information in method 200). After receiving the logical tag creation rule corresponding to logical tag #1, the TMF can determine the M physical tags #1 corresponding to logical tag #1.

[0394] S408, Physical Tag Access Network.

[0395] For example, in S408, one or more physical tags from M physical tags #1 access the network.

[0396] S409, TMF sends a physical tag disable command.

[0397] For example, in S409, the TMF sends a physical tag disable instruction to the M physical tags #1 (corresponding to the second information in method 200), or sends a physical tag disable instruction to the physical tags of the M physical tags #1 that are connected to the network.

[0398] Optionally, before executing S409, the TMF can check whether the flag to be disabled for logical label #1 has been saved. If the TMF has saved the flag to be disabled for logical label #1, then the TMF executes S409. If the TMF has not saved the flag to be disabled for logical label #1, then the TMF does not perform any processing.

[0399] S410, Physical tag sends feedback information #1.

[0400] Correspondingly, TMF received feedback information #1.

[0401] For example, in S410, the TMF receives feedback information #1 from physical tag #1.

[0402] Feedback message #1 (corresponding to the third message or third message #a in method 200) indicates whether the physical tag was successfully disabled.

[0403] It should be understood that in S410, because some of the M physical tags #1 are not connected to the network or are not powered, the TMF may not be able to receive feedback information #1 from all physical tags #1.

[0404] Optionally, after receiving feedback information #1, the TMF can also set a disabled flag (corresponding to the third flag with the third value in method 200) or a pending disabled flag (corresponding to the third flag with the second value in method 200) for physical tag #1 according to the content indicated by feedback information #1. Specifically, if feedback information #1 indicates that physical tag #1 was successfully disabled, the TMF sets the disabled flag for physical tag #1; if feedback information #1 indicates that physical tag was not successfully disabled, or that the disabling failed, the TMF sets the pending disabled flag for physical tag #1.

[0405] S411, TMF determines whether a logical tag has been successfully disabled based on the logical tag disabling rules.

[0406] For example, the TMF determines whether logical label #1 has been successfully disabled based on the disabling rule corresponding to logical label #1. The TMF can obtain the disabling rule corresponding to logical label #1 from the UDM, or the disabling rule corresponding to logical label #1 can be predefined or preconfigured.

[0407] Taking the disabling rule corresponding to logical tag #1 as the disabling rule #1 described in S401 above as an example, if the TMF receives a feedback message #1 and the feedback message #1 indicates that the physical tag was successfully disabled, then the TMF determines that the logical tag #1 was successfully disabled.

[0408] It should be understood that if the TMF determines that the logical tag #1 has not been successfully disabled, the TMF may repeat steps S407 to S410 until the TMF determines that the logical tag #1 has been successfully disabled. Optionally, the TMF may repeat steps S407 to S410 only for the physical tag #1 that has not been successfully disabled. That is, in S407, the TMF may only inventory or page the physical tag #1 that has not been successfully disabled, and in S409, the TMF may only send a physical tag disable command to the physical tag #1 that has not been successfully disabled.

[0409] If the TMF determines that disabling logical label #1 is successful, then method 400 continues to execute S412.

[0410] S412, TMF sends logical tag to disable completion notification.

[0411] Accordingly, the UDM receive logic tag disables completion notification.

[0412] For example, the logical tag disable completion notification sent by TMF (corresponding to the fourth information in method 400) indicates that the logical tag #1 was successfully disabled.

[0413] Optionally, the logical tag disable completion notification may also indicate whether each of the M physical tags #1 was successfully disabled. For example, the logical tag disable completion notification may also include a disabled flag or a pending flag for each of the M physical tags #1.

[0414] Optionally, method 400 also includes S413.

[0415] S413, UDM completes the logical label disabling process.

[0416] For example, in S413, UDM deletes the stored logical tag #1, or sets the disabled flag for logical tag #1 (corresponding to the flag #a with the value #a2 in method 200).

[0417] S414, UDM sends notification response #2.

[0418] Correspondingly, TMF received notification response #2.

[0419] Notification response #2 indicates that UDM has received the logical tag disabled completion notification.

[0420] Optionally, if the TMF stores the context corresponding to logical label #1, then method 400 also includes S415.

[0421] S415, TMF deletes logical tag context.

[0422] For example, in S415, the TMF deletes the context corresponding to logical label #1.

[0423] Optionally, method 400 also includes S416 and S417.

[0424] S416, UDM sends logical tags to disable completion reports.

[0425] Accordingly, the NEF / BOSS receive logic tag disables completion reporting.

[0426] For example, the logic label disable completion report indicates that the logic label #1 was successfully disabled.

[0427] S417, NEF / BOSS sends a report response.

[0428] Accordingly, UDM receives the report response.

[0429] For example, the report response indicates that NEF / BOSS has received a logical tag disabled completion report.

[0430] In this embodiment of the application, by mapping multiple physical tags to one logical tag, each network element (e.g., including UDM, TMF, NEF or BOSS) can interact to instruct the logical tag to execute a disable instruction, thereby achieving the purpose of disabling multiple physical tags, thus avoiding frequent interaction between network elements to instruct each physical tag to execute a disable instruction.

[0431] Furthermore, when UDM and / or TMF set the disable flag and the pending disable flag for logical tags, regardless of whether the physical tag can receive the physical tag disable instruction (or whether the disable is successful), it can ensure that the network side can asynchronously process the disablement of logical tags.

[0432] The method provided in this application embodiment will be described below with reference to Figure 5, taking the first operation including inventory as an example.

[0433] Figure 5 is a schematic diagram of a communication method 500 provided in an embodiment of this application. As shown in Figure 5, method 500 may include the following steps.

[0434] S501, NEF / BOSS sends an inventory request (example of first information).

[0435] Accordingly, TMF received an inventory count request.

[0436] An inventory request instructs an inventory count to be performed on a single logical label, or on a group of logical labels. For ease of description, the logical label indicated by the inventory request will be denoted as logical label #x below.

[0437] For example, suppose the inventory request instructs an inventory count to be performed on logical tag #1, or instructs an inventory count to be performed on logical tag group #1. Logical tag group #1 includes logical tag #1. Logical tag #1 (corresponding to the first identifier in method 200) corresponds to M physical tags #1 (corresponding to the M tags in method 200), where M is an integer greater than 1.

[0438] Optionally, the inventory request may also include at least one inventory rule (corresponding to the first condition in method 200), each inventory rule corresponds to a logical label #x, and each inventory rule is used to determine whether the inventory of the logical label #x corresponding to the inventory rule was successful.

[0439] For example, the inventory rules include one or more of the following: Inventory Rule #1, if the inventory of one physical tag corresponding to a logical tag is successful, the inventory of the logical tag is considered successful; Inventory Rule #2, if the inventory of all physical tags corresponding to a logical tag is successful, the inventory of the logical tag is considered successful; Inventory Rule #3, if the ratio of the number of successfully inventoried physical tags to the number of all physical tags corresponding to a logical tag is not less than threshold #1 (corresponding to the second threshold in method 200), the inventory of the logical tag is considered successful; Inventory Rule #4, if the ratio of the number of successfully inventoried physical tags to the number of all physical tags corresponding to a logical tag within time period #1 (corresponding to the first time period in method 200), the inventory of the logical tag is considered successful. The inventory rules can be customized by the enterprise or operator.

[0440] For example, if all physical tags corresponding to logical tag #x correspond to a single terminal, then the inventory rule for logical tag #x is inventory rule #1. As another example, if the inventory request indicates that the inventory of logical tag #x is for location purposes, then the inventory rule for logical tag #x is inventory rule #2.

[0441] The remaining steps of method 500 are described below, taking the TMF in Figure 5 as an example for providing services to logical tag #1.

[0442] S502, TMF sends request information #1 (corresponding to the fifth information in method 200).

[0443] Accordingly, UDM receives request information #1.

[0444] Request information #1 includes logical label #1, and request information #1 is used to request information from logical label #1.

[0445] S503, UDM sends information for logical tag #1 (corresponding to the sixth information in method 200).

[0446] Correspondingly, the TMF receives information from logical tag #1.

[0447] For example, the information for logical label #1 includes the logical label creation rule corresponding to logical label #1.

[0448] For example, the information of logical tag #1 includes the identifiers of the M physical tags #1 corresponding to logical tag #1.

[0449] Optionally, the information for logical tag #1 may also include a logical tag disabled flag, which indicates whether logical tag #1 is disabled.

[0450] It should be noted that steps S502 and S503 are optional. In conjunction with method 300 above, if the UDM sends logical tag #1 and the corresponding logical tag creation rule to the TMF before executing method 500, then method 500 may not include S502 and S503.

[0451] S504, TMF sends a physical tag inventory request.

[0452] For example, in S504, the TMF sends a physical tag inventory request to M physical tags #1 (corresponding to the second information in method 200).

[0453] S505, Physical Tag sends Physical Tag Inventory Response.

[0454] Correspondingly, the TMF receives the physical tag inventory response.

[0455] For example, in S505, the TMF receives a physical tag inventory response from physical tag #1.

[0456] The physical tag inventory response (corresponding to the third message or third message #a in method 200) indicates whether the physical tag inventory was successful.

[0457] It should be understood that in S505, because some of the M physical tags #1 are not connected to the network or are not powered on, the TMF may not be able to receive physical tag inventory responses from all physical tags #1.

[0458] Optionally, if in S503 the TMF obtains a logical tag disabled flag, and the logical tag disabled flag indicates that logical tag #1 is not disabled, then method 500 executes S506 to S510 below. If the logical tag indicates that logical tag #1 is disabled, then the TMF performs an inventory check on the M physical tags #1 according to the existing scheme. For example, each time the TMF receives a physical tag inventory check response from a physical tag #1, the TMF sends an inventory check response message to NEF / BOSS, indicating whether the inventory check of physical tag #1 was successful.

[0459] S506, Get the logical label.

[0460] It should be understood that after receiving the physical tag inventory response from physical tag #1, the TMF can determine whether the inventory of logical tag #1 was successful based on the inventory rules corresponding to logical tag #1. The TMF can obtain the inventory rules corresponding to logical tag #1 from the received inventory request, or the inventory rules corresponding to logical tag #1 may be predefined or pre-configured.

[0461] Taking the inventory rule corresponding to logical tag #1 as the inventory rule #1 described in S501 above as an example, if the TMF receives a physical tag inventory response and the physical tag inventory response indicates that the physical tag is successfully disabled, then the TMF determines that the inventory of logical tag #1 is successful.

[0462] It should be understood that if the TMF determines that the inventory of logical tag #1 was unsuccessful, the TMF may repeat steps S504 to S505 until the TMF determines that the inventory of logical tag #1 was successful. Optionally, the TMF may repeat steps S504 to S505 only for physical tag #1 that was not successfully inventoried; that is, in step S504, the TMF may only send a physical tag inventory request to physical tag #1 that was not successfully inventoried.

[0463] If the TMF determines that the inventory count of logical tag #1 was successful, then the TMF can save logical tag #1. Therefore, in S506, the TMF retrieving the logical tag is equivalent to querying whether logical tag #1 has been saved; in other words, the TMF retrieving the logical tag is equivalent to determining whether the inventory count of logical tag #1 was successful.

[0464] Optionally, if the TMF has already saved logical tag #1, then the TMF will not perform any further processing after receiving the physical tag inventory response.

[0465] Optionally, if the TMF fails to obtain a logical label, then method 500 executes steps S507 and S508.

[0466] S507, TMF sends a validity verification request.

[0467] Accordingly, UDM receives validity verification requests.

[0468] For example, the validity verification request sent by TMF includes the identifier of physical tag #1, and the validity verification request is used to request the validity verification of physical tag #1.

[0469] S508, UDM sends a validity verification response.

[0470] Correspondingly, the TMF receives the validity verification response.

[0471] For example, the validity check response indicates whether physical tag #1 has passed the validity check.

[0472] It should be noted that steps S507 and S508 are optional. For example, if the TMF has not performed a validity check on any of the M physical tags #1, then method 500 can execute steps S507 and S508. If the TMF has already performed a validity check on at least one of the M physical tags #1, then the TMF will not perform a validity check on the remaining physical tags #1.

[0473] It should be understood that when M physical labels #1 correspond to one logical label #1, the M physical labels #1 are associated. If any one of the M physical labels #1 passes the validity check, then all M physical labels #1 can be considered to have passed the validity check. Therefore, by performing validity checks on at least one of the M physical labels #1, the network can achieve the goal of validating all M physical labels #1 without requiring frequent signaling interactions that would result from validating all M physical labels #1.

[0474] S509, TMF stores logical tags.

[0475] As described in S506, if the TMF determines that the inventory count of logical tag #1 is successful, then the TMF saves logical tag #1.

[0476] Optionally, method 500 also includes S510.

[0477] S510, TMF sends a successful inventory count response (corresponding to the fourth message in method 200).

[0478] Correspondingly, NEF / BOSS received a successful inventory count response.

[0479] The inventory count was successful. The response indicated that the inventory count was successful for logic tag #1.

[0480] In this embodiment of the application, by mapping multiple physical tags to one logical tag, the network elements (such as UDM, TMF, NEF or BOSS) can interact to instruct the logical tag to perform an inventory of multiple physical tags, thereby avoiding frequent interaction between the network elements to instruct each physical tag to perform an inventory of multiple physical tags.

[0481] Furthermore, different inventory rules can be defined to address different inventory requirements, thereby minimizing the signaling interaction required for inventory checks while still meeting the needs. For example, in a warehouse inventory scenario, if multiple physical tags on a terminal (or an object) are mapped to a single logical tag, the inventory rule corresponding to the logical tag can be determined as inventory rule #1 mentioned in S501, thus reducing the signaling interaction required for inventory checks. As another example, in a location-based scenario, the inventory rule corresponding to the logical tag can be determined as inventory rule #2 mentioned in S501, thereby ensuring the accuracy of location tracking.

[0482] The method provided in the embodiments of this application will be described below with reference to Figure 6, taking the first operation including degree as an example.

[0483] Figure 6 is a schematic diagram of a communication method 600 provided in an embodiment of this application. As shown in Figure 6, method 600 may include the following steps.

[0484] S601, NEF / BOSS sends a read logical tag request (example of first information).

[0485] Correspondingly, the TMF receives a request to read the logical tag.

[0486] A read logical tag request indicates that a read operation be performed on a single logical tag, or on a group of logical tags. For ease of description, the logical tag indicated by the read logical tag request will be denoted as logical tag #x below.

[0487] For example, suppose a read logical tag request instructs a read operation on logical tag #1, or instructs a read operation on logical tag group #1. Logical tag group #1 includes logical tag #1. Logical tag #1 (corresponding to the first identifier in method 200) corresponds to M physical tags #1 (corresponding to the M tags in method 200), where M is an integer greater than 1.

[0488] Optionally, the read logic tag request also includes at least one read rule (corresponding to the first condition in method 200), each read rule corresponds to a logic tag #x, and each read rule is used to determine whether the read of the logic tag #x corresponding to the read rule was successful.

[0489] For example, the read rules include one or more of the following: Read rule #1, if a read of one physical tag corresponding to a logical tag is successful, then the read of the logical tag is successful; Read rule #2, if a read of all physical tags corresponding to a logical tag is successful, then the read of the logical tag is successful; Read rule #3, if the ratio of the number of successfully read physical tags to the number of all physical tags corresponding to the logical tag is not less than threshold #1 (corresponding to the second threshold in method 200), then the read of the logical tag is successful; Read operation rule #4, if the ratio of the number of successfully read physical tags to the number of all physical tags corresponding to the logical tag within time period #1 (corresponding to the first time period in method 200) is not less than threshold #2 (corresponding to the third threshold in method 200), then the read of the logical tag is successful. The read rules can be customized by the enterprise or operator.

[0490] The remaining steps of method 600 are described below, taking the TMF in Figure 6 as an example for providing services to logical tag #1.

[0491] S602, TMF sends request information #2 (corresponding to the fifth information in method 200).

[0492] Accordingly, UDM receives request information #2.

[0493] Request information #2 includes logical tag #1. Request information #2 is used to request information about the physical tag corresponding to logical tag #1.

[0494] S603, UDM sends information about the physical tag (corresponding to the sixth information in method 200).

[0495] Correspondingly, the TMF receives information from the physical tags.

[0496] For example, the TMF receives information #1 of M physical tags #1 corresponding to logical tag #1 (the first tag information of the M tags in method 200).

[0497] For example, the information #1 of physical tag #1 includes one or more of the following: the identifier or written flag of physical tag #1 (corresponding to the second flag with a first value in method 200).

[0498] It should be noted that steps S602 and S603 are optional. In conjunction with method 300 above, if the UDM sends logical tag #1 and the corresponding logical tag creation rule to the TMF before executing method 600, then method 600 may not include steps S602 and S603.

[0499] S604, TMF inventory or paging physical tags.

[0500] For example, in S604, there are M physical tags #1 corresponding to TMF inventory or paging logic tag #1.

[0501] For example, the TMF can initiate paging to active tags (such as Class C tags) among the M physical tags #1, and / or, the TMF can initiate an inventory of passive tags (such as Class A tags or Class B tags) among the M physical tags #1, to trigger the M physical tags #1 to access the network.

[0502] S605, physical tag access network.

[0503] For example, in S605, one or more physical tags from M physical tags #1 access the network.

[0504] S606, TMF sends physical tag read command.

[0505] For example, in S606, the TMF sends a physical tag read instruction to M physical tags #1 (corresponding to the second information in method 200), or sends a physical tag read instruction to the physical tag #1 that is connected to the network among the M physical tags #1, or sends a physical tag read instruction to the physical tag #1 with the written flag among the M physical tags #1.

[0506] S607, Physical tag sends feedback information #2.

[0507] Correspondingly, TMF received feedback information #2.

[0508] For example, in S607, the TMF receives feedback information #2 from physical tag #1.

[0509] Feedback message #2 (corresponding to the third message or third message #a in method 200) indicates whether the physical tag was read successfully.

[0510] It should be understood that in S607, because some of the M physical tags #1 are not connected to the network or are not powered, the TMF may not be able to receive feedback information #2 from all physical tags #1.

[0511] S608, TMF determines whether a logical tag has been successfully read based on the logical tag reading rules.

[0512] For example, TMF determines whether a read of logical tag #1 was successful based on the read rule corresponding to logical tag #1. TMF can obtain the read rule corresponding to logical tag #1 from the read logical tag request, or the read rule corresponding to logical tag #1 may be predefined or preconfigured.

[0513] Taking the read rule corresponding to logical tag #1 as the read rule #1 described in S601 above as an example, if the TMF receives a feedback message #2 and the feedback message #2 indicates that the physical tag is successfully disabled, then the TMF determines that the logical tag #1 is successfully disabled.

[0514] It should be understood that if the TMF determines that the logical tag #1 was not successfully read, the TMF can repeat S604 to S607 until the TMF determines that the logical tag #1 was successfully read. Optionally, the TMF only repeats S604 to S607 for the physical tag #1 that was not successfully read. That is, in S604, the TMF only checks or pages the physical tag #1 that was not successfully read, and in S606, the TMF only sends a physical tag read command to the physical tag #1 that was not successfully read.

[0515] If the TMF determines that the logical tag #1 was read successfully, then method 600 continues to execute S609.

[0516] S609, TMF sends a logical tag read success notification.

[0517] Correspondingly, NEF / BOSS receives a successful read notification for the logical tag.

[0518] For example, the logical tag read success notification sent by TMF (corresponding to the fourth information in method 400) indicates that the logical tag #1 was read successfully.

[0519] Optionally, method 600 also includes S610.

[0520] S610, NEF / BOSS sends a notification response.

[0521] Correspondingly, the TMF receives the notification response.

[0522] The notification response indicates that NEF / BOSS has successfully received the logical tag read success notification.

[0523] In this embodiment of the application, by mapping multiple physical tags to one logical tag, each network element (such as TMF, NEF or BOSS) can perform read operations on multiple physical tags by interactively instructing the logical tag to execute read operations, thereby avoiding frequent interactive instructions between network elements to execute read operations on each of the multiple physical tags.

[0524] The method provided in the embodiments of this application will be described below with reference to Figure 7, taking the first operation including writing as an example.

[0525] Figure 7 is a schematic diagram of a communication method 700 provided in an embodiment of this application. As shown in Figure 4, method 700 may include the following steps.

[0526] S701, NEF / BOSS sends a write logic tag request (example of the twelfth message).

[0527] Correspondingly, UDM receives write logic tag requests.

[0528] A write logical tag request indicates that a write operation be performed on a single logical tag, or on a group of logical tags. For ease of description, the logical tag indicated by the write logical tag request will be denoted as logical tag #x below.

[0529] For example, suppose a write logic tag request instructs a write operation to logic tag #1, or instructs a write operation to logic tag group #1. Logic tag group #1 includes logic tag #1. Logic tag #1 (corresponding to the first identifier in method 200) corresponds to M physical tags #1 (corresponding to the M tags in method 200), where M is an integer greater than 1.

[0530] Optionally, the write logic tag request also includes at least one write rule (corresponding to the first condition in method 200), each write rule corresponds to a logic tag #x, and each write rule is used to determine whether the write to the logic tag #x corresponding to the write rule was successful.

[0531] For example, the write rules include one or more of the following: Write rule #1, if a write to one physical tag corresponding to a logical tag is successful, then the write to the logical tag is successful; Write rule #2, if a write to all physical tags corresponding to a logical tag is successful, then the write to the logical tag is successful; Write rule #3, if the ratio of the number of successfully written physical tags to the number of all physical tags corresponding to the logical tag is not less than threshold #1 (corresponding to the second threshold in method 200), then the write to the logical tag is successful; Write rule #4, if the ratio of the number of successfully written physical tags to the number of all physical tags corresponding to the logical tag within time period #1 (corresponding to the first time period in method 200) is not less than threshold #2 (corresponding to the third threshold in method 200), then the write to the logical tag is successful. The write rules can be customized by the enterprise or operator.

[0532] S702, UDM sets the logical tag to be written.

[0533] UDM sets the logical label #x to a write-ready flag.

[0534] For example, suppose UDM sets the write-ready flag for logical tag #1 (corresponding to the flag #a with the value #a1 in method 200), or UDM sets the write-ready flag for at least one logical tag in logical tag group #1.

[0535] Optionally, UDM stores the write flag for logical tag #x in non-volatile memory.

[0536] It should be noted that S702 is an optional step.

[0537] S703, UDM sends a write logic tag response.

[0538] Correspondingly, NEF / BOSS receives the write logic tag response.

[0539] The write logic tag response indicates that UDM has successfully received the write logic tag request.

[0540] For more details on S703, please refer to the above text on S403.

[0541] S704, UDM sends a write logic tag notification.

[0542] Correspondingly, the TMF receives write logic tag notifications.

[0543] For example, in S704, the UDM sends a write logical tag notification to the TMF, which is used to provide services for the physical tag corresponding to the logical tag #x.

[0544] The method by which the UDM sends write logical tag notifications can be referenced in S404 above, which describes the method by which the UDM sends disable logical tag notifications.

[0545] For example, suppose in S704, the UDM sends a write logical tag notification (corresponding to the first information in method 200) to the TMF used to provide services for logical tag #1. Optionally, the UDM also sends the write rule corresponding to logical tag #1 to the TMF used to provide services for logical tag #1.

[0546] The remaining steps of method 700 are described below, taking the TMF in Figure 7 as an example for providing services to logical tag #1.

[0547] Optionally, if the TMF stores the context of logical tag #1, then method 700 also includes S705.

[0548] S705, TMF to logical tag pending write flag.

[0549] For example, in S705, TMF sets the logical tag #1 to be written.

[0550] S706, TMF sends notification response #3.

[0551] Accordingly, UDM received notification response #3.

[0552] Notification response #3 indicates that the TMF has received a write notification for logical tag #1.

[0553] S707, TMF inventory or paging physical tags.

[0554] For example, in S707, there are M physical tags #1 corresponding to TMF inventory or paging logic tag #1.

[0555] For more details on S707, please refer to the section on S407 above.

[0556] S708, physical tag access network.

[0557] For example, in S708, one or more physical tags from M physical tags #1 access the network.

[0558] S709, TMF sends physical tag write commands.

[0559] For example, in S709, the TMF sends a physical tag write instruction to M physical tags #1 (corresponding to the second information in method 200), or sends a physical tag write instruction to the physical tags of the M physical tags #1 that are connected to the network.

[0560] Optionally, before executing S709, the TMF can check whether the write flag for logical tag #1 has been saved. If the TMF has saved the write flag for logical tag #1, then the TMF executes S709. If the TMF has not saved the write flag for logical tag #1, then the TMF does not perform any processing.

[0561] S710, physical tag sends feedback information #3.

[0562] Correspondingly, TMF received feedback information #3.

[0563] For example, in S710, the TMF receives feedback information #3 from physical tag #1.

[0564] Feedback message #3 (corresponding to the third message or third message #a in method 200) indicates whether the physical tag was written successfully.

[0565] It should be understood that in the S710, because some of the M physical tags #1 are not connected to the network or are not powered, the TMF may not be able to receive feedback information #3 from all physical tags #1.

[0566] Optionally, after receiving feedback information #3, the TMF can also set either a written flag (corresponding to the third flag with the third value in method 200) or a pending flag (corresponding to the third flag with the second value in method 200) for physical tag #1 according to the content indicated by feedback information #3. Specifically, if feedback information #3 indicates that physical tag #1 was successfully written, the TMF sets the written flag for physical tag #1; if feedback information #3 indicates that the physical tag was not successfully written, or the writing failed, the TMF sets the pending flag for physical tag #1.

[0567] S711, TMF determines whether the logical tag was written successfully based on the logical tag write rules.

[0568] For example, the TMF determines whether the write to logical tag #1 was successful based on the write rule corresponding to logical tag #1. The TMF can obtain the write rule corresponding to logical tag #1 from the UDM, or the write rule corresponding to logical tag #1 can be predefined or preconfigured.

[0569] Taking the write rule corresponding to logical tag #1 as the write rule #1 described in S701 above as an example, if the TMF receives a feedback message #3 and the feedback message #3 indicates that the physical tag was successfully written, then the TMF determines that the logical tag #1 was successfully written.

[0570] It should be understood that if the TMF determines that the logical tag #1 was not successfully written, the TMF can repeat S707 to S710 until the TMF determines that the logical tag #1 was successfully written. Optionally, the TMF only repeats S707 to S710 for the physical tag #1 that was not successfully written. That is, in S707, the TMF only checks or pages the physical tag #1 that was not successfully written, and in S709, the TMF only sends a physical tag write command to the physical tag #1 that was not successfully written.

[0571] If the TMF determines that the logical tag #1 was written successfully, then method 700 continues to execute S712.

[0572] S712, TMF sends a logical tag write success notification.

[0573] Correspondingly, the UDM receives a successful write notification for the logical tag.

[0574] For example, the logical tag write success notification sent by TMF (corresponding to the fourth information in method 700) indicates that the logical tag #1 was written successfully.

[0575] Optionally, the logical tag write success notification may also indicate whether the write was successful for each of the M physical tags #1. For example, the logical tag write completion notification may also include a write flag or a pending flag for each of the M physical tags #1.

[0576] Optionally, method 700 also includes S713.

[0577] S713, UDM performs logical tag write completion processing.

[0578] For example, in S713, UDM sets the written flag for logic tag #1 (corresponding to flag #a, which takes the value #a2 in method 200).

[0579] S714, UDM sends notification response #4.

[0580] Correspondingly, TMF received notification response #4.

[0581] Notification response #4 indicates that UDM has received the logical tag write complete notification.

[0582] Optionally, if the TMF stores the context corresponding to logical label #1, then method 700 also includes S715.

[0583] S715, TMF sets the logical tag to be written.

[0584] For example, in S715, the TMF sets the write flag for logic tag #1.

[0585] Optionally, method 700 also includes S716 and S717.

[0586] S716, UDM sends a logical tag write completion report.

[0587] Correspondingly, a NEF / BOSS receive logic tag write completion report is generated.

[0588] For example, a logical tag write complete report indicates that logical tag #1 was written successfully.

[0589] S717, NEF / BOSS sends a report response.

[0590] Accordingly, UDM receives the report response.

[0591] For example, the report response indicates that NEF / BOSS has received the logical tag write complete report.

[0592] In this embodiment of the application, by mapping multiple physical tags to one logical tag, each network element (e.g., including UDM, TMF, NEF or BOSS) can perform write operations on multiple physical tags by interactively instructing the logical tag to execute write instructions, thereby avoiding frequent interactive instructions between network elements to execute write instructions on each of the multiple physical tags.

[0593] Furthermore, when UDM and / or TMF set the write flag and write flag for logical tags, regardless of whether the physical tag can receive the physical tag write command (or whether the write is successful), it can ensure that the network side can asynchronously process the write to the logical tag.

[0594] It should be understood that the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. For example, S415 in method 400 can be executed before S412, or S415 can be executed after S412.

[0595] It should also be understood that, in the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0596] It is understood that, in the above-described method embodiments, the methods and operations implemented by the apparatus (such as the first apparatus, the second apparatus, and the third apparatus) can also be implemented by components of the apparatus (such as chips or circuits).

[0597] The communication method provided in the embodiments of this application has been described in detail above with reference to Figures 2 to 7. The above communication method is mainly described from the perspective of interaction between devices. It is understood that, in order to achieve the above functions, the first device, the second device, and the third device include hardware structures and / or software modules corresponding to the execution of each function.

[0598] It is understood that, in order to achieve the functions in the above embodiments, the first device, the second device, and the third device include hardware structures and / or software modules corresponding to perform each function. Those skilled in the art should readily recognize that, based on the units and method steps of the various examples described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0599] Figures 8 and 9 are schematic block diagrams of possible apparatuses provided in embodiments of this application. These apparatuses can be used to implement the terminal-side or network-side functions in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments.

[0600] Figure 8 is a schematic block diagram of the apparatus provided in an embodiment of this application. The apparatus 1500 shown in Figure 8 may include a processing module 1510 and a communication module 1520.

[0601] In one possible design, device 1500 can be used to implement the communication method implemented by the first device in any of the embodiments shown in Figures 2 to 7. For example, processing module 1510 is used to implement the processing-related steps performed by the first device in each method embodiment; communication module 1520 is used to implement the sending and / or receiving steps performed by the first device in each method embodiment, such as receiving first information, sending second information, receiving third information, or sending fourth information, or one or more of these steps.

[0602] For example, the communication module 1520 is configured to: receive first information, the first information including a first identifier, the first identifier corresponding to M tags, the first information indicating that a first operation is performed on the first identifier; M≥2, M is an integer; send second information to M1 tags among the M tags, the second information indicating that the first operation is performed on the M1 tags, M1≤M, and M1 is an integer; receive third information from each of the N second tags, the third information indicating that the first operation was successfully performed on the tag; the N tags belong to the M1 tags, N≤M1, and N is an integer; send fourth information, the fourth information indicating that the first operation was successfully performed on the first tag.

[0603] A more detailed description of the processing module 1510 and the communication module 1520 can be obtained directly from the relevant descriptions in the method embodiments shown in Figures 2 to 7, and will not be repeated here.

[0604] In another possible design, device 1500 can be used to implement the communication method implemented by the second device in any of the embodiments shown in Figures 2 to 7. For example, processing module 1510 is used to implement the processing-related steps performed by the second device in each method embodiment; communication module 1520 is used to implement the sending and / or receiving steps performed by the second device in each method embodiment, such as receiving one or more of the twelfth information, sending the first information, and receiving the fourth information.

[0605] For example, the communication module 1520 is configured to: receive a twelfth message, the twelfth message including a first identifier, the first identifier corresponding to M tags, the twelfth message indicating that a first operation is performed on the identifier; M≥2, M is an integer; send a first message, the first message including a first identifier, the first message indicating that a first operation is performed on the first identifier; and receive a fourth message, the fourth message indicating that the first operation was successfully performed on the first identifier.

[0606] A more detailed description of the processing module 1510 and the communication module 1520 can be obtained directly from the relevant descriptions in the method embodiments shown in Figures 2 to 7, and will not be repeated here.

[0607] It should be noted that the communication module can also be called a transceiver module, transceiver unit, transceiver, transceiver device, or transceiver apparatus, etc. The processing module can also be called a processor, processing board, processing unit, or processing apparatus, etc. Optionally, the communication module is used to execute the sending and receiving operations of the first or second device in the above method. The device in the communication module that implements the receiving function can be considered as the receiving module, and the device in the communication module that implements the sending function can be considered as the sending module; that is, the communication module can include both a receiving module and a sending module.

[0608] It should also be noted that, in one possible design, the aforementioned processing module and / or communication module can be implemented through virtual modules. For example, the processing module can be implemented through software functional units or virtual devices, and the communication module can be implemented through software functions or virtual devices. In another possible design, the processing module or communication module can also be implemented through physical devices. For example, if the communication device is implemented using a chip / chip circuit, the communication module can be an input / output circuit and / or a communication interface, performing input operations (corresponding to the aforementioned receiving operation) and output operations (corresponding to the aforementioned sending operation); the processing module can be an integrated processor, a microprocessor, or an integrated circuit.

[0609] The module division in this embodiment is illustrative and represents only one logical functional division; in actual implementation, other division methods may be used. Furthermore, the functional modules in the various examples of this embodiment can be integrated into a single processor, exist as separate physical entities, or be integrated into a single module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0610] Figure 9 is a schematic diagram of the structure of a communication device provided in another embodiment of this application. As shown in Figure 9, the device 1600 includes a processing circuit 1610 and a communication circuit 1620. The processing circuit 1610 and the communication circuit 1620 are coupled to each other.

[0611] It can be understood that the processing circuit 1610 can be one or more processors, or it can be all or part of the circuits with processing functions in one or more processors.

[0612] Understandably, the communication circuit 1620 can be a transceiver or an input / output interface.

[0613] Optionally, the device 1600 may further include a memory 1630 for storing instructions executed by the processing circuit 1610, or storing input data required for the running instructions of the processing circuit 1610, or storing data generated after the running instructions of the processing circuit 1610.

[0614] It is understood that the memory 1630 may be located outside the processing circuit 1610, or inside the processing circuit 1610.

[0615] As an example, the processing circuit 1610 is used to implement the functions of the processing module 1510, and the communication circuit 1620 is used to implement the functions of the communication module 1520.

[0616] As an example, device 1600 can be a communication device or a chip used in a communication device.

[0617] When device 1600 is a communication device, the communication circuit can be a transceiver; when device 1600 is a chip, the communication circuit can be an input / output circuit, a bus, pins, or other types of communication interfaces. The input circuit in the input / output circuit can be used for receiving, and the output interface can be used for transmitting.

[0618] This application also provides a computer program product that, when run on a processor, can implement the communication method executed by the first device or the communication method executed by the second device in the above method embodiments.

[0619] This application also provides a computer-readable storage medium containing computer instructions that, when executed on a processor, can implement the communication method executed by the second device in the above method embodiments.

[0620] This application also provides a communication system, including the aforementioned second device and second device. The first device can be used to implement the communication method implemented by the first device in the above method embodiments, and the second device can be used to implement the communication method implemented by the second device in the above method embodiments.

[0621] It is understood that the processor in the embodiments of this application may be any of the following devices or all or part of the circuitry used for processing functions: a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor.

[0622] The terms “unit”, “module”, etc., used in this specification may be used to refer to computer-related entities, hardware, firmware, combinations of hardware and software, software, or software in execution.

[0623] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0624] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0625] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0626] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0627] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

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

[0629] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0630] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, the method being applied to a communication device, characterized by, The method comprises: receiving first information, the first information comprising a first identifier corresponding to M tags, the first information indicating that a first operation is to be performed on the first identifier; M≥2, M being an integer; sending second information to M1 tags of the M tags, the second information indicating that the first operation is to be performed on the M1 tags, M1≤M, and M1 being an integer; receiving third information from each of N tags, the third information indicating that the first operation is successfully performed on the tag, the N tags belonging to the M1 tags, N≤M1, and N being an integer; sending fourth information, the fourth information indicating that the first operation is successfully performed on the first identifier.

2. The method of claim 1, wherein: the M tags correspond to a first terminal; or the M tags correspond to P terminals, and any two tags of the M tags are of a same type, P being an integer greater than 1.

3. The method of claim 1, wherein, The sending of the fourth information comprises: if a quantity of the third information satisfies a first condition, the fourth information is sent; wherein the first condition comprises one or more of: the quantity of the third information is not less than a first threshold; a ratio between the quantity of the third information and M is not less than a second threshold; the quantity of the third information is equal to M; a ratio between a quantity of the third information received in a first time period and M is not less than a third threshold.

4. The method of claim 3, wherein, The first information further indicates the first condition.

5. The method according to any one of claims 1 to 4, characterized in that, Before the sending of the second information, the method further comprises: sending fifth information, the fifth information comprising the first identifier, the fifth information being used to request first tag information of the M tags, the first tag information of any one of the M tags being used to determine the tag; receiving sixth information, the sixth information comprising the first tag information of the M tags.

6. The method according to any one of claims 1 to 4, characterized in that, Before the sending of the second information, the method further comprises: sending fifth information, the first information comprising the first identifier, the fifth information being used to request a correspondence between the first identifier and the M tags; receiving sixth information, the sixth information comprising the correspondence between the M tags and the first identifier; determining the M tags according to the correspondence.

7. The method according to any one of claims 1 to 4, characterized in that, Before the receiving of the first information, the method further comprises: receiving seventh information; the seventh information comprising the first identifier and first tag information of the M tags, the first tag information of any one of the M tags is used to determine the tag; or the seventh information comprising a correspondence between the first identifier and the M tags, the correspondence being used to determine the M tags.

8. The method according to claim 5 or 6, characterized in that, The sixth information further comprises a first flag, the first flag indicating that the first identifier is not disabled.

9. The method of claim 5, wherein, The first operation comprises reading, the first tag information of a first tag of the M tags comprising a second flag with a first value, the second flag with the first value indicating that a write operation is successfully performed on the first tag.

10. The method according to any one of claims 1 to 9, characterized in that, The first operation comprises reading, the M1 tags being tags of the M tags on which a write operation is successfully performed.

11. The method according to any one of claims 1 to 8, characterized in that, The first operation comprises inventory, no legitimacy check is performed on any of the N tags, and before the fourth information is sent, the method further comprises: The legitimacy of one of the N tags is checked.

12. The method according to any one of claims 1 to 11, characterized in that, The fourth information further indicates whether the first operation is successfully performed on each of the M tags.

13. The method of claim 12, wherein, The first operation comprises disabling or writing; The fourth information comprises second tag information of the M tags, the second tag information of a fourth tag in the M tags comprises a third flag taking a second value, and the second tag information of a fifth tag in the M tags comprises a third flag taking a third value; wherein the third flag taking the second value indicates that the first operation is to be performed on the fourth tag, and the third flag taking the third value indicates that the first operation is successfully performed on the fifth tag.

14. The method according to any one of claims 1 to 13, characterized in that, The first identifier is determined based on an identifier of one or more of the M tags, and the identifier of the tag comprises one or more of the following: a tag identifier, an electronic product code, or a user identifier.

15. The method according to any one of claims 1 to 14, characterized in that, The method further comprises: receiving eighth information, the eighth information comprising a fourth identifier corresponding to a tag, the eighth information indicating that a second operation is performed on the fourth identifier; sending ninth information to the tag corresponding to the fourth identifier, the ninth information indicating that the second operation is performed on the tag corresponding to the fourth identifier; receiving tenth information from the tag corresponding to the fourth identifier, the tenth information indicating whether the second operation is successfully performed on the tag corresponding to the fourth identifier; sending eleventh information, the eleventh information indicating whether the second operation is successfully performed on the fourth identifier.

16. The method according to any one of claims 1 to 15, characterized in that, The communication device comprises a tag management function entity or a chip in the tag management function entity.

17. A communication method, the method being applied to a communication device, characterized by Comprise: receiving twelfth information, the twelfth information comprising a first identifier corresponding to M tags, the twelfth information indicating that a first operation is performed on the first identifier; M≥2, M is an integer; sending first information, the first information comprising the first identifier, the first information indicating that the first operation is performed on the first identifier; receiving fourth information, the fourth information indicating that the first operation is successfully performed on the first identifier.

18. The method of claim 17, wherein The M tags correspond to a first terminal; or The M tags correspond to P terminals, and any two tags in the M tags are of the same type, P being an integer greater than 1.

19. The method of claim 17 or 18, wherein, The fourth information further indicates whether the first operation is successfully performed on each of the M tags; 20. The method of claim 19, wherein, The first operation comprises disabling or writing, The fourth information includes second label information of the M labels, the second label information of a fourth label in the M labels includes a third flag with a second value, and the second label information of a fifth label in the M labels includes a third flag with a third value; the third flag with the second value indicates that the first operation is to be performed on the fourth label, and the third flag with the third value indicates that the first operation is successfully performed on the fifth label.

21. The method according to any one of claims 17 to 20, characterized in that, The method further includes: sending thirteenth information indicating that the first operation is successfully performed on the first identifier.

22. The method of any one of claims 17-21, wherein, Before receiving the fourth information, the method further includes: sending seventh information; the seventh information includes the first identifier and first label information of the M labels, the first label information of any one of the M labels being used to determine the label; or the seventh information includes a correspondence between the M labels and the first identifier, the correspondence being used to determine the M labels.

23. The method of any one of claims 17-22, wherein, The first identifier is determined based on an identifier of one or more labels in the M labels, and the identifier of the M labels includes one or more of the following: a label identifier, an electronic product code, or a user identifier.

24. The method of any one of claims 17-23, wherein, Before receiving the twelfth information, the method further includes: receiving fourteenth information indicating that the first identifier is determined; determining and saving the first identifier.

25. The method of claim 24, wherein, The fourteenth information further indicates a manner of determining the first identifier based on an identifier of one or more labels in the M labels.

26. The method of claim 24 or 25, wherein, The saving of the first identifier includes: saving an association between the first identifier and the M labels; or saving the first identifier in subscription information of each label in the M labels.

27. The method of any one of claims 17-26, wherein, The communication device includes a data management network element, an application function, a chip in the data management network element, or a chip in the application function.

28. A communications device, characterized by The communication device includes a module for implementing the method of any one of claims 1-16.

29. The communication apparatus according to claim 28, wherein, The communication device includes any one of the following: a label management function entity or a chip.

30. A communications device, characterized by The communication device includes a module for implementing the method of any one of claims 17-27.

31. The communication apparatus according to claim 30, wherein The communication device includes any one of the following: a data management network element, an application function, or a chip.

32. A computer-readable storage medium, comprising: The computer-readable storage medium stores a computer program or instructions, which, when executed, cause the method of any one of claims 1-16 or the method of any one of claims 17-27 to be implemented.

33. A computer program product comprising a computer program or instructions, characterized in that, The computer-readable storage medium stores a computer program or instructions, which, when executed, cause any one of the methods of claims 1-16 to be implemented, or cause any one of the methods of claims 17-27 to be implemented.

Images