Communication method, and device, system and storage medium

Abstract

The present disclosure relates to a communication method, and a device, a system and a storage medium. The method may be executed by an Internet of Things (IOT) device. The method comprises: sending uplink data to a network device, wherein the uplink data comprises at least one transport block (TB). In this way, the IoT device can reliably transmit uplink data to the network device by means of sending at least one TB to the network device, thereby ensuring that the network device can reliably perform information interaction with the IoT device.

Description

Communication methods, devices, systems and storage media Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to communication methods, devices, systems and storage media. Background Technology

[0002] Compared to traditional IoT technologies, Ambient Internet of Things (A-IoT) technology allows for a much larger number of A-IoT devices that can be connected to the network. Furthermore, A-IoT devices have a simpler structure, lower hardware and maintenance costs, and lower power consumption, meaning they can operate for extended periods without requiring battery replacements. Summary of the Invention

[0003] This disclosure provides a communication method, device, system, and storage medium.

[0004] According to a first aspect of the present disclosure, a communication method is provided, performed by an Internet of Things (IoT) device, the method comprising:

[0005] Uplink data is sent to network devices, the uplink data including at least one transmit block (TB).

[0006] According to a second aspect of the embodiments of this disclosure, a communication method is provided, performed by a network device, the method comprising:

[0007] Receive uplink data sent by Internet of Things (IoT) devices, wherein the uplink data includes at least one transport block (TB).

[0008] According to a third aspect of the embodiments of this disclosure, an Internet of Things (IoT) device is provided, comprising:

[0009] A transceiver module is used to send uplink data to network devices, the uplink data including at least one transport block (TB).

[0010] According to a fourth aspect of the embodiments of this disclosure, a network device is provided, comprising:

[0011] The transceiver module is used to receive uplink data sent by Internet of Things (IoT) devices, wherein the uplink data includes at least one transport block (TB).

[0012] According to a fifth aspect of the embodiments of this disclosure, a communication device is provided, comprising:

[0013] One or more processors;

[0014] The communication device is used to perform the communication method described in the first or second aspect.

[0015] According to a sixth aspect of the present disclosure, a communication system is proposed, including a network device and an Internet of Things (IoT) device, wherein the IoT device is configured to implement the communication method described in the first aspect, and the network device is configured to implement the communication method described in the second aspect.

[0016] According to a seventh aspect of the present disclosure, a storage medium is provided that stores instructions which, when executed on a communication device, cause the communication device to perform the communication method as described in the first or second aspect.

[0017] According to an eighth aspect of the present disclosure, a computer program product is provided, comprising a computer program and / or instructions that, when executed by a communication device, implement the communication method as described in the first or second aspect.

[0018] In the above embodiments, the IoT device can reliably transmit uplink data to the network device by sending at least TB to the network device, ensuring that the network device can reliably interact with the IoT device. Attached Figure Description

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

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

[0021] Figure 1B is another exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.

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

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

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

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

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

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

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

[0029] Figure 3D is an exemplary interactive schematic diagram of a communication method provided according to an embodiment of the present disclosure.

[0030] Figure 4A is an exemplary flowchart of a communication method provided according to an embodiment of the present disclosure.

[0031] Figure 4B is an exemplary flowchart of a communication method provided according to an embodiment of the present disclosure.

[0032] Figure 4C is an exemplary flowchart of a communication method provided according to an embodiment of the present disclosure.

[0033] Figure 5A is an exemplary structural diagram of an IoT device provided according to an embodiment of the present disclosure.

[0034] Figure 5B is an exemplary structural diagram of a network device provided according to an embodiment of the present disclosure.

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

[0036] Figure 6B is an exemplary structural diagram of a communication device provided according to an embodiment of the present disclosure. Detailed Implementation

[0037] This disclosure provides a communication method, device, system, and storage medium.

[0038] In a first aspect, embodiments of this disclosure propose a communication method executed by an Internet of Things (IoT) device, the method comprising:

[0039] Uplink data is sent to network devices, the uplink data including at least one transport block (TB).

[0040] In the above embodiments, the IoT device can reliably transmit uplink data to the network device by sending at least TB to the network device, ensuring that the network device can reliably interact with the IoT device.

[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the method includes:

[0042] Based on the first condition, determine whether the uplink data transmission uses both retransmission and forward error correction (FEC) encoding simultaneously;

[0043] The first condition includes at least one of the following:

[0044] The signal quality identifier (QI) value of the data service of the IoT device is within the preset QI value range;

[0045] The size of TB is greater than a preset size threshold;

[0046] The priority value of the TB is less than a preset priority value threshold;

[0047] The IoT device supports feedback based on Hybrid Automatic Repeat reQuest (HARQ), and the number of negative acknowledgments (NACKs) received from the network device after sending M TBs is greater than or equal to N, where M and N are preset positive integers.

[0048] The IoT device supports HARQ-based feedback, and the number of NACKs received from network devices within a preset time period is greater than a preset threshold.

[0049] In the above embodiments, the IoT device can determine whether it needs to use repeated transmission and FEC coding simultaneously based on a first condition, so that the IoT device can schedule uplink transmission more flexibly, ensuring the reliability of uplink transmission while reducing the computational overhead of uplink transmission.

[0050] In conjunction with some embodiments of the first aspect, in some embodiments, the method includes:

[0051] It is determined that blind retransmission or HARQ-based retransmission is supported, and reserved resources are determined. The reserved resources are configured by the network device and are used for blind retransmission or retransmission of the uplink data.

[0052] In the above embodiments, when the network device determines that the IoT device supports blind retransmission or retransmission based on HARQ feedback, it can configure corresponding reserved resources for the IoT device, thereby enabling the IoT device to retransmit uplink data based on these reserved resources, ensuring the reliability of uplink transmission.

[0053] In conjunction with some embodiments of the first aspect, in some embodiments, the method includes:

[0054] If HARQ-based retransmission is supported, the first TB of data transmission is completed. Within a preset time window, an acknowledgment (ACK) or NACK is listened for.

[0055] Based on the monitoring results, determine whether to use the reserved resources to retransmit the first TB;

[0056] The first TB is any TB included in the uplink data.

[0057] In conjunction with some embodiments of the first aspect, in some embodiments, determining whether to use the reserved resources for retransmission of the first TB based on the monitoring results includes at least one of the following:

[0058] Once the ACK is detected, the reserved resources will no longer be used for retransmission of the first TB.

[0059] If the NACK is detected, the reserved resources are used to retransmit the first TB.

[0060] In the above embodiments, the IoT device can determine whether TB needs to be retransmitted by listening to ACK or NACK, effectively ensuring the rational use of resources.

[0061] In conjunction with some embodiments of the first aspect, in some embodiments, the first interval between the first time and the second time is greater than or equal to a first interval threshold, and the second interval between the second time and the third time is greater than a second interval threshold;

[0062] The first time is the transmission time of the first TB, the second time is the start time of the preset time window, and the third time is the end time of the preset time window.

[0063] In the above embodiments, by setting corresponding time intervals between the transmission time of TB and the start time of the preset time window, and between the transmission time of TB and the end time of the preset time window, the reliability of the monitoring results can be effectively ensured, thereby ensuring the reliability of the uplink transmission.

[0064] In conjunction with some embodiments of the first aspect, in some embodiments, the number of blind retransmissions of the first TB is equal to the number of reserved resources configured by the network device for the first TB, where the first TB is any TB included in the uplink data.

[0065] In conjunction with some embodiments of the first aspect, in some embodiments, the reserved resources include at least one of time-domain resources, frequency-domain resources, or spatial-domain resources;

[0066] The number of reserved resources configured by the network device for a TB is one or more, and there is a time interval between each two adjacent resources of the multiple reserved resources configured by the network device for a TB.

[0067] In the above embodiments, the network device can configure one or more reserved resources for a TB and set a corresponding time interval between every two reserved resources to ensure the reliability of uplink transmission.

[0068] In conjunction with some embodiments of the first aspect, in some embodiments, when the uplink transmission type of the IoT device is a periodic service, the network device is configured with periodic resources for TB transmission, and the reserved resources are configured in each period.

[0069] In conjunction with some embodiments of the first aspect, in some embodiments, the number of frequency domain resource units in each of the reserved resources is the same, and the positions of the frequency domain resource units in each of the reserved resources are the same or different.

[0070] In conjunction with some embodiments of the first aspect, in some embodiments, sending uplink data to the network device includes:

[0071] In cases where HARQ-based retransmission is supported, if a TB transmission failure is determined, at least two TBs are merged and transmitted, wherein the at least two TBs include at least one failed TB.

[0072] In the above embodiments, when an IoT device determines that one or more TBs have failed to be sent, it can merge multiple TBs and send them together, which can effectively avoid uplink data loss due to TB transmission failure and effectively ensure the reliability of uplink transmission.

[0073] In conjunction with some embodiments of the first aspect, in some embodiments, the method includes:

[0074] If a TB is confirmed to have received a NACK from the network device on all reserved resources, it is determined that the TB transmission has failed.

[0075] In the above embodiments, the IoT device can determine that the TB has failed to be sent only when it receives NACK on all the reserved resources corresponding to a TB, which can effectively avoid false judgments.

[0076] In conjunction with some embodiments of the first aspect, in some embodiments, the merging and sending of at least two TBs includes:

[0077] At least one failed TB and a second TB are sent using a first resource, wherein the first resource is a resource configured by the network device for sending the second TB, and the second TB is a new TB to be sent by the IoT device.

[0078] In the above embodiments, the IoT device can utilize the resources reserved for sending a new TB next time to send multiple merged TBs to the network device, effectively improving the flexibility of resource scheduling.

[0079] In conjunction with some embodiments of the first aspect, in some embodiments, the third interval between the fourth time and the fifth time is less than or equal to a third interval threshold, the fourth time being the transmission time of the first TB among the at least one failed TB, and the fifth time being the start time of the first resource.

[0080] In the above embodiments, the sending time of TB and the start time of the resource can be used to determine which TBs that failed to be sent can be merged and sent together.

[0081] In conjunction with some embodiments of the first aspect, in some embodiments, the merging and sending of at least two TBs includes:

[0082] Send a third TB, which is obtained by merging at least one failed TB and the second TB in chronological order and adding a CRC; or,

[0083] Send the fourth TB, which is obtained by adding CRC to at least one failed TB and the second TB and merging them in chronological order.

[0084] In conjunction with some embodiments of the first aspect, in some embodiments, the method includes:

[0085] Send a first message, which indicates the number of TBs to be sent in this merge and the length of each TB.

[0086] In the above embodiments, the IoT device can report first information to the network device, so that the network device can know the number of TBs merged and sent in this merged transmission and the length of each TB, thereby enabling the network side to reliably decode the multiple TBs merged and sent.

[0087] In conjunction with some embodiments of the first aspect, in some embodiments, when the IoT device is a device that operates based on backscattering and the type of uplink transmission of the IoT device is a periodic service, the period for the IoT device to transmit the uplink data is an integer multiple of the period of a continuous electromagnetic wave (CW), which is used by the IoT device for backscattering to transmit data.

[0088] Secondly, embodiments of this disclosure provide a communication method executed by a network device, the method comprising:

[0089] Receive uplink data sent by Internet of Things (IoT) devices, wherein the uplink data includes at least one transport block (TB).

[0090] In conjunction with some embodiments of the second aspect, in some embodiments, the uplink data simultaneously uses retransmission and forward error correction (FEC) coding, wherein whether the uplink data simultaneously uses retransmission and FEC coding is determined based on a first condition, the first condition including at least one of the following:

[0091] The QI value of the data service of the IoT device is within the preset QI value range;

[0092] The size of TB is greater than a preset size threshold;

[0093] The priority value of the TB is less than a preset priority value threshold;

[0094] The IoT device supports feedback based on Hybrid Automatic Repeat Request (HARQ), and the number of negative acknowledgments (NACKs) received from the network device after sending M TBs is greater than or equal to N, where M and N are preset positive integers.

[0095] The IoT device supports HARQ-based feedback, and the number of NACKs received from network devices within a preset time period is greater than a preset threshold.

[0096] In conjunction with some embodiments of the second aspect, in some embodiments, the method includes:

[0097] The IoT device is determined to support blind retransmission or retransmission based on HARQ feedback. Reserved resources are determined, and the reserved resources are used for blind retransmission or retransmission of the uplink data.

[0098] In conjunction with some embodiments of the second aspect, in some embodiments, the number of blind retransmissions of the first TB is equal to the number of reserved resources configured by the network device for the first TB, where the first TB is any TB included in the uplink data.

[0099] In conjunction with some embodiments of the second aspect, in some embodiments, the reserved resources include at least one of time-domain resources, frequency-domain resources, or spatial-domain resources;

[0100] The number of reserved resources configured by the network device for a TB is one or more, and there is a time interval between each two adjacent resources of the multiple reserved resources configured by the network device for a TB.

[0101] In conjunction with some embodiments of the second aspect, in some embodiments, when the uplink transmission type of the IoT device is a periodic service, the network device is configured with periodic resources for TB transmission, and the reserved resources are configured in each period.

[0102] In conjunction with some embodiments of the second aspect, in some embodiments, the number of frequency domain resource units of each of the reserved resources is the same, and the positions of the frequency domain resource units of each of the reserved resources are the same or different.

[0103] In conjunction with some embodiments of the second aspect, in some embodiments, the method includes:

[0104] The device receives at least two TBs that are merged and sent by the IoT device. The at least two TBs are sent by the IoT device when it determines that the TB transmission has failed, provided that retransmission based on HARQ feedback is supported. The at least two TBs include at least one failed TB.

[0105] In conjunction with some embodiments of the second aspect, in some embodiments, receiving at least two TBs merged and transmitted by the IoT device includes:

[0106] The first resource is used to receive at least one failed TB and a second TB sent by the IoT device, wherein the first resource is a resource configured by the network device for sending the second TB, and the second TB is a new TB to be sent by the IoT device.

[0107] In conjunction with some embodiments of the second aspect, in some embodiments, receiving at least two TBs merged and transmitted by the IoT device includes:

[0108] Receive a third TB, which is obtained by merging at least one failed TB and the second TB in chronological order, and adding a CRC; or,

[0109] Receive the fourth TB, which is obtained by adding CRC to at least one failed TB and the second TB and merging them in chronological order.

[0110] In conjunction with some embodiments of the second aspect, in some embodiments, the method includes:

[0111] Receive first information, which indicates the number of TBs that the IoT device is sending in this merge, and the length of each TB.

[0112] In conjunction with some embodiments of the second aspect, in some embodiments, when the IoT device is a device that operates based on backscattering and the type of uplink transmission of the IoT device is a periodic service, the period for the IoT device to transmit the uplink data is an integer multiple of the period of a continuous electromagnetic wave (CW), which is used by the IoT device for backscattering to transmit data.

[0113] Thirdly, embodiments of this disclosure provide an Internet of Things (IoT) device, comprising:

[0114] A transceiver module is used to send uplink data to network devices, the uplink data including at least one transport block (TB).

[0115] Fourthly, embodiments of this disclosure provide a network device, including:

[0116] The transceiver module is used to receive uplink data sent by Internet of Things (IoT) devices, wherein the uplink data includes at least one transport block (TB).

[0117] Fifthly, embodiments of this disclosure provide a communication device, comprising:

[0118] One or more processors;

[0119] The communication device is used to perform the communication method described in the first or second aspect.

[0120] In a sixth aspect, embodiments of this disclosure provide a communication system comprising: an IoT device and a network device; wherein the IoT device is configured to perform the method described in the optional implementation of the first aspect, and the network device is configured to perform the method described in the optional implementation of the second aspect.

[0121] In a seventh aspect, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method as described in the optional implementations of the first and second aspects.

[0122] Eighthly, embodiments of this disclosure provide a computer program product, including a computer program and / or instructions, which, when executed by a communication device, cause the communication device to perform the method as described in the optional implementations of the first and second aspects.

[0123] In a ninth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described in alternative implementations of the first and second aspects.

[0124] In a tenth aspect, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the methods described according to optional implementations of the first and second aspects above.

[0125] It is understood that the aforementioned IoT devices, network devices, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0126] This disclosure provides communication methods, devices, systems, and storage media. In some embodiments, the terms "communication method" and "information processing method," "capability reporting method," etc., can be used interchangeably; the terms "communication device" and "information processing device," "capability reporting device," etc., can be used interchangeably; and the terms "information processing system" and "communication system," etc., can be used interchangeably.

[0127] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

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

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

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

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

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

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

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

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

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

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

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

[0139] 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”.

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

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

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

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

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

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

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

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

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

[0149] Figure 1A is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. As shown in Figure 1A, the communication system 100 includes an Internet of Things (IoT) device 101 and a network device 102. Optionally, the network device 102 may include at least one of an access network device and a core network device.

[0150] In the communication system architecture shown in Figure 1A, IoT device 101 and network device 102 can directly receive and transmit DL and UL data. In some other possible implementations, IoT device 101 can receive and transmit DL and UL data with network device 102 through an intermediate node.

[0151] Figure 1B is a schematic diagram of the architecture of another communication system according to an embodiment of the present disclosure. As shown in Figure 1B, the communication system 200 includes an IoT device 101, a network device 102, and an intermediate node 103. There is an intermediate node between the IoT device 101 and the network device 102 for forwarding. The intermediate node 103 may be, for example, a relay, an Integrated Access and Backhaul (IAB) node, a user equipment, or a repeater.

[0152] In some embodiments, IoT device 101 can be an Ambient IoT (A-IoT) device. Compared with traditional IoT technology, a significant feature is that the number of A-IoT devices (such as A-IoT UE, A-IoT device, A-IoT Tag) that can be accessed in the network is large, and the structure is simple, the hardware and maintenance costs are low, the power consumption is low, and the battery can be used for a long time without needing to be replaced.

[0153] In some embodiments, A-IoT devices can be applied to scenarios involving large-scale inventory management, where A-IoT devices report Electronic Product Codes (EPCs) to network device 102, intermediate nodes, or user devices. They can also be applied to sensing scenarios such as smart homes and environmental monitoring, where data is reported upon meeting certain triggering conditions. Furthermore, they can be used in location scenarios to locate items or pinpoint locations within shopping malls. Finally, they can be used in command scenarios to respond to commands sent by network device 102.

[0154] In some embodiments, A-IoT devices may include the following types of devices:

[0155] Type 1: Peak power consumption is 1uW, with energy storage, but cannot perform independent signal generation / amplification; for example, it uses a backscattering operating mode. It lacks downlink (DL) and / or uplink (UL) signal amplification capabilities.

[0156] Type 2: Peak power consumption is several hundred µW, with energy storage capability, but cannot generate signals independently; it operates using backscattering. The stored energy can be used for DL ​​and / or UL signal amplification.

[0157] Type 3: Peak power consumption is several hundred uW, with energy storage capacity, and can generate signals independently, such as RF modules that actively transmit signals.

[0158] Type 4: Possesses both the ability to actively transmit information and the ability to backscatter.

[0159] Among them, Type 1 and Type 2 devices can only use the backscattering working mode and cannot actively send signals. When they need to send information, they must be provided with electromagnetic waves (continuous waves, CW) from the outside for backscattering.

[0160] In some embodiments, for devices using backscattering, a continuous electromagnetic wave (CW) energy source (CW node) is required to provide electromagnetic waves for reflection while transmitting data. The CW is generally of constant amplitude. A CW node can be a standalone node or a network / intermediate node (e.g., user equipment or terminal) communicating with IoT devices. The A-IoT device reflects the received CW, loads the signaling / data to be transmitted onto the reflected wave, and sends it out. The reflected wave and the CW are at the same frequency or have a certain frequency offset. Simultaneously, the CW also serves to power the A-IoT device. When a Type 1 device receives the wireless signal CW, it activates its internal receiving and processing module to encode and modulate the signaling / data that the A-IoT device needs to upload.

[0161] In some embodiments, devices in an A-IoT network may include network devices, user devices, intermediate nodes, auxiliary nodes, etc. Intermediate nodes may be relays, IAB nodes, user devices, or repeaters.

[0162] In some embodiments, the user equipment includes, but is not limited to, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication capabilities, smart car, tablet computer, computer with wireless transceiver capabilities, 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.

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

[0164] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. 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.

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

[0166] In some embodiments, the core network equipment can be a single device, including a first network element, a second network element, etc., or it can be multiple devices or a group of devices, each including all or part of the first network element, the second network element, etc. Network elements can be virtual or physical. The core network includes, for example, at least one of the Evolved Packet Core (EPC), 5G Core Network (5GCN), and Next Generation Core (NGC).

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

[0168] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1A, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1A are illustrative. The communication system may include all or some of the main bodies in FIG1A, or it may include other main bodies outside of FIG1A. The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies 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.

[0169] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, 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, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0170] In some embodiments, such as in the communication system shown in Figure 1A or Figure 1B, data transmission by the IoT device includes the following types:

[0171] Type 1: Based on network demand report data, such as inventory count. This refers to device-initiated but device-terminated (DO-DTT) services that require a trigger message to terminate.

[0172] Type 2: Based on A-IoT device triggering, actively reporting data, for example, the temperature of the sensor (Sesor) is higher than the configured threshold. That is, device-initiated (DO) service.

[0173] Type 3: Periodic Data Reporting. This involves periodic reporting of environmental IoT data, triggered automatically by the IoT device. In other words, it's a Device-originated-autonomous (DO-A) service.

[0174] Type 4: The network side sends a command, and the device performs the corresponding operation based on the command. This means the device terminates (DT) the service.

[0175] In some embodiments, it is necessary to further enhance DOA services, sensor, and positioning application scenarios. Here, "sensor" refers to a device that can perceive its surrounding environment and obtain environmental information such as temperature and humidity. This requires supporting device-initiated services, i.e., DOA services, which typically involve periodic uplink transmissions without requiring network device triggering, to support environment awareness-related applications. In positioning scenarios, through information exchange between network devices and terminals, the network device obtains the terminal's location information, etc.

[0176] In some embodiments, to ensure reliability for uplink transmission, uplink retransmission and forward error correction (FEC) coding were investigated. Both methods can improve transmission reliability. Uplink retransmission is simpler to implement on the device compared to FEC coding. FEC coding requires multiple registers within the device to support encoding, which increases the device's complexity and cost to some extent. Additionally, the network side needs to perform decoding. However, although FEC is complex, it is still feasible for the device.

[0177] Figure 2A is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2A, the embodiments of the present disclosure relate to a communication method, which includes:

[0178] In step S2101, the IoT device determines, based on the first condition, whether uplink data transmission uses both retransmission and FEC encoding.

[0179] In some embodiments, the IoT device may be an A-IoT device. Optionally, the IoT device may be a 6G IoT device. Optionally, the IoT device may be a 6G A-IoT device.

[0180] In some embodiments, the uplink data includes at least one TB.

[0181] In some embodiments, the first condition includes at least one of the following:

[0182] Condition A: The signal quality indicator (QI) value of the data service of the IoT device is within the preset QI value range;

[0183] Condition B: The size of TB is greater than the preset size threshold;

[0184] Condition C: The priority value of TB is less than the preset priority value threshold;

[0185] Condition D: The IoT device supports feedback based on Hybrid Automatic Repeat Request (HARQ), and the number of negative acknowledgments (NACKs) received from the network device after sending M TBs is greater than or equal to N, where M and N are preset positive integers.

[0186] Condition E: The IoT device supports HARQ-based feedback, and the number of NACKs received from the network device within a preset time period is greater than a preset threshold.

[0187] In some embodiments, the QI value can be a parameter representing the QoS of the service, such as priority level, PDB value, packet error rate, etc. Optionally, a predefined range of QI values ​​indicates that the data service has high reliability requirements.

[0188] In some embodiments, the TB in the uplink data may have a corresponding priority value. Optionally, the preset priority value threshold may be a value pre-configured by RRC or a value pre-agreed upon by the protocol.

[0189] In some embodiments, the values ​​of M and N in condition D, the preset duration of UI in condition E, and the preset quantity threshold can be configured by the network device, agreed upon in advance by the protocol, or determined by the IoT device itself. This disclosure does not limit these aspects.

[0190] Optionally, the IoT device may determine that uplink data transmission uses both retransmission and FEC encoding when the first condition is met. Optionally, the IoT device may determine that uplink data transmission does not use both retransmission and FEC encoding when the first condition is not met. Optionally, the IoT device may determine that uplink data transmission uses only retransmission when the first condition is not met.

[0191] In some embodiments, the IoT device may determine that the first condition is met if any one of the first conditions is satisfied. Optionally, the IoT device may determine that the first condition is not met if all of the first conditions are not satisfied.

[0192] In some embodiments, the IoT device may determine that the first condition is met if all conditions in the first condition are met. Optionally, the IoT device may determine that the first condition is not met if any one of the conditions in the first condition is not met.

[0193] For example, the first condition may include the above conditions A, B and C. When the IoT device determines that condition C is met, the first condition can be determined to be met. Alternatively, the first condition can be determined to be met only when the IoT device determines that conditions A, B and C are met simultaneously.

[0194] In step S2102, the IoT device sends uplink data to the network device.

[0195] In some embodiments, the IoT device uses both retransmission and FEC encoding to send uplink data to the network device. Optionally, the IoT device uses only retransmission to send uplink data to the network device.

[0196] In some embodiments, the network device receives uplink data sent by the IoT device. Optionally, the network device receives at least one TB of data sent by the IoT device. Optionally, the uplink data uses both retransmission and FEC encoding, wherein whether the uplink data uses both retransmission and forward error correction (FEC) encoding is determined based on a first condition.

[0197] In this embodiment of the disclosure, when the IoT device is a device that operates based on backscattering and the type of uplink transmission of the IoT device is a periodic service, the period for the IoT device to transmit uplink data is an integer multiple of the period of CW, and CW is used by the IoT device for backscattering to transmit data.

[0198] In this embodiment of the disclosure, when an IoT device sends data or signaling to a network device, it can mean that the IoT device sends the data or signaling directly to the network device, or that the IoT device first sends the data or signaling to an intermediate node, and then the intermediate node forwards the data or signaling to the network device. Correspondingly, when a network device sends data or signaling to an IoT device, it can mean that the network device sends the data or signaling directly to the IoT device, or that the network device first sends the data or signaling to an intermediate node, and then the intermediate node forwards the data or signaling to the IoT device. Optionally, there can be one or more intermediate nodes.

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

[0200] In some embodiments, the terms "codebook," "codeword," and "precoding matrix" can be used interchangeably. For example, a codebook can be a collection of one or more codewords / precoding matrices.

[0201] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".

[0202] In some embodiments, the terms “downlink control information (DCI),” “downlink (DL) assignment,” “DL DCI,” “uplink (UL) grant,” and “UL DCI” can be used interchangeably.

[0203] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, as can terms such as "physical uplink shared channel (PUSCH)" and "UL data".

[0204] In some embodiments, the terms "synchronization signal (SS)," "synchronization signal block (SSB)," "reference signal (RS)," "pilot," and "pilot signal" can be used interchangeably.

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

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

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

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

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

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

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

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

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

[0214] The communication method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2102. For example, step S2101 may be implemented as a separate embodiment, and step S2102 may be implemented as a separate embodiment, but are not limited thereto.

[0215] In some embodiments, step S2102 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

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

[0217] Figure 2B is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2B, the embodiments of the present disclosure relate to a communication method, which includes:

[0218] Step S2201: The IoT device and the network device determine that the IoT device supports HARQ-based retransmission and determine the reserved resources.

[0219] In some embodiments, the reserved resources are configured for network devices. Optionally, the reserved resources are used for retransmission of uplink data. Optionally, the reserved resources are used for retransmission of TBs of uplink data.

[0220] In some embodiments, an IoT device may send capability information to a network device, which can be used to indicate whether the IoT device supports HARQ-based retransmission. The network device can determine whether the IoT device supports HARQ retransmission based on this capability information.

[0221] In some embodiments, the network device may configure reserved resources for the IoT device when it determines that the IoT device supports HARQ-based retransmission. Optionally, the network device sends configuration information to the IoT device, which may be used to indicate the reserved resources configured by the network device for the IoT device.

[0222] In some embodiments, the IoT device determines that it supports HARQ-based retransmission and expects to receive configuration information from the network device. This configuration information indicates the reserved resources configured by the network device for the IoT device. Optionally, the IoT device determines the reserved resources based on the configuration information sent by the network device.

[0223] In some embodiments, reserved resources include at least one of time-domain resources, frequency-domain resources, or spatial-domain resources. For example, the reserved resources configured by the network device for the IoT device may include only time-domain resources, or may include time-frequency domain resources, or may include time-domain resources, spatial domain resources, and frequency domain resources simultaneously.

[0224] In some embodiments, the number of reserved resources configured by the network device for a TB is one or more, and there is a time interval between every two adjacent resources among the multiple reserved resources configured by the network device for a TB. Optionally, the unit of the time interval can be any of the following: subframe, time slot, OFDM symbol, chip.

[0225] For example, a network device can configure 3 resources for a TB, with a time interval of two OFDM symbols between each pair of adjacent resources.

[0226] In some embodiments, the maximum number of reserved resources configured by the network device for one TB can be Rmax. The value of Rmax can be pre-configured by the network device, for example, the network device can configure it according to the capabilities of the IoT device, or it can be agreed by the protocol. This disclosure does not limit this.

[0227] In some embodiments, when the uplink transmission type of the IoT device is a periodic service, the network device configures the resources for TB transmission as periodic resources, and reserved resources are configured in each period.

[0228] In some embodiments, the number of frequency domain resource elements (RFIs) is the same for each reserved resource, and the positions of the RRIs of the RRIs of each reserved resource may be the same or different. Optionally, the number of RRIs is either PRB or RE.

[0229] For example, if a network device reserves two resources for 1TB of transmission for an IoT device, namely resources r1 and r2, the frequency domain resource corresponding to resource r1 is f1, and the frequency domain resource corresponding to resource r2 is f2. The frequency domain resource unit is PRB. Both f1 and f2 contain 5 PRBs, but the positions of the PRBs can be different. For example, f1 contains PRBs with sequence numbers 20-25, but f2 contains PRBs with sequence numbers 80-85.

[0230] In step S2202, the IoT device sends the first TB to the network device.

[0231] In some embodiments, the first TB can be any TB included in the uplink data. It is understood that when the IoT device sends each TB to the network device, steps S2202 to S2204 can be repeated until the uplink data transmission is complete.

[0232] In some embodiments, the network device receives a first TB sent by the IoT device. Optionally, after receiving the first TB, the network device sends an ACK or NACK response. Optionally, when the network device sends an ACK, the IoT device can determine that the first TB was successfully sent; when the network device sends a NACK, the IoT device can determine that the first TB was not successfully sent.

[0233] Step S2203: The IoT device listens for ACK or NACK within a preset time window.

[0234] In some embodiments, the IoT device determines that the first TB has been sent and listens for confirmation ACK or NACK within a preset time window.

[0235] In some embodiments, the start time of the preset time window and the time when the first TB is sent are subject to a certain time interval, and the end time of the preset time window and the first TB are also subject to a certain time interval.

[0236] In some embodiments, the first interval between the first time and the second time is greater than or equal to the first interval threshold, and the second interval between the second time and the third time is greater than the second interval threshold; the first time is the transmission time of the first TB, the second time is the start time of the preset time window, and the third time is the end time of the preset time window.

[0237] The first interval threshold and the second interval threshold can be configured by the network device, agreed upon in advance by the protocol, or determined by the IoT device itself. This embodiment does not limit these settings.

[0238] In step S2204, the IoT device determines whether to use reserved resources to retransmit the first TB based on the monitoring results.

[0239] In some embodiments, the result of the monitoring includes at least one of the following: ACK is detected within a preset time window; NACK is detected within a preset time window.

[0240] In some embodiments, the IoT device determines whether to use reserved resources to retransmit the first TB based on the monitoring result, including at least one of the following: if an ACK is detected, the reserved resources are no longer used to retransmit the first TB; if a NACK is detected, the reserved resources are used to retransmit the first TB.

[0241] In some embodiments, the IoT device retransmits the first TB only after receiving a NACK from the network device for the first TB. Optionally, the IoT device stops retransmitting the first TB only after receiving an ACK from the network device for the first TB.

[0242] In this embodiment of the disclosure, when the IoT device is a device that operates based on backscattering and the type of uplink transmission of the IoT device is a periodic service, the period for the IoT device to transmit uplink data is an integer multiple of the period of CW, and CW is used by the IoT device for backscattering to transmit data.

[0243] The communication method involved in the embodiments of this disclosure may include at least one of steps S2201 to S2204. For example, step S2201 may be implemented as an independent embodiment, step S2204 may be implemented as an independent embodiment, step S2202 + step S2203 may be implemented as an independent embodiment, steps S2202 to S2204 may be implemented as independent embodiments, and steps S2201 to S2203 may be implemented as independent embodiments, but are not limited thereto.

[0244] In some embodiments, steps S2202 to S2204 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0245] In some embodiments, steps S2201 to S2203 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

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

[0247] Figure 2C is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2C, the embodiments of the present disclosure relate to a communication method, which includes:

[0248] Step S2301: The IoT device and the network device determine that the IoT device supports blind retransmission and determine the reserved resources.

[0249] In some embodiments, the reserved resources are configured for network devices. Optionally, the reserved resources are used for blind retransmission of uplink data. Optionally, the reserved resources are used for blind retransmission of TBs of uplink data.

[0250] In some embodiments, an IoT device can send capability information to a network device, which can be used to indicate whether the IoT device supports blind retransmission. The network device can determine whether the IoT device supports blind retransmission based on the capability information.

[0251] In some embodiments, the network device may configure reserved resources for the IoT device when it determines that the IoT device supports blind retransmission. Optionally, the network device sends configuration information to the IoT device, which may be used to indicate the reserved resources configured by the network device for the IoT device.

[0252] In some embodiments, the IoT device determines that it supports blind retransmission and expects to receive configuration information sent by the network device. This configuration information indicates the reserved resources configured by the network device for the IoT device. Optionally, the IoT device determines the reserved resources based on the configuration information sent by the network device.

[0253] In some embodiments, reserved resources include at least one of time-domain resources, frequency-domain resources, or spatial-domain resources. For example, the reserved resources configured by the network device for the IoT device may include only time-domain resources, or may include time-frequency domain resources, or may include time-domain resources, spatial domain resources, and frequency domain resources simultaneously.

[0254] In some embodiments, the number of reserved resources configured by the network device for a TB is one or more, and there is a time interval between every two adjacent resources among the multiple reserved resources configured by the network device for a TB. Optionally, the unit of the time interval can be any of the following: subframe, time slot, OFDM symbol, chip.

[0255] For example, a network device can configure 3 resources for a TB, with a time interval of two OFDM symbols between each pair of adjacent resources.

[0256] In some embodiments, the maximum number of reserved resources configured by the network device for one TB can be Rmax. The value of Rmax can be pre-configured by the network device, for example, the network device can configure it according to the capabilities of the IoT device, or it can be agreed by the protocol. This disclosure does not limit this.

[0257] In some embodiments, the maximum number of reserved resources configured by the network device for one TB can be Rmax. The value of Rmax can be pre-configured by the network device, for example, the network device can configure it according to the capabilities of the IoT device, or it can be agreed by the protocol. This disclosure does not limit this.

[0258] In some embodiments, when the uplink transmission type of the IoT device is a periodic service, the network device configures the resources for TB transmission as periodic resources, and reserved resources are configured in each period.

[0259] In some embodiments, the number of frequency domain resource elements (RFIs) is the same for each reserved resource, and the positions of the RRIs of the RRIs of each reserved resource may be the same or different. Optionally, the number of RRIs is either PRB or RE.

[0260] For example, if a network device reserves two resources for 1TB of transmission for an IoT device, namely resources r1 and r2, the frequency domain resource corresponding to resource r1 is f1, and the frequency domain resource corresponding to resource r2 is f2. The frequency domain resource unit is PRB. Both f1 and f2 contain 5 PRBs, but the positions of the PRBs can be different. For example, f1 contains PRBs with sequence numbers 20-25, but f2 contains PRBs with sequence numbers 80-85.

[0261] In step S2302, the IoT device uses reserved resources to perform blind retransmission of uplink data.

[0262] In some embodiments, after sending the first TB, the IoT device determines that the reserved resources configured by the network device for the first TB have arrived, and uses the reserved resources to perform blind retransmission of the first TB. Optionally, the arrival of reserved resources may mean that the resources allocated by the network device for the IoT device are available.

[0263] In some embodiments, the number of blind retransmissions of the first TB is equal to the number of reserved resources configured by the network device for the first TB.

[0264] In some embodiments, the first TB can be any TB included in the uplink data. It is understood that when the IoT device sends each TB to the network device, it can utilize the corresponding reserved resources configured by the network device for blind retransmission until the uplink data transmission is complete.

[0265] It should be understood that when an IoT device supports blind retransmission, after the network device receives the TB sent by the IoT device, the network device may not return ACK or NACK, and the IoT device may also retransmit directly when the resource for blind retransmission arrives without waiting for ACK and NACK.

[0266] In this embodiment of the disclosure, when the IoT device is a device that operates based on backscattering and the type of uplink transmission of the IoT device is a periodic service, the period for the IoT device to transmit uplink data is an integer multiple of the period of CW, and CW is used by the IoT device for backscattering to transmit data.

[0267] The communication method involved in the embodiments of this disclosure may include at least one of steps S2301 to S2302. For example, step S2301 may be implemented as a separate embodiment, and step S2302 may be implemented as a separate embodiment, but are not limited thereto.

[0268] Figure 2D is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2D, the embodiments of the present disclosure relate to a communication method, which includes:

[0269] Step S2401: The IoT device and the network device determine that the IoT device supports HARQ-based retransmission and determine the reserved resources.

[0270] In some embodiments, the reserved resources are configured for network devices. Optionally, the reserved resources are used for retransmission of uplink data. Optionally, the reserved resources are used for retransmission of TBs of uplink data.

[0271] In some embodiments, an IoT device may send capability information to a network device, which can be used to indicate whether the IoT device supports HARQ-based retransmission. The network device can determine whether the IoT device supports HARQ retransmission based on this capability information.

[0272] In some embodiments, the network device may configure reserved resources for the IoT device when it determines that the IoT device supports HARQ-based retransmission. Optionally, the network device sends configuration information to the IoT device, which may be used to indicate the reserved resources configured by the network device for the IoT device.

[0273] In some embodiments, the IoT device determines that it supports HARQ-based retransmission and expects to receive configuration information from the network device. This configuration information indicates the reserved resources configured by the network device for the IoT device. Optionally, the IoT device determines the reserved resources based on the configuration information sent by the network device.

[0274] In some embodiments, reserved resources include at least one of time-domain resources, frequency-domain resources, or spatial-domain resources. For example, the reserved resources configured by the network device for the IoT device may include only time-domain resources, or may include time-frequency domain resources, or may include time-domain resources, spatial domain resources, and frequency domain resources simultaneously.

[0275] In some embodiments, the number of reserved resources configured by the network device for a TB is one or more, and there is a time interval between every two adjacent resources among the multiple reserved resources configured by the network device for a TB. Optionally, the unit of the time interval can be any of the following: subframe, time slot, OFDM symbol, chip.

[0276] For example, a network device can configure 3 resources for a TB, with a time interval of two OFDM symbols between each pair of adjacent resources.

[0277] In some embodiments, the maximum number of reserved resources configured by the network device for one TB can be Rmax. The value of Rmax can be pre-configured by the network device, for example, the network device can configure it according to the capabilities of the IoT device, or it can be agreed by the protocol. This disclosure does not limit this.

[0278] In some embodiments, when the uplink transmission type of the IoT device is a periodic service, the network device configures the resources for TB transmission as periodic resources, and reserved resources are configured in each period.

[0279] In some embodiments, the number of frequency domain resource elements (RFIs) is the same for each reserved resource, and the positions of the RRIs of the RRIs of each reserved resource may be the same or different. Optionally, the number of RRIs is either PRB or RE.

[0280] For example, if a network device reserves two resources for 1TB of transmission for an IoT device, namely resources r1 and r2, the frequency domain resource corresponding to resource r1 is f1, and the frequency domain resource corresponding to resource r2 is f2. The frequency domain resource unit is PRB. Both f1 and f2 contain 5 PRBs, but the positions of the PRBs can be different. For example, f1 contains PRBs with sequence numbers 20-25, but f2 contains PRBs with sequence numbers 80-85.

[0281] In step S2402, the IoT device determines that a TB has received NACKs from the network device on all reserved resources, and thus determines that the TB transmission failed.

[0282] In some embodiments, for a TB, the IoT device determines that the TB transmission has failed if it receives a NACK from the network device on every reserved resource. Optionally, for a first TB, the IoT device determines that the first TB transmission has failed if it receives a NACK from the network device on every reserved resource allocated by the network device for the first TB.

[0283] Step S2403: The IoT devices merge at least two TBs to obtain a third or fourth TB.

[0284] In some embodiments, the third TB or the fourth TB may also be referred to as at least two TBs sent in a merged manner. Optionally, the at least two TBs sent in a merged manner include at least one failed TB.

[0285] In some embodiments, the at least two TBs to be sent in a merged manner include one or more TBs that failed to be sent, and a second TB. Optionally, the second TB is a new TB to be sent by the IoT device. Optionally, the second TB is a TB whose corresponding resource is about to arrive. Optionally, the resource corresponding to the second TB can be a first resource, which can be a resource configured by the network device for sending the second TB.

[0286] In some embodiments, the third interval between the fourth time and the fifth time is less than or equal to a third interval threshold, wherein the fourth time is the transmission time of the first TB among the at least one failed TB, and the fifth time is the start time of the first resource. That is, among the merged TBs, the time interval between the transmission time of the earliest failed TB and the start time of the first resource is less than or equal to the third interval threshold.

[0287] The third interval threshold can be configured by the network device, pre-agreed by the protocol, or determined by the IoT device itself. This embodiment does not limit this.

[0288] In some embodiments, the third TB is obtained by merging at least one failed TB and the second TB in chronological order and adding a CRC.

[0289] In some embodiments, the fourth TB is obtained by adding CRC to at least one failed TB and the second TB respectively and merging them in chronological order.

[0290] For example, the uplink data may include TB1, TB2, TB3, and TB4 transmitted sequentially in time. The IoT device determines that TB2 and TB3 failed to transmit, and TB4 is the new TB to be transmitted. The IoT device can then merge TB2, TB3, and TB4 to obtain a third TB or a fourth TB. The third TB can be represented, for example, as CRC+TB2+TB3+TB4, and the fourth TB can be represented, for example, as (CRC1+TB2)+(CRC2+TB3)+(CRC3+TB4).

[0291] It is understandable that multiple TBs transmitted sequentially in time can refer to the resources used to transmit these TBs arriving in chronological order. For example, TB1, TB2, TB3, and TB4 transmitted sequentially in time can be understood as TB1's resources arriving first and TB4's resources arriving last.

[0292] In step S2404, the IoT device sends the third TB or the fourth TB to the network device.

[0293] In some embodiments, the IoT device uses the first resource to send a third TB or a fourth TB. Optionally, the IoT device uses the first resource to send at least one failed TB along with a second TB.

[0294] In some embodiments, the network device receives a third TB or a fourth TB sent by the IoT device. Optionally, the network device uses a first resource to receive the third TB or the fourth TB sent by the IoT device.

[0295] Optionally, the third or fourth TB is sent by the IoT device when it determines that the TB transmission has failed, provided that HARQ-based retransmission is supported.

[0296] In some embodiments, the network device receives at least two TBs of data transmitted in a merged manner by the IoT device. Optionally, the network device uses a first resource to receive at least two TBs of data transmitted in a merged manner by the IoT device.

[0297] Optionally, the at least two TBs sent in the merged transmission are sent when the IoT device determines that the TB transmission has failed, provided that HARQ-based retransmission is supported, and the at least two TBs include at least one failed TB.

[0298] In some embodiments, the third TB is obtained by merging at least one failed TB and the second TB in chronological order and adding a CRC.

[0299] In some embodiments, the fourth TB is obtained by adding CRC to at least one failed TB and the second TB respectively and merging them in chronological order.

[0300] In some embodiments, the transmission of a third TB or a fourth TB from an IoT device to a network device may be pre-agreed upon by a protocol or instructed by the network device. For example, an IoT device may transmit a third TB or a fourth TB to a network device by default, or it may transmit a third TB or a fourth TB in response to an instruction from the network device. This disclosure does not limit the scope of the embodiments.

[0301] In step S2405, the IoT device sends the first information to the network device.

[0302] In some embodiments, the first information is also used to indicate the length of each of the at least two TBs that the IoT device is currently merging and sending.

[0303] In some embodiments, the first information is used to indicate the number of TBs that the IoT device is sending in this merge.

[0304] In some embodiments, the first information is used to indicate that the third TB or the fourth TB (i.e., at least two TBs sent in a merged manner) is obtained by merging several failed TBs with the second TB.

[0305] In some embodiments, the first information is used by the network device to decode the TB that is merged and sent by the IoT device.

[0306] In some embodiments, the network device receives first information sent by the IoT device. Optionally, the network device decodes the first information to obtain each TB that the IoT device has merged and sent in this instance.

[0307] In some embodiments, the first information may be a Medium Access Control-Control Element (MAC-CE), or one or more fields included in the MAC-CE.

[0308] In some embodiments, the first information may be referred to as "merging instruction information", "control information", etc., and the name is not limited in the embodiments disclosed herein.

[0309] In some embodiments, the number of TBs (terabytes) that the IoT device is merging and sending in this instance can be indicated implicitly. For example, the number of TBs can be indicated by the length of the TBs in the first information. For instance, if the first information is [size1, size2, size3, size4], where size1 indicates the length of the first TB in the merged and sent TB, size2 indicates the length of the second TB, size3 indicates the length of the third TB, and size4 indicates the length of the fourth TB, the network device can determine that the number of TBs merged and sent by the IoT device in this instance is 4, and determine the length of each TB.

[0310] In some embodiments, steps S2403 and S2405 may be performed in an alternate order or simultaneously.

[0311] In some embodiments, steps S2404 and S2405 may be performed in an alternate order or simultaneously.

[0312] In this embodiment of the disclosure, when the IoT device is a device that operates based on backscattering and the type of uplink transmission of the IoT device is a periodic service, the period for the IoT device to transmit uplink data is an integer multiple of the period of CW, and CW is used by the IoT device for backscattering to transmit data.

[0313] The communication method involved in the embodiments of this disclosure may include at least one of steps S2401 to S2405. For example, step S2401 may be implemented as a standalone embodiment, step S2404 may be implemented as a standalone embodiment, step S2402 + step S2403 may be implemented as a standalone embodiment, steps S2403 to S2405 may be implemented as standalone embodiments, and steps S2401 to S2404 may be implemented as standalone embodiments, but is not limited thereto.

[0314] In some embodiments, steps S2402 to S2405 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0315] In some embodiments, steps S2401 to S2404 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

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

[0317] Figure 3A is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 3A, the embodiments of the present disclosure relate to a communication method, which includes:

[0318] Step S3101: The IoT device sends uplink data to the network device.

[0319] Optional implementations of step S3101 can be found in the optional implementations of steps S2101 to S2102 in FIG2A, steps S2201 to S2204 in FIG2B, steps S2301 to S2302 in FIG2C, and steps S2401 to S2405 in FIG2D, as well as other related parts in the embodiments involved in FIG2A to FIG2D.

[0320] In some embodiments, the method includes:

[0321] Based on the first condition, the IoT device determines whether uplink data transmission uses both retransmission and forward error correction (FEC) coding simultaneously.

[0322] The first condition includes at least one of the following:

[0323] The signal quality indicator (QI) value of the data service of IoT devices is within the preset QI value range;

[0324] The size of TB is greater than the preset size threshold;

[0325] The priority value of TB is less than the preset priority value threshold;

[0326] IoT devices support feedback based on Hybrid Automatic Repeat Request (HARQ), and the number of negative acknowledgments (NACKs) received from the network device after sending M TBs is greater than or equal to N, where M and N are preset positive integers.

[0327] IoT devices support HARQ-based feedback, and the number of NACKs received from network devices within a preset time period is greater than a preset threshold.

[0328] In some embodiments, the method includes:

[0329] The IoT device is determined to support blind retransmission or HARQ-based retransmission, and reserved resources are determined. The reserved resources are configured by the network device and are used for blind retransmission or retransmission of uplink data.

[0330] In some embodiments, the method includes:

[0331] If an IoT device determines that the first TB has been sent and supports retransmission based on HARQ feedback, it will listen for ACK or NACK confirmation within a preset time window.

[0332] Based on the monitoring results, IoT devices determine whether to use reserved resources to retransmit the first TB.

[0333] The first TB refers to any TB included in the uplink data.

[0334] In some embodiments, based on the results of the monitoring, determining whether to use reserved resources for retransmission of the first TB includes at least one of the following:

[0335] Once the IoT device confirms that it has received an ACK, it will no longer use the reserved resources to retransmit the first TB.

[0336] If the IoT device detects a NACK, it will use the reserved resources to retransmit the first TB.

[0337] In some embodiments, the first interval between the first time and the second time is greater than or equal to a first interval threshold, and the second interval between the second time and the third time is greater than a second interval threshold;

[0338] The first time is the transmission time of the first TB, the second time is the start time of the preset time window, and the third time is the end time of the preset time window.

[0339] In some embodiments, the number of blind retransmissions of the first TB is equal to the number of reserved resources configured by the network device for the first TB, where the first TB is any TB included in the uplink data.

[0340] In some embodiments, the reserved resources include at least one of time-domain resources, frequency-domain resources, or spatial-domain resources;

[0341] The number of reserved resources configured by a network device for a TB is one or more, and there is a time interval between each two adjacent resources among the multiple reserved resources configured by the network device for a TB.

[0342] In some embodiments, when the uplink transmission type of the IoT device is a periodic service, the network device configures the resources for TB transmission as periodic resources, and reserved resources are configured in each period.

[0343] In some embodiments, the number of frequency domain resource units in each reserved resource is the same, and the positions of the frequency domain resource units in each reserved resource are the same or different.

[0344] In some embodiments, sending uplink data to a network device includes:

[0345] If an IoT device supports HARQ-based retransmission, and determines that a TB transmission has failed, it will merge and transmit at least two TBs, with the two TBs including at least one failed TB.

[0346] In some embodiments, the method includes:

[0347] For a TB, an IoT device determines that the TB transmission has failed if it receives a NACK from the network device on all reserved resources.

[0348] In some embodiments, the combined transmission of at least two TBs includes:

[0349] The IoT device uses a first resource to send at least one failed TB and a second TB. The first resource is a resource configured by the network device for sending the second TB, and the second TB is a new TB to be sent by the IoT device.

[0350] In some embodiments, the third interval between the fourth time and the fifth time is less than or equal to a third interval threshold, the fourth time is the transmission time of the first TB in at least one failed TB, and the fifth time is the start time of the first resource.

[0351] In some embodiments, the combined transmission of at least two TBs includes:

[0352] The IoT device sends a third TB, which is obtained by merging at least one failed TB and the second TB in chronological order and adding a CRC checksum; or,

[0353] The IoT device sends a fourth TB, which is obtained by adding CRC to at least one failed TB and the second TB respectively and merging them in chronological order.

[0354] In some embodiments, the method includes:

[0355] The IoT device sends a first message indicating the number of TBs to be sent in this merge and the length of each TB.

[0356] In some embodiments, when the IoT device is a device that operates based on backscattering and the type of uplink transmission of the IoT device is a periodic service, the period for the IoT device to transmit uplink data is an integer multiple of the period of the continuous electromagnetic wave (CW), which is used by the IoT device for backscattering to transmit data.

[0357] In some embodiments, the method includes:

[0358] The network device receives uplink data sent by the Internet of Things (IoT) device, and the uplink data includes at least one transport block (TB).

[0359] In some embodiments, uplink data uses both retransmission and forward error correction (FEC) coding simultaneously, wherein whether uplink data uses both retransmission and FEC coding simultaneously is determined based on a first condition, the first condition including at least one of the following:

[0360] The QI value of data services on IoT devices is within the preset QI value range;

[0361] The size of TB is greater than the preset size threshold;

[0362] The priority value of TB is less than the preset priority value threshold;

[0363] IoT devices support feedback based on Hybrid Automatic Repeat Request (HARQ), and the number of negative acknowledgments (NACKs) received from the network device after sending M TBs is greater than or equal to N, where M and N are preset positive integers.

[0364] IoT devices support HARQ-based feedback, and the number of NACKs received from network devices within a preset time period is greater than a preset threshold.

[0365] In some embodiments, the method includes:

[0366] The network device determines that the IoT device supports blind retransmission or retransmission based on HARQ feedback, and determines the reserved resources, which are used for blind retransmission or retransmission of uplink data.

[0367] In some embodiments, the number of blind retransmissions of the first TB is equal to the number of reserved resources configured by the network device for the first TB, where the first TB is any TB included in the uplink data.

[0368] In some embodiments, the reserved resources include at least one of time-domain resources, frequency-domain resources, or spatial-domain resources;

[0369] The number of reserved resources configured by a network device for a TB is one or more, and there is a time interval between each two adjacent resources among the multiple reserved resources configured by the network device for a TB.

[0370] In some embodiments, when the uplink transmission type of the IoT device is a periodic service, the network device configures the resources for TB transmission as periodic resources, and reserved resources are configured in each period.

[0371] In some embodiments, the number of frequency domain resource units in each reserved resource is the same, and the positions of the frequency domain resource units in each reserved resource are the same or different.

[0372] In some embodiments, the method includes:

[0373] The network device receives at least two TBs merged and sent by the IoT device. The at least two TBs merged and sent are sent by the IoT device when it determines that the TB transmission has failed, provided that retransmission based on HARQ feedback is supported. The at least two TBs include at least one failed TB.

[0374] In some embodiments, receiving at least two TBs sent by the combined IoT device includes:

[0375] The network device uses a first resource to receive at least one failed TB and a second TB sent by the IoT device. The first resource is a resource configured by the network device for sending the second TB, and the second TB is a new TB to be sent by the IoT device.

[0376] In some embodiments, receiving at least two TBs sent by the combined IoT device includes:

[0377] The network device receives the third TB, which is obtained by merging at least one failed TB and the second TB in chronological order, and then adding a CRC checksum; or,

[0378] The network device receives the fourth TB, which is obtained by adding CRC to at least one failed TB and the second TB respectively and merging them in chronological order.

[0379] In some embodiments, the method includes:

[0380] The network device receives the first information, which indicates the number of TBs that the IoT device is sending in this merge, as well as the length of each TB.

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

[0382] Figure 3B is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 3B, the present disclosure relates to a communication method, which includes:

[0383] In step S3201, the IoT device determines, based on the first condition, whether uplink data transmission uses both retransmission and FEC encoding.

[0384] The optional implementation of step S3201 can be found in the optional implementation of step S2101 in FIG2A, as well as other related parts in the embodiments involved in FIG2A to FIG2D and FIG3A, which will not be repeated here.

[0385] In step S3202, the IoT device sends uplink data to the network device.

[0386] Optional implementations of step S3202 can be found in the optional implementations of step S2102 in FIG2A, as well as other related parts in the embodiments involved in FIG2A to FIG2D and FIG3A, which will not be repeated here.

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

[0388] Figure 3C is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 3C, the embodiments of the present disclosure relate to a communication method, which includes:

[0389] Step S3301: The IoT device and the network device determine whether the IoT device supports blind retransmission or retransmission based on HARQ feedback, and determine the reserved resources.

[0390] Optional implementations of step S3201 can be found in the optional implementations of step S2201 in Figure 2B, step S2301 in Figure 2C, and other related parts in the embodiments involved in Figures 2A to 2D and Figure 3A, which will not be repeated here.

[0391] In step S3302, the IoT device uses reserved resources to perform blind retransmission or retransmission of uplink data.

[0392] Optional implementations of step S3302 can be found in steps S2202 to S2204 in Figure 2B, optional implementations of step S2302 in Figure 2C, and other related parts in the embodiments involved in Figures 2A to 2D and Figure 3A, which will not be repeated here.

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

[0394] Figure 3D is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 3D, the embodiments of the present disclosure relate to a communication method, which includes:

[0395] In step S3401, if the IoT device determines that a TB transmission has failed and supports retransmission based on HARQ feedback, it merges and transmits at least two TBs.

[0396] The optional implementation of step S3401 can be found in the optional implementations of steps S2401 to S2404 in FIG2D, as well as other related parts in the embodiments involved in FIG2A to FIG2D and FIG3A, which will not be repeated here.

[0397] Step S3402: The IoT device sends the first information to the network device.

[0398] Optional implementations of step S3402 can be found in optional implementations of step S2405 in FIG2D, as well as other related parts in the embodiments involved in FIG2A to FIG2D and FIG3A, which will not be repeated here.

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

[0400] Figure 4A is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 4A, the present disclosure relates to a communication method, which includes:

[0401] In step S4101, the device determines whether to use both repetitive transmission and FEC encoding for its uplink transmission based on preset conditions.

[0402] The aforementioned preset conditions include at least one of the following:

[0403] Condition 1: If the QI (QoS Identifier) ​​value of the device's data service is within a predefined QI value range, the device uses both retransmission and FEC encoding for transmission; otherwise, it only uses retransmission. The QI value represents QoS-related parameters of the service, such as priority level, PDB value, and packet error rate. Optionally, a QI value within the predefined range indicates a high reliability requirement for the data service.

[0404] Condition 2: If the TB size transmitted by the device is greater than a certain threshold, the device will use both retransmission and FEC encoding; otherwise, it will only use retransmission.

[0405] Condition 3: If the TB transmitted by the device has a priority value, and the priority value satisfies the condition that the priority value is less than the priority value threshold, then both repeated transmission and FEC encoding are used; otherwise, only repeated transmission is used. Optionally, the priority value threshold is a parameter value pre-configured by RRC.

[0406] Condition 4: If the device supports HARQ-based feedback, and the device sends M TBs, and N TBs out of the M TBs receive NACK feedback from the network device, then the device will use both FEC and repetition in subsequent uplink transmissions; otherwise, it will only use repetition. Here, M and N are integers and can be pre-configured parameter values ​​for the network device.

[0407] Condition 5: If the device supports HARQ-based feedback, and within a time period [t1, t2], the device receives N NACKs from the network device, and N > Nmax, then the device will use both FEC and repetition in subsequent uplink transmissions; otherwise, it will only use repetition. Nmax is a pre-configured parameter value for the network device. Nmax and N are integers.

[0408] Figure 4B is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 4B, the present disclosure relates to a communication method, which includes:

[0409] Step S4201: The network device determines that the device supports retransmission based on HARQ feedback or blind retransmission, and configures reserved resources for the device to perform retransmission.

[0410] In some embodiments, if the device supports retransmission based on HARQ feedback, the behavior of the corresponding device may include at least one of the following:

[0411] Behavior 1: After sending 1 TB, the device needs to listen for ACK or NACK within the time window [t1,t2]. If an ACK is received, the device will not use the reserved resources to retransmit the TB.

[0412] Behavior 2: After sending 1 TB, the device listens for ACK or NACK within the time window [t1,t2]. If NACK is received, the device uses the reserved resources to retransmit the TB.

[0413] Optionally, for the listening time window [t1, t2], there needs to be a certain time interval between time t1 and the time t3 when the device sends TB, such as t1≥t3+gap1, and there needs to be a certain time interval between t2 and the time t3 when the device sends TB, such as t2≥t3+gap2. Here, gap1 and gap2 can be pre-configured by the network device or predefined time intervals.

[0414] In some embodiments, if the device supports blind retransmission, the corresponding device behavior may include: for devices that support blind retransmission, the device does not listen for ACK or NACK, but instead performs a retransmission when the reserved resources arrive. Optionally, the number of blind retransmissions is equal to the number of resources reserved for 1 TB.

[0415] For example, three resources are reserved for a 1TB transmission on the device, namely resources r1, r2, and r3. The device sends TB1 on resource r1. When resource r2 arrives, the device sends TB1 again on resource r2. When resource r3 arrives, the device sends TB1 again on resource r3.

[0416] In some embodiments, the maximum number of resources reserved for 1 TB is Kmax, where Kmax is pre-configured by the network device. Optionally, the reserved resources include time-domain resources, frequency-domain resources, or spatial-domain resources. Optionally, there is a time interval between any two adjacent reserved resources, and the time interval can be in units of any one of subframes, time slots, OFDM symbols, or chips.

[0417] In some embodiments, if it is a DOA service, which is generally a periodic service, the network device can configure periodic resources for the transmission of TB and pre-configure reserved resources for the transmission of TB in each period.

[0418] In some embodiments, the reserved resources contain the same number of frequency domain resource elements, and the positions of the frequency domain resources may be the same or different. Optionally, the frequency domain resource element may be a PRB or a RE.

[0419] For example, if a network device reserves two resources, r1 and r2, for a 1TB transmission, with frequency domain resource f1 corresponding to resource r1 and frequency domain resource f2 corresponding to resource r2, and frequency domain resource units (PRBs), both f1 and f2 contain 5 PRBs, but their positions differ. For instance, f1 contains PRBs with sequence numbers 20-25, while f2 contains PRBs with sequence numbers 80-85. This is understandable because different frequency domain resources experience different channel fading conditions. Switching frequency domain resources can, to some extent, prevent the same channel fading experienced during subsequent TB transmissions, thus avoiding transmission failures.

[0420] Figure 4C is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 4C, the present disclosure relates to a communication method, which includes:

[0421] Step S4301: If the device supports retransmission based on HARQ feedback, for 1 TB, when the device receives NACK feedback from the network device on all reserved resources, the device will merge and send multiple TBs.

[0422] In some embodiments, for a 1TB, when the device receives a NACK from the network device on all reserved resources, the device can determine that the TB has failed to be sent.

[0423] In some embodiments, the device merges and sends multiple failed TBs.

[0424] In some embodiments, the merging method may be as follows: if the time interval between the sending time of the failed TB sent by the device and the start time of the resource r1 configured by the network for the device to send the new TB next time is within the time threshold range, the device uses the resource r1 configured by the network for the next time to send the new TB, and sends the failed X TBs and the new TB together on the resource r1.

[0425] In some embodiments, the device needs to support the ability to cache TB, and the processing methods may include at least one of the following:

[0426] Method 1: The device merges TBs sent on resource r1. This can be done by merging X+1 TBs (excluding CRC) in chronological order to form a longer new TB, and then adding a CRC to the new TB.

[0427] Method 2: After adding CRC to each TB in X+1 TBs, combine them into a longer new TB according to the chronological order.

[0428] For example, if the failed TBs are TB1, TB2, and TB3, and the new TB to be transmitted on resource r1 is TB4, then using method 1, the final merged new TB will be CRC + TB1 + TB2 + TB3 + TB4.

[0429] In some embodiments, the MAC CE also needs to simultaneously indicate the number of TBs X and the length L of each TB in this merged transmission, for the network side to decode X TBs.

[0430] In some embodiments, the time of resource r1 is t1 (or the start time of resource r1 is t1), the time of the first failed TB in X TBs is t2, and the time interval between t2 and t1 is less than or equal to the time threshold T. In this way, the device can determine which TBs that failed to be sent can be merged together for transmission.

[0431] In some embodiments, the X failed TBs sent in the merged transmission are all different.

[0432] In some embodiments, for devices operating on backscatter, a waveform wave (CW) is required to transmit uplink data. In this case, for DOA (Device On Array) services, the periodic resource configured for the device has a period value of p1. If the CW transmission is also periodic with a period of p2, then the CW period and the device's data transmission period are the same or multiples of each other, i.e., P1 = a × P2, where a is a positive integer. However, this condition is not required for devices that generate their own waveforms.

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

[0434] This disclosure also provides an apparatus for implementing any of the above methods. For example, an apparatus is provided that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Alternatively, another apparatus is provided that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

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

[0436] 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 (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a 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 using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0437] Figure 5A is a schematic diagram of the structure of an IoT device proposed in an embodiment of this disclosure. As shown in Figure 5A, the IoT device 5100 may include at least one of a transceiver module 5101, a processing module 5102, etc.

[0438] In some embodiments, the transceiver module 5101 sends uplink data to the network device, the uplink data including at least one transport block (TB).

[0439] Optionally, the transceiver module 5101 is used to perform at least one of the communication steps such as sending and / or receiving performed by the IoT device in any of the above methods, which will not be described in detail here. Optionally, the processing module 5102 is used to perform at least one of the other steps performed by the IoT device in any of the above methods, which will not be described in detail here.

[0440] Figure 5B is a schematic diagram of the structure of a network device proposed in an embodiment of this disclosure. As shown in Figure 5B, the network device 5200 may include at least one of a transceiver module 5201, a processing module 5202, etc.

[0441] In some embodiments, the transceiver module 5201 receives uplink data sent by an Internet of Things (IoT) device, the uplink data including at least one transport block (TB).

[0442] Optionally, the transceiver module 5201 is used to perform at least one of the communication steps such as sending and / or receiving performed by the network device in any of the above methods, which will not be described in detail here. Optionally, the processing module 5202 is used to perform at least one of the other steps performed by the network device in any of the above methods, which will not be described in detail here.

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

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

[0445] Figure 6A is a schematic diagram of the structure of the communication device 6100 proposed in an embodiment of this disclosure. The communication device 6100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal 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.

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

[0447] 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 method, and 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.

[0448] 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 6102 and can be used to receive data from the memories 6102 or other devices, and to send data to the memories 6102 or other devices. For example, the interface circuits 6104 can read data stored in the memories 6102 and send the data to the processor 6101.

[0449] The communication device 6100 described in the above embodiments may be a network device or a terminal, 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; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

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

[0451] Chip 6200 includes one or more processors 6201. Chip 6200 is used to perform any of the methods described above.

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

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

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

[0455] This disclosure also proposes a storage medium storing instructions that, when executed on the communication device 6100, cause the communication device 6100 to perform any of the above methods. 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.

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

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

Claims

1. A communication method, characterized in that, Performed by an Internet of Things (IoT) device, the method includes: Uplink data is sent to network devices, the uplink data including at least one transport block (TB).

2. The method according to claim 1, characterized in that, The method includes: Based on the first condition, determine whether uplink data transmission uses both retransmission and forward error correction (FEC) coding simultaneously. The first condition includes at least one of the following: The signal quality indicator (QI) value of the data service of the IoT device is within the preset QI value range; The size of TB is greater than a preset size threshold; The priority value of the TB is less than a preset priority value threshold; The IoT device supports feedback based on Hybrid Automatic Repeat Request (HARQ), and the number of negative acknowledgments (NACKs) received from the network device after sending M TBs is greater than or equal to N, where M and N are preset positive integers. The IoT device supports HARQ-based feedback, and the number of NACKs received from network devices within a preset time period is greater than a preset threshold.

3. The method according to claim 1, characterized in that, The method includes: It is determined that blind retransmission or HARQ-based retransmission is supported, and reserved resources are determined. The reserved resources are configured by the network device and are used for blind retransmission or retransmission of the uplink data.

4. The method according to claim 3, characterized in that, The method includes: If HARQ-based retransmission is supported, the first TB of data transmission is completed, and ACK or NACK is listened for within a preset time window. Based on the monitoring results, determine whether to use the reserved resources to retransmit the first TB; The first TB is any TB included in the uplink data.

5. The method according to claim 4, characterized in that, The step of determining whether to use the reserved resources for retransmission of the first TB based on the monitoring results includes at least one of the following: Once the ACK is detected, the reserved resources will no longer be used for retransmission of the first TB. If the NACK is detected, the reserved resources are used to retransmit the first TB.

6. The method according to claim 4 or 5, characterized in that, The first interval between the first time and the second time is greater than or equal to the first interval threshold, and the second interval between the second time and the third time is greater than the second interval threshold; The first time is the transmission time of the first TB, the second time is the start time of the preset time window, and the third time is the end time of the preset time window.

7. The method according to claim 3, characterized in that, The number of blind retransmissions for the first TB is equal to the number of reserved resources configured by the network device for the first TB, where the first TB is any TB included in the uplink data.

8. The method according to any one of claims 3-7, characterized in that, The reserved resources include at least one of time-domain resources, frequency-domain resources, or spatial-domain resources; The number of reserved resources configured by the network device for a TB is one or more, and there is a time interval between each two adjacent resources of the multiple reserved resources configured by the network device for a TB.

9. The method according to any one of claims 3-8, characterized in that, When the uplink transmission type of the IoT device is a periodic service, the network device is configured with periodic resources for TB transmission, and the reserved resources are configured in each period.

10. The method according to any one of claims 3-9, characterized in that, The number of frequency domain resource units in each of the reserved resources is the same, and the positions of the frequency domain resource units in each of the reserved resources may be the same or different.

11. The method according to claim 1, characterized in that, Sending uplink data to the network device includes: In cases where HARQ-based retransmission is supported, if a TB transmission failure is determined, at least two TBs are merged and transmitted, wherein the at least two TBs include at least one failed TB.

12. The method according to claim 11, characterized in that, The method includes: If a TB is confirmed to have received a NACK from the network device on all reserved resources, it is determined that the TB transmission has failed.

13. The method according to claim 11 or 12, characterized in that, The merged transmission of at least two TBs includes: At least one failed TB and a second TB are sent using a first resource, wherein the first resource is a resource configured by the network device for sending the second TB, and the second TB is a new TB to be sent by the IoT device.

14. The method according to claim 13, characterized in that, The third interval between the fourth time and the fifth time is less than or equal to the third interval threshold, wherein the fourth time is the sending time of the first TB among the at least one failed TB, and the fifth time is the start time of the first resource.

15. The method according to any one of claims 11-14, characterized in that, The merged transmission of at least two TBs includes: Send a third TB, which is obtained by merging at least one failed TB and the second TB in chronological order and adding a CRC; or, Send the fourth TB, which is obtained by adding CRC to at least one failed TB and the second TB and merging them in chronological order.

16. The method according to any one of claims 11-15, characterized in that, The method includes: Send a first message, which indicates the number of TBs to be sent in this merge and the length of each TB.

17. The method according to claim 1, characterized in that, When the IoT device is a device that operates based on backscattering and the type of uplink transmission of the IoT device is a periodic service, the period for the IoT device to transmit the uplink data is an integer multiple of the period of continuous electromagnetic wave (CW), where CW is used by the IoT device for backscattering to transmit data.

18. A communication method, characterized in that, Performed by a network device, the method includes: Receive uplink data sent by Internet of Things (IoT) devices, wherein the uplink data includes at least one transport block (TB).

19. The method according to claim 18, characterized in that, The uplink data uses both retransmission and forward error correction (FEC) coding. Whether the uplink data uses both retransmission and FEC coding is determined based on a first condition, which includes at least one of the following: The QI value of the data service of the IoT device is within the preset QI value range; The size of TB is greater than a preset size threshold; The priority value of the TB is less than a preset priority value threshold; The IoT device supports feedback based on Hybrid Automatic Repeat Request (HARQ), and the number of negative acknowledgments (NACKs) received from the network device after sending M TBs is greater than or equal to N, where M and N are preset positive integers. The IoT device supports HARQ-based feedback, and the number of NACKs received from network devices within a preset time period is greater than a preset threshold.

20. The method according to claim 18, characterized in that, The method includes: The IoT device is determined to support blind retransmission or retransmission based on HARQ feedback. Reserved resources are determined, and the reserved resources are used for blind retransmission or retransmission of the uplink data.

21. The method according to claim 20, characterized in that, The number of blind retransmissions for the first TB is equal to the number of reserved resources configured by the network device for the first TB, where the first TB is any TB included in the uplink data.

22. The method according to any one of claims 20-21, characterized in that, The reserved resources include at least one of time-domain resources, frequency-domain resources, or spatial-domain resources; The number of reserved resources configured by the network device for a TB is one or more, and there is a time interval between each two adjacent resources of the multiple reserved resources configured by the network device for a TB.

23. The method according to any one of claims 20-22, characterized in that, When the uplink transmission type of the IoT device is a periodic service, the network device is configured with periodic resources for TB transmission, and the reserved resources are configured in each period.

24. The method according to any one of claims 20-23, characterized in that, The number of frequency domain resource units in each of the reserved resources is the same, and the positions of the frequency domain resource units in each of the reserved resources may be the same or different.

25. The method according to claim 18, characterized in that, The method includes: The device receives at least two TBs that are merged and sent by the IoT device. The at least two TBs are sent by the IoT device when it determines that the TB transmission has failed, provided that retransmission based on HARQ feedback is supported. The at least two TBs include at least one failed TB.

26. The method according to claim 25, characterized in that, The receipt of at least two TBs sent by the IoT device includes: The first resource is used to receive at least one failed TB and a second TB sent by the IoT device, wherein the first resource is a resource configured by the network device for sending the second TB, and the second TB is a new TB to be sent by the IoT device.

27. The method according to any one of claims 25-26, characterized in that, The receipt of at least two TBs sent by the IoT device includes: Receive a third TB, which is obtained by merging at least one failed TB and the second TB in chronological order, and adding a CRC; or, Receive the fourth TB, which is obtained by adding CRC to at least one failed TB and the second TB and merging them in chronological order.

28. The method according to any one of claims 25-27, characterized in that, The method includes: Receive first information, which indicates the number of TBs that the IoT device is sending in this merge, and the length of each TB.

29. The method according to claim 18, characterized in that, When the IoT device is a device that operates based on backscattering and the type of uplink transmission of the IoT device is a periodic service, the period for the IoT device to transmit the uplink data is an integer multiple of the period of continuous electromagnetic wave (CW), where CW is used by the IoT device for backscattering to transmit data.

30. An Internet of Things (IoT) device, characterized in that, include: A transceiver module is used to send uplink data to network devices, the uplink data including at least one transport block (TB).

31. A network device, characterized in that, include: The transceiver module is used to receive uplink data sent by Internet of Things (IoT) devices, wherein the uplink data includes at least one transport block (TB).

32. A communication device, characterized in that, include: One or more processors; The communication device is used to perform the communication method according to any one of claims 1-17 or any one of claims 18-29.

33. A communication system, characterized in that, The invention includes network devices and Internet of Things (IoT) devices, wherein the IoT devices are configured to implement the communication method of any one of claims 1-17, and the network devices are configured to implement the communication method of any one of claims 18-29.

34. A storage medium storing instructions, characterized in that, When the instruction is executed on the communication device, the communication device performs the communication method as claimed in any one of claims 1-17 or any one of claims 18-29.

35. A computer program product comprising a computer program and / or instructions, characterized in that, When the computer program and / or the instructions are executed by the communication device, they implement the communication method as described in any one of claims 1-17 or any one of claims 18-29.

Images