Method and apparatus for facilitating network registration of low power devices

Abstract

A method for performing registration in a low-power device (LPD) to a wireless network, the method comprising: broadcasting (705) a first uplink UL message indicating a registration request, the message including the ID of the LPD in the wireless network; receiving (710) an acknowledgment from at least one communication node, the acknowledgment including the node ID of the communication node that received the first UL message; and determining (715) an initial network topology based on the acknowledgment.

Description

Technical Field

[0001] This disclosure relates to wireless communication between a wireless device and a wireless network. Specifically, a solution is provided for triggering network registration of a wireless device, particularly a low-power device, such as a passive wireless device configured to transmit in response to receiving radio frequency energy. Background Technology

[0002] The various protocols and technical requirements for wireless communication have been standardized under the supervision of organizations such as the 3rd Generation Partnership Project (3GPP). Continuous improvement and further development result in new or modified functions and features being implemented in successive versions of the technical specifications that provide the framework for wireless communication.

[0003] Wireless communication can occur between wireless networks and wireless devices in various scenarios. A wireless network typically comprises an access network containing multiple access nodes, historically known as base stations. In 5G radio access networks, such base stations may be called gNBs. Each access node can be configured to serve one or more cells of the cellular wireless network. Various different types of wireless devices can be configured to communicate with the access network, and these devices are typically called user equipment (UEs). Communication involving transmission from the UE and reception in the wireless network is typically referred to as uplink (UL) communication, while communication involving transmission from the wireless network and reception in the UE is typically referred to as downlink (DL) communication.

[0004] Each UE requires power in some way to communicate with the wireless network. Regardless of the UE's capabilities, energy efficiency is a relevant factor to consider. A notable development in the evolution of specifications providing regulations and guidance for wireless communications is the implementation of more types of UEs, including less complex UEs, and associated regulations that may simplify or relax communication configurations for these less complex UEs. This can be seen as part of the evolution towards an Internet of Things (IoT) environment, where a large number of connectable UEs and UE types are conceivable, some of which may be configured only for simple communication tasks, such as occasionally reporting measurements of specific parameters such as radio signal measurements, location, and sensor outputs. One UE type to consider is the Ambient IoT device. According to 3GPP TR 22.840 Release 2.2.0 (2023-12), an Ambient IoT device is an environmentally powered IoT device that is powered by energy harvesting and is either battery-free or has limited energy storage capacity (e.g., using capacitors).

[0005] For at least some types, such UEs (e.g., environmental IoT devices) may be expected to be able to operate for very long periods without requiring battery charging or replacement, especially for UE types configured to have long periods of inactivity between sparse and brief communication instances. However, for such UEs, signaling according to the traditional procedures used to complete network registration may be challenging or even impossible in many cases. Summary of the Invention

[0006] In view of the above, the object of the present invention is to provide a solution for processing UEs in a wireless network, the solution being configured to facilitate network registration of UEs operating under power and / or processing constraints. One aspect of the invention aims to provide a solution that facilitates the registration of passive type UEs (such as environmental IoT devices) that can be configured to perform UL transmissions only in response to DL reception.

[0007] The proposed solution is set forth in the independent claims, while various examples thereof are set forth in the dependent claims and in the following detailed description. Attached Figure Description

[0008] Figure 1 The diagram illustrates an implementation of a wireless communication system in which the UE communicates with the wireless network via radio communication with a communication node.

[0009] Figure 2 A communication node in the form of an access node for a wireless network is schematically illustrated, configured to operate according to the proposed solution as described herein.

[0010] Figure 3A The illustrations illustrate the general characteristics of a UE configured to operate with a wireless network according to various examples.

[0011] Figure 3B It shows according to Figure 3A Examples of specific types of passive UEs, which are configured to operate as low-power devices by harvesting radio frequency energy from received radio signals and to process and transmit in the uplink via reflective bearers.

[0012] Figure 4 Various examples of network topologies are provided, which can be identified and indicated in the examples of the proposed solutions.

[0013] Figure 5A The signaling diagram associated with the proposed solution in a network-based or network-centric configuration is shown.

[0014] Figure 5BSignaling diagrams associated with device-based or device-centric configurations of the proposed solution are shown.

[0015] Figure 6 The resource configuration for at least UE transmission is illustrated schematically, and this resource configuration is useful in various examples of the proposed solution.

[0016] Figure 7 Flowcharts are provided illustrating methods for implementation in low-power devices based on various examples of the proposed solutions.

[0017] Figure 8A Flowcharts are provided illustrating methods executed in access nodes based on various network-based examples of the proposed solution.

[0018] Figure 8B Flowcharts are provided illustrating methods executed in an access node based on various device-based examples of the proposed solution.

[0019] Figure 9 Flowcharts are provided illustrating methods performed in a wireless communication node acting as an auxiliary node, based on various network-based examples of the proposed solution. Detailed Implementation

[0020] In the following description, details relating to various examples are set forth for purposes of explanation and not limitation. However, it will be apparent to those skilled in the art that the invention may be practiced in other examples that depart from these specific details. In some instances, detailed descriptions of well-known apparatuses, circuits, and methods have been omitted so as not to obscure the description of the invention with unnecessary detail. The functionality of various elements comprising functional blocks (including, but not limited to, functional blocks labeled or described as “computer,” “processor,” or “controller”) can be provided using hardware such as circuit hardware and / or hardware capable of executing software stored on a computer-readable medium in the form of coded instructions. Thus, such functionality and illustrated functional blocks will be understood as hardware-implemented and / or computer-implemented, and therefore machine-implemented. In terms of hardware implementation, functional blocks may include or comprise, but are not limited to, digital signal processor (DSP) hardware, reduced instruction set processors, hardware (e.g., digital or analog) circuitry (including, but not limited to, application-specific integrated circuits (ASICs)), and (where appropriate) state machines capable of performing such functionality. In terms of computer implementation, a computer is generally understood to include one or more processors or one or more controllers, and the terms computer, processor, and controller are used interchangeably herein. When provided by a computer, processor, or controller, the functionality may be provided by a single dedicated computer, processor, or controller, by a single shared computer, processor, or controller, or by multiple separate computers, processors, or controllers (some of which may be shared or distributed). Furthermore, the use of the terms "processor" or "controller" should also be interpreted to refer to other hardware capable of performing such functionality and / or executing software, such as the example hardware described above.

[0021] The accompanying drawings are to be considered schematic representations, and the elements shown are not necessarily shown to scale. Rather, various elements are shown such that their function and general purpose will be apparent to those skilled in the art. Any connection or coupling between functional blocks, devices, components, or other physical or functional units shown in the drawings or described herein may also be achieved through indirect connections or couplings. Coupling between components may also be established via wireless connections. Functional blocks may be implemented in hardware, firmware, software, or a combination thereof. The term “receive” or “receiving” data or information should be understood as “detection from a received signal.”

[0022] Figure 1A high-level perspective view of the operation of a wireless system is shown, in which a wireless communication network 100 (hereinafter referred to as wireless network 100) is configured to operate with various wireless devices. Wireless network 100 may be a radio communication network 100, which is configured to operate in accordance with the specifications specified by 3GPP according to various examples. Wireless network 100 may include a core network (CN) 110, which is capable of connecting to an external network 130 such as the Internet. The core network may include multiple core network nodes that implement logical functions. For an example of a 5G system (as shown in the figure), this may in particular include Access and Mobility Management Functions (AMF), Session Management Functions (SMF), User Plane Functions (UPF), Network Opening Functions (NEF), Location Management Functions (LMF), and Application Functions (AF), all of which are conventional functions of 5G systems.

[0023] Core network 110 is connected to at least one access network 120, such as a radio access network (RAN), which includes one or more base stations or access nodes, as illustrated in the figure of access node 121. Access node 121 is a radio node configured to wirelessly communicate with multiple UEs (UE 10 shown) on physical channels 140, 142. In some examples, node 20 may be another UE. According to various conventional procedures, UE 10 may also be configured to communicate directly with wireless network 100 on physical channel 140, or indirectly with wireless network 100 via physical channels 141, 142 and using node UE 20. Physical channels may be used to establish one or more logical channels.

[0024] Before discussing further details and aspects of the proposed method, the functional elements of an example entity for performing the proposed solution will be briefly discussed with reference to the accompanying drawings.

[0025] Figure 2 A communication node in the form of an access node 121 of a wireless network 100 is schematically shown, which is configured to perform the various method steps outlined. In various examples, access node 121 is a radio base station for operating in the radio communication network 100 to serve one or more radio UEs (such as UE 10 and node 20).

[0026] Access node 121 may include a wireless transceiver 213, such as a wireless transceiver for communicating with other entities (such as UE 10) of the radio communication network 100. Therefore, transceiver 213 may include a radio receiver and transmitter for communicating via at least an air interface. The wireless transceiver may be configured, within the context of the proposed solution, to support registration and communication with low-power devices, such as environmental IoT or zero-energy devices as described herein.

[0027] Access node 121 may also include or be connected to antenna 214, which may include multiple antennas (antenna elements) in an array configuration. Antenna array 214 is connected to transceiver 213.

[0028] Access node 121 also includes logic circuitry 210 configured to control access node 121 to communicate with the UE via radio transceiver 213 on a physical channel. Logic circuitry 210 can be configured for resource allocation and can implement a scheduler for scheduling data communications.

[0029] Logic circuitry 210 may include processing device 211, which includes one or more processors, microprocessors, data processors, coprocessors, and / or some other type of component that interprets and / or executes instructions and / or data. Processing device 211 may be implemented as hardware (e.g., a microprocessor) or a combination of hardware and software (e.g., a system-on-a-chip (SoC), an application-specific integrated circuit (ASIC), etc.). Processing device 211 may be configured to perform one or more operations based on an operating system and / or various applications or programs.

[0030] Logic circuit 210 may also include a memory storage device 212, which may include one or more memories and / or one or more other types of storage media. For example, memory storage device 212 may include random access memory (RAM), dynamic random access memory (DRAM), cache, read-only memory (ROM), programmable read-only memory (PROM), flash memory, and / or some other type of memory. Memory storage device 212 may include a hard disk (e.g., magnetic disk, optical disk, magneto-optical disk, solid-state disk, etc.). Memory storage device 212 is configured to store computer program code executable by processing device 211, wherein logic 210 is configured to control access node 121 to perform any method steps as provided herein. Software defined by the computer program code may include applications or programs that provide functionality and / or procedures. Software may include device firmware, operating system (OS), or various applications executable in logic 210.

[0031] Access node 121 may also include interface 215 configured to communicate with core network 110.

[0032] Figure 3A An example of a UE 10 configured to communicate with a wireless network 100 as presented herein and configured to perform various method steps as outlined herein is illustrated schematically. In this case, the UE 10 may be configured as a low-power device (LPD) in various examples, as discussed below. In some examples, the UE or LPD 10 is configured to operate as an environmental IoT device or a zero-energy device. The accompanying drawings illustrate some relevant elements or functions of the UE 10. However, in addition to the features and elements shown in the drawings or described herein, the UE 10 may include other features and elements such as a housing, user interface, sensors, etc., but these items are omitted for simplicity. In the case where node 20 is another UE, the node may also be configured to... Figure 3A Configure it.

[0033] UE 10 includes a radio transceiver 313 (also referred to herein as modem 313) for communicating, for example, via sidelink communication or by using simplified or novel protocols suitable for IoT environments, with other entities of the radio communication network 100, such as access node 121 or another UE via an air interface, in one or more frequency bands. Therefore, transceiver 313 may include a receiver chain (Rx) and a transmitter chain (Tx) for communication at least via an air interface (referred to as Uu in 3GPP). Transceiver 313 may be or include a modem configured to encode, transmit, receive, and decode data using radio wave transmission. In some examples, the transceiver may be configured to operate under very low-complexity modulation, such as on-off keying (OOK) modulation, binary frequency shift keying (BFSK), and binary phase shift keying (BPSK) and may use backscatter communication, as referenced... Figure 3B As described.

[0034] UE 10 may also include an antenna system 314, which may include one or more antennas, antenna ports, or antenna arrays. The antenna system 314 is connected to the transceiver 313.

[0035] UE 10 also includes logic circuitry 310 configured to control data and signal communication with the serving access node of wireless network 100 over a physical channel via a radio transceiver, as well as data encoding and decoding. The logic circuitry is also configured to control the UE to perform any of the steps associated with the proposed solution as outlined herein.

[0036] The logic circuit 310 may include a processing device 311, which includes one or more processors, microprocessors, data processors, coprocessors, and / or some other type of component that interprets and / or executes instructions and / or data. The processing device 311 may be implemented as hardware (e.g., a microprocessor) or a combination of hardware and software (e.g., a system-on-a-chip (SoC), an application-specific integrated circuit (ASIC), etc.). The processing device 311 may be configured to perform one or more operations based on an operating system and / or various applications or programs.

[0037] Logic circuitry 310 may further include a memory storage device 312, which may include one or more memories and / or one or more other types of storage media. For example, memory storage device 312 may include random access memory (RAM), dynamic random access memory (DRAM), cache, read-only memory (ROM), programmable read-only memory (PROM), flash memory, and / or some other type of memory. Memory storage device 312 may include a hard disk (e.g., magnetic disk, optical disk, magneto-optical disk, solid-state disk, etc.). Memory storage device 312 is configured to store computer program code executable by processing device 311, wherein logic circuitry 310 is configured to control UE 10 to perform any method steps as provided herein. Software defined by the computer program code may include applications or programs that provide functionality and / or procedures. Software may include device firmware, operating system (OS), or various applications executable in logic circuitry 310.

[0038] UE 10 also includes a power source 315 that provides power to other components of UE 10. In some examples, power source 315 may include a battery. In various implementations of low-complexity UE types, battery 315 may be non-replaceable and even non-rechargeable. In yet another example, power source 315 is configured to harvest incoming radio frequency (RF) energy or other energy resources (e.g., light, kinetic energy, etc.) to power other components of UE 10, thereby enabling certain processing and UL transmissions.

[0039] Figure 3B A schematic overview of this example is provided for use in UE 10, where UE 10 can be configured as an LPD (such as an ultra-low power IoT device), including passive or semi-passive circuitry, and harvesting energy to perform UL transmission. Therefore, UE 10 can be configured to employ so-called backscatter communication, similar to an RFID tag. Backscatter refers to the transceiver 313 in UE 10 simultaneously harvesting energy using a DL carrier (labeled RF in the figure) and reflecting the carrier back for UL transmission by modulating the carrier with UL data. Figure 3B The use ofFigure 3A The same reference numerals are used, but the functional elements are implemented in different ways. In this case, and using Figure 3B The logic representation provided indicates that power supply 315 may include power harvesting circuitry 316 connected to antenna 314, a power management module, and capacitors (such as supercapacitors). Transceiver 313 may include a communication control module powered by the power management module. The communication control module may be connected to a demodulator for demodulating incoming RF signals and to a modulator for subsequently modulating outgoing "reflected" RF signals. Logic circuitry 310, including processor 311 and memory 312, is also powered by and connected to the power management module to control the operation of at least transceiver 313.

[0040] Other types of UEs exist, including other types of RFID devices, which collectively have high or extremely high energy and power limitations. Therefore, given the various types of UEs operating under such stringent power limitations, such as those operating under 3GPP specifications, the inventors have identified a need to address and optimize system overhead. In the case of such UEs configured to operate under strict energy limitations (e.g., capable of transmitting only in response to received RF energy or other external energy stimuli, or configured to transmit only in response to received triggers), the operation of the UE can be entirely under the control of the application functions or application server associated with the UE.

[0041] A 3GPP study refers to low-power or low-complexity devices as Ambient IoT. Based on 3GPP TR 38.848 Release 18.0.0 (2023-12), the study focuses on design goals for relevant use cases of new 3GPP IoT technologies, based on suitable deployment scenarios within 3GPP systems. These technologies rely on ultra-low complexity devices and ultra-low power consumption, making them suitable for very low-end IoT applications. In the study, Ambient IoT devices are categorized into three different device types / groups (but more or fewer are also feasible) based on their energy storage capacity and ability to generate RF signals for transmission: - Device A: No energy storage, no independent signal generation / amplification, i.e., backscatter transmission.

[0042] - Device B: It has energy storage but no independent signal generation, i.e., backscatter transmission. The use of the stored energy can include amplification of the reflected signal.

[0043] - Device C: It has energy storage and independent signal generation, i.e., an active RF component for transmission.

[0044] The target power consumption and device complexity of IoT devices in three types of environments are as follows: - For device A, the power consumption target during transmission / reception is ≤1 μW or ≤10 μW, and the complexity target is comparable to RFID. - For device B, the objective during transmission / reception is such that: o Power consumption of device A << power consumption of device B < power consumption of device C; or o Power consumption of device A ≤ Power consumption of device B < Power consumption of device C.

[0045] Similarly, the objective complexity makes: The complexity of device A is less than the complexity of device B, which is less than the complexity of device C.

[0046] - For device C, the device power consumption during transmission / reception is ≤1 mW to ≤10 mW, and the complexity target is several orders of magnitude lower than that of narrowband-IoT (NB-IoT).

[0047] Table 1 shows an overview of device classifications and their target power consumption.

[0048]

[0049] Table 1

[0050] It can be noted that the limited energy storage may differ between implementations within device B or within device C, and may also differ between device B and device C. This storage is expected to be one or more orders of magnitude smaller than the storage typically included in NB-IoT devices. Class A, B, and C devices are capable of demodulating control, data, etc., from relevant entities based on the connectivity topology.

[0051] The proposed solution will then be provided in the case where the UE 10 is configured as a low-power device (LPD) 10 (such as an environmental IoT (AIoT) device). In this document, LPD can refer to a UE configured with energy harvesting circuitry, such as the reference UE. Figure 3B The circuit 315 is illustrated. In one or more examples, the LPD is associated with a device type. In one or more examples, the device type can be classified based on one or more sets of capabilities, such as energy storage capacity and / or synchronization capability, and whether the circuit, such as the LPD, is active, semi-active, or passive. The information provided in Table 1 provides an example of such device type classification.

[0052] To support low-power connectivity (i.e., LPD connectivity such as AIoT devices), various network topologies can be envisioned, such as... Figure 4As shown in the figure. The example shown in this figure is provided in 3GPP TR 38.848. Network topology refers to the physical or logical layout of a network, defining how different nodes or devices are connected and how data is transmitted between them. In the case of the proposed solution, LPD 10 can be configured to register and communicate with wireless network 100 in different ways, wherein LPD 10 can communicate directly with access node 121, or wherein signals and / or data are transmitted to access node 121 through another device.

[0053] In this context, Topology 1 involves LPD 10 communicating directly with access node 21 of the wireless network. Topology 2 refers to communication with wireless network 100 via an intermediate node. Such transmissions between LPD 10 and access node 121 can be performed, for example, via node 20 (such as another UE, a relay, or a coverage enhancement device (CED)). Topology 3 refers to communication with wireless network 100 using an auxiliary node (such as a UE acting as node 20). The alternatives shown are a) DL auxiliary and b) UL auxiliary. Topology 4 refers to communication with another communication node that does not require communication related to wireless network 100.

[0054] In existing 3GPP IoT standards, devices first need to fully scan all possible frequency ranges with a specific channel raster, finding the correct base station by measuring and decoding different synchronization signals and system information, including the Master Information Block (MIB) and System Information Block Type 1 (SIB1). The device registers with the core network via a random access procedure and then camps on the selected base station (access node). However, since the target power consumption of LPDs such as AIoT is very limited compared to existing low-power cellular connections (such as NB-IoT and Machine-Type Communication (MTC)), the existing registration and discovery process (i.e., finding a suitable cell in the Uu interface or discovering / finding other UEs in the sidelink) is very energy-intensive. Such legacy procedures also do not support network topologies for IoT environments.

[0055] refer to Figure 5A and Figure 5B The signaling diagrams provided below illustrate various examples of the proposed solution. In these diagrams, the same reference numerals are used to identify the same or corresponding features and steps. Furthermore, some examples of the proposed solution may involve the use of resources dedicated to (or available from) the EPD device, as described in the references... Figure 6 Further details are provided below. Additionally... Figure 7 , Figure 8A , Figure 8B and Figure 9 The document provides flowcharts that cover the process based on the proposed solution and, for example... Figure 5A and Figure 5BThe signaling graph supports various methods.

[0056] Figure 5A and Figure 5B The diagram illustrates the signaling and various actions taken between an EPD labeled UE 10, an access node 121 of the wireless network 100, and one or more additional communication nodes 20 labeled as auxiliary nodes (Ass. Nodes). In this case, the communication node 20 can be a UE 20 (not an LPD), such as a mobile phone, smartphone, laptop computer, or other type of wireless communication device with better features and functions than UE 10. The proposed solution is based on the concept that the EPD 10 can register and connect to the wireless network 100 by communicating directly with the network through RAN 120 (represented by access node 121), or partially or entirely by communicating via another wireless device (represented by communication node 20) that can wirelessly connect to the wireless network 100. It can be noted that in the case of the proposed solution, registration can refer to the so-called initial registration, i.e., when the EPD 10 first registers to the wireless network. Alternatively, the proposed solution can be applied to the re-registration phase of the LPD 10, which may be triggered by mobility (such as when the LPD leaves and re-enters the coverage area of ​​the wireless network 100, by the expiration of a timer in the LPD 100, or by channel conditions that cause a change in connectivity (e.g., the termination of the ability to monitor signaling from a communication node)).

[0057] It should be noted that not all steps or actions shown in the signaling diagram are included in the broadest scope of the proposed solution, but for ease of understanding, each step of the signaling diagram will be described in turn.

[0058] refer to Figure 5A and Figure 5B In some examples, access node 121 may send information 50 indicating LPD registration support (501), which identifies registration capability via LPD broadcast signaling. If LPD 10 receives and detects this broadcast message (502), this information indicates that LPD 10 is in an area where it can register (or connects when already registered) to wireless network 100. The ability to register the LPD can be explicitly indicated, for example, in a message included in broadcast 50, either to wireless network 100 or specifically to access node 121. In some examples, this capability is implicitly indicated, for example, by sending a specific reference / synchronization signal 50 dedicated to the LPD (e.g., an AIoT device). In some examples, LPD 10 may be pre-configured to monitor one or more resources dedicated to broadcast 50. In some examples, broadcast 50 may be transmitted over a period of time, such that the radio frequency of transmission 50 can be determined, for example, according to... Figure 3BThe configured device collects data for backscattering. In some examples, broadcast 50 indicates the resource or other configuration for the LPD to send registration requests.

[0059] LPD 10 can broadcast 503 a first UL message 51 indicating a registration request, wherein the first UL message 51 includes the ID of LPD 10 in wireless network 100. In this case, broadcasting means that message 51 can be received by any node, such as auxiliary node 20 and access node 121. The ID can be broadcast 503 using some predetermined encryption method or code pre-encoded in LPD 10 or determined based on the received information 50. The ID can include hard-coded data in LPD 10 or be derived from such hard-coded data. In some examples, the ID can be a temporary ID or a fully unique ID of LPD 10. In some other examples, the ID is a subscription ID associated with wireless network 100. In some examples, the ID can include SUPI (5G Globally Unique Permanent Subscription Identifier) ​​or SUCI (Encrypted SUPI). By broadcasting 503, any communication node within range that can be used to assist LPD 10 in the registration process becomes aware of the registration request. In some examples, the first UL message is broadcast within certain radio resources (e.g., a resource pool) dedicated to a given device type (such as for AIoT type devices, or one of types A to C as described in Table 1 above, or other definitions for low-power or low-complexity type wireless devices). In some examples, the first UL message 51 is broadcast using resources dedicated to LPD network registration (such as one or more specific resources within the illustrated resource pool). See below for further details. Figure 6 Examples of such resources are given. Broadcasting using such dedicated resources allows any communication node that detects the broadcast to identify the transmission as a dedicated registration request. In some examples, the first UL message may include indicators such as flags, bits, or sequences to identify the registration request, rather than allocating specific resources for the registration request. In some examples, the first UL message 51 may include capability signaling that indicates the LPD type, such as one of type A, B, or C. In other examples, the capability signaling is performed separately, rather than within the first UL message used for the registration request. For example, referring to Table 1, broadcast 503 may be performed via ambient backscattering, where LPD 10 is a type A or B device, or via simple modulation, where LPD 10 is a type C device.

[0060] The first UL message 51 broadcast may be received 504 in access node 121, and / or 505 in one or more other communication nodes (such as node 20) that may assist LPD 10 in connecting to and registering with wireless network 100.

[0061] Next,Figure 5A and Figure 5B Alternative implementations, which will be described separately, are shown. Here, communication with respect to wireless network 100 is indicated to be performed by access node 121. However, it should be noted that the registration of LPD 10 to wireless network 100 also includes registration in core network 110. According to the proposed solution, the registration-related process may also include communication between access network 120 (e.g., access node 121) and core network 110, or NAS (non-access stratum) communication between core network 110 and LPD 10 and / or other communication nodes 20. Communication with core network 110 is not described in detail herein, but... Figure 5A and Figure 5B The information is displayed in the background of access node 121 via the core network 110.

[0062] Figure 5A An example of network-based registration and topology discovery is described. Any communication node (such as auxiliary node 20) that receives the registration message 505 broadcast 51 sends a report message 506 52 for reception in access node 121 507. The report message 52 indicates / confirms the reception of the registration request 51 in communication node 20, as well as a measurement or indication of the signal strength detected at the time of reception. In this case, it should be noted that access node 121 does not need to detect the registration request 51.

[0063] In step 508, access node 121 determines or assigns a communication node to communicate directly with LPD 10 for the registration process. According to some examples, this determination may include selecting the communication node with the highest detected signal strength. In some examples, access node 121 may be configured to select itself in step 508 if access node 121 and communication node 20 detect equal signal strengths for receiving registration request 51 (within a certain tolerance).

[0064] If access node 121 chooses to communicate directly with LPD 10, it sends an acknowledgment (ACK) 55A to LPD 10 for receipt 513. This acknowledgment includes or is accompanied by an indication of the supported or selected topology type, such as... Figure 4 The example uses one of topologies 1 through 3. In this case, it can be noted that when confirmation is mentioned herein, the confirmation can be conveyed in the confirmation message. The selected topology is further used after registration for any UL and DL communication between UE 10 and the network (e.g., directly to access node 121 or indirectly through auxiliary node 20).

[0065] When access node 121 selects communication node 20 to communicate directly with LPD 10, access node 121 sends control message 510 53 for reception 511 in control node 20, configuring control node 20 to be in direct contact with LPD 10, i.e., the communication node closest in terms of connectivity. Control message 53 may also indicate the supported or selected topology type as described. Communication node 20, assigned by the access network in step 508, is configured via control message 53 to send 512 acknowledgment (ACK) 55B of the registration request to LPD 10, including or accompanied by an indication of the supported topology type. After registration, UE 10 and the network communicate via the selected topology and perform UL and DL transmissions.

[0066] exist Figure 5A In the example, it is confirmed that 55A and 55B are therefore alternatives, and therefore LPD 10 will only receive one of them (if any).

[0067] Alternatively, in either of these scenarios, a corresponding control message indicating the selected topology can be sent to any other communication node that has sent report message 52. If such another communication node receives a request message that does not instruct it to further participate in the registration process, any record of the received registration request 31 can be erased.

[0068] Step 518 instructs the execution of additional steps for LPD 10 to register with wireless network 100. In this case, LPD 10 is configured to communicate with wireless network 100 via acknowledgment request 55A or 55B according to the indicated topology.

[0069] Figure 5B An example device-based solution is described. Any communication node (such as...) that receives the registration message broadcast by 504, 505, or 51... Figure 5B In the example shown, access node 121 and auxiliary node 20 are configured to send acknowledgments (ACKs) 56A and 56B to the registration request for reception in LPD 10, 514 and 515, respectively. This acknowledgment includes a measurement or indication of its signal strength. In this case, it should be noted that neither access node 121 nor communication node 20 needs to detect the registration request 51. ACK messages 56A and 56B may also include the ID of the received communication node 121 or 20, or may indicate its node type, such as an access node or auxiliary node in the communication context between LPD 10 and wireless network 100. In various examples, the ID of node 20 or 121 included in the acknowledgment may be encrypted or transmitted over an encrypted link, as shown in the reference. Figure 5A The situations that may occur in the described example.

[0070] If LPD 10 receives multiple ACKs 56A and 56B, LPD 10 continues the registration process with one of the nodes from which it received ACK 516. This is in Figure 5B As shown in step 517, the LPD 10 determines or assigns a communication node to communicate directly with the LPD 10 for the operation of registration process 518. According to some examples, this determination may include selecting the communication node with the highest detected signal strength.

[0071] In some examples, if the signal strength of the received registration request 51 detected by access node 121 and communication node 20 is equal (within a certain tolerance value), LPD 10 can be configured to select access node 121 in step 517. Any communication node 121, 20 not selected in step 517 can be configured to erase any record of the received registration request 51 if the LPD 10 device does not communicate with a communication node for a certain period of time.

[0072] Figure 6 An example resource allocation 66 (such as a resource pattern) for UL transmission information or data that can be used with an LPD (such as LPD 10) is shown. The example resource allocation can be a predefined resource allocation, such as a generic resource allocation that can be used for UL transmissions with an LPD. In another example, it could be for transmissions from access node 121 ( Figure 6 Similar predetermined resource allocations are defined for DL ​​transmissions performed on access node 121 (not shown in the image). In another example, a similar allocation can be defined for DL ​​transmissions performed on access node 121 (not shown in the image). Figure 6 The UL / DL transmission (not shown) defines a similar predetermined resource allocation. For communication between LPD 10 and communication node 20, a side-link configuration of resources can be used instead. General resource allocation can include multiple time windows 62, such as the uplink transmission window (UTW), in which UL transmissions from the LPD can be performed. Figure 6 In the example resource allocation, a first time window 62A, a second time window 62B, and a third time window 62C are shown. Time windows 62, 62A, 62B, and 62C can be separated by a DTX (Discontinuous Transfer) period 64. In one or more examples, the DTX period can be defined based on the expected periodicity of the UL transmission (such as based on the delay requirements of the DTX period 64 and / or the LPD). In other words, multiple LPDs can be scheduled within the same time window. Furthermore, multiple LPDs can also be scheduled with different DTX periods.

[0073] Each time window 62 may include multiple transmission opportunities (TOs) 66. Each TO may include one or more time and / or frequency resources. A TO can be considered here as a subset of resources (such as time and frequency resources) included within a time window. Each TO may be associated with one or more LPDs (such as a group of LPDs). In other words, different LPDs or groups of LPDs may be allocated in different TOs, such as in different time and / or frequency resources within a time window. Time window 62 may be associated with a discontinuous transmission (DTX) mode and resource size, where the DTX mode is associated with a DTX period 64. Each transmission cycle of an LPD may be a time window (such as a UL transmission window) for UL transmission, including one or more transmission opportunities (TOs) with a specific time and frequency distance between two consecutive transmission opportunities within a time window. In one or more examples, a UL transmission window may be a resource allocation available for multiple LPDs and / or a group of LPDs. In one or more examples, a UL transmission window may be considered as a configuration applicable to multiple LPDs and / or a group of LPDs. In one or more examples, a resource configuration may indicate one or more TOs 66, such as resources associated with time opportunities. The allocation of transmission opportunities for each LPD within each time window may depend on the capabilities of the LPD, such as synchronization capabilities. In these examples, the allocation of transmission opportunities can be determined based on the LPD type (e.g., type A, B, or C), which can be identified via capability signaling. As mentioned above, in some examples, this can be communicated in the first UL message 51. In one or more examples, the configuration for transmission opportunity allocation is predefined or can be transmitted to the LPD by the network node. In one or more examples, an LPD with coarse synchronization capabilities may not be scheduled in the first few TOs of each time window, while an LPD with high synchronization capabilities (such as fine synchronization capabilities) may be scheduled in the first few TOs of each time window.

[0074] Wireless network 100 can broadcast information, for example, broadcast by access node 121, indicating one or more predetermined resource configurations for UL transmission of data from the LPD (e.g., LPD 10), such as a general resource configuration for UL transmission of data from the LPD. The one or more predetermined resource configurations can indicate resource allocations available for UL transmission of data from the LPD, such as... Figure 6The example resource allocation is shown. A resource allocation available for UL transmission of data from an LPD can be considered as all resources available for data transmission from any LPD. A predetermined resource configuration can also be used by the auxiliary node 20 when the auxiliary node 20 communicates with the LPD 10. In one or more example methods, one or more predetermined resource configurations can indicate multiple distinct subsets of resources within the resource allocation of the predetermined resource configuration, such as the entire resource allocation. Therefore, multiple distinct subsets of resources can be a portion of all resources available for UL transmission of data from an LPD. Multiple distinct subsets of resources can, for example, be dedicated to different types of LPDs or different groups of LPDs, and / or can be dedicated to different types of transmission.

[0075] For example, and referring to the proposed solution, the resources of resource allocation 66 can be used when LPD 10 registers with wireless network 100. In some examples, LPD 10 can transmit anywhere and at any time within a given resource pool of resource allocation 66. In other examples, LPD 10 can transmit within specific time and frequency resources dedicated to registration purposes. Therefore, one or more specific resources of resource allocation 66 can define a subset of resources dedicated to registration transmission, thereby allowing LPD 10 to register with wireless network 100. The subset of resources dedicated to registration can be used to broadcast registration request 51 (503). In some examples, different subsets of resources can be allocated for registration of different types of LPDs (such as types A, B, and C discussed above).

[0076] Figure 7 Flowcharts of methods executed in the LPD 10 according to various examples of the proposed solution are provided. The LPD 10, including the wireless transceiver 313 and logic circuitry 310, is also configured to execute... Figure 7 The steps will be further referenced. Figure 5A and Figure 5B Examples (where applicable) are provided to indicate the corresponding steps.

[0077] According to one aspect of the proposed solution, a method for use in LPD 10 when registering to a wireless network is provided. More broadly, the method may include the following steps: 700: Monitoring information signaling from the wireless network. This may involve: listening for DL ​​broadcasts in predetermined resources. Specifically, this may involve: monitoring the reception 502 of information 50 indicating that the network supports registration via broadcast signaling. In some examples, this may also include: collecting RF energy obtained when receiving information transmitted from an access node of the wireless network.

[0078] 705: Broadcast a first UL message indicating registration request 51, which includes the ID of LPD 10 in the wireless network. The message may be encrypted for security reasons. The first UL message may be transmitted in a resource that can be defined for use by the LPD or a class of LPDs (e.g., dedicated or non-dedicated resources), optionally in a specific resource within a resource pool dedicated to the LPD for registration request transmission. Resources may be defined for use by the LPD by pre-determining in the specification or by a general decision and configuration by RAN 120 (such as Access Node 121) and by broadcasting system information or by other network signaling notification. Broadcasting the first UL message may be accomplished using energy collected in connection with receiving DL broadcast 50.

[0079] 710: Receive acknowledgments 55A / 55B, 56A, 56B from at least one communication node, the acknowledgment including the node ID of the communication node that received the first UL message. In some network-based examples, only one acknowledgment 55A or 55B may be received. In other examples related to device-based solutions, multiple acknowledgments may be received from different communication nodes.

[0080] 715: Determining the initial network topology based on acknowledgments. In a network-based solution, the initial network topology can be determined by receiving an indication of the initial network topology in acknowledgments 55A or 55B. In a UE-based alternative, determining the initial network topology may further include selecting a 517 communication node based on the received acknowledgments. In some examples of either alternative, the indication of the initial network topology may include the ID of the selected communication node that sent the acknowledgment, wherein determining the initial network topology may include mapping the ID or ID type of the selected communication node to a communication node type that indicates the initial network topology. In other examples, the specific radio resources used by the selected communication node for DL ​​transmission acknowledgments may be an indication that can be used to determine the initial network topology in LPD 10.

[0081] In some examples, determining the initial network topology may include: determining or mapping to a resource configuration that indicates radio resources in the time and / or frequency domains for communicating with the wireless network, i.e., for UL and / or DL ​​communication with nodes 20, 121 that are communicatively closest to LPD 10, based on the initial network topology.

[0082] 720: Register with the wireless network based on the determined initial network topology. This may correspond to... Figure 5A and Figure 5BStep 518. Registration based on the determined initial network topology may involve: using resource configurations for UL and / or DL ​​communications determined based on the determined initial network topology. In some examples, registration based on the determined initial network topology may include: using a sidelink configuration where the communication nearest node 20 is a UE acting as an auxiliary node, or including: using a simplified or novel protocol suitable for the IoT environment. In some examples, registration based on the determined initial network topology may include: selecting modulation or coding based on the communication nearest node according to the determined initial network topology. The actual registration itself is not part of the proposed solution. Specifically, this part can be performed using conventional features and steps, and therefore is not described in detail.

[0083] Figure 8A and Figure 8B A flowchart is provided showing the methods performed in access node 121 of wireless network 100 according to various examples of the proposed solution. Figure 8A A network-based alternative is shown, while Figure 8B Device-based alternatives are shown. Both correspond to the different alternatives described above. The access node 121, including wireless transceiver 213 and logic circuitry 210, is also configured to perform various operations in different examples. Figure 8A and Figure 8B The steps. Both alternatives include the following steps: 800: Information 50 indicating network support or registration capabilities is sent from the LPD via broadcast signaling. This corresponds to step 501. The capability or support of the wireless network 100 or specifically access node 121 for registering the LPD can be explicitly indicated, for example, based on information included in the message contained in the broadcast 50, such as one or more bits indicating support for the LPD and / or LPD type. In some examples, this capability is implicitly indicated, for example, by transmitting a specific reference / synchronization signal dedicated to the LPD (e.g., an AIoT device). Once the LPD is able to detect the reference / synchronization signal, the LPD considers the network to support the operation of the LPD in the network. In some examples, the broadcast 50 can be transmitted over a period of time, such that the radio frequency of the transmission 50 can be determined by, for example, according to... Figure 3B The configured device collects backscattered signals. Broadcasting can be performed using radio resources that overlap in frequency with resource pool 66 configured for LPD response request registration. Information transmission 50 may include, or be transmitted together with, a signal providing RF energy for energy harvesting for the LPD employing backscattered transmission, as referenced. Figure 3B The explanation given.

[0084] 805: Receive a first UL message indicating registration request 51, which includes the ID of LPD 10 in the wireless network. The first UL message may be received in a resource dedicated to LPD or a class of LPDs, or optionally in a specific resource within a resource pool dedicated to LPDs for registration request transmission.

[0085] 810: Controls the transmission of the first UL message acknowledgment 55A, 55B, 56A, which includes the node ID.

[0086] Different examples apply to network-based implementations and device-based implementations.

[0087] refer to Figure 8A In a network-based alternative, step 810 of controlling the confirmation transmission may further include any one of the steps 811 to 814: 811: Receive from at least one communication node 20 as per reference Figure 5A The described report message 52 confirms receipt of the first UL message and indicates the signal strength when the first UL signal is received.

[0088] 812: Selecting an initial network topology. This may involve selecting a communication node among itself 121 and any communication device 20 that received the report message 52 to establish the closest possible communication with LPD 10 to register with the wireless network 100. This can be determined based on signal strength, as described above.

[0089] 813: If another communication node 20 is selected, a control message 53 can be sent to the communication device 20, thereby configuring the communication device to send an acknowledgment 55B to the LPD 10.

[0090] 814: On the other hand, if in step 812 the access node 121 is selected to continue using the latest communication with LPD 10 for registration, the access node sends an acknowledgment 55A to LPD 10.

[0091] In either step 813 or 814, the confirmation includes an indication of the selected initial network topology.

[0092] In cases including step 813, the method may further include: 815: Erase any records of registration requests from LPD 10.

[0093] In cases including step 814, the method may further include: 820: Continue registering LPD 10 to the wireless network.

[0094] Figure 9A flowchart is provided of a method performed in a communication node 20, which may be a UE 20 acting as an auxiliary node in LPD 10 registration. Figure 9 A network-based alternative corresponding to the foregoing example is shown. Communication node 20 can be configured according to reference... Figure 3A The UE described is an example as previously described, but not as an LPD, but as a conventional UE, such as a mobile phone, computer, or other wireless device. Therefore, communication node 20 may include a wireless transceiver 313 and logic circuitry 310, and is configured in various examples to perform... Figure 9 The method may include the following steps: 905: Receive a first UL message indicating registration request 51, which includes the ID of LPD 10 in the wireless network. The first UL message may be received in a resource dedicated to LPD or a class of LPDs, or optionally in a specific resource within a resource pool dedicated to LPDs for registration request transmission.

[0095] 910: Controls the transmission of confirmation of the first UL message, which includes the node ID.

[0096] Step 910 of controlling and confirming the transmission may also include any one of the following steps 911 to 913: 911: Send to access node 121 as per reference Figure 5A The described report message 52 reports the receipt of a first UL message in the communication node and indicates the signal strength when the first UL signal is received.

[0097] As described in this article, the registration preparation and further processing depend on the topology selection in access node 121.

[0098] When selecting a communication node in topology selection 508, the method further includes: 912: Receives control message 53 from access node 121, thereby being configured to send acknowledgment 55B to LPD 10.

[0099] 913: Send acknowledgment 55B to LPD 10.

[0100] 920: Step 913 can be performed with communication node 121 as the nearest communication node, which acts as an auxiliary node in the registration of LPD to wireless network 100.

[0101] 915: If access node 121 makes another topology selection, communication node 20 may be arranged to erase any records from the registration request from LPD 10, for example, triggered by a timer timeout after a report message is sent in step 911.

[0102] The foregoing describes various examples related to the initial network topology. Depending on some aspects, the initial network topology may include an indication of the ID, type, or role of any of the communication nodes 20 or 121 that are most communicatively close to LPD 10. In some examples, the initial network topology may include or indicate resource configuration, scheduling, encoding, modulation, or other communication parameters for further communication involved during or after registration 518. In this case, determining the initial network topology in LPD 10 (obtained based on an indication of access node 121 or other communication node 20 in a network-based alternative, or determined based on received acknowledgments in a device-based alternative) is advantageous for further operation of LPD 10 during the registration process.

[0103] Table 2 below provides an example of an initial network topology determination 715 based on acknowledgment according to some implementations. Here, the communication node 20 that can operate as an auxiliary device is labeled as UE 20. The first column defines three alternatives related to acknowledgment reception in LPD 10. The top labels of columns 2 and 3 identify the node ID received in the acknowledgment. Note that... The node ID of the communication node that received the registration request is forwarded to LPD 10 via auxiliary node 20 or access node 121.

[0104]

[0105] Table 2

[0106] The various aspects of the proposed solution have been described above. Unless there is an obvious contradiction, features of any examples provided herein can be combined in any way within the scope defined by the appended claims.

Claims

1. A method performed in a low-power device when registering to a wireless network, the method comprising: The broadcast (705) indicates a first uplink message for a registration request, the first uplink message including the ID of the low-power device in the wireless network; Receive (710) an acknowledgment from at least one communication node, the acknowledgment including the node ID of the communication node that received the first uplink message; Based on the confirmation, the initial network topology (715) is determined.

2. The method according to claim 1, wherein, The first uplink message is broadcast within a resource pool, which is defined as being used by a given device type.

3. The method according to claim 2, wherein, The confirmation is received in the resources associated with the resource pool.

4. The method according to any one of the preceding claims, wherein, The first uplink message is encrypted using a predetermined encryption method or code.

5. The method according to any one of the preceding claims, wherein, The first uplink message indicates a low-power device type.

6. The method according to any one of the preceding claims, wherein, The first uplink message is broadcast using resources dedicated to network registration.

7. The method according to any one of claims 1 to 5, wherein, The first uplink message also includes an indicator that identifies the registration request.

8. The method according to any one of the preceding claims, comprising: Monitoring (700) information signaling from the wireless network; Specifically, based on the monitoring, the broadcast is performed when information indicating that the network supports registration via broadcast signaling is received.

9. The method according to any one of the preceding claims, comprising: Collect radio frequency energy obtained when receiving radio frequency signals from the wireless network; The broadcast is conducted using the collected energy.

10. The method according to claims 8 and 9, wherein, The information is received on the radio frequency signal.

11. The method according to any one of the preceding claims, wherein, The node ID indicates the initial network topology for the connection of the low-power device.

12. The method according to any one of claims 1 to 10, wherein, The initial network topology is determined by the wireless network and indicated in the confirmations (55A, 55B).

13. The method according to any one of claims 1 to 11, wherein, The receiving includes receiving acknowledgments (56A, 56B) from multiple communication nodes. And the determination includes: selecting (517) an initial network topology based on receiving the confirmation.

14. The method according to any one of the preceding claims, wherein, The node ID indicates that the first communication node is an access node of the wireless network or a user equipment (UE) wirelessly connected to the wireless network.

15. A low-power device, comprising: Wireless transceiver; as well as A logic circuit is configured to control the low-power device to perform the steps according to any one of claims 1 to 14.

16. The low-power device according to claim 15, wherein, The wireless transceiver is configured to operate under low-complexity modulation.

17. The low-power device according to claim 16, wherein, The modulation is one of on-off keying modulation, binary frequency shift keying, and binary phase shift keying.

18. The low-power device according to claim 16 or 17, wherein, The transceiver is configured to operate using backscatter communication.

19. The low-power device according to any one of claims 15 to 18, further comprising: A collection module is configured to collect radio frequency energy obtained from received signals, wherein the wireless transceiver and the logic circuit are powered by the collection module.

20. A method performed in a communication node when a low-power device registers to a wireless network, the method comprising: Receive a (805, 905) first uplink broadcast message, the first uplink message including the ID of the low-power device in the wireless network; Control (810, 910) the transmission of an acknowledgment for the first uplink message, the acknowledgment including the node ID.

21. The method according to claim 20, wherein, The communication node is the access node of the wireless network, wherein the control confirmation transmission includes: Receive (811) a report message from at least one other communication node, the report message confirming receipt of the first uplink message and an indication of the signal strength when the first uplink signal was received; Based on the report message, select (812) the initial network topology for registering the low-power device 10.

22. The method according to claim 21, wherein, The selection of the initial network topology (812) includes: Send the acknowledgment (814) to the low-power device; or A control message (813) is sent to a selected communication node among the at least one other communication node to configure the selected communication node to send the acknowledgment to the low-power device.

23. The method according to any one of claims 20 to 22, further comprising: The broadcast indicates that the network supports registration information via uplink broadcast signaling.

24. The method according to claim 19, wherein, The communication node is an auxiliary communication node connected to the access node of the wireless network, wherein the transmission of control confirmation includes: Send a (911) report message to the access node, the report message confirming receipt of the first uplink message and an indication of the signal strength when the first uplink signal was received.

25. The method of claim 24, further comprising: When the control message (912) is received from the access node, the acknowledgment (913) is sent to the low-power device.

26. The method according to any one of claims 20 to 25, wherein, The first uplink message is received within a resource pool, which is defined for use by a specific device type.

27. The method according to claim 25, wherein, The confirmation is sent in the resources associated with the resource pool.

28. The method according to claims 20 to 27, wherein, The first uplink message is received in a resource dedicated to network registration.

29. The method according to any one of claims 20 to 27, wherein, The first uplink message also includes an indicator that identifies the registration request.

30. A communication node, comprising: Wireless transceiver; as well as A logic circuit is configured to control the communication node to perform the steps of any one of claims 20 to 29.

Images