Methods for node for wireless communication, and apparatus

Abstract

Provided are methods for a node for wireless communication, and an apparatus. A method comprises: a first node sending first information, the first information being used for indicating a capability of the first node to write data; a second node sending a write instruction and data on the basis of the first information; and the first node writing the data.

Description

Methods and apparatus for nodes used in wireless communication Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a method and apparatus for use in a node for wireless communication. Background Technology

[0002] With the evolution of communication systems, many new technologies have been introduced into wireless communication systems. For example, the Internet of Things (IoT) has been introduced, where tags act as terminal devices, base stations as readers, and tags communicate with readers. However, these tag-like terminal devices are small, have limited battery capacity, and restricted transmission capabilities. Insufficient power during data writing can lead to write failures, affecting service transmission. Improving the reliability of transmission capabilities for these terminal devices is a pressing issue that needs to be addressed. Summary of the Invention

[0003] This application provides a method and apparatus for use in a node for wireless communication. The various aspects covered in this application are described below.

[0004] In a first aspect, a method is provided for a first node in wireless communication, comprising: transmitting first information, the first information indicating the first node's ability to write data; receiving a write instruction and data; and writing the data according to the write instruction.

[0005] In a second aspect, a method for a second node in wireless communication is provided, comprising: acquiring capability information of a first node, the capability information being used to indicate the first node's ability to write data; sending a write command and data; and performing service transmission based on the data.

[0006] Thirdly, a first node for wireless communication is provided, comprising a transceiver, a memory, and a processor, wherein the memory stores a program, the processor invokes the program in the memory, and controls the transceiver to receive or transmit signals to cause the first node to perform the method as described in the first aspect.

[0007] Fourthly, a second node for wireless communication is provided, comprising a transceiver, a memory, and a processor, wherein the memory stores a program, the processor invokes the program in the memory, and controls the transceiver to receive or transmit signals to cause the second node to perform the method as described in the second aspect.

[0008] Fifthly, embodiments of this application provide a communication system including the aforementioned first node and / or second node. In another possible design, the system may further include other devices that interact with the first node or second node as provided in the embodiments of this application.

[0009] Sixthly, embodiments of this application provide a computer-readable storage medium storing a computer program that causes a computer to perform some or all of the steps in the methods described above.

[0010] In a seventh aspect, embodiments of this application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps of the methods described in the foregoing aspects. In some implementations, the computer program product may be a software installation package.

[0011] Eighthly, embodiments of this application provide a chip including a memory and a processor, the processor being able to call and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects.

[0012] In this embodiment, a first node sends first information, which indicates the first node's ability to write data; a second node sends a write command and data based on the first information; and the first node writes the data. This application can effectively manage the power consumption of AIoT devices to avoid power outages or delayed writes when writing to the NVM. Attached Figure Description

[0013] Figure 1 is a system architecture example diagram of a wireless communication system that can be applied to the embodiments of this application.

[0014] Figure 2 is a schematic diagram of a network architecture applicable to embodiments of this application.

[0015] Figures 3A and 3B are schematic diagrams of wireless protocol stack structures applicable to embodiments of this application.

[0016] Figure 4 is a schematic diagram of the wireless communication system 100 used in an embodiment of this application.

[0017] Figure 5 shows one possible structure of the energy harvesting module.

[0018] Figure 6 illustrates the backscatter communication principle of an embodiment of this application.

[0019] Figure 7 is a circuit diagram of a terminal based on resistive load modulation technology.

[0020] Figures 8 and 9 are architecture diagrams of low-power Internet of Things based on cellular networks applicable to the embodiments of this application.

[0021] Figure 10 is a diagram showing the energy accumulation of an ambient internet of things (AIoT) device according to an embodiment of this application.

[0022] Figure 11 is a schematic diagram of data writing in an AIoT device according to an embodiment of this application.

[0023] Figure 12 is a flowchart illustrating a method for a first node and a second node in wireless communication according to an embodiment of this application.

[0024] Figure 13 is a flowchart illustrating another method for a first node and a second node in wireless communication provided in an embodiment of this application.

[0025] Figure 14 is an example of the method shown in Figure 13.

[0026] Figure 15 is an example of one of the methods shown in Figures 12 and 13.

[0027] Figure 16 shows another example of the methods illustrated in Figures 12 and 13.

[0028] Figure 17 is a schematic diagram of the structure of a first node for wireless communication provided in an embodiment of this application.

[0029] Figure 18 is a schematic diagram of the structure of a second node for wireless communication provided in an embodiment of this application.

[0030] Figure 19 is a schematic diagram of the structure of a communication device provided in an embodiment of this application.

[0031] Figure 20 is a schematic diagram of the hardware module of the communication device provided in the embodiment of this application. Detailed Implementation

[0032] Communication system architecture

[0033] The wireless communication system of this application embodiment may include a network device and a terminal device. The network device may be a device that communicates with the terminal device. The network device may provide communication coverage for a specific geographical area and may communicate with terminal devices located within that coverage area.

[0034] Figure 1 exemplarily illustrates a wireless communication system 100 including a network device 110 and multiple terminal devices, such as terminal devices 120a to 120j in the figure. Optionally, the wireless communication system 100 may include multiple network devices, and each network device may include other numbers of terminal devices within its coverage area; this application embodiment does not limit this.

[0035] Optionally, the wireless communication system may also include other network entities such as a network controller and a mobility management entity, which is not limited in this embodiment.

[0036] It should be understood that the technical solutions of the embodiments of this application can be applied to various communication systems, such as: 5th-generation (5G) systems or new radio (NR) systems, long-term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, advanced long-term evolution (LTE-A) systems, enhanced 5G (5G advanced) systems, low-power communication systems, etc. The technical solutions provided in this application can also be applied to future communication systems, such as 6th-generation (6G) mobile communication systems, satellite communication systems, and so on.

[0037] Prior to NR systems, communication technologies allowed terminal devices to simultaneously support multiple communication technologies, with each technology corresponding to a different multiple access method. However, with technological advancements, in NR systems and subsequent communication technologies, a single communication system can now support multiple multiple access methods.

[0038] It should be understood that multiple access methods, also known as multiple access schemes or multiple access technologies, refer to the techniques used in a network (such as a mobile communication cell or wireless local area network) to efficiently share a single wireless resource (such as time / frequency / space / carrier) when multiple users access the network. That is, when multiple users share a wireless resource, it is divided according to time, frequency, space, coding, subcarriers, etc., so that different users can use (or access) that segmented resource for communication under different segmentation methods. Occupying different segmented resources is like having different addresses, and the same wireless resource can have multiple addresses, hence the name multiple access. Multiple access methods are broadly divided into two categories: orthogonal multiple access (OMA), where there is no interference between users; and non-orthogonal multiple access (NOMA), where each user's signal may interfere with other users' signals.

[0039] The multiple access methods involved in this application include, but are not limited to, the following: frequency division multiple access (FDMA), time division multiple access (TDMA), code division multiple access (CDMA), space division multiple access (SDMA), carrier sense multiple access with collision avoidance (CSMA / CA), non-orthogonal multiple access (NOMA), orthogonal frequency division multiple access (OFDMA), single-carrier frequency division multiple access (SC-FDMA), and other multiple access methods.

[0040] The following description is for illustrative purposes and uses NR terminology in most of the description. However, these technologies can also be applied to applications beyond NR systems, such as 6th Generation (6G) communication systems. Wireless communication systems include terminal equipment and network-side equipment.

[0041] It should be understood that 6G systems will employ more flexible and efficient multiple access methods. For example, Non-Orthogonal Multiple Access (NOMA) technology transmits data from multiple users simultaneously within the same frequency band and utilizes the differences between users to optimize resource allocation and interference management; sparse codebooks and multi-modulation techniques can be used to improve spectrum efficiency and transmission performance. Other methods include interleaved multiple access, multi-user shared access, resource-extended multiple access, and UMA (unsourced multiple access).

[0042] The terms "system" and "network" in the embodiments of this application are often used interchangeably, and the described technologies can be used in the systems and radio technologies mentioned above, as well as in other systems and radio technologies.

[0043] It should be understood that all or part of the functions of the communication device in this application can also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (e.g., a cloud platform).

[0044] Figure 2 illustrates a schematic diagram of a network architecture 200 according to an embodiment of this application. This network architecture 200 describes the network architecture of a 5G NR / LTE / LTE-A system, which can also be referred to as a 5G system (5GS) / evolved packet system (EPS) network architecture. The network architecture 200 includes at least one of the following: network device 110, terminal device 120, 5G core network (5GC) / evolved packet core (EPC) 210, home subscriber server (HSS) / unified data management (UDM) 220, and Internet service 230. The network device and terminal device in Figure 2 are illustrated using RAN and UE as examples, respectively.

[0045] As shown in Figure 2, network device 110 provides user plane and control plane protocol termination to terminal device 120. Network device 110 is connected to 5GC / EPC 210 via an S1 / NG interface. 5GC / EPC 210 includes a mobility management entity (MME) / authentication management field (AMF) / session management function (SMF) 211, other MMEs / AMFs / SMFs 214, a service gateway (S-GW) / user plane function (UPF) 212, and a packet data network gateway (P-GW) / UPF 213. MME / AMF / SMF 211 is the control node that handles signaling between terminal device 120 and 5GC / EPC 210. Generally, MME / AMF / SMF 211 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the S-GW / UPF212, which is itself connected to the P-GW / UPF213. The P-GW provides UE IP address allocation and other functions. The P-GW / UPF213 is connected to Internet service 230. Internet service 230 includes operator-compliant Internet Protocol services, specifically including the Internet, intranet, IP multimedia subsystem (IMS), and packet-switched streaming services. It is evident that network architecture 200 provides packet-switched services; however, those skilled in the art will readily understand that the various concepts presented herein can be extended to networks providing circuit-switched services or other cellular networks.

[0046] Figures 3A and 3B respectively illustrate a schematic diagram of a wireless protocol stack structure according to an embodiment of this application. Figures 3A and 3B use a 5G wireless protocol stack as an example for illustration. The 5G wireless protocol stack is divided into two planes: the user plane (UP) protocol stack and the control plane (CP) protocol stack. The user plane protocol stack is the protocol suite used for user data transmission, and the control plane protocol stack is the protocol suite used for control signaling transmission in the 5G system. The specific names of each protocol stack layer are as follows:

[0047] As shown in Figure 3A, the user plane protocol stack includes, from top to bottom, the following layers: Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and Physical (PHY) layer.

[0048] As shown in Figure 3B, the control plane protocol stack includes, from top to bottom: non-access stratum (NAS); radio resource control (RRC) layer, PDCP layer, RLC layer, MAC layer, and PHY layer.

[0049] It should be understood that the different layers in the above protocol stack have different functions, and they work together through inter-layer interaction to achieve communication between terminal devices and network devices. With the development of artificial intelligence technology, AI-assisted computing has permeated the processing implementation methods of the above protocol stack. For example, the scheduling algorithm of the MAC layer and the encoding / decoding algorithm of the PHY layer can apply artificial intelligence algorithms to improve the performance of communication algorithms.

[0050] As an example, the wireless protocol architecture in Figures 3A and 3B is applicable to the first node in this application.

[0051] As an example, the wireless protocol architecture in Figures 3A and 3B is applicable to the second node in this application.

[0052] It should be understood that some functionalities in a wireless protocol architecture can also be implemented in one or more devices. For example, the functions of different layers in the control plane protocol stack can be implemented by multiple nodes on the network side.

[0053] It should be understood that the interpretation of the terminology in the embodiments of this application may refer to the TS36, TS37 and TS38 series of specifications of the 3rd generation partnership project (3GPP), but may also refer to the specifications of the Institute of Electrical and Electronics Engineers (IEEE).

[0054] To facilitate understanding, some related technical knowledge involved in the embodiments of this application is first introduced. The following related technologies are optional solutions and can be arbitrarily combined with the technical solutions of the embodiments of this application, all of which fall within the protection scope of the embodiments of this application. The embodiments of this application include at least some of the following contents.

[0055] AIoT

[0056] Artificial Intelligence of Things (AIoT) communication typically employs energy harvesting and backscatter communication technologies. AIoT devices are IoT devices powered by various environmental energy sources, such as radio frequency energy, light energy, solar energy, thermal energy, and mechanical energy. These devices may have no energy storage capacity or very limited energy storage capacity (e.g., using capacitors with a capacitance of tens of microfarads (µF)). Compared to traditional Internet of Things (IoT) devices, AIoT devices offer numerous advantages, including no need for conventional batteries, maintenance-free operation, small size, low complexity and low cost, and long lifespan.

[0057] In some scenarios, AIoT devices can also be referred to as zero-power devices.

[0058] An environmental Internet of Things (IoT) can include a network device 110 and an AIoT device 120, as shown in Figure 4. The network device is used to send wireless power signals and downlink communication signals to the AIoT device, and to receive backscattered signals from the AIoT device. A basic AIoT device includes an energy harvesting module, a backscattered communication module, and a low-power computing module. In addition, the AIoT device may also have a memory or sensor to store basic information (such as object identification) or acquire sensor data such as ambient temperature and humidity.

[0059] It should be noted that Figure 4 exemplarily illustrates a network device and an AIoT device. Optionally, the communication system 100 may include multiple network devices, and each network device may include other AIoT devices within its coverage area. This application embodiment does not limit this.

[0060] In addition, in some implementations, the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in this application embodiment.

[0061] It should be understood that the technical solutions of the embodiments of this application can be applied to various communication systems, such as: 5th generation (5G) systems or new radio (NR), long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, cellular IoT, etc. The technical solutions provided in this application can also be applied to future communication systems, such as 6th generation mobile communication systems, etc.

[0062] The AIoT device in this application embodiment can be a type of terminal device, which can also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal equipment, wireless communication device, user agent, or user device. The terminal device in this application embodiment can be a device that provides voice and / or data connectivity to the user, and can be used to connect people, objects, and machines, such as home appliances, sensors, electronic tags, etc., with wireless connectivity. The terminal in this application embodiment can be a wireless terminal in a smart home, a wireless terminal in an industrial wireless sensor network (IWSN), a wireless terminal in smart logistics and smart warehousing, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, etc.

[0063] The network device in this application embodiment can be a device for communicating with a terminal device. If the terminal is an electronic tag, the network device can be a reader / writer for reading and writing electronic tags (e.g., a reader / writer based on radio frequency identification (RFID) technology). An electronic tag is a passive or semi-active device, with typical applications including logistics, warehousing, industrial manufacturing, identification, and environmental monitoring. The network device can also be an access network device or a wireless access network device, such as a base station. In this application embodiment, the network device can refer to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master MeNB, secondary SeNB, multi-mode radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or similar, or a combination thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. Base stations can also be mobile switching centers, devices that perform base station functions in device-to-device (D2D), vehicle-to-everything (V2X), and machine-to-machine (M2M) communications, network-side devices in 6G networks, and devices that perform base station functions in future communication systems. Base stations can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.

[0064] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0065] In some deployments, the network device in this application embodiment may refer to a CU or a DU, or the network device may include both a CU and a DU. The gNB may also include an AAU.

[0066] Network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located.

[0067] It should be understood that all or part of the functions of the communication device in this application can also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (e.g., a cloud platform).

[0068] In some implementations, terminal 120 may include an energy harvesting module 121 and a backscatter communication module 122. The energy harvesting module 121 and the backscatter communication module 122 will be described below with reference to Figures 5 to 7; for brevity, they will not be elaborated upon here. In some cases, terminal 120 may also include a low-power computing module 123. The low-power computing module 123 provides computing functions for the terminal, such as data processing. In other cases, terminal 120 may also include a sensor 124 for collecting external information (e.g., ambient temperature, ambient humidity, etc.). In still other cases, terminal 120 may also include a memory 125 for storing information (e.g., external information collected by the aforementioned sensors, or such as object identification).

[0069] The energy harvesting module 121 described above is used to harvest energy. In some implementations, energy can be harvested via a wireless power supply signal sent by a network device. This wireless power supply signal can be a radio frequency (RF) signal sent by the network device; therefore, the energy harvesting module described above is also called an "RF energy harvesting module."

[0070] Figure 5 illustrates one possible structure of the energy harvesting module. As shown in Figure 5, the energy harvesting module 121 can harvest the energy of spatial electromagnetic waves from radio frequency signals based on the principle of electromagnetic induction, and store the harvested energy in capacitor C, which is the charging process of capacitor C. After the charging process of capacitor C is completed, capacitor C can begin to discharge to provide power for the terminal's operation. For example, the discharge of capacitor C can be used to drive the terminal to perform low-power demodulation of data sent by network devices. Another example is that the discharge of capacitor C can be used to drive the modulation of data to be transmitted by the terminal. Yet another example is that the discharge of capacitor C can be used to drive the terminal's sensors to perform data acquisition. And yet another example is that the discharge of capacitor C can be used to drive the terminal to read data from memory 125, etc.

[0071] The aforementioned backscatter communication module 122 is used for backscatter communication between the terminal and network devices. The principle of backscatter communication in this embodiment is described below with reference to Figure 6. Referring to Figure 6, the terminal 120 receives a wireless signal sent by the network device 110 and modulates the wireless signal to load the information to be transmitted. Finally, the modulated signal is radiated from the antenna; this information transmission process is called backscatter communication. Backscatter communication and load modulation are inseparable. Load modulation adjusts and controls the circuit parameters of the terminal's oscillation circuit according to the data stream's rhythm, causing parameters such as the terminal's impedance to change accordingly, thus completing the modulation process. Load modulation technology mainly includes two methods: resistive load modulation and capacitive load modulation. In resistive load modulation, a resistor is connected in parallel with the load. This resistor is switched on or off based on the control of the binary data stream, as shown in Figure 7. The switching on and off of the resistor causes a change in the circuit voltage, thus implementing amplitude-shift keying (ASK) modulation, that is, signal modulation and transmission are achieved by adjusting the amplitude of the terminal's backscatter signal. Similarly, in capacitive load modulation, the resonant frequency of the circuit can be changed by switching the capacitor on and off, thus realizing frequency-shift keying (FSK) modulation. That is, the modulation and transmission of the signal are achieved by adjusting the operating frequency of the backscattered signal of the terminal.

[0072] In some implementations, the network device 110 may also have other devices on its transmit (TX) path for processing the signal to be transmitted, such as an amplifier (AMP). Similarly, the network device 110 may have other devices on its receive (RX) path for processing the received signal, such as a low-noise amplifier (LNA).

[0073] In some implementations, terminal 120 may be equipped with an energy harvesting unit for harvesting energy from the wireless power supply signal sent by the network device. Of course, terminal 120 may also include a logic processing unit to perform corresponding calculation functions.

[0074] It should be noted that, whether it is network device 110 or terminal 120, Figure 6 only shows the connection structure of the signal processing circuit as an example. The processing circuit of network device 110 and / or terminal 120 may contain other components, and this application embodiment does not specifically limit this.

[0075] Typically, load modulation can be implemented using either resistive load modulation or capacitive load modulation. Figure 7 shows a circuit diagram of a terminal based on resistive load modulation technology. It should be noted that the circuit in Figure 7 implements load modulation in a manner similar to existing circuits for implementing load modulation. For simplicity, the functions of resistors R2 and R3, capacitors C1 and C2, and inductors L1 and L2 shown in Figure 7 will not be elaborated further.

[0076] In resistive load modulation, a resistor R can be connected in parallel with the load. L The switch S can be controlled based on binary data stream to achieve the resistor R. L The resistor R is switched on or off. L Switching the circuit on and off will cause changes in the circuit voltage, and the changes in the circuit voltage can control the amplitude of the backscattered signal of the terminal, thereby achieving modulation of the backscattered signal, that is, ASK modulation of the backscattered signal.

[0077] Similarly, in capacitive load modulation, the switching of the capacitor can be controlled based on the binary data stream to change the circuit resonant frequency, thereby changing the operating frequency of the backscattered signal to achieve FSK modulation.

[0078] As described above, the terminal can use load modulation to modulate the incoming signal (i.e., the signal sent by the network device), thereby realizing the backscatter communication process. Therefore, the terminal in backscatter communication typically has the following advantages.

[0079] One advantage is that since the terminal does not need to actively transmit signals, there is no need to construct a complex radio frequency (RF) path. For example, the RF path does not need to include power amplifiers (PAs) or RF filters, thus reducing the cost and size of the terminal.

[0080] The second advantage is that since the terminal does not need to actively generate high-frequency signals, it does not need a high-frequency crystal oscillator, thus reducing the cost and size of the terminal.

[0081] Thirdly, because the terminal can use backscatter technology to communicate with network devices, the terminal consumes less energy during communication, or even does not need to consume its own energy.

[0082] Classification of AIoT devices

[0083] In some scenarios, AIoT devices can be divided into three categories based on their energy source and energy usage: passive AIoT devices, semi-passive AIoT devices, and active AIoT devices.

[0084] I. Passive AIoT devices.

[0085] Passive AIoT devices typically do not require internal batteries. When an AIoT device approaches a network device, it falls within the near-field range of the network device's antenna radiation. At this point, the AIoT device's antenna can generate an induced current through electromagnetic induction. This induced current powers the AIoT device, enabling it to demodulate the received signal and / or modulate and encode the signal to be transmitted. In some implementations, the passive AIoT device can be an electronic tag, and correspondingly, the network device can be a reader / writer for a radio frequency identification (RFID) system, used to read and / or modify the content of the electronic tag.

[0086] II. Semi-passive AIoT devices.

[0087] Semi-passive AIoT devices do not have conventional batteries installed, but they can use an energy harvesting module 121 to harvest radio wave energy and store the harvested energy in an energy storage unit (such as a capacitor). After obtaining energy, the energy storage unit can power the AIoT device to demodulate the received signal and / or modulate and encode the signal to be transmitted.

[0088] III. Active AIoT Devices

[0089] Active AIoT devices can have built-in batteries. The battery powers the AIoT device to demodulate received signals and / or modulate and encode signals to be transmitted. However, when the AIoT device uses backscatter communication technology, it does not consume battery power. Therefore, for this type of AIoT device, "zero power consumption" is primarily reflected in scenarios where the terminal uses backscatter communication technology.

[0090] In some implementations, the aforementioned active AIoT device can be an electronic tag, and the network device can be an RFID reader. In this case, the built-in battery can power the RFID chip within the AIoT device, thereby increasing the read / write distance between the RFID reader and the electronic tag. On the other hand, the built-in battery can also power the RFID chip within the AIoT device, reducing the read / write latency of the RFID reader on the electronic tag and improving communication reliability.

[0091] In other scenarios, AIoT devices can be categorized into three types based on transmitter type: backscatter-based AIoT devices, active transmitter-based AIoT devices, and AIoT devices that combine both backscatter and active transmitters.

[0092] 1) AIoT devices based on backscattering.

[0093] These types of AIoT devices transmit uplink data using the backscatter method described above. These devices do not have an active transmitter for active transmission, but only a backscatter transmitter. Therefore, when these terminals transmit data, a network device needs to provide a carrier wave, and the terminal devices perform backscattering based on this carrier wave to achieve data transmission.

[0094] 2) AIoT devices based on active transmitters.

[0095] These types of AIoT devices use active transmitters with active transmission capabilities for uplink data transmission. Therefore, when sending data, these AIoT devices can use their own active transmitters to send data without requiring a carrier wave from network equipment. Suitable active transmitters for AIoT devices include, for example, ultra-low-power ASK or ultra-low-power FSK transmitters. Based on current implementations, these transmitters can reduce overall power consumption to 400–600 µW when transmitting a 100 µW signal.

[0096] 3) AIoT devices that simultaneously possess backscatter and active transmitter capabilities.

[0097] These terminals can support both backscatter and active transmitters. The terminal can determine which uplink signal transmission method to use based on different conditions (such as battery level and available ambient energy) or the scheduling of network devices: whether to use backscatter or active transmitter for active transmission.

[0098] Low-power IoT based on cellular networks

[0099] Cellular IoT is booming. For example, 3GPP has standardized IoT technologies such as narrowband Internet of Things (NB-IoT), machine-type communication (MTC), and reduced capability (RedCap). However, there are still many IoT communication needs in various scenarios that cannot be met by existing technologies. These include harsh communication environments (high temperature, extremely low temperature, high humidity, high pressure, high radiation, or high speed movement, etc.), the need for extremely small terminal form factors, and extremely low cost.

[0100] Therefore, in order to cover these unmet IoT communication needs, and to further make full use of the communication capabilities of wireless cellular networks to achieve the effect of interconnecting everything, it is also necessary to develop ultra-low cost, extremely small size, battery-free / maintenance-free IoT in cellular networks, and environmental IoT can meet this need.

[0101] Based on the discussion of AIoT application scenarios using the 3GPP system architecture (SA), AIoT can be used in at least the following four types of scenarios:

[0102] Scenario 1: Object recognition, such as logistics, production line product management, and supply chain management.

[0103] Scenario 2: Environmental monitoring, such as monitoring of temperature, humidity, and harmful gases in the work environment and natural environment.

[0104] Scenario 3: Location services, such as indoor location services, smart item search, and production line item location.

[0105] Scenario 4: Intelligent control, such as the intelligent control of various electrical appliances in smart homes (turning on and off air conditioners, adjusting temperature), and the intelligent control of various facilities in agricultural greenhouses (automatic irrigation, fertilization).

[0106] In low-power IoT based on cellular networks, AIoT devices can directly transmit and receive carrier waves, data, or signals from the base station, and send or backscatter data or channels to the base station, as shown in Figure 8 (denoted as the first topology). Alternatively, communication between the AIoT device and the base station can be achieved through an intermediate node. In this case, the intermediate node sends carrier waves, data, or signals to the AIoT device, the AIoT device sends or backscatters data or signals to the intermediate node, and the intermediate node sends the received data or signals to the base station, as shown in Figure 9 (denoted as the second topology).

[0107] As described above, passive AIoT devices do not require a built-in battery; they are equipped with only a small energy storage device that collects energy from the surrounding environment, such as sunlight, wind, and radio frequency signals, and stores it within the device. When communication is needed, they perform short-term, small-volume data transmissions with the network. To conserve power, passive AIoT devices receive paging messages during a pre-agreed paging period with the network, and compared to other UEs, the density of these paging periods in the time domain is lower than that of normal UEs. In this embodiment, energy can also be referred to as "electrical power" or "electrical energy."

[0108] Figure 10 shows the energy accumulation of AIoT devices. The horizontal axis represents time, and the vertical axis represents the energy storage level of the AIoT devices. In the initial state, the AIoT devices have no energy (0). Over time, the AIoT devices collect energy from the environment, i.e., they are charged using energy pulses. However, a small amount of energy leakage may occur during the charging process.

[0109] When an AIoT device has enough energy to receive data, it can receive downlink data; when it has enough energy to transmit data, it can transmit uplink data. As shown in Figure 10, the AIoT device requires the least energy to maintain its state (used to store data in a cache), the next most energy-intensive energy is required to receive downlink data, and the highest energy is required to transmit uplink data.

[0110] Traditional communication processes are designed for active terminal devices. Although power saving for terminal devices is considered in the design, even the most power-efficient NB-IoT in the current network has a much larger energy consumption than AIoT. Therefore, the communication process needs to be redesigned for AIoT devices.

[0111] Currently, AIoT devices include two types of memory. The first type is non-volatile memory (NVM), which consumes more power to write data, retains data even when power is off, but has a slow write speed. It is mainly used to store long-term, unchanging data, such as device identifiers. The second type is volatile memory (VM), which consumes less power to write data, loses data when power is off, and has a fast write speed. It is mainly used for temporary data storage. Considering the significant power consumption of writing data to non-volatile memory, AIoT devices currently do not frequently write data to it; that is, they do not write data to NVM constantly. It is worth noting that the aforementioned device identifier is defined by the service provider to facilitate the service provider's identification of AIoT devices.

[0112] Currently, it has been found that if power management is not fully performed before AIoT devices write data to NVM, the following behaviors may occur, as shown in Figure 11, where the horizontal axis represents time and the vertical axis represents power.

[0113] As shown in Figure 11(a), when the AIoT device has low power, if it receives a write data instruction from the network device at time T2, the AIoT device immediately starts writing data to the non-volatile memory. However, before the data is finished being written, the AIoT device loses power at time T3 because the power is exhausted.

[0114] As shown in Figure 11(b), when the AIoT device has low battery, if it receives a write data command from the network device at time T2, the AIoT device determines that its current battery level is insufficient to complete the data writing. Therefore, the AIoT device continues to store power until time T4, when it has sufficient stored power, at which point it begins writing data to the non-volatile memory, completing the entire data writing process at time T5. Alternatively, the AIoT device can continue collecting power at time T4, waiting until it has more stored power before starting to write data. While this method avoids the problem of running out of power, it introduces a delay in the AIoT device's data writing process. If the network device transmits the data using the identifier before time T5, errors may occur.

[0115] As shown in Figure 11(c), when the AIoT device has low battery, if it receives a write data command from the network device at time T2, it immediately begins writing data to the NVM. However, if the data writing is not completed by time T6 and a battery alarm sounds, the AIoT device pauses writing data to maintain a non-power-loss state. The AIoT device continues to collect power until time T7 when the stored power is sufficient to write the remaining data, at which point it resumes writing, completing the data writing process at time T8. Similar to the behavior shown in Figure 11(b), this scheme also requires a delay to complete the data writing process. Errors may also occur if the network device transmits the data using the identifier represented by the data before the data writing is complete.

[0116] To address the aforementioned issues, this application implements power management for AIoT devices to prevent power outages or delayed writes during NVM writing. The wireless communication method provided in this application primarily involves several distinct stages, each with different solutions. The wireless communication methods for the first and second stages can operate independently or in combination. It should be understood that the executing entities for the first and second stages can be the same or different; for example, the core network control node (such as AMF) acquires the capability information of the AIoT device, while the access network node (Reader) sends write commands and data to the AIoT device.

[0117] Phase 1: Acquiring AIoT device capability information;

[0118] The second stage involves sending write commands and data to the AIoT device. After receiving the write commands and data, the AIoT device writes the data to the NVM. The second node then transmits services to the AIoT device based on the aforementioned data.

[0119] The following sections will elaborate on this point in stages.

[0120] Phase 1

[0121] Figure 12 is a schematic flowchart of a wireless communication method according to an embodiment of this application. The method shown in Figure 12 includes steps S1210 and S1220.

[0122] In S1210, the first node sends first information, which is used to indicate the first node's ability to write data.

[0123] In some implementations, the first node can refer to an AIoT device, and the second node can refer to network devices such as base stations and LMFs.

[0124] In some embodiments, the first node and the second node may be relative. For example, a relay device may also be referred to as a terminal device relative to a network device. For example, a relay device may also be referred to as a network device relative to a terminal device.

[0125] In some implementations, the first information can also be called capability information. AIoT devices can send capability information through any of the following message types: MACCE, NAS layer message, or application layer message.

[0126] In some implementations, the capability information of an AIoT device includes at least one of the following: the size of the NVM, the size of the VM, the rate at which data is written to the NVM, the amount of electricity required to write a unit of data to the NVM; the energy storage speed; whether multiple writes to the NVM are supported; and whether writes to the NVM continue after a power outage.

[0127] Optionally, the capability information may also include at least one of the following: the maximum number of writes to the NVM supported, the maximum storage power, the minimum interval between sending write commands and data, or the amount of write data that can be supported when the storage power is at its maximum.

[0128] For example, the capability information of a smart door lock includes 40MB of NVM, 50KB of VM, a data writing rate of 50KB / s to NVM, a data consumption of 10 microjoules when writing 1 byte of data to NVM, and a charging current of 300mA.

[0129] In S1220, after receiving the first information, the second node synchronizes the first information to other nodes in the network device group.

[0130] In some possible implementations, the network device group has second nodes 1 to N, where N is a positive integer; the second node can be the second node 1 in the diagram, and the second node in the network device group can refer to one or more of the following nodes: AIoT server, core network node, base station, or reader.

[0131] For example, after receiving the capability information of an AIoT device, the reader notifies the base station, which in turn notifies the core network node, and the core network node notifies the AIoT server. It is worth noting that when transmitting AIoT device capability information between network-side nodes, all capability parameters can be transmitted, or only a subset of the capability parameters can be transmitted.

[0132] In some possible implementations, the capability information of an AIoT device, once reported, can be stored at one of the nodes on the network side. When the terminal reconnects to the network, it does not need to report the capability information again; the network-side nodes can retrieve it from the node that stores the capability information.

[0133] In other possible implementations, AIoT devices can report capability information periodically or in real time. For example, an AIoT device may proactively report capability information at set intervals.

[0134] In other possible implementations, AIoT devices can proactively report capability information when their physical environment changes. For example, when the location or light intensity of an AIoT device changes, it can proactively report capability information.

[0135] In some possible implementations, AIoT devices can also periodically report their current battery level.

[0136] It should be understood that in some other possible implementations, in addition to the capability information reported by the AIoT device, the second node can also obtain the capability information of the AIoT device through network management configuration or pre-configuration.

[0137] In addition, after the second node obtains the capability information of the AIoT device through network management configuration or pre-configuration, the second node synchronizes the information to other network-side nodes, or the network management system configures the capability information of the AIoT device to each network-side node, or directly pre-configures the capability information of the AIoT device to each network-side node.

[0138] Phase Two

[0139] Figure 13 is a schematic flowchart of a wireless communication method according to an embodiment of this application. The method shown in Figure 13 includes steps S1310 and S1320.

[0140] In S1310, the second node sends write commands and data to the first node.

[0141] In some implementations, the second node sends the write command and the data to the AIoT device via the same message or simultaneously; alternatively, the second node sends the write command and the data via different messages or sequentially. The second node can send the write command first, then the data, or vice versa.

[0142] In some implementations, when the write command and the written data are sent separately, the minimum interval between the two transmission times (GAP) is a set duration or falls within a set time interval. This minimum interval can be specified by the protocol or indicated by the network side.

[0143] In some implementations, after sending the write command, the second node can continue to send the data to be written only after receiving feedback information from the AIoT device, such as feedback information indicating that the AIoT device has sufficient power and can support writing all data.

[0144] In some implementations, after sending a write command, the second node can receive feedback information from the AIoT device, such as feedback indicating sufficient power and the ability to write some data, or support continuing to write data after a power outage.

[0145] In some implementations, after sending the write command, the second node can support writing all data after receiving feedback information from the AIoT device, such as feedback information indicating that the battery level has been waiting for T1 hours.

[0146] In some implementations, after sending the write command, the second node can write K bits of data after receiving feedback from the AIoT device, such as feedback indicating that the battery level has reached T2 hours later. T1 and T2 can be set according to actual needs. K is a positive integer.

[0147] In some implementations, after sending the write command, the second node starts a timer, and when the timer expires, it sends the data to be written to the AIoT device.

[0148] In some implementations, the logical channel ID (LCHID) used to write data can be a fixed value defined by the protocol or a value configured by the network side.

[0149] In some implementations, the write instruction may include at least one of the following:

[0150] a. The type of information to be written, such as all information or partial information.

[0151] b. The length of the information to be written, for example, in bits (Byte).

[0152] c. If the type of information written is partial information, then indicate the bytes corresponding to the partial information.

[0153] d. Write the starting address of the NVM within the AIoT.

[0154] e. Write the end address of the NVM within AIoT.

[0155] f. The time interval between the write command and the written data (GAP).

[0156] g. The time required for AIoT devices to complete writing data.

[0157] For example, the write completion time can be indicated by a set time elapsed since the write command was sent, or by a set time elapsed since the data was sent, or by a specific absolute time. For instance, the write command instructs the AIoT device to write data within 30 minutes, or to write data before 15:00:00 on February 14, 2025.

[0158] In S1320, the first node writes data.

[0159] In one possible implementation, after the AIoT device has completed writing all data, it can send a communication message to notify the second node that the data writing was successful. For example, the AIoT device can notify the second node of the writing completion via PUCCH, MACCE, NAS, or application-layer messages. Optionally, if the AIoT device has previously indicated sufficient battery power to the network side, it may not need to notify the network side of the writing completion.

[0160] In another possible implementation, if the AIoT device has not yet written all the data, but the AIoT device is not currently powered off, the AIoT device can notify the network to wait for a set period of time. Within the set period of time, the AIoT device can complete the writing of all the data. Alternatively, it can notify the network to pause the data writing process and resume writing after the set period of time. Or it can notify the network of the number of bits of the data already written and pause the writing process now.

[0161] In another possible implementation, if the AIoT device has not yet written all the data and its current battery level is low, the remaining "data to be written" stored in the VM will be lost due to power failure. Therefore, after the AIoT device is powered on again, it can notify the second node to resend the data. Upon receiving the notification, the second node will resend the data. For example, the second node can resend all the data to be written. As another example, if the AIoT device supports continuing to write to the NVM after a power failure, and the notification indicates the completed data portion, the second node can also only send the data that has not yet been written to the NVM.

[0162] In another possible implementation, if the AIoT device supports multiple writes to the NVM, the second node can split the large data block to be written into multiple sub-data blocks and use status flags to enable power-off continuation of writing, avoiding data loss due to full write failure. For example, after each sub-data block is received for writing, the AIoT device updates the status flags, such as the write progress and checksum. If the AIoT device experiences a power outage during data writing, it restarts and resumes writing the remaining sub-data blocks based on the status flags. For example, as shown in Figure 14, suppose the second node needs to write 100 bytes to the AIoT device. After writing 60 bytes, the AIoT device loses power. When the AIoT device powers on again, in one scenario, if the terminal supports power-off continuation of writing, only the remaining 40 bytes need to be written, which are then combined with the 60 bytes written before the power outage to form the total 100 bytes. In another scenario, if the AIoT device does not support power-off continuation of writing to the NVM, the 60 bytes need to be erased first, and then the entire 100 bytes need to be written.

[0163] In another possible implementation, if the AIoT device's capability information includes the power required to write a unit of data to the NVM (e.g., 5 joules for writing 1KB of data), and includes the speed of energy storage (e.g., the charging rate of solar / vibration energy), then the second node can establish an NVM writing energy consumption model based on this capability information. This allows it to determine or predict when the AIoT device's power supply is sufficient to write the data, and at that time, send the data so that the AIoT device can successfully write all the data.

[0164] In one possible implementation, the data sent by the second node is divided into high-priority and low-priority data portions. For example, the high-priority and low-priority data portions are indicated by bits within the data. After receiving the data, the AIoT device can prioritize writing to the high-priority data portion, followed by the low-priority data portion. The advantage of this implementation is that urgent tasks corresponding to the high-priority data portion are executed first, reducing the loss of critical data. This approach is primarily suitable for scenarios such as medical devices and security monitoring.

[0165] In S1330, the second node performs service transmission based on the data.

[0166] In some implementations, the AIoT device writes all the data and then notifies the second node, which then transmits the service based on that data.

[0167] In another possible implementation, the second node can build a model for NVM write energy consumption model based on the capability information of the AIoT device, thereby determining or predicting the end time when the AIoT device finishes writing all the data, and then perform business transmission based on the data after the end time to avoid errors.

[0168] In other implementations, the second node can wait a set amount of time before transmitting data based on it. That is, if the second node knows the AIoT device has enough power to complete writing all data, it assumes the AIoT device has finished writing after a certain period and can then transmit data based on that data. Otherwise, the second node waits until the AIoT device reports that all data has been written before using that data for transmission.

[0169] To facilitate understanding, the above method will be illustrated below with several examples shown in Figures 15 and 16.

[0170] Example 1, as shown in Figure 15, includes S1510 to S1530.

[0171] S1510, AIoT devices send capability information to the base station.

[0172] Optionally, the base station obtains the capability information of the AIoT device and synchronizes it to other nodes in the network device group, eliminating the need for the AIoT device to report repeatedly.

[0173] S1520, the base station sends write commands to AIoT devices through a reader / writer.

[0174] The reader / writer is a Reader terminal that executes the Reader function after being verified by the network side. It can write data to AIoT devices within a certain coverage area and interact with AIoT devices.

[0175] S1530, the AIoT device sends feedback information to the base station.

[0176] Feedback messages sent by AIoT devices can indicate that the AIoT device is ready to write data, or they can indicate one of the following:

[0177] A. The current battery level of the AIoT device can support the amount of data that can be written.

[0178] For example, the network side may want to write a total of 100 bytes of data, but the current battery power of the AIoT device can only support writing 60 bytes of data. The AIoT device then sends 60 bytes of data back to the base station.

[0179] B. The estimated battery power is sufficient to support the charging time required to write all the data. In other words, after the set time, the battery power of the AIoT device will be sufficient to support the writing of all the data.

[0180] For example, the network side wants to write 100 bytes of data, but the terminal's current battery level only supports writing 60 bytes. The AIoT device reports to the base station: "In one hour, the collected battery level will be sufficient to write 100 bytes of data." Upon receiving this feedback, the base station can choose to send the "write data" message after a gap period, or it can choose to send it one hour later. This depends on whether the UE supports multiple data writes. If the UE supports this, the base station can wait one hour before sending the data; otherwise, it will choose to wait one hour.

[0181] C. The predicted timeframe for AIoT devices to write all the data.

[0182] S1540, the base station sends the data to be written to the AIoT device.

[0183] S1550: After receiving data, the AIoT device writes the data to the NVM.

[0184] S1560: After completing all the data, the AIoT device sends a notification to the base station.

[0185] S1570, the second node performs service transmission based on the data.

[0186] Example 2, as shown in Figure 16, includes S1610 to S1630.

[0187] S1610, the AIoT device sends capability information to the base station, which includes the size of the NVM, the size of the VM, the rate at which data is written to the NVM, the power required to write a unit of data to the NVM, and the energy storage speed.

[0188] S1620: After receiving the capability information, the base station establishes an NVM write energy consumption model. Based on the NVM write energy consumption model and the data to be written, the base station predicts the power consumption change curve of the AIoT device, thereby predicting the completion time of writing all the data to be written.

[0189] S1630, the base station sends a write command to the AIoT device, and sends the data to be written to the AIoT device.

[0190] S1640: After receiving the data, the AIoT device writes the data to the NVM.

[0191] In this step, when the AIoT device receives a write command, it can dynamically determine whether to execute immediately, delay execution, or write in segments based on the current real-time power E_remaining, the NVM write energy consumption model, and the environmental energy harvesting rate. If E_remaining is greater than or equal to the energy required for writing, the AIoT device immediately executes a full write; otherwise, it enters a waiting mode and delays data writing. During the waiting process, the AIoT device continuously harvests energy and dynamically updates the threshold for initiating data writing. For example, writing is initiated when E_remaining + expected harvested energy ≥ a safety threshold. It is worth noting that the safety threshold setting can introduce a redundancy coefficient (such as 1.2 times the theoretical energy consumption) to avoid write interruptions due to environmental energy fluctuations. Optionally, the AIoT device can also write the data to be written within a time window determined by the NVM write energy consumption model.

[0192] S1650, after the predicted write completion time, the base station performs service transmission based on the data.

[0193] In summary, the above implementation method can fully consider the power consumption of AIoT devices during the data writing process, avoid situations such as data writing failure or incomplete data writing, and use the data for business transmission to avoid errors, ensure that AIoT devices can work normally, and improve transmission performance.

[0194] The method embodiments of this application have been described in detail above with reference to Figures 1 to 16. The apparatus embodiments of this application will be described in detail below with reference to Figures 17 to 20. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments; therefore, any parts not described in detail can be referred to the preceding method embodiments.

[0195] Figure 17 illustrates a first node for wireless communication provided in an embodiment of this application. The first node can be a terminal device or a network device. As shown in Figure 17, the first node 1700 includes a first transceiver module 1710 and a first processing module 1720.

[0196] The first transceiver module 1710 is used to send first information, which indicates the ability of the first node to write data; and to receive write instructions and data.

[0197] The first processing module 1720 is used to write the data according to the write instruction.

[0198] In some possible embodiments, the first information includes at least one of the following:

[0199] The size of the non-volatile memory (NVM);

[0200] The size of the volatile memory VM;

[0201] The rate at which data is written to the NVM;

[0202] The amount of electricity required to write a unit of data to the NVM;

[0203] The speed of energy storage;

[0204] Does it support multiple writes to NVM?

[0205] Does it support continuing to write to NVM after a power outage?

[0206] The maximum number of times NVM can be written to is supported.

[0207] The maximum amount of electricity that can be stored;

[0208] Minimum interval between sending write commands and sending data;

[0209] The maximum amount of data that can be written when the storage battery is at its maximum capacity.

[0210] In some possible embodiments, the write instruction includes at least one of the following:

[0211] The type of information being written;

[0212] Length of the information written;

[0213] When the type of information written is partial information, the bytes corresponding to the partial information are;

[0214] Write to the starting address of NVM;

[0215] Write to the end address of NVM;

[0216] The time interval between the write command and the written data;

[0217] The duration of writing all data;

[0218] Priority of writing data.

[0219] In some possible embodiments, the first transceiver module 1710 is further configured to: send notification information, the notification information being used to notify whether all or part of the data has been successfully written.

[0220] In some possible embodiments, the first transceiver module 1710 is further configured to: send feedback information, the feedback information being used to notify the first node of its power status.

[0221] In some possible embodiments, the feedback information includes at least one of the following: the current battery level can support the size of the data to be written; the estimated charging time required to support writing all the data; and the estimated time to write all the data.

[0222] In some possible embodiments, when the first processing module 1720 writes the data according to the write instruction, it is specifically used for:

[0223] Based on the priority of the data to be written in the write instruction, the high-priority data portion is written first, followed by the low-priority data portion.

[0224] In some possible embodiments, when the first processing module 1720 writes the data according to the write instruction, it is specifically used for:

[0225] When the power is insufficient, the data is written with a delay until the energy storage capacity is sufficient to support the writing of all data, at which point the data is written.

[0226] As one embodiment, the first transceiver module 1710 can be a transceiver 1930, and the first processing module 1720 can be a processor 1910. The first node 1700 may also include a memory 1920, as shown in Figure 19.

[0227] Figure 18 illustrates a second node for wireless communication provided in an embodiment of this application. The second node can be a network-side device or entity used for positioning, such as a base station. As shown in Figure 18, the second node 1800 includes a second transceiver module 1810 and a second processing module 1820.

[0228] The second transceiver module 1810 is also used to acquire the capability information of the first node, the capability information being used to indicate the first node's ability to write data; and to send write commands and data.

[0229] The second transceiver module 1810 is also used for service transmission based on the data.

[0230] In some possible embodiments, the first information includes at least one of the following:

[0231] The size of the non-volatile memory (NVM);

[0232] The size of the volatile memory VM;

[0233] The rate at which data is written to the NVM;

[0234] The amount of electricity required to write a unit of data to the NVM;

[0235] The speed of energy storage;

[0236] Does it support multiple writes to NVM?

[0237] Does it support continuing to write to NVM after a power outage?

[0238] The maximum number of times NVM can be written to is supported.

[0239] The maximum amount of electricity that can be stored;

[0240] Minimum interval between sending write commands and sending data;

[0241] The maximum amount of data that can be written when the storage battery is at its maximum capacity.

[0242] In some possible embodiments, the write instruction includes at least one of the following:

[0243] The type of information being written;

[0244] Length of the information written;

[0245] When the type of information written is partial information, the bytes corresponding to the partial information are;

[0246] Write to the starting address of NVM;

[0247] Write to the end address of NVM;

[0248] The time interval between the write command and the written data;

[0249] The duration of writing all data;

[0250] Priority of writing data.

[0251] In some possible embodiments, the second transceiver module 1810 is further configured to: receive notification information, the notification information being used to notify whether all or part of the data has been successfully written.

[0252] In some possible embodiments, the second transceiver module 1810 is further configured to: receive feedback information, the feedback information being used to notify the first node of its power status.

[0253] In some possible embodiments, the feedback information includes at least one of the following: the current battery level can support the size of the data that can be written;

[0254] The estimated charging time required to write all the data is expected; the estimated time required to write all the data is also expected.

[0255] In some possible embodiments, the second processing module 1820 is further configured to: establish an NVM write power consumption model based on the information; and determine, based on the NVM write power consumption model, when the power consumption of the first node is sufficient to write the data.

[0256] When the second transceiver module sends write instructions and data, it is specifically used to: send the write instructions and data at the specified timing.

[0257] In some possible embodiments, the second processing module 1820 is further configured to: establish an NVM write energy consumption model based on the information; determine, based on the NVM write energy consumption model, the power consumption of the first node meets the end time of writing all the data; and after the end time, perform service transmission based on the data.

[0258] As one embodiment, the second transceiver module 1810 can be a transceiver 1930, and the second processing module 1820 can be a processor 1910. The second node 1800 may also include a memory 1920, as shown in Figure 19.

[0259] Figure 19 is a schematic structural diagram of a communication device according to an embodiment of this application. The dashed lines in Figure 19 indicate that the unit or module is optional. This device 1900 can be used to implement the methods described in the above method embodiments. Device 1900 can be a chip, user equipment, or network device.

[0260] Apparatus 1900 may include one or more processors 1910. The processor 1910 may support apparatus 1900 in implementing the methods described in the preceding method embodiments. The processor 1910 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0261] The apparatus 1900 may further include one or more memories 1920. The memories 1920 store a program that can be executed by the processor 1910, causing the processor 1910 to perform the methods described in the preceding method embodiments. The memories 1920 may be independent of the processor 1910 or integrated within the processor 1910.

[0262] The device 1900 may also include a transceiver 1930. The processor 1910 can communicate with other devices or chips via the transceiver 1930. For example, the processor 1910 can send and receive data with other devices or chips via the transceiver 1930.

[0263] Figure 20 is a schematic diagram of the hardware modules of the communication device provided in this application embodiment. Specifically, Figure 20 shows a block diagram of a first communication device 2050 and a second communication device 2010 communicating with each other in the access network.

[0264] The first communication device 2050 includes a controller / processor 2059, a memory 2060, a data source 2067, a transmitting processor 2068, a receiving processor 2056, a multi-antenna transmitting processor 2057, a multi-antenna receiving processor 2058, a transmitter / receiver 2054, and an antenna 2052.

[0265] The second communication device 2010 includes a controller / processor 2075, a memory 2076, a data source 2077, a receiver processor 2070, a transmitter processor 2016, a multi-antenna receiver processor 2072, a multi-antenna transmitter processor 2071, a transmitter / receiver 2018, and an antenna 2020.

[0266] In the transmission from the second communication device 2010 to the first communication device 2050, upper-layer data packets from the core network or from the data source 2077 are provided to the controller / processor 2075 at the second communication device 2010. The core network and data source 2077 represent all protocol layers above the L2 layer. The controller / processor 2075 implements the functionality of the L2 layer. In the transmission from the second communication device 2010 to the first communication device 2050, the controller / processor 2075 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation for the first communication device 2050 based on various priority metrics. The controller / processor 2075 is also responsible for retransmitting lost packets and signaling to the first communication device 2050. The transmit processor 2016 and the multi-antenna transmit processor 2071 implement various signal processing functions for the L1 layer (i.e., the physical layer). Transmit processor 2016 performs encoding and interleaving to facilitate forward error correction at the second communication device 2010, and mapping of signal clusters based on various modulation schemes (e.g., binary phase shift keying, quadrature phase shift keying, M-phase shift keying, M-quadrature amplitude modulation). Multi-antenna transmit processor 2071 performs digital spatial precoding on the encoded and modulated symbols, including codebook-based precoding and non-codebook-based precoding, and beamforming processing, generating one or more spatial streams. Transmit processor 2016 then maps each spatial stream to subcarriers, multiplexes it with a reference signal (e.g., a pilot) in the time and / or frequency domains, and subsequently uses inverse fast Fourier transform to generate a physical channel carrying the time-domain multicarrier symbol stream. Multi-antenna transmit processor 2071 then performs transmit analog precoding / beamforming operations on the time-domain multicarrier symbol stream. Each transmitter 2018 converts the baseband multicarrier symbol stream provided by the multi-antenna transmit processor 2071 into an radio frequency stream, which is then provided to different antennas 2020.

[0267] In the transmission from the second communication device 2010 to the first communication device 2050, at the first communication device 2050, each receiver 2054 receives signals through its corresponding antenna 2052. Each receiver 2054 recovers the information modulated onto the radio frequency carrier and converts the radio frequency stream into a baseband multicarrier symbol stream, which is then provided to the receiver processor 2056. The receiver processor 2056 and the multi-antenna receiver processor 2058 implement various signal processing functions of Layer 1. The multi-antenna receiver processor 2058 performs receive analog precoding / beamforming operations on the baseband multicarrier symbol stream from the receiver 2054. The receiver processor 2056 uses a fast Fourier transform to convert the baseband multicarrier symbol stream after the receive analog precoding / beamforming operations from the time domain to the frequency domain. In the frequency domain, the physical layer data signal and the reference signal are demultiplexed by the receiver processor 2056, where the reference signal is used for channel estimation, and the data signal is recovered in the multi-antenna receiver processor 2058 after multi-antenna detection to recover any spatial stream destined for the first communication device 2050. Symbols on each spatial stream are demodulated and recovered in the receive processor 2056, generating soft decisions. The receive processor 2056 then decodes and deinterleaves the soft decisions to recover the upper-layer data and control signals transmitted by the second communication device 2010 over the physical channel. The upper-layer data and control signals are then provided to the controller / processor 2059. The controller / processor 2059 implements the functions of Layer 2 (L2). The controller / processor 2059 may be associated with a memory 2060 storing program code and data. The memory 2060 may be referred to as computer-readable media. In the transmission from the second communication device 2010 to the first communication device 2050, the controller / processor 2059 provides multiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport and logical channels to recover the upper-layer data packets from the second communication device 2010. The upper-layer data packets are then provided to all protocol layers above Layer 2. Various control signals may also be provided to Layer 3 (L3) for L3 processing.

[0268] In the transmission from the first communication device 2050 to the second communication device 2010, at the first communication device 2050, upper-layer data packets are provided to the controller / processor 2059 using a data source 2067. The data source 2067 represents all protocol layers above the L2 layer. Similar to the transmission functions at the second communication device 2010 described in the transmission from the second communication device 2010 to the first communication device 2050, the controller / processor 2059 implements header compression, encryption, packet segmentation and reordering, and multiplexing between logic and transport channels, implementing L2 layer functions for the user plane and control plane. The controller / processor 2059 is also responsible for retransmitting lost packets and signaling to the second communication device 2010. Transmit processor 2068 performs modulation mapping and channel coding processing, while multi-antenna transmit processor 2057 performs digital multi-antenna spatial precoding, including codebook-based and non-codebook-based precoding, and beamforming processing. Subsequently, transmit processor 2068 modulates the generated spatial stream into a multi-carrier / single-carrier symbol stream. After analog precoding / beamforming operations in multi-antenna transmit processor 2057, the stream is provided to different antennas 2052 via transmitter 2054. Each transmitter 2054 first converts the baseband symbol stream provided by multi-antenna transmit processor 2057 into a radio frequency symbol stream before providing it to antenna 2052.

[0269] In the transmission from the first communication device 2050 to the second communication device 2010, the function at the second communication device 2010 is similar to the receiving function at the first communication device 2050 described in the transmission from the second communication device 2010 to the first communication device 2050. Each receiver 2018 receives radio frequency signals through its corresponding antenna 2020, converts the received radio frequency signals into baseband signals, and provides the baseband signals to the multi-antenna receiving processor 2072 and the receiving processor 2070. The receiving processor 2070 and the multi-antenna receiving processor 2072 jointly implement the L1 layer function. The controller / processor 2075 implements the L2 layer function. The controller / processor 2075 may be associated with a memory 2076 that stores program code and data. The memory 2076 may be referred to as computer-readable media. In the transmission from the first communication device 2050 to the second communication device 2010, the controller / processor 2075 provides multiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transmission and logical channels to recover the upper-layer data packets from the first communication device 2050. The upper-layer data packets from the controller / processor 2075 can be provided to the core network or all protocol layers above Layer 2, and various control signals can also be provided to the core network or Layer 3 for Layer 3 processing.

[0270] As one embodiment, the first communication device 2050 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used with the at least one processor.

[0271] As one embodiment, the first communication device 2050 includes: a memory storing a computer-readable instruction program that produces action when executed by at least one processor.

[0272] As an example, the first communication device 2050 corresponds to the first node in this application.

[0273] As an example, the second communication device 2010 corresponds to the second node in this application.

[0274] As one embodiment, the first communication device 2050 is a user equipment that can act as a relay node.

[0275] As one embodiment, the first communication device 2050 is a network control relay (NCR).

[0276] As one embodiment, the first communication device 2050 is a relay wireless repeater.

[0277] As one embodiment, the first communication device 2050 is a relay.

[0278] As one embodiment, the second communication device 2010 is a Location Management Function (LMF).

[0279] As an example, the first communication device 2050 corresponds to the first node in this application, and the controller / processor 1159 is used to execute the above method.

[0280] This application also provides a computer-readable storage medium for storing a program. This computer-readable storage medium can be applied to a terminal or network device provided in this application, and the program causes a computer to execute the methods performed by the terminal device, network device, or core network entity in various embodiments of this application.

[0281] This application also provides a computer program product. The computer program product includes a program. This computer program product can be applied to a terminal or network device provided in this application embodiment, and the program causes a computer to execute the methods performed by the terminal device, network device, or core network entity in various embodiments of this application.

[0282] This application also provides a computer program. This computer program can be applied to the terminal or network device provided in this application, and the computer program causes the computer to execute the methods performed by the terminal device, network device, or core network entity in the various embodiments of this application.

[0283] It should be understood that the terms "system" and "network" in this application can be used interchangeably. Furthermore, the terminology used in this application is only for explaining specific embodiments of the application and is not intended to limit the application. The terms "first," "second," "third," and "fourth," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. In addition, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.

[0284] In the embodiments of this application, the term "instruction" can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0285] In the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0286] In the embodiments of this application, the term "correspondence" can indicate a direct or indirect correspondence between two things, or an association between two things, or a relationship such as instruction and being instructed, configuration and being configured.

[0287] In this application embodiment, "predefined" or "preconfigured" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including user equipment and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0288] In this application embodiment, the "protocol" may refer to a standard protocol in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems. This application does not limit this.

[0289] In the embodiments of this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0290] In the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0291] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0292] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0293] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0294] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can read or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs, DVDs) or semiconductor media (e.g., solid-state disks, SSDs), etc.

[0295] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for a first node in wireless communication, characterized in that, The method includes: Send the first message, which indicates the first node's ability to write data; Receive write commands and data; The data is written according to the write instruction.

2. The method according to claim 1, characterized in that, The first information includes at least one of the following: The size of the non-volatile memory (NVM); The size of the volatile memory VM; The rate at which data is written to the NVM; The amount of electricity required to write a unit of data to the NVM; The speed of energy storage; Does it support multiple writes to NVM? Does it support continuing to write to NVM after a power outage? The maximum number of times NVM can be written to; The maximum amount of electricity that can be stored; Minimum interval between sending write commands and sending data; The maximum amount of data that can be written when the storage battery is at its maximum capacity.

3. The method according to claim 1 or 2, characterized in that, The write instruction includes at least one of the following: The type of information being written; Length of the information written; When the type of information written is partial information, the bytes corresponding to the partial information are; Write to the starting address of NVM; Write to the end address of NVM; The time interval between the write command and the written data; The duration of writing all data; Priority of writing data.

4. The method according to any one of claims 1 to 3, characterized in that, Also includes: Send a notification message, which is used to notify whether all or part of the data has been successfully written.

5. The method according to any one of claims 1 to 4, characterized in that, Also includes: Send feedback information, which is used to notify the first node of its battery status.

6. The method according to claim 5, characterized in that, The feedback information includes at least one of the following: The current battery level allows for the size of data that can be written. The battery capacity is expected to support the charging time required to write all the data; Estimated time required to write all the data.

7. The method according to any one of claims 1 to 6, characterized in that, According to the write instruction, the data is written, including: Based on the priority of the data to be written in the write instruction, the high-priority data portion is written first, followed by the low-priority data portion.

8. The method according to any one of claims 1 to 6, characterized in that, According to the write instruction, the data is written, including: When the power is insufficient, the data is written with a delay until the energy storage capacity is sufficient to support the writing of all data, at which point the data is written.

9. A method for a second node in wireless communication, characterized in that, include: Obtain the capability information of the first node, which indicates the first node's ability to write data; Send write commands and data; Service transmission is performed based on the data.

10. The method according to claim 9, characterized in that, The capability information of the first node includes at least one of the following: The size of the non-volatile memory (NVM); The size of the volatile memory VM; The rate at which data is written to the NVM; The amount of electricity required to write a unit of data to the NVM; The speed of energy storage; Does it support multiple writes to NVM? Does it support continuing to write to NVM after a power outage? The maximum number of times NVM can be written to; The maximum amount of electricity that can be stored; Minimum interval between sending write commands and sending data; The maximum amount of data that can be written when the storage battery is at its maximum capacity.

11. The method according to claim 9 or 10, characterized in that, The write instruction includes at least one of the following: The type of information being written; Length of the information written; When the type of information written is partial information, the bytes corresponding to the partial information are; Write to the starting address of NVM; Write to the end address of NVM; The time interval between the write command and the written data; The duration of writing all data; Priority of writing data.

12. The method according to claim 9 or 10, characterized in that, Also includes: Receive notification information, which is used to notify whether the data has been written successfully.

13. The method according to any one of claims 9 to 12, characterized in that, Also includes: Receive feedback information, which is used to notify the first node of its battery status.

14. The method according to claim 13, characterized in that, The feedback information includes at least one of the following: The current battery level allows for the size of data that can be written. The battery capacity is expected to support the charging time required to write all the data; Estimated time required to write all the data.

15. The method according to any one of claims 9 to 14, characterized in that, Also includes: Based on the information provided, an NVM write energy consumption model is established. Based on the NVM write energy consumption model, determine when the power consumption of the first node is sufficient to write the data. The sending of write instructions and data includes: sending the write instructions and data at the specified timing.

16. The method according to any one of claims 9 to 14, characterized in that, Also includes: Based on the information provided, an NVM write energy consumption model is established. Based on the NVM write energy consumption model, it is determined that the power consumption of the first node satisfies the end time of writing all the data; After this end time, service transmission is performed based on the data.

17. A first node for wireless communication, characterized in that, include: The first transceiver module is used to send first information, which indicates the first node's ability to write data; and to receive write commands and data. The first processing module is used to write the data according to the write instruction.

18. The first node according to claim 17, characterized in that, The first information includes at least one of the following: The size of the non-volatile memory (NVM); The size of the volatile memory VM; The rate at which data is written to the NVM; The amount of electricity required to write a unit of data to the NVM; The speed of energy storage; Does it support multiple writes to NVM? Does it support continuing to write to NVM after a power outage? The maximum number of times NVM can be written to; The maximum amount of electricity that can be stored; Minimum interval between sending write commands and sending data; The maximum amount of data that can be written when the storage battery is at its maximum capacity.

19. The first node according to claim 17 or 18, characterized in that, The write instruction includes at least one of the following: The type of information being written; Length of the information written; When the type of information written is partial information, the bytes corresponding to the partial information are; Write to the starting address of NVM; Write to the end address of NVM; The time interval between the write command and the written data; The duration of writing all data; Priority of writing data.

20. The first node according to any one of claims 17 to 19, characterized in that, The first transceiver module is also used for: Send a notification message, which is used to notify whether all or part of the data has been successfully written.

21. The first node according to any one of claims 17 to 20, characterized in that, The first transceiver module is also used for: Send feedback information, which is used to notify the first node of its battery status.

22. The first node according to claim 21, characterized in that, The feedback information includes at least one of the following: The current battery level allows for the size of data that can be written. The battery capacity is expected to support the charging time required to write all the data; Estimated time required to write all the data.

23. The first node according to any one of claims 17 to 22, characterized in that, When the first processing module writes the data according to the write instruction, it is specifically used for: Based on the priority of the data to be written in the write instruction, the high-priority data portion is written first, followed by the low-priority data portion.

24. The first node according to any one of claims 17 to 22, characterized in that, When the first processing module writes the data according to the write instruction, it is specifically used for: When the power is insufficient, the data is written with a delay until the energy storage capacity is sufficient to support the writing of all data, at which point the data is written.

25. A second node for wireless communication, characterized in that, include: The second transceiver module is used to obtain the capability information of the first node, and the capability information is used to indicate the first node's ability to write data. Send write commands and data; The second processing module is used for service transmission based on the data.

26. The second node according to claim 25, characterized in that, The capability information of the first node includes at least one of the following: The size of the non-volatile memory (NVM); The size of the volatile memory VM; The rate at which data is written to the NVM; The amount of electricity required to write a unit of data to the NVM; The speed of energy storage; Does it support multiple writes to NVM? Does it support continuing to write to NVM after a power outage? The maximum number of times NVM can be written to; The maximum amount of electricity that can be stored; Minimum interval between sending write commands and sending data; The maximum amount of data that can be written when the storage battery is at its maximum capacity.

27. The second node according to claim 25 or 26, characterized in that, The write instruction includes at least one of the following: The type of information being written; Length of the information written; When the type of information written is partial information, the bytes corresponding to the partial information are; Write to the starting address of NVM; Write to the end address of NVM; The time interval between the write command and the written data; The duration of writing all data; Priority of writing data.

28. The second node according to claim 25 or 26, characterized in that, The second transceiver module is also used for: Receive notification information, which is used to notify whether the data has been written successfully.

29. The second node according to any one of claims 25 to 28, characterized in that, The second transceiver module is also used for: Receive feedback information, which is used to notify the first node of its battery status.

30. The second node according to claim 29, characterized in that, The feedback information includes at least one of the following: The current battery level allows for the size of data that can be written. The battery capacity is expected to support the charging time required to write all the data; Estimated time required to write all the data.

31. The second node according to any one of claims 25 to 30, characterized in that, The second processing module is further configured to: establish an NVM write energy consumption model based on the information; and determine, based on the NVM write energy consumption model, when the power consumption of the first node is sufficient to write the data. When the second transceiver module sends write instructions and data, it is specifically used to: send the write instructions and data at the specified timing.

32. The second node according to any one of claims 25 to 31, characterized in that, The second processing module is also used for: Based on the information provided, an NVM write energy consumption model is established. Based on the NVM write energy consumption model, it is determined that the power consumption of the first node satisfies the end time of writing all the data; After this end time, service transmission is performed based on the data.

33. A node used for wireless communication, characterized in that, It includes a transceiver, a memory, and a processor, wherein the memory is used to store a program, the processor is used to invoke the program in the memory, and to control the transceiver to receive or send signals so that the node performs the method as described in any one of claims 1-8 or 9-16.

34. A communication device, characterized in that, Includes a processor for calling a program from memory to cause the device to perform the method as described in any one of claims 1-8 or 9-16.

35. A chip, characterized in that, Includes a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1-8 or 9-16.

36. A computer-readable storage medium, characterized in that, It contains a program that causes a computer to perform the method as described in any one of claims 1-8 or 9-16.

37. A computer program product, characterized in that, Includes a program that causes a computer to perform the method as described in any one of claims 1-8 or 9-16.

38. A computer program, characterized in that, The computer program causes the computer to perform the method as described in any one of claims 1-8 or 9-16.

Images