Communication method, communication device, communication system, storage medium, and program product

Abstract

The present disclosure relates to a communication method, a communication device, a communication system, a storage medium, and a program product. The communication method is executed by a first device. The method comprises: receiving a first message sent by a second device, wherein the first message carries first information, the first information is used for indicating an operation that the second device expects the first device to perform, the first message is sent by the second device when the second device has not received a second message, and the second message carries a device identifier of the first device. The communication method can improve communication efficiency.

Description

Communication methods, communication equipment, communication systems, storage media and software products Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a communication method, communication device, communication system, storage medium, and program product. Background Technology

[0002] With the application of Internet of Things (IoT) technology in various industries, the large-scale deployment of IoT devices powered by traditional batteries is limited by factors such as environment, cost, energy conservation and environmental protection, and cannot meet the needs in some scenarios.

[0003] In light of this, an IoT technology supporting ambient energy is proposed. Ambient energy-enabled IoT devices can utilize energy sources present in the environment to power themselves, enabling communication and data transmission. Summary of the Invention

[0004] Improving the efficiency of communication between IoT devices and network devices is a problem that needs to be solved.

[0005] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.

[0006] According to a first aspect of the present disclosure, a communication method is provided, performed by a first device, the method comprising: receiving a first message sent by a second device, the first message carrying first information, the first information being used to indicate an operation that the second device expects the first device to perform; the first message being sent by the second device when it has not received a second message, the second message carrying a device identifier of the first device.

[0007] According to a second aspect of the present disclosure, a communication method is provided, performed by a second device, the method comprising: sending a first message to a first device, the first message carrying first information, the first information being used to indicate an operation that the second device expects the first device to perform; the first message being sent when a second message has not been received, the second message carrying a device identifier of the first device.

[0008] According to a third aspect of the present disclosure, a communication device is provided, deployed on a first device. The communication device includes: a transceiver module, configured to receive a first message sent by a second device, the first message carrying first information, the first information indicating an operation that the second device expects the first device to perform; the first message being sent by the second device when it has not received a second message, the second message carrying a device identifier of the first device.

[0009] According to a fourth aspect of the present disclosure, a communication device is provided, deployed on a second device. The communication device includes: a transceiver module, configured to send a first message to a first device, the first message carrying first information, the first information indicating an operation that the second device expects the first device to perform; the first message is sent when a second message is not received, the second message carrying a device identifier of the first device.

[0010] According to a fifth aspect of the present disclosure, a communication device is provided, comprising: one or more processors, and one or more memories for storing a computer program; wherein the processor executes the computer program to implement the steps of the communication methods described in the first and second aspects.

[0011] According to a sixth aspect of the present disclosure, a communication system is provided, including a first device and a second device, wherein the second device is configured to send a first message to the first device, the first message carrying first information, the first information being used to indicate an operation that the second device expects the first device to perform; the first message is sent by the second device when it has not received a second message, the second message carrying a device identifier of the first device. The first device is configured to receive the first message sent by the second device.

[0012] According to a seventh aspect of the present disclosure, a computer-readable storage medium is provided that stores a computer program thereon, wherein the computer program, when executed by a processor, implements the steps of the communication methods described in the first and second aspects above.

[0013] According to an eighth aspect of the present disclosure, a computer program product is provided, comprising a computer program that, when executed by a processor, implements the steps of the communication methods described in the first and second aspects above.

[0014] According to a ninth aspect of the present disclosure, a computer program is provided, the computer program including code that, when executed by a processor, implements the steps of the communication methods described in the first and second aspects above.

[0015] The technical solutions provided in this disclosure can improve the efficiency of communication between IoT devices and network devices. Attached Figure Description

[0016] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments of the invention and, together with the description, serve to explain the principles of the embodiments of the invention.

[0017] Figure 1A is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

[0018] Figure 1B is a schematic diagram illustrating wireless communication based on backscattering according to an embodiment of the present disclosure.

[0019] Figure 1C is a schematic diagram of an architecture of an A-IoT system according to an embodiment of the present disclosure.

[0020] Figure 1D is a schematic diagram of another architecture of an A-IoT system according to an embodiment of the present disclosure.

[0021] Figure 1E is a schematic diagram of another architecture of an A-IoT system according to an embodiment of the present disclosure.

[0022] Figure 1F is a schematic diagram of another architecture of an A-IoT system according to an embodiment of the present disclosure.

[0023] Figure 1G is a schematic diagram of a passive device according to an embodiment of the present disclosure.

[0024] Figure 1H is a schematic diagram illustrating the interaction between a reader and a device in a passive Internet of Things system according to an embodiment of the present disclosure.

[0025] Figure 1I is a schematic diagram illustrating a random access process for an Internet of Things (IoT) device according to an embodiment of the present disclosure.

[0026] Figure 2A is an exemplary interactive schematic diagram of a communication method according to an embodiment of the present disclosure.

[0027] Figure 2B is an exemplary interactive schematic diagram of a communication method according to an embodiment of the present disclosure.

[0028] Figure 2C is an exemplary interactive schematic diagram of a communication method according to an embodiment of the present disclosure.

[0029] Figure 3 is an exemplary interactive schematic diagram of a communication method shown in an embodiment of this disclosure.

[0030] Figure 4 is a schematic diagram of the structure of a communication device shown in an embodiment of this disclosure.

[0031] Figure 5A is a schematic diagram of the structure of a communication device shown in an embodiment of this disclosure.

[0032] Figure 5B is a schematic diagram of the chip structure shown in an embodiment of this disclosure. Detailed Implementation

[0033] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.

[0034] In a first aspect, embodiments of this disclosure propose a communication method executed by a first device. The method includes: receiving a first message sent by a second device, the first message carrying first information, the first information being used to indicate an operation that the second device expects the first device to perform; the first message being sent by the second device when it has not received a second message, the second message carrying a device identifier of the first device.

[0035] In the above embodiments, the first information is used to indicate the operation that the second device expects the first device to perform. Therefore, when the first device receives a first message carrying the first information, it can determine the operation to be performed based on the first information. This avoids the waiting time incurred by the first device due to uncertainty about subsequent operations, significantly reducing communication latency and improving communication efficiency.

[0036] In conjunction with some embodiments of the first aspect, in some embodiments, the above method includes: receiving a first paging message sent by a second device, the first paging message being received before a first message, the first paging message being associated with a first Internet of Things service; and sending a third message to the second device based on the first paging message, the third message being used to trigger the second device to send a fourth message, the fourth message being used to schedule the second message.

[0037] In conjunction with some embodiments of the first aspect, in some embodiments, the first information is at least one of the following: resource configuration information, used to indicate the resources allocated by the network to the first device; contention resolution indication information, used to indicate that the contention has been resolved; first indication information, used to indicate that the first device sends a second message; second indication information, used to indicate that the first device stops processing the first IoT service; third indication information, used to indicate that the first device re-enters random access; a first random number, associated with the first IoT service; wherein the first IoT service is the IoT service associated with the second message.

[0038] In conjunction with some embodiments of the first aspect, in some embodiments, the operation is to send a second message after receiving a first message, wherein the first message is one of the following: resource configuration information, contention resolution instruction information, or first instruction information.

[0039] In conjunction with some embodiments of the first aspect, in some embodiments, the above method further includes one of the following: the first information is resource configuration information, and a second message is sent to the second device; the first information is contention resolution indication information, and a second message is sent to the second device; the first information is a first indication information, and a second message is sent to the second device.

[0040] In conjunction with some embodiments of the first aspect, in some embodiments, the operation is to not respond to the reader to device (R2D) message associated with the first IoT service, and the first information is the second indication information.

[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the above method further includes: the first information being the second indication information, determining that the R2D message associated with the first IoT service will not be responded to.

[0042] In conjunction with some embodiments of the first aspect, in some embodiments, the above method further includes: receiving a second paging message sent by a second device, the second paging message being associated with a second Internet of Things (IoT) service, the second IoT service being different from the first IoT service; and performing random access based on the second paging message.

[0043] In conjunction with some embodiments of the first aspect, in some embodiments, the operation is to re-perform random access, and the first information is one of the following: third indication information, first random number.

[0044] In conjunction with some embodiments of the first aspect, in some embodiments, the above method further includes one of the following: the first information is a third indication information, and random access is performed again; the first information is a first random number, and random access is performed again.

[0045] In conjunction with some embodiments of the first aspect, in some embodiments, re-performing random access includes: listening to a fifth message, the fifth message being used to trigger the first device to perform random access, the fifth message being associated with a first IoT service.

[0046] In conjunction with some embodiments of the first aspect, in some embodiments, the above method further includes one of the following: discarding the access layer identifier associated with the first IoT service, the access layer identifier being carried in the device-to-reader (D2R) message and the R2D message associated with the first IoT service; discarding the first random number associated with the first IoT service.

[0047] Secondly, embodiments of this disclosure propose a communication method executed by a second device, the method comprising: sending a first message to a first device, the first message carrying first information, the first information being used to indicate an operation that the second device expects the first device to perform; the first message being sent when a second message has not been received, the second message carrying a device identifier of the first device.

[0048] In the above embodiments, the second device sends a first message carrying first information to the first device. The first information is used to instruct the second device on the operation that the first device expects the first device to perform. By specifying different formats for the first information, waiting time caused by uncertainty about subsequent operations can be avoided for the first device, significantly reducing communication latency and improving communication efficiency.

[0049] In conjunction with some embodiments of the second aspect, in some embodiments, the above method further includes: sending a first paging message to a first device, the first paging message being sent before the first message and associated with a first IoT service; receiving a third message sent by the first device, the third message being a response message to the first paging message; and sending a fourth message to the first device based on the third message, the fourth message being used to schedule the second message.

[0050] In conjunction with some embodiments of the second aspect, in some embodiments, the first information is at least one of the following: resource configuration information, used to indicate the resources allocated by the network to the first device; contention resolution indication information, used to indicate that the contention has been resolved; first indication information, used to indicate that the first device sends a second message; second indication information, used to indicate that the first device stops processing the first IoT service; third indication information, used to indicate that the first device re-enters random access; a first random number, associated with the first IoT service; wherein the first IoT service is the IoT service associated with the second message.

[0051] In conjunction with some embodiments of the second aspect, in some embodiments, the operation is to send a second message after receiving a first message, wherein the first message is one of the following: resource configuration information, contention resolution instruction information, or first instruction information.

[0052] In conjunction with some embodiments of the second aspect, in some embodiments, the above method further includes: the first information being resource configuration information, receiving a second message sent by the first device; the first information being contention resolution indication information, receiving a second message sent by the first device; the first information being a first indication information, receiving a second message sent by the first device.

[0053] In conjunction with some embodiments of the second aspect, in some embodiments, the operation is to not respond to the R2D message associated with the first IoT service, and the first information is the second indication information.

[0054] In conjunction with some embodiments of the second aspect, in some embodiments, the above method further includes: sending a second paging message to a first device, the second paging message being used to trigger the first device to perform random access, the second paging message being associated with a second Internet of Things (IoT) service, the second IoT service being different from the first IoT service.

[0055] In conjunction with some embodiments of the second aspect, in some embodiments, the operation is to re-perform random access, and the first information is one of the following: third indication information, first random number.

[0056] In conjunction with some embodiments of the second aspect, in some embodiments, the above method further includes: sending a fifth message to a first device, the fifth message being used to trigger the first device to perform random access, and the fifth message being associated with a first Internet of Things service.

[0057] Thirdly, embodiments of this disclosure provide a communication device deployed on a first device. The communication device includes: a transceiver module, configured to receive a first message sent by a second device, the first message carrying first information, the first information indicating an operation that the second device expects the first device to perform; the first message is sent by the second device when it has not received a second message, the second message carrying a device identifier of the first device.

[0058] In conjunction with some embodiments of the third aspect, in some embodiments, the transceiver module is further configured to receive a first paging message sent by the second device, the first paging message being received before the first message, the first paging message being associated with the first IoT service; and according to the first paging message, to send a third message to the second device, the third message being used to trigger the second device to send a fourth message, the fourth message being used to schedule the second message.

[0059] In conjunction with some embodiments of the third aspect, in some embodiments, the first information is at least one of the following: resource configuration information, used to indicate the resources allocated by the network to the first device; contention resolution indication information, used to indicate that the contention has been resolved; first indication information, used to indicate that the first device sends a second message; second indication information, used to indicate that the first device stops processing the first IoT service; third indication information, used to indicate that the first device re-enters random access; a first random number, associated with the first IoT service; wherein the first IoT service is the IoT service associated with the second message.

[0060] In conjunction with some embodiments of the third aspect, in some embodiments, the operation is to send a second message after receiving a first message, wherein the first message is one of the following: resource configuration information, contention resolution instruction information, or first instruction information.

[0061] In conjunction with some embodiments of the third aspect, in some embodiments, the transceiver module is further configured to send a second message to the second device when the first information is resource configuration information; send a second message to the second device when the first information is contention resolution indication information; and send a second message to the second device when the first information is a first indication information.

[0062] In conjunction with some embodiments of the third aspect, in some embodiments, the operation is to not respond to the R2D message associated with the first IoT service, and the first information is the second indication information.

[0063] In conjunction with some embodiments of the third aspect, in some embodiments, the communication device further includes: a processing module, configured to determine that the first information is the second indication information and not to respond to the R2D message associated with the first Internet of Things service.

[0064] In conjunction with some embodiments of the third aspect, in some embodiments, the transceiver module is further configured to receive a second paging message sent by the second device, the second paging message being associated with a second Internet of Things (IoT) service, the second IoT service being different from the first IoT service; and to perform random access based on the second paging message.

[0065] In conjunction with some embodiments of the third aspect, in some embodiments, the operation is to re-perform random access, and the first information is one of the following: third indication information, first random number.

[0066] In conjunction with some embodiments of the third aspect, in some embodiments, the processing module is further configured to perform random access again when the first information is a third indication information; or to perform random access again when the first information is a first random number.

[0067] In conjunction with some embodiments of the third aspect, in some embodiments, the processing module is also used to listen for a fifth message, which is used to trigger the first device to perform random access, and the fifth message is associated with the first Internet of Things service.

[0068] In conjunction with some embodiments of the third aspect, in some embodiments, the processing module is further configured to discard the access layer identifier associated with the first IoT service, the access layer identifier being carried in the D2R message and the R2D message associated with the first IoT service; and discard the first random number associated with the first IoT service.

[0069] Fourthly, embodiments of this disclosure provide a communication device deployed on a first device. The communication device includes: a transceiver module, configured to send a first message to the first device, the first message carrying first information, the first information being used to instruct a second device to perform an operation expected by the first device; the first message is sent when a second message is not received, and the second message carrying a device identifier of the first device.

[0070] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transceiver module is further configured to send a first paging message to the first device, the first paging message being sent before the first message and associated with the first IoT service; receive a third message sent by the first device, the third message being a response message to the first paging message; and send a fourth message to the first device based on the third message, the fourth message being used to schedule the second message.

[0071] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first information is at least one of the following: resource configuration information, used to indicate the resources allocated by the network to the first device; contention resolution indication information, used to indicate that the contention has been resolved; first indication information, used to indicate that the first device sends a second message; second indication information, used to indicate that the first device stops processing the first IoT service; third indication information, used to indicate that the first device re-enters random access; a first random number, associated with the first IoT service; wherein the first IoT service is the IoT service associated with the second message.

[0072] In conjunction with some embodiments of the fourth aspect, in some embodiments, the operation is to send a second message after receiving a first message, wherein the first message is one of the following: resource configuration information, contention resolution instruction information, or first instruction information.

[0073] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transceiver module is further configured to receive a second message sent by the first device when the first information is resource configuration information; receive a second message sent by the first device when the first information is contention resolution indication information; and receive a second message sent by the first device when the first information is a first indication information.

[0074] In conjunction with some embodiments of the fourth aspect, in some embodiments, the operation is to not respond to the R2D message associated with the first IoT service, and the first information is the second indication information.

[0075] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transceiver module is further configured to send a second paging message to the first device. The second paging message is used to trigger the first device to perform random access. The second paging message is associated with a second Internet of Things (IoT) service, which is different from the first IoT service.

[0076] In conjunction with some embodiments of the fourth aspect, in some embodiments, the operation is to re-perform random access, and the first information is one of the following: third indication information, first random number.

[0077] In conjunction with some embodiments of the second aspect, in some embodiments, the transceiver module is further configured to send a fifth message to the first device, the fifth message being used to trigger the first device to perform random access, and the fifth message being associated with the first IoT service.

[0078] Fifthly, embodiments of this disclosure provide a communication device, comprising: one or more processors, and one or more memories for storing computer programs; wherein the processors execute the computer programs to implement the steps of the communication methods described in the first and second aspects.

[0079] In a sixth aspect, embodiments of this disclosure provide a communication system including a first device and a second device, wherein the second device is configured to send a first message to the first device, the first message carrying first information, the first information being used to instruct the second device to perform an operation that the first device expects the first device to perform; the first message is sent by the second device when it has not received a second message, the second message carrying a device identifier of the first device. The first device is configured to receive the first message sent by the second device.

[0080] In conjunction with some embodiments of the sixth aspect, in some embodiments, the second device is further configured to send a first paging message to the first device, the first paging message being sent before the first message, the first paging message being associated with a first IoT service; the first device is further configured to receive the first paging message; and send a third message to the second device according to the first paging message; the second device is further configured to receive the third message; and send a fourth message to the first device according to the third message, the fourth message being used to schedule the second message.

[0081] In conjunction with some embodiments of the sixth aspect, in some embodiments, the first device is further configured to send a second message to the second device when the first information is resource configuration information; send a second message to the second device when the first information is contention resolution indication information; and send a second message to the second device when the first information is a first indication information. The second device is further configured to receive the second message sent by the first device when the first information is resource configuration information; receive the second message sent by the first device when the first information is contention resolution indication information; and receive the second message sent by the first device when the first information is a first indication information.

[0082] In conjunction with some embodiments of the sixth aspect, in some embodiments, the second device is further configured to send a second paging message to the first device. The second paging message is used to trigger the first device to perform random access. The second paging message is associated with a second Internet of Things (IoT) service, which is different from the first IoT service. The first device is further configured to receive the second paging message and perform random access based on the second paging message.

[0083] In conjunction with some embodiments of the sixth aspect, in some embodiments, the second device is further configured to send a fifth message to the first device, the fifth message being used to trigger the first device to perform random access, and the fifth message being associated with a first IoT service. The first device is also configured to listen to the fifth message.

[0084] In a seventh aspect, embodiments of this disclosure provide a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the communication method described in any of the first aspect, the second aspect, and their possible implementations.

[0085] Eighthly, embodiments of this disclosure provide a computer program product, including a computer program that, when executed by a processor, implements the steps of the communication method described in any of the first, second, and possible implementations thereof.

[0086] In a ninth aspect, embodiments of this disclosure provide a computer program comprising code that, when executed by a processor, implements the steps of the communication method described in any of the first, second, and possible implementations thereof.

[0087] It is understood that the aforementioned communication equipment, communication system, storage medium, program product, etc., are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0088] This disclosure provides a communication method, communication device, communication system, storage medium, and program product. In some embodiments, terms such as communication method, information processing method, and paging method can be used interchangeably; terms such as terminal, communication device, information processing device, information transmission device, A-IoT device, reader, network device, communication equipment, network function, and network entity can be used interchangeably; and terms such as communication system, information processing system, and information transmission system can be used interchangeably.

[0089] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments. In all embodiments of this disclosure, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0090] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0091] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0092] In the embodiments disclosed herein, "multiple" refers to two or more.

[0093] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0094] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.

[0095] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.

[0096] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0097] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0098] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.

[0099] In some embodiments, the terms “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “if…”, “if…”, etc., can be used interchangeably.

[0100] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0101] In some embodiments, devices, etc., can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as “device”, “equipment”, “circuit”, “network element”, “node”, “function”, “unit”, “section”, “system”, “network”, “chip”, “chip system”, “entity”, and “subject” can be used interchangeably.

[0102] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0103] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.

[0104] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.

[0105] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.

[0106] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0107] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0108] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0109] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0110] Figure 1A is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. As shown in Figure 1A, the communication system 100 includes a terminal 101 and a network device 102. In one embodiment, the network device 102 may include at least one of an access network device and a core network device.

[0111] In some embodiments, terminal 101 includes, but is not limited to, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home.

[0112] In some embodiments, the access network device, such as a node or device that connects a terminal to a wireless network, may include at least one of, but is not limited to, an evolved node B (eNB), a next-generation eNB (ng-eNB), a next-generation node B (gNB), a node B (NB), a home node B (HNB), a home evolved node B (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open RAN, a cloud RAN, a base station in other communication systems, and an access node in a Wi-Fi system.

[0113] In some embodiments, the technical solutions of this disclosure can be applied to Open Radio Access Network (Open RAN) architectures. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0114] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0115] In some embodiments, a core network device may be a single device comprising one or more network elements, or it may be multiple devices or a group of devices, each comprising all or part of one or more network elements. Network elements may be virtual or physical. The core network may include, for example, at least one of an evolved packet core (EPC) network, a 5G core (5GC) network, and a next-generation core (NGC) network.

[0116] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0117] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1A, or some of the main components in the communication system 100, but are not limited thereto. The main components shown in FIG1A are illustrative. The communication system 100 may include all or some of the main components in FIG1A, or may include other main components other than those in FIG1A. The number and form of each main component are arbitrary. Each main component may be physical or virtual. The connection relationship between the main components is illustrative. The main components may not be connected or may be connected. The connection may be in any way, such as direct connection or indirect connection, wired connection or wireless connection.

[0118] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), Super 3G, International Mobile Telecommunications-Advanced (IMT-Advanced), 4th Generation Mobile Communication System (4G), 5th Generation Mobile Communication System (5G), 5G New Radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future Generation Radio Access (FX), Global System for Mobile Communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, ultra-wideband (UWB), Bluetooth (a registered trademark), public land mobile network (PLMN) networks, device-to-device (D2D) systems, machine-to-machine (M2M) systems, internet of things (IoT) systems, vehicle-to-everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0119] In some cases, with the application of Internet of Things (IoT) technology across various industries, the large-scale deployment of IoT devices powered by traditional batteries is limited by factors such as environment, cost, and energy conservation. This makes it unsuitable for certain scenarios and negatively impacts user experience. In some embodiments, the astronomical growth of IoT networks, coupled with the proliferation of IoT devices, has pushed network maintenance costs, including labor and battery costs, to unprecedented levels. Furthermore, billions of traditional batteries are discarded annually, with only a small fraction being effectively recycled, causing harmful impacts on the Earth's ecosystem. Maintaining IoT networks and replacing batteries can be extremely challenging under extreme environmental conditions. Therefore, battery-free IoT (also known as passive IoT) communication has been proposed, which improves network performance and sustainability and expands application scenarios. Moreover, battery-free communication is more environmentally friendly and safer for children and the elderly. By eliminating traditional batteries, device size and cost can be significantly reduced, paving the way for a variety of new applications.

[0120] In some embodiments, various low-power wide-area (LPWA) technologies, such as machine-type communication (MTC), narrowband Internet of Things (NB-IoT), and reduced-capability (RedCap) terminals, have been developed to meet the growing demands of vertical industries. These LPWA technologies achieve low cost, low power consumption, and massive connectivity, satisfying the requirements of many applications. However, the following issues still need to be addressed: 1. In some scenarios (such as extreme environmental conditions, such as high pressure, extremely high / low temperatures, and humid environments), traditional battery-powered devices are not suitable. 2. Maintenance-free devices (such as devices that do not require replacement of traditional batteries) are needed. 3. Devices with ultra-low complexity, very small device size (e.g., millimeter (mm) thickness), and longer lifespan are required. To meet these unmet needs, ambient energy-enabled IoT is a promising technology.

[0121] In some embodiments, an ambient energy-enabled IoT device is an IoT device powered by harvested energy. Such IoT devices are battery-free or have limited energy storage capacity (e.g., the device uses capacitors). An ambient energy-enabled IoT device can power itself by harvesting radio waves, light, motion, heat, or any other suitable source of energy to drive wireless communication or data transmission.

[0122] In some embodiments, the above-mentioned IoT devices that support ambient energy can be used interchangeably with terms such as passive devices, passive IoT devices, ambient energy-based devices, and ambient IoT (A-IoT) devices.

[0123] In some embodiments, energy harvested from the environment can power IoT devices that support ambient energy for data transmission and wireless communication. Current mainstream low-power IoT communication chips (such as Bluetooth Low Energy (BLE) chips, Long Range Radio (LoRa) chips, and NB-IoT chips) consume tens or even hundreds of milliwatts of power for transmission and reception, while energy harvested from the environment is only in the microwatt range, insufficient to power devices with these types of chips. Therefore, a new wireless communication technology is needed to reduce communication power consumption to tens or even less than ten microwatts. Backscatter (BS) communication technology can be used for this purpose. Backscatter communication is one of the key technologies for building a green, energy-efficient, low-cost, and flexibly deployable future IoT, and is an important means of realizing "intelligent interconnection of everything."

[0124] In some embodiments, backscatter communication utilizes the principle of backscattering radio frequency signals to design an extremely low-power modulation and transmission technology. As shown in Figure 1B, which is a schematic diagram illustrating wireless communication based on backscattering according to an embodiment of this disclosure, an excitation source 11 transmits a radio frequency signal to a passive device 12. When the radio frequency signal reaches the passive device 12, a portion is reflected. The passive device 12 can adjust the matching between its receiving antenna and impedance according to the information to be transmitted to enhance the reflection of the radio frequency signal and modulate the information to be transmitted onto the backscattered signal for transmission. This process is similar to a reflector. Compared to other communication technologies, backscatter transmission does not require complex radio frequency structures, reducing the use of devices such as power amplifiers, high-precision crystal oscillators, duplexers, and high-precision filters. It also does not require complex baseband processing, thus simplifying terminal design and significantly reducing terminal node costs.

[0125] In some embodiments, the radio frequency signal is used to provide energy for the passive device 12 to transmit signals. Therefore, the radio frequency signal can be referred to as an excitation signal or a trigger signal.

[0126] In some embodiments, the excitation source 11 may be the reader of the passive device 12 or the anchor point of the reader.

[0127] In some embodiments, backscatter communication has been widely used in radio frequency identification (RFID) systems, resulting in many large-scale commercial applications. Its working principle is that the receiver (typically an RFID reader) sends a radio frequency excitation signal to activate a passive node (typically an RFID tag). The tag uses backscatter communication to modulate its own information onto the radio frequency signal. The reader receives the reflected signal from the tag and demodulates it to achieve information transmission.

[0128] However, current RFID technology also has many drawbacks, such as short coverage distance (the wireless signal experiences double-path fading during communication, resulting in significant path loss and a short effective communication distance), single-channel transmission, the need for precise tag alignment, and the lack of power control. There is significant room for improvement in the communication aspects of RFID technology. For example, integrating 3GPP communication technologies is needed to improve the wireless communication performance of RFID in A-IoT.

[0129] In some embodiments, when A-IoT technology is integrated into the communication system 100 described above, the present disclosure embodiments may provide, but are not limited to, the following A-IoT system architectures:

[0130] Architecture 1: As shown in Figure 1C, Figure 1C is a schematic diagram of an A-IoT system architecture according to an embodiment of this disclosure. Uplink and / or downlink transmissions are directly performed between the passive device 12 and the network device 20 (such as an access network device).

[0131] Architecture 2: As shown in Figure 1D, Figure 1D is a schematic diagram of another architecture of an A-IoT system according to an embodiment of this disclosure. The passive device 12 and the network device 20 (such as an access network device) indirectly perform uplink and / or downlink transmissions through an intermediate node 30.

[0132] In some embodiments, intermediate node 30 forwards uplink and / or downlink transmissions. For example, intermediate node 30 may be a relay node, an access integration backhaul (IAB) node, a terminal, a repeater, etc.

[0133] Architecture 3: As shown in Figure 1E, Figure 1E is a schematic diagram of another architecture of an A-IoT system according to an embodiment of this disclosure. The passive device 12 and the network device 20 (such as an access network device) directly perform one of the uplink and downlink transmissions, and indirectly perform the other of the uplink and downlink transmissions through an auxiliary node 40.

[0134] In some embodiments, the auxiliary node 40 forwards uplink and / or downlink transmissions. For example, the auxiliary node 40 may be a relay node, an access integration backhaul (IAB) node, a terminal, a repeater, etc.

[0135] Architecture 4: As shown in Figure 1F, Figure 1F is a schematic diagram of another architecture of the A-IoT system according to an embodiment of this disclosure. The passive device 12 and the terminal 50 directly perform uplink and downlink transmissions. The terminal 50 is responsible for collecting data from the passive device 12 and forwarding the collected data to the network side.

[0136] In some embodiments, the excitation source of the passive device 12 may include at least one of the network device 20, intermediate node 30, auxiliary node 40, and terminal 50.

[0137] In some embodiments, the A-IoT system can support both Architecture 1 and Architecture 2 topologies described above. In one embodiment, when the A-IoT system can communicate using either Architecture 1 or Architecture 2, the available spectrum resources can include three deployment modes: in-band mode, guard-band mode, or stand-alone mode. In-band mode refers to transmission using general uplink and / or downlink spectrum resources. Guard-band mode refers to transmission using the guard band spectrum resources between the general uplink and downlink spectrum. Stand-alone mode refers to transmission using spectrum resources unrelated to the general transmission spectrum.

[0138] In some embodiments, FIG1G is a schematic diagram of a passive device according to an embodiment of the present disclosure. As shown in FIG1G, the passive device 12 may be, but is not limited to, the following three types:

[0139] Type A: No energy storage and no independent signal generation / amplification, and transmission is based on backscattering.

[0140] Type B: Has energy storage but no independent signal generation, and transmits based on backscattering. The energy stored in passive device 12 can be used to amplify the backscattered signal.

[0141] Type C: It has energy storage to enable independent signal generation and uses active radio frequency components for transmission.

[0142] In some embodiments, the following constraints may be imposed on A-IoT devices:

[0143] The overall goal should be to research a coordinated air interface design that minimizes the differences in IoT environments (where necessary) to enable the following devices:

[0144] Peak power consumption is approximately 1 μW, with energy storage capability. Initial sampling frequency offset (SFO) is as high as 10Xppm (per million units). The device contains neither DL nor UL amplification. The UL transmission of this device is backscattered on an externally provided carrier.

[0145] Peak power consumption ≤ several hundred μW, with energy storage capability, initial SFO up to 10X ppm, and DL and / or UL amplification capabilities. The UL transmission of the device can be generated internally or backscattered on an externally provided carrier.

[0146] The above X will be decided within the work group (WG).

[0147] In some cases, in order to support data transmission from passive device 12, a device in the network needs to support at least one of the following functions.

[0148] :

[0149] The function of the energy source (ES) is only used for passive devices 12 of type B and passive devices 12 of type C.

[0150] The downlink transmission (DT) function sends an indication message to the passive device 12, thereby triggering the uplink transmission of the passive device 12. This function is only used for type A passive devices 12.

[0151] As a continuous wave (CW) function, it is only used for Type A passive devices 12 and Type B passive devices 12. Type A passive devices 12 achieve uplink transmission through backscattered CW. CW is actually also a type of energy storage (ES), and Type A passive devices 12 can receive CW and store energy.

[0152] The uplink receive (UR) function receives D2R messages backscattered by passive device 12, or receives D2R messages actively transmitted by passive device 12, and is only used for passive device 12 of type A.

[0153] It should be noted that the devices that perform the above-mentioned ES, DT, CW, UR and other functions can be terminals, repeaters, relay nodes or network devices, etc.

[0154] In some embodiments, a passive device 12 may support only one of the above functions. Alternatively, a passive device 12 may support only a number of the above functions. Or, a passive device 12 may support only all of the above functions.

[0155] In some embodiments, FIG1H is a schematic diagram of the interaction between a reader and a device in a passive Internet of Things system according to an embodiment of the present disclosure.

[0156] Step S1: The reader sends an inventory command to the device (such as a tag).

[0157] In some embodiments, inventory commands include Query, QueryAdjust, QueryRep, ACK, and NACK.

[0158] In some embodiments, the Query command carries a parameter Q. In one example, the value of parameter Q is between 0 and 15.

[0159] In step S2, after receiving a valid Query command, the device generates a random value (such as RN16) based on the Q value and sends the RN16 back to the reader.

[0160] Step S3: The reader sends an ACK command carrying RN16.

[0161] In some embodiments, the reader generates the same RN16 as RN16 in step S2 and sends the RN16 in the ACK command.

[0162] In step S4, after receiving a valid ACK command, the device backscatters application data to the reader and enters the acknowledgment state.

[0163] In some embodiments, after receiving a valid ACK command carrying the correct RN16, the device sends application data to the reader so that the reader can identify the device. In one example, the application data may include protocol control (PC), EPC, and checksum (CRC).

[0164] In some embodiments, if the device does not receive a valid ACK command or receives an ACK command but the ACK command carries an incorrect RN16, it will not respond.

[0165] In step S5, the reader sends a random number request (such as Req_RN) to the device, wherein Req_RN carries the same RN16 as RN16 in step S2.

[0166] In step S6, after receiving a valid Req_RN, the device sends a handle back to the reader to identify the communication between the reader and the device.

[0167] In some embodiments, if the device does not receive a valid Req_RN or receives a Req_RN but the Req_RN carries an incorrect RN16, it will not respond.

[0168] In step S7, the reader sends a command to access the device.

[0169] In some embodiments, the command carries a handle configured by the reader for the device.

[0170] Step S8: The device verifies the above command.

[0171] In some embodiments, an IoT device can access the network through a random access procedure. Figure 1I is a schematic diagram of a random access procedure for an IoT device according to an embodiment of the present disclosure. As shown in Figure 1I, the random access procedure for an IoT device includes steps S101 to S105.

[0172] In step S101, the network device sends a paging message to the IoT device.

[0173] In some embodiments, the paging message may be triggered by a service request message. In one embodiment, the A-IoT core network (CN) may send a service request message to a network device, and the network device may respond to the service request message by sending a paging message to the IoT device.

[0174] In some embodiments, the network device can be a reader. The IoT device can be a passive device.

[0175] In some embodiments, the network device broadcasts a paging message.

[0176] In some embodiments, the paging message may also be referred to as message 0 (msg0).

[0177] In some embodiments, network devices trigger random access of IoT devices via msg0.

[0178] It should be noted that the term "message" in this disclosure can be replaced with terms such as "information," "signaling," "signaling," or "command." Of course, it can also refer to other transmission forms sent by network devices to IoT devices to perform a certain operation on the IoT devices. This disclosure does not specifically limit this.

[0179] In step S102, the IoT device returns message 1 (msg1) to the network device based on the paging message.

[0180] In some embodiments, after receiving a paging message, the IoT device determines whether random access is required based on the device that needs to respond as indicated in the paging message. If random access is required, the IoT device may send msg1 as a response message to the paging message.

[0181] In some embodiments, msg1 carries an RN16 generated by an IoT device.

[0182] In step S103, the network device sends message 2 (msg2) to the IoT device.

[0183] In some embodiments, after receiving msg1, the network device, based on the successfully received RN16 response msg1, sends msg2, which is a response message to msg1. In one example, msg2 could be referred to as a random access response (RAR) message.

[0184] In some embodiments, msg2 carries RN16.

[0185] In some embodiments, after receiving msg2, the IoT device can respond to msg2 by sending msg3 to the network device.

[0186] In step S104, the IoT device sends message 3 (msg3) to the network device.

[0187] In some embodiments, after receiving msg2, the IoT device can respond to msg2 by sending msg3 to the network device.

[0188] In some embodiments, msg3 may carry RN16 and the device ID of the IoT device.

[0189] In some embodiments, after the IoT device sends msg3 to the network device, the network device does not receive msg3.

[0190] In step S105, the network device sends message 4 (msg4) to the IoT device.

[0191] In some embodiments, if the network device does not receive msg3, it can send msg4 to the IoT device to notify it that msg3 was not received. In one example, msg4 can be a NACK message.

[0192] In some embodiments, the network device sends a NACK message to the IoT device if it does not receive msg3. This can cause the IoT device to spend time determining subsequent actions, increasing communication latency and reducing communication efficiency.

[0193] To address the aforementioned issues, this disclosure provides a communication method, communication device, communication system, storage medium, and program product that can avoid the waiting time caused by uncertainty in subsequent operations in the first device, significantly reduce communication latency, and improve communication efficiency.

[0194] In some embodiments, the first device may be a passive device. In one example, the passive device may be an environmental IoT device.

[0195] In some embodiments, the second device can be a reader of the first device. In one example, the second device can be a base station, an intermediate node or an auxiliary node, or a terminal.

[0196] Figure 2A is an exemplary interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2A, the embodiment of the present disclosure relates to a communication method executed by the aforementioned A-IoT system. In one example, the communication method includes steps S2101 to S2107 of Figure 2A.

[0197] In some embodiments, the second device does not receive message 3 and expects the first device to respond quickly. In this scenario, steps S2101 to S2107 can be performed.

[0198] In one embodiment, the first device sends message 3 to the second device, but the second device does not receive message 3. In one example, the second device may not have received message 3 due to network congestion, unstable transmission links, or other reasons.

[0199] In one embodiment, the first device did not send message 3 to the second device, resulting in the second device not receiving message 3.

[0200] In one example, the first device did not send message 3 as a response to message 2 because it did not receive message 2 sent by the second device, resulting in the second device not receiving message 3.

[0201] In one example, the first device receives message 2 sent by the second device, but may not send message 3 to the second device for some reason, resulting in the second device not receiving message 3.

[0202] In step S2101, the second device sends a first paging message.

[0203] In some embodiments, the second device sends a first paging message. In some embodiments, the first paging message may be sent by the second device, but is not limited thereto, and may also be sent by other entities.

[0204] In some embodiments, the first device receives a first paging message. In some embodiments, the first paging message may be received by the first device, but is not limited thereto, and may also be received by other entities.

[0205] In some embodiments, the first paging message may be triggered by a service request message. In one embodiment, the A-IoT core network may send a service request message to a second device, and the second device, in response to the service request message, sends a first paging message to the first device.

[0206] In some embodiments, the second device broadcasts a first paging message. In one embodiment, the first paging message may be msg0.

[0207] In some embodiments, the first paging message may be triggered by a service request message of a first IoT service. In one embodiment, the A-IoT core network may send a service request message of the first IoT service to a second device, and the second device responds to the service request message by sending the first paging message.

[0208] In some embodiments, the first paging message may carry a service identifier, which may indicate the IoT service (such as a first IoT service) associated with the first paging message. In one example, the service identifier may be the session ID of the first IoT service or the transaction ID of the first IoT service.

[0209] In some embodiments, when the service identifier is service identifier A, service identifier A may also instruct the first device and the second device to establish a connection for the first IoT service through a random access procedure.

[0210] In some embodiments, the first paging message may also carry device identification information, which may indicate the device that needs to respond to the paging message, and may also be referred to as the paged device. In one example, the device identification information may be the device identifier of the device that needs to respond. In one implementation, the device identifier may be assigned by a second device (such as an A-IoT RAN) or by the core network (such as an A-IoT CN). In one embodiment, a device identifier may uniquely identify a device; in other words, the device identifier may be a global identifier.

[0211] In one example, the device identifier can be a temporary identifier (temp-ID), a tag ID (TID), or an electronic product code (EPC).

[0212] In some embodiments, the first paging message may further include device group identification information, which may indicate the device group to which the device requiring a response belongs. In other words, the device group identification information may indicate a group of devices requiring a response. In one example, the device group identification information may be the group identifier of the device group to which the device requiring a response belongs. In some implementations, the group identifier may be assigned by a second device (such as an A-IoT RAN) or by the core network (such as an A-IoT CN). In one embodiment, a group identifier may uniquely identify a device group. This group identifier may be a global identifier.

[0213] In some embodiments, the first paging message may include device identification information and group identification information, thereby indicating a device in one or more device groups that needs to respond. In this case, the device identification information is not a global identifier and cannot uniquely identify a specific device, but rather indicates a specific device within different device groups.

[0214] In some embodiments, the first paging message may not include any identification information; in other words, the first paging message does not include device identification information and / or device group identification information. Thus, the device requiring a response indicated by the first paging message can be one or more devices that received the paging message. In one embodiment, where the first paging message does not include any identification information, the devices requiring a response can be all devices that received the first paging message.

[0215] In some embodiments, the first paging message may include a first field indicating that the devices required to respond are one or more devices that received the paging message. In one example, the first field may be "all".

[0216] In some embodiments, the device requiring a response may be an A-IoT device in a connected state. In some embodiments, the device requiring a response may be an A-IoT device in an idle state. In some embodiments, the device requiring a response may be an A-IoT device in an inactive state.

[0217] In some embodiments, the random access procedure triggered by the first paging message is a contention-based random access procedure.

[0218] In step S2102, the second device sends a first R2D trigger message.

[0219] In some embodiments, after sending the first paging message in step S2101, the second device may also send a first R2D trigger message. In one embodiment, the first R2D trigger message is associated with a first IoT service; in other words, the first R2D trigger message is a first R2D trigger message associated with the first IoT service.

[0220] In some embodiments, the first R2D trigger message is used to instruct the second device to allocate access resources for a device requiring a response to the first IoT service. In one embodiment, the device requiring a response can send message 1 associated with the first IoT service on the access resources. In one embodiment, the access resources can be time-domain resources or frequency-domain resources, and this disclosure does not specifically limit them. In one example, the R2D trigger message can be referred to as a resource indication message, resource boundary indication message, access resource indication message, initial access resource indication message, random access resource indication message, etc., and this disclosure does not specifically limit them.

[0221] In one example, message 1 could be the first message in a random access process triggered by a first paging message, such as msg1 associated with a first IoT service.

[0222] In some embodiments, the first R2D trigger message is used to instruct the responding device and the second device to synchronize. In one example, the first R2D trigger message may be referred to as a synchronization indication message, a resource synchronization indication message, etc., and this disclosure does not specifically limit it.

[0223] In some embodiments, step S2102 is optional and can be omitted.

[0224] In step S2103, the first device sends message 1 to the second device.

[0225] In some embodiments, the first device sends message 1. In some embodiments, message 1 may be sent by the first device, but is not limited thereto, and may also be sent by other entities.

[0226] In some embodiments, the second device receives message 1. In some embodiments, message 1 may be received by the second device, but is not limited thereto, and may also be received by other entities.

[0227] In some embodiments, after receiving a first paging message, the first device determines whether random access is required based on the device that needs to respond, as indicated in the first paging message. In one embodiment, the first device can determine whether it is a device that needs to respond based on its own identification information and the identification information carried in the first paging message. In one embodiment, if the first device is a device that needs to respond, the first device determines to perform random access. If the first device is not a device that needs to respond, the first device determines not to perform random access.

[0228] In some embodiments, the identification information of the first device may be device identification information of the first device, which is locally stored in the first device and is used to identify the first device. In one embodiment, the identification information of the first device may be device group identification information of the device group to which the first device belongs, which is locally stored in the first device and is used to identify the device group to which the first device belongs. In one embodiment, the first device stores both its own device identification information and the device group identification information of the device group to which it belongs.

[0229] In some embodiments, when the first paging message includes device identification information, the first device matches the device identification information included in the first paging message with the device identification information of the first device stored locally to determine whether the first device is a device that needs to respond. In one embodiment, if the two match, such as the device identification information included in the first paging message being the same as the device identification information of the first device stored locally, then the first device is a device that needs to respond. Otherwise, it indicates that the first device is not a device that needs to respond.

[0230] In some embodiments, when the first paging message includes device group identifier information of a device group, the first device matches the device group identifier information included in the first paging message with the device group identifier information of the device group to which the first device belongs, stored locally, to determine whether the first device is a device that needs to respond. In one embodiment, if the two match, such as the device group identifier information included in the first paging message being the same as the device group identifier information of the device group to which the first device belongs, then the first device is a device that needs to respond. Otherwise, it indicates that the first device is not a device that needs to respond.

[0231] In some embodiments, when the first paging message includes device identification information and device group identification information, the first device matches the device identification information included in the first paging message with the device identification information of the first device stored locally, and matches the device group identification information included in the first paging message with the device group identification information of the device group to which the first device belongs stored locally, to determine whether the first device is a device that needs to respond. In one embodiment, if all four match, it indicates that the first device is a device that needs to respond. Otherwise, it indicates that the first device is not a device that needs to respond.

[0232] In some embodiments, after the first device determines to perform random access, it sends message 1 to the second device. In this case, message 1 is the third message.

[0233] In some embodiments, if step S2102 is executed, the first device sends message 1 to the second device on the resource indicated by the first R2D trigger message.

[0234] In some embodiments, message 1 is a response message to the first paging message. In one example, message 1 is a msg1.

[0235] In some embodiments, message 1 carries a first random number to identify the first device. In one embodiment, the first random number can be a 16-bit random number (such as RN16). In another embodiment, the first random number can be randomly generated by the first device.

[0236] In step S2104, the second device sends message 2 to the first device.

[0237] In some embodiments, the second device sends message 2. In some embodiments, message 2 may be sent by the second device, but is not limited thereto, and may also be sent by other entities.

[0238] In some embodiments, the first device receives message 2. In some embodiments, message 2 may be received by the first device, but is not limited thereto, and may also be received by other entities.

[0239] In some embodiments, after receiving message 1, the second device responds to message 1 with a first random number that has been successfully received, and then sends message 2. In one embodiment, message 2 is a response message to message 1. In this case, message 2 is the fourth message.

[0240] In one example, message 2 could be msg2 in the random access process associated with the first IoT service.

[0241] In some embodiments, message 2 carries a first random number. In one embodiment, the first random number in message 2 is the same as the first random number in message 1.

[0242] In some embodiments, after receiving message 2, the first device can compare the first random number in message 2 with a first random number it generates itself to determine whether the competition is resolved. In one embodiment, if the two are the same, the first device determines that the competition is resolved; if the two are different, the first device determines that the competition is not resolved.

[0243] In some embodiments, the first device determines contention resolution, that is, completes the random access procedure and enters the contention-free transmission phase.

[0244] In some embodiments, message 2 carries an access layer identifier (AS ID) assigned by the second device to the first device for the first IoT service. In other words, the access layer identifier is associated with the first IoT service.

[0245] In some embodiments, the access stratum identifier is a globally unique identifier configured by the second device for the first device to perform a random access. In one embodiment, the length of the access stratum identifier is shorter than the length of the device identifier of the first device. The access stratum identifier can be a part of the device identifier of the first device or a new identifier.

[0246] In some embodiments, the access stratum identifier may be carried in the D2R message of the IoT service associated with the paging message and the R2D message of the IoT service associated with the paging message.

[0247] In one embodiment, the access layer identifier assigned by the second device to the first device for the first IoT service can be a first access layer identifier, which uniquely identifies the first device in the session associated with the first IoT service.

[0248] In one example, the first access stratum identifier can reuse the first random number sent by the first device. In another example, the first access stratum identifier can be a new identifier configured by the second device for the first service. Of course, the first access stratum identifier can also be allocated in other ways, and this disclosure does not specifically limit this method.

[0249] In some embodiments, message 2 carries resource information allocated by the second device to the first device for the first IoT service, indicating the resources allocated by the network to the first device. In one embodiment, the first device can send message 3 associated with the first IoT service on the resources indicated by the resource information. In one embodiment, the resource can be a time-domain resource and / or a frequency-domain resource, which is not specifically limited in this disclosure.

[0250] In some embodiments, resources may be allocated to terminals by network devices (such as base stations) in the A-IoT system.

[0251] In some embodiments, message 2 may also carry an access layer identifier associated with the first IoT service, and resource information allocated by the second device to the first device for the first IoT service.

[0252] In some embodiments, after receiving message 2, the first device may locally store the access layer identifier associated with the first IoT service.

[0253] In some embodiments, if the first device does not receive message 2, step S2105 may not be executed. In this case, step S2105 can be omitted. In one embodiment, the first device may not have received message 2 due to network congestion, unstable transmission link, or other reasons.

[0254] In step S2105, the first device sends message 3 to the second device.

[0255] In some embodiments, the first device sends message 3. In some embodiments, message 3 may be sent by the first device, but is not limited thereto, and may also be sent by other entities.

[0256] In some embodiments, the second device receives message 3. In some embodiments, message 3 may be received by the second device, but is not limited thereto, and may also be received by other entities.

[0257] In some embodiments, after receiving message 2, the first device may respond to message 2 by sending message 3 to the second device. In one embodiment, message 3 is a response message to message 2. In other words, message 2 is used to schedule message 3. In this case, message 3 is the second message.

[0258] In one example, message 3 could be msg3 during the random access procedure.

[0259] In some embodiments, message 3 may carry the device identifier of the first device.

[0260] In some embodiments, message 3 may carry a first random number and a device identifier of the first device. In some embodiments, message 3 may carry a first access stratum identifier and a device identifier of the first device.

[0261] In some embodiments, when the second device receives message 3, it can determine the service associated with the continued paging message from the first device (such as a first IoT service). In one embodiment, the second device can send a first command to the first device, the first command being a command associated with the first IoT service. In one example, the first command can be a read, write, lock, or access command, etc., and this disclosure does not specifically limit this.

[0262] In some embodiments, if the second device does not receive message 3, it may perform the following step S2106.

[0263] In step S2106, the second device sends a first message to the first device.

[0264] In some embodiments, the first message may carry first information, which indicates an operation that the second device expects the first device to perform. In one embodiment, the operation that the second device expects the first device to perform may be: the first device sending message 3 to the second device.

[0265] In some embodiments, if the second device does not receive message 3, the second device expects to quickly obtain a response from the first device. In this case, the second device can send a first message to the first device to instruct the first device to send message 3 to the second device. In one example, the first message can be a NACK message, which also serves to notify the second device that message 3 has not been received.

[0266] In some embodiments, if the second device does not receive message 3 within a preset time period, the second device expects to quickly obtain a response from the first device. In this case, the second device can send a first message to the first device to instruct the first device to send message 3 to the second device. The start time of the preset time period is the time when message 3 is sent. In one embodiment, the preset time period can be pre-written into the communication protocol, pre-defined by the second device, or determined through negotiation between the second device and the first device. This disclosure does not specifically limit this aspect.

[0267] In some embodiments, the second device expects the first device to send message 3. The first information may be at least one of resource configuration information, contention resolution indication information, and a first indication information. In one embodiment, the resource configuration information is used to indicate the resources allocated by the network to the first device. In one embodiment, the contention resolution indication information is used to indicate that the contention has been resolved. In one embodiment, the first indication information is used to instruct the first device to send a second message.

[0268] In some embodiments, the first information is resource configuration information, and the first device can send message 3 to the second device on the resource. In one embodiment, the resource can be a time-domain resource and / or a frequency-domain resource, which is not specifically limited in this embodiment.

[0269] In some embodiments, the second device expects the first device to send message 3, but the second device believes that the first device may be unable to determine the resources for sending message 3, and therefore fails to send message 3 successfully. In this case, the first information sent by the second device to the first device may be resource configuration information to indicate to the first device the resources for sending message 3.

[0270] In some embodiments, the second device expects the first device to send message 3. Since the second device has already sent message 2 to the first device, the second device considers the contention to be resolved. In this case, the first message sent by the second device to the first device can be a contention resolution indication message to indicate to the first device that the contention has been resolved, so that the first device can send message 3.

[0271] In some embodiments, the second device expects the first device to send message 3, and the second device may instruct the first device to send message 3. In this case, the first information sent by the second device to the first device may be first instruction information, directly instructing the first device to send message 3.

[0272] In some embodiments, the first information received by the first device is at least one of resource configuration information, contention resolution instruction information, and first instruction information. In this case, the first device determines to send message 3 to the second device.

[0273] In some embodiments, the second device may send a first random number (such as RN16) or a first access stratum identifier to the first device simultaneously with sending the first information. In one example, the first information and the first random number may be carried in the first message.

[0274] In step S2107, the first device sends message 3 to the second device.

[0275] In some embodiments, the first information received by the first device instructs the first device to send message 3 to the second device. In this case, the first device can quickly send message 3 in response to the second device.

[0276] In some embodiments, the first information is resource configuration information, and the first device sends message 3 to the second device.

[0277] In some embodiments, the first information is resource configuration information, and the first device can send message 3 to the second device on the resource indicated by the resource configuration information.

[0278] In some embodiments, the first information is a contention resolution indication information. Based on the contention resolution indication information, the first device can determine that the contention has been resolved. At this time, the first device can send message 3 to the second device.

[0279] In some embodiments, the first information is a first indication information, and the first device sends message 3 to the second device.

[0280] In one embodiment, when the first device receives message 2 through step S2104, the first information is contention resolution instruction information or first instruction information. At this time, the first device can send message 3 to the second device on the resource indicated by the resource information carried in the received message 2.

[0281] In some embodiments, the first information is resource configuration information and contention resolution indication information. The first device can determine that the contention has been resolved based on the contention resolution indication information and send message 3 to the second device on the resource indicated by the resource configuration information.

[0282] In some embodiments, the first information is resource configuration information and first indication information, and the first device can send message 3 to the second device on the resource indicated by the resource configuration information.

[0283] In some embodiments, when step S2105 is executed, the first device has sent message 3 to the second device, but the second device has not received message 3. In this case, the message 3 sent by the first device in step S2107 can be understood as being sent repeatedly.

[0284] In some embodiments, if the first device does not receive message 2, it will be unable to determine the resource for sending message 3. In this case, step S2105 is omitted. In this case, message 3 sent by the first device in step S2107 is the first time it has been sent.

[0285] In some embodiments, the second device expects to quickly receive a response from the first device. The first information instructs the first device to send message 3 to the second device. In this case, after receiving the first message carrying the first information, the first device can quickly send message 3 to respond to the second device. This avoids the additional latency and congestion caused by the first device needing to re-enter random access, significantly reducing communication latency and improving communication efficiency.

[0286] Figure 2B is an exemplary interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2B, the embodiment of the present disclosure relates to a communication method executed by the aforementioned A-IoT system. In one example, the communication method includes steps S2101 to S2105, S2206, and S2207 of Figure 2B.

[0287] In some embodiments, the second device does not receive message 3 and expects the first device not to respond to the R2D message associated with the first IoT service. In this scenario, steps S2101 to S2105 and steps S2206 to S2207 can be performed.

[0288] In step S2101, the second device sends a first paging message.

[0289] In step S2102, the second device sends a first R2D trigger message.

[0290] In step S2103, the first device sends message 1 to the second device.

[0291] In step S2104, the second device sends message 2 to the first device.

[0292] In step S2105, the first device sends message 3 to the second device.

[0293] The optional implementations of steps S2101 to S2105 can be found in the optional implementations of steps S2101 to S2105 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0294] In step S2206, the second device sends a first message to the first device.

[0295] In some embodiments, the first message may carry first information, which indicates an operation that the second device expects the first device to perform. In one embodiment, the operation that the second device expects the first device to perform may be: the first device does not respond to the R2D message associated with the first IoT service.

[0296] In some embodiments, if the second device does not receive message 3, the second device expects the first device not to respond to the R2D message associated with the first IoT service. In this case, the second device can send a first message to the first device to indicate that the first device will not respond to the R2D message associated with the first IoT service. In one example, the first message can be a NACK message, which is also used to notify the second device that message 3 has not been received.

[0297] In some embodiments, if the second device does not receive message 3 within a preset time period, the second device expects the first device not to respond to the R2D message associated with the first IoT service. In this case, the second device can send a first message to the first device to instruct the first device not to respond to the R2D message associated with the first IoT service. The start time of the preset time period is the time when message 3 is sent. In one embodiment, the preset time period can be pre-written into the communication protocol, pre-defined by the second device, or determined through negotiation between the second device and the first device. This disclosure does not specifically limit this.

[0298] In some embodiments, the second device expects the first device not to respond to R2D messages associated with the first IoT service, and the first information can be second indication information. In one embodiment, the second indication information is used to instruct the first device to stop processing the first IoT service.

[0299] In some embodiments, the second device expects the first device not to respond to R2D messages associated with the first IoT service. In this case, the first information sent by the second device to the first device may be a second indication message, indicating that the first device does not respond to R2D messages associated with the first IoT service.

[0300] In some embodiments, the first information received by the first device is the second indication information. In this case, the first device determines not to respond to the R2D message associated with the first IoT service.

[0301] In some embodiments, the second device may send a first random number (such as RN16) or a first access stratum identifier to the first device simultaneously with sending the first information. In one example, the first information and the first random number may be carried in the first message.

[0302] In step S2207, the first device does not respond to the R2D message associated with the first IoT service.

[0303] In some embodiments, the first information received by the first device indicates that the first device should not respond to the R2D message associated with the first IoT service. In this case, the first device may not respond to the R2D message associated with the first IoT service.

[0304] In some embodiments, the first information is a second indication information, and the first device determines not to respond to the R2D message associated with the first IoT service.

[0305] In some embodiments, the second indication information instructs the first device to stop processing the first IoT service. Based on the second indication information, the first device can determine not to respond to the R2D message of the first IoT service. In one embodiment, the first device does not respond to the first message sent by the second device and the subsequently sent first command associated with the first IoT service.

[0306] In some embodiments, if the first device does not respond to the R2D message associated with the first IoT service, the first device may discard the access layer identifier associated with the first IoT service.

[0307] In some embodiments, if the first device does not respond to the R2D message associated with the first IoT service, the first device may discard the first random number associated with the first IoT service.

[0308] In some embodiments, if the first device does not respond to the R2D message associated with the first IoT service, the first device can discard or delete the first random number associated with the first IoT service stored locally. Thus, after the first random number associated with the first IoT service is released, the first device can still associate the first random number with other services, improving resource utilization.

[0309] In some embodiments, when performing step S2105, the first device has already received message 2. In one embodiment, if the first device does not respond to the R2D message associated with the first IoT service, the first device can discard or delete the access layer identifier associated with the first IoT service carried in message 2. Thus, after the access layer identifier associated with the first IoT service is released, the second device can also allocate the access layer identifier to other devices, improving resource utilization.

[0310] In some embodiments, the first device does not respond to the R2D message associated with the first IoT service until it receives a paging message carrying a new service identifier from the second device. Thus, the first device repeats steps S2101 to S2105.

[0311] In some embodiments, the first device can receive a second paging message sent by the second device. The second paging message is associated with a second IoT service, which is different from the first IoT service. After receiving the second paging message, the first device can perform random access based on the second paging message.

[0312] In some embodiments, the first information is used to indicate the operation that the second device expects the first device to perform. Therefore, when the first device receives a first message carrying the first information, it can determine the operation to be performed based on the first information. This avoids the waiting time incurred by the first device due to uncertainty about subsequent operations, significantly reduces communication latency, and improves communication efficiency.

[0313] Figure 2C is an exemplary interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2C, the present disclosure relates to a communication method executed by the aforementioned A-IoT system. In one example, the communication method includes steps S2101 to S2105, S2306, and S2307 of Figure 2C.

[0314] In some embodiments, the second device does not receive message 3 and expects the first device to re-access randomly. In this scenario, steps S2101 to S2105, S2306 and S2307 can be performed.

[0315] In step S2101, the second device sends a first paging message.

[0316] In step S2102, the second device sends a first R2D trigger message.

[0317] In step S2103, the first device sends message 1 to the second device.

[0318] In step S2104, the second device sends message 2 to the first device.

[0319] In step S2105, the first device sends message 3 to the second device.

[0320] The optional implementations of steps S2101 to S2105 can be found in the optional implementations of steps S2101 to S2105 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0321] In step S2306, the second device sends a first message to the first device.

[0322] In some embodiments, the first message may carry first information, which indicates an operation that the second device expects the first device to perform. In one embodiment, the operation that the second device expects the first device to perform may be: the first device re-entering random access.

[0323] In some embodiments, if the second device does not receive message 3, the second device may expect the first device to re-establish random access. In this case, the second device may send a first message to the first device to instruct the first device to re-establish random access. In one example, the first message may be a NACK message, which also serves to notify the second device that message 3 has not been received.

[0324] In some embodiments, if the second device does not receive message 3 within a preset time period, the second device expects the first device to re-establish random access. In this case, the second device may send a first message to the first device to instruct the first device to re-establish random access. The start time of the preset time period is the time when message 3 is sent. In one embodiment, the preset time period may be pre-written into the communication protocol, pre-defined by the second device, or determined through negotiation between the second device and the first device. This disclosure does not specifically limit this aspect.

[0325] In some embodiments, the second device expects the first device to re-enter random access, and the first information can be at least one of a third indication information and a first random number. In one embodiment, the third indication information is used to instruct the first device to re-enter random access.

[0326] In some embodiments, the second device may request the first device to re-establish random access, and the second device may instruct the first device to re-establish random access. In this case, the first information sent by the second device to the first device may be a third instruction, directly instructing the first device to re-establish random access.

[0327] In some embodiments, the second device may request the first device to re-establish random access, and the second device may instruct the first device to re-establish random access. In this case, the first information sent by the second device to the first device may be a first random number to instruct the first device to re-establish random access.

[0328] In some embodiments, the first information received by the first device is at least one of a third indication information and a first random number. In this case, the first device determines to re-perform random access.

[0329] In step S2307, the first device re-enters random access.

[0330] In some embodiments, the first information received by the first device instructs the first device to re-establish random access. In this case, the first device can re-establish random access. In other words, the first device re-establishes a connection with the second device for the first IoT service.

[0331] In some embodiments, the first information is a third indication information, and the first device re-enters random access.

[0332] In some embodiments, the first information is a first random number, and the first device re-accesses the random number.

[0333] In some embodiments, the first information is a third indication information and a first random number, and the first device re-enters random access.

[0334] In some embodiments, if the first device re-accesses randomly, the first device may discard the access layer identifier associated with the first IoT service.

[0335] In some embodiments, if the first device re-accesses the random connection, the first device may discard the first random number associated with the first IoT service.

[0336] In some embodiments, if the first device re-accesses the random network, the first device may discard or delete the first random number associated with the first IoT service stored locally.

[0337] In some embodiments, when performing step S2105, the first device has already received message 2. In one embodiment, if the first device re-accesses randomly, the first device may discard or delete the access layer identifier associated with the first IoT service carried in message 2.

[0338] In some embodiments, the first device may listen for paging messages associated with the first IoT service. In this case, the paging message associated with the first IoT service is the fifth message. Upon detecting a paging message associated with the first IoT service, the first device repeats steps S2101 to S2105.

[0339] In this embodiment of the disclosure, the first information is used to indicate the operation that the second device expects the first device to perform. Therefore, when the first device receives a first message carrying the first information, it can determine the operation to be performed based on the first information. This avoids the waiting time incurred by the first device due to uncertainty about subsequent operations, significantly reduces communication latency, and improves communication efficiency.

[0340] In some embodiments, the terms “passive device,” “environmental IoT device,” “tag,” “electronic tag,” and “IoT device” can be used interchangeably.

[0341] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink".

[0342] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably, as can terms such as “duration,” “segment,” “time window,” “window,” and “time.”

[0343] In some embodiments, the terms "component carrier (CC)," "cell," "frequency carrier," and "carrier frequency" can be used interchangeably.

[0344] In some embodiments, the terms “resource block (RB)”, “physical resource block (PRB)”, “sub-carrier group (SCG)”, “resource element group (REG)”, “PRB pair”, “RB pair”, “resource element (RE)”, and “sub-carrier” can be used interchangeably.

[0345] In some embodiments, the terms “frame”, “radio frame”, “subframe”, “slot”, “sub-slot”, “mini-slot”, “symbol”, “symbol”, and “transmission time interval (TTI)” can be used interchangeably.

[0346] In some embodiments, "acquire," "get," "obtain," "receive," "transmit," "bidirectional transmission," and "send and / or receive" can be used interchangeably and can be interpreted as receiving from other entities, acquiring from protocols, acquiring from higher layers, obtaining through self-processing, or autonomous implementation. Protocols include, for example, at least one of the 3GPP protocol, Wi-Fi protocol, and audio and / or video protocols.

[0347] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0348] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0349] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0350] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data and / or instructions received; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the receiver to respond to the sent content.

[0351] Figure 3 is another exemplary interactive schematic diagram of the communication method shown in this embodiment of the present disclosure. As shown in Figure 3, the communication method includes step S301.

[0352] In step S301, the second device sends a first message to the first device.

[0353] In some embodiments, the first message carries first information, which is used to indicate an operation that the second device expects the first device to perform.

[0354] In some embodiments, the first message is sent by the second device when it has not received the second message, and the second message carries the device identifier of the first device.

[0355] In some embodiments, the first information may be at least one of the following: resource configuration information, used to indicate the resources allocated by the network to the first device; contention resolution indication information, used to indicate that the contention has been resolved; first indication information, used to indicate that the first device sends a second message; second indication information, used to indicate that the first device stops processing the first IoT service; third indication information, used to indicate that the first device re-enters random access; and a first random number, associated with the first IoT service; wherein the first IoT service is the IoT service associated with the second message.

[0356] In some embodiments, the second device expects the first device to perform the operation of sending a second message after receiving a first message, wherein the first message is one of the following: resource configuration information, contention resolution instruction information, or first instruction information.

[0357] In some embodiments, the second device expects the first device to perform an operation that does not respond to the R2D message associated with the first IoT service, where the first information is the second indication information.

[0358] In some embodiments, the second device expects the first device to perform an operation of re-random access, and the first information is one of the following: third indication information, first random number.

[0359] The optional implementations of step S301 can be found in the optional implementations of steps S2101 to S2107 in Figure 2A, steps S2101 to S2105, S2206 and S2207 in Figure 2B, steps S2101 to S2105, S2306 and S2307 in Figure 2C, as well as other related parts in the embodiments involved in Figures 2A, 2B and 2C, which will not be repeated here.

[0360] In the following, specific embodiments of the present disclosure will be described by way of example.

[0361] Solution 1a is provided: If the device does not receive message 2, and the reader does not receive message 3 within the specified time, and the reader wants to quickly obtain the device's response, then:

[0362] The reader carries the device's RN16 in the NACK message, and / or carries the resource configuration for sending subsequent messages. For example, time-domain resources and frequency-domain resources. Upon receiving the NACK message, the device implicitly understands from the resource configuration carried in the message that the reader requests it to resend message 3 on that resource. The device determines that the contention has been resolved and sends message 3 according to the resource configuration of the reader.

[0363] The reader can also carry the device's RN16 in the NACK message, and / or indicate that the contention has been resolved. If the contention has been resolved, the device determines that the contention is resolved and retransmits message 3 using the resources previously used to send message 3.

[0364] Option 1b is provided: If the device receives message 2, but the reader does not receive message 3 within the specified time, and the reader wants to quickly obtain the device's response, then:

[0365] The reader carries the device's RN16 in the NACK message, and / or carries the resource configuration for sending subsequent messages. For example, time-domain resources and frequency-domain resources. After receiving the NACK message, the device implicitly knows from the resource configuration carried in the message that the reader requests it to resend message 3 on that resource. The device determines that the contention has been resolved based on the previously received message 2, and then sends message 3 through the resources configured by the reader according to the NACK message.

[0366] The reader carries the device's RN16 in the NACK message, and / or indicates to continue sending message 3. If message 3 is to be sent again, the device determines that the contention has been resolved based on the previously received message 2, and then resends message 3 using the resources previously used to send message 3.

[0367] Option 2: If the device receives or does not receive message 2, but the reader does not receive message 3 within the specified time, and the reader no longer wants to receive a response from the device, then:

[0368] The reader carries the device's RN16 in the NACK message and / or indicates that the device should no longer process this service. For example, 1 indicates that the service should no longer be processed. If the device receives 1, meaning that the service does not need to be processed, and if the device has already determined that the contention has been resolved based on the previously received message 2, and already has an AS ID or RN16, the device needs to delete the original RN16 or the network-assigned AS ID. The device will no longer respond to subsequent trigger messages for this service until it receives message 0 carrying a new service identifier.

[0369] Option 3a: If the device does not receive message 2, the reader does not receive message 3 within the specified time, and the reader wants the device to re-trigger a contention-based access via message 0, then:

[0370] The reader carries the device's RN16 in the NACK message, and / or indicates that the device needs to re-trigger random access via message 0 to continue the service. For example, message 0 indicates that random access should be re-triggered to continue processing the service. If the device receives message 0, indicating that random access should be re-triggered via message 0 to continue completing the service, the device starts listening for message 0 again. When it receives message 0 carrying the same service identifier, the device re-initiates access.

[0371] Option 3b: If the device receives message 2, but the reader does not receive message 3 within the specified time, and the reader wants the device to re-trigger a contention-based access using message 0, then:

[0372] The reader carries the device's RN16 in the NACK message, and / or indicates that the device needs to re-trigger access via message 0 to continue the service. For example, message 0 indicates that random access should be re-triggered to continue processing the service. If the device receives message 0, indicating that random access should be re-triggered to continue the service, since the device determined that the contention was resolved based on the previously received message 2, the device needs to delete the original RN16 or the network-assigned AS ID, and the device starts listening for message 0 again. When it receives message 0 carrying the same service identifier, the device re-initiates access.

[0373] In the embodiments disclosed herein, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations in other embodiments.

[0374] This disclosure also provides communication devices for implementing any of the above methods. For example, this disclosure provides a communication device including units or modules for implementing the steps performed by the first device in any of the above methods. Furthermore, this disclosure also provides another communication device including units or modules for implementing the steps performed by the second device in any of the above methods.

[0375] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through a configuration file, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0376] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a CPU, microprocessor, graphics processing unit (GPU) (which can be understood as a microprocessor), or digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an ASIC or PLD, such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), tensor processing unit (TPU), deep learning processing unit (DPU), etc.

[0377] Figure 4 is a schematic diagram of the structure of a communication device according to an embodiment of the present disclosure. As shown in Figure 4, the communication device 400 may include a transceiver module 401.

[0378] In some embodiments, the communication device 400 may be a first device. In some embodiments, the transceiver module 401 is configured to receive a first message sent by a second device. The first message carries first information, which is used to indicate an operation that the second device expects the first device to perform. The first message is sent by the second device when it has not received a second message, and the second message carries the device identifier of the first device. Optionally, the transceiver module 401 is configured to perform at least one of the communication steps (e.g., steps S2101, S2102, S2103, S2104, S2105, S2107, S2206, S2306, but not limited thereto) performed by the first device in any of the above methods. Further details are omitted here. Optionally, the communication device 400 may also include a processing module, which is configured to perform at least one of the other steps (e.g., steps S2207, S2307, but not limited thereto) performed by the first device in any of the above methods. Further details are omitted here.

[0379] In some embodiments, the communication device 400 may be a second device. In some embodiments, the transceiver module 401 is configured to send a first message to the first device, the first message carrying first information, the first information being used to indicate an operation that the second device expects the first device to perform; the first message is sent when a second message is not received, and the second message carries the device identifier of the first device. Optionally, the transceiver module 401 is configured to perform at least one of the communication steps (e.g., steps S2101, S2102, S2103, S2104, S2105, S2107, but not limited thereto) performed by the first device in any of the above methods, which will not be elaborated here.

[0380] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.

[0381] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module.

[0382] In some embodiments, the processing module can be replaced by the processor, and the transceiver module can be replaced by the transceiver.

[0383] Figure 5A is a schematic diagram of the structure of a communication device according to an embodiment of this disclosure. The communication device 5100 can be a first device, a second device, a chip, chip system, or processor that supports the first device in implementing any of the above methods, or a chip, chip system, or processor that supports the second device in implementing any of the above methods. The communication device 5100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0384] As shown in Figure 5A, the communication device 5100 is used to execute any of the above methods. In some embodiments, the communication device 5100 includes one or more processors 5101. The processor 5101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 5100 is used to execute any of the above methods. Optionally, one or more processors 5101 are used to invoke instructions to cause the communication device 5100 to execute any of the above methods.

[0385] In some embodiments, the communication device 5100 further includes one or more transceivers 5102. When the communication device 5100 includes one or more transceivers 5102, the transceiver 5102 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S2101, S2102, S2103, S2104, S2105, S2106, S2107, S2206, and S2306, but not limited thereto), and the processor 5101 performs at least one of other steps (e.g., steps S2207 and S2307, but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated together. Optionally, terms such as transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface can be used interchangeably; terms such as transmitter, transmitter unit, transmitter, and transmitter circuit can be used interchangeably; and terms such as receiver, receiver unit, receiver, and receiver circuit can be used interchangeably.

[0386] In some embodiments, the communication device 5100 further includes one or more memories 5103 for storing data and / or instructions. Optionally, one or more processors 5101 are used to invoke instructions stored in the memory 5103 to cause the communication device 5100 to perform any of the above methods. Optionally, all or part of the memory 5103 may also be located outside the communication device 5100. In an optional embodiment, the communication device 5100 may include one or more interface circuits 5104. Optionally, the interface circuit 5104 is connected to the memory 5103 and can be used to receive data and / or instructions from the memory 5103 or other devices, and can be used to send data and / or instructions to the memory 5103 or other devices. For example, the interface circuit 5104 can read data and / or instructions stored in the memory 5103 and send the data and / or instructions to the processor 5101.

[0387] The communication device 5100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 5100 described in this disclosure is not limited thereto, and the structure of the communication device 5100 may not be limited by FIG. 5A. The communication device may be a standalone device or may be part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0388] Figure 5B is a schematic diagram of the chip structure shown in an embodiment of this disclosure. For cases where the communication device 5100 can be a chip or a chip system, please refer to the schematic diagram of the chip 5200 shown in Figure 5B, but it is not limited thereto.

[0389] Chip 5200 includes one or more processors 5201. Chip 5200 is used to perform any of the methods described above.

[0390] In some embodiments, chip 5200 further includes one or more interface circuits 5202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 5200 further includes one or more memories 5203 for storing data and / or instructions. Optionally, all or part of the memories 5203 may be located outside of chip 5200. Optionally, the interface circuit 5202 is connected to the memories 5203, and the interface circuit 5202 can be used to receive data and / or instructions from the memories 5203 or other devices, and the interface circuit 5202 can be used to send data and / or instructions to the memories 5203 or other devices. For example, the interface circuit 5202 can read data and / or instructions stored in the memories 5203 and send the data and / or instructions to the processor 5201.

[0391] In some embodiments, the interface circuit 5202 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., steps S2101, S2102, S2103, S2104, S2105, S2106, S2107, S2206, and S2306, but not limited thereto). The interface circuit 5202 performing the communication steps such as sending and / or receiving in the above-described method refers, for example, to the interface circuit 5202 performing data and / or instruction interaction between the processor 5201, the chip 5200, the memory 5203, or the transceiver device. In some embodiments, the processor 5201 performs at least one of other steps (e.g., steps S2207 and S2307, but not limited thereto).

[0392] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0393] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform any of the methods described above. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0394] This disclosure also provides a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.

[0395] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

[0396] Other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of the invention are indicated by the following claims.

[0397] It should be understood that the present invention is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A communication method, performed by a first device, the method comprising: Receive a first message sent by a second device, the first message carrying first information, the first information being used to indicate the operation that the second device expects the first device to perform; The first message is sent by the second device when it has not received the second message, and the second message carries the device identifier of the first device.

2. The method according to claim 1, wherein, The method further includes: Receive a first paging message sent by the second device, wherein the first paging message is received before the first message, and the first paging message is associated with a first IoT service; Based on the first paging message, a third message is sent to the second device, the third message being used to trigger the second device to send a fourth message, and the fourth message being used to schedule the second message.

3. The method according to claim 1 or 2, wherein, The first information is at least one of the following: Resource configuration information, used to indicate the resources allocated by the network to the first device; Race resolution indication information, used to indicate that a race has been resolved; The first instruction information is used to instruct the first device to send the second message; The second instruction information is used to instruct the first device to stop processing the first IoT service; The third instruction information is used to instruct the first device to re-enter random access; A first random number is associated with a first IoT service; wherein the first IoT service is the IoT service associated with the second message.

4. The method according to claim 3, wherein, The operation is to send a second message after receiving the first message, wherein the first message is one of the following: the resource configuration information, the contention resolution instruction information, or the first instruction information.

5. The method according to claim 4, wherein, The method also includes one of the following: The first information is the resource configuration information, and the second message is sent to the second device; The first information is the contention resolution instruction information, and the second message is sent to the second device; The first information is the first indication information, which is used to send the second message to the second device.

6. The method according to claim 3, wherein, The operation is to not respond to the reader-to-device R2D message associated with the first IoT service, where the first information is the second indication information.

7. The method according to claim 6, wherein, The method further includes: The first information is the second indication information, which determines that the R2D message associated with the first IoT service will not be responded to.

8. The method according to claim 6 or 7, wherein, The method further includes: Receive a second paging message sent by the second device, the second paging message being associated with a second IoT service, the second IoT service being different from the first IoT service; Random access is performed based on the second paging message.

9. The method according to claim 3, wherein, The operation is to re-randomly access the system, and the first information is one of the following: the third indication information, or the first random number.

10. The method according to claim 9, wherein, The method also includes one of the following: The first information is the third indication information, and random access is performed again; The first information is the first random number, and a new random access is performed.

11. The method according to claim 10, wherein, The re-random access procedure includes: Listen for a fifth message, which is used to trigger the first device to perform random access, and the fifth message is associated with the first IoT service.

12. The method according to any one of claims 6 to 11, wherein, The method also includes one of the following: Discard the access layer identifier associated with the first IoT service, which is carried in the device-to-reader (D2R) message and the R2D message associated with the first IoT service. Discard the first random number associated with the first IoT service.

13. A communication method performed by a second device, the method comprising: Send a first message to the first device, the first message carrying first information, the first information being used to indicate the operation that the second device expects the first device to perform; The first message is sent before the second message is received, and the second message carries the device identifier of the first device.

14. The method according to claim 13, wherein, The method further includes: Send a first paging message to the first device. The first paging message is sent before the first message and is associated with the first IoT service. Receive a third message sent by the first device, wherein the third message is a response message to the first paging message; Based on the third message, a fourth message is sent to the first device, the fourth message being used to schedule the second message.

15. The method according to claim 13 or 14, wherein, The first information is at least one of the following: Resource configuration information, used to indicate the resources allocated by the network to the first device; Race resolution indication information, used to indicate that a race has been resolved; The first instruction information is used to instruct the first device to send the second message; The second instruction information is used to instruct the first device to stop processing the first IoT service; The third instruction information is used to instruct the first device to re-enter random access; The first random number is associated with the first IoT business; The first IoT service is the IoT service associated with the second message.

16. The method according to claim 15, wherein, The operation is to send a second message after receiving the first message, wherein the first message is one of the following: the resource configuration information, the contention resolution instruction information, or the first instruction information.

17. The method according to claim 16, wherein, The method further includes: The first information is the resource configuration information, and the second message sent by the first device is received; The first information is the contention resolution indication information, and the second message sent by the first device is received; The first information is the first indication information, and the second message sent by the first device is received.

18. The method according to claim 15, wherein, The operation is to not respond to the reader-to-device R2D message associated with the first IoT service, where the first information is the second indication information.

19. The method according to claim 18, wherein, The method further includes: A second paging message is sent to the first device. The second paging message is used to trigger the first device to perform random access. The second paging message is associated with a second Internet of Things (IoT) service, which is different from the first IoT service.

20. The method of claim 15, wherein, The operation is to re-randomly access the system, and the first information is one of the following: the third indication information, or the first random number.

21. The method according to claim 20, wherein, The method further includes: A fifth message is sent to the first device, the fifth message being used to trigger the first device to perform random access, and the fifth message being associated with the first IoT service.

22. A communication method, wherein the communication device is used to perform the communication method according to any one of claims 1 to 12, 13 to 21.

23. A communication system comprising a first device and a second device, the first device being configured to implement the communication method of any one of claims 1 to 12, and the second device being configured to implement the communication method of any one of claims 13 to 21.

24. A storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the communication method as described in any one of claims 1 to 12, 13 to 21.

25. A program product comprising at least one of a program and instructions, wherein the program and instructions, when executed by a communication device, implement the steps of the communication method according to any one of claims 1 to 12, 13 to 21.

Images