Method for sending downlink information, method for receiving downlink information, and network device, terminal and storage medium

Abstract

The present disclosure relates to a method for sending downlink information, a method for receiving downlink information, and a network device, a terminal and a storage medium. The method for sending downlink information comprises: sending downlink information to a terminal, wherein the downlink information comprises an energy charging signal, and the energy charging signal is used to provide energy for the terminal. In the method of the present disclosure, the network device issues downlink information, and supplies energy to the terminal by means of the energy charging signal in the downlink information. Therefore, the terminal can be subjected to energy charging while receiving the downlink information, thereby improving the energy charging efficiency and ensuring sufficient energy for data transceiving.

Description

Method, network device, terminal and storage medium for sending and receiving downlink information Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular to a method for sending and receiving downlink information, a network device, a terminal, and a storage medium. Background Art

[0002] The Ambient Internet of Things (Ambient-IoT) is a type of IoT. Compared to cellular-based Narrowband Internet of Things (NB-IoT) terminals, Ambient-IoT terminals are less complex, less expensive, and require less maintenance. Because Ambient-IoT terminals require energy from the external environment, they are also called ambient-powered terminals or passive terminals.

[0003] A method for charging Ambient-IoT terminals must be provided.

[0004] Summary of the Invention

[0005] Embodiments of the present disclosure provide a method, network device, terminal, and medium for sending and receiving downlink information.

[0006] In a first aspect, an embodiment of the present disclosure provides a method for sending downlink information, performed by a network device, the method comprising:

[0007] Downlink information is sent to the terminal, where the downlink information includes a charging signal, wherein the charging signal is used to provide energy to the terminal.

[0008] In a second aspect, an embodiment of the present disclosure provides a method for receiving downlink information, performed by a terminal, the method comprising:

[0009] Receive downlink information sent by the network device, where the downlink information includes a charging signal, wherein the charging signal is used to provide energy for the terminal.

[0010] In a third aspect, an embodiment of the present disclosure provides a network device, including:

[0011] The transceiver module is used to send downlink information to the terminal, where the downlink information includes a charging signal, wherein the charging signal is used to provide energy for the terminal.

[0012] In a fourth aspect, an embodiment of the present disclosure provides a terminal, including:

[0013] The transceiver module is used to receive downlink information sent by a network device, where the downlink information includes a charging signal, wherein the charging signal is used to provide energy for the terminal.

[0014] In a fifth aspect, an embodiment of the present disclosure provides a network device, including:

[0015] one or more processors;

[0016] The network device is configured to implement the method described in the first aspect.

[0017] In a sixth aspect, an embodiment of the present disclosure provides a terminal, including:

[0018] one or more processors;

[0019] The network device is configured to implement the method described in the second aspect.

[0020] In a seventh aspect, an embodiment of the present disclosure provides a communication system, including a terminal and a network device, wherein:

[0021] The network device is configured to implement the method according to the first aspect;

[0022] The terminal is configured to implement the method according to the second aspect.

[0023] In an eighth aspect, an embodiment of the present disclosure provides a storage medium, wherein the storage medium stores instructions, wherein:

[0024] When the instruction is executed on a communication device, the communication device is caused to execute the method according to the first aspect or the second aspect.

[0025] In a ninth aspect, an embodiment of the present disclosure provides a program product, wherein:

[0026] When the program product is executed by a communication device, the communication device is caused to execute the method according to the first aspect or the second aspect.

[0027] In the embodiment of the present disclosure, the network device sends downlink information and supplies energy to the terminal through the charging signal in the downlink information, so that the terminal can be charged while receiving the downlink information, thereby improving the charging efficiency and facilitating sufficient energy for data transmission and reception. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

[0029] 1a to 1b are exemplary schematic diagrams of the architecture of a communication system provided according to an embodiment of the present disclosure;

[0030] FIG2a is an exemplary interaction diagram of a method provided according to an embodiment of the present disclosure;

[0031] FIG2b is a schematic diagram of a frame structure provided according to an embodiment of the present disclosure;

[0032] 2c to 2d are schematic diagrams of circuit architectures of a terminal according to an embodiment of the present disclosure;

[0033] FIG3 is an exemplary flowchart of a method provided according to an embodiment of the present disclosure;

[0034] FIG4 is an exemplary flowchart of a method provided according to an embodiment of the present disclosure;

[0035] FIG5a is a schematic structural diagram of a terminal according to an embodiment of the present disclosure;

[0036] FIG5b is a schematic structural diagram of a network device according to an embodiment of the present disclosure;

[0037] FIG6a is a schematic diagram of a communication device according to an embodiment of the present disclosure;

[0038] FIG6 b is a schematic diagram of a communication device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0039] Embodiments of the present disclosure provide a method for sending and receiving downlink information, a network device, a terminal, and a storage medium.

[0040] In a first aspect, an embodiment of the present disclosure provides a method for sending downlink information, performed by a network device, the method comprising:

[0041] Downlink information is sent to the terminal, where the downlink information includes a charging signal, wherein the charging signal is used to provide energy to the terminal.

[0042] In the above embodiment, the network device sends downlink information and supplies energy to the terminal through the charging signal in the downlink information, so that the terminal can be charged while receiving the downlink information, thereby improving the charging efficiency and facilitating sufficient energy for data transmission and reception.

[0043] In conjunction with the embodiments of the first aspect, in some embodiments, the downlink information includes at least one of the following information types:

[0044] Query signaling;

[0045] Repeat query QueryRep signaling;

[0046] Operation command.

[0047] In the above embodiment, downlink information of different information types may include charging signals, so that the terminal is charged through the corresponding type of downlink information in different application scenarios.

[0048] In conjunction with the embodiment of the first aspect, in some embodiments, the sending power of the charging signal is greater than a threshold, or,

[0049] The downlink information also includes a non-charging signal, and the sending power of the charging signal is greater than the sending power of the non-charging signal.

[0050] In the above embodiment, the charging signal carried in the downlink information may have a higher transmission power, thereby improving the efficiency of charging the terminal.

[0051] In combination with the embodiments of the first aspect, in some embodiments, the downlink information includes multiple information types, and the sending power of the charging signal in the downlink information of different information types is the same.

[0052] In the above embodiment, different types of downlink information can carry charging signals with the same transmission power, so that the terminal can be effectively charged through different types of downlink information, simplifying the operation of network devices in different scenarios.

[0053] In combination with the embodiments of the first aspect, in some embodiments, the downlink information includes multiple information types, and the sending power of the charging signal in the downlink information of different information types is different, wherein the information type and the sending power have a mapping relationship.

[0054] In the above embodiment, different types of downlink information can carry charging signals with different transmission powers, so that appropriate power can be used to charge the terminal in different scenarios, thereby improving the flexibility of charging the terminal in different scenarios.

[0055] In combination with the embodiments of the first aspect, in some embodiments, the duration of the charging signal is greater than or equal to a first duration, and the first duration is the duration required for terminal charging configured by the network device or defined by the protocol.

[0056] In the above embodiment, the duration can satisfy the time required for charging the terminal, so that the terminal can obtain sufficient energy through the charging signal of the downlink information to perform subsequent data transmission and reception.

[0057] In combination with the embodiments of the first aspect, in some embodiments, the downlink information includes multiple information types, and the duration of downlink information of different information types is the same.

[0058] In the above embodiment, different types of downlink information may carry charging signals of the same duration, thereby simplifying the structures of different types of downlink information.

[0059] In combination with the embodiments of the first aspect, in some embodiments, the downlink information includes multiple information types, and the duration of downlink information of different information types is different, wherein the information type and the duration have a mapping relationship.

[0060] In the above embodiment, different types of downlink information can carry charging signals of different durations, thereby adapting to the charging needs of terminals in different scenarios and improving the flexibility of charging in different scenarios.

[0061] In combination with the embodiments of the first aspect, in some embodiments, the frequency of the charging signal includes a single frequency point or multiple frequency points.

[0062] In the above embodiment, the single-frequency charging signal has low requirements on the terminal capability while charging the terminal. The multi-frequency charging signal can charge the terminal at other frequencies when deep channel attenuation occurs at a certain frequency, thereby improving the success rate of charging the terminal.

[0063] In combination with the embodiments of the first aspect, in some embodiments, the frequency domain bandwidth of the charging signal is a first value.

[0064] In the above embodiment, the charging signal has a certain bandwidth, which can improve the problem of charging being affected by deep channel attenuation at a single frequency point, thereby improving the charging success rate and efficiency.

[0065] In combination with the embodiments of the first aspect, in some embodiments, the frequency domain bandwidth of the non-charging signal is a second value, and the first value is the same as or different from the second value.

[0066] In the above embodiment, different signals included in the downlink information frame may have the same or different frequency domain bandwidths, thereby improving the flexibility of frame structure design.

[0067] In some embodiments, the first value is smaller than the second value, that is, the frequency domain bandwidth of the charging signal may be smaller than the bandwidth of the non-charging portion.

[0068] In the above embodiment, the charging signal may be a high-power signal. For example, the transmission power of the charging signal is higher than the transmission power of the non-charging signal, so that the charging signal uses a smaller frequency domain bandwidth, which can reduce the impact on adjacent frequency communication signals.

[0069] In combination with the embodiments of the first aspect, in some embodiments, the network device includes an energy source node (Energy Source Node, ESN) and a downlink signal node (Downlink Signal Node, DSN).

[0070] In the above embodiment, the network device can not only provide energy for the terminal, but also interact with the terminal to simplify the communication nodes.

[0071] In a second aspect, an embodiment of the present disclosure provides a method for receiving downlink information, performed by a terminal, the method comprising:

[0072] Receive downlink information sent by the network device, where the downlink information includes a charging signal, wherein the charging signal is used to provide energy for the terminal.

[0073] In the above embodiment, the terminal is charged by receiving the charging signal in the downlink information, thereby improving the charging efficiency and facilitating sufficient energy for data transmission and reception.

[0074] In conjunction with the embodiments of the second aspect, in some embodiments, the downlink information includes at least one of the following information types:

[0075] Query signaling;

[0076] Repeat query QueryRep signaling;

[0077] Operation command.

[0078] In conjunction with the embodiment of the second aspect, in some embodiments, the sending power of the charging signal is greater than a threshold, or,

[0079] The downlink information also includes a non-charging signal, and the sending power of the charging signal is greater than the sending power of the non-charging signal.

[0080] In combination with the embodiments of the second aspect, in some embodiments, the downlink information includes multiple information types, and the sending power of the charging signal in the downlink information of different information types is the same.

[0081] In combination with the embodiments of the second aspect, in some embodiments, the downlink information includes multiple information types, and the sending power of the charging signal in the downlink information of different information types is different, wherein the information type and the sending power have a mapping relationship.

[0082] In combination with the embodiments of the second aspect, in some embodiments, the duration of the charging signal in the downlink information is greater than or equal to the first duration, and the first duration is the duration required for terminal charging configured by the network device or defined by the protocol.

[0083] In combination with the embodiments of the second aspect, in some embodiments, the downlink information includes multiple information types, and the duration of downlink information of different information types is the same.

[0084] In combination with the embodiments of the second aspect, in some embodiments, the downlink information includes multiple information types, and the duration of downlink information of different information types is different, wherein the information type and the duration have a mapping relationship.

[0085] In combination with the embodiments of the second aspect, in some embodiments, the frequency of the charging signal includes a single frequency point or multiple frequency points.

[0086] In combination with the embodiments of the second aspect, in some embodiments, the frequency domain bandwidth of the charging signal is a first value.

[0087] In combination with the embodiments of the second aspect, in some embodiments, the frequency domain bandwidth of the non-charging signal is a second value, and the first value is the same as or different from the second value.

[0088] In combination with the embodiments of the second aspect, in some embodiments, the network device includes an energy source node ESN and a downlink information sending node DSN.

[0089] In a third aspect, an embodiment of the present disclosure provides a network device, including:

[0090] The transceiver module is used to send downlink information to the terminal, where the downlink information includes a charging signal, wherein the charging signal is used to provide energy for the terminal.

[0091] In a fourth aspect, an embodiment of the present disclosure provides a terminal, including:

[0092] The transceiver module is used to receive downlink information sent by a network device, where the downlink information includes a charging signal, wherein the charging signal is used to provide energy for the terminal.

[0093] In a fifth aspect, an embodiment of the present disclosure provides a network device, including:

[0094] one or more processors;

[0095] The network device is configured to implement the method described in the first aspect.

[0096] In a sixth aspect, an embodiment of the present disclosure provides a terminal, including:

[0097] one or more processors;

[0098] The network device is configured to implement the method described in the second aspect.

[0099] In a seventh aspect, an embodiment of the present disclosure provides a communication system, including a terminal and a network device, wherein:

[0100] The network device is configured to implement the method according to the first aspect;

[0101] The terminal is configured to implement the method according to the second aspect.

[0102] In an eighth aspect, an embodiment of the present disclosure provides a storage medium, wherein the storage medium stores instructions, wherein:

[0103] When the instruction is executed on a communication device, the communication device is caused to execute the method according to the first aspect or the second aspect.

[0104] In a ninth aspect, an embodiment of the present disclosure provides a program product, wherein:

[0105] When the program product is executed by a communication device, the communication device is caused to execute the method according to the first aspect or the second aspect.

[0106] In a tenth aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the optional implementation of the first and second aspects.

[0107] In an eleventh aspect, an embodiment of the present disclosure provides a chip or a chip system, wherein the chip or chip system includes a processing circuit configured to execute the method described in the optional implementation of the first and second aspects above.

[0108] It is understandable that the above-mentioned terminals, network devices, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to perform the methods proposed in 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.

[0109] The embodiments of the present disclosure are not exhaustive and are merely 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 steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

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

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

[0112] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may 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 may be understood as a singular expression or a plural expression.

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

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

[0115] In some embodiments, "at least one of A and B", "A and / or B", "A in one case, B in another case", "in response to one case A, in response to another case B", etc., may include the following technical solutions according to 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); in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, C, etc.

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

[0117] 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 information" and the "second information" can be the same information or different information, and their contents can be the same or different.

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

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

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

[0121] In some embodiments, devices and equipment can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", etc.

[0122] In some embodiments, "network" can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.

[0123] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", and in some embodiments may also be understood as "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission and / or 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)", etc.

[0124] In some embodiments, "terminal" or "terminal device" may be referred to as "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.

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

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

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

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

[0129] As shown in FIG. 1 a , a communication system 100 includes a terminal 101 and a network device 102 .

[0130] In some embodiments, terminal 101 may be an Ambient-IoT terminal or device. Terminal 101 may not be equipped with a battery and may be excited and powered by received electromagnetic signals; or it may be equipped with a battery with a small amount of electrical storage capacity and obtain energy from the battery by obtaining external electromagnetic waves, thermal energy, kinetic energy, etc.

[0131] Optionally, the power acquisition and storage capabilities of the terminal 101 may vary depending on the type and working mode of the terminal 101. For example, the types of the terminal 101 may include the following:

[0132] Device 1: cannot independently generate or amplify signals. For example, Device 1 uses a backscattering mode or backscattering communication and does not have the ability to amplify downlink (DL) signals and / or uplink (UL) signals.

[0133] Device 2a: Has energy storage capabilities but cannot independently generate signals. For example, if device 2a operates in a backscatter mode, it can use the stored energy for DL ​​and / or UL signal amplification.

[0134] Device 2b: has energy storage capabilities and can independently generate signals, such as a radio frequency (RF) module that actively sends signals.

[0135] Among the aforementioned terminal 101 types, device 2b has the strongest capabilities and the highest terminal cost. Device 1 and device 2a have weaker capabilities and lower terminal costs. Furthermore, because devices 1 and 2a require backscattering and cannot actively transmit signals, their supported coverage range is smaller. However, the power consumption of device 1 or 2a in this operating mode is lower than that of device 2b.

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

[0137] In some embodiments, the network device 102 may include at least one of an access network device and a core network device.

[0138] Optionally, the access network device is, for example, a node or device that accesses the terminal to the 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 wireless fidelity (WiFi) system, but is not limited thereto.

[0139] In some embodiments, in an Ambient-IoT scenario, as shown in FIG1b , the communication system 100 may further include a continuous wave node (CWN) 103, an uplink receiver (UR) 104, and an energy source node (ESN) 105. The network device 102 may function as a downlink signal node (DSN). Alternatively, the network device 102 may be configured to implement at least one of the following functions: a DSN, CWN 103, UR 104, or ESN 105.

[0140] Optionally, the DSN is used to send downlink information or indication information. The DSN can be a network device 102 such as a base station or a relay device such as a relay UE. The DSN can send indication information to the terminal 101 to trigger uplink transmission of the terminal 101.

[0141] Optionally, CWN 103 is used to transmit continuous electromagnetic waves (CWs). Terminal 101 can use CWs to transmit uplink information based on backscatter. CWN 103 can implement an excitation function, enabling devices A and B to perform uplink transmission based on backscatter. In addition, CWs can serve as an energy source (ES), providing energy to Terminal 101, which can receive and store CWs.

[0142] Optionally, UR104 may be another terminal or user equipment (UE) other than terminal 101, configured to receive uplink information sent by Ambient-IoT terminal 101. For example, UR104 may receive uplink information sent by terminal 101 based on backscatter communication, or receive uplink information actively transmitted by terminal 101.

[0143] Optionally, ESN 105 is used to provide energy to terminal 101. For example, ESN 105 functions for device B and device C. Due to the limited energy storage capacity supported by device A, ES signals other than CW may not be defined for device A. Alternatively, ES may also be used for device A.

[0144] In some embodiments, as shown in Figure 1b, the Ambient-IoT communication system may include four links, for example: link 1 for transmitting downlink information, link 2 for receiving uplink information, link 3 for sending CW, and link 4 for sending charging signals.

[0145] Optionally, link 4 may be controlled by the network. For example, the network may control ESN 105 to turn on or off charging of terminal 101. The energy provided by ESN 105 may come from electromagnetic waves or non-electromagnetic waves. In this case, ESN 105 can better coordinate with network scheduling and other functions to ensure that terminal 101 is charged while minimizing the impact on terminal 101's communications. Alternatively, ESN 105 is not controlled by the network. In other words, terminal 101 flexibly collects energy on its own based on its capabilities and the energy sources in the actual environment. For example, it collects electromagnetic or non-electromagnetic wave energy that is not controlled by the network, and there is no specific ESN 105 node. In this case, link 4 can be considered non-existent.

[0146] Optionally, the nodes involved in the four links in the above embodiment, such as DSN, CWN 103, ESN 104, and UR 105, can be independently configured, or can be the same node or device, or two, three, or four of them can be configured as one node or device. For example, in some embodiments, link 4 can be omitted or non-existent.

[0147] In some embodiments, the functions of the above-mentioned different nodes can be implemented or supported by a single device. For example, a single device can support the functions of multiple nodes or all of the above-mentioned nodes. Alternatively, a single device can correspond to a node with only one of the above-mentioned functions. Network device 102 can coordinate the behavior of the above-mentioned different nodes, such as CWN 103, ESN 104, and UR 105, to support effective communication with terminal 101.

[0148] In some embodiments, the number of devices or nodes in FIG. 1 a and FIG. 1 b is for illustration only, and in actual applications, multiple devices or nodes may be used.

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

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

[0151] In some embodiments, the core network device can be a device including one or more network elements, or it can be multiple devices or device groups, each including all or part of one or more network elements. The network element can be virtual or physical. The core network includes, for example, at least one of the Evolved Packet Core (EPC), the 5G Core Network (5GCN), and the Next Generation Core (NGC). Alternatively, the core network device refers to a network element with a specific function, such as the Access Management Function (AMF), the Service Management Function (SMF), etc.

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

[0153] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG. 1 a or FIG. 1 b , or a partial body thereof, but are not limited thereto.

[0154] The entities shown in Figure 1a or 1b are examples. The communication system may include all or part of the entities in Figure 1a or 1b, or may include other entities other than Figure 1a or 1b. The number and form of each entity are arbitrary. The connection relationship between the entities is an example. The entities may be connected or disconnected, and the connection may be in any manner, which may be direct or indirect, and may be wired or wireless.

[0155] 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 utilizing other communication processing methods, and next-generation systems based on and extending these. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0156] Due to the complexity and variability of energy sources, an effective or reliable energy supply method needs to be provided for the Ambient-IoT terminal 101 .

[0157] FIG2a is an interactive diagram of a method for sending and receiving downlink information according to an embodiment of the present disclosure. As shown in FIG2a, an embodiment of the present disclosure relates to a method for sending and receiving downlink information, the method comprising:

[0158] Step S2101 , the network device 102 sends downlink information to the terminal 101 .

[0159] In some embodiments, the downlink information includes a charging signal, wherein the charging signal is used to provide energy to the terminal 101.

[0160] Optionally, the charging signal is an electromagnetic signal.

[0161] In some embodiments, the charging signal is placed in the downlink information, and the network device 102 can charge the terminal 101 by sending downlink information carrying the charging signal, thereby providing the terminal 101 with wireless electromagnetic wave energy controlled by the network device 102, thereby improving the reliability and stability of the energy.

[0162] In some embodiments, the downlink information includes at least one of the following information types:

[0163] Query signaling;

[0164] Repeat query QueryRep signaling;

[0165] Operation command (command).

[0166] Optionally, Query signaling can also be referred to as a Query command, and QueryRep signaling can also be referred to as a QueryRep command. Query signaling and QueryRep signaling are used in the Ambient-IoT warehouse inventory scenario. In the inventory process, network device 102 first sends a Query signaling, then a QueryRep signaling, and may send Query signaling or QueryRep signaling multiple times. In this scenario, terminal 101 can be a radio frequency identification (RFID) tag.

[0167] In the RFID warehouse inventory business model, after receiving a Query signaling, an RFID tag can set a random value counter based on the Q value in the Query signaling, where counter <= Q. If counter = 0, the RFID tag can begin backscattering uplink information, such as RN16 (a 16-bit random number) used to temporarily represent the tag ID. If the counter value is not 0, the RFID tag does not transmit information and waits to receive a QueryRep command. Each time the RFID tag receives a QueryRep command, the counter value is decremented by 1 until the counter value reaches 0, at which point the RFID tag will transition to the reply state and backscatter uplink information. If an ACK is received, the RFID tag confirms successful access. Otherwise, if an invalid ACK is received, an ACK with an erroneous RN16 is received, or if no corresponding command is received within a set period of time, the RFID tag considers the access unsuccessful.

[0168] Optionally, the operation command or simply command is used to instruct the operation of the terminal 101, such as instructing the RFID tag to write (write) or access (access).

[0169] In some embodiments, all of the above types of downlink information are applicable to the downlink information structure or downlink information frame structure in this embodiment, such as the downlink information including the charging signal. Alternatively, the charging signal and the non-charging signal are located in the same downlink information frame structure.

[0170] In one example, as shown in FIG2b , the downlink information includes a charging signal and a non-charging signal. The frame structure of the downlink information may include a first part and a second part, wherein the first part is used to carry the charging signal, and the second part is used to carry the non-charging signal. The time domain position of the second part is before or after the first part.

[0171] Alternatively, the non-charging signal may be another downlink signal. The non-charging signal may include at least one of the following: a preamble, control information, data information, etc. For example, the first part carries the charging signal, and the second part includes the preamble, control information, and data information in order from front to back in the time domain.

[0172] In some embodiments, some of the types of downlink information described above are applicable to the downlink information structure or the frame structure of downlink information in this embodiment, such as the downlink information including a charging signal, or including a charging signal and a non-charging signal.

[0173] In one example, still taking the example of Figure 2b as an example, for multiple downlink signalings in the inventory process, such as Query signaling and QueryRep signaling, only Query signaling is applicable to the frame structure of the downlink information in this embodiment, and QueryRep signaling is not applicable to the frame structure of the downlink information in this embodiment, such as Query signaling includes a charging signal, while QueryRep signaling does not include a charging signal.

[0174] In this example, when network device 102 initiates the inventory process, it can use the first Query signaling sent to charge terminal 101 with sufficient energy. The QueryRep signaling following the Query signaling does not need to carry a charging signal. Alternatively, if terminal 101 still needs to be charged after the Query signaling, it can be charged using methods other than the charging signal, such as other charging signals or other non-radio methods.

[0175] In some embodiments, the charging signal and the non-charging signal are located in the same frame structure of downlink information, and the downlink information can be sent through the same node, namely, network device 102. With reference to the structure of Figure 1b, in this embodiment, the network device includes ESN 105 and DSN, that is, ESN and DSN are the same node.

[0176] In some embodiments, parameters such as duration, power, or frequency of the charging signal in the downlink information may be implemented in multiple ways.

[0177] In some embodiments, the transmission power of the charging signal is greater than a threshold, or the downlink information further includes a non-charging signal, and the transmission power of the charging signal is greater than the transmission power of the non-charging signal.

[0178] Optionally, the charging signal is a high-power signal, which is higher than a threshold or higher than other downlink signals, thereby improving the charging effect.

[0179] Optionally, the downlink information includes multiple information types, and the sending power of the charging signal in the downlink information of different information types is the same.

[0180] For example, in conjunction with the aforementioned inventory process, the downlink information may include multiple downlink signaling messages, such as Query signaling and QueryRep signaling, both of which have the same power charging signal. Alternatively, the downlink information may include Query signaling and an operation command, both of which have the same power charging signal. Alternatively, the downlink information may include Query signaling, QueryRep signaling, and an operation command, all of which have the same power charging signal.

[0181] Optionally, the downlink information includes multiple information types, and the sending power of the charging signal in the downlink information of different information types is different, wherein the information type and the sending power have a mapping relationship.

[0182] For example, in conjunction with the aforementioned inventory process, downlink information includes three types: Query signaling, QueryRep signaling, and operation command signaling, each of which has a different power charging signal. A mapping relationship can be used to determine the corresponding transmit power for each type of downlink information. For example, Query signaling corresponds to a charging signal with a first transmit power, QueryRep signaling corresponds to a charging signal with a second transmit power, and operation command corresponds to a charging signal with a third transmit power.

[0183] In some embodiments, the duration of the charging signal is greater than or equal to a first duration, where the first duration is the duration required for charging the terminal configured by the network device or defined by the protocol.

[0184] Optionally, the duration can meet the charging requirement of the terminal 101, so that the terminal 101 can obtain sufficient energy during the process of receiving the charging signal. Optionally, the length of the first part is greater than or equal to the first duration.

[0185] Optionally, the downlink information includes multiple information types, and the durations of downlink information of different information types are the same.

[0186] For example, the duration is recorded as T. In combination with the above inventory process, downlink information includes three types: Query signaling, QueryRep signaling, and operation command, and the duration of the three types is the same T. Alternatively, downlink information includes two types: Query signaling and operation command, and the duration of the two types is the same T.

[0187] Optionally, the downlink information includes multiple information types, and the duration of the charging signal in the downlink information of different information types is different, wherein the information type and the duration have a mapping relationship.

[0188] For example, in combination with the aforementioned inventory process, downlink information includes three types: Query signaling, QueryRep signaling, and operation command, and the duration of the three is different.

[0189] For another example, in conjunction with the aforementioned inventory process, downlink information includes two types: query signaling and operation command, and the duration of the two types is different. For example, the duration of the charging signal in the query signaling is T1, and the duration of the charging signal in the operation command is T2, where T1>T2.

[0190] In some embodiments, the frequency of the charging signal includes a single frequency point or multiple frequency points.

[0191] Optionally, the charging signal may be a single-frequency signal, such as a single-frequency signal at frequency f0.

[0192] Optionally, the charging signal may be a multi-frequency signal, such as a charging signal including signals at multiple single-frequency points of frequency points f0, f1, f2, and f3. If deep channel attenuation occurs at a certain frequency point, the energy of the other frequency parts of the charging signal can continue to charge the terminal 101. For example, for a charging signal including multiple single-frequency point signals of f0, f1, f2, and f3, if deep channel attenuation occurs at frequency point f0, the charging signal can still be transmitted at f1, f2, and f3.

[0193] In some embodiments, the frequency domain bandwidth of the charging signal is a first value.

[0194] Optionally, the charging signal has a set frequency domain bandwidth. For example, the charging signal is a bandwidth signal with a bandwidth of W.

[0195] Optionally, within the bandwidth of the charging signal, if deep channel attenuation occurs in a certain frequency range, the energy of the charging signal in other frequency ranges can continue to charge the terminal 101. For example, for a charging signal with a bandwidth of W, if deep attenuation occurs in the frequency range f4-f5, the portion of the charging signal outside the frequency range f4-f5 can continue to charge the terminal 101.

[0196] Optionally, the frequency domain bandwidth of the non-charging signal is a second value, and the first value is the same as or different from the second value. For example, as shown in FIG2b , the frequency domain bandwidth of the charging signal and the frequency domain bandwidth of the downlink signal can be the same as or different.

[0197] In some embodiments, the first value is smaller than the second value, that is, the frequency domain bandwidth of the charging signal may be smaller than the bandwidth of the non-charging portion.

[0198] Optionally, in combination with the foregoing embodiment, the charging signal can be a high-power signal, for example, the transmission power of the charging signal is higher than the transmission power of the non-charging signal, so that the charging signal uses a smaller frequency domain bandwidth, which can reduce the impact on adjacent frequency communication signals.

[0199] In some embodiments, the terminal 101 receives downlink information from the network device 102 .

[0200] Step S2102: Terminal 101 stores the energy provided by the downlink information.

[0201] In some embodiments, the terminal 101 of this embodiment may be an Ambient-IoT terminal.

[0202] In some embodiments, the terminal 101 obtains radio electromagnetic wave energy by receiving a charging signal in downlink information, and the terminal 101 stores the energy for information reception, transmission, etc.

[0203] In some embodiments, the terminal 101 may perform corresponding operations according to the type of downlink information.

[0204] Optionally, in combination with the aforementioned inventory process, the terminal 101 may determine whether to perform uplink transmission according to the Query signaling and the QueryRep signaling.

[0205] Optionally, the terminal 101 may perform a corresponding write or access operation according to the instruction of the operation command.

[0206] In some embodiments, the terminal 101 may also perform corresponding operations according to the non-charging signal portion in the downlink information.

[0207] Optionally, the terminal 101 may be synchronized according to the preamble.

[0208] Optionally, the terminal 101 may obtain the operation indicated by the network device 102 according to the data information and perform the corresponding operation.

[0209] In some embodiments, the terminal 101 may communicate based on a backscattering method. Backscattering or backscatter communications is an extremely low-power modulation and transmission technology that uses the principle of backscattering of radio frequency signals, and is a means to achieve the intelligent connection of all things. In backscattering communications, radio frequency signals such as electromagnetic waves are received by the terminal 101, and the internal circuit of the terminal 101 modulates the information to be transmitted on the basis of the incident electromagnetic wave through load impedance modulation and other methods, and then sends out the modulated electromagnetic wave carrying the information. There are many ways to modulate information, such as amplitude shift keying (ASK), frequency-shift keying (FSK) or phase-shift keying (PSK).

[0210] In some embodiments, for a terminal 101 using a backscatter method, the workflow may include: the network device 102 sends a downlink instruction (such as Query signaling or QueryRep signaling) to the terminal 101, and after receiving the downlink instruction, the terminal 101 sends a corresponding response to the network device 102 or performs a corresponding operation.

[0211] Optionally, when terminal 101 transmits data to UR 104, it requires an energy source, such as CWN 103, to provide CW for reflection (i.e., link 3 is required). CW typically has a constant amplitude. The frequency of the electromagnetic wave reflected by terminal 101 can be exactly the same as the CW frequency, or there can be some offset. The offset size depends on the hardware characteristics of terminal 101. For example, the offset may be a fixed value, or, if supported by terminal 101 hardware, it may support multiple fixed values, or a dynamically adjustable value.

[0212] In some embodiments, for the Ambient-IoT terminal 101, one way to utilize frequency resources is to divide the available spectrum into multiple sub-channels, each sub-channel occupies a fixed bandwidth, and the sub-channels are orthogonal in the frequency domain. The terminal 101 can be instructed by the network to use one or more of the sub-channels to transmit data, or it can select one or more sub-channels to transmit data through a certain algorithm. For the terminal 101 using the backscattering method, the working bandwidth of its antenna is relatively wide, for example, tens of megahertz (Mhz). If the CWN 103 transmits CWs at multiple frequency points within the working bandwidth of the terminal 101, then the terminal 101 will receive CWs at multiple frequency points and backscatter these multiple CWs, that is, the terminal 101 does not have the ability to reflect only the CW of the specific sub-channel it selects. Which uplink sub-channel the terminal 101 can use for uplink transmission actually depends on the frequency and offset capabilities of the CW.

[0213] In some embodiments, different types of terminals 101 may have different circuit system architectures.

[0214] In one example, if terminal 101 is device 1 (device 1), its circuit system architecture can be referenced as shown in Figure 2c. In this example, terminal 101 may include a clock generator, base band logics (BB logics), and memory, as well as an antenna, a link for charging, a link for uplink transmission, and a link for downlink reception.

[0215] The logic circuit may include a decoder, a controller, and an encoder.

[0216] The link for charging may include at least the following circuit structures: a matching network (Matching Network), an RF energy harvester (RF Energy Harvester), a power management unit (Power Management Unit, PMU) and an energy storage unit (Energy Storage), etc.

[0217] The link for downlink reception may include at least the following circuit structures: a matching network, an RF bandpass filter (BPF), an RF envelope detector (RF Envelope Detector), a baseband low-pass filter (BB LPF), a comparator, etc.

[0218] The link for uplink transmission may include at least the following circuit structures: a backscatter modulator, which can be used for impedance switching.

[0219] In another example, if terminal 101 is device 2a and has an RF receiver, its circuit system architecture can be shown in Figure 2d. In this example, terminal 101 may include a clock generator, logic circuits, and memory, as well as an antenna, a link for charging, a link for uplink transmission, and a link for downlink reception.

[0220] Among them, the logic circuit may include a decoder, a controller and an encoder.

[0221] The link for charging may include at least the following circuit structures: a matching network, an RF energy harvester, a PMU, an energy storage unit, and an energy harvester (other than RF).

[0222] The link for downlink reception may include at least the following circuit structures: a matching network, an RF BPF, a low noise amplifier (LNA), an RF envelope detector, a baseband amplifier (BB AMP), a BB LPF, and a comparator or an analog-to-digital converter (N-bit ADC), etc.

[0223] The link for uplink transmission may include at least the following circuit structures: a reflection amplifier, a backscatter modulator, and a large frequency shifter; wherein the backscatter modulator can be used for impedance switching.

[0224] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", and "field" can be used interchangeably.

[0225] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0226] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0227] In some embodiments, the terms "radio", "wireless", "radio access network (RAN)", "access network (AN)", "RAN-based" and the like may be used interchangeably.

[0228] In some embodiments, terms such as "moment", "time point", "time", and "time position" can be replaced with each other, and terms such as "duration", "period", "time window", "window", and "time" can be replaced with each other.

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

[0230] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "a certain", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, or first A, etc., but not limited to this.

[0231] In some embodiments, the determination or judgment can be performed by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values ​​(for example, comparison with a predetermined value), but is not limited thereto.

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

[0233] The method involved in the embodiment of the present disclosure may include at least one of steps S2101 to S2102.

[0234] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2 a .

[0235] FIG3 is a flow chart of a method for sending downlink information according to an embodiment of the present disclosure. As shown in FIG3 , the embodiment of the present disclosure relates to a method for sending downlink information, which is executed by the network device 102 and includes:

[0236] Step S3101, sending downlink information to terminal 101.

[0237] In some embodiments, the implementation of step S3101 can refer to the implementation of step S2101 and will not be repeated here.

[0238] Optionally, the downlink information includes a charging signal, wherein the charging signal is used to provide energy to the terminal.

[0239] In some embodiments, the downlink information includes at least one of the following information types:

[0240] Query signaling;

[0241] Repeat query QueryRep signaling;

[0242] Operation command.

[0243] In some embodiments, the sending power of the charging signal is greater than a threshold, or,

[0244] The downlink information also includes a non-charging signal, and the sending power of the charging signal is greater than the sending power of the non-charging signal.

[0245] In some embodiments, the downlink information includes multiple information types, and the sending power of the charging signal in the downlink information of different information types is the same.

[0246] In some embodiments, the downlink information includes multiple information types, and the sending power of the charging signal in the downlink information of different information types is different, wherein the information type and the sending power have a mapping relationship.

[0247] In some embodiments, the duration of the charging signal in the downlink information is greater than or equal to a first duration, where the first duration is the duration required for charging the terminal configured by the network device or defined by the protocol.

[0248] In some embodiments, the downlink information includes multiple information types, and the duration of downlink information of different information types is the same.

[0249] In some embodiments, the downlink information includes multiple information types, and the downlink information of different information types has different durations, wherein the information types and durations have a mapping relationship.

[0250] In some embodiments, the frequency of the charging signal includes a single frequency point or multiple frequency points.

[0251] In some embodiments, the frequency domain bandwidth of the charging signal is a first value.

[0252] In some embodiments, the frequency domain bandwidth of the non-charging signal included in the downlink information is a second value, and the first value is the same as or different from the second value.

[0253] In some embodiments, the network device includes an energy source node ESN and a downlink information sending node DSN.

[0254] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 3 .

[0255] FIG4 is a flow chart of a method for receiving downlink information according to an embodiment of the present disclosure. As shown in FIG4 , the embodiment of the present disclosure relates to a method for receiving downlink information, which is executed by terminal 101 and includes:

[0256] Step S4101: Receive downlink information sent by the network device 102.

[0257] In some embodiments, the implementation of step S4101 can refer to the implementation of step S2101 and will not be repeated here.

[0258] Optionally, the downlink information includes a charging signal, wherein the charging signal is used to provide energy to the terminal.

[0259] In some embodiments, the downlink information includes at least one of the following information types:

[0260] Query signaling;

[0261] Repeat query QueryRep signaling;

[0262] Operation command.

[0263] In some embodiments, the sending power of the charging signal is greater than a threshold, or,

[0264] The downlink information also includes a non-charging signal, and the sending power of the charging signal is greater than the sending power of the non-charging signal.

[0265] In some embodiments, the downlink information includes multiple information types, and the sending power of the charging signal in the downlink information of different information types is the same.

[0266] In some embodiments, the downlink information includes multiple information types, and the sending power of the charging signal in the downlink information of different information types is different, wherein the information type and the sending power have a mapping relationship.

[0267] In some embodiments, the duration of the charging signal in the downlink information is greater than or equal to a first duration, where the first duration is the duration required for charging the terminal configured by the network device or defined by the protocol.

[0268] In some embodiments, the downlink information includes multiple information types, and the duration of downlink information of different information types is the same.

[0269] In some embodiments, the downlink information includes multiple information types, and the duration of downlink information of different information types is different, wherein the information type and the duration have a mapping relationship.

[0270] In some embodiments, the frequency of the charging signal includes a single frequency point or multiple frequency points.

[0271] In some embodiments, the frequency domain bandwidth of the charging signal is a first value.

[0272] In some embodiments, the frequency domain bandwidth of the non-charging signal included in the downlink information is a second value, and the first value is the same as or different from the second value.

[0273] In some embodiments, the network device includes an energy source node ESN and a downlink information sending node DSN.

[0274] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 4 .

[0275] In the method of the embodiment of the present disclosure, a method for wireless charging in an ambient IoT network is provided to ensure that the device has sufficient energy to send and receive information. Optionally, the device corresponds to the terminal 101 in the aforementioned embodiment. To facilitate understanding of the embodiment of the present disclosure, some examples are listed below:

[0276] Example 1:

[0277] Provides a frame structure design for sending information from network device to device, and places the charging signal in the frame structure.

[0278] Optionally, as shown in FIG2b , the frame structure includes a charging signal portion and other downlink signal portions.

[0279] Optionally, other downlink signal parts may be composed of preamble, downlink control information, data information, etc.

[0280] Example 2:

[0281] Based on Example 1, the charging signal portion includes a charging signal for wirelessly charging the device. The charging signal can be a high-power signal, for example, having a higher transmission power than other downlink signals.

[0282] Example 3:

[0283] Based on Example 1 or Example 2, the duration of the charging signal portion is T to meet the requirement of charging the device.

[0284] Example 4:

[0285] Based on any of the above examples, the frequency of the charging signal may be a single-frequency signal, for example, a single-frequency signal at frequency f0.

[0286] Example 5:

[0287] Based on any of the above examples, the charging signal can be a multi-frequency signal, such as a signal at multiple single frequencies of frequency points f0 / f1 / f2 / f3. It can also be a signal with a certain bandwidth, such as a bandwidth signal with a bandwidth of W.

[0288] Optionally, if deep channel attenuation occurs at a certain frequency / frequency range, the energy of the charging signal at other frequencies / frequency ranges can continue to charge the device. For example, for a charging signal at multiple single frequencies (f0 / f1 / f2 / f3), if deep channel attenuation occurs at frequency f0, the charging signal can still be transmitted at frequencies f1 / f2 / f3. For another example, for a charging signal with a bandwidth of W, if deep attenuation occurs in the frequency range f4-f5, the portion of the charging signal outside the f4-f5 frequency range can continue to charge the device.

[0289] Example 6:

[0290] Based on any of the above examples, the charging signal and other downlink signals are sent by the same node and are in the same frame structure, that is, the ESN and DSN are the same node.

[0291] Example 7:

[0292] Based on any of the above examples, this frame structure is applied to downlink transmission of all types of downlink signals between the DSN and the device.

[0293] Optionally, different types of downlink signals have the same T. For example, multiple downlink signalings (Query, QueryRep) in an inventory process and commands (such as write, access, etc.) used to send operation instructions to a device all have the same T.

[0294] Optionally, different types of downlink signals have different Ts. For example, multiple downlink signalings (Query, QueryRep) in an inventory process and commands (such as write, access, etc.) used to send operation instructions to a device have different Ts.

[0295] Optionally, different types of downlink signals may have the same charging signal power. For example, multiple downlink signalings (Query, QueryRep) in an inventory process, and commands (such as write, access, etc.) used to send operation instructions to the device, may all have the same charging signal power.

[0296] Optionally, different charging signal powers may be used for different types of downlink signals. For example, multiple downlink signalings (Query, QueryRep) in an inventory process, and commands (such as write, access, etc.) used to send operation instructions to the device, may have different charging signal powers.

[0297] Example 8:

[0298] Based on any of the above examples, this frame structure is only applied to the downlink transmission of some types of downlink signals between the DSN and the device.

[0299] Optionally, the multiple downlink signaling (Query, QueryRep) in the inventory process is only used in the Query information frame, not in the QueryRep frame. This means that when the network initiates the inventory process, the device can be charged sufficiently when the first Query signaling is sent, and there is no need to add the charging signal frame structure in subsequent QueryRep signaling. However, this does not mean that the device cannot be charged through signals outside the frame structure or through other non-radio methods.

[0300] Optionally, in some types of downlink signals using this frame structure, the duration T of the charging signal may be the same or different. For example, in a frame containing query information, the duration of the charging signal is T1, and in a frame containing a downlink command, the duration of the charging signal is T2, where T1>T2.

[0301] The embodiments of the present disclosure further 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, a core network function node, a core network device, etc.) in any of the above methods.

[0302] It should be understood that the division of the various units or modules in the above device 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 device, 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.

[0303] 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. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing 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.

[0304] Figure 5a is a schematic diagram of the structure of a terminal according to an embodiment of the present disclosure. As shown in Figure 5a, terminal 5100 may include at least one of a transceiver module 5101 and a processing module 5102. In some embodiments, transceiver module 5101 is configured to receive downlink information sent by a network device, wherein the downlink information includes a charging signal, wherein the charging signal is used to provide energy to the terminal.

[0305] Optionally, the transceiver module 5101 is configured to execute at least one of the communication steps of sending and / or receiving performed by the terminal 101 in any of the above methods, which are not described in detail here. Optionally, the processing module 5102 is configured to execute at least one of the other steps performed by the terminal 101 in any of the above methods, which are not described in detail here.

[0306] In some embodiments, the downlink information includes at least one of the following information types:

[0307] Query signaling;

[0308] Repeat query QueryRep signaling;

[0309] Operation command.

[0310] In some embodiments, the sending power of the charging signal is greater than a threshold, or,

[0311] The downlink information also includes a non-charging signal, and the sending power of the charging signal is greater than the sending power of the non-charging signal.

[0312] In some embodiments, the downlink information includes multiple information types, and the sending power of the charging signal in the downlink information of different information types is the same.

[0313] In some embodiments, the downlink information includes multiple information types, and the sending power of the charging signal in the downlink information of different information types is different, wherein the information type and the sending power have a mapping relationship.

[0314] In some embodiments, the duration of the charging signal in the downlink information is greater than or equal to a first duration, where the first duration is the duration required for charging the terminal configured by the network device or defined by the protocol.

[0315] In some embodiments, the downlink information includes multiple information types, and the duration of downlink information of different information types is the same.

[0316] In some embodiments, the downlink information includes multiple information types, and the duration of downlink information of different information types is different, wherein the information type and the duration have a mapping relationship.

[0317] In some embodiments, the frequency of the charging signal includes a single frequency point or multiple frequency points.

[0318] In some embodiments, the frequency domain bandwidth of the charging signal is a first value.

[0319] In some embodiments, the frequency domain bandwidth of the non-charging signal included in the downlink information is a second value, and the first value is the same as or different from the second value.

[0320] In some embodiments, the network device includes an energy source node ESN and a downlink information sending node DSN.

[0321] Figure 5b is a schematic diagram of the structure of a network device according to an embodiment of the present disclosure. As shown in Figure 5b, network device 5200 may include at least one of a transceiver module 5201 and a processing module 5202. In some embodiments, when network device 5200 is a network device, transceiver module 5201 is configured to send downlink information to a terminal, where the downlink information includes a charging signal, wherein the charging signal is configured to provide energy to the terminal.

[0322] Optionally, the transceiver module 5201 is configured to execute at least one of the communication steps of sending and / or receiving performed by the network device in any of the above methods, which are not described in detail here. Optionally, the processing module 5202 is configured to execute at least one of the other steps performed by the network device 102 in any of the above methods, which are not described in detail here.

[0323] In some embodiments, the downlink information includes at least one of the following information types:

[0324] Query signaling;

[0325] Repeat query QueryRep signaling;

[0326] Operation command.

[0327] In some embodiments, the sending power of the charging signal is greater than a threshold, or,

[0328] The downlink information also includes a non-charging signal, and the sending power of the charging signal is greater than the sending power of the non-charging signal.

[0329] In some embodiments, the downlink information includes multiple information types, and the sending power of the charging signal in the downlink information of different information types is the same.

[0330] In some embodiments, the downlink information includes multiple information types, and the sending power of the charging signal in the downlink information of different information types is different, wherein the information type and the sending power have a mapping relationship.

[0331] In some embodiments, the duration of the charging signal in the downlink information is greater than or equal to a first duration, where the first duration is the duration required for charging the terminal configured by the network device or defined by the protocol.

[0332] In some embodiments, the downlink information includes multiple information types, and the duration of downlink information of different information types is the same.

[0333] In some embodiments, the downlink information includes multiple information types, and the duration of downlink information of different information types is different, wherein the information type and the duration have a mapping relationship.

[0334] In some embodiments, the frequency of the charging signal includes a single frequency point or multiple frequency points.

[0335] In some embodiments, the frequency domain bandwidth of the charging signal is a first value.

[0336] In some embodiments, the frequency domain bandwidth of the non-charging signal included in the downlink information is a second value, and the first value is the same as or different from the second value.

[0337] In some embodiments, the network device includes an energy source node ESN and a downlink information sending node DSN.

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

[0339] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.

[0340] Figure 6a is a schematic diagram of the structure of a communication device 6100 proposed in an embodiment of the present disclosure. Communication device 6100 can be a network device (e.g., an access network device, a core network device, etc.), a terminal (e.g., a user equipment, etc.), a chip, a chip system, or a processor that supports a network device implementing any of the above methods, or a chip, a chip system, or a processor that supports a terminal implementing any of the above methods. Communication device 6100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0341] As shown in Figure 6a, the communication device 6100 includes one or more processors 6101. The processor 6101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process the communication protocol and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. Optionally, the communication device 6100 is used to perform any of the above methods. Optionally, one or more processors 6101 are used to call instructions to enable the communication device 6100 to perform any of the above methods.

[0342] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceiver 6102 performs at least one of the communication steps, such as sending and / or receiving, in the above-described method, and the processor 6101 performs at least one of the other steps. In an optional embodiment, the transceiver may include a receiver and / or a transmitter, and the receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface 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.

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

[0344] The communication device 6100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 6100 described in the present disclosure is not limited thereto, and the structure of the communication device 6100 may not be limited by FIG. 6a. The communication device may be 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.

[0345] FIG6b is a schematic diagram of the structure of a chip 6200 according to an embodiment of the present disclosure. If the communication device 6100 can be a chip or a chip system, reference can be made to the schematic diagram of the structure of the chip 6200 shown in FIG6b , but the present disclosure is not limited thereto.

[0346] The chip 6200 includes one or more processors 6201. The chip 6200 is configured to execute any of the above methods.

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

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

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

[0350] The present disclosure also proposes a storage medium having instructions stored thereon. When the instructions are executed on the communication device 6100, the communication device 6100 executes 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 is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a transient storage medium.

[0351] The present disclosure also provides a program product, which, when executed by the communication device 6100, enables the communication device 6100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0352] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods. Industrial Applicability

[0353] The network device sends downlink information and supplies energy to the terminal through the charging signal in the downlink information, so that the terminal can be charged while receiving downlink information, improving the charging efficiency and ensuring sufficient energy for data transmission and reception.

Claims

1. A method for sending downlink information, performed by a network device, the method comprising: Downlink information is sent to a terminal, where the downlink information includes a charging signal, wherein the charging signal is used to provide energy for the terminal.

2. The method according to claim 1, wherein The downlink information includes at least one of the following information types: Query signaling; Repeat query QueryRep signaling; Operation command.

3. The method according to claim 1 or 2, wherein The sending power of the charging signal is greater than a threshold, or, The downlink information further includes a non-charging signal, and a transmission power of the charging signal is greater than a transmission power of the non-charging signal.

4. The method according to claim 3, wherein: The downlink information includes multiple information types, and the sending power of the charging signal in the downlink information of different information types is the same.

5. The method according to claim 3, wherein: The downlink information includes multiple information types, and the sending power of the charging signal in the downlink information of different information types is different, wherein the information type and the sending power have a mapping relationship.

6. The method according to claim 1 or 2, wherein: The duration of the charging signal in the downlink information is greater than or equal to a first duration, where the first duration is a duration required for charging the terminal configured by the network device or defined by a protocol.

7. The method according to claim 6, wherein: The downlink information includes multiple information types, and the durations in the downlink information of different information types are the same.

8. The method of claim 6, wherein: The downlink information includes multiple information types. The durations in the downlink information of different information types are different. The information types and the durations are in a mapping relationship.

9. The method according to any one of claims 1 to 8, wherein: The frequency of the charging signal includes a single frequency point or multiple frequency points.

10. The method according to any one of claims 1 to 8, wherein: The frequency domain bandwidth of the charging signal is a first value.

11. The method according to claim 10, wherein: The frequency domain bandwidth of the non-charging signal included in the downlink information is a second value, and the first value is the same as or different from the second value.

12. The method according to any one of claims 1 to 8, wherein: The network device includes an energy source node ESN and a downlink information sending node DSN.

13. A method for receiving downlink information, performed by a terminal, the method comprising: Receive downlink information sent by a network device, where the downlink information includes a charging signal, wherein the charging signal is used to provide energy for the terminal.

14. The method of claim 13, wherein: The downlink information includes at least one of the following information types: Query signaling; Repeat query QueryRep signaling; Operation command.

15. The method according to claim 13 or 14, wherein: The sending power of the charging signal is greater than a threshold, or, The downlink information further includes a non-charging signal, and a transmission power of the charging signal is greater than a transmission power of the non-charging signal.

16. The method of claim 15, wherein: The downlink information includes multiple information types, and the sending power of the charging signal in the downlink information of different information types is the same.

17. The method of claim 15, wherein: The downlink information includes multiple information types, and the sending power of the charging signal in the downlink information of different information types is different, wherein the information type and the sending power have a mapping relationship.

18. The method according to claim 13 or 14, wherein The duration of the charging signal in the downlink information is greater than or equal to a first duration, where the first duration is the duration required for charging the terminal configured by the network device or defined by a protocol.

19. The method of claim 18, wherein: The downlink information includes multiple information types, and the durations in the downlink information of different information types are the same.

20. The method of claim 18, wherein: The downlink information includes multiple information types. The durations in the downlink information of different information types are different. The information types and the durations are in a mapping relationship.

21. The method according to any one of claims 13 to 20, wherein: The frequency of the charging signal includes a single frequency point or multiple frequency points.

22. The method according to any one of claims 13 to 20, wherein: The frequency domain bandwidth of the charging signal is a first value.

23. The method of claim 22, wherein: The frequency domain bandwidth of the non-charging signal included in the downlink information is a second value, and the first value is the same as or different from the second value.

24. The method according to any one of claims 12 to 19, wherein: The network device includes an energy source node ESN and a downlink information sending node DSN.

25. A network device comprising: The transceiver module is used to send downlink information to the terminal, where the downlink information includes a charging signal, wherein the charging signal is used to provide energy for the terminal.

26. A terminal comprising: The transceiver module is used to receive downlink information sent by a network device, where the downlink information includes a charging signal, wherein the charging signal is used to provide energy for the terminal.

27. A network device comprising: one or more processors; The network device is configured to implement the method according to any one of claims 1 to 12.

28. A terminal comprising: one or more processors; The network device is configured to implement the method according to any one of claims 13 to 24.

29. A communication system comprising a terminal and a network device, wherein: The network device is configured to implement the method according to any one of claims 1 to 12; The terminal is configured to implement the method according to any one of claims 13 to 24.

30. A storage medium storing instructions, wherein: When the instruction is executed on a communication device, the communication device is caused to perform the method according to any one of claims 1 to 12 or any one of claims 13 to 24.

31. A program product, wherein When the program product is executed by a communication device, the communication device is caused to execute the method according to any one of claims 1 to 12 or any one of claims 13 to 24.

Images