Feedback information transmission method, communication device, and storage medium

Abstract

A feedback information transmission method, a communication device, and a storage medium. The feedback information transmission method comprises: using a feedback resource to send feedback information to a network device, wherein one feedback resource can be used by a plurality of terminals for sending feedback information, and the feedback information is used for feeding back receiving states of the terminals regarding information of the network device.

Description

Feedback information transmission method, communication device and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a feedback information transmission method, a communication device, and a storage medium. Background Art

[0002] Ambient Internet of Things (AIoT) devices are a new type of IoT devices that have the following characteristics compared to traditional IoT devices: AIoT devices can communicate with the help of ambient energy; the number of AIoT devices is huge.

[0003] Summary of the Invention

[0004] Embodiments of the present disclosure provide a feedback information transmission method, a communication device, and a storage medium.

[0005] According to a first aspect of an embodiment of the present disclosure, a feedback information transmission method is provided, which is executed by a terminal, and the method includes: using a feedback resource to send feedback information to a network device; one feedback resource can be used by multiple terminals to send feedback information; the feedback information is used to feedback the terminal's reception status of information from the network device.

[0006] According to a second aspect of an embodiment of the present disclosure, a feedback information transmission method is provided, which is executed by a network device and includes: receiving feedback information sent by a terminal; one feedback resource can be used for multiple terminals to send feedback information; the feedback information is used to feedback the terminal's reception status of information from the network device.

[0007] According to a third aspect of an embodiment of the present disclosure, a terminal is provided, wherein the terminal includes: a sending module configured to use a feedback resource to send feedback information to a network device; one feedback resource can be used for multiple terminals to send feedback information; the feedback information is used to feedback the terminal's reception status of information from the network device.

[0008] According to a fourth aspect of an embodiment of the present disclosure, a network device is provided, wherein the network device includes:

[0009] The receiving module is configured to receive feedback information sent by the terminal; one feedback resource can be used for multiple terminals to send feedback information; the feedback information is used to feedback the terminal's reception status of information from the network device.

[0010] According to a fifth aspect of an embodiment of the present disclosure, a communication device is provided, wherein the communication device includes: one or more processors; wherein the processor is used to call instructions to enable the communication device to execute the feedback information transmission method provided by any technical solution of the aforementioned first to second aspects.

[0011] According to a sixth aspect of an embodiment of the present disclosure, a storage medium is provided, wherein the storage medium stores instructions, which, when the instructions are executed on a communication device, enable the communication device to execute the feedback information transmission method provided by any of the first to second aspects.

[0012] The technical solution provided by the embodiments of the present disclosure allows multiple terminals to share one feedback resource to send feedback information, thereby improving the effective utilization of wireless resources and increasing the system capacity of the communication system.

[0013] It should be understood that the foregoing general description and the following detailed description are merely exemplary and explanatory and are not restrictive of the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the present disclosure and, together with the description, serve to explain the principles of the embodiments of the present disclosure.

[0015] FIG1A is a schematic diagram showing an architecture of a communication system according to an exemplary embodiment;

[0016] FIG1B is a schematic diagram showing wireless communication based on a backscatter transmission mechanism according to an exemplary embodiment;

[0017] FIG1C is a schematic topology diagram illustrating wireless communication using a backscatter transmission mechanism according to an exemplary embodiment;

[0018] FIG1D is a schematic diagram showing wireless communication based on a backscatter transmission mechanism according to an exemplary embodiment;

[0019] FIG1E is a schematic topology diagram illustrating wireless communication using a backscatter transmission mechanism according to an exemplary embodiment;

[0020] FIG1F is a topological diagram illustrating wireless communication using a backscatter transmission mechanism according to an exemplary embodiment;

[0021] FIG1G is a topological diagram illustrating wireless communication using a backscatter transmission mechanism according to an exemplary embodiment;

[0022] FIG1H is a schematic diagram of a device that performs wireless communication using three backscatter transmission mechanisms according to an exemplary embodiment;

[0023] FIG1I is a schematic diagram showing phase rotation based on a cyclic shift value according to an exemplary embodiment;

[0024] FIG2A is a schematic flow chart showing a method for transmitting feedback information according to an exemplary embodiment;

[0025] FIG2B is a schematic flow chart showing a method for transmitting feedback information according to an exemplary embodiment;

[0026] FIG3A is a schematic flow chart showing a method for transmitting feedback information according to an exemplary embodiment;

[0027] FIG3B is a schematic flow chart showing a method for transmitting feedback information according to an exemplary embodiment;

[0028] FIG4A is a schematic flow chart showing a method for transmitting feedback information according to an exemplary embodiment;

[0029] FIG4B is a schematic flow chart showing a method for transmitting feedback information according to an exemplary embodiment;

[0030] FIG5A is a schematic structural diagram of a terminal according to an exemplary embodiment;

[0031] FIG5B is a schematic structural diagram of a network device according to an exemplary embodiment;

[0032] FIG6A is a schematic structural diagram of a communication device according to an exemplary embodiment;

[0033] FIG6B is a schematic structural diagram of a chip according to an exemplary embodiment. DETAILED DESCRIPTION

[0034] Embodiments of the present disclosure provide a feedback information transmission method, a communication device, a communication system, and a storage medium.

[0035] A first aspect provides a feedback information transmission method, performed by a terminal, the method comprising:

[0036] Feedback information is sent to the network device using feedback resources. One feedback resource can be used by multiple terminals to send feedback information. Feedback information is used to feedback the terminal's reception status of information from the network device.

[0037] Based on the above solution, multiple terminals can share one feedback resource to send feedback information, which can improve the effective utilization of wireless resources and increase the system capacity of the communication system.

[0038] In some embodiments of the first aspect, one feedback resource can be code-division multiplexed by multiple terminals.

[0039] Based on the above solution, multiple terminals code-division multiplex one feedback resource, and multiple terminals send feedback information on one feedback resource at the same time without interfering with each other, thereby improving the effective utilization of resources and ensuring the transmission quality of the feedback information.

[0040] In some embodiments of the first aspect, feedback information transmitted by different terminals uses different cyclic shift parameters; the cyclic shift parameter includes at least one of the following: a cyclic shift value, a cyclic shift pair, and a cyclic shift pair number; a cyclic shift pair includes two cyclic shift values; the cyclic shift pair number indicates the number of cyclic shift pairs; or, the feedback information transmitted by different terminals uses different orthogonal codes.

[0041] Based on the above solution, cyclic shift values ​​and orthogonal codes are used to implement code division multiplexing of one feedback resource for multiple terminals, which is easy to implement. In some embodiments of the first aspect, cyclic shift parameters corresponding to terminals of different terminal types belong to different sets.

[0042] Based on the above solution, it is equivalent to setting the cyclic shift parameter according to the terminal type. The appropriate cyclic shift parameter can be determined according to the characteristics of different types of terminals, thereby further improving the transmission quality of the feedback information.

[0043] In some embodiments of the first aspect, the granularity of the cyclic shift is related to the granularity of the frequency domain resources occupied by the feedback resources.

[0044] Based on the above solution, the granularity of the cyclic shift is determined based on the granularity (or level) of the feedback resource, so that feedback information of different terminals can be accurately distinguished on one feedback resource.

[0045] In some embodiments of the first aspect, the cyclic shift parameter is a cyclic shift logarithm n; n is a positive integer;

[0046] The feedback information is a negative response, and one feedback resource can be reused by 2*n terminals; or,

[0047] Feedback information includes negative responses and confirmation responses, and one feedback resource can be multiplexed by n terminals.

[0048] Based on the above solution, the number of terminals that multiplex a feedback resource configured with a cyclic shift logarithm n is given in scenarios where the feedback information is a separate negative acknowledgment, or the feedback information may include both a positive acknowledgment and a negative acknowledgment.

[0049] In some embodiments of the first aspect, the length of the orthogonal code is agreed upon by a protocol; or, the length of the orthogonal code is related to the terminal type.

[0050] Based on the above solution, it is equivalent to setting the length of the orthogonal code according to the terminal type. The appropriate cyclic shift parameter can be determined according to the characteristics of different types of terminals, thereby further improving the transmission quality of the feedback information.

[0051] In some embodiments of the first aspect, the orthogonal codes are used for frequency domain orthogonality and / or time domain orthogonality.

[0052] Based on the above solution, orthogonal codes can be used for frequency domain and / or time domain orthogonality, which can be conveniently and flexibly selected in specific communications.

[0053] In some embodiments of the first aspect, the orthogonal code includes: an orthogonal cover code OCC.

[0054] Based on the above scheme, using a simple OCC can reduce the amount of calculation to achieve orthogonality.

[0055] In some embodiments of the first aspect, the cyclic shift parameter or the orthogonal code is configured by a network; or, the cyclic shift parameter or the orthogonal code is agreed upon by a protocol; or, the cyclic shift parameter or the orthogonal code is determined by a predefined rule.

[0056] The above solution provides alternative methods for cyclic shift parameters or orthogonal codes, which can be flexibly selected during actual operation. In some embodiments of the first aspect, the cyclic shift parameter or orthogonal code is associated with terminal identification information, and / or the cyclic shift parameter or orthogonal code is associated with the terminal type; wherein terminals of different terminal types have different energy storage conditions or different operating modes.

[0057] Based on the above, it can be seen that by associating the terminal type and / or identification information with the cyclic shift parameter or orthogonal code, the terminal does not need to additionally transmit its own identification information or indicate its own type when sending feedback information, which can save signaling overhead.

[0058] In some embodiments of the first aspect, the identification information includes at least one of the following: a source identification of the terminal; a target identification of the terminal; a transmission identification of a downlink reception of the terminal; a device identification of the terminal; or a product identification of the terminal.

[0059] In some embodiments of the first aspect, the feedback information is a negative acknowledgement.

[0060] In this way, when the terminal successfully receives information from the network device, it does not send feedback information, which reduces the terminal's signaling overhead, the energy consumption overhead of sending feedback information, and reduces the cyclic shift parameters and / or orthogonal codes occupied by sending confirmation responses.

[0061] In some embodiments of the first aspect, the length of the feedback information is equal to the number of times the terminal receives information from the network device.

[0062] In this case, the terminal may feed back the reception status of the network information once, or may feed back the reception status of the network information multiple times, thereby facilitating the terminal to make flexible choices.

[0063] In some embodiments of the first aspect, the feedback resource is a data channel resource. In this way, the feedback resource uses the data channel instead of a specially designed channel, which has the characteristic of simple implementation.

[0064] A second aspect provides a feedback information transmission method, which is performed by a network device and includes:

[0065] Feedback information sent by the receiving terminal; one feedback resource can be used by multiple terminals to send feedback information; feedback information is used to feedback the terminal's reception status of information from the network device.

[0066] In some embodiments of the second aspect, one feedback resource can be code-division multiplexed by multiple terminals.

[0067] In some embodiments of the second aspect, feedback information transmitted by different terminals uses different cyclic shift parameters; the cyclic shift parameter includes at least one of the following: a cyclic shift value, a cyclic shift pair, and a number of cyclic shift pairs; a cyclic shift pair includes two cyclic shift values; the number of cyclic shift pairs indicates the number of cyclic shift pairs; or,

[0068] The feedback information transmitted by different terminals uses different orthogonal codes.

[0069] In some embodiments of the second aspect, cyclic shift parameters corresponding to terminals of different terminal types belong to different sets.

[0070] In some embodiments of the second aspect, the granularity of the cyclic shift is related to the granularity of the frequency domain resources occupied by the feedback resources.

[0071] In some embodiments of the second aspect, the cyclic shift parameter is a cyclic shift logarithm n; n is a positive integer;

[0072] The feedback information is a negative response, and one feedback resource can be reused by 2*n terminals; or,

[0073] Feedback information includes negative responses and confirmation responses, and one feedback resource can be multiplexed by n terminals.

[0074] In some embodiments of the second aspect, the length of the orthogonal code is agreed upon by a protocol; or, the length of the orthogonal code is related to the terminal type.

[0075] In some embodiments of the second aspect, the orthogonal codes are used for frequency domain orthogonality and / or time domain orthogonality.

[0076] In some embodiments of the second aspect, the orthogonal code includes: an orthogonal cover code OCC.

[0077] In some embodiments of the second aspect, the cyclic shift parameter or the orthogonal code is configured by the network; or,

[0078] The cyclic shift parameter or orthogonal code is agreed upon by the protocol; or;

[0079] The cyclic shift parameter or orthogonal code is determined by a predefined rule.

[0080] In some embodiments of the second aspect, the cyclic shift parameter or the orthogonal code is associated with identification information of the terminal, and / or,

[0081] The cyclic shift parameter or the orthogonal code is associated with the terminal type of the terminal; wherein terminals of different terminal types have different energy storage conditions or different working modes.

[0082] In some embodiments of the second aspect, the identification information includes at least one of the following: a source identification of the terminal; a target identification of the terminal; a transmission identification of downlink reception of the terminal; a device identification of the terminal; or a product identification of the terminal.

[0083] In some embodiments of the second aspect, the feedback information is a negative acknowledgement.

[0084] In some embodiments of the second aspect, the length of the feedback information is equal to the number of times the terminal receives information from the network device.

[0085] In some embodiments of the second aspect, the feedback resource is a resource of a data channel.

[0086] In some embodiments of the second aspect, the length of the feedback information is equal to the number of times the terminal receives information from the network device.

[0087] The third aspect provides a terminal, wherein the terminal includes: a sending module, configured to use feedback resources to send feedback information to a network device; one feedback resource can be used by multiple terminals to send feedback information; the feedback information is used to feedback the terminal's reception status of information from the network device.

[0088] The fourth aspect provides a network device, wherein the network device includes: a receiving module, configured to receive feedback information sent by a terminal; one feedback resource can be used for multiple terminals to send feedback information; feedback information is used to feedback the terminal's reception status of information from the network device.

[0089] In a fifth aspect, an embodiment of the present disclosure provides a communication device, the communication device including: one or more processors;

[0090] The processor is used to call instructions to enable the communication device to execute the feedback information transmission method described in the optional implementation of the first aspect to the second aspect.

[0091] In a sixth aspect, an embodiment of the present disclosure provides a storage medium, wherein the storage medium stores instructions, which, when the instructions are executed on a communication device, enable the communication device to execute the feedback information transmission method described in the optional implementation of the first aspect to the second aspect.

[0092] In a seventh aspect, an embodiment of the present disclosure provides a program product. When the program product is executed by a communication device, the communication device executes the feedback information transmission method described in the optional implementation of the first to fifth aspects.

[0093] In an eighth aspect, an embodiment of the present disclosure provides a computer program, which, when executed on a computer, enables the computer to execute the feedback information transmission method described in the optional implementation manners of the first to fifth aspects.

[0094] It is understandable that the above-mentioned terminals, network devices, communication systems, program products, and computer programs are all used to execute the methods provided by the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0095] The embodiments of the present disclosure propose a feedback information transmission method, communication equipment, communication system and storage medium. The embodiments of the present disclosure are not exhaustive, but are only illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain 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 certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all of the steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0096] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0097] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0098] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "the", "the", 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" in English in translation, the noun following the article can be understood as a singular expression or a plural expression.

[0099] In the embodiments of the present disclosure, “plurality” refers to two or more.

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

[0101] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "in one case A, in another case B," or "in one case A, in another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The same applies when there are more branches such as A, B, and C.

[0102] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0103] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different. For another example, if the description object is "information", then the "first category of information" and the "second category of information" can be the same information or different information, and their contents can be the same or different.

[0104] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0105] In some embodiments, terms such as "...", "determine...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0106] In some embodiments, terms such as "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 less than", and "above" can be replaced with each other, and terms such as "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" can be replaced with each other.

[0107] 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", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", and "subject" can be used interchangeably.

[0108] In some embodiments, "network" can be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).

[0109] 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", "bandwidth part (BWP)" and the like may be used interchangeably.

[0110] 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, client, etc. can be used interchangeably.

[0111] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it is also possible to set the structure in which the terminal has all or part of the functions of the access network device. In addition, terms such as "uplink" and "downlink" can also be replaced by terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

[0112] 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, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.

[0113] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

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

[0115] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0116] FIG1A is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0117] As shown in Figure 1A, a communication system 100 includes a terminal 101 and a network device 102. The network device 102 may include an access network device and / or a core network device.

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

[0119] In some embodiments, the terminal is also referred to as User Equipment (UE).

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

[0121] In some embodiments, the technical solution of the present disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0122] In some embodiments, the access network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0123] In some embodiments, the core network device may be a single device including a first network element, or may be a plurality of devices or a group of devices, each including a first network element. The network element may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0124] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution provided by the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present disclosure is also applicable to similar technical problems.

[0125] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1A , or a portion thereof, but are not limited thereto. The entities shown in FIG1A are illustrative only. The communication system may include all or part of the entities shown in FIG1A , or may include other entities other than those shown in FIG1A . The number and form of the entities may be arbitrary. The connection relationship between the entities is illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0126] The embodiments of the present disclosure 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 (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (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 using configuration methods for other resources, and next-generation systems based on and extending these systems. Furthermore, multiple systems may be combined (for example, LTE and NR).

[0127] In some cases, IoT devices are often powered by traditional batteries with limited lifespans, negatively impacting the user experience. The expected astronomical growth in the number of IoT devices, coupled with the massive scale of these devices, has pushed maintenance expenses, including labor and battery costs, to a whole new level. Billions of traditional batteries are discarded each year, with only a small fraction effectively recycled, negatively impacting the Earth's ecosystem. Maintaining IoT network operations and replacing batteries can be extremely challenging in extreme environmental conditions. Battery-free IoT communications have been proposed to improve network performance and sustainability, expanding their application scenarios. Furthermore, battery-free communications are more environmentally friendly and safer for children and the elderly. Eliminating traditional batteries significantly reduces device size and cost, paving the way for a variety of new applications.

[0128] In some implementations, various Low Power Wide Area (LPWA) technologies, such as Machine Type Communication (MTC), Narrow Band Internet of Things (NB-IoT), and Reduced Capability (RedCap), have been developed to meet the growing demands of various vertical sectors. These LPWA technologies offer low cost, low power consumption, and large-scale connectivity, meeting the requirements of many applications. However, many use cases and applications remain unaddressed. First, battery-powered devices are not suitable, such as in extreme environmental conditions (e.g., high voltage, extremely high / low temperatures, and humid environments). Second, maintenance-free devices are required (e.g., devices without traditional batteries requiring replacement). Finally, ultra-low complexity, very small device size / form factor (e.g., mm thickness), and extended lifecycles are required. Ambient-powered IoT devices are promising technologies that can address these unmet needs. Ambient-powered IoT devices are IoT devices powered by energy harvesting, either without batteries or with limited energy storage capabilities (e.g., using capacitors). Energy is collected from radio waves, light, motion, heat, or any other suitable power source.

[0129] Energy obtained from the environment can drive data transmission and wireless communication of sensing nodes. The current mainstream low-power IoT communication chips (such as BLE, LoRa, NB-IoT) have a transmit and receive power consumption of tens or even hundreds of milliwatts, while the energy obtained by environmental energy harvesting is only at the microwatt level, which is unable to drive these types of nodes to work. Therefore, a new wireless communication technology is needed to reduce communication energy consumption to tens of microwatts or even less than ten microwatts. The current mainstream method uses backscatter communication technology. Backscatter Communications is one of the key technologies for building a green, energy-saving, low-cost, and flexibly deployable future Internet of Things, and is an important means to achieve "Intelligent Connection of Everything". The methods that can be used include backscatter transmission (Backscatter Communications) technology.

[0130] As shown in Figure 1B, backscatter transmission can utilize the principle of RF signal backscattering to design extremely low-power modulation and transmission technologies. A reader sends a physical layer signal to an ambient IoT device. This physical layer signal can be a pulse signal or other AC signal. In some embodiments, this physical layer signal is used to provide energy for the ambient IoT device to transmit the signal. Therefore, this physical layer signal can be referred to as an excitation signal or trigger signal. For example, since a portion of the excitation signal is reflected when it reaches the ambient IoT device, the ambient IoT device can adjust the matching between the receiving antenna and the impedance according to the intended information to enhance the reflection of the incident excitation signal and modulate the acquired sensor data onto the reflected signal to complete the data transmission. This process is similar to a reflector. Compared to other communication technologies, backscatter transmission does not require complex RF structures, reducing the use of components such as power amplifiers, high-precision crystal oscillators, duplexers, and high-precision filters. It also does not require complex baseband processing. Therefore, it can simplify the design of ambient IoT devices and significantly reduce the cost of ambient IoT device nodes. Ambient IoT devices are IoT devices that use environmental energy to operate. This environmental energy can include the aforementioned wireless signal energy, as well as other environmental capabilities such as geothermal energy and / or light energy.

[0131] Here, the device that sends a physical layer signal to the ambient IoT device and triggers the ambient IoT device to return a reflected signal can be called an anchor point of the ambient IoT device reader.

[0132] It is worth noting that an ambient IoT device is a device that uses the backscatter transmission mechanism for wireless communication. In specific implementations, other devices can also use the backscatter transmission mechanism for wireless communication.

[0133] The anchor point or reader of the ambient IoT device may be a network node of a wireless communication network, such as an access network device, a relay node (or intermediate node), or a terminal.

[0134] Backscatter transmission network architectures can include but are not limited to the following:

[0135] Architecture 1: As shown in Figure 1C, uplink (UL) and downlink (DL) data transmission is performed directly between ambient IoT devices and access network devices.

[0136] Architecture 2: As shown in Figure 1D, DL and UL data transmission occurs indirectly between ambient IoT devices and access network equipment. Intermediary nodes (also called auxiliary nodes) are present to forward data. These nodes can be relays, integrated access backhaul (IAB), user equipment (UE), or repeaters (RP).

[0137] Architecture 3: As shown in Figure 1E, data is directly transmitted between the ambient IoT device and the access network device on the uplink (UL), and an auxiliary node exists on the downlink (DL) to assist the base station and the ambient IoT device in downlink transmission. As shown in Figure 1F, data is directly transmitted between the ambient IoT device and the access network device on the DL, and an auxiliary node exists on the UL to assist the base station and the ambient IoT device in uplink transmission. Exemplarily, the auxiliary node can be a relay, an integrated access backhaul (IAB) node, a first terminal, and a network controlled repeater (NCR).

[0138] Architecture 4: As shown in Figure 1G, ambient IoT devices and UEs directly receive and transmit data on the downlink and uplink. The UE collects data and forwards it to the network.

[0139] As shown in Figure 1H, ambient IoT devices that use the backscatter transmission mechanism for wireless communication can be divided into the following three types:

[0140] Device A: has no energy storage, cannot generate or amplify signals independently, and can only perform backscatter transmission.

[0141] Device B: Has energy storage, cannot generate signals independently, and can only perform backscatter transmission. The use of stored energy can include amplification of the backscattered signal.

[0142] Device C: has energy storage and can independently generate signals, i.e., has active radio frequency (RF) components for transmission. The use of stored energy can include amplification of the backscattered signal.

[0143] In view of this, as shown in FIG2A , an embodiment of the present disclosure provides a method for transmitting feedback information, which may include:

[0144] S2101: The network device sends the network configuration to the terminal.

[0145] In some embodiments, the terminal is an AIoT device, and the network device is an AIoT network device. The AIoT network device may include: an access network device of a cellular communication network and / or a communication device capable of transmitting information with an access network device of a cellular communication network. For example, the communication device may be the intermediate node shown in Figure 1D and / or the auxiliary node shown in Figure 1F.

[0146] In some embodiments, if the terminal is not an AIoT device, but is merely a conventional device that can communicate directly with a cellular communication network, the network device may include an access network device.

[0147] In some embodiments, the terminal may be a Reduced Capability (Redcap) device and / or an Enhanced Reduced Capability (eRedcap) device that stores energy. The following uses an AIoT device as an example, but the specific implementation is not limited to AIoT devices.

[0148] In some embodiments, the network device broadcasts, multicasts, or unicasts the network configuration to the terminals.

[0149] In some embodiments, the network configuration may include, but is not limited to, at least one of the following:

[0150] Resource information, used to indicate the frequency domain position and / or time domain position of the feedback resource;

[0151] The cyclic shift information indicates the cyclic shift parameter used by the terminal to transmit feedback information using the feedback resource.

[0152] In some embodiments, the network configuration may include resource information, and the cyclic shift information may be determined by protocol agreement or predefined rules.

[0153] In some embodiments, the network configuration may include cyclic shift information, and the feedback resources may be reserved resources. For example, the reserved resources may be determined by protocol agreement or predefined rules.

[0154] In some embodiments, the network configuration may include resource information and cyclic shift information, and the feedback resources may be reserved resources. For example, the reserved resources may be determined by protocol agreement or predefined rules.

[0155] In some embodiments, the resource information and the cyclic shift information may be included in different information elements (IEs).

[0156] In some embodiments, the resource information and the cyclic shift information may be included in the same information element (IE).

[0157] In some embodiments, the resource information and the cyclic shift information may be included in different network messages, for example, the network message includes but is not limited to RRC message, MAC layer signaling and / or downlink control information.

[0158] In some embodiments, the resource information and the cyclic shift information may be included in the same network message, for example, the network message includes but is not limited to an RRC message, a MAC layer signaling and / or downlink control information.

[0159] In some embodiments, the resource information may include at least one of the following:

[0160] Frequency domain information, indicating the frequency domain position of the feedback resource;

[0161] Time domain information indicates the time domain location of the feedback resource.

[0162] In some embodiments, one feedback resource may be multiplexed by multiple terminals to send feedback information.

[0163] In some embodiments, multiple terminals may code-division multiplex the feedback resource.

[0164] In some embodiments, the cyclic shift parameter may include a cyclic shift value and / or a cyclic shift logarithm.

[0165] In some embodiments, one cyclic shift pair may correspond to two cyclic shift values.

[0166] In some embodiments, the phase difference between two cyclic shift values ​​in a cyclic shift pair may be π.

[0167] Exemplarily, the cyclic shift value can be determined based on the cyclic shift logarithm. For example, the phase range of the analog wave for the physical layer is 0 to 2π. If the cyclic shift logarithm is 1, there are two corresponding cyclic shift values, and these two cyclic shift values ​​are 0 and π respectively. And (0, π) constitutes a cyclic shift pair. If the cyclic shift logarithm is 2, there are four corresponding cyclic shift values, and these four cyclic shift values ​​are: 0, π / 2, 3π / 2 and π respectively. And the two cyclic shift pairs formed by these cyclic shift values ​​are (0, π) and (π / 2, 3π / 2) respectively. For another example, if the cyclic shift logarithm is 4, there are 8 corresponding cyclic shift values, and these 8 cyclic shift values ​​are (0, π), (π / 4, 5π / 4), (π / 2, 3π / 2) and (3π / 4, 7π / 4) respectively. The 8 cyclic shift values ​​corresponding to the 4 cyclic shift pairs shown in Figure 1I.

[0168] In some embodiments, one cyclic shift value corresponds to one terminal, and different terminals have different cyclic shift values.

[0169] In some embodiments, the cyclic shift parameter indicated by the network configuration may be the number of cyclic shift pairs, cyclic shift pairs and / or a specific cyclic shift value.

[0170] For example, if the network configuration indicates the number of cyclic shift pairs, the terminal can determine the available cyclic shift values ​​according to the number of cyclic shift pairs, the phase difference between two cyclic shift values ​​in a cyclic shift pair, and the phase difference between two adjacent cyclic shift pairs.

[0171] In some embodiments, the network device configuration performs terminal (i.e., UE) granularity configuration, for example, configuring feedback resources and / or cyclic shift parameters for each terminal. For example, when the network device configures the cyclic shift parameters of a terminal, the network configuration may indicate to the terminal the cyclic shift pairs, number of cyclic shift pairs that the terminal can use, or directly indicate the cyclic shift value.

[0172] In some embodiments, the terminal that sends feedback information to the network device can be an AIoT device or other device. The other device is different from the AIoT device. In some embodiments, the feedback information is fed back by the AIoT device to the reception status of the information of the network device. For example, if the network device is a base station, the feedback information is fed back to the AIoT device to the reception status of the downlink received information.

[0173] In some embodiments, the terminal type can be distinguished based on the energy stored by the AIoT device itself. For example, the terminal can be an AIoT device of type A, an AIoT device of type B, or an AIoT device of type C as shown in Figure 1H. For example, an AIoT device of type A does not store energy itself. An AIoT device of type B stores a small amount of energy itself. An AIoT device of type C stores energy itself. Generally speaking, an AIoT device of type C stores more energy than an AIoT device of type B.

[0174] In some embodiments, terminal types can be differentiated based on the operating mode of the AIoT device. For example, Type A AIoT devices are completely dependent on the environment for communication and completely rely on the base station for communication. Type B AIoT devices are partially dependent on the environment for communication and completely rely on the base station for communication. Type C AIoT devices may not rely on the environment for communication and completely rely on the base station for communication.

[0175] In some embodiments, the terminal type can be distinguished based on the device form of the AIoT device. For example, the terminal may include an AIoT user equipment (UE), an AIoT device, or an AIoT tag. AIoT devices of different terminal forms have different appearances, functions, and / or sizes to meet the needs of different scenarios.

[0176] In some embodiments, the reception status of the information may include: successful reception and / or failed reception.

[0177] In some embodiments, the feedback information may include an Acknowledgement character (ACK). ACK is used to indicate successful reception.

[0178] In some embodiments, the feedback information may include a non-acknowledgement character (N ACK). NACK is used to indicate a reception failure.

[0179] In some embodiments, regardless of whether the AIoT device successfully receives information from the network device, it will inform the network device through feedback information. In this case, the feedback information transmitted on the feedback resource may include ACK and / or NACK. In this case, a cyclic shift pair can be used to transmit feedback information for a terminal. The two cyclic shift values ​​in a cyclic shift pair represent the ACK and NACK of the terminal, respectively.

[0180] In some embodiments, to conserve resources and improve the effective utilization of feedback resources, the AIoT device only sends feedback information on the feedback resource when it fails to receive information from the network device. In this case, the feedback information transmitted on the feedback resource is all NACK. In this case, the two cyclic shift values ​​of a cyclic shift pair can be used to transmit NACKs to two terminals. Therefore, one feedback resource can be used to transmit feedback information from 2*n terminals, where n can be the number of cyclic shift pairs.

[0181] In short, if the feedback information is ACK or the terminal does not send feedback information to the network device, it means that the terminal successfully receives the information from the network device; if the feedback information is NACK, it means that the terminal fails to receive the information from the network device.

[0182] In some embodiments, the cyclic shift parameter is the cyclic shift logarithm n; n is a positive integer;

[0183] The feedback information is a negative response, and one feedback resource can be reused by 2*n terminals; or,

[0184] Feedback information includes negative responses and confirmation responses, and one feedback resource can be multiplexed by n terminals.

[0185] Based on the above solution, the number of terminals that multiplex a feedback resource configured with a cyclic shift logarithm n is given in scenarios where the feedback information is a separate negative acknowledgment, or the feedback information may include both a positive acknowledgment and a negative acknowledgment.

[0186] In some embodiments, a dedicated feedback channel may be designed for the feedback resource.

[0187] In other embodiments, a dedicated feedback channel may not be designed for this feedback resource, but rather a channel from related technologies may be reused. For example, the feedback resource may be a control channel, such as, but not limited to, a physical uplink control channel. Another example is that the feedback resource may be a data channel, such as, but not limited to, a physical uplink shared channel.

[0188] In some embodiments, cyclic shift parameters corresponding to terminals of different terminal types belong to different sets.

[0189] For example, different sets are configured for AIoT devices of type A, type B, and type C.

[0190] For example, the same set can be configured for type A AIoT devices and type B AIoT devices, but considering that type C AIoT devices themselves store more energy, different sets of type A and type B AIoT devices can be configured.

[0191] For example, if the AIoT device of type A does not store any energy at all, the AIoT device of type B and the AIoT device of type C can be configured with the same set, while the set corresponding to the AIoT device of type A is different from the set of the AIoT device of type B.

[0192] In some embodiments, cyclic shift parameters corresponding to terminals of different terminal types belong to different sets, which may include but are not limited to at least one of the following:

[0193] The cyclic shift values ​​corresponding to terminals of different terminal types belong to different sets;

[0194] The cyclic shift pairs corresponding to terminals of different terminal types belong to different sets;

[0195] The cyclic shift logarithms corresponding to terminals of different terminal types belong to different sets.

[0196] In some embodiments, different sets contain different cyclic shift values ​​and / or different sets contain different numbers of cyclic shift pairs. The fewer the number of cyclic shift pairs a set contains, the greater the phase difference between two adjacent cyclic shift pairs and the greater the mutual interference capability.

[0197] In some embodiments, the number of cyclic shift pairs contained in the set corresponding to type A AIoT devices may be less than the number of cyclic shift pairs contained in the sets corresponding to type B AIoT devices and type C AIoT devices.

[0198] In some embodiments, the number of cyclic shift pairs contained in the set corresponding to type B AIoT devices may be less than the number of cyclic shift pairs contained in the set corresponding to type C AIoT devices.

[0199] Of course, the above are just examples of the cyclic shift value parameters of AIoT devices of different terminal types, and the specific implementation is not limited to the above examples.

[0200] In some embodiments, the cyclic shift parameter is associated with identification information of the terminal. Exemplarily, the cyclic shift parameter is associated with identification information of AIoT.

[0201] In some embodiments, the identification information includes at least one of the following:

[0202] The source identifier of the terminal; for example, the source identifier of an AIoT device;

[0203] Target identification of the terminal; target identification of the AIoT device;

[0204] The service identifier of the terminal's downlink reception; the service identifier of the terminal AIoT device's downlink transmission;

[0205] Device identification of the terminal; device identification of the AIoT device;

[0206] The product identification of the terminal, for example, the product identification of the AIoT device, such as the Electronic Product Code (EPC) of the AIOT device.

[0207] In some embodiments, the source identification may include at least a source address.

[0208] In some embodiments, the target identifier may include at least a destination address.

[0209] In some embodiments, the downlink reception may include downlink data and / or downlink instructions sent by the base station. The transmission identifier may include a service identifier of the downlink data and / or an instruction identifier of the downlink instruction. Specifically, the transmission identifier may include a resource identifier corresponding to the downlink reception, etc.

[0210] In some embodiments, the device identifier may include: an International Mobile Subscriber Identification Number (IMSI) and / or an International Mobile Equipment Identity (IMEI).

[0211] In some embodiments, the product identifier may be a serial number provided by a device manufacturer of the terminal, or a user account used by an application running on the terminal.

[0212] Of course, the above is only an example of identification information, and the specific implementation is not limited to this example.

[0213] If the cyclic shift parameter is associated with the identification information of the terminal, when the network device receives the feedback information, it can directly know the terminal that sent the feedback information based on the cyclic shift parameter used in the feedback information. Therefore, the terminal does not need to send its own identification information additionally when sending the feedback information, thereby reducing the signaling overhead between the terminal and the network device.

[0214] In some embodiments, the cyclic shift parameter is associated with a device type of the first device. Exemplarily, the cyclic shift parameter is associated with a terminal type of AIoT.

[0215] In some embodiments, terminals of different terminal types may have different energy storage conditions or different operating modes. For example, the terminal types may include the aforementioned type A, type B, and / or type C.

[0216] Different types of AIoT devices use different cyclic shift parameters, and cyclic shift can be performed according to the characteristics of the corresponding terminal type to ensure the transmission quality of feedback information.

[0217] In some embodiments, the granularity of the cyclic shift is related to the granularity of the frequency domain resources occupied by the feedback resources.

[0218] For example, if the feedback resource is in the granularity of a resource block (RB), then the cyclic shift is also in the granularity of an RB.

[0219] For example, if the feedback resource has a granularity of a resource element (RE), then the cyclic shift also has a granularity of an RE.

[0220] In this way, when a terminal uses different cyclic shift code division multiplexing to multiplex a feedback resource, the cyclic shift value used for modulation can be determined based on the frequency domain granularity of the feedback resource. When the feedback resource includes one or more REs and the number of REs included in the feedback resource is less than 12 REs, different terminals modulate the feedback information sequence by one phase offset according to the determined cyclic shift value on one or more REs. When the feedback resource includes one or more RBs, different terminals modulate the transmitted sequence by one phase offset according to the determined cyclic shift value on one or more RBs.

[0221] For example, the sequence corresponding to the feedback information of terminal 1 is s(n), and the cyclic shift value determined by terminal 1 is π / 2. Then terminal 1 adjusts the phase offset of sequence s(n) by π / 2, which is s(n)×e jπ / 2 The sequence transmitted by terminal 2 is m(n), and the cyclic shift value determined by terminal 1 is π / 2. Terminal 1 adjusts the phase offset of sequence s(n) by π / 4, which is m(n)×e jπ / 4 .

[0222] It is worth noting that: in some embodiments, S2101 is an optional step. The cyclic shift parameter is agreed upon by the protocol, or the cyclic shift parameter is determined by a predefined rule. Exemplarily, the feedback resource and / or the cyclic shift parameter can be determined in a predefined manner. For example, the feedback resource and / or the cyclic shift parameter can be agreed upon by the protocol. In another exemplary embodiment, the terminal and the network device both determine the cyclic shift parameter based on the predefined rules. For example, the predefined rule may specify the correspondence between the terminal's identification information and the cyclic shift parameter, and the terminal can then determine the cyclic shift parameter based on the correspondence. For another example, the predefined rule may specify the correspondence between the terminal type of the terminal and the cyclic shift parameter, and the terminal can then determine the cyclic shift parameter based on the correspondence.

[0223] S2102: The terminal uses feedback resources to send feedback information to the network device.

[0224] In some embodiments, multiple terminals code-division multiplex feedback resources to send feedback information to the network device.

[0225] In some embodiments, the terminal determines a cyclic shift value to use; and sends feedback information on a feedback resource according to a reception status of network information by the terminal.

[0226] In some embodiments, the sending of feedback information is used to provide feedback on information reception status.

[0227] In some embodiments, sending feedback information once can be used to provide feedback on information reception status multiple times.

[0228] In some embodiments, the length of the feedback information is equal to the number of times the terminal receives information from the network device.

[0229] The length of the feedback information can be understood as the number of bits of the feedback information.

[0230] In some embodiments, one bit in the feedback information may indicate a status of information reception by the network device.

[0231] In this way, if the feedback information has N bits, the feedback information is used for the terminal to feed back N reception statuses of the network information.

[0232] In some embodiments, the N bits of the feedback information, from high to low, respectively indicate N reception statuses of the terminal for the network information.

[0233] In some embodiments, the N bits of the feedback information, from low to high, respectively indicate N reception statuses of the network information by the terminal.

[0234] In view of this, as shown in FIG2B , an embodiment of the present disclosure provides a method for transmitting feedback information, which is performed by a communication system. The method may include:

[0235] S2201: The network device sends the network configuration to the terminal.

[0236] In some embodiments, if the terminal is an AIoT device, the network device is an AIoT network device. The AIoT network device may include: an access network device of a cellular communication network and / or a communication device capable of transmitting information with an access network device of a cellular communication network. For example, the communication device may be the intermediate node shown in Figure 1D and / or the auxiliary node shown in Figure 1F.

[0237] In some embodiments, if the terminal is not an AIoT device, but is just a conventional device that can directly communicate with a cellular communication network,

[0238] The network device may include an access network device.

[0239] In some embodiments, the terminal may be a Reduced Capability (Redcap) device and / or an Enhanced Reduced Capability (eRedcap) device that stores energy. The following uses an AIoT device as an example, but the specific implementation is not limited to AIoT devices.

[0240] In some embodiments, the network device broadcasts, multicasts, or unicasts the network configuration to the terminals.

[0241] In some embodiments, the network configuration may include, but is not limited to, at least one of the following:

[0242] Resource information, used to indicate the frequency domain position and / or time domain position of the feedback resource;

[0243] The orthogonal code information indicates the orthogonal code used by the terminal to transmit the feedback information using the feedback resource.

[0244] In some embodiments, the network configuration may include resource information, and the orthogonal code may be determined by protocol agreement or predefined rules.

[0245] In some embodiments, the network configuration may include orthogonal code information, and the feedback resources may be reserved resources. For example, the reserved resources may be determined by protocol agreement or predefined rules.

[0246] In some embodiments, the network configuration may include resource information and orthogonal code information, and the feedback resources may be reserved resources. For example, the reserved resources may be determined by protocol agreement or predefined rules.

[0247] In some embodiments, the resource information and the orthogonal code information may be included in different information elements (IEs).

[0248] In some embodiments, the resource information and the orthogonal code information may be included in the same information element (IE).

[0249] In some embodiments, the resource information and the orthogonal code information may be included in different network messages, for example, the network message includes but is not limited to RRC message, MAC layer signaling and / or downlink control information.

[0250] In some embodiments, the resource information and the orthogonal code information may be included in the same network message, for example, the network message includes but is not limited to an RRC message, a MAC layer signaling and / or downlink control information.

[0251] In some embodiments, the resource information may include at least one of the following:

[0252] Frequency domain information, indicating the frequency domain position of the feedback resource;

[0253] Time domain information indicates the time domain location of the feedback resource.

[0254] In some embodiments, one feedback resource may be multiplexed by multiple terminals to send feedback information.

[0255] In some embodiments, multiple terminals may code-division multiplex the feedback resource.

[0256] In some embodiments, the orthogonal code information includes: an identifier or index of the orthogonal code, which is an orthogonal code used by the terminal itself.

[0257] In some embodiments, the orthogonal code may include, but is not limited to, a Walsh code.

[0258] In some other embodiments, the orthogonal code is an orthogonal covering code (OCC), and the OCC has the characteristics of being of suitable length and simple.

[0259] In some embodiments, orthogonal codes are used for frequency domain orthogonality and / or time domain orthogonality.

[0260] In some embodiments, in order to reduce the amount of calculation, the orthogonal code can be used for time domain or frequency domain orthogonality.

[0261] In some embodiments, the terminal that sends feedback information to the network device can be an AIoT device or other device. The other device is different from the AIoT device. In some embodiments, the feedback information is fed back by the AIoT device to the reception status of the information of the network device. For example, if the network device is a base station, the feedback information is fed back to the AIoT device to the reception status of the downlink received information.

[0262] In some embodiments, the terminal type can be distinguished based on the energy stored by the AIoT device itself. For example, the terminal can be an AIoT device of type A, an AIoT device of type B, or an AIoT device of type C as shown in Figure 1H. For example, an AIoT device of type A does not store energy itself. An AIoT device of type B stores a small amount of energy itself. An AIoT device of type C stores energy itself. Generally speaking, an AIoT device of type C stores more energy than an AIoT device of type B.

[0263] In some embodiments, terminal types can be differentiated based on the operating mode of the AIoT device. For example, Type A AIoT devices are completely dependent on the environment for communication and completely rely on the base station for communication. Type B AIoT devices are partially dependent on the environment for communication and completely rely on the base station for communication. Type C AIoT devices may not rely on the environment for communication and completely rely on the base station for communication.

[0264] In some embodiments, the terminal type can be distinguished based on the device form of the AIoT device. For example, the terminal may include an AIoT user equipment (UE), an AIoT device, or an AIoT tag. AIoT devices of different terminal forms have different appearances, functions, and / or sizes to meet the needs of different scenarios.

[0265] In some embodiments, the reception status of the information may include: successful reception and / or failed reception.

[0266] In some embodiments, the feedback information may include an Acknowledgement character (ACK). ACK is used to indicate successful reception.

[0267] In some embodiments, the feedback information may include a non-acknowledgement character (N ACK). NACK is used to indicate a reception failure.

[0268] In some embodiments, a dedicated feedback channel may be involved for the feedback resource.

[0269] In other embodiments, the feedback resource may not involve a dedicated feedback channel, but may reuse a channel in related technologies. For example, the feedback resource may be a control channel, such as, but not limited to, a physical uplink control channel. For another example, the feedback resource may be a data channel, such as, but not limited to, a physical uplink shared channel.

[0270] In some embodiments, the length of the orthogonal code is agreed upon by the protocol.

[0271] In some other embodiments, the length of the orthogonal code is related to the terminal type.

[0272] Exemplarily, the length of the orthogonal code may be the number of binary bits contained in the orthogonal code.

[0273] For example, different lengths are configured for type A, type B, and type C AIoT devices.

[0274] For example, the same length can be configured for type A AIoT devices and type B AIoT devices, but considering that type C AIoT devices themselves store more energy, the lengths of the orthogonal codes of type A and type B AIoT devices can be configured differently.

[0275] For example, if the AIoT device of type A does not store any energy at all, the AIoT device of type B and the AIoT device of type C can be configured with the same length, while the length corresponding to the AIoT device of type A is different from the length of the AIoT device of type B.

[0276] In some embodiments, the orthogonal code is associated with identification information of the terminal. Exemplarily, the orthogonal code is associated with identification information of AIoT.

[0277] In some embodiments, the identification information includes at least one of the following:

[0278] The source identifier of the terminal; for example, the source identifier of an AIoT device;

[0279] Target identification of the terminal; target identification of the AIoT device;

[0280] The service identifier of the terminal's downlink reception; the service identifier of the terminal AIoT device's downlink transmission;

[0281] Device identification of the terminal; device identification of the AIoT device;

[0282] The product identification of the terminal, for example, the product identification of an AIoT device.

[0283] In some embodiments, the source identification may include at least a source address.

[0284] In some embodiments, the target identifier may include at least a destination address.

[0285] In some embodiments, the downlink reception may include downlink data and / or downlink instructions sent by the base station. The transmission identifier may include a service identifier of the downlink data and / or an instruction identifier of the downlink instruction. Specifically, the transmission identifier may include a resource identifier corresponding to the downlink reception, etc.

[0286] In some embodiments, the device identifier may include: an International Mobile Subscriber Identification Number (IMSI) and / or an International Mobile Equipment Identity (IMEI).

[0287] In some embodiments, the product identifier may be a serial number provided by a device manufacturer of the terminal, or a user account used by an application running on the terminal.

[0288] Of course, the above is only an example of identification information, and the specific implementation is not limited to this example.

[0289] If the orthogonal code is associated with the identification information of the terminal, when the network device receives the feedback information, it can directly know the terminal that sent the feedback information based on the orthogonal code used in the feedback information. Therefore, the terminal does not need to send its own identification information additionally when sending the feedback information, thereby reducing the signaling overhead between the terminal and the network device.

[0290] In some embodiments, the orthogonal code is associated with a device type of the first device. Exemplarily, the orthogonal code is associated with a terminal type of AIoT.

[0291] In some embodiments, terminals of different terminal types may have different energy storage conditions or different operating modes. For example, the terminal types may include the aforementioned type A, type B, and / or type C.

[0292] Different types of AIoT devices use different orthogonal codes, which can be cyclically shifted according to the characteristics of the corresponding terminal type to ensure the transmission quality of feedback information.

[0293] It is worth noting that: in some embodiments, S2201 is an optional step.

[0294] That is, the orthogonal code is agreed upon by the protocol; or the orthogonal code is determined by predefined rules. Exemplarily, the feedback resource and / or the orthogonal code can be determined in a predefined manner. For example, the feedback resource and / or the orthogonal code can be agreed upon by the protocol. In another exemplary embodiment, both the terminal and the network device independently determine the orthogonal code according to the predefined rules. For example, the predefined rules may specify the correspondence between the terminal's identification information and the orthogonal code, and the terminal can then independently determine the orthogonal code based on this correspondence. For another example, the predefined rules may specify the correspondence between the terminal's terminal type and the orthogonal code, and the terminal can then independently determine the orthogonal code based on this correspondence.

[0295] S2202: The terminal sends feedback information to the network device using feedback resources.

[0296] In some embodiments, multiple terminals code-division multiplex feedback resources to send feedback information to the network device.

[0297] In some embodiments, the terminal determines the orthogonal code to be used; and sends feedback information on the feedback resource according to the reception status of the network information by the terminal.

[0298] In some embodiments, the sending of feedback information is used to provide feedback on information reception status.

[0299] In some embodiments, sending feedback information once can be used to provide feedback on information reception status multiple times.

[0300] In some embodiments, the length of the feedback information is equal to the number of times the terminal receives information from the network device.

[0301] The length of the feedback information can be understood as the number of bits of the feedback information.

[0302] In some embodiments, one bit in the feedback information may indicate a status of information reception by the network device.

[0303] In this way, if the feedback information has N bits, the feedback information is used for the terminal to feed back N reception statuses of the network information.

[0304] In some embodiments, the N bits of the feedback information, from high to low, respectively indicate N reception statuses of the terminal for the network information.

[0305] In some embodiments, the N bits of the feedback information, from low to high, respectively indicate N reception statuses of the network information by the terminal.

[0306] As shown in FIG3A , an embodiment of the present disclosure provides a feedback transmission method, which is performed by a terminal. The method includes:

[0307] S3101: Receive network configuration.

[0308] In some embodiments, the terminal receives the network configuration broadcast, unicast, or multicast by the network device.

[0309] For relevant content of the network configuration, please refer to the embodiment corresponding to Figure 2A.

[0310] S3102: Use feedback resources to send feedback information.

[0311] In some embodiments, the feedback information is sent using feedback information based on a cyclic shift value.

[0312] For relevant contents of the feedback resource and / or feedback information, please refer to the embodiment corresponding to FIG. 2A .

[0313] In some embodiments, the optional implementation of S3102 can refer to the optional implementation of S2102, which will not be repeated here.

[0314] It is worth noting that S3101 may be an optional step. For example, when the feedback resource and / or cyclic shift parameter is determined according to a protocol agreement or a predefined rule, this step may be omitted.

[0315] As shown in FIG3B , an embodiment of the present disclosure provides a feedback transmission method, which is performed by a terminal. The method includes:

[0316] S3201: Receive network configuration.

[0317] In some embodiments, the terminal receives the network configuration broadcast, unicast, or multicast by the network device.

[0318] For relevant content of the network configuration, please refer to the embodiment corresponding to Figure 2B.

[0319] S3202: Send feedback information using feedback resources.

[0320] In some embodiments, the feedback information is sent using feedback information based on an orthogonal code.

[0321] For relevant contents of the feedback resource and / or feedback information, please refer to the embodiment corresponding to FIG. 2B .

[0322] It is worth noting that the optional implementation methods of S3202 can refer to the optional implementation methods of S2202, which will not be repeated here.

[0323] It is worth noting that S3201 may be an optional step. For example, when the feedback resource and / or orthogonal code is determined according to a protocol agreement or a predefined rule, this step may be omitted.

[0324] As shown in FIG4A , an embodiment of the present disclosure provides a feedback transmission method, which is performed by a terminal. The method includes:

[0325] S4101: Send network configuration.

[0326] In some embodiments, the network device broadcasts, unicasts, or multicasts the network configuration.

[0327] For relevant content of the network configuration, please refer to the embodiment corresponding to Figure 2A.

[0328] In some embodiments, the optional implementation of S4102 can refer to the optional implementation of S2101.

[0329] S4102: Receive feedback information on the feedback resource.

[0330] In some embodiments, feedback information sent by a terminal using feedback information based on a cyclic shift value is received on a feedback resource.

[0331] For relevant contents of the feedback resource and / or feedback information, please refer to the embodiment corresponding to FIG. 2A .

[0332] It is worth noting that S4101 may be an optional step. For example, when the feedback resource and / or cyclic shift parameter is determined according to a protocol agreement or a predefined rule, this step may be omitted.

[0333] As shown in FIG4B , an embodiment of the present disclosure provides a feedback transmission method, which is performed by a terminal. The method includes:

[0334] S4201: Receive network configuration.

[0335] In some embodiments, the network device broadcasts, unicasts, or multicasts the network configuration.

[0336] For relevant content of the network configuration, please refer to the embodiment corresponding to Figure 2A.

[0337] In some embodiments, the optional implementation of S4202 can refer to the optional implementation of S2201.

[0338] S4202: Receive feedback information on the feedback resource.

[0339] In some embodiments, feedback information sent by a terminal using feedback information based on an orthogonal code is received on a feedback resource.

[0340] For relevant contents of the feedback resource and / or feedback information, please refer to the embodiment corresponding to FIG. 2B .

[0341] It is worth noting that S4201 may be an optional step. For example, when the feedback resource and / or Z-interleaving code is determined according to a protocol agreement or a predefined rule, this step may be omitted.

[0342] In the AIoT system, if a large number of devices need to be connected, more feedback resources are needed. Therefore, it is necessary to design the reuse of feedback resources to support feedback from a large number of AIoT devices.

[0343] The disclosed embodiments propose a method of code division multiplexing of feedback resources to support feedback from a large number of AIoT devices and improve resource utilization.

[0344] In some embodiments, the feedback information is transmitted on a channel not designed for transmitting the feedback information, for example, the feedback information is transmitted on a data channel.

[0345] When sending feedback information on a data channel, the feedback information may be transmitted independently, or the feedback information may be multiplexed with data information and transmitted together.

[0346] Method 1: The feedback information transmitted by different AIoT devices reuses the same time-frequency domain resources, and different cyclic shift values ​​are used for the feedback information transmitted by different AIoT devices.

[0347] Option 1: The granularity of the cyclic shift is determined by the granularity of the frequency domain resources occupied by the feedback information.

[0348] For example, if the frequency domain resource occupied by the feedback information is at the RB level, the cyclic shift at the RB level is used.

[0349] For example, if the frequency domain resource occupied by the feedback information is at the RE level, the cyclic shift at the RE level is used.

[0350] Option 2: The number of supported cyclic shift pairs n (or supported cyclic shift values) is determined based on at least one of the following methods:

[0351] Option 2.1: Determined by the network device and indicated to the AIoT device based on physical layer control signaling or high-layer signaling.

[0352] For example, the cyclic shift value is indicated through high-layer signaling such as RRC and / or MAC CE.

[0353] Option 2.2: The AIoT device determines the cyclic shift value. For example, the AIoT device determines the cyclic shift value based on its ID information.

[0354] For example, the identification (ID) information may include but is not limited to at least one of the following:

[0355] Source ID or destination ID when data is sent, product ID and / or device ID, etc.

[0356] Option 2.3: The cyclic shift logarithm or the cyclic shift value is specified by the protocol or determined based on a certain rule.

[0357] When the number of cyclic shift pairs supported is n and the ACK / NACK feedback mechanism is supported, n AIoT devices can transmit feedback information on the same time-frequency domain resources.

[0358] When supporting only NACK feedback, 2n AIoT devices can transmit feedback information on the same time-frequency domain resources. In this case, no ACK is fed back.

[0359] For example, different types of AIoT devices support different numbers of cyclic shift pairs.

[0360] For AIoT devices that do not work based on backreflection (such as device C), the cyclic shift logarithm M is supported. For AIoT devices that work based on backreflection (such as device A or device B), the configured cyclic shift logarithm N is supported.

[0361] Exemplarily, different AIoT devices determine cyclic shift values ​​in different cyclic shift value sets, such as device A determines the cyclic shift value in set 1, device B determines the cyclic shift value in cyclic shift value set 2, and device C determines the cyclic shift value in set 3.

[0362] Option 2.4: The feedback information transmitted by the AIoT device is N bits, where N is an integer.

[0363] For example, if N=1, the AIoT device is supported to provide feedback on one downlink data or signaling at a time.

[0364] For another example, if N>1, the AIoT device is supported to provide feedback on multiple downlink data or signaling received at one time.

[0365] Example 1: The feedback information is a sequence, and the feedback information transmitted by an AIoT device is 1 bit. Four cyclic shift pairs are supported. The four cyclic shift pairs are {0, π}{π / 4, 5π / 4}{π / 2, 3π / 2}{3π / 4, 7π / 4}.

[0366] With an ACK / NACK feedback mechanism, four different AIoT devices can simultaneously transmit feedback information on the same time-frequency resource. Referring to Figure 1I, the cyclic shift value of the AIoT device can be used as follows:

[0367] AIoT device 1 uses a cyclic shift value {0, π} for the transmitted sequence, where a cyclic shift value of 0 represents ACK and a cyclic shift value of π represents NACK.

[0368] AIoT device 2 uses a cyclic shift value of {π / 4, 5π / 4} for the transmitted sequence, where a cyclic shift value of π / 4 represents ACK and a cyclic shift value of 5π / 4 represents NACK.

[0369] AIoT device 3 uses a cyclic shift value {π / 2, 3π / 2} for the transmitted sequence, where a cyclic shift value of π / 2 represents ACK and a cyclic shift value of 3π / 2 represents NACK.

[0370] AIoT device 4 uses cyclic shift values ​​{3π / 4, 7π / 4} for the transmitted sequence, where a cyclic shift value of 3π / 4 represents ACK and a cyclic shift value of 7π / 4 represents NACK.

[0371] Example 2: The feedback information is 1 sequence, the feedback information transmitted by 1 AIoT device is 1 bit, and the supported cyclic shift values ​​are {0, π, π / 4, 5π / 4, π / 2, 3π / 2, 3π / 4, 7π / 4}. For the NACK-only feedback mode, 8 AIoT devices can be supported to transmit feedback information simultaneously on the same time-frequency resources.

[0372] Method 2: The feedback information transmitted by different AIoT devices reuses the same time-frequency domain resources, but the time-domain or frequency-domain OCC orthogonal code is used for the feedback information transmitted by different AIoT devices.

[0373] Option 1: The AIoT device determines the OCC code based on one or more of the following:

[0374] The supported OCC length is N, which means that N AIoT devices can be multiplexed on the same time-frequency resources.

[0375] If N=2, two terminals are supported for multiplexing, and the OCC codes are [1, 1] and [1, -1] respectively.

[0376] N=4 supports 4 terminal multiplexing, and the OCC codes are [1, 1, 1, 1], [1, -1, 1, -1], [1, 1, -1, -1] and / or [1, -1, -1, 1].

[0377] Option 1.1: The OCC code is indicated by the network device to the AIoT device. For example, the network device indicates the OCC code based on physical layer control signaling or high-layer signaling.

[0378] Embodiment: The OCC code is indicated through high-layer signaling such as RRC and / or MAC CE.

[0379] Option 1.2: The OCC code is specified by the protocol and has a fixed length or is determined based on some rules.

[0380] Option 1.3: The OCC code is pre-configured on network devices based on the type of different AIoT devices.

[0381] Example: For AIoT devices that do not work based on back reflection (such as device C), the length of OCC can be pre-configured to M. For AIoT devices that work based on back reflection (such as device A or device B), the length of OCC can be pre-configured to N.

[0382] Option 1.4: The OCC code is determined by the AIoT device based on its own ID information in the OCC code length set.

[0383] Its own ID information can be the source ID or destination ID when data is sent, or the product ID, device ID, etc.

[0384] Example 1: When the feedback information transmitted by the AIoT device occupies multiple frequency domain resource units (such as frequency domain resource units are RE, RB, etc., OCC orthogonal code is used in the frequency domain.

[0385] Example 1: Assuming that the length of OCC is 2, the feedback information transmitted by the AIoT device occupies 12 frequency domain units in the frequency domain, the OCC determined by AIoT device 1 is [1, 1], and the OCC sequence determined by AIoT device 2 is [1, -1]. Then the sequence S0 transmitted by AIoT device 1 on the frequency domain resources is multiplied by the OCC sequence [1, 1] at every two adjacent frequency domain resources, and the sequence M0 transmitted by AIoT device 2 on the frequency domain resources is multiplied by the OCC sequence [1, -1] at every two adjacent frequency domain resource units.

[0386] Example 2: When the feedback information transmitted by the AIoT device occupies multiple time units. (For example, the time unit is a symbol, a time slot, a micro-time slot, etc.) When the AIoT device transmits the feedback information, the OCC orthogonal code is used in the time domain.

[0387] Example 2: When the length of the OCC is 2, the feedback information transmitted by the AIoT device occupies 2 time units in the time domain.

[0388] In these two time units, the OCC determined by AIoT device 1 is [1, 1] and the OCC sequence determined by AIoT device 2 is [1, -1]. Then the sequence S0 transmitted by AIoT device 1 is multiplied by the OCC sequence [1, 1] in two adjacent time units, and the sequence M0 transmitted by AIoT device 2 is multiplied by the OCC sequence [1, -1] in two adjacent time units.

[0389] Example 3: When the feedback information transmitted by the AIoT device occupies multiple time domain and frequency domain resource units, OCC can be used in both the time and frequency domains.

[0390] Example: Assuming that the length of the OCC in the time domain and frequency domain is 2, the feedback information transmitted by the AIoT device occupies 2 time units in the time domain and 2 frequency domain resource units in the frequency domain. AIoT device 1 determines the frequency domain OCC to be [1, 1] and the time domain OCC to be [1, 1]. AIoT device 2 determines the frequency domain OCC to be [1, -1] and the time domain OCC to be [1, 1]. AIoT device 3 determines the frequency domain OCC to be [1, 1] and the time domain OCC to be [1, -1]. AIoT device 4 determines the frequency domain OCC to be [1, -1] and the time domain OCC to be [1, -1].

[0391] The sequence transmitted by the AIoT device is multiplied by the frequency domain and time domain OCC respectively, supporting four AIoT devices to reuse the same time and frequency domain resources. The feedback resource reuse method provided by the embodiment of this disclosure can support feedback from a large number of AIoT devices, improving resource utilization.

[0392] In the embodiments of the present disclosure, 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 of other embodiments.

[0393] In the embodiments of the present disclosure, 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 of other embodiments.

[0394] The embodiments of the present disclosure also provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device or a core network device) in any of the above methods.

[0395] It should be understood that the division of the various units or modules in the above devices is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above devices, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0396] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution 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 relationship of the hardware circuit, and the logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable, such as a hardware circuit implemented by a processor as 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 to implement the hardware circuit configuration 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. In addition, 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), a deep learning processing unit (DPU), etc.

[0397] As shown in FIG5A , an embodiment of the present disclosure provides a terminal, wherein the terminal includes:

[0398] The sending module 5101 is configured to use feedback resources to send feedback information to the network device; one feedback resource can be used for multiple terminals to send feedback information; the feedback information is used to feedback the terminal's reception status of the information of the network device.

[0399] In some embodiments, the terminal may further include: a processing module and / or a receiving module.

[0400] In some embodiments, the sending module and / or the receiving module may correspond to a network interface and / or a transceiver antenna of the terminal.

[0401] In some embodiments, the processing module may be used by the terminal to execute steps related to information processing in any feedback information transmission method.

[0402] In some embodiments, the sending module may be used for the terminal to execute steps related to information sending in any feedback information transmission method.

[0403] In some embodiments, the receiving module may be used by the terminal to execute steps related to information sending in any feedback information transmission method.

[0404] In some embodiments, one feedback resource can be code-division multiplexed by multiple terminals.

[0405] In some embodiments, feedback information transmitted by different terminals uses different cyclic shift parameters; the cyclic shift parameters include at least one of the following: a cyclic shift value, a cyclic shift pair, and a cyclic shift pair number; a cyclic shift pair includes two cyclic shift values; the cyclic shift pair number indicates the number of cyclic shift pairs; or, feedback information transmitted by different terminals uses different orthogonal codes.

[0406] In some embodiments, cyclic shift parameters corresponding to terminals of different terminal types belong to different sets.

[0407] In some embodiments, the granularity of the cyclic shift is related to the granularity of the frequency domain resources occupied by the feedback resources.

[0408] In some embodiments, the cyclic shift parameter is the cyclic shift logarithm n; n is a positive integer;

[0409] The feedback information is a negative response, and one feedback resource can be multiplexed by 2*n terminals; or

[0410] The feedback information includes a negative response and a confirmation response, and one feedback resource can be multiplexed by n terminals.

[0411] In some embodiments, the length of the orthogonal code is agreed upon by a protocol; or, the length of the orthogonal code is related to the terminal type.

[0412] In some embodiments, orthogonal codes are used for frequency domain orthogonality and / or time domain orthogonality.

[0413] In some embodiments, the orthogonal code comprises an orthogonal cover code OCC.

[0414] In some embodiments, the cyclic shift parameter or the orthogonal code is configured by the network; or,

[0415] The cyclic shift parameter or orthogonal code is agreed upon by the protocol; or;

[0416] The cyclic shift parameter or orthogonal code is determined by a predefined rule.

[0417] In some embodiments, the cyclic shift parameter or the orthogonal code is associated with identification information of the terminal, and / or,

[0418] The cyclic shift parameter or the orthogonal code is associated with the terminal type of the terminal; wherein terminals of different terminal types have different energy storage conditions or different working modes.

[0419] In some embodiments, the identification information includes at least one of the following:

[0420] The source identifier of the terminal;

[0421] The target identifier of the terminal;

[0422] The transmission identifier of the terminal's downlink reception;

[0423] The device identification of the terminal;

[0424] The product identifier of the terminal.

[0425] In some embodiments, the feedback information is a negative acknowledgement.

[0426] In some embodiments, the length of the feedback information is equal to the number of times the terminal receives information from the network device.

[0427] In some embodiments, the feedback resource is a resource of a data channel.

[0428] FIG5B is a network device provided by an embodiment of the present disclosure, wherein the network device includes:

[0429] The receiving module 5201 is configured to receive feedback information sent by a terminal. One feedback resource can be used by multiple terminals to send feedback information. The feedback information is used to feedback the terminal's reception status of information from the network device.

[0430] In some embodiments, the network device may further include: a processing module and / or a receiving module.

[0431] In some embodiments, the processing module may be configured to execute any steps related to information processing in the feedback information transmission method executed by the network device.

[0432] In some embodiments, the sending module and / or the receiving module may correspond to a network interface and / or a transceiver antenna of a network device.

[0433] In some embodiments, one feedback resource can be code-division multiplexed by multiple terminals.

[0434] In some embodiments, feedback information transmitted by different terminals uses different cyclic shift parameters; the cyclic shift parameter includes at least one of the following: a cyclic shift value, a cyclic shift pair, and a number of cyclic shift pairs; a cyclic shift pair includes two cyclic shift values; the number of cyclic shift pairs indicates the number of cyclic shift pairs; or,

[0435] The feedback information transmitted by different terminals uses different orthogonal codes.

[0436] In some embodiments, cyclic shift parameters corresponding to terminals of different terminal types belong to different sets.

[0437] In some embodiments, the granularity of the cyclic shift is related to the granularity of the frequency domain resources occupied by the feedback resources.

[0438] In some embodiments, the cyclic shift parameter is the cyclic shift logarithm n; n is a positive integer;

[0439] The feedback information is a negative response, and one feedback resource can be multiplexed by 2*n terminals; or

[0440] The feedback information includes a negative response and a confirmation response, and one feedback resource can be multiplexed by n terminals.

[0441] In some embodiments, the length of the orthogonal code is agreed upon by a protocol; or, the length of the orthogonal code is related to the terminal type.

[0442] In some embodiments, orthogonal codes are used for frequency domain orthogonality and / or time domain orthogonality.

[0443] In some embodiments, the orthogonal code comprises an orthogonal cover code OCC.

[0444] In some embodiments, the cyclic shift parameter or the orthogonal code is configured by the network; or,

[0445] The cyclic shift parameter or orthogonal code is agreed upon by the protocol; or;

[0446] The cyclic shift parameter or orthogonal code is determined by a predefined rule.

[0447] In some embodiments, the cyclic shift parameter or the orthogonal code is associated with identification information of the terminal, and / or,

[0448] The cyclic shift parameter or the orthogonal code is associated with the terminal type of the terminal; wherein terminals of different terminal types have different energy storage conditions or different working modes.

[0449] In some embodiments, the identification information includes at least one of the following:

[0450] The source identifier of the terminal;

[0451] The target identifier of the terminal;

[0452] The transmission identifier of the terminal's downlink reception;

[0453] The device identification of the terminal;

[0454] The product identifier of the terminal.

[0455] In some embodiments, the feedback information is a negative acknowledgement.

[0456] In some embodiments, the length of the feedback information is equal to the number of times the terminal receives information from the network device.

[0457] In some embodiments, the feedback resource is a resource of a data channel.

[0458] In some embodiments, the length of the feedback information is equal to the number of times the terminal receives information from the network device.

[0459] An embodiment of the present disclosure further provides a communication device, which may include: one or more processors; wherein the processor is used to call instructions to enable the communication device to execute the feedback information transmission method that can be implemented in any of the aforementioned embodiments.

[0460] 6A and / or 6B , the communication device 8100 further includes one or more memories 8102 for storing instructions. Optionally, all or part of the memories 8102 may be located outside the communication device 8100.

[0461] The communication device may be the aforementioned terminal and network device. In some embodiments, the network device may be a master node and / or an auxiliary node.

[0462] In some embodiments, the communication device 8100 further includes one or more transceivers 8103. When the communication device 8100 includes one or more transceivers 8103, the communication steps such as sending and receiving in the above method are performed by the transceiver 8103, and the other steps are performed by the processor 8101.

[0463] In some embodiments, a transceiver may include a receiver and a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0464] Optionally, the communication device 8100 further includes one or more interface circuits 8104, which are connected to the memory 8102. The interface circuits 8104 can be used to receive signals from the memory 8102 or other devices, and can be used to send signals to the memory 8102 or other devices. For example, the interface circuits 8104 can read instructions stored in the memory 8102 and send the instructions to the processor 8101.

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

[0466] 6B is a schematic diagram of the structure of a chip 8200 provided in an embodiment of the present disclosure. If the communication device 8100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 8200 shown in FIG6B , but the present disclosure is not limited thereto.

[0467] The chip 8200 includes one or more processors 8201 , and the processor 8201 is used to call instructions to enable the chip 8200 to execute any of the above feedback information transmission methods.

[0468] In some embodiments, chip 8200 further includes one or more interface circuits 8202, which are connected to memory 8203. Interface circuit 8202 can be used to receive signals from memory 8203 or other devices, and can be used to send signals to memory 8203 or other devices. For example, interface circuit 8202 can read instructions stored in memory 8203 and send the instructions to processor 8201. Optionally, the terms interface circuit, interface, transceiver pin, and transceiver are interchangeable.

[0469] In some embodiments, the chip 8200 further includes one or more memories 8203 for storing instructions. Alternatively, all or part of the memories 8203 may be outside the chip 8200.

[0470] The present disclosure also provides a storage medium having instructions stored thereon, which, when executed on the communication device 8100, causes the communication device 8100 to execute 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 may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but may also be a transient storage medium.

[0471] The present disclosure further provides a program product, which, when executed by the communication device 8100, enables the communication device 8100 to perform any of the above feedback information transmission methods. Optionally, the program product is a computer program product.

[0472] The present disclosure also provides a computer program, which, when executed on a computer, enables the computer to execute any one of the above feedback information transmission methods.

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

[0474] It should be understood that the embodiments of the present disclosure are not limited to the precise structures described above and shown in the drawings, and various modifications and changes can be made without departing from the scope thereof. The scope of the embodiments of the present disclosure is limited only by the appended claims.

Claims

1. A feedback information transmission method, wherein, Executed by a terminal, the method includes: Feedback information sent to a network device using a feedback resource; one such feedback resource can be used by multiple terminals to send feedback information; the feedback information is used to feedback the reception status of information of the network device by the terminal.

2. The method according to claim 1, wherein One such feedback resource can be code division multiplexed by multiple terminals.

3. The method according to claim 1 or 2, wherein, The feedback information transmitted by different terminals uses different cyclic shift parameters; the cyclic shift parameters include at least one of the following: cyclic shift value, cyclic shift pair, and cyclic shift logarithm; wherein, one cyclic shift pair includes two cyclic shift values; the cyclic shift logarithm indicates the number of cyclic shift pairs; Or, The feedback information transmitted by different terminals uses different orthogonal codes.

4. The method according to claim 3, wherein The cyclic shift parameters corresponding to terminals of different terminal types belong to different sets.

5. The method according to claim 3 or 4, wherein The granularity of cyclic shift is related to the granularity of the frequency domain resources occupied by the feedback resource.

6. The method according to claim 3, wherein The cyclic shift parameter is the cyclic shift logarithm n; the n is a positive integer; The feedback information is a negative acknowledgment, and one feedback resource can be multiplexed by 2*n terminals; Or, The feedback information includes a negative acknowledgment and a positive acknowledgment, and one feedback resource can be multiplexed by n terminals.

7. The method according to claim 3, wherein, The length of the orthogonal code is agreed by the protocol; or, the length of the orthogonal code is related to the terminal type.

8. The method according to claim 3, wherein The orthogonal code includes: orthogonal cover code OCC.

9. The method according to claim 3, wherein, The cyclic shift parameter or the orthogonal code is configured by the network; or, The cyclic shift parameter or the orthogonal code is agreed by the protocol; or; The cyclic shift parameter or the orthogonal code is determined by predefined rules.

10. The method according to claim 9, wherein, The cyclic shift parameter or the orthogonal code is associated with the identification information of the terminal, and / or, The cyclic shift parameter or the orthogonal code is associated with the terminal type of the terminal; wherein, the energy storage status or the working mode of terminals of different terminal types is different.

11. The method according to claim 10, wherein, The identification information includes at least one of the following: The source identification of the terminal; The target identification of the terminal; The transmission identification of the downlink reception of the terminal; The device identification of the terminal; The product identification of the terminal.

12. The method according to any one of claims 1 to 11, wherein, The length of the feedback information is equal to the number of times the terminal receives information from the network device.

13. The method according to any one of claims 1 to 13, wherein The feedback resource is a data channel resource.

14. A feedback information transmission method, wherein, Executed by the network side, the method includes: Receiving feedback information sent by a terminal; one such feedback resource can be used by multiple terminals to send feedback information; the feedback information is used to feedback the reception status of information of the network device by the terminal.

15. The method according to claim 14, wherein, One such feedback resource can be code division multiplexed by multiple terminals.

16. The method according to claim 14, wherein, The feedback information transmitted by different terminals uses different cyclic shift parameters; the cyclic shift parameters include at least one of the following: cyclic shift value, cyclic shift pair, and cyclic shift logarithm; one cyclic shift pair includes two cyclic shift values; the cyclic shift logarithm indicates the number of cyclic shift pairs; Or, The feedback information transmitted by different terminals uses different orthogonal codes.

17. The method according to claim 16, wherein, The cyclic shift parameters corresponding to the terminals of different terminal types belong to different sets.

18. The method according to claim 16 or 17, wherein The granularity of the cyclic shift is related to the granularity of the frequency domain resources occupied by the feedback resource.

19. The method according to claim 18, wherein The cyclic shift parameter is the cyclic shift logarithm n; n is a positive integer; The feedback information is a negative acknowledgment, and one feedback resource can be multiplexed by 2*n terminals; Or, The feedback information includes a negative acknowledgment and a positive acknowledgment, and one feedback resource can be multiplexed by n terminals.

20. The method according to claim 16, wherein, The length of the orthogonal code is specified by the protocol; or, the length of the orthogonal code is related to the terminal type.

21. The method according to claim 16, wherein, The orthogonal code includes: Orthogonal Cover Code (OCC).

22. According to the method of claim 16, wherein, The cyclic shift parameter or the orthogonal code is configured by the network; or, The cyclic shift parameter or the orthogonal code is specified by the protocol; or; The cyclic shift parameter or the orthogonal code is determined by a predefined rule.

23. According to the method of claim 22, wherein, The cyclic shift parameter or the orthogonal code is associated with the identification information of the terminal, and / or, The cyclic shift parameter or the orthogonal code is associated with the terminal type of the terminal; wherein, the energy storage status or the working mode of the terminals of different terminal types is different.

24. The method according to claim 22, wherein, The identification information includes at least one of the following: The source identification of the terminal; The target identification of the terminal; The transmission identification received by the terminal in the downlink; The device identification of the terminal; The product identification of the terminal.

25. The method according to any one of claims 14 to 24, wherein, The length of the feedback information is equal to the number of times the terminal receives information from the network device.

26. The method according to any one of claims 14 to 25, wherein The feedback resource is a data channel.

27. A terminal, wherein, Includes: A sending module, configured to send feedback information to a network device using a feedback resource; One feedback resource can be used for multiple terminals to send feedback information; The feedback information is used to feedback the reception status of the information of the terminal from the network device.

28. A network device, wherein, Includes: A receiving module, configured to receive the feedback information sent by the terminal; One feedback resource can be used for multiple terminals to send feedback information; The feedback information is used to feedback the reception status of the information of the terminal from the network device.

29. A communication device, wherein, The communication device includes: One or more processors; Wherein, the processor is used to call instructions to cause the communication device to execute the method according to any one of claims 1 to 13 and / or claims 14 to 26.

30. A storage medium, wherein, The storage medium stores instructions, which when running on the communication device, cause the communication device to execute the method according to any one of claims 1 to 13 and / or claims 14 to 26.

Images