Communication method and apparatus

Abstract

A communication method and apparatus, relating to the field of communications, and capable of solving the problem that an A-IoT device cannot determine whether it is needed to repeatedly respond to a paging message of the same service sent by the same reader / writer or different readers / writers. In the method, a first access device can determine a second identifier different from an identifier identifying a first service, to be carried in a sent message associated with the first service, and different access devices can determine different second identifiers, so that on the basis of the second identifiers, a first apparatus can respond to the messages associated with the same service and sent from different access devices.

Description

Communication methods and devices

[0001] This application claims priority to Chinese Patent Application No. 202411598584.7, filed with the State Intellectual Property Office of China on November 8, 2024, entitled "Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more particularly to communication methods and apparatus. Background Technology

[0003] Ambient Internet of Things (A-IoT) devices are low-power, low-complexity IoT terminal devices. A-IoT devices receive and respond to paging messages sent by readers to randomly connect to the reader for device-to-reader (D2R) data transmission, and / or reader-to-device (D2R) data transmission, or directly perform D2R data transmission with the reader. The paging message includes a requested service identifier (such as a session ID).

[0004] Currently, to prevent A-IoT devices from failing to receive paging messages, a paging retransmission scheme has been introduced. This allows the same reader / writer to repeatedly send paging messages containing the same session ID to the same A-IoT device. However, to prevent A-IoT devices from repeatedly responding to multiple paging messages for the same service based on core network service requests (which could cause repeated random access operations), the A-IoT device responds to one paging message containing a session ID and completes one service request. If it then receives another paging message with the same session ID, it will not respond. However, this response method for A-IoT devices is not applicable in some service or application scenarios that require repeated responses to the same paging message, such as proximity positioning services or pipeline scenarios. Summary of the Invention

[0005] This application provides a communication method and apparatus that enables A-IoT devices to determine whether they need to repeatedly respond to paging messages for the same service sent by the same reader or different readers, thus flexibly adapting to the needs of different services or application scenarios.

[0006] To achieve the above objectives, this application adopts the following technical solution:

[0007] Firstly, a communication method is provided. This method can be executed by a first access device, or by a component of the first access device, such as a processor, chip, or chip system of the first access device, or by a logic module or software capable of implementing all or part of the first access device. Taking the application of this method to a first access device or a chip in the first access device as an example, the method includes: sending a first message, the first message being associated with a first identifier, the first identifier being used to identify a first service, and the first message including a second identifier; and communicating with a first device, the first device being a device responding to the first message.

[0008] In this respect, the first access device can carry a second identifier in the first message associated with the first service. This second identifier is different from the first identifier that identifies the first service. The second identifier can be used by the first device to determine whether to respond to the first message. Thus, in scenarios where multiple access devices send messages associated with the same service, different access devices can determine different identifiers with similar functions to the second identifier (or different second identifiers). Any two access devices can determine different identifiers with similar functions to the second identifier. Alternatively, in scenarios where one access device sends multiple messages associated with the same service, that access device can also determine different identifiers with similar functions to the second identifier to carry multiple messages associated with the same service. This allows the first device to determine whether to respond to messages associated with the same service, such as paging messages, sent from the same or different access devices based on the second identifier, thereby flexibly adapting to the needs of different services or application scenarios.

[0009] In one possible design, the communication method may further include: receiving a first identifier and first indication information, wherein the first indication information is used to indicate that a first message and a second message need to be responded to by a first device, the first message being a message associated with a first service sent by a first access device, and the second message being a message associated with the first service sent by a second access device. Thus, the first access device can receive the first identifier and first indication information sent from a core network element or other access device, thereby determining the second identifier so that the first device can respond to the first message.

[0010] In one possible design, the first identifier and the first indication information are carried in the first service request, which is used to request the first service.

[0011] In one possible design, the communication method may further include receiving second indication information, which is used to determine a second identifier. Therefore, the first access device may also receive second indication information sent from a core network element or other access device to determine the second identifier, enabling the first device to respond to the first message.

[0012] In one possible design, the second indication information is used to indicate at least one of the following: the location index of the first access device among the plurality of access devices that send the message associated with the first service, the third identifier in the message associated with the first service sent by the second access device, or the second identifier, wherein the plurality of access devices includes the second access device, and the third identifier is different from the second identifier.

[0013] Secondly, a communication method is provided. This method can be executed by a first device, or by a component of the first device, such as a processor, chip, or chip system of the first device, or by a logic module or software capable of implementing all or part of the first device. Taking the application of this method to the first device or a chip in the first device as an example, the method includes: receiving a first message, the first message being associated with a first identifier, the first identifier being used to identify a first service, and the first message including a second identifier; and determining whether to respond to the first message based on the second identifier.

[0014] In one possible design, determining whether to respond to the first message based on the second identifier may include responding to the first message if the second identifier is different from the stored identifier.

[0015] In one possible design, responding to the first message may include: performing random access and / or performing data transmission related to the first service.

[0016] In one possible design, the communication method may further include: receiving a second message, the second message being associated with a first identifier, the second message including a third identifier, the third identifier being different from the second identifier.

[0017] Thirdly, a communication method is provided. This method can be executed by a core network element, a component of the core network element (such as a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the core network element. Taking the application of this method to a core network element or a chip within a core network element as an example, the method includes: sending a first identifier and first indication information to a first access device. The first identifier is used to identify a first service, and the first indication information is used to indicate that a first message and a second message need to be responded to by a first device. The first message is a message associated with the first service sent by the first access device, and the second message is a message associated with the first service sent by a second access device. Communication with the first access device is then established.

[0018] In one possible design, the communication method may further include: receiving a third identifier of the second access device, wherein the third identifier is an identifier carried in the second message.

[0019] In one possible design, the communication method may further include: sending a second indication message to a first access device, the second indication message being used to determine a second identifier, the second identifier being an identifier carried in a first message.

[0020] In one possible design, the second indication information is used to indicate at least one of the following: the location index of the first access device among the multiple access devices that send the message associated with the first service, a third identifier, or a second identifier, wherein the third identifier is an identifier carried in the second message, and the multiple access devices include the second access device.

[0021] The description of the technical effects of the method described in the second or third aspect can be found in the description of the relevant technical effects of the method described in the first aspect, and will not be repeated here.

[0022] Fourthly, a communication method is provided. This method can be executed by a core network element, or by a component of the core network element, such as a processor, chip, or chip system of the core network element. It can also be implemented by a logic module or software capable of implementing all or part of the core network element. Taking the application of this method to a core network element or a chip within a core network element as an example, the method includes: sending a first service request to a first access device, the first service request including a first identifier; and sending a second service request to the first access device, the second service request including a fourth identifier, the first identifier and the fourth identifier being used to identify the first service.

[0023] In this method, the core network element can send multiple service requests associated with the same service to the same access device. However, the service identifiers that identify the same service in different service requests are different. That is, the same service can correspond to multiple service identifiers. This allows the first access device to use different service identifiers that identify the same service to carry in the message associated with the first service and send it to the first device. This enables the first device to respond to the message associated with the same service from the same access device according to the different service identifiers.

[0024] In one possible design, the communication method may further include: determining that the first service is a service that needs to be repeatedly responded to by the first device. Therefore, the core network element can determine whether to send a different identifier to the access device to identify the first service based on the first service.

[0025] In one possible design, the communication method may further include sending a third service request to a second access device, the third service request including a fifth identifier, which also identifies the first service. Thus, the core network element can also send different service identifiers containing the identifier of the first service to different access devices, enabling the first device to respond to messages from different access devices related to the same service.

[0026] In one possible design, the first service request or the second service request further includes first indication information. The first indication information is used to indicate that the first message and the second message need to be responded to by the first device. The first message is a message associated with the first service sent by the first access device, and the second message is a message associated with the first service sent by the second access device.

[0027] Fifthly, a communication method is provided. This method can be executed by a first access device, or by a component of the first access device, such as a processor, chip, or chip system of the first access device, or by a logic module or software capable of implementing all or part of the first access device. Taking the application of this method to a first access device or a chip in the first access device as an example, the method includes: receiving a first service request from a core network element, the first service request including a first identifier; receiving a second service request from a core network element, the first service request including a fourth identifier, the first identifier and the fourth identifier being used to identify the first service.

[0028] In one possible design, the first service request or the second service request further includes first indication information. The first indication information is used to indicate that the first message and the second message need to be responded to by the first device. The first message is a message associated with the first service sent by the first access device, and the second message is a message associated with the first service sent by the second access device.

[0029] In one possible design, the communication method may further include: sending a first message, the first message including an identifier associated with a first identifier; and sending a third message, the third message including an identifier associated with a fourth identifier, wherein the first message and the third message are messages related to the first service.

[0030] In one possible design, the communication method may further include: communicating with a first device, which is a device that responds to a first message and a third message.

[0031] The description of the technical effects of the method described in the fifth aspect can be found in the description of the relevant technical effects of the method described in the fourth aspect, and will not be repeated here.

[0032] Sixthly, a communication method is provided. This method can be executed by a first access device, or by a component of the first access device, such as a processor, chip, or chip system of the first access device, or by a logic module or software capable of implementing all or part of the first access device. Taking the application of this method to a first access device or a chip in the first access device as an example, the method includes: receiving a fifth identifier and first indication information, wherein the fifth identifier is used to identify a first service, and the first indication information is used to indicate that a first message and a second message need to be responded to by a first device, wherein the first message is a message associated with the first service sent by the first access device, and the second message is a message associated with the first service sent by a second access device; and sending a first message, wherein the first message includes a sixth identifier, the sixth identifier being used to identify the first service, and the sixth identifier being determined based on the fifth identifier and the first indication information.

[0033] In this method, the first access device can obtain a fifth identifier and a first indication information that identify the first service from the core network element and / or other access devices, so as to determine a sixth identifier based on the fifth identifier and the first indication information. The sixth identifier may be a service identifier that is different from the fifth identifier or the same as the fifth identifier, so that the first device can respond to the first message.

[0034] In one possible design, receiving the fifth identifier and the first indication information may include: receiving the fifth identifier from the second access device, wherein the fifth identifier is an identifier carried in the second message; and receiving the first indication information from the core network element.

[0035] In one possible design, receiving the fifth identifier and the first indication information may include: receiving the fifth identifier and the first indication information from the second access device, wherein the fifth identifier is an identifier carried in the second message.

[0036] In one possible design, receiving the fifth identifier and the first indication information may include: receiving the fifth identifier and the first indication information from the core network element, wherein the fifth identifier is an identifier carried in a second message.

[0037] In one possible design, the communication method may also include sending a sixth identifier to the core network element.

[0038] In a seventh aspect, a communication method is provided. This method can be executed by a core network element, or by a component of the core network element, such as a processor, chip, or chip system of the core network element, or by a logic module or software capable of implementing all or part of the core network element. Taking the application of this method to a core network element or a chip in a core network element as an example, the method includes: sending a first identifier and first indication information, wherein the first identifier is used to identify a first service, and the first indication information is used to indicate that a first message and a second message need to be responded to by a first device, wherein the first message is a message associated with the first service sent by a first access device, and the second message is a message associated with the first service sent by a second access device. Receiving a sixth identifier from the first access device, wherein the sixth identifier is used to identify the first service, and the sixth identifier is an identifier carried in the first message.

[0039] In one possible design, the communication method may further include: receiving a fifth identifier from a second access device, the fifth identifier being used to identify the first service, and the fifth identifier being an identifier carried in a second message.

[0040] Eighthly, a communication method is provided. This method can be executed by a first access device, or by a component of the first access device, such as a processor, chip, or chip system of the first access device, or by a logic module or software capable of implementing all or part of the first access device. Taking the application of this method to a first access device or a chip in the first access device as an example, the method includes: sending a first message, the first message including a first identifier, a seventh identifier, and third indication information, the first identifier being used to identify a first service, the seventh identifier being used to identify the first access device, and the third indication information being used to instruct a first device to respond to the first message sent by the first access device; and communicating with the first device.

[0041] In this method, each of the multiple access devices that send messages associated with the first service can jointly instruct the first device to respond to the messages associated with the first service from different access devices by means of the service identifier, the access device identifier, and the third indication information.

[0042] In one possible design, the communication method may further include: receiving a first identifier and a first indication information from a core network element or a second access device, wherein the first indication information is used to indicate that a first message and a second message need to be responded to by a first device, and the second message is a message associated with a first service sent by the second access device.

[0043] In one possible design, the communication method may further include: receiving a first identifier from a second access device.

[0044] In one possible design, the communication method may further include receiving third indication information from the second access device.

[0045] A ninth aspect provides a communication method, which can be executed by a first device, or by a component of the first device, such as a processor, chip, or chip system of the first device, or by a logic module or software capable of implementing all or part of the first device. Taking the method applied to a first device or a chip in the first device as an example, the method includes: receiving a first message, the first message including a first identifier, a seventh identifier, and third indication information, wherein the first identifier is used to identify a first service, the seventh identifier is used to identify a first access device, and the third indication information is used to instruct the first device to respond to the first message sent by the first access device. Determining whether to respond to the first message based on the first identifier, the seventh identifier, and the first indication information.

[0046] In one possible design, responding to the first message may include: performing random access and / or performing data transmission related to the first service.

[0047] Tenthly, a communication method is provided. This method can be executed by a core network element, or by a component of the core network element, such as a processor, chip, or chip system of the core network element, or by a logic module or software capable of implementing all or part of the core network element. Taking the application of this method to a core network element or a chip in a core network element as an example, the method includes: sending a first identifier and first indication information to a first access device, wherein the first identifier is used to identify a first service, the first indication information is used to indicate that a first message and a second message need to be responded to by a first device, the first message is a message associated with the first service sent by the first access device, and the second message is a message associated with the first service sent by a second access device. Communication with the first access device is also provided.

[0048] The description of the technical effects of the method described in the ninth or tenth aspect can be found in the description of the relevant technical effects of the method described in the eighth aspect, and will not be repeated here.

[0049] Eleventhly, a communication apparatus is provided for implementing the various methods described above. This communication apparatus may be a device, apparatus, or network element as described in any of the first to tenth aspects, or an apparatus containing such a device, apparatus, or network element, or an apparatus included in such a device, apparatus, or network element, such as a chip. The communication apparatus includes corresponding modules, units, or means for implementing the methods described in any of the first to tenth aspects. These modules, units, or means may be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.

[0050] In some possible designs, the communication device includes a processing module and a transceiver module. The processing module implements the processing functions of the device, apparatus, or network element described in any of the first to tenth aspects, while the transceiver module implements the transceiver functions of the device, apparatus, or network element described in any of the first to tenth aspects. Specific implementation details can be found in the relevant descriptions of the methods described in any of the first to tenth aspects, and will not be elaborated upon here.

[0051] In one possible design, the transceiver module may include a receiving module and a transmitting module. The transmitting module implements the transmitting function of the communication device described in the eleventh aspect, and the receiving module implements the receiving function of the communication device described in the eleventh aspect.

[0052] In one possible design, the communication device described in the eleventh aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device described in the eleventh aspect can perform any of the methods described in the first to tenth aspects.

[0053] In a twelfth aspect, a communication device is provided (e.g., the communication device may be a chip or a chip system). The communication device includes a processor for implementing the functions involved in any of the preceding aspects.

[0054] In one possible design, the communication device may further include a memory for storing necessary program instructions and data. A processor is coupled to the memory and is used to execute the computer program or instructions stored in the memory, causing the communication device to perform the method described in any of the possible implementations of the first to tenth aspects.

[0055] In one possible design, the communication device described in the twelfth aspect may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the twelfth aspect and other communication devices.

[0056] In one possible design, the processor can be integrated with the memory.

[0057] In some possible designs, when the device is a chip system, it can be composed of chips or contain chips and other discrete components.

[0058] In a thirteenth aspect, a communication device is provided, the communication device including a processor and an interface circuit, the interface circuit being configured to receive signals from other communication devices outside the communication device and transmit them to the processor or to send signals from the processor to other communication devices outside the communication device, the processor being configured to implement the method as described in any one of the possible implementations of the first to tenth aspects via logic circuits or execution code instructions.

[0059] It is understood that when the communication device provided in either the twelfth or thirteenth aspect is a chip, the aforementioned transmitting action / function can be understood as an output, and the aforementioned receiving action / function can be understood as an input.

[0060] In a fourteenth aspect, a computer-readable storage medium is provided that stores a computer program or instructions that, when executed on a communication device, enable the communication device to perform the method described in any one of the first to tenth aspects.

[0061] In a fifteenth aspect, a computer program product comprising instructions is provided, including computer program code, which, when executed on a communication device, enables the communication device to perform the method described in any one of the first to tenth aspects.

[0062] In a sixteenth aspect, a communication system is provided, comprising: a first access device for implementing the method of the first aspect, a first apparatus for implementing the method of the second aspect, and a core network element for implementing the method of the third aspect. Alternatively, it may include a core network element for implementing the method of the fourth aspect and a first access device for implementing the method of the fifth aspect. Alternatively, it may include a first access device for implementing the method of the sixth aspect and a core network element for implementing the method of the seventh aspect. Alternatively, it may include a first access device for implementing the method of the eighth aspect, a first apparatus for implementing the method of the ninth aspect, and a core network element for implementing the method of the tenth aspect.

[0063] In a seventeenth aspect, a communication chip is provided, wherein instructions are stored that, when the chip is operated on a communication device, cause the method described in any one of the first to tenth aspects above to be implemented. Attached Figure Description

[0064] Figure 1 is a schematic diagram of an RFID access process provided in an embodiment of this application;

[0065] Figure 2 is a schematic diagram of an A-IoT device access process provided in an embodiment of this application;

[0066] Figure 3 is a schematic diagram of a repeat paging process provided in an embodiment of this application;

[0067] Figure 4 is a schematic diagram of a proximity positioning service and pipeline scenario provided in an embodiment of this application;

[0068] Figure 5 is a schematic diagram of the architecture of an A-IoT communication system provided in an embodiment of this application;

[0069] Figures 6 to 9 are schematic diagrams of network topology architectures suitable for A-IoT communication systems provided in the embodiments of this application;

[0070] Figures 10 to 12 are schematic diagrams of the O-RAN architecture applicable to communication systems provided in the embodiments of this application;

[0071] Figures 13 to 21 are schematic flowcharts of the communication method provided in the embodiments of this application;

[0072] Figures 22 and 23 are schematic diagrams of the communication device provided in the embodiments of this application. Detailed Implementation

[0073] This application will present various aspects, embodiments, or features relating to systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that individual systems may include additional devices, components, modules, etc., and / or may not include all the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Furthermore, combinations of these approaches are also possible.

[0074] The technical solutions of this application embodiment can be applied to various communication systems, such as Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access (CDMA) system, Wireless Local Area Network (WLAN), Wireless Fidelity (Wi-Fi) system, wired network, Vehicle to Everything (V2X) communication system, Device-to-Device (D2D) communication system, Vehicle-to-Everything (V2X) communication system, 4th generation (4G) mobile communication system, such as Long Term Evolution (LTE) system, Worldwide Interoperability for Microwave Access (WiMAX) communication system, 5th generation (5G) mobile communication system, such as New Radio (NR) system, and future communication systems.

[0075] To better understand the embodiments of this application, the following points are explained before introducing the embodiments of this application.

[0076] First, in the embodiments of this application, "for indicating" can include both direct and indirect indication. When describing a certain "indication information" for indicating A, it can include whether the indication information directly indicates A or indirectly indicates A, but does not necessarily mean that the indication information carries A.

[0077] The information indicated by the instruction is called the information to be instructed. In the specific implementation process, 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 be indirectly indicated 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 indicated, 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. At the same time, common parts of various pieces of information can be identified and indicated uniformly to reduce the instruction overhead caused by individually indicating the same information.

[0078] Furthermore, the specific indication method can also be any existing indication method, such as, but not limited to, the above-mentioned indication methods and their various combinations. Specific details of various indication methods can be found in existing technologies, and will not be repeated here. As described above, for example, when multiple pieces of information of the same type need to be indicated, the indication methods for different pieces of information may differ. In the specific implementation process, the required indication method can be selected according to specific needs. This application embodiment does not limit the selected indication method; therefore, the indication methods involved in this application embodiment should be understood to cover various methods that enable the party to be indicated to obtain the information to be indicated.

[0079] The information to be instructed can be sent as a whole or divided into multiple sub-information messages, and the sending period and / or timing of these sub-information messages can be the same or different. This application does not limit the specific sending method. The sending period and / or timing of these sub-information messages can be predefined, for example, according to a protocol, or configured by the transmitting device by sending configuration information to the receiving device.

[0080] Second, in the embodiments of this application, the terms "first," "second," and various numerical designations are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. For example, "first device" and "second device" are only used to distinguish different devices and do not limit their order. Those skilled in the art will understand that the terms "first," "second," etc., do not limit the quantity or execution order, and that "first," "second," etc., are not necessarily different.

[0081] Third, in the embodiments of this application, descriptions such as "when," "under the circumstances," "if," and "if" all refer to the device making corresponding processing under certain objective circumstances. They are not time limits, nor do they require the device to make a judgment action during implementation, nor do they imply any other limitations.

[0082] Fourth, in the embodiments of this application, the words "exemplary" or "for example" are used to indicate that they are examples, illustrations, or descriptions. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design options. Specifically, the use of the words "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0083] In this application, "sending information" can be understood as one device sending information to another device, or it can also be understood as one logical module within a device sending information to another logical module. For example, "access network device sending information" can be understood as an access network device sending information to another device (such as a terminal device), or it can be understood as logical module 1 in the access network device sending information to logical module 2 in the access network device.

[0084] In this application, "receiving information" can be understood as one device receiving information from another device, or it can also be understood as a logical module within a device receiving information from another logical module. For example, "access network device receiving information" can be understood as the access network device receiving information from another device (such as a terminal device), or it can be understood as logical module 1 in the access network device receiving information from logical module 2 in the access network device.

[0085] In this application, phrases such as "sending information to... (e.g., a terminal device)" or related illustrations in the accompanying drawings can be understood as the destination of the information being a terminal. This can include sending information directly or indirectly to a terminal. Similarly, phrases such as "receiving information from... (e.g., a terminal device)," "receiving information from... (e.g., a terminal device)," or "receiving information sent (e.g., by a terminal device)," or related illustrations in the accompanying drawings, can be understood as the source of the information being a terminal. This can include receiving information directly or indirectly from a terminal. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be interpreted similarly and will not be elaborated further here.

[0086] The related technologies involved in the embodiments of this application.

[0087] 1. Radio Frequency Identification (RFID)

[0088] An RFID system consists of an interrogator and tags. The interrogator reads information from the tags or writes information to the tags. The interrogator and tags communicate non-contactly. Tags have simple functions, requiring excitation from the interrogator to transmit information; that is, the tag converts the wireless signals emitted by the interrogator into energy to power itself. Tags support power consumption in the microwatt or hundreds of microwatts range, limiting their ability to support complex designs.

[0089] A reader / writer can also be called a reader, exciter, excitation source, radio frequency source, or interrogator, etc., without limitation. A tag uses a low-precision, low-power, medium-to-low frequency ring oscillator or a completely oscillator-less receiver to receive downlink signals. Tags can also be called low-power terminal devices, tag devices, passive devices, etc.

[0090] If RFID is applied to mobile communication systems, such as 5G systems, then base stations can act as readers, fulfilling their functions. Currently, RFID technology can be used to identify targets; for example, readers can interact with electronic tags to manage them.

[0091] The basic inventory (access process) for RFID is shown in Figure 1, including:

[0092] S101, The reader sends a select command to the tag. Correspondingly, the tag receives the select command from the reader.

[0093] The selection command is used to select one or a group of tags for access. The selection command may include a selected (SL) identifier (or an inventoried identifier) ​​and a mask.

[0094] The tag receives a selection command from the reader and determines whether the information stored in the corresponding location of its own storage area matches the mask information in the selection command. If they match, the tag considers itself to meet the read / write selection criteria. At this point, the tag can set the status of a certain disk storage flag, for example, setting the first disk storage flag from state A to state B. Conversely, tags that do not match the reader's selection criteria will set the first disk storage flag from state B to state A. Here, A / B can also be replaced with 0 / 1; there is no restriction on this.

[0095] S102, The reader sends a query command to the tag. Correspondingly, the tag receives the query command from the reader.

[0096] The query command is used to initialize a storage cycle. The query command carries flag information (such as selection identifier or storage identifier) ​​and parameter Q, which is used to calculate the total number of time slots allocated by the tag reader for random access.

[0097] Tags that meet the above reader selection criteria determine whether their own flag information is consistent with the flag information in the reader query command. If they are consistent, the tag calculates the access time slot range [0, 2] based on the Q value. Q -1]. Labels can be in [0, 2]. QA random value k is selected from [-1] and stored as a counter. Whenever the tag receives a query response (QueryRep) command, counter = counter - 1. When counter equals 0, the tag can send a random number, such as a 16-bit random number or a pseudo-random number (RN16).

[0098] In one possible scenario, if the time slot corresponding to the reader sending the query is 0, then a tag with an initial counter value of 0 is generated, and the tag can initiate access as soon as it receives the query.

[0099] S103, The tag sends RN16 to the reader. Correspondingly, the reader receives RN16 from the tag.

[0100] RN16 is used to indicate the tag's temporary ID. When a tag receives a query command, if the tag confirms that counter = 0, it selects a 16-bit random number as RN16 and sends this RN16 back to the reader. If the reader detects that the tag has sent back RN16, it means that the inventory process is proceeding normally, and the reader executes the next action. Specifically, RN16 is carried in message (Msg)3, which is also known as message three or the third message.

[0101] S104. The reader sends an acknowledgment message (ACK) to the tag. Correspondingly, the tag receives the acknowledgment message from the reader.

[0102] ACK is used to indicate that the reader has successfully received the RN16 sent by the tag. The ACK includes a 16-bit random number previously sent by the tag, which the tag uses to check whether the ACK matches.

[0103] S105. The tag sends uplink data to the reader. Correspondingly, the reader receives the uplink data from the tag.

[0104] If the 16-bit random number included in the tag acknowledgment ACK is the same as the RN16 sent by the tag, it indicates that the tag has successfully accessed the network. Then, the tag sends uplink data to the reader, such as the electronic product code (EPC). The EPC is used to indicate the tag's real ID.

[0105] Optionally, after the tag completes random access, the following interaction process still exists between the tag and the reader:

[0106] S106. The reader sends a first instruction to the tag. Correspondingly, the tag receives the first instruction from the reader.

[0107] The first instruction is used to instruct the tag to perform a read operation, a write operation, or a read-write operation, etc. After receiving the first instruction, the tag responds to the first instruction by performing a read operation, a write operation, or a read-write operation, etc.

[0108] S107. The tag sends a first response to the reader. Correspondingly, the reader receives the first response from the tag.

[0109] The first response is the response message to the first instruction, used to instruct the tag to complete an operation, write operation, or read / write operation, etc.

[0110] After the reader finishes processing a tag, it can send a QueryRep command to the tag. Upon receiving the QueryRep command, the tag communicating with the reader will toggle its storage flag bit, for example, setting it from B to A. This QueryRep signaling can also be used to trigger the next access opportunity; that is, tags with a non-zero counter will decrement by 1, and when counter = 0, the tag can initiate the next random access.

[0111] 2. A-IoT technology

[0112] A-IoT is based on cellular network communication infrastructure and consists of readers (such as network devices or terminal devices) and passive / semi-passive / active A-IoT terminal devices. In other words, both readers and A-IoT terminal devices can be devices within the cellular network. For example, the functionality of a reader can be implemented by network devices, such as base stations, and A-IoT terminal devices can be implemented by terminal devices within the cellular network, such as ultra-low power, ultra-low complexity IoT terminal devices.

[0113] The reader / writer communicates with the A-IoT terminal device without contact, thereby reading information from the A-IoT terminal device and / or writing information that needs to be stored to the A-IoT terminal device. The A-IoT terminal device, also known as a first-type terminal device, is an extremely low-power, extremely low-complexity IoT terminal device; or, in other words, a first-type terminal device can be a device with A-IoT terminal device functionality. Currently, the 3rd Generation Partnership Project (3GPP) standard agrees that 5G A-IoT can include the following three types of A-IoT devices:

[0114] Device A (similar to a passive A-IoT terminal device): It has no energy storage, cannot generate signals independently, and uses reflection transmission;

[0115] Device B (similar to a semi-passive A-IoT terminal device): It has energy storage, cannot generate signals independently, and uses reflection transmission;

[0116] Device C (similar to an active A-IoT terminal device): It has energy storage, can generate signals independently, and has active radio frequency components for transmission.

[0117] A-IoT technology can be used to achieve one or more of the following business functions: inventory, positioning, sensing, and command. Typical application scenarios include logistics, warehousing, industrial manufacturing, identity recognition, and environmental monitoring.

[0118] For example, inventory management can be achieved by using a reader (which can be a network device / terminal device) to access A-IoT terminal devices within the coverage area. Once successfully connected, the device needs to send its unique identifier (which the network can recognize, such as EPC in RFID) to the reader.

[0119] Positioning can be achieved by using positioning signals to locate the position of A-IoT terminal devices.

[0120] Sensing can be achieved by A-IoT terminal devices reporting sensor data to the base station, such as temperature data.

[0121] Commands can be operation instructions, such as write and lock. The write process is when a network device (such as a base station) sends a downlink command and data, instructing the A-IoT terminal device to write the data into its own memory. The lock process is when a downlink command is sent, instructing the A-IoT terminal device to lock the location at a specified address in the memory, making the contents of that memory area unchangeable and / or unreadable.

[0122] 3. Device access process in A-IoT

[0123] As shown in Figure 2, the air interface / access stratum (AS) process of an A-IoT device in an A-IoT communication system includes:

[0124] S201, the reader sends an A-IoT paging message to the A-IoT device. Correspondingly, the A-IoT device receives the A-IoT paging message from the reader.

[0125] For example, the reader can be a base station or a terminal device. The reader can send an A-IoT paging message according to the service request from the core network, indicating the A-IoT device that needs to respond.

[0126] At the AS layer, the function of A-IoT paging messages is to indicate which A-IoT devices need to respond. For A-IoT paging messages, an identifier (ID) may be needed to identify the devices / groups of devices included or associated with this trigger message (e.g., a single device, a group of devices, or all devices). Several possible design schemes are possible, and no limitation is made on them.

[0127] In one possible design, the A-IoT paging message may contain a single A-IoT device ID.

[0128] In one possible design, the A-IoT paging message contains a group ID mapped to multiple A-IoT devices.

[0129] One possible design is an A-IoT paging message that does not contain any identifier, which instructs all A-IoT devices that can receive the A-IoT paging message to respond.

[0130] One possible design includes an A-IoT paging message containing multiple A-IoT device identifiers.

[0131] Optionally, for A-IoT paging messages, it can also be indicated that the device can determine, without limitation, the resources (such as time-domain and / or frequency-domain resources) to be used for D2R response messages based on this information.

[0132] Optionally, the paging function for A-IoT devices can be understood as not supporting traditional paging messages, traditional paging timings, and traditional discontinuous reception (DRX) from NR; this will not be implemented. It can be assumed that A-IoT devices can receive A-IoT paging messages as long as they have sufficient power.

[0133] In this embodiment of the application, "A-IoT paging message" can be replaced with "(initial) trigger message", and there is no limitation on this.

[0134] S202, the A-IoT device sends D2R data to the reader. Correspondingly, the reader receives D2R data from the A-IoT device.

[0135] For example, an A-IoT device triggered by an A-IoT paging message can perform D2R data (such as device ID) transmission through the A-IoT random access procedure or without using the A-IoT random access procedure (such as contention-free resolution).

[0136] S203, Data transmission between the reader and the A-IoT device.

[0137] S203 may include S203-1 and / or S203-2, wherein,

[0138] S203-1 represents possible R2D data transmission between the reader / writer and the A-IoT device, for example, for sending commands such as read, write, lock, deactivate, and sense commands.

[0139] S203-2 specifies possible D2R data transmission between A-IoT devices and readers, such as responses to commands, like data read by a read command, success / failure feedback for a write command, etc.

[0140] Then, the above process can support inventory and command application scenarios in the following ways:

[0141] For the "inventory-only" scenario, the baseline solutions include S201 and S202.

[0142] For the "inventory and command" scenario, the baseline scheme includes steps S201, S202, S203-1, and S203-2.

[0143] For "command-only" scenarios:

[0144] It can also be supported by a baseline scheme having steps S201, S202, S203-1 and S203-2.

[0145] In addition, another candidate solution to support the "command-only" scenario is as follows:

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

[0147] Step S202: The A-IoT device performs possible D2R data transmission (e.g., device ID or corresponding response to a command) with or without using the A-IoT random access procedure.

[0148] 4. A-IoT random access

[0149] The A-IoT random access procedure is used for A-IoT devices to access the network for data transmission.

[0150] A-IoT random access is triggered by a reader or writer, including access triggered by a single A-IoT device, a group of A-IoT devices, or all A-IoT devices under the coverage of the reader or writer. The time slot Aloha (lotted-ALOHA) is the baseline of the A-IoT random access process.

[0151] In the access process shown in Figure 2, when the A-IoT device responds to the A-IoT paging message, the A-IoT device executes the following process:

[0152] Step 1: Random access type and access timing / resource determination:

[0153] (1) If random access is contention-free access:

[0154] Select the appropriate D2R timing / resources;

[0155] Skip the race resolution in step 2 and proceed to step 3 to perform data transmission.

[0156] (2) If it is contention-based random access:

[0157] Determining / selecting the timing / resources for access, such as random selection;

[0158] Step 2 of the competition resolution procedure.

[0159] Step 2: Contention-based random access contention resolution:

[0160] - Regarding contention resolution, there are two possible solutions:

[0161] Option 1: A-IoT Msg1 has no data

[0162] A-IoT Msg1: When an A-IoT device recognizes the start of its access occasion, it sends a randomly generated ID to the reader. The steps for generating the random ID are specified, such as random generation or generation based on the device ID. The size of the random ID is also not limited, for example, it can be a 16-bit random number.

[0163] A-IoT Msg2: The reader responds with a random ID that has been successfully received.

[0164] If the A-IoT device receives A-IoT Msg2 containing a random ID, and that random ID is the same as the one previously sent in A-IoT Msg1, then the race condition is considered resolved successfully.

[0165] It should be understood that A-IoT Msg2 is used for contention resolution because it is assumed that the size of the random ID in A-IoT Msg1 should be sufficient for contention resolution purposes. It is highly unlikely that A-IoT devices choosing the same access timing / resources will send the same random ID value in A-IoT Msg1; therefore, the range of random ID values ​​can be considered sufficiently large.

[0166] Option 2: A-IoT Msg1 has data

[0167] A-IoT Msg1: When an A-IoT device recognizes the start of its own access event, it sends A-IoT Msg1 containing upper-layer data, which can be the device ID and / or any other upper-layer data. Optionally, in Scheme 2, the A-IoT Msg1 may or may not include a random ID.

[0168] A-IoT Msg2: The reader can respond with the successfully received random ID and / or device ID (partial or complete) and / or ACK, or it can choose not to respond. If Msg1 does not receive a signal indicating failure, reconnection, or retransmission, it is considered that the access is successful, the data transmission is successful, or the service is successful.

[0169] If an A-IoT device receives an A-IoT Msg2 containing a random ID and / or a device ID (partial or complete) and / or an ACK, and this information is a part of the previously sent information in A-IoT Msg1 or information generated based on A-IoT Msg1 (e.g., a hash function on Msg1), then the A-IoT device considers the race to be resolved successfully.

[0170] Step 3, Data Transmission:

[0171] If contention-based random access is used, or if contention-free access is used, the A-IoT device can perform upper-layer data transmission with the reader after it considers the contention to be resolved successfully. The upper-layer data transmission may be the device ID and / or any other upper-layer data (if any).

[0172] In step 3, it can be understood that subsequent R2D transmissions after a D2R transmission do not always need to be sent. The use / existence of subsequent R2D transmissions requires further research; for example, handling retransmissions or reconnections after a D2R transmission failure could be considered (due to various reasons).

[0173] Currently, to prevent A-IoT devices from failing to receive paging messages, a paging retransmission scheme has been introduced, as shown in Figure 3. Reader 1 and Reader 2 respectively receive service requests from the CN with the same session ID. Based on the service request, they repeatedly send paging messages to the same A-IoT device. The repeatedly sent paging messages contain the same session ID. However, to prevent the A-IoT device from repeatedly responding to multiple paging messages with the same session ID, after the A-IoT device responds to a paging message containing a session ID and completes a service once, it will not respond to any subsequent paging messages containing the same session ID.

[0174] However, in some scenarios, such as proximity positioning services and pipeline scenarios as shown in Figure 4, the same A-IoT device may need to respond to paging messages from different readers but associated with the same session ID. Alternatively, the same A-IoT device may need to repeatedly respond to paging messages from the same reader but associated with the same session ID. Currently, A-IoT devices cannot determine whether they need to repeatedly respond to paging messages from the same reader or different readers for the same service, thus failing to flexibly adapt to the needs of different services or application scenarios. In other words, the above-mentioned response method of A-IoT devices is not applicable in some service or application scenarios that require repeated responses to the same paging messages, such as proximity positioning services or pipeline scenarios.

[0175] Therefore, embodiments of this application provide a communication method and apparatus that enable A-IoT devices to determine whether they need to repeatedly respond to paging messages for the same service sent by the same reader or different readers.

[0176] Please refer to Figure 5, which is a schematic diagram of the architecture of an A-IoT communication system provided in an embodiment of this application. As shown in Figure 5, the A-IoT communication system includes: a first device, an access device, and core network elements. The elements can communicate directly or indirectly with each other, and there is no limitation on this.

[0177] The first device can be a terminal device with extremely low power consumption and / or extremely low complexity, or a device within a terminal device with extremely low power consumption and / or extremely low complexity. The first device can be referred to as a terminal device in the Internet of Things (IoT), a first-class terminal device, or an A-IoT device, A-IoT terminal, passive A-IoT, terminal device, terminal equipment, passive tag, tag, tag device, passive device, passive equipment, semi-active device, battery-free terminal / device, battery-less terminal / device, backscatter terminal / device, backscatter terminal, passive IoT, reflector, reflective terminal, or ambient signal device, etc.

[0178] Access devices (such as the first access device and the second access device) serve as readers in the A-IoT communication system. They can be network devices or second-type terminal devices, and there is no limitation on which one is used.

[0179] Network equipment, also known as radio access network (RAN) equipment, RAN nodes, RAN entities, or access nodes, is located on the network side of the aforementioned communication system. It assists terminal devices in achieving wireless access and is a device with wireless transceiver capabilities, or a chip or chip system that can be installed in the device. This network equipment includes, but is not limited to: base stations, evolved NodeBs (eNodeBs), access points (APs), transmission reception points (TRPs), next-generation NodeBs (gNBs), base stations in future mobile communication systems, or access nodes in Wi-Fi systems. Network equipment can be macro base stations, micro base stations or indoor stations, relay nodes or donor nodes, open radio access networks (ORANs), or wireless controllers in centralized radio access network (CRAN) scenarios. Optionally, RAN nodes can also be servers, wearable devices, vehicles, or in-vehicle equipment. For example, network equipment in V2X technology can be roadside units (RSUs). All or part of the functions of the network device in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform). The network device in this application can also be a logical node, logical module, or software capable of implementing all or part of the functions of a network device.

[0180] In another possible scenario, multiple RAN nodes collaborate to assist terminal devices in achieving wireless access, with different RAN nodes each implementing a portion of the base station's functions. For example, RAN nodes can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs), etc. CUs and DUs can be set up separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0181] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. 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 and hardware modules.

[0182] The form of the network device is not limited in the embodiments of this application. The device used to implement the function of the network device can be the network device itself, or it can be a device that supports the network device in implementing the function, such as a chip system. The device can be installed in the network device or used in conjunction with the network device.

[0183] The second type of terminal equipment can be a terminal with transceiver functions, or it can be a chip or chip system installed in the terminal. This second type of terminal equipment can also be called user equipment (UE), access terminal, subscriber unit, user station, mobile station (MS), mobile station, remote station, remote terminal, mobile device, user terminal, terminal equipment, wireless communication equipment, user agent, or user device. The second type of terminal device in the embodiments of this application can be a mobile phone, cellular phone, smartphone, tablet computer, wireless data card, personal digital assistant (PDA), wireless modem, handset, laptop computer, machine type communication (MTC) terminal, computer with wireless transceiver function, virtual reality (VR) terminal, augmented reality (AR) terminal, smart home device (e.g., refrigerator, television, air conditioner, electricity meter, etc.), intelligent robot, robotic arm, workshop equipment, wireless terminal in autonomous driving, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical care, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, vehicle terminal, or roadside unit with terminal function. The second type of terminal equipment in this application can also be an onboard module, onboard unit, onboard component, onboard chip, or onboard unit that is built into a vehicle as one or more components or units. The second type of terminal equipment can also be other devices with terminal functions; for example, it can also be a device that functions as a terminal in D2D communication.

[0184] The embodiments of this application do not limit the device form of the first type of terminal and the second type of terminal. The device for implementing the function of the first type of terminal can be a terminal device; it can also be a device that supports the terminal device in implementing the function, such as a chip system. This device can be installed in the terminal device or used in conjunction with the terminal device. In the embodiments of this application, the chip system can be composed of chips or can include chips and other discrete devices. The device for implementing the function of the second type of terminal can be a terminal device; it can also be a device that supports the terminal device in implementing the function, such as a chip system. This device can be installed in the terminal device or used in conjunction with the terminal device. In the embodiments of this application, the chip system can be composed of chips or can include chips and other discrete devices.

[0185] A core network element is a device deployed in the core network to provide services to the first device; it can also be called a core network equipment. In systems employing different radio access technologies, the names of core network elements with similar wireless communication functions may differ. In this embodiment, the core network element can be an access and mobility management element. For example, when the method of this embodiment is applied to a 5G system, the access and mobility management element can be an access and mobility management function (AMF). When the method of this embodiment is applied to an LTE system, the access and mobility management element can be a mobility management entity (MME). Another example is that the core network element is an A-IoT management function (A-IoT MF) defined in an A-IoT communication system. For ease of description, in this embodiment, the aforementioned devices that can provide services to the first device are collectively referred to as core network elements.

[0186] It should be noted that the solutions in the embodiments of this application can also be applied to other communication systems, and the corresponding names can be replaced by the names of the corresponding functions in other communication systems. In addition, the communication system shown in Figure 5 may also include other devices or core network elements, and there are no limitations on this.

[0187] For the communication system shown in Figure 5, the following are some applicable network topologies:

[0188] As shown in network topology 1 in Figure 6, taking the access device as the network device and the first device as the A-IoT device as an example, the A-IoT device and the network device communicate directly and bidirectionally. The communication between the network device and the A-IoT device includes A-IoT data and / or signaling. This topology includes network devices sending data to the A-IoT device and network devices receiving data from the A-IoT device, that is, there is uplink and downlink data / signaling between the network device and the A-IoT device.

[0189] As shown in network topology 2 in Figure 7, taking the access device as the network device and the first device as the A-IoT device as an example, the network device and the A-IoT device communicate bidirectionally through an intermediate node. In this topology, the intermediate node can be a repeater, an integrated access backhaul (IAB) node, a UE, etc., enabling environmental IoT. The intermediate node transmits A-IoT data and / or signaling between the network device and the A-IoT device.

[0190] As shown in network topology 3 in Figure 8, taking the access device as the network device and the first device as the A-IoT device as an example, the network device and the A-IoT device communicate bidirectionally through auxiliary nodes. As shown in Figure 8(a), the A-IoT device sends data / signaling to the network device and receives data / signaling from the auxiliary node; or as shown in Figure 8(b), the A-IoT device receives data / signaling from the network device and sends data / signaling to the auxiliary node. In this topology, the auxiliary node can be a repeater, IAB, UE, etc., and these devices enable the Internet of Things (IoT).

[0191] As shown in network topology 4 in Figure 9, taking the access device as the terminal device (such as the second type of terminal device mentioned above) and the first device as the A-IoT device as an example, the A-IoT device and the terminal device communicate bidirectionally. The communication between the terminal device and the A-IoT device includes A-IoT data and / or signaling.

[0192] The O-RAN architecture applicable to network devices in the above communication systems is described below.

[0193] For example, Figure 10 is a schematic diagram of an O-RAN architecture based on a RAN intelligent controller (RIC) suitable for the above-mentioned communication system provided by an embodiment of this application. As shown in Figure 10, the O-RAN architecture includes: RU, DU, CU, near-real-time RIC (near-RT RIC) and non-real-time RIC (non-RT RIC), wherein CU includes CU-CP and CU-UP.

[0194] Near real-time (NRT) RICs are used for model training and inference. For example, they are used to train artificial intelligence (AI) models and then use these AI models for inference. NRT RICs can obtain network-side and / or terminal-side information from network devices (e.g., CUs, CU-CPs, CU-UPs, DUs, and / or RUs) and / or terminal devices. This information can be used as training data or inference data. Optionally, the NRT RIC can deliver inference results to network devices and / or terminal devices. Optionally, inference results can be exchanged between CUs and DUs, and / or between DUs and RUs. For example, the NRT RIC delivers inference results to the DU, and the DU sends them to the RU.

[0195] Non-real-time RICs are used for model training and inference. For example, they are used to train AI models and then use those models for inference. Non-real-time RICs can obtain network-side and / or terminal-side information from network devices (e.g., CUs, CU-CPs, CU-UPs, DUs, and / or RUs) and / or terminal devices. This information can be used as training data or inference data, and the inference results can be delivered to the network devices and / or terminal devices. Optionally, inference results can be exchanged between CUs and DUs, and / or between DUs and RUs; for example, a non-real-time RIC delivers inference results to a DU, which then forwards them to an RU.

[0196] Near real-time RICs and non-real-time RICs can also be configured as separate network elements. Optionally, near real-time RICs and non-real-time RICs can also be part of other devices. For example, near real-time RICs can be set in network devices (e.g., CU, DU), while non-real-time RICs can be set in operation administration and maintenance (OAM) systems, cloud servers, core network devices, or other network devices.

[0197] In a communication system, network elements are connected via interfaces (e.g., NG, Xn) or over-the-air interfaces. These network element nodes, such as core network equipment, network equipment, terminal equipment, or one or more devices in the OAM (Operational Network Module), are equipped with one or more AI modules. Network equipment can be a single RAN node or can comprise multiple RAN nodes, for example, including CU and DU. The CU and / or DU can also be equipped with one or more AI modules. Optionally, the CU can be further divided into CU-CP and CU-UP. One or more AI models are configured in the CU-CP and / or CU-UP.

[0198] AI modules are used to implement corresponding AI functions. AI modules deployed in different network elements can be the same or different. Depending on the parameter configuration, the AI ​​module can implement different functions. The AI ​​module model can be configured based on one or more of the following parameters: structural parameters (e.g., at least one of the following: number of neural network layers, neural network width, inter-layer connections, neuron weights, neuron activation function, or biases in the activation function), input parameters (e.g., the type and / or dimension of the input parameters), or output parameters (e.g., the type and / or dimension of the output parameters). The biases in the activation function can also be referred to as the neural network biases.

[0199] An AI module can have one or more models. A model can infer an output, which includes one or more parameters. The learning, training, or inference processes of different models can be deployed on different nodes or devices, or they can be deployed on the same node or device.

[0200] This application also provides an architecture diagram of an O-RAN system applicable to the above-described communication system. As shown in Figure 11, the network device can be a RAN (e.g., an eNB, gNB, or access network device in a future mobile communication system). The network device can communicate with the core network device via a backhaul link and with the terminal device via an air interface.

[0201] In this network device, the BBU communicates with the core network via a backhaul link, and the RU communicates with at least one terminal device via an air interface. The BBU communicates with at least one RU via a fronthaul link. The BBU and RU may or may not be co-located. The BBU includes at least one CU and at least one DU, which can communicate via at least one midhaul link.

[0202] Figure 12 is a schematic diagram of the network element function division and protocol layer structure of an O-RAN device. As shown in Figure 12, it includes: network devices and a management system. In some examples, the CU 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 network device. The CU is connected to network nodes such as the core network through some interfaces, which can be interfaces such as E2 interfaces. Optionally, the CU can have some functions of the core network. The CU (e.g., the PDCP layer and higher layers) is connected to the DU (e.g., the radio link control (RLC) layer and lower layers) through some interfaces, which can be interfaces such as F1 interfaces. In some examples, these interfaces (e.g., the F1 interface) can provide control plane CU and user plane UP functions (e.g., interface management, system information management, terminal device context management, RRC message transmission, etc.). The F1 application protocol (F1AP) is the application protocol for the F1 interface, defining the F1 signaling procedures in some examples. The F1 interface supports the control plane F1-C and the user plane F1-U.

[0203] In some examples, 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 (AMF) network elements, such as the access and mobility management function (AMF) in a 5G system. The AMF network element is responsible for mobility management in the mobile network, such as terminal device location updates, terminal device registration with the network, and terminal device handover. 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. These network elements in the core network, such as the user plane function (UPF) in a 5G system, are responsible for data forwarding and receiving in terminal devices.

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

[0205] In some examples, a DU is a logical node that carries the RLC layer, medium access control (MAC) layer, higher physical layer (Higher PHY) layer, and other functions. In some examples, a DU can control at least one RU. 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.

[0206] In some examples, 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 3GPP TRP or RRH or other similar entity. In some examples, the Low-PHY includes PHY processing functions such as Fast Fourier Transform (FFT), Inverse Fast Fourier Transform (IFFT), digital beamforming, and filtering. The RU communicates with one or more terminal devices via a wireless link.

[0207] 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 the Lower-Layer Split CUS-Plane (LLS-CUS) interface. LLS-CUS may include LLS-C and LLS-U interfaces providing the control plane (CU) and user plane (UP), respectively. In some examples, the control plane (CP) refers to real-time control between the DU and RU. The DU and RU exchange management information via an LLS-M interface on the fronthaul link; the management plane (M-Plane) refers to non-real-time management operations between the DU and RU.

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

[0209] The communication method provided in the embodiments of this application will be described in detail below with reference to Figures 13-21.

[0210] For example, Figure 13 is a flowchart illustrating a communication method provided in an embodiment of this application. This communication method is illustrated using the communication between the first device, the access device, and the core network element shown in Figure 4 as an example. Of course, the subject executing the action of the first device in this method can also be a device / module in the first device, such as a chip, processor, or processing unit in the first device, and is not limited thereto; the subject executing the action of the access device in this method can also be a device / module in the access device, such as a chip, processor, or processing unit in the access device, and is not limited thereto; the subject executing the action of the core network element in this method can also be a device / module in the core network element, such as a chip, processor, or processing unit in the core network element, and is not limited thereto.

[0211] As shown in Figure 13, the communication method includes:

[0212] S1301, The first access device sends a first message. Correspondingly, the first device receives the first message.

[0213] The first message is the message associated with the first service, and it includes a second identifier. This can be understood as the message used to trigger / request / instruct the first service.

[0214] The first message can page or select one or more first devices to perform a first service, or one or more first devices can respond to the first message to perform a first service. For example, the first message can be used to instruct, trigger, or request a first device to access a first access device, or to instruct or trigger a first device to send uplink data related to the first service, or to page or select a first device, or to instruct, trigger, or request a first device to perform a first service, or to instruct a first device to access a first access device. For example, the first message can be a paging message, a select message, or an initial trigger message, etc.

[0215] In one possible design, the first message is associated with a first identifier, which is used to identify the first service. The first identifier can be an identification information generated by a core network element to identify the first service; for example, the first identifier can be a service identifier, a session ID, or a transaction ID.

[0216] Optionally, the first message may also include a first identifier, that is, the first message includes a first identifier and a second identifier.

[0217] Optionally, the first message may include a second identifier and identifiers related to the first identifier (such as part of the content of the first identifier, or new identifier information generated based on the first identifier, such as a new identifier calculated based on the first identifier, such as hash, modulo, remainder, etc.), without limitation.

[0218] Regarding how the first access device obtains the first identifier, there are two possible designs:

[0219] In one possible design scheme 1, the core network element sends a first identifier to the first access device, and correspondingly, the first access device receives the first identifier from the core network element. That is, the first identifier can be obtained by the first access device from the core network element. For example, the first identifier can be carried in a first service request, which is used to request the performance of a first service, and the first service request includes the first identifier. Alternatively, the first identifier can be carried in other IoT-related service requests or messages, such as inventory requests or command requests, without limitation. It should be understood that the embodiments of this application do not limit the names of the messages, signaling, etc., carrying the first identifier, and can be any message carried on the Next Generation Access Protocol (NGAP) / XXAP / AIOT(-NG) AP interface.

[0220] In the case of multiple access devices sending messages associated with the first service, taking N (N is a positive integer greater than 1) access devices (including the first access device) as an example, the first identifier obtained by each of the N access devices can be sent by the core network element. For example, the core network element sends service requests to the N access devices respectively, and each service request includes the first identifier.

[0221] In one possible design scheme 2, the second access device sends a first identifier to the first access device, and correspondingly, the first access device receives the first identifier from the second access device. The second access device can be any other access device that sends a message associated with the first service. In this design scheme 2, there are multiple access devices (N) that send messages associated with the first service. At least one of these N access devices obtains the first identifier from a core network element. The first access device is not included among the at least one access device that obtains the first identifier from the core network element. Therefore, the first access device can obtain the first identifier from either of these at least one access device or from the access device that obtained the first identifier from the at least one access device; there is no limitation on this.

[0222] For example, after obtaining the first identifier from the core network element, the second access device can send the first identifier to the first access device, or after obtaining the first identifier from the core network element, the second access device can send the first identifier to a third access device other than the first access device, and then the third access device can send it back to the first access device; there is no limitation on this. The timing of the second or third access device sending the first identifier can be either after the second or third access device has completed sending the message associated with the first service, or after the second or third access device has completed the first service with the first device; there is no limitation on this.

[0223] For example, if the first access device and the second access device are network devices, they can interact via Xn signaling (such as exchanging the first identifier). Alternatively, if one of the first access device and the other is a network device and the other is a terminal device (such as the second type of terminal device mentioned above), they can interact via RRC signaling or MAC signaling. Or, if both the first access device and the second access device are terminal devices (such as the second type of terminal device mentioned above), they can interact via a sidelink or D2D communication; there are no limitations on this. It should be understood that for more access devices, the interaction method between access devices is also related to the device type; see the interaction implementation of the first access device and the second access device.

[0224] The first business can be a business related to the application scenario. The first business can be at least one of the following: inventory business, command business, positioning business, sensing business, proximity determination, reading business, writing business, deactivation business, locking business, or security business (such as authentication, authorization, registration, etc.), or it can be a business type that will be newly defined in the future. There are no restrictions on the specific naming.

[0225] In the embodiments of this application, "service" can also be replaced with "task," "session," "request," "transaction," "process," "procedure," or "service," etc., and the embodiments of this application do not limit the name. For example, the first service can also be called the first task, and the inventory service can also be called the inventory task, inventory request, inventory process, or inventory transaction, etc.

[0226] The first service can also refer to a process-related service triggered by a message associated with the first service (such as the first message), which can include at least one of the following: access process, data transmission process (hereinafter referred to as data transmission process), etc., or it can be understood as the service being the corresponding process. The access process can be a random access process, such as contention-based random access or contention-free random access. The access process and the data transmission process are not strictly distinguished. The data transmission process is executed after the access process is completed. Alternatively, data transmission can occur during the access process. For example, during the access process, service-related uplink data, such as the device ID, can be reported. For instance, message 1 sent by the device to the reader includes not only RN16 but also service-related uplink data. Alternatively, in contention-free random access, the device can send D2R / uplink data in message 1.

[0227] For example, the first service is one or more random access procedures and / or data transmission procedures executed by the first device triggered by the first message, and the procedure is the procedure between the first device and the access device.

[0228] In this embodiment, instead of assigning a single first identifier such as a session identifier or transaction identifier (session / transaction ID) to each service, a session / transaction ID is assigned to each process corresponding to a service. Subsequent processes (such as a core network re-triggered or "newly initiated" (not a retransmission) service request / paging, even for the same type of service, can be considered as different session / transaction IDs. Different session / transaction IDs can correspond to different first services. For example, if the core network initiates two inventory management services, the trigger / request messages (such as service request / paging) corresponding to these two inventory management services can carry different session / transaction ID identifiers.

[0229] The first device performing the first service can also be understood as the first device receiving or receiving a signaling message within a certain period of time. This signaling message is used to paging / trigger / select / store / request the first device, for example, a paging signaling message. In other words, this signaling message is used to trigger / select / store / request the first device to process the first service.

[0230] This can be understood as meaning that first service A and first service B are the same first service associated with different second identifiers.

[0231] In one possible scenario, the first service is a business, process, or application scenario that requires repeated responses from the first device. This first service can correspond to one or more access devices, including the first access device. That is, an access device (such as the first access device) repeatedly sends multiple messages related to the first service, requiring repeated responses from the first device; or multiple access devices (such as the first and second access devices) separately send messages related to the first service, requiring repeated responses from the first device. For example, the type / application scenario of the first service may include at least one of the following: location services, proximity determination, assembly line services / scenarios, warehouse logistics scenarios, etc.

[0232] For example, repeated responses can be understood as follows: the first device responds to a process initiated by the first access device that is related to the first service (such as responding to a paging message sent by the first access device and successfully accessing / transmitting data), such as successfully accessing or transmitting data or completing the first service, and also needs to respond to a process initiated by the second access device that is related to the first service (such as responding to a paging message sent by the second access device and performing access / transmission), even if it is related to the first service or the same first identifier, so as to meet the needs of some service types or application scenarios.

[0233] In some scenarios, the first service can be a service or process that does not require repeated responses from the first device. This first service can correspond to one or more access devices, including the first access device. That is, if an access device (such as the first access device) repeatedly sends multiple messages related to the first service without requiring repeated responses from the first device, or if multiple access devices (such as the first and second access devices) separately send messages related to the first service that do not require repeated responses from the first device, then the first device, after performing a first service with an access device based on the messages related to the first service, will no longer respond to other messages related to the first service or will not perform another first service, regardless of whether the other messages related to the first service come from the same access device or multiple different access devices.

[0234] The second identifier is an identifier obtained by the first access device or generated locally that is different from the first identifier. It can be understood that the second identifier is used by the first device to determine whether to respond to the first message, or the second identifier is used to indicate whether the first device responds to the first message, or the second identifier is used to indicate whether the first device responds to or repeatedly responds to the first service. There is no limitation on this.

[0235] In some scenarios, the second identifier can be considered as being used to distinguish different access devices. Optionally, the second identifier is the device identifier of the first access device (such as a reader ID), or an identifier related to the device identifier of the first access device, such as one calculated based on the device identifier of the first access device (such as through hashing, modulo, or remainder calculations), or a part of the identifier of the first access device; there is no limitation on this.

[0236] Regarding how the first access device determines the second identifier, that is, how it determines the message associated with the first service that requires a response from the first device, one possible design is that the first access device receives first indication information and can determine the second identifier based on the first indication information. The first indication information indicates that both the first and second messages require a response from the first device. The second message is a message associated with the first service sent by the second access device. It can be understood that the second message and the first message are functionally similar but sent by different access devices.

[0237] In other words, when the access device that received the first instruction information sends a message associated with the first service, such as a first message sent by the first access device and a second message sent by the second access device, the first device receives the first message, responds to the first message, and completes / successfully performs random access and / or data transmission and / or the first service. When the first device receives the second message, the first device needs to respond to the second message, wherein the first message and the second message are associated with the same first identifier and / or the first service.

[0238] The first indication information can be generated by the core network element. When the first access device and the second access device are different access devices, the first indication information can be understood as indicating that the message related to the first service sent by multiple different access devices needs to be responded to by the first device, or in other words, indicating that multiple different access devices need to trigger the first device to perform the first service.

[0239] Responding to the first message / second message can be understood as executing the subsequent random access and / or data transmission process based on the first / second message, or as executing the first service; there is no limitation on this. Optionally, the first device should also meet the conditions for responding to the first message / second message. For example, if the first device meets the mask and / or device identifier included in the first message / second message, such as the mask having the first 4 bits set to 1000 and the first device's identifier information having the first 4 bits set to 1000, then the first device responds to the first message / second message.

[0240] In some implementations, the first indication information can also be generated by the access device. For example, the access device can generate the first indication information based on the type of the first service or the indication sent by other core network elements, without any limitation.

[0241] In this embodiment of the application, two access devices are used as an example, namely, the first access device and the second access device. For example, the first indication information can be used to indicate that the first access device and the second access device use different second identifiers (that is, to indicate that different access devices use different second identifiers), or the first indication information can be information used to indicate the type of the first service, such as a type identifier. The type of the first service can be used to indicate that the first message and the second message need to be responded to by the first device, or the type of the first service can be used to indicate that the first service is a service that needs to be repeatedly responded to by the first device.

[0242] It is understandable that the first instruction information may also be called a repeat response instruction, repeat instruction, response instruction, adjustment / modification / update of the second identifier instruction, etc., without limitation.

[0243] In some scenarios, the first indication information can be used to indicate that multiple different messages related to the first service sent by the same access device are responded to by the first device. In this case, the first access device and the second access device can be considered as the same access device, and the first message and the second message are different messages related to the first service sent by the same access device. In other words, the same access device needs to repeatedly trigger the first device to perform the first service. This application embodiment mainly uses the first indication information to indicate that multiple different messages related to the first service sent by different access devices are responded to by the first device.

[0244] Regarding how the first access device obtains the first indication information, there are two possible design schemes similar to those for obtaining the first identifier:

[0245] In one possible design scheme 1, the core network element sends first indication information to the first access device, and correspondingly, the first access device can receive the first indication information from the core network element. For example, the first indication information is carried in a first service request sent by the core network element, in which case the first service request may include a first identifier and the first indication information. For the second access device, similar to the first access device, it receives a third service request from the core network element, the third service request including the first identifier and the first indication information. That is, the core network element can send first indication information to multiple access devices respectively.

[0246] In cases where multiple access devices need to send messages associated with the first service sequentially—that is, after one access device sends a message associated with the first service, which is then responded to by the first device, triggering the next access device to send the same message—in addition to the core network element sending first indication information to each access device, the core network element can also send the first indication information only to the first access device that sends the message associated with the first service. After the first access device completes sending the message associated with the first service or the first device responds to its message, the core network element can send the first indication information to the next access device (e.g., based on information sent by the core network, or based on the access device list), thus sequentially transmitting the first indication information. In this case, the core network element can also send a list of the locations of multiple access devices to the first access device, including the correspondence between the access device identifier and its location index. This location index is used to indicate the order in which the access devices send messages associated with the first service among the multiple access devices. The first access device can be the first access device to send the message associated with the first service.

[0247] In one possible design scheme 2, the second access device sends first indication information to the first access device, and correspondingly, the first receiving device receives the first indication information from the second access device. In this case, the second access device can be any other access device that needs to be responded to by the first device for sending messages related to the first service. The second access device can obtain the first indication information from the core network element as described in design scheme 1, or it can obtain the first indication information from other access devices that need to be responded to by the first device for sending messages related to the first service, as described in design scheme 2. There is no limitation on this.

[0248] For design scheme 2, when the above-mentioned multiple access devices need to send messages related to the first service in sequence, the first access device is not the first access device to send the message related to the first service. The second access device can be the previous access device that sent the message related to the first service or another access device that sent the message related to the first service, and there is no limitation in this regard.

[0249] When multiple access devices send messages related to the first service in parallel, the core network element sends a first identifier and a first indication information to each access device respectively. For example, the first identifier and the first indication information are carried in the first service request and sent to the first access device, and the first identifier and the first indication information are carried in the third service request and sent to the second access device.

[0250] At this time, the messages associated with the first service sent by different access devices include different second identifiers. Any two access devices among the multiple access devices use different second identifiers. In other words, the messages associated with the first service sent by access devices other than the first access device include identifiers with similar functions to the second identifier, but different from the second identifier used by the first access device. For example, the third identifier in the second message sent by the second access device, which is different from the second identifier but has a similar function, can be indicated by core network elements.

[0251] It is understandable that the two schemes for the first access device to obtain the first identifier and the two schemes for obtaining the first indication information can be combined arbitrarily for different sending scenarios, and there are no restrictions on this.

[0252] After the first access device obtains the first identifier and the first indication information, if the first indication information indicates that a message associated with the first service sent by an access device needs to be repeatedly responded to by the first device (i.e., the first device needs to respond to multiple messages associated with the first service sent from the same access device), then the first access device can send multiple different messages associated with the first service. These multiple different messages associated with the first service include the first message, and these multiple different messages associated with the first service need to be responded to by the same first device. At this time, the first access device can obtain or generate multiple functionally similar different identifiers, including a second identifier, from the core network element. Each different message associated with the first service sent contains an identifier with a function similar to the second identifier, and the identifiers in any two messages associated with the first service are different. Thus, the same first device can respond multiple times to messages associated with the same service sent by the same access device, which can be understood as repeatedly performing the first service.

[0253] For example, the identifier used by the first device to determine whether to respond to the message associated with the first service is a task ID, and the message associated with the first service that needs to be responded to by the first device is a paging message. If the first access device sends three paging messages to the first device, namely paging messages #1 to #3, then the first access device can generate three different task IDs, such as task IDs 1, 2 and 3, which are respectively carried in paging messages #1 to #3. That is, paging message #1 includes task ID = 1, paging message #2 includes task ID = 2, and paging message #3 includes task ID = 3.

[0254] For example, if the first indication information is used to indicate that a message associated with a first service sent by an access device does not need to be repeatedly responded to by the first device, then the first access device only needs to repeatedly send the first message, that is, repeatedly send the same message associated with the first service including the same identifier (such as the second identifier). Then, for the first device that receives the first message, after it completes the first service with the first access device once according to the first message, it will no longer respond to other first messages containing the second identifier, or the first message may not contain the second identifier, or the second identifier and the third identifier are the same.

[0255] When the first indication information is used to indicate that messages associated with the first service sent by multiple access devices (including the first access device) need to be responded to by the first device, that is, when the first device needs to respond to messages associated with the first service sent from different access devices, in this case, any two access devices among the multiple access devices will generate different identifiers (including the second identifier) ​​with similar functions to the second identifier, or in other words, the identifiers with similar functions to the second identifier contained in the messages associated with the first service sent by any two access devices among the multiple access devices are different. For the first access device, the second identifier in its first message must be different from the identifier with similar functions to the second identifier generated by any other access device that sent a message associated with the first service.

[0256] In one possible implementation, the first access device receives second indication information, which is used to determine a second identifier. That is, the first access device determines the second identifier based on the received second indication information. The second indication information indicates at least one of the following: the position index of the first access device among multiple access devices that sent a message associated with the first service, a third identifier in the message associated with the first service sent by the second access device, or the second identifier, wherein the third identifier is different from the second identifier.

[0257] If the second indication information is used to indicate the location index of the first access device among multiple access devices that send messages associated with the first service, then the second identifier is associated with the location index of the first access device; for example, the second identifier is the location index of the first access device. This can be understood as each access device using an identifier with a similar function to the second identifier is associated with its location index among the multiple access devices, making the second identifier generated by the first access device different from any other access device's identifier with a similar function.

[0258] The second identifier is related to the location index of the first access device among multiple access devices. The multiple access devices may send messages associated with the first service in order of location index or in parallel, without limitation.

[0259] At this time, the first access device can receive second indication information from a core network element or a second access device. The second access device can be any access device other than the first access device among multiple access devices. If the second indication information is sent by a core network element, it can be sent to the first access device along with the first identifier and the first indication information, carried in the first service request.

[0260] If the second indication information is used for the third identifier in a message associated with the first service sent by the second access device, then the first access device generates a second identifier that is different from the third identifier based on the third identifier. It should be understood that if the multiple access devices include other access devices in addition to the first and second access devices, then the first access device can also obtain an identifier that functions similarly to the second identifier used by other access devices to generate a second identifier that is different from the identifier used by other access devices.

[0261] When multiple access devices can sequentially send messages associated with the first service, the first access device to complete sending the message associated with the first service can use an identifier similar in function to the second identifier to send the message associated with the first service. The second access device can generate a different identifier based on the acquired identifier. After completing sending the message associated with the first service, it can send its generated identifier along with the identifier used by the first access device to the third access device to send the message associated with the first service, and so on. In this case, the first access device is not necessarily the first access device to send the message associated with the first service; the second access device can be the access device that sent the message associated with the first service in the preceding position.

[0262] Therefore, the first access device can receive the second indication information from the second access device.

[0263] It should be understood that if the first access device is the first access device to send a message associated with the first service, then the first access device may randomly generate a second identifier or use a predefined second identifier, without any limitation.

[0264] When multiple access devices can sequentially send messages associated with the first service, the access device that has completed sending the message associated with the first service can send its identifier, which has a function similar to the second identifier, to the core network element. The core network element then distributes the identifier to the next access device, enabling the next access device to generate an identifier different from other access devices. Thus, the first access device can receive the second indication information from the core network element.

[0265] For example, the third message sent by the second access device includes a third identifier. After completing the sending of the third message, the second access device can send the third identifier to the core network element. Similarly, the first access device can also send the second identifier to the core network element.

[0266] If the second indication information is used to indicate the second identifier, then the first access device directly uses the second identifier indicated by the second indication information to send the first message. In this case, multiple access devices can send messages associated with the first service sequentially or in parallel.

[0267] When multiple access devices sequentially send messages associated with the first service, a second access device or core network element can receive an identifier similar in function to the second identifier used by other access devices that have completed sending messages associated with the first service. Based on the obtained identifier, a second identifier is generated and sent to the first access device via second indication information. Thus, the first access device can receive the second indication information from the second access device or core network element. In this case, the second access device could also be the access device that sent the message associated with the first service, located at the previous position before the first access device.

[0268] When multiple access devices send messages related to the first service in parallel, the second identifier used by the first access device and identifiers with similar functions used by other access devices may be indicated by core network elements. Furthermore, the identifiers with similar functions to the second identifier contained in the messages related to the first service sent by any two of the multiple access devices may differ. Therefore, the first access device can receive second indication information from the core network elements.

[0269] Therefore, the first device can respond to messages related to the same service from different access devices, which can be understood as the first device performing the same service with different access devices respectively.

[0270] For example, the identifier used by the first device to determine whether to respond to the message associated with the first service is a task ID, and the message associated with the first service that needs to be responded to by the first device is a paging message. If multiple access devices include a first access device and a second access device, then the task ID in the paging message sent by the first access device is different from the task ID in the paging message sent by the second access device. For example, the task ID in the paging message sent by the first access device is 2, and the task ID in the paging message sent by the second access device is 1.

[0271] It is understandable that, to avoid the first device responding to identification, the same access device may repeatedly send messages associated with the first service containing the same identifier. For example, if the first access device repeatedly sends a first message containing the second identifier, then for the first device receiving the first message, after completing one first service with the first access device, it will not respond to any other first messages containing the second identifier. Other access devices are similar to the second access device, and will not be elaborated further.

[0272] It should be understood that in some scenarios, the first indication information can also be used to indicate that the first message and the second message do not need to be responded to by the first device. That is, messages related to the first service sent by multiple access devices (including the first access device) do not need to be responded to by the first device. In this case, multiple access devices can use the same identifier carried in the messages related to the first service. This identifier can be predefined or pre-configured in each access device, or it can be indicated by the core network element, without limitation. For example, multiple access devices may use task ID=0 by default to send messages related to the first service. Alternatively, the first indication information may not need to be sent. In the absence of the first indication information, the access devices do not need the first device to respond repeatedly by default.

[0273] For the specific implementation of how the first message paging or selecting the first device, please refer to the indication method for paging or selecting A-IoT devices in S201 of the related technology 3 above. For example, the first message may include the identifier of the first device or the identifier of the device group to which the first device belongs, etc., and there is no limitation thereto. For example, the first access device may send the first message in the form of broadcast, unicast, etc.

[0274] S1302, The first device determines whether to respond to the first message based on the second identifier.

[0275] After receiving the first message, the first device can determine whether the second identifier in the first message is the same as the identifier stored locally. If they are different, the first device determines to respond to the first message; if they are the same, the first device determines not to respond to the first message.

[0276] In this embodiment of the application, the first device responding to the first message may refer to the first device performing a first service, such as the first device performing random access and / or the first device performing data transmission related to the first service. That is to say, the first device is the device that responds to the first message, or in other words, the first device is the device that receives the first message.

[0277] The identifier stored locally by the first device may include an identifier similar in function to the second identifier from a message sent by the first device in response to another access device that has a similar function to the first message. For example, if the first device receives and responds to a second message that includes a third identifier, then the first device stores the third identifier.

[0278] In a scenario where multiple access devices send messages associated with the first service in parallel, the messages exchanged between the first device and the first access device can carry a second identifier. For example, each random access message carries a second identifier, and / or each data transmission message carries a second identifier.

[0279] In one possible design, the first device can store the access, data transmission, paging, or service status associated with the second identifier. If the first device completes a first service (e.g., successful random access and / or successful data transmission) based on a first message including the second identifier, the corresponding access, data transmission, paging, or service status is successful. If the first device fails to complete the first service (e.g., failed random access and / or failed data transmission) based on the first message including the second identifier, the corresponding access, data transmission, paging, or service status is failed. For example, the access, data transmission, paging, or service status can be indicated by 0 or 1.

[0280] If the first device receives the first message containing the second identifier and fails to respond, the first device may continue to respond when it receives the next first message containing the second identifier, until the response is successful and then it will stop responding.

[0281] The status of data transmission, access, paging, or service success (or completion or execution). Taking access status as an example, for access status, the first device can save whether the access process associated with the second identifier is successful.

[0282] For example, when the first device receives a paging message containing the second identifier #1, it saves / initializes the access status associated with the second identifier #1 as unsuccessful. When the first device successfully accesses the network, the access status associated with the second identifier #1 can be set to successful.

[0283] Optionally, the first device may store the status of whether the access was successful for one or more second identifiers.

[0284] The first device storing this information can be implemented in various ways:

[0285] In one possible implementation, the first device may include multiple capacitors, each corresponding one-to-one with a specific service. Each capacitor can be used to maintain information reflecting whether the service's status has been successfully stored for a period of time. The storage duration can be determined by the capacitor's capacitance. The capacitors may also have the function of continuing to maintain this information for a period of time without being recharged.

[0286] In one example, "1" can be used to indicate that the service state was successfully stored, and "0" can be used to indicate that the service state was not successfully stored. The capacitor can maintain either a "1" or "0" state. When the capacitor's capacitance is depleted, the first device may not maintain a "1" or "0" state.

[0287] The multiple capacitors may include capacitor 1 and capacitor 2. Capacitor 1 can be used to maintain information reflecting whether the status of the first service A (associated with the first identifier #1 and / or the second identifier #1) was successful for a period of time. Capacitor 2 can be used to maintain information reflecting whether the status of the first service B (associated with the first identifier #2 and / or the second identifier #2) was successfully stored for a period of time.

[0288] If the first device receives a signaling message carrying the second identifier #1, such as paging, the first device can charge capacitor 1. Capacitor 1 then has capacitance and can maintain the state of the first service A. The state of the first service A can be "0" or "1". Optionally, when the first device does not charge capacitor 1, capacitor 1 can discharge, and its maintenance time can be 0 to L1. The specific value of L1 depends on the capacitance of capacitor 1 and is hardware-related. After L1, the state of the first service is no longer maintained. If the first device receives a signaling message carrying the second identifier #2, the first device can charge capacitor 2. Capacitor 2 then has capacitance and can maintain the state of the first service B. The state of the first service B can be "0" or "1". When the first device does not charge capacitor 2, capacitor 2 can discharge, and its maintenance time can be 0 to L2. The specific value of L2 depends on the capacitance of capacitor 2 and is hardware-related. After L2, the state of the first service is no longer maintained.

[0289] In another possible implementation, the first device may store information reflecting whether the status of the first service A and the first service B is successful through registers, memory, latches or storage.

[0290] For example, a register may include a bit. When the bit is 0, it corresponds to the first service A (or the second identifier = 0). When the bit is 1, it corresponds to the first service B (or the second identifier = 1). It also needs to store status information: status = 0 indicates success, and status = 1 indicates failure. The status information is associated with the service. For example, in sequence, the stored content is second identifier = 0, status = 0, second identifier = 1, status = 1, indicating that the first service was successful and the second service was unsuccessful.

[0291] In another possible implementation, the first device can use a timer to maintain information reflecting whether the business status has been successfully stored over a period of time.

[0292] For example, the first device may start two timers. Timer 1 may be used to maintain information reflecting whether the state of the first service A has been successfully stored for a period of time. Timer 2 may be used to maintain information reflecting whether the state of the first service B has been successfully stored for a period of time.

[0293] If the first device receives a signaling message carrying a second identifier of 0, such as paging, the first device can start timer 1. During the timer 1's counting process, the state of the first service A can be maintained. The state of the first service A can be either "0" or "1". When timer 1 reaches its duration, the state of the first service A is no longer maintained. If the first device receives a signaling message carrying a second identifier of 1, the first device can start timer 2. During the timer 2's counting process, the state of the first service B can be maintained. The state of the first service B can be either "0" or "1". When timer 2 reaches its duration, the state of the first service B is no longer maintained.

[0294] Optionally, the above-mentioned implementation methods can be used in combination. For example, the second identifier and / or the first identifier information can be stored in a memory, and the state information can be maintained using a capacitor.

[0295] Optionally, if the access or data transmission status is successful, the first device may not need to re-access or retransmit. For example, while maintaining the access or data transmission status as successful, the first device's behavior may include one or more of the following: not responding to re-access indication information, not actively re-accessing, not responding to retransmission indication information, and not re-responding to downlink data. This prevents repeated responses to the associated first service (e.g., via the second and / or first identifier), thus avoiding additional signaling overhead.

[0296] Optionally, if the access or data transmission status is unsuccessful / failed, the first device needs to re-access or retransmit. For example, while maintaining the access or data transmission status as unsuccessful (failed), the first device's behavior may include one or more of the following: responding to re-access indication information or retransmission (failure) indication information, re-responding to downlink data, and responding to segmented retransmission (failure) indication information, thereby improving service reliability.

[0297] In one possible design, the first device may have only one access, data transmission, paging, or service state. This access, data transmission, paging, or service state changes according to the identifier in the received message. In other words, different access devices correspond to one access, data transmission, paging, or service state. For example, if the first device receives a first message containing a second identifier, then the first device performs a first service with the first access device based on the first message. If the first service is completed or successful, the data transmission state is 1; if the first service is completed or fails, the data transmission state is 0. If the first service is not completed or fails (e.g., the first service is interrupted), and if the first device receives a second message containing a third identifier, and the third identifier is different from the second identifier, regardless of whether the first service performed by the first device with the second access device based on the second message is completed, the first device releases the data transmission state corresponding to the second identifier and updates the data state corresponding to the third identifier.

[0298] In another possible design, the first device can also set an access, data transmission, paging, or service status for each identifier (or each access device). For example, if the first device receives a first message containing a second identifier, then the first device saves a data transmission status (0 / 1) corresponding to the second identifier. If the first device receives a second message containing a third identifier, and the third identifier is different from the second identifier, then the first device saves a data transmission status corresponding to the third identifier.

[0299] The release or expiration time for access, data transmission, paging, or service status can be set periodically. This timing setting can be indicated by the access device or core network element, pre-configured in the first device, or specified by a protocol; there is no limitation on this. For example, this timing can be implemented through a timer or capacitor discharge time. That is, during the timing period, the first device saves / maintains the access, data transmission, paging, or service status corresponding to the second identifier; when the timing ends, the status is released, expired, reset, or no longer maintained / saved.

[0300] The start time of the timing can refer to the time when the second identifier corresponding to the access, data transmission, paging, or service status becomes effective. For example, the start time of the timing can be the time when the first message containing the second identifier is received, or the time when the response to the first message begins, or the moment when the access, data transmission, paging, or service status changes from failure to success, or the moment when the access, data transmission, paging, or service status changes from success to failure, or the start time of the timing can be the moment when the access, data transmission, paging, or service status changes, such as when the access status is initialized.

[0301] For example, the first device receives a first message containing a second identifier, responds to the first message and performs a first service with the first access device. If the first service is not completed, the data transmission status corresponding to the second identifier is failure or unsuccessful. If the first device receives another first message containing a second identifier, responds to the first message and performs the first service with the first access device again, and if the first service is completed, the data transmission status corresponding to the second identifier is successful. At this time, the start time of the timing of the data transmission status corresponding to the second identifier is the moment when the status changes.

[0302] In one possible design, during the effective period of the status, that is, the timed period, the core network element or access device can send an indication message to indicate when the first device should release or disable the access, data transmission, paging, or service status, or to instruct the first device to immediately release or disable the access, data transmission, paging, or service status.

[0303] In the communication method shown in Figure 13, the access device can determine an identifier different from the identifier of the first service to be carried in the message associated with the first service. Different access devices determine different identifiers so that the first device can respond to messages associated with the same service from different access devices.

[0304] The method shown in Figure 13 will be illustrated with specific examples in the following scenarios.

[0305] Taking the access device as the reader / writer, the first device as A-IoT device 1, the core network element as AMF, the message associated with the first service as a paging message, the first identifier as session ID1, and the identifier used by the first device to determine whether to respond to the message associated with the first service as task ID, with N=2 (i.e., reader / writer 1 and reader / writer 2) as an example, as shown in Figure 14, this communication method includes:

[0306] S1401, AMF sends service request 1 to reader 1. Correspondingly, reader 1 receives service request 1 from AMF.

[0307] S1402, AMF sends service request 2 to reader 2. Correspondingly, reader 2 receives service request 2 from AMF.

[0308] Service Request 1 and Service Request 2 are used to request the first service, including Session ID1, First Indication Information and Reader List. Session ID1 is used to identify the first service. The First Indication Information is used to indicate that Paging Message 1 and Paging Message 2 need to be responded to by the same A-IoT device (such as an A-IoT device). Paging Message 1 is a paging message sent by Reader 1 associated with the first service, and Paging Message 2 is a paging message sent by Reader 2 associated with the first service. The Reader List is used to indicate the order of the readers that send the paging messages associated with the first service. It may include the identifier of Reader 1 (reader1 ID) and the identifier of Reader 2 (reader2 ID), as well as the position index (or sequence index) associated with the identifier of the reader, taking the order of Reader 1 -> Reader 2 as an example.

[0309] S1403, the reader 1 repeatedly sends paging message 1 to the A-IoT device 1. Correspondingly, the A-IoT device 1 repeatedly receives paging message 1 from the reader 1.

[0310] Among them, paging message 1 includes task ID1, such as task ID1 = 0.

[0311] Reader 1 can determine the need to send a paging message that is responded to by A-IoT device 1 based on the session ID1 and the first indication information in service request 1. Furthermore, it can determine the first reader in the reader list to send the paging message, and thus, reader 1 generates a task ID1. For example, the task ID1 can be the position index or sequence index of reader 1 in the reader list, such as task ID1 = 0 (index starts from 0) or task ID1 = 1 (index starts from 1). Alternatively, task ID1 can be a randomly generated identifier by reader 1. Since reader 1 is the first reader to send the paging message associated with the first service, the task ID1 used can also be predefined or preconfigured; there are no limitations on this.

[0312] Optionally, reader 1 can also send a service start message to the next reader in the AMF and / or reader list (such as reader 2). This service start message indicates the initiation of the first service and includes session ID1. Optionally, the service start message may also include task ID1 used by reader 1.

[0313] For A-IoT device 1, upon receiving a paging message 1, it determines whether the task ID 1 in paging message 1 is the same as a previously received and stored task ID. If they are different, it responds to paging message 1 and performs random access and / or data transmission, i.e., performs the first service. If the first service is completed or successful, A-IoT device 1 will no longer respond to other paging messages containing task ID 1, i.e., other repeatedly sent paging messages 1. If the first service is not completed or fails, A-IoT device 1 can continue to respond to other paging messages containing task ID 1 until the first service is completed or successful, after which it will no longer respond. Furthermore, A-IoT device 1 stores task ID 1.

[0314] S1404, Reader 1 sends an end mark message 1 to Reader 2. Correspondingly, Reader 2 receives the end mark message 1 from Reader 1.

[0315] The termination message 1 is used to instruct reader 1 to complete sending the paging message, or for reader 1 to respond to the paging message sent by reader 1, or for reader 1 to complete the first service with A-IoT device 1. The termination message 1 includes session ID1 and task ID1. Optionally, termination message 1 may also include first indication information, which is not limited.

[0316] For example, after reader 1 completes the transmission of paging message 1, or after reader 1 receives a response from A-IoT device 1, such as a random access procedure or a data transmission procedure, or after reader 1 completes the first service with A-IoT device 1, reader 1 can send end message 1 to the next reader 2 that sent the paging message.

[0317] S1405, the reader 2 repeatedly sends paging message 2 to the A-IoT device 1. Correspondingly, the A-IoT device 1 repeatedly receives paging message 2 from the reader 1.

[0318] Among them, paging message 2 includes task ID2, and task ID2 is different from task ID1, such as task ID2=1.

[0319] Therefore, based on the service request 2 sent by the AMF, the reader 2 determines that it needs to perform the first service with the A-IoT device 1, that is, the paging message it sends needs to be responded to by the A-IoT device 1. After receiving the end message 1 from the reader 1, the reader 2 can generate a task ID2 that is different from the task ID1 obtained by the reader 1 to satisfy the first indication information, and send the task ID2 in the paging message 2.

[0320] For example, the task ID2 can be the position index or sequence index of reader 2 in the reader list, such as task ID2 = 1 (index starts from 0) or task ID1 = 2 (index starts from 1), or task ID2 can be a randomly generated identifier of reader 2 that is different from task ID1.

[0321] Accordingly, for A-IoT device 1, after receiving a paging message 2, it determines whether the task ID 2 in paging message 2 is the same as the previously received and stored task ID (such as task ID 1). If they are different, it responds to paging message 2 and performs random access and / or data transmission, i.e., performs the first service. If the first service is completed or successful, A-IoT device 1 will no longer respond to other paging messages containing task ID 2, i.e., other repeatedly sent paging messages 2. If the first service is not completed or fails, A-IoT device 1 can continue to respond to other paging messages containing task ID 2 until the first service is completed or successful, after which it will no longer respond. Furthermore, A-IoT device 1 stores task ID 2.

[0322] It should be understood that if there are more readers sending paging messages related to the first service, such as readers 3, readers 4, etc. in the reader list, then reader 2 can also send end message 2 to reader 3. At this time, end message 2 includes session ID1, task ID1, and task ID2. That is, it can include the task IDs used by all readers that have previously sent paging messages, so that reader 2 can generate different task IDs, such as task ID3. The same process applies to subsequent readers.

[0323] In the scenario shown in Figure 14, when multiple readers receive the same service-related service request from the CN, the reader can determine a task ID based on the first indication information in the service request. Different readers generate different task IDs to instruct the same A-IoT device to respond to the paging messages related to the same service sent by different readers.

[0324] As exemplarily shown in Figure 15, the communication method includes:

[0325] S1501, AMF sends Service Request 1 to Reader 1. Correspondingly, Reader 1 receives Service Request 1 from AMF.

[0326] Service Request 1 is used to request the first service, and Service Request 1 includes Session ID 1. Optionally, Service Request 1 includes first indication information and / or a list of readers / writers.

[0327] S1502, the reader 1 repeatedly sends paging message 1 to the A-IoT device 1. Correspondingly, the A-IoT device 1 repeatedly receives paging message 1 from the reader 1.

[0328] Among them, paging message 1 includes task ID1, such as task ID1 = 0.

[0329] Since reader 1 is the first reader to send a paging message associated with the first service triggered by the AMF, service request 1 may not carry the first indication information. Therefore, reader 1 can randomly generate a task ID1 based on service request 1, or the task ID1 can be predefined or preconfigured, or a task ID1 can be generated according to a predetermined rule, without any limitation.

[0330] For A-IoT device 1, the response process is similar to S1403 above, and will not be described in detail here.

[0331] S1503, Reader 1 sends End Message 1 to AMF. Correspondingly, AMF receives End Message 1 from Reader 1.

[0332] The function description of End Message 1 can be found in S1404 above. In this case, End Message 1 includes Task ID 1. Optionally, End Message 1 may also include Session ID 1.

[0333] S1504, AMF sends service request 2 to reader 2. Correspondingly, reader 2 receives service request 2 from AMF.

[0334] Among them, business request 2 is used to request the first business. Business request 2 includes session ID 1, first indication information and second indication information. The second indication information is used to determine the task ID used by reader 2.

[0335] For example, each reader's task ID is its location index among multiple readers, and these multiple readers are the readers that send paging messages associated with the first service. Then, the second indication information is used to indicate the location index of reader 2 among the multiple readers. Accordingly, reader 2 can determine the task ID 2 to use as its location index based on the location index indicated by the first and second indication information.

[0336] For example, if the task ID is randomly generated by each reader, then the second indication information is used to indicate the task ID1 of reader 1. Correspondingly, reader 2 can randomly generate a task ID2 that is different from task ID1 based on the task ID1 indicated by the first and second indication information.

[0337] For example, the AMF randomly generates a task ID2 that is different from the task ID1 of the reader 1, and sends the task ID2 to the reader 1 through the second indication information. At this time, the second indication information is used to indicate the task ID2 used by the reader 2.

[0338] S1505, the reader 2 repeatedly sends paging message 2 to the A-IoT device 1. Correspondingly, the A-IoT device 1 repeatedly receives paging message 2 from the reader 1.

[0339] The paging message 2 includes a task ID 2. The reader / writer 2 can send a paging message 2, including a task ID 2, to the A-IoT device 1 based on the triggering of the service request 2. The task ID 2 is different from the task ID 1.

[0340] For A-IoT device 1, its implementation is similar to that in S1405 above, and will not be described in detail here.

[0341] Optionally, reader 2 can also send task ID2 to AMF, for example, send end message 2, which includes task ID2.

[0342] It should be understood that if there are more readers sending paging messages related to the first service, such as readers 3 and 4, readers 2 can send an end message 2 to the AMF, similar to readers 1. The end message 2 includes task ID 2, so the AMF sends a service request 3 to readers 3 based on the stored task ID 1 and task ID 2. The service request 3 may include session ID 1, first indication information, and indication information for determining the task ID 3 used by readers 3. Task ID 3 is different from task ID 1 and task ID 2, and so on. This will not be elaborated further.

[0343] In the scenario shown in Figure 15, the CN sequentially sends a service request to trigger a reader to send a paging message associated with the first service. The paging message carries a task ID. For different readers that trigger the same service, a different task ID can be generated based on the first indication information in the service request, so as to instruct the same A-IoT device to respond to the paging messages associated with the same service sent by different readers.

[0344] Figures 14 and 15 above illustrate how to determine the task ID in a scenario where multiple readers send paging messages sequentially, enabling the same A-IoT device to respond to paging messages associated with the same service sent by different readers. In addition, multiple readers can also send paging messages associated with the same service in parallel. In this scenario, the different task IDs used by each reader can all be assigned by the CN. For example, the service request sent by the CN includes Session ID1, first indication information, and the task ID used by the reader. If the same A-IoT device responds to a paging message from a certain reader, the task ID can be carried in the random access message or data transmission message in the subsequent random access or data transmission process to distinguish the different responding readers. This is not limited. For example, each R2D message carries a corresponding task ID, and / or the sent D2R message also carries a corresponding task ID.

[0345] This application embodiment also provides a communication method in which a core network element can assign different service identifiers to different access devices or the same access device for the same service, so that the same first device can respond to paging messages associated with the same service sent by different access devices or the same access device. For example, as shown in FIG16, the communication method includes:

[0346] S1601, The core network element sends a first service request to the first access device. Correspondingly, the first access device receives the first service request from the core network element.

[0347] S1602, The core network element sends a second service request to the first access device. Correspondingly, the first access device receives the second service request from the core network element.

[0348] The first service request includes a first identifier, and the second service request includes a fourth identifier. The first identifier and the fourth identifier are used to identify the first service, and the first identifier and the fourth identifier are different identifiers. For example, the first identifier and the fourth identifier can be a service identifier, a session ID, or a transaction ID.

[0349] When a core network element determines that a first service is one that needs to be repeatedly responded to by a first device, such as when paging messages associated with the same service sent by the same access device need to be responded to by the same first device, the core network element can generate different service identifiers that can be used to identify the first service. Alternatively, the multiple different service identifiers corresponding to the first service may be predefined or preconfigured, without limitation. The core network element can then select different service identifiers from the multiple predefined or preconfigured service identifiers to send to the access device.

[0350] For the first service, there is usually a predefined or preconfigured service identifier (hereinafter referred to as the original identifier). Therefore, different service identifiers corresponding to the first service can be identifiers with the same format as the original identifier, or different service identifiers corresponding to the first service can include the original identifier (in this application embodiment, the first identifier can be the original identifier), or different service identifiers corresponding to the first service can be identifiers with the same format as the original identifier that have been truncated. The truncated identifiers can still identify the first service, which can save overhead, and there is no limitation on this.

[0351] S1603, The first access device sends a first message. Correspondingly, the first device receives the first message.

[0352] The first message may include identifiers related to the first identifier. These identifiers can still be used to identify the first service. The identifiers related to the first identifier can be the first identifier, a portion of the first identifier, or new identifier information generated based on the first identifier, such as identifiers calculated based on the first identifier, like hash, modulo, or remainder. In other words, the identifiers related to the first identifier are determined based on the first identifier; this is not limited. The first message is a message associated with the first service. Descriptions related to the functions of the first message and the first service can be found in the relevant descriptions of the first message and the first service in S1301 above; this is not limited. That is, the first access device triggers the sending of the first message based on the first service request, and this first message needs to be responded to by the first device.

[0353] For example, the first message includes a first identifier, that is, the identifier associated with the first identifier is the first identifier.

[0354] For the first device, it determines whether the identifier related to the first identifier in the first message is one of the service identifiers stored locally. If so, it does not respond to the first message; otherwise, it responds to the first message and stores the identifier related to the first identifier, such as for random access and / or data transmission related to the first service. The service identifier stored locally may be obtained from previously responded to or received messages associated with the first service.

[0355] S1604, the first access device sends a third message. Correspondingly, the first device receives the third message.

[0356] The third message includes an identifier associated with the fourth identifier. This identifier can still be used to identify the first service. The identifier associated with the fourth identifier can be the fourth identifier itself, a portion of the fourth identifier, or new identifier information generated based on the fourth identifier, such as an identifier calculated based on the fourth identifier, like a hash, modulo, or remainder. In other words, the identifier associated with the fourth identifier is determined based on the fourth identifier; this is not limited. The third message is a message associated with the first service and has a similar function to the first message; this is also not limited. That is, the first access device triggers the sending of the third message based on the second service request, and this third message needs to be responded to by the first device.

[0357] For example, the third message includes a fourth identifier, that is, the identifier associated with the fourth identifier is the fourth identifier.

[0358] For example, the service identifier stored locally by the first device includes a first identifier. That is, if the first device receives the first message first, then after receiving the third message, the first device determines whether the fourth identifier in the third message is the same as the first identifier. If so, it does not respond to the third message; otherwise, it responds to the third message, performs the first service, and stores the fourth identifier. Alternatively, the service identifier stored locally by the first device includes a fourth identifier. That is, if the first device receives the third message first, then after receiving the first message, the first device determines whether the first identifier in the first message is the same as the fourth identifier. If so, it does not respond to the first message; otherwise, it responds to the first message, performs the first service, and stores the first identifier.

[0359] This can be understood as the first device believing that different service identifiers require a response, without being aware of whether they are the same service.

[0360] It should be understood that, in order to avoid unsuccessful responses to the first and third messages, the first access device may resend the first and third messages. However, after responding to one first and third message and completing one first service, it may not respond to other resent first and third messages.

[0361] The above S1601 to S1604 describe how CN sends multiple service requests associated with the same service to the same access device, but the service identifiers in the service requests are different, thereby enabling the first device to respond to messages associated with the same service sent by the same access device.

[0362] In scenarios where multiple access devices send messages related to the first service that require a response from the first device, the above-mentioned S1602 can be replaced by, or the communication method can further include: the core network element sending a third service request to the second access device. Correspondingly, the second access device receives the third service request from the first access device. The third service request includes a fifth identifier, which is used to identify the first service.

[0363] At this point, the fifth identifier can also be generated by a core network element, or it can be a service identifier different from the first identifier selected from multiple predefined or preconfigured service identifiers for the first service. The descriptions of the first and fourth identifiers above are relevant to the fifth identifier and will not be repeated here.

[0364] Optionally, the first service request and the third service request may further include first indication information. The first indication information is used to indicate that the first message and the second message need to be responded to by the first device. The first message is a message associated with the first service sent by the first access device, and the second message is a message associated with the first service sent by the second access device. For a detailed description of the first indication information, please refer to the relevant description of the first indication information in S1301 above, which will not be repeated here.

[0365] The above-mentioned S1604 can be replaced by another communication method, which may further include: the second access device sending a second message. Correspondingly, the first device receives the second message.

[0366] The second message includes an identifier associated with the fifth identifier. A description of the identifier associated with the fifth identifier can be found in the descriptions of the identifiers associated with the first / fourth identifiers mentioned above, and will not be repeated here. For example, the second message includes the fifth identifier.

[0367] For the first device, upon receiving a first message, it determines whether the identifier related to the first identifier in the first message is one of the service identifiers stored locally. If so, it does not respond to the first message; otherwise, it responds to the first message to perform the first service and stores the identifier related to the first identifier, such as performing random access and / or data transmission related to the first service. The service identifier stored locally may be obtained from previously responded to or received messages associated with the first service. In this case, the first message may be the first message received by the first device that is associated with the first service, therefore the first device may not have stored any service identifiers, and this is not a limitation.

[0368] For the first device, if it receives a third message, it determines whether the identifier related to the fifth identifier in the third message (such as the fifth identifier) ​​is one of the service identifiers stored locally (such as including the first identifier). If it is, it does not respond to the first message; if it is not, it responds to the first message to perform the first service and stores the identifier related to the fifth identifier, such as performing random access and / or data transmission related to the first service.

[0369] For the first device, it can store an access, data transmission, paging, or service status for each different service identifier, or multiple different service identifiers can correspond to the same access, data transmission, paging, or service status. The access, data transmission, paging, or service status can be released and updated according to the received service identifier, without any limitation.

[0370] The release or expiration time for access, data transmission, paging, or service status can be set at a time. This time setting can be indicated by the access device or core network element, and there are no restrictions on it.

[0371] For descriptions of access, data transmission, paging, or service status, please refer to the relevant descriptions in S1302 above, which will not be repeated here.

[0372] Therefore, CN can also send service requests associated with the same service to different access devices, but the service identifiers in the service requests are different, which enables the first device to respond to messages associated with the same service sent by different access devices.

[0373] It should be understood that in the method embodiment shown in FIG18, the first identifier may be different from the method embodiment shown in FIG13. The first identifier may be the identifier in the method embodiment shown in FIG13, or it may be a new identifier obtained by processing the identifier in the method embodiment shown in FIG13, but both can be used to identify the first service.

[0374] The communication method shown in Figure 16 will be illustrated with specific examples in the following scenarios.

[0375] Taking the access device as the reader / writer, the first device as A-IoT device 1, the core network element as A-IoT MF, and the message associated with the first service as a paging message, with the first identifier as session ID1 and the fifth identifier as session ID2, and taking the CN triggering reader / writer 1 and reader / writer 2 to send a paging message associated with the first service requiring a response from the first device as an example, as shown in Figure 17, this communication method includes:

[0376] S1701, the A-IoT MF sends service request 1 to reader 1. Correspondingly, reader 1 receives service request 1 from the A-IoT MF.

[0377] Service Request 1 is used to request a first service. Service Request 1 includes Session ID 1, which is used to identify the first service. Optionally, Service Request 1 may also include first indication information and / or a reader list, which indicates the readers that need to send a paging message associated with the first service and which have been responded to by the first device.

[0378] S1702, the A-IoT MF sends service request 2 to reader 2. Correspondingly, reader 2 receives service request 2 from the A-IoT MF.

[0379] Service request 2 is used to request the first service. Service request 2 includes session ID2, which identifies the first service, and session ID1 is different from session ID2. Optionally, service request 2 may also include first indication information and / or a reader list, which indicates the readers that need to send paging messages associated with the first service and have been responded to by the first device.

[0380] S1703, Reader 1 repeatedly sends paging message 1. Correspondingly, A-IoT device 1 receives paging message 1.

[0381] Among them, paging message 1 is associated with the first service, and the paging message includes session ID 1.

[0382] S1704, Reader 2 repeatedly sends paging message 2. Correspondingly, A-IoT device 1 receives paging message 2.

[0383] Among them, paging message 2 is associated with the first service, and paging message 2 includes session ID 2.

[0384] A-IoT device 1 can receive paging messages and determine whether the session ID in the paging message is one of the session IDs stored locally. If it is, it will not respond to the paging message; otherwise, it will respond to the paging message and perform the first service.

[0385] For example, if A-IoT device 1 receives paging message 1 first, it responds to paging message 1 and saves session ID 1. Upon receiving paging message 2, it determines whether session ID 2 in paging message 2 is the same as the stored session ID 1. If they are the same, it does not respond to paging message 2; otherwise, it responds to paging message 2 and performs the first service. Alternatively, if A-IoT device 1 receives paging message 2 first, it responds to paging message 2 and saves session ID 2. Upon receiving paging message 1, it determines whether session ID 1 in paging message 1 is the same as session ID 2. If they are the same, it does not respond to paging message 1; otherwise, it responds to paging message 1 and performs the first service.

[0386] In addition, this application embodiment also provides a communication method in which access devices generate different service identifiers for a first service to indicate that a first device responds to messages associated with the same service from different access devices. As shown in FIG18, the communication method includes:

[0387] S1801, The first access device receives the fifth identifier and the first indication information.

[0388] The fifth identifier is used to identify the first service, and the first indication information is used to indicate that the first message and the second message need to be responded to by the first device. The first message is a message sent by the first access device that is associated with the first service, and the second message is a message sent by the second access device that is associated with the first service. For a detailed description of the first service and the first indication information, please refer to the relevant description of the first service and the first indication information in S1301 above, which will not be repeated here.

[0389] In a scenario where messages associated with the first service sent by different access devices need to be responded to by the first device, the access device that sends the message associated with the first service is indicated by the core network element. In this embodiment, two different access devices, namely the first access device and the second access device, are used as an example.

[0390] S1802, the first access device sends a first message. Correspondingly, the first device receives the first message.

[0391] The first message includes the sixth identifier, which is used to identify the first service.

[0392] In one possible scenario (Scenario 1), where the first access device and the second access device send messages associated with the first service sequentially, if the first access device is the first access device to send a message associated with the first service triggered by an indication from a core network element, then the first access device can receive a fifth identifier and first indication information from the core network element. In this case, the first access device can also receive a location list from the core network element, which includes the correspondence between the access device's identifier and its location index, i.e., the execution order of the first and second access devices. For example, the first access device receives a first service request from a core network element, which includes a fifth identifier, first indication information, and a location list. In this case, the fifth identifier can be a sixth identifier carried in the first message, which the first access device can use.

[0393] In one possible scenario 2, where the first access device and the second access device sequentially send messages associated with the first service, if the second access device is the first access device to send a message associated with the first service triggered by a core network element indication, and the first access device is the second access device to send a message associated with the first service triggered by a core network element indication, then the fifth identifier refers to the identifier carried in the second message by the second access device. The first access device can generate a sixth identifier, different from the fifth identifier, based on the fifth identifier and the first indication information. The sixth identifier is used to identify the first service. In other words, the sixth identifier is determined based on the fifth identifier and the first indication information.

[0394] The first access device could have the following possible designs for obtaining the fifth identifier and the first indication information:

[0395] Design 1: The first access device can receive the fifth identifier and the first indication information from the second access device.

[0396] For example, a core network element sends a third service request to a second access device. The third service request includes a first identifier, first indication information, and a location list. The first identifier is used to identify the first service. The second access device can use the first identifier (i.e., the fifth identifier is the first identifier), or process the first identifier (e.g., truncate it) to obtain a fifth identifier that still identifies the first service, or generate a fifth identifier with the same format as the first identifier but different from it, and then send the fifth identifier in the second message. After the second access device completes sending the second message, or the second message is responded to by the first device, or the second access device and the first device complete the first service, the second access device sends the fifth identifier and the first indication information to the first access device. If the fifth identifier and the first indication information can be carried in the end mark, the first access device can generate a sixth identifier different from the fifth identifier based on the first indication information and the fifth identifier, and send it in the first message.

[0397] Design 2: The first access device can receive the fifth identifier from the second access device, as well as the first indication information from the core network element.

[0398] For example, a core network element sends a first service request to a first access device. The first service request includes a first identifier and first indication information. The core network element also sends a third service request to a second access device. The third service request includes a first identifier, first indication information, and a location list. The first identifier is used to identify the first service. The second access device can use the first identifier (i.e., the fifth identifier is the first identifier), or process the first identifier (e.g., truncate it) to obtain a fifth identifier that still identifies the first service, or generate a fifth identifier with the same format as the first identifier but different from it. This fifth identifier is then carried in a second message and sent. After the second access device completes sending the second message, or the second message is responded to by the first device, or the second access device completes the first service with the first device, the second access device sends the fifth identifier to the first access device. If this fifth identifier can be carried in an end mark message, the first access device can generate a sixth identifier different from the fifth identifier based on the first indication information in the first service request sent by the core network element and the fifth identifier used by the second access device.

[0399] Design 3: The first access device can receive the fifth identifier and the first indication information from the core network element.

[0400] For example, a core network element sends a third service request to a second access device. The third service request includes a first identifier, first indication information, and a location list. The first identifier is used to identify the first service. The second access device can use the first identifier (i.e., the fifth identifier is the first identifier), or process the first identifier (such as truncating, hashing, modulo, or remainder calculation) to obtain a fifth identifier that still identifies the first service, or generate a fifth identifier with the same format as the first identifier but different from it, and then send the fifth identifier in a second message. After the second access device completes sending the second message, or the second message is responded to by the first device, or the second access device and the first device complete the first service, the second access device sends the fifth identifier to the core network element. The core network element then sends a first service request to the first access device. The first service request includes the fifth identifier and the first indication information. Therefore, the first access device can generate a sixth identifier different from the fifth identifier based on the first indication information and the fifth identifier in the first service request sent by the core network element.

[0401] It should be understood that there may also be a design 4, in which the first access device can receive the fifth identifier from the core network element and the first indication information from the second access device, which will not be elaborated here.

[0402] Optionally, after generating the sixth identifier, the first access device can send the sixth identifier to the core network element to inform the core network element of the identifier it uses to identify the first service. For example, the first access device sends a message to the core network element to inform it of sending the first message, such as a service start message, or a message to inform it of completing the sending of the first message, such as an end mark message. The sixth identifier can be carried in either the message informing it of sending the first message or the message informing it of completing the sending of the first message; there is no limitation on this.

[0403] In the case where more than two access devices send messages related to the first service and the first device responds, the sixth identifier must be different from the identifier used by any other access device to identify the first service. Its implementation is similar to that described above, or you can refer to the communication method shown in Figure 14 for the determination of the second identifier in the case where more than two access devices send messages related to the first service and the first device responds; details will not be elaborated here. Optionally, each of the more than two access devices can report its identifier used to identify the first service to the core network element.

[0404] The first device receives a first message and determines whether the sixth identifier in the first message is one of the service identifiers stored locally. If it is, it does not respond to the first message; otherwise, it responds to the first message and performs the first service, including random access and / or data transmission related to the first service. For example, the service identifiers stored locally by the first device include a fifth identifier. If the sixth identifier is the same as the fifth identifier, it does not respond to the first message; if the sixth identifier is different from the fifth identifier, it responds to the first message and performs the first service.

[0405] In this embodiment of the application, when the first device performs random access and / or data transmission related to the first service with the first access device, each random access message and each data transmission message may carry a sixth identifier to distinguish which service identifier the message belongs to, without limitation.

[0406] For the first device, it can store an access, data transmission, paging, or service status for each different service identifier, or multiple different service identifiers can correspond to the same access, data transmission, paging, or service status. The access, data transmission, paging, or service status can be released and updated according to the received service identifier, without any limitation.

[0407] The release or expiration time for access, data transmission, paging, or service status can be set at a time. This time setting can be indicated by the access device or core network element, and there are no restrictions on it.

[0408] For descriptions of access, data transmission, paging, or service status, please refer to the relevant descriptions in S1302 above, which will not be repeated here.

[0409] In the communication method shown in Figure 18, when multiple access devices (including the first access device) send messages associated with the first service and the first device responds, the access device can generate a service identifier that is different from the service identifier carried in the message associated with the first service by any of the other access devices based on the received first indication information and service identifier. This allows different access devices to generate different service identifiers, thereby enabling the first device to respond to messages associated with the same service sent by different access devices.

[0410] The communication method shown in Figure 18 will be illustrated with specific examples in the following scenarios.

[0411] Taking the access device as the reader / writer, the first device as A-IoT device 1, the core network element as AMF, the message associated with the first service as a paging message, the fifth identifier as session ID1, and the sixth identifier as session ID2, as an example where CN triggers reader / writer 1 and reader / writer 2 to send a paging message associated with the first service, which requires a response from the first device, as shown in Figure 19, this communication method includes:

[0412] S1901, AMF sends service request 1 to reader 1. Correspondingly, reader 1 receives service request 1 from AMF.

[0413] Among them, Service Request 1 is used to request the first service. Service Request 1 includes Session ID1, First Indication Information and Reader List. Session ID1 is used to identify the first service. First Indication Information is used to indicate that Paging Message 1 and Paging Message 2 are responded to by A-IoT Device 1. Reader List is used to indicate that the order of readers sending paging messages is Reader 1 -> Reader 2.

[0414] S1902, AMF sends service request 2 to reader 2. Correspondingly, reader 2 receives service request 2 from AMF.

[0415] Among them, business request 2 is used to request the first business, and business request 2 includes session ID 1, first indication information and reader list.

[0416] S1903, Reader 1 repeatedly sends paging message 1 to A-IoT device 1. Correspondingly, A-IoT device 1 receives paging message 1 from reader 1.

[0417] Among them, paging message 1 is associated with the first service, and paging message 1 includes session ID 1.

[0418] A-IoT device 1 receives paging message 1 and determines that session ID 1 in paging message 1 is a new session ID. A-IoT device 1 then responds to paging message 1, such as by performing random access and / or data transmission associated with the first service with reader 1. Furthermore, it saves session ID 1.

[0419] S1904, Reader 1 sends an end mark message 1 to Reader 2. Correspondingly, Reader 2 receives the end mark message 1 from Reader 1.

[0420] End message 1 includes session ID 1. Optionally, end message 1 may also include first indication information. A functional description of end message 1 can be found in the relevant descriptions in the above embodiments, and will not be repeated here.

[0421] S1905, the reader 2 repeatedly sends paging message 2 to the A-IoT device 1. Correspondingly, the A-IoT device 1 receives the paging message 2 from the reader 2.

[0422] Among them, paging message 2 is associated with the first service, and paging message 2 includes session ID2, which is used to identify the first service.

[0423] Based on the received session ID1 and the first indication information, reader 2 determines to generate a session ID2 that is different from session ID1, and sends the session ID2 in the paging message 2.

[0424] A-IoT device 1 receives paging message 2, compares session ID2 with the locally stored session ID1 to determine if they are the same identifier. If they are different, it responds to paging message 2 to perform the first service, such as random access with reader 2 and / or data transmission associated with the first service. It also saves session ID2. In other words, A-IoT device 1 needs to determine if the service identifier in the received paging message is the same as the service identifier previously responded to; if they are different, it responds to the paging message to perform the first service.

[0425] Therefore, different readers can generate different service identifiers based on the first instruction information sent by the CN, so that the same A-IoT device can respond to paging messages associated with the same service sent by different readers.

[0426] It should be understood that in the method embodiments shown in Figures 16 and 18, the first service corresponds to multiple different service identifiers. The different identifiers can be obtained by transforming the same identifier or by transforming different identifiers, and there is no limitation on this.

[0427] This application embodiment also provides a communication method that uses a service identifier, an access device identifier, and first indication information to jointly instruct a first device to respond to messages associated with a first service by different access devices. As shown in Figure 20, the communication method includes:

[0428] S2001, The first access device sends a first message. Correspondingly, the first device receives the first message.

[0429] The first message includes a first identifier, a seventh identifier, and a third indication information. The first identifier is used to identify the first service, the seventh identifier is used to identify the first access device, and the third indication information is used to instruct the first device to respond to the first message sent by the first access device.

[0430] For example, the seventh identifier is the reader ID. If the first access device is a terminal device, the seventh identifier can be a UE ID such as a temporary mobile subscriber identity (TMSI). If the first access device is a network device, the seventh identifier can be a cell ID or a TRP ID, etc. There are no restrictions on this.

[0431] Optionally, the seventh identifier can be the second identifier in the method embodiment shown in FIG13, which can be used by the first device to distinguish different access devices, and there is no limitation thereto.

[0432] In one possible design, the third indication information can be determined based on the first indication information, wherein the first indication information is used to indicate that the first message and the second message need to be responded to by the first device, and the second message is a message sent by the second access device that is associated with the first service. For example, the third indication information is the first indication information, or the third indication information is a new indication information generated by the first access device based on the first indication information, used to instruct the first device to respond to messages associated with the first service from different access devices.

[0433] For a detailed description of the first identifier, the first service, and the first instruction information, please refer to the relevant descriptions of the first identifier, the first service, and the first instruction information in S1301 above, which will not be repeated here.

[0434] In one possible design scheme 1, the first access device receives a first identifier and a first indication information from a core network element. For example, the core network element sends a first service request to the first access device, and correspondingly, the first access device receives the first service request from the core network element. The first service request is used to request a first service, and the first service request includes a first identifier and first indication information.

[0435] In one possible design scheme 2, the first access device receives a first identifier and a first indication information from the second access device. For example, a core network element sends a third service request to the second access device. Correspondingly, the second access device receives the third service request from the core network element. The third service request includes a first identifier, the first indication information, and a list of access device identifiers. This list includes the identifiers of the first access device and the second access device. Therefore, the second access device sends the first identifier and the first indication information to the first access device based on the identifier of the first access device in the identifier list.

[0436] In cases where more than two access devices send messages related to the first service and the first device responds, the method by which each access device obtains the first identifier and the first indication information is similar to the two design schemes for the first access device to obtain them, and will not be elaborated further.

[0437] In some implementations, the first identifier and / or the third indication information may also be indicated by the second access device to the first access device, without limitation.

[0438] For the second access device, the second message includes a first identifier, an eighth identifier, and a fourth indication information. The eighth identifier is used to identify the second access device. The fourth indication information is similar in function to the third indication information, or it can be determined based on the first indication information. This will not be elaborated further.

[0439] It should be understood that when the first indication information indicates that the first message and the second message do not need to be responded to by the first device, the third indication information can also be used to indicate that the first device does not respond to the first message, and the fourth indication information can also be used to indicate that the first device does not respond to the second message, without limitation.

[0440] S2002, the first device determines whether to respond to the first message based on the first identifier, the seventh identifier and the third indication information.

[0441] After receiving the first message, if the first identifier is the same as the service identifier in the previously received message associated with the first service (or the stored service identifier that has already been responded to), then the first device determines whether the first message and the previously received message containing the first identifier come from the same access device based on the seventh identifier. If not, it further determines whether it needs to respond to messages with the same service identifier from different access devices based on the third indication information.

[0442] For example, if the first device has previously responded to the second message sent by the second access device, then the first device determines that it has previously responded to the second message sent from the second access device, which includes the service identifier as the first identifier. After receiving the first message, the first device can determine, based on the identifier of the first access device and the third indication information in the first message, that it needs to respond to the second message sent from the first access device, which includes the service identifier as the first identifier.

[0443] Similarly, responding to the first message can involve random access and / or data transmission associated with the first service.

[0444] For each access device, the first device can set an access, data transmission, paging, or service status, or multiple access devices can correspond to one access, data transmission, paging, or service status. The access, data transmission, paging, or service status is released and updated according to the identifier of the access device and the first indication information.

[0445] The release or expiration time for access, data transmission, paging, or service status can be set at a time. This time setting can be indicated by the access device or core network element, and there are no restrictions on it.

[0446] For descriptions of access, data transmission, paging, or service status, please refer to the relevant descriptions in S1302 above, which will not be repeated here.

[0447] In the communication method shown in Figure 20, each of the multiple access devices that send messages associated with the first service can jointly instruct the first device to respond to the messages associated with the first service from different access devices through the service identifier, the access device identifier, and the third indication information.

[0448] The communication method shown in Figure 20 will be illustrated with specific examples in the following scenarios.

[0449] Taking the access device as the reader / writer, the first device as A-IoT device 1, the core network element as AMF, the message associated with the first service as a paging message, and the first identifier as session ID1, as an example where CN triggers reader / writer 1 and reader / writer 2 to send a paging message associated with the first service, which needs to be responded to by the first device, as shown in Figure 21, this communication method includes:

[0450] S2101, AMF sends service request 1 to reader 1. Correspondingly, reader 1 receives service request 1 from AMF.

[0451] Among them, Service Request 1 is used to request the first service. Service Request 1 includes Session ID 1 and First Indication Information. Session ID 1 is used to identify the first service, and the First Indication Information is used to indicate that Paging Message 1 and Paging Message 2 are responded to by A-IoT Device 1.

[0452] S2102, AMF sends service request 2 to reader 2. Correspondingly, reader 2 receives service request 2 from AMF.

[0453] Among them, business request 2 is used to request the first business, and business request 2 includes session ID 1 and first indication information.

[0454] S2103, Reader 1 repeatedly sends paging message 1 to A-IoT device 1. Correspondingly, A-IoT device 1 receives paging message 1 from reader 1.

[0455] Among them, paging message 1 is associated with the first service, and paging message 1 includes session ID 1, reader ID 1 and first indication information.

[0456] S2104, the reader 2 repeatedly sends paging message 2 to the A-IoT device 1. Correspondingly, the A-IoT device 1 receives the paging message 2 from the reader 2.

[0457] Among them, paging message 2 is associated with the first service, and paging message 2 includes session ID1, reader ID2 and first indication information.

[0458] For example, A-IoT device 1 first receives paging message 1. A-IoT device 1 determines that session ID 1 in paging message 1 is a new session ID and originates from a reader / writer 1. A-IoT device 1 responds to paging message 1, such as by performing random access and / or data transmission associated with the first service with reader / writer 1. It also saves session ID 1 and the ID of reader / writer 2. Then, when A-IoT device 1 receives paging message 2, it can determine that session ID 1 in paging message 2 is not a new session ID, but the sending reader / writer is a new reader / writer, i.e., reader / writer 2. A-IoT device 1 can then determine, based on the first indication information, that it needs to respond to paging messages with the same session ID from different readers, i.e., respond to paging message 2, such as by performing random access and / or data transmission associated with the first service with reader / writer 2. It also saves session ID 1 and the ID of reader / writer 2.

[0459] Therefore, the same A-IoT device can determine the response to paging messages with the same session ID received from different readers based on the session ID + reader ID + first indication information in the paging message.

[0460] In this embodiment, the first access device is a network device, and the second or seventh identifier can be the identification information of the network device. The identification information of the network device can be any identification information that can be used to represent a network device. For example, it could be the identification information of a TRP; the identification information of a packet radio unit (PRU); the identification information of an RRU; the identification information of a BBU; the identification information of an RRU hub; the identification information of a headend; the identification information of an antenna; the identification information of a relay device; the identification information of a cell; the identification information of a reader / writer; the identification information of an A-IoT reader / writer; the NR cell global identifier (CGI); AAU sector information; tracking area information; the identification information of an A-IoT-MF; the identification information of a tag management function (TMF); beam angle; distance information; and coverage level. Among these, the NR CGI is the identifier of the cell where the first device is located.

[0461] In another implementation, the second identifier or the seventh identifier can be an identifier that measures the location information of the first access device. The location information can include at least one of the following: TRP area information; PRU area information; RRU area information; BBU area information; RRU hub area information; headend area information; antenna area information; relay device area information; cell area information; reader area information; and A-IoT reader area information. The area corresponding to the area information of the TRP, PRU, RRU, BBU, RRU hub, headend, antenna, relay device, cell, reader, or A-IoT reader is part of the cell.

[0462] The first access device is a terminal device. The second or seventh identifier can be the terminal device's identification information. This identification information can be any information that can represent the terminal device. For example, the terminal device's identification information can be the terminal device's UE identity (UE ID), Internet Protocol (IP) address, MAC layer identification information, temporary identification information, access layer identification information, core network identification information, application layer identification information, non-access layer identification information, A-IoT MAC layer identification information, etc. Alternatively, the terminal device's identification information can also be temporary identification information configured for the terminal device by the network device or core network device, such as NGAP UE ID, AMF UE ID, etc. There are no restrictions. Based on this temporary identification information, the first terminal device can be identified more conveniently, while also saving signaling overhead.

[0463] It should be understood that the embodiments of this application do not limit the type or name of each piece of information, message, signaling, and device in the above embodiments. For example, a service request can be replaced with an inventory request or command request or other IoT service requests in other environments.

[0464] When the access device is a network device, the steps performed by the access device can be executed by the network device or a module or chip within the network device. For example, in the O-RAN architecture shown in Figure 11 or Figure 12 above, the actions performed by the access device can be transmitted between the CU and DU, or the CU can receive information from the core network element and then send it to the DU for processing, or the DU can generate information, send it to the CU, and then the CU can send it out. There are no limitations on this.

[0465] It is understood that, in the above embodiments, the methods and / or steps implemented by the access device can also be implemented by components (e.g., processors, chips, chip systems, circuits, logic modules, or software) that can be used in the access device; the methods and / or steps implemented by the first device can also be implemented by components (e.g., processors, chips, chip systems, circuits, logic modules, or software) that can be used in the first device; and the methods and / or steps implemented by the core network element can also be implemented by components (e.g., processors, chips, chip systems, circuits, logic modules, or software) that can be used in the core network element.

[0466] The foregoing mainly describes the solutions provided in this application. Accordingly, this application also provides a communication device for implementing various methods in the above method embodiments. This communication device can be an access device in the above method embodiments, or a device containing an access device, or a component that can be used in an access device, such as a chip or chip system. Alternatively, the communication device can be the first device in the above method embodiments, or a device containing a first device, or a component that can be used in a first device, such as a chip or chip system. Alternatively, the communication device can be a core network element in the above method embodiments, or a device containing a core network element, or a component that can be used in a core network element, such as a chip or chip system.

[0467] It is understood that, in order to achieve the aforementioned functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, 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 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.

[0468] This application embodiment can divide the communication device into functional modules according to the above method embodiment. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0469] Taking the communication device as an example, specifically the access device, the first device, or the core network element in the above method embodiments, Figure 22 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. As shown in Figure 22, the communication device 2200 includes a processing module 2201 and a transceiver module 2202. The processing module 2201 is used to execute the processing functions of the access device, the first device, or the core network element in the above method embodiments. The transceiver module 2202 is used to execute the transceiver functions of the access device, the first device, or the core network element in the above method embodiments. All relevant content of each step involved in the above method embodiments can be referenced from the functional descriptions of the corresponding functional modules, and will not be repeated here.

[0470] In one possible design, in this embodiment of the application, the transceiver module 2202 may include a receiving module and a sending module (not shown in FIG22). The sending module and the receiving module are respectively used to implement the sending and receiving functions of the communication device 2200.

[0471] In one possible design, the communication device 2200 may further include a storage module (not shown in FIG. 22) that stores programs or instructions. When the processing module 2201 executes the program or instructions, the communication device 2200 can perform the functions of the access device, the first device, or the core network element in any of the methods shown in FIG. 13-FIG. 21.

[0472] In some embodiments, the processing module 2201 involved in the communication device 2200 may be implemented by a processor or processor-related circuit components, and may be a processor or processing unit; the transceiver module 2202 may be implemented by a transceiver or transceiver-related circuit components, and may be a transceiver or transceiver unit.

[0473] For example, Figure 23 is a schematic diagram of another communication device provided in an embodiment of this application. This communication device can be an access device, a first device, or a core network element as described in the above method embodiments, or it can be a chip (system) or other component or assembly that can be disposed in the access device, the first device, or the core network element. As shown in Figure 23, the communication device 2300 may include a processor 2301, a bus 2302, a communication interface 2303, and a memory 2304. The processor 2301, the memory 2304, and the communication interface 2303 communicate via the bus 2302. The communication device 2300 can be the aforementioned access device, the first device, or a core network element. It should be understood that this application does not limit the number of processors and memories in the communication device 2300.

[0474] Bus 2302 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, only one line is used in Figure 23, but this does not imply that there is only one bus or one type of bus. Bus 2302 can include pathways for transmitting information between various components of communication device 2300 (e.g., memory 2304, processor 2301, communication interface 2303).

[0475] The processor 2301 may include any one or more processors such as a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

[0476] The memory 2304 may include volatile memory, such as random access memory (RAM). The processor 2301 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD).

[0477] The communication interface 2303 uses a transceiver module, such as, but not limited to, a network interface card or transceiver, to enable communication between the communication device 2300 and other devices or communication networks. The memory 2304 stores executable program code, which the processor 2301 executes to implement the functions of the network device or terminal device in the aforementioned method embodiments. That is, the memory 2304 stores instructions for executing the aforementioned communication method.

[0478] In another aspect, embodiments of this application also provide a computer program product containing instructions, including computer program code, which, when run on a communication device, enables the communication device to execute the methods described in any of the above embodiments.

[0479] Furthermore, embodiments of this application also provide a computer-readable storage medium. This computer-readable storage medium stores a computer program or instructions that, when executed on a communication device, enable the communication device to perform the methods described in any of the above embodiments.

[0480] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is 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, 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 containing one or more servers, data centers, etc., that can be integrated with the medium. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video disks (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

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

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

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

[0484] 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. Furthermore, the functional units in the various embodiments of this application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0485] 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, ROM, RAM, magnetic disks, or optical disks.

[0486] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, the disclosure, and the appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple instances. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

[0487] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the spirit and scope of this application. Accordingly, this specification and drawings are merely exemplary illustrations of this application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from the spirit and scope of this application. Thus, if such modifications and modifications of this application fall within the scope of the claims of this application and their equivalents, this application is also intended to include such modifications and modifications.

Claims

1. A communication method, characterized in that, The method includes: (The chip is applied in a first access device or a first access network device.) Send a first message, which is associated with a first identifier. The first identifier is used to identify the first service. The first message includes a second identifier. Communicates with a first device, which is a device that responds to the first message.

2. The method according to claim 1, characterized in that, The method further includes: The device receives the first identifier and the first indication information. The first indication information is used to indicate that the first message and the second message need to be responded to by the first device. The first message is a message sent by the first access device that is associated with the first service, and the second message is a message sent by the second access device that is associated with the first service.

3. The method according to claim 1 or 2, characterized in that, The method further includes: Receive second indication information, the second indication information being used to determine the second identifier, the second indication information being used to indicate at least one of the following: the location index of the first access device among a plurality of access devices that send a message associated with the first service, a third identifier in the message associated with the first service sent by the second access device, or the second identifier, wherein the plurality of access devices includes the second access device, and the third identifier is different from the second identifier.

4. A communication method, characterized in that, The method, which applies to a first device or a chip in the first device, includes: Receive a first message, the first message being associated with a first identifier, the first identifier being used to identify a first service, and the first message including a second identifier; Whether to respond to the first message is determined based on the second identifier.

5. The method according to claim 4, characterized in that, Determining whether to respond to the first message based on the second identifier includes: If the second identifier is different from the stored identifier, respond to the first message.

6. The method according to claim 4 or 5, characterized in that, The method further includes: A second message is received, which is associated with the first identifier and includes a third identifier that is different from the second identifier.

7. A communication method, characterized in that, The method includes applying a chip to a core network element or a chip within the core network element: Send a first identifier and a first indication information to a first access device. The first identifier is used to identify a first service, and the first indication information is used to indicate that a first message and a second message need to be responded to by the first device. The first message is a message associated with the first service sent by the first access device, and the second message is a message associated with the first service sent by the second access device. Communicate with the first access device.

8. The method according to claim 7, characterized in that, The method further includes: Receive a third identifier of the second access device, wherein the third identifier is an identifier carried in the second message.

9. The method according to claim 7 or 8, characterized in that, The method further includes: Send a second indication message to the first access device. The second indication message is used to determine a second identifier, which is an identifier carried in the first message. The second indication message is used to indicate at least one of the following: the location index of the first access device among multiple access devices that send messages associated with the first service, a third identifier, or the second identifier, wherein the third identifier is an identifier carried in the second message, and the multiple access devices include the second access device.

10. A communication method, characterized in that, The method further includes: a chip applied to a core network element or a core network element; and a chip used in a core network element. Send a first service request to the first access device, wherein the first service request includes a first identifier; A second service request is sent to the first access device. The second service request includes a fourth identifier, and the first identifier and the fourth identifier are used to identify the first service.

11. A communication method, characterized in that, The method further includes: (The method is applied to a first access device or a chip within the first access device.) Receive a first service request from a core network element, wherein the first service request includes a first identifier; A second service request is received from the core network element. The first service request includes a fourth identifier, and the first identifier and the fourth identifier are used to identify the first service.

12. The method according to claim 11, characterized in that, The method further includes: Send a first message, the first message including an identifier associated with the first identifier; Send a third message, the third message including an identifier related to the fourth identifier, the first message and the third message being messages associated with the first service.

13. A communication method, characterized in that, The method further includes: (The chip is applied to a first access device or within the first access device.) Receive a fifth identifier and a first indication information, wherein the fifth identifier is used to identify a first service, and the first indication information is used to indicate that a first message and a second message need to be responded to by a first device, wherein the first message is a message associated with the first service sent by the first access device, and the second message is a message associated with the first service sent by the second access device. Send the first message, which includes a sixth identifier used to identify the first service. The sixth identifier is determined based on the fifth identifier and the first indication information.

14. The method according to claim 13, characterized in that, The receiving of the fifth identifier and the first indication information includes: Receive the fifth identifier from the second access device, the fifth identifier being an identifier carried in the second message; Receive the first indication information from the core network element.

15. The method according to claim 13, characterized in that, The receiving of the fifth identifier and the first indication information includes: The system receives the fifth identifier and the first indication information from a core network element or the second access device, wherein the fifth identifier is an identifier carried in the second message.

16. A communication method, characterized in that, The method further includes: (1) A chip applied to a core network element or a chip within the core network element; Send a first identifier and a first indication information. The first identifier is used to identify a first service, and the first indication information is used to indicate that a first message and a second message need to be responded to by a first device. The first message is a message associated with the first service sent by a first access device, and the second message is a message associated with the first service sent by a second access device. Communicate with the first access device.

17. The method according to claim 16, characterized in that, The method further includes: Receive a fifth identifier from the second access device, the fifth identifier being used to identify the first service, and the fifth identifier being an identifier carried in the second message.

18. A communication method, characterized in that, The method, which applies to a first access device or a chip within the first access device, includes: Send a first message, the first message including a first identifier, a seventh identifier and third indication information, the first identifier being used to identify a first service, the seventh identifier being used to identify the first access device, and the third indication information being used to instruct the first device to respond to the first message sent by the first access device; Communicate with the first device.

19. The method according to claim 18, characterized in that, The method further includes: The device receives the first identifier and the first indication information from a core network element or a second access device. The first indication information is used to indicate that the first message and the second message need to be responded to by the first device. The second message is a message sent by the second access device that is associated with the first service.

20. A communication method, characterized in that, The method further includes: (The method is applied to a first device or a chip in the first device.) Receive a first message, the first message including a first identifier, a seventh identifier and third indication information, the first identifier being used to identify a first service, the seventh identifier being used to identify a first access device, and the third indication information being used to instruct the first device to respond to the first message sent by the first access device; Whether to respond to the first message is determined based on the first identifier, the seventh identifier, and the third indication information.

21. A communication device, characterized in that, Includes modules for performing the method as described in any one of claims 1-20.

22. A communication device, characterized in that, include: processor; The processor is configured to run computer programs or instructions to enable the method as described in any one of claims 1-20 to be implemented.

23. A communication chip, characterized in that, It stores instructions that, when the chip is running on a communication device, cause the method as described in any one of claims 1-20 to be implemented.

24. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions, which, when executed by a communication device, implement the method as described in any one of claims 1-20.

25. A computer program product, characterized in that, It includes computer program code, which, when run on a communication device, implements the method as described in any one of claims 1-20.

Images