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

Abstract

The present disclosure relates to a communication method, a communication apparatus, a communication device and a storage medium. The method comprises: receiving an R2D PDU sent by a second device, wherein the R2D PDU carries first information and command-related information of a plurality of devices, the first information is used for determining the position of the command-related information of each device in the R2D PDU, and the command-related information of each device is used for indicating an R2D command configuration of each device. The present disclosure implements R2D PDU multiplexing, reduces signaling overheads, increases the utilization rate of resources, and improves system performance.

Description

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

[0001] This disclosure relates to the field of wireless 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 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, and cannot meet the needs in some scenarios. Therefore, ambient energy-enabled IoT technologies have been 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

[0003] How to achieve the multiplexing of reader-to-device (R2D) protocol data units (PDUs) is a technical problem that needs to be solved.

[0004] According to a first aspect of the present disclosure, a communication method is provided, performed by a first device, the method comprising: receiving an R2D PDU sent by a second device, the R2D PDU carrying first information and command-related information of a plurality of devices, the first information being used to determine the position of the command-related information of each device in the R2D PDU, and the command-related information of each device being used to indicate the R2D command configuration of each device.

[0005] According to a second aspect of the present disclosure, a data transmission method is provided, performed by a second device, the method comprising: sending an R2D PDU to a first device, the R2D PDU carrying first information and command-related information of a plurality of devices, the first information being used to determine the position of the command-related information of each device in the R2D PDU, and the command-related information of each device being used to indicate the R2D command configuration of each device.

[0006] According to a third aspect of the present disclosure, a communication method is provided, executed by a communication system including a first device and a second device; the method includes: the second device sending an R2D PDU to the first device, the R2D PDU carrying first information and command-related information of multiple devices, the first information being used to determine the position of the command-related information of each device in the R2D PDU, and the command-related information of each device being used to indicate the R2D command configuration of each device.

[0007] According to a fourth aspect of the present disclosure, a communication device, such as a first device, is provided, comprising: a transceiver module for receiving an R2D PDU sent by a second device, the R2D PDU carrying first information and command-related information of multiple devices, the first information being used to determine the position of the command-related information of each device in the R2D PDU, and the command-related information of each device being used to indicate the R2D command configuration of each device.

[0008] According to a fifth aspect of the present disclosure, a communication device, such as a second device, is provided, comprising: a transceiver module for sending an R2D PDU to a first device, the R2D PDU carrying first information and command-related information of a plurality of devices, the first information being used to determine the position of the command-related information of each device in the R2D PDU, and the command-related information of each device being used to indicate the R2D command configuration of each device.

[0009] According to a sixth aspect of the present disclosure, a communication device, such as a first device or a second device, is provided, comprising: one or more processors; one or more memories for storing a computer program; wherein the processor executes the computer program to implement the communication method described in either the first aspect or the second aspect.

[0010] According to a seventh aspect of the present disclosure, a communication system is provided, comprising a first device and a second device. The first device performs the communication method as described in the first aspect; the second device performs the communication method as described in the second aspect.

[0011] According to an eighth 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 communication method described in either the first or second aspect.

[0012] According to a ninth aspect of the present disclosure, a computer program product is provided, including a computer program that, when executed by a processor, implements the communication method described in either the first or second aspect.

[0013] According to a tenth aspect of the present disclosure, a computer program is provided, the computer program including code that, when executed by a processor, implements the communication method described in either the first aspect or the second aspect.

[0014] The technical solutions provided in this disclosure enable the reuse of R2D PDUs, reduce signaling overhead, improve resource utilization, and enhance system performance.

[0015] The above general description and the following detailed description are exemplary and explanatory only, and do not constitute a limitation on the embodiments of this disclosure. Attached Figure Description

[0016] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.

[0017] Figure 1A is a schematic diagram of an 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 a passive Internet of Things system according to an embodiment of the present disclosure.

[0020] Figure 1D is a schematic diagram of another architecture of a passive Internet of Things system according to an embodiment of the present disclosure.

[0021] Figure 1E is a schematic diagram of another architecture of a passive Internet of Things system according to an embodiment of the present disclosure.

[0022] Figure 1F is a schematic diagram of another architecture of a passive Internet of Things system according to an embodiment of the present disclosure.

[0023] Figure 1G is a schematic diagram illustrating different types of environmental IoT devices according to embodiments of the present disclosure.

[0024] Figure 1H 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.

[0025] Figure 1I shows a schematic diagram of an R2D PDU according to an embodiment of the present disclosure.

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

[0027] Figure 3A is an example diagram of an R2D PDU according to an embodiment of the present disclosure.

[0028] Figure 3B is an example diagram of an R2D PDU according to an embodiment of the present disclosure.

[0029] Figure 3C is an example diagram of an R2D PDU according to an embodiment of the present disclosure.

[0030] Figure 3D is an example diagram of an R2D PDU according to an embodiment of the present disclosure.

[0031] Figure 4 is an exemplary interaction diagram of a communication method according to an embodiment of the present disclosure.

[0032] Figure 5 is a schematic diagram of a communication device provided according to an embodiment of the present disclosure.

[0033] Figure 6A is a schematic diagram of a communication device provided according to an embodiment of the present disclosure.

[0034] Figure 6B is a schematic diagram of a chip structure provided according to an embodiment of the present disclosure. Detailed Implementation

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

[0036] In a first aspect, embodiments of this disclosure provide a communication method executed by a first device. The method includes: receiving an R2D PDU sent by a second device. The R2D PDU carries first information and command-related information of multiple devices. The first information is used to determine the position of the command-related information of each device in the R2D PDU, and the command-related information of each device is used to indicate the R2D command configuration of each device.

[0037] In this embodiment of the disclosure, the R2D PDU carries command-related information of multiple devices and first information indicating the location of these command-related information in the R2D PDU. This allows the first device to determine its own command-related information in the R2D PDU based on the first information, thereby decoding the command sent to the first device by the second device. In this way, the R2D PDU is reused, signaling overhead is reduced, resource utilization is improved, and system performance is enhanced.

[0038] In conjunction with some embodiments of the first aspect, in some embodiments, the first information includes multiple identification information, each identification information being used to indicate one of the multiple devices, different identification information indicating different devices, and command-related information for each device being associated with the identification information indicating each device.

[0039] In conjunction with some embodiments of the first aspect, in some embodiments, multiple identification information is carried in a first field of the R2D PDU, and multiple device command-related information is carried in a second field of the R2D PDU. The position of the multiple device command-related information in the second field is set according to the order of the multiple identification information in the first field.

[0040] In conjunction with some embodiments of the first aspect, in some embodiments, the first information further includes quantity information, which is used to indicate the quantity of multiple identification information.

[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the first information further includes a plurality of first indication information, each first indication information being associated with one of the plurality of identification information, the identification information associated with different first indication information being different, and each first indication information being used to indicate the starting position of the command-related information of the device indicated by the associated identification information in the second field.

[0042] In conjunction with some embodiments of the first aspect, in some embodiments, multiple first indication information is carried in a first field, and each identification information is adjacent to the first indication information associated with each identification information.

[0043] In conjunction with some embodiments of the first aspect, in some embodiments, multiple first indication information is carried in a first field, the multiple first indication information is located after multiple identification information in the first field, and the multiple first indication information is set sequentially in the first field according to the order of the multiple identification information in the first field.

[0044] In conjunction with some embodiments of the first aspect, in some embodiments, each identification information is adjacent to the command-related information associated with each identification information.

[0045] In conjunction with some embodiments of the first aspect, in some embodiments, a second indication is set after the command-related information associated with each identification information, the second indication being used to indicate the end of the command-related information associated with each identification information.

[0046] In conjunction with some embodiments of the first aspect, in some embodiments, the command-related information includes at least one of the following: command type, used to indicate the class of the R2D command; command length, used to indicate the length of the command container; and command container, used to hold the R2D command.

[0047] In conjunction with some embodiments of the first aspect, in some embodiments, the R2D PDU further includes second information for indicating that the type of the R2DPDU is R2D data.

[0048] Secondly, embodiments of this disclosure provide a communication method executed by a second device. The method includes sending an R2D PDU to a first device. The R2D PDU carries first information and command-related information of multiple devices. The first information is used to determine the position of the command-related information of each device in the R2D PDU, and the command-related information of each device is used to indicate the R2D command configuration of each device.

[0049] In this embodiment of the disclosure, the R2D PDU carries command-related information of multiple devices and first information indicating the location of these command-related information in the R2D PDU. This allows the first device to determine its own command-related information in the R2D PDU based on the first information, thereby decoding the command sent to the first device by the second device. In this way, the R2D PDU is reused, signaling overhead is reduced, resource utilization is improved, and system performance is enhanced.

[0050] In conjunction with some embodiments of the second aspect, in some embodiments, the first information includes multiple identification information, each identification information is used to indicate one of the multiple devices, different identification information indicates different devices, and the command-related information of each device is associated with the identification information indicating each device.

[0051] In conjunction with some embodiments of the second aspect, in some embodiments, multiple identification information is carried in a first field of the R2D PDU, and multiple device command-related information is carried in a second field of the R2D PDU. The position of the multiple device command-related information in the second field is set according to the order of the multiple identification information in the first field.

[0052] In conjunction with some embodiments of the second aspect, in some embodiments, the first information further includes quantity information, which is used to indicate the quantity of multiple identification information.

[0053] In conjunction with some embodiments of the second aspect, in some embodiments, the first information further includes a plurality of first indication information, each first indication information being associated with one of the plurality of identification information, the identification information associated with different first indication information being different, and each first indication information being used to indicate the starting position of the command-related information of the device indicated by the associated identification information in the second field.

[0054] In conjunction with some embodiments of the second aspect, in some embodiments, multiple first indication information is carried in a first field, and each identification information is adjacent to the first indication information associated with each identification information.

[0055] In conjunction with some embodiments of the second aspect, in some embodiments, multiple first indication information is carried in a first field, the multiple first indication information is located after multiple identification information in the first field, and the multiple first indication information is set sequentially in the first field according to the order of the multiple identification information in the first field.

[0056] In conjunction with some embodiments of the second aspect, in some embodiments, a second indication is set after the command-related information associated with each identification information, the second indication being used to indicate the end of the command-related information associated with each identification information.

[0057] In conjunction with some embodiments of the second aspect, in some embodiments, the command-related information includes at least one of the following: command type, used to indicate the class of the R2D command; command length, used to indicate the length of the command container; and command container, used to hold the R2D command.

[0058] In conjunction with some embodiments of the second aspect, in some embodiments, the R2D PDU further includes second information for indicating that the type of the R2DPDU is R2D data.

[0059] Thirdly, embodiments of this disclosure provide a communication device, such as a first device. The communication device includes a transceiver module configured to receive an R2D PDU sent by a second device. The R2D PDU carries first information and command-related information of multiple devices. The first information is used to determine the position of the command-related information of each device in the R2D PDU, and the command-related information of each device is used to indicate the R2D command configuration of each device.

[0060] In conjunction with some embodiments of the third aspect, in some embodiments, the first information includes multiple identification information, each identification information is used to indicate one of the multiple devices, different identification information indicates different devices, and the command-related information of each device is associated with the identification information indicating each device.

[0061] In conjunction with some embodiments of the third aspect, in some embodiments, multiple identification information is carried in a first field of the R2D PDU, and multiple device command-related information is carried in a second field of the R2D PDU. The position of the multiple device command-related information in the second field is set according to the order of the multiple identification information in the first field.

[0062] In conjunction with some embodiments of the third aspect, in some embodiments, the first information further includes quantity information, which is used to indicate the quantity of multiple identification information.

[0063] In conjunction with some embodiments of the third aspect, in some embodiments, the first information further includes a plurality of first indication information, each first indication information being associated with one of the plurality of identification information, the identification information associated with different first indication information being different, and each first indication information being used to indicate the starting position of the command-related information of the device indicated by the associated identification information in the second field.

[0064] In conjunction with some embodiments of the third aspect, in some embodiments, multiple first indication information is carried in a first field, and each identification information is adjacent to the first indication information associated with each identification information.

[0065] In conjunction with some embodiments of the third aspect, in some embodiments, multiple first indication information is carried in a first field, the multiple first indication information is located after multiple identification information in the first field, and the multiple first indication information is set sequentially in the first field according to the order of the multiple identification information in the first field.

[0066] In conjunction with some embodiments of the third aspect, in some embodiments, each identification information is adjacent to the command-related information associated with each identification information.

[0067] In conjunction with some embodiments of the third aspect, in some embodiments, a second indication is set after the command-related information associated with each identification information, the second indication being used to indicate the end of the command-related information associated with each identification information.

[0068] In conjunction with some embodiments of the third aspect, in some embodiments, the command-related information includes at least one of the following: command type, used to indicate the class of the R2D command; command length, used to indicate the length of the command container; and command container, used to hold the R2D command.

[0069] In conjunction with some embodiments of the third aspect, in some embodiments, the R2D PDU further includes second information for indicating that the type of the R2DPDU is R2D data.

[0070] Fourthly, embodiments of this disclosure provide a communication device, such as a second device. The communication device includes a transceiver module configured to send an R2D PDU to a first device. The R2D PDU carries first information and command-related information for multiple devices. The first information is used to determine the position of the command-related information for each device in the R2D PDU, and the command-related information for each device is used to indicate the R2D command configuration for each device.

[0071] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first information includes multiple identification information, each identification information being used to indicate one of the multiple devices, different identification information indicating different devices, and the command-related information of each device being associated with the identification information indicating each device.

[0072] In conjunction with some embodiments of the fourth aspect, in some embodiments, multiple identification information is carried in a first field of the R2D PDU, and multiple device command-related information is carried in a second field of the R2D PDU. The position of the multiple device command-related information in the second field is set according to the order of the multiple identification information in the first field.

[0073] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first information further includes quantity information, which is used to indicate the quantity of multiple identification information.

[0074] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first information further includes a plurality of first indication information, each first indication information being associated with one of the plurality of identification information, the identification information associated with different first indication information being different, and each first indication information being used to indicate the starting position of the command-related information of the device indicated by the associated identification information in the second field.

[0075] In conjunction with some embodiments of the fourth aspect, in some embodiments, multiple first indication information is carried in a first field, and each identification information is adjacent to the first indication information associated with each identification information.

[0076] In conjunction with some embodiments of the fourth aspect, in some embodiments, multiple first indication information is carried in a first field, the multiple first indication information is located after multiple identification information in the first field, and the multiple first indication information is set sequentially in the first field according to the order of the multiple identification information in the first field.

[0077] In conjunction with some embodiments of the fourth aspect, in some embodiments, a second indication is set after the command-related information associated with each identification information, the second indication being used to indicate the end of the command-related information associated with each identification information.

[0078] In conjunction with some embodiments of the fourth aspect, in some embodiments, the command-related information includes at least one of the following: command type, used to indicate the class of the R2D command; command length, used to indicate the length of the command container; and command container, used to hold the R2D command.

[0079] In conjunction with some embodiments of the fourth aspect, in some embodiments, the R2D PDU further includes second information for indicating that the type of the R2DPDU is R2D data.

[0080] Fifthly, embodiments of this disclosure provide a communication method executed by a communication system, the communication system including a first device and a second device. The communication method includes: the second device sending an R2D PDU to the first device, the R2D PDU carrying first information and command-related information of multiple devices, the first information being used to determine the location of the command-related information of each device in the R2D PDU, and the command-related information of each device being used to indicate the R2D command configuration of each device.

[0081] In a sixth aspect, embodiments of this disclosure provide a communication device, comprising: one or more processors; one or more memories for storing a computer program; wherein the processor executes the computer program to implement the steps of the method described in any of the first aspect, the second aspect, and their possible implementations.

[0082] In a seventh aspect, embodiments of this disclosure provide a communication system including a first device and a second device. The first device performing the communication method includes: the first device performing the communication method as described in any one of the first aspects and their possible embodiments; and the second device performing the communication method as described in any one of the second aspects and their possible embodiments.

[0083] Eighthly, 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 communication method as described in any one of the first aspect, the second aspect, and their possible implementations.

[0084] In a ninth aspect, embodiments of this disclosure provide a computer program product, including a computer program that, when executed by a processor, implements the communication method described in any one of the first aspect, the second aspect, and their possible implementations.

[0085] In a tenth aspect, embodiments of this disclosure provide a computer program including code that, when executed by a processor, implements the communication method described in any one of the first aspect, the second aspect, and their possible implementations.

[0086] Eleventhly, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the communication method described in any one of the first aspect, the second aspect, and their possible implementations.

[0087] It is understood that the aforementioned communication devices, communication equipment, computer-readable storage media, computer program products, and computer programs are all used to perform 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, a communication device, a communication equipment, a communication system, a storage medium, and a program product. In some embodiments, terms such as communication method, information transmission method, and information processing method can be used interchangeably. Terms such as communication device, information transmission device, and information processing device can be used interchangeably. Terms such as information transmission system, communication system, and information processing 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 contradictory, 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 implementations 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. As another example, a particular embodiment can be arbitrarily combined with optional implementations of other embodiments.

[0090] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0091] 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.

[0092] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the aforementioned," "this," etc., can mean "one and only one," or "one or more," "multiple," 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.

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

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

[0095] 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 B); in some embodiments, B (execute B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, A and B (both A and B are executed). The same applies when there are more branches such as A, B, C, etc.

[0096] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execution of A regardless of B); in some embodiments, B (execution of B regardless of A); 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, C, etc.

[0097] 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. As another example, if the object being described is "information", then "first information" and "quantity information" can be the same information or different information, and their content can be the same or different.

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

[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 the 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," "access node," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femtocell," "picocell," "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 with 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 with 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. Sidelink can also be replaced with sidelink.

[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 with 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] As shown in Figure 1A, Figure 1A is a schematic diagram of an architecture of a communication system according to an embodiment of the present disclosure. The communication system 100 includes a terminal 101 and a network device 102. In one example, 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 outside of 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 can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a 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, ambient energy-enabled IoT devices are passive devices powered by harvested energy. These IoT devices are battery-free or have limited energy storage capacity (e.g., the device uses capacitors). In some embodiments, ambient energy-enabled IoT devices can power themselves 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 terms “ambient energy-enabled IoT device”, “passive device”, “passive IoT device”, “ambient energy-based device”, “ambient IoT device”, and “tag” can be used interchangeably.

[0123] In some embodiments, environmentally friendly IoT devices (such as ambient IoT devices) can use energy harvested from the environment to power their data transmission and wireless communication. Currently, 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 an environmental IoT device 12. When the radio frequency signal reaches the environmental IoT device 12, a portion is reflected. The environmental IoT 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. Therefore, it simplifies the design of the aforementioned environmentally friendly IoT devices and significantly reduces device costs.

[0125] In some embodiments, the radio frequency signal is used to provide energy for the IoT device in the aforementioned environment 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 can be a reader of an environmental IoT device or an anchor point of the reader.

[0127] In some embodiments, when passive Internet of Things (IoT) technology is integrated into the communication system 100 described above, the present disclosure embodiments may provide, but are not limited to, the following architectures of the communication system 100 (also referred to as an IoT system):

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

[0129] Architecture 2: As shown in Figure 1D, Figure 1D is a schematic diagram of another architecture of an Internet of Things (IoT) system according to an embodiment of this disclosure. The IoT device 12 and the network device 20 (such as a base station) indirectly transmit uplink and / or downlink data through an intermediate node 30.

[0130] 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.

[0131] Architecture 3: As shown in Figure 1E, Figure 1E is a schematic diagram of another architecture of an Internet of Things (IoT) system according to an embodiment of this disclosure. The IoT 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.

[0132] 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.

[0133] Architecture 4: As shown in Figure 1F, Figure 1F is a schematic diagram of another architecture of the Internet of Things (IoT) system according to an embodiment of this disclosure. Uplink and downlink transmissions are directly performed between the environmental IoT device 12 and the terminal 50. The terminal 50 is responsible for collecting data from the environmental IoT device 12 and forwarding the collected data to the network side.

[0134] In some embodiments, when the IoT system communicates using Architecture 1 and Architecture 2 as described above, 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.

[0135] It should be noted that the terms "Internet of Things system", "radio frequency identification (RFID) system", "passive Internet of Things system", and "environmental Internet of Things system" mentioned above are interchangeable.

[0136] In some embodiments, as shown in FIG1G, FIG1G is a schematic diagram illustrating different types of environmental IoT devices according to embodiments of the present disclosure. The aforementioned environmental IoT devices can be, but are not limited to, the following three types:

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

[0138] Type B: Features energy storage but lacks independent signal generation, transmitting data based on backscattering. The energy stored in environmental IoT devices can be used to amplify the backscattered signal.

[0139] Type C: Features energy storage and independent signal generation, and uses active radio frequency components for transmission.

[0140] In some cases, to support data transmission from passive devices, a device in a network needs to support at least one of the following functions:

[0141] The function of serving as an energy source (ES) is only applicable to Type B and Type C devices;

[0142] The Downlink Transmission (DT) function sends an indication message to a passive device, thereby triggering an uplink transmission on the passive device. It is only used for Type A devices.

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

[0144] The uplink receive (UR) function receives uplink information backscattered by a passive device or receives uplink information actively transmitted by a passive device. It is only used for Type A devices.

[0145] 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.

[0146] In some embodiments, an environmental IoT device may support only one of the above functions. Alternatively, an environmental IoT device may support multiple of the above functions. Or, an environmental IoT device may support all of the above functions.

[0147] In some embodiments, from a functional perspective, RFID communication systems are divided into three categories: tag selection, inventory, and access commands.

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

[0149] In some embodiments, the command for selecting a class includes two options: select and challenge.

[0150] In some embodiments, access commands include random number request (Req_RN), read, write, kill, lock, access, blockwrite, and blockerase.

[0151] 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. As shown in FIG1H, the interaction process between the reader and the device is as follows:

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

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

[0154] 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.

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

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

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

[0158] 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), electronic product code (EPC), and checksum (CRC).

[0159] 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.

[0160] 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.

[0161] 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.

[0162] 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.

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

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

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

[0166] In some embodiments, the reader carries messages and commands sent to various devices via R2D PDUs. In one embodiment, three reader-to-device PDU types are defined: paging / R2D trigger messages, msg2, and R2D data. In one embodiment, when the R2D PDU type is R2D data, the command (which may be referred to as an R2D command) sent by the reader to the device is carried within the R2D PDU.

[0167] In some embodiments, R2D commands may include select commands, inventory commands, and access commands.

[0168] In some embodiments, FIG1I is a schematic diagram of an R2D PDU according to an embodiment of the present disclosure. As shown in FIG1I, an R2DPDU includes a "protocol version (PV)" field, a "PDU type (PDU type)" field, an "identifier (RN16)" field, a "command type (CMD type)" field, a "command length (CMD length)" field, and a "command container (CMD container)".

[0169] In some embodiments, the "PV" field indicates the protocol version currently in use.

[0170] In some embodiments, the "PDU type" field indicates the type of R2D PDU and occupies 2 bits. For example, if the "PDU type" field is 0, the type of R2D PDU is a paging message; if the "PDU type" field is 1, the type of R2D PDU is message 2; if the "PDU type" field is 2, the type of R2D PDU is retrieval R2D data; and if the "PDU type" field is 3, the type of R2D PDU is a reserved type.

[0171] In some embodiments, the "RN16" field indicates the device receiving the R2D PDU. In one embodiment, different RN16 fields indicate different devices; that is, one RN16 can uniquely identify one device. Therefore, in the R2D PDU, one "RN16" field corresponds to one device.

[0172] In one embodiment, the “RN16” field can also be replaced with the “Access Layer Identifier (AS ID)” field.

[0173] In some embodiments, the "CMD type" field, "CMD length" field, and "CMD container" field respectively indicate information related to the R2D command sent by the reader. These fields can then be combined into a "command-related information" field. In one embodiment, the "CMD type" field indicates the class of the R2D command; for example, the "CMD type" field indicates that the R2D command is a select command, an inventory command, or an access command. In one embodiment, the "CMD length" field indicates the length of the R2D command. For example, the number of bits occupied by the R2D command can also indicate the length of the "CMD container" field. In one embodiment, the "CMD container" field carries the R2D command. In some embodiments, the "command-related information" field may include the "CMD container" field, and may also include at least one of the "CMD type" field and the "CMD length" field. Of course, the "command-related information" field may also include other fields, and this disclosure does not specifically limit this.

[0174] In some embodiments, the "CMD type" field can also indicate the name of the R2D command, that is, the name of the R2D command carried in the "CMD container" field, such as any of the following commands: Query, QueryAdjust, QueryRep, ACK, NACK, select, challenge, Req_RN, read, write, kill, lock, access, blockwrite, and blockerase.

[0175] Therefore, it is evident that a single R2D PDU can typically only carry R2D commands from one device (as shown in Figure 1I), which leads to resource waste and low communication efficiency. Thus, how to achieve R2D PDU reuse is a technical problem that needs to be solved.

[0176] To address the aforementioned issues, embodiments of this disclosure provide a communication method, communication device, communication equipment, communication system, storage medium, and program product to achieve R2D PDU reuse, reduce signaling overhead, improve resource utilization, and enhance system performance.

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

[0178] In some embodiments, the second device can be the excitation source for the first device. In one example, the second device is a reader for an environmental IoT device.

[0179] In some embodiments, the second device may be a base station, an intermediate node or an auxiliary node, or a terminal.

[0180] It should be noted that the term "command" in the embodiments of this disclosure can be replaced by terms such as "signaling", "signaling", "information", "message", and "packet data unit (PDU)".

[0181] As shown in Figure 2, Figure 2 is an exemplary interaction diagram illustrating a communication method according to an embodiment of the present disclosure. This disclosure relates to a communication method performed by the aforementioned passive Internet of Things (IoT) system. The communication method includes steps S201 and S202.

[0182] In step S201, the second device sends an R2D PDU to the first device.

[0183] In some embodiments, the second device broadcasts an R2D PDU, and the first device receives the R2D PDU. In one example, the R2D PDU can be a medium access control (MAC) PDU, in which case the R2D PDU can be an R2D MAC PDU.

[0184] In some embodiments, the R2D PDU may carry second information indicating the type of the R2D PDU. In this case, the second information indicates that the type of the R2D PDU is R2D data. In one example, the second information may be a "PDU type" field with a value of 2.

[0185] In some embodiments, the R2D PDU carries first information and command-related information for multiple devices.

[0186] In some embodiments, the first information is used to indicate the location of each device's command-related information in the R2D PDU, so that the device can decode its own command-related information at the corresponding location according to the indication of the first information.

[0187] In some embodiments, the first information may include multiple identification information, each identifying a device. Then, command-related information for a device can be associated with the identification information indicating that device. In this case, the location of command-related information for multiple devices in the R2D PDU can be determined by the location of these device identification information in the R2D PDU.

[0188] In some embodiments, the identification information described above may be a temporary identifier for the device. In one embodiment, the identification information may be randomly generated by the device during the access process (such as RN16) or configured by the network side (such as AS ID).

[0189] In some embodiments, the command-related information of each device can indicate the R2D command configuration sent by the second device to each device. In one embodiment, since the R2D commands sent by the second device to each device can be the same or different commands, the R2D configuration indicated by the command-related information of multiple devices can be the same or different, and thus the command-related information of multiple devices can be the same or different.

[0190] In some embodiments, the device's command-related information indicates the device's R2D command configuration. In one example, the device's command-related information may include at least one of the following: command type, command length, and command container. Wherein, CMD type indicates the class of the R2D command, for example, a select command, an inventory command, or an access command. CMD length indicates the length of the CMD container. The CMD container holds the R2D command.

[0191] In one example, identification information can be carried in the "RN16" field, and command-related information for the device can be carried in the "Command-Related Information" field. The "RN16" field, which carries identification information for a device, is associated with the device's "Command-Related Information" field; that is, the "RN16" field is associated with the "Command-Related Information" field one-to-one.

[0192] In some embodiments, multiple identification information items can be centrally stored in the R2D PDU, and command-related information items for multiple devices can also be centrally stored in the R2D PDU. In one embodiment, the R2D PDU may include a first field and a second field, with multiple identification information items carried in the first field and command-related information items for multiple devices carried in the second field. In the second field, the command-related information items for multiple devices can be set in the order of the multiple identification information items in the first field.

[0193] In some embodiments, multiple identification information items are carried in the first field, where the first field can be understood as a list of identification information items. In one example, the first field may include multiple "RN16" fields, each carrying one identification information item. In this case, the first field can also be referred to as the "identification information list" field.

[0194] In some embodiments, command-related information for multiple devices is carried in the second field; in this case, the second field can be understood as a list of command-related information. In one example, the second field may include multiple "command-related information" fields, each carrying command-related information for one device. In this case, the second field can also be referred to as a "list of command-related information" field.

[0195] In one example, Figure 3A is an example diagram of an R2D PDU according to an embodiment of the present disclosure. As shown by the solid lines in Figure 3A, N devices reuse one R2D PDU, where N is a positive integer greater than 1. In this case, the R2D PDU includes the following fields: a "PV" field, a "PDU type" field, N "RN16" fields, and N "command-related information" fields. The "PDU type" field has a value of 2, and each "command-related information" field may include a "CMD type" field, a "CMD length" field, and a "CMD container" field. In the above R2D PDU, the N "RN16" fields sequentially indicate device 1, device 2, ..., device N; correspondingly, the N "command-related information" fields sequentially carry command-related information for device 1, command-related information for device 2, ..., command-related information for device N.

[0196] In some embodiments, where multiple identification information sets are centrally located in the R2D PDU, the first information may further include quantity information indicating the number of identification information carried in the R2D PDU. In this case, by decoding the quantity information, it is possible to determine how many device command-related information exists in the R2D PDU. In one example, the quantity information may be carried in the "RN16 number" field of the R2D PDU. The "RN16 number" field may precede the first field.

[0197] In one example, as shown by the dashed line in Figure 3A, the R2D PDU also includes an "RN16number" field, which takes the value N.

[0198] In some embodiments, where multiple identification information is centrally located in the R2D PDU, the first information may further include multiple first indication information. One first indication information can be associated with one identification information, and different first indication information is associated with different identification information. That is, the first indication information and the identification information are associated one-to-one. A first indication information is associated with the command-related information associated with its associated identification information. In one example, the first indication information may be carried in the "Command Location (CMD location)" field of the R2D PDU. The R2D PDU also includes multiple "CMD location" fields, each corresponding one-to-one with the "RN16" field.

[0199] In some embodiments, the first indication information can be used to determine the starting position of the associated command-related information in the R2D PDU. In one embodiment, the first indication information can indicate the starting position of the associated command-related information in the R2D PDU. In one embodiment, multiple command-related information items are carried in a second field of the R2D PDU; in this case, the first indication information can indicate the starting position of the associated command-related information in the second field. In one embodiment, the starting position of the command-related information can be the position of the first bit of the command-related information in the R2D PDU. In this case, the order of the command-related information items of multiple devices in the R2D PDU can be consistent with or inconsistent with the order of multiple identification information items.

[0200] In some embodiments, the first indication information may indicate the offset of the starting position of the associated command-related information relative to a reference position in the R2D PDU.

[0201] In some embodiments, the reference positions corresponding to different first indication information may be different.

[0202] In one embodiment, the reference position corresponding to the first indication information can be the position of the identification information associated with the first indication information. Therefore, the first indication information indicates the offset of the starting position of the command-related information associated with the first indication information relative to the associated identification information. In one example, for device 1, identification information 1 indicates device 1. Therefore, the first indication information associated with identification information 1 indicates the offset between identification information 1 and the command-related information of device 1.

[0203] In one embodiment, the reference position corresponding to the first indication information can be the position of the first indication information itself. Therefore, the first indication information indicates the offset of the starting position of the command-related information associated with the first indication information relative to the associated identification information. In one example, for device 1, identification information 1 indicates device 1. Therefore, the first indication information associated with identification information 1 indicates the offset between the first indication information and the command-related information of device 1.

[0204] In some embodiments, the reference positions corresponding to different first indication information may be the same.

[0205] In one embodiment, the reference position corresponding to the first indication information can be the position of the first identification information among multiple identification information. Therefore, the first indication information indicates the offset of the starting position of the command-related information associated with the first indication information relative to the position of the first identification information. In one example, three devices reuse one R2D PDU. For device 3, identification information 3 indicates device 3. Therefore, the first indication information associated with identification information 3 can indicate the offset between the position of identification information 1 and the starting position of the command-related information of device 3.

[0206] In one embodiment, the reference position corresponding to the first indication information can be the position of the last identification information among multiple identification information. Therefore, the first indication information indicates the offset of the starting position of the command-related information associated with the first indication information relative to the position of the last identification information. In one example, three devices share one R2D PDU. For device 3, identification information 3 indicates device 3. Therefore, the first indication information associated with identification information 3 can indicate the offset between the position of identification information 3 and the starting position of the command-related information of device 3.

[0207] In one embodiment, the reference position corresponding to the first indication information can be the position of the first indication information among a plurality of first indication information. In this case, the first indication information indicates the offset of the starting position of the command-related information associated with the first indication information relative to the position of the first indication information. In one example, three devices reuse one R2D PDU. For device 3, identification information 3 indicates device 3. Therefore, the first indication information associated with identification information 3 can indicate the offset between the position of the first indication information associated with identification information 1 and the starting position of the command-related information of device 3.

[0208] In one embodiment, the reference position corresponding to the first indication information can be the position of the last first indication information among multiple first indication information. In this case, the first indication information indicates the offset of the starting position of the command-related information associated with that first indication information relative to the position of the last first indication information. In one example, three devices reuse one R2D PDU. For device 3, the identification information 3 indicates device 3. Therefore, the first indication information associated with the identification information 3 can indicate the offset between itself and the starting position of the command-related information of device 3.

[0209] In one embodiment, the reference position corresponding to the first indication information can be the position of the first command-related information among multiple command-related information. Therefore, the first indication information indicates the offset of the starting position of the command-related information associated with the first indication information relative to the position of the first command-related information. In one example, three devices multiplex one R2D PDU. For device 3, identification information 3 indicates device 3. Therefore, the first indication information associated with identification information 3 can indicate the offset between the position of the command-related information associated with identification information 1 and the starting position of the command-related information of device 3.

[0210] In one embodiment, when the first information also includes quantity information, the reference position corresponding to the first indication information can be the position of the quantity information. Therefore, the first indication information indicates the offset of the starting position of the command-related information associated with the first indication information relative to the position of the quantity information. In one example, three devices share one R2D PDU. For device 3, identification information 3 indicates device 3. Therefore, the first indication information associated with the identification information 3 can indicate the offset between the quantity information and the starting position of the command-related information of device 3.

[0211] In some embodiments, the position of the identification information can be any bit within the identification information. In one example, the position of the identification information can be the start position of the identification information, i.e., the first bit of the identification information. In another example, the position of the identification information can be the end position of the identification information, i.e., the last bit of the identification information. Of course, the position of the identification information can also be other cases, and this disclosure does not specifically limit it.

[0212] In some embodiments, the position of the first indication information can be any bit in the first indication information. In one example, the position of the first indication information can be the start position of the first indication information, that is, the first bit of the first indication information. In another example, the position of the first indication information can be the end position of the first indication information, that is, the last bit of the first indication information. Of course, the position of the first indication information can also be other cases, and this disclosure does not specifically limit it.

[0213] In some embodiments, the position of the command-related information can be any bit within the command-related information. In one example, the position of the command-related information can be the start position of the command-related information, i.e., the first bit of the command-related information. In another example, the position of the command-related information can be the end position of the command-related information, i.e., the last bit of the command-related information. Of course, the position of the command-related information can also be other cases, and this disclosure does not specifically limit this.

[0214] In some embodiments, the position of the quantity information can be any bit within the quantity information. In one example, the position of the quantity information can be the starting position of the quantity information, i.e., the first bit of the quantity information. In another example, the position of the quantity information can be the ending position of the quantity information, i.e., the last bit of the quantity information. Of course, the position of the quantity information can also be other cases, and this disclosure does not specifically limit it.

[0215] It should be noted that the reference position corresponding to the first indication information mentioned above can also be any bit in any information in the R2D PDU. The above is only an exemplary description of the reference position, and the embodiments disclosed herein do not impose any specific limitations on it.

[0216] In some embodiments, each of the plurality of first indication information can be set adjacent to an associated identification information. That is, the identification information and the first indication information are set alternately. In this case, the plurality of first indication information can be carried in a first field. In one example, the first field also includes a plurality of "CMD location" fields.

[0217] In one example, for three devices, the identification information and the first indication information are set in the following order: the identification information 1 of device 1, the first indication information associated with the identification information 1, the identification information 2 of device 2, the first indication information associated with the identification information 2, the identification information 3 of device 3, and the first indication information associated with the identification information 3.

[0218] In one example, Figure 3B is an example diagram of an R2D PDU according to an embodiment of the present disclosure. As shown in Figure 3B, N devices reuse one R2D PDU, where N is a positive integer greater than 1. The R2D PDU includes the following fields: a "PV" field, a "PDU type" field, N "RN16" fields, N "CMD location" fields, and N "command-related information" fields. The "PDU type" field has a value of 2, and the N "RN16" fields and N "CMD location" fields are alternately set. Each "command-related information" field may include a "CMD type" field, a "CMD length" field, and a "CMD container" field. In the above R2D PDU, the N "RN16" fields sequentially indicate device 1, device 2, ..., device N; correspondingly, the N "command-related information" fields sequentially carry command-related information for device 1, device 2, ..., device N.

[0219] In some embodiments, multiple first indication information follows multiple identification information, and the multiple first indication information is set sequentially in the R2D PDU according to the order of the multiple identification information; that is, the multiple first indication information as a whole follows the multiple identification information and is set in the order of the multiple identification information. In this case, the multiple first indication information can be carried in a third field. In one embodiment, the third field can be located between the first field and the second field. In one embodiment, the third field can be the first field. In one example, the third field may include multiple "CMD location" fields, set in the order of the associated "RN16" fields.

[0220] In one example, for three devices, the identification information and the first indication information are set in the following order: the identification information 1 of device 1, the identification information 2 of device 2, the identification information 3 of device 3, the first indication information associated with identification information 1, the first indication information associated with identification information 2, and the first indication information associated with identification information 3.

[0221] In one example, Figure 3C is an example diagram of an R2D PDU according to an embodiment of the present disclosure. As shown in Figure 3C, N devices multiplex one R2D PDU, where N is a positive integer greater than 1. In this case, the R2D PDU includes the following fields: a "PV" field, a "PDU type" field, N "RN16" fields, N "CMD location" fields, and N "command-related information" fields. The "PDU type" field has a value of 2, the N "CMD location" fields are set after the N "RN16" fields, and each "command-related information" field may include a "CMD type" field, a "CMD length" field, and a "CMD container" field. In the aforementioned R2DPDU, the N “RN16” fields sequentially indicate device 1, device 2, ..., device N. Correspondingly, the N “CMD location” fields sequentially indicate the starting position of the “command-related information” field associated with device 1, the starting position of the “command-related information” field associated with device 2, ..., the starting position of the “command-related information” field associated with device N. The N “command-related information” fields sequentially carry the command-related information of device 1, the command-related information of device 2, ..., the command-related information of device N.

[0222] It should be noted that the above is only an exemplary description of the first instruction information, and the first instruction information may also exist in other ways, which are not specifically limited in this disclosure.

[0223] In some embodiments, multiple identification information can be discretely set in the R2D PDU, and command-related information of multiple devices can also be discretely set in the R2D PDU. In one embodiment, multiple identification information and their respective associated command-related information are set adjacent to each other. In one example, for three devices, the identification information and associated command-related information are set in the following order: identification information 1 indicating device 1, command-related information of device 1, identification information 2 indicating device 2, command-related information of device 2, identification information 3 indicating device 3, and command-related information 3 of device 3.

[0224] In one example, the "Command-related information" field, which carries command-related information for a device, is set in the field following the "RN16" field, which carries identification information indicating the device.

[0225] In some embodiments, to mark the end of each command-related information item, the R2D PDU also includes second indication information. One identification information item is associated with one second indication information item, and the second indication information item indicates the end position of the associated command-related information item. Thus, in the R2D PDU, for a given device, the following information is sequentially set: identification information indicating the device, command-related information for the device, and second indication information. In one example, the second indication information is carried in an "end" field, and the next field after a "command-related information" field is set to the "end" field.

[0226] In one example, Figure 3D is an example diagram of an R2D PDU according to an embodiment of the present disclosure. As shown in Figure 3D, N devices reuse one R2D PDU, where N is a positive integer greater than 1. The R2D PDU includes the following fields: a "PV" field, a "PDU type" field, N "RN16" fields, N "command-related information" fields, and N "End" fields. The "PDU type" field has a value of 2. Each "command-related information" field may include a "CMD type" field, a "CMD length" field, and a "CMD container" field. The N "RN16" fields, the N "command-related information" fields, and the N "End" fields are set in the order of "RN16" field, "command-related information" field, and "End" field. In the above R2D PDU, the N "RN16" fields sequentially indicate device 1, device 2, ..., device N; correspondingly, the N "command-related information" fields sequentially carry command-related information for device 1, command-related information for device 2, ..., command-related information for device N.

[0227] It should be noted that the above is only an exemplary description of the R2D PDU. Other information may also be carried in the R2D PDU, and this disclosure does not specifically limit this.

[0228] In step S202, the first device decodes the R2D PDU.

[0229] In some embodiments, after receiving the R2D PDU in step S201, the first device sequentially decodes the fields in the R2D PDU. In one embodiment, the R2D PDU may carry command-related information of the first device, and in this case, the first device is included among the multiple devices multiplexing the R2D PDU. Then, by decoding the R2D PDU, the first device can obtain its own command-related information, and thus obtain the R2D command sent by the second device. In one embodiment, the R2D PDU may not carry command-related information of the first device, and in this case, the first device is not included among the multiple devices multiplexing the R2D PDU. Then, by decoding the R2D PDU, the first device cannot obtain its own command-related information and thus discards the R2D PDU.

[0230] In some embodiments, when multiple identification information and command-related information of multiple devices are centrally located in the R2D PDU, and the first information includes multiple identification information, the first device sequentially decodes the fields in the R2D PDU. After decoding to obtain multiple identification information, the first device can determine whether the R2D PDU carries its own command-related information based on whether the multiple identification information includes identification information indicating the first device. If the multiple identification information includes identification information indicating the first device, the first device can determine that the R2D PDU carries the command-related information of the first device. In this case, the first device continues to decode the remaining information until it obtains its own command-related information. Conversely, if the multiple identification information does not include identification information indicating the first device, the first device can determine that the R2D PDU does not carry the command-related information of the first device. In this case, the first device discards the R2D PDU. In this situation, the first device can determine whether the R2D PDU includes its own command-related information simply by decoding multiple identification information, thus improving decoding efficiency, reducing decoding latency, and saving device power consumption.

[0231] In one embodiment, the first device can also determine the position of the command-related information of the first device in the R2D PDU based on the position of the first device's identification information in multiple identification information. In this way, the first device can decode its own command-related information at the corresponding position without decoding the command-related information of other devices, thereby achieving rapid location of its own command-related information, greatly reducing decoding latency and saving device power consumption.

[0232] In one embodiment, where the first information may further include multiple first indication information, the first device sequentially decodes the fields in the R2D PDU. After decoding to obtain the identification information indicating the first device, the first device can determine the first indication information associated with the identification information and decode the first indication information. Then, the first device determines the position of its command-related information in the R2D PDU based on the decoded first indication information, and then decodes its own command-related information at that position. This improves decoding efficiency, reduces decoding latency, and saves device power consumption. In another embodiment, the first device determines the offset between the starting position and the reference position of its command-related information based on the decoded first indication information, and then determines the position of its command-related information in the R2D PDU based on the offset.

[0233] In some embodiments, when multiple identification information and command-related information of multiple devices are discretely set in the R2D PDU, and the first information includes multiple identification information, the first device decodes the fields in the R2D PDU sequentially. After decoding to obtain the identification information indicating the first device, the first device can determine that the R2D PDU carries its own command-related information. If the first device still does not obtain the identification information indicating the first device after decoding all the identification information, the first device can determine that the R2D PDU does not carry its own command-related information.

[0234] In one embodiment, when the first device decodes the identification information indicating the first device, the first device can determine that command-related information follows the identification information. In this case, the first device continues to decode subsequent information to obtain its own command-related information. In another embodiment, a second indication information is provided after the device's identification information. In this case, the first device decodes the information following the identification information until it decodes the second indication information, thereby obtaining its own command-related information.

[0235] In one example, as shown in Figure 3A, N devices reuse one R2D PDU, with device 2 being the first device and N being a positive integer greater than 1. This R2D PDU includes the following fields: a "PV" field, a "PDU type" field, an "RN16 number" field, N "RN16" fields, and N "command-related information" fields. The "PDU type" field has a value of 2. Each "command-related information" field can include a "CMD type" field, a "CMD length" field, and a "CMD container" field. In the R2D PDU, the N "RN16" fields sequentially indicate device 1, device 2, ..., device N. Correspondingly, the N "command-related information" fields sequentially carry command-related information for device 1, device 2, ..., device N. In this case, after receiving the R2D PDU, device 2 sequentially decodes the "PV" field, the "PDU type" field, and the "RN16 number" field. Then, device 2 begins sequentially decoding the N "RN16" fields. When device 2 decodes the second "RN16" field, it determines that the RN16 carried in the field is consistent with its own RN16. At this time, device 2 decodes the second "command-related information" field among the N "command-related information" fields, thereby obtaining the command-related information of device 2, and then obtaining the R2D command sent by the second device to device 2.

[0236] In one example, Figure 3B is an example diagram of an R2D PDU according to an embodiment of the present disclosure. As shown in Figure 3B, N devices reuse one R2D PDU, where N is a positive integer greater than 1. The R2D PDU includes the following fields: a "PV" field, a "PDU type" field, N "RN16" fields, N "CMD location" fields, and N "command-related information" fields. The "PDU type" field has a value of 2, and the N "RN16" fields and N "CMD location" fields are alternately set. Each "command-related information" field may include a "CMD type" field, a "CMD length" field, and a "CMD container" field. In the above R2D PDU, the N "RN16" fields sequentially indicate device 1, device 2, ..., device N; correspondingly, the N "command-related information" fields sequentially carry command-related information for device 1, device 2, ..., device N. In this scenario, after receiving the R2D PDU, device 2 sequentially decodes the "PV" field, the "PDU type" field, and the "RN16 number" field. Then, device 2 begins decoding N "RN16" fields sequentially. When device 2 decodes the second "RN16" field, it determines that the RN16 carried in this field is consistent with its own RN16. At this point, device 2 decodes the adjacent "CMD location" field to obtain the offset between the first bit of the "command-related information" field associated with device 2 and the first bit of the second "RN16" field. Based on this, device 2 can determine the first bit (i.e., the starting position) of the "command-related information" field associated with device 2. Then, device 2 begins decoding the "command-related information" field associated with device 2 at the determined position to obtain the command-related information of device 2, thereby obtaining the R2D command sent to device 2 by the second device.

[0237] In one example, Figure 3C is an example diagram of an R2D PDU according to an embodiment of the present disclosure. As shown in Figure 3C, N devices multiplex one R2D PDU, where N is a positive integer greater than 1. In this case, the R2D PDU includes the following fields: a "PV" field, a "PDU type" field, N "RN16" fields, N "CMD location" fields, and N "command-related information" fields. The "PDU type" field has a value of 2, the N "CMD location" fields are set after the N "RN16" fields, and each "command-related information" field may include a "CMD type" field, a "CMD length" field, and a "CMD container" field. In the aforementioned R2DPDU, the N "RN16" fields sequentially indicate device 1, device 2, ..., device N. Correspondingly, the N "CMD location" fields sequentially indicate the starting position of the "command-related information" field associated with device 1, the starting position of the "command-related information" field associated with device 2, ..., the starting position of the "command-related information" field associated with device N. These N "command-related information" fields sequentially carry the command-related information of device 1, device 2, ..., device N. In this case, after receiving the R2DPDU, device 2 sequentially decodes the "PV" field, the "PDU type" field, and the "RN16 number" field. Then, device 2 begins sequentially decoding the N "RN16" fields. When device 2 decodes the second "RN16" field, it determines that the RN16 carried in this field is consistent with its own RN16. At this point, device 2 decodes the second "CMD location" field to obtain the offset between the first bit of the "command-related information" field associated with device 2 and the first bit of the second "RN16" field. Based on this, device 2 can determine the first bit (i.e., the starting position) of the "command-related information" field associated with device 2. Then, device 2 begins decoding the "command-related information" field associated with device 2 at the determined position to obtain the command-related information of device 2, and thus obtain the R2D command sent by the second device to device 2.

[0238] In one example, Figure 3D is an example diagram of an R2D PDU according to an embodiment of the present disclosure. As shown in Figure 3D, N devices reuse one R2D PDU, where N is a positive integer greater than 1. The R2D PDU includes the following fields: a "PV" field, a "PDU type" field, N "RN16" fields, N "command-related information" fields, and N "End" fields. The "PDU type" field has a value of 2. Each "command-related information" field may include a "CMD type" field, a "CMD length" field, and a "CMD container" field. The N "RN16" fields, the N "command-related information" fields, and the N "End" fields are set in the order of "RN16" field, "command-related information" field, and "End" field. In the above R2D PDU, the N "RN16" fields sequentially indicate device 1, device 2, ..., device N; correspondingly, the N "command-related information" fields sequentially carry command-related information for device 1, command-related information for device 2, ..., command-related information for device N. In this scenario, after receiving the R2DPDU, device 2 decodes the "PV" field and the "PDU type" field sequentially. Then, device 2 begins decoding the first "RN16" field. If device 2 determines that the RN16 carried in the first "RN16" field is inconsistent with its own RN16, it skips the "command-related information" field and the "End" field following the first "RN16" field and begins decoding the second "RN16" field. When device 2 decodes the second "RN16" field, it determines that the RN16 carried in this field is consistent with its own RN16. At this point, device 2 decodes the "command-related information" field adjacent to the second "RN16" field until it decodes an "End" field, thereby obtaining device 2's command-related information and ultimately the R2D command sent by the second device.

[0239] In one embodiment, when decoding the "command-related information" field, the first device decodes the "CMD type" field, the "CMD length" field, and the "CMD container" field in that order to obtain the R2D command.

[0240] The communication method involved in the embodiments of this disclosure may include at least one of steps S201 to S202. For example, step S201 may be implemented as a standalone embodiment. For example, step S202 may be implemented as a standalone embodiment. For example, a combination of steps S201 and S202 may be implemented as a standalone embodiment. It should be noted that possible standalone embodiments may consist of one or more steps S201 to S202, but are not limited thereto.

[0241] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0242] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.

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

[0244] In some embodiments, terms such as wireless access scheme and waveform can be used interchangeably.

[0245] In some embodiments, “get,” “obtain,” “receive,” “transmit,” “bidirectional transmission,” and “send and / or receive” can be used interchangeably and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining through self-processing, or autonomous implementation, among other meanings.

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

[0247] In some embodiments, the terms "passive device", "environmental IoT device", "tag", "electronic tag", "IoT device" can be used interchangeably.

[0248] In some embodiments, the terms “carrying,” “bearing,” and “containing” can be used interchangeably.

[0249] 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.

[0250] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0251] As shown in Figure 4, Figure 4 is an exemplary interaction diagram illustrating a communication method according to an embodiment of the present disclosure. This disclosure relates to a communication method performed by the aforementioned passive Internet of Things (IoT) system. The communication method includes step S401.

[0252] In step S401, the second device sends an R2D PDU to the first device.

[0253] The optional implementation of step S401 can be found in step S201 of Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0254] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

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

[0256] In some embodiments, a scheme 1 is provided: the R2D MAC PDU (R2D data) may further include the following information:

[0257] RN16 number: Indicates how many RN16-corresponding R2D signaling messages exist for this R2D PDU.

[0258] RN16 is a temporary identifier for a device, randomly generated during the access process or configured as a random value on the network side. It is used to identify a device. The RN16 number field is followed by RN16 number times.

[0259] CMD-related fields, such as CMD type, CMD length, and CMD container.<CMD type,CMD length,CMD container> It is linked to the previous RN16 list one by one.

[0260] CMD type is used to indicate the name or type of the R2D command.

[0261] CMD length is used to indicate the length of the following CMD container.

[0262] The CMD container carries R2D commands from the upper layer.

[0263] In some embodiments, each RN16 corresponds to a pointer (such as the second indication information) indicating that the CMD related field of the device is offset by n bits from the end of the RN16 of the device, where n is a positive integer.

[0264] In some embodiments, each RN16 corresponds to a pointer (such as the second indication information) indicating that the CMD related field of the device is offset by n bits from the end of the RN16 of all devices, where n is a positive integer.

[0265] In some embodiments, a second approach is provided: the R2D MAC PDU (R2D data) may further include the following information:

[0266] RN16 is a temporary identifier for a device, randomly generated during the access process, or a random value configured on the network side. It is used to identify a device.

[0267] CMD-related fields, such as CMD type, CMD length, and CMD container, must include at least one of these.

[0268] CMD type is used to indicate the name or type of the R2D command.

[0269] CMD length is used to indicate the length of the following CMD container.

[0270] The CMD container carries R2D commands from the upper layer.

[0271] The End directive indicates the end of the CMD content corresponding to this RN16. A new CMD for the next device will then begin.

[0272] In some embodiments, the advantage of Option 1 is that the device can quickly know whether its own CMD-related fields and content exist, while Option 2 requires decoding to the very end to know whether its own CMD-related fields and content exist.

[0273] In some embodiments, the advantage of Scheme 2 is that the device can decode until the end or until it finds its own CMD content. Scheme 2 requires the number of RN16s and which RN16 it is to obtain the content, while Scheme 1 does not need to remember this content.

[0274] 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.

[0275] This disclosure also provides communication apparatuses for implementing any of the above methods. For example, this disclosure provides a communication apparatus including units or modules for implementing the steps performed by a terminal in any of the above methods. For example, this disclosure provides a communication apparatus including units or modules for implementing the steps performed by a network device in any of the above methods.

[0276] 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 configuration files, 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.

[0277] 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 central processing unit, microprocessor, graphics processing unit (GPU) (which can be understood as a type of 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 application-specific integrated circuit (ASIC) or a programmable logic device, 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.

[0278] Figure 5 is a schematic diagram of a communication device provided according to an embodiment of the present disclosure. As shown in Figure 5, the communication device 500 may include at least one of the following: a transceiver module 501 and a processing module 502.

[0279] In some embodiments, the communication device 500 may be a first device. In some embodiments, the transceiver module 501 may be configured to: receive an R2D PDU sent by a second device, the R2D PDU carrying first information and command-related information of multiple devices, the first information being used to determine the position of the command-related information of each device in the R2D PDU, and the command-related information of each device being used to indicate the R2D command configuration of each device. Optionally, the transceiver module 501 may be configured to perform at least one of the communication steps such as sending and / or receiving performed by the first device in any of the above methods, which will not be elaborated here. Optionally, the processing module 502 may be configured to perform at least one of the other steps performed by the first device in any of the above methods besides the communication steps such as sending and / or receiving, which will not be elaborated here.

[0280] In some embodiments, the communication device 500 may be a second device. In some embodiments, the transceiver module 501 may be configured to: send an R2D PDU to a first device, the R2D PDU carrying first information and command-related information of multiple devices, the first information being used to determine the position of the command-related information of each device in the R2D PDU, and the command-related information of each device being used to indicate the R2D command configuration of each device. Optionally, the transceiver module 501 may be configured to perform at least one of the communication steps such as sending and / or receiving performed by the second device in any of the above methods, which will not be elaborated here. Optionally, the processing module 502 may be configured to perform at least one of the other steps performed by the second device in any of the above methods besides the communication steps such as sending and / or receiving, which will not be elaborated here.

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

[0282] 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. Optionally, the processing module may be interchangeable with a processor.

[0283] Figure 6A is a schematic diagram of a communication device provided according to an embodiment of the present disclosure. The communication device 6100 can be a first device or a second device, or it can be a chip, chip system, or processor that supports the first device or the second device in implementing any of the above methods. The communication device 6100 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.

[0284] As shown in Figure 6A, the communication device 6100 includes one or more processors 6101. The processor 6101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can 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 6100 can be used to execute any of the above methods. Optionally, one or more processors 6101 can be used to invoke instructions to cause the communication device 6100 to execute any of the above methods.

[0285] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceiver 6102 performs at least one of the communication steps such as sending and / or receiving in the above-described method. The processor 6101 performs at least one of the other steps. In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0286] In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data. Optionally, all or part of the memories 6103 may be located outside the communication device 6100. In optional embodiments, the communication device 6100 may include one or more interface circuits 6104. Optionally, the interface circuits 6104 are connected to the memories 6103 and can be used to receive data from the memories 6103 or other devices, and to send data to the memories 6103 or other devices. For example, the interface circuits 6104 can read data stored in the memories 6103 and send that data to the processor 6101.

[0287] The communication device 6100 described in the above embodiments may be a terminal or a network device, but the scope of the communication device 6100 described in this disclosure is not limited thereto, and the structure of the communication device 6100 may not be limited by FIG. 6A. The communication device may be a standalone device or a 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 and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (6) 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.; (4) others, etc.

[0288] Figure 6B is a schematic diagram of a chip provided according to an embodiment of the present disclosure. For cases where the communication device 6100 can be a chip or a chip system, please refer to the schematic diagram of the chip 6200 shown in Figure 6B, but it is not limited thereto.

[0289] In some embodiments, chip 6200 includes one or more processors 6201. Chip 6200 is used to perform any of the methods described above.

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

[0291] In some embodiments, the interface circuit 6202 performs at least one of the communication steps, such as sending and / or receiving, in the above-described method. For example, the interface circuit 6202 performing the communication steps, such as sending and / or receiving, in the above-described method means that the interface circuit 6202 performs data interaction between the processor 6201, the chip 6200, the memory 6203, or the transceiver device. In some embodiments, the processor 6201 performs at least one of the other steps.

[0292] 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.

[0293] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device 6100, cause the communication device 6100 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.

[0294] This disclosure also provides a program product that, when executed by a communication device 6100, causes the communication device 6100 to perform any of the above methods. Optionally, the program product is a computer program product.

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

[0296] 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.

[0297] 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: The device receives a Reader-to-Device Protocol Data Unit (PDU) sent by a second device. The R2D PDU carries first information and command-related information of multiple devices. The first information is used to determine the position of the command-related information of each device in the R2D PDU. The command-related information of each device is used to indicate the R2D command configuration of each device.

2. The method of claim 1, wherein, The first information includes multiple identification information, each of which is used to indicate one of the multiple devices. Different identification information indicates different devices, and the command-related information of each device is associated with the identification information indicating each device.

3. The method of claim 2, wherein, The plurality of identification information is carried in a first field of the R2D PDU, and the command-related information of the plurality of devices is carried in a second field of the R2D PDU. The position of the command-related information of the plurality of devices in the second field is set according to the order of the plurality of identification information in the first field.

4. The method of claim 2 or 3, wherein, The first information also includes quantity information, which is used to indicate the quantity of the plurality of identification information.

5. The method according to any one of claims 2 to 4, wherein, The first information also includes a plurality of first indication information, each of which is associated with one of the plurality of identification information. Different first indication information is associated with different identification information. Each first indication information is used to indicate the starting position of the command-related information of the device indicated by the associated identification information in the second field.

6. The method of claim 5, wherein, The plurality of first indication information is carried in the first field, and each identification information is adjacent to the first indication information associated with each identification information.

7. The method of claim 5, wherein, The plurality of first indication information is carried in the third field. The plurality of first indication information is located after the plurality of identification information. The plurality of first indication information is set in the third field in the order of the plurality of identification information in the first field.

8. The method of claim 2, wherein, Each identification information is adjacent to the command-related information associated with that identification information.

9. The method of claim 8, wherein, A second indication is set after each identifier information is associated with the command-related information. The second indication is used to indicate the end of the command-related information associated with each identifier information.

10. The method according to any one of claims 1 to 9, wherein, The command-related information includes at least one of the following: Command type, used to indicate the class of the R2D command; Command length, used to indicate the length of the command container; A command container for holding the R2D commands.

11. The method according to any one of claims 1 to 10, wherein, The R2D PDU also includes second information, which indicates that the type of the R2D PDU is R2D data.

12. A communication method performed by a second device, the method comprising: A reader is sent to a device R2D protocol data unit (PDU) to a first device. The R2D PDU carries first information and command-related information of multiple devices. The first information is used to determine the location of the command-related information of each device in the R2D PDU. The command-related information of each device is used to indicate the R2D command configuration of each device.

13. The method of claim 12, wherein, The first information includes multiple identification information, each of which is used to indicate one of the multiple devices. Different identification information indicates different devices, and the command-related information of each device is associated with the identification information indicating each device.

14. The method of claim 13, wherein, The plurality of identification information is carried in a first field of the R2D PDU, and the command-related information of the plurality of devices is carried in a second field of the R2D PDU. The position of the command-related information of the plurality of devices in the second field is set according to the order of the plurality of identification information in the first field.

15. The method of claim 13 or 14, wherein, The first information also includes quantity information, which is used to indicate the quantity of the plurality of identification information.

16. The method according to any one of claims 13 to 15, wherein, The first information also includes a plurality of first indication information, each of which is associated with one of the plurality of identification information. Different first indication information is associated with different identification information. Each first indication information is used to indicate the starting position of the command-related information of the device indicated by the associated identification information in the second field.

17. The method of claim 16, wherein, The plurality of first indication information is carried in the first field, and each identification information is adjacent to the first indication information associated with each identification information.

18. The method of claim 16, wherein, The plurality of first indication information is carried in the first field. The plurality of first indication information is located after the plurality of identification information in the first field. The plurality of first indication information is set sequentially in the first field according to the order of the plurality of identification information in the first field.

19. The method of claim 13, wherein, Each identification information is adjacent to the command-related information associated with that identification information.

20. The method of claim 19, wherein, A second indication is set after each identifier information is associated with the command-related information. The second indication is used to indicate the end of the command-related information associated with each identifier information.

21. The method of any one of claims 12 to 20, wherein, The command-related information includes at least one of the following: Command type, used to indicate the class of the R2D command; Command length, used to indicate the length of the command container; A command container for holding the R2D commands.

22. The method of any one of claims 12 to 20, wherein, The R2D PDU also includes second information, which indicates that the type of the R2D PDU is R2D data.

23. A communication method, performed by a communication system, said communication system comprising a first device and a second device; The method includes: The second device sends a reader to the first device via a device R2D protocol data unit (PDU). The R2D PDU carries first information and command-related information for multiple devices. The first information is used to determine the location of the command-related information for each device in the R2D PDU. The command-related information for each device is used to indicate the R2D command configuration for each device.

24. A communication device, the communication device being configured to perform at least one of the following: The communication method as described in any one of claims 1 to 11; the communication method as described in any one of claims 12 to 22.

25. A communication system comprising a first device and a second device; the first device being configured to perform a communication method as described in any one of claims 1 to 11; and the second device being configured to perform a communication method as described in any one of claims 12 to 22.

26. A storage medium storing instructions, wherein, When the instructions are executed on the communication device, the communication device implements the communication method as described in any one of claims 1 to 11, or implements the communication method as described in any one of claims 12 to 22.

27. A program product comprising instructions, wherein, When the instruction is executed on the communication device, it causes the communication device to implement the communication method as described in any one of claims 1 to 11, or to implement the communication method as described in any one of claims 12 to 22.

Images