Communication method and related device

Abstract

The present application relates to the field of communications. Provided are a communication method and a related device, which are used for avoiding a situation where, when a service of a terminal is suspended, a network side mistakenly determines the suspended service as a service failure, such that the network side and the terminal can take related measures to save on resources consumed by a suspended task. In the method, a second apparatus receives first information sent by a first apparatus, wherein the first information is used for indicating that a first service of the first apparatus is in a suspended state or the first apparatus is dormant; and the second apparatus sending second information, wherein the second information is used for indicating that the first service is in the suspended state or the first apparatus is dormant, and the second information comprises a first identifier, which is associated with the first apparatus or the first service.

Description

Communication method and related device

[0001] This application claims priority from the Chinese patent application No. 202410954147.8 filed on July 15, 2024, and entitled "A communication method and related device", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

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

[0003] At present, due to the characteristics of maintenance-free, low complexity, low cost and sustainability of ambient internet of things (A-IoT) technology, A-IoT technology has broad application prospects in many fields such as logistics and environmental detection. The network system applying A-IoT technology is called A-IoT system, which includes a reader and a terminal. For example, the function of the reader can be realized by a network device, and the terminal in the A-IoT system can be an extremely low-power and extremely low-complexity Internet of Things terminal.

[0004] When the terminal is executing a service, the service may be suspended, for example, the terminal in the A-IoT system usually takes a long time to charge, and when it is in the charging state, the terminal cannot send or receive messages, so the service being executed by the terminal will be suspended when it is in the charging state. After the charging is completed, the terminal will resume the service. However, at this time, the network side may misjudge that the service has failed. This misjudgment may cause the terminal to repeat the completed part of the interrupted service after the service is resumed, resulting in waste of resources.

[0005] Therefore, how to avoid the network side misjudging the interrupted service as a service failure when the terminal's service is interrupted is a technical problem to be solved. SUMMARY

[0006] The present application provides a communication method and related device, which can avoid the network side misjudging the suspended service as a service failure when the terminal's service is suspended, so that the network side and the terminal can take relevant measures to save the resources required to complete the service.

[0007] The first aspect of the present application provides a communication method. Optionally, the method is executed by a second device, or the method is executed by some components (e.g., a processor, a chip, or a chip system, etc.) in the second device, or the method can also be implemented by a logic module or software capable of realizing all or part of the functions of the second device. In the first aspect and its possible implementation manners, the communication method is taken as an example executed by the second device. The second device receives first information sent by a first device, the first information being used to indicate that a first service of the first device is in a suspended state or the first device is in a sleep state; the second device sends second information, the second information being used to indicate that the first service is in the suspended state or the first device is in the sleep state, and the second information comprising a first identifier, the first identifier being associated with the first device or the first service.

[0008] Based on the above method, the second device can send the first service being in the suspended state or the first device being in the sleep state to a third device, and further inform a fourth device, for example, a core network element, of the information through the third device. Thus, the network side can know that the first service is in the suspended state or the first device is in the sleep state, and the first service has not failed, and the first service can be restored later, so that the network side can avoid misjudging the suspended service, i.e., the first service, as a service failure. In addition, after the network side knows that the first service can still not fail later, the network side and the terminal can take relevant measures to save resources, for example: the second device / third device or the fourth device can save relevant information of the first service accordingly, so that the first service does not need to be reconnected to the second device or the network when the first service is restored later, and the second / third / fourth device does not need to retransmit the data that has been transmitted before the first service is suspended by the first device, so that the first device does not need to repeatedly generate or obtain the data, and / or the first device transmits the data that has been transmitted before the first service is suspended to the second / third / fourth device, so that the second / third / fourth device does not need to repeatedly obtain the data.

[0009] In a possible implementation manner of the first aspect, the second information further comprises time information T, wherein the T is a time length of the suspended state or a sleep time length of the first device.

[0010] Based on the above implementation manner, the second device can indicate the first device to suspend the first service for a duration of T, so as to prevent the first device from suspending the first service for too long, which causes the first service to have too long latency, or prevent the first device from suspending the first service for too short, which causes the first service to be suspended again. Alternatively, the second device can indicate the first device to sleep for a duration of T, so as to prevent the first device from sleeping for too long or too short. By sending the second identifier, the second device can be notified that the service-related data is associated with the second identifier.

[0011] In a possible implementation manner of the first aspect, the second device sends first scheduling information to the first device, the first scheduling information being used to indicate to resume the first service or to wake up the first device, the first scheduling information including the second identifier, the second identifier being associated with the first device or the first service, the second identifier being related to the first identifier; the second device receives first uplink data reported by the first device, the first uplink data being related to the first service; and the second device sends third information, the third information including: second uplink data associated with the second identifier, the first identifier, information used to indicate to resume the first service or information used to indicate to wake up the first device, wherein the second uplink data includes the first uplink data.

[0012] Based on the above implementation manner, by sending the scheduling information, the first device can be indicated to resume the first service or wake up the first device. And by the second identifier, the first device can be indicated to resume the first service or wake up the first device. Correspondingly, the first device can send uplink data related to the service, and the first device can send second uplink data associated with the second identifier to a third device, for example, the third device can be an access network device, so that the access network device can receive the uplink data related to the first service, and report the uplink data to an application side through a core network element, so as to resume the first service.

[0013] In a possible implementation manner of the first aspect, the second device receives second scheduling information, the second scheduling information being used to indicate to resume the first service or to wake up the first device, the second scheduling information including the first identifier.

[0014] Based on the above implementation manner, the second device can have a device in an upper layer of the second device, which is used to control the first device to resume the first service or wake up the first device. For example, the upper layer of the second device can be an access network device or a core network element or the like network side device, and the network side device can control the first device to resume the first service or wake up the first device through the second scheduling information.

[0015] In a possible implementation of the first aspect, the second scheduling information comprises downlink data used to instruct the first device to perform a target operation, the target operation comprising reading, writing, locking, positioning, sensing, or deactivation.

[0016] Based on the above implementation, the above method can be applied to a scenario in which the first service is a command service, in which case the command service requires the first device to perform the target operation, and the downlink data is carried in the scheduling information. When the first service is suspended or the first device is in hibernation, the above method can be used to send the first information to notify the network device that the first service is suspended or the first device is in hibernation, thereby being applicable to a command scenario in which the network device, such as a core network element, needs to receive feedback of service suspension or device hibernation to avoid misjudgment of service failure.

[0017] The second aspect of the present application provides a communication method. Optionally, the method is executed by a third device, or the method is executed by part of components (such as a processor, a chip, or a chip system) in the third device, or the method can also be implemented by a logic module or software that can realize all or part of the functions of the third device. In the second aspect and its possible implementation, the communication method is taken as an example to be executed by the third device, the third device receives fourth information, the fourth information is used to indicate that the first service of the first device is in a suspended state, and the fourth information comprises a third identifier, the third identifier is associated with the first device or the first service; the third device sends fifth information, the fifth information is used to indicate that the first service of the first device is in the suspended state, and the fifth information comprises a fourth identifier, the fourth identifier is related to the third identifier, and the fourth identifier is associated with the first device or the first service.

[0018] In a possible implementation of the second aspect, the fourth information further comprises information used to identify the first device or the first service or T, wherein the T is a time length of the suspended state or a hibernation period of the first device.

[0019] In a possible implementation of the second aspect, the fifth information further comprises information used to identify the first device or the first service or the T, wherein the T is a time length of the suspended state or a hibernation period of the first device.

[0020] In a possible implementation manner of the second aspect, the third device receives sixth information, wherein the sixth information comprises: third uplink data, the third identifier, information for instructing to resume the first service, or information for instructing to wake up the first device; and the third device sends seventh information, wherein the seventh information comprises: fourth uplink data, the fourth identifier, information for instructing to resume the first service, or information for instructing to wake up the first device, and the fourth uplink data comprises the third uplink data.

[0021] In a possible implementation manner of the second aspect, the third device receives third scheduling information, wherein the third scheduling information is used for instructing to resume the first service or wake up the first device, and the third scheduling information comprises the fourth identifier; and the third device sends fourth scheduling information, wherein the fourth scheduling information is used for instructing to resume the first service or wake up the first device, and the fourth scheduling information comprises the third identifier.

[0022] In a possible implementation manner of the second aspect, the third scheduling information comprises downlink data, and the downlink data is used for instructing the first device to perform a target operation, and the target operation comprises: reading, writing, locking, positioning, sensing, or deactivation.

[0023] The third aspect of the present application provides a communication method. Optionally, the method is executed by a fourth device, or the method is executed by part of components (for example, a processor, a chip, or a chip system) in the fourth device, or the method can also be implemented by a logic module or software which can realize all or part of the functions of the fourth device. In the third aspect and possible implementation manners thereof, the communication method is taken as an example for description, and the fourth device receives fifth information, wherein the fifth information is used for indicating that a first service of a first device is in a suspended state, and the fifth information comprises: a fourth identifier, and the fourth identifier is associated with the first device or the first service. The fourth device saves related information of the first service, and the related information comprises the fourth identifier.

[0024] In a possible implementation manner of the third aspect, the related information further comprises: a security parameter or data related to the first service which is cached before the suspended state starts.

[0025] In a possible implementation manner of the third aspect, the fourth device saves the related information for a time length which is not less than time information T, and the T is a time length of the suspended state or a sleep time length of the first device.

[0026] Based on the above implementation manner, by limiting the time length for saving the related information of the first service to be no less than the time information T, it can be ensured that after the suspension state ends or the first device hibernation ends, the fourth device can still directly obtain the related information of the first service from the area for saving the related information of the first service, so that after the service is resumed or the device is woken up, it is not necessary to repeatedly execute the already executed process.

[0027] In a possible implementation manner of the third aspect, the fifth information further includes: information for identifying the first service or the time information T, wherein the T is the time length of the suspension state or the hibernation time length of the first device.

[0028] In a possible implementation manner of the third aspect, the fourth device receives seventh information, and the seventh information includes: fourth uplink data, and the fourth identifier is used for indicating information for resuming the first service or information for waking up the first device.

[0029] In a possible implementation manner of the third aspect, the fourth device sends third scheduling information, and the third scheduling information is used for indicating the resumption of the first service, and the fourth scheduling information includes the fourth identifier.

[0030] In a possible implementation manner of the third aspect, the third scheduling information includes downlink data, and the downlink data is used for indicating that the first device performs a target operation, and the target operation includes: reading, writing, locking, positioning, sensing or inactivation.

[0031] The fourth aspect of the present application provides a communication method, and optionally, the method is executed by a first device, or the method is executed by part of components (for example, a processor, a chip or a chip system, etc.) in the first device, or the method can also be implemented by a logic module or software which can realize all or part of the functions of the first device. In the fourth aspect and possible implementation manners thereof, the communication method is taken as an example to be executed by the first device, the first device sends first information to a second device, and the first information is used for indicating that a first service of the first device is in a suspension state or the first device hibernates; and the first device resumes the first service.

[0032] In a possible implementation manner of the fourth aspect, the first device receives first scheduling information sent by the second device, the first scheduling information is used for indicating the resumption of the first service or the waking up of the first device, the first scheduling information includes a second identifier, and the second identifier is associated with the first device or the first service; and the first device sends first uplink data to the second device, and the first uplink data is related to the first service.

[0033] In a possible implementation of the fourth aspect, the first device receives first scheduling information sent by the second device, the first scheduling information being used to indicate resuming the first service or waking up the first device, the first scheduling information comprising a second identifier, the second identifier being associated with the first device or the first service, the second identifier being related to the first identifier; and the first device sends first uplink data to the second device, the first uplink data being related to the first service.

[0034] In a possible implementation of the fourth aspect, the first scheduling information comprises downlink data, the downlink data being used to instruct the first device to perform a target operation, the target operation comprising reading, writing, locking, positioning, sensing or deactivating.

[0035] The fifth aspect of the present application provides a communication device, which can be the first device. The communication device comprises modules or units for performing the method of the first aspect and any possible implementation thereof.

[0036] The sixth aspect of the present application provides a communication device, which can be the second device. The communication device comprises modules or units for performing the method of the second aspect and any possible implementation thereof.

[0037] The seventh aspect of the present application provides a communication device, which can be the third device. The communication device comprises modules or units for performing the method of the third aspect and any possible implementation thereof.

[0038] The eighth aspect of the present application provides a communication device, which can be the fourth device. The communication device comprises modules or units for performing the method of the fourth aspect and any possible implementation thereof.

[0039] The ninth aspect of the present application provides a communication device, which can be the first device, the second device, the third device, or the fourth device, can be a component (for example, a processor, a chip, or a chip system, etc.) applied to the first device, the second device, the third device, or the fourth device, and can also be a logic module or software (for example, a CU, a DU, or a RU, etc.) capable of realizing all or part of the functions of the first device, the second device, the third device, or the fourth device. The communication device comprises:

[0040] The processor is configured to execute a program, so that the communication device performs the method of the first aspect, the second aspect, the third aspect, or the fourth aspect and any possible implementation thereof.

[0041] Optionally, the communication device further comprises a memory, and the processor is coupled to the memory; and the memory is configured to store the program.

[0042] The tenth aspect of the present application provides a chip or a chip system, which comprises at least one processor and a communication interface, the communication interface and the at least one processor are interconnected through a line, and the at least one processor is configured to run computer programs or instructions to perform the communication method described in any one of the possible implementation manners of the first aspect, the second aspect, the third aspect, or the fourth aspect.

[0043] The communication interface in the chip can be an input / output interface, a pin, or a circuit, etc.

[0044] In a possible implementation, the chip or the chip system described in the present application further comprises at least one memory, and the at least one memory stores instructions. The memory can be a storage unit inside the chip, such as a register, a cache, etc., or a storage unit of the chip, such as a read-only memory, a random access memory, etc.

[0045] The eleventh aspect of the present application provides a communication system, which comprises a communication device performing the method of the first aspect and any one of its possible implementation manners, a communication device performing the method of the second aspect and any one of its possible implementation manners, a communication device performing the method of the third aspect and any one of its possible implementation manners, and a communication device performing the method of the fourth aspect and any one of its possible implementation manners.

[0046] Or,

[0047] The gateway station, the communication device performing the method of the first aspect and any one of its possible implementation manners, the communication device performing the method of the second aspect and any one of its possible implementation manners, the communication device performing the method of the third aspect and any one of its possible implementation manners, and the communication device performing the method of the fourth aspect and any one of its possible implementation manners.

[0048] The twelfth aspect of the present application provides a computer readable storage medium, which comprises instructions, when the instructions are run on a computer, the computer is caused to perform the method of the first aspect, or the computer is caused to perform the method of the second aspect, or the computer is caused to perform the method of the third aspect, or the computer is caused to perform the method of the fourth aspect.

[0049] The thirteenth aspect of the present application provides a computer program product comprising instructions, when the instructions are run on a computer, the computer is caused to perform the method of the first aspect, or the computer is caused to perform the method of the second aspect, or the computer is caused to perform the method of the third aspect, or the computer is caused to perform the method of the fourth aspect.

[0050] The technical effects brought by the second aspect to the thirteenth aspect or any possible implementation manner thereof can refer to the technical effects brought by the first aspect or the related possible implementation manner of the first aspect, which will not be described here again. BRIEF DESCRIPTION OF DRAWINGS

[0051] FIG. 1 is a schematic diagram of a system in an embodiment of the present application;

[0052] FIGS. 2A to 2D are schematic diagrams of application scenarios in an embodiment of the present application;

[0053] FIG. 3 is a schematic diagram of a flow of a communication method in Embodiment 1 of the present application;

[0054] FIG. 4 is a schematic diagram of a flow of access of a first device in Embodiment 1 of the present application;

[0055] FIG. 5 is a schematic diagram of a flow of a communication method in Embodiment 2 of the present application;

[0056] FIG. 6 is a schematic diagram of a flow of a communication method in Embodiment 3 of the present application;

[0057] FIG. 7 is a schematic diagram of a flow of a communication method in Embodiment 4 of the present application;

[0058] FIG. 8 is a schematic diagram of an embodiment of a communication device in the present application;

[0059] FIG. 9 is a schematic diagram of another embodiment of a communication device in the present application. DETAILED DESCRIPTION

[0060] The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application.

[0061] The technical solutions in the embodiments of the present application can be applied to various communication systems, for example, an integration of sensing and communication (ISAC) communication system, a wireless local area network (WLAN), a short-range wireless communication system (such as a sidelink, wireless fidelity (Wi-Fi or WiFi), Bluetooth, and the like), a wired network, a vehicle to everything (V2X) communication system, a device-to-device (D2D) communication system, a vehicle networking communication system, a 4th generation (4G) mobile communication system (such as a long term evolution (LTE) system), an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD), a worldwide interoperability for microwave access (WiMAX) communication system, a 5th generation (5G) mobile communication system (such as a new radio (NR) system), a future communication system, or other similar communication systems, and the like, without limitation.

[0062] The present application will present various aspects, embodiments or features around a system that can include a plurality of devices, components, modules, and the like. It should be understood and appreciated that each system can include additional devices, components, modules, and the like, and / or can not include all of the devices, components, modules, and the like discussed in conjunction with the figures. Moreover, combinations of these aspects can also be used.

[0063] In order to facilitate understanding of the embodiments of the present application, FIG. 1 shows a possible, non-limiting system schematic diagram. As shown in FIG. 1, the communication system 10 includes a radio access network (RAN) 100 and a core network (CN) 200. Optionally, the communication system 10 can also include the Internet 300.

[0064] The RAN 100 includes at least one RAN node 110 (e.g., 110a and 110b in FIG. 1, collectively referred to as 110) and at least one terminal (e.g., 120a-120j in FIG. 1, collectively referred to as 120). Other RAN nodes 110 can also be included in the RAN 100, such as wireless relay devices and / or wireless backhaul devices (not shown in FIG. 1), etc. The terminals 120 are wirelessly connected to the RAN nodes 110. The RAN nodes 110 are connected to the core network 200 through wireless or wired means. The core network network elements in the core network 200 and the RAN nodes 110 in the RAN 100 can be different physical devices, respectively, or can be the same physical device integrated with the logical functions of the core network and the logical functions of the wireless access network.

[0065] The RAN 100 can be a 3rd generation partnership project (3GPP) related cellular system, such as a 4G, 5G mobile communication system, or a future evolution system. The RAN 100 can also be an open radio access network (O-RAN or ORAN), a cloud radio access network (CRAN), or a WiFi system. The RAN 100 can also be a communication system that integrates two or more of the above systems.

[0066] The RAN nodes, which can also be referred to as RAN entities or access nodes, access network devices. In the present application, the RAN nodes 110 are used to represent the RAN nodes unless otherwise specified. The RAN nodes (e.g., RAN nodes 110) form part of the communication system and are used to help terminals to access wirelessly. The RAN nodes 110 in the communication system 10 can be the same type of node or different types of nodes. In some scenarios, the roles of the RAN nodes 110 and the terminals 120 are relative, for example, the network element 120i in FIG. 1 can be a helicopter or a drone, which can be configured as a mobile base station. For those terminals 120j that access the RAN 100 through the network element 120i, the network element 120i is a base station; but for the base station 110a, the network element 120i is a terminal. The RAN nodes 110 and the terminals 120 are sometimes referred to as communication apparatuses, for example, the network elements 110a and 110b in FIG. 1 can be understood as communication apparatuses with base station functions, and the network elements 120a-120j can be understood as communication apparatuses with terminal functions.

[0067] The RAN node 110 can be a device or module with corresponding communication functions located at the network side of the above communication system. The RAN node 110 is usually provided with a communication module, circuit or chip for performing corresponding communication functions. The RAN node 110 is also provided with programs or instructions configured for performing corresponding communication functions and corresponding programs or instructions.

[0068] In a possible scenario, the RAN node 110 can be a base station (BS), an evolved NodeB (eNodeB), a transmitting point (TP), an access point (AP), a transmission reception point (TRP), a mobile switching center, a next generation NodeB (gNB), a next generation base station in a future communication system, or an access node in a WiFi system, etc. The RAN node 110 can be a macro base station (such as 110a in FIG. 1), a micro base station or an indoor station (such as 110b in FIG. 1), a relay node or a donor node, or a wireless controller in a CRAN scenario, a satellite, a drone, a balloon or an airplane, etc. Alternatively, the RAN node 110 can also be a server, a wearable device, a vehicle or a vehicle-mounted device, etc. For example, the RAN node 110 in a vehicle to everything (V2X) technology can be a road side unit (RSU). All or part of the functions of the RAN node 110 in this application can also be implemented by software functions running on hardware, or by virtualized functions instantiated on a platform such as a cloud platform. The RAN node 110 in this application can also be a logical node or a logical module or software capable of implementing all or part of the functions of the RAN node 110.

[0069] In another possible scenario, a terminal is assisted by multiple RAN nodes 110 to implement wireless access in cooperation, and different RAN nodes 110 respectively implement part of the functions of a base station. For example, the RAN node 110 can be a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), etc. The CU and the DU can be separately arranged, or can also be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or a radio frequency unit, such as a radio frequency remote unit (RRU), an active antenna processing unit (AAU), or a remote radio head (RRH).

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

[0071] A terminal 120 can access the above-described communication system and have a corresponding communication function. The terminal (e.g., the terminal 120) is also referred to as a user equipment (UE), a mobile station (MS), a mobile terminal (MT), or the like, and refers to a device that provides voice and / or data connectivity to a user. For example, the terminal can be a handheld device having wireless connection capability, a vehicle-mounted device, or the like. Examples of the terminal currently available include a mobile phone, a smart phone, a tablet computer, a notebook computer, a palmtop computer, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, or the like.

[0072] For example, the terminal 120 can include a mobile phone (or called a "cellular" phone), a computer with a mobile terminal, or a portable, pocket, handheld, computer-embedded mobile device, or the like. For example, the terminal can be a device such as a personal communication service (PCS) phone, a cordless phone, a session initiation protocol phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), or the like. The terminal can also include a limited device such as a device with limited power consumption, a device with limited storage capacity, a device with limited computing capability, or the like. For example, the terminal can be an information sensing device such as a bar code, a radio frequency identification (RFID), a sensor, a global positioning system (GPS), or a laser scanner. Embodiments of the present application do not limit the device form of the terminal.

[0073] The core network 200 includes core network network elements, which are collectively referred to as network-side multiple function entities for managing users, data transmission, and base station configuration, including access and mobility management function (AMF) entities, user plane function (UPF) entities, session management function (SMF) entities, tag management function (TMF) entities, ambient IoT management function (AIoTMF) entities, and the like.

[0074] Based on the above description of the core network network elements, the RAN node 110, and the terminal 120, several possible application scenarios are proposed in the present application.

[0075] In one possible application scenario 1, as shown in FIG. 2A, the topology includes a network device 201a or a terminal 202a, and the network device 201a and the terminal 202a directly communicate with each other. For example, when the above communication system is an ambient IoT communication system, the terminal 202a is an A-IoT terminal, the network device 201a is a RAN node, and the communication between the RAN node and the A-IoT terminal includes ambient IoT information. The topology includes RAN nodes that send to A-IoT terminals and RAN nodes that receive from A-IoT terminals, i.e., there is uplink / downlink data / signaling between the RAN node and the A-IoT terminal.

[0076] In another possible application scenario 2, as shown in FIG. 2B, the topology includes a network device 201b, an intermediate node 202b or a terminal 203b, and the network device 201b and the terminal 203b communicate with each other through the intermediate node 202b. The intermediate node 202b includes a reader, an IAB node, a UE, or a repeater. For example, when the above communication system is an ambient IoT communication system, the terminal 203b is an A-IoT terminal, the network device 201b is a RAN node, and the intermediate node can help implement ambient IoT, in which case the intermediate node 202b transmits A-IoT information between the RAN node and the A-IoT terminal.

[0077] In another possible application scenario 3, as shown in FIG. 2C.1 and FIG. 2C.2, the topology includes: a network device 201c, an auxiliary node 202c or a terminal 203c, wherein the auxiliary node includes: a reader, an IAB, a UE or a repeater. For example, when the above communication system is an environmental Internet of Things (IoT) communication system, the terminal 203c is an A-IoT terminal, the network device 201c is a RAN node, the A-IoT terminal sends data / signaling to the RAN node and receives information from the auxiliary node; or the A-IoT terminal receives information from the RAN node and sends information to the auxiliary node. The topology composed of the A-IoT terminal, the auxiliary node 202c and the RAN node can implement the IoT.

[0078] In another possible application scenario, as shown in FIG. 2D, the topology includes: an A-IoT terminal 202d or a terminal 201d, and the A-IoT terminal communicates with a UE in a bidirectional manner. The communication between the A-IoT terminal and the UE includes environmental IoT information.

[0079] In the above, the network device 201a, the network device 201b and the network device 201c can include: the RAN node 110 or the core network element in FIG. 1, for example, the network device 201a can include one RAN node 110 and one core network element, the terminal 120 can communicate with the RAN node 110, report information to the RAN node 110, and the RAN node 110 can send the information reported by the terminal 202a to the core network element. The terminal 202a, the terminal 203b or the terminal 203c can be the terminal 120 in FIG. 1, and a typical application scenario of the present application is that the terminal 202a, the terminal 203b and the terminal 203c are A-IoT terminals, wherein the electronic A-IoT terminal can be referred to as radio frequency identification (RFID). The A-IoT terminal can be divided into three types: active, passive and semi-active. For the passive A-IoT terminal, it can also be referred to as passive IOT, i.e., a passive IoT device.

[0080] In an implementation manner, the terminal device in the A-IoT can be divided into three categories:

[0081] One type of device (which can be referred to as device 1): ~1 μW peak power consumption; neither downlink (DL) amplification function nor uplink (UL) amplification function is included in the device; UL transmission of the device is backscattered on an externally provided carrier. Optionally, the device has an energy storage. Optionally, the device is similar to a passive A-IoT terminal.

[0082] Another type of device (may be referred to as device 2a): ≤ several hundred μW peak power consumption; the device has DL amplification function and / or UL amplification function. The UL transmission of the device is backscattered on an externally provided carrier. Optionally, the device has energy storage. Optionally, the device is similar to a semi-passive A-IoT terminal.

[0083] Still another type of device (may be referred to as device 2b): similar to an active A-IoT terminal: ≤ several hundred μW peak power consumption; the device has DL amplification function and / or UL amplification function. The UL transmission of the device is generated internally by the device. Optionally, the device has energy storage. Optionally, the device is similar to an active A-IoT terminal.

[0084] To help understand the above scenarios, for example: A-IoT terminal can be implemented by a terminal in a cellular network, such as an extremely low power consumption, extremely low complexity Internet of Things terminal, i.e. the first type of terminal. Non-contact data communication can be performed between the network device and the first type of terminal, so as to read information from the first type of terminal and / or write information to be stored into the first type of terminal.

[0085] In still another possible application scenario 4, the present application can also be applicable to an O-RAN architecture, in which an access network device communicates with a core network through a backhaul link and communicates with a user equipment (UE) through an air interface. For example, a baseband unit (BBU) in the access network device communicates with a core network through a backhaul link, and a radio unit (RU) in the access network device communicates with at least one UE through an air interface. The BBU communicates with at least one RU through a front-haul link, and the BBU and the RU can be co-located or not co-located. The BBU includes at least one control unit (CU) and at least one distributed unit (DU), which can communicate through at least one mid-haul link.

[0086] It should be noted that the communication system described in the embodiments of the present application is for more clearly illustrating the technical solutions of the embodiments of the present application, and does not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those skilled in the art can know that the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems as the network architecture evolves and new business scenarios appear.

[0087] The following first explains the related terms involved in the embodiments of the present application. It should be noted that these explanations are to make the embodiments of the present application easier to understand, and should not be regarded as a limitation on the scope of protection required by the present application.

[0088] 1. Reader-writer:

[0089] Reader-writer, also known as RFID radio frequency identification device, reader, interrogator, communicator, scanner, reader and writer, programmer, reading device, portable readout device or AEI device (Automatic Equipment Identification device). It can be understood as a device for reading (or writing) A-IoT terminal information, which can be handheld or fixed. It can also be understood as a device for communicating with A-IoT terminals, which can be a terminal, an access network device such as a base station, or a signal sending node such as a headend, pRU, TRP (transmission reception point), or a device with read-write function. It can also be an IAB (integrated access and backhaul) node or a smart repeater or a relay node.

[0090] 2. In this application, less than and less than or equal to can be replaced with each other, and greater than and greater than or equal to can be replaced with each other.

[0091] 3. In this application, transmission can include sending and / or receiving. In this application, "sending" and "receiving" can represent the direction of information transmission. For example, "sending information to X device" can be understood as the destination of the information is X device, which can include direct transmission through the air interface, or indirect transmission through the air interface by other units or modules. "Receiving information from Y device" can be understood as the source of the information is Y device, which can include direct reception from Y device through the air interface, or indirect reception from Y device through the air interface by other units or modules. Transmission is an example of naming, which can be replaced by any possible naming, for example, it can also be named as reporting, uploading or inputting, etc. Receiving is an example of naming, which can be replaced by any possible naming, for example, it can also be named as obtaining, etc. "Sending information to … (terminal)" can be understood as the destination of the information is the terminal, which can include direct or indirect transmission of information to the terminal. "Receiving information from … (terminal)" can be understood as the source of the information is the terminal, which can include direct or indirect reception of information from the terminal. The information between the source and the destination of the information transmission can be processed as necessary, such as format change, etc., but the destination can understand the valid information from the source. Similar expressions in this application can be similarly understood, and will not be repeated here. "Sending information to … (terminal)" can be one-time transmission of all information, or the information can be divided into multiple sub-information, and then the sub-information is sent respectively.

[0092] 4. In this application, information is an example of naming, which can be replaced by any possible naming, for example, it can also be named as message, signaling, command, indication or data.

[0093] 5. In this application, interval is an example of naming, which can be replaced by any possible naming, for example, it can also be time interval or spacing, without limitation.

[0094] 6. In this application, "for indicating" can include for directly indicating and for indirectly indicating. When describing that certain indication information is for indicating A, it can be understood as the indication information carries A, directly indicates A or indirectly indicates A.

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

[0096] 8. "Downlink" in the present application can also be replaced by "reader-to-device (R2D)" or "reader device (RD)"; "Uplink" in the present application can be replaced by "device-to-reader (D2R)" or "device reader (DR)". For example, the transmission of the second device to the first device is downlink transmission or R2D transmission, and the transmission of the first device to the second device is uplink transmission or D2R transmission.

[0097] 9. "Data" in the present application can be replaced by data packet, protocol data unit (PDU), message, signaling, etc.

[0098] 10. "Electronic product code (EPC)" and "device identity (device ID)" in the present application can be interchangeable. Alternatively, the EPC can be one or part of the content of the device ID.

[0099] 11. In the present application, the security parameter includes: information for encryption, device-related configuration information or information for integrity protection.

[0100] 12. In the present application, saving can be saved to buffer, storage, register, etc., and the form is not limited.

[0101] 13. In this application, interval can also be replaced by other names, such as time interval or spacing, without limitation.

[0102] Radio frequency identification, RFID for short, is a kind of automatic identification technology. An RFID system includes a reader and a tag device. The reader reads information from the tag device or writes information required to be stored in the tag device into the tag device. The reader and the tag device perform non-contact data communication. The tag device has simple functions and needs to rely on the excitation of the reader to send information, that is, the tag device converts the wireless signal sent by the reader into energy to drive itself to work. The tag supports micro-watt or hundred-micro-watt power consumption and cannot support complex design.

[0103] A-IoT technology can be understood as an extension of RFID in 3GPP. Although A-IoT technology has some principles in common with RFID, such as similar inventory business processes, more valuable scenarios are introduced in 3GPP. A-IoT technology has the characteristics of maintenance-free, low complexity, low cost and sustainability, so A-IoT technology has broad application prospects in logistics, environmental detection and many other fields. The network system applied with A-IoT technology is called A-IoT system. The A-IoT system includes a reader and a terminal. For example, the function of the reader can be realized by a network device. For example, the terminal in the A-IoT system can be an Internet of Things terminal with extremely low power consumption and extremely low complexity.

[0104] When the terminal is executing a service, the service may be suspended. For example, the terminal in the A-IoT system usually has a long charging time, and when in the charging state, the terminal cannot send and receive messages, so the service being executed by the terminal in the charging state will be suspended. After the charging is completed, the terminal will resume the service. However, at this time, the network side may misjudge that the service fails. This misjudgment may cause the terminal to repeat the completed part of the interrupted service after the service is resumed, resulting in waste of resources.

[0105] Therefore, how to avoid the network side from misjudging the interrupted service as a service failure when the terminal interrupts the service is a technical problem to be solved.

[0106] To solve the above technical problem, the embodiments of the present application provide a communication method. For the communication method, the embodiments of the communication method in various application scenarios are provided.

[0107] It should be noted that the first device in the following embodiment 1, embodiment 2, embodiment 3 and embodiment 4 can be a terminal or a device, or a module in the terminal, a communication module, a circuit or a chip responsible for the communication function (such as a modem chip, or a system on chip (SoC) chip or a system in package (SIP) chip containing a modem core, a chip system or a processor, or a logical node or a logical module capable of realizing all or part of the terminal function. For example, when the method shown in FIG. 3 is applied to the system shown in FIG. 1, the first device can be the terminal 120. As mentioned earlier, a typical application example of the present solution is that the first device is an environmental Internet of Things terminal or device.

[0108] It should be noted that the second device in the following embodiment 1, embodiment 2, embodiment 3 and embodiment 4 can be a reader / writer, or a module in the reader / writer, a communication module, a circuit or a chip responsible for the communication function (such as a modem chip, or a SoC chip or a SIP chip containing a modem core), a chip system or a processor, or a logical node or a logical module capable of realizing all or part of the reader / writer function. For example, when the method shown in FIG. 3 is applied to FIG. 2A, the reader / writer can be the network device 201a, such as an access network device with reader / writer function or a module in the access network device capable of realizing the reader / writer function; when the method shown in FIG. 3 is applied to FIG. 2B, the reader / writer can be the intermediate node 202b, which can be an access network device or a terminal with reader / writer function, for example, which can be an access network device or a module in the terminal capable of realizing the reader / writer function; when the method shown in FIG. 3 is applied to FIG. 2C.1 or FIG. 2C.2, the reader / writer can be the network device 201c or the auxiliary node 202c, which can be an access network device or a terminal, for example, which can be an access network device or a module in the terminal capable of realizing the reader / writer function; when the method shown in FIG. 3 is applied to FIG. 2D, the reader / writer can be the terminal 202d, and can also be a module in the terminal 202d capable of realizing the reader / writer function.

[0109] It should be noted that the third device in the following embodiment 1, embodiment 2, embodiment 3 and embodiment 4 can be an access network device, or a module in the access network device, a communication module, a circuit or a chip responsible for the communication function (such as a modem chip, or a SoC chip or a SIP chip containing a modem core), a chip system or a processor, or a logical node or a logical module capable of realizing all or part of the access network device function.

[0110] It should be noted that the fourth device in the following embodiment 1, embodiment 2, embodiment 3 and embodiment 4 can be a core network element, or a module in the core network element, a communication module, a circuit or chip responsible for communication function (such as a modem chip, or a SoC chip or SIP chip containing a modem core), a chip system or a processor, or a logic node or a logic module capable of realizing all or part of the functions of the core network element.

[0111] Embodiment 1

[0112] Embodiment 1 is an example of the application applied to the scenario shown in FIG. 2B, and triggered by the second device (such as a reader) to restore the service.

[0113] FIG. 3 is a flowchart of the communication method in embodiment 1 of the application. In FIG. 3, the first device, the second device, the third device and the fourth device are taken as an example of the execution subject of the interaction to illustrate the method, but the application does not limit the execution subject of the interaction. As shown in FIG. 3, the method comprises:

[0114] S301: The second device receives the first information sent by the first device;

[0115] It should be noted that the first information is used to indicate that the first service of the first device is in a suspended state, or the first information includes information indicating that the first service of the first device is in a suspended state, or the first information is used to indicate that the first device is in sleep, or the first information contains information indicating that the first device is in sleep.

[0116] It should be noted that the "service" in the application is an example of naming, which can also be replaced by any possible naming, such as task, process or procedure, etc.

[0117] Optionally, the state of the first service in the embodiment can include a suspended state or a resumed state. Optionally, the suspended state can be a state in which the first service that is in progress or has started is temporarily stopped, temporarily disconnected, or stopped for a period of time, the service entering the suspended state is not failed, and the service can still be resumed at or after the end of the suspended state. The suspended state is an example of naming, which can be replaced by any possible naming, such as interrupted state, suspended state, or paused state. The naming of the state is not limited, and any naming that can describe a service in an interrupted state but can be resumed later can be used. For example, the first device can be unable to continue the first service due to insufficient power, and the first service enters the suspended state at this time. When the power is full, the first device can also resume the service. Optionally, the resumed state is to resume the first service, for example, can be to continue the first service in the suspended state, for example, can be to resume the information transmission process of the suspended first service, for example, can be to continue the related flow, step, or process of the first service before the suspended state starts. Resumed is an example of naming, which can be replaced by any possible naming, such as continued or extended.

[0118] Optionally, the state of the first device in the embodiment includes sleep or wake up. Optionally, in the sleep state, the first device can maintain basic functions, such as maintaining the storage state of the register / memory, but generally cannot perform data transmission, such as cannot receive information, cannot perform data transmission, or only maintains receiving information, does not send data, or only receives some specific information, such as trigger information, and / or paging message. It should be understood that sleep is an example of expression, which can also be replaced by any possible expression, such as insufficient power, insufficient energy, service interruption, unable to transmit information, or energy saving. Optionally, in the wake-up state, the first device can perform data transmission or continue to perform the service, such as can continue to perform data transmission, such as can continue to send data, such as trigger information, and / or paging message.

[0119] Optionally, there can be a certain association between the state of the first device and the state of the first service in the application, for example, when the first device is in sleep, the first service can enter the suspended state; for example, when the first device is in wake-up, the first service can enter the resumed state; for example, when the first service is in the suspended state, the first device can be in sleep, for example, when the first service can enter the resumed state, the first device can be in wake-up.

[0120] Optionally, a timer can also be maintained in the sleep state. For example, a timer can be configured in the first terminal, and the timer can control the first terminal to end the sleep state after T, where T is the sleep period or the duration of the suspended state of the first service.

[0121] It should be noted that, from the perspective of a service or an application scenario, the first service can include at least one of the following: an inventory service, a command service, a positioning service, a sensing service, proximity, reading, writing, deactivation, locking, or a security process (such as authentication, certification, registration, and the like), wherein the reading, writing, deactivation, and locking can be a separate service type or can be a type of command service. From the perspective of a process, the first service can include at least one of the following: a paging process, an access process, or a data transmission process. The access process includes at least one of the following: random access or reporting of a device ID. For example, the random access can be contention-based random access or contention-free random access. Alternatively, the first service can include one service type or multiple service types. For example, the first service includes two service types, namely, the inventory service and the reading service, and the reading service is a type of command service and can be referred to as a reading command service. Alternatively, before the first service is suspended or before the first device is put into hibernation, the first service can be of the inventory service type, and the first service can be used to complete an inventory process. After the first service is resumed or the first device is woken up, the first service can be of the reading command service type, and the first service can be used to complete a reading command process. The first service can include transmission of one uplink data and / or one downlink data, or transmission of multiple uplink data and / or multiple downlink data. For example, the first service includes transmission of three uplink data and three downlink data. Before the first service is suspended or before the first device is put into hibernation, the first service is used to transmit the first uplink data and the first downlink data. After the first service is resumed or the first device is woken up, the first service is used to transmit the subsequent two uplink data and downlink data, and the subsequent two uplink data and downlink data can be transmitted at one time or can be transmitted in two times, which is not limited in the present application.

[0122] Alternatively, in the present application, all uplink and downlink, such as uplink data, downlink data, uplink command, uplink command, and the like, can be associated with the first device and / or the first service.

[0123] Alternatively, the first information includes a security parameter. Alternatively, the first device can encrypt the first information by using the security parameter.

[0124] It should be noted that, step 301 is an optional step, and step 301 can be replaced by the following steps: the second device determines that the first device is in hibernation; the second device determines that the first service is in a suspended state; the second device obtains information indicating that the first device is in hibernation, or the second device obtains information indicating that the first service is in a suspended state.

[0125] Optionally, before step S301, step S300 is further included. The first device accesses the second device. For example, FIG. 4 is a flow diagram of a process in which the first device accesses, according to an embodiment of the present application. Step S300 includes the following steps:

[0126] S300a. The fourth device sends a service request to the third device.

[0127] It should be noted that the service request can also be referred to as a paging message. Optionally, the service request can be used to instruct the first device to perform the first service. Optionally, the service request can include information (service ID) used to identify the service. For example, the service ID can be used to identify the first service. Optionally, the service ID can be assigned by the fourth device, or can be sent to the fourth device by another device. Alternatively, another device can send service-related information or first-device-related information to the fourth device, and the fourth device can obtain the service ID based on the information.

[0128] In an optional implementation, the service ID can be understood as a process number of the service. The service ID can be used to associate identification information of a requested or initiated service. For example, the service ID can be updated each time a new service is sent by the network. The service associated with the service ID can include inventory service, command service, positioning service, sensing service, proximity, read, write, inactivation, lock or security process (such as authentication, authorization, registration, etc.). The read, write, inactivation and lock can be a separate type of service, or can be a type of command service. The service associated with the service ID can be completely identical to the first service, or can not be completely identical to the first service. For example, the first service can include random access, inventory service or command service, and the service associated with the service ID can be inventory service or command service. After the first device saves the service ID, the first device can determine which service is suspended by the first device, and whether the currently executed service is the service suspended by the first device.

[0129] In another alternative implementation, the service ID can be used to indicate a type of service, which can include: inventory service, command service, inventory service, command service, location service, sensing service, proximity, read, write, deactivate, lock or security procedure (e.g., authentication, authorization, registration, etc.), wherein read, write, deactivate and lock can be a separate type of service or can be a type of command service. When the first device saves the service ID, it can determine the type of service to be performed before the suspension state starts or before the first device goes to sleep.

[0130] It should be noted that the service ID is an example designation, which can be replaced by any possible designation, such as session ID, task ID, transaction ID.

[0131] For example, the service ID can be 1-bit indication information, such as service ID = 0 indicating that the current requested / initiated service is the service associated with service ID = 0, and service ID = 1 indicating that the current requested / initiated service is the service associated with service ID = 1, which is a new request / initiation of the service relative to the service associated with service ID = 0.

[0132] S300b. The third device sends response information (response) to the fourth device;

[0133] Optionally, the response is an example designation, which can be replaced by any possible designation, such as response message, response information, confirmation information or indication information. It can be understood that the third device sends the response to the fourth device in response to or to confirm the service request sent by the fourth device to the third device.

[0134] S300c. The third device sends a paging message to the second device;

[0135] It should be noted that the paging message is an example designation, which can be replaced by any possible designation, such as select message, trigger message, initial trigger message or indication message, etc. The application does not limit the designation, and any message used to implement the function of the paging message in the embodiments of the application can be understood as the paging message.

[0136] Optionally, the paging can be a paging message, or a triggering message of paging, or a message / request message indicating paging A-IoT. For example, the third device can send an RRC message to the second device, for indicating the second device to send A-IoT paging. For example, the A-IoT can be the first device.

[0137] It should be noted that the order of S300a, S300b and S300c is not limited, and S300a, S300b and S300c are optional steps. For example, the execution order of S300a, S300b and S300c can be S300a, S300c, S300b. For example, only S300a and S300c can be executed.

[0138] Optionally, the paging can also be triggered by the fourth device, for example, a core network element, for example, the core network element sends the above service request to the third device, and then the third device sends the response to confirm the service request, at this time the fourth device can trigger the paging.

[0139] Optionally, the paging can be used to instruct the first device to access the second device, such as when the second device is an access network device, the paging can be used to instruct the terminal to access the network; when the second device is a terminal, such as terminal 2, the paging can be used to instruct the terminal to access the terminal 2, and optionally, in accessing the terminal 2, the first device can access the network through the terminal 2. Optionally, the paging can also be used to trigger or instruct the first device to send uplink data or perform first service. Alternatively, the paging is used to page the first device, which can page one or more or all first devices receiving the paging message, or a part of the first devices satisfying the matching condition, wherein the matching condition can include: the paging message carries a first identifier, the first identifier can be a group identifier or a mask or an identifier of the first device, and the second device determines whether to match the first identifier according to its own identifier, such as the second device determines whether the first identifier is the same as its own identifier (or identifier part information), and the specific matching condition is not limited by the present scheme; for another example, the paging message does not carry the identifier information related to the first device, and by default all first identifiers can satisfy the matching condition. Among them, paging is an example of naming, which can also be replaced by any possible naming, such as selection / triggering / screening, etc. For example, Paging can be used to instruct AIOT device to access reader, such as: when the reader is a base station / access network device, Paging can be used to instruct device to access the network. When the reader is a terminal device, Paging can be used to instruct device to access the terminal device, and optionally, device can access the network through the terminal device. Paging can also be used to trigger / instruct device to send uplink data, or to trigger / instruct / request device to perform first service, wherein the first service can include at least one of the following: paging service, inventory service, command service (such as read, write, inactivate, lock, etc.), positioning service, sensing service. Paging, or called trigger message / instruction, initial trigger message / instruction, downlink trigger message / instruction, initial downlink trigger message / instruction, selection message, etc. The specific name is not limited, which can be triggered by the core network element.

[0140] The first device accessing the second device can be random access, which can be contention free random access (CFRA) or contention based random access (CBRA). Alternatively, the first device can not access the second device through random access, but access the second device or network in a mobile terminated (MT) mode. For example, the second device sends a Paging message to the first device, and triggers the first device to send data directly without random access. Optionally, the Paging message can include Query signaling.

[0141] Optionally, the paging can indicate a command, which can be used to indicate a target operation, such as reading, writing, locking, positioning, sensing or deactivation. The default paging triggers inventory service, and the inventory service and the command service are two types of services. The inventory service is to send the device ID of the first device in random access or after successful random access, that is, to complete the inventory service.

[0142] For example, in the case where the paging indicates the command, the uplink data reported by the first device to the second device can be data responding to the command. In the case where the paging triggers the inventory service or the paging does not carry the command, the uplink data reported by the first device to the second device can be the device ID of the first device by default. The specific message format can be in the form of sending the two messages paging and command in parallel, or in the form of sending one paging message carrying the command.

[0143] For example, in the case where the paging does not carry the command, the first device needs to record or save the content related to the command, such as reading / writing operation on the content of which storage area. After receiving the scheduling information sent by the second device, the first device sends the corresponding data.

[0144] S300d. The second device sends a paging to the first device;

[0145] It should be noted that the paging content in step S300d can be determined according to the paging in S300c, for example, the paging in S300c is the first A-IoT paging request message, and the second device can forward the content in the first A-IoT paging request message in S300c to the first device; or the second device can also process and forward the content, such as obtaining the content carried in the first A-IoT paging request message, generating a second A-IoT paging message according to the content, and sending the second A-IoT paging message to the first device. For example, the message sent in S300c can be a radio resource control (RRC) message, and the message sent in S300d can be a media access control (MAC) message.

[0146] S300e. The second device sends query information (query) to the first device;

[0147] It should be noted that in this application, the query information is an example of naming, which can also be replaced by any possible naming, such as access indication / trigger, access round indication / trigger, inquiry information or inquiry message, etc., or any message used to realize the function of the query information in the embodiments of the application can be understood as the query information. The query can be used to trigger / indicate at least one access opportunity. For example, it can directly or indirectly indicate the total number of access opportunities, and can also be used to trigger the first access opportunity. The above-mentioned access opportunity can also be described as an access occasion, an access time slot, etc., and each access opportunity can allow the first device to send at least one of the following: an access request, identification information for contention resolution, data, etc. For example, the query can include: Q value, session or flag bit, for example, when the session in the query is S0 and the flag bit is A, when the session of the first device is also S0 and the flag bit is A, that is, the session and the flag bit in the query match the session and the flag bit of the first device, the first device can generate a random number of 0~2^Q-1 as the initial value of the Counter according to the Q value.

[0148] It should be noted that the above-mentioned query can be combined with the paging in S300d into one message for sending.

[0149] If no terminal sends a response, the second device will perform S300f.

[0150] S300f. The second device sends a repeated query message (queryrep) to the first device.

[0151] Optionally, the queryrep can be used to trigger / indicate at least one access opportunity, such as an access opportunity to access the third device, such as directly or indirectly indicating the total number of the at least one access opportunity. The queryrep can be used to trigger the next access opportunity, or can be understood as indicating / associating with a boundary of an access opportunity, which can be a start or an end. The access opportunity can be a time period, such as including at least one of a symbol, a slot, a subframe, or a radio frame, and the specific time domain granularity is not limited. The repeated query message can be used to trigger the first access opportunity, and thus the repeated query message can also be used to trigger the first access opportunity.

[0152] It should be understood that the repeated query message is an example of a naming, and can be replaced by any possible naming, such as an access indication / trigger, an access round indication / trigger, or any message used to implement the function of the query message in the embodiments of the present application can be understood as the repeated query message.

[0153] Optionally, when the first device receives the queryrep, the counter of the first device is counter-1. If the counter of the first device is 0, the first device performs step S300g. If the counter of the first device is 0, the first device does not need to perform step S300g.

[0154] S300g. The first device sends a random number (RN) to the second device.

[0155] Optionally, the RN is used for contention resolution, and is used to distinguish different terminals in the random access process or to distinguish different terminals in the contention resolution process. The RN is an example of a naming, and can be replaced by any possible naming, such as a random access ID or a random ID. Optionally, the RN is a 16-bit random number, and the RN is RN16. Optionally, the RN can also be an 8-bit random number, and the RN is RN8. Similarly, the RN can also be RN24, and so on.

[0156] It is to be noted that the second device, after receiving the RN, if the RN is successfully received, including successfully decoding the RN, such as only receiving the RN sent by one device, or receiving the RN sent by multiple devices and successfully decoding at least one RN, i.e. only receiving the RN sent by one terminal, executes step S300h.

[0157] S300h. The second device sends an acknowledgement (ACK) to the first device.

[0158] Optionally, the ACK is used to indicate whether the contention resolution is successful, and the ACK is an exemplary naming, which can also be replaced by any possible naming, for example, it can also be named as an access ID response or an access response, or a contention resolution identity, for example, it can be a contention resolution identity of a terminal.

[0159] Optionally, the RN can be included in the ACK, for example, it can be the RN sent by the first device in step S300g, so as to indicate that the contention resolution is successful.

[0160] Optionally, after step S300h, if the first device receives the ACK, and the RN carried in the ACK matches the RN of the first device, the first device feeds back an electronic product code (EPC), otherwise, it does not feed back the EPC.

[0161] Optionally, when the first device sends the EPC and the first device receives the queryrep, it indicates that the data transmission is successful or the access is successful. At this time, the first device can flip a flag bit, for example, it is flipped to B, wherein the flag bit can be used to prevent a tag that has been inventoried from being inventoried repeatedly, for example, when a query with the flag bit being A is received subsequently, since the flag bit has been flipped to B, the first device will not respond to the query at this time, and the corresponding tag will not be inventoried repeatedly.

[0162] Optionally, after step S301, after the first device sends the first information to the second device, the second device can send first response information in response to the first information sent by the first device, for example, the first response information is sent in the form of queryrep, or the first response information is sent separately in addition to queryrep, the first response information can be used to indicate whether the first device is allowed or not allowed to suspend the first service, or the first response information can also be used to indicate whether the first device can sleep. For example, the first response information can include 1-bit indication information, which is used to indicate whether the first service is allowed to be suspended. For example, indication information = 0 indicates that the suspension is refused, and indication information = 1 indicates that the suspension is not allowed. Or the indication information is used to indicate that the first device can sleep, for example, indication information = 0 indicates that the sleep is allowed, and indication information = 1 indicates that the sleep is not allowed.

[0163] Optionally, the above-mentioned service request, paging, response, query, queryrep or ACK information can be carried in the MAC layer, such as MAC control element (CE) or MAC service data unit (SDT) or MAC protocol data unit (PDU), or the MAC layer can be replaced by "ambient IoT access stratum (A-IoT AS) layer".

[0164] Optionally, two examples are provided below to illustrate how the second device indicates the time length information T and the identity of the first device, or how the second device agrees on the time length information T and the identity of the first device.

[0165] Example 1:

[0166] The method shown in FIG. 3 further includes step S302, which is specifically as follows:

[0167] S302: The second device sends time information T and / or a second identity to the first device;

[0168] It should be noted that the second identity is associated with the first device or the first service. In this application, the time information T can be used to indicate the sleep time length of the first device. Optionally, T can be used to indicate the maximum sleep time length of the first device, for example, after receiving the time information T, the sleep time length of the first device cannot exceed T. Optionally, T can also be used to indicate the sleep period of the first device, or can be used to indicate the time length of the suspension state of the first service. For example, when T is used to indicate the sleep period of the first device, the first device will wake up every T time, and optionally, after the first device wakes up, it can continue to receive messages for T1 time and then enter sleep.

[0169] Optionally, the information transmitted between the first device and the second device in the application can be carried in a MAC CE message, or in a message capable of realizing a function similar to that of a MAC CE message, or in an A-IoT AS message, or in a message capable of realizing a function similar to that of an A-IoT AS message, or in a NAS message, or in a message capable of realizing a function similar to that of a NAS message. For example, the information transmitted between the first device and the second device can be the time information T and / or the second identifier described above, and can also be the first information.

[0170] Optionally, the T described above can be agreed upon in a protocol, or can be determined by the second device according to historical information of the first device or related information of the first service, or can be sent to the second device by a third device or a fourth device. For example, the second device can determine T according to the historical charging time of the first device and the completion progress of the first service.

[0171] Optionally, T1 can be specified by a protocol, or can be determined by the second device according to historical information of the first device or related information of the first service, or can be sent to the second device by the first device, or can be sent to the first device by the second device.

[0172] Optionally, the unit of the T or T1 described above can be an absolute time, such as millisecond, microsecond, second, minute, etc., or can be a relative time, such as a number of a certain unit of time, such as a time slot, a frame, etc.

[0173] Optionally, the second identifier and the time information T can be indicated in the same message, or can be indicated separately.

[0174] It can be understood that by sending T, the second device can indicate the duration of the suspension state of the first device, so as to prevent the first device from suspending the first service for too long, causing the time delay of the first service to be too long, and also to prevent the first device from suspending the first service for too short, causing the first device to resume the first service when the power is not sufficient enough, resulting in the first service being possibly suspended again. By sending the second identifier, the second identifier can be attached when transmitting service-related data or other information subsequently, so as to inform the second device that the service-related data is associated with the second identifier.

[0175] Optionally, the second identity can be associated with one or more first devices, the second identity can be the RN in step S300g, the second identity can be derived from the RN, for example, second identity = log(RN), the second identity can be determined by the second device, for example, the second device can assign an identity to each A-IoT accessing the network, the identity is used to distinguish each A-IoT, for example, there are four A-IoTs accessing the network through the second device, the first device is the second A-IoT, and the second identity can be #2. The second identity can also be the device ID of the first device, or be determined according to the device ID of the first device, or the second identity can be determined in combination with the RN and the device ID, or the second identity can be sent by the third device or the fourth device to the second device.

[0176] Optionally, the first response information can include the T and the second identity, or the first response information can include the T, and the second identity is sent through other information, or the first response information can include the second identity, and the T is sent through other information, or the second identity and the T are sent through one or more messages other than the first response information, the second identity and the T can be sent simultaneously or separately.

[0177] Example 2

[0178] S302 is optional, for example, step S302 can not be performed in the following examples. One example is that when the T and / or the second identity are to be sent by the first device to the second device, S302 can not be performed. For example, the T and / or the second identity are configured through the aforementioned ACK message, or are indicated by the aforementioned paging or query, the first device can also indicate the T and / or the second identity when sending the RN in S300g, or take the RN of S300g as the second identity, at this time S300g can not assign the second identity, at this time the second identity can be used for contention resolution, that is, for S300h. In another example, the second device and the first device can also not agree on the T and / or the second identity, at this time S302 can not be performed. For example, the second device can first estimate the duration of the suspension of the first service as m, and then send an indication information to the first device at a time point that is m away from the time point when the first information is received, the indication information is used to indicate the resumption of the first service, or the information for waking up the first device, or to indicate that the first device has woken up, or that the first device is in a wake-up state, or to indicate that the first device will wake up (for example, the first device will wake up after a period of time); or the second device can randomly select a time point to send an indication information to the first device after receiving the first information, the indication information is used to indicate the resumption of the first service or the waking up of the first device.

[0179] S303. The second device sends second information to the third device;

[0180] The second information is used for indicating that the first service is in the suspension state or the first device is in dormancy, and the second information comprises a first identifier, the first identifier being associated with the first device or the first service, or the second information comprises information used for identifying the first device, or the second information comprises information used for associating with the first device.

[0181] It can be understood that, by sending the first identifier, the second device can indicate the third device that the terminal in service suspension is the first device or the first device is in dormancy.

[0182] It can be understood that, in the present application, the first device in dormancy generally does not mean that the first device has entered or immediately enters dormancy, but can be that the first device will enter dormancy after a period of time, and waits for the preparation work of dormancy to be completed, such as obtaining the second identifier, and then enters dormancy, and therefore it can also be understood that the indication information is used for indicating that the first device will enter / needs to enter / prepares to enter / is about to enter dormancy, etc. Of course, if the preparation work of dormancy has been completed, the first device can also immediately enter dormancy after sending the indication information.

[0183] It can be understood that, in the present application, the first task in suspension generally does not mean that the first task has entered or immediately enters suspension, but can be that the first task will enter suspension after a period of time, and waits for the preparation work of suspension to be completed, such as obtaining the second identifier, and then enters suspension, and therefore it can also be understood that the indication information is used for indicating that the first task will enter / needs to enter / prepares to enter / is about to enter suspension, etc. Of course, if the preparation work of suspension has been completed, the first device can also immediately enter suspension after sending the indication information.

[0184] Optionally, the information transmitted between the second device and the third device in the present application can be carried in an RRC message, or carried in a message capable of realizing a function similar to that of the RRC message, or carried in a NAS message, or carried in a message capable of realizing a function similar to that of the NAS message. For example, the information transmitted between the second device and the third device can be the second information or the second scheduling information, etc.

[0185] Optionally, the second device can save the second information.

[0186] Optionally, the third device can save the second information.

[0187] Optionally, the first identifier can include the second identifier, or the first identifier can include an identifier associated with the second identifier, or the first identifier can be associated with the second identifier, such as the first identifier being the same as the second identifier, or the first identifier can also be obtained by the second device based on the second identifier, for example, the first identifier can be obtained in combination with the second identifier and the device id of the first device or the RN, or the first identifier can also be generated by the third device, for example, the third device can assign an identifier to each terminal accessing the network, which is used to distinguish each terminal, for example, there are three terminals accessing the network through the third device, and the first device is the third terminal accessing the network, and the first identifier can be #3, respectively. The first identifier can also be the device ID of the first device, or be determined according to the device ID of the first device, and the first identifier can also be sent by the fourth device to the second device or the third device.

[0188] Optionally, the first identifier can also include a service ID, such as the first identifier being the service ID, or the first identifier including the second identifier and the service ID, or the first identifier including the service ID and an identifier associated with the second identifier, when the service ID is associated with the first service, the first identifier can be the service ID, when the first service is a service triggered in the service request, the first identifier can be the service ID included in the service request in S300a, or when the first service is a new service, the second device can also generate a service identifier, for example, when the first service in the suspended state is not the same service as the service suspended before the first device goes to sleep, the first service is considered to be a new service. For example, the service identifier can be determined according to the identifier of the first device, the type of the service, or the time of triggering the first service. Or the first identifier can also not include the service ID, and the service ID is included in the second information.

[0189] Optionally, the second device can determine whether the first service identifier matches the service ID currently possessed by the second device, if not, it means that the first service is a new service, if yes, it means that the first service is not a new service, if it is determined that the first service is a new service, the fourth device can be requested by the third device to determine whether to restore the previous related service, or the second device can also directly discard the previous related service, if it is determined that the first service is not a new service, the previous related service can be restored.

[0190] The following describes other information carried in the second information:

[0191] In an optional implementation, the second information further includes time information T, where T is the duration of the suspension state or the sleep duration of the first device.

[0192] In an optional implementation, the second information further includes a security parameter.

[0193] Optionally, the security parameter can be a security parameter reported by the first device. The second terminal can encrypt the second information by using the security parameter.

[0194] Optionally, the second device can send all information in the second information through one message, or the second device can send information in the second information through multiple messages, for example, through two messages, where one message is used to send the first identifier and the security parameter, and the other message is used to send T and the first service identifier.

[0195] Optionally, the method shown in FIG. 3 further includes the following steps:

[0196] S304. The third device sends fifth information to the fourth device.

[0197] The fifth information is used to indicate that the first service of the first device is in a suspension state or the first device is in sleep, and the fifth information includes a fourth identifier, where the fourth identifier is related to the third identifier, and the fourth identifier is associated with the first device or the first service.

[0198] It can be understood that, by sending the fourth identifier, the fourth device can be notified that the terminal in the suspension state is the first device or the first device is in sleep or the first device will be in sleep (for example, in a period of time). By reporting the fifth information, the fourth device can be indicated that the first service is in a suspension state or the first device is in sleep, and after a period of time, the first service can be restored or the first device can be woken up. Through the above notification, the fourth device can be prevented from mistakenly considering that the first service fails.

[0199] Optionally, information transmitted between the third device and the fourth device in the application can be carried in a NAS message, or carried in a message capable of realizing a function similar to that of the NAS message, or a next generation application protocol (NGAP) message, or carried in a message capable of realizing a function similar to that of the NGAP message. For example, the information transmitted between the third device and the fourth device can be the fifth information.

[0200] In an optional implementation, the fifth information includes T, where T is the duration of the suspension state or the sleep duration of the first device.

[0201] By reporting the T, the fourth device can determine the duration of service suspension, and thus determine the duration of saving the related information of the first service, the time of triggering the first service recovery or the time of waking up the first device.

[0202] In an optional implementation, the fifth information further includes a security parameter.

[0203] Optionally, the security parameter can be the security parameter carried in the second information, and the fourth device can determine whether the security parameter in the fifth information is consistent with the security parameter generated by the fourth device. When consistent, the fifth information can be decrypted. In addition, the security parameter can also be transmitted in the first information, the second information or the fifth information. The third device can also separately send an information to the fourth device, and signaling or message can be used to send the security parameter of the first device to the fourth device.

[0204] S305. The fourth device saves the related information of the first service and / or the first device.

[0205] The related information includes the fourth identifier.

[0206] Optionally, the related information can be the information associated with the first identifier or the first device in the fourth device. By saving the related information of the first service, the related information of the first service can be called when the service is recovered, without the need to repeatedly obtain, generate or transmit the related information of the first service, so that the resources consumed by executing the first service can be saved.

[0207] In an optional implementation, the related information further includes a security parameter, data related to the first service cached before the first device sleeps, data related to the first service cached before the first service enters the suspended state, data already transmitted before the first device sleeps, and data already transmitted before the first service enters the suspended state.

[0208] Optionally, before or after S305, the second device can save the related information of the first service and / or the related information of the first device. For example, the second device can save at least one of the following: the first identifier, the second identifier, the service ID, the security parameter or the data related to the first service cached before the suspended state.

[0209] Optionally, before or after S305, the third device can save the related information of the first service and / or the related information of the first device. For example, the third device can save the related information including the third identifier, the fourth identifier, the service ID, the security parameter or the data related to the first service cached before the suspended state.

[0210] Optionally, the security parameter can be generated by the fourth device, or can be generated by the first device, or can be a security parameter carried in the fifth information.

[0211] Optionally, the data related to the first service cached before the start of the suspension state can be application layer data related to the first service, for example, when the first service is a sensing service, the cached data can be sensing data.

[0212] In an optional implementation, the duration for which the information related to the first service is saved is not less than time information T, wherein T is the duration of the suspension state or the sleep duration of the first device.

[0213] Based on the above implementation, by limiting the duration for which the information related to the first service is saved to be not less than time information T, it can be ensured that after the end of the suspension state or the end of the sleep of the first device, the fourth device can still directly obtain the information related to the first service from the area where the information related to the first service is saved, so that after the service is resumed or the device is woken up, it is not necessary to repeatedly execute the already executed process.

[0214] Optionally, the fourth device saves the information related to the first service for not more than Tmax, Tmax can be determined according to the duration of the suspension of the first service, or can be determined according to the maximum time of the service, or can be determined according to the maximum delay of the service. For example, when the duration of the suspension of the first service is T and the maximum delay of the service is T1, Tmax can be T+△, for example, the△ can be 1Ms, Tmax≤T1. Optionally, Tmax can be determined by the first device; or can be determined by the second device, or Tmax can be sent by the third device, for example, Tmax can be carried in the fifth information, or the first device or the second device can separately send the Tmax.

[0215] S306. The second device sends first scheduling information to the first device;

[0216] The first scheduling information is used to indicate resuming the first service, or waking up the first device, or indicating that the first device has been woken up, or that the first device is in a wake-up state, or indicating that the first device will be woken up (for example, the first device will be woken up after a period of time), the first scheduling information includes a second identifier, the second identifier is associated with the first device or the first service, and the second identifier is related to the first identifier.

[0217] It should be understood that the scheduling information is an example of a naming, which can also be replaced by any possible naming, such as configuration information, wake-up information, resumption information, etc., and any information used to implement the function of the scheduling information of the embodiments of the present application can be understood as the scheduling information.

[0218] Optionally, the first scheduling information can be carried in a media access control control element (MAC CE), or an A-IoT access stratum (AS) message, or a non-access stratum (NAS) message.

[0219] Optionally, the second device can send the first scheduling information to the first device after T, for example, can be at a time length of T from the time of receiving the first information, or at a time length of T from the time of sending the second information. At this time, the first service end suspension state in the first device or the first device ends dormancy, the second device sends the first scheduling information to remind or notify the first device to resume the first service, or the second device sends the first scheduling information to remind or notify to wake up the first device.

[0220] Optionally, the first scheduling information can also not carry the second identifier, but carry the aforementioned RN, or the device id of the second device.

[0221] Optionally, after receiving the first scheduling information, if the second identifier in the first scheduling information matches the first identifier saved by the first device, the first device responds to the first scheduling information and performs step S307, and if it does not match, the first device does not respond to the first scheduling information. Optionally, the "first identifier saved by the first device" can be the identifier carried in the second information received in step S302.

[0222] S307. The first device sends first uplink data to the second device;

[0223] Wherein, the first uplink data is related to the first service.

[0224] Optionally, the first uplink data (UL data) can also be replaced by the first data, the first service data or the first service information. Optionally, the first uplink data can be data generated by the first device due to the resumption of the execution of the first service, which needs to be reported to the fourth device. Optionally, the first device can send the first uplink data in multiple times, or can send the uplink data at one time. The first uplink data can be sent after the first device completes the first service, or can be sent in the process of executing the first service. At this time, the first device can send the uplink data to the second device multiple times.

[0225] Optionally, the first device can send the first uplink data to the fourth device through the second device, at this time, steps S308 and S309 can not be performed.

[0226] S308. The second device sends third information to the third device;

[0227] The third information includes: the second uplink data associated with the second identifier, the first identifier, information indicating resuming the first service or information indicating waking up the first device, and the second uplink data includes the first uplink data.

[0228] Optionally, the third information can also include information indicating that the first device has woken up, information indicating that the first device is in a wake-up state, or information indicating that the first device will wake up (for example, the first device will wake up after a period of time).

[0229] It can be understood that by sending the first identifier, the third device or the fourth device can be notified that the terminal resuming the first service is the first device, by sending the information indicating the first service, the third device or the fourth device can be notified that the resuming is the first service, and by sending the second uplink data, the uplink data can be finally reported to the fourth device, thereby completing the first service.

[0230] Optionally, the second uplink data can be one or more uplink data associated with the second identifier, and the second uplink data includes: the first uplink data sent by the second device this time, the second uplink data can also include uplink data previously sent by the second device but not yet sent to the fourth device, and the second uplink data can also include information related to the first service saved by the third device.

[0231] S309. The third device sends seventh information to the fourth device.

[0232] The seventh information includes: fourth uplink data, the fourth identifier, information indicating resuming the first service or information indicating waking up the first device, and the fourth uplink data includes the third uplink data. The third uplink data in this embodiment is the second uplink data.

[0233] Optionally, the seventh information can also include information indicating that the first device has woken up, information indicating that the first device is in a wake-up state, or information indicating that the first device will wake up (for example, the first device will wake up after a period of time).

[0234] Optionally, the above steps S303 and S304 can be combined, and the above steps S308 and S309 can be combined, for example, the second device can transmit the second information to the fourth device through the third device, and for example, the fourth device can transmit the seventh information to the first device through the third device.

[0235] Optionally, the fourth uplink data can be associated with the third identifier.

[0236] Firstly, through the above embodiment, the second device can send the first service in the suspended state or the first device in the dormant state to the third device, and further inform the fourth device, for example, a core network element, of the information through the third device. Thus, the network side can know that the first service is in the suspended state or the first device is in the dormant state, the first service is not in service failure, and the first service can be restored subsequently. At this time, the second device / third device or the fourth device can save the relevant information of the first service accordingly, so that the first service does not need to be reconnected to the second device or the network when the first service is restored subsequently, and the first service does not need to be re-completed. For example, the second / third / fourth device re-sends the data transmitted before the first service is suspended to the first device, so that the first device does not need to repeatedly generate or obtain the data, and / or the first device sends the data transmitted before the first service is suspended to the second / third / fourth device, so that the second / third / fourth device does not need to repeatedly obtain the data.

[0237] Embodiment 2

[0238] Embodiment 2 is an example of the application applied to the scenario shown in FIG. 2B and triggered by the fourth device (for example, a core network element) to restore the service.

[0239] FIG. 5 is a flowchart of the communication method in Embodiment 2 of the application. In FIG. 5, the first device, the second device, the third device, and the fourth device are taken as an example of the execution subject of the interaction to illustrate the method, but the application does not limit the execution subject of the interaction. The first device in this embodiment can be the same as or different from the first device in Embodiment 1, the second device in this embodiment can be the same as or different from the second device in Embodiment 1, the third device in this embodiment can be the same as or different from the third device in Embodiment 1, and the fourth device in this embodiment can be the same as or different from the fourth device in Embodiment 1. As shown in FIG. 5, the method comprises:

[0240] S500. The first device accesses the second device;

[0241] Step S500 can refer to the description of step S300 in Embodiment 1, which will not be repeated here.

[0242] S501. The first device sends uplink data 1 to the second device;

[0243] Step S501 in this embodiment 1 means that before the first service is suspended or the first device is in the dormant state, the first device can have sent some relevant data of the service to the second device, which is referred to as uplink data 1.

[0244] S502. The second device sends the uplink data 1 to the third device;

[0245] It can be understood that the uplink data 1 sent by the first device to the second device needs to be reported to the network side through the second device.

[0246] S503. The third device sends the uplink data 1 to the fourth device.

[0247] S504. The fourth device sends the downlink data 1 to the third device.

[0248] For example, the uplink data 1 can be data related to inventory business, and the uplink data 1 includes the device ID of the first device. After the CN receives the device ID, it is determined that the target operation, such as read-write operation, needs to be performed on the first device according to the device ID. At this time, the fourth device can send the downlink data 1 to the third device, and the downlink data 1 can carry a downlink command (DL command). The command can instruct the first device to perform the target operation, which includes reading, writing, locking, positioning, sensing or inactivation.

[0249] S505. The third device sends the downlink data 1 to the second device.

[0250] S506. The second device sends the downlink data 1 to the first device.

[0251] It can be understood that the downlink data 1 can be transmitted to the first device through the forwarding of the third device and the second device. Optionally, steps S504 and S505 can be combined, that is, the fourth device transmits the downlink data 1 to the first device through the third device.

[0252] Optionally, after receiving the downlink data 1, the first device may find that the power is insufficient to complete the target operation indicated by the DL command, for example, the data transmission energy is insufficient to complete the target operation indicated by the DL command. At this time, the first device will perform step S507.

[0253] S507. The first device sends the second device first information.

[0254] S508. The second device sends T and / or the second identifier to the first device, wherein T is the time length of the suspended state or the sleep time length of the first device.

[0255] S509. The second device sends the second information to the third device.

[0256] S510. The third device sends the fifth information to the fourth device.

[0257] S511. The fourth device saves the related information of the first business.

[0258] The steps S507-S511 can refer to the description of steps S301-S305 in Embodiment 1, which will not be repeated here.

[0259] S512. The fourth device sends second scheduling information to the second device;

[0260] The second scheduling information is used to indicate that the first service is resumed, or the first device is woken up, or the first device is already woken up or the first device is in a woken-up state or the first device is about to be woken up, and the second scheduling information includes the first identifier.

[0261] In an optional implementation, the second scheduling information includes downlink data, and the downlink data is used to instruct the first device to perform a target operation, and the target operation includes reading, writing, locking, positioning, sensing or deactivation.

[0262] Based on the above implementation, the fourth device can ultimately control the first device to perform the command service via the second device. And the reason why the fourth device can instruct the first device to perform the command service in the present application is that the fourth device receives the feedback of the first device in the foregoing steps, that is, the first device feeds back that the first service is in a suspended state or the first device is in sleep through the sending of the first information. Therefore, the present solution can be applied to the scenario that the first service is a command and the command needs feedback. When the fourth device knows that the first service is suspended or the first device is in sleep, the fourth device can wait for a period of time and then resume the first service, or wake up the fourth device, to avoid misjudging that the service fails.

[0263] It should be noted that in the present embodiment, the fourth device actively triggers the second scheduling information. Alternatively, when the fourth device receives T, if the time difference between the current time and the time when the fourth device receives the information indicating that the first service is in a suspended state reaches T, or the time difference between the current time and the time when the fourth device receives the information indicating that the first device is in sleep reaches T, the fourth device can perform step S513. Alternatively, when the fourth device does not receive T, the fourth device can estimate the time when the suspended state of the first service ends or the time when the first device ends sleep, and perform step S513 when the estimated time is reached, or the fourth device can determine the time when the suspended state of the first service ends or the time when the first device ends sleep according to a protocol, and perform step S513 when the determined time is reached; or multiple scheduling attempts can be made, for example, step S513 can be performed multiple times.

[0264] Optionally, the second scheduling information can be transmitted by the fourth device to the second device through the third device, and the fourth identifier is included in the second scheduling information; or the fourth device sends the scheduling information to the third device first, and the third device sends the second scheduling information to the second device based on the scheduling information, and the first identifier is included in the second scheduling information.

[0265] S513. The second device sends the first scheduling information to the first device.

[0266] The first scheduling information is used to indicate the continuation of the first service, and the second identifier associated with the first device or the first service is carried in the first scheduling information, and the second identifier is related to the first identifier.

[0267] S514. The first device sends the first uplink data to the second device.

[0268] S515. The second device sends the third information to the third device.

[0269] S516. The third device sends the seventh information to the fourth device.

[0270] The steps S514 to S516 can refer to the description of steps S307 to S309 in Embodiment 1, and will not be described here.

[0271] Embodiment 3

[0272] Embodiment 3 is an example applied to the scenario shown in FIG. 2A in the present application, for example, the embodiment 3 can be an example that the network device such as the base station is directly connected with the terminal.

[0273] FIG. 6 is a flowchart of a communication method in Embodiment 3 of the present application. In FIG. 6, the first device, the second device, the third device and the fourth device are taken as an example of the execution subject of the interaction to illustrate the method, but the present application does not limit the execution subject of the interaction. The first device in the present embodiment can be the same as or different from the first device in Embodiment 1 or Embodiment 2, the second device in the present embodiment can be the same as or different from the second device in Embodiment 1 or Embodiment 2, the third device in the present embodiment can be the same as or different from the third device in Embodiment 1 or Embodiment 2, and the fourth device in the present embodiment can be the same as or different from the fourth device in Embodiment 1 or Embodiment 2. As shown in FIG. 6, the method comprises:

[0274] S601. The first device accesses the third device.

[0275] The step S601 can refer to the description of step S300 in Embodiment 1, and will not be described here.

[0276] S602. The first device sends fourth information to the third device;

[0277] It should be noted that, in the network architecture shown in FIG. 2A, the first device can communicate directly with the network device, without the aid of the intermediate node-second device. In the embodiments of the present application, the third device has the function of a reader / writer, i.e., the third device can read out information in the first device, or write information required to be stored in the first device into the first device, so that the function of the reader / writer can be implemented without the aid of the second device.

[0278] It should be noted that, step S602 can refer to the description of step S303 in Embodiment 1, but the second device is replaced by the first device, and the content of the fourth information can refer to the description of the second information in step S303, which will not be described here again. In S602, the second identification is included in the fourth information, while in S303, the first identification is included in the second information in the third device, and the description of the second identification in S602 can refer to the description of the second identification in Embodiment 1. It can be understood that the focus here is that the identification carried in the fourth information needs to be associated with the first service or associated with the first device, and as for the naming of the identification as the first identification or the second identification, it is only for the convenience of distinguishing, and the present application does not limit the naming method of the identification.

[0279] Optionally, the third device can save all or part of the information in the fourth information.

[0280] S603. The third device sends fifth information to the fourth device;

[0281] It should be noted that S603 can refer to the description of step S304 in Embodiment 1, which will not be described here again.

[0282] S604. The fourth device saves the relevant information of the first service;

[0283] It should be noted that S604 can refer to the description of step S305 in Embodiment 1, which will not be described here again.

[0284] S605b. The third device sends fourth scheduling information to the first device;

[0285] Here, an example of the third device actively triggering the scheduling information is given, in addition to which, exemplarily, the fourth device can also trigger the scheduling information, for example, before S605b, step S605a can be performed, i.e., the fourth device can send third scheduling information to the third device, the third scheduling information including the fourth identification, the scheduling information being used to indicate resuming the first service, or waking up the first device, or the first device has been woken up, or the first device is in a wake-up state, or the first device will be woken up. Wherein, the fourth identification here can refer to the description of the fourth identification in Embodiment 1.

[0286] S606. The first device sends sixth information to the third device;

[0287] The third uplink data, the third identifier, information for identifying the first service, or information for indicating to continue the first service are included in the sixth information.

[0288] Optionally, the first device sends the third uplink data to the fourth device through the third device.

[0289] It should be noted that S606 can refer to the description of step S307 in embodiment 1, and will not be repeated here.

[0290] S607. The third device sends seventh information to the fourth device;

[0291] It should be noted that S607 can refer to the description of step S309 in embodiment 1, and will not be repeated here.

[0292] S608. The fourth device sends a downlink command (DL command) to the third device;

[0293] Optionally, when the time difference between the current time and step S605 reaches Tmax, and the first service is still not completed, the fourth device can send a downlink command to the third device, which indicates to terminate or release the first service, to prevent abnormal situations.

[0294] Optionally, the downlink command can be sent together with the second identifier.

[0295] S609. The third device sends an end indication to the fourth device.

[0296] It can be understood that the third device can send an end indication to the fourth device as a response to the DL command, which can be used by the third device to inform the fourth device that it has terminated or released the first service.

[0297] Embodiment 4:

[0298] Embodiment 4 is an example applied to application scenario 4 in the present application.

[0299] FIG. 7 is a flowchart of a communication method according to an embodiment of the present application. FIG. 7 illustrates the method using a first device, a second device, a DU, a CU, and a RIC as an example of an execution subject of the interaction, but the present application is not limited to the execution subject of the interaction. The first device in this embodiment can be the same as or different from the first device in the embodiment 1 or the embodiment 2, and the second device in this embodiment can be the same as or different from the second device in the embodiment 1 or the embodiment 2.

[0300] It should be noted that, in this embodiment, the CU and the DU are generally located in the same access network device, but the present application is not limited thereto, and the CU and the DU can also be located in different access network devices. The RAN intelligent controller (RIC) can be configured in the same access network device as the CU and the DU, or the RIC can be configured in the same access network device as the CU, and the DU can be located in a different access network device, or the RIC can be configured in the same access network device as the DU, and the CU can be located in a different access network device, or the RIC can be configured in a terminal or a server. The RIC includes a non-real time RAN intelligent controller (Non-RT RIC) and a near-real time RAN intelligent controller (Near-RT RIC). The Non-RT RIC is used to implement non-real time intelligent management of RAN functions, and the Non-RT RIC is located in a service management and orchestration framework (SMO) module. The Near-RT RIC is used to implement near-real time intelligent management of RAN, and implements near-real time control and optimization of modules and resources of the O-RAN through data collection and related operations on the E2 interface.

[0301] As shown in FIG. 7, the method includes the following steps.

[0302] S701. The RIC sends configuration information to the CU.

[0303] The configuration information can also be referred to as related first delay information. Optionally, the RIC can determine the AS ID by sending the configuration information, and then by the CU, the DU or the reader. The AS ID can be used to identify the type of the first device. The RIC can distinguish different types of terminal devices through the AS ID. At this time, the configuration information includes: the number of terminals or the inventory expected time. Or the RIC can directly determine the AS ID according to the related information such as the number of terminals or the inventory expected time. Therefore, the configuration information includes: the AS ID.

[0304] S702. The CU sends paging to the second device;

[0305] S703. The second device sends paging to the first device;

[0306] S704. The second device sends query to the first device;

[0307] S705. The second device sends queryrep to the first device;

[0308] S706. The first device sends RN to the second device;

[0309] S707. The second device sends ACK to the first device;

[0310] The steps S702 to S706 can refer to S300c to S300h in Embodiment 1. The ACK in step S706 can carry the second identifier. When the step S707 is executed, the first service access is successful, and the AS ID is saved.

[0311] S708. The first device sends uplink data to the second device;

[0312] S709. The second device sends queryrep to the first device;

[0313] After step S709, the first service in the first device can enter a suspended state or the first device sleeps. When the first service enters the suspended state or the first device sleeps, the process of notifying the network side of the suspended state or the sleep can refer to Embodiment 1, Embodiment 2 or Embodiment 3. This embodiment focuses on how to determine the identifier of the device and the T through the RIC when the method provided in the application is applied to the application scenario 4, that is, the O-RAN architecture.

[0314] S710. The RIC sends T to the CU;

[0315] Optionally, the RIC can determine the time length of charging or energizing the first device according to prior information such as historical information, so as to determine the time T. For example, the RIC determines that the average charging time length of the first device is 3 min according to historical information, and T is 3 min. Since the RIC has determined T at this time, and T is sent to the CU, the first device can report the time T or can not report the time T.

[0316] S711. The CU sends paging to the second device;

[0317] It should be noted that in the above steps, the CU indicates to resume the first service, or to wake up the first device, or that the first device has woken up, or that the first device is in a wake-up state, or that the first device will wake up, by sending paging.

[0318] S712. The second device sends paging to the first device;

[0319] It can be understood that the second device can indicate to resume the first service, or to wake up the first device, or that the first device has woken up, or that the first device is in a wake-up state, or that the first device will wake up, by forwarding the scheduling information to the first device.

[0320] S713. The first device sends uplink data to the second device;

[0321] It should be noted that step S713 can refer to the description of step S307 in Embodiment 1, and will not be described here.

[0322] S714. The second device sends downlink trigger information (DL trigger) to the first device.

[0323] Optionally, the DL trigger can also be replaced by queryrep, and the second device can indicate the success of uplink data transmission by sending downlink trigger information DL trigger or queryrep to the first device.

[0324] The communication method provided by the embodiments of the present application is described in detail above in combination with FIGS. 3-7. The communication device for executing the communication method provided by the embodiments of the present application is described in detail below in combination with FIGS. 8 and 9.

[0325] Exemplarily, FIG. 8 is a structural schematic diagram of a communication device provided by an embodiment of the present application. As shown in FIG. 8, the communication device 800 includes a processing module 801 and a transceiver module 802. For the convenience of description, FIG. 8 only shows the main components of the communication device.

[0326] In some embodiments, the communication apparatus 800 can be applicable in the communication system shown in Fig. 1, and perform the function of the second device in the communication method shown in Fig. 3, Fig. 4, Fig. 5 or Fig. 6.

[0327] The transceiver module 802 is configured to receive first information sent by a first device, the first information being used to indicate that a first service of the first device is in a suspended state or the first device is in sleep; and send second information, the second information being used to indicate that the first service is in the suspended state or the first device is in sleep, the second information comprising a first identifier, the first identifier being associated with the first device or the first service.

[0328] The specific implementation of the transceiver module 802 can refer to the related description in the method provided in Fig. 3, and will not be repeated here. Optionally, the transceiver module 802 can include a receiving module and a sending module (not shown in Fig. 8). The transceiver module is configured to implement the sending function and the receiving function of the communication apparatus 800.

[0329] Optionally, the communication apparatus 800 can further include a storage module (not shown in Fig. 8), which stores a program or an instruction. When the processing module 801 executes the program or the instruction, the communication apparatus 800 can perform the function of the terminal device in the communication method shown in any one of Fig. 3, Fig. 4, Fig. 5 or Fig. 6.

[0330] It should be understood that the processing module 801 involved in the communication apparatus 800 can be implemented by a processor or a processor-related circuit component, and can be a processor or a processing unit; the transceiver module 802 can be implemented by a transceiver or a transceiver-related circuit component, and can be a transceiver or a transceiving unit.

[0331] In addition, the communication apparatus 800 can be a network device or a terminal device, can be a chip (system) or other components or assemblies, and can also be an apparatus containing a network device or a terminal device, which is not limited in the present application. The above-mentioned chip (system) or other components or assemblies can be arranged in a terminal or a network device. The technical effects of the communication apparatus 800 can refer to the technical effects of the communication method shown in any one of Fig. 3, Fig. 4, Fig. 5 or Fig. 6, which will not be repeated here.

[0332] In some other embodiments, the communication apparatus 800 can be applicable in the communication system shown in Fig. 5, and perform the function of the third device in the communication method shown in Fig. 3.

[0333] The transceiver module 802 is configured to receive fourth information, the fourth information being used to indicate that the first service of the first device is in a suspended state, the fourth information comprising a third identifier, the third identifier being associated with the first device or the first service; and transmit fifth information, the fifth information being used to indicate that the first service of the first device is in the suspended state, the fifth information comprising a fourth identifier, the fourth identifier being related to the third identifier, and the fourth identifier being associated with the first device or the first service.

[0334] Optionally, the communication apparatus 800 further includes a storage module (not shown in FIG. 8) storing programs or instructions. When the processing module 801 executes the programs or instructions, the communication apparatus 800 can perform the functions of the network device in the communication method shown in FIG. 3.

[0335] It should be understood that the processing module 801 involved in the communication apparatus 800 can be implemented by a processor or a processor-related circuit component, and can be a processor or a processing unit; and the transceiver module 802 can be implemented by a transceiver or a transceiver-related circuit component, and can be a transceiver or a transceiving unit.

[0336] In addition, the communication apparatus 800 can be a network device, a chip (system) or other components or assemblies arranged in the network device, or a device containing the network device, and the embodiments of the present application do not limit the same. The technical effects of the communication apparatus 800 can be referred to the technical effects of the communication method shown in any one of FIG. 3, FIG. 4, FIG. 5 or FIG. 6, which will not be repeated here.

[0337] In some other embodiments, the communication apparatus 800 can be applied to the communication system shown in FIG. 1, and perform the functions of the fourth device in the communication method shown in FIG. 3, FIG. 4, FIG. 5 or FIG. 6.

[0338] The transceiver module 802 is configured to receive fifth information, the fifth information being used to indicate that the first service of the first device is in a suspended state, the fifth information comprising a fourth identifier, the fourth identifier being associated with the first device or the first service.

[0339] The processing module 801 is configured to save related information of the first service, wherein the related information comprises the fourth identifier.

[0340] Optionally, the communication apparatus 800 further includes a storage module (not shown in FIG. 8) storing programs or instructions. When the processing module 801 executes the programs or instructions, the communication apparatus 800 can perform the functions of the network device in the communication method shown in FIG. 3.

[0341] It should be understood that the processing module 801 involved in the communication device 800 can be implemented by a processor or a processor-related circuit component, and can be a processor or a processing unit; the transceiver module 802 can be implemented by a transceiver or a transceiver-related circuit component, and can be a transceiver or a transceiving unit.

[0342] Exemplarily, FIG. 9 is a structural schematic diagram of a communication device provided by an embodiment of the present application. The communication device can be a terminal device or a network device, or can be a chip (system) or other components or assemblies that can be arranged in the terminal device or the network device. As shown in FIG. 9, the communication device 900 can include a processor 901. Optionally, the communication device 900 can further include a memory 902 and / or a transceiver 903. The processor 901 is coupled with the memory 902 and the transceiver 903, for example, through a communication bus.

[0343] The various constituent components of the communication device 900 will be specifically introduced below in combination with FIG. 9.

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

[0345] Optionally, the processor 901 can perform various functions of the communication device 900 by running or executing software programs stored in the memory 902, and calling data stored in the memory 902.

[0346] In a specific implementation, as an embodiment, the processor 901 can include one or more CPUs, for example, CPU0 and CPU1 shown in FIG. 9.

[0347] In a specific implementation, as an example, the communication apparatus 900 can also include multiple processors, such as the processor 901 and the processor 904 shown in FIG. 9. Each of the processors can be a single-CPU or a multi-CPU. The processor herein can refer to one or more devices, circuits, and / or processing cores for processing data (for example, computer program instructions).

[0348] The memory 902 is configured to store a software program for implementing the solutions of the present application, and the processor 901 is configured to control the execution of the software program. The specific implementation can refer to the above method embodiments, and details are not described herein.

[0349] Optionally, the memory 902 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disk storage, an optical disk storage (including a compact disk, a laser disc, an optical disc, a digital versatile disc, a Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to this. The memory 902 can be integrated with the processor 901 or exist independently and be coupled to the processor 901 through an interface circuit (not shown in FIG. 9) of the communication apparatus 900, and the embodiments of the present application are not limited in this regard.

[0350] The transceiver 903 is configured to communicate with other communication apparatuses. For example, the communication apparatus 900 is a terminal device, and the transceiver 903 can be configured to communicate with a network device or another terminal device. For another example, the communication apparatus 900 is a network device, and the transceiver 903 can be configured to communicate with a terminal device or another network device.

[0351] Optionally, the transceiver 903 can include a receiver and a transmitter (not shown separately in FIG. 9). The receiver is configured to implement the receiving function, and the transmitter is configured to implement the transmitting function.

[0352] Optionally, the transceiver 903 can be integrated with the processor 901, or exist independently, and be coupled with the processor 901 through an interface circuit (not shown in FIG. 9) of the communication apparatus 900, and the embodiments of the present application do not make a limitation in this regard.

[0353] It should be noted that the structure of the communication apparatus 900 shown in FIG. 9 does not constitute a limitation on the communication apparatus, and an actual communication apparatus can include more or fewer components than those shown, or combine certain components, or have different arrangement of components.

[0354] In addition, the technical effects of the communication apparatus 900 can refer to the technical effects of the communication method described in the above method embodiments, which will not be repeated here.

[0355] It should be understood that the processor in the embodiments of the present application can be a CPU, and can also be other general-purpose processors, DSPs, ASICs, FPGAs or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor.

[0356] It should also be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. The non-volatile memory can be a ROM, a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an EEPROM or a flash memory. The volatile memory can be a RAM used as an external cache. By way of example and not limitation, many forms of RAM can be used, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM) and direct rambus RAM (DR RAM).

[0357] The above-described embodiments can be implemented in part or in whole through software implemented by a processor. The above-described embodiments can be implemented by a single processor or a combination of processors.

[0358] It should be understood that the term "and / or" in this document is merely used to describe associated objects, and can represent that three relationships are possible. For example, A and / or B can mean that there is only A, there is only B, or there is both A and B. In addition, the character " / " is generally used to represent an "or" relationship between the front and rear associated objects, but it can also represent an "and / or" relationship. The specific meaning can be understood according to the context.

[0359] In this application, "at least one" means one or more, and "multiple" means two or more. "At least one of the following" or similar expressions means any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can mean a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, and c can be single or multiple.

[0360] It should be understood that in various embodiments of the present application, the size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of the processes should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0361] Those skilled in the art can clearly understand that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be realized by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0362] Those skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working processes of the above-described system, device and unit can refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

[0363] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the above-described device embodiments are only schematic, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, device or unit, and can be electrical, mechanical or other forms.

[0364] The units described as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.

[0365] In addition, each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically independently, or two or more units can be integrated into one unit.

[0366] If the functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application essentially or the parts that contribute to the prior art or parts of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a ROM, a RAM, a magnetic disk or an optical disk, and various media that can store program codes.

[0367] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A communication method characterized by comprising: The method comprises: receiving first information sent by a first device, the first information being used for indicating that a first service of the first device is in a suspended state or the first device is in a sleep state; sending second information, the second information being used for indicating that the first service is in the suspended state or the first device is in the sleep state, the second information comprising a first identifier, the first identifier being associated with the first device or the first service.

2. The method of claim 1, wherein, The second information further comprises time information T, wherein the T is a time length of the suspended state or a sleep time length of the first device.

3. The method according to claim 1 or 2, characterized in that, The method further comprises: sending first scheduling information to the first device, the first scheduling information being used for indicating to resume the first service or wake up the first device, the first scheduling information comprising a second identifier, the second identifier being associated with the first device or the first service, the second identifier being related to the first identifier; receiving first uplink data sent by the first device, the first uplink data being related to the first service; sending third information, the third information comprising second uplink data associated with the second identifier, the first identifier, information used for indicating to resume the first service or information used for indicating to wake up the first device, wherein the second uplink data comprises the first uplink data.

4. The method of claim 3, wherein, Before the step of sending the first scheduling information to the first device, the method further comprises: receiving second scheduling information, the second scheduling information being used for indicating to resume the first service or wake up the first device, the second scheduling information comprising the first identifier.

5. The method according to any one of claims 1 to 4, characterized in that, The second scheduling information comprises downlink data, the downlink data being used for indicating the first device to perform a target operation, the target operation comprising reading, writing, locking, positioning, sensing or deactivation.

6. A communication method characterized by comprising: The method comprises: receiving fourth information, the fourth information being used for indicating that a first service of a first device is in a suspended state, the fourth information comprising a third identifier, the third identifier being associated with the first device or the first service; sending fifth information, the fifth information being used for indicating that the first service of the first device is in the suspended state, the fifth information comprising a fourth identifier, the fourth identifier being related to the third identifier, the fourth identifier being associated with the first device or the first service.

7. The method of claim 6, wherein, The fourth information further comprises information used for identifying the first service or T, wherein the T is a time length of the suspended state or a sleep period of the first device.

8. The method according to claim 6 or 7, characterized in that, The fifth information further comprises information used for identifying the first service or the T, wherein the T is a time length of the suspended state or a sleep period of the first device.

9. The method according to any one of claims 6 to 8, characterized in that, The method further comprises: receiving sixth information, the sixth information comprising third uplink data, the third identifier, information used for indicating to resume the first service or information used for indicating to wake up the first device; sending seventh information, the seventh information comprising: fourth uplink data, the fourth identifier, information for indicating resuming the first service or information for indicating waking up the first device, wherein the fourth uplink data comprises the third uplink data.

10. The method according to any one of claims 6 to 9, characterized in that, The method further comprises: receiving third scheduling information, the third scheduling information for indicating resuming the first service or waking up the first device, the third scheduling information comprising the fourth identifier; sending fourth scheduling information, the fourth scheduling information for indicating resuming the first service or waking up the first device, the fourth scheduling information comprising the third identifier.

11. The method of claim 10, wherein, The third scheduling information comprises downlink data, the downlink data for instructing the first device to perform a target operation, the target operation comprising: reading, writing, locking, positioning, sensing or deactivating.

12. A communication method characterized by comprising: Comprising: receiving fifth information, the fifth information for indicating that a first service of a first device is in a suspended state, the fifth information comprising: a fourth identifier, the fourth identifier being associated with the first device or the first service, storing related information of the first service, wherein the related information comprises: the fourth identifier.

13. The method of claim 12, wherein, The related information further comprises: a security parameter or data related to the first service cached before the suspended state starts.

14. The method according to claim 12 or 13, characterized in that, The related information is stored for a time period no less than time information T, wherein the T is a time period of the suspended state or a sleep time period of the first device.

15. The method according to any one of claims 12 to 14, characterized in that, The fifth information further comprises: information for identifying the first service or the time information T, wherein the T is a time period of the suspended state or a sleep time period of the first device.

16. The method according to any one of claims 12 to 15, characterized in that, The method further comprises: receiving seventh information, the seventh information comprising: fourth uplink data, the fourth identifier for information indicating resuming the first service or information for indicating waking up the first device.

17. The method according to any one of claims 12 to 15, characterized in that, Before the receiving fourth information, the method further comprises: sending third scheduling information, the third scheduling information for indicating resuming the first service, the fourth scheduling information comprising the fourth identifier.

18. The method of claim 17, wherein, The third scheduling information comprises downlink data, the downlink data for instructing the first device to perform a target operation, the target operation comprising: reading, writing, locking, positioning, sensing or deactivating.

19. A communications device, characterized by Comprising units for performing the method according to any one of claims 1-18.

20. A communications device, characterized by Comprising a processor for executing a computer program or instructions, so that the device performs the method according to any one of claims 1-18.

21. A computer-readable storage medium, characterized in that, The computer readable storage medium stores a computer program or instructions, when the computer program or instructions are executed, the method according to any one of claims 1-18 is implemented.

22. A computer program product, characterised in that, The computer program product comprises: computer program code, when the computer program code is run, the method according to any one of claims 1-18 is implemented.

Images