Communication method and related apparatus

By configuring resource pools and validity periods in the terminal's idle state, the problem of the terminal being unable to execute A-IoT services is solved, achieving more efficient A-IoT service execution and resource management.

WO2026067517A1PCT designated stage Publication Date: 2026-04-02HUAWEI TECH CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-09-25
Publication Date
2026-04-02

AI Technical Summary

Technical Problem

In existing communication systems, terminals cannot execute A-IoT (Ambient Internet of Things) services when they are in an idle state, resulting in low service execution efficiency.

Method used

By utilizing the resource pool and valid time configured in the access network device when the terminal is in an idle state, the terminal is allowed to communicate with the device, thereby enabling the execution of A-IoT services.

Benefits of technology

It improves the efficiency of terminals in executing A-IoT services in idle state, saves signaling overhead, and is more flexible and efficient in resource configuration and service execution.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2025123910_02042026_PF_FP_ABST
    Figure CN2025123910_02042026_PF_FP_ABST
Patent Text Reader

Abstract

A communication method and a related apparatus, which belong to the technical field of communications. In the communication method, a first access network device sends a first message to a terminal, and correspondingly, the terminal receives the first message, wherein the first message comprises a valid time period T during which a first resource is used for the terminal to communicate with a device; and during the valid time period T in an idle state, the terminal communicates with the device on the basis of the first resource. Thus, by executing an A-IoT service during a valid time period T in an idle state, a terminal improves the execution efficiency of the A-IoT service compared with executing the A-IoT service only in a connected state.
Need to check novelty before this filing date? Find Prior Art

Description

Communication method and related apparatus

[0001] This application claims priority to the Chinese patent application No. 202411391971.3, filed on September 30, 2024, with the State Intellectual Property Office of China, and entitled "Communication method and related apparatus", the whole content of which is incorporated herein by reference. TECHNICAL FIELD

[0002] The present application relates to the field of communication technology, in particular to a communication method and related apparatus. BACKGROUND

[0003] With the development of communication technology, various communication systems have emerged, for example, ambient internet of things (A-IoT) technology. A-IoT in A-IoT technology can be composed of a reader and passive / semi-passive / active A-IoT devices. The reader and A-IoT devices can be devices in a cellular network, such as a network device or a terminal. The functions of the reader can be implemented by a network device or a terminal, and the A-IoT device can be implemented by a terminal in a cellular network. In one possible A-IoT architecture, the network device and the A-IoT device communicate bidirectionally through an intermediate node, or unidirectionally through an auxiliary node. The intermediate node or the auxiliary node can be a terminal in a cellular network. When the terminal is in a connected state, it implements or assists the network device and the A-IoT device to perform A-IoT services. However, it cannot support the terminal to perform A-IoT services when the terminal is in an idle state. SUMMARY

[0004] The present application provides a communication method and related apparatus, which enables a terminal to perform A-IoT services in an idle state.

[0005] The communication method provided by the present application relates to a first device, a second device and a third device. The first device is a terminal-side device, such as a terminal or a communication module in the terminal, or a circuit or chip responsible for communication functions in the terminal (such as a modem chip, also known as a baseband chip, or a system on chip (SoC) chip or system in package (SIP) chip containing a modem core). The second device is a network-side device, such as an access network device on the network side, or a distributed unit (DU) on the network side, or a control unit (CU) or its components (such as circuits, chips or chip systems, etc.). The third device is a device that communicates with the network side through the terminal to implement A-IoT technology, such as a tag or an A-IoT terminal, or a component therein.

[0006] In a first aspect, the communication method is described by taking a terminal as the first device, a first access network device as the second device, and a device as the third device. The method is applied to the terminal side. In the method, the terminal receives a first message from the first access network device, and the first message includes a first resource and a valid time for the terminal to communicate with the device; and the terminal communicates with the device according to the first resource within the valid time in an idle state.

[0007] It can be seen that, in the method, the terminal communicates with the device according to the first resource within the valid time in the idle state, and the terminal performs the A-IoT service in the idle state is realized. In addition, compared with performing the A-IoT service only in the connected state, the execution efficiency of the A-IoT service is improved.

[0008] Optionally, the valid time is a time length for the terminal to communicate with the device according to the first resource, or a time length allowed by the first access network device for the terminal to communicate with the device according to the first resource. The valid time can be referred to as an effective time length (or an effective time) of the first resource, an activation time length (or an activation time). Alternatively, the valid time is a timing length of a timer, the timer is started when the terminal receives the first message or when the terminal enters the idle state, and the terminal stops communicating with the device according to the first resource when the timer times out. Alternatively, the valid time is a timing length of a timer, the timer starts timing when the terminal receives the first message or when the terminal enters the idle state, and the terminal stops communicating with the device according to the first resource when the timing time is up.

[0009] Optionally, after receiving the first message, the terminal enters the idle state and saves at least one of the context information related to the communication with the device, such as the valid time or identification information.

[0010] It can be seen that, in the embodiment, the terminal enters the idle state and communicates with the device by using the context information.

[0011] The first resource is an air interface resource or a wireless resource for the terminal to communicate with the device.

[0012] In an optional embodiment, the first resource is a resource pool at an area level, that is, a plurality of cells share one or more resource pools; or is a resource at a cell level, that is, a plurality of terminals accessing the same cell can share the resource to perform the A-IoT service; or is a resource shared by multiple stations, and the like.

[0013] It can be seen that, in the embodiment, the first resource is not exclusive to the terminal and can be preconfigured, thereby saving signaling overhead.

[0014] In another alternative implementation, the first resource is configured by the first access network device for the terminal, and is per-UE. The method further includes: the terminal receiving first information, the first information being used to indicate the first resource allocated by the first access network device for the terminal. Optionally, the first information can be included in the first message or received separately.

[0015] It can be seen that in this implementation, the first access network device separately configures the resource for the terminal to communicate with the device, so that in combination with the validity time (e.g., the validity time is T time), the first access network device can avoid allocating the same resource to other terminals in the same cell within the T time. If the same resource is allocated to other terminals in the same cell within the T time, the first access network device can determine whether the terminals are far enough apart based on the positions of the terminals or determine the approximate distance between the terminals based on measurement, and when the distance exceeds a distance threshold, the terminals can use the same resource to communicate with the device.

[0016] In an alternative implementation, the method further includes: the terminal receiving second information, the second information being used to indicate the terminal to communicate with the device in the idle state. Optionally, the second information can be transmitted together in the first message or transmitted relatively independently. In another alternative implementation, the second information is used to indicate the terminal to perform A-IoT service in the idle state. In yet another alternative implementation, the first message is a connection release message, and the first message includes the second information, the second information being used to indicate the terminal to continue using the first resource, so that the terminal can continue to use the first resource to communicate with the device in the idle state.

[0017] It can be seen that in this implementation, the first access network device can explicitly indicate the terminal to communicate with the device in the idle state, which is beneficial for the first access network device to determine, based on the service type or an indication from a core network element, the terminal to communicate with the device in the idle state and explicitly indicate the terminal through the second information.

[0018] In an alternative implementation, the terminal sends a message to the first access network device for requesting to communicate with the device in the idle state.

[0019] It can be seen that in this implementation, the terminal can actively request to communicate with the device in the idle state, which is beneficial for the terminal itself to determine, based on the service type or an indication from a core network element, to actively request to the first access network device when communicating with the device in the idle state.

[0020] In an alternative implementation, the method further includes: the terminal sending a message to the first access network device for requesting a resource to communicate with the device; and the sent message including identification information associated with the terminal communicating with the device.

[0021] It can be seen that in this embodiment, the terminal re-requests the resource for communicating with the device when the valid time expires. In addition, the message includes the identification information, so that the first access network device can request the core network element to confirm whether the terminal communicates with the device based on the identification information even if the context information of the terminal communicating with the device is not saved, and then determine whether to configure the terminal with the requested resource.

[0022] In an optional embodiment, the method further includes: the terminal sending, to the first access network device, a message for requesting to report the data from the device, and the sent message includes the identification information.

[0023] It can be seen that in this embodiment, the terminal requests to report the obtained data through the message when the terminal communicates with the device. In addition, the message includes the identification information, so that the first access network device can request the core network element to confirm whether the terminal communicates with the device based on the identification information even if the context information of the terminal communicating with the device is not saved, and then determine whether to instruct the terminal to report the data.

[0024] The method further relates to a fourth apparatus, which is an apparatus on the side of an access network device to which the terminal moves or reselects a cell, such as a distributed unit (DU) or a control unit (CU) or a component (such as a circuit, a chip or a chip system, etc.) thereof on the network side. For ease of description, the method is described by taking the fourth apparatus as the second access network device.

[0025] In an optional embodiment, the method further includes: the terminal sending, to the second access network device, a message for requesting the resource for communicating with the device or a message for requesting whether to report the data from the device according to an area associated with the second cell, wherein the second cell is a cell reselected by the terminal, and the message includes the identification information.

[0026] It can be seen that in this embodiment, after the terminal reselects a cell in an idle state, the terminal determines whether to request the resource for continuing to communicate with the device or to request whether to report the obtained data without continuing to communicate with the device, by combining the area associated with the reselected cell. Optionally, the area associated with the second cell is a service area or a coverage area of the second cell, or a service area or an inventory area of an A-IoT service supported by the second cell, etc.

[0027] In an alternative implementation, the terminal sends a message to the second access network device for requesting resources for communicating with the device or for requesting whether to report data from the device according to the area associated with the second cell, including: when the area associated with the second cell contains the first area, or is contained in the first area, or is the same as the first area, the terminal sends a message to the second access network device for requesting resources for communicating with the device, so that the terminal can continue to communicate with the device based on the re-requested resources. When the area associated with the second cell does not contain the first area, and is not contained in the first area, and is not the same as the first area, the terminal sends a message to the second access network device for requesting whether to report data from the device, so that the terminal does not continue to communicate with the device, and only requests whether to report data. The first area is an area associated with the terminal for communicating with the device.

[0028] It can be seen that in this implementation, the terminal can determine whether to continue to communicate with the device in combination with the area associated with the reselected cell and the area associated with the terminal for communicating with the device.

[0029] In another alternative implementation, the terminal sends a message to the second access network device for requesting resources for communicating with the device or for requesting whether to report data from the device according to the area associated with the second cell, including: when the area associated with the second cell contains the location of the terminal, the terminal sends a message to the second access network device for requesting resources for communicating with the device to continue to communicate with the device; when the area associated with the second cell does not contain the location of the terminal, the terminal sends a message to the second access network device for requesting whether to report data from the device, and does not continue to communicate with the device.

[0030] It can be seen that in this implementation, the terminal can determine whether to continue to communicate with the device in combination with the location of the terminal and the area associated with the reselected cell.

[0031] The message sent by the terminal contains identification information, which is conducive to the second access network device confirming whether the terminal is communicating with the device or confirming whether to report data from the device to the core network element.

[0032] In another alternative implementation, whether the terminal continues to communicate with the device or whether to report the obtained data after the terminal reselects the cell is confirmed by the core network element or is defaulted by the terminal. The following describes three implementations including but not limited to.

[0033] In a possible design, the terminal sends a message to the second access network device for requesting whether to communicate with the device and / or for requesting whether to report data from the device. The message sent contains identification information.

[0034] It can be seen that in the design, after the terminal reselects the cell in the idle state, the terminal requests the core network to determine whether the terminal continues to communicate with the device and whether to report data through the second access network device, thereby reducing the processing complexity of the terminal. Even if the terminal reselects the second cell in the idle state and accesses the second access network device, the second access network device does not save the context information of the terminal communicating with the device, and the second access network device can request the core network element to confirm whether the terminal continues to communicate with the device and / or whether to report the data of the device based on the identification information.

[0035] In another possible design, when the terminal reselects the second cell, the terminal deletes the information related to the communication with the device, such as the valid time, and sends a message for requesting whether to report the data obtained from the device to the second access network device, wherein the message includes the identification information.

[0036] It can be seen that in the design, after the terminal reselects the cell, the terminal does not continue to communicate with the device by default, and can request whether to report the data obtained from the device, thereby saving signaling overhead.

[0037] In another possible design, when the terminal reselects the second cell, the terminal deletes the information related to the communication with the device and the data from the device.

[0038] It can be seen that in the design, after the terminal reselects the cell, the terminal stops communicating with the device by default, that is, stops the A-IoT service, thereby saving signaling overhead.

[0039] Optionally, in the present application, the identification information includes at least one of the following: a service identifier, a session identifier, a task identifier, a stock area, a reader identifier, or an address of the core network element, which are associated with the communication between the terminal and the device. The message sent by the terminal to the access network device includes the identification information, so that even if the access network device does not save the context information of the terminal communicating with the device, the access network device can obtain the information related to the communication between the terminal and the device based on the identification information.

[0040] In a second aspect, the present application also provides a communication method. In a possible implementation, the method corresponds to the first aspect and can be applied to a second device, which can be a network-side device as described above. For the convenience of description, the second device is taken as an example of the first access network device. In the method, the first access network device determines that the first resource is used for the terminal to communicate with the device in the idle state, and the first access network device sends a first message to the terminal, wherein the first message includes the valid time.

[0041] It can be seen that in the method, the first access network device enables the terminal to communicate with the device according to the first resource within the valid time in the idle state, thereby realizing the terminal to perform the A-IoT service in the idle state. In addition, compared with the terminal performing the A-IoT service only in the connected state, the execution efficiency of the A-IoT service is improved.

[0042] In an optional implementation, the method further includes: the first access network device sending first information, the first information being used to indicate the first resource allocated for the terminal. It can be seen that in this implementation, the first access network device separately configures the resource for the terminal to communicate with the device, so that in combination with the valid time (for example, the valid time is T time), the first access network device can avoid allocating the same resource for other terminals to communicate with the device in the same cell within T time. Alternatively, if the same resource is allocated for other terminals to communicate with the device in the same cell within the valid time, the first access network device can determine whether the terminals are far enough apart based on the positions of the terminals, or determine the approximate distance between the terminals based on measurement, and when the distance exceeds a distance threshold, the terminals can use the same resource (i.e., the A IoT resource used to communicate with the device).

[0043] In an optional implementation, the method further includes: the first access network device sending second information to the terminal, the second information being used to indicate the terminal to communicate with the device in the idle state.

[0044] It can be seen that in this implementation, it is beneficial for the first access network device to determine that the terminal needs to perform the service in the idle state based on the service type, and to timely instruct the terminal to perform the service.

[0045] In an optional implementation, the method further includes: the first access network device receiving a message from the terminal, the message being used to request to communicate with the device.

[0046] It can be seen that in this implementation, it is beneficial for the terminal to determine to communicate with the device in the idle state based on the service type, and to request the first access network device through the message.

[0047] In an optional implementation, the method further includes: the first access network device receiving a message from the terminal, the message being used to request a resource to communicate with the device, or being used to request to report data from the device; and the first access network device sending a message to a core network element to request to confirm whether the terminal is communicating with the device, wherein the message received by the first access network device and the message sent by the first access network device include identification information associated with the terminal communicating with the device. It can be seen that before the first access network device allocates a resource for the terminal to communicate with the device, or instructs the terminal to report data from the device, the first access network device can first request the core network element to determine whether the terminal is communicating with the device, so that even if the first access network device does not save the context information of the terminal communicating with the device when the terminal is in the idle state, the first access network device can also request the confirmation of the core network element based on the identification information.

[0048] Optionally, other optional implementations and beneficial effects in this aspect can refer to the related content described in the first aspect, which will not be described in detail here.

[0049] In a third aspect, the present application also provides a communication method. In one possible implementation, the method can be applied to the fourth device, i.e., the device on the side of the second access network equipment to which the terminal reselects. Taking the fourth device as the second access network equipment, in the method, the second access network equipment receives a message from the terminal for requesting a resource for communicating with the device or for requesting whether to report data from the device; and the second access network equipment sends a message to a core network element for requesting confirmation of whether the terminal communicates with the device. The message received by the second access network equipment from the terminal and the message sent by the second access network equipment to the core network element both include identification information.

[0050] It can be seen that, in the method, the terminal in the idle state reselects a cell to access the second access network equipment, the second access network equipment does not save the context information of the terminal communicating with the device, and can request the core network element to confirm the context information based on the identification information, thereby facilitating the terminal to communicate with the device in the idle state and improving the execution efficiency of the A-IoT service. In addition, the method facilitates the terminal to determine whether to continue to communicate with the device after reselecting a cell.

[0051] Optionally, other optional implementation manners and beneficial effects in this aspect can refer to the related content described in the first aspect, and will not be described in detail here.

[0052] In a fourth aspect, the present application also provides a communication method. In another possible implementation, the method can be applied to the fourth device, i.e., the device on the side of the second access network equipment to which the terminal reselects. Taking the fourth device as the second access network equipment, in the method, the second access network equipment receives a message from the terminal for requesting whether to communicate with the device and / or whether to report data from the device; and the second access network equipment sends a message to a core network element for requesting confirmation of whether the terminal communicates with the device and / or whether to report data from the device. The message received by the second access network equipment and the message sent by the second access network equipment both include identification information associated with the terminal communicating with the device.

[0053] It can be seen that, in the method, even if the terminal is in the idle state, the second access network equipment does not save the context information of the terminal communicating with the device, and can request the core network element to confirm the context information based on the identification information, thereby facilitating the terminal to communicate with the device in the idle state and improving the execution efficiency of the A-IoT service. In addition, the method facilitates the core network element to determine whether the terminal continues to communicate with the device or whether the terminal reports the data obtained from the device.

[0054] Optionally, other optional implementation manners and beneficial effects in this aspect can refer to the related content described in the first aspect, and will not be described in detail here.

[0055] In a fifth aspect, the present application provides a communication method. In one possible implementation, the method corresponds to the third aspect and is applied to a core network element. In the method, the core network element receives a message from a first access network device for requesting confirmation of whether a terminal communicates with a device, the received message comprising identification information associated with the communication between the terminal and the device; and the core network element sends a message to the first access network device for confirming that the terminal communicates with the device or for confirming that the terminal does not communicate with the device.

[0056] Optionally, the core network element performs authorization judgment on the terminal based on the identification information, and if it is judged that the terminal has the right to perform A-IoT service or is communicating with the device, the core network element sends a message to the first access network device for confirming that the terminal communicates with the device; and if it is judged that the terminal does not have the right or is not performing A-IoT service with the device, the core network element sends a message to the first access network device for confirming that the terminal does not communicate with the device.

[0057] It can be seen that in the method, the terminal is in an idle state, and even if the first access network device does not save the context information of the communication between the terminal and the device, the core network element can confirm whether the terminal communicates with the device, so that the first access network device knows whether to continue to configure resources for the communication between the terminal and the device or to instruct the terminal to report data from the device.

[0058] Optionally, the other optional implementation and beneficial effects in this aspect can refer to the related content described in the third aspect, and will not be described in detail here.

[0059] In a sixth aspect, the present application provides a communication method. In another possible implementation, the method corresponds to the fourth aspect and can be applied to a core network element. In the method, the core network element receives a message from a second access network device for requesting whether a terminal communicates with a device and / or whether the terminal reports data from the device, the received message comprising identification information associated with the communication between the terminal and the device; and the core network element sends a message to the second access network device for confirming that the terminal communicates with the device, for confirming that the terminal reports data from the device, or for confirming that the terminal does not communicate with the device and does not report data from the device.

[0060] The method differs from the method of the fifth aspect in that, in the fifth aspect, the first access network device is configured to request whether the terminal is in communication with the device, such as whether the terminal is currently in communication with the device, and in the sixth aspect, the second access network device is configured to request whether the terminal is in communication with the device and / or whether the terminal reports data from the device. The method of the sixth aspect can be applied to the case where the terminal reselects a cell from the first access network device to access the second access network device, and is advantageous in enabling the core network element to confirm whether the terminal continues to communicate with the device or reports the obtained data of the device. In this way, even if the second access network device cannot obtain the context information of the terminal communicating with the device from the source access network device (i.e., the first access network device) when the terminal is in an idle state, the core network element can confirm whether the terminal continues to communicate with the device or reports the obtained data of the device based on the reported identification information of the terminal.

[0061] Optionally, the other optional implementation manners and advantages of the aspect can refer to the related content of the fourth aspect, and will not be described in detail here.

[0062] In the seventh aspect, the present application further provides a communication method, which is based on the communication method of the first aspect to the sixth aspect, and in one possible implementation, is described from the perspective of the interaction between the terminal, the first access network device, the second access network device, and the core network element. The second access network device is the access network device accessed by the terminal after the terminal reselects a cell from the first access network device.

[0063] In the method, the first access network device determines a valid time during which the terminal communicates with the device in an idle state based on the first resource, and sends a first message to the terminal, the first message comprising the valid time. Correspondingly, the terminal receives the first message and communicates with the device based on the first resource within the valid time in the idle state.

[0064] As can be seen, in the method, the terminal communicates with the device based on the first resource within the valid time in the idle state, thereby enabling the terminal to perform A-IoT services in the idle state, which greatly improves the execution efficiency of A-IoT services compared with the case where the terminal only performs A-IoT services in the connected state.

[0065] In an alternative implementation, the terminal sends a message to the first access network device for requesting a resource for communicating with the device; the sent message comprises the identification information associated with the terminal communicating with the device; correspondingly, the first access network device receives the message and sends a message to the core network element for requesting confirmation of whether the terminal communicates with the device; wherein the message sent by the first access network device comprises the identification information; the core network element receives the message and sends a message to the first access network device for confirming that the terminal communicates with the device, or a message for confirming that the terminal does not communicate with the device. It can be seen that this implementation is beneficial for the terminal to request a resource from the first access network device again when the terminal does not complete the communication with the device within the effective time, and even if the first access network device does not save the context information of the terminal communicating with the device, the core network element can also send a message comprising the identification information to confirm whether the terminal communicates with the device, so as to facilitate the first access network device to allocate a resource for the terminal to communicate with the device again.

[0066] Optionally, the first access network device receives the message from the core network element for confirming that the terminal communicates with the device, and allocates a resource for the terminal to communicate with the device. The first access network device receives the message from the core network element for confirming that the terminal does not communicate with the device, and sends a service completion indication to the terminal, so that the terminal ends the communication with the device.

[0067] In an alternative implementation, the terminal sends a message to the first access network device for requesting to report data of the device, and the sent message comprises the identification information; correspondingly, the first access network device receives the message and sends a message to the core network element for requesting confirmation of whether the terminal communicates with the device; wherein the message sent by the first access network device comprises the identification information; the core network element receives the message and sends a message to the first access network device for confirming that the terminal communicates with the device, or a message for confirming that the terminal does not communicate with the device. It can be seen that this implementation is beneficial for the terminal to request the first access network device to report data when the terminal completes the communication with the device within the effective time, and even if the first access network device does not save the context information of the terminal communicating with the device, the core network element can also send a message comprising the identification information to confirm whether the terminal communicates with the device, so as to facilitate the first access network device to instruct the terminal to report the obtained data.

[0068] Optionally, the first access network device receives the message for confirming that the terminal communicates with the device, and instructs the terminal to report data of the device. The first access network device receives the message for confirming that the terminal does not communicate with the device, and sends a service completion indication to the terminal, so that the terminal ends the communication with the device.

[0069] In an alternative implementation, the terminal sends a message to the second access network device for requesting resources for communicating with the device according to the area associated with the second cell, or sends a message to the second access network device for requesting whether to report data from the device; correspondingly, the second access network device receives the message and sends a message to the core network element for requesting confirmation of whether the terminal communicates with the device; correspondingly, the core network element receives the message and sends a message to the second access network device for confirming that the terminal communicates with the device or for confirming that the terminal does not communicate with the device. The message received by the second access network device from the terminal and the message sent by the second access network device to the core network element both include the identification information.

[0070] It can be seen that, in this implementation, when the terminal reselects to the second cell in the idle state and accesses the second access network device, the second access network device does not save the context information of the terminal communicating with the device, and the second access network device can request the core network element to confirm whether the terminal communicates with the device based on the identification information. That is, in this implementation, the terminal judges whether to continue to communicate with the device after reselecting the cell in the idle state by itself.

[0071] Optionally, in each of the above implementations, the core network element determines the A-IoT service associated with the identification information, or determines the terminal communicating with the device associated with the identification information, performs authorization judgment on the terminal, and if the terminal has the permission to perform the A-IoT service or it is determined that the terminal is communicating with the device, sends a message to the first access network device for confirming that the terminal communicates with the device; if the terminal does not have the permission to perform the A-IoT service or it is determined that the terminal does not communicate with the device, sends a message to the first access network device for confirming that the terminal does not communicate with the device.

[0072] In another alternative implementation, the terminal sends a message to the second access network device for requesting whether to communicate with the device and / or whether to report data from the device; correspondingly, the second access network device receives the message and sends a message to the core network element for requesting whether the terminal communicates with the device and / or whether the terminal reports data from the device; the core network element receives the message and sends a message to the second access network device: a message for confirming that the terminal communicates with the device; a message for confirming that the terminal reports data from the device; or a message for confirming that the terminal does not communicate with the device and does not report data from the device. The message received by the second access network device and the message sent by the second access network device both include the identification information.

[0073] The embodiment is beneficial for the terminal to request the core network to determine whether the terminal continues to communicate with the device and whether to report data after the terminal reselects the cell in the idle state. In addition, even if the terminal reselects the second cell in the idle state, the second access network device does not save the context information of the terminal communicating with the device, and the second access network device can request the core network element to confirm whether the terminal continues to communicate with the device and / or whether to report data of the device based on the identification information.

[0074] Optionally, the second access network device allocates resources for the terminal to communicate with the device when receiving the message for confirming the terminal to communicate with the device; instructs the terminal to report data of the device when receiving the message for confirming to report data; and instructs the terminal to complete communication with the device, i.e., stop the A IoT service, when receiving the message for confirming that the terminal does not communicate with the device and does not report data of the device.

[0075] In another optional embodiment, the terminal sends a message for requesting whether to report data from the device to the second access network device; correspondingly, the second access network device receives the message and sends a message for requesting whether the terminal reports data from the device to the core network element; the core network element receives the message and sends a message for confirming that the terminal reports data from the device or a message for confirming that the terminal does not report data from the device to the second access network device. The message received by the second access network device and the message sent by the second access network device both contain identification information.

[0076] In the embodiment, the terminal does not continue to communicate with the device by default when reselecting the second cell in the idle state, and can request whether to report obtained data. Optionally, the terminal can also release context information of communication with the device, such as a valid time and / or resources for communication with the device.

[0077] In another optional embodiment, the terminal releases context information of communication with the device and / or deletes data from the device. It can be seen that in the embodiment, the terminal stops communicating with the device by default when reselecting the second cell in the idle state.

[0078] The seventh aspect can refer to the related content of the first aspect to the sixth aspect for other optional embodiments and beneficial effects, which will not be described in detail here.

[0079] It should be noted that in the present application, the message and / or information sent by the first access network device to the terminal can include or indicate one or more of the following: a valid time, a first resource, or an indication of the terminal communicating with the device in the idle state. For example, the present application can also provide one or more communication methods.

[0080] The application further provides a communication method, in which a terminal receives a first message from a first access network device, the first message comprising a first resource for the terminal to communicate with the device; and the terminal communicates with the device according to the first resource in an idle state.

[0081] The application further provides a communication method, in which a terminal receives a first message from a first access network device, the first message comprising indication information for the terminal to communicate with the device in an idle state; and the terminal communicates with the device in the idle state.

[0082] The application further provides a communication method, in which a terminal receives a first message from a first access network device, the first message comprising indication information for the terminal to communicate with the device in an idle state and a first resource for the terminal to communicate with the device; and the terminal communicates with the device according to the first resource in the idle state.

[0083] The application further provides a communication method, in which a terminal receives a first message from a first access network device, the first message comprising a first resource and a validity time for the terminal to communicate with the device using the first resource; and the terminal communicates with the device according to the first resource within the validity time in an idle state.

[0084] The application further provides a communication method, in which a terminal receives a first message from a first access network device, the first message comprising a first resource, a validity time for the terminal to communicate with the device using the first resource, and indication information for the terminal to communicate with the device in an idle state; and the terminal communicates with the device according to the first resource within the validity time in the idle state.

[0085] It can be seen that, in the above communication method, after receiving the first message, the terminal can enter the idle state to communicate with the device and perform A-IoT services, thereby improving the execution efficiency of A-IoT services. In addition, the optional implementation of the above communication method can also refer to the related content described in the first aspect to the sixth aspect, which will not be described in detail here.

[0086] Optionally, the indication for the terminal to communicate with the device in the idle state can be an indication for allowing the terminal to communicate with the device in the idle state. The indication for the terminal to communicate with the device in the idle state can be replaced by an indication for the terminal to perform A-IoT services in the idle state, or an indication for the terminal to continue to use the first resource in the idle state, or an indication for the terminal to continue to use the first resource, etc.

[0087] Optionally, the resource used by the terminal to communicate with the device in the idle state and the resource used by the terminal to communicate with the device in the connected state can be the same or different, or partially the same, and can be indicated separately or together.

[0088] In an eighth aspect, the present application provides a communication apparatus, which has the function of implementing any one of the first aspect to the sixth aspect or the optional implementation of any one of the first aspect to the sixth aspect. For example, the communication apparatus includes a module or unit or means corresponding to the operation related to the function of any one of the first aspect to the sixth aspect or the optional implementation of any one of the first aspect to the sixth aspect. The module or unit or means can be implemented by software, or by hardware, or by software and hardware together.

[0089] In a ninth aspect, the present application provides a communication apparatus, which includes an interface circuit and one or more processors. The one or more processors are coupled to a memory. The memory is used to store part or all of the computer program or instructions necessary for implementing the function related to any one of the first aspect to the sixth aspect or the optional implementation of any one of the first aspect to the sixth aspect. The one or more processors can execute the computer program or instructions, when the computer program or instructions are executed, so that the communication apparatus implements the method in any one of the first aspect to the sixth aspect or the optional implementation of any one of the first aspect to the sixth aspect. The interface circuit is used to implement the communication function within the communication apparatus and / or the communication function of the communication apparatus with other devices or components.

[0090] In a possible design, the processor is used to communicate with other devices or components through the interface circuit.

[0091] In a possible design, the communication apparatus can further include the memory.

[0092] The communication apparatus can be a terminal, or a communication / processing module in the terminal, or a chip responsible for communication function such as a modem chip (also known as a baseband chip) or a SoC or SIP chip containing a modem module in the terminal, or a circuit or chip responsible for processing function (such as a GPU) in the terminal. The communication apparatus can be a network device, or a communication / processing module in the network device, or a chip responsible for communication function such as a modem chip (also known as a baseband chip) or a SoC or SIP chip containing a modem module in the network device, or a circuit or chip responsible for processing function (such as a GPU) in the network device.

[0093] In a tenth aspect, the present application provides a communication system, which comprises a first communication device and a second communication device; the first communication device is configured to perform the method described in the first aspect or any possible implementation manner of the first aspect, and the second communication device is configured to perform the method described in the second aspect or any possible implementation manner of the second aspect. Optionally, the communication system further comprises a third communication device, which is configured to perform the method described in the third aspect or any possible implementation manner of the third aspect, or is configured to perform the method described in the fourth aspect or any possible implementation manner of the fourth aspect. Optionally, the communication system further comprises a core network element, which is configured to perform the method described in the fifth aspect or any possible implementation manner of the fifth aspect, or is configured to perform the method described in the sixth aspect or any possible implementation manner of the sixth aspect.

[0094] In an eleventh aspect, the present application provides a computer readable storage medium, which stores computer readable instructions, when a computer reads and executes the computer readable instructions, the computer is caused to perform the method in any possible implementation manner of the first aspect to the sixth aspect.

[0095] In a twelfth aspect, the present application provides a computer program product, when a computer reads and executes the computer program product, the computer is caused to perform the method in any possible implementation manner of the first aspect to the sixth aspect. BRIEF DESCRIPTION OF DRAWINGS

[0096] FIG. 1 is a schematic diagram of a 5G communication system architecture to which the present application can be applied;

[0097] FIG. 2 is a schematic diagram of a framework of an open access network;

[0098] FIG. 3 is a schematic diagram of an architecture of an ORAN device;

[0099] FIGS. 4 to 7 are schematic diagrams of network architectures of A-IoT technology;

[0100] FIGS. 8 to 14 are schematic diagrams of flow of a communication method according to an embodiment of the present application;

[0101] FIG. 15 is a schematic diagram of a structure of a communication device according to an embodiment of the present application;

[0102] FIG. 16 is a schematic diagram of a structure of a terminal according to an embodiment of the present application. DETAILED DESCRIPTION

[0103] The application can be applied to various communication systems, including but not limited to: a long term evolution (LTE) system, a 5th Generation (5G) system such as a new radio access technology (NR), a network integrating multiple systems, an Internet of Things system, a vehicle-to-vehicle network system, an open-radio access network (O-RAN) system, and a future communication system such as a 6th Generation (6G) system, and the like.

[0104] FIG. 1 is a schematic diagram of a 5G communication system architecture to which the application can be applied, where the 5G communication system architecture is a 5G network infrastructure, network functions are decoupled based on modularization, and decoupled network functions (NFs) can be independently scaled, independently evolved, and deployed on demand. Service-based interfaces are used between all NFs in the control plane, the same service can be called by multiple NFs, the coupling degree of interface definition between NFs is reduced, and finally the network functions are customized on demand, and different business scenarios and requirements are flexibly supported. As shown in the architecture of FIG. 1, the network element in the dashed box is a service-based NF network element, the interface between the NF network elements is a service-based interface, and the interaction message is a service-based message. The architecture can include an access network and a core network, and optionally, a user equipment (UE) can also be included.

[0105] The UE is a device with wireless transceiver function, which can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; can also be deployed on the water surface (such as ships, etc.); can also be deployed in the air (such as airplanes, balloons and satellites, etc.). The UE can be a mobile phone, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a vehicle-mounted terminal device, a wireless terminal in self driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, a wearable terminal device, etc. The UE can also be called terminal, terminal device, access terminal device, vehicle-mounted terminal, industrial control terminal, UE unit, UE station, mobile station, mobile station, remote station, remote terminal device, mobile device, UE agent or UE apparatus, etc. The UE can also be fixed or mobile. Alternatively, the device for implementing the function of the terminal can be a terminal, or a device capable of supporting the terminal to implement the function, such as a chip system, or a communication module, or a modem, etc., which can be installed in the terminal. In the embodiments of the present application, the chip system can be composed of a chip, or can include a chip and other discrete devices. In the technical solutions provided in the embodiments of the present application, the device for implementing the function of the terminal is the terminal, and taking the terminal as an example of the UE, the technical solutions provided in the embodiments of the present application are described. The embodiments of the present application do not limit the specific technology and specific device form of the terminal device. In a possible implementation manner, the UE can be used to act as a base station. For example, the UE can act as a scheduling entity, which provides sidelink signals between UEs in V2X, D2D or P2P, etc., without relaying communication signals through the base station. In a possible implementation manner, the UE can also be used to act as a relay node. For example: the UE can act as a relay device or an integrated access and backhaul (IAB) node, which is used to provide wireless backhaul service for terminal devices.

[0106] The access network is used to implement access-related functions, can provide network access functions for authorized users in a specific area, and can determine transmission tunnels of different qualities to transmit user data according to the level of a user, the demand of a service, and the like. The access network forwards control signals and user data between a terminal device and a core network. The access network can include access network devices. For example, in this application, information exchanged between a terminal device and a network element of a core network can be forwarded through an access network device. The access network device is a device that provides access for a terminal device, and can include a radio access network (RAN) device and an access network (AN) device. The RAN device is mainly responsible for functions such as radio resource management, quality of service (QoS) management, data compression, and encryption on the air interface side. The RAN device can include various forms of base stations (BSs), such as macro base stations, micro base stations (also referred to as small stations), relay stations, access points, balloon stations, and the like.

[0107] In systems employing different radio access technologies, the name of the device with base station functionality can be different. Exemplarily, the base station involved in the embodiments of the present application can be a base station in 5G, a base station in a 6G mobile communication system, an access network device or a module of an access network device in an open radio access network (O-RAN) system, a base station in a future mobile communication system or an access node in a WiFi system, or an evolved node B (eNB) in LTE, etc. Among them, the base station in 5G can also be called a transmission reception point (TRP) or a 5G base station (gNB). The base station can also be replaced by the following names, such as: a wireless access point, a node B (nodeB), a transmitting point (TP), a master station MeNB, a secondary station SeNB, a multi-standard radio (MSR) node, a home base station, a network controller, an access node, a wireless node, an access point (AP), a transmission node, a transceiver node, a baseband unit (BBU), a remote radio unit (RRU), an active antenna unit (AAU), a remote radio head (RRH), a centralized unit (CU), a distributed unit (DU), a positioning node, an IAB donor (IAB donor), etc. The base station can be fixed or mobile. For example, a helicopter or a drone can be configured to act as a mobile base station, and one or more cells can move according to the location of the mobile base station. In other examples, a helicopter or a drone can be configured to serve as a device that communicates with another base station.

[0108] Optionally, the RAN device can also be a device including a CU, or a DU, or a device including a CU and a DU, or a control plane CU node (central unit-control plane (CU-CP)) and a user plane CU node (central unit-user plane (CU-UP)) and a DU node. For example, the RAN device can include a gNB-CU-CP, a gNB-CU-UP and a gNB-DU.

[0109] In some deployments, wireless access is assisted by multiple RAN devices cooperating to serve a terminal, with different RAN devices implementing parts of the functionality of a base station. For example, a RAN node can be a CU, a DU, a CU-CP, a CU-UP, or a radio unit (RU), etc. A CU and a DU can be separately deployed or can be included in the same network element, e.g., a BBU. An RU can be included in a radio device or a radio unit, e.g., in a RRU, an AAU, or a RRH.

[0110] A RAN device can support one or more types of fronthaul interface, with different fronthaul interfaces corresponding to DUs and RUs having different functionalities. If the fronthaul interface between a DU and an RU is a common public radio interface (CPRI), the DU is configured to implement one or more of the baseband functionalities, and the RU is configured to implement one or more of the radio frequency functionalities. If the fronthaul interface between a DU and an RU is another interface, which, compared to the CPRI, moves one or more of the partial baseband functionalities of the downlink, e.g., precoding, digital beamforming (BF), or inverse fast Fourier transform (IFFT) / add cyclic prefix (CP), or one or more of the partial baseband functionalities of the uplink, e.g., digital beamforming (BF), or fast Fourier transform (FFT) / remove cyclic prefix (CP), from the DU to the RU. In one possible implementation, the interface can be an enhanced common public radio interface (eCPRI). Under the eCPRI architecture, the split between the DU and the RU is different, corresponding to different categories (Cat) of eCPRI, e.g., eCPRI Cat A, B, C, D, E, F.

[0111] Taking eCPRI Cat A as an example, for downlink transmission, with layer mapping as the cut, the DU is configured to implement layer mapping and one or more functions (i.e., one or more of encoding, rate matching, scrambling, modulation, layer mapping) before layer mapping, while other functions (e.g., one or more of resource element (RE) mapping, digital beamforming (BF), or inverse fast Fourier transform (IFFT) / adding cyclic prefix (CP)) after layer mapping are implemented in the RU. For uplink transmission, with de-RE mapping as the cut, the DU is configured to implement de-mapping and one or more functions (i.e., one or more of decoding, de-rate matching, de-scrambling, de-modulation, inverse discrete Fourier transform (IDFT), channel equalization, de-RE mapping) before de-mapping, while other functions (e.g., one or more of digital BF or fast Fourier transform (FFT) / CP removal) after de-mapping are implemented in the RU. It can be understood that the function description of the DU and the RU corresponding to various types of eCPRI can refer to the eCPRI protocol, which is not described here.

[0112] In a possible design, the processing unit in the BBU for implementing baseband functions is referred to as a base band high (BBH) unit, and the processing unit in the RRU / AAU / RRH for implementing baseband functions is referred to as a base band low (BBL) unit.

[0113] In different systems, the CU (or CU-CP and CU-UP), DU or RU can also have different names, but those skilled in the art can understand their meanings. For example, in an open ORAN system, the CU can also be referred to as an O-CU (open CU), the DU can also be referred to as an O-DU, the CU-CP can also be referred to as an O-CU-CP, the CU-UP can also be referred to as an O-CU-UP, and the RU can also be referred to as an O-RU. Any of the CU (or CU-CP, CU-UP), DU and RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0114] In the embodiments of the present application, the apparatus for implementing the function of the network device can be the network device; or can be an apparatus capable of supporting the network device to implement the function, such as a chip system, a hardware circuit, a software module, or a hardware circuit plus a software module. The apparatus can be installed in the network device or used in matching with the network device. In the embodiments of the present application, only the apparatus for implementing the function of the network device is taken as an example for description, and the scheme of the embodiments of the present application is not limited in this way.

[0115] The core network is responsible for maintaining the subscription data of the mobile network, and provides the UE with functions such as session management, mobility management, policy management, and security authentication. The core network can include the following network elements: a user plane function (UPF) network element, an authentication server function (AUSF) network element, an access and mobility management function (AMF) network element, a session management function (SMF) network element, a network slice selection function (NSSF) network element, a network exposure function (network exposure function, NEF) network element, a network function repository function (NF repository function, NRF) network element, a policy control function (policy control function, PCF) network element, a unified data management (unified data management, UDM) network element, a unified data repository (unified data repository, UDR) network element, a location management function (location management function, LMF) network element, a home gateway mobile location center (home gateway mobile location center, HGMLC), a visited gateway mobile location center network element (visited gateway mobile location center, VGMLC), and an application function (application function, AF) network element.

[0116] AMF network element, mainly responsible for mobility management in the mobile network, such as user location update, user registration network, user handover, etc. SMF network element, mainly responsible for session management in the mobile network, such as session establishment, modification, release. Specific functions such as allocating an internet protocol (IP) address for a user, selecting a UPF that provides message forwarding functions, etc. UPF network element, mainly responsible for forwarding and receiving user data, which can receive user data from a data network and transmit it to a UE through an access network device; it can also receive user data from a UE through an access network device and forward it to a data network. PCF network element, mainly supports providing a unified policy framework to control network behavior, providing policy rules to control layer network functions, and responsible for obtaining user subscription information related to policy decision. PCF network element can provide policies such as quality of service (QoS) policy, slice selection policy, etc. to AMF network element and SMF network element. AUSF network element, used to perform security authentication of UE. NSSF network element, used to select network slices for UE. NEF network element, mainly used to support the opening of capabilities and events. UDM / UDR network element, used to store user data such as subscription data, authentication / authorization data, etc. AF network element, mainly supports interaction with the 3GPP core network to provide services, such as affecting data routing decisions, policy control functions, or providing third-party services to the network side.

[0117] NRF network element, mainly provides service registration, discovery and authorization, and maintains available network function (NF) instance information, which can realize on-demand configuration of network functions and services and interconnection between NFs. Among them, service registration means that NF network elements need to be registered with the NRF network element before they can provide services. Service discovery means that when NF network elements need other NF network elements to provide services for them, they need to perform service discovery through the NRF network element first to discover the desired NF network elements that provide services for them. For example, NF network element 1 needs NF network element 2 to provide services for it, and needs to perform service discovery through the NRF network element first to discover NF network element 2.

[0118] Among them, the data network (data network, DN) is used to provide business services for users, which can be a private network such as a local area network, or an external network not under the control of an operator, such as the Internet, or a dedicated network jointly deployed by operators, such as an IP multimedia subsystem (IP multimedia subsystem, IMS) network. The UE can access the DN through the established protocol data unit (protocol data unit, PDU) session.

[0119] In addition, in the 5G communication system architecture shown in FIG. 1, the UE and the AMF can interact through the N1 interface, and the interactions between other network function network elements are similar, such as the interaction between the AN and the AMF through the N2 interface, the N3 interface supports the selective activation / deactivation of the user plane connection; the SMF network element and the UPF network element interact through the N4 interface, and the UPF network element and the DN interact through the N6 interface. The control plane can use a service interface to interact between all NFs. For example, the LMF network element and other network function network elements can interact through the service interface N1mf, and the interface between the LMF network element and the AMF network element is NL1. The NSSF network element and other network function network elements can interact through the service interface Nnssf. The NEF network element and other network function network elements can interact through the service interface Nnef. The NRF network element and other network function network elements can interact through the service interface Nnrf. The PCF network element and other network function network elements can interact through the service interface Npcf. The UDM network element and other network function network elements can interact through the service interface Nudm. The AF network element and other network function network elements can interact through the service interface Naf. The AUSF network element and other network function network elements can interact through the service interface Nausf. The AMF network element and other network function network elements can interact through the service interface Namf. The SMF network element and other network function network elements can interact through the service interface Nsmf.

[0120] Optionally, the 5G communication system architecture can also use the non-3GPP system architecture in 5G, allowing terminal devices and 3GPP core networks to interconnect and interoperate using non-3GPP technologies. Non-3GPP technologies can include, but are not limited to, Wireless Fidelity (Wi-Fi), Worldwide Interoperability for Microwave Access (WiMAX), Code Division Multiple Access (CDMA) networks, etc.

[0121] The present application is also applicable to an open RAN (ORAN) architecture. FIG. 2 is a schematic diagram of a framework of an open RAN. An ORAN system can include an access network device, a terminal device, and a core network device. The ORAN system can include other components in addition to the components shown in the figure. As shown in FIG. 2, an access network device (which can be an eNB or a gNB or a next-generation access network device) communicates with a core network (CN) device through a backhaul link and communicates with a user equipment (UE) through an air interface. For example, a BBU in the access network device communicates with the core network through a backhaul link, and a RU in the access network device communicates with at least one UE through an air interface. The BBU communicates with at least one RU through a front-haul link. The BBU and the RU can be co-located or not co-located. The BBU includes at least one of at least one CU and at least one DU, which can communicate through at least one mid-haul link. In the ORAN system, the CU can also be an O-CU, and the DU can also be an O-DU.

[0122] FIG. 3 is a schematic diagram of a framework structure involving a RIC module in an ORAN architecture. As shown in FIG. 3, a communication system includes a radio access network intelligent controller (RIC). For example, the RIC can be used to implement AI-related functions. The RIC includes a near-real time RIC (near-RT RIC) and a non-real time RIC (Non-RT RIC). The non-real time RIC mainly processes non-real-time information, such as data that is not sensitive to latency, which can be on the order of seconds. The real-time RIC mainly processes near-real-time information, such as data that is relatively sensitive to latency, which can be on the order of tens of milliseconds.

[0123] The near-real-time RIC is used for model training and inference. For example, it is used to train an artificial intelligence (AI) model and perform inference using the AI model. The near-real-time RIC can obtain network-side and / or terminal-side information from RAN nodes (such as CUs, CU-CPs, CU-UPs, DUs, and / or RUs) and / or terminals. This information can be used as training data or inference data. The near-real-time RIC can deliver inference results to RAN nodes and / or terminals. The CUs and DUs, and / or the DUs and RUs, can exchange inference results. For example, the near-real-time RIC delivers inference results to a DU, which then sends them to a RU.

[0124] The non-real-time RIC is also used for model training and inference. For example, the non-real-time RIC is used for training an AI model, and inference is performed using the model. The non-real-time RIC can obtain network-side and / or terminal-side information from a RAN node (e.g., a CU, a CU-CP, a CU-UP, a DU, and / or a RU) and / or a terminal. The information can be used as training data or inference data, and the inference result can be delivered to the RAN node and / or the terminal. The inference result can be exchanged between a CU and a DU, and / or between a DU and a RU, for example, the non-real-time RIC delivers the inference result to the DU, which then delivers it to the RU.

[0125] The near-real-time RIC and the non-real-time RIC can also be separately provided as a network element, respectively. The near-real-time RIC and the non-real-time RIC can also be part of other devices, for example, the near-real-time RIC is provided in a RAN node (e.g., a CU, a DU), and the non-real-time RIC is provided in an OAM, a cloud server, a core network device, or another network device.

[0126] In a communication system, network elements are connected through interfaces (e.g., an NG interface, an Xn interface), or air interfaces. One or more AI modules are provided in one or more of the network elements, such as a core network element, an access network device, a terminal, or a device in an OAM. The access network device can be a separate RAN node, or can include multiple RAN nodes, such as a CU and a DU. The CU and / or the DU can also be provided with one or more AI modules. Optionally, the CU can be split into a CU-CP and a CU-UP, and the CU-CP and / or the CU-UP can be provided with one or more AI modules.

[0127] An AI module is used to implement a corresponding AI function. AI modules deployed in different network elements can be the same or different. An AI module can implement different functions according to different parameter configurations of a model of the AI module. An AI module can have one or more models. A model can infer an output including one parameter or multiple parameters. The learning process, the training process, or the inference process of different models can be deployed in different nodes or devices, or can be deployed in the same node or device.

[0128] Based on the infrastructure in a communication system, such as an A-IoT technology scenario. The device that communicates with a terminal in this application can be a tag or an A-IoT terminal (or an A-IoT device). Among them, the A-IoT terminal is a separate device that implements the function of the tag, or the tag and the terminal device are integrated together, that is, the tag is part of the terminal device.

[0129] For the A-IoT technology, in an implementation, a reader and a tag (or a label, an electronic label, a label device) can be included. The reader and the tag interact with each other to exchange information, so as to manage the tag. The reader and the tag perform non-contact data communication. The tag has simple functions and needs to rely on the excitation of the reader to send information, that is, the tag converts the wireless signal sent by the reader into energy, and drives itself to work by using the energy. The tag is a micro wireless transceiver device, mainly including a built-in tag device antenna, a coupling element, and a chip. The chip of the tag has a storage space that can support the reader to read or write tag data. After the tag receives the radio frequency signal sent by the reader through the antenna, the tag can realize the coupling of the radio frequency signal through the coupling element, and then in the coupling channel, the tag can provide energy for the chip and feed back the data stored in the chip to the reader through the antenna. For example, the reader can send a carrier signal to the tag, the tag receives the carrier signal through the antenna, and the tag reflects the transmission of the reflected signal based on the carrier signal. The tag can adjust the information to be transmitted in the reflected signal. Through the above manner, the tag uses a low-precision low-power consumption medium-low frequency ring oscillator or a completely non-oscillator to receive the downlink signal, so that the power consumption of the tag in the downlink reception can be further reduced.

[0130] The tag supports micro-watt or hundreds of micro-watt power consumption, and cannot support complex design. The main application scenario of the A-IoT technology is identity recognition, and further can be used for data reading and writing. The tag has the following characteristics: the tag design is simple, and the application layer and air interface signaling are designed together; the tag supports micro-watt or hundreds of micro-watt power consumption, and cannot support complex design and complex measurement; when multiple tags communicate, time division multiplexing is used, and multiple tags use serial reading mode. The frequency domain and code domain are not supported, and the parallel performance is poor. In addition, the tag also has a low power consumption characteristic, for example, the power consumption of different types of tags is introduced as follows: passive tag (or passive tag): ~ 1 μW power consumption, the passive tag itself has no energy storage capability, and the energy of the received and transmitted signals is entirely derived from the radio frequency energy of the reader. Uplink transmission needs to rely on reflection communication, and needs the reader to send a carrier signal to trigger the passive tag to send a reflection signal, and uses radio frequency energy to send the uplink signal to the reader; semi-passive tag or semi-passive tag: ~ 100 μW power consumption, compared with the passive tag, the semi-passive tag can store a part of energy (such as using a capacitor), so the transmission power consumption can be greater than that of the passive tag, and the communication also relies on reflection communication, but the communication capability is stronger than that of the passive tag (transmission rate, etc.); active tag or active tag: ~ 50 mW power consumption, the active tag itself has a battery and can actively send signals, and does not rely on reflection signals for communication, and has stronger communication capability. Among them, the passive tag and the semi-passive tag can use a reflection (backscatter) based communication mode, and the active tag uses a communication mode of actively generating a carrier.

[0131] In another classification manner, the tag can be divided into the following three types of devices: device A: no energy storage, cannot independently generate signals, and uses backscatter transmission signals; device B: has energy storage, but cannot independently generate signals, uses backscatter transmission signals, and the stored energy can amplify the reflection signals; device C: has energy storage, can independently generate signals, and has active radio frequency elements for transmission. The tag uses a low-precision, low-power consumption medium-low frequency ring oscillator or a completely non-local oscillator to receive a downlink signal. When the tag works, the communication energy and carrier come from the reader supply, and the communication is based on reflection carrier.

[0132] A-IoT technology is to apply A-IoT technology to a mobile communication system, for example, to a 5G system, and the reader and the tag device are both devices in the mobile communication system. The communication network composed of the reader and the tag based on the cellular network infrastructure can be referred to as a passive / passive internet of things (IoT) network or an ambient internet of things (A IoT or A-IoT). For example, the function of the reader can be implemented by an access network device such as a base station. The A-IoT terminal can be implemented by a terminal device in the cellular network, such as an extremely low-power, extremely low-complexity IoT terminal, i.e., a first type of terminal. Non-contact data communication can be performed between the access network device and the A-IoT terminal, so as to read information from the A-IoT terminal and / or write information to be stored into the A-IoT terminal. It can be understood that, in the present application, the access network device can have the function of the reader; the A-IoT terminal has the function of the tag, or the A-IoT terminal can be a terminal device in the A IoT or IoT system. The reader can be a handheld or fixed reader or writer of A-IoT terminal information, and can also be understood as a device in communication with the A-IoT terminal. The reader can be a terminal device, an access network device, or a device with reading and writing functions. The reader can also be an IAB node or a relay node. Optionally, the related forms of the access network device and the terminal device can be referred to the foregoing, and will not be described in detail here.

[0133] In the present application, the terminal can perform a first service in communication with the device. The first service is related to the device and is a service currently being performed or to be performed. The first service includes one or more of the following: inventory service, command service, positioning service, sensing service, proximity, read service, write service, deactivation service, lock service, or security service (such as authentication, authorization, registration, etc.), or a new service type defined in the future, without limitation on the specific name. The service can also be replaced by task, or session, or request, or transaction, process, procedure, service, etc., and the name is not limited in the embodiments of the present application. Exemplarily, the first service can also be referred to as a first task, and the inventory service can also be referred to as an inventory task, or an inventory request, or an inventory procedure, or an inventory transaction, etc.

[0134] In the embodiments of the present application, the first service can also be a service related to a process (a process between the terminal and the device), such as at least one of the following: an access process, or a data transmission process, and the like, which can be understood as performing the first service as performing the corresponding process. The access process can be random access, such as contention-based random access, or contention-free random access. Alternatively, the access process can include reporting a device ID, such as the ID of the device in communication with the terminal. The data transmission process can be device-to-reader (D2R) uplink data transmission, reader-to-device (R2D) downlink data transmission, and the like. Alternatively, the data transmission process can also include reporting a device ID. Alternatively, the access process and the data transmission process are not strictly distinguished, and the two can also be combined for execution, such as in the access process, data transmission can also be performed, for example, contention-free random access, and the device can send D2R / uplink data in the first message. The terminal can process different processes of the first service. The first service can be associated with a service triggered by a core network element or an access network device, or can be associated with a process.

[0135] The following one or more of the first service is described by way of example:

[0136] Inventory service: The inventory service can also be referred to as an inventory operation, which can obtain the identification information of the device, for example, the reader can obtain the identification information of the device through query, acknowledgment (ACK) and the like. In order to facilitate inventory of the device, the device includes a total of 4 session identifiers S0-S3, and each session identifier corresponds to two inventory states A and B. The inventory state is indicated by an inventory flag (sessInventoried flag). When the reader selects a device, the select command sent to the device will include a session identifier, and the device will store the session identifier. When the reader performs the inventory service on the device, the query command sent to the device will include the session identifier, and at this time the device can flip the inventory state corresponding to the session identifier from A to B. If the reader sends the query command again to perform the inventory service, since the inventory state in the device is B, the device will not respond to the reader, thereby avoiding the same device being inventoried multiple times in a round of inventory cycle.

[0137] Read service: The read service can read the electronic product code (EPC) in the storage area of the device, the tag identifier (TID), the content stored in the reserved area of the device, or the content stored in the user storage area, and the like.

[0138] Write service: the write service can perform a write operation on the storage area of the device.

[0139] Inactivation service: the inactivation service can make the device never work.

[0140] Lock service: the lock service can lock the information of the device, which can prevent the read service or the write service from being performed on the device. Alternatively, the lock service can also lock the storage area, which can prevent or allow the read service or the write service from being performed on the storage area.

[0141] In one possible implementation, the network architecture of the A-IoT technology can include, but is not limited to, part or all of the architectures shown in FIG. 4, FIG. 5, FIG. 6a, FIG. 6b and FIG. 7.

[0142] The architecture shown in FIG. 4 includes an access network device (such as a base station) and an A-IoT terminal, the access network device has a reader / writer function, the access network device can communicate with the A-IoT terminal as a reader / writer, and the communication interface between the access network device and the A-IoT terminal is a uu interface (or an A-IoT-uu interface). As shown in FIG. 4, the A-IoT terminal directly communicates with the access network device in a bidirectional manner, and interacts with data and / or signaling under the first service.

[0143] FIG. 5 shows another network architecture of the A-IoT technology. As shown in FIG. 5, the communication system includes an access network device, an intermediate node and an A-IoT terminal. In the communication system, the intermediate node can serve as a relay node between the access network device and the A-IoT terminal, the A-IoT terminal transmits information to the intermediate node, and the intermediate node forwards the information to the access network device through a uu interface. Among them, the A-IoT terminal can be connected to the intermediate node through a uu interface, and the intermediate node is connected to the base station through a uu interface. Among them, the intermediate node can be an IAB node or a terminal device, the terminal device serves as a relay node between the access network device and the A-IoT terminal, the A-IoT terminal transmits information to the terminal device, and the terminal device forwards the information to the access network device through a uu interface.

[0144] In the present application, the communication system including the access network device, the auxiliary node and the A-IoT terminal can also be a split architecture system. In the system, the auxiliary node is a terminal device. In the communication system, the access network device and the A-IoT terminal can directly communicate with each other as shown in FIG. 6a and FIG. 6b. The access network device can also have the function of a reader-writer. As shown in FIG. 6a, there is an uplink connection between the A-IoT terminal and the access network device, and there is a downlink connection between the A-IoT terminal and the auxiliary node. The auxiliary node can transmit information to the A-IoT terminal, and the A-IoT terminal can forward the information to the access network device. Alternatively, as shown in FIG. 6b, there is a downlink connection between the A-IoT terminal and the access network device, and there is an uplink connection between the A-IoT terminal and the auxiliary node. The access network device can transmit information to the A-IoT terminal, and the A-IoT terminal can forward the information to the auxiliary node. The energy required by the A-IoT terminal to send information can be provided by an energy signal, which can come from the access network device, the auxiliary node or other devices. The energy signal can also be referred to as an excitation signal or a carrier signal.

[0145] In the split architecture system, the auxiliary node is a terminal device. In one implementation, the terminal device can send data to the A-IoT terminal. The terminal device or the access network device provides a carrier signal, the A-IoT terminal generates or sends an uplink signal according to the carrier signal, and sends the uplink signal to the access network device. The uplink signal can include data sent by the A-IoT terminal to the access network device. The data can be data of the A-IoT terminal itself or data received from the terminal device. In another implementation, the access network device can send data to the A-IoT terminal. The terminal device or the access network device provides a carrier signal, the A-IoT terminal generates a downlink signal according to the carrier signal, and sends the downlink signal to the terminal device. The downlink signal can include data sent by the A-IoT terminal to the terminal device. The data can be data of the A-IoT terminal itself or data received from the access network device.

[0146] In the direct connection architecture, the auxiliary node is a terminal device, and the A-IoT terminal and the access network device can directly transmit data. When the A-IoT terminal sends an uplink signal to the access network device, the carrier signal used to generate the uplink signal is provided by the terminal device.

[0147] FIG. 7 shows another network architecture of A-IoT technology. As shown in FIG. 7, the communication system includes a terminal device and an A-IoT terminal. The A-IoT terminal can be a separate device, or the A-IoT terminal can be integrated with the terminal device. In the communication system, the terminal device can have the function of a reader-writer, i.e., the terminal device can communicate with the A-IoT terminal as a reader-writer, and the terminal device and the A-IoT terminal can communicate through a sidelink.

[0148] Under the A-IoT architecture, the terminal in the connected state can implement or assist the network device and the device to perform the first service, cannot support the terminal in the idle state to perform the first service, and there is a problem of low efficiency of the first service execution, and cannot support the continuity of the first service execution.

[0149] The present application provides a communication method, which realizes the terminal in the idle state to perform the first service, improves the execution efficiency of the first service, and supports the continuity of the first service execution when the terminal changes from the connected state to the idle state. Taking the network architecture of A-IoT technology shown in FIG. 5 as an example, the intermediate node shown in FIG. 5 is a terminal. The access network device forwards a first message to the terminal through a uu interface, and the first message includes a first resource used by the terminal to communicate with a tag device in an idle state for a valid time; the terminal communicates with the A-IoT terminal according to the first resource within the idle state valid time, such as obtaining information of the A-IoT terminal; and the terminal forwards the information to the access network device through the uu interface.

[0150] It can be seen that the present application realizes the terminal in the idle state to perform the first service. In addition, compared with only performing the first service in the connected state, the execution efficiency of the first service is improved, and the continuity of the first service execution is also supported. The network side not only controls the configuration of the air interface resource in the IoT technology, but also can configure the valid time of the air interface resource, so as to realize the terminal in the idle state to perform the A-IoT service.

[0151] In addition, the present application considers the content of the network side controlling the configuration of the air interface resource in the IoT technology, and proposes some schemes for the terminal to communicate with the A-IoT terminal in the manner of terminal self-judgment, or core network element judgment, or terminal default, to support the mobility scenario of the terminal in the first service execution.

[0152] For the convenience of understanding the present application, some terms involved are simply introduced as follows.

[0153] 1. Terminal in idle state and device communication, identification information.

[0154] In the present application, the terminal communicates with the device in the idle state, which can be expressed as the terminal performs the first service in the idle state, or the terminal continues to use the first resource in the idle state, and the like. Correspondingly, the terminal does not communicate with the device in the idle state, which can be expressed as the terminal stops communicating with the device in the idle state, or the terminal does not perform the first service in the idle state, or the terminal does not use the first resource in the idle state, and the like. Wherein, the first resource is the air interface resource or the wireless resource used by the terminal to communicate with the device.

[0155] In the present application, the terminal communicates with the device can be expressed as the terminal performs the first service associated with the identification information; correspondingly, the terminal does not communicate with the device can be expressed as: the terminal stops communicating with the device, or the terminal stops the first service associated with the identification information.

[0156] The identification information is information used to identify the terminal communicating with the device, or information associated with the terminal communicating with the device, or information used to identify the first service. The terminal is in the idle state, and the access network device does not save the context information of the terminal communicating with the device. Based on the identification information, the associated terminal communicating with the device or the associated first service is obtained. The identification information includes at least one of the following: service identification associated with the terminal communicating with the device, session identification (session ID), task identification, inventory area, reader identification, or address of core network element, or device identification (device ID). Wherein, the core network element can be a tag management (TMF) element, or an ambient IoT management function (AIoTMF) element, or an A-IOT element, or an A-IOT management element.

[0157] In the embodiment of the present application, it is not limited that one service corresponds to one identification information, but one service corresponds to one flow to assign one identification information, and the next flow (such as the core network retriggering or "newly initiating" (not retransmitting) one paging, even if it is the same service type, it can be regarded as different identification information). Different identification information can correspond to different first services. For example, the core network element or the access network device initiates two inventory services, and the trigger / request messages (such as paging messages) corresponding to the two inventory services can carry different identification information. Optionally, the paging message can carry or be associated with the identification information.

[0158] Wherein, the session in the session identification can be replaced by task, or service, or request, or transaction, process, procedure, service, and the like, and the present application embodiment does not limit the name.

[0159] 2. first resource, validity time.

[0160] The first resource is a radio resource or a wireless resource for the terminal to communicate with the device. Optionally, the first resource includes a frequency domain resource and / or a time resource. Optionally, the first resource further includes a code domain, a coding mode, and a modulation mode, etc.

[0161] The configuration of the frequency domain resource is indicated by a frequencyBandList field (NR or Evolved UMTS Terrestrial Radio Access Network (E-UTRAN)) for example, which indicates a frequency band. Optionally, one or more resource blocks (RBs) are configured by using one or more of the following fields: an absoluteFrequencyPointA field, a locationAndBandwidth field, and a sub-carrier space (SCS) interval definition (SCS-SpecificCarrier) field.

[0162] The configuration of the time domain resource can be indicated by a Duration field for example, which indicates a time domain resource for the first service. The coding mode indicates one or more of the following for example: Manchester coding, polar code, convolutional code, etc. The modulation mode indicates one or more of the following for example: on-off keying (OOK), quadrature phase shift keying (QPSK), orthogonal frequency division multiplexing (OFDM), etc.

[0163] In an optional implementation, the first resource is a resource pool at a region level, i.e., a plurality of cells share one or more resource pools; or, a resource at a cell level, i.e., a plurality of terminals accessing the same cell can share the resource to perform the first service; or, a resource shared by multiple stations, etc. The first resource can be pre-configured.

[0164] In another optional implementation, the first resource is a resource configured by the access network device for the terminal, i.e., a per-UE resource.

[0165] In yet another optional implementation, the first resource and / or the validity time are determined by a core network element, which can be directly or through the access network device indicated to the terminal.

[0166] In another optional embodiment, the first resource and / or the validity time is calculated or determined by the RIC in the ORAN architecture according to prior information, so as to make no interference between the NR and A-IoT communication, or no interference between A-IoT communications of different terminals. In this embodiment, the RIC can flexibly configure the first resource and / or the validity time according to historical data. Optionally, in this embodiment, the RIC needs to additionally collect historical data related to terminal and device communication. In this embodiment, the first resource and / or the validity time calculated or determined by the RIC can be sent to the DU by the CU and indicated to the terminal by the DU.

[0167] The validity time is the time length of the first resource for terminal and device communication, or the time length allowed by the first access network device for the terminal to communicate with the device according to the first resource, or the time allowed to use the first resource. The validity time can be referred to as the effective time length (or effective time) of the first resource, the activation time length (or activation time); or the validity time is the timing length of a timer, which is started when the terminal receives the first message or when the terminal enters the idle state, and the terminal stops communicating with the device according to the first resource when the timer times out; or the validity time is the timing length of a timer, which starts timing when the terminal receives the first message or when the terminal enters the idle state, and stops communicating with the device according to the first resource when the timing time is up.

[0168] 3. Area.

[0169] The area involved in the present application includes at least one of the following: an area associated with terminal and device communication, or an area associated with a cell. The area associated with terminal and device communication can be a service area, a coverage area, a service area, an inventory area, an area associated with a first service, or an area associated with the above-mentioned identification information. The area associated with a cell can be a service area, a coverage area, a location area, or an area associated with a list of cells.

[0170] In the present application, the area associated with terminal and device communication can include a plurality of location areas corresponding to a plurality of cell identifications, wherein the location area corresponding to the cell identification is an area related to the location, or an area associated with a cell.

[0171] The area involved in the present application can be indicated by physical identification information or geographical area information. The physical identification information can be a cell identification list (cell ID list), a physical cell identification list (PCI list), or base station identification information (list), etc. The geographical area information can be a latitude and longitude range, a geographical area name, a geographical area identification, or a geographical area index, etc.

[0172] 4. Idle state, connected state of the terminal.

[0173] In the case that the terminal is in the RRC idle state, the access network device does not save the access stratum (AS) context related to the terminal, such as the RRC context, and there is no RRC connection between the terminal and the access network device, in other words, the access network device is not aware of the existence of the terminal. The behaviors that the terminal can perform in the RRC idle state include: Public Land Mobile Network (PLMN) selection, receiving broadcast system messages, cell reselection, receiving paging, etc.

[0174] In the case that the terminal is in the RRC connected state, the access network device establishes and saves the access stratum context related to the terminal, such as the RRC context, and there is no RRC connection between the terminal and the access network device, and the access network device can be aware of the existence of the terminal. The behaviors that the terminal can perform in the RRC connected state include: the core network establishes a connection with the terminal (such as a next generation-radio access network (NG-RAN) connection), the access network device saves the AS context of the terminal, the access network device knows which cell the terminal belongs to, the terminal transmits (unicast) data with the network device (the access network device and / or the core network device), etc.

[0175] 5. Uplink RRC message, MAC CE, downlink RRC message, NAS message, PDU session-based message.

[0176] In this application, the message or information carried by the message sent by the terminal to the access network device can be or carried in the uplink RRC message (UE to Network) or MAC CE. The message or information carried by the message sent by the access network device to the terminal can be or carried in the downlink RRC message (Network to UE). In addition, the interface between the first access network device and the core network element is the next generation (NG) interface, and the message or information carried by the message exchanged between the two is the next generation application protocol (NG AP) message.

[0177] An uplink RRC message, such as a user assistance information (UEAssistanceInformation), a user capability information (UECapabilityInformation), an uplink information transfer (ULInformationTransfer), an RRC reconfiguration complete (RRCReconfigurationComplete), an RRC setup request (RRCSetupRequest), an RRC setup complete (RRCSetupComplete), an RRC reestablishment request (RRCReestablishmentRequest), an RRC reestablishment complete (RRCReestablishmentComplete), an RRC resume request (RRCResumeRequest), or an RRC resume complete (RRCResumeComplete), etc.

[0178] A downlink RRC message, such as a downlink information transfer (DLInformationTransfer) (or downlink data, DL data) message, an RRC reestablishment (RRCReestablishment) message, an RRC reconfiguration (RRCReconfiguration) message, an RRC reject (RRCReject) (such as an indication of rejection) message, or an RRC release (RRCRelease) message, an RRC resume (RRCResume) message, an RRC setup (RRCSetup), or a UE capability enquiry (UECapabilityEnquiry) message, etc.

[0179] In another optional implementation, the messages or information exchanged between the terminal and the access network device can be directly sent to the core network element through the NAS message, that is, the terminal can directly interact with the core network element through the NAS message, so that the access network device does not need to perceive these messages or information, and the core network element directly interacts with the terminal.

[0180] In another optional implementation, the messages or information exchanged between the terminal and the access network device can be directly sent to the core network element through the NAS message, that is, the terminal can directly interact with the core network element through the NAS message, so that the access network device does not need to perceive these messages or information, and the core network element directly interacts with the terminal.

[0181] The communication method for improving the execution efficiency of A-IoT services is described below in combination with FIGS. 8 to 10. The communication method described in FIG. 8 is executed by the terminal, the device, and the access network device. The communication method described in FIGS. 9 to 10 also needs the participation of the core network element in execution. The device in communication with the terminal includes a tag, an A-IoT terminal, or an A-IoT device involved in A-IoT technology, etc.

[0182] FIG. 8 is a flow diagram of a communication method provided by an embodiment of the present application, which enables a terminal to communicate with a device in an idle state within a valid time. As shown in FIG. 8, the communication method includes some or all of the following steps:

[0183] S101. The first access network device determines a valid time for the terminal to communicate with the device in the idle state using the first resource.

[0184] In one possible implementation, the valid time is a time length during which the terminal communicates with the device using the first resource, or a time length during which the first resource is allowed to be used for the terminal to communicate with the device, or a time during which the first resource is allowed to be used, or a time length during which the first access network device allows the terminal to communicate with the device according to the first resource. The valid time can be referred to as an effective time length (or effective time) of the first resource, an active time length (or active time).

[0185] In one example, the valid time T is a timing length of a timer, the terminal starts the timer when receiving the first message containing the valid time or when entering the idle state, and stops communicating with the device according to the first resource or stops communicating with the device when the timing time of the timer expires; when the timing time of the timer does not expire, but the terminal completes the communication with the device, the timer can be triggered to terminate.

[0186] In another example, the valid time T is a timing length of a timer, the terminal starts the timer when receiving the first message containing the valid time or when entering the idle state, and stops communicating with the device according to the first resource when the timing time of the timer expires; when the timing time of the timer does not expire, but the terminal completes the communication with the device, the timer can be triggered to terminate the timing.

[0187] Optionally, the terminal is in the idle state, the first access network device receives a paging message from a core network element, and forwards the paging message to the terminal; the terminal initiates a random access (RA) procedure and establishes an RRC connection with the first access network device, and is in a connected state.

[0188] In one possible implementation, the core network element sends a service request (such as an A-IoT service request) to the first access network device, the request contains identification information; the first access network device forwards the request to the terminal device. The terminal can save the identification information and other information in the request, which is used for the terminal to request a resource and report data later, and for the core network element to identify the corresponding first service or terminal.

[0189] In a possible implementation, the first access network device returns, based on the request, a service response (e.g., an A-IoT service response) for determining whether to perform or not to perform the first service to the core network element without waiting for a response from the terminal. In another possible implementation, the first access network device forwards the service response for determining whether to perform or not to perform the first service from the terminal to the core network element.

[0190] S102. The first access network device sends, to the terminal, a first message including the validity time; correspondingly, the terminal receives the first message.

[0191] In an optional implementation, after receiving the first message, the terminal can save context information (e.g., identification information and the validity time) of communication between the terminal and the device, and enter an idle state. In addition, the terminal can also save an area associated with the communication between the terminal and the device. For details about the area associated with the communication between the terminal and the device, refer to the term introduction section, which will not be described here.

[0192] In an optional implementation, the first access network device determines whether the terminal is in the idle state and communicates with the device to perform steps S101 to S102. In another optional implementation, the terminal itself determines whether to communicate with the device in the idle state, and if the terminal determines to communicate with the device in the idle state, the terminal can send, to the first access network device, a message for requesting to communicate with the device in the idle state.

[0193] In a possible implementation, the first access network device or the terminal can determine whether the terminal communicates with the device in the idle state according to a service type of the first service. For example, if the service type is an inventory service, it is determined to allow or trigger the terminal to communicate with the device in the idle state; if the service type is not the inventory service, or if the service type is another service (e.g., a command service or a service requiring data transmission), it is determined not to allow or trigger the terminal to communicate with the device in the idle state (or not to release the terminal in the idle state).

[0194] Optionally, the first access network device or the terminal obtains the service type from the core network element, for example, from an AMF network element, or an AIoT MF network element, or an A-IOT network element, or an A-IOT management network element. Optionally, the terminal obtains the service type from the core network element through, for example, a NAS message, or the terminal obtains the service type from the access network device through, for example, an RRC message.

[0195] In another possible implementation, the core network element directly indicates the first access network device or the terminal not to perform the first service in the idle state, or directly indicates that there is subsequent data transmission, for example, the terminal has other data transmission after receiving the identification information and the like. Then, the first access network device or the terminal determines not to allow or trigger the terminal to communicate with the device in the idle state (not to perform the first service in the idle state).

[0196] The first access network device reserves or allocates the first resource for the terminal within the valid time. In a possible implementation, the first access network device further sends first information to the terminal, where the first information is used to indicate the first resource allocated by the first access network device for the terminal. Optionally, the first information can be included in the first message or received separately.

[0197] It can be seen that, in this embodiment, the first access network device separately configures the resource for the terminal to communicate with the device. Thus, in combination with the valid time, the first access network device can avoid allocating the same resource for other terminals to communicate with the device in the same cell within the T time.

[0198] Optionally, before the first access network device allocates the same resource for other terminals in the same cell within the valid time, the first access network device can determine whether the terminals are far enough apart based on the positions of the terminals, or determine the approximate distance between the terminals based on measurement. When the distance exceeds a distance threshold, the terminals can use the same resource (i.e., for communicating with the device).

[0199] For example, the first access network device can determine whether the terminals are far enough apart based on the positions of the terminals, including: the first access network device determines the distance between the terminals based on the positions of the terminals, and if the distance is greater than a certain threshold, it is determined that the terminals are far enough apart, and the same resource can be used.

[0200] For example, the first access network device determines the approximate distance between the terminals based on measurement, including: the first access network device determines the distance of each terminal from the first access network device according to the signal strength (such as reference signal receiving power (RSRP), reference signal receiving quality (RSRQ), signal to interference plus noise ratio (SINR), signal to noise ratio (SNR), channel state information (CSI), and the like) and / or the signal arrival angle of one or more terminals, or determines the distance between the terminals.

[0201] For example, the first access network device can determine whether the terminals can use the same resource based on the signal strength to determine the interference strength between the terminals.

[0202] In an alternative embodiment, the first access network device sends second information to the terminal, and the second information is used to instruct the terminal to communicate with the device in the idle state. In this embodiment, the first access network device explicitly instructs the terminal to perform the first service in the idle state. Optionally, the second information is carried in the RRC downlink message, and the RRC downlink message is described above and will not be described here.

[0203] It should be noted that in the above various alternative embodiments, the message and / or information sent by the first access network device to the terminal can include or be used to indicate one or more of the following: the valid time, the first resource, or the indication of the terminal communicating with the device in the idle state.

[0204] The indication of the terminal communicating with the device in the idle state can be replaced by the indication of the terminal performing the first service in the idle state, or the indication of the terminal continuing to use the first resource in the idle state, or the indication of the terminal continuing to use the first resource, and the like.

[0205] Optionally, the resource used by the terminal to communicate with the device in the idle state and the resource used by the terminal to communicate with the device in the connected state can be the same or different, or partially the same, and can be indicated separately or together.

[0206] Optionally, the valid time, the first resource, and / or the indication of the terminal communicating with the device in the idle state sent by the first access network device to the terminal can be carried in a message in the downlink RRC message or the MAC CE, wherein the downlink RRC message is described above and will not be described here.

[0207] Optionally, the message sent by the terminal to the first access network device to request to communicate with the device in the idle state can be or carried in the uplink RRC message or the MAC CE, wherein the uplink RRC message is described above and will not be described here.

[0208] S103. The terminal communicates with the device according to the first resource within the valid time in the idle state.

[0209] In an alternative embodiment, the terminal communicates with the device according to the first resource within the valid time in the idle state, including: when the terminal receives the first message (such as the RRC connection release message), starting a timer, the timing duration of the timer is the valid time T, and communicating with the device according to the first resource before the timer expires. Optionally, the terminal can start the timer when it enters the idle state.

[0210] In another optional implementation, the terminal communicates with the device according to the first resource within the validity time of the idle state, including: the terminal starts timing when the RRC connection is released to the idle state, and communicates with the device according to the first resource within the validity time of the timing.

[0211] It can be seen that in the communication method of FIG. 8, the terminal communicates with the device according to the first resource within the validity time of the idle state, which realizes that the terminal performs the first service in the idle state, and greatly improves the execution efficiency of the first service compared with performing the first service only in the connected state.

[0212] FIG. 9 is a flowchart of another communication method provided by the present application. Based on the communication method of FIG. 8, in the communication method of FIG. 9, the terminal enters the connected state to request the resource for communicating with the device from the first access network device when the validity time is expired. For example, when the timer is expired, the terminal has not completed the communication with the device (i.e., the first service is not completed) or the first resource is not available, the terminal can request the resource from the first access network device. As shown in FIG. 9, the terminal communicates with the device in the idle state, and when the validity time is expired, the communication method can include the following part or all steps:

[0213] S201. The terminal sends an RRC connection setup request (RRC Setup Request) to the first access network device to establish an RRC connection and enter the connected state (Connected).

[0214] Optionally, after the terminal sends the RRC connection setup request to the first access network device, the first access network device can return an RRC connection setup (RRC Setup) to the terminal. Optionally, the terminal returns an RRC connection complete (RRC Conection Complete) to the first access network device.

[0215] Optionally, the RRC connection setup request can include an RRC connection setup reason, such as requesting the resource for communicating with the device (i.e., requesting an A-IoT resource).

[0216] S202. The terminal sends a message for requesting the resource for communicating with the device to the first access network device.

[0217] Correspondingly, the first access network device receives the message. The message sent includes identification information.

[0218] S203. The first access network device sends a message for requesting to confirm whether the terminal communicates with the device (or sends auxiliary information for the core network element to confirm whether the terminal communicates with the device) to the core network element.

[0219] Correspondingly, the core network element receives the message from the first access network device. The message sent by the first access network device also includes identification information.

[0220] S204. The core network element performs authorization judgment on the terminal based on the identification information.

[0221] In an optional implementation, the authorization judgment performed by the core network element based on the identification information comprises: the core network element determines the terminal associated with the identification information or the first service, and performs authorization judgment on the terminal. If the core network element judges that the terminal has the right to perform the first service or is communicating with the device, the core network element sends a message to the first access network device for confirming that the terminal is communicating with the device; if the core network element judges that the terminal does not have the right to perform the first service or is not communicating with the device, the core network element sends a message to the first access network device for confirming that the terminal is not communicating with the device.

[0222] In another optional implementation, the message sent by the terminal to the first access network device in step S202, and the message or the auxiliary information sent by the first access network device to the core network element in step S203, in addition to the identification information such as the session ID, further comprise at least one of the following information for the core network element to identify the current service or the terminal:

[0223] 1) terminal identification information: identification information for the core network element to authorize, authenticate, etc. the terminal, which can be allocated by the core network element. For example, temporary mobile subscriber identity (TMSI).

[0224] 2) the number of device IDs (or inventory rate, or the number of devices) that the terminal has collected or obtained: the terminal calculates the number of devices that fail to be inventoried in each round of inventory, and calculates the number of devices that still fail to be inventoried or fail to be inventoried after multiple rounds of inventory, or the time of inventory, so that the core network element can determine the completion degree of the service inventory according to these information to determine whether the terminal needs to continue to communicate with the device. For example, if it is determined that the completion degree of the service inventory is below a certain threshold, the terminal is instructed to continue to communicate with the device; if it is determined that the completion degree of the service inventory is above a certain threshold, it means that the completion degree of the service inventory is high enough, and the terminal can be instructed to stop communicating with the device.

[0225] 3) information indicating the first resource: for the implementation in which the core network element determines the first resource, the core network element determines whether the first resource needs to be updated, and if not, confirms that the terminal continues to use the first resource to communicate with the device, and there is no need to indicate a new first resource. Optionally, the message sent by the core network device to the first access network device for confirming that the terminal is communicating with the device can carry a confirmation indication.

[0226] 4) Inventory area (service area, or AIOT service associated area, or area associated with identification information): used to prevent different inventory areas from using the same identification information; for example, the core network element can determine whether the terminal continues to communicate with the device according to the inventory area and the area or cell where the terminal is currently located.

[0227] 5) Reader identification: identification information of the terminal reader, similar to the terminal identification, but as an identification allocated or generated by the AIOT reader, for example, used by the core network element such as AMF or AIOT MF to authorize and confirm whether the current reader is valid according to the reader ID.

[0228] In some possible implementations, for the direct connection architecture in which the access network device is directly connected to the TMF network element, or the AIoT MF network element, or the A-IOT network element, or the A-IOT management network element, and the like, the terminal also needs to report the address of the above-mentioned core network element to the access network device in step S202, so that the access network device can directly address to these network elements.

[0229] S205. The core network element sends a message to the first access network device for confirming whether the terminal communicates with the device or not.

[0230] S206. If the core network element sends a message to the first access network device for confirming that the terminal communicates with the device, the terminal is allocated resources for communicating with the device; if the core network element sends a message to the first access network device for confirming that the terminal does not communicate with the device, the terminal is instructed to complete the communication with the device.

[0231] When the terminal receives the resources for communicating with the device, the terminal can communicate with the device according to the resources; when the terminal receives the instruction for completing the communication with the device, the terminal releases the context information for communicating with the device and deletes the obtained data.

[0232] For example, the context information related to the communication between the terminal and the device includes but is not limited to at least one of the following information: AIOT communication resource information, transmission configuration parameters (or coding and modulation method), temporary identification (such as AS ID), paging identification (such as mask, device group ID, etc.), or random access parameters (such as R2D / D2R frequency information, total number of access opportunities, etc.), and the like. The obtained data includes the data received from the AIOT device (such as the device ID), or the AIOT data in the buffer area (such as the received device ID).

[0233] In an optional embodiment, the message sent by the terminal to the first access network device, or the message carrying the information sent, can be the uplink RRC message or the MAC CE described above; correspondingly, the message sent by the first access network device to the terminal, or the message carrying the information sent, can be the downlink RRC message described above. In addition, the message exchanged between the first access network device and the core network element, or the message carrying the information exchanged, is the NG AP message.

[0234] In another optional embodiment, the message exchanged between the terminal and the first access network device, or the message carrying the information exchanged, is a non-access stratum (NAS) message, so that the first access network device is not aware of the request of the terminal, and directly interacts with the terminal, such as allocating resources for the terminal to communicate with the device, by the core network element.

[0235] In yet another optional embodiment, the message exchanged between the terminal and the first access network device, or the message carrying the information exchanged, is a packet data unit (PDU) session-based message, so that the terminal directly interacts with the UPF in the message or the information, such as allocating resources for the terminal to communicate with the device.

[0236] It can be seen that in the communication method described in FIG. 9, before the first access network device allocates resources for the terminal to communicate with the device, the first access network device can first request the core network element to determine whether the terminal is communicating with the device, so that even if the first access network device does not save the context information of the terminal communicating with the device when the terminal is in the idle state, the first access network device can still request the confirmation of the core network element based on the identification information.

[0237] In another embodiment, the first access network device itself can also confirm whether the terminal is communicating with the device, that is, in the communication method shown in FIG. 9, the first access network device does not need to interact with the core network element, but determines whether to communicate with the device by the first access network device, which will not be described here.

[0238] FIG. 10 is a flow diagram of another communication method provided by the present application. Based on the communication method shown in FIG. 8, in the communication method described in FIG. 10, when the terminal completes the communication with the device, the terminal requests the first access network device to report the obtained data of the device. As shown in FIG. 10, the communication method includes the following part or all steps:

[0239] S301. The terminal sends an RRC connection establishment request to the first access network device, establishes an RRC connection, and enters a connected state.

[0240] Optionally, after the terminal sends the RRC connection setup request to the first access network device, the first access network device returns an RRC connection setup (RRC Setup) to the terminal. Optionally, the terminal returns an RRC connection complete (RRC Conection Complete) to the first access network device.

[0241] Optionally, the RRC connection setup request can include an RRC connection setup cause, such as a request to report data from the device.

[0242] S302. The terminal sends a message to the first access network device for requesting to report data from the device.

[0243] Correspondingly, the first access network device receives the message. The message sent by the terminal includes the identification information.

[0244] Optionally, the message sent by the terminal to the first access network device includes one or more of the terminal identification information, the number of device identifications collected or obtained by the terminal, and the inventory area or the reader identification, and the related content can be referred to the related content in the embodiment described with reference to FIG. 9, which will not be described in detail here.

[0245] S303. The first access network device sends a message to the core network element for requesting to confirm whether the terminal communicates with the device (or sends auxiliary information for the core network element to confirm whether the terminal communicates with the device).

[0246] The message sent by the first access network device also includes the identification information. Correspondingly, the core network element receives the message from the first access network device.

[0247] S304. The core network element performs authorization judgment based on the identification information.

[0248] S305. The core network element sends a message to the first access network device for confirming that the terminal communicates with the device, or a message for confirming that the terminal does not communicate with the device.

[0249] The related content of steps S303 to S305 can be referred to the related content of steps S203 to S205 in the embodiment described with reference to FIG. 9, which will not be described in detail here.

[0250] S306. When the first access network device receives the message for confirming that the terminal communicates with the device, the first access network device instructs the terminal to report data; when the first access network device receives the message for confirming that the terminal does not communicate with the device, the first access network device instructs the terminal to complete the communication with the device.

[0251] The terminal releases the context information of the communication with the device and deletes the obtained data when the first access network device instructs the terminal to complete the communication with the device. The context information of the communication with the device and the obtained data can refer to the related content in the embodiment described with reference to FIG. 9, which is not described in detail herein.

[0252] Optionally, the message sent by the terminal to the first access network device or the message carrying the information sent by the terminal can be the uplink RRC message or the MAC CE described above; the message sent by the first access network device to the terminal or the message carrying the information sent by the first access network device can be the downlink RRC message described above. Alternatively, the message or the message carrying the information exchanged between the terminal and the first access network device can be the NAS message. Alternatively, the message or the message carrying the information exchanged between the terminal and the first access network device can be the PDU session-based message. Further details can refer to the related content in the embodiments described above, which are not described in detail herein.

[0253] It can be seen that in the communication method shown in FIG. 10, the first access network device can request the core network element to determine whether the terminal is communicating with the device before instructing the terminal to report the data from the device. In this way, even if the first access network device does not save the context information of the communication between the terminal and the device when the terminal is in the idle state, the first access network device can still request the confirmation of the core network element based on the identification information and the like.

[0254] In another embodiment, the first access network device can also confirm whether the terminal reports the data from the device. That is, in the communication method shown in FIG. 10, the first access network device does not need to interact with the core network element, but determines whether to communicate with the device, which is not described in detail herein.

[0255] The following describes a communication method supporting mobility in the execution of the first service with reference to FIGS. 11 to 14. The communication method described in FIGS. 11 to 14 is executed by the terminal, the device, the second access network device, and the core network element. The device in communication with the terminal includes a tag, an A-IoT terminal, or an A-IoT device related to A-IoT technology.

[0256] FIG. 11 is a flowchart of another communication method provided by an embodiment of the application, which supports mobility in the execution of the first service by the terminal. The terminal moves to the second cell or reselects the cell in the communication with the device, and determines whether to continue the communication with the device. As shown in FIG. 11, the communication method includes the following steps or all the steps:

[0257] S401. The terminal determines whether to continue the communication with the device according to the area associated with the second cell. If the communication with the device is continued, steps S402 to S406 are executed. If the communication with the device is not continued, steps S407 to S411 are executed.

[0258] In a possible implementation, the terminal acquires the second cell-associated area from system information of the second cell.

[0259] In an optional implementation, the terminal determines to continue the communication with the device when the second cell-associated area contains the first area, or the second cell-associated area is contained in the first area, or the second cell-associated area is the same as the first area; and the terminal determines not to continue the communication with the device when the second cell-associated area does not contain the first area, is not contained in the first area, and is not the same as the first area. The first area is an area associated with the communication between the terminal and the device.

[0260] S402. The terminal sends a message for requesting a resource for the communication between the terminal and the device to the second access network device; and the second access network device receives the message, where the message contains the identification information.

[0261] S403. The second access network device sends a message for requesting confirmation of whether the terminal is in the communication with the device to the core network element; and the core network element receives the message, where the message contains the identification information.

[0262] S404. The core network element determines whether the terminal is in the communication with the device according to the received message.

[0263] S405. When the core network element determines that the terminal is in the communication with the device, the core network element sends a message for confirming that the terminal is in the communication with the device to the second access network device; and when the core network element determines that the terminal is not in the communication with the device, the core network element sends a message for confirming that the terminal is not in the communication with the device to the second access network device; and the second access network device receives the message.

[0264] S406. When the second access network device receives the message for confirming that the terminal is in the communication with the device, the second access network device allocates a resource for the communication with the device to the terminal; and when the second access network device receives the message for confirming that the terminal is not in the communication with the device, the second access network device instructs the terminal to complete the communication with the device.

[0265] The resource allocated by the second access network device to the terminal is an A IoT resource of a current cell, i.e., the second cell.

[0266] After receiving the instruction to complete the communication with the device, the terminal can release context information for the communication with the device and delete data from the device. The context information for the communication with the device and the data from the device can refer to the related descriptions in the foregoing content, which will not be described in detail herein.

[0267] S407. The terminal sends a message for requesting whether to report data from the device to the second access network device; and the second access network device receives the message, where the message contains the identification information.

[0268] The information carried in the message sent by the terminal to the second access network device can refer to the description of the information carried in the message sent to the first access network device in the foregoing embodiments, which will not be described here in detail. Correspondingly, the information carried in the message sent by the second access network device to the core network element can refer to the description of the information carried in the message sent by the first access network device to the core network element in the foregoing embodiments, which will not be described here in detail either.

[0269] S408. The second access network device sends a message for requesting confirmation of whether the terminal reports data from the device to the core network element. Correspondingly, the core network element receives the message.

[0270] S409. The core network element determines whether the terminal reports data from the device according to the received message.

[0271] S410. The core network element sends a message for confirming that the terminal reports data to the second access network device when it is determined that the terminal reports data, and sends a message for confirming that the terminal does not report data to the second access network device when it is determined that the terminal does not report data.

[0272] S411. The second access network device instructs the terminal to report data when it receives the message for confirming that the terminal reports data, and instructs the terminal to complete communication with the device when it receives the message for confirming that the terminal does not report data.

[0273] The related content described in the embodiments of the application, such as the optional implementation of steps S402 to S411, can refer to the related content described in the implementation of FIG. 9 or FIG. 10, which will not be described here in detail.

[0274] It can be seen that in the method, the terminal judges by itself whether to continue communication with the device after reselecting a cell or changing a station.

[0275] FIG. 12 is a schematic diagram of another communication method provided by the application. Based on the communication method supporting mobility described in FIG. 11 and the communication method of performing first service in an idle state described in FIG. 8, in the communication method described in FIG. 12, for example, the terminal is in communication with the device in an idle state, and mobility or cell reselection occurs. Optionally, the terminal also needs to send an RRC connection establishment request to the second access network device, and the RRC connection establishment between the terminal and the second access network device is completed, and the terminal is in a connected state. The terminal performs steps S401 to S411 described in FIG. 11 in the connected state.

[0276] Optionally, the terminal obtains the area associated with the second cell from the system information of the second cell or in the RRC connection establishment process.

[0277] In an optional implementation, the terminal can acquire the A-IoT capability of the second access network device from the system information of the second cell or in the RRC connection establishment process. If the second access network device supports the A-IoT capability, the RRC connection establishment between the terminal and the second access network device is completed; otherwise, the terminal stops communicating with the device (i.e., stops the first service) or reselects a cell until the terminal reselects an access network device that supports the A-IoT capability.

[0278] In another optional implementation, the terminal can acquire whether the second cell supports or allows the A-IoT capability (or A-IoT service or A-IoT communication) from the system information of the second cell or in the RRC connection establishment process. If the second cell supports or allows the A-IoT capability, the RRC connection establishment between the terminal and the second access network device is completed; otherwise, the terminal stops communicating with the device or reselects a cell until the terminal reselects an access network device that supports the A-IoT capability.

[0279] Optionally, whether the second access network device or the second cell supports the A-IoT capability can be whether the second access network device or the second cell supports the A-IoT protocol stack. Alternatively, whether the second access network device or the second cell supports the A-IoT capability is determined based on the load of the second access network device or the second cell. For example, the second access network device or the second cell cannot support the A-IoT capability due to a high load.

[0280] As can be seen, in the method, after the terminal reselects a cell or changes a station in the idle state, the terminal itself determines whether to continue communicating with the device. That is, even if the terminal reselects the second cell in the idle state and accesses the second access network device, the second access network device does not save the context information of the terminal communicating with the device, and the second access network device can request the core network element to confirm whether the terminal communicates with the device based on the identification information. If it is determined to continue communicating with the device, the second access network device can allocate resources for the terminal; if it is determined not to continue communicating with the device, the second access network device can instruct the terminal to report the obtained data.

[0281] FIG. 13 is a flow diagram of another communication method provided by the present application. The communication method described in FIG. 13 also supports the mobility of the terminal, but in the communication method described in FIG. 11, after the terminal reselects a cell or changes a station, the terminal itself determines whether to continue communicating with the device. In the communication method described in FIG. 13, after the terminal reselects a cell or changes a station, the core network element determines whether to continue communicating with the device. As shown in FIG. 13, the method includes the following steps or all of the steps:

[0282] S501. The terminal sends a message for requesting whether the terminal communicates with the device and / or whether to report data from the device to the second access network device; correspondingly, the second access network device receives the message, wherein the message contains identification information.

[0283] The information that can be further included in the message sent by the terminal to the second access network device can refer to the foregoing, such as the related description of steps S202 and S203 in FIG. 9, and at least one of the following: terminal identification information, the number of device identifications that the terminal has collected or acquired, an inventory area, or a reader identification, which can be used to determine whether the terminal continues to communicate with the device and / or whether to report data from the device.

[0284] S502. The second access network device sends a message to the core network element for requesting confirmation of whether the terminal continues to communicate with the device and / or whether to report data from the device; correspondingly, the core network element receives the message, wherein the message contains identification information.

[0285] S503. The core network element sends the following message to the second access network device: a message for confirming that the terminal communicates with the device; a message for confirming that the terminal reports data from the device; or a message for confirming that the terminal does not communicate with the device and does not report data from the device. Correspondingly, the second access network device receives the message.

[0286] In a possible implementation, the core network element determines a first service associated with the identification information, or determines a terminal associated with the identification information that communicates with the device, performs authorization judgment on the terminal, and if the terminal has the right to perform the first service or it is determined that the terminal is communicating with the device, sends a message for confirming that the terminal communicates with the device or a message for confirming that the terminal reports data to the second access network device; if the terminal does not have the right to perform the first service or it is determined that the terminal does not communicate with the device, sends a message for confirming that the terminal does not communicate with the device and does not report data from the device to the second access network device.

[0287] In another possible implementation, the authorization judgment operation of the core network element can also refer to the related content described in the foregoing FIG. 9 and FIG. 10, which is not described in detail here.

[0288] S504. When the second access network device receives the message for confirming that the terminal communicates with the device, allocates resources for the terminal to communicate with the device; when receiving the message for confirming that the terminal reports data, instructs the terminal to report data from the device; and when receiving the message for confirming that the terminal does not communicate with the device and does not report data, instructs the terminal to complete communication with the device.

[0289] The resources allocated by the second access network device to the terminal are the current message, that is, the A IoT resources of the second cell.

[0290] It can be seen that in the method, after the terminal reselects the cell, the core network is requested by the second access network device to determine whether the terminal continues to communicate with the device and whether to report data.

[0291] The application also provides a communication method which also supports mobility, but different from the communication method described in FIG. 11 and FIG. 13, in which the terminal reselects a cell and by default stops communicating with the device, releases the context information of the communication with the device and deletes the obtained data of the device.

[0292] In a possible implementation, the terminal can also send a message to the second access network device to indicate that the terminal has stopped communicating with the device, and the message includes the identification information; and the second access network device sends the message to the core network element.

[0293] In another possible implementation, the terminal does not need to send a message to the core network element to indicate that the terminal has stopped communicating with the device, but the core network element releases the context information of the communication between the terminal and the device based on the time out of the communication between the terminal and the device, such as the first service time out, or the core network element determines that it needs to continue to perform the first service and initiates paging to the terminal again.

[0294] The application also provides a communication method which also supports mobility, but different from the communication method described in FIG. 11 and FIG. 13, in which the terminal reselects a cell and by default does not continue to communicate with the device, and sends a message to the second access network device to request reporting data. The second access network device sends a message to the core network element to confirm whether the terminal reports data. When the core network element sends a message to the second access network device to confirm that the terminal reports data, the second access network device instructs the terminal to report data; and when the core network element sends a message to the second access network device to confirm that the terminal does not report data, the second access network device instructs the terminal to delete the obtained data.

[0295] In the above two communication methods, the optional implementation and / or exemplary content can refer to the related description in the foregoing embodiments, which will not be described in detail herein.

[0296] The optional implementation and / or exemplary content in the above two communication methods can refer to the related description in the foregoing embodiments, which will not be described in detail herein.

[0297] Figure 14 is a schematic diagram of another communication method provided by the present application, based on the communication method supporting mobility described in Figure 13 and the communication method performing the first service in the idle state described in Figure 8, in the communication method described in Figure 14, the terminal in the idle state communicates with the device, and after the terminal moves or performs cell reselection, the terminal optionally sends an RRC connection establishment request to the second access network device, the RRC connection establishment between the terminal and the second access network device is completed, and the terminal is in the connected state. The terminal performs steps S501 to S504 described in Figure 13, or performs the above method in which the terminal stops communicating with the device by default, or performs the method in which the terminal does not continue to communicate with the device by default but can report data according to the indication of the core network element.

[0298] In an optional embodiment, the terminal can obtain the A-IoT capability of the second access network device from the system information of the second cell or in the RRC connection establishment process, and if the second access network device supports the A-IoT capability, the RRC connection establishment between the terminal and the second access network device is completed; otherwise, the terminal stops communicating with the device (i.e., stops the first service), or the terminal reselects a cell until the terminal reselects an access network device supporting the A-IoT capability, or the terminal stops communicating with the device (i.e., stops the first service).

[0299] In another optional embodiment, the terminal can obtain whether the second cell supports or allows the A-IoT capability (or A-IoT service or A-IoT communication) from the system information of the second cell or in the RRC connection establishment process, and if the second cell supports or allows the A-IoT capability, the RRC connection establishment between the terminal and the second access network device is completed; otherwise, the terminal stops communicating with the device, or the terminal reselects a cell until the terminal reselects an access network device supporting the A-IoT capability.

[0300] In another optional embodiment, the RRC connection establishment request sent by the terminal to the second access network device can include identification information, so that the second access network device can request the core network element to confirm whether the second access network device supports the A-IoT capability; if the core network element returns a message confirming that the second access network device supports the A-IoT capability, the second access network device completes the RRC connection with the terminal; if the core network element returns a message confirming that the second access network device does not support the A-IoT capability, the second access network device sends a message to the terminal indicating that the communication with the device is completed, and the terminal receiving the message can release the context information of the communication with the device and delete the obtained data, or the second access network device indicates to the terminal to reselect a cell.

[0301] It can be seen that in the communication method, even if the terminal reselects to the second cell in the idle state, the second access network device does not save the context information of the terminal and the device communication, and the second access network device can request the core network element to confirm whether the terminal continues to communicate with the device and / or whether the data of the device is reported based on the identification information.

[0302] Similar to FIG. 14, the above method in which the terminal stops communicating with the device by default, or the above two communication methods in which the terminal does not continue to communicate with the device by default, are also applicable to the scenario in which the terminal communicates with the device in the idle state as described in FIG. 8, and details are not described herein.

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

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

[0305] In this application, "sending information to (for example, an access network device)" or related illustrations in the drawings can be understood as that the destination of the information is the access network device. It can include directly or indirectly sending information to the access network device. "Receiving information from (for example, a terminal)" or "receiving information from (for example, a terminal)" or "receiving information sent by (for example, a terminal)", or related illustrations in the drawings can be understood as that the source of the information is the terminal, and can include directly or indirectly receiving information from the terminal. The information between the source and the destination of the information sending can be processed as necessary, for example, format change, etc., but the destination can understand the valid information from the source. Similar expressions in this application can be similarly understood, and details are not described herein.

[0306] The above describes the communication method provided by the embodiments of the application in combination with FIGS. 8 to 14. In various embodiments of the application, if there is no special description and logical conflict, the terms and / or descriptions between various embodiments are consistent and can be mutually referenced. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0307] The communication apparatus provided in the embodiments of the present application is described below with reference to FIG. 15 to FIG. 16. It should be understood that the description of the apparatus embodiments corresponds to the description of the method embodiments, and thus, the content not described in detail can be referred to the method embodiments described above, which will not be repeated here for brevity.

[0308] FIG. 15 shows a possible exemplary block diagram of the communication apparatus involved in the embodiments of the present application. As shown in FIG. 15, the communication apparatus can include modules or units for implementing the corresponding method embodiments described above. In a possible design, the communication apparatus includes a communication unit 601 and a processing unit 602. Optionally, the communication apparatus can further include a storage unit 603 for storing apparatus program code and / or data.

[0309] The communication apparatus can be the terminal-side apparatus in the embodiments described above, such as the first apparatus, for example, a terminal or a communication module in the terminal, or a circuit or chip responsible for the communication function in the terminal.

[0310] For example, in one embodiment, the communication unit 601 is configured to receive a first message from a second apparatus, the first message including a first resource used by the first apparatus to communicate with a third apparatus in an active time; and communicate with the third apparatus according to the first resource in the active time in an idle state. Optionally, the processing unit 602 is configured to configure a time length of a timer as T, so that the communication unit 601 communicates with the third apparatus according to the first resource before the timer expires.

[0311] In a possible design, the communication unit 601 is further configured to receive first information and / or second information; the first information is used to indicate the first resource allocated by the second apparatus to the first apparatus; and the second information is used to indicate the first apparatus to communicate with the third apparatus in the idle state.

[0312] In a possible design, the communication unit 601 is further configured to send, to the second apparatus, a message used to request to communicate with the third apparatus in the idle state.

[0313] In a possible design, the communication unit 601 is further configured to send, to the second apparatus, a message used to request a resource for communicating with the third apparatus; and the sent message includes identification information associated with the first apparatus communicating with the third apparatus.

[0314] In a possible design, the communication unit 601 is further configured to send, to the second apparatus, a message used to request to report data from the third apparatus; and the sent message includes the identification information.

[0315] In a possible design, the communication unit 601 is further configured to send, to the fourth device, a message for requesting resources for communicating with the third device or for requesting whether to report data from the third device according to a region associated with the second cell; the second cell is a cell to which the first device reselects, and the fourth device is an access network device corresponding to the second cell; and the message sent by the communication unit 601 includes the identification information.

[0316] In a possible design, the communication unit 601 is further configured to send, to the fourth device, a message for requesting whether to communicate with the third device and / or whether to report data from the third device; and the message sent by the communication unit 601 includes the identification information.

[0317] In a possible design, the processing unit 602 is further configured to delete information related to communication with the third device when reselecting to the second cell, and the communication unit 601 is further configured to send, to the fourth device, a message for requesting whether to report data from the third device; and the message sent by the communication unit 601 includes the identification information.

[0318] In a possible design, the processing unit 602 is further configured to delete information related to communication with the third device when reselecting to the second cell, and the communication unit 601 is further configured to send, to the fourth device, a message for requesting whether to report data from the third device; and the message sent by the communication unit 601 includes the identification information.

[0319] In a possible design, the identification information includes at least one of the following: a service identifier associated with communication between the first device and the third device, a session identifier, a task identifier, a stocktaking region, a reader identifier, or an address of a core network element.

[0320] In a possible design, when the communication apparatus is a terminal or a communication module in a terminal, the function of the processing unit 602 can be implemented by one or more processors. Specifically, the processor can include a modem chip, or a system on chip (SoC) chip or a SIP chip that includes a modem core. The function of the communication unit 601 can be implemented by a transceiver circuit.

[0321] In a possible design, when the communication apparatus is a circuit or chip responsible for communication functions in a terminal, such as a modem chip or a system on chip (SoC) chip or a SIP chip that includes a modem core, the function of the processing unit 602 can be implemented by a circuit system including one or more processors or processor cores in the chip. The function of the communication unit 601 can be implemented by an interface circuit or a data transceiver circuit on the chip.

[0322] In a possible design, when the communication apparatus is a terminal or a processing module in a terminal, the function of the processing unit 602 can be implemented by one or more processors. Specifically, the processor can include a GPU, or a system on chip (SoC) chip or a SIP chip that includes a GPU. The function of the communication unit 601 can be implemented by a transceiver circuit.

[0323] In a possible design, when the communication apparatus is a circuit or a chip responsible for processing functions in a terminal, such as a GPU or a System on Chip (SoC) chip or a System in Package (SIP) chip containing a GPU, the function of the processing unit 602 can be implemented by circuitry including one or more processors or processor cores in the chip. The function of the communication unit 601 can be implemented by an interface circuit or a data transceiver circuit on the chip.

[0324] The communication apparatus can be a network-side apparatus in the above-described embodiments, such as the first access network device or the second apparatus.

[0325] For example, in an embodiment, the processing unit 602 is configured to: determine a valid time during which the first resource is used by the first apparatus to communicate with the third apparatus in the idle state.

[0326] The communication unit 601 is configured to: send, to the first apparatus, a first message, where the first message includes the valid time.

[0327] In a possible design, the communication unit 601 is further configured to: send first information and / or second information, where the first information is used to indicate the first resource allocated to the first apparatus, and the second information is used to indicate that the first apparatus communicates with the third apparatus in the idle state.

[0328] In a possible design, the communication unit 601 is further configured to: receive, from the first apparatus, a message used to request the first apparatus to communicate with the third apparatus in the idle state.

[0329] In a possible design, the communication unit 601 is further configured to: receive, from the first apparatus, a message used to request a resource for communicating with the third apparatus, or used to request reporting of data from the third apparatus, and send, to a core network element, a message used to request confirmation of whether the first apparatus communicates with the third apparatus, where the received message and the sent message include identification information.

[0330] The communication apparatus can be a network-side apparatus in the above-described embodiments, such as the second access network device or the fourth apparatus.

[0331] For example, in an embodiment, the communication unit 601 is configured to: receive, from the first apparatus, a message used to request a resource for communicating with the third apparatus, or used to request whether to report data from the third apparatus, and send, to a core network element, a message used to request confirmation of whether the first apparatus communicates with the third apparatus, where the received message and the sent message include identification information associated with the communication between the first apparatus and the third apparatus.

[0332] In another embodiment, the communication unit 601 is configured to: receive a message from the first device for requesting whether to communicate with the third device and / or whether to report data from the third device; and send a message to the core network element for requesting to confirm whether the first device communicates with the third device and / or whether to report data from the third device; wherein the received message and the sent message comprise identification information associated with the communication between the first device and the third device.

[0333] The communication device can be the network side device in the above embodiments, such as the core network element.

[0334] For example, in one embodiment, the communication unit 601 is configured to: receive a message from the second device for requesting to confirm whether the first device communicates with the third device, the received message comprising identification information associated with the communication between the first device and the third device; and send a message to the second device for confirming that the first device communicates with the third device or for confirming that the first device does not communicate with the third device.

[0335] For example, in another embodiment, the communication unit 601 is configured to: receive a message from the fourth device for requesting whether the first device communicates with the third device and / or whether to report data from the third device, the received message comprising identification information associated with the communication between the first device and the third device; and send a message to the second device for confirming that the first device communicates with the third device, for confirming that the first device reports data from the third device, or for confirming that the first device does not communicate with the third device and does not report data from the third device.

[0336] It can be understood that the division of the units in the above device is a logical function division, one function unit can be used for one function, or two or more functions can be integrated into one function unit. In actual implementation, all or part of the units can be integrated into one physical entity, or can be distributed in different physical entities. In addition, the above function units can be implemented in the form of hardware, or in the form of software, or in the form of hardware combined with software. Whether a certain function is implemented in hardware or software depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for specific applications, but such implementation should not be considered beyond the scope of the present application.

[0337] In one example, the functional units in any of the above apparatuses can be one or more integrated circuits configured to implement the above methods, for example: one or more application specific integrated circuits (ASICs), or, one or more central processing units (CPUs), one or more microcontroller units (MCUs), one or more digital signal processors (DSPs), or, one or more field programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms.

[0338] In one example, the storage unit 603 can include random access memory, flash memory, read only memory, programmable read only memory, electrically erasable programmable memory, and / or registers, etc.

[0339] FIG. 16 is a structural schematic diagram of a terminal according to an embodiment of the present application, which can correspond to the terminal or the first apparatus shown in FIGS. 1 to 14, and is used to implement the operations of the terminal or the first apparatus in the above embodiments. As shown in FIG. 16, the terminal includes one or more antennas 710, a radio frequency processing system 720, and a processor system 730.

[0340] In the downlink or sidelink direction, the radio frequency processing system 720 receives radio frequency signals through the antenna 710, and sends the signals after radio frequency processing to the processor system 730 for further processing. In the uplink or sidelink direction, the processor system 730 performs signal processing on the information at the terminal side, and sends the signal to the radio frequency processing system 720, which performs radio frequency processing on the signal and transmits it through the antenna 710.

[0341] In one example, the radio frequency processing system 720, which serves as a communication interface for the terminal to communicate with the outside, can include a radio frequency front end 721 (RFFE) and a radio frequency transceiver 722. The RFFE 721 is mainly used for one or more of shaping, passband selection, or gain processing of radio frequency (RF) signals received by an antenna or to be transmitted through an antenna, and can include one or more of radio frequency switches, duplexers, filters, power amplifiers, antenna tuning, and low-noise amplifiers. The RFFE 721 can be a circuit system composed of a plurality of discrete devices, or can be integrated and packaged in one or more chips. The radio frequency transceiver 722 is used to process RF signals received by the RFFE 721 into baseband / intermediate frequency signals for further processing by the processor system 730, and to process baseband / intermediate frequency signals provided by the processor system 730 into RF signals for transmission to the RFFE 721. The baseband / intermediate frequency signals transmitted between the radio frequency transceiver 722 and the processor system 730 can be digital signals or analog signals. The radio frequency transceiver 722 can be implemented by one or more chips, which are commonly referred to as radio frequency integrated circuits (RFICs).

[0342] In one example, the processor system 730 can include one or more processors for processing signals and executing one or more communication protocols. Optionally, the processor system 730 can further include a memory 736. In one example, the one or more processors include at least one baseband processor 731 (also referred to as a modem processor). The memory 736 is used to store data and / or computer program instructions. Optionally, the processor system 730 can further include one or more application processors 732 for implementing processing of the terminal operating system and the application layer. The application processor 732 can include a GPU, for example. Optionally, the processor system 730 can further include one or more of a voice subsystem 733, a multimedia subsystem 734, or an interface circuit 735. The voice subsystem 733 is used to process voice signals, the multimedia subsystem 734 is used to process multimedia-related operations such as video encoding and decoding, image processing, etc., and the interface circuit 735 is used to implement communication with other terminal components such as the display 740, the input device 750, the memory 760, etc. The above-mentioned components in the processor system 730 can communicate with each other through a bus or a communication interface circuit.

[0343] In one example, the processor system 730 can be packaged as one processor chip, such as a SoC chip or a SIP chip. In one example, the processor system 730 can be a system composed of multiple chips, for example, the baseband processor 731 can be packaged as a separate chip, or packaged as a chip with part or all of the circuitry of the radio frequency processing system.

[0344] In one example, the memory 736 can be an on-chip memory, i.e., located on the chip of the processor system 730. In one example, the memory 760 can be an off-chip memory, i.e., located off the chip of the processor system 730.

[0345] In one example, the baseband processor 731 can include one or more processor cores 7311 and interface circuitry 7314. The one or more processor cores 7311 are configured to process signals and perform one or more communication protocols. Optionally, the baseband processor 731 can further include a memory 7312 configured to store at least part of corresponding computer program instructions and / or data. In one example, the one or more processor cores 7311 implement the relevant operations (such as generating and sending the first information) in the above method embodiments by executing the computer program instructions stored in the memory 7312. In this application, the memory 7312 configured to store corresponding computer program instructions and / or data can mean that the memory 7312 is configured to store all corresponding computer program instructions and / or data for execution by the processor core 7311; or can mean that the memory 7312 is configured to store part of corresponding computer program instructions and / or data, which includes computer program instructions and / or data currently required for execution by the processor core 7311, and the memory 7312 can store different parts of computer program instructions and / or data for execution by the processor core 7311 multiple times to implement the relevant operations in the above method embodiments. The interface circuitry 7314 serves as a communication interface to enable communication with other components, such as transmitting signals with the radio frequency processing system 720, communicating with other subsystems and related components of the processor system 730 through a bus, such as transmitting data control signals with the application processor 732, and transmitting data or computer program instructions with the memory 736 or the memory 760. Optionally, to reduce the load of the processor core, a baseband signal processing circuit 7313 can be further provided to implement at least part of the processing of baseband signals, including one or more of demodulation, modulation, encoding or decoding of signals.

[0346] The processor, processor system, application processor, baseband processor, processor circuit, or processor core can be collectively referred to as a processor, which can include one or a combination of a central processing unit (CPU), a digital signal processor (DSP), a microprocessor unit (MPU), a microcontroller unit (MCU), a graphics processing unit (GPU), a field programmable gate array (FPGA), an artificial intelligence processor (AI processor), or a neural processing unit (NPU).

[0347] The above-mentioned memory can include one or more of the following storage media: random access memory (RAM), static RAM (SRAM), dynamic random access memory (DRAM), phase-change memory (PCM), resistive random access memory (RERAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), cache, register, read-only memory (ROM), flash memory, erasable programmable read-only memory (EPROM), hard disk, etc. In one example, computer program instructions for implementing the above-embodiments can be stored on a non-volatile memory, such as at least part of the above-mentioned memory 760 (e.g., one or more of ROM, flash memory, EPROM, or hard disk). During terminal operation, the corresponding computer program instructions can be loaded in whole or in part into a memory with faster transmission speed than the processor, such as at least part of the above-mentioned memory 736 and / or memory 7312 (e.g., one or more of RAM, SRAM, DRAM, PCM, RERAM, MRAM, FRAM, cache, or register), for execution by the processor to implement the steps in the above-mentioned method embodiments.

[0348] In one example, the radio frequency transceiver 722 and the radio frequency front end 721 can also be packaged in one chip. In one example, the radio frequency transceiver 722, the radio frequency front end 721, and the baseband processor 731 can also be packaged in one chip.

[0349] The terms "system" and "network" in the embodiments of the present application can be used interchangeably. "At least one" means one or more, and "multiple" means two or more. The "and / or" describes the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B, which can represent the cases of A alone, A and B together, and B alone, where A and B can be singular or plural. The character " / " generally represents an "or" relationship between the front and rear associated objects. "At least one of the following" or similar expressions means any combination of these items, including any combination of single or multiple items. For example, "at least one of A, B or C" includes A, B, C, AB, AC, BC or ABC, and "at least one of A, B and C" can also be understood to include A, B, C, AB, AC, BC or ABC. In addition, unless otherwise specified, the ordinal numbers "first", "second" and the like mentioned in the embodiments of the present application are used to distinguish a plurality of objects, and are not used to limit the order, time sequence, priority or importance of the plurality of objects.

[0350] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, etc.) containing computer-usable program code.

[0351] The present application is described with reference to flowcharts and / or block diagrams according to the methods, devices (systems), and computer program products of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and the combination of flows and / or blocks in the flowcharts and / or block diagrams can be implemented by computer program instructions. These computer program instructions can be provided to a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing apparatus to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing apparatus produce the functions specified in one or more flows in the flowcharts and / or one or more blocks in the block diagrams.

[0352] These computer program instructions can also be stored in a computer-readable storage medium that can direct the computer or other programmable data processing apparatus to work in a specific manner, so that the instructions stored in the computer-readable storage medium produce a product including instruction means, which implements the functions specified in one or more flows in the flowcharts and / or one or more blocks in the block diagrams.

[0353] These computer program instructions can also be loaded into a computer or other programmable data processing devices, so that a series of operational steps are performed on the computer or other programmable devices to generate computer-implemented processes, so that the instructions executed on the computer or other programmable devices provide steps for implementing the functions specified in one or more flows in the flowchart and / or one or more blocks in the block diagram.

[0354] Obviously, various modifications and changes can be made to the present application by those skilled in the art without departing from the scope of the present application. Thus, it is intended that the present application embrace all such modifications and changes and, accordingly, the application is not to be limited by the above-described one or more embodiments.

Claims

1. A communication method characterized by comprising: The method comprises: The first device receives a first message from a second device, the first message comprising a first resource valid for the first device to communicate with a third device; The first device communicates with the third device according to the first resource in an idle state within the valid time.

2. The method of claim 1, wherein, The method further comprises: The first device receives first information and / or second information; The first information is used to indicate the first resource allocated by the second device for the first device; The second information is used to indicate the first device to communicate with the third device in an idle state.

3. The method according to claim 1 or 2, characterized in that, The method further comprises: The first device sends a message to the second device for requesting to communicate with the third device in an idle state.

4. The method according to any one of claims 1 to 3, characterized in that, The method further comprises: The first device sends a message to a fourth device for requesting a resource to communicate with the third device or for requesting whether to report data from the third device according to a region associated with a second cell; The second cell is a cell reselected by the first device, the fourth device is an access network device corresponding to the second cell, and the sent message comprises the identification information.

5. The method according to any one of claims 1 to 3, characterized in that, The method further comprises: The first device sends a message to a fourth device for requesting whether to communicate with the third device and / or whether to report data from the third device; The sent message comprises the identification information.

6. The method according to any one of claims 1 to 3, characterized in that, The method further comprises: The first device deletes information related to communication with the third device when reselecting to a second cell, and sends a message to a fourth device for requesting whether to report data from the third device; The sent message comprises the identification information.

7. The method according to any one of claims 1 to 3, characterized in that, The method further comprises: The first device deletes information related to communication with the third device and data from the third device when reselecting to a second cell.

8. The method according to any one of claims 1 to 3, characterized in that, The method further comprises: The first device sends a message to the second device for requesting a resource to communicate with the third device; the sent message comprises identification information associated with the first device and the third device.

9. The method of any one of claims 1 to 3, or claim 8, wherein, The method further comprises: The first device sends a message to the second device for requesting to report data from the third device; the sent message comprises the identification information.

10. The method according to any one of claims 1 to 9, characterized in that, The identification information comprises at least one of the following: A service identifier, a session identifier, a task identifier, a stocktaking region, a reader identifier, or an address of a core network element associated with the first device and the third device.

11. A communication method, comprising: The method comprises: The second device determines a valid time for a first resource used by a first device to communicate with a third device in an idle state; The second device sends a first message to the first device, the first message comprising the valid time.

12. The method of claim 11, wherein, The method further comprises: The second device sends first information and / or second information; The first information is used to indicate the first resource allocated for the first device; The second information is used to indicate the first device to communicate with the third device in an idle state.

13. The method according to claim 11 or 12, characterized in that, The method further comprises: The second device receives a message from the first device for requesting the first device to communicate with the third device in an idle state.

14. The method according to any one of claims 11 to 13, characterized in that, The method further comprises: The second device receives a message from the first device for requesting a resource for communication with the third device, or for requesting reporting data from the third device; The second device sends a message to a core network element for requesting confirmation of whether the first device communicates with the third device; The received message and the sent message comprise the identification information.

15. A method of communication, comprising: The method comprises: The fourth device receives a message from the first device for requesting a resource for communication with the third device, or for requesting whether to report data from the third device; The fourth device sends a message to a core network element for requesting confirmation of whether the first device communicates with the third device; The received message and the sent message comprise identification information associated with the communication between the first device and the third device.

16. The method of claim 15, wherein, The method further comprises: The fourth device receives a message from the core network element for confirming that the first device communicates with the third device, or for confirming that the first device does not communicate with the third device.

17. A communications device, characterized by The apparatus comprises means or modules for implementing the method of any of claims 1 to 16.

18. A communications device, characterized by The communication device comprises at least one processor; the at least one processor is configured to cause the communication device to implement the method of any of claims 1 to 16.

19. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer instructions, which, when executed, cause the computer to perform the method of any of claims 1 to 16.

20. A communication system, characterized by The communication system comprises at least a first device, a second device and a fourth device; The first device is configured to perform the method of any of claims 1 to 10; The second device is configured to perform the method of any of claims 11 to 14; The fourth device is configured to perform the method of claim 15 or 16.

21. A computer program product, characterised in that, The computer program product comprises computer program code, which, when run on a computer, causes the computer to perform the method of any of claims 1 to 16.

22. A communications device, characterized by The communication device comprises a logic circuit and an interface, the interface is configured to input and / or output information, and the logic circuit is configured to cause the communication device to perform the method of any of claims 1 to 16.

23. A chip, characterized by The chip further comprises an interface circuit, which is configured to receive the executed instructions and transmit to the processor, or output information from the processor.

24. The chip of claim 23, wherein, ​

Citation Information

Patent Citations

  • Communication method and apparatus

    CN113170415A

  • Method and apparatus for measuring cell

    CN113316972A

  • Method and device for determining effective duration of reference signal, and terminal

    CN116545595A

  • Data transmission method and device

    CN116761268A

  • Communication method and apparatus

    WO2023160624A1