Communication method and related device

Abstract

A communication method and a related device belong to the technical field of communication. In the communication method, a first access network device sends a first message to a terminal, correspondingly, the terminal receives the first message, and the first message comprises effective time T of a first resource for communication between the terminal and the device; and the terminal communicates with the device according to the first resource within the idle state effective time T. It can be seen that the terminal executes the A-IoT service in the idle state effective time T, and compared with the mode that the A-IoT service is executed only in the connected state, the execution efficiency of the A-IoT service is improved.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method and related apparatus. Background Technology

[0002] With the development of communication technology, various communication systems have emerged, such as the Ambient Internet of Things (A-IoT) technology. A-IoT in this context can consist of a reader and passive / semi-passive / active A-IoT devices. Both the reader and the A-IoT devices can be located within a cellular network. For example, the reader's functionality can be implemented by network devices or terminals, while the A-IoT devices can be implemented by terminals within the cellular network. In one possible A-IoT architecture, network devices and A-IoT devices communicate bidirectionally through intermediate nodes or unidirectionally through auxiliary nodes. Intermediate or auxiliary nodes can be terminals within the cellular network. When a terminal is in a connected state, it enables or assists the network device and A-IoT device in executing A-IoT services; however, it cannot support A-IoT services when the terminal is idle. Summary of the Invention

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

[0004] The communication method provided in this application involves 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 a terminal, or a circuit or chip in a terminal responsible for communication functions (such as a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip containing a modem core, or a system-in-package (SIP) chip). The second device is a network-side device, such as a network-side access network device, or a network-side distributed unit (DU), or a control unit (CU), or its components (such as circuits, chips, or chip systems). The third device is a device that implements A-IoT technology by communicating between the terminal and the network side, such as a tag, or an A-IoT terminal, or its components.

[0005] Firstly, the communication method provided in this application is illustrated using a first device as the terminal, a second device as the first access network device, and a third device as the device. This method is applied to the terminal side. In this method, the terminal receives a first message from the first access network device. The first message includes a first resource for a valid period of time for communication between the terminal and the device. During the valid idle time, the terminal communicates with the device according to the first resource.

[0006] As can be seen, in this method, the terminal communicates with the device based on the first resource during the effective idle time, enabling the terminal to execute A-IoT services in the idle state. Furthermore, compared to executing A-IoT services only in the connected state, this method improves the execution efficiency of A-IoT services.

[0007] Optionally, the effective time is the duration during which the first resource is used for communication between the terminal and the device, or the duration during which the first access network device allows the terminal to communicate with the device based on the first resource. This effective time may be referred to as the effective duration (or effective time) or activation duration (or activation time) of the first resource; or, the effective time is the timing duration of a timer that starts when the terminal receives the first message or when the terminal enters an idle state, and the terminal stops communicating with the device based on the first resource when the time expires; or, the effective time is the counting duration of a timer that starts counting when the terminal receives the first message or when the terminal enters an idle state, and stops communicating with the device based on the first resource when the counting time expires.

[0008] Optionally, after receiving the first message, the terminal enters an idle state and saves at least one of the context information related to device communication, such as the validity period or identification information.

[0009] It is evident that this implementation method facilitates the terminal entering an idle state and communicating with the device using the context information.

[0010] The first resource is the air interface resource or wireless resource for communication between the terminal and the device.

[0011] In one optional implementation, the first resource is an area-level resource pool, meaning that multiple cells share one or more resource pools; or, it is a cell-level resource, meaning that multiple terminals accessing the same cell can share the resource to perform A-IoT services; or, it is shared by multiple stations, and so on.

[0012] As can be seen, in this implementation, the first resource is not terminal-specific and can be pre-configured, saving signaling overhead.

[0013] In another optional implementation, the first resource is configured by the first access network device for the terminal at the terminal level (per UE). The method further includes: the terminal receiving first information, which indicates the first resource allocated by the first access network device for the terminal. Optionally, the first information may be included in a first message or received separately.

[0014] As can be seen, in this embodiment, the first access network device configures resources for communication between the terminal and the device separately. Thus, combined with the effective time (e.g., time T), the first access network device can avoid allocating the same resources to other terminals in the same cell within time T. If the same resources are allocated to other terminals in the same cell within time T, the first access network device can determine whether the distance between the terminals is sufficiently far based on their locations or determine the approximate distance between the terminals based on measurements. When this distance exceeds a distance threshold, the terminals can use the same resources to communicate with the device.

[0015] In one optional embodiment, the method further includes: the terminal receiving second information, the second information being used to instruct the terminal to communicate with the device in an idle state. Optionally, the second information may be carried in the first message and transmitted together, or transmitted relatively independently. In another optional embodiment, the second information is used to instruct the terminal to perform A-IoT services in an idle state. In yet another optional embodiment, the first message is a connection release message, the first message includes the second information, the second information being used to instruct the terminal to continue using the first resource, then the terminal can continue to use the first resource to communicate with the device in an idle state.

[0016] As can be seen, in this embodiment, the first access network device can explicitly instruct the terminal to communicate with the device in the idle state, which is beneficial for the first access network device to determine when the terminal is communicating with the device in the idle state based on the service type or the indication from the core network element, and then explicitly instruct the terminal through the second information.

[0017] In one alternative implementation, the terminal sends a message to the first access network device requesting communication with the device in an idle state.

[0018] As can be seen, in this embodiment, the terminal can actively request to communicate with the device in the idle state, which is beneficial for the terminal to actively request to the first access network device when determining whether to communicate with the device in the idle state based on the service type or the indication from the core network element.

[0019] In an optional implementation, the method further includes: the terminal sending a message to a first access network device to request resources for communicating with the device; the message sent includes identification information associated with the terminal communicating with the device.

[0020] As can be seen, in this embodiment, the terminal requests the resources to communicate with the device again when the validity period expires. Furthermore, the message includes the identification information, enabling the first access network device to request the core network element to confirm whether the terminal is communicating with the device, and thus determine whether to configure the requested resources for the terminal, even if it does not store the context information of the terminal's communication with the device.

[0021] In an optional implementation, the method further includes: the terminal sending a message to the first access network device requesting the reporting of data from the device, the message including identification information.

[0022] As can be seen, this implementation allows the terminal to request the reporting of acquired data via this message when it completes communication with the device. Furthermore, this message includes identification information, enabling the first access network device to request confirmation from the core network element, based on this identification information, whether the terminal is communicating with the device, and thus determine whether to instruct the terminal to report data, even if it does not store the context information of the terminal-device communication.

[0023] The method also involves a fourth device, which is a device on the access network equipment side that the terminal accesses after moving or reselecting a cell, such as a distributed unit (DU) or control unit (CU) or its components (e.g., circuits, chips, or chip systems) on the network side. For ease of explanation, the method is illustrated using the second access network equipment as an example of the fourth device.

[0024] In an optional implementation, the method further includes: the terminal sending a message to the second access network device requesting resources for communication with the device, or sending a message requesting whether to report data from the device, based on the area associated with the second cell. The second cell is a cell reselected by the terminal, and the message includes identification information.

[0025] As can be seen, in this embodiment, after the terminal reselects a cell in the idle state, it determines, based on the area associated with the reselected cell, whether to request resources to continue communicating with the device or to request whether to report the data already obtained and cease communication with the device. Optionally, the area associated with the second cell is the service area or coverage area of ​​the second cell, or the service area or storage area of ​​the A-IoT services supported by the second cell, etc.

[0026] In one optional implementation, the terminal sends a message to the second access network device requesting resources for communication with the device, or a message to the second access network device requesting whether to report data from the device, based on the area associated with the second cell. This includes: when the area associated with the second cell includes, is contained within, or is identical to, the terminal sends a message to the second access network device requesting resources for communication with the device, allowing the terminal to continue communication with the device based on the re-requested resources. When the area associated with the second cell does not include, is not contained within, or is different from, the terminal sends a message to the second access network device requesting whether to report data from the device, thus ceasing communication with the device and only requesting whether to report data. The first area is the area associated with communication between the terminal and the device.

[0027] As can be seen, in this embodiment, the terminal can combine the area associated with the reselected cell with the area associated with the terminal's communication with the device to determine whether to continue communicating with the device.

[0028] In another optional implementation, the terminal sends a message to the second access network device to request resources for communication with the device, or sends a message to the second access network device to request whether to report data from the device, depending on the area associated with the second cell. This includes: when the area associated with the second cell contains the terminal's location, the terminal sends a message to the second access network device to request resources for communication with the device to continue communicating with the device; when the area associated with the second cell does not contain the terminal's location, the terminal sends a message to the second access network device to request whether to report data from the device and ceases communicating with the device.

[0029] As can be seen, in this implementation, the terminal can determine whether to continue communicating with the device by combining its own location with the area associated with the reselected cell.

[0030] The messages sent by the terminal all contain identification information, which helps the second access network device to confirm with the core network element whether the terminal is communicating with the device or whether it is reporting data from the device.

[0031] In another optional implementation, whether the terminal continues to communicate with the device or reports the data it has obtained after reselecting a cell is determined by the core network element or by the terminal's default setting. The following describes three implementation methods, including but not limited to these three methods.

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

[0033] As can be seen, in this design, after the terminal reselects a cell in the idle state, it requests the core network through the second access network device to determine whether the terminal should continue communicating with the device and whether to report data, thus reducing the processing complexity of the terminal. Even if the terminal reselects to the second cell in the idle state and accesses the second access network device, the second access network device, which does not store the context information of the terminal's communication with the device, can still request confirmation from the core network element based on this identification information whether the terminal should continue communicating with the device and / or whether to report data from the device.

[0034] In another possible design, when the terminal reselects to the second cell, it deletes information related to device communication, such as the validity period, and sends a message to the second access network device to request whether to report the data obtained from the device. This message includes identification information.

[0035] As can be seen, in this design, after the terminal reselects a cell, it will no longer continue to communicate with the device by default, and can simply request whether to report the data it has obtained from the device, thus saving signaling overhead.

[0036] In another possible design, when the terminal reselects to the second cell, it deletes the relevant information about communication with the device and the data from the device.

[0037] As can be seen, in this design, the terminal stops communicating with the device by default after reselecting the cell, that is, it stops the A-IoT service, thus saving signaling overhead.

[0038] Optionally, in this application, the identification information includes at least one of the following: a service identifier, session identifier, task identifier, storage area, reader identifier, or the address of a core network element associated with terminal-device communication. The message sent by the terminal to the access network device contains the identification information, enabling the access network device to obtain information related to terminal-device communication based on this identification information even if the terminal-device communication context information is not stored during idle state.

[0039] Secondly, this application also provides a communication method. In one possible implementation, this 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 ease of explanation, the second device is taken as a first access network device. In this method, the first access network device determines a first resource for the terminal to communicate with the device in an idle state; the first access network device sends a first message to the terminal, the first message including the validity period.

[0040] As can be seen, in this method, the first access network device enables the terminal to communicate with the device based on the first resource during the effective idle time, thereby enabling the terminal to execute A-IoT services in the idle state. Furthermore, compared to the terminal only executing A-IoT services in the connected state, this method improves the execution efficiency of A-IoT services.

[0041] In an optional implementation, the method further includes: a first access network device sending first information, the first information indicating a first resource allocated to a terminal. Thus, in this implementation, the first access network device configures resources for communication between the terminal and the device individually. In this way, combined with a valid time period (e.g., time T), the first access network device can avoid allocating the same communication resources for other terminals in the same cell within time T. Alternatively, before allocating the same resources for other terminals in the same cell within the valid time period, the first access network device can determine whether the distance between each terminal is sufficiently far based on their location, or determine the approximate distance between terminals based on measurements. If this distance exceeds a distance threshold, the terminals can use the same resources (i.e., AIoT resources for communication with the device).

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

[0043] As can be seen, this implementation method is beneficial for the first access network device to promptly instruct the terminal to perform services when it determines that the terminal needs to perform services in the idle state based on the service type.

[0044] In one optional implementation, the method further includes: a first access network device receiving a message from a terminal requesting to communicate with the device in an idle state.

[0045] As can be seen, this implementation method allows the terminal to request the first access network device through this message when it determines whether it is communicating with the device in the idle state based on the service type.

[0046] In an optional implementation, the method further includes: a first access network device receiving a message from a terminal requesting resources to communicate with the device, or requesting to report data from the device; the first access network device sending a message to a core network element requesting confirmation of whether the terminal is communicating with the device; wherein the message received and sent by the first access network device includes identification information associated with the terminal's communication with the device. Therefore, before allocating resources for communication between the terminal and the device, or instructing 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 currently communicating with the device. Thus, even if the terminal is in an idle state and the first access network device has not saved the context information of the terminal's communication with the device, it can still request confirmation from the core network element based on the identification information.

[0047] Optionally, other alternative implementation methods and beneficial effects in this aspect can be found in the relevant content described in the first aspect, and will not be detailed here.

[0048] Thirdly, this application also provides a communication method. In one possible implementation, this method can be applied to a fourth device, namely, the device on the second access network equipment side after the terminal reselects. Taking the fourth device as the second access network equipment as an example, in this method, the second access network equipment receives a message from the terminal requesting resources to communicate with the equipment, or requesting whether to report data from the equipment; the second access network equipment sends a message to the core network element requesting confirmation of whether the terminal is communicating with the equipment. Both the message received from the terminal and the message sent to the core network element by the second access network equipment include identification information.

[0049] As can be seen, in this method, the terminal, while in an idle state, reselects a cell to access the second access network device. The second access network device does not store the context information of the communication between the terminal and the device, but it can still request confirmation of the above content from the core network element based on this identification information. This facilitates communication between the terminal and the device in the idle state, improving the execution efficiency of A-IoT services. Furthermore, this method allows the terminal to determine whether to continue communicating with the device after reselecting a cell.

[0050] Optionally, other alternative implementation methods and beneficial effects in this aspect can be found in the relevant content described in the first aspect, and will not be detailed here.

[0051] Fourthly, this application also provides a communication method. In another possible implementation, the method can be applied to a fourth device, namely, a device on the second access network device side after the terminal reselects. Taking the fourth device as the second access network device as an example, in this method, the second access network device receives a message from the terminal requesting whether to communicate with the device and / or whether to report data from the device; the second access network device sends a message to the core network element requesting confirmation of whether the terminal communicates with the device and / or whether to report data from the device; wherein the messages received and sent by the second access network device include identification information associated with the communication between the terminal and the device.

[0052] As can be seen, in this method, even if the terminal is in an idle state and the second access network device does not store the context information of the terminal's communication with the device, it can still request confirmation of the above content from the core network element based on the identification information. This facilitates communication between the terminal and the device in the idle state, improving the execution efficiency of A-IoT services. Furthermore, this method allows the core network element to determine whether the terminal should continue communicating with the device or whether the terminal should report the data it has obtained from the device.

[0053] Optionally, other alternative implementation methods and beneficial effects in this aspect can be found in the relevant content described in the first aspect, and will not be detailed here.

[0054] Fifthly, this application also provides a communication method. In one possible implementation, this method corresponds to the third aspect and is applied to a core network element. In this method, the core network element receives a message from a first access network device requesting confirmation of whether a terminal is communicating with the device. The received message includes identification information associated with communication between the terminal and the device. The core network element then sends a message to the first access network device confirming communication between the terminal and the device, or confirming that the terminal is not communicating with the device.

[0055] Optionally, the core network element performs an authorization determination on the terminal based on the identification information. If it determines that the terminal has the authority to execute A-IoT services or is communicating with the device, it sends a message to the first access network device to confirm that the terminal is communicating with the device. If it determines that the terminal does not have the authority or is not communicating with the device to execute A-IoT services, it sends a message to the first access network device to confirm that the terminal is not communicating with the device.

[0056] As can be seen, in this method, even if the terminal is in an idle state, the first access network device can still confirm whether the terminal is communicating with the device through the core network element, even if the first access network device does not save the context information of the terminal communicating with the device. This allows the first access network device to know whether to continue configuring resources for the terminal to communicate with the device or to instruct the terminal to report data from the device.

[0057] Optionally, other alternative implementation methods and beneficial effects in this aspect can be found in the relevant content described in the third aspect, and will not be detailed here.

[0058] Sixthly, this application also provides a communication method. In another possible implementation, this method corresponds to the fourth aspect and can be applied to a core network element. In this method, the core network element receives a message from a second access network device requesting whether a terminal is communicating with the device and / or whether it is reporting data from the device. The received message includes identification information associated with the terminal communicating with the device. The core network element sends the following messages to the second access network device: a message confirming that the terminal is communicating with the device; a message confirming that the terminal is reporting data from the device; or a message confirming that the terminal is not communicating with the device and is not reporting data from the device.

[0059] The difference between this method and the method described in the fifth aspect is that, in the fifth aspect, the first access network device is used to request whether the terminal is communicating with the device, such as whether it is currently communicating with the device; in the sixth aspect, the second access network device is used to request whether the terminal is communicating with the device and / or whether it is reporting data from the device. The method described in the sixth aspect can be applied to situations where the terminal reselects a cell from the first access network device to access the second access network device. This facilitates the core network element in confirming whether the terminal should continue communicating with the device or report the data already obtained from the device. Thus, even if the terminal is in an idle state and the second access network device cannot obtain the context information of the terminal's communication with the device from the source access network device (i.e., the first access network device), the core network element can still confirm whether to continue communicating with the device or report the data already obtained from the device based on the identification information reported by the terminal.

[0060] Optionally, other alternative implementation methods and beneficial effects in this aspect can be found in the relevant content described in the fourth aspect, and will not be detailed here.

[0061] Seventhly, this application also provides a communication method, which is based on the communication methods described in the first to sixth aspects. One possible implementation of this method describes the interaction between a terminal, a first access network device, a second access network device, and core network elements. The second access network device is the access network device that the terminal accesses after reselecting a cell from the first access network device.

[0062] In this method, the first access network device determines the effective time for the first resource to be used for the terminal to communicate with the device in the idle state; the first access network device sends a first message to the terminal, the first message including the effective time; accordingly, the terminal receives the first message and communicates with the device according to the first resource during the effective time in the idle state.

[0063] As can be seen, in this method, the terminal communicates with the device based on the first resource during the effective time of the idle state, so as to realize the execution of A-IoT services in the idle state. Compared with the terminal only executing A-IoT services in the connected state, this method greatly improves the execution efficiency of A-IoT services.

[0064] In one optional implementation, the terminal sends a message to a first access network device requesting resources for communication with the device. The message includes identification information associated with the terminal's communication with the device. Correspondingly, the first access network device receives the message and sends a message to a core network element requesting confirmation of whether the terminal is communicating with the device. The message sent by the first access network device includes the identification information. The core network element receives the message and sends a message to the first access network device confirming communication between the terminal and the device, or confirming that the terminal is not communicating with the device. This implementation allows the terminal to request resources from the first access network device again if it fails to complete communication with the device within the valid time. Even if the first access network device does not save the context information of the terminal's communication with the device, it can still send a message containing the identification information to the core network element, allowing the core network element to confirm whether the terminal is communicating with the device. This facilitates the first access network device reallocating resources for communication between the terminal and the device.

[0065] Optionally, the first access network device receives a message from the core network element confirming communication between the terminal and the device, and allocates resources to the terminal for communication with the device. Alternatively, the first access network device receives a message from the core network element confirming that the terminal is not communicating with the device, and sends a service completion instruction to the terminal, causing the terminal to terminate communication with the device.

[0066] In one optional implementation, the terminal sends a message to a first access network device requesting the reporting of data from the device. This message includes identification information. Correspondingly, the first access network device receives this message and sends a message to a core network element requesting confirmation of whether the terminal is communicating with the device. The message sent by the first access network device includes identification information. The core network element receives this message and sends a message to the first access network device confirming communication between the terminal and the device, or confirming that the terminal is not communicating with the device. This implementation allows the terminal to request data reporting from the first access network device when it completes communication with the device within the effective timeframe. Even if the first access network device does not store the context information of the terminal's communication with the device, it can still send a message containing identification information to the core network element, allowing the core network element to confirm whether the terminal is communicating with the device, thus enabling the first access network device to instruct the terminal to report the obtained data.

[0067] Optionally, the first access network device receives a message confirming communication between the terminal and the device, instructing the terminal to report data from the device. Alternatively, the first access network device receives a message confirming that the terminal is not communicating with the device, and sends a service completion instruction to the terminal, causing the terminal to terminate communication with the device.

[0068] In one optional implementation, the terminal sends a message to the second access network device requesting resources for communication with the device, or a message to the second access network device requesting whether to report data from the device, based on the area associated with the second cell. Correspondingly, the second access network device receives the message and sends a message to the core network element requesting confirmation of whether the terminal is communicating with the device. The core network element receives the message and sends a message to the second access network device confirming that the terminal is communicating with the device, or confirming that the terminal is not communicating with the device. Both the message received by the second access network device from the terminal and the message sent to the core network element include identification information.

[0069] As can be seen, this implementation method is advantageous because even if the terminal reselects a second cell while in an idle state and accesses the second access network device, the second access network device, which does not store the context information of the terminal's communication with the device, can still request confirmation from the core network element based on this identification information whether the terminal is communicating with the device. In other words, in this implementation method, after the terminal reselects a cell in an idle state, the terminal itself determines whether to continue communicating with the device.

[0070] Optionally, in the above embodiments, the core network element determines the A-IoT service associated with the identification information, or determines the terminal associated with the identification information that is communicating with the device, and performs an authorization judgment on the terminal. If the terminal has the authority to execute the A-IoT service or it is determined that the terminal is communicating with the device, it sends a message to the first access network device to confirm that the terminal is communicating with the device; if the terminal does not have the authority to execute the A-IoT service or it is determined that the terminal is not communicating with the device, it sends a message to the first access network device to confirm that the terminal is not communicating with the device.

[0071] In another optional implementation, the terminal sends a message to the second access network device requesting whether to communicate with the device and / or whether to report data from the device. Correspondingly, the second access network device receives this message and sends a message to the core network element requesting whether the terminal communicates with the device and / or whether to report data from the device. The core network element receives this message and sends the following messages to the second access network device: a message confirming that the terminal is communicating with the device; a message confirming that the terminal is reporting data from the device; or a message confirming that the terminal is not communicating with the device and is not reporting data from the device. Both the messages received and sent by the second access network device contain identification information.

[0072] This implementation method allows the terminal, after reselecting a cell in the idle state, to request the core network via the second access network device to determine whether the terminal should continue communicating with the device and whether to report data. Furthermore, even if the terminal reselects a second cell while in the idle state, and the second access network device does not store the context information of the terminal's communication with the device, the second access network device can still request confirmation from the core network element based on this identification information whether the terminal should continue communicating with the device and / or whether to report data from the device.

[0073] Optionally, when the second access network device receives a message confirming communication between the terminal and the device, it allocates resources for communication between the terminal and the device; when it receives a message confirming the reporting of data, it instructs the terminal to report the data of the device; when it receives a message confirming that the terminal is not communicating with the device and is not reporting the data of the device, it instructs the terminal to complete communication with the device, i.e., to stop the AIoT service.

[0074] In another optional implementation, the terminal sends a message to the second access network device 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 requesting whether the terminal should report data from the device; the core network element receives the message and sends the following messages to the second access network device: a message confirming that the terminal has reported data from the device; or a message confirming that the terminal has not reported data from the device. Both the messages received and sent by the second access network device contain identification information.

[0075] In this implementation, when the terminal reselects a second cell in the idle state, it defaults to not continuing communication with the device and only needs to request whether to report the data it has obtained. Optionally, the terminal can also release the context information of communication with the device, such as the validity period and / or the resources used for communication with the device.

[0076] In another optional implementation, the terminal releases the context information for communication with the device and / or deletes data from the device. Therefore, in this implementation, the terminal stops communicating with the device by default when reselecting a second cell in the idle state.

[0077] Other optional implementation methods and beneficial effects in the seventh aspect can be found in the relevant content described in the first to sixth aspects, and will not be detailed here.

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

[0079] This application also provides a communication method in which a terminal receives a first message from a first access network device, the first message including a first resource for communication between the terminal and the device; the terminal communicates with the device in an idle state according to the first resource. Optionally, the first message may be a connection release message.

[0080] This application also provides a communication method in which a terminal receives a first message from a first access network device, the first message including indication information that the terminal communicates with the device in an idle state; the terminal communicates with the device in an idle state.

[0081] This application also provides a communication method in which a terminal receives a first message from a first access network device. The first message includes 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. In the idle state, the terminal communicates with the device according to the first resource.

[0082] This application also provides a communication method in which a terminal receives a first message from a first access network device, the first message including a first resource and a valid time for the first resource to be used for communication between the terminal and the device; the terminal communicates with the device according to the first resource during the valid time of the idle state.

[0083] This application also provides a communication method in which a terminal receives a first message from a first access network device. The first message includes a first resource, a valid time for the first resource to be used for communication between the terminal and the device, and indication information for the terminal to communicate with the device in an idle state. During the valid time of the idle state, the terminal communicates with the device according to the first resource.

[0084] As can be seen, in the above communication method, after receiving the first message, the terminal can enter an idle state to communicate with the device and execute A-IoT services, thereby improving the execution efficiency of A-IoT services. Furthermore, optional implementations of the above communication method can also be found in the relevant content described in aspects one through six, and will not be detailed here.

[0085] Optionally, the indication that the terminal communicates with the device in the idle state can be an indication that allows the terminal to communicate with the device in the idle state. This indication can be replaced by an indication that the terminal performs A-IoT services in the idle state, or an indication that the terminal continues to use the first resource in the idle state, or an indication that the terminal continues to use the first resource, etc.

[0086] Optionally, the resources used by the terminal to communicate with the device in the idle state and the resources used by the terminal to communicate with the device in the connected state may be the same or different, or partially the same. They may be indicated relatively separately or together.

[0087] Eighthly, this application provides a communication device that has the function of implementing any one of the first to sixth aspects or any optional implementation of any one aspect. For example, the communication device includes modules, units or means corresponding to the operations involved in any one of the first to sixth aspects or any optional implementation of any one aspect. The modules, units or means can be implemented by software, or by hardware, or by a combination of software and hardware.

[0088] Ninthly, this application provides a communication device including an interface circuit and one or more processors. The one or more processors are coupled to a memory. The memory stores part or all of the necessary computer program or instructions for implementing the functions involved in any one of the first to sixth aspects or any optional embodiments thereof. The one or more processors are executable to carry out the computer program or instructions, which, when executed, cause the communication device to implement the methods in any one of the first to sixth aspects or any possible design or implementation thereof. The interface circuit is used to implement the communication functions within the communication device and / or the communication functions between the communication device and other devices or components.

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

[0090] In one possible design, the communication device may also include the memory.

[0091] The aforementioned communication device may be a terminal, or a communication / processing module within a terminal, or a chip within a terminal responsible for communication functions such as a modem chip (also known as a baseband chip), or a SoC or SIP chip containing a modem module, or a circuit or chip within a terminal responsible for processing functions (such as a GPU). The aforementioned communication device may also be a network device, or a communication / processing module within a network device, or a chip within a network device responsible for communication functions such as a modem chip (also known as a baseband chip), or a SoC or SIP chip containing a modem module, or a circuit or chip within a network device responsible for processing functions (such as a GPU).

[0092] In a tenth aspect, this application provides a communication system comprising 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 embodiment thereof, and the second communication device is configured to perform the method described in the second aspect or any possible embodiment thereof. Optionally, the communication system further comprises a third communication device, configured to perform the method described in the third aspect or any possible embodiment thereof, or to perform the method described in the fourth aspect or any possible embodiment thereof. Optionally, the communication system further comprises a core network element, configured to perform the method described in the fifth aspect or any possible embodiment thereof, or to perform the method described in the sixth aspect or any possible embodiment thereof.

[0093] In one aspect, this application provides a computer-readable storage medium storing computer-readable instructions that, when read and executed by a computer, cause the computer to perform any of the possible designs in the first to sixth aspects described above.

[0094] In a twelfth aspect, this application provides a computer program product that, when read and executed by a computer, causes the computer to perform any of the possible designs in the first to sixth aspects described above. Attached Figure Description

[0095] Figure 1 This is a schematic diagram of a 5G communication system architecture to which this application is applicable;

[0096] Figure 2 This is a schematic diagram of an open access network framework;

[0097] Figure 3 This is an architectural diagram of an ORAN device;

[0098] Figures 4 to 7This is a schematic diagram of the network architecture of A-IoT technology;

[0099] Figures 8 to 14 This is a flowchart illustrating the communication method provided in an embodiment of this application;

[0100] Figure 15 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0101] Figure 16 This is a schematic diagram of the structure of a terminal provided in an embodiment of this application. Detailed Implementation

[0102] This application can be applied to various communication systems, including but not limited to: Long Term Evolution (LTE) systems, 5th Generation (5G) systems, such as new radio access technology (NR), multi-system converged networks, Internet of Things (IoT) systems, vehicle-to-everything (V2X) systems, open-radio access network (O-RAN) systems, and future communication systems such as 6th Generation (6G) systems.

[0103] Figure 1 This is a schematic diagram of a 5G communication system architecture to which this application is applicable. The 5G communication system architecture is the 5G network infrastructure. Network functions are based on modular decomposition, and decoupled network functions (NFs) can be independently expanded, evolved, and deployed on demand. All NFs in the control plane use service-oriented interfaces, allowing the same service to be called by multiple NFs, reducing the coupling between interface definitions and ultimately enabling on-demand customization of the entire network's functions, flexibly supporting different business scenarios and requirements. Figure 1 In the architecture shown, the network elements within the dashed boxes are service-oriented network elements (NFs). The interfaces between NFs are service-oriented interfaces, and the messages exchanged are service-oriented messages. This architecture may include an access network and a core network, and optionally, it may also include user equipment (UE).

[0104] A UE (User Equipment) is a wireless transceiver device that can be deployed on land, including indoors or outdoors, handheld, wearable, or vehicle-mounted; it can also be deployed on water (such as on ships); and it can be deployed in the air (such as on airplanes, balloons, and satellites). A UE can be a mobile phone, tablet, computer with wireless transceiver capabilities, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal in industrial control, vehicle-mounted terminal device, wireless terminal in self-driving, wireless terminal in remote medical care, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, wearable terminal device, etc. A UE may also be referred to as a 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 device, etc. The UE can be fixed or mobile. Optionally, the device used to implement the terminal's functions can be a terminal itself; it can also be a device capable of supporting the terminal in implementing these functions, such as a chip system, a communication module, or a modem, which can be installed in the terminal. In the embodiments of this application, the chip system can be composed of chips or can include chips and other discrete devices. In the technical solutions provided in the embodiments of this application, the device used to implement the terminal's functions is a terminal, and the terminal is a UE, as an example, to describe the technical solutions provided in the embodiments of this application. The embodiments of this application do not limit the specific technology or specific device form adopted by the terminal device. In one possible implementation, the UE can be used as a base station. For example, the UE can act as a scheduling entity, providing sidelink signals between UEs in V2X, D2D, or P2P, without relaying communication signals through a base station. In another possible implementation, the UE can also be used as a relay node. For example, the UE can act as a relay device or an integrated access and backhaul (IAB) node to provide wireless backhaul services to the terminal device.

[0105] The access network is used to implement access-related functions. It can provide network access functionality for authorized users in a specific area and determine transmission tunnels of different qualities to transmit user data based on user level, service requirements, etc. The access network forwards control signals and user data between terminal equipment and the core network. The access network may include access network equipment. For example, in this application, information exchanged between terminal equipment and network elements of the core network can be forwarded through access network equipment. Access network equipment is equipment that provides access for terminal equipment and may include radio access network (RAN) equipment and access network (AN) equipment. RAN equipment is mainly responsible for functions such as radio resource management, quality of service (QoS) management, data compression, and encryption on the air interface side. RAN equipment may include various forms of base stations (BS), such as macro base stations, micro base stations (also known as small stations), relay stations, access points, balloon stations, etc.

[0106] In systems employing different wireless access technologies, the names of devices with base station functions may vary. For example, the base station involved in this application embodiment may be a base station in 5G, a base station in a 6G mobile communication system, an access network device or module of an access network device in an open radio access network (O-RAN) system, a base station in a future mobile communication system, an access node in a WiFi system, or an evolved node B (eNB) in LTE, etc. Among these, a base station in 5G may also be referred to as a transmission reception point (TRP) or a 5G base station (next-generation node B, gNB). Base stations can also be replaced by names such as: wireless access point, node B, transmitting point (TP), master MeNB, secondary SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), centralized unit (CU), distributed unit (DU), location node, IAB donor, etc. Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move according to the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0107] Optionally, the RAN equipment may also be a device that includes a CU, or a DU, or a device that includes both CU and 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 equipment may include gNB-CU-CP, gNB-CU-UP, and gNB-DU.

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

[0109] RAN equipment can support one or more types of fronthaul interfaces, with different fronthaul interfaces corresponding to DUs and RUs with different functions. If the fronthaul interface between the DU and RU is a common public radio interface (CPRI), the DU is configured to implement one or more baseband functions, and the RU is configured to implement one or more radio frequency functions. If the fronthaul interface between the DU and RU is another type of interface, relative to CPRI, some downlink and / or uplink baseband functions, such as, for downlink, precoding, digital beamforming (BF), or one or more of inverse fast Fourier transform (IFFT) / cyclic prefix addition (CP), are moved from the DU to the RU; and for uplink, one or more of digital beamforming (BF), or fast Fourier transform (FFT) / cyclic prefix removal (CP), are moved 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 segmentation between DU and RU differs, corresponding to different categories (Cat) of eCPRI, such as eCPRI Cat A, B, C, D, E, F.

[0110] Taking eCPRI Cat A as an example, for downlink transmission, the DU is configured to implement one or more functions preceding and following layer mapping (i.e., coding, rate matching, scrambling, modulation, and layer mapping), while other functions following layer mapping (e.g., resource element (RE) mapping, digital beamforming (BF), or one or more functions following inverse fast Fourier transform (IFFT) / cyclic prefix (CP) addition) are moved to the RU. For uplink transmission, the DU is configured to implement one or more functions preceding and following de-mapping (i.e., decoding, rate matching de-mapping, descrambling, demodulation, inverse discrete Fourier transform (IDFT), channel equalization, and de-RE mapping), while other functions following de-mapping (e.g., digital BF or fast Fourier transform (FFT) / CP removal) are moved to the RU. It is understandable that the functional descriptions of the DU and RU corresponding to various types of eCPRI can be found in the eCPRI protocol, and will not be elaborated here.

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

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

[0113] In this embodiment, the apparatus for implementing the functions of a network device can be a network device itself; it can also be an apparatus capable of supporting the network device in implementing those functions, such as a chip system, hardware circuit, software module, or a hardware circuit plus a software module. This apparatus can be installed in the network device or used in conjunction with the network device. In this embodiment, the example of a network device being used to implement the functions of a network device is provided only and does not constitute a limitation on the solutions described in this embodiment.

[0114] The core network is responsible for maintaining the subscription data of the mobile network and providing UEs with functions such as session management, mobility management, policy management, and security authentication. The core network may include the following network elements: User Plane Function (UPF) network elements, Authentication Server Function (AUSF) network elements, Access and Mobility Management Function (AMF) network elements, Session Management Function (SMF) network elements, Network Slice Selection Function (NSSF) network elements, Network Exposure Function (NEF) network elements, Network Function Repository Function (NRF) network elements, Policy Control Function (PCF) network elements, Unified Data Management (UDM) network elements, Unified Data Repository (UDR) network elements, Location Management Function (LMF) network elements, Home Gateway Mobile Location Center (HGMLC) network elements, Visited Gateway Mobile Location Center (VGMLC) network elements, and Application Function (AF) network elements.

[0115] The AMF (Agency Flow Management) network element is primarily responsible for mobility management in mobile networks, such as user location updates, user network registration, and user handover. The SMF (Segment Flow Management) network element is primarily responsible for session management in mobile networks, such as session establishment, modification, and release. Specific functions include assigning Internet Protocol (IP) addresses to users and selecting a UPF (User Provider Function) to provide packet forwarding. The UPF (User Provider Function) network element is primarily responsible for forwarding and receiving user data. It can receive user data from the data network and transmit it to the UE (User Equipment) through access network equipment; it can also receive user data from the UE through access network equipment and forward it to the data network. The PCF (Programmable Flow Management) network element primarily supports providing a unified policy framework to control network behavior, providing policy rules to control layer network functions, and is responsible for obtaining user subscription information related to policy decisions. The PCF network element can provide policies to the AMF and SMF network elements, such as Quality of Service (QoS) policies and slice selection policies. The AUSF (User Safe Flow Management) network element is used to perform UE security authentication. The NSSF (User Safe Flow Management) network element is used to select network slices for the UE. The NEF (Network Element Default Configuration) network element is primarily used to support the opening of capabilities and events. UDM / UDR network elements are used to store user data, such as subscription data and authentication / authorization data. AF network elements primarily support interaction with the 3GPP core network to provide services, such as influencing data routing decisions, policy control functions, or providing third-party services to the network side.

[0116] NRF network elements primarily provide service registration, discovery, and authorization, and maintain information on available network function (NF) instances. They enable on-demand configuration of network functions and services, as well as interconnection between NFs. Service registration means that an NF can only provide services after registering with the NRF network element. Service discovery means that when an NF needs services from other NFs, it must first perform service discovery through the NRF network element to find the desired NF providing the service. For example, if NF element 1 needs services from NF element 2, it must first perform service discovery through the NRF network element to find NF element 2.

[0117] The data network (DN) is used to provide services to users. It can be a private network, such as a local area network (LAN); an external network not controlled by the operator, such as the Internet; or a proprietary network jointly deployed by operators, such as a network providing an IP multimedia subsystem (IMS). The UE can access the DN through an established protocol data unit (PDU) session.

[0118] in addition, Figure 1 In the illustrated 5G communication system architecture, the UE and AMF can interact via the N1 interface. Interactions between other network function elements are similar; for example, the AN and AMF can interact via the N2 interface, and the N3 interface supports selective activation / deactivation of user plane connections. The SMF and UPF elements interact via the N4 interface, and the UPF and DN elements interact via the N6 interface. All NFs in the control plane can interact via service-oriented interfaces. For example, the LMF element can interact with other network function elements via the service-oriented interface N1mf, and the interface between the LMF and AMF elements is NL1. The NSSF element can interact with other network function elements via the service-oriented interface Nnssf. The NEF element can interact with other network function elements via the service-oriented interface Nnef. The NRF element can interact with other network function elements via the service-oriented interface Nnrf. The PCF element can interact with other network function elements via the service-oriented interface Npcf. The UDM element can interact with other network function elements via the service-oriented interface Nudm. AF network elements can interact with other network function elements via the service interface Naf. AUSF network elements can interact with other network function elements via the service interface Nausf. AMF network elements can interact with other network function elements via the service interface Namf. SMF network elements can interact with other network function elements via the service interface Nsmf.

[0119] Optionally, the 5G communication system architecture can also adopt a non-3GPP system architecture, allowing terminal devices and the 3GPP core network to interconnect using non-3GPP technologies. These non-3GPP technologies may include, but are not limited to: Wireless Fidelity (Wi-Fi), Worldwide Interoperability for Microwave Access (WiMAX), and Code Division Multiple Access (CDMA) networks.

[0120] This application also applies to open RAN (ORAN) architectures. Figure 2 This is a schematic diagram of an Open RAN (Organic Access Network) system. An ORAN system may include access network equipment, terminal equipment, and core network equipment. The ORAN system may include other components besides those shown in the diagram. For example... Figure 2As shown, access network equipment (e.g., eNB, gNB, or next-generation access network equipment) communicates with core network (CN) equipment via a backhaul link and with user equipment (UE) via an air interface. For example, a BBU in the access network equipment communicates with the core network via a backhaul link, and an RU in the access network equipment communicates with at least one UE via an air interface. The BBU communicates with at least one RU via a fronthaul link; the BBU and RU may or may not be co-located. The BBU includes at least one CU and at least one DU, which can communicate via at least one midhaul link. In the ORAN system, the CU can also be an O-CU, and the DU can also be an O-DU.

[0121] Figure 3 This is a framework structure diagram involving RIC modules under an ORAN architecture. (Example:) Figure 3 As shown, the communication system includes a RAN (Radio Access Network Intelligent Controller, RIC). For example, the RIC can be used to implement AI-related functions. RICs include near-real-time RICs (near-RT RICs) and non-real-time RICs (non-RT RICs). Non-real-time RICs primarily process non-real-time information, such as data that is not sensitive to latency, with latency in the order of seconds. Real-time RICs primarily process near-real-time information, such as data that is relatively sensitive to latency, with latency in the order of tens of milliseconds.

[0122] Near real-time (NRT) RICs are used for model training and inference. For example, they are used to train artificial intelligence (AI) models and then use those AI models for inference. NRT RICs can obtain network-side and / or terminal-side information from RAN nodes (e.g., CUs, CU-CPs, CU-UPs, DUs, and / or RUs) and / or terminals. This information can be used as training data or inference data. NRT RICs can deliver inference results to RAN nodes and / or terminals. Inference results can be exchanged between CUs and DUs, and / or between DUs and RUs. For example, a NRT RIC delivers an inference result to a DU, which then forwards it to an RU.

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

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

[0125] In a communication system, network elements are connected via interfaces (e.g., NG interfaces, Xn interfaces) or over-the-air interfaces. These network elements, such as core network elements, access network devices, terminals, or one or more devices in the OAM (Operational Access Management) system, are equipped with one or more AI modules. Access network devices can be standalone RAN nodes or can comprise multiple RAN nodes, such as CUs and DUs. The CU and / or DU can also be equipped with one or more AI modules. Optionally, the CU can be further divided into CU-CPs and CU-UPs, with one or more AI models configured in the CU-CP and / or CU-UP.

[0126] AI modules are used to implement corresponding AI functions. AI modules deployed in different network elements can be the same or different. Depending on the parameter configuration, an AI module can perform different functions. An AI module can have one or more models. A model can infer an output, which includes one or more parameters. The learning, training, or inference processes of different models can be deployed on different nodes or devices, or they can be deployed on the same node or device.

[0127] Based on the infrastructure of the communication system, such as A-IoT technology, the device communicating with the terminal in this application can be a tag or an A-IoT terminal (or A-IoT device). Here, the A-IoT terminal is a standalone device that implements the tag's function, or it can integrate the tag with the terminal device, meaning the tag is part of the terminal device.

[0128] In one implementation of A-IoT technology, a reader and a tag (also called a tag, electronic tag, or tag device) may be included. The reader interacts with the tag to manage it. The reader and tag communicate via contactless data transmission. The tag's function is simple; it requires stimulation from the reader to transmit information. Specifically, the tag converts the wireless signal emitted by the reader into energy, which powers its operation. A tag is a miniature wireless transceiver device, primarily consisting of a built-in tag device antenna, coupling element, and chip. The tag's chip contains storage space capable of supporting the reader's reading and writing of tag data. After receiving the radio frequency signal transmitted by the reader through the antenna, the tag can couple the radio frequency signal through the coupling element. This coupling channel provides energy to the tag's chip and allows the data stored in the chip to be fed back 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 transmits a reflected signal based on the carrier signal reflection. The tag can adjust the information to be transmitted within the reflected signal. By using the above methods, the tag can receive downlink signals using a low-precision, low-power, medium-to-low frequency ring oscillator or a completely local oscillator-free method, which can further reduce the power consumption of the tag's downlink reception.

[0129] The tags support power consumption at the microwatt or microwatt level, but cannot support complex designs. The primary application of A-IoT technology is identification, and it can also be used for data reading and writing. The tags have the following characteristics: simple tag design, with application layer and air interface signaling integrated into a single design; supporting power consumption at the microwatt or microwatt level, but unable to support complex designs or measurements; time-division multiplexing is used for multi-tag communication, and multiple tags are read serially. It does not support the distinction between frequency and code domains, resulting in poor parallel performance. In addition, the tags also feature low power consumption. For example, the power consumption of different types of tags is described below: Passive tags: ~1μW power consumption. Passive tags themselves have no energy storage capacity. The energy for receiving and transmitting signals comes entirely from the radio frequency energy of the reader. Uplink transmission relies on reflection communication, requiring the reader to send a carrier signal to trigger the passive tag to send a reflected signal, using radio frequency energy to send the uplink signal to the reader; Semi-passive tags: ~100μW power consumption. Compared to passive tags, semi-passive tags can store some energy (e.g., using capacitors). Therefore, the transmission power consumption can be greater than that of passive tags. Communication also relies on reflection communication, but the communication capability is stronger than that of passive tags (transmission rate, etc.); Active tags: ~50mW power consumption. Active tags have their own batteries and can actively send signals, not relying on reflected signals for communication, resulting in stronger communication capabilities. Among them, passive tags and semi-passive tags can use a backscatter-based communication method, while active tags use a carrier-generating communication method.

[0130] Another classification method divides tags into three types: Device A: No energy storage, cannot generate signals independently, and uses backscattering for signal transmission; Device B: Has energy storage but cannot generate signals independently, also uses backscattering for signal transmission, and its stored energy amplifies the reflected signal; Device C: Has energy storage, can generate signals independently, and has active radio frequency components for transmission. Tags use low-precision, low-power mid-to-low frequency ring oscillators or completely oscillator-less receivers for downlink signals. During operation, the energy and carrier wave for communication are supplied by the reader, and communication is based on the reflected carrier wave.

[0131] A-IoT technology applies A-IoT technology to mobile communication systems, such as 5G systems. Both readers and tags are devices within the mobile communication system. This communication network, based on cellular network infrastructure and composed of readers and tags, can be called a passive Internet of Things (IoT) network or environmental IoT (A IoT or A-IoT). For example, the reader's function can be implemented by access network devices, such as base stations. The A-IoT terminal can be implemented by terminal devices in the cellular network, such as ultra-low power, ultra-low complexity IoT terminals, i.e., the first type of terminal. The access network device and the A-IoT terminal can perform contactless data communication, thereby reading information from the A-IoT terminal and / or writing information that needs to be stored into the A-IoT terminal. It can be understood that in this application, the access network device can have the function of a reader; the A-IoT terminal can have the function of a tag, or the A-IoT terminal can be a terminal device in an AIoT or IoT system. The reader / writer can be a handheld or fixed device for reading or writing information from A-IoT terminals. It can also be understood as a device that communicates with A-IoT terminals. The reader / writer can be a terminal device, an access network device, or any device with read / write capabilities. It can also be an IAB node or a relay node. Optional details regarding the forms of access network devices and terminal devices can be found above and will not be elaborated here.

[0132] In this application, the terminal communicates with the device to execute a first service, which is device-related and is a currently ongoing or upcoming service. The first service includes one or more of the following: inventory management, command service, location service, sensing service, proximity determination, read service, write service, deactivation service, lock service, or security service (such as authentication, authorization, registration, etc.), or it may be a newly defined service type in the future; the specific naming is not limited. The term "service" can also be replaced with "task," "session," "request," "transaction," "process," "procedure," or "service," etc., and this application embodiment does not limit the name. For example, the first service can also be called a first task, and the inventory management service can also be called an inventory management task, an inventory management request, an inventory management process, or an inventory management transaction, etc.

[0133] In this embodiment, the first service can also be a process-related service (a process between the terminal and the device), such as including at least one of the following: an access process, or a data transmission process, etc., which can be understood as performing the first service being equivalent to performing the corresponding process. The access process can be random access, such as contention-based random access or contention-free random access. Optionally, the access process may include reporting a device ID, such as the identifier of the device communicating with the terminal. The data transmission process can be device-to-reader (D2R) uplink data transmission, reader-to-device (R2D) downlink data transmission, etc. Optionally, the data transmission process may also include reporting a device ID. Optionally, the access process and the data transmission process are not strictly distinguished, and they can be combined for execution. For example, data transmission can also occur within the access process, such as contention-free random access, where the device can send D2R / uplink data in the first message. The terminal can handle different processes of the first service. The first service can be associated with a service triggered by a core network element or access network device, or it can be associated with a process.

[0134] The following are examples of one or more of the following aspects of the first business:

[0135] Inventory Management: Also known as inventory counting, inventory management involves retrieving device identification information. For example, a reader can use query and acknowledge (ACK) commands to obtain this information. To facilitate device inventory, devices are assigned four session identifiers (S0-S3), each corresponding to two inventory states: A and B. The inventory state is indicated by a sessionInventoried flag. When a reader selects a device, its select command includes a session identifier, which the device stores. When the reader performs an inventory management operation on the device, its query command includes this session identifier, allowing the device to flip its inventory state from A to B. If the reader sends another query command to perform the inventory management operation, the device will not respond because its inventory state is B, thus preventing the same device from being inventoryed multiple times in a single inventory cycle.

[0136] Read service: The read service can read the electronic product code (EPC), device identifier (TID), content stored in the device's reserved area, or content stored in the user's storage area from the device's storage area.

[0137] Write operations: Write operations can perform write operations on the device's storage area.

[0138] Inactivation service: Inactivation service can render equipment permanently unusable.

[0139] Locking services: Locking services can lock information on a device, preventing read or write operations on that device. Alternatively, locking services can also lock a storage area, preventing or allowing read or write operations on that storage area.

[0140] In one possible implementation, the network architecture of A-IoT technology may include, but is not limited to, Figure 4 , Figure 5 , Figure 6a , Figure 6b and Figure 7 The architecture shown is part or all of the architecture.

[0141] Figure 4 The architecture shown includes access network devices (such as base stations) and A-IoT terminals. The access network devices have reader / writer functionality and can communicate with the A-IoT terminals as readers / writers. The communication interface between the access network devices and the A-IoT terminals is a UU interface (or an A-IoT-UU interface). Figure 4 As shown, the A-IoT terminal directly communicates bidirectionally with the access network equipment, exchanging data and / or signaling under the first service.

[0142] Figure 5 This illustrates another network architecture for A-IoT technology. For example... Figure 5 As shown, the communication system includes access network equipment, intermediate nodes, and A-IoT terminals. In this system, the intermediate node acts as a relay node between the access network equipment and the A-IoT terminal. The A-IoT terminal transmits information to the intermediate node, which then forwards the information to the access network equipment via the UU interface. The A-IoT terminal can connect to the intermediate node via the UU interface, and the intermediate node then connects to the base station via the UU interface. The intermediate node can be either an IAB node or a terminal device. The terminal device acts as a relay node between the access network equipment and the A-IoT terminal. The A-IoT terminal transmits information to the terminal device, which then forwards the information to the access network equipment via the UU interface.

[0143] In this application, the communication system including access network equipment, auxiliary nodes, and A-IoT terminals can also be a system with a separate architecture. The auxiliary node is the terminal device. In this communication system, such as... Figure 6a , Figure 6bAs shown, access network devices and A-IoT terminals can communicate directly. Access network devices can also function as readers, such as... Figure 6a As shown, there is an uplink connection between the A-IoT terminal and the access network device, and 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 then forwards the information to the access network device. Or, as... Figure 6b As shown, there is a downlink connection between the A-IoT terminal and the access network device, and an uplink connection between the A-IoT terminal and the auxiliary node. The access network device can transmit information to the A-IoT terminal, which then forwards the information to the auxiliary node. The energy required for the A-IoT terminal to transmit information can be provided by an energy signal, which can come from the access network device, the auxiliary node, or other devices. This energy signal can also be called an excitation signal or a carrier signal.

[0144] In a split-architecture system, the auxiliary node is the terminal device. In one implementation, the terminal device can send data to the A-IoT terminal. The terminal device or access network device provides a carrier signal, and the A-IoT terminal generates or sends an uplink signal based on the carrier signal and sends this uplink signal to the access network device. This uplink signal may include data sent by the A-IoT terminal to the access network device; this data can be the A-IoT terminal's own data 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 access network device provides a carrier signal, and the A-IoT terminal generates a downlink signal based on the carrier signal and sends this downlink signal to the terminal device. This downlink signal may include data sent by the A-IoT terminal to the terminal device; this data can be the A-IoT terminal's own data or data received from the access network device.

[0145] In the direct connection architecture, the auxiliary node is the terminal device. 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.

[0146] Figure 7 This demonstrates yet another network architecture for A-IoT technology. For example... Figure 7 As shown, the communication system includes a terminal device and an A-IoT terminal. The A-IoT terminal can be a standalone device or integrated with the terminal device. In this communication system, the terminal device can function as a reader / writer, meaning it can communicate with the A-IoT terminal as a reader / writer. Communication between the terminal device and the A-IoT terminal can be achieved via a sidelink.

[0147] In the A-IoT architecture, when the terminal is in the connected state, it can realize or assist network devices and devices in executing the first service. However, it cannot support the terminal to execute the first service in the idle state, resulting in low execution efficiency of the first service and the inability to support the continuity of the first service execution.

[0148] This application provides a communication method that enables a terminal to execute a first service in an idle state, improving the execution efficiency of the first service and supporting the continuity of the first service execution when the terminal transitions from a connected state to an idle state. Figure 5 Taking the network architecture of A-IoT technology shown as an example, Figure 5 The intermediate node shown is the terminal. The access network device forwards the first message to the terminal through the uu interface. The first message includes a first resource for the effective time of communication between the terminal and the tag device in the idle state. During the effective time of the idle state, the terminal communicates with the A-IoT terminal according to the first resource, such as obtaining information of the A-IoT terminal. The terminal forwards this information to the access network device through the uu interface.

[0149] As can be seen, this application enables the terminal to execute the first service in the idle state. Furthermore, compared to executing the first service only in the connected state, it improves the execution efficiency of the first service and also supports the continuity of its execution. The network side not only controls the configuration of air interface resources in IoT technology but also configures the effective time of these resources, enabling the terminal to execute A-IoT services in the idle state.

[0150] In addition, when considering the configuration of air interface resources in IoT technology controlled by the network side in the standard discussion, this application also proposes some solutions for communication between the terminal and the A-IoT terminal in a manner that is determined by the terminal itself, by the core network element, or by the terminal's default mode, in order to support the terminal's mobility scenario during the first service execution, such as terminal mobility, link failure, or cell reselection caused by condition switching.

[0151] To facilitate understanding of this application, the following simple examples illustrate some of the terms used.

[0152] 1. The terminal communicates with the device and identifies information in the idle state.

[0153] In this application, the terminal communicating with the device in an idle state can be described as the terminal performing a first service in the idle state, or the terminal continuing to use a first resource in the idle state, etc. Correspondingly, the terminal not communicating with the device in an idle state can be described as the terminal ceasing to communicate with the device in the idle state, or the terminal not performing the first service in the idle state, or the terminal not using the first resource in the idle state, etc. Here, the first resource refers to the air interface resource or wireless resource used by the terminal to communicate with the device.

[0154] In this application, communication between the terminal and the device can be described as the terminal performing a first service associated with the identification information; correspondingly, the non-communication between the terminal and the device can be described as the terminal ceasing to communicate with the device, or the terminal ceasing to perform the first service associated with the identification information.

[0155] Identification information is used to identify communication between a terminal and a device, or information associated with such communication, or information used to identify the first service. When the terminal is in an idle state and the access network device does not store the context information of the terminal-device communication, it retrieves the associated terminal-device communication or the associated first service based on this identification information. The identification information includes at least one of the following: a service identifier associated with the terminal-device communication, a session identifier, a task identifier, an inventory area, a reader identifier, or the address of a core network element, or a device identifier. The core network element can be a tag management function (TMF) element, an ambient IoT management function (AIoTMF) element, an A-IoT element, or an A-IoT management element.

[0156] In this embodiment, it is not limited to one identification information corresponding to one service, but rather one identification information is assigned to one process corresponding to one service. Subsequent processes (such as a core network re-triggered or "newly initiated" (not a retransmission) paging, even if the service type is the same, can be considered as different identification information). Different identification information can correspond to different first services. For example, if a core network element or access network device initiates two inventory services, the trigger / request messages (such as paging messages) corresponding to these two inventory services can carry different identification information. Optionally, the paging message can carry or be associated with identification information.

[0157] In this application, the session identifier can also be replaced with task, service, request, transaction, process, procedure, service, etc. The embodiments of this application do not limit the name.

[0158] 2. First resource, effective time.

[0159] The primary resource is the air interface resource or wireless resource for communication between the terminal and the device. Optionally, the primary resource includes frequency domain resources and / or time resources. Optionally, the primary resource also includes code domain, encoding method, and modulation method, etc.

[0160] The configuration of frequency domain resources can be achieved by indicating a frequency band through the frequencyBandList field (NR or Evolved UMTS Terrestrial Radio Access Network, E-UTRAN). Optionally, one or more resource blocks (RBs) can be configured using one or more fields from the absolute FrequencyPointA field, the locationAndBandwidth field, and the sub-carrier space (SCS) spacing definition field.

[0161] The configuration method for time-domain resources can be, for example, by indicating the time-domain resources used for the first service through a service duration field. Encoding methods can indicate one or more of the following: Manchester coding, polar codes, convolutional codes, etc. Modulation methods can indicate one or more of the following: binary on-off keying (OOK), quadrature phase shift keying (QPSK), orthogonal frequency division multiplexing (OFDM), etc.

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

[0163] In another alternative implementation, the first resource is a terminal-level (perUE) resource configured by the access network device for the terminal.

[0164] In another alternative implementation, the first resource and / or validity period is determined by the core network element and can be directly or through the access network equipment to the terminal.

[0165] In another optional implementation, the first resource and / or validity period is calculated or determined by the RIC in the ORAN architecture based on prior information, to ensure no interference between NR and A-IoT communication, or between A-IoT communication between different terminals. The RIC can flexibly configure this first resource and / or validity period based on historical data. Optionally, in this implementation, the RIC needs to additionally collect historical data related to terminal-device communication. In this implementation, the first resource and / or validity period calculated or determined by the RIC can be sent to the DU via the CU, and the DU instructs the terminal.

[0166] The effective time is the duration during which the first resource is used for communication between the terminal and the device, or the duration during which the first access network device allows the terminal to communicate with the device based on the first resource, or the time during which the terminal is allowed to use the first resource. This effective time may be referred to as the effective duration (or effective time) or activation duration (or activation time) of the first resource; or, the effective time is the timing duration of a timer that starts when the terminal receives the first message or when the terminal enters an idle state, and the terminal stops communicating with the device based on the first resource when the time expires; or, the effective time is the counting duration of a timer that starts counting when the terminal receives the first message or when the terminal enters an idle state, and stops communicating with the device based on the first resource when the counting time expires.

[0167] 3. Region

[0168] The areas covered by this application include at least one of the following: areas associated with terminal-device communication, or areas associated with cells. The areas associated with terminal-device communication may be service areas, coverage areas, service areas, inventory areas, areas associated with the first service, or areas associated with the aforementioned identification information. The areas associated with cells may be the service areas, coverage areas, location areas, or areas associated with the cell's cell list.

[0169] In this application, the area associated with terminal and device communication may include multiple location areas corresponding to multiple cell identifiers, wherein the location area corresponding to the cell identifier is a location-related area or a cell-associated area.

[0170] The areas covered in this application can be indicated using either physical identification information or geographic area information. Physical identification information can be a cell ID list, a physical cell identifier list (PCI list), or a base station identifier list, etc. Geographic area information can be a latitude and longitude range, a geographic area name, a geographic area identifier, or a geographic area index, etc.

[0171] 4. The terminal's idle state and connected state.

[0172] When a terminal is in RRC idle mode, the access network device does not store the terminal's associated access stratum (AS) context, such as the RRC context. There is no RRC connection between the terminal and the access network device; in other words, the access network device is unaware of the terminal's existence. Actions a terminal can perform in RRC idle mode include: Public Land Mobile Network (PLMN) selection, receiving broadcast system messages, cell reselection, and receiving paging messages.

[0173] When a terminal is in RRC connected state, the access network device establishes and saves the access layer context related to the terminal, such as the RRC context. Even without an RRC connection between the terminal and the access network device, the access network device can still detect the terminal's presence. Actions a terminal can perform in RRC connected state include: establishing a connection between the core network and the terminal (e.g., a next-generation radio access network (NG-RAN) connection); the access network device saving the terminal's AScontext; the access network device knowing which cell the terminal belongs to; and the terminal transmitting (unicast) data with network devices (access network devices and / or core network devices).

[0174] 5. Uplink RRC messages, MAC CE, downlink RRC messages, NAS messages, and PDU-based session messages.

[0175] In this application, the messages or information carried by the terminal sending them to the access network device can be or are carried in uplink RRC messages (UE to Network) or MAC CE. The messages or information carried by the access network device sending them to the terminal can be or are carried in downlink RRC messages (Network to UE). Furthermore, the interface between the first access network device and the core network element is a next-generation (NG) interface, and the messages or information carried by the two are next-generation application protocol (NG AP) messages.

[0176] Uplink RRC messages, such as UE Assistance Information, UE Capability Information, UL Information Transfer, RRC Reconfiguration Complete, RRC Setup Request, RRC Setup Complete, RRC Reestablishment Request, RRC Reestablishment Complete, RRC Resume Request, or RRC Resume Complete, etc.

[0177] Downlink RRC messages, such as downlink information transfer (DLInformationTransfer) (or downlink data (DLdata) messages, RRCReestablishment (RRCReestablishment) messages, RRCReconfiguration (RRCReconfiguration) messages, RRCReject (RRCReject) (e.g., indication of rejection) messages, or RRCRelease (RRCRelease) messages, RRCResume (RRCResume) messages, RRCSetup (RRCSetup) messages, or UECapabilityEnquiry (UECapabilityEnquiry) messages.

[0178] In another alternative implementation, messages or information exchanged between the terminal and the access network device can be directly sent to the core network element via NAS messages. That is, the terminal can directly interact with the core network element via NAS messages. In this way, the access network device does not need to be aware of these messages or information, and the core network element directly interacts with the terminal.

[0179] In another optional implementation, messages or information exchanged between the terminal and the access network device can be directly sent to the UPF network element through messages based on the PDU session. That is, the terminal can directly interact with the UPF network element based on messages based on the PDU session, so the access network device does not need to be aware of these messages or information.

[0180] The following combination Figures 8 to 10 This paper introduces communication methods to improve the execution efficiency of A-IoT services. Among them, Figure 8 The communication method is performed by the terminal, the device, and the access network device. Figures 9 to 10The communication method described also requires the participation of core network elements. Devices communicating with the terminal include tags, A-IoT terminals, or A-IoT devices involved in A-IoT technology.

[0181] Figure 8 This is a flowchart illustrating a communication method provided in an embodiment of this application. This communication method enables a terminal to communicate with a device during the effective idle time. Figure 8 As shown, the communication method includes some or all of the following steps:

[0182] S101. The first access network device determines the effective time for the first resource to be used for the terminal to communicate with the device in the idle state.

[0183] In one possible implementation, the effective time is the duration during which the first resource is used for communication between the terminal and the device, or the duration during which the first resource is allowed to be used for communication between the terminal and the device, or the time during which the first access network device allows the terminal to communicate with the device based on the first resource. This effective time may be referred to as the effective duration (or effective time) or activation duration (or activation time) of the first resource.

[0184] In one example, the effective time T is the timing duration of the timer. The timer is started when the terminal receives a first message containing the effective time or when the terminal enters an idle state. When the timer expires, the terminal stops communicating with the device according to the first resource or stops communicating with the device. If the timer expires but the terminal completes communication with the device, the timer can be terminated.

[0185] In another example, the effective time T is the duration of the timer. The timer is started when the terminal receives a first message containing the effective time or when the terminal enters an idle state. When the effective time T is reached, the terminal stops communicating with the device based on the first resource. If the effective time T is not reached, but the terminal completes communication with the device, the timer can be triggered to terminate the timing.

[0186] Optionally, when the terminal is in an 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.

[0187] 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 containing 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 can be used by the core network element to identify the corresponding first service or terminal when the terminal makes subsequent resource requests or reports data.

[0188] One possible implementation is that, based on the request, the first access network device can directly return a service response (such as an A-IoT service response) to the core network element to determine whether to execute the first service, without waiting for a response from the terminal. Another possible implementation is that the first access network device receives the service response from the terminal to determine whether to execute the first service and then forwards it to the core network element.

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

[0190] In one optional implementation, after receiving the first message, the terminal can save the context information of the communication between the terminal and the device, such as identification information and validity period, and enter an idle state. Additionally, the terminal can also save the area associated with the communication between the terminal and the device. For a description of the area associated with the communication between the terminal and the device, please refer to the terminology section; it will not be detailed here.

[0191] In one optional implementation, the first access network device determines whether the terminal is communicating with the device in an idle state, and then executes steps S101 to S102. In another optional implementation, the terminal itself determines whether it is communicating with the device in an idle state. If the terminal determines that it is communicating with the device in an idle state, it can send a message to the first access network device requesting to communicate with the device in an idle state.

[0192] In one possible implementation, the first access network device or terminal can determine whether the terminal should communicate with the device in an idle state based on the service type of the first service. For example, if the service type is inventory service, then it is determined that the terminal is allowed or triggered to communicate with the device in an idle state; if the service type is not inventory service, or if the service type is other service, such as command service or service requiring data transmission, then it is determined that the terminal is not allowed or not triggered to communicate with the device in an idle state (or the terminal is not released from the idle state).

[0193] Optionally, the first access network device or terminal obtains the service type from a core network element, such as an AMF network element, an AIoTMF network element, an A-IoT network element, or an A-IoT management network element. Optionally, the terminal obtains the service type from a core network element via a NAS message, or the terminal obtains the service type from an access network device via an RRC message.

[0194] In another possible implementation, the core network element directly instructs the first access network device or terminal not to perform the first service in the idle state; or directly instructs that there will be subsequent data transmission. For example, if the terminal has other data transmission after receiving identification information, then the first access network device or terminal determines that it is not allowed or will not trigger the terminal to communicate with the device in the idle state (not to perform the first service in the idle state).

[0195] Within the valid time period, the first access network device reserves or allocates first resources to the terminal. In one possible implementation, the first access network device further sends first information to the terminal, which instructs the first access network device to allocate the first resources to the terminal. Optionally, the first information may be included in the first message or received separately.

[0196] As can be seen, in this embodiment, the first access network device configures the communication resources between the terminal and the device separately. In this way, combined with the effective time, the first access network device can avoid allocating the same communication resources between the terminal and the device to other terminals in the same cell within the time T.

[0197] Optionally, if the first access network device allocates the same resources to other terminals in the same cell within the effective time, it may determine whether the distance between each terminal is far enough based on the location of each terminal, or determine the approximate distance between terminals based on measurement. If the distance exceeds the distance threshold, the terminals may use the same resources (i.e., for communication with the device).

[0198] For example, the first access network device can determine whether the distance between each terminal is far enough based on the location of each terminal, including: the first access network device determines the distance between the terminals based on the location of each terminal, and if the distance is greater than a certain threshold, it determines that the terminals are far enough apart and can use the same resources.

[0199] For example, the first access network device determines the approximate distance between terminals based on measurements, including: the first access network device determines the distance of each terminal from the first access network device, or the distance between terminals, based on the signal strength of one or more terminals (e.g., 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), etc.), and / or the angle of arrival of the signal.

[0200] For example, the first access network device may also determine the interference intensity between terminals based on signal strength to determine whether each terminal can use the same resources.

[0201] In one optional implementation, the first access network device sends second information to the terminal, the second information being used to instruct the terminal to communicate with the device in an idle state. Therefore, in this implementation, the first access network device explicitly instructs the terminal to perform a first service in an idle state. Optionally, the second information is carried in an RRC downlink message; a description of RRC downlink messages can be found above and will not be detailed here.

[0202] It should be noted that in the various optional embodiments described above, the messages and / or information sent by the first access network device to the terminal may include or be used to indicate one or more of the following: effective time, first resource, or indication that the terminal is communicating with the device in an idle state.

[0203] The indication that the terminal communicates with the device in the idle state can be replaced by an indication that the terminal performs the first service in the idle state, or an indication that the terminal continues to use the first resource in the idle state, or an indication that the terminal continues to use the first resource, etc.

[0204] Optionally, the resources used by the terminal to communicate with the device in the idle state and the resources used by the terminal to communicate with the device in the connected state may be the same or different, or partially the same. They may be indicated relatively separately or together.

[0205] Optionally, the effective time, first resource, and / or 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 downlink RRC message or a MAC CE message. The downlink RRC message can be referred to above and will not be described in detail here.

[0206] Optionally, the message sent by the terminal to the first access network device to request communication with the device in the idle state may be carried in an uplink RRC message or a MAC CE. The uplink RRC message has been described above and will not be detailed here.

[0207] S103. During the idle state's effective time, the terminal communicates with the device based on the first resource.

[0208] In one optional implementation, during the effective time of the idle state, the terminal communicates with the device according to a first resource, including: when the terminal receives a first message (such as an RRC connection release message), it starts a timer, the duration of which is the effective time T; before the timer expires, it communicates with the device according to the first resource. Optionally, the terminal may start the timer when entering the idle state.

[0209] In another optional implementation, the terminal communicates with the device according to the first resource during the effective time of the idle state, including: timing when the terminal releases the RRC connection to the idle state, and communicating with the device according to the first resource during the effective time of the timing period.

[0210] visible, Figure 8 In the aforementioned communication method, the terminal communicates with the device according to the first resource during the effective time of the idle state, thereby enabling the terminal to execute the first service in the idle state. Compared with executing the first service only in the connected state, this greatly improves the execution efficiency of the first service.

[0211] Figure 9 This is a flowchart illustrating another communication method provided in this application. Based on Figure 8 The aforementioned communication method, Figure 9 In the described communication method, if the terminal times out within the valid time period, it can enter a connected state and request resources from the first network access device to communicate with the device. For example, if the terminal has not completed communication with the device (i.e., has not completed the first service) or the first resource is unavailable when the timer expires, then the terminal can request resources from the first access network device. Figure 9 As shown, when a terminal communicates with a device in an idle state and the effective time expires, the communication method may include some or all of the following steps:

[0212] S201. The terminal sends an RRC Setup Request to the first access network device to establish an RRC connection and enter the connected state.

[0213] Optionally, after the terminal sends an RRC connection establishment request to the first access network device, the first access network device may return an RRC connection establishment response to the terminal. Optionally, the terminal may return an RRC connection completion response to the first access network device.

[0214] Optionally, the RRC connection establishment request may include the reason for establishing the RRC connection, such as requesting resources to communicate with the device (i.e., requesting A-IoT resources).

[0215] S202. The terminal sends a message to the first access network device requesting resources to communicate with the device.

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

[0217] S203. The first access network device sends a message to the core network element to request confirmation of whether the terminal is communicating with the device (or sends auxiliary information for the core network element to confirm whether it is communicating with the device).

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

[0219] S204. Core network elements use this identification information to determine the authorization of the terminal.

[0220] In one optional implementation, the core network element makes an authorization determination based on the identification information, including: the core network element determining the terminal or first service associated with the identification information, and performing an authorization determination on the terminal. If the core network element determines that the terminal has the authority to execute the first service or is communicating with a device, it sends a message to the first access network device to confirm that the terminal is communicating with the device; if the core network element determines that the terminal does not have the authority to execute the first service or is not communicating with a device, it sends a message to the first access network device to confirm that the terminal is not communicating with the device.

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

[0222] 1) Terminal identification information: Identification information used by core network elements for authorization, authentication, etc., of the terminal. This identification information can be assigned by core network elements. For example, Temporary Mobile Subscriber Identity (TMSI).

[0223] 2) Number of device IDs (or inventory rate, or number of devices) collected or acquired by the terminal: The terminal calculates the number of devices that failed to be inventoried in each round. After multiple rounds of inventory, it calculates the number of devices that are still not inventoried or have failed to be inventoried, or the time that has been inventoried. In this way, the core network elements can determine the completion rate of service inventory based on this information to determine whether the terminal needs to continue communicating with the devices. For example, if the completion rate of service inventory is determined to be below a certain threshold, the terminal is instructed to continue communicating with the devices; if the completion rate of service inventory is determined to be above a certain threshold, it means that the completion rate of service inventory is high enough, and the terminal can be instructed to stop communicating with the devices.

[0224] 3) Requesting information indicating the first resource: In the implementation where the core network element determines the first resource, the core network element determines whether the first resource needs to be updated. If no update is needed, it confirms that the terminal continues to use the first resource to communicate with the device, and there is no need to re-indicate a new first resource. Optionally, the message sent by the core network device to the first access network device to confirm communication between the terminal and the device may carry an acknowledgment indication.

[0225] 4) Inventory area (service area, or area associated with AIoT services, 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 two are included or the same based on the inventory area and the area or cell where the terminal is currently located, and confirm whether the terminal should continue to communicate with the device.

[0226] 5) Reader ID: The identification information of the terminal reader, similar to the terminal ID, but as an ID assigned or generated by the AIOT reader. For example, it is used by core network elements such as AMF or AIOTMF to authorize and confirm the validity of the current reader based on the reader ID.

[0227] In some possible implementations, for a direct connection architecture where the access network device is directly connected to core network elements such as TMF network elements, AIoTMF network elements, A-IOT network elements, or A-IOT management network elements, in step S202, the terminal also needs to report the addresses of the aforementioned core network elements to the access network device so that the access network device can directly address these network elements.

[0228] S205. The core network element sends a message to the first access network device to confirm that the terminal is communicating with the device, or to confirm that the terminal is not communicating with the device.

[0229] S206. If the core network element sends a message to the first access network device to confirm that the terminal is communicating with the device, then the core network element allocates resources for the terminal to communicate with the device; if the core network element sends a message to the first access network device to confirm that the terminal is not communicating with the device, then the core network element instructs the terminal to complete the communication with the device.

[0230] When a terminal receives a resource for communicating with a device, it can communicate with the device based on that resource; when the terminal receives an instruction to complete communication with the device, it releases the context information for communicating with the device and deletes the data it has acquired.

[0231] For example, the contextual information related to terminal-device communication includes, but is not limited to, at least one of the following: resource information for AIoT communication, transmission configuration parameters (or coding and modulation methods), temporary identifiers (such as AS ID), paging identifiers (such as mask, device group ID, etc.), or random access parameters (such as R2D / D2R frequency information, total number of access opportunities, etc.). Acquired data includes data received from the AIoT device (e.g., data including the device ID), or AIoT data in the buffer (e.g., the received device ID).

[0232] In one optional implementation, the message or information carried by the terminal sent to the first access network device can be an uplink RRC message or a MAC CE as described above; correspondingly, the message or information carried by the first access network device sent to the terminal can be a downlink RRC message as described above. Additionally, the message or information carried by the first access network device interacting with the core network element is an NG AP message.

[0233] In another optional implementation, the messages or information carried by the terminal and the first access network device are non-access stratum (NAS) messages. In this way, the first access network device is unaware of whether the terminal requests resources or other requests. The core network elements directly interact with the terminal, such as allocating resources for the terminal to communicate with the device.

[0234] In another optional implementation, the messages or information carried by the terminal and the first access network device are messages based on packet data unit (PDU) sessions. In this way, the terminal and the UPF directly interact with the aforementioned messages or information, such as allocating resources for communication between the terminal and the device.

[0235] visible, Figure 9 In the aforementioned communication method, before allocating resources for communication between the terminal and the device to the terminal, the first access network device may request the core network element to determine whether the terminal is communicating with the device. In this way, even if the terminal is in an idle state and does not save the context information of the terminal communicating with the device, the first access network device can still request confirmation from the core network element based on the identification information.

[0236] In another embodiment, the first access network device itself can also confirm whether the terminal is communicating with the device, i.e. Figure 9 In the communication method shown, the first access network device does not need to interact with the core network elements. Instead, the first access network device decides whether to communicate with the device, which will not be described in detail here.

[0237] Figure 10 This is a flowchart illustrating another communication method provided in this application. Based on Figure 8 The communication method shown Figure 10 In the described communication method, when the terminal completes communication with the device, it requests the first access network device to report the data it has obtained from the device. For example... Figure 10 As shown, the communication method includes some or all of the following steps:

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

[0239] Optionally, after the terminal sends an RRC connection establishment request to the first access network device, the first access network device may return an RRC connection establishment response to the terminal. Optionally, the terminal may return an RRC connection completion response to the first access network device.

[0240] Optionally, the RRC connection establishment request may include a reason for establishing the RRC connection, such as a request to report data from the device.

[0241] S302. The terminal sends a message to the first access network device requesting the reporting of data from the device.

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

[0243] Optionally, in addition to identification information, the message sent by the terminal to the first access network may also include one or more of the following: terminal identification information, the number of device identifiers that the terminal has collected or acquired, and the disk storage area or reader identifier. For a description of this information, please refer to [link / reference needed]. Figure 9 The relevant content in the embodiments described will not be detailed here.

[0244] S303. The first access network device sends a message to the core network element to request confirmation of whether the terminal is communicating with the device (or sends auxiliary information for the core network element to confirm whether the terminal is communicating with the device).

[0245] The message sent by the first access network device also includes identification information. Correspondingly, the core network elements receive this message from the first access network device.

[0246] S304. Core network elements make authorization decisions based on this identification information.

[0247] S305. The core network element sends a message to the first access network device to confirm that the terminal is communicating with the device, or to confirm that the terminal is not communicating with the device.

[0248] For details regarding steps S303 to S305, please refer to [link / reference]. Figure 9 The relevant descriptions of steps S203 to S205 in the embodiments will not be detailed here.

[0249] S306. When the first access network device receives a message confirming that the terminal is communicating with the device, it instructs the terminal to report data; when the first access network device receives a message confirming that the terminal is not communicating with the device, it instructs the terminal to complete communication with the device.

[0250] When the first access network device instructs the terminal to complete communication with the device, the terminal releases the communication context information and deletes the acquired data. For a description of the terminal's communication context information and the acquired data, please refer to [reference needed]. Figure 9 The relevant content in the embodiments described will not be detailed here.

[0251] Optionally, the message or information carried by the terminal sending to the first access network device can be an uplink RRC message or MAC CE as described above; the message or information carried by the first access network device sending to the terminal can be a downlink RRC message as described above. Alternatively, the message or information carried by the terminal interacting with the first access network device can be a NAS message. Alternatively, the message or information carried by the terminal interacting with the first access network device can be a PDU session-based message. Further elaboration of this part can be found in the relevant content of the embodiments described above, and will not be detailed here.

[0252] visible, Figure 10 In the communication method shown, before the first access network device instructs the terminal to report data from the device, it can first request the core network element to determine whether the terminal is communicating with the device. In this way, 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 an idle state, it can still request confirmation from the core network element based on the identification information and other content.

[0253] In another embodiment, the first access network device itself can also confirm whether the terminal reports data from the device, i.e. Figure 10 In the communication method shown, the first access network device does not need to interact with the core network elements. Instead, the first access network device determines whether to communicate with the device, which will not be described in detail here.

[0254] The following combination Figures 11 to 14 This section introduces the communication methods that support mobility during the execution of the first service. Among them, Figures 11 to 14 The communication method is executed by a terminal, a device, a second access network device, and core network elements. Devices communicating with the terminal include tags, A-IoT terminals, or A-IoT devices related to A-IoT technology.

[0255] Figure 11 This is a flowchart illustrating another communication method provided in an embodiment of this application. This communication method supports mobility during the execution of a first service by the terminal. During communication with the device, the terminal can move to or reselect a cell to a second cell, and the terminal determines whether to continue communicating with the device. For example... Figure 11 As shown, the communication method includes some or all of the following steps:

[0256] S401. The terminal determines whether to continue communicating with the device based on the area associated with the second cell; if it continues to communicate with the device, it executes steps S402 to S406; if it does not continue to communicate with the device, it executes steps S407 to S411.

[0257] In one possible implementation, the terminal obtains the area associated with the second cell from the system information of the second cell.

[0258] In one optional implementation, the terminal determines to continue communicating with the device when the area associated with the second cell includes the first area, or the area associated with the second cell is contained within the first area, or the area associated with the second cell is the same as the first area; the terminal determines not to continue communicating with the device when the area associated with the second cell does not include the first area, is not contained within the first area, and is not the same as the first area. Here, the first area is the area associated with communication between the terminal and the device.

[0259] S402. The terminal sends a message to the second access network device requesting resources for communication between the terminal and the device; correspondingly, the second access network device receives the message, wherein the message contains identification information.

[0260] S403. The second access network device sends a message to the core network element to request confirmation of whether the terminal is communicating with the device; correspondingly, the core network element receives the message, wherein the message contains identification information.

[0261] S404. The core network element determines whether the terminal is communicating with the device based on the received message.

[0262] S405. When a core network element determines that a terminal is communicating with a device, it sends a message to the second access network device to confirm that the terminal is communicating with the device. When a core network element determines that a terminal is not communicating with a device, it sends a message to the second access network device to confirm that the terminal is not communicating with the device. Accordingly, the second access network device receives this message.

[0263] S406. When the second access network device receives a message confirming that the terminal is communicating with the device, it allocates resources to the terminal for communication with the device; when the second access network device receives a message confirming that the terminal is not communicating with the device, it instructs the terminal to complete the communication with the device.

[0264] The resource allocated by the second access network device to the terminal is the AIoT resource of the current cell, namely the second cell.

[0265] Upon receiving an instruction indicating the completion of communication with the device, the terminal can release the communication context information and delete the data from the device. The communication context information between the terminal and the device, as well as the data from the device, can be found in the preceding explanations and will not be detailed here.

[0266] S407. The terminal sends a message to the second access network device requesting whether to report data from the device. Accordingly, the second access network device receives the message, which includes identification information.

[0267] The information carried in the message sent by the terminal to the second access network device can be referred to in the previous embodiment regarding the information carried in the message sent to the first access network device, and will not be detailed here. Similarly, the information carried in the message sent by the second access network device to the core network element can be referred to in the previous embodiment regarding the information carried in the message sent by the first access network device to the core network element, and will not be detailed here either.

[0268] S408. The second access network device sends a message to the core network element requesting confirmation as to whether the terminal has reported data from the device. Correspondingly, the core network element receives this message.

[0269] S409. The core network element determines whether the terminal should report data from the device based on the received message.

[0270] S410. When a core network element determines that a terminal is reporting data, it sends a message to the second access network device to confirm that the terminal is reporting data; when a core network element determines that a terminal is not reporting data, it sends a message to the second access network device to confirm that it is not reporting data.

[0271] S411. When the second access network device receives a message to confirm that the terminal has reported data, it instructs the terminal to report data; when the second access network device receives a message to confirm that the terminal has not reported data, it instructs the terminal to complete communication with the device.

[0272] The relevant content described in the embodiments of this application, such as the optional implementation methods of steps S402 to S411, can be referred to. Figure 9 or Figure 10 The implementation details will not be elaborated here.

[0273] As can be seen, in this method, after the terminal reselects a cell or changes its base station, the terminal itself determines whether to continue communicating with the device.

[0274] Figure 12 This is a schematic diagram of yet another communication method provided in this application. Based on Figure 11 The aforementioned communication method supporting mobility and Figure 8 The communication method for performing the first service in the idle state, Figure 12In the described communication method, for example, when the terminal is communicating with the device in the idle state, a move or cell reselection occurs. Optionally, the terminal also needs to send an RRC connection establishment request to the second access network device. After the RRC connection with the second access network device is established, the terminal is in the connected state. The terminal executes in the connected state. Figure 11 Steps S401 to S411 are described above.

[0275] Optionally, the terminal may obtain the area associated with the second cell from the system information of the second cell or during the RRC connection establishment process.

[0276] In one optional implementation, the terminal may obtain the A-IoT capability of the second access network device from the system information of the second cell or during the RRC connection establishment process. If the second access network device supports A-IoT capability, the RRC connection with the second access network device is established; otherwise, communication with the device is stopped (i.e., the first service is stopped), or the terminal reselects a cell until it reselects an access network device that supports A-IoT capability.

[0277] In another optional implementation, the terminal may obtain information from the system information of the second cell or during the RRC connection establishment process to determine whether the second cell supports or allows A-IoT capabilities (or A-IoT services, or A-IoT communication). If the second cell supports or allows A-IoT capabilities, the RRC connection with the second access network device is established; otherwise, communication with the device is stopped, or the terminal reselects a cell until it reselects an access network device that supports A-IoT capabilities.

[0278] Optionally, whether the second access network device or the second cell supports A-IoT capabilities can be determined by 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 A-IoT capabilities can be 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 may be unable to support A-IoT capabilities due to reasons such as high load.

[0279] As can be seen, in this method, after the terminal reselects a cell or switches sites in the idle state, the terminal itself determines whether to continue communicating with the device. That is, even if the terminal reselects a second cell while 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's communication with the device. The second access network device can still request confirmation from the core network element based on this identification information whether the terminal should continue communicating with the device. If it determines to continue communicating with the device, the second access network device can allocate resources to the terminal; if it determines not to continue communicating with the device, the second access network device can instruct the terminal to report the data it has obtained.

[0280] Figure 13This is a flowchart illustrating another communication method provided in this application. Figure 13 The communication method described also supports terminal mobility, but Figure 11 In the aforementioned communication method, after the terminal reselects a cell or changes its base station, the terminal itself determines whether to continue communicating with the device. Figure 13 In the aforementioned communication method, after the terminal reselects a cell or changes its base station, the core network element determines whether to continue communication with the device. For example... Figure 13 As shown, the method includes some or all of the following steps:

[0281] S501. The terminal sends a message to the second access network device requesting whether the terminal should communicate with the device and / or report data from the device; accordingly, the second access network device receives the message, wherein the message contains identification information.

[0282] The information that may also be included in the message sent by the terminal to the second access network device can be found in the preceding text, such as... Figure 9 The relevant descriptions of steps S202 and S203 include at least one of the following: terminal identification information, the number of device identifiers that the terminal has collected or acquired, storage area, or reader identifier, which can be used to determine whether the terminal continues to communicate with the device and / or whether it reports data from the device.

[0283] S502. The second access network device sends a message to the core network element to request confirmation of whether the terminal is communicating with the device and / or whether it is reporting data from the device; accordingly, the core network element receives the message, wherein the message contains identification information.

[0284] S503. The core network element sends the following messages to the second access network device: a message confirming communication between the terminal and the device; a message confirming that the terminal has reported data from the device; or a message confirming that the terminal is not communicating with the device and is not reporting data from the device. Accordingly, the second access network device receives the above messages.

[0285] In one possible implementation, the core network element determines the first service associated with the identification information, or determines the terminal associated with the identification information that is communicating with the device. It then performs an authorization check on the terminal. If the terminal has the authority to execute the first service or it is determined that the terminal is communicating with the device, it sends a message to the second access network device to confirm that the terminal is communicating with the device or to confirm that the terminal is reporting data. If the terminal does not have the authority to execute the first service or it is determined that the terminal is not communicating with the device, it sends a message to the second access network device to confirm that the terminal is not communicating with the device and is not reporting data from the device.

[0286] In another possible implementation, the authorization determination operation of the core network element can also be referred to the above text. Figure 9 , Figure 10The relevant content will not be elaborated here.

[0287] S504. When the second access network device receives a message confirming that the terminal is communicating with the device, it allocates resources for the terminal to communicate with the device; when it receives a message confirming that the terminal is reporting data, it instructs the terminal to report data from the device; when it receives a message confirming that the terminal is not communicating with the device and is not reporting data, it instructs the terminal to complete communication with the device.

[0288] The resource allocated by the second access network device to the terminal is the current message, i.e., the AIoT resource of the second cell.

[0289] As can be seen, in this method, after the terminal reselects a cell, it requests the core network through the second access network device to determine whether the terminal should continue to communicate with the device and whether to report data.

[0290] This application also provides a communication method that supports mobility, but unlike... Figure 11 , Figure 13 The difference in this communication method lies in that, by default, the terminal stops communicating with the device when reselecting a cell, releases the communication context information with the device, and deletes the data obtained from the device.

[0291] In one possible implementation, the terminal may also send a message to the second access network device indicating that the terminal has stopped communicating with the device, the message including identification information; the second access network device sends the message to the core network element.

[0292] In another possible implementation, the terminal does not need to indicate to the core network element that it has stopped communicating with the device. Instead, the core network element releases the context information of the terminal's communication with the device based on the timeout of the communication between the terminal and the device, such as the first service timeout, or when the core network element determines that the first service needs to be continued, it initiates paging for the terminal again.

[0293] This application also provides a communication method that supports mobility, but unlike... Figure 11 , Figure 13 The difference in this communication method lies in that, after the terminal reselects a cell, it defaults to not continuing communication with the device and sends a message to the second access network device requesting data reporting. The second access network device sends a message to the core network element to confirm whether the terminal should report data. When the core network element sends a message to the second access network device to confirm that the terminal has reported data, the second access network device instructs the terminal to report data; when the core network element sends a message to the second access network device to confirm that the terminal will not report data, the second access network device instructs the terminal to delete the data already obtained.

[0294] By default, the terminal will not continue to communicate with the device, and can release the context information related to device communication. It can then report data according to the instructions of the core network element.

[0295] The optional implementation methods and / or examples of the two communication methods described above can be found in the relevant descriptions in the embodiments described above, and will not be detailed here.

[0296] Figure 14 This is a schematic diagram of another communication method provided in this application, based on Figure 13 The aforementioned communication method supporting mobility and Figure 8 The communication method for performing the first service in the idle state, Figure 14 In the aforementioned communication method, for example, when the terminal is communicating with the device in the idle state, after a move or cell reselection occurs, optionally, the terminal also sends an RRC connection establishment request to the second access network device. The RRC connection between the terminal and the second access network device is then established, and the terminal is in the connected state. The terminal executes [the following steps] in the connected state. Figure 13 The steps S501 to S504 described above may be executed, or the terminal may be executed in a way that stops communicating with the device by default, or the terminal may be executed in a way that does not continue to communicate with the device by default but may report data according to the instructions of the core network element.

[0297] In one optional implementation, the terminal may obtain the A-IoT capability of the second access network device from the system information of the second cell or during the RRC connection establishment process. If the second access network device supports A-IoT capability, the RRC connection between the terminal and the second access network device is established; otherwise, communication with the device is stopped (i.e., the first service is stopped), or the terminal reselects a cell until it reselects an access network device that supports A-IoT capability, otherwise communication with the device is stopped (i.e., the first service is stopped).

[0298] In another optional implementation, the terminal may obtain information from the system information of the second cell or during the RRC connection establishment process to determine whether the second cell supports or allows A-IoT capabilities (or A-IoT services, or A-IoT communication). If the second cell supports or allows A-IoT capabilities, the RRC connection with the second access network device is established; otherwise, communication with the device is stopped, or the terminal reselects a cell until it reselects an access network device that supports A-IoT capabilities.

[0299] In another optional implementation, the RRC connection establishment request sent by the terminal to the second access network device may include identification information. In this way, the second access network device can request confirmation from the core network element whether the second access network device supports A-IoT capability. If the core network element returns a message confirming that the second access network device supports 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 A-IoT capability, the second access network device sends a message to the terminal indicating that communication with the device is complete. Upon receiving this message, the terminal can release the context information of communication with the device and delete the acquired data. Alternatively, the second access network device can instruct the terminal to reselect a cell.

[0300] As can be seen, in this communication method, even if the terminal is in an idle state and reselects to the second cell, the second access network device does not save the context information of the terminal's communication with the device. The second access network device can still request confirmation from the core network element based on the identification information whether the terminal should continue to communicate with the device and / or whether to report the device's data.

[0301] and Figure 14 Similarly, the above methods for the terminal to stop communicating with the device by default, or the two communication methods described above for the terminal to stop communicating with the device by default, also apply. Figure 8 The scenario of the terminal communicating with the device in the idle state will not be described in detail here.

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

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

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

[0305] The above combination Figures 8 to 14 The communication method provided in the embodiments of this application is explained. In the various embodiments of this application, unless otherwise specified or logically conflicting, the terms and / or descriptions between the various embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0306] The following is combined Figures 15 to 16 This application describes the communication device provided in the embodiments. It should be understood that the description of the device embodiments corresponds to the description of the method embodiments. Therefore, for content not described in detail, please refer to the above method embodiments. For the sake of brevity, it will not be repeated here.

[0307] Figure 15 A possible exemplary block diagram of the communication device involved in an embodiment of this application is shown. For example... Figure 15 As shown, the communication device may include modules or units for implementing the methods described in the embodiments above. In one possible design, the communication device includes a communication unit 601 and a processing unit 602. Optionally, the communication device may further include a storage unit 603 for storing device program code and / or data.

[0308] The communication device can be a terminal-side device as described in the above embodiments, such as the first device, for example, a terminal or a communication module in a terminal, or a circuit or chip in a terminal that is responsible for communication functions.

[0309] For example, in one embodiment, the communication unit 601 is configured to: receive a first message from the second device, the first message including a first resource for the effective time of communication between the first device and the third device; and communicate with the third device according to the first resource during the effective time of the idle state. Optionally, the processing unit 601 is configured to: configure the timing duration of the timer to T, such that the communication unit 601 communicates with the third device according to the first resource before the timer expires;

[0310] In one possible design, the communication unit 601 is further configured to: receive first information and / or second information; the first information is used to instruct the second device to allocate first resources to the first device; and the second information is used to instruct the first device to communicate with the third device in an idle state.

[0311] In one possible design, the communication unit 601 is also used to send a message to the second device requesting communication with the third device in an idle state.

[0312] In one possible design, the communication unit 601 is further configured to: send a message to the second device requesting resources for communication with the third device; the message sent includes identification information associated with the communication between the first device and the third device.

[0313] In one possible design, the communication unit 601 is also used to: send a message to the second device requesting the reporting of data from the third device; the message sent includes identification information.

[0314] In one possible design, the communication unit 601 is further configured to: send a message to the fourth device, based on the area associated with the second cell, to request resources for communication with the third device, or to request whether to report data from the third device; wherein the second cell is the cell reselected by the first device, the fourth device is the access network device corresponding to the second cell, and the message sent includes identification information.

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

[0316] In one 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 a message to the fourth device requesting whether to report data from the third device; the message sent includes identification information.

[0317] In one possible design, the processing unit 602 is also used to delete information related to communication with the third device, as well as data from the third device, when reselecting to the second cell.

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

[0319] In one possible design, when the communication device is a terminal or a communication module within a terminal, the functionality of the processing unit 602 can be implemented by one or more processors. Specifically, the processor may include a modem chip, or a system-on-a-chip (SoC) or SIP chip containing a modem core. The functionality of the communication unit 601 can be implemented by transceiver circuitry.

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

[0321] In one possible design, when the communication device is a terminal or a processing module within a terminal, the functionality of the processing unit 602 can be implemented by one or more processors. Specifically, the processor may include a GPU, or a system-on-a-chip (SoC) or SIP chip containing a GPU. The functionality of the communication unit 601 can be implemented by transceiver circuitry.

[0322] In one possible design, when the communication device is a circuit or chip in the terminal responsible for processing functions, such as a GPU or a system-on-a-chip (SoC) or SIP chip containing a GPU, the function of the processing unit 602 can be implemented by a circuit system in the aforementioned chip that includes one or more processors or processor cores. The function of the communication unit 601 can be implemented by interface circuitry or data transceiver circuitry on the aforementioned chip.

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

[0324] For example, in one embodiment, the processing unit 602 is configured to: determine the effective time for the first resource to be used for the first device to communicate with the third device in an idle state;

[0325] The communication unit 601 is used to send a first message to the first device, the first message including a validity period.

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

[0327] In one possible design, the communication unit 601 is also configured to: receive a message from the first device requesting the first device to communicate with the third device in an idle state.

[0328] In one possible design, the communication unit 601 is further configured to: receive a message from the first device requesting resources to communicate with the third device, or requesting the reporting of data from the third device; and send a message to the core network element requesting confirmation of whether the first device is communicating with the third device; wherein the received message and the sent message include identification information.

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

[0330] For example, in one embodiment, the communication unit 601 is used to: receive a message from the first device requesting resources to communicate with the third device, or requesting whether to report data from the third device; and send a message to the core network element requesting confirmation of whether the first device is communicating with the third device; wherein the received message and the sent message include identification information associated with the communication between the first device and the third device.

[0331] In another embodiment, the communication unit 601 is configured to: receive a message from the first device 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 requesting confirmation of 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 include identification information associated with the communication between the first device and the third device.

[0332] The communication device can be a network-side device as described in the above embodiments, such as a core network element.

[0333] For example, in one embodiment, the communication unit 601 is configured to: receive a message from the second device requesting confirmation of whether the first device is communicating with the third device, the received message including identification information associated with the communication between the first device and the third device; and send a message to the second device to confirm that the first device is communicating with the third device, or to confirm that the first device is not communicating with the third device.

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

[0335] It is understood that the division of units in the above-described device is a logical functional division. One function can correspond to one functional unit, or two or more functions can be integrated into one functional unit. In actual implementation, all or some units can be integrated into one physical entity, or distributed across different physical entities. Furthermore, the aforementioned functional units can be implemented in hardware, software, or a combination of both. Whether a function is executed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for specific applications, but such implementations should not be considered beyond the scope of this application.

[0336] In one example, the functional unit in any of the above devices may be one or more integrated circuits configured to implement the above methods, such as: 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.

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

[0338] Figure 16 This is a schematic diagram of the structure of a terminal provided in an embodiment of this application. The terminal can correspond to... Figures 1 to 14 The terminal or first device shown is used to implement the operation of the terminal or first device in the above embodiments. For example... Figure 16 As shown, the terminal includes: one or more antennas 510, a radio frequency processing system 720, and a processor system 730.

[0339] In the downlink or sidelink direction, the RF processing system 720 receives RF signals through the antenna 710 and sends the RF-processed signals to the processor system 730 for further processing. In the uplink or sidelink direction, the processor system 730 processes the terminal-side information and sends it to the RF processing system 720, which then processes the signal and transmits it through the antenna 710.

[0340] In one example, the radio frequency (RF) processing system 720 serves as the communication interface for external communication of the terminal and may include a radio frequency front end (RFFE) 721 and a radio frequency transceiver 722. The RFFE 721 is primarily used for one or more processing operations, such as shaping, passband selection, or gain adjustment, on the RF signals received by the antenna or those to be transmitted through the antenna. It may include one or more components such as RF switches, duplexers, filters, power amplifiers, antenna tuners, and low-noise amplifiers. The RFFE 721 can be a circuit system composed of multiple discrete components or integrated into one or more chips. The RF transceiver 722 processes the RF signals received by the RFFE 721 into baseband / IF signals for further processing by the processor system 730, and processes the baseband / IF signals provided by the processor system 730 into RF signals for transmission to the RFFE 721. The baseband / IF signals transmitted between the RF transceiver 722 and the processor system 730 can be digital or analog signals. The RF transceiver 722 can be implemented by one or more chips, which are usually referred to as radio frequency integrated circuits (RFICs).

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

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

[0343] In one example, memory 736 can be on-chip memory, i.e., located on the processor system 730 chip. In another example, memory 760 can be off-chip memory, i.e. located outside the processor system 730 chip.

[0344] In one example, the baseband processor 731 may include one or more processor cores 7311 and interface circuitry 7314. The one or more processor cores 7311 are used to process signals and execute one or more communication protocols. Optionally, the baseband processor 731 may also include a memory 7312 for storing at least a portion of the corresponding computer program instructions and / or data. In one example, the one or more processor cores 7311 execute the computer program instructions stored in the memory 7312 to implement the relevant operations (such as generating and sending first information) in the above method embodiments. In this application, the memory 7312 storing the corresponding computer program instructions and / or data may mean that the memory 7312 stores all the corresponding computer program instructions and / or data for the processor core 7311 to execute; or it may mean that the memory 7312 stores a portion of the corresponding computer program instructions and / or data, which includes the computer program instructions and / or data that the processor core 7311 currently needs to execute. The memory 7312 can store different portions of the computer program instructions and / or data multiple times for the processor core 7311 to execute in order to implement the relevant operations in the above method embodiments. Interface circuit 7314 serves as a communication interface for communication with other components, such as transmitting signals with RF processing system 720, communicating with other subsystems and related components of processor system 730 via bus, such as transmitting data control signals with application processor 732, and transmitting data or computer program instructions with memory 736 or memory 760. Optionally, to reduce the load on the processor core, baseband signal processing circuit 7313 can also be provided to perform at least some baseband signal processing, including one or more of signal demodulation, modulation, encoding, or decoding.

[0345] The processor, processor system, application processor, baseband processor, processor circuit, or processor core mentioned above can be collectively referred to as a processor. The processor may include one or more of the following: central processing unit (CPU), digital signal processor (DSP), microprocessor unit (MPU), microcontroller unit (MCU), graphics processing unit (GPU), field programmable gate array (FPGA), artificial intelligence processor (AI processor), or neural processing unit (NPU).

[0346] The aforementioned memory may include one or more of the following storage media: random access memory (RAM), static random access memory (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 executing the above embodiments may be stored in non-volatile memory, such as at least a portion of the aforementioned memory 760 (e.g., one or more of ROM, flash memory, EPROM, or hard disk). When the terminal is running, the corresponding computer program instructions may be partially or wholly loaded onto a memory with a faster transfer speed than the processor, such as at least a portion of memory 736 and / or memory 7312 (e.g., one or more of RAM, SRAM, DRAM, PCM, RERAM, MRAM, FRAM, cache, or register), for the processor to execute in order to implement the steps in the above method embodiments.

[0347] In one example, the RF transceiver 722 and the RF front-end 721 can also be packaged in a single chip. In another example, the RF transceiver 722, the RF front-end 721, and the baseband processor 731 can also be packaged in a single chip.

[0348] The terms "system" and "network" in this application embodiment are used interchangeably. "At least one" refers to one or more, and "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, "at least one of A, B, or C" includes A, B, C, AB, AC, BC, or ABC; "at least one of A, B, and C" can also be understood as including A, B, C, AB, AC, BC, or ABC. Furthermore, unless otherwise specified, the ordinal numbers such as "first" and "second" mentioned in this application embodiment are used to distinguish multiple objects and are not used to limit the order, sequence, priority, or importance of multiple objects.

[0349] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, etc.) containing computer-usable program code.

[0350] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0351] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0352] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0353] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

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, ​

Images