Communication method and apparatus

Abstract

The present application belongs to the technical field of communications. Provided are a communication method and apparatus, which are used for improving the efficiency of operating a plurality of terminal devices. In the method, after receiving a random access request of a terminal device, an access network device can determine for the terminal device an identifier used in a first signaling layer, such that the access network device and a core network device can indicate the terminal device by means of the identifier, so as to operate the terminal device. That is, the access network device and the core network device can set, for each terminal device among a plurality of terminal devices that are required to be operated, an identifier that can be used in the first signaling layer. In this case, the access network device can initiatively trigger the random access of each of the plurality of terminal devices without depending on an indication of the core network device, and during the random access of each terminal device, the core network device can operate a terminal device which has completed the random access, and thus the efficiency of operating the plurality of terminal devices can be improved.

Description

Communication method and device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on February 7, 2024, with application number 202410175965.8 and application name “Communication Method and Device”, and the Chinese patent application filed with the State Intellectual Property Office on August 9, 2024, with application number 202411098009.0 and application name “Communication Method and Device”, the entire contents of which are incorporated by reference into this application. Technical Field

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

[0003] In the Ambient IoT (A-IoT), when multiple devices need to be operated, the reader relies on instructions from core network elements (such as the access and mobility management function (AMF) and the tag management function (TMF)) to access multiple devices. Furthermore, after a terminal device completes random access, the core network element will operate on that terminal device. Only after the operation on the terminal device is completed will the reader trigger random access for the next terminal device.

[0004] However, the above method is relatively inefficient. How to improve the efficiency of operating multiple terminal devices is a hot topic currently under discussion. Summary of the Invention

[0005] Embodiments of the present application provide a communication method and apparatus for improving the efficiency of operations of multiple terminal devices.

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

[0007] In a first aspect, a communication method is provided. This method can be executed by an access network device, or by a component of the access network device, such as a processor, chip, or chip system of the access network device. It can also be implemented by a logic module or software that implements all or part of the functions of the access network device. The access network device can be a device with access functionality. When a terminal device functions as a reader / writer, the terminal device is considered an access network device, meaning that the terminal device can access other terminal devices and connect to core network devices. The access network device can also be other devices without limitation. The following description uses the method executed by an access network device as an example. The method includes: after receiving a first random access request from a first terminal device, the access network device determines the first identifier of the first terminal device, and the first identifier is used to indicate the first terminal device at a first signaling layer; the access network device sends the first identifier and the identifier of the first terminal device to a core network device, and the identifier of the first terminal device is used to indicate the first terminal device at a second signaling layer; the access network device receives an operation request message from the core network device, and the operation request message is determined based on the identifier of the first terminal device, and the operation request message includes the first identifier and an operation instruction; the access network device obtains a second identifier based on the first identifier, and the second identifier is used to indicate the first terminal device at an access control layer; the access network device sends the operation instruction and the second identifier to the first terminal device.

[0008] Based on the method of the first aspect, it can be known that after the access network device receives the random access request of the terminal device, such as when the access network device completes the random access process with the terminal device, and such as when the access network device is in the process of executing the random access process with the terminal device, it can determine the identifier used in the first signaling layer for the terminal device, so that the access network device and the core network device can indicate the terminal device through the identifier, thereby realizing the operation of the terminal device. For example, after the core network device determines the operation of the first terminal device according to the identifier of the first terminal device, it can send an operation request message to the access network device, and the operation request message includes a first identifier and an operation instruction, that is, the terminal device indicated by the first identifier (that is, the first terminal device) is instructed to perform the operation indicated by the operation instruction through the operation request message; the access network device can determine whether to send an operation instruction to the first terminal device according to the operation request message, that is, at this time the access network device can send a second identifier and an operation instruction to the first terminal device, so that the first terminal device can determine that the operation instruction is an instruction sent to it through the second identifier, thereby performing the operation indicated by the operation instruction. That is to say, the access network device and the core network device can set an identifier that can be used for the first signaling layer for each terminal device among the multiple terminal devices that need to be operated. In this case, the access network device can trigger the random access of each terminal device among the multiple terminal devices without relying on the instructions of the core network device, and the core network device can operate the terminal device that has completed random access during the random access of the terminal device. That is, at this time, the random access of each terminal device among the multiple terminal devices and the operation of the terminal device may not be serial, that is, there is no need to complete the random access and operation of one terminal device before performing random access and operation on the next terminal device, thereby improving the efficiency of operating multiple terminal devices.

[0009] It can be understood that the operation instruction and the second identifier can be two parallel pieces of information, or the second identifier can be carried in the operation instruction. The specific form can be flexibly set according to actual conditions and is not limited.

[0010] In one possible design, the method of the first aspect further includes: the access network device receiving a first random access request, the first random access request including a second identifier; and determining the first identifier of the first terminal device includes: the access network device assigning the first identifier to the first terminal device based on the second identifier. It is understood that the access network device may generate the first identifier based on the second identifier, and the first identifier is different from the second identifier.

[0011] Optionally, the method described in the first aspect further includes: the access network device storing the context of the first terminal device, where the context of the first terminal device includes the second identifier and the first identifier. It is understood that the first identifier and the second identifier have a corresponding relationship. After assigning the first identifier to the first terminal device, the access network device can maintain the corresponding relationship between the first identifier and the second identifier, so that the access network device can subsequently determine the second identifier based on the first identifier, thereby sending an operation instruction to the first terminal device based on the second identifier.

[0012] Furthermore, the operation request message also includes first indication information, which is used to instruct the access network device to delete the context of the first terminal device after completing the operation on the first terminal device. It is understood that after completing the operation on the first terminal device, the access network device may no longer use the context of the first terminal device, or may not use the context of the first terminal device for a period of time after completing the operation on the first terminal device. In this way, the access network device can release the context of the first terminal device in a timely manner, thereby avoiding redundancy and improving storage efficiency.

[0013] Furthermore, before the access network device receives the first random access request, the method described in the first aspect also includes: the access network device receives an operation task request message from the core network device, and the operation task request message includes a task identifier; the access network device broadcasts a second random access request based on the operation task request message; and the context of the first terminal device also includes a task identifier. In other words, the access network device can associate the first identifier, the second identifier, and the task identifier, that is, the first identifier, the second identifier, and the task identifier have a corresponding relationship, such as the task identifier has a corresponding relationship with the first identifier, and the first identifier has a corresponding relationship with the second identifier. In this way, it is convenient for the core network device to manage the operation task indicated by the task identifier through the task identifier, for example: after the operation task is completed, the access network device is instructed to delete the context containing the task identifier, thereby deleting the entire context of the terminal device corresponding to the completed operation task. In this way, management can be performed at the task granularity.

[0014] Optionally, the second identifier is the identifier of a first process, which is used by the first terminal device to perform a random access procedure, and the first process is related to the access control layer. That is, the first process can be used by the first terminal device to perform random access, that is, the first terminal device can perform random access within the first process. It is understood that when the access network device has multiple processes available for random access, the access network device can assign the first process to the first terminal device; alternatively, the first terminal device can select a process independently, such as by broadcasting identifiers corresponding to multiple processes, and the first terminal device selecting a process based on the identifiers. In this case, the first process can indicate a unique terminal device, namely, the first terminal device, and therefore the second identifier can be the identifier of the first process. It is also understood that the first process can also be used by the first terminal device to perform an operation indicated by an operation instruction, that is, the first process can also be used by the first terminal device to perform the operation indicated by the operation instruction, that is, the first terminal device can perform the operation within the first process.

[0015] Optionally, the second identifier is a random number RN16. It is understandable that the second identifier can be a label (i.e., a temporary identifier) ​​temporarily used by the terminal device during the random access process, and can be represented by RN16. The value of RN16 can be generated by the first terminal device, or configured by the network side, such as by the access network device, or predefined by the protocol. It can be flexibly set according to actual conditions without limitation. Of course, the second identifier can also be other types of identifiers without limitation.

[0016] In a possible design scheme, the method described in the first aspect also includes: the access network device receives a first random access request, the first random access request includes a second identifier; determining the first identifier of the first terminal device includes: the access network device determines that the second identifier is the first identifier. That is, the first identifier can reuse the second identifier. In other words, after receiving the second identifier of the access control layer, the access network device can reuse the second identifier of the access control layer to the first identifier of the first signaling layer, that is, the access network device can assign the value of the second identifier to the first identifier, and at this time the values ​​of the second identifier and the first identifier are the same. In this way, the access network device does not need to generate the first identifier, thereby reducing the processing overhead of the access network device.

[0017] Optionally, before the access network device receives the first random access request, the method described in the first aspect also includes: the access network device receives an operation task request message from the core network device, the operation task request message includes a task identifier; the access network device broadcasts a second random access request based on the operation task request message; after the access network device determines that the second identifier is the first identifier, the access network device saves the context of the first terminal device, and the context of the first terminal device includes the task identifier and the first identifier. In other words, the access network device can associate the first identifier with the task identifier, that is, the first identifier and the task identifier have a corresponding relationship. In this way, it is convenient for the core network device to manage the operation task indicated by the task identifier through the task identifier, for example: after the operation task is completed, the access network device is instructed to delete the context including the task identifier, thereby deleting the entire context of the terminal device corresponding to the completed operation task. In this way, management can be performed at the task granularity.

[0018] Furthermore, after the access network device saves the context of the first terminal device, the method described in the first aspect also includes: the access network device receives a task identifier and a second indication information from the core network device, the second indication information is used to instruct the access network device to delete the context containing the task identifier; the access network device deletes the context of the first terminal device according to the task identifier and the second indication information. It can be understood that the core network device can instruct the access network device to delete the context containing the task identifier after determining that the operation task indicated by the task identifier is completed. In this way, the context of each terminal device corresponding to the operation task can be deleted as a whole, that is, there is no need for the core network device to send multiple indication information for deleting the context of the terminal device to the access network device, thereby reducing the communication overhead of the core network device.

[0019] Optionally, the second identifier is an identifier of a first process, the first process is used by the first terminal device to execute a random access procedure, and the first process is related to the access control layer.

[0020] Optionally, the second identifier is a random number RN16.

[0021] In a possible design scheme, before the access network device sends the first identifier and the identifier of the first terminal device to the core network device, the method described in the first aspect also includes: the first terminal device performs a random access process through a first process. That is, the first terminal device can perform a random access process within the first process. It can be understood that the first process can also be used by the first terminal device in the operation process indicated by the operation instruction, that is, the first process can also be used for the first terminal device to perform the operation indicated by the operation instruction, that is, the first terminal device can perform the operation within the first process. In addition, when the access network device has multiple processes that can be used for random access, the access network device can allocate the first process to the first terminal device; or, the first terminal device can select a process, such as the access network device broadcasts identifiers corresponding to multiple processes, and the first terminal device selects a process based on the identifier.

[0022] Optionally, the first terminal device performs a random access procedure through a first process, including: the access network device broadcasts a second random access request, the second random access request includes an identifier of the first process, the first process is used by the terminal device to perform the random access procedure, and the first process is associated with the access control layer; the access network device receives the first random access request, the first random access request includes the identifier of the first process; the access network device sends a confirmation message to the first terminal device based on the first random access request, the confirmation message includes the identifier of the first process; and the access network device receives the identifier of the first terminal device from the first terminal device. In this way, the first terminal device can achieve random access through the first process.

[0023] Furthermore, before the first terminal device completes random access, the method described in the first aspect also includes: the access network device broadcasts a third random access request, the third random access request includes an identifier of a second process, the second process is used by the terminal device in executing the random access process, and the second process is related to the access control layer. It can be understood that the second process is different from the first process, and the access network device can broadcast the third random access request after broadcasting the second random access request. In other words, the access network device does not need to trigger the random access of the next terminal device after the random access of the first terminal device is completed, that is, the access network device can trigger the random access of the next terminal device during the process of random access of the first terminal device, such as during the time period of waiting for feedback information from the first terminal device, thereby improving the time slot utilization of the access network device.

[0024] In one possible design, the operation request message may further include a third identifier of the first terminal device determined by the core network device. This third identifier may be used to indicate the first terminal device at the first signaling layer and may be used to identify the first terminal device between the access network device and the core network device. The third identifier may be determined based on the identifier of the first terminal device or the first identifier; in other words, the third identifier may be allocated based on the identifier of the first terminal device or the first identifier.

[0025] In one possible design scheme, after the access network device sends the operation instruction and the second identifier to the first terminal device, the method described in the first aspect further includes: the access network device receives the operation result from the first terminal device, and the operation result is the result of the first terminal device executing the operation instruction; the access network device sends the operation result and the first identifier to the core network device. In other words, the access network device can send the result of the first terminal device executing the operation indicated by the operation instruction to the core network device. It can be understood that the core network device can send the operation result to the service requester (such as a server) so that the service requester adjusts the service based on the operation result.

[0026] In one possible design scheme, the core network device is AMF or TMF (or passive Internet of Things device management function AIoTMF), which can be flexibly set according to actual conditions without any restrictions.

[0027] In one possible design scheme, the first signaling layer is the Next Generation Application Protocol NGAP layer.

[0028] In one possible design scheme, the second signaling layer is a non-access NAS layer.

[0029] In a second aspect, a communication method is provided. The method can be executed by a core network device, or by a component of the core network device, such as a processor, chip, or chip system of the core network device, or by a logic module or software that can implement all or part of the core network device functions. The following description takes the method executed by the core network device as an example. The method includes: the core network device receives a first identifier and an identifier of a first terminal device from an access network device, the first identifier being used to indicate the first terminal device at a first signaling layer, and the identifier of the first terminal device being used to indicate the first terminal device at a second signaling layer; the core network device determines an operation for the first terminal device based on the identifier of the first terminal device; and the core network device sends an operation request message to the access network device, the operation request message including the first identifier and an operation instruction.

[0030] In a possible design scheme, the operation request message also includes first indication information, and the first indication information is used to instruct the access network device to delete the context of the first terminal device after completing the operation on the first terminal device.

[0031] In one possible design scheme, the operation request message may also include a third identifier of the first terminal device determined by the core network device.

[0032] In one possible design scheme, before the core network device receives the first identifier and the identifier of the first terminal device from the access network device, the method described in the second aspect also includes: the core network device sends an operation task request message to the access network device, and the operation task request message includes a task identifier; after determining that the operation task indicated by the task identifier is completed, the core network device sends the task identifier and second indication information to the access network device, and the second indication information is used to instruct the access network device to delete the context containing the task identifier.

[0033] In one possible design scheme, the operation of the first terminal device is an environmental energy Internet of Things operation, such as inventory operation, write operation, read operation, invalidation operation, interactive information operation, etc., which can be set according to actual conditions without restriction.

[0034] In one possible design scheme, the core network device is AMF or TMF (or passive Internet of Things device management function AIoTMF).

[0035] In one possible design scheme, the first signaling layer is the Next Generation Application Protocol NGAP layer.

[0036] In one possible design scheme, the second signaling layer is a non-access NAS layer.

[0037] In addition, the technical effects of the method described in the second aspect can also refer to the technical effects of the method described in the first aspect, and will not be repeated here.

[0038] In a third aspect, a communication method is provided. The method can be executed by a first terminal device, or by a component of the first terminal device, such as a processor, chip, or chip system of the first terminal device, or by a logic module or software that can implement all or part of the functions of the first terminal device. The following description takes the method executed by the first terminal device as an example. The method includes: the first terminal device receives a second random access request from an access network device, the second random access request includes an identifier of a first process, the first process is used by the terminal device in executing a random access procedure, and the first process is related to the access control layer; the first terminal device sends a first random access request to the access network device based on the second random access request, the first random access request includes an identifier of the first process; the first terminal device receives a confirmation message from the access network device, and sends the identifier of the first terminal device to the access network device based on the confirmation message, the confirmation message includes the identifier of the first process, and the identifier of the first terminal device is used to indicate the first terminal device at the second signaling layer.

[0039] In one possible design, before the first terminal device receives the first random access request from the access network device, the method according to the third aspect further includes: the first terminal device receiving a process number for random access; and the first terminal device determining, based on the process number, to participate in the random access corresponding to the first process. It is understood that the process number is the number of processes determined by the access network device that can be used for random access, and the process number is an integer greater than 1.

[0040] In addition, the technical effects of the method described in the third aspect can also refer to the technical effects of the method described in the first aspect, and will not be repeated here.

[0041] In a fourth aspect, a communication method is provided. The method can be executed by a reader / writer, or by a component of the reader / writer, such as a processor, chip, or chip system of the reader / writer, or by a logic module or software that can realize all or part of the functions of the reader / writer. The reader / writer can also be a terminal device. The following description takes the method executed by a reader / writer as an example. The method includes: after receiving a first random access request from a first terminal device, the reader / writer determines a first identifier of the first terminal device, and the first identifier is used to indicate the first terminal device at the access control layer; the reader / writer sends a first identifier and first information to the access network device, and the first information is used to indicate the first terminal device at the first signaling layer; the reader / writer receives a first operation request message from the access network device, and the first operation request message includes a first identifier and an operation instruction, and the operation instruction is determined based on the first information; the reader / writer obtains a second identifier based on the first identifier, and sends the operation instruction and the second identifier to the first terminal device, and the second identifier is used to indicate the first terminal device at the second signaling layer.

[0042] Based on the method of the fourth aspect, it can be known that after receiving the random access request of the terminal device, the reader / writer can determine the identifier used in the access control layer for the terminal device, so that the terminal device can be indicated by the identifier between the reader / writer and the access network device, thereby realizing the operation of the terminal device. In this way, when the reader / writer needs to operate on multiple terminal devices, it can trigger the random access of each terminal device in the multiple terminal devices independently without relying on the instructions of the core network network element, that is, the reader / writer can determine a different identifier for each terminal device in the multiple terminal devices that need random access to distinguish different terminal devices. In this case, the core network network element can operate the terminal device that has completed random access during the process of random access of the terminal device, that is, there is no need to wait until the random access and operation of one terminal device are completed before performing random access and operation on the next terminal device, thereby improving the efficiency of operations on multiple terminal devices.

[0043] In a possible design scheme, the method described in the fourth aspect also includes: the reader receives a first random access request, the first random access request includes a second identifier; the reader determines the first identifier of the first terminal device, including: the reader assigns the first identifier to the first terminal device based on the second identifier.

[0044] Optionally, the method described in the fourth aspect further includes: the reader / writer storing the correspondence between the first identifier and the second identifier, so that the reader / writer can subsequently determine the second identifier based on the first identifier, thereby sending an operation instruction to the first terminal device based on the second identifier.

[0045] Optionally, the method described in the fourth aspect further includes: the reader / writer saves a first context of the first terminal device, where the first context includes a first identifier and a second identifier.

[0046] Furthermore, the first operation request message also includes first indication information, and the first indication information is used to instruct the reader to delete the first context after completing the operation on the first terminal device.

[0047] Furthermore, the first context also includes a task identifier. Before the reader / writer receives the first random access request, the method described in the fourth aspect also includes: the reader / writer device receives a first operation task request message from the access network device, and the first operation task request message includes a task identifier; the access network device broadcasts a second random access request based on the first operation task request message.

[0048] Furthermore, after the reader / writer saves the first context of the first terminal device, the method described in the fourth aspect also includes: the reader / writer receives a task identifier and third indication information from the access network device, the third indication information being used to instruct the reader / writer to delete the context containing the task identifier; the reader / writer deletes the first context based on the task identifier and the third indication information.

[0049] In a possible design scheme, the method described in the fourth aspect also includes: the reader / writer receives an operation result from the first terminal device, and the operation result is the result of the first terminal device executing the operation indicated by the operation instruction; the reader / writer sends the operation result and the first identifier to the access network device.

[0050] In a possible design scheme, the method described in the fourth aspect also includes: the reader receives a first random access request, the first random access request includes a second identifier; the reader determines the first identifier of the first terminal device, including: the reader determines the second identifier as the first identifier.

[0051] Optionally, before the reader receives the first random access request, the method described in the fourth aspect also includes: the reader device receives a first operation task request message from the access network device, and the first operation task request message includes a task identifier; the reader broadcasts a second random access request based on the operation task request message; after the reader determines that the second identifier is the first identifier, the reader saves the first context of the first terminal device, and the first context includes the task identifier and the first identifier.

[0052] Furthermore, after the reader / writer saves the first context of the first terminal device, the method described in the fourth aspect also includes: the reader / writer receives a task identifier and third indication information from the access network device, the third indication information being used to instruct the reader / writer to delete the context containing the task identifier; the reader / writer deletes the first context based on the task identifier and the third indication information.

[0053] In one possible design scheme, the access control layer is any one of the following: media access control MAC layer, physical PHY layer, packet data convergence protocol PDCP layer, radio resource control RRC layer, or radio link control RLC layer.

[0054] In one possible design scheme, the first signaling layer is a non-access NAS layer.

[0055] In one possible design scheme, the second signaling layer is the access AS layer.

[0056] In a fifth aspect, a communication method is provided, which can be executed by an access network device, or by a component of the access network device, such as a processor, chip, or chip system of the access network device, or by a logic module or software that can realize all or part of the functions of the access network device. The following is an illustration of the method executed by the access network device. The method includes: after receiving a first identifier and first information from a reader / writer, the access network device determines a third identifier, the first identifier is used to indicate the first terminal device at the access control layer, the first information is used to indicate the first terminal device at the first signaling layer, and the third identifier is used to indicate the first terminal device at the third signaling layer; the access network device sends the third identifier and the first information to the core network network element; the access network device receives a second operation request message from the core network network element, the second operation request message is determined based on the first information, and the second operation request message includes the third identifier and an operation instruction; the access network device obtains the first identifier based on the third identifier, and sends a first operation request message to the reader / writer, the first operation request message includes an operation instruction and the first identifier.

[0057] Based on the fifth aspect, it can be known that after the access network device receives the first identifier used to indicate the first terminal device at the access control layer, it can determine the third identifier that can be used for the third signaling layer based on the first identifier, and send the third identifier to the core network network element, so that the first terminal device can be indicated at the third signaling layer between the access network device and the core network element through the third identifier, thereby realizing the indication of the operation of the first terminal device.

[0058] In a possible design scheme, the method described in the fifth aspect also includes: the access network device receives the first identifier and the first information; the access network device determines the third identifier, including: the access network device allocates the third identifier to the first terminal device based on the first identifier.

[0059] Optionally, the method described in the fifth aspect also includes: the access network device saves the correspondence between the first identifier and the third identifier.

[0060] Optionally, the method described in the fifth aspect also includes: the access network device saves the second context of the first terminal device, and the second context includes the first identifier and the third identifier.

[0061] Furthermore, the second operation request message also includes second indication information, and the second indication information is used to instruct the access network device to delete the context of the first terminal device after completing the operation on the first terminal device.

[0062] Furthermore, the second context also includes a task identifier. Before the access network device receives the first identifier and the first information, the method described in the fifth aspect also includes: the access network device receives a second operation task request message from the core network network element, and the second operation task request message includes a task identifier; the access network device sends a first operation task request message to the reader / writer based on the second task request message, and the first operation task request message includes a task identifier.

[0063] Furthermore, after the access network device saves the second context of the first terminal device, the method described in the fifth aspect also includes: the access network device receives a task identifier and fourth indication information from the core network network element, and the fourth indication information is used to instruct the access network device to delete the context containing the task identifier; the access network device deletes the second context according to the task identifier and the fourth indication information.

[0064] In a possible design scheme, the method described in the fifth aspect also includes: the access network device receives the operation result from the reader / writer, and the operation result is the result of the first terminal device executing the operation indicated by the operation instruction; the access network device sends the operation result and the third identifier to the core network network element.

[0065] In a possible design scheme, the method described in the fifth aspect also includes: the access network device receives the first identifier and the first information; the access network device determines the third identifier, including: the access network device determines that the first identifier is the third identifier.

[0066] Optionally, before the access network device receives the first identifier and the first information, the method described in the fifth aspect also includes: the access network device receives a second operation task request message from the core network network element, and the second operation task request message includes a task identifier; the access network device sends a first operation task request message to the reader / writer based on the second task request message, and the first operation task request message includes a task identifier; after the access network device determines that the first identifier is the third identifier, the access network device saves the second context of the first terminal device, and the second context includes the task identifier and the third identifier.

[0067] Furthermore, after the access network device saves the second context of the first terminal device, the method described in the fifth aspect also includes: the access network device receives a task identifier and fourth indication information from the core network network element, and the fourth indication information is used to instruct the access network device to delete the context containing the task identifier; the access network device deletes the second context according to the task identifier and the fourth indication information.

[0068] In one possible design scheme, the access control layer is any one of the following: media access control MAC layer, physical PHY layer, packet data convergence protocol PDCP layer, access control layer RRC layer, or radio link control RLC layer.

[0069] In one possible design scheme, the first signaling layer is a non-access NAS layer.

[0070] In one possible design, the third signaling layer is the Next Generation Application Protocol (NGAP) layer.

[0071] In one possible design, the core network element is any one of the following: access and mobility management function, or passive IoT device management function.

[0072] In addition, the technical effects of the method described in the fifth aspect can also refer to the technical effects of the method described in the fourth aspect, and will not be repeated here.

[0073] In a sixth aspect, a communication method is provided, which can be executed by a core network network element, or by a component of the core network network element, such as a processor, chip, or chip system of the core network element, or by a logic module or software that can realize all or part of the core network network element functions. And the core network network element can be an AMF or TMF (AIoTMF). The following is an example of the method being executed by a core network network element. The method includes: the core network network element receives a third identifier and first information from an access network device, the third identifier is used to indicate the first terminal device at the third signaling layer, and the first information is used to indicate the first terminal device at the first signaling layer; the core network network element determines the operation of the first terminal device based on the first information, and sends a second operation request message to the access network device, the second operation request message includes a third identifier and an operation instruction.

[0074] In one possible design scheme, the second operation request message also includes second indication information, and the second indication information is used to instruct the access network device to delete the context of the first terminal device after completing the operation on the first terminal device.

[0075] In a possible design scheme, the method described in the sixth aspect also includes: the core network element stores the correspondence between the identifier of the reader / writer and the third identifier, and the reader / writer is used to serve the first terminal device.

[0076] In one possible design scheme, before the core network network element receives the third identifier and first information from the access network device, the method described in the sixth aspect also includes: the core network network element sends a second operation task request message to the access network device, and the second operation task request message includes a task identifier; after determining that the operation task indicated by the task identifier is completed, the core network network element sends the task identifier and fourth indication information to the access network device, and the fourth indication information is used to instruct the access network device to delete the context containing the task identifier.

[0077] In one possible design, the core network element is any one of the following: access and mobility management function, or passive IoT device management function.

[0078] In one possible design, the third signaling layer is the Next Generation Application Protocol (NGAP) layer.

[0079] In one possible design scheme, the first signaling layer is a non-access NAS layer.

[0080] In addition, the technical effects of the method described in the sixth aspect can also refer to the technical effects of the method described in the fifth aspect, and will not be repeated here.

[0081] In the seventh aspect, a communication method is provided, which includes: the access network device executes the method described in the first aspect, and the core network device executes the method described in the second aspect; or, the access network device executes the method described in the first aspect, the core network device executes the method described in the second aspect, and the first terminal device executes the method described in the third aspect.

[0082] In addition, the technical effects of the method described in aspect 7 can also refer to the technical effects of the methods described in aspects 1 to 2, or the technical effects of the methods described in aspects 1 to 3, and will not be repeated here.

[0083] In the eighth aspect, a communication method is provided, which includes: the access network device executes the method described in the fifth aspect, and the core network network element executes the method described in the sixth aspect; or, the reader / writer executes the method described in the fourth aspect, the access network device executes the method described in the fifth aspect, and the core network network element executes the method described in the sixth aspect.

[0084] In addition, the technical effects of the method described in aspect 8 can also refer to the technical effects of the methods described in aspects 5 to 6, or the technical effects of the methods described in aspects 4 to 6, and will not be repeated here.

[0085] In a ninth aspect, a communication device is provided. The communication device includes: a module for executing the method described in any one of aspects 1 to 6, such as a transceiver module and a processing module. For example, the transceiver module is configured to indicate the transceiver function of the communication device, and the processing module is configured to perform functions of the communication device other than the transceiver function.

[0086] Optionally, the transceiver module may include a sending module and a receiving module, wherein the sending module is used to implement the sending function of the communication device described in the ninth aspect, and the receiving module is used to implement the receiving function of the communication device described in the ninth aspect.

[0087] Optionally, the communication device described in the ninth aspect may further include a storage module, wherein the storage module stores a program or instruction. When the processing module executes the program or instruction, the communication device may execute the method described in any one of the first to sixth aspects.

[0088] It can be understood that the communication device described in the ninth aspect can be a terminal device or a network device, or it can be a chip (system) or other parts or components that can be set in the terminal device or the network device, or it can be a device that includes the terminal device or the network device. This application does not limit this.

[0089] In addition, the technical effects of the communication device described in the ninth aspect can refer to the technical effects of the method described in any one of the implementation methods of the first to sixth aspects, and will not be repeated here.

[0090] In a tenth aspect, a communication device is provided, comprising: a processor, wherein when the processor executes computer instructions, the communication device executes the method described in any possible implementation manner of the first to sixth aspects.

[0091] In one possible design solution, the communication device described in the tenth aspect may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver may be used for the communication device described in the tenth aspect to communicate with other communication devices.

[0092] In one possible design, the communication device described in aspect 10 may further include a memory. The memory may be integrated with the processor or provided separately. The memory may be used to store the computer program and / or data involved in the method described in any one of aspects 1 to 6.

[0093] In an embodiment of the present application, the communication device described in the tenth aspect can be the terminal device or network device described in any one of the first to sixth aspects, or a chip (system) or other parts or components that can be set in the terminal device or the network device, or a device that includes the terminal device or the network device.

[0094] In addition, the technical effects of the communication device described in the tenth aspect can refer to the technical effects of the method described in any one of the implementation methods of the first aspect to the sixth aspect, and will not be repeated here.

[0095] In an eleventh aspect, a communication device is provided. The communication device includes: a processor coupled to a memory, the processor being configured to execute a computer program stored in the memory, so that the communication device performs the method described in any possible implementation of the first to sixth aspects.

[0096] In one possible design solution, the communication device described in the eleventh aspect may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver may be used for the communication device described in the eleventh aspect to communicate with other communication devices.

[0097] In an embodiment of the present application, the communication device described in the eleventh aspect can be the terminal device or network device described in any one of the first to sixth aspects, or a chip (system) or other parts or components that can be set in the terminal device or the network device, or a device that includes the terminal device or the network device.

[0098] In addition, the technical effects of the communication device described in the eleventh aspect can refer to the technical effects of the method described in any one of the implementation methods of the first aspect to the sixth aspect, and will not be repeated here.

[0099] In the twelfth aspect, a communication device is provided, comprising: a processor and a memory; the memory is used to store a computer program, and when the processor executes the computer program, the communication device executes the method described in any one of the implementation methods of the first to sixth aspects.

[0100] In one possible design solution, the communication device described in aspect 12 may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver may be used for the communication device described in aspect 12 to communicate with other communication devices.

[0101] In an embodiment of the present application, the communication device described in aspect 12 may be the terminal device or network device described in any one of aspects 1 to 6, or a chip (system) or other parts or components that can be set in the terminal device or the network device, or a device that includes the terminal device or the network device.

[0102] In addition, the technical effects of the communication device described in the twelfth aspect can refer to the technical effects of the method described in any one of the implementation methods of the first to sixth aspects, and will not be repeated here.

[0103] In a thirteenth aspect, a communication device is provided for implementing the method described in any possible implementation method of the first to sixth aspects.

[0104] In the fourteenth aspect, a communication chip is provided, comprising: a logic circuit and a communication interface, wherein the logic circuit is used to execute computer instructions, and the communication interface is used for the communication chip to communicate with other devices or chips, and when the logic circuit executes the computer instructions, the method described in any one of the implementation methods of the first to sixth aspects is implemented.

[0105] In a fifteenth aspect, a communication system is provided, which includes at least one of the following: an access network device for executing the method described in the first aspect, a core network device for executing the method described in the second aspect, or a first terminal device for executing the method described in the third aspect.

[0106] In the sixteenth aspect, a communication system is provided, which includes at least one of the following: a reader / writer for executing the method described in the fourth aspect, an access network device for executing the method described in the fifth aspect, or a core network element for executing the method described in the sixth aspect.

[0107] In the seventeenth aspect, a computer-readable storage medium is provided, comprising: a computer program or instructions; when the computer program or instructions are run on a computer, the computer executes the method described in any possible implementation method of the first to sixth aspects.

[0108] In the eighteenth aspect, a computer program product is provided, comprising a computer program or instructions, which, when executed on a computer, enables the computer to execute the method described in any one of the possible implementations of aspects one to six. BRIEF DESCRIPTION OF THE DRAWINGS

[0109] FIG1 is a schematic diagram of the architecture of a fifth-generation mobile communication system 5GS provided in an embodiment of the present application;

[0110] FIG2 is a schematic diagram of an ambient energy acquisition Internet of Things (A-IoT) service flow according to an embodiment of the present application;

[0111] FIG3 is a flow chart of an A-IoT device operation process according to an embodiment of the present application;

[0112] FIG4 is a schematic diagram of the architecture of a communication system according to an embodiment of the present application;

[0113] FIG5 is a flow chart of a communication method according to an embodiment of the present application;

[0114] FIG6 is a schematic diagram of random access by multiple processes according to an embodiment of the present application;

[0115] FIG7 is a second flow chart of the communication method provided in an embodiment of the present application;

[0116] FIG8 is a third flow chart of the communication method provided in an embodiment of the present application;

[0117] FIG9 is a fourth flow chart of a communication method according to an embodiment of the present application;

[0118] FIG10 is a second schematic diagram of the architecture of the communication system provided in an embodiment of the present application;

[0119] FIG11 is a schematic diagram of a protocol stack provided in an embodiment of the present application;

[0120] FIG12 is a fifth flow chart of a communication method according to an embodiment of the present application;

[0121] FIG13 is a sixth flow chart of a communication method according to an embodiment of the present application;

[0122] FIG14 is a seventh flow chart of a communication method according to an embodiment of the present application;

[0123] FIG15 is a flow chart eight of a communication method according to an embodiment of the present application;

[0124] FIG16 is a ninth flowchart of a communication method according to an embodiment of the present application;

[0125] FIG17 is a first structural diagram of a communication device provided in an embodiment of the present application;

[0126] FIG18 is a second structural diagram of the communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0127] For ease of understanding, the technical terms involved in the embodiments of this application are first introduced below.

[0128] 1. Fifth-generation (5G) mobile communication system (abbreviated as 5G system (5G system, 5GS))

[0129] Figure 1 is a schematic diagram of the 5GS architecture. As shown in Figure 1, 5GS includes: an access network (AN) and a core network (CN), and may also include: terminal equipment.

[0130] The terminal device may be a terminal device with transceiver functions, or a chip or chip system that can be provided in the terminal device. The terminal device may also be referred to as user equipment (UE), terminal, access terminal, subscriber unit (subscriber unit), user station, mobile station (MS), mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication device, device, user agent or user equipment. The terminal device in the embodiments of the present application can be a cellular phone, a wireless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5G network or a terminal device in a future-evolved public land mobile network (PLMN) or a non-terrestrial network (NTN), etc.; it can also be an end device, a logical entity, an intelligent device, such as a mobile phone, an intelligent terminal and other terminal devices, or a server, a gateway, a base station, a controller and other communication devices, or an Internet of Things (IoT) device, such as a passive Internet of Things (IoT) device, a passive-passive Internet of Things (IoT) device, an active-passive Internet of Things (IP) device, a semi-active-passive Internet of Things (IP) device, a sensor, an electricity meter, a water meter and other IoT devices; it can also be an unmanned aerial vehicle (UAV) with communication function; it can also be an ambient Internet of Things (AIoT) device. When the terminal is a passive IoT device, it can receive or send data by obtaining energy. The way of obtaining energy may include radio, solar energy, light energy, wind energy, water energy, thermal energy, kinetic energy, etc. This application does not limit the way in which passive or semi-active terminals obtain energy. It should be understood that the passive IoT devices involved in this application can be in the form of passive IoT devices or in any terminal form.

[0131] The AN is used to implement access-related functions, providing network access for authorized users in a specific area and determining transmission links of varying quality for user data transmission based on user level and service requirements. The AN forwards control signals and user data between the terminal and the CN. The AN may include access network equipment, also known as radio access network (RAN) equipment. The CN is primarily responsible for maintaining mobile network subscription data and providing terminal devices with functions such as session management, mobility management, policy management, and security authentication. The CN primarily includes the following: user plane function (UPF), authentication server function (AUSF), access and mobility management function (AMF), session management function (SMF), network slice selection function (NSSF), network exposure function (NEF), network repository function (NRF), policy control function (PCF), unified data management (UDM), unified data repository (UDR), application function (AF), and TMF.

[0132] As shown in Figure 1, the UE accesses the 5G network through the RAN equipment. The UE communicates with the AMF through the N1 interface (referred to as N1); the RAN communicates with the AMF through the N2 interface (referred to as N2); the RAN communicates with the UPF through the N3 interface (referred to as N3); the SMF communicates with the UPF through the N4 interface (referred to as N4), and the UPF accesses the data network (DN) through the N6 interface (referred to as N6). In addition, the control plane functions shown in Figure 1, such as AUSF, AMF, SMF, NSSF, NEF, NRF, PCF, UDM, UDR, AF, NWDAF, and ADRF, interact using service-based interfaces. For example, the service-oriented interface provided by AUSF to the outside world includes Nausf; the service-oriented interface provided by AMF to the outside world includes Namf; the service-oriented interface provided by SMF to the outside world includes Nsmf; the service-oriented interface provided by NSSF to the outside world includes Nnssf; the service-oriented interface provided by NEF to the outside world includes Nnef; the service-oriented interface provided by NRF to the outside world includes Nnrf; the service-oriented interface provided by PCF to the outside world includes Npcf; the service-oriented interface provided by UDM to the outside world includes Nudm; the service-oriented interface provided by UDR to the outside world includes Nudr; the service-oriented interface provided by AF to the outside world includes Naf; and the service-oriented interface provided by TMF to the outside world includes Ntmf.

[0133] RAN equipment can be equipment that provides access to terminal equipment. For example, the RAN equipment may include: a next-generation mobile communication system, such as an access network device of 6G, such as a 6G base station, or in the next-generation mobile communication system, the network equipment may also have other naming methods, which are all included in the protection scope of the embodiments of this application, and this application does not impose any restrictions on this. Alternatively, the RAN equipment may also include 5G, such as a gNB in ​​a new radio (NR) system, or one or a group of (including multiple antenna panels) antenna panels of a base station in 5G, or a network node constituting a gNB, a transmission point (TRP or transmission point, TP) or a transmission measurement function (TMF), such as a baseband unit (building base band unit, BBU), or a centralized unit (CU) or a distributed unit (DU), an RSU with base station function, or a wired access gateway, or a 5G core network. Alternatively, RAN devices may also include access points (APs) in wireless fidelity (WiFi) systems, wireless relay nodes, wireless backhaul nodes, various forms of macro base stations, micro base stations (also known as small stations), relay stations, access points, wearable devices, vehicle-mounted devices, and the like.

[0134] UPF is mainly responsible for user data processing (forwarding, receiving, billing, etc.).

[0135] AUSF is mainly used to perform security authentication of terminal devices.

[0136] AMF is mainly used for mobility management in mobile networks, such as user location update, user network registration, user switching, etc.

[0137] The SMF is primarily used for session management in mobile networks, such as session establishment, modification, and release. Specific functions include allocating Internet Protocol (IP) addresses to users and selecting the UPF that provides packet forwarding capabilities.

[0138] PCF primarily supports providing a unified policy framework to control network behavior, providing policy rules to the control layer network functions, and is responsible for obtaining user subscription information related to policy decisions. PCF can provide policies to AMF and SMF, such as quality of service (QoS) policies and slice selection policies.

[0139] NSSF is mainly used to select network slices for terminal devices.

[0140] NEF is mainly used to support the opening of capabilities and events. For example, NEF can open some capabilities of the 5G network to third-party applications through the application program interface (API). Third-party applications can obtain some capabilities of the 5G network by calling the API provided by NEF through AF, allowing third-party applications to control certain behaviors of the 5G network and terminal devices.

[0141] UDM is mainly used to store user data, such as contract data, authentication / authorization data, etc.

[0142] UDR is mainly used to store structured data, including contract data and policy data, externally exposed structured data, and application-related data.

[0143] AF mainly supports interaction with CN to provide services, such as influencing data routing decisions, policy control functions, or providing some third-party services to the network side.

[0144] The TMF is primarily used to transmit and / or manage terminal device service data. For example, if the terminal device is an A-IoT device, the TMF can transmit and / or manage the service data of the A-IoT device. It is understood that the TMF may also be referred to as the Ambient Internet of Things Management Function (AIoTMF), or other names without limitation.

[0145] 2.A-IoT

[0146] A-IoT can also be referred to as Passive IoT (P-IoT) or other names. In A-IoT, some network nodes can be passive, semi-passive, or active. Alternatively, some network nodes can be DT, DO-DTT, or DO-A. It is understood that passive network nodes can obtain energy through solar energy, radio frequency, wind energy, hydropower, or tidal energy, and there is no restriction on the method of energy acquisition. These nodes do not have their own power supply devices or do not rely on batteries. Instead, they obtain energy from the environment to support data perception, transmission, and distributed computing. These nodes can also store the energy they obtain.

[0147] A-IoT may include IoT terminals, readers, IoT functions, and service requesters.

[0148] IoT terminals can also be called passive terminals. They can be in the form of passive IoT devices, tags, sensors, or any other terminal form factors, without limitation.

[0149] A reader can be an access network device, such as a base station, pole station, micro base station, macro station, relay point (such as an integrated access and backhaul node), or mobile base station. It can also be a terminal device, such as a mobile phone, IoT device, or handheld reader. For details, please refer to the aforementioned "1.5GS" and will not be repeated here. A reader, also known as a reader, can conduct contactless, two-way data communication via radio frequency (RF) and read and write to passive electronic IoT devices or RF tags using RF to achieve target identification and data exchange. For details, please refer to existing technologies and will not be repeated here. A reader operates in two ways. One is that when a tag enters the reader's effective recognition range, it receives the RF signal emitted by the reader and uses the energy generated by the induced current to transmit the information stored in the chip (this corresponds to a passive tag). The other is that the tag can store some electrical energy through methods such as solar energy, allowing it to actively transmit a signal of a certain frequency (this type of tag is also called a semi-passive or semi-active tag). The reader receives and decodes the information and sends it to the central information system for relevant data processing.

[0150] The IoT function, which may also be referred to as a passive IoT management function, an ambient energy harvesting IoT function, or other names, can be used to manage IoT terminals or transmit service data. The IoT function can be at least one network element in the core network, such as the aforementioned AMF or TMF. It is understood that the AMF and TMF can be co-deployed; when they are co-deployed, the TMF can be a function within the AMF.

[0151] The service requester can also be called the service operator or a third party, which can be a server (such as AF, application server (AS), or passive IoT application function (P-IoT AF or A-IoT AF)), application function, or other device capable of sending operation instructions. In addition, the operation requester can correspond to a certain type of user, which can include enterprises, tenants, third parties, or companies, without restriction. The operation requester corresponding to a certain type of user can be understood as belonging to that type of user, that is, managed by that type of user.

[0152] When the service requester operates the IoT terminal, an operation instruction can be sent through the IoT function. The operation instruction may include an operation to obtain IoT terminal information, an inventory operation (or an inventory operation), a read operation, a write operation, a failure operation (disable or kill), an operation of interactive information of a passive IoT device, an instruction (command) operation, etc. The operation instruction may also include information such as the regional location and the identifier of the IoT terminal to indicate the IoT terminal device that needs to perform the operation indicated by the operation instruction. For example, the service requester can send an operation instruction to the IoT function, and after receiving the instruction, the IoT function triggers the reader to perform random access of the IoT terminal; after the random access of the IoT terminal is completed, that is, after the IoT terminal is connected to the reader, the IoT function can send an operation instruction to the IoT terminal through the reader to complete the operation of the IoT device.

[0153] For example, as shown in Figure 2, when the AF (the above-mentioned service requester) operates the tag (the above-mentioned IoT terminal), an operation instruction can be sent to the AMF (the above-mentioned IoT function) through the NEF. After receiving the operation instruction, the AMF can send the operation instruction to the base station (the above-mentioned reader). After receiving the operation instruction, the base station can trigger random access of the tag according to the operation instruction. After the random access of the tag is completed, the AMF can send an operation instruction to the tag through the base station so that the tag completes the operation indicated by the operation instruction. It can be understood that the AMF can also be replaced by the TMF, which can be set according to the actual situation without limitation.

[0154] 3. Initial context establishment process

[0155] After the UE establishes an RRC connection with the RAN and the UE registers with the RAN, the RAN can generate the UE's RAN UE Next Generation Application Protocol (NGAP) ID when sending an uplink message (such as a NAS message or other message) to the AMF. The AMF can subsequently generate the UE's AMF UE NGAP ID and send it to the RAN via an Initial Context Request. After receiving the AMF UE NGAP ID, the RAN sends the RAN UE NGAP ID to the AMF. The RAN and AMF can maintain the correspondence between the RAN UE NGAP ID and the AMF UE NGAP ID.

[0156] When the AMF sends an NGAP message to the RAN, it can carry the AMF UE NGAP ID. The RAN can determine, based on the above correspondence, which UE the NGAP message is sent to. Correspondingly, when the RAN sends an NGAP message to the AMF, it can carry the RAN UE NGAP ID. The AMF can determine, based on the above correspondence, which UE the NGAP message is sent to.

[0157] It can be understood that the initial context establishment message can carry multiple information elements (IEs), such as message type, AMF UE NGAP ID, RAN UE NGAP ID, PDU session ID, etc.

[0158] 4.A-IoT device operation process

[0159] As shown in Figure 3, when operating multiple devices, after the reader / writer (RAN in Figure 3) completes random access to one device, it needs to trigger random access to the next device according to the instruction of the IoT function (TMF in Figure 3 as an example). In this case, the reader / writer and the IoT function can send operation instructions to the IoT terminal that has completed random access according to the interaction time sequence. For example, after IoT terminal #1 randomly accesses the reader / writer, the IoT function sends an operation instruction to IoT terminal #1 through the reader / writer; after IoT terminal #1 completes the operation indicated by the operation instruction, the IoT function instructs the reader / writer to start random access to the next IoT terminal, and after the random access of the next IoT terminal is completed, it operates on the IoT terminal to complete all operations. The following is a detailed introduction to the A-IoT operation tag process one.

[0160] S301: The AF sends an ambient energy acquisition IoT service request (Nnef_AmbientIoT_service request) to the NEF. Correspondingly, the NEF receives the ambient energy acquisition IoT service request from the AF.

[0161] An ambient energy acquisition IoT service request may include at least one of the following: a service requester identifier, an operation type, a device identifier to be operated (e.g., a device list), or a geographic range to be operated. The service requester identifier may be used to indicate the service requester and may be an AF identity (ID), an AF Internet Protocol (IP) address, or an AF port number. The operation type may be a read operation, a write operation, an invalidation operation, etc., and may be set based on actual circumstances without limitation. The device identifier may include the identifier of the device to be operated, such as the identifier of device 1 and the identifier of device 2. The geographic range to be operated may include the geographic range where the device to be operated is located and may be represented by identifiers such as a TA identifier, a Cell identifier, longitude and latitude, coordinate values, or a CAG identifier. It is understood that the device to be operated may be indicated by the device identifier to be operated or the geographic range to be operated, and the device to be operated may be set based on actual circumstances without limitation. In addition, when the ambient energy acquisition IoT service request includes a read operation and a device list, it may indicate a read operation on each device in the device list, i.e., a read operation on device 1 and device 2 in the device list. S302, NEF performs TMF selection operation.

[0162] S302, NEF performs TMF selection operation.

[0163] The NEF selects the required TMF based on the ambient energy acquisition IoT service request. It is understood that this TMF can operate on both Device 1 and Device 2. In other words, the NEF can determine the TMF based on the device to be operated, such as Device 1 and Device 2.

[0164] S303: NEF sends an environmental energy acquisition IoT service request to TMF. Correspondingly, TMF receives the environmental energy acquisition IoT service request from NEF.

[0165] For the environmental energy acquisition IoT service request, please refer to the relevant introduction in the aforementioned "S301" and will not be repeated here.

[0166] It can be understood that AF can provide the environmental energy acquisition IoT service request to TMF through NEF, or provide the environmental energy acquisition IoT service request to TMF through subscription. The specific equipment can be determined according to actual conditions without any restrictions.

[0167] Furthermore, upon receiving an ambient energy acquisition IoT service request, the TMF can authenticate the corresponding operation to confirm that the service requester can access the corresponding core network service. For example, the TMF can query the contract data in the UDM / UDR to confirm whether a corresponding core network service exists for the operation. After authentication is complete, the TMF can request the reader to trigger a random access process for the devices in the device list.

[0168] S304, TMF performs a reader / writer selection operation.

[0169] The TMF obtains IoT service requests based on ambient energy and determines the RAN (i.e., reader / writer) to be used. It is understood that this RAN can access both Device 1 and Device 2. In other words, the TMF can randomly determine the RAN that can access the device to be operated, such as determining the TMF based on Device 1 and Device 2.

[0170] S305: TMF sends N2 message (Msg) #1 to RAN. Correspondingly, RAN receives N2 message #1 from TMF.

[0171] N2 message #1 can be used to trigger RAN to perform a random access process for the device that needs to be operated. N2 message #1 may include at least one of the following: random access indication mode 2, a mask corresponding to the identifier of the device that needs to be operated, or a random access indication. Among them, random access indication mode 2 can be used to indicate that the reader (i.e., RAN) needs to broadcast a repeated query (QueryRep) message according to the instruction of the Internet of Things function (i.e., TMF) when performing random access on multiple devices. The mask corresponding to the identifier of the device that needs to be operated can be the mask corresponding to the identifier of device 1 and the identifier of device 2. The mask can be generated by TMF or by AF. When the mask is generated by AF, AF can send the generated mask to TMF. The random access indication can trigger the random access process of the reader. The random access indication can reuse the existing paging (Paging) message or use a new indication information element without restriction.

[0172] S306, RAN broadcasts a Select command.

[0173] The selection command carries a device range, such as a mask, including a specific range of electronic product codes (EPCs) and public land mobile network (PLMN) IDs. The device range includes the devices to be operated, namely, device 1 and device 2. It is understood that the device range can be a mask corresponding to the identifiers of the devices to be operated.

[0174] After receiving the Select command, the device determines whether it belongs to the device range specified in the Select command. If the device belongs to the device range, the device will respond with information indicating this after the RAN broadcasts the Query command, i.e., send a random access request. If the device does not belong to the device range, the device will not perform any operation after the RAN broadcasts the Query command.

[0175] S307, RAN broadcasts a query command.

[0176] The query command can be understood as a random access request or random access instruction sent by the RAN to each device that needs random access, so that the device that receives the query command feeds back information to the RAN for random access. It can be understood that this device falls within the scope of the above-mentioned devices.

[0177] After broadcasting the selection command, the RAN may continue to broadcast the query command.

[0178] S308 , device 2 sends a random number (RN) 16 - 1 to the RAN. Correspondingly, the RAN receives the RN 16 - 1 from device 2 .

[0179] When device 2 determines that it belongs to the device range in the selection command, it can feedback an RN 16-1 to the RAN through a competitive manner. This RN 16-1 can be used by the RAN to identify device 2. The RN 16-1 can be generated by device 2 or configured by the network side, without limitation.

[0180] S309: RAN sends a confirmation message #1 to device 2 according to RN16-1 sent by device 2. Correspondingly, device 2 receives the confirmation message #1 from RAN.

[0181] Confirmation message #1 may also be referred to as an ACK command, and may include RN16-1 sent by device 2. Thus, after receiving confirmation message #1, device 2 may determine, based on RN16-1 in confirmation message #1, that confirmation message #1 is intended for it, thereby determining that the RAN has received the random access request sent by it.

[0182] S310 , device 2 sends a radio resource control (RRC) message #1 to the RAN based on the confirmation message #1. Correspondingly, the RAN receives the RRC message #1 from device 2.

[0183] RRC message #1 includes the identifier of device 2. The identifier of device 2 may be an EPC or other information capable of identifying device 2, without limitation. It is understood that the RAN cannot determine the identifier of device 2, i.e., it cannot decode the information containing the identifier of device 2 (e.g., the non-access stratum (NAS) information in RRC message #1) to obtain the identifier of device 2.

[0184] It is understood that S306-S310 are the random access process between device 2 and RAN, which is only an example of an implementation method. Device 2 and RAN can also perform random access in other ways without limitation.

[0185] S311: RAN sends N2 message #2 to TMF according to RRC message #1. Correspondingly, TMF receives N2 message #2 from RAN.

[0186] The N2 message #2 may be used to indicate that the device 2 has randomly accessed the RAN, that is, the device 2 is already in the network. The N2 message #2 may include an identifier of the device 2.

[0187] It can be understood that the RAN forwards the information containing the identifier of device 2 in RRC message #1 to the TMF. That is, the RAN cannot determine the identifier of device 2. The TMF can decode the information containing the identifier of device 2 to obtain the identifier of device 2. In addition, after receiving N2 message #2, the TMF can determine that device 2 has randomly accessed the RAN and thus perform operations on device 2.

[0188] S312, TMF sends service request #1 to device 2. Correspondingly, device 2 receives service request #1 from TMF.

[0189] The service request may include a read operation and an identifier of the device 2 , that is, the service request is used to instruct the device 2 to perform a read operation.

[0190] S313: After completing the operation corresponding to service request #1, device 2 sends service response #1 to TMF. Correspondingly, TMF receives service response #1 from device 2.

[0191] The service response #1 includes the data (referred to as data #1) stored in the storage area of ​​the device 2. It can be understood that when the operation performed by the device 2 is different, the service response is also different.

[0192] S314: TMF sends N2 message #3 to RAN. Correspondingly, RAN receives N2 message #3 from TMF.

[0193] N2 message #3 is used to instruct the RAN to continue random access, that is, to instruct the RAN to trigger random access of the next device, that is, to instruct the RAN to send a repeated query message.

[0194] S315, RAN broadcasts a repeat query message.

[0195] The repeated query message can be understood as a random access request or random access instruction broadcast by the RAN, so that the device requiring random access, after receiving the repeated query message, feeds back information to the RAN to perform random access. It is understood that in this case, the device requiring random access does not include a device that has already completed random access, such as the aforementioned device 2.

[0196] S316 , device 1 sends RN 16 - 2 to RAN. Correspondingly, RAN receives RN 16 - 2 from device 1 .

[0197] When device 1 determines that it belongs to the device range in the selection command, it will feedback an RN 16-2 to the RAN through competition. It is understood that the RN 16-2 can be generated by device 1 or configured by the network side without limitation.

[0198] S317, RAN sends a confirmation message #2 to device 1 according to RN16-2 sent by device 1. Correspondingly, device 1 receives the confirmation message #2 from RAN.

[0199] Confirmation message #2 is similar to confirmation message #1 described above, and may include RN16-2 sent by device 1. Thus, after receiving confirmation message #2, device 1 may determine, based on RN16-2 in confirmation message #2, that confirmation message #2 is intended for it, thereby confirming that the RAN has received the random access request sent by it.

[0200] S318 : Device 1 sends RRC message # 2 to RAN based on confirmation message # 2 . Correspondingly, RAN receives RRC message # 2 from device 1 .

[0201] RRC message #2 is similar to RRC message #1 described above and may include the identifier of device 1. The identifier of device 1 may be an EPC or other information capable of identifying device 1, without limitation. It is understood that the RAN cannot determine the identifier of device 1, i.e., it cannot decode the information containing the identifier of device 1 (e.g., the NAS information in RRC message #2) to obtain the identifier of device 1.

[0202] S319: RAN sends N2 message #4 to TMF according to RRC message #2. Correspondingly, TMF receives N2 message #4 from RAN.

[0203] N2 message #4 may be used to indicate that device 1 has randomly accessed the RAN, that is, device 1 is already in the network. The N2 message #4 may include an identifier of device 1.

[0204] It can be understood that the RAN forwards the information containing the identifier of device 1 in RRC message #2 to the TMF. That is, the RAN cannot determine the identifier of device 1. The TMF can decode the information containing the identifier of device 1 to obtain the identifier of device 1. In addition, after receiving N2 message #4, the TMF can determine that device 1 has randomly accessed the RAN and thus perform operations on device 1.

[0205] S320, TMF sends service request #2 to device 1. Correspondingly, device 1 receives service request #2 from TMF.

[0206] The service request may include a read operation and an identifier of the device 1 , that is, the service request is used to instruct the device 1 to perform a read operation.

[0207] S321: After completing the operation corresponding to service request #2, device 1 sends service response #2 to TMF. Correspondingly, TMF receives service response #2 from device 1.

[0208] The service response #2 includes the data (referred to as data #2) stored in the storage area of ​​the device 1. It can be understood that when the operation performed by the instructing device 2 is different, the service response is also different.

[0209] S322: After receiving the service response #1, the TMF sends an ambient energy acquisition IoT response (Nnef_AmbientIoT_service response) #1 to the NEF. Accordingly, the NEF receives the ambient energy acquisition IoT response #1 from the TMF.

[0210] The ambient energy acquisition IoT response #1 is used to indicate the result of the read operation performed by device 2, which may include the identifier of AF, the identifier of device 2 and data #1.

[0211] It is understandable that S322 can be executed after S313 or S314, and S322 can be performed simultaneously with RAN operations (such as S315-S318). The specific settings can be flexibly made according to actual conditions without limitation.

[0212] S323: After receiving the environmental energy acquisition IoT response #1 from the TMF, the NEF sends the environmental energy acquisition IoT response #1 to the AF. Correspondingly, the AF receives the environmental energy acquisition IoT response #1 from the NEF.

[0213] S324: After receiving the service response #2, the TMF sends an environmental energy acquisition IoT response #2 to the NEF. Correspondingly, the NEF receives the environmental energy acquisition IoT response #2 from the TMF.

[0214] The ambient energy acquisition IoT response #2 is used to indicate the result of the read operation performed by device 1, which may include the identifier of AF, the identifier of device 1 and data #2.

[0215] S325, after receiving the environmental energy acquisition IoT response #2 from the TMF, the NEF sends the environmental energy acquisition IoT response #2 to the AF. Correspondingly, the AF receives the environmental energy acquisition IoT response #2 from the NEF.

[0216] It can be understood that when the number of devices to be operated is greater than 2, the operations of other devices can refer to the operations of the above-mentioned device 1, and will not be repeated here.

[0217] As can be seen in the process shown in Figure 3, the RAN requires an indication from the TMF (i.e., S314) before triggering the next device's random access, i.e., sending a repeated query message (i.e., S315). Furthermore, the RAN triggers the next device's random access only after completing an operation on one device, and then operates the next device after the next device completes its random access.

[0218] However, this approach is inefficient, as random access and operations on multiple terminal devices are performed serially. Only after the operation on one terminal device is completed can the next terminal device be randomly accessed and operated. Therefore, improving the efficiency of performing operations on multiple terminal devices is a hot topic of discussion.

[0219] In response to the above technical problems, the embodiments of the present application propose the following technical solutions to improve the efficiency of executing operations on multiple terminal devices.

[0220] The technical solution in this application will be described below with reference to the accompanying drawings.

[0221] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as 4th generation (4G) mobile communication systems, such as long term evolution (LTE) systems, fifth generation (5G) mobile communication systems, such as new radio (NR) systems, and communication systems evolved after 5G, such as sixth generation (6G) mobile communication systems. They can also be applied to wireless fidelity (WiFi) systems, vehicle to everything (V2X) communication systems, device-to-device (D2D) communication systems, and Internet of Vehicles communication systems.

[0222] This application will present various aspects, embodiments, or features in the context of systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that each system may include additional devices, components, modules, etc., and / or may not include all of the devices, components, modules, etc. discussed in conjunction with the figures. Furthermore, combinations of these aspects may also be used.

[0223] Additionally, in the embodiments of this application, words such as "exemplary" and "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of the word "exemplary" is intended to present concepts in a concrete manner.

[0224] In the embodiments of the present application, "information", "signal", "message", "channel" and "signaling" can sometimes be used interchangeably. It should be noted that when the distinction between them is not emphasized, the meanings they intend to express are matched. "of", "corresponding, relevant" and "corresponding" can sometimes be used interchangeably. It should be noted that when the distinction between them is not emphasized, the meanings they intend to express are matched. In addition, the " / " mentioned in this application can be used to express an "or" relationship.

[0225] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field will know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0226] To facilitate understanding of the embodiments of the present application, a communication system applicable to the embodiments of the present application is first described in detail using the communication system shown in Figure 4 as an example. For example, Figure 4 is a schematic diagram of the architecture of a communication system applicable to the communication method provided in the embodiments of the present application.

[0227] As shown in FIG4 , the communication system can be applied to the above-mentioned 5GS, including: access network equipment, core network equipment and terminal equipment.

[0228] The access network device can be a device with access functionality, such as a reader / writer. For details, please refer to the relevant description in the aforementioned "2.A-IoT" and will not be repeated here. It is understood that when the terminal device functions as a reader / writer, the terminal device can be considered an access network device, that is, the terminal device can be used to access other terminal devices and connect to the core network device. Of course, the access network device can also be other devices without limitation. It is understood that when the access network device is a reader / writer, the reader / writer can be performed by the terminal device or by other devices (such as the access network device). The specific configuration can be based on actual circumstances and is not limited. The core network device can be used to manage the first terminal device and can be the aforementioned IoT function, such as AMF or TMF. For details, please refer to the relevant description in the aforementioned "2.A-IoT" and will not be repeated here. The terminal device can include at least one terminal device, and the device form of the terminal device can refer to the relevant description in the aforementioned "1.5GS" and will not be repeated here.

[0229] It is understood that when the core network device is TMF (AIoTMF), a protocol layer, such as N2 tag management information or AIoT NGAP, can be set between the access network device and TMF to enable interaction between the access network device and TMF. The embodiment of the present application does not limit the name of the protocol layer between the access network device and TMF.

[0230] In a communication system, an access network device can determine an identifier that can be used in the first signaling layer for a terminal device that needs to be operated, and send the identifier to a core network device, so that the access network device and the core network device can indicate the terminal device in the first signaling layer through the identifier, thereby realizing the operation of the terminal device. For example, the access network device can determine a first identifier that can be used in the first signaling layer for the terminal device, and send the first identifier and the identifier of the terminal device to the core network device; after the core network device determines the operation of the terminal device based on the identifier of the terminal device, it sends an operation request message to the access network device; the access network device can determine the second identifier based on the first identifier included in the operation request message, and send the second identifier and the operation instruction in the operation request message to the terminal device, so that the terminal device can determine that the operation instruction is the instruction sent to it based on the second identifier, and execute the operation instruction. In this way, when it is necessary to operate multiple terminal devices, the access network device can trigger random access of each of the multiple terminal devices by itself, that is, it does not need to rely on the instruction of the core network device to trigger random access of the terminal device. In this case, the core network equipment can operate the terminal devices that have completed random access during the process of random access of the terminal devices. That is, there is no need to wait until the random access and operation of one terminal device are completed before performing random access and operation on the next terminal device, thereby improving the efficiency of operations on multiple terminal devices.

[0231] It can be understood that FIG4 is a simplified schematic diagram for ease of understanding, and the communication system may also include other network devices and / or other terminal devices, which are not shown in FIG4 .

[0232] For ease of understanding, the communication method provided in the embodiment of the present application will be described in detail below with reference to FIG5 .

[0233] For example, Figure 5 is a flow chart of a communication method provided in an embodiment of the present application. This method can be applied to the interaction between terminal devices, access network devices, and core network devices in the above-mentioned communication system. For ease of understanding, the communication method is described below using a first terminal device as an example.

[0234] As shown in Figure 5, the process of the communication method is as follows:

[0235] S501: After receiving a first random access request from a first terminal device, the access network device determines a first identifier of the first terminal device.

[0236] The first random access request can be used to request random access to an access network device. The first random access request may be different in different random access procedures. Exemplarily, the first random access request may be a message sent by the first terminal device to the access network device in accordance with the second random access request after the access network device broadcasts the second random access request, requesting access to the access network device. The second random access request may be used to instruct the terminal device that needs to randomly access the access network device to send a message to the access network device requesting access to the access network device. The second random access request may be a paging message or a query command as described in the aforementioned "4. A-IoT Operation Device Process". For details, please refer to the aforementioned relevant introduction and will not be repeated here. It will be understood that the embodiments of the present application can be used in different random access procedures, and the first random access request can be determined based on actual circumstances. In addition, the "first random access request" and "second random access request" in the embodiments of the present application are merely exemplary expressions, and both can be replaced with any possible expression, and the embodiments of the present application are not limited thereto.

[0237] After the access network device receives the first random access request, it can be understood that after the access network device receives the first random access request, and before the first terminal device registers with the access network device (or network). In other words, the time period corresponding to the access network device receiving the first random access request can be understood as the time period after the access network device receives the first random access request and the first terminal device has not registered with the access network device, that is, the access network device determines that the first identification is performed during this time period. It can be understood that if the first terminal device needs to register with the access network device, then after the first terminal device registers with the access network device, the access network device and the core network device will perform the initial context establishment process of the first terminal device. For details, please refer to the relevant introduction of the aforementioned "3. Initial context establishment process", which will not be repeated here. After completing the initial context establishment process, the access network device and the core network device can maintain the corresponding relationship for the identifier of the first terminal device, so that the access network device and the core network device can determine that the message is for the first terminal device based on the identifier in the message and the corresponding relationship. That is to say, in an embodiment of the present application, within a time period corresponding to when the access network device receives the first random access request from the first terminal device, the access network device and the core network device do not perform the initial context establishment process required after the first terminal device registers to the access network device.

[0238] After the access network device receives the first random access request, it can also be understood that the access network device completes the random access process with the first terminal device. For example, with respect to the aforementioned "4.A-IoT operation device process", the access network device (the above-mentioned RAN) can determine the first identifier when receiving a message (i.e., S310) including the identifier of the first terminal device sent by the first terminal device (the above-mentioned device 2). It can be understood that this is only an example, and in different random access processes, the time point at which the access network device completes the random access process with the first terminal device can be determined accordingly without limitation.

[0239] After receiving the first random access request, the access network device can also be understood to be in the process of executing the random access process. For example, for the aforementioned "4. A-IoT operation device process", the first identifier can be determined when the access network device (the above-mentioned RAN) sends a confirmation message (i.e., S309) to the first terminal device (the above-mentioned device 2) based on the first random access request. It can be understood that this is only an example, and different processes for executing random access processes can be determined according to different random access processes. The specific process can be determined according to actual conditions without limitation.

[0240] The first identifier can be used to indicate the first terminal device at the first signaling layer, and the first signaling layer can be a protocol layer between the access network device and the core network device, such as the NGAP layer, the A-IoT NGAP layer, etc. The "A-IoT NGAP layer" in the embodiment of the present application is only an exemplary expression, which can be replaced by any possible expression, and the embodiment of the present application is not limited. It can be understood that the first signaling layer can also be other layers, which can be set according to actual conditions without limitation. The first identifier can be a temporary identifier (i.e., a temporary identifier), and the format of the first identifier can be multiple, such as the format of the above-mentioned NGAP ID can be reused, which can be set according to actual conditions without limitation. The first identifier can be determined based on the information sent by the first terminal device during the random access process, such as the first identifier can be assigned to the first terminal device based on the information, or the information can be determined as the first identifier. The following explains the different situations.

[0241] Case 1: A first identifier is allocated based on information sent by the first terminal device during the random access process.

[0242] In this case, before the access network device determines the first identifier of the first terminal device, the above-mentioned communication method may also include: the access network device receives a first random access request, and the first random access request includes a second identifier; the above-mentioned determination of the first identifier of the first terminal device may specifically include: the access network device allocates a first identifier to the first terminal device based on the second identifier.

[0243] The second identifier can be used to indicate the first terminal device in the access control layer. It is understandable that the second identifier can be used to identify the first terminal device between the access network device and the first terminal device, that is, the access network device can identify the terminal device indicated by the second identifier as the first terminal device. The second identifier can be a temporary identifier (i.e., a temporary identifier), such as RN16, or other information that can characterize the first terminal device. It is understandable that the second identifier can be generated by the first terminal device itself, or configured by the network side, or predefined by the protocol, and can be flexibly set according to actual conditions without limitation. The access control layer can be a protocol layer between the terminal device (such as the first terminal device) and the access network device, which can include at least one of the following: media access control (MAC) layer, physical (PHY) layer, packet data convergence protocol (PDCP) layer, RRC layer, or radio link control (RLC) layer. Each protocol layer can refer to the existing technology and will not be described in detail here. It is understandable that the access control layer can also be other layers, which can be set according to actual conditions without limitation.

[0244] The second identifier may also be the identifier of the first process. The first process can be used by the first terminal device to perform a random access procedure. That is, the first process can be used by the first terminal device to perform a random access procedure. In other words, the first terminal device can perform random access within the first process. The first process is also related to the access control layer. That is, the first process can be a process in the access control layer. In this case, the access network device may have multiple processes for random access. That is, different terminal devices can perform random access through different processes. For example, if the access network device determines that it has two processes for random access and needs to operate two terminal devices, then these two terminal devices can use different processes for random access. Alternatively, if there are three terminal devices that need to operate, then one of the three terminal devices can use one process for random access, and the other two terminal devices can use another process for random access. It is understood that one process corresponds to the operation of one terminal device within a time period. That is, when a process is used by one terminal device, it must complete all operations on that terminal device before it can be used by another terminal device. In other words, a unique terminal device can be identified by the process identifier. That is, when a first terminal device uses the first process, the first terminal device can be identified by the first process identifier. It is understood that the first process can also be used by the first terminal device to execute the operation flow corresponding to the operation instruction (described below). That is, the first process can also be used by the first terminal device to perform the operation indicated by the operation instruction, that is, the first terminal device can perform the operation within the first process.

[0245] In scenario 1, the aforementioned allocation of the first identifier to the first terminal device based on the second identifier can be understood as generating the first identifier based on the second identifier. That is, after receiving the second identifier, the access network device can generate the first identifier based on the second identifier. In this case, the second identifier is different from the first identifier. It can be understood that the first identifier and the second identifier have a corresponding relationship. After the access network device allocates the first identifier to the first terminal device based on the second identifier, the access network device can maintain the corresponding relationship between the second identifier and the first identifier, facilitating the subsequent access network device to determine the second identifier based on the first identifier, and thus determine the first terminal device based on the second identifier.

[0246] In addition, in addition to being carried in the first random access request, the second identifier can also be carried in other messages sent by the first terminal device during the random access process. For example, for the aforementioned "4. A-IoT operation device process", the second identifier can also be carried in the RRC message sent by the first terminal device to the access network device based on the confirmation message (RRC message #1 in the above S310). The operation of carrying the second identifier in the other message is similar to the operation of carrying the second identifier in the first random access request, which can be understood by reference and will not be repeated here.

[0247] Case 2: The information sent by the first terminal device during the random access process is determined as the first identifier.

[0248] In this case, before the access network device determines the first identifier of the first terminal device, the above-mentioned communication method may also include: the access network device receives a first random access request, and the first random access request includes a second identifier; the above-mentioned determination of the first identifier of the first terminal device may specifically include: the access network device determines that the second identifier is the first identifier.

[0249] The second identifier can be used to indicate the first terminal device in the access control layer, and it can be the identifier of RN16 or the first process. For details, please refer to the relevant introduction in the above "Case 1" and will not be repeated here.

[0250] In case 2, the first identifier can reuse the second identifier. That is, after receiving the second identifier of the access control layer, the access network device can multiplex the second identifier of the access control layer to the first identifier of the first signaling layer, that is, the access network device can assign the value of the second identifier to the first identifier, and at this time the values ​​of the second identifier and the first identifier are the same. In this way, the access network device does not need to generate the first identifier, thereby reducing the processing overhead of the access network device. In addition, after the access network device determines the second identifier as the first identifier, it can maintain the correspondence between the second identifier and the first identifier, so that the subsequent access network device can determine the second identifier according to the first identifier, and thus determine the first terminal device according to the second identifier. Alternatively, the access network device may not maintain the correspondence between the second identifier and the first identifier, but when determining the second identifier through the first identifier in subsequent operations, assign the value of the first identifier to the second identifier; or when determining the first identifier through the second identifier in subsequent operations, assign the value of the second identifier to the first identifier.

[0251] It can be understood that, in addition to being carried in the first random access request, the second identifier can also be carried in other messages sent by the first terminal device during the random access process. For example, for the aforementioned "4. A-IoT Operation Device Process", the second identifier can also be carried in the RRC message sent by the first terminal device to the access network device based on the confirmation message (RRC message #1 in the above S310). In addition, the operation of carrying the second identifier in the other message is similar to the operation of carrying the second identifier in the first random access request, which can be understood by reference and will not be repeated here.

[0252] The above content describes a method for determining the first identifier based on information sent by the first terminal device during the random access process. It is understood that the access network device can also determine the first identifier based on other methods, without limitation. After the access network device determines the first identifier through other methods, it can associate the first identifier with the second identifier described above. That is, the first identifier and the second identifier now have a corresponding relationship, and the access network device can maintain this corresponding relationship, facilitating subsequent access network device determination of the second identifier based on the first identifier, thereby determining the first terminal device based on the second identifier.

[0253] In addition, the access network device may determine the first identifier of the first terminal device after receiving the first random access request of the first terminal device when multiple terminal devices are already connected.

[0254] S502: The access network device sends the first identifier and the identifier of the first terminal device to the core network device. Correspondingly, the core network device receives the first identifier and the identifier of the first terminal device from the access network device.

[0255] The first identifier can refer to the relevant introduction in the aforementioned "S501", which will not be repeated here.

[0256] The identifier of the first terminal device can be used to indicate the first terminal device in the second signaling layer. This identifier can be the EPC of the terminal device or other information that can identify the terminal device, without limitation. The identifier of the first terminal device can be sent by the first terminal device to the access network device, for example, during a random access process. For example, after receiving the first random access request, the access network device can send a confirmation message to the first terminal device. After receiving the confirmation message, the first terminal device can send the identifier of the first terminal device to the access network device. For details, please refer to the relevant description of "4. A-IoT Device Operation Process" above, which will not be repeated here. It is understood that the access network device cannot determine the identifier of the first terminal device, that is, it cannot decode the identifier of the first terminal device, such as by decoding information carrying the identifier of the first terminal device (such as special NAS information, such as AIoT NAS information) to obtain the identifier of the first terminal device. The aforementioned second signaling layer can be a protocol layer between the terminal device (such as the first terminal device) and the core network device, which can be a NAS layer. It is understood that the second signaling layer can also be other layers, which can be set according to actual circumstances and are not limited. And the first signaling layer and the second signaling layer may be different.

[0257] After determining the first identifier, the access network device can send the first identifier and the identifier of the first terminal device to the core network device to inform the core network device that the first terminal device has completed random access, that is, the core network device is already in the network. The message used to send the first identifier and the identifier of the first terminal device can reuse the message in the existing technology, such as the N2 message, or it can be a new message, such as a message of other interfaces. It can be set according to actual conditions and is not limited. It can be understood that the identifier of the first terminal device can be carried on a NAS message (or information), and the NAS message (or information) can be located in the message used to send the first identifier and the identifier of the first terminal device. Exemplarily, the first identifier is an N2 message, and the identifier of the first terminal device is a NAS message. The NAS message can be carried in the N2 message, that is, the access network device sends an N2 message to the core network device, and the N2 message includes the first identifier and a NAS message, and the NAS message carries the identifier of the first terminal device.

[0258] After receiving the first identifier and the identifier of the first terminal device from the access network device, the core network device can store the correspondence between the first identifier and the first terminal device, and can maintain the correspondence. In this way, after the core network device subsequently receives information including the first identifier, it can determine that the information is for the first terminal device based on the correspondence and the first identifier. It can be understood that the core network device can also associate the first identifier, the identifier of the first terminal device with the task identifier corresponding to the operation task (described below), that is, the first identifier, the identifier of the first terminal device and the task identifier have a correspondence. At this time, the core network device can maintain the correspondence. In addition, when the core network device interacts with multiple network devices, the core network device can also associate the first identifier, the identifier of the first terminal device, the task identifier and the identifier of the access network device, that is, the first identifier, the identifier of the first terminal device, the task identifier and the identifier of the access network device have a correspondence, so that when the core network device operates the first terminal, it can determine the access network device to which the operation instruction needs to be sent based on the correspondence.

[0259] S503, the core network device determines the operation of the first terminal device according to the identifier of the first terminal device (recorded as operation #1).

[0260] Operation #1 may be an environmental energy physical operation, such as a write operation, an inventory operation, a read operation, an invalidation operation, an interactive information operation, etc., which may be set according to actual conditions without limitation.

[0261] The core network device can determine operation #1 from the operations of multiple stored terminal devices based on the identifier of the first terminal device. The operations of the multiple stored terminal devices can be sent by the service requester (such as AF) to the core network device. Exemplarily, before the core network device operates on multiple terminal devices, it can receive a service request from the service requester. The service request may include operations performed on each of the multiple terminal devices. For example, the service request may include a read operation, the identifier of the first terminal device, and the identifier of the second terminal device, that is, the service request can be used to request a read operation on the first terminal device and the second terminal device. For details, please refer to the relevant introduction in the aforementioned "4.A-IoT Operation Device Process", which will not be repeated here. Of course, the operations of the multiple stored terminal devices can also be pre-configured or pre-defined by the protocol, and can be flexibly set according to actual conditions.

[0262] S504: The core network device sends an operation request message to the access network device. Correspondingly, the access network device receives the operation request message from the core network device.

[0263] The operation request message is determined based on the identifier of the first terminal device. The operation request message can be used to request the terminal device indicated by the first identifier to perform the operation indicated by the operation instruction (i.e., the above-mentioned operation #1), and it may include at least one of the following: a first identifier, or an operation instruction. The operation instruction can be used to instruct the execution of the above-mentioned operation #1, that is, it may include operation #1. It can be understood that the "operation request message" and "operation instruction" in the embodiment of the present application are only an exemplary expression, and the "operation request message" can be replaced by any possible expression, and the "operation instruction" can be replaced by any possible expression, and the embodiment of the present application does not limit it.

[0264] After determining Operation #1, the core network device may send an operation request message to the access network device based on the correspondence between the identifier of the first terminal device and the first identifier, as well as Operation #1, so that the access network device sends an operation instruction to the first terminal device based on the operation request message. It is understood that after receiving the operation request message, the access network device may not obtain the content of the operation instruction, that is, at this time, the access network device may not be aware of Operation #1.

[0265] S505: The access network device obtains a second identifier according to the first identifier.

[0266] The second identifier can refer to the relevant introduction in the aforementioned "S501" and will not be repeated here.

[0267] After receiving the operation request message, the access network device needs to send the operation instruction in the operation request message to the terminal device indicated by the first identifier (i.e., the first terminal device) so that the terminal device performs the operation indicated by the operation instruction. In this case, the access network device needs to determine the identifier indicating the first terminal device at the access control layer, that is, the access network device needs to determine the identifier based on the first identifier. Exemplarily, when the first identifier and the second identifier have a corresponding relationship, the access network device can index the second identifier based on the first identifier; or, when the first identifier and the second identifier are the same, the access network device can assign the value of the first identifier to the second identifier to obtain the second identifier.

[0268] S506: The access network device sends an operation instruction and a second identifier to the first terminal device. Correspondingly, the first terminal device receives the operation instruction and the second identifier from the access network device.

[0269] The operation instruction can refer to the relevant introduction in the aforementioned "S504", which will not be repeated here. The second identifier can refer to the relevant introduction in the aforementioned "S501", which will not be repeated here. It can be understood that the operation instruction and the second identifier can be two parallel information, or the second identifier can be carried in the operation instruction. The specific form can be flexibly set according to the actual situation without restriction. The access network device may not know the operation instruction. In this case, it can transparently transmit the operation instruction to the first terminal device according to the operation request message, such as sending the operation instruction through a NAS message.

[0270] The access network device sends a second identifier to the first terminal device, enabling the terminal device that receives the operation instruction to determine whether the operation instruction is the instruction sent to it based on the second identifier carried in the operation instruction, thereby ensuring that the operation instruction is sent to the first terminal device. Furthermore, the access network device sends the operation instruction to the first terminal device, enabling the first terminal device to execute the operation instruction, thereby completing operation #1 above. That is, after receiving the operation instruction from the access network device, the first terminal device can perform the operation indicated by the operation instruction. For example, when the operation instruction is a read operation, the first terminal device can send data information stored in the first terminal device's storage area to the access network device. For example, when the operation instruction is a write operation, the first terminal device can store the data information to be written in the operation instruction in its storage area.

[0271] In summary, in an embodiment of the present application, the access network device can determine the first identifier for the first signaling layer for the first terminal device, and send the first identifier and the identifier of the first terminal device to the core network device; the core network device can determine the operation instruction to be executed by the first terminal device based on the identifier of the first terminal device, and send the operation instruction and the first identifier to the access network device, so that the access network device indexes the second identifier based on the first identifier, and sends the operation instruction and the second identifier to the first terminal device. At this time, the first terminal device can determine that the operation instruction is the instruction sent to it based on the second identifier, thereby executing the operation indicated by the operation instruction. It can be understood that the first terminal device can be any terminal device among the terminal devices that need to be operated. In other words, the access network device can determine the identifier used for the terminal device at the first signaling layer, so that the access network device and the core network device can indicate the terminal device through the identifier, thereby realizing the operation of the terminal device. In this way, when operations need to be performed on multiple terminal device processes, the access network device can trigger random access of each of the multiple terminal devices by itself, and the core network device can operate the terminal device that has completed random access when the terminal device is performing random access; that is, for multiple terminal devices that need to be operated, there is no need to complete random access and operation on one terminal device before performing random access and operation on the next terminal device, which can improve the efficiency of operating multiple terminal devices.

[0272] Optionally, in combination with the above embodiment, after the first terminal device completes the operation instruction, the above communication method may further include: the first terminal device sends the operation result to the access network device, and accordingly, the access network device receives the operation result from the first terminal device, and the operation result is the result of the first terminal device executing the operation instruction; the access network device sends the operation result and the first identifier to the core network device, and accordingly, the core network device receives the operation result and the first identifier from the access network device. In other words, the access network device can send the result of the first terminal device executing the operation indicated by the operation instruction to the core network device. The core network device can send the operation result to the service requester (such as AF), so that the service requester adjusts the service based on the operation result.

[0273] It can be understood that when the operation instructions are different, the corresponding results are also different. For example: when the operation instruction is a read operation, the operation result may be the data information stored in the storage area of ​​the first terminal device; for example: when the operation instruction is a write operation, the operation result may be that the first terminal device has stored the data information to be written in the operation instruction in its storage area.

[0274] Optionally, in combination with the above embodiment, for the above situation 1, after the access network device assigns the first identifier to the first terminal device based on the second identifier, the above communication method may further include: the access network device saves the context of the first terminal device, and the context of the first terminal device may include the first identifier and / or the second identifier. It can be understood that the context of the first terminal device may also include the correspondence between the first identifier and the second identifier, and the access network device may maintain the correspondence. That is, at this time, the context of the first terminal device may include at least one of the following: the first identifier, the second identifier, or the correspondence between the first identifier and the second identifier. In this way, it is convenient for the access network device to determine the second identifier based on the context of the first terminal device, such as the first identifier and the correspondence, after receiving the message carrying the first identifier, thereby determining the first terminal device based on the second identifier.

[0275] Furthermore, the operation request message may also include first indication information, where the first indication information is used to instruct the access network device to delete (or release) the context of the first terminal device after completing the operation on the first terminal device.

[0276] After receiving the above-mentioned operation request message, the access network device may delete (or release) the context of the first terminal device after completing the operation on the first terminal device. In different situations, the time point when the access network device completes the operation on the first terminal device may be different. For example, in the case where the access network device does not need to send the operation result of the first terminal device executing the operation instruction #a1 to the core network device, the access network device completing the operation on the first terminal device can be understood as when the access network device has finished sending the operation instruction #a1 to the first terminal device. Alternatively, in the case where the access network device needs to send the operation result of the first terminal device executing the operation instruction #a1 to the core network device, the access network device completing the operation on the first terminal device can be understood as when the access network device has finished sending the operation result of the first terminal device executing the operation instruction #a1 to the core network device. Among them, the operation instruction #a1 can be the last operation instruction sent by the access network device to the first terminal device. The context of the first terminal device may include a first identifier and a second identifier. For details, please refer to the relevant introduction in the aforementioned "Case 1", which will not be repeated here. After completing the operation on the first terminal device, the access network device deletes the context of the first terminal device, so that the access network device can release the context of the first terminal device in time, thereby avoiding redundancy and improving storage efficiency.

[0277] It is understood that after completing the operation on the first terminal device, the core network device may delete (or release) the context of the first terminal device. The context of the first terminal device may include at least one of the following: a first identifier, an identifier of the first terminal device, and an identifier of the access network device. For details, please refer to the aforementioned description of "S502" and will not be repeated here. In different situations, the time when the core network device completes the operation on the first terminal device may vary. Continuing with the above example, if the core network device does not require the access network device to provide feedback on the result of the first terminal device executing operation instruction #a1, the core network device completing the operation on the first terminal device can be understood as when the core network device completes sending operation instruction #a1 to the access network device. Alternatively, if the core network device requires the access network device to provide feedback on the result of the first terminal device executing operation instruction #a1, the core network device completing the operation on the first terminal device can be understood as when the core network device receives the result of the first terminal device executing operation instruction #a1 from the access network device. After the core network device completes the operation on the first terminal device, deleting the context of the first terminal device allows the core network device to release the context of the first terminal device in a timely manner, thereby avoiding redundancy and improving storage efficiency.

[0278] In addition, the access network device can also periodically delete the context of the first terminal device, for example: the access network device deletes the context of the first terminal device after each preset time period. The access network device can also delete the context of the first terminal device according to the instructions of other devices other than the core network device. The access network device can also determine by itself whether the operation on the first terminal device is completed, and delete the context of the first terminal device after determining that the operation on the first terminal device is completed, that is, there is no need to delete the context of the first terminal device according to the above-mentioned first indication information. In the case where the access network device determines by itself whether the operation on the first terminal device is completed, the access network device can send information for instructing the deletion of the context of the first terminal device to the core network device after determining that the operation on the first terminal device is completed, so that the core network device deletes the context of the first terminal device.

[0279] Furthermore, when the access network device saves the context of the first terminal device, the context of the first terminal device can also be associated with the operation task. In this case, when the access network device saves the context of the first terminal device, it can also save the task identifier (task ID) of the operation task. The task identifier can be preset, predefined by the protocol, or sent to the access network device by the core network device, and the "task identifier" in the embodiment of the present application is only an exemplary expression. The "task identifier" can be replaced by any possible expression, such as "event identifier", which is not limited in the embodiment of the present application. It can be understood that the task identifier, the first identifier, and the second identifier have a corresponding relationship, that is, the task identifier has a corresponding relationship with the first identifier, the first identifier has a corresponding relationship with the second identifier, and the access network device can maintain the corresponding relationship. It can be understood that at this time, the context of the first terminal device can include at least one of the following: the first identifier, the second identifier, the task identifier, the corresponding relationship between the first identifier and the second identifier, or the corresponding relationship between the first identifier and the task identifier.

[0280] Exemplarily, before the access network device receives the first random access request, the communication method may further include: the core network device sending an operation task request message to the access network device; the access network device correspondingly receiving the operation task request message from the core network device, the operation task request message including a task identifier; the access network device broadcasting a second random access request based on the operation task request message; and the context of the first terminal device also including the task identifier. The operation task request message may be a request for random access to multiple terminal devices sent by the core network device to the access network device. For details, please refer to the description of N2 message #1 in "S305" above and will not be repeated here. The operation task request message may also instruct the access network device to save the context of the terminal device requiring operation, such as the context of the first terminal device. The task identifier may be the identifier of the task corresponding to the operation task request message. It is understood that the entire operation corresponding to the operation task request message may be considered a task, and the task identifier may be understood as the identifier of the task. That is, the operation task may include an operation on the first terminal device, or in other words, the operation task may include operations on multiple terminal devices requiring operation. This allows the core network device to manage the operation task indicated by the task identifier using the task identifier. For example, after the operation task is completed, the core network device can be instructed to delete the context containing the task identifier, thereby deleting the entire context of the terminal device corresponding to the completed operation task. This allows management at the task granularity.

[0281] It is understood that the core network device can obtain the task identifier from the service requester. For example, when the service requester includes an NEF and an AF, the NEF can generate a task identifier based on the service request sent by the AF, identify the operation corresponding to the service request through the task identifier, and send the task identifier to the core network device. The core network device can also generate a task identifier based on the operation task without limitation.

[0282] In this case, after the access network device saves the context of the first terminal device, the above-mentioned communication method may also include: after the core network device determines that the operation task indicated by the task identifier is completed, the core network device sends the task identifier and the second indication information to the access network device, and accordingly, the access network device receives the task identifier and the second indication information from the core network device, and the second indication information is used to instruct the access network device to delete the context containing the task identifier; the access network device deletes the context of the first terminal device according to the task identifier and the second indication information.

[0283] The core network device can determine that the operation task is completed when it determines the operation results corresponding to each terminal device in the received operation task. For example, if there are three terminal devices that need to be operated, the core network device can determine that the operation task is completed after receiving the operation results of these three terminal devices. The core network device can also determine that the operation task is completed after sending an operation instruction to each terminal device in the operation task. For example, if there are four terminal devices that need to be operated, the core network device can determine that the operation task is completed after sending the corresponding operation instruction to the access network device, without restriction. After determining that the operation task is completed, the core network device sends a task identifier and a second indication information to the access network device, which enables the access network device to delete the context of multiple terminal devices corresponding to the operation task, thereby realizing the management of the entire task.

[0284] It is understood that the core network device may also send a task identifier and a second indication information to the access network device when receiving the deletion indication information from the service requester. The deletion indication information is used to indicate the deletion of the context containing the task identifier, and it may include the task identifier. The "deletion indication information" in the embodiment of the present application is only an exemplary expression, and the "deletion indication information" can be replaced by any possible expression, such as "deletion instruction", which is not limited by the embodiment of the present application.

[0285] It can also be understood that the core network device can delete (or release) the context of the first terminal device after determining that the operation task indicated by the task identifier is completed. The context of the first terminal device may include at least one of the following: the first identifier, the identifier of the first terminal device, the task identifier, and the identifier of the access network device. For details, please refer to the relevant introduction of "S502" above, which will not be repeated here. After the core network device completes the operation on the first terminal device, deleting the context of the first terminal device can enable the core network device to release the context of the first terminal device in a timely manner, thereby avoiding redundancy and improving storage efficiency.

[0286] In addition, the access network device can also periodically delete the context of the first terminal device, for example: the access network device deletes the context of the first terminal device after each preset time period. The access network device can also delete the context of the first terminal device according to the instructions of other devices other than the core network device. The access network device can also determine by itself whether the operation task is completed, and after determining that the operation task is completed, delete the context corresponding to the operation task, that is, the context containing the task identifier, that is, the context of the first terminal device. In other words, at this time, the access network device does not need to delete the context of the first terminal device according to the above-mentioned second indication information. In the case where the access network device determines by itself whether the operation is completed, the access network device can send information for indicating the deletion of the context corresponding to the operation task, or information for deleting the context containing the task identifier to the core network device after determining that the operation task is completed, so that the core network device deletes the context corresponding to the operation task, that is, the context containing the task identifier.

[0287] Optionally, in combination with the above embodiment, for the above situation 2, after the access network device determines that the second identifier is the first identifier, the access network device can associate the first identifier of the first terminal device with the task. That is, the access network device can save the context of the first terminal device, and the context of the first terminal device can include at least one of the following: the first identifier, the second identifier, or the task identifier of the task. The task identifier can be pre-set, pre-defined by the protocol, or sent to the access network device by the core network device. It can be understood that the task identifier and the first identifier have a corresponding relationship, the first identifier and the second identifier have a corresponding relationship, and the access network device can maintain these two sets of corresponding relationships. And the context of the first terminal device can also include that the task identifier and the first identifier have a corresponding relationship, and / or that the first identifier and the second identifier have a corresponding relationship.

[0288] Exemplarily, before the access network device receives the first random access request, the above-mentioned communication method may further include: the core network device sends an operation task request message to the access network device, and accordingly, the access network device receives the operation task request message from the core network device, and the operation task request message includes a task identifier; the access network device broadcasts a second random access request according to the operation task request message; after the access network device determines that the second identifier is the first identifier, the access network device saves the context of the first terminal device, and the context of the first terminal device includes the task identifier and the first identifier. The operation task request message and the task identifier can refer to the above-mentioned related introduction and will not be repeated here. In this way, it is convenient for the core network device to manage the operation task indicated by the task identifier through the task identifier, for example: after the operation task is completed, the access network device is instructed to delete the context including the task identifier, thereby deleting the entire context of the terminal device corresponding to the completed operation task. In this way, management can be performed at the task granularity.

[0289] In this case, after the access network device saves the context of the first terminal device, the above-mentioned communication method may further include: after the core network device determines that the operation task indicated by the task identifier is completed, the core network device sends the task identifier and second indication information to the access network device, and accordingly, the access network device receives the task identifier and second indication information from the core network device, the second indication information being used to instruct the access network device to delete (or release) the context containing the task identifier; and the access network device deletes (or releases) the context of the first terminal device according to the task identifier and the second indication information. For details, please refer to the above-mentioned related introduction and will not be repeated here.

[0290] It is understood that the core network device may also send the task identifier and the second indication information to the access network device when receiving the deletion indication information from the service requester. The deletion indication information can be referred to the above related introduction and will not be repeated here.

[0291] It can also be understood that the core network device can delete (or release) the context of the first terminal device after determining that the operation task indicated by the task identifier is completed. The context of the first terminal device may include at least one of the following: the first identifier, the identifier of the first terminal device, the task identifier, and the identifier of the access network device. For details, please refer to the above-mentioned relevant introduction and will not be repeated here.

[0292] In addition, the access network device may also periodically delete the context of the first terminal device; the access network device may also delete the context of the first terminal device according to instructions from other devices other than the core network device; the access network device may also independently determine whether the operation task is completed, and delete the context corresponding to the operation task after determining that the operation task is completed. For details, please refer to the above-mentioned related introduction, which will not be repeated here. In the case where the access network device independently determines whether the operation is completed, the access network device may send information for instructing to delete the context corresponding to the operation task, or information for deleting the context containing the task identifier, to the core network device after determining that the operation task is completed, so that the core network device deletes the context corresponding to the operation task, that is, the context containing the task identifier.

[0293] Optionally, in combination with the above embodiment, before the access network device receives the first random access request from the first terminal device, the above communication method may further include: the core network device sends third indication information to the access network device, and accordingly, the access network device receives the third indication information from the core network device, and the third indication information is used to instruct the access network device to trigger random access for each of the multiple terminal devices when accessing multiple terminal devices. In other words, the core network device can instruct the access network device to trigger random access for each of the multiple terminal devices on its own, that is, after the core network device completes random access for one terminal device, it does not need to wait for the instruction of the core network device to trigger random access for the next terminal device. In this way, the time slot utilization rate of the access network device can be improved.

[0294] Optionally, in combination with the above embodiment, before the access network device sends the first identifier and the identifier of the first terminal device to the core network device, the above communication method may also include: the access network device broadcasts a second random access request, and accordingly, the first terminal device receives the second random access request from the access network device, the second random access request includes the identifier of the first process, the first process is used by the terminal device in executing the random access process, and the first process is related to the access control layer; the first terminal device sends a first random access request to the access network device based on the second random access request, and accordingly, the access network device receives the first random access request, and the first random access request includes the identifier of the first process; the access network device sends a confirmation message to the first terminal device based on the first random access request, and accordingly, the first terminal device receives the confirmation message from the access network device, the confirmation message including the identifier of the first process; the first terminal device sends the identifier of the first terminal device to the access network device based on the confirmation message, and accordingly, the access network device receives the identifier of the first terminal device from the first terminal device.

[0295] The second random access request may refer to the relevant description in the aforementioned "S501" and will not be repeated here. The second random access request includes the identifier of the first process, which enables the terminal device (such as the first terminal device) that determines to perform random access in the first process to send a random access request to the access network device after receiving the second random access request.

[0296] The first process can be used by the first terminal device to perform random access, that is, the first terminal device can perform random access within the first process. The first process can also be used by the first terminal device to perform the operation indicated by the operation instruction, that is, the first process can also be used by the first terminal device to perform the operation indicated by the operation instruction, that is, the first terminal device can perform the operation within the first process. The first process can be one of multiple processes determined by the access network device for random access. There are various relationships between the number of multiple processes and the number of multiple terminal devices that need to be operated, which are explained in detail below.

[0297] The number of multiple processes can be less than the number of multiple terminal devices. In this case, at least some of the terminal devices in the multiple processes use the same process. It can be understood that when the at least some of the terminal devices use the same process, the operation of the next terminal device will not start until the operation of one terminal device is completed, that is, each terminal device in the at least some of the terminal devices uses the same process in sequence. In other words, a terminal device can be determined by a process. For example, the number of multiple processes is 3, namely process #b1-process #b3, and the number of multiple terminal devices is 4, namely terminal device #b1-terminal device #b4. At this time, terminal device #b1 can use process #b1 for random access, terminal device #b2 can use process #b2 for random access, and terminal device #b3 and terminal device #b4 can use process #b3 for random access. For example, terminal device #b3 first uses process #b3 for random access, and after terminal device #b3 completes random access and completes the corresponding operation, terminal device #b4 uses process #b3 for random access.

[0298] The number of multiple processes can be equal to the number of multiple terminal devices. In this case, multiple terminal devices can use different processes for random access. For example, if the number of multiple processes is three, i.e., process #c1 - process #c3, and the number of multiple terminal devices is three, i.e., terminal device #c1 - terminal device #c3, then terminal device #c1 can use process #c1 for random access, terminal device #c2 can use process #c2 for random access, and terminal device #c3 can use process #c3 for random access.

[0299] The number of multiple processes can be greater than the number of multiple terminal devices. In this case, multiple terminal devices can use at least some of the multiple processes for random access, and multiple terminal devices can use different processes for random access. For example, if the number of multiple processes is six, namely process #d1 - process #d6, and the number of multiple terminal devices is three, namely terminal device #d1 - terminal device #d3, then terminal device #d1 can use process #d1 for random access, terminal device #d2 can use process #d3 for random access, and terminal device #d3 can use process #d5 for random access.

[0300] The first random access request includes the identifier of the first process, which enables the access network device to determine that the first random access request is a request for the first process based on the identifier of the first process in the first random access request. It can be understood that the first random access request can also include RN16 corresponding to the first terminal device. At this time, for Case 1 and Case 2, the second identifier can be the identifier of the first process or RN16, which can be determined based on actual conditions and will not be repeated here. It can be understood that when the second identifier is the identifier of the first process, the first random access request can also include RN16, and the access network device can maintain the correspondence between the identifier of the first process and RN16 when receiving the first random access request. At this time, the context of the first terminal device can include at least one of the following: the identifier of the first process, RN16, or the correspondence between the identifier of the first process and RN16.

[0301] The confirmation message may be a message sent by the access network device in response to the first random access request, which may be an ACK command. The confirmation message may also include RN16.

[0302] Before the access network device sends the first identifier and the identifier of the first terminal device to the core network device, the first terminal device can perform random access through the first process. That is, when the access network device broadcasts the second random access request for the first process, the first terminal device can send the first random access request to the access network device based on the second random access request to request access to the access network device. In this way, the first terminal device can achieve random access through the first process. It is understood that when the first terminal device performs random access in the above manner, the access network device can determine the first identifier after receiving the first random access request; it can also determine the first identifier after receiving the identifier of the first terminal device. The specific setting can be set according to actual circumstances and is not limited.

[0303] In addition, the access network device may allocate a first process to the first terminal device. Alternatively, the first terminal may be pre-set or pre-defined by a protocol to use the first process for random access. Alternatively, the first terminal device may select the first process on its own. For example, the access network device may broadcast the number of processes used for random access (the number of processes) or the identifier of the process used for random access. The first terminal device may select the first process for random access based on the number of processes or the identifier. The method for determining the first process may be flexibly set according to actual circumstances and is not restricted.

[0304] Exemplarily, before the access network device broadcasts the second random access request, the above communication method may also include: the access network device broadcasts the process number used for random access, and accordingly, the first terminal device receives the process number; the first terminal device determines to participate in the random access corresponding to the first process based on the process number.

[0305] For example, the number of processes broadcast by the access network device is 5, that is, there are 5 processes available for random access, such as process #a1 to process #5. Terminal device #a1 can choose process #a1 for random access, and terminal device #a2 can choose process #a3 for random access.

[0306] Exemplarily, before the access network device broadcasts the second random access request, the above-mentioned communication method may also include: the access network device broadcasts the process identifiers of multiple processes used for random access, and accordingly, the first terminal device receives the process identifier; the first terminal device determines to participate in the random access corresponding to the first process based on the process identifier.

[0307] For example, the access network device broadcasts three process identifiers, such as process ID#1-process ID#3, and the terminal device #a11 can select the process corresponding to process ID#1 for random access.

[0308] After the first terminal device determines to participate in the random access corresponding to the first process, when the first terminal device receives a second random access request including the identifier of the first process, it can send the first random access request based on the second random access request. It is understood that each of the multiple terminal devices to be operated can determine the process in which the terminal device participates based on the process number or process identifier. When multiple terminal devices select the same process for random access, random access can be performed in a competitive manner, and the terminal device that fails in the competition can subsequently perform random access again.

[0309] Furthermore, before the first terminal device completes random access, the above-mentioned communication method may further include: the access network device broadcasts a third random access request, and the third random access request includes an identifier of the second process. The second process is used by the terminal device to execute the random access process, and the second process is related to the access control layer, that is, the second process can be a process in the access control layer. It can be understood that the second process is different from the first process. In other words, the access network device does not need to trigger the random access of the next terminal device after the random access of the first terminal device is completed, that is, the access network device can trigger the random access of the next terminal device during the process of random access of the first terminal device, thereby improving the time slot utilization of the access network device.

[0310] For example, as shown in Figure 6, there are two terminal devices that need to be operated. If random access is performed on these two terminal devices through one process (process #1 in Figure 6), the random access of the next terminal device can only be triggered after the access of one terminal device is completed. That is, after completing the operation of sending the first repeated query message to the EPC in Figure 6, the access network device will send a repeated query message again to trigger the random access of the next terminal device. If the access network device accesses these two terminal devices respectively through two processes (process #2 and process #3 in Figure 6), that is, these two terminal devices perform random access respectively through these two processes, the access network device can use the time period (T2 in Figure 6) of waiting for the terminal device to return a confirmation message during the first random access process to send a repeated query message again to trigger the random access of the next terminal device. In this way, the time slot utilization rate of the access network device can be improved.

[0311] It is understood that the above content is an introduction to a specific random access process. The embodiment of the present application can also be used for other random access processes. When used for different random access processes, the random access process can be adaptively changed to enable the first terminal device to achieve random access through the first process.

[0312] Optionally, in combination with the above embodiment, after the core network device receives the first identifier and the identifier of the first terminal device from the access network device, the communication method may further include: the core network device determining a third identifier for the first terminal device. The third identifier may be used to indicate the first terminal device at the first signaling layer, and the third identifier may be used to identify the first terminal device between the access network device and the core network device. The third identifier may be determined based on the identifier of the first terminal device or the first identifier; in other words, the third identifier may be assigned based on the identifier of the first terminal device or the first identifier. It is understood that after determining the third identifier, the core network device may associate the third identifier with the first identifier, i.e., the third identifier and the first identifier now have a corresponding relationship, and the core network device may maintain this corresponding relationship. Furthermore, the core network device may store the corresponding relationship between the third identifier and the first identifier when storing the context of the first terminal device, i.e., the context of the first terminal device corresponding to the core network device now includes the corresponding relationship between the third identifier and the first identifier. In this case, when the access network device deletes the context of the first terminal device, it may delete the corresponding relationship between the third identifier and the first identifier.

[0313] Furthermore, the operation request message may also include a third identifier of the first terminal device determined by the core network device. After receiving the operation request message, the access network device may determine that the third identifier and the first identifier have a corresponding relationship based on the third identifier and the first identifier carried in the operation request message, and maintain the corresponding relationship. In addition, the access network device may store the corresponding relationship between the third identifier and the first identifier when storing the context of the first terminal device, that is, at this time, the context of the first terminal device includes the corresponding relationship between the third identifier and the first identifier. In this case, the access network device may delete the corresponding relationship between the third identifier and the first identifier when deleting the context of the first terminal device.

[0314] It can be understood that in the embodiments of the present application, the access network device can also be understood as a reader / writer, or in other words, the access network device can be replaced by a reader / writer, and the reader / writer can be a terminal device or other device with reader / writer functions. The reader / writer can be specifically described in the aforementioned "2.A-IoT", which will not be repeated here.

[0315] In addition, in the embodiments of the present application, the names of each message, each instruction, each signaling layer, each protocol layer, and each identifier are merely examples of expressions. Each message, each instruction, each signaling layer, each protocol layer, and each identifier may be replaced with any possible expression, without limitation in the embodiments of the present application. Furthermore, the instructions in the embodiments of the present application may also be replaced with information elements, information, or messages, and the specific settings may be made according to actual circumstances without limitation.

[0316] The above is a general introduction to the communication method provided by the embodiment of the present application in combination with the method embodiment. For ease of understanding, the above method is introduced below with three specific scenarios.

[0317] Scenario 1:

[0318] Figure 7 is a second flow chart of the communication method provided in an embodiment of the present application. This method is applicable to the communication system shown in Figure 4, and mainly involves the interaction between RAN (the above-mentioned access network device), TMF (the above-mentioned core network device), device #1, device #2, NEF, and AF. In scenario 1, it is necessary to operate on device #1 and device #2. RAN allocates a temporary identifier to the device based on the identifier in the random access request sent by the device (device #1 or device #2), and identifies the uplink and downlink signaling through the identifier, thereby completing the operation on the device.

[0319] S701: AF sends an environmental energy acquisition IoT service request to NEF. Correspondingly, NEF receives the environmental energy acquisition IoT service request from AF.

[0320] The ambient energy acquisition IoT service request includes the AF identifier, a read operation, and a device list, which includes the identifiers of device #1 and device #2. It is understood that the read operation can be replaced with other operations, such as inventory operations or write operations, depending on the actual situation.

[0321] S702: NEF performs TMF selection operation.

[0322] S703: NEF sends an environmental energy acquisition IoT service request to TMF. Correspondingly, TMF receives the environmental energy acquisition IoT service request from NEF.

[0323] S704, TMF performs a reader / writer selection operation.

[0324] S705: TMF sends N2 message #1 to RAN. Correspondingly, RAN receives N2 message #1 from TMF.

[0325] N2 message #1 corresponds to the above-mentioned operation task request message.

[0326] Optionally, the N2 message #1 may further include a task identifier of the operation task.

[0327] S706: RAN broadcasts a selection command.

[0328] S707, RAN broadcasts a query command.

[0329] The query command corresponds to the above-mentioned second random access request.

[0330] S708: Device #2 sends RN16-1 to RAN. Correspondingly, RAN receives RN16-1 from device #2.

[0331] It can be understood that the message used to send RN16-1 corresponds to the first random access request, and RN16-1 corresponds to the second identifier.

[0332] S709: RAN sends a confirmation message #1 to device #2 according to RN16-1 sent by device #2. Correspondingly, device #2 receives the confirmation message #1 from RAN.

[0333] Confirmation message #1 includes RN16-1, and confirmation message #1 corresponds to the above confirmation message.

[0334] S710: Device #2 sends RRC message #1 to RAN according to confirmation message #1. Correspondingly, RAN receives RRC message #1 from device #2.

[0335] Optionally, RRC message #1 includes RN16-1.

[0336] S711, RAN generates a temporary identifier (denoted as identifier #f1) according to RN16-1.

[0337] The identifier #f1 corresponds to the first identifier mentioned above.

[0338] It is understood that after generating the identifier #f1, the RAN can store the context of the device #2 and maintain the corresponding relationship between the RN 16-1 and the identifier #f1. The context of the device #2 includes the RN 16-1 and the identifier #f1.

[0339] S712: RAN sends N2 message #2 to TMF according to RRC message #1. Correspondingly, TMF receives N2 message #2 from RAN.

[0340] The N2 message #2 includes the identifier of the device #2 and the identifier #f1, and the information carrying the identifier of the device #2 may be NAS information.

[0341] S713: RAN broadcasts a repeated query message.

[0342] S714, device #1 sends RN16-2 to RAN. Correspondingly, RAN receives RN16-2 from device #1.

[0343] It can be understood that the message used to send RN16-2 corresponds to the first random access request, and RN16-2 corresponds to the second identifier, and RN16-1 is different from RN16-2.

[0344] S715: RAN sends a confirmation message #2 to device #1 according to RN16-2 sent by device #1. Correspondingly, device #1 receives the confirmation message #2 from RAN.

[0345] Among them, confirmation message #2 includes RN16-2, and confirmation message #2 corresponds to the above confirmation message.

[0346] S716: Device 1 sends RRC message #2 to RAN based on confirmation message #2. Correspondingly, RAN receives RRC message #2 from device #1.

[0347] Optionally, RRC message #2 includes RN16-2.

[0348] S717, RAN generates a temporary identifier (denoted as identifier #f2) according to RN16-2.

[0349] The identifier #f2 corresponds to the first identifier mentioned above.

[0350] It is understood that after generating the identifier #f2, the RAN can store the context of the device #1 and maintain the corresponding relationship between the RN 16-2 and the identifier #f2. The context of the device #1 includes the RN 16-2 and the identifier #f2.

[0351] S718: RAN sends N2 message #3 to TMF according to RRC message #2. Correspondingly, TMF receives N2 message #3 from RAN.

[0352] N2 message #3 includes the identifier of device #1 and identifier #f2. The information carrying the identifier of device #1 may be NAS information.

[0353] S719: TMF sends N2 message #4 to RAN. Correspondingly, RAN receives N2 message #4 from TMF.

[0354] N2 message #4 includes a service request, an identifier #f1, and an end indication. When the service request is a read operation, the read operation may include the location that the device needs to read (e.g., storage area information). N2 message #4 corresponds to the operation request message, the service request corresponds to the operation instruction, and the end indication corresponds to the first indication.

[0355] It can be understood that S719 can be performed after device #2 completes random access, for example: after device #2 completes random access, it can be executed during the random access process of device #1, such as after S713 and before S714. The specific settings can be made according to actual conditions without any restrictions.

[0356] S720: RAN sends RRC message #3 to device #2 according to N2 message #4. Accordingly, device #2 receives RRC message #3 from RAN.

[0357] RRC message #3 includes a service request and RN 16-1.

[0358] S721: Device #2 sends RRC message #4 to RAN according to RRC message #3. Correspondingly, RAN receives RRC message #4 from device #2.

[0359] RRC message #4 includes service response #1, which corresponds to the above-mentioned operation result. For details, please refer to the above-mentioned related introduction and will not be repeated here.

[0360] Optionally, RRC message #4 may include RN16-1.

[0361] S722: RAN sends N2 message #5 to TMF according to RRC message #3. Correspondingly, TMF receives N2 message #5 from RAN.

[0362] The N2 message #5 includes a service response and an identifier #f1.

[0363] S723, RAN and TMF release identification #f1.

[0364] That is, RAN and TMF delete the context of device #2.

[0365] S724: TMF sends service result #1 to NEF. Correspondingly, NEF receives service result #1 from TMF.

[0366] Service result #1 includes the identifier of AF, the identifier of device #1, and data, where the data is the result of the operation performed by device #1.

[0367] S725, NEF sends service result #1 to AF. Correspondingly, AF receives service result #1 from NEF.

[0368] S726: TMF sends N2 message #6 to RAN. Correspondingly, RAN receives N2 message #6 from TMF.

[0369] The N2 message #6 includes a service request, an identifier #f2, and end indication information. The N2 message #6 corresponds to the operation request message, the service request corresponds to the operation instruction, and the end indication information corresponds to the first indication information.

[0370] It can be understood that S726 can be performed after device #1 completes random access, for example: it can be performed after device #1 completes random access and before operating device #2, such as after S716 and before S719. The specific settings can be made according to actual conditions and will not be repeated here.

[0371] S727: RAN sends RRC message #5 to device #1 according to N2 message #6. Accordingly, device #1 receives RRC message #5 from RAN.

[0372] RRC message #5 includes a service request and RN16-2, and corresponds to the above-mentioned operation instructions. For details, please refer to the above-mentioned related introduction, which will not be repeated here.

[0373] S728: Device #1 sends RRC message #6 to the RAN according to RRC message #5. Correspondingly, the RAN receives RRC message #6 from device #1.

[0374] RRC message #6 includes service response #2, which corresponds to the above-mentioned operation result. For details, please refer to the above-mentioned related introduction and will not be repeated here.

[0375] Optionally, RRC message #6 may include RN16-2.

[0376] S729: RAN sends N2 message #7 to TMF according to RRC message #6. Correspondingly, TMF receives N2 message #7 from RAN.

[0377] The N2 message #7 includes a service response and an identifier #f2.

[0378] S730, RAN and TMF release identifier #f2.

[0379] That is, RAN and TMF delete the context of device #1.

[0380] S731, TMF sends service result #2 to NEF. Correspondingly, NEF receives service result #2 from TMF.

[0381] Service result #2 includes the identifier of AF, the identifier of device #2, and data, which is the result of the operation performed by device #1.

[0382] S732: NEF sends service result #2 to AF. Correspondingly, AF receives service result #2 from NEF.

[0383] It is understood that the above-mentioned S701-S732 can refer to the above-mentioned "S301-S325" and the related description of the embodiment shown in the above-mentioned FIG5, and will not be repeated here. In addition, the above-mentioned messages (such as N2 messages, NAS messages, etc.) can be replaced with other types of messages according to actual circumstances without limitation.

[0384] It should also be understood that when N2 message #1 includes the task identifier of the operation task, the access network device may also store the task identifier when storing the contexts of device #1 and device #2, allowing the core network device to delete the contexts of device #1 and device #2 by instructing it to delete the contexts containing the task identifier. In this case, after receiving N2 message #7 from the access network device, the core network device may send information to the access network device instructing it to delete the context containing the task identifier. Furthermore, N2 messages #4 and #6 may not carry end indication information.

[0385] Scenario 2:

[0386] Figure 8 is a flow chart of the communication method provided in an embodiment of the present application. This method is applicable to the communication system shown in Figure 4, and mainly involves the interaction between RAN (the above-mentioned access network device), TMF (the above-mentioned core network device), device #1, device #2, NEF, and AF. In scenario 2, it is necessary to operate on device #1 and device #2. The RAN determines the identifier in the random access request sent by the device (device #1 or device #2) as a temporary identifier, and identifies the uplink and downlink signaling through the identifier, thereby completing the operation of the device.

[0387] S801: AF sends an environmental energy acquisition IoT service request to NEF. Correspondingly, NEF receives the environmental energy acquisition IoT service request from AF.

[0388] S802, NEF performs TMF selection operation.

[0389] S803: NEF sends an environmental energy acquisition IoT service request to TMF. Correspondingly, TMF receives the environmental energy acquisition IoT service request from NEF.

[0390] S804, TMF performs a reader / writer selection operation.

[0391] S805: TMF sends N2 message #1 to RAN. Correspondingly, RAN receives N2 message #1 from TMF.

[0392] N2 message #1 corresponds to the above-mentioned operation task request message.

[0393] Optionally, the N2 message #1 may further include a task identifier of the operation task.

[0394] S806: RAN broadcasts a selection command.

[0395] S807, RAN broadcasts a query command.

[0396] The query command corresponds to the above-mentioned second random access request.

[0397] S808: Device #2 sends RN16-1 to RAN. Correspondingly, RAN receives RN16-1 from device #2.

[0398] It can be understood that the message used to send RN16-1 corresponds to the above-mentioned first random access request, and RN16-1 corresponds to the second identifier.

[0399] S809: RAN sends a confirmation message #1 to device #2 according to RN16-1 sent by device #2. Correspondingly, device #2 receives the confirmation message #1 from RAN.

[0400] Confirmation message #1 includes RN16-1, and confirmation message #1 corresponds to the above confirmation message.

[0401] S810: Device #2 sends RRC message #1 to RAN according to confirmation message #1. Correspondingly, RAN receives RRC message #1 from device #2.

[0402] Optionally, RRC message #1 includes RN16-1.

[0403] S811: RAN sends N2 message #2 to TMF according to RRC message #1. Correspondingly, TMF receives N2 message #2 from RAN.

[0404] N2 message #2 includes the identifier of device #2 and RN16-1. The information carrying the identifier of device #2 may be NAS information. It is understood that RN16-1 corresponds to the first identifier. That is, the RAN determines the second identifier as the first identifier.

[0405] S812: RAN broadcasts a repeated query message.

[0406] S813: Device #1 sends RN 16-2 to RAN. Correspondingly, RAN receives RN 16-2 from device #1.

[0407] It can be understood that the message used to send RN16-2 corresponds to the first random access request, and RN16-2 corresponds to the second identifier, and RN16-2 is different from RN16-1.

[0408] S814: RAN sends a confirmation message #2 to device #1 according to RN16-2 sent by device #1. Accordingly, device #1 receives the confirmation message #2 from RAN.

[0409] Confirmation message #2 includes RN16-2, and confirmation message #2 corresponds to the above confirmation message.

[0410] S815: Device #1 sends RRC message #2 to RAN based on confirmation message #2. Correspondingly, RAN receives RRC message #2 from device #1.

[0411] Optionally, RRC message #2 includes RN16-2.

[0412] S816: RAN sends N2 message #3 to TMF according to RRC message #2. Correspondingly, TMF receives N2 message #3 from RAN.

[0413] Among them, N2 message #3 includes the identifier of device #1 and RN16-2. The information carrying the identifier of device #1 can be NAS information. It can be understood that RN16-2 corresponds to the first identifier mentioned above. That is, the RAN determines the second identifier as the first identifier.

[0414] S817: TMF sends N2 message #4 to RAN. Correspondingly, RAN receives N2 message #4 from TMF.

[0415] The N2 message #4 includes a service request, RN16-1, and end indication information. The N2 message #4 corresponds to the operation request message, the service request corresponds to the operation instruction, and the end indication information corresponds to the first indication information.

[0416] It can be understood that S817 can be performed after device #2 completes random access, for example: after device #2 completes random access, it is executed during the random access process of device #1, such as after S810 and before S815. The specific settings can be made according to actual conditions without any restrictions.

[0417] S818: RAN sends RRC message #3 to device #2 according to N2 message #4. Accordingly, device #2 receives RRC message #3 from RAN.

[0418] RRC message #3 includes a service request and RN 16-1.

[0419] S819: Device #2 sends RRC message #4 to RAN according to RRC message #3. Correspondingly, RAN receives RRC message #4 from device #2.

[0420] RRC message #4 includes service response #1, which corresponds to the above operation result.

[0421] Optionally, RRC message #4 may include RN16-1.

[0422] S820: RAN sends N2 message #5 to TMF according to RRC message #3. Correspondingly, TMF receives N2 message #5 from RAN.

[0423] The N2 message #5 includes a service response and RN16-1.

[0424] S821, TMF sends service result #1 to NEF. Correspondingly, NEF receives service result #1 from TMF.

[0425] Service result #1 includes the identifier of AF, the identifier of device #1, and data, where the data is the result of the operation performed by device #1.

[0426] S822: NEF sends service result #1 to AF. Correspondingly, AF receives service result #1 from NEF.

[0427] S823: TMF sends N2 message #6 to RAN. Correspondingly, RAN receives N2 message #6 from TMF.

[0428] N2 message #6 includes a service request, RN16-2, and an end indication message. The N2 message #6 corresponds to the above-mentioned operation request message, the service request corresponds to the above-mentioned operation instruction, and the end indication message corresponds to the above-mentioned first indication message. For details, please refer to the above-mentioned related introduction and will not be repeated here.

[0429] It can be understood that S823 can be performed after device #1 completes random access, for example: it can be performed after device #1 completes random access and before operating device #2, such as after S815 and before S817. The specific settings can be made according to actual conditions and will not be repeated here.

[0430] S824: RAN sends RRC message #5 to device #1 according to N2 message #6. Accordingly, device #1 receives RRC message #5 from RAN.

[0431] RRC message #5 includes a service request and RN16-2.

[0432] S825: Device #1 sends RRC message #6 to the RAN according to RRC message #5. Correspondingly, the RAN receives RRC message #6 from device #1.

[0433] RRC message #6 includes service response #2, which corresponds to the above operation result.

[0434] Optionally, RRC message #6 may include RN16-2.

[0435] S826: RAN sends N2 message #7 to TMF according to RRC message #6. Correspondingly, TMF receives N2 message #7 from RAN.

[0436] The N2 message #7 includes a service response and RN16-2.

[0437] S827, TMF sends service result #2 to NEF. Correspondingly, NEF receives service result #2 from TMF.

[0438] Service result #2 includes the identifier of AF, the identifier of device #2, and data, which is the result of the operation performed by device #1.

[0439] S828: NEF sends service result #2 to AF. Correspondingly, AF receives service result #2 from NEF.

[0440] It can be understood that the above S801-S828 can refer to the relevant introduction of the embodiment shown in the aforementioned "S301-S325" and the aforementioned Figure 5, and will not be repeated here. And each of the messages mentioned above (such as N2 messages, NAS messages, etc.) can be replaced with other types of messages according to actual conditions without limitation. It can also be understood that when N2 message #1 includes a task identifier of the operation task, the access network device can also store the task identifier when storing the context of device #1 and device #2, so that the core network device can delete the context of device #1 and device #2 by instructing to delete the context containing the task identifier. For details, please refer to the relevant introduction in the above scenario 1, and will not be repeated here.

[0441] In addition, when device #1 and device #2 perform random access through different processes, the access network device and the core network device can also indicate the device based on the process identifier.

[0442] Scenario 3:

[0443] Figure 9 is a fourth flow chart of the communication method provided in an embodiment of the present application. This method is applicable to the communication system shown in Figure 4, and mainly involves the interaction between RAN (the above-mentioned access network device), TMF (the above-mentioned core network device), device #1, device #2, NEF, and AF. In scenario 3, it is necessary to operate on device #1 and device #2. RAN sets an identifier for temporary use of the device according to the identifier in the random access request sent by the device (device #1 or device #2), and identifies the uplink and downlink signaling through the identifier, thereby completing the operation of the device. In addition, device #1 and device #2 can perform random access through different processes.

[0444] S901: AF sends an environmental energy acquisition IoT service request to NEF. Correspondingly, NEF receives the environmental energy acquisition IoT service request from AF.

[0445] The ambient energy acquisition IoT service request includes the AF identifier, a read operation, and a device list, which includes the identifiers of device #1 and device #2. It is understood that the read operation can be replaced with other operations, such as inventory operations or write operations, depending on the actual situation.

[0446] S902: NEF performs TMF selection operation.

[0447] S903: NEF sends an environmental energy acquisition IoT service request to TMF. Correspondingly, TMF receives the environmental energy acquisition IoT service request from NEF.

[0448] S904, TMF performs a reader / writer selection operation.

[0449] S905: TMF sends N2 message #1 to RAN. Correspondingly, RAN receives N2 message #1 from TMF.

[0450] N2 message #1 corresponds to the above-mentioned operation task request message.

[0451] Optionally, the N2 message #1 may further include a task identifier of the operation task.

[0452] S906: RAN broadcasts a selection command.

[0453] The selection command includes the number of processes that can be used for random access, and the number of processes is 2, that is, the random access process can be performed through two processes.

[0454] S907, device #1 selects process #1 according to the selection command.

[0455] That is, device #1 selects process #1 for subsequent random access.

[0456] S908: Device #2 selects process #2 according to the selection command.

[0457] That is, device #2 selects process #2 for subsequent random access.

[0458] It is understandable that S907 and S908 can be performed simultaneously or in sequence without limitation.

[0459] S909: RAN broadcasts a query command.

[0460] The query command includes the identifier of process #2, that is, the RAN requests to select the device of process #2 for random access. The query command corresponds to the second random access request.

[0461] S910: Device #2 sends RN 16-1 to RAN. Correspondingly, RAN receives RN 16-1 from device #2.

[0462] It can be understood that device #2 also sends the identifier of process #2 to the RAN.

[0463] S911, RAN sends a confirmation message #1 to device #2 according to RN16-1 sent by device #2. Correspondingly, device #2 receives the confirmation message #1 from RAN.

[0464] Among them, confirmation message #1 includes the identifiers of RN16-1 and process #2, and confirmation message #1 corresponds to the above confirmation message. For details, please refer to the above related introduction and will not be repeated here.

[0465] S912: Device #2 sends RRC message #1 to RAN according to confirmation message #1. Correspondingly, RAN receives RRC message #1 from device #2.

[0466] Optionally, RRC message #1 may include an identifier of RN16-1 and / or process #2.

[0467] S913, RAN generates a temporary identifier (denoted as identifier #f1) according to RN16-1.

[0468] The identifier #f1 corresponds to the first identifier mentioned above.

[0469] It is understood that after generating the identifier #f1, the RAN can store the context of the device #2 and maintain the corresponding relationship between the RN 16-1 and the identifier #f1. The context of the device #2 includes the RN 16-1 and the identifier #f1.

[0470] S914: RAN sends N2 message #2 to TMF according to RRC message #1. Correspondingly, TMF receives N2 message #2 from RAN.

[0471] The N2 message #2 includes the identifier of the device #2 and the identifier #f1, and the information carrying the identifier of the device #2 may be NAS information.

[0472] S915: RAN broadcasts a repeat query message.

[0473] The repeated query message includes the identifier of process #1, that is, the RAN requests to select the device of process #1 for random access.

[0474] S916, device #1 sends RN16-2 to RAN. Correspondingly, RAN receives RN16-2 from device #1.

[0475] It can be understood that device #1 also sends the identifier of process #2 to the RAN.

[0476] S917: RAN sends a confirmation message #2 to device #1 according to RN16-2 sent by device #1. Correspondingly, device #1 receives the confirmation message #2 from RAN.

[0477] Confirmation message #2 includes the identifiers of RN16-2 and process #1, and confirmation message #2 corresponds to the above confirmation message. For details, please refer to the above related introduction and will not be repeated here.

[0478] S918: Device 1 sends RRC message #2 to RAN based on confirmation message #2. Correspondingly, RAN receives RRC message #2 from device #1.

[0479] Optionally, RRC message #2 may include an identifier of RN16-2 and / or process #1.

[0480] S919, RAN generates a temporary identifier (denoted as identifier #f2) according to RN16-2.

[0481] The identifier #f2 corresponds to the first identifier mentioned above.

[0482] It is understood that after generating the identifier #f2, the RAN can store the context of the device #1 and maintain the corresponding relationship between the RN 16-2 and the identifier #f2. The context of the device #1 includes the RN 16-2 and the identifier #f2.

[0483] S920: RAN sends N2 message #3 to TMF according to RRC message #2. Correspondingly, TMF receives N2 message #3 from RAN.

[0484] N2 message #3 includes the identifier of device #1 and identifier #f2. The information carrying the identifier of device #1 may be NAS information.

[0485] S921: TMF sends N2 message #4 to RAN. Correspondingly, RAN receives N2 message #4 from TMF.

[0486] N2 message #4 includes a service request, an identifier #f1, and an end indication message. The N2 message #4 corresponds to the operation request message, the service request corresponds to the operation instruction, and the end indication message corresponds to the first indication message. For details, please refer to the above related introduction and will not be repeated here.

[0487] It is understandable that S921 can be performed after the random access of device #2 is completed, for example: after the random access of device #2 is completed, during the random access process of device #1, such as after S915 and before S916. The specific setting can be made according to actual conditions without limitation.

[0488] S922: RAN sends RRC message #3 to device #2 according to N2 message #4. Accordingly, device #2 receives RRC message #3 from RAN.

[0489] RRC message #3 includes a service request and RN 16-1.

[0490] S923: Device #2 sends RRC message #4 to the RAN according to RRC message #3. Correspondingly, the RAN receives RRC message #4 from device #2.

[0491] RRC message #4 includes service response #1, which corresponds to the above-mentioned operation result. For details, please refer to the above-mentioned related introduction and will not be repeated here.

[0492] Optionally, RRC message #4 may include identifier #f1.

[0493] S924: RAN sends N2 message #5 to TMF according to RRC message #3. Correspondingly, TMF receives N2 message #5 from RAN.

[0494] The N2 message #5 includes a service response #1 and an identifier #f1.

[0495] S925, RAN and TMF release identifier #f1.

[0496] That is, RAN and TMF delete the context of device #2.

[0497] S926: TMF sends service result #1 to NEF. Correspondingly, NEF receives service result #1 from TMF.

[0498] Service result #1 includes the identifier of AF, the identifier of device #1, and data, where the data is the result of the operation performed by device #1.

[0499] S927, NEF sends service result #1 to AF. Correspondingly, AF receives service result #1 from NEF.

[0500] S928: TMF sends N2 message #6 to RAN. Correspondingly, RAN receives N2 message #6 from TMF.

[0501] N2 message #6 includes a service request, an identifier #f2, and an end indication message. The N2 message #6 corresponds to the operation request message, the service request corresponds to the operation instruction, and the end indication message corresponds to the first indication message. For details, please refer to the above related introduction and will not be repeated here.

[0502] It can be understood that S928 can be performed after device #1 completes random access, for example: it can be performed after device #1 completes random access and before operating device #2, such as after S918 and before S921. The specific settings can be made according to actual conditions and will not be repeated here.

[0503] S929: RAN sends RRC message #5 to device #1 according to N2 message #6. Accordingly, device #1 receives RRC message #5 from RAN.

[0504] RRC message #5 includes a service request and RN16-2.

[0505] S930: Device #1 sends RRC message #6 to the RAN according to RRC message #5. Correspondingly, the RAN receives RRC message #6 from device #1.

[0506] RRC message #6 includes service response #2, which corresponds to the above-mentioned operation result. For details, please refer to the above-mentioned related introduction and will not be repeated here.

[0507] Optionally, RRC message #6 may include identifier #f2.

[0508] S931: RAN sends N2 message #7 to TMF according to RRC message #6. Correspondingly, TMF receives N2 message #7 from RAN.

[0509] The N2 message #7 includes a service response #2 and an identifier #f2.

[0510] S932, RAN and TMF release identifier #f2.

[0511] That is, RAN and TMF delete the context of device #1.

[0512] S933: TMF sends service result #2 to NEF. Correspondingly, NEF receives service result #2 from TMF.

[0513] Service result #2 includes the identifier of AF, the identifier of device #2, and data, which is the result of the operation performed by device #1.

[0514] S934: NEF sends service result #2 to AF. Correspondingly, AF receives service result #2 from NEF.

[0515] It is understood that the above-mentioned S901-S934 can refer to the above-mentioned "S301-S325" and the related description of the embodiment shown in the above-mentioned FIG5, and will not be repeated here. In addition, the above-mentioned messages (such as N2 messages, NAS messages, etc.) can be replaced with other types of messages according to actual circumstances without limitation.

[0516] It can also be understood that when the N2 message #1 includes the task identifier of the operation task, the access network device can also store the task identifier when storing the context of device #1 and device #2, so that the core network device can delete the context of device #1 and device #2 by instructing to delete the context containing the task identifier. For details, please refer to the relevant introduction in the aforementioned scenario 1, which will not be repeated here.

[0517] In addition, a temporary identifier can be generated based on the identifier of the process, that is, in S913, identifier #f1 is generated based on the identifier of process #2. In this case, the information sent by the access network device to device #2 can carry the identifier of process #2, such as carrying the identifier of process #2 in S922; in S919, identifier #f2 is generated based on the identifier of process #1. In this case, the information sent by the access network device to device #1 can carry the identifier of process #1, such as carrying the identifier of process #1 in S929.

[0518] The above description, in conjunction with Figures 6-9, details a communication method applicable to the communication system shown in Figure 4. It is understood that the embodiments of the present application may also be applicable to other communication systems. To facilitate understanding of the embodiments of the present application, the communication system shown in Figure 10 is first used as an example to describe in detail a communication system applicable to the embodiments of the present application. For example, Figure 10 is a second schematic diagram of the architecture of a communication system applicable to the communication method provided in the embodiments of the present application.

[0519] As shown in Figure 10, the communication system can be applied to the above-mentioned 5GS, including: a first terminal device, a reader / writer, an access network device, and a core network element.

[0520] For the first terminal device and access network device, please refer to the relevant introduction in the aforementioned "1.5GS" and will not be repeated here.

[0521] The reader / writer can be a terminal device. In this case, the terminal device can act as a reader / writer. For details, please refer to the relevant introduction in the aforementioned "2.A-IoT" and will not be repeated here.

[0522] The core network network element can be AMF or AIoTMF (TMF). For details, please refer to the relevant introduction in the aforementioned "1.5GS", which will not be repeated here. It can be understood that, as shown in Figure 11, when the core network network element is AIoTMF, a protocol layer can be set between the access network device and AIoTMF, such as the N2 tag management information or AIoT NGAP and other protocols shown in Figure 11, so that the access network device and AIoTMF can interact. It can also be understood that the embodiment of the present application does not limit the name of the protocol layer between the access network device and AIoTMF. In addition, in Figure 11, the various protocol layers (such as RRC layer, PHY layer, etc.) between the first terminal device (terminal device in Figure 11), the reader / writer, the access network device, the AMF, and the AIoTMF can refer to the relevant introduction in the prior art, which will not be repeated here.

[0523] In a communication system, a reader / writer can determine a first identifier that can be used at the access control layer for a first terminal device requiring operation, and send the first identifier to an access network device. This allows the reader / writer and the access network device to indicate the first terminal device at the access control layer via the first identifier, thereby enabling operation on the first terminal device. Furthermore, after receiving the first identifier, the access network device can determine a third identifier that can be used at the third signaling layer based on the first identifier, and send the third identifier to a core network element. This allows the access network device and the core network element to indicate the first terminal device at the third signaling layer via the third identifier, thereby enabling operation on the first terminal device. In this manner, when operation on multiple terminal devices is required, the reader / writer can automatically trigger random access for each of the multiple terminal devices. Specifically, the reader / writer can determine a different identifier for each of the multiple terminal devices requiring random access to distinguish between the different terminal devices. In this case, the core network element can perform operations on terminal devices that have completed random access during the random access process. This eliminates the need to wait until random access and operation on one terminal device are complete before performing random access and operation on the next terminal device, thereby improving the efficiency of operations on multiple terminal devices.

[0524] It can be understood that FIG10 is a simplified schematic diagram for ease of understanding, and the communication system may also include other network devices and / or other terminal devices, which are not shown in FIG10 .

[0525] For ease of understanding, the communication method provided in the embodiment of the present application will be described in detail below with reference to FIG12 .

[0526] For example, Figure 12 illustrates a flow chart of a communication method according to an embodiment of the present application. This method can be applied to the interaction between the first terminal device, the reader / writer, the access network device, and the core network element in the above-mentioned communication system. For ease of understanding, the communication method is described below using the first terminal device as an example.

[0527] S1201: After receiving a first random access request from a first terminal device, the reader / writer determines a first identifier of the first terminal device.

[0528] The first random access request may be used to request random access to the reader / writer. The first random access request may vary in different random access procedures. The first random access request can be understood by referring to the description of "S501" above. For example, the access network device in S501 may be replaced with the reader / writer, and further description is omitted.

[0529] "After the reader receives the first random access request," it can also be understood as the reader completing the random access procedure between the first terminal device and the reader, or after completing the random access procedure between the first terminal device and the reader. "After the reader receives the first random access request," it can also be understood as the reader executing the random access procedure of the first terminal device. For details of the above two situations, please refer to the relevant descriptions in "S501" above. For example, the access network device in S501 can be replaced with the reader for further understanding, and no further explanation is given.

[0530] The first identifier is used to identify the first terminal device at the access control layer. That is, the first identifier can be used to identify the first terminal device between the reader and the access network device, i.e., the reader and the access network device can recognize or determine that the terminal device indicated by the second identifier is the first terminal device. The access control layer is a protocol layer between the reader and the access network device, such as the MAC layer, PHY layer, PDCP layer, RRC layer, or RLC layer. The specific principles of each protocol layer can be referred to in the prior art and will not be further described here.

[0531] The first identifier can be determined based on information sent by the first terminal device during the random access process. For example, the reader can assign the first identifier to the first terminal device based on the information. Alternatively, the reader can determine the information as the first identifier. Specific cases are described below.

[0532] Case 12.1: The reader / writer allocates (or generates) a first identifier according to the information sent by the first terminal device during the random access process.

[0533] In this case, before the reader / writer determines the first identifier of the first terminal device, the above-mentioned communication method may also include: the first terminal device sends a first random access request, and accordingly, the reader / writer receives the first random access request, and the first random access request includes the second identifier; the reader / writer determines the first identifier of the first terminal device, which may specifically include: the reader / writer allocates the first identifier to the first terminal device based on the second identifier.

[0534] The second identifier is used to indicate the first terminal device at the second signaling layer. That is, the second identifier can identify the first terminal device between the first terminal device and the reader / writer, that is, the reader / writer can identify or determine that the terminal device indicated by the second identifier is the first terminal device. The second identifier can be a temporary identifier (i.e., a temporary identifier), such as RN16, or it can be other information that can characterize the first terminal device, such as the IP address / port number information, frequency band / frequency information, temporary name information, geographic location information, or interface information of the first terminal. It can be understood that the second identifier can be generated by the first terminal device itself, can be configured by the network side, or can be predefined by the protocol. It can be flexibly set according to actual conditions without restriction.

[0535] The second signaling layer can be a protocol layer between the terminal device (such as the first terminal device) and the reader / writer, such as an access (AS) layer or an AIoT AS layer.

[0536] It is understood that the second identifier is different from the first identifier, and the first identifier and the second identifier have a corresponding relationship. After the reader / writer assigns the first identifier to the first terminal device based on the second identifier, the reader / writer can save (or maintain) the corresponding relationship between the second identifier and the first identifier, so that the reader / writer can subsequently determine the second identifier based on the first identifier and send information to the first terminal device based on the second identifier.

[0537] It can also be understood that, in addition to being carried in the first random access request, the second identifier can also be carried in other messages sent by the first terminal device during the random access process. For example, after the reader receives the first random access request sent by the first terminal device, it sends a confirmation message to the first terminal device; after receiving the confirmation message, the first terminal device sends information indicating the first terminal device (such as the identifier of the first terminal device) and the second identifier to the reader. The operation of carrying the second identifier in the other message is similar to the operation of carrying the second identifier in the first random access request, which can be understood by reference and will not be repeated here.

[0538] Case 12.2: The reader / writer determines the information sent by the first terminal device during the random access process as the first identifier.

[0539] In this case, before the reader / writer determines the first identifier of the first terminal device, the above-mentioned communication method may also include: the first terminal device sends a first random access request, and accordingly, the reader / writer receives the first random access request, and the first random access request includes the second identifier; the reader / writer determines the first identifier of the first terminal device, which may specifically include: the reader / writer determines that the second identifier is the first identifier.

[0540] The second identifier is used to indicate the first terminal device in the second signaling layer. The second identifier and the second signaling layer can refer to the relevant introduction in the aforementioned "Case 12.1", which will not be repeated here.

[0541] In case 12.2, the first identifier can reuse the second identifier, i.e., the first identifier and the second identifier are the same. In other words, after receiving the second identifier, the reader can reuse the second identifier in the second signaling layer. For example, the reader can assign the value of the second identifier to the first identifier. In this case, the second identifier and the first identifier have the same value.

[0542] S1202: The reader sends a first identifier and first information to the access network device. Correspondingly, the access network device receives the first identifier and first information from the reader.

[0543] The first information is used to indicate the first terminal device at the first signaling layer. The first information may be an identifier of the terminal device, which may be a third-party identifier, such as the EPC of the first terminal device, or identifier information assigned to the terminal device by the operator, or a combination of a third-party identifier and identifier information assigned to the terminal device by the operator. In this case, the first information may be a partial identifier (part of the ID) or a full identifier (full ID) of the terminal device, which may be flexibly set according to actual circumstances and is not limited. The first information may also be other information that can indicate or identify the terminal device, such as a temporary identifier assigned to the first terminal device by the core network (such as an SAE-temporary mobile subscriber identity (S-TMSI) or a globally unique temporary UE identity (GUTI), etc.), or mask information, etc. The first information may be sent by the first terminal device to the reader / writer, for example, by the first terminal device to the reader / writer during a random access process. For details, please refer to the relevant description in the aforementioned "S502", for example, replace the identifier of the first terminal device and the access network device in S502 with the first information and the reader / writer, respectively, and will not be repeated here.

[0544] It can be understood that the reader cannot determine the first information, that is, the reader cannot decode the first information. For details, please refer to the relevant introduction in the aforementioned "S502", such as replacing the identifier of the first terminal device and the access network device in S502 with the first information and the reader respectively for understanding, and no further details will be given.

[0545] In an embodiment of the present application, after determining the first identifier, the reader can send the first identifier and the first information to the access network device, so that the access network device sends the first information to the core network network element. The message used to send the first identifier and the first information can reuse the message in the prior art, such as the access layer message (such as the RRC message), or it can be a newly defined message such as a message of another interface. It can be set according to the actual situation without limitation. It can be understood that the first information can be carried on the AIoT NAS message (or information), and the AIoT NAS message (or information) can be located in the message used to send the first identifier and the identifier of the first terminal device.

[0546] S1203: After receiving the first identifier and the first information from the reader, the access network device determines a third identifier.

[0547] The third identifier is used to indicate the first terminal device in the third signaling layer. That is, the third identifier can be used to identify the first terminal device between the access network device and the core network network element, that is, the access network device and the core network network element can identify or determine that the terminal device indicated by the third identifier is the first terminal device. The third signaling layer can be a protocol layer between the access network device and the core network network element. It can be understood that when the core network network element is a different network element, the third signaling layer is different. For example, when the core network network element is an AMF, the third signaling layer can be an NGAP layer. Alternatively, when the core network network element is an AIoTMF, the third signaling layer is a protocol layer set between the access network device and the AIoTMF, such as the AIoT NGAP and other protocols in Figure 11.

[0548] The third identifier can be determined based on the first identifier. For example, the access network device can assign the third identifier to the first terminal device based on the first identifier. Another example is that the access network device can determine the first identifier as the third identifier.

[0549] Case 12.3: The access network device allocates (or generates) a third identifier for the first terminal device based on the first identifier.

[0550] In this case, after the access network receives the first identifier and the first information, the access network device determines the third identifier, which may specifically include: the access network device allocates the third identifier to the first terminal device according to the first identifier.

[0551] It is understood that the first identifier and the third identifier are different, and the first identifier and the third identifier have a corresponding relationship. After the access network device assigns the third identifier to the first terminal device based on the first identifier, the access network device can save (or maintain) the corresponding relationship between the first identifier and the third identifier, so that the access network device can subsequently determine the first identifier based on the third identifier, thereby sending relevant information of the first terminal device to the reader / writer based on the first identifier.

[0552] Case 12.4: The access network device determines the first identifier as the third identifier.

[0553] In this case, after the access network receives the first identifier and the first information, the access network device determining the third identifier may specifically include: the access network device determining the first identifier as the third identifier.

[0554] In scenario 12.4, the third identifier can reuse the first identifier, meaning it is identical to the first identifier. In other words, after receiving the first identifier, the access network device can reuse it at the third signaling layer. For example, the access network device can assign the value of the first identifier to the third identifier, in which case the third identifier will have the same value as the first identifier. This eliminates the need for the access network device to generate the third identifier, thereby reducing its processing overhead.

[0555] S1204: The access network device sends the third identifier and the first information to the core network element. Correspondingly, the core network element receives the third identifier and the first information from the access network device.

[0556] After determining the third identifier, the access network device may send the third identifier and the first information to the core network element.

[0557] It is understood that the message used to send the first identifier and the first information can reuse messages in the prior art, such as the N2 message, or can be a newly defined message, such as a message of another interface. It can be flexibly set according to actual conditions without limitation. It is understood that the first information can be carried on an AIoT NAS message (or information), and the AIoT NAS message (or information) can be located in the message used to send the third identifier and the first information.

[0558] It can also be understood that after receiving the first information, the core network element can save or maintain the correspondence between the first information and the third identifier. In addition, the core network element can also associate the first identifier, the identifier of the first terminal device with the task identifier corresponding to the operation task (described below), that is, the first identifier, the identifier of the first terminal device and the task identifier have a correspondence. At this time, the core network device saves or maintains the correspondence. For details, please refer to the relevant introduction in the aforementioned "S502", such as replacing the identifier of the first terminal device and the access network device in S502 with the first information and the reader / writer respectively for understanding, and no further details will be given.

[0559] S1205, the core network element determines the operation of the first terminal device based on the first information (recorded as operation #1).

[0560] Operation #1 can refer to the relevant introduction in the aforementioned "S503" and will not be repeated here.

[0561] The core network element may determine operation #1 from the stored operations of the multiple terminal devices based on the first information. The stored operations of the multiple terminal devices may be operations sent by a service requester (e.g., AF) to the core network device. For details, please refer to the relevant description in the aforementioned "S503" and will not be repeated here.

[0562] S1206: The core network element sends a second operation request message to the access network device. Correspondingly, the access network device receives the second operation request message from the core network element.

[0563] The second operation request message can be used to request the terminal device indicated by the third identifier to perform the operation indicated by the operation instruction (i.e., the above-mentioned operation #1). The second operation request message can include at least one of the following: the third identifier, or the operation instruction. The operation instruction can be used to instruct the execution of operation #1. The operation instruction can be carried in a NAS message (or information). It is understood that the core network element can determine the above-mentioned operation #1 based on the first information, that is, the second operation request message is determined based on the first information.

[0564] S1207: The access network device obtains the first identifier according to the third identifier.

[0565] After receiving the second operation request message, the access network device may obtain the first identifier based on the third identifier in the second operation request message. Exemplarily, when the access network device stores a correspondence between the third identifier and the first identifier, after receiving the second operation request message, the access network device may index the first identifier based on the third identifier in the second operation request message.

[0566] It is understood that after receiving the second operation request message, the access network device needs to send the operation instruction in the second operation request message to the reader / writer, so that the reader / writer sends the operation instruction to the terminal device indicated by the third identifier (i.e., the first terminal device), so that the terminal device performs the operation indicated by the operation instruction. In this case, the access network device needs to determine the identifier corresponding to the third identifier at the access control layer, that is, the access network device needs to determine the identifier corresponding to the access control layer based on the third identifier.

[0567] S1208: The access network device sends a first operation request message to the reader / writer. Correspondingly, the reader / writer receives the first operation request message from the access network device.

[0568] The first operation request message may be used to request the terminal device indicated by the first identifier to perform the operation indicated by the operation instruction (ie, the above-mentioned operation #1). The first operation request message may include at least one of the following: the first identifier, or the operation instruction.

[0569] S1209: The reader obtains a second identifier according to the first identifier.

[0570] After receiving the first operation request message, the reader / writer can obtain the second identifier based on the first identifier in the first operation request message. For example, when the reader / writer stores a correspondence between the first identifier and the second identifier, after receiving the first operation request message, the reader / writer can index the second identifier based on the first identifier in the first operation request message.

[0571] It is understood that after receiving the first operation request message, the reader / writer needs to send the operation instruction in the first operation request message to the terminal device indicated by the first identifier (i.e., the first terminal device) so that the terminal device performs the operation indicated by the operation instruction. In this case, the reader / writer needs to determine the identifier corresponding to the first identifier at the second signaling layer and send the operation instruction to the first terminal device based on the identifier.

[0572] S1210: The reader / writer sends an operation instruction and a second identifier to the first terminal device. Correspondingly, the first terminal device receives the operation instruction and the second identifier from the reader / writer.

[0573] It can be understood that the operation instruction and the second identifier can be two parallel pieces of information, or the second identifier can be carried in the operation instruction. The specific form can be flexibly set according to actual conditions and is not limited.

[0574] The reader / writer sends the second identifier to the first terminal device. Upon receiving the operation instruction, the terminal device determines whether the operation instruction is intended for it based on the second identifier carried in the operation instruction, thereby ensuring that the operation instruction is delivered to the first terminal device. Furthermore, the reader / writer sends the operation instruction to the first terminal device, causing the first terminal device to perform the operation indicated by the operation instruction, thereby completing Operation #1 described above. In other words, after the first terminal device receives the operation instruction and the second identifier, it performs the operation indicated by the operation instruction. For details, please refer to the aforementioned "S506" and will not be repeated here.

[0575] It is understood that the reader / writer may not send the second identifier to the first terminal device, but instead send an operation instruction to the first terminal device based on the second identifier. For example, a frequency corresponding to the second identifier may be preconfigured or predefined by a protocol. After obtaining the second identifier based on the first identifier, the reader / writer may send the operation instruction at the frequency corresponding to the second identifier. Accordingly, the first terminal device may receive the operation instruction at this frequency.

[0576] In summary, in an embodiment of the present application, the reader / writer can determine a first identifier that can be used for the access control layer for a first terminal device that needs to be operated, so that the reader / writer and the access network device can indicate the first terminal device through the first identifier to achieve interaction of relevant information of the first terminal device. Moreover, the access device can determine a third identifier that can be used for third signaling for the first terminal device based on the first identifier, so that the access network device and the core network element can indicate the first terminal device through the third identifier to achieve interaction of relevant information of the first terminal device. In this way, when it is necessary to operate the terminal device, the reader / writer can automatically trigger random access of each terminal device among multiple terminal devices, that is, the reader / writer can determine a different identifier for each terminal device among the multiple terminal devices that initiate random access to distinguish different terminal devices. At this time, the core network element can operate the terminal device that has completed random access during the process of random access of the terminal device, that is, there is no need to complete random access and operation of one terminal device before performing random access and operation of the next terminal device, thereby improving the efficiency of operations on multiple terminal devices.

[0577] Optionally, in combination with the above embodiments, after the first terminal device receives the operation instruction and the second identifier, the above communication method may further include: the first terminal device sends the operation result to the reader / writer, and accordingly, the reader / writer receives the operation result from the first terminal device, and the operation result is the result of the first terminal device performing the operation indicated by the operation instruction; the reader / writer sends the operation result and the first identifier to the access network device, and accordingly, the access network device receives the operation result from the reader / writer; the access network device sends the operation result and the third identifier to the core network network element, and accordingly, the core network network element receives the operation result and the third identifier from the access network device.

[0578] It is understood that the core network element can determine that the operation result is the result of the operation of the first terminal device based on the third identifier and the operation result. After determining the operation result of the first terminal device, the core network element sends the operation result to the service requester (such as AF), so that the service requester adjusts the service based on the operation result. When the operation instruction is different, the corresponding result is also different. For details, please refer to the relevant description of the embodiment shown in Figure 5 above, and will not be repeated here.

[0579] Optionally, in conjunction with the above embodiment, with respect to scenario 12.1, after the reader / writer assigns the first identifier to the first terminal device based on the second identifier, the communication method may further include: the reader / writer storing the correspondence between the first identifier and the second identifier. This facilitates the reader / writer transmitting relevant information about the first terminal device between the first terminal device and the access network device. For example, upon subsequently receiving a message from the access network device containing the first identifier, the reader / writer may determine the second identifier based on the correspondence between the first identifier and the second identifier, and transmit information corresponding to the message to the first terminal device based on the second identifier.

[0580] Optionally, in combination with the above embodiment, with respect to the above scenario 12.2, after the access network device assigns the third identifier to the first terminal device based on the first identifier, the above communication method may further include: the access network device storing the correspondence between the first identifier and the third identifier. This facilitates the access network device to transmit relevant information about the first terminal device between the core network element and the reader / writer. For example, upon subsequently receiving a message from the core network element containing the third identifier, the access network device may determine the first identifier based on the correspondence between the first identifier and the third identifier, and transmit information corresponding to the message to the reader / writer based on the first identifier.

[0581] Optionally, in combination with the above embodiment, after the core network network element receives the third identifier and the first information from the access network device, the above communication method may also include: the core network network element saves the correspondence between the identifier of the reader and the third identifier, and the reader is used to serve the first terminal device.

[0582] The reader identifier can be the reader's own identifier. For example, when the reader is a terminal device, the reader identifier can be the terminal device identifier, such as a subscription permanent identifier (SUPI), a subscriber concealed identifier (SUCI), a GUTI, or a TMSI (S-TMSI, 5G-S-TMSI), etc. It can also be the reader's identifier (reader ID), which can be allocated by the operator or a third party without restriction.

[0583] The reader / writer identifier can also be an identifier used to indicate the reader / writer between the core network element (AIoTMF) and the access network device, such as an NGAP ID. Exemplarily, the signaling layer between the access network device and the AIoTMF can be an AIoT NGAP layer, which can be used to transmit the signaling of the reader / writer between the access network device and the AIoTMF. In this case, for RAN or AIoTMF, after receiving the RAN AIoTMF NGAP pair or Reader (UE) AIoTMF NGAP ID, it can identify the specific reader / writer, that is, the reader / writer corresponding to the identifier, based on the received RAN AIoTMF NGAP pair or Reader (UE) AIoTMF NGAP ID, and perform signaling forwarding based on the identified reader / writer. It can be understood that the combination of Reader (UE) RAN AIoT NGAP ID and Reader (UE) AIoTMF NGAP ID identifies the information of a Reader (UE) on an AIoT NGAP, and the combination can be called a RAN AIoTMF NGAP pair.

[0584] In an embodiment of the present application, the core network element stores the correspondence between the reader / writer identifier and the third identifier, which enables the core network element to determine or identify the corresponding reader / writer based on the reader / writer identifier, that is, the reader / writer used to perform the operation task.

[0585] Optionally, in combination with the above embodiment, for the above situation 12.1, after the reader / writer assigns the first identifier to the first terminal device based on the second identifier, the above communication method may also include: the reader / writer saves the first context of the first terminal device, and the first context includes the first identifier and / or the second identifier.

[0586] The first context can be understood as all information related to the first terminal device, or it can be understood as partial information related to the first terminal device, such as the correspondence between the first identifier and the second identifier. It is understood that in the first context, the first identifier and the second identifier have a correspondence, that is, the first context can include the correspondence between the first identifier and the second identifier. In this case, the first context can include at least one of the following: the first identifier, the second identifier, or the correspondence between the first identifier and the second identifier. This facilitates the reader / writer to determine the second identifier based on the first context, such as the first identifier and the correspondence between the first identifier and the second identifier, after receiving a message carrying the first identifier, and thus send information to the first terminal device based on the second identifier.

[0587] Furthermore, the first operation request message also includes first indication information, and the first indication information is used to instruct the reader to delete (or release) the first context after completing the operation on the first terminal device.

[0588] After receiving the first operation request message, the reader / writer may delete (or release) the first context after completing the operation on the first terminal device. The time point at which the reader / writer completes the operation on the first terminal device may vary in different situations. For details, please refer to the relevant description of the embodiment shown in FIG. 5 , replacing the access network device in FIG. 5 with the reader / writer for further understanding. This description will not be repeated here.

[0589] In an embodiment of the present application, the reader / writer deletes (or releases) the first context after completing the operation on the first terminal device according to the first indication information, so that the reader / writer can release storage space in time, thereby avoiding redundancy and improving storage efficiency.

[0590] It is understood that, in addition to deleting the first context according to the first instruction information, the reader / writer may also periodically delete the first context. Alternatively, the reader / writer may delete the first context in response to instructions from another device. Alternatively, the reader / writer may independently determine whether the operation on the first terminal device is uncompleted, and delete the first context upon determining that the operation on the first terminal device is complete.

[0591] Furthermore, when the reader / writer saves the first context, the first context can be associated with the operation task. In this case, when the reader / writer saves the first context, it can also save the task identifier (task ID) corresponding to the operation task. The task identifier can refer to the relevant introduction in the embodiment shown in Figure 5 above, and will not be repeated here. It can be understood that the task identifier, the first identifier, and the second identifier have a corresponding relationship, such as the task identifier has a corresponding relationship with the first identifier, and the first identifier has a corresponding relationship with the second identifier, and the reader / writer can maintain the corresponding relationship. In this case, the first context can include at least one of the following: the first identifier, the second identifier, the task identifier, the corresponding relationship between the first identifier and the second identifier, or the corresponding relationship between the first identifier and the task identifier.

[0592] Exemplarily, the first context also includes a task identifier. Before the reader / writer receives the first random access request, the above-mentioned communication method may also include: the access network device sends a first operation task request message to the reader / writer, and accordingly, the reader / writer device receives the first operation task request message from the access network device, and the first operation task request message includes a task identifier; the access network device broadcasts a second random access request based on the first operation task request message.

[0593] Among them, the first operation task request message is used to request the reader to perform (or initiate) random access to multiple terminal devices. And the first operation task request message can also be used to instruct the reader to save the context of the terminal device that needs to be operated, such as the first context mentioned above. The task identifier can be the identifier of the task corresponding to the operation task request message. For details, please refer to the relevant introduction in the embodiment shown in Figure 5 above, and will not be repeated here. It can be understood that the task identifier can be sent by the core network network element to the access network device (described below). In addition, the above-mentioned first operation task request message is similar to the operation task request message in the embodiment shown in Figure 5 above, and they can be understood by reference to each other, and will not be repeated here.

[0594] In this embodiment of the present application, the access network device sends a first operation task request message carrying a task identifier to the reader / writer. This allows the core network element or access network device to manage the operation task indicated by the task identifier using the task identifier. For example, after the operation task is completed, the reader / writer is instructed to delete the context containing the task identifier, thereby deleting the entire context of the terminal device corresponding to the completed operation task. In this way, the core network element or access network device can manage the reader / writer at the task granularity.

[0595] Furthermore, after the reader / writer saves the first context of the first terminal device, the above-mentioned communication method may also include: the access network device sends a task identifier and a third indication information to the reader / writer, and accordingly, the reader / writer receives the task identifier and the third indication information from the access network device, and the third indication information is used to instruct the reader / writer to delete the context containing the task identifier; the reader / writer deletes the first context according to the task identifier and the third indication information.

[0596] Upon receiving a deletion instruction from a core network device or other device, the access network device can send a task identifier and third instruction information to the reader / writer. This deletion instruction information can be used to instruct the access network device and / or reader / writer to delete the context containing the task identifier. Alternatively, the access network device can send the task identifier and third instruction information to the reader / writer after determining that the operation task indicated by the task identifier has been completed, such as after receiving the operation result corresponding to the task identifier. This facilitates the reader / writer to promptly delete or release the first context, thereby avoiding redundancy and improving storage efficiency.

[0597] In addition, the reader / writer may also periodically delete the first context. For details, please refer to the above related introduction, which will not be repeated here.

[0598] Optionally, in combination with the above embodiment, for situation 12.2, before the reader receives the first random access request, the above communication method may also include: the access network device sends a first operation task request message to the reader, and accordingly, the reader device receives the first operation task request message from the access network device, and the first operation task request message includes a task identifier; the reader broadcasts a second random access request based on the operation task request message; after the reader determines that the second identifier is the first identifier, the reader saves the first context of the first terminal device, and the first context includes the task identifier and the first identifier.

[0599] The first operation request message and the task identifier can be referred to the aforementioned related introduction and will not be repeated here.

[0600] That is, after the reader / writer determines that the second identifier is the first identifier, the reader / writer can associate the first identifier with the task identifier (or task). In this case, the task identifier and the first identifier have a corresponding relationship, and the first identifier and the second identifier have a corresponding relationship, and the reader / writer can maintain these two sets of corresponding relationships. The first context can include at least one of the following: the first identifier, the second identifier, the task identifier, the corresponding relationship between the task identifier and the first identifier, or the corresponding relationship between the first identifier and the second identifier. For example, the first context includes the first identifier and the task identifier, or the first context includes the corresponding relationship between the first identifier and the task identifier.

[0601] In an embodiment of the present application, the reader / writer stores a first context including a task identifier and a first identifier. This facilitates a core network element or access network device to manage the operation task indicated by the task identifier using the task identifier. For example, after the operation task is completed, the reader / writer can be instructed to delete the context including the task identifier, thereby deleting the entire context of the terminal device corresponding to the completed operation task. In this way, the core network element or access network device can manage the reader / writer at the task granularity.

[0602] Furthermore, after the reader / writer saves the first context of the first terminal device, the above-mentioned communication method may also include: the access network device sends a task identifier and third indication information to the reader / writer, and accordingly, the reader / writer receives the task identifier and third indication information from the access network device, and the third indication information is used to instruct the reader / writer to delete the context containing the task identifier; the reader / writer deletes the first context according to the task identifier and the third indication information.

[0603] It is understood that the specific implementation of the reader deleting the first context according to the third indication information can be understood by referring to the aforementioned related introduction, which will not be repeated here. In addition, in the embodiment of the present application, the reader can also periodically delete the first context, which can be specifically referred to the aforementioned related introduction, which will not be repeated here.

[0604] Optionally, in combination with the above implementation, for situation 12.3, after the access network device assigns a third identifier to the first terminal device based on the first identifier, the above communication method may also include: the access network device saves the second context of the first terminal device, and the second context includes the first identifier and the third identifier.

[0605] The second context can be understood as all information related to the first terminal device, or it can be understood as partial information related to the first terminal device, such as the correspondence between the first identifier and the third identifier. It can be understood that in the second context, the first identifier and the third identifier have a correspondence, that is, the second context can include the correspondence between the first identifier and the third identifier. In this case, the second context can include at least one of the following: the first identifier, the third identifier, or the correspondence between the first identifier and the third identifier. This facilitates the reader / writer to determine the first identifier based on the second context, such as the third identifier and the correspondence between the first identifier and the third identifier, after receiving a message carrying the third identifier. Based on the first identifier, the reader / writer can then send relevant information about the first terminal device to the reader / writer.

[0606] Furthermore, the second operation request message also includes second indication information, and the second indication information is used to instruct the access network device to delete the context of the first terminal device after completing the operation on the first terminal device.

[0607] After receiving the second operation request message, the access network device may delete (or release) the second context after completing the operation on the first terminal device. In different situations, the time point at which the access network device completes the operation on the first terminal device varies. For details, please refer to the relevant description of the embodiment shown in Figure 5 above, and will not be repeated here.

[0608] In an embodiment of the present application, the access network device deletes (or releases) the second context after completing the operation on the first terminal device based on the second indication information, so that the reader / writer can release storage space in time, thereby avoiding redundancy and improving storage efficiency.

[0609] It can be understood that in addition to deleting the second context according to the second indication information, the access network device can also periodically delete the context of the first terminal device; or, the access network device can also delete the second context according to the indication of other devices other than the core network network element; or, the access network device can also determine on its own whether the operation for the first terminal device is completed, and delete the second context after determining that the operation for the first terminal device is completed. For details, please refer to the relevant introduction in the aforementioned Example 5, which will not be repeated here.

[0610] Furthermore, when the access network device saves the second context, it can also associate the second context with the operation task. In this case, when the access network device saves the second context, it can also save the task identifier of the operation task. The task identifier can refer to the aforementioned related introduction and will not be repeated here. It can be understood that the task identifier, the first identifier, and the third identifier have a corresponding relationship, that is, the task identifier has a corresponding relationship with the first identifier, and the first identifier has a corresponding relationship with the third identifier, and the access network device can maintain these corresponding relationships. In this case, the second context can include at least one of the following: the first identifier, the third identifier, the task identifier, the corresponding relationship between the first identifier and the third identifier, or the corresponding relationship between the first identifier and the task identifier.

[0611] Exemplarily, the second context also includes a task identifier. Before the access network device receives the first identifier and the first information, the above-mentioned communication method may also include: the core network network element sends a second operation task request message to the access network device, and accordingly, the access network device receives the second operation task request message from the core network network element, and the second operation task request message includes the task identifier; the access network device sends a first operation task request message to the reader / writer based on the second task request message, and the first operation task request message includes the task identifier.

[0612] Among them, the first operation task request message and task identifier can refer to the aforementioned related introduction, which will not be repeated here. It can be understood that the core network network element can obtain the task identifier from the service requester. For details, please refer to the relevant introduction in the embodiment shown in Figure 5 above, which will not be repeated here. The second operation task request message is used to request operations on multiple terminal devices, such as reading, writing, and other operations on the terminal. The second operation task request message can also be used to instruct the access network device to save the context of the terminal device that needs to be operated, such as the second context mentioned above.

[0613] In this embodiment of the present application, a core network element sends a second operation task request message carrying a task identifier to an access network device. This allows the core network element to manage the operation task indicated by the task identifier using the task identifier. For example, after the operation task is completed, the core network element instructs the access network device to delete the context containing the task identifier, thereby deleting the entire context of the terminal device corresponding to the completed operation task. In this way, the core network element can manage access network devices at the task granularity.

[0614] Furthermore, after the access network device saves the second context of the first terminal device, the above-mentioned communication method may also include: after the core network network element determines that the operation task indicated by the task identifier is completed, the core network network element sends the task identifier and fourth indication information to the access network device, and accordingly, the access network device receives the task identifier and fourth indication information from the core network network element, and the fourth indication information is used to instruct the access network device to delete the context containing the task identifier; the access network device deletes the second context according to the task identifier and the fourth indication information.

[0615] The core network network element can send a fourth indication message to the access network device when determining that the operation task is completed. There are many ways for the core network network element to determine that the operation is completed. For example, the core network network element can determine that the operation task is completed when determining the operation results corresponding to each terminal device in the received operation task. For example, the core network device can also determine that the operation task is completed after sending an operation instruction to each terminal device in the operation task. For details, please refer to the relevant introduction in the embodiment shown in Figure 5 above for understanding. For example, replace the core network device in the embodiment shown in Figure 5 with the core network network element for understanding, and no further details will be given here. In this way, after the operation task is completed, the core network network element can instruct the access network device to delete the contexts of multiple terminal devices corresponding to the operation task, thereby realizing the management of the entire task.

[0616] It can be understood that the core network network element can also send a task identifier and a fourth indication information to the access network device when receiving the deletion indication information from the service requester. For details, please refer to the relevant introduction in the embodiment shown in Figure 5 above for understanding, such as replacing the core network device in the embodiment shown in Figure 5 with the core network network element for understanding, and no further details will be given here.

[0617] It is also understood that the core network element can delete (or release) the context of the first terminal device after determining that the operation task indicated by the task identifier is completed. The context of the first terminal device can include at least one of the following: the third identifier, the first information, the task identifier, the identifier of the access network device, or the identifier of the reader / writer. For details, please refer to the relevant introduction above and will not be repeated here. In this way, the core network element can release the context of the first terminal device in a timely manner, thereby avoiding redundancy and improving storage efficiency.

[0618] In addition, the access network device may also periodically delete the second context. For details, please refer to the above related introduction, which will not be repeated here.

[0619] Optionally, for situation 12.4, before the access network device receives the first identifier and the first information, the above-mentioned communication method may also include: the core network network element sends a second operation task request message to the access network device, and accordingly, the access network device receives the second operation task request message from the core network element, and the second operation task request message includes the task identifier; the access network device sends a first operation task request message to the reader / writer based on the second task request message, and accordingly, the reader / writer receives the first operation task request message, and the first operation task request message includes the task identifier; after the access network device determines that the first identifier is the third identifier, the access network device saves the second context of the first terminal device, and the second context includes the task identifier and the third identifier.

[0620] The second operation task request message, the first operation task request message and the task identifier can be referred to the aforementioned related introduction and will not be repeated here.

[0621] That is, after the access network device determines that the first identifier is the third identifier, the access network device can associate the third identifier with the task identifier (or task). In this case, the task identifier and the third identifier have a corresponding relationship, and the third identifier and the first identifier have a corresponding relationship, and the access network device can maintain these two sets of corresponding relationships. And the second context can include at least one of the following: the first identifier, the third identifier, the task identifier, the corresponding relationship between the task identifier and the third identifier, or the corresponding relationship between the third identifier and the first identifier. For example, the second context includes the task identifier and the third identifier, or the second context includes the corresponding relationship between the task identifier and the third identifier.

[0622] In the embodiment of the present application, the access network device stores a second context including a task identifier and a third identifier. This facilitates the core network element to manage the operation task indicated by the task identifier using the task identifier. For example, after the operation task is completed, the access network device is instructed to delete the context including the task identifier, thereby deleting the entire context of the terminal device corresponding to the completed operation task. In this way, the core network element can manage the access network device at the task granularity.

[0623] Furthermore, after the access network device saves the second context of the first terminal device, the above-mentioned communication method may also include: after the core network network element determines that the operation task indicated by the task identifier is completed, the core network network element sends the task identifier and fourth indication information to the access network device, and accordingly, the access network device receives the task identifier and fourth indication information from the core network network element, and the fourth indication information is used to instruct the access network device to delete the context containing the task identifier; the access network device deletes the second context according to the task identifier and the fourth indication information.

[0624] It is understood that the specific implementation of the access network device deleting the second context according to the fourth indication information can be understood with reference to the aforementioned related introduction, which will not be repeated here. In addition, in the embodiment of the present application, the access network device can also periodically delete the second context, which can be specifically referred to the aforementioned related introduction, which will not be repeated here.

[0625] It should be understood that in the embodiments of the present application, context is merely a form of data storage, and the embodiments of the present application do not limit the specific storage format of the correspondence between the above-mentioned identifiers and the task identifiers, or the specific storage format of the above-mentioned identifiers and the task identifiers. Furthermore, the NAS messages (or information) in the embodiments of the present application may be AIoT NAS messages (or information).

[0626] In addition, in the embodiments of the present application, the names of each message, each instruction, each signaling layer, each protocol layer, and each identifier are merely examples of expressions. Each message, each instruction, each signaling layer, each protocol layer, and each identifier may be replaced with any possible expression, and the embodiments of the present application do not limit this. Furthermore, the instructions in the embodiments of the present application may also be replaced with information elements, information, or messages, and the specific settings can be made according to actual circumstances without limitation.

[0627] The above is a general introduction to the communication method provided by the embodiment of the present application in combination with the method embodiment. For ease of understanding, the above method is introduced below with four specific scenarios.

[0628] Scenario 1:

[0629] Figure 13 is a flow chart of the communication method provided in an embodiment of the present application. This method is applicable to the communication system shown in Figure 10, and mainly involves the interaction between device #1 (the above-mentioned first terminal device), device #2, reader / writer, RAN (the above-mentioned access network device), AIoTMF (the above-mentioned core network element), UDM, NEF, and AF. In scenario 1, AF needs to operate on device #1 and device #2. The reader / writer allocates a temporary identifier to the device according to the identifier in the random access request sent by the device (device #1 or device #2), and RAN allocates a new temporary identifier to the device according to the identifier, thereby completing the operation of the device by temporarily identifying the uplink and downlink signaling.

[0630] S1301: AF sends an environmental energy acquisition IoT service request #1 to NEF. Correspondingly, NEF receives the environmental energy acquisition IoT service request #1 from AF.

[0631] AF is the service requester, and AF can also be replaced by AS. The specific setting can be made according to actual conditions without restriction.

[0632] The ambient energy acquisition IoT service request #1 includes at least one of the following: the identifier of the service requester (such as the identifier of the AF, the IP address / port number of the AF), the reader target set (target set ID or Reader ID(s)), the device list, the geographic location information (such as coordinate values, longitude and latitude, or tracking area information, etc.), or the instruction parameter. The reader target set is used to indicate one or more readers. The device list is used to indicate the devices that need to be operated, and the device list includes the identifier of device #1 and the identifier of device #2. The geographic location information is used to indicate the geographic location of the UE requesting the operation. The instruction parameter includes relevant parameters of the operation that the device needs to perform, such as a write operation or a read operation.

[0633] S1302, NEF performs AIoTMF selection operation.

[0634] That is, the NEF selects an AIoTMF to perform the operation from at least one AIoTMF. Exemplarily, the NEF may select an AIoTMF to perform the operation based on the aforementioned geographic location information, the identifier of the service requester, and the reader / writer target set.

[0635] S1303: NEF sends an environmental energy acquisition IoT service request #2 to AIoTMF. Correspondingly, AIoTMF receives the environmental energy acquisition IoT service request #2 from NEF.

[0636] Environmental energy acquisition IoT service request #2 includes at least one of the following: the identifier of the service requester (such as the identifier of AF, the IP address / port number of AF), the reader target set (target set ID or Reader ID(s)), the geographic location information (such as coordinate values, longitude and latitude, or tracking area information, etc.), or instruction parameters. The parameters can be referred to the relevant introduction in the aforementioned "S1301" and will not be repeated here.

[0637] S1304, AIoTMF authorizes the service request and constructs a mask.

[0638] That is, AIoTMF can authorize this service request and determine the mask for subsequent use.

[0639] The above authorization request for this service operation can be understood as: AIoTMF determines whether the business requester requesting the operation has the authority to operate the device list, and / or whether the parameters provided by the business requester are consistent with the contract information of the business requester and / or the contract information of one or more devices in the device list requested for operation.

[0640] The above determination of the mask for subsequent use can be understood as follows: AIoTMF determines the mask for subsequent use based on one or more of the following: the identifier of the service requester, the identifier of the user of the device requesting the operation, the identifier of the home network of the device requesting the operation, and the identifier of the device requesting the operation. This mask is used to randomly access the reader during the paging operation initiated by the reader.

[0641] Optionally, AIoTMF performs reader / writer selection operations.

[0642] If the ambient energy acquisition IoT service request #2 contains the information of the reader target set, AIoTMF can select the reader to perform this task based on the reader target set.

[0643] For example, if the AIoTMF stores the reader information corresponding to the reader target set, the AIoTMF can select the reader to perform this task based on the stored reader information corresponding to the reader target set. Alternatively, the AIoTMF can obtain the reader information corresponding to the reader target set from the UDM / UDR and select the reader to perform this task based on the obtained reader information corresponding to the reader target set. Alternatively, if the reader target set is Reader ID(s), the AIoTMF can directly determine the reader based on the reader target set.

[0644] If the IoT service request #2 does not contain information about the reader target set, AIoTMF can determine the reader to perform this task based on the geographic location information of the requested operation, such as AIoTMF determines the reader to perform this task based on the location information and geographic location information of the reader.

[0645] S1305: AIoTMF sends message #1 to RAN. Correspondingly, RAN receives message #1 from AIoTMF.

[0646] Message #1 includes at least one of the following: a task identifier, a mask, or operation instruction #11. The task identifier identifies the operation corresponding to operation request #2. For details, refer to the description of the embodiment shown in Figure 12 above and will not be repeated here. Operation instruction #11 is used to subsequently trigger the reader to initiate a paging operation.

[0647] It is understood that if the AIoTMF does not select a reader in S1305 above, Message #1 also carries geographic location information and / or reader target set information. In this case, the RAN selects the reader to perform this task based on the geographic location information and / or reader target set information.

[0648] S1306: RAN sends RRC message #1 to the executing reader / writer. Correspondingly, the reader / writer receives RRC message #1 from RAN.

[0649] The above reader / writer is the reader / writer that performs this task, and the reader / writer belongs to at least one reader / writer indicated by the reader / writer target set information.

[0650] The RRC message #1 includes at least one of the following: a task identifier, a mask, or an operation instruction #11. The operation instruction #11 can be used to trigger the reader to initiate a paging operation.

[0651] S1307: The reader performs a paging operation.

[0652] The reader broadcasts a paging message that carries the mask.

[0653] S1308: Device #1 and device #2 perform a random access operation.

[0654] The following describes the specific process of device #1 performing a random access operation through S1309a-S13013a, and the specific process of device #1 performing the operation through S1304a-S13022a. Furthermore, the following describes the specific process of device #2 performing a random access operation through S1309b-S13013b, and the specific process of device #1 performing the operation through S1304b-S13022b.

[0655] It is understood that S1309a and S1309b can be performed simultaneously or sequentially, such as performing S1309a first and then S1309b, or performing S1309b first and then S1309a. The specific configuration can be based on actual conditions and is not limited. In addition, the random access process and operation process of device #1 and device #2 can be performed in parallel, that is, it is not necessary to wait until device #1 completes the operation before performing the relevant operation of device #2. The specific order of the steps in FIG13 can be referred to for understanding, and will not be repeated here.

[0656] S1309a: Device #1 sends a D2R (Device to Reader) transmission message #1 to the reader. In response, the reader receives the D2R (Device to Reader) transmission message #1 from device #1.

[0657] D2R transmission message #1 includes the identifiers of RN16-1 and device #1 (denoted as identifier #1). Identifier #1 is carried on the AIoT NAS message (or information). Identifier #1 corresponds to the first information mentioned above, and RN16-1 corresponds to the second identifier.

[0658] S13010a, the reader generates a device session ID #1 based on RN16-1.

[0659] The device session identifier #1 corresponds to the first identifier mentioned above.

[0660] In addition, the reader / writer maintains the correspondence between RN16-1 and device session identifier #1. This correspondence can be stored in a temporary context of the reader / writer, such as a context indexed by the task identifier or a context indexed by RN16-1 / device session identifier #1.

[0661] S13011a: The reader sends RRC message #2 to the RAN. In response, the RAN receives the RRC message #2 from the reader.

[0662] The RRC message #2 includes at least one of the following: a device session identifier #1, a task identifier, or an identifier #1. The identifier #1 is carried in an AIoT NAS message (or information).

[0663] S13012a: RAN generates device N2 identifier #1 based on device session identifier #1.

[0664] The device N2 identifier #1 corresponds to the third identifier mentioned above.

[0665] In addition, the RAN maintains a correspondence between session identifier #1 and device N2 identifier #1. This correspondence may be stored in a temporary context of the RAN, such as a context indexed by the task identifier or a context indexed by device N2 identifier #1 / device session identifier #1.

[0666] S13013a: RAN sends message #2 to AIoTMF. Correspondingly, AIoTMF receives message #2 from RAN.

[0667] Message #2 includes at least one of the following: device N2 identifier #1, task identifier, reader identifier (such as AIOT NGAP ID), or identifier #1.

[0668] S13014a, AIoTMF determines the corresponding operation of device #1 based on message #2.

[0669] That is, the AIoTMF can determine the operation that needs to be performed on device #1 based on identifier #1 and / or task identifier.

[0670] In addition, AIoTMF stores the correspondence between identifier #1, device N2 identifier #1 and reader identifier, and the correspondence can be stored in the context of device #1.

[0671] S13015a: AIoTMF sends message #3 to RAN. Correspondingly, RAN receives message #3 from AIoTMF.

[0672] Message #3 includes at least one of the following: device N2 identifier #1, reader identifier, task identifier, or operation instruction #1. The reader identifier corresponds to the identifier of the reader.

[0673] S13016a: The RAN determines the device session identifier #1 based on the device N2 identifier #1.

[0674] The RAN determines device session identifier #1 based on the correspondence between device N2 identifier #1 and device session identifier #1. For example, the RAN can index the correspondence between device N2 identifier #1 and device session identifier #1 based on the task identifier and determine device session identifier #1 based on this correspondence. Alternatively, the RAN can index the temporary context of device #1 on the RAN based on device N2 identifier #1 and, based on this temporary context, determine the correspondence between device N2 identifier #1 and device session identifier #1 and, based on this correspondence, determine device session identifier #1.

[0675] S13017a: RAN sends RRC message #3 to the reader / writer. Correspondingly, the reader / writer receives RRC message #3 from RAN.

[0676] The RRC message #3 includes at least one of the following: a device session identifier #1, an operation instruction #1, or a task identifier. The RRC message #3 corresponds to the first operation request message.

[0677] S13018a, the reader determines RN16-1 based on the device session identifier #1.

[0678] The reader / writer can determine RN16-1 based on the correspondence between device session identifier #1 and RN16-1. For example, the reader / writer can use the task identifier to index the correspondence between device session identifier #1 and RN16-1, and determine RN16-1 based on this correspondence. Alternatively, the reader / writer can use the device session identifier #1 to index the temporary context of device #1 on the reader / writer, determine the correspondence between device session identifier #1 and RN16-1 based on this temporary context, and determine RN16-1 based on this correspondence.

[0679] S13019a: The reader sends a D2R transmission message #2 to device #1. In response, device #1 receives the D2R transmission message #2 from the reader.

[0680] D2R transmission message #2 includes operation instruction #1. In this case, the reader can determine the frequency band and frequency point corresponding to RN16-1 and send D2R transmission message #2 based on the frequency band and frequency point.

[0681] Optionally, the D2R transmission message #2 also includes RN16-1.

[0682] S13020a: Device #1 sends D2R transmission message #3 to the reader / writer. In response, the reader / writer receives D2R transmission message #3 from device #1.

[0683] The D2R transmission message #3 includes an operation result #1. The operation result #1 is used to indicate the result of the operation indicated by the operation instruction executed by the device #1.

[0684] Optionally, the D2R transmission message #3 also includes RN16-1.

[0685] S13021a: The reader sends RRC message #4 to the RAN. In response, the RAN receives the RRC message #4 from the reader.

[0686] The RRC message #4 includes at least one of the following: a device session identifier #1, an operation result #1, or a task identifier.

[0687] S13022a: RAN sends message #4 to AIoTMF. Correspondingly, AIoTMF receives message #4 from RAN.

[0688] Message #4 includes at least one of the following: device N2 identification #1, or operation result #1.

[0689] S1309b: Device #2 sends a D2R transmission message #4 to the RAN. The RAN receives the D2R transmission message #4 from the device #2.

[0690] D2R transmission message #4 includes the identifier of RN16-2 and device #2 (denoted as identifier #2). Identifier #2 is carried on the AIoT NAS message (or information). Identifier #2 corresponds to the first information mentioned above, and RN16-2 corresponds to the second identifier.

[0691] S13010b, RAN generates device session identifier #2 according to RN16-2.

[0692] Device session identifier #2 corresponds to the above-mentioned first identifier.

[0693] S13011b: The reader sends RRC message #5 to the RAN. Correspondingly, the RAN receives RRC message #5 from the reader.

[0694] The RRC message #5 includes at least one of the following: a device session identifier #2, a task identifier, or an identifier #2. The identifier #2 is carried in the AIoT NAS message (or information).

[0695] S13012b: RAN generates device N2 identifier #2 based on device session identifier #2.

[0696] The device N2 identifier #2 corresponds to the third identifier mentioned above.

[0697] In addition, the RAN maintains a correspondence between session identifier #2 and device N2 identifier #2. This correspondence may be stored in a temporary context of the RAN, such as a context indexed by the task identifier or a context indexed by device N2 identifier #2 / device session identifier #2.

[0698] S13013b: RAN sends message #5 to AIoTMF. Correspondingly, AIoTMF receives message #5 from RAN.

[0699] Message #5 includes at least one of the following: device N2 identifier #2, task identifier, reader / writer identifier, or identifier #2.

[0700] S13014b, AIoTMF determines the corresponding operation of device #2 based on message #5.

[0701] That is, the AIoTMF can determine the operation that needs to be performed on device #2 based on identifier #2 and / or task identifier.

[0702] In addition, AIoTMF stores the correspondence between identifier #2, device N2 identifier #2 and reader identifier, and the correspondence can be stored in the context of device #2.

[0703] S13015b: AIoTMF sends message #6 to RAN. Correspondingly, RAN receives message #6 from AIoTMF.

[0704] Message #6 includes at least one of the following: device N2 identifier #2, reader identifier, task identifier, or operation instruction #2.

[0705] S13016b: RAN determines device session identifier #2 based on device N2 identifier #2.

[0706] The RAN determines device session identifier #2 based on the correspondence between device N2 identifier #2 and device session identifier #2. For example, the RAN can index the correspondence between device N2 identifier #2 and device session identifier #2 based on the task identifier and determine device session identifier #2 based on this correspondence. Alternatively, the RAN can index the temporary context of device #2 on the RAN based on device N2 identifier #2 and, based on this temporary context, determine the correspondence between device N2 identifier #1 and device session identifier #1 and, based on this correspondence, determine device session identifier #2.

[0707] S13017b: RAN sends RRC message #6 to the reader / writer. Correspondingly, the reader / writer receives RRC message #6 from RAN.

[0708] The RRC message #6 includes at least one of the following: a device session identifier #2, an operation instruction #2, or a task identifier. The RRC message #6 corresponds to the second operation request message.

[0709] S13018b, the reader determines RN16-2 based on the device session identifier #2.

[0710] The reader / writer can determine RN16-2 based on the correspondence between device session identifier #2 and RN16-2. For example, the reader / writer can index the correspondence between device session identifier #2 and RN16-2 based on the task identifier, and determine RN16-2 based on this correspondence. Alternatively, the reader / writer can index the temporary context of device #2 on the reader / writer based on device session identifier #2, determine the correspondence between device session identifier #2 and RN16-2 based on this temporary context, and determine RN16-2 based on this correspondence.

[0711] S13019b: The reader sends a D2R transmission message #5 to device #2. In response, device #2 receives the D2R transmission message #5 from the reader.

[0712] D2R transmission message #5 includes operation instruction #2. In this case, the reader can determine the frequency band and frequency point corresponding to RN16-2 and send D2R transmission message #5 based on the frequency band and frequency point.

[0713] Optionally, the D2R transmission message #5 also includes RN16-2.

[0714] S13020b: Device #2 sends D2R transmission message #6 to the reader / writer. Correspondingly, the reader / writer receives D2R transmission message #6 from device #2.

[0715] The D2R transmission message #6 includes an operation result #2, where the operation result #2 is used to indicate the result of the operation indicated by the operation instruction executed by the device #2.

[0716] Optionally, the D2R transmission message #6 also includes RN16-1.

[0717] S13021b: The reader sends RRC message #7 to the RAN. Correspondingly, the RAN receives RRC message #7 from the reader.

[0718] The RRC message #7 includes at least one of the following: a device session identifier #2, an operation result #2, or a task identifier.

[0719] S13022b: RAN sends message #7 to AIoTMF. Correspondingly, AIoTMF receives message #7 from RAN.

[0720] Message #7 includes at least one of the following: device N2 identification #2, or operation result #2.

[0721] It is understood that the specific implementation of S1309a-S13002a is similar to that of S1309b-S13002b, and they can be understood by reference to each other, and will not be repeated here. Furthermore, the above-mentioned S1301-S13022b can refer to the relevant description of the embodiment shown in FIG. 12 , and will not be repeated here. Furthermore, the above-mentioned messages (such as RRC messages, D2R messages, etc.) can be replaced with other types of messages according to actual circumstances, without limitation.

[0722] It can also be understood that in scenario 1, the AIoTMF can also interact with the RAN through the AMF. In this case, the AIoTMF can send the information sent by the NEF to the AMF. After receiving the information from the AIoTMF, the AMF can send corresponding information to the RAN based on the information. Alternatively, after receiving the information from the RAN, the AMF can send corresponding information to the AIoTMF based on the information.

[0723] For example, with respect to the above S1303, the NEF may send an environmental energy acquisition IoT service request #2 to the AIoTMF. After receiving the environmental energy acquisition IoT service request #2, the AIoTMF may send an N1N2 transmission message to the AMF based on the environmental energy acquisition IoT service request #2, so that the AMF sends an N2 message to the RAN based on the N1N2 transmission message. The N1N2 transmission message may include at least one of the following: a reader identifier (such as SUPI), a task identifier, a mask, or an operation instruction #11; and the N2 message may include at least one of the following: a reader identifier (such as a RAN / AMF NGAP UE ID pair), a task identifier, a mask, or an operation instruction #11.

[0724] It can be understood that the above content is only an example, and the specific implementation can be set accordingly according to actual conditions, and is not limited here.

[0725] Scenario 2:

[0726] Figure 14 is a flow chart of the communication method provided in an embodiment of the present application. This method is applicable to the communication system shown in Figure 10, and mainly involves the interaction between device #1 (the above-mentioned first terminal device), device #2, reader / writer, RAN (the above-mentioned access network device), AIoTMF (the above-mentioned core network element), UDM, NEF, and AF. In scenario 2, AF needs to operate on device #1 and device #2. The reader / writer allocates a temporary identifier to the device according to the identifier in the random access request sent by the device (device #1 or device #2), and RAN can reuse the identifier, thereby identifying the uplink and downlink signaling through the temporary identifier to complete the operation of the device.

[0727] It can be understood that the embodiment shown in FIG14 is similar to the embodiment shown in FIG13 , except that: in the embodiment shown in FIG13 , after receiving the device session identifier (e.g., device session identifier #1 or device session identifier #2) from the reader / writer, the RAN generates a device N2 identifier (e.g., device N2 identifier #1 or device N2 identifier #2) based on the device session identifier, as shown in S13012a and S13012b. In contrast, in the embodiment shown in FIG14 , after receiving the device session identifier from the reader / writer, the RAN can reuse the device session identifier, as shown in S14012a and S14012b in FIG14 . Furthermore, the other steps in the embodiment shown in FIG14 , except for S14012a and S14012b, can be understood by referring to the relevant description of the embodiment shown in FIG13 and will not be repeated here.

[0728] Scenario 3:

[0729] Figure 15 is a flowchart eight of the communication method provided in an embodiment of the present application. This method is applicable to the communication system shown in Figure 10, and mainly involves the interaction between device #1 (the above-mentioned first terminal device), device #2, reader / writer, RAN (the above-mentioned access network device), AIoTMF (the above-mentioned core network element), UDM, NEF, and AF. In scenario 3, AF needs to operate on device #1 and device #2. The reader / writer reuses the identifier in the random access request sent by the device (device #1 or device #2), and RAN allocates a new temporary identifier to the device based on the identifier, thereby identifying the uplink and downlink signaling through the temporary identifier to complete the operation of the device.

[0730] It can be understood that the embodiment shown in Figure 15 is similar to the embodiment shown in Figure 13, except that: in the embodiment shown in Figure 13, after receiving the identifier (such as RN16-1 or RN16-2) sent by the device in the random access request process, the reader will generate a device session identifier (such as device session identifier #1 or device session identifier #2) based on the identifier, such as S13010a and S13010b. In the embodiment shown in Figure 14, after receiving the identifier sent by the device in the random access request process, the reader can reuse the identifier, such as S15010a and S15010b shown in Figure 15. In addition, the other steps in the embodiment shown in Figure 15, except for S15010a and S15010b, can be understood by referring to the relevant introduction of the embodiment shown in Figure 13, and will not be repeated here.

[0731] Scenario 4:

[0732] Figure 16 is a flowchart eight of the communication method provided in an embodiment of the present application. This method is applicable to the communication system shown in Figure 10, and mainly involves the interaction between device #1 (the above-mentioned first terminal device), device #2, reader / writer, RAN (the above-mentioned access network device), AIoTMF (the above-mentioned core network element), UDM, NEF, and AF. In scenario 4, AF needs to operate on device #1 and device #2, and the reader / writer and RAN multiplex the identifier in the random access request sent by the device (device #1 or device #2), thereby identifying the uplink and downlink signaling through the temporary identifier to complete the operation of the device.

[0733] It can be understood that the embodiment shown in Figure 16 is similar to the embodiment shown in Figure 13, with the difference that: after the reader receives the identifier (such as RN16-1 or RN16-2) sent by the device in the random access request process, it will generate a device session identifier (such as device session identifier #1 or device session identifier #2) based on the identifier, such as S13010a and S13010b; after the RAN receives the device session identifier (such as device session identifier #1 or device session identifier #2) from the reader, it will generate a device N2 identifier (such as device N2 identifier #1 or device N2 identifier #2) based on the device session identifier, such as S13012a and S13012b. In the embodiment shown in FIG14 , after receiving the identifier sent by the device in the random access request process, the reader can reuse the identifier, as shown in S16010a and S16010b of FIG16 . After receiving the device session identifier from the reader, the RAN can reuse the device session identifier, as shown in S16012a and S16012b of FIG16 . Furthermore, steps other than S16010a, S16010b, S16012a, and S16012b of the embodiment shown in FIG16 can be understood by referring to the relevant description of the embodiment shown in FIG13 , and will not be repeated here.

[0734] The communication method provided in the embodiment of the present application is described in detail above in conjunction with Figures 6-9 and Figures 12-16. The communication device for executing the communication method provided in the embodiment of the present application is described in detail below in conjunction with Figures 17-18.

[0735] Figure 17 is a structural diagram of a communication device according to an embodiment of the present application. As shown in Figure 17 , the communication device 1700 includes a transceiver module 1701 and a processing module 1702. For ease of illustration, Figure 17 only shows the main components of the communication device.

[0736] Among them, the transceiver module 1701 is used to perform the transceiver function of the method shown in Figures 6-9 and 12-16 above, and the processing module 1702 is used to perform other functions of the method shown in Figures 6-9 and 12-16 except the transceiver function.

[0737] Optionally, the transceiver module 1701 may include a sending module (not shown in FIG17 ) and a receiving module (not shown in FIG17 ). The sending module is used to implement the sending function of the communication device 1700 , and the receiving module is used to implement the receiving function of the communication device 1700 .

[0738] Optionally, the communication device 1700 may further include a storage module (not shown in FIG. 17 ) storing a program or instruction. When the processing module 1702 executes the program or instruction, the communication device 1700 may perform the functions of a terminal device (such as a reader / writer, etc.) or a network device (such as an access network device, a core network element, or a core network device, etc.) in the methods shown in FIG. 6-FIG . 9 and FIG. 12-FIG . 16 of the above method.

[0739] It can be understood that the communication device 1700 can be a terminal device or a network device, or a chip (system) or other parts or components that can be set in the terminal device or the network device, or a device that includes the terminal device or the network device. This application does not limit this.

[0740] In addition, the technical effects of the communication device 1700 can refer to the technical effects of the communication methods shown in Figures 6 to 9 and Figures 12 to 16, and will not be repeated here.

[0741] Figure 18 is a second structural diagram of a communication device provided in an embodiment of the present application. Exemplarily, the communication device may be a terminal device, an access network device, or a core network device, or may be a chip (system) or other parts or components that can be set in the terminal device, the access network device, or the core network device. As shown in Figure 18, the communication device 1800 may include a processor 1801. Optionally, the communication device 1800 may further include a memory 1802 and / or a transceiver 1803. The processor 1801 is coupled to the memory 1802 and the transceiver 1803, such as by being connected via a communication bus.

[0742] The following is a detailed introduction to the various components of the communication device 1800 with reference to FIG18 :

[0743] The processor 1801 is the control center of the communication device 1800 and can be a single processor or a collective term for multiple processing elements. For example, the processor 1801 can be one or more central processing units (CPUs), an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application, such as one or more microprocessors (digital signal processors, DSPs) or one or more field programmable gate arrays (FPGAs).

[0744] Optionally, the processor 1801 can execute various functions of the communication device 1800, such as executing the above-mentioned communication method, by running or executing a software program stored in the memory 1802 and calling data stored in the memory 1802.

[0745] In a specific implementation, as an embodiment, the processor 1801 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG. 18 .

[0746] In a specific implementation, as an embodiment, the communication device 1800 may also include multiple processors, such as the processor 1801 and the processor 1804 shown in FIG18 . Each of these processors may be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). The processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0747] Among them, the memory 1802 is used to store the software program for executing the solution of this application, and the execution is controlled by the processor 1801. The specific implementation method can refer to the above method embodiment and will not be repeated here.

[0748] Alternatively, the memory 1802 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, an optical disc storage (including a compact disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 1802 may be integrated with the processor 1801 or exist independently and be coupled to the processor 1801 via an interface circuit (not shown in FIG. 18 ) of the communication device 1800, which is not specifically limited in this embodiment of the present application.

[0749] Transceiver 1803 is used for communication with other communication devices. For example, if communication device 1800 is a terminal, transceiver 1803 can be used to communicate with a network device or another terminal device. For another example, if communication device 1800 is a network device, transceiver 1803 can be used to communicate with a terminal or another network device.

[0750] Optionally, the transceiver 1803 may include a receiver and a transmitter (not shown separately in FIG18 ), wherein the receiver is used to implement a receiving function, and the transmitter is used to implement a transmitting function.

[0751] Optionally, the transceiver 1803 may include a transmitter, a receiver, a radio frequency circuit, an antenna, and input / output devices (not shown separately in FIG6 ). The transmitter is used to implement the transmission function; the receiver is used to implement the reception function; the radio frequency circuit is mainly used for converting baseband signals into radio frequency signals and processing radio frequency signals; the antenna is mainly used to transmit and receive radio frequency signals in the form of electromagnetic waves; the input / output devices may include a touch screen, a display screen, or a keyboard; the input / output devices are mainly used to receive data input by the user and output data to the user. It should be noted that some types of terminal devices may not have input / output devices.

[0752] When data needs to be sent, the processor performs baseband processing on the data to be sent and outputs the baseband signal to the RF circuit. Then, the RF circuit performs RF processing on the baseband signal and sends the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the terminal device, the RF circuit receives the RF signal through the antenna. The RF circuit converts the RF signal into a baseband signal and outputs the baseband signal to the processor. The processor converts the baseband signal into data and processes the data. In an actual terminal device product, there may be one or more processors and one or more memories. The memory may also be referred to as a storage medium or a storage device, etc. The memory may be set independently of the processor or integrated with the processor, and the embodiments of the present application do not limit this.

[0753] In the embodiment of the present application, the antenna and radio frequency circuit with transceiver functions can be regarded as the transceiver module of the terminal device, and the processor with processing function can be regarded as the processing module of the terminal device.

[0754] Optionally, the t...

Claims

1. A communication method, characterized in that: The method comprises: After receiving the first random access request from the first terminal device, the access network device determines a first identifier of the first terminal device, where the first identifier is used to indicate the first terminal device at a first signaling layer; The access network device sends the first identifier and the identifier of the first terminal device to the core network device, where the identifier of the first terminal device is used to indicate the first terminal device at the second signaling layer; The access network device receives an operation request message from the core network device, where the operation request message is determined based on an identifier of the first terminal device, and the operation request message includes the first identifier and an operation instruction; The access network device obtains a second identifier according to the first identifier, where the second identifier is used to indicate the first terminal device at the access control layer; The access network device sends the operation instruction and the second identifier to the first terminal device.

2. The method according to claim 1, characterized in that The method further comprises: The access network device receives the first random access request, where the first random access request includes the second identifier; The determining the first identifier of the first terminal device includes: The access network device allocates the first identifier to the first terminal device according to the second identifier.

3. The method according to claim 2, characterized in that The method further comprises: The access network device saves the context of the first terminal device, where the context of the first terminal device includes the second identifier and the first identifier.

4. The method according to claim 3, characterized in that The operation request message also includes first indication information, and the first indication information is used to instruct the access network device to delete the context of the first terminal device after completing the operation on the first terminal device.

5. The method according to claim 3, characterized in that Before the access network device receives the first random access request, the method further includes: The access network device receives an operation task request message from the core network device, where the operation task request message includes a task identifier; The access network device broadcasts a second random access request according to the operation task request message; the context of the first terminal device also includes the task identifier.

6. The method according to claim 1, characterized in that The method further comprises: The access network device receives the first random access request, where the first random access request includes a second identifier; The determining the first identifier of the first terminal device includes: The access network device determines that the second identifier is the first identifier.

7. The method according to claim 6, characterized in that Before the access network device receives the first random access request, the method further includes: The access network device receives an operation task request message from the core network device, where the operation task request message includes a task identifier; The access network device broadcasts a second random access request according to the operation task request message; After the access network device determines that the second identifier is the first identifier, the access network device saves the context of the first terminal device, where the context of the first terminal device includes the task identifier and the first identifier.

8. The method according to claim 5 or 7, characterized in that After the access network device saves the context of the first terminal device, the method further includes: The access network device receives a task identifier and second indication information from the core network device, where the second indication information is used to instruct the access network device to delete a context including the task identifier; The access network device deletes the context of the first terminal device according to the task identifier and the second indication information.

9. The method according to any one of claims 1 to 8, characterized in that The method further comprises: The access network device receives an operation result from the first terminal device, where the operation result is a result of the first terminal device executing the operation indicated by the operation instruction; The access network device sends the operation result and the first identifier to the core network device.

10. A communication method, characterized in that: The method comprises: The core network device receives a first identifier and an identifier of a first terminal device from an access network device, where the first identifier is used to indicate the first terminal device at a first signaling layer, and the identifier of the first terminal device is used to indicate the first terminal device at a second signaling layer; The core network device determines an operation of the first terminal device according to the identifier of the first terminal device; The core network device sends an operation request message to the access network device, where the operation request message includes the first identifier and an operation instruction.

11. The method according to claim 10, characterized in that The operation request message also includes first indication information, and the first indication information is used to instruct the access network device to delete the context of the first terminal device after completing the operation on the first terminal device.

12. The method according to claim 10, characterized in that Before the core network device receives the first identifier and the identifier of the first terminal device from the access network device, the method further includes: The core network device sends an operation task request message to the access network device, where the operation task request message includes a task identifier; After determining that the operation task indicated by the task identifier is completed, the core network device sends the task identifier and second indication information to the access network device, where the second indication information is used to instruct the access network device to delete the context including the task identifier.

13. A communication method, characterized in that: The method comprises: After receiving the first random access request from the first terminal device, the reader / writer determines a first identifier of the first terminal device, where the first identifier is used to indicate the first terminal device at the access control layer; The reader / writer sends the first identifier and first information to the access network device, where the first information is used to indicate the first terminal device at a first signaling layer; The reader / writer receives a first operation request message from the access network device, where the first operation request message includes the first identifier and an operation instruction, where the operation instruction is determined based on the first information; The reader / writer obtains a second identifier according to the first identifier, where the second identifier is used to indicate the first terminal device at a second signaling layer; The reader / writer sends the operation instruction and the second identifier to the first terminal device.

14. The method according to claim 13, characterized in that The method further comprises: The reader receives the first random access request, where the first random access request includes the second identifier; The reader / writer determines the first identification of the first terminal device, including: The reader / writer allocates a first identification to the first terminal device according to the second identification.

15. The method according to claim 14, characterized in that The method further comprises: The reader / writer saves a first context of the first terminal device, where the first context includes the first identifier and the second identifier.

16. The method according to claim 15, characterized in that The first operation request message further includes first indication information, where the first indication information is used to instruct the reader to delete the first context after completing the operation on the first terminal device.

17. The method according to any one of claims 13 to 16, characterized in that The method further comprises: The reader / writer receives an operation result from the first terminal device, where the operation result is a result of the first terminal device executing the operation indicated by the operation instruction; The reader / writer sends the operation result and the first identifier to the access network device.

18. A communication method, characterized in that: The method comprises: After receiving the first identifier and the first information from the reader / writer, the access network device determines a third identifier, where the first identifier is used to indicate the first terminal device at the access control layer, the first information is used to indicate the first terminal device at the first signaling layer, and the third identifier is used to indicate the first terminal device at the third signaling layer; The access network device sends the third identifier and the first information to the core network network element; The access network device receives a second operation request message from the core network element, where the second operation request message is determined based on the first information and includes the third identifier and an operation instruction; The access network device obtains the first identifier according to the third identifier; The access network device sends a first operation request message to the reader / writer, where the first operation request message includes the operation instruction and the first identifier.

19. The method according to claim 18, characterized in that The method further comprises: The access network device receives the first identifier and the first information; The access network device determining the third identifier includes: The access network device allocates the third identifier to the first terminal device based on the first identifier.

20. The method according to claim 19, characterized in that The method further comprises: The access network device saves a second context of the first terminal device, where the second context includes the first identifier and the third identifier.

21. The method according to claim 20, characterized in that The second operation request message also includes second indication information, and the second indication information is used to instruct the access network device to delete the context of the first terminal device after completing the operation on the first terminal device.

22. The method according to any one of claims 18 to 21, characterized in that The method further comprises: The access network device receives an operation result from the reader / writer, where the operation result is a result of the first terminal device executing the operation indicated by the operation instruction; The access network device sends the operation result and the third identifier to the core network network element.

23. A communication method, characterized in that: The method comprises: The core network network element receives a third identifier and first information from the access network device, where the third identifier is used to indicate the first terminal device at the third signaling layer, and the first information is used to indicate the first terminal device at the first signaling layer; The core network element determines, based on the first information, an operation of the first terminal device; The core network element sends a second operation request message to the access network device, where the second operation request message includes the third identifier and an operation instruction.

24. The method according to claim 23, wherein The second operation request message also includes second indication information, and the second indication information is used to instruct the access network device to delete the context of the first terminal device after completing the operation on the first terminal device.

25. The method according to claim 23 or 24, characterized in that The method further comprises: The core network element stores the correspondence between the identifier of the reader / writer and the third identifier, and the reader / writer is used to serve the first terminal device.

26. A communication device, characterized in that: The apparatus comprises: a module for executing the method according to any one of claims 1-25.

27. A communication device, characterized in that: The communication device is configured to execute the communication method according to any one of claims 1 to 25.

28. A communication device, characterized in that: include: processor and memory; The memory is used to store computer instructions, and when the processor executes the instructions, the communication device executes the communication method according to any one of claims 1 to 25.

29. A communication chip, characterized in that: The communication chip includes: a logic circuit and a communication interface, the logic circuit is used to execute computer instructions, and the communication interface is used for the communication chip to communicate with other devices or chips. When the logic circuit executes the computer instructions, the method described in any one of claims 1 to 25 is implemented.

30. A computer-readable storage medium, characterized in that The computer-readable storage medium comprises a computer program or instructions, which, when executed on a communication device, causes the communication device to perform the method according to any one of claims 1 to 25.

31. A computer program product, characterized in that The computer program product includes a computer program or instructions, and when the computer program or instructions are executed by a communication device, the method according to any one of claims 1 to 25 is executed.

Images