Communication method and apparatus

Abstract

The present application relates to the field of communications, and provides a communication method and apparatus, so as to achieve rapid service recovery, reduce service delay, and ensure service continuity. The method is applied to a first apparatus or a chip in the first apparatus. The method comprises: determining a first identifier, and receiving a second identifier of a second apparatus, so as to recover a first service. The first identifier is associated with the first apparatus and / or the suspended first service, the first service is a service associated with the first apparatus and the second apparatus, and the second identifier is associated with the first identifier.

Description

Communication methods and devices

[0001] This application claims priority to Chinese Patent Application No. 202410949424.6, filed on July 15, 2024, entitled "Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

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

[0003] With the development of communication technology, the 3rd Generation Partnership Project (3GPP) defined A-IoT. It can be understood as an extension of passive radio frequency identification (RFID) within 3GPP. A-IoT is based on cellular network communication infrastructure and consists of readers (such as base stations) and passive / semi-passive / active A-IoT terminals (A-IoT terminals are terminals within the cellular network, understood as extremely low-power, extremely low-complexity IoT terminals).

[0004] A-IoT terminals may lose power due to insufficient battery while executing business processes. After the A-IoT terminal is fully charged, it needs to re-execute the business process, resulting in significant business latency and affecting business continuity. Summary of the Invention

[0005] This application provides a communication method and apparatus to enable rapid service recovery, reduce service latency, and ensure service continuity.

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

[0007] In a first aspect, a communication method is provided, applied to a first device or a chip in the first device, the method comprising: determining a first identifier and receiving a second identifier of a second device to resume a first service. The first identifier is associated with the first device and / or a suspended first service, the first service being a service associated with both the first device and the second device, and the second identifier is associated with the first identifier.

[0008] Therefore, the first device can determine a first identifier, such as when the first service is suspended. This first identifier is associated with the suspended first service and / or the first device. Subsequently, the first device can receive a second identifier from the second device, which can be associated with the first identifier determined in advance by the first device. This allows the first device to directly resume the suspended first service, i.e., continue executing the first service process without re-establishing the first service. This not only ensures service continuity but also reduces service latency.

[0009] In one possible design, the conditions for resuming the first service include: the second identifier being associated with the first identifier, and / or the first device ending its sleep state. For example, the second identifier being associated with the first identifier means that the first identifier and the second identifier are the same. That is, the first device may suspend the first service due to insufficient power, enter sleep mode and charge, and then end sleep mode after charging is complete. Based on this, setting the above conditions can ensure that when the first service is resumed, the first device has sufficient power to continue to complete the first service.

[0010] In one possible design, resuming the first service includes: transmitting data of the first service to the second device; and / or: entering a first state, which is a state that allows the transmission of data of the first service, that is, continuing the process of the first service through data transmission, such as transmitting data that has not yet been completed, to ensure the continuity of the service.

[0011] Optionally, transmitting data of the first service with the second device includes: transmitting data of the first service with the second device according to the instruction of the first service to avoid transmission errors.

[0012] Optionally, the method may further include: receiving an indication of a first service from the second device. The first device may receive the indication of the first service before entering a sleep state. Based on this, the first device may also save the indication of the first service so that the second device does not need to retransmit the indication of the first service subsequently, thereby saving overhead. Alternatively, the first device may also receive the indication of the first service when the first device exits a sleep state; the specific method is not limited.

[0013] In one possible design, determining the first identifier includes: receiving the first identifier from the second device, such as before sleep mode or before the first service is suspended, so that the first identifier can be used for association matching, such as determining whether it is associated with the second identifier.

[0014] Optionally, receiving a first identifier from the second device includes: receiving a first message from the second device; the first message is at least one of the following: a message indicating permission to access, a message for paging, or a message for responding to a service. The first message contains a first identifier, which means that the message transmission first identifier in the existing process (such as paging, access, or data transmission process) can be reused, which is simple to implement, or a newly defined message transmission first identifier can be used to decouple it from the existing message, making information transmission flexible.

[0015] In one possible design, the method may further include: saving the first identifier to avoid the inability to complete subsequent association matching due to the loss of the first identifier.

[0016] In one possible design approach, the method could also include suspending the first business process.

[0017] Optionally, suspending the first service includes: entering a second state, where the first service is suspended. If the second state is not entered, the first service may not be able to be suspended. In other words, setting a second state can prevent accidental operation, such as suspending the first service when it is in the first state or when it is not necessary to suspend the first service.

[0018] In one possible design, the conditions for suspending the first service include: the first device going into sleep mode, to avoid the loss of the first information due to the first service not being suspended while the first device is in sleep mode.

[0019] In one possible design, the method may further include: sending an indication message to a second device, the indication message being used to indicate that the first service is suspended, so as to trigger the second device to subsequently resume the first service by sending a second identifier.

[0020] Optionally, the indication information is also used to instruct the first device to go into sleep mode, so as to trigger the second device to send a second identifier when the first device ends its sleep mode.

[0021] Optionally, sending indication information to the second device includes: sending a second message to the second device, the second message being a message for the first device to access or a message for business data transmission, the second message including indication information, that is, the message transmission indication information in the existing process (such as access search or data transmission process, etc.) can be reused, which is simple to implement, or the message transmission indication information can be newly defined to decouple it from the existing message, making information transmission flexible.

[0022] In one possible design, the method may further include: transmitting time information to the second device, the time information being used to indicate the sleep time of the first device, i.e., aligning the sleep time so that the first device can end its sleep on time, and the second device can send a second identifier when the first device ends its sleep.

[0023] In one possible design, the first device is an environmental IoT device.

[0024] In a second aspect, a communication method is provided, applied to a second device or a chip in the second device, the method comprising: receiving indication information from a first device, the indication information being used to indicate suspending a first service, the first service being a service associated with both the first device and the second device; sending a second identifier to the first device, the second identifier being associated with the first device and / or the first service, the first service being configured to resume if the second identifier is associated with a first identifier stored in the first device.

[0025] In one possible design, sending a second identifier to the first device includes: sending a second identifier to the first device in response to the first device ending its sleep state.

[0026] In one possible design, the method may further include: determining, based on time information, that the first device ends its sleep state, wherein the time information is used to indicate the duration of the first device's sleep state.

[0027] Optionally, the method may further include: transmitting time information to the first device, and / or receiving time information from the third device. That is, the duration of the first device's sleep can be determined not only by the first device, but also by other devices, such as the third device. The specific implementation can be flexibly selected without limitation.

[0028] In one possible design, the method may further include: sending a first identifier to the first device.

[0029] Optionally, sending a first identifier to the first device includes: sending the first identifier to the first device according to the instruction information, that is, sending the first identifier when the first service is suspended / the first device is in sleep mode, so as to achieve on-demand sending and avoid communication redundancy.

[0030] Optionally, the first identifier is included in the first message, which is at least one of the following: a message indicating permission to access, a paging message, or a message responding to a service.

[0031] In one possible design, the instruction information is also used to instruct the first device to go into sleep mode.

[0032] One possible design scheme for receiving instruction information from a first device includes: receiving a second message from the first device, the second message being a message for the first device to access the network or a message for business data transmission, the second message including instruction information.

[0033] In one possible design, the method may further include: transmitting data of the first service to the first device when the first service is restored.

[0034] In one possible design, the method may further include: sending an indication of a first service to a first device, the indication of the first service being used to indicate the data transmission of the first service.

[0035] It is understandable that the technical effects of the method described in the second aspect can also refer to the relevant introduction of the method described in the first aspect above, and will not be repeated here.

[0036] Thirdly, a communication method is provided, applied to a third device or a chip in the third device, the method comprising: determining time information, the time information being used to indicate the sleep time of a first device; and sending the time information to a second device, the second device being associated with the first device having the same service.

[0037] In one possible design, determining the time information includes: determining the time information based on the sleep time of one or more devices, so as to ensure that the determined sleep duration is more consistent with the actual situation.

[0038] It is understandable that the technical effects of the method described in the third aspect can be referred to the relevant introduction of the method described in the first aspect above, and will not be repeated here.

[0039] Fourthly, a communication apparatus is provided. The communication apparatus includes a module for performing the communication method described in any implementation of the first or third aspect.

[0040] In this application, the communication device may be a terminal device or a network device, or a chip (system) or other component or assembly, or a device containing the terminal device or network device. The aforementioned chip (system) or other component or assembly may be disposed within the terminal device or network device.

[0041] It should be understood that the communication device includes modules, units, or means corresponding to the communication method described in either the first or third aspect above. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units for performing the functions involved in the aforementioned communication method.

[0042] Fifthly, a communication device is provided. The communication device includes a processor configured to execute the communication method described in any possible implementation of the first or third aspect.

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

[0044] In one possible design, the communication device may further include a memory. This memory may be integrated with the processor or disposed separately. The memory may be used to store computer programs and / or data relating to the communication method described in either the first or third aspect.

[0045] In this application, the communication device may be a terminal device or a network device, or a chip (system) or other component or assembly, or a device containing the terminal device or network device. The aforementioned chip (system) or other component or assembly may be disposed within the terminal device or network device.

[0046] A sixth aspect provides a communication device. The communication device includes a processor coupled to a memory, the processor executing a computer program stored in the memory, such that the communication device performs the communication method described in any possible implementation of the first or third aspect.

[0047] In one possible design, the communication device may also include a transceiver. This transceiver can be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device and other communication devices.

[0048] In this application, the communication device may be a terminal device or a network device, or a chip (system) or other component or assembly, or a device containing the terminal device or network device. The aforementioned chip (system) or other component or assembly may be disposed within the terminal device or network device.

[0049] A seventh aspect provides a communication device, comprising: a processor and a memory; the memory being used to store a computer program, which, when executed by the processor, causes the communication device to perform the communication method described in any one of the first or third aspects.

[0050] In one possible design, the communication device may also include a transceiver. This transceiver can be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device and other communication devices.

[0051] In this application, the communication device may be a terminal device or a network device, or a chip (system) or other component or assembly, or a device containing the terminal device or network device. The aforementioned chip (system) or other component or assembly may be disposed within the terminal device or network device.

[0052] Eighthly, a communication device is provided, comprising: a processor; the processor being coupled to a memory and, after reading a computer program from the memory, executing a communication method as described in any implementation of the first or third aspect according to the computer program.

[0053] In one possible design, the communication device may also include a transceiver. This transceiver can be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device and other communication devices.

[0054] In this application, the communication device may be a terminal device or a network device, or a chip (system) or other component or assembly, or a device containing the terminal device or network device. The aforementioned chip (system) or other component or assembly may be disposed within the terminal device or network device.

[0055] A ninth aspect provides a processor. The processor is configured to execute the communication method described in any possible implementation of the first or third aspect.

[0056] In a tenth aspect, a chip is provided, wherein the chip may include a processor for executing the communication method described in any possible implementation of the first or third aspect.

[0057] Optionally, the chip also includes a memory coupled to the processor, the memory storing a program for executing the communication method described in any of the possible implementations of the first or third aspect.

[0058] Eleventhly, a communication system is provided. The communication system includes one or more terminal devices for performing any possible implementation of the first or third aspect, and one or more network devices for performing any possible implementation of the first or third aspect.

[0059] In a twelfth aspect, a computer-readable storage medium is provided, comprising: a computer program or instructions; when the computer program or instructions are executed on a computer, causing the computer to perform the communication method described in any possible implementation of the first or third aspect.

[0060] In a thirteenth aspect, a computer program product is provided, comprising a computer program or instructions that, when executed on a computer, cause the computer to perform the communication method described in any possible implementation of the first or third aspect.

[0061] Furthermore, the technical effects of the communication devices described in aspects four through thirteen above can be referred to the technical effects of the communication methods described in aspects one or three above, and will not be repeated here. Attached Figure Description

[0062] Figure 1 is a schematic diagram of the RFID process;

[0063] Figure 2 is a schematic diagram of the A-IoT process;

[0064] Figure 3 is a schematic diagram of the architecture of the communication system provided in an embodiment of this application;

[0065] Figure 4 is a schematic diagram of the architecture of the communication system provided in an embodiment of this application;

[0066] Figure 5 is a flowchart illustrating the communication method provided in an embodiment of this application;

[0067] Figure 6 is a schematic flowchart of the communication method provided in an embodiment of this application;

[0068] Figure 7 is a flowchart illustrating the communication method provided in an embodiment of this application.

[0069] Figure 8 is a flowchart illustrating the communication method provided in an embodiment of this application.

[0070] Figure 9 is a schematic diagram of the communication device provided in an embodiment of this application;

[0071] Figure 10 is a second schematic diagram of the structure of the communication device provided in the embodiment of this application. Detailed Implementation

[0072] The technical solutions of this application embodiment can be applied to various communication systems, such as Wi-Fi wireless network systems, vehicle-to-everything (V2X) communication systems, device-to-device (D2D) communication systems, vehicle-to-everything (V2X) communication systems, fourth-generation (4G) mobile communication systems, such as long-term evolution (LTE) systems, worldwide interoperability for microwave access (WiMAX) communication systems, fifth-generation (5G) mobile communication systems, such as new radio (NR) systems, and future communication systems.

[0073] The technical terms and related technical solutions in this application will be described below with reference to the accompanying drawings.

[0074] 1. Passive Radio Frequency Identification (RFID):

[0075] An RFID system includes an interrogator and a tag.

[0076] The reader reads information from the tag device or writes information that the tag device needs to store into the tag device. The reader and tag device communicate without contact. The tag device has simple functionality, requiring excitation from the reader to send information; that is, the tag device converts the wireless signal emitted by the reader into energy to power itself. Tags support power consumption in the microwatt or hundreds of microwatts range, limiting their ability to support complex designs. If RFID is applied to mobile communication systems, such as 5G systems, then the base station can act as a reader, fulfilling its functions.

[0077] The primary application of RFID is identification, but it can also be used for data reading and writing, such as inventory / access.

[0078] As shown in Figure 1, the inventory / access process is as follows:

[0079] S101, the reader sends a select message:

[0080] The selection message is used to select a set of tags. The selection message can carry the inventory session, action, mask, etc.

[0081] When a tag device receives a selection message, the matching tag device sets the selection message and the corresponding flag bit. For example, if the inventory session indicator is session S0 and the behavior indicator is 0, and the mask matches, the tag device sets the flag bit of session S0 to A, which is the initial flag bit. Afterward, the EPC success flag bit will be flipped to B. Thus, A represents tag devices that have not yet transmitted EPC, and B represents tag devices that have successfully transmitted.

[0082] 1) The session and the subsequent flag are bound together. Each flag corresponds to a session. The disk storage session will specify which session's flag is set.

[0083] 2) The behavior specifies how to set the flag, such as behavior indicating 1 or 0. After the tag device receives the flag, if the mask matches, it will set the flag corresponding to the session, such as A (action=1) or B (action=0).

[0084] 3) The mask is used to filter which tag devices are selected. For example, if a tag device stores a complete 96-bit identifier, the mask can indicate that the first 16 bits of the tag are 111...111 and the tag device is selected. If the mask matches, the tag device can further set the bit according to the session's instructions and then listen for subsequent query messages.

[0085] S102, the reader sends a query message.

[0086] Query messages can carry Q-values, session information, or flags.

[0087] Suppose that the session carried by the query message is S0 and the flag bit is A. The session and flag bit of the tag are matched with it, so a random number between 0 and 2^Q-1 is randomly generated according to Q as the initial value of the counter.

[0088] S103, the reader sends a duplicate query message (queryRep).

[0089] Repeated query messages do not need to carry content, have no Q value or session, and can be sent multiple times.

[0090] If no tag device sends a response, such as RN16, the reader continues to send duplicate query messages. If a tag device receives a duplicate query message, it decrements the counter value by 1, e.g., Counter = Counter - 1.

[0091] S104, the tag device sends RN16.

[0092] If the tag device generates a count value of 0, the tag will respond with RN16; otherwise, it will not respond. RN16 is a 16-bit random number (or it could be 16 bits or 8 bits) used for contention resolution. For example, after the tag receives (potentially multiple) duplicate query messages, its count value decreases to 0, and the tag will respond with RN16; otherwise, it will not respond. For example, each duplicate query message corresponds to the start or end of an access time slot. Each duplicate query message received by the tag device signifies the end of the previous time slot and the start of the next time slot. The tag device can randomly select an access time slot to initiate access, send uplink data (EPC), or receive downlink data in the corresponding access time slot.

[0093] S105, the reader returns an acknowledgment message (ACK).

[0094] When the reader receives the RN16 sent by the tag device, if there is no collision (e.g., only one tag sent the RN16), it sends back an ACK, which includes the received RN16 and indicates that the contention was successfully resolved.

[0095] S106, Tag device sends device identification code (electronic product code, EPC).

[0096] If the tag device receives an ACK and the RN16 matches, it will send an EPC response; otherwise, it will not send a response.

[0097] S107, the reader returns a duplicate query message.

[0098] If the tag device sends an EPC and receives a duplicate query message, it indicates that the transmission was successful and flips the flag bit to B. For example, the flag bit can be used to prevent tags that have been stored from being stored again. If the subsequent query message carries the flag bit A, the tag device will not respond if the flag bit is flipped to B.

[0099] 2. Ambient IoT (A-IoT):

[0100] With the development of communication technology, the 3rd Generation Partnership Project (3GPP) defined A-IoT. It can be understood as an extension of RFID within 3GPP. Although it shares some principles with RFID, such as similar inventory management processes, 3GPP introduces more value-added scenarios.

[0101] A-IoT is based on cellular network communication infrastructure and consists of readers (such as base stations) and passive / semi-passive / active A-IoT terminals (A-IoT terminals are terminals in the cellular network, which can be understood as IoT terminals with extremely low power consumption and extremely low complexity).

[0102] For example, A-IoT includes network devices and Type I terminal devices, or in other words, an A-IoT-based communication system includes network devices and Type I terminal devices. The Type I terminal devices can be devices with the functionality of A-IoT terminal devices. In this case, both the reader / writer and the A-IoT terminal device can be implemented based on cellular network infrastructure. In other words, both the reader / writer and the A-IoT terminal device can be devices within a cellular network. For example, the functionality of the reader / writer can be implemented by network devices, such as base stations. The A-IoT terminal device can be implemented by terminals within a cellular network, such as ultra-low power, ultra-low complexity IoT terminals, i.e., Type I terminals. The network device and the Type I terminal can perform contactless data communication, thereby reading information from the Type I terminal and / or writing information that needs to be stored into the Type I terminal.

[0103] A-IoT technology can be used to implement one or more of the following functions: inventory management, location tracking, sensing, and commands. Command functions can be understood as implementing write or lock processes. In terms of application scope, A-IoT technology can be applied to scenarios such as logistics, warehousing, industrial manufacturing, identity recognition, or environmental monitoring.

[0104] Inventory management involves using a reader (which can be a base station / terminal) to access A-IoT terminals (A-IoT terminal devices) within the coverage area. Once successfully connected, the device needs to send its unique identifier (which the network can recognize, such as EPC in RFID) to the reader.

[0105] Positioning is the process of using location signals to pinpoint the location of an A-IoT terminal.

[0106] Sensing involves A-IoT terminals reporting sensor data to the base station, such as temperature data.

[0107] Commands can be operation instructions, such as write or lock. Write process: The base station sends downlink commands and data, instructing the A-IoT terminal to write the data into its own memory. Lock process: The base station sends downlink commands, instructing the A-IoT terminal to lock a specified address in the memory area; the contents of that memory area cannot be modified or read.

[0108] A-IoT terminals can be divided into three categories: Device A, Device B, and Device C. Device A or Device 1a can be understood as a passive A-IoT terminal. Device B or Device 1b can be understood as a semi-passive A-IoT terminal. Device C or Device 1c can be understood as an active A-IoT terminal.

[0109] Taking device A as an example (device B may also have similar issues), its power consumption is approximately in the 1 microwatt (uW) range. On the one hand, the capacitor's charge is maintained for a short time, such as less than 1 second; on the other hand, due to low sensitivity, it cannot distinguish between charging energy and effective signal energy. Therefore, it cannot transmit or receive signals during RF charging, and the charging time may reach several seconds or even tens of seconds. The charging-operating mode of this type of device is as follows: charge until the capacitor is fully charged, then begin transmitting and receiving messages. Furthermore, for AIoT, power consumption and cost are low, especially for device 1 (1uW). The device's storage capacity is also relatively low; additional storage of information would incur additional design costs / power consumption, therefore, the storage information needs to be strictly considered. The information temporarily stored in the registers will be lost after the power is depleted.

[0110] Therefore, when an A-IoT terminal executes the process shown in Figure 1, the problem shown in Figure 2 may occur.

[0111] As shown in Figure 2:

[0112] S201, the reader sends a selection message:

[0113] S202, the reader sends a query message.

[0114] S203, the reader sends a repeat query message (may be sent multiple times).

[0115] S204, the A-IoT terminal sends RN16.

[0116] At this point, the A-IoT terminal ran out of power after sending RN16 and began charging.

[0117] After charging is complete, it needs to be reconnected, as described in S205-S208 below.

[0118] S205, the reader sends a selection message:

[0119] S206, the reader sends a query message.

[0120] S207, the reader sends a repeat query message (may be sent multiple times).

[0121] S208, the A-IoT terminal sends RN16.

[0122] S209, the reader returns ACK.

[0123] S210, the tag device sends EPC.

[0124] S211, the reader returns a duplicate query message.

[0125] It can be seen that when an A-IoT terminal loses power and is powered on again, it needs to re-execute the aforementioned incomplete process, resulting in significant business latency and affecting business continuity.

[0126] To address the aforementioned technical problems, this application proposes the following technical solutions. The technical solutions in this application will now be described in conjunction with the accompanying drawings.

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

[0128] Furthermore, in the embodiments of this application, words such as "exemplarily" and "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as an "example" in this application should not be construed as being better or more advantageous than other embodiments or designs. Rather, the use of the word "example" is intended to present the concept in a specific manner.

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

[0130] The information indicated by a given piece of information is called the information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated, such as, but not limited to, directly indicating the information to be indicated, such as the information to be indicated itself or its index. It can also be indirectly indicated by indicating other information, where there is a relationship between the other information and the information to be indicated. It can also indicate only a part of the information to be indicated, while the other parts are known or pre-agreed upon. For example, the indication of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing the indication overhead to some extent. At the same time, common parts of various pieces of information can be identified and indicated uniformly to reduce the indication overhead caused by individually indicating the same information.

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

[0132] The information to be instructed can be sent as a whole or divided into multiple sub-information messages, and the sending period and / or timing of these sub-information messages can be the same or different. This application does not limit the specific sending method. The sending period and / or timing of these sub-information messages can be predefined, for example, according to a protocol, or configured by the transmitting device by sending configuration information to the receiving device. This configuration information can include, for example, but not limited to, one or a combination of at least two of radio resource control (RRC) signaling, medium access control (MAC) layer signaling, and physical layer signaling. MAC layer signaling includes, for example, a MAC control element (CE); physical (PHY) layer signaling includes, for example, downlink control information (DCI).

[0133] Second, in the embodiments shown below, the first, second, and various numerical designations are merely distinctions for descriptive convenience and are not intended to limit the scope of the embodiments of this application. For example, to distinguish different indication information.

[0134] Third, "pre-defined," "pre-configured," or "pre-specified" can be achieved by pre-saving corresponding codes, tables, or other means of indicating relevant information in the device (e.g., including terminal devices and network devices), or by pre-defining them in a protocol. This application does not limit the specific implementation method. "Saving" can refer to saving in one or more memories. These memories can be separate installations or integrated into the encoder, decoder, processor, or communication device. Alternatively, some memories can be separately installed, while others are integrated into the decoder, processor, or communication device. The type of memory can be any form of storage medium, and this application does not limit this.

[0135] Fourth, the “protocol” involved in the embodiments of this application may refer to standard protocols in the field of communication, such as 3GPP’s LTE protocols (such as technical specification (TS) 36, i.e., the TS36 series of technical specifications), NR protocols (such as the TS38 series of technical specifications), and related protocols applied to future communication systems. This application does not limit this.

[0136] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0137] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0138] To facilitate understanding of the embodiments of this application, the communication system applicable to the embodiments of this application will be described in detail first using the communication system shown in FIG3 as an example. Exemplarily, FIG3 is a schematic diagram of the architecture of a communication system to which the method provided in the embodiments of this application is applicable.

[0139] Figure 3 is a schematic diagram of the communication system architecture, which mainly includes a first device and a second device. The first device can be a terminal or a network device, and similarly, the second device can also be a terminal or a network device.

[0140] A terminal can be a device or module that accesses the aforementioned communication system and has corresponding communication functions. A terminal can also be called a terminal device, user equipment (UE), mobile station, mobile terminal, etc. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), the Internet of Things (IoT), such as ambient internet of networks (A-IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. A terminal can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, wearable device, vehicle, drone, helicopter, airplane, ship, robot, robotic arm, smart home device, transportation vehicle with wireless communication capabilities, communication module, etc. The embodiments of this application do not limit the device form of the terminal. A terminal typically contains a communication module, circuit, or chip that performs the corresponding communication functions. The terminal can also be configured with program instructions for performing corresponding communication functions.

[0141] Network equipment can be devices that provide access services, such as radio access network (RAN) nodes, or network equipment with core network logical functions. RAN nodes can be 3GPP-related cellular systems, such as 4G, 5G mobile communication systems, or future-oriented evolution systems. RAN nodes can also be open RAN (O-RAN or ORAN), cloud radio access network (CRAN), or wireless fidelity (WiFi) systems. RAN nodes can also be communication systems that integrate two or more of the above systems. RAN nodes are sometimes also referred to as access network equipment, RAN entities, or access nodes, forming part of the communication system to help terminals achieve wireless access. Multiple RAN nodes in a communication system can be of the same type or different types.

[0142] In one possible scenario, the RAN node can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a base station in a future mobile communication system, or an access node in a WiFi system. The RAN node can be a macro base station, a micro base station or indoor station, a relay node or donor node, or a radio controller in a CRAN scenario. Optionally, the RAN node can also be a server, a wearable device, a vehicle, or in-vehicle equipment. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). All or part of the functions of the RAN node in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The RAN node can also be equipped with communication modules, circuits, or chips that perform corresponding communication functions. The RAN node can also be configured with program instructions for performing corresponding communication functions and corresponding program instructions. The RAN node in this application can also be a logical node, logical module, or software that can implement all or part of the functions of the RAN node.

[0143] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, with each RAN node performing some of the base station's functions. For example, RAN nodes can be central units (CUs), distributed units (DUs), or radio units (RUs), etc.

[0144] In some examples, the CU is a logical node carrying the Radio Resource Control (RRC) layer, Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, and other control functions of the access network equipment. The CU connects to network nodes such as the core network through interfaces, which can be interfaces like the E2 interface. Optionally, the CU may have some core network functions. The CU (e.g., the PDCP layer and higher layers) connects to the DU (e.g., the RLC layer and lower layers) through interfaces, which can be interfaces like the F1 interface. In some examples, these interfaces (e.g., the F1 interface) can provide control plane (C-plane) and user plane (U-plane) functions (e.g., interface management, system information management, UE context management, RRC message transmission, etc.). F1AP is the application protocol for the F1 interface, defining the F1 signaling procedures in some examples. The F1 interface supports control plane F1-C and user plane F1-U.

[0145] In some examples, the CU can be split into CU-CP (control unit-control plane) and CU-UP (control unit-user plane). CU-CP is a logical node carrying the RRC layer and PDCP-C (control plane part of PDCP) layer, used to implement the CU's control plane functions. CU-CP can interact with network elements in the core network used to implement control plane functions. These network elements in the core network can be access and mobility function (AMF) network elements, such as the access and mobility management function (AMF) in a 5G system. The AMF network element is responsible for mobility management in the mobile network, such as terminal device location updates, terminal device registration with the network, and terminal device handover. CU-UP is a logical node carrying the SDAP layer and PDCP-U (user plane part of PDCP) layer, used to implement the CU's user plane functions. CU-UP can interact with network elements in the core network used to implement user plane functions. These network elements in the core network, such as the user plane function (UPF) in a 5G system, are responsible for data forwarding and receiving in terminal devices. The above CU and DU configurations are merely examples; the functions of the CU and DU can be configured as needed. For instance, the CU or DU can be configured to have more protocol layer functions, or only some protocol layer processing functions. For example, some RLC layer functions and protocol layer functions above the RLC layer can be placed in the CU, while the remaining RLC layer functions and protocol layer functions below the RLC layer can be placed in the DU. Furthermore, the functions of the CU or DU can be divided according to service type or other system requirements, such as by latency. Functions that require low latency can be placed in the DU, while functions that do not require low latency can be placed in the CU.

[0146] In some examples, a DU is a logical node that carries the radio link control (RLC) layer, medium access control (MAC) layer, higher physical layer (PHY) layer, and other functions. In some examples, a DU can control at least one RU. The DU connects to the RU through interfaces, which can be fronthaul interfaces. In some examples, the higher physical layer includes parts of the PHY layer processing, such as forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation.

[0147] In some examples, the RU (Remote Utility Unit) may be included in radio frequency (RF) equipment or units, such as in a remote radio unit (RRU), active antenna unit (AAU), or remote radio head (RRH). The RU is a logical node carrying both lower physical layer (PHY) and radio frequency (RF) processing. In some examples, the RU may be a 3GPP transmission reception point (TRP), a remote radio head (RRH), or other similar functionalities. In some examples, the Low-PHY includes PHY processing components such as Fast Fourier Transform (FFT), Inverse Fast Fourier Transform (IFFT), digital beamforming, and filtering. The RU communicates with one or more UEs via a radio link.

[0148] The DU and RU can be co-located or not. The DU and RU exchange control plane and user plane information via a lower-layer split-control, user, and synchronization (LLS-CUS) interface through a fronthaul link. LLS-CUS may include LLS-C and LLS-U interfaces, respectively providing the control plane (C-plane) and user plane (U-plane). In some examples, the control plane (C-plane) refers to real-time control between the DU and RU. The DU and RU exchange management information via an LLS-M interface on the fronthaul link; the management plane (M-plane) refers to non-real-time management operations between the DU and RU.

[0149] DU and RU can cooperate to implement the functions of the PHY layer. A DU can be connected to one or more RUs. The functions of DU and RU can be configured in various ways depending on the design. For example, a DU can be configured to implement baseband functions, and an RU can be configured to implement mid-RF functions. Another example is that a DU can be configured to implement higher-level functions in the PHY layer, and an RU can be configured to implement lower-level functions in the PHY layer, or to implement both lower-level and RF functions. Higher-level functions in the physical layer can include a portion of the physical layer's functions that are closer to the MAC layer, while lower-level functions in the physical layer can include another portion of the physical layer's functions that are closer to the mid-RF side.

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

[0151] In the ORAN system, RAN nodes communicate with the core network (CN) via backhaul links and with terminals via air interfaces. The ORAN system also includes RAN intelligent controllers (RICs), which can be further divided into non-real-time (Non-RT) RICs and near-real-time (Near-RT) RICs. Non-RT RICs are used for non-real-time intelligent management of RAN functions and are located within the Service Management and Orchestration Framework (SMO) module. Near-RT RICs are used for near-real-time intelligent management of the RAN, achieving near-real-time control and optimization of ORAN modules and resources through data collection and related operations on the E2 interface.

[0152] In some examples, the communication system of this application embodiment can be applied to A-IoT scenarios. As shown in Figure 4(a), the A-IoT terminal and the network device communicate directly and bidirectionally. The communication between the network device and the A-IoT terminal includes environmental IoT data and / or signaling, such as the network device sending downlink data / signaling to the A-IoT terminal and the network device receiving uplink data / signaling from the A-IoT terminal. As shown in Figure 4(b), the A-IoT terminal and the network device communicate bidirectionally through an intermediate node. The intermediate node can be a repeater, an integrated access and backhaul (IAB) node, a UE, or other devices capable of realizing environmental IoT, used to transmit environmental IoT data and / or signaling between the A-IoT terminal and the network device. As shown in Figure 4(c), the A-IoT terminal sends data / signaling to the network device and receives data / signaling from an auxiliary node; or the A-IoT terminal receives data / signaling from the network device and sends data / signaling to the auxiliary node. The auxiliary node can be a repeater, an IAB, a UE, or other devices capable of realizing environmental IoT. As shown in Figure 4(d), the A-IoT terminal communicates bidirectionally with the terminal device, such as exchanging environmental IoT data and / or signaling.

[0153] Based on this, the first device can be an environmental IoT device as shown in Figure 4, such as an A-IoT terminal, specifically a passive A-IoT terminal, a semi-passive A-IoT terminal, or an active A-IoT terminal. The second device can include a combination of one or more of the network devices, intermediate nodes, auxiliary nodes, or terminal devices shown in Figure 4, such as network devices, intermediate nodes, network devices + intermediate nodes, network devices + auxiliary nodes, or terminal devices. The second device is also a part of the network devices, such as CU, DU, RU, or O-CU, O-DU, and O-RU in O-RAN. The second device supports environmental IoT functions; the first device and the second device can interact with environmental IoT data and / or signaling to realize corresponding environmental IoT services, such as inventory, positioning, sensing, and command.

[0154] For example, the first device can determine a first identifier, such as when a first service is suspended. This first identifier is associated with the suspended first service and / or the first device. Then, the first device can receive a second identifier from a second device, which can be associated with the first identifier determined in advance by the first device. This allows the first device to directly resume the suspended first service, i.e., continue executing the first service process without re-establishing the first service. This not only ensures service continuity but also reduces service latency.

[0155] The first service can be a service associated with the first device and the second device, such as a service performed by the first device and the second device in cooperation.

[0156] The first business can be a business related to the application scenario, such as including at least one of the following: inventory business, command business, positioning business, sensing business, proximity determination, read business, write business, deactivation business, lock business, or security business (such as authentication, certification, registration, etc.), or it can be a newly defined business type in the future, and there are no restrictions on the specific naming.

[0157] The first service can also be a process-related service, such as including at least one of the following: access process, or data transmission process, etc. This can be understood as performing the first service being equivalent to performing the corresponding process. The access process can be random access, such as contention-based random access or contention-free random access. Optionally, the access process may include reporting the device ID, such as the identifier of the first device, which can be referred to the method description below and will not be repeated here. The data transmission process can be device-to-reader (D2R) / uplink data transmission, reader-to-device (R2D) / downlink data transmission, etc. Optionally, the data transmission process may also include reporting the device ID, which can also be referred to the method description below and will not be repeated here. Optionally, the access process and the data transmission process are not strictly distinguished, and the two can be combined. For example, data transmission can also be performed in the access process, such as contention-free random access, where the device can send D2R / uplink data in the first message.

[0158] Suspending the first service (or having the first service suspended) refers to paused / interrupted the first service that is not yet completed, or pausing / interrupting the first service before it is finished. Resuming the first service (or having the first service resumed) refers to resuming the suspended first service, meaning the first service is no longer paused / interrupted and continues with the subsequent processes. This avoids disrupting service continuity and causing excessive latency due to re-executing the first service. For example, if the first service process includes steps 1-6, and the first service is suspended at step 3 (e.g., allowing access), then resuming the first service will continue with step 4 (e.g., sending device identifier / D2R / uplink data), without needing to start from step 1 again.

[0159] It should be understood that "suspending the first service" is an exemplary expression, and it can be replaced by any possible expression, such as pausing / interrupting / waiting for the first service, or the first service being unable to complete, or anything that can be used to describe pausing the first service when it is not completed, can be understood as suspending the first service; the specific expression is not limited. Similarly, "resuming the first service" is also an exemplary expression, and it can be replaced by any possible expression, such as continuing to complete / continue executing / continue performing the first service, or anything that can be used to describe the first service continuing execution after the pause ends can be understood as resuming the first service; the specific expression is not limited.

[0160] It should be understood that the communication method provided in the embodiments of this application can be applied to the devices shown in Figures 3-4, such as between the first device and the second device. Specific implementations can be found in the following method embodiments, which will not be repeated here. The solutions in the embodiments of this application can also be applied to other communication systems, and the corresponding names can be replaced with the names of the corresponding functions in other communication systems.

[0161] It should also be understood that Figures 3 and 4 are simplified schematic diagrams for ease of understanding only, and the communication system may also include other network devices and / or other terminal devices, which are not shown in Figures 3 and 4.

[0162] The interaction process between devices in the above-described communication system will be specifically described below with reference to Figures 5-9, through method embodiments. The communication method provided in this application embodiment can be applied to the above-described communication system, such as the interaction between the first device and the second device, which will be described in detail below.

[0163] As shown in Figure 5, the flow of this communication method is as follows:

[0164] S501, the first device determines the first identifier.

[0165] The first identifier can be associated with the first device and / or the suspended first service. It can be used by the first device to distinguish received messages. If a message carrying the first identifier is received, the device will perform corresponding processing (such as resuming the first service). If a message without the first identifier is received, the device will not respond or will perform other processing.

[0166] In one possible implementation, the first identifier can be implemented using existing information cells. For example, the first identifier can include at least one or more of the following: the identifier (AS ID) of the access stratum (AS) of the first device, a random number of the first device, such as RN16, or it can also be a protocol-predefined or pre-configured identifier.

[0167] An AS ID can be used to identify a first device at the AS layer, such as an AS layer device uniquely identifying the first device through the AS ID. It should be understood that the AS ID is one example and could also be other types of identifiers, such as a non-access stratum (NAS) identifier (NAS ID).

[0168] RN16 can be a 16-bit random number used for contention resolution (e.g., to distinguish different terminals during contention resolution) or for random access or requesting access to a second device. The generation of RN16 can include at least one or more of the following: randomly generated by the first device, or generated according to certain rules, such as obtaining the first device's unique identifier through a hash function, or it can be pre-configured / predefined in the first device. It should be understood that RN16 is one example; it can also be a random number of other bit counts, such as RN18, RN24, etc., or it can be other names, such as random access ID, random ID, etc., or it can be other forms of fields / strings.

[0169] In another possible implementation, the first identifier can also be a newly defined identifier, such as a newly defined / generated / assigned string / encoding / random number / sequence, etc., and the specific implementation method is not limited.

[0170] There are multiple or multiple combinations of ways for the first device to determine the first identifier. The following describes methods 1 and 2 respectively.

[0171] Method 1: The first device obtains the first identifier from the second device.

[0172] The second device can decide to send the first identifier to the first device on its own, or the second device can receive the information from the first device first and then send the first identifier to the first device based on the information from the first device. Accordingly, the first device receives the first identifier from the second device, which will be described in detail below.

[0173] In one possible scenario, the second device may, at its own discretion, send a first identifier to the first device at any possible time, such as by sending a first message containing the first identifier. In this case, the first message may be at least one of the following: a paging message, a message indicating permission to access, or a message responding to a service.

[0174] A paging message may include at least one of the following: a paging message or other paging messages.

[0175] Taking a paging message as an example, a paging message can be used to page a first device, such as pageing one or more or all devices that receive the paging message (which may include the first device), or page a subset of devices that meet the matching conditions (which may also include the first device). The matching condition can be identifier matching. For example, the paging message carries an identifier for matching. This identifier can include a first identifier or other identifiers, such as the identifier of a device group, a mask, or one or more of the identifiers of the first device. The receiving device determines whether its own identifier matches the identifier carried in the paging message, such as whether the identifiers are the same. If the identifiers match, it responds to the paging message, such as triggering / executing a first service, such as accessing a second device; otherwise, it does not respond. Of course, if the paging message does not carry an identifier for matching, it can be assumed that all paged devices meet the matching conditions.

[0176] Optionally, the paging message can also be used to trigger / instruct / request the first device to perform a first service, such as containing an identifier of the first service. During the first service process, the first device typically transmits relevant data, such as sending uplink data and / or receiving downlink data; therefore, the paging message can also be understood as a request / trigger / instruction for the first device to transmit data.

[0177] A paging message can be triggered by a core network element to be sent by a second device. For example, one or more core network elements (such as AMF, Ambient IoT Management Function (AIoTMF), or Ambient IoT Function (AIoTF)) can instruct / request / trigger the second device to send a paging message to the first device according to the needs of the first service, or they can directly send a paging message to the second device. If the second device decides to pass the first identifier to the first device during the paging phase, the second device can pass the currently / previously generated / allocated first identifier, or the first identifier obtained in advance from the first device, or the first identifier predefined or preconfigured by the protocol, to the first device through the paging message. Accordingly, the first device can receive the paging message and obtain the first identifier from it, i.e., determine the first identifier.

[0178] It should be understood that the first device for paging is an exemplary description and can also be replaced by a first device for selecting / triggering / filtering. Furthermore, the paging message is also an exemplary name and can be replaced by any possible name, such as a select message, trigger message, initial trigger message, indication message, etc., or any message used to implement the paging message function in the embodiments of this application can be understood as a paging message.

[0179] It should also be understood that paging messages can be replaced by query messages, meaning the query message carries a first identifier. Query messages can also indicate configuration information related to access and / or data transmission, such as access and / or data transmission resources (e.g., time, frequency resources). Query messages and paging messages can be combined into a single message; the naming of this message is unrestricted, or they can be transmitted through the same message.

[0180] Messages used to indicate permission to access may include at least one of the following: an acknowledgment message (ACK), or other messages used to confirm access.

[0181] Taking a confirmation message as an example, the confirmation message can be used to indicate that the first device is allowed to access the second device. That is, when it is confirmed that the first device is allowed to access, the first identifier is transmitted to the first device by reusing the confirmation message. If the second device is an access network device, then the first device accessing the second device is accessing the network side. If the second device is a terminal device, then the first device accessing the second device is accessing the terminal device. In this case, the first device can also access the network side through the terminal device.

[0182] If the second device decides to pass the first identifier to the first device during the access phase, the second device can pass the currently / previously generated / assigned first identifier, or the first identifier obtained in advance from the first device, or the first identifier predefined or preconfigured by the protocol, to the first device via an acknowledgment message. Accordingly, the first device can receive the acknowledgment message and obtain the first identifier from it, thus determining the first identifier.

[0183] It should be understood that the acknowledgment message is an exemplary name, which can be replaced with any possible name, such as access response message, random access response message, etc., or any message used to implement the function of the acknowledgment message in the embodiments of this application can be understood as an acknowledgment message.

[0184] Messages used to respond to services can include at least one of the following: a query reply message or other messages used to respond to services. Taking a query reply message as an example, it can be used to indicate whether service transmission was successful or failed, such as whether the service data sent by the first device was successfully received by the second device. If the second device decides to pass a first identifier to the first device during the data transmission phase, the second device can pass one or more of the following: a currently / previously generated / assigned first identifier, or a first identifier obtained in advance from the first device, or a first identifier predefined or preconfigured by the protocol, to the first device via a query reply message. Accordingly, the first device can receive the query reply message and obtain the first identifier from it, i.e., determine the first identifier.

[0185] It should be understood that the term "repeated query message" is an exemplary name and can be replaced with any possible name, such as an access occasion indication / trigger message, or any message used to implement the function of repeated query messages in the embodiments of this application.

[0186] It should also be understood that carrying the first identifier through the above message is one example. The first identifier can also be transmitted through a separate message, which can be an existing message or a newly defined message. There are no restrictions on the specific implementation.

[0187] In another possible scenario, the second device may send a first identifier to the first device based on information from the first device, such as sending a first message containing the first identifier. In this case, the first message may be at least one of the following: a message indicating permission to access, or a message responding to a service request.

[0188] For example, the first device sends instruction information to the second device, and the second device receives the instruction information from the first device.

[0189] The instruction information can be used to instruct the suspension of the first service.

[0190] The conditions for suspending the first service can include at least one of the following: the first device is in sleep mode, or other conditions, such as a poor state of the first service. Taking the first device being in sleep mode as an example, it can mean that the first device enters sleep mode due to insufficient power / energy. In sleep mode, the first device can maintain basic functions, such as maintaining the stored state of registers / memory, or maintaining the preservation of temporary storage information. In sleep mode, the first device typically does not perform data transmission, such as not listening or sending data, or only maintaining listening, such as listening for specific information, such as trigger information and / or paging messages, without sending data.

[0191] It should be understood that the indication message indicating the suspension of the first service can also be replaced with the indication message indicating the interruption / pause / waiting for the first service, or the first service being unable to be completed. The specific wording is not limited and can be replaced with the equivalent wording of suspending the first service, which will not be elaborated further below. Furthermore, the condition for suspending the first service including the first device going to sleep is only one example; it could also be that the condition for the first device going to sleep includes suspending the first service. The indication message can also be used to indicate that the first device has insufficient power or is in sleep mode (or it can only indicate that the first device has insufficient power or is in sleep mode, without indicating the suspension of the first service). For example, the indication message can be a cell containing one or more bits, such as 1 bit, where 0 indicates no power and 1 indicates that the first device is suspending the first service. Since the condition for suspending the first service is that the first device is in sleep mode, it can also implicitly indicate that the first device has insufficient power or is in sleep mode. Another example is 2 bits, where 00 indicates that the first device has insufficient power, 01 indicates that the first device is in sleep mode, and 10 indicates that the first service is suspended. Other cases are also possible, and there are no specific limitations. Alternatively, the first information can contain multiple information cells, such as information cell #1 and information cell #2. Information cell #1 is a single bit, where 0 indicates no activity and 1 indicates that the first device has suspended the first service. Information cell #2 is also a single bit, where 0 indicates no activity and 1 indicates that the first device has insufficient power or is in sleep mode.

[0192] It should be understood that "first device in sleep mode" is an exemplary expression, which can be replaced with any possible expression, such as "first device has insufficient power / energy", "first device needs to be charged / recharged", or any state that can be used to describe the first device as being in sleep mode while maintaining only basic functions and unable to transmit data. No specific expression is limited.

[0193] It should also be understood that an instruction message instructing the first device to hibernate does not usually mean that the first device has already entered hibernation or immediately. Rather, it may mean that after a period of time, the device is waiting for the preparations for hibernation to be completed, such as obtaining the first identifier, before entering hibernation. Therefore, the instruction message can also be understood as indicating that the first device will / needs / prepares / is about to enter hibernation. Of course, if the preparations for hibernation have been completed, the first device can also enter hibernation immediately after sending the instruction message.

[0194] The first device can send a second message to the second device, and the second device can receive the second message from the first device. The second message contains indication information and can be at least one of the following: a message for the first device to access the network, or a message for business data transmission.

[0195] The message used by the first device to access the second device may include at least one of the following: a random access message, or other messages requesting random access. Taking a random access message as an example, it may be a message sent by the first device at an access opportunity to request access to the second device. For example, the random access message may contain a random number, such as RN16. It should be understood that "random access message" is an exemplary designation and can be replaced with any possible designation, such as "access request message," "random access request message," etc., or any message used to implement the function of the random access message in the embodiments of this application can be understood as a random access message.

[0196] Messages used for business data transmission can include any possible named message, and there are no restrictions on the specific message name. This message can be used to carry business data sent by the first device, such as the identifier of the first device, or other types of data, such as sensing data, location data, speed data, read / write commands, etc., and can also be described as uplink data / D2R, with no specific restrictions.

[0197] During the completion of the first service, the first device can continuously assess its remaining power / energy. If the first device assesses that its remaining power / energy is insufficient to support the completion of the first service, such as when its remaining power / energy is less than the power / energy required to complete the process, the first device can decide to send an indication message to the second device. This indication message will be transmitted to the second device through a subsequent message in the first service process. For example, during the random access phase, if the first device assesses that its remaining power / energy is insufficient to support the completion of the first service, it will send a random access message containing the indication message to the second device. Similarly, during the data transmission phase, if the first device assesses that its remaining power / energy is insufficient to support the completion of the first service, it will send an uplink data / D2R message containing the indication message to the second device.

[0198] Of course, assessing insufficient power / energy and sending indication information can also be decoupled. For example, if the first device assesses its current remaining power / energy during the random access phase, and its power / energy is sufficient for the data transmission phase, then the first device can also carry indication information in the uplink data / D2R.

[0199] Furthermore, the above example of carrying instruction information through a message is just one example. The instruction information can also be transmitted through a separate message, which can be an existing message or a newly defined message. There are no restrictions on the specific implementation.

[0200] The second device can send a first identifier to the first device based on the indication information. For example, the second device can obtain the indication information from the second message to determine that the first service is suspended, or that the first device has insufficient power or is in sleep mode. Based on this, the second device can transmit the currently / previously generated / assigned first identifier, or the first identifier obtained from the first device (such as RN16 carried in the second message, where the first identifier is RN16), or a first identifier predefined or preconfigured by the protocol, to the first device through the first message. In one possible approach, the first message can be a response to the second message, such as the second message being a message for the first device to access the network, the first message being a message indicating that access is allowed, or the second message being a message for service data transmission, and the first message being a message responding to a service. Alternatively, in another possible approach, the first message can also be a message independent of the second message, i.e., it is not associated with the second message.

[0201] It should be understood that carrying the first identifier through the above message is one example. The first identifier can also be transmitted through a separate message, which can be an existing message or a newly defined message. There are no restrictions on the specific implementation.

[0202] Method 2: The first device determines the first identifier itself.

[0203] The first identifier can be generated / assigned by the first device itself, such as by determining at least one of RN16 or AS ID as the first identifier, or by generating it randomly or through hashing; the specific implementation method is not limited. The first device can generate the first identifier when its current remaining power / energy is insufficient, or it can generate the first identifier at any possible time, or it can generate the first identifier by default; the specific method is not limited. The first identifier can be transmitted to the second device together with the aforementioned indication information, or the first identifier can be sent to the second device separately; the specific transmission method is not limited, and the relevant introduction of Method 1 can be referred to, which will not be repeated here.

[0204] The first device can store the first identifier.

[0205] Before / after / when the first device goes into hibernation / suspends the first service, the first device may save the first identifier.

[0206] For example, the first device may include a first state and a second state. The first state is the state in which data transmission of the first service is permitted, such as the service recovery / normal state, i.e., the state in which the service is completed normally. Furthermore, the first state may also have other naming conventions, such as power-on state. The second state is the state in which the first service is suspended, or in other words, the state in which the service is suspended, interrupted, or incomplete. Furthermore, the second state may also have other naming conventions, such as sleep state, disconnected state, inactive state, deep / medium / light sleep state, etc. Before / after the first device goes into sleep / suspends the first service, the first device may enter the second state, such as entering the second state from the first state. In this state, the first device may save identification information related to the first device, such as the first identifier, and / or information related to the first service, such as the context of the first service.

[0207] The first device can determine its own state using a register. For example, the register can store one or more bits, where 1 represents the first state and 0 represents the second state, or 01 represents the first state and 00 represents the second state. Alternatively, the state of the first device can be reflected by holding a capacitor (such as a latch). If the capacitor is charged, it is in the first state; if the capacitor is below a certain threshold or depleted, it is in the second state. The specific implementation is not limited.

[0208] Optionally, the first device may also store other information, such as security parameters, so that when the service is restored, the security parameters do not need to be re-acquired / updated, thereby further reducing service latency.

[0209] Security parameters can be used to protect the communication between the first device and the second device, such as for encryption / decryption and / or integrity protection of uplink and downlink data, for example, for encryption / decryption and / or integrity protection of the data of the first service. Security parameters may include one or more parameters, such as confidentiality keys, integrity protection keys, random numbers, counter values, etc. Security parameters can be generated / derived by the first device and / or generated by the core network / second device. Security parameters can be sent from the first device to the core network / second device, or vice versa, for example, they can be carried in the following messages: paging messages, or message #1 (RN16), or message #2 (ACK), or uplink data, or downlink data, without restriction.

[0210] After saving the first identifier, if the first device determines that its remaining power / energy is insufficient to support its continued completion of the first service, such as sending a message to the second device, the first device enters sleep / suspend or interrupts the first service, and uses its remaining power / energy to maintain the saved information. During sleep, the first device can recharge so that when its power / energy is sufficient to support its continued completion of the first service, the first device can end sleep and listen for specific messages, discarding other messages received.

[0211] S502, the second device sends a second identifier to the first device, and the first device receives the second identifier from the second device.

[0212] The second identifier is associated with the first identifier. For example, the second identifier may be the same as the first identifier, or the second identifier may be part of the first identifier, or the second identifier may be determined based on the first identifier, such as by calculating / deriving the first identifier through some calculation rules.

[0213] The second identifier can be carried in the scheduling information, or it can be any other possible information / message, without any specific limitation. In addition, the scheduling information is also an exemplary name, which can be replaced with any possible name, such as configuration information, wake-up information, recovery information, etc. Any information used to implement the function of the scheduling information in the embodiments of this application can be understood as scheduling information.

[0214] The second device can poll the first device to send scheduling information. For example, after obtaining the second identifier based on the first identifier, the second device can poll the first device to send scheduling information carrying the second identifier, without considering whether the first device has ended its sleep state or the sleep time of the first device. Alternatively, the second device can estimate the time when the first device will end its sleep state, such as sending scheduling information based on time information at the time the first device wakes up. The time information can be used to indicate the sleep time of the first device, such as a periodic period or a periodic period, as detailed in the relevant introduction below, and will not be repeated here.

[0215] It should be understood that the scheduling information is an exemplary name, and it can be replaced with any possible name, such as configuration information, wake-up information, recovery information, etc. Any information used to implement the function of the scheduling information in the embodiments of this application can be understood as scheduling information. In addition, the scheduling information can be carried in paging messages, MAC-CE, AIoT access layer, or NAS messages, and there are no specific limitations.

[0216] S503, the first device resumes first service.

[0217] The conditions for the first device to resume the first service may include: the second identifier being associated with the first identifier; and / or: the first device ending its dormancy period.

[0218] For example, when the first device ends its hibernation, it can listen for scheduling information. Upon receiving scheduling information, the first device can determine whether the second identifier carried in the scheduling information is associated with a pre-saved first identifier, such as whether the first and second identifiers are the same, whether the second identifier is part of the first identifier, or whether the second identifier can be determined based on the first identifier. If the second identifier is not associated with the first identifier, the first device can discard the received scheduling information and continue listening. If the second identifier is associated with the first identifier, the first device resumes the first service.

[0219] The first device resuming the first service may include: transmitting data of the first service to the second device; and / or: entering a first state.

[0220] For example, the first device can enter the first state from the second state. In this state, the first device transmits data of the first service to the second device. For example, it can continue to send data of the first service that has not yet been sent or has been sent completely to the second device, such as the identifier of the first device, or other types of data, such as location data, sensing data, etc.

[0221] It should be understood that if the first device does not receive scheduling information within the preset time after ending its sleep period, or if the identifier in the received scheduling information does not match, the first device may revert to the existing technology process, such as re-entering random access. The preset time can be pre-configured, such as by carrying it through the aforementioned paging message, query message, or repeat query message, or it can be carried through separate signaling, or it can be predefined by the protocol, such as defining the ratio between the preset time and the sleep time of the first device, such as 1 / 4 or 1 / 10, etc.

[0222] Additionally, if the first service is a command service, the first device can also transmit data for the first service to the second device according to the instructions of the first service. The instructions for the first service can be commands of the command service, such as read commands or write commands, specifically indicating which contents in which storage areas should be read / written. In this case, the transmission of data for the first service between the first device and the second device can be based on the command, either reading data from the first device and sending it to the second device, or writing data to the second device.

[0223] Optionally, the second device can send an instruction for the first service to the first device, and the first device can send an instruction for the first service to the second device. For example, the second device can carry the instruction for the first service in a paging message / query message / repeat query message before the first device goes into sleep mode. The first device can save the instruction for the first service so that when the first device resumes the first service, it can transmit the data of the first service with the second device according to the pre-saved instruction for the first service. Alternatively, the instruction for the first service can also be carried in the scheduling information, or in the same message as the scheduling information, or in a separate message; there is no specific limitation.

[0224] It is understood that the aforementioned messages / signaling / information can be used interchangeably without restriction. Furthermore, there can be multiple first devices; that is, a first identifier can be associated with multiple first devices for the rapid recovery of services across multiple first devices.

[0225] It can also be understood that the above suspension / resumption of the first service is based on the example of the first device going into hibernation / ending hibernation, but it is not a limitation. The conditions for suspending / resumption of the first service may not include the first device going into hibernation / ending hibernation. For example, the first device may suspend the first service when the service quality is poor (such as poor channel quality or poor service stability). Subsequently, the second device may send a second identifier when it is determined that the service quality has recovered, so that the first device can resume the first service.

[0226] In summary, the first device can determine a first identifier, such as when a first service is suspended. This first identifier is associated with the suspended first service and / or the first device. Subsequently, the first device can receive a second identifier from the second device, which can be associated with the first identifier pre-determined by the first device. This allows the first device to directly resume the suspended first service, i.e., continue executing the first service process without re-establishing the first service. This not only ensures service continuity but also reduces service latency.

[0227] Optionally, in conjunction with the above S501-S503, the method may further include:

[0228] The first device transmits time information to the second device / the second device transmits time information to the first device.

[0229] Time information can be used to indicate the time / duration of the first device's sleep period, or simply the sleep duration. The time information can indicate at least one of the following: the duration of a time period, such as ΔT; or it can indicate the start time to the end time, such as t1-t2; or it can indicate a periodic time, for example, a sleep duration / period of T, indicating that the first device will wake up every T time intervals, used to align the first device's sleep and sleep end times with the second device.

[0230] The first device can determine the time information itself, such as determining the sleep duration based on local rules / policies / protocols, and generating the time information. The first device can carry the time information in the aforementioned first message to send to the second device, or it can carry it in a separate message; the specific implementation is not limited.

[0231] The second device can determine the time information itself, such as by determining the sleep duration of the first device according to local rules / policies and generating the time information. Alternatively, the second device can obtain the time information from a third device. For example, the third device can be a device / function / entity in the management domain / management plane, such as a RIC, or it can be a network element in the service plane / service domain, such as AIoTMF, AMF, PCF, UDM, etc. The third device can determine the time information, such as by determining the time information based on the sleep time of one or more devices. One or more devices may include the first device, or may be different from the first device. The third device can determine the approximate sleep time required by the first device based on the sleep time of these one or more devices, such as by taking the average sleep time of one or more devices as the sleep time of the first device, thereby determining the time information. The third device can send the time information to the second device, and the second device receives the time information from the third device accordingly. Based on this, the second device can carry the time information in the aforementioned second message to send to the first device, or it can carry it in a separate message; the specific implementation is not limited.

[0232] The second device can also send scheduling information to the first device based on time information. For example, the second device can confirm that the first device is about to suspend the first service based on received indication information. Therefore, the second device can start a timer based on the time information, with the timeout period being the end time of the first device's sleep mode. If the timer expires, the second device can send scheduling information to the first device.

[0233] The overall process of the method has been described above with reference to Figure 5. The specific process of the method provided in the embodiments of this application will be described below with reference to Figures 6-8.

[0234] Figure 6 is a schematic flowchart of the communication method provided in this application embodiment. This communication method can be applied to the aforementioned communication system and mainly involves the communication interaction between a first device and a second device. For example, in the random access process, the first device determines to go into sleep mode. The first device can save a first identifier and then enter sleep mode. If the first device ends its sleep state and the identifier received from the second device matches the pre-saved first identifier, the first device continues the unfinished RA process to access the second device.

[0235] Specifically, as shown in Figure 6, the communication method flow is as follows:

[0236] S601, the second device sends a paging message to the first device.

[0237] For paging messages, please refer to the relevant description in S501 above, which will not be repeated here.

[0238] S602, the second device sends a query message to the first device.

[0239] The query message can be used to trigger / indicate at least one access opportunity (such as an access opportunity to access a second device), or to directly or indirectly indicate the total number of such access opportunities.

[0240] An access opportunity can be a period of time, including at least one of the following: a symbol, a slot, a subframe, or a frame, without limitation on the specific temporal granularity. A query message can mark the start of the first access opportunity; therefore, a query message can also be used to trigger the first access opportunity.

[0241] It should be understood that the query message is an exemplary name and can be replaced with any possible name, such as access indication / trigger, access round indication / trigger, etc., or any message used to implement the function of the query message in the embodiments of this application can be understood as a query message.

[0242] It should also be understood that S601-S602 can be executed together, meaning that paging messages and query messages can be encapsulated in a single message for transmission.

[0243] S603, the second device sends a duplicate query message (queryrep) to the first device.

[0244] Repeated query messages can be used to trigger / indicate the next access opportunity, or they can be understood as indicating / associating with the boundary (start or end) of an access opportunity, such as the end of the previous access opportunity / the start of the next access opportunity, so that the first device can choose to initiate random access at the next access opportunity.

[0245] It should be understood that the term "repeated query message" is an exemplary name and can be replaced with any possible name, such as an access occasion indication / trigger message, or any message used to implement the function of repeated query messages in the embodiments of this application.

[0246] It is understandable that S603 is optional, such as not triggering access through repeated query messages.

[0247] The process principles of S601-S603 can also be found in the relevant introductions of S101-S103 above, and will not be repeated here.

[0248] S604, the first device determines that the first device is in hibernation / suspending the first service.

[0249] Upon receiving a repeated query message, the first device can determine that its remaining power / energy is insufficient to support the subsequent processes of the first service after its completion. Therefore, it can determine that the first device should hibernate / suspend the first service. Furthermore, the specific implementation of S604 can be found in the relevant description in S501 above, and will not be repeated here.

[0250] In addition, S601-S604 are optional. For example, the first device may not know whether it is in sleep mode or suspending the first service. By default, if it receives the first identifier, it saves the first identifier and goes into sleep mode.

[0251] S605, the first device sends message #1 (msg1) to the second device.

[0252] Message #1 can be a message sent by an access opportunity selected by the first device to request access to the second device. The specific selection principle can be found in the relevant description of S104 above, and will not be repeated here. Message #1 may include RN16.

[0253] Message #1 may also contain instruction information. The specific implementation of the instruction information can be found in the relevant introduction to "instruction information" in S501 above, and will not be repeated here.

[0254] It should be understood that message #1 is an exemplary name, which can be replaced with any possible name, such as A-IoT message #1 (A-IoT msg1), random access message, access request message, random access request message, etc., or any message used to implement the function of message #1 in the embodiments of this application can be understood as message #1. In addition, the above is an example of message #1 carrying indication information, and the indication information can also be transmitted through a separate signaling / message.

[0255] S606, the second device sends message #2 (msg2) to the first device.

[0256] Message #2 can be used to confirm that the first device can access the network (such as the second device), such as ACK.

[0257] Message #2 includes the aforementioned RN16, used to associate with the first device, indicating successful contention resolution (UE contention resolution identity), meaning the first device can access the network. Message #2 may also include a first identifier; for specific implementation details, please refer to the relevant description of "first identifier" in S501, which will not be repeated here. Optionally, message #2 may also include time information; for specific implementation details, please refer to the relevant description of "time information" above, which will not be repeated here.

[0258] It should be understood that message #2 is an exemplary name, and it can be replaced with any possible name, such as A-IoT message #2 (A-IoT msg2), confirmation message, access response message, random access response message, etc., or any message used to implement the function of message #2 in the embodiments of this application can be understood as message #2. Message #2 carrying the first identifier is only an example, and the first identifier can also be carried in other messages, such as the paging message, query message, or repeat query message mentioned above. That is to say, the second device can also decide to provide the first identifier to the first device at any possible time.

[0259] It should also be understood that message #2 carrying time information is only one example. Time information can also be carried in other messages, such as the paging message, query message, or repeat query message mentioned above. Alternatively, the time information can also be provided by the first device, such as when the first device sends duration information to the second device. In this case, the duration information can be carried in message #1 mentioned above. Or, if the first device and the second device have their sleep times predefined or preconfigured by the protocol, they may not need to exchange duration information.

[0260] S607, the first device stores the first identifier.

[0261] If the first device determines that its electrical energy is insufficient to support the execution of S609, the first device can save the first identifier and enter sleep mode.

[0262] S608, the second device sends scheduling information, and the first device receives scheduling information.

[0263] The first device determines that the second identifier in the scheduling information is associated with the first identifier that was saved in advance, and executes S609.

[0264] S609, the first device sends message #3 (msg3) to the second device.

[0265] Message #3 can carry uplink data / D2R, or the identifier of the first device, such as the device ID, to complete the data transmission or report the device identifier.

[0266] It should be understood that message #3 is an exemplary name, which can be replaced with any possible name, such as A-IoT message #3 (A-IoT msg3), etc., or any message used to implement the function of message #3 in the embodiments of this application can be understood as message #3.

[0267] It is understandable that S607-S609 can also refer to the relevant introductions of S502-S503 mentioned above.

[0268] S610, the second device sends a repeat query message to the first device.

[0269] A repeat query message can be used in response to message #3. At this point, the first device, based on the identifier of the sending first device and having received the repeat query message, confirms successful transmission, or in other words, successful random access.

[0270] Furthermore, S610 is optional; for example, the second device may not respond to S609, i.e., it may not execute S610. The implementation principle of S610 can also be referred to the relevant introduction of S106-S107 above, and will not be repeated here.

[0271] As can be seen from the process shown in Figure 6, after the first device resumes hibernation, it can quickly resume the first service through the first identifier that has been saved in advance, so as to continue to complete the random access without having to re-randomly access the device. This reduces latency and ensures service continuity.

[0272] It should also be understood that in the process shown in Figure 6, the messages / information / data / information elements transmitted in S601-S608 and S610 can be carried in the MAC layer, such as MAC-CE, or MAC service data unit (SDU), or MAC protocol data unit (PDU), or the MAC layer can be replaced by the A-IoT access layer. The messages / information / data / information elements transmitted in S609 can be carried in the A-IoT access layer, NAS layer, or application layer. The following process can be understood by reference and will not be repeated here.

[0273] Figure 7 is a schematic flowchart of the communication method provided in this application embodiment. This communication method can be applied to the aforementioned communication system and mainly involves communication interaction between a first device and a second device. For example, during a random access process, the first device determines to enter sleep mode. The first device can save a first identifier and send its identifier to the second device before entering sleep mode. If the first device ends its sleep mode and the identifier received from the second device matches the pre-saved first identifier, the first device continues subsequent data transmission.

[0274] S701, the second device sends a paging message to the first device.

[0275] S702, the second device sends a query message to the first device.

[0276] S703, the second device sends a repeat query message to the first device.

[0277] S704, the first device determines that the first device is in hibernation / suspending the first service.

[0278] In addition, S701-S704 are optional. For example, the first device may not know whether it is in sleep mode or suspending the first service. By default, if it receives the first identifier, it saves the first identifier and goes into sleep mode.

[0279] S705, the first device sends message #1 to the second device.

[0280] Message #1 can carry RN16, and message #1 can also carry indication information, or the indication information can also be carried in a separate message.

[0281] S706, the second device sends message #2 to the first device.

[0282] Message #2 can be an ACK and can carry the first identifier.

[0283] S707, the first device sends message #3 to the second device.

[0284] Message #3 may carry uplink data / D2R, or the identifier of the first device.

[0285] It is understandable that the relevant introductions of S701-S707 can also refer to the relevant introductions of S601-S606 mentioned above, and will not be repeated here.

[0286] S708, the second device sends downlink data / R2D to the first device.

[0287] After the first device transmits its identifier to the second device via message #3, the first device and the second device can continue to transmit data, i.e., execute S708 to continue the first business process.

[0288] S709, the first device stores the first identifier.

[0289] If the first device determines that its power / energy is insufficient to support the execution of S711, the first device can save the first identifier and enter sleep mode. That is to say, both Figure 6 and Figure 7 show the first device determining to enter sleep mode after receiving a repeated query message, but the difference is that Figure 7 shows the first device entering sleep mode only after its power / energy is sufficient to complete uplink data transmission or report the first device's identifier.

[0290] In addition, S708-S709 are optional; for example, the first device can perform no data transmission, wait for a period of time, and then enter sleep mode.

[0291] S710, the second device sends scheduling information, and the first device receives scheduling information.

[0292] The first device determines that the second identifier in the scheduling information is associated with the first identifier that was saved in advance, and executes S711.

[0293] S711, the first device sends uplink data / D2R to the second device.

[0294] Optionally, the scheduling information may carry an indication of the first service, or the first device may obtain and save the indication of the first service in advance during or before S709, so that the first device can send uplink data / D2R to the second device according to the indication.

[0295] It is understandable that S710-S711 can also refer to the relevant introductions of S502-S503 mentioned above.

[0296] S712, the second device sends a repeat query message to the first device.

[0297] A repeat query message can be used in response to uplink data / D2R. In this case, the first device confirms successful transmission by sending uplink data / D2R and receiving the repeat query message.

[0298] Furthermore, S712 is optional; for example, the second device may not respond to S711, that is, it may not execute S712. The implementation principle of S712 can also be referred to the relevant introduction of S106-S107 above, and will not be repeated here.

[0299] Figure 8 is a schematic flowchart of the communication method provided in this application embodiment. This communication method can be applied to the aforementioned communication system and mainly involves the communication interaction between a first device and a second device. For example, when the first device determines to enter sleep mode during data transmission, it can save a first identifier and send its identifier to the second device before entering sleep mode. If the first device ends its sleep mode and the identifier received from the second device matches the pre-saved first identifier, the first device continues subsequent data transmission.

[0300] S801, the second device sends a paging message to the first device.

[0301] S802, the second device sends a query message to the first device.

[0302] S803, the second device sends a repeat query message to the first device.

[0303] S804, the first device sends message #1 to the second device.

[0304] Message #1 can carry RN16.

[0305] S805, the second device sends message #2 to the first device.

[0306] Message #2 can be ACK.

[0307] It is understandable that the implementation principles of S801-S806 can also refer to the relevant introductions of S601-S606 mentioned above, and will not be repeated here.

[0308] S806, the first device determines that the first device is in hibernation / suspending the first service.

[0309] Upon receiving message #2, the first device can determine that its remaining power / energy is insufficient to support the subsequent processes of the first service after it is completed. Therefore, it can determine that the first device should hibernate / suspend the first service.

[0310] It should be understood that the specific implementation of S806 can also refer to the relevant introduction in S501 above, and will not be repeated here.

[0311] In addition, S801-S604 are optional. For example, before S801-S806, the first device can receive and save the ACK in advance. In this case, there is no need to execute S801-S806. Or, for example, the first device may not know whether it is in sleep mode or suspending the first service. By default, if it receives the first identifier, it saves the first identifier and goes into sleep mode.

[0312] S807, the first device sends message #3 to the second device.

[0313] Message #3 may carry uplink data / D2R, or it may carry the identifier of the first device. Message #3 may also carry indication information, or the indication information may be carried in a separate message. The specific implementation of the indication information can be referred to the relevant description in S501 above, and will not be repeated here. In addition, the specific implementation of message #3 can be referred to the relevant description of message #3 in Figure 6 above, and will not be repeated here.

[0314] S808, the second device sends a repeat query message to the first device.

[0315] The duplicate query message is used in response to message #3. The duplicate query message may carry a first identifier, and optionally, it may also carry time information. The specific implementation of the first identifier can be found in the relevant description in S501 above, and the time information can be found in the relevant description of "time information" in Figure 5 above, and will not be repeated here. Furthermore, the specific implementation of the duplicate query message can be found in the relevant description of "duplicate query message" in Figure 6 above, and will not be repeated here either.

[0316] At this point, the data transmission was successful, and the first service's process for this paging request has ended.

[0317] S809, the first device stores the first identifier.

[0318] Before the first service begins its process for the next paging, such as periodic inventory or paging retransmission, the first device can save the first identifier and go into hibernation so that the first service can be quickly resumed on the next paging.

[0319] Optionally, the first device may also store information such as the session ID and mask of the first service to distinguish the first service from other services. For example, when the first service is restored, for paging messages that do not carry the session ID and mask, i.e. paging messages of other services, the first device executes the existing random access procedure.

[0320] Furthermore, the specific implementation of the session identifier and mask can be found in the relevant introduction of S101 above, and will not be repeated here.

[0321] S810, the second device sends a paging message, and the first device receives the paging message.

[0322] The paging message may contain scheduling information. The first device determines that the second identifier in the scheduling information is associated with the first identifier that has been saved in advance, and executes S811, that is, without the need for random access, performs periodic inventory or paging retransmission.

[0323] S811, the first device sends uplink data / D2R or the identifier of the first device to the second device.

[0324] Optionally, the scheduling information may carry an indication of the first service, or the first device may obtain and save the indication of the first service in advance during or before S809, so that the first device can send uplink data / D2R or the identifier of the first device to the second device according to the indication.

[0325] It is understandable that S810-S811 can also refer to the relevant introductions of S502-S503 mentioned above.

[0326] S812, the second device sends a repeat query message to the first device.

[0327] A repeat query message can be used in response to uplink data / D2R. In this case, the first device confirms successful transmission by sending uplink data / D2R and receiving the repeat query message.

[0328] Furthermore, S812 is optional; for example, the second device may not respond to S711, that is, it may not execute S812. The implementation principle of S812 can also be referred to the relevant introduction of S106-S107 above, and will not be repeated here.

[0329] It is understandable that Figures 6-8 above can also be applied to the O-RAN scenario, in which the third device can also configure the second device. For example, the third device can be a controller, such as a RIC, or any other possible controller. The third device can allocate / generate a first identifier based on the information of the first device obtained in advance. The third device can also determine the approximate sleep duration of the first device based on the sleep time of one or more devices, thereby generating time information.

[0330] The third device can configure the first identifier and / or time information to the second device, either by sending it directly to the second device or through access network equipment, such as a CU and / or DU. In this case, the second device may not need to determine the first identifier and / or time information itself, but can directly provide the acquired first identifier and / or time information to the first device. Correspondingly, the first device may no longer need to report the first identifier and / or time information. At this time, the second device can determine, based on the information obtained from the third device, that the first device corresponding to this information has not yet completed the first service, and can preferentially trigger the first device to execute the first service.

[0331] Optionally, the third device may also know the capability or power consumption of the first device, and the third device may also instruct the second device to prioritize triggering the first device with low capability / high power consumption to perform the first service.

[0332] Figure 9 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Exemplarily, as shown in Figure 9, the communication device 900 includes a transceiver module 902 and a processing module 901. For ease of explanation, Figure 9 only shows the main components of the communication device.

[0333] The communication device 900 can be applied to the communication methods shown in Figures 5-8 to achieve the corresponding functions. For example, the transceiver module 902 can be used to implement the transceiver function in the communication methods shown in Figures 5-8, and the processing module 901 can be used to implement other functions in the communication methods shown in Figures 5-8 besides the transceiver function.

[0334] Optionally, the transceiver module 902 may include a transmitting module (not shown in FIG. 9) and a receiving module (not shown in FIG. 9). The transmitting module is used to implement the transmitting function of the communication device 900, and the receiving module is used to implement the receiving function of the communication device 900.

[0335] Optionally, the communication device 900 may further include a storage module (not shown in FIG. 9) that stores programs or instructions. When the processing module 901 executes the program or instructions, the communication device 900 can perform the functions in the methods shown in FIG. 5-8.

[0336] It is understood that the communication device 900 can be a network device, or a chip (system) or other component or assembly that can be set in the network device, or a device that includes the network device. This application does not limit this.

[0337] Furthermore, the technical effects of the communication device 900 can be referenced from the technical effects of the communication method described above, and will not be repeated here.

[0338] Figure 10 is a second schematic diagram of the structure of the communication device provided in an embodiment of this application. Exemplarily, the communication device can be a terminal, or a chip (system) or other component or assembly that can be disposed in the terminal. As shown in Figure 10, the communication device 1000 may include a processor 1001. Optionally, the communication device 1000 may further include a memory 1002 and / or a transceiver 1003. The processor 1001 is coupled to the memory 1002 and the transceiver 1003, for example, they can be connected via a communication bus.

[0339] The following is a detailed description of each component of the communication device 1000, with reference to Figure 10:

[0340] The processor 1001 is the control center of the communication device 1000. It can be a single processor or a collective term for multiple processing elements. For example, the processor 1001 can be one or more central processing units (CPUs), application-specific integrated circuits (ASICs), or one or more integrated circuits configured to implement the embodiments of this application, such as one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs).

[0341] Optionally, the processor 1001 can execute various functions of the communication device 1000 by running or executing software programs stored in the memory 1002 and calling data stored in the memory 1002, such as executing the communication methods shown in Figures 5-8 above.

[0342] In a specific implementation, as one example, processor 1001 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG10.

[0343] In a specific implementation, as one embodiment, the communication device 1000 may also include multiple processors, such as processors 1001 and 1004 shown in FIG. 10. Each of these processors may be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). Here, a processor may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0344] The memory 1002 is used to store the software program that executes the solution of this application, and is controlled by the processor 1001 to execute it. The specific implementation method can be referred to the above method embodiment, and will not be repeated here.

[0345] Optionally, the memory 1002 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory 1002 may be integrated with the processor 1001 or may exist independently and be coupled to the processor 1001 through the interface circuit of the communication device 1000 (not shown in FIG. 10). This application embodiment does not specifically limit this.

[0346] Transceiver 1003 is used for communication with other communication devices. For example, if communication device 1000 is a terminal, transceiver 1003 can be used to communicate with a network device or with another terminal device. As another example, if communication device 1000 is a network device, transceiver 1003 can be used to communicate with a terminal or with another network device.

[0347] Optionally, transceiver 1003 may include a receiver and a transmitter (not shown separately in Figure 10). The receiver is used to implement the receiving function, and the transmitter is used to implement the transmitting function.

[0348] Optionally, the transceiver 1003 can be integrated with the processor 1001 or exist independently and be coupled to the processor 1001 through the interface circuit of the communication device 1000 (not shown in FIG10). This application embodiment does not specifically limit this.

[0349] It is understood that the structure of the communication device 1000 shown in Figure 10 does not constitute a limitation on the communication device. Actual communication devices may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0350] Furthermore, the technical effects of the communication device 1000 can be referred to the technical effects of the method described in the above method embodiments, and will not be repeated here.

[0351] It should be understood that the processor in the embodiments of this application can be a central processing unit (CPU), or it can be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (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 any conventional processor.

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

[0353] The above embodiments can be implemented, in whole or in part, by software, hardware (such as circuits), firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.

[0354] This application also provides a computer-readable storage medium storing a computer program that, when executed by a computer, enables the computer to perform the aforementioned communication method. Alternatively, the computer program includes instructions for implementing the aforementioned communication.

[0355] This application also provides a computer program product, including: computer program code, which, when run on a computer, enables the computer to execute the communication method provided above.

[0356] This application also provides a communication system, which includes a first device and a second device for performing the communication method described above.

[0357] This application also provides a chip, which may include a processor that executes the communication method described above. Optionally, the chip may further include a memory coupled to the processor, the memory storing a program for executing the communication method described above.

[0358] It should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. A and B can be singular or plural. Additionally, the character " / " in this article generally indicates an "or" relationship between the preceding and following related objects, but it can also represent an "and / or" relationship. Please refer to the context for a more accurate understanding.

[0359] In this application, "at least one" means one or more, and "more than one" means two or more. "At least one of the following" or similar expressions refer to 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, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0360] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0361] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0362] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0363] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0364] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0365] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0366] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0367] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method characterized by comprising: The method applied to a first device or a chip in the first device, comprising: determining a first identifier, the first identifier being associated with the first device and / or a first service suspended, the first service being a service associated with the first device and a second device; receiving a second identifier of the second device, the second identifier being associated with the first identifier; resuming the first service.

2. The method of claim 1, wherein, The condition for resuming the first service comprises that the second identifier is associated with the first identifier, and / or the first device ends hibernation.

3. The method according to claim 1 or 2, characterized in that, The second identifier being associated with the first identifier means that the first identifier is the same as the second identifier.

4. The method according to any one of claims 1 to 3, characterized in that, The resuming the first service comprises: transmitting data of the first service with the second device; and / or; entering a first state, the first state being a state allowing transmission of data of the first service.

5. The method of claim 4, wherein, The transmitting data of the first service with the second device comprises: transmitting data of the first service with the second device according to an indication of the first service.

6. The method of claim 5, wherein, The method further comprises: receiving the indication of the first service from the second device.

7. The method according to any one of claims 1 to 6, characterized in that, The determining the first identifier comprises: receiving the first identifier from the second device.

8. The method according to any one of claims 1-7, characterized in that, The method further comprises: saving the first identifier.

9. The method according to any one of claims 1-8, characterized in that, The method further comprises: suspending the first service.

10. The method according to any one of claims 1-9, characterized in that, The condition for suspending the first service comprises that the first device hibernates.

11. The method according to any one of claims 1-10, characterized in that, The method further comprises: sending indication information to the second device, the indication information being used to indicate suspension of the first service, or the indication information being further used to indicate that the first device hibernates.

12. The method according to any one of claims 1-11, characterized in that, The method further comprises: transmitting time information with the second device, the time information being used to indicate a time for the first device to hibernate.

13. A communication method characterized by comprising: The method applied to a second device or a chip in the second device, comprising: receiving indication information from a first device, the indication information being used to indicate suspension of a first service or hibernation of the first device, the first service being a service associated with the first device and a second device; sending a second identifier to the first device, the second identifier being associated with the first device and / or the first service, the first service being configured to be resumed in a case that the second identifier is associated with a first identifier saved by the first device.

14. The method of claim 13, wherein, The sending the second identifier to the first device comprises: in response to the first device ending hibernation, sending the second identifier to the first device.

15. The method according to claim 13 or 14, characterized in that, The method further comprises: determining that the first device ends hibernation according to time information, the time information being used to indicate a time for the first device to hibernate.

16. The method of claim 15, wherein, The method further comprises: transmitting the time information with the first device, and / or receiving the time information from a third device.

17. The method according to any one of claims 13-16, characterized by, The method further comprises: sending the first identifier to the first device.

18. The method of claim 17, wherein, The sending the first identifier to the first device comprises: sending the first identifier to the first device according to the indication information.

19. The method according to any one of claims 13-18, characterized by, The method further comprises: in a case that the first service is resumed, transmitting data of the first service with the first device.

20. The method of any one of claims 13-19, wherein, The method further comprises: sending, to the first device, an indication of the first traffic, the indication of the first traffic indicating a data transmission of the first traffic.

21. A communications device, characterized by The communication device comprises modules for performing the method of any of claims 1-20.

22. A communications device, characterized by comprising: a processor; the processor is configured to couple with a memory storing computer instructions that, when executed by the processor, cause the communication device to perform the method of any of claims 1-20.

23. The communication apparatus according to claim 22, wherein, The communication device is a chip.

24. A computer-readable storage medium, characterized in that, The computer readable storage medium comprises a computer program or instructions that, when executed on a computer, cause the computer to perform the method of any of claims 1-20.

Images