Energy efficient and robust wakeup signaling-group wakeup

By relaying UEs to use group wake-up signaling and low-power wake-up signals in wireless communication systems, the problem of wake-up of ultra-low power devices in the case of RF link difference is solved, and efficient and low-energy-consuming device wake-up and data transmission are achieved.

CN118923160APending Publication Date: 2024-11-08TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280093912.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-03-23
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

The prior art is difficult to effectively wake up ultra-low power wireless communication devices (such as IoT UEs), especially in the case of radio frequency link difference or loss between base stations and devices, and the traditional wake-up mechanism is low efficiency and high energy consumption, making it difficult to meet energy saving. Robust requirements.

Method used

The relay UE is introduced to reduce signaling overhead and improve wake-up efficiency through group wake-up signaling and low power wake-up signaling (LPWUS) to reduce signaling overhead and improve wake-up efficiency. The distance between the relay UE and the remote UE is shortened to reduce power consumption, and the device is realized. Energy-saving wake-up and data transmission.

Benefits of technology

Improves the efficiency and robustness of device wake-up, reduces the power consumption of remote UEs, enhances communication capabilities in non-coverage areas, supports lower uplink transmission power and simple wake-up receiver mode.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118923160A_ABST
    Figure CN118923160A_ABST
Patent Text Reader

Abstract

Systems and methods for group wakeup for relays of a group of remote user equipments (UEs) in a wireless communication system are disclosed. In one embodiment, a method performed by a relay UE for a group of remote UEs comprises receiving a group wake-up signal (WUS) from another radio node, and performing a group wake-up procedure on the group of remote UEs in an idle state, the group of remote UEs comprising one or more remote UEs. In this manner, the efficiency of the wake-up procedure is improved by minimizing signaling overhead via simultaneous wake-up signaling to the UE group.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Systems and methods related to wake-up signaling in wireless communication systems are disclosed herein. Background Art

[0002] Relay connections using sidelink or device-to-device (D2D) communications have been proposed to increase wireless communication coverage in situations where the radio frequency (RF) link between a base station (BS) and a user equipment (UE) may be very poor or completely lost. See, for example, the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) D2D Proximity Services (ProSe) and related studies in 3GPP Technical Report (TR) 36.843, entitled "LTE Device-to-Device Proximity Services Study - Radio Aspects".

[0003] On the other hand, wake-up signaling has been proposed to enable the UE to enter deep sleep, and the BS is able to wake up the UE using certain signaling. For example, the 3GPP LTE cellular network uses a wake-up signal (WUS) to wake up the Internet of Things (IoT) UE. This WUS is transmitted by the BS to the IoT UE that is in idle mode (e.g., deep sleep) and is required to decode the physical downlink control channel (PDCCH) at the paging opportunity (see, for example, 3GPP Technical Specification (TS) 36.211 V16.1.0). In these cases, if the IoT finds that the WUS is targeted at itself, the IoT UE needs to wake up to perform time and frequency synchronization, receive and decode the WUS, and further receive and decode the paging information carried in the PDCCH. Since the distance between the BS and the IoT UE is usually long, the WUS is usually transmitted with a certain RF bandwidth and / or encoded in the time domain or frequency domain to reduce its false detection rate.

[0004] Ultra-low power UEs (e.g., IoT UEs) may be powered by batteries of very limited capacity, or may be powered by energy harvested from the environment in which the UE is located. It is important that the amount of energy consumed by these UEs for communication is as low as possible. Allowing these UEs to enter a deep sleep mode (e.g., idle mode) when communication is not required is one technique for minimizing energy consumption. Another technique is to minimize the amount of energy consumed by the UE when performing necessary communications, for example by keeping the UE's transmit power (e.g., uplink (UL) transmit power) as low as possible.

[0005] There are many relevant uses for ultra-low power UEs (e.g. different types of sensors, etc.). They can be deployed in environments where the UE has a very poor RF link to the BS, such as basements, behind walls, etc. This makes it very challenging to ensure that the UE is properly woken up by the BS, and also requires that the UL signaling from the UE must occur at very high transmit power when waking up. In addition, the wake-up mechanism for such ultra-low power UEs should be robust and reliable against false detections, without consuming too much additional power.

[0006] Therefore, there is a need for systems and methods that provide energy-efficient and robust solutions to wake up UEs (eg, ultra-low power UEs) and transfer data between these UEs and a BS. Summary of the invention

[0007] A system and method for relayed group wakeup of a remote user equipment (UE) group in a wireless communication system is disclosed. In one embodiment, a method for group wakeup of a remote UE group performed by a relay UE includes: receiving a group wakeup signal (WUS) from another radio node, and performing a group wakeup procedure on a remote UE group in an idle state, the remote UE group including one or more remote UEs. In this way, signaling overhead is minimized by simultaneous wakeup signaling to the UE group, thereby improving the efficiency of the wakeup procedure.

[0008] In another embodiment, performing the group wake-up procedure includes detecting a group WUS received from another radio node, decoding the group WUS to determine one or more remote UEs in a remote UE group, and generating and sending a WUS to each of the one or more remote UEs in the group.

[0009] In another embodiment, performing a group wake-up procedure includes: monitoring wake-up confirmations from one or more remote UEs, and determining whether wake-up confirmations from all remote UEs in the one or more remote UEs are detected when monitoring the wake-up confirmations. Performing the group wake-up procedure further includes: in response to determining that the wake-up confirmation has not been detected for all remote UEs in the one or more remote UEs, identifying one or more remote UEs in the group for which the wake-up confirmation has not been detected, and sending a wake-up signal to the one or more remote UEs in the group for which the wake-up confirmation has not been detected. In one embodiment, performing the group wake-up procedure further includes: setting one or more timers, wherein monitoring the wake-up confirmations from the one or more remote UEs includes: monitoring the wake-up confirmations from the one or more remote UEs while the one or more timers are running. In one embodiment, the method further includes: repeating the steps of monitoring, determining, identifying, and sending until the wake-up confirmation has been detected for all remote UEs in the one or more remote UEs in the group or the maximum number of wake-up attempts has been reached. In one embodiment, generating and sending a WUS to each remote UE in the one or more remote UEs in the group includes: generating and sending a LPWUS to each remote UE in the one or more remote UEs in the group. In one embodiment, the LPWUS has one or more characteristics, and the one or more characteristics enable the power cost for detecting the LPWUS to be less than the power cost for detecting the WUS from the base station. In one embodiment, the method further comprises: generating and sending a synchronization signal for one or more remote UEs in the group. In one embodiment, generating and sending a synchronization signal for one or more remote UEs in the group comprises: broadcasting a synchronization signal for one or more remote UEs in the group. In another embodiment, generating and sending a synchronization signal for one or more remote UEs in the group comprises: generating and sending a separate synchronization signal to each of the one or more remote UEs in the group.

[0010] In one embodiment, performing a group wake-up procedure includes: detecting a group WUS received from another radio node, decoding the group WUS to determine one or more remote UEs in a remote UE group, monitoring wake-up confirmations from the one or more remote UEs, and determining whether wake-up confirmations from all remote UEs in the one or more remote UEs are detected when monitoring the wake-up confirmations. Performing the wake-up procedure further includes: in response to determining that the wake-up confirmation has not been detected for all remote UEs in the one or more remote UEs, identifying one or more remote UEs in the group for which the wake-up confirmation has not been detected, and sending a wake-up signal to the one or more remote UEs in the group for which the wake-up confirmation has not been detected. In one embodiment, performing the group wake-up procedure further includes: setting one or more timers, wherein monitoring the wake-up confirmation from the one or more remote UEs includes: monitoring the wake-up confirmation from the one or more remote UEs while the one or more timers are running. In one embodiment, sending a wake-up signal to the one or more remote UEs in the group for which the wake-up confirmation has not been detected includes: sending a low power wake-up signal (LPWUS) to each remote UE in the one or more remote UEs in the group for which the wake-up confirmation has not been detected. In one embodiment, the LPWUS has one or more characteristics, and the one or more characteristics enable the power cost for detecting the LPWUS to be less than the power cost for detecting the WUS from the base station. In one embodiment, the method further comprises: sending a synchronization signal for one or more remote UEs in the group for which a wake-up confirmation has not been detected. In one embodiment, sending a synchronization signal for one or more remote UEs in the group for which a wake-up confirmation has not been detected comprises: broadcasting a synchronization signal for one or more remote UEs in the group for which a wake-up confirmation has not been detected. In another embodiment, sending a synchronization signal for one or more remote UEs in the group for which a wake-up confirmation has not been detected comprises: sending a separate synchronization signal to each remote UE in the group for which a wake-up confirmation has not been detected. In one embodiment, the method further comprises repeating the steps of monitoring, determining, identifying and sending until a wake-up confirmation has been detected for all remote UEs in the one or more remote UEs in the group, or a predefined or preconfigured maximum number of wake-up attempts has been reached. In one embodiment, the transmit power used to send the wake-up signal is increased for at least one iteration of repeating these steps. In one embodiment, the predefined or preconfigured maximum number of wake-up attempts is configured by the base station.

[0011] In one embodiment, receiving the group WUS from another radio node comprises receiving the group WUS from the base station via one or more additional relay UEs.

[0012] In one embodiment, the method further comprises relaying the group WUS to one or more additional relay UEs.

[0013] Corresponding embodiments of a relay UE are also disclosed.In one embodiment, a relay UE for group wakeup of a remote UE group is adapted to receive a group WUS from another radio node and perform a group wakeup procedure for a remote UE group in an idle state, the remote UE group comprising one or more remote UEs.

[0014] In one embodiment, a relay UE for group wakeup of a remote UE group includes one or more transmitters, one or more receivers, and processing circuits associated with the one or more transmitters and the one or more receivers. The processing circuits are configured to cause the relay UE to receive a group WUS from another radio node and perform a group wakeup procedure for a remote UE group in an idle state, the remote UE group including one or more remote UEs.

[0015] An embodiment of a method performed by a remote UE is also disclosed. In one embodiment, the method performed by the remote UE for waking up from an idle state includes: receiving a WUS for group wakeup of a first remote UE group including the remote UE from a first relay UE; and when performing wakeup in response to receiving the WUS from the first relay UE, avoiding responding to a WUS for group wakeup of another remote UE group also including the remote UE from any other relay UE.

[0016] In one embodiment, the method further comprises, after waking up, receiving from the second relay UE a WUS for group wakeup of a second remote UE group including the remote UE, and responding to the second relay UE. In one embodiment, responding to the second relay UE comprises sending a negative acknowledgement to the second relay UE. In another embodiment, responding to the second relay UE comprises sending a positive acknowledgement to the second relay UE.

[0017] In one embodiment, the remote UE for waking up from an idle state is adapted to receive a WUS for group wakeup of a first remote UE group including the remote UE from a first relay UE, and when performing wakeup in response to receiving the WUS from the first relay UE, avoid responding to a WUS for group wakeup of another remote UE group also including the remote UE from any other relay UE.

[0018] In one embodiment, a remote UE for waking up from an idle state includes one or more transmitters, one or more receivers, and processing circuits associated with the one or more transmitters and the one or more receivers. The processing circuits are configured to cause the remote UE to receive a WUS for group wakeup of a first remote UE group including the remote UE from a first relay UE, and when performing wakeup in response to receiving the WUS from the first relay UE, avoid responding to a WUS for group wakeup of another remote UE group also including the remote UE from any other relay UE. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The accompanying drawings incorporated in and forming a part of this specification illustrate several aspects of the disclosure and together with the description serve to explain the principles of the disclosure.

[0020] Figure 1 A system is shown in which embodiments of the present disclosure may be implemented;

[0021] Figure 2 is a flow chart illustrating operations of a base station, a relay user equipment (UE), and a remote UE for low power wake-up (LPWUS) signaling according to an embodiment of the present disclosure;

[0022] Figure 3A , 3B 4A and 4B illustrate example subframes in which synchronization signals and LPWUS are transmitted according to example embodiments of the present disclosure;

[0023] Figure 5 illustrating operation of a base station, a relay UE, and a remote UE according to at least some embodiments described herein;

[0024] Figure 6 A system is shown in which relayed group wake-up signaling may be used according to an example embodiment of the present disclosure;

[0025] Figure 7 is a flowchart illustrating the operation of a base station performing a grouping process according to an example embodiment of the present disclosure;

[0026] Figure 8 illustrates the operation of a group wake-up for relaying of a base station, a relay UE, and a remote UE group according to an example embodiment of the present disclosure;

[0027] Fig. 9 is a more detailed illustration of an exemplary embodiment according to the present disclosure Figure 8 Flowchart of steps 804 and 806;

[0028] Fig.10 is a more detailed illustration of another exemplary embodiment according to the present disclosure. Figure 8 Flowchart of steps 804 and 806;

[0029] Fig.11 An example of a system in which hierarchical wake-up is provided according to an embodiment of the present disclosure is shown;

[0030] Fig.12 An example of a system providing group wakeup of relays with overlapping groups according to an embodiment of the present disclosure is shown;

[0031] Fig.13 is a flow chart illustrating the operation of a remote UE in two or more groups simultaneously according to an embodiment of the present disclosure;

[0032] Fig.14 is a schematic block diagram of a radio access node according to some embodiments of the present disclosure;

[0033] Fig.15 is a diagram showing some embodiments according to the present disclosure Fig.14 A schematic block diagram of an embodiment of a virtualization of a radio access node;

[0034] Fig.16 According to some other embodiments of the present disclosure Fig.14 A schematic block diagram of a radio access node;

[0035] Fig.17 is a schematic block diagram of a UE according to some embodiments of the present disclosure;

[0036] Fig.18 According to some other embodiments of the present disclosure Fig.17 A schematic block diagram of a UE;

[0037] Fig.19 shows a telecommunications network connected to a host via an intermediate network according to certain embodiments of the present disclosure;

[0038] Fig. 20 is a general block diagram of a host communicating with a UE over a partial wireless connection via a base station according to some embodiments of the present disclosure;

[0039] Fig.21 is a flow chart showing a method implemented in a communication system according to an embodiment of the present disclosure;

[0040] Fig. 22 is a flow chart showing a method implemented in a communication system according to an embodiment of the present disclosure;

[0041] Fig.23 is a flowchart illustrating a method implemented in a communication system according to an embodiment of the present disclosure; and

[0042] Fig.24is a flow chart showing a method implemented in a communication system according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0043] The embodiments set forth below represent information that enables those skilled in the art to practice the embodiments, as well as illustrate the best way to practice the embodiments. After reading the following description in conjunction with the accompanying drawings, those skilled in the art will understand the concepts of the present disclosure and will recognize the applications of these concepts not specifically addressed herein. It should be understood that these concepts and applications fall within the scope of the present disclosure.

[0044] Radio Node: As used herein, a "radio node" is a radio access node or a wireless communication device.

[0045] Radio access node: As used herein, a "radio access node" or "radio network node" or "radio access network node" is any node in a radio access network (RAN) of a cellular communication network that operates to wirelessly transmit and / or receive signals. Some examples of radio access nodes include, but are not limited to, a base station (e.g., a new radio (NR) base station (gNB) in a third generation partnership project (3GPP) fifth generation (5G) NR network or an enhanced or evolved node B (eNB) in a 3GPP long term evolution (LTE) network), a high power or macro base station, a low power base station (e.g., a micro base station, a pico base station, a home eNB, etc.), a relay node, a network node implementing part of the functionality of a base station, or a network node implementing a gNB distributed unit (gNB-DU), or a network node implementing part of the functionality of some other type of radio access node.

[0046] Core network node: As used herein, a "core network node" is any type of node in a core network or any node that implements a core network function. Some examples of core network nodes include, for example, a mobility management entity (MME), a packet data network gateway (P-GW), a service capability exposure function (SCEF), a home subscriber server (HSS), etc. Some other examples of core network nodes include nodes that implement access and mobility functions (AMF), user plane functions (UPF), session management functions (SMF), authentication server functions (AUSF), network slice selection functions (NSSF), network exposure functions (NEF), network functions (NF) repository functions (NRF), policy control functions (PCF), unified data management (UDM), etc.

[0047] Communication Device: As used herein, a "communication device" is any type of device that can access an access network. Some examples of communication devices include, but are not limited to: mobile phones, smart phones, sensor devices, meters, vehicles, household appliances, medical devices, media players, cameras, or any type of consumer electronics, such as, but not limited to, televisions, radios, lighting devices, tablets, laptops, or personal computers (PCs). A communication device may be a portable, handheld, computer-contained, or vehicle-mounted mobile device that is enabled to transmit voice and / or data via a wireless or wired connection.

[0048] User Equipment (UE): One type of communication device is a UE, which refers herein to any wireless communication device that can access (i.e., be served by) a wireless network (e.g., a cellular network). Some examples of wireless communication devices include, but are not limited to: 3GPP UE (i.e., a UE in a 3GPP network), Machine Type Communication (MTC) devices (also referred to herein as MTC UEs), and Internet of Things (IoT) devices (also referred to herein as IoT UEs). Such UEs may be or may be integrated into a mobile phone, a smart phone, a sensor device, an instrument, a vehicle, a home appliance, a medical device, a media player, a camera, or any type of consumer electronic product, such as, but not limited to, a television, a radio, a lighting device, a tablet, a laptop, or a PC. A UE may be a portable, handheld, computer-contained, or vehicle-mounted mobile device that is enabled to transmit voice and / or data via a wireless connection.

[0049] Relay UE: As used herein, a "relay UE" is a UE that, in addition to having communications to / from a RAN node (e.g., a base station), may also have communications to and from another UE, e.g., via a D2D link or a 3GPP side link. The other UE is referred to herein as a "remote UE". In addition, a relay UE may receive and send data and control signals on behalf of a remote UE with which it has a direct communication link. A relay UE is located in the vicinity of one or more remote UEs.

[0050] Remote UE: As used herein, a "remote UE" is a UE capable of D2D or 3GPP sidelink communication with a relay UE and direct communication with a base station. Typically, a remote UE is power constrained. A remote UE operates in a deep sleep mode (e.g., 3GPP idle mode) and can be awakened by a wake-up signal. Sometimes in this disclosure, the term "sensor UE" or "sensor node" is used to denote a type of remote UE that is extremely power constrained.

[0051] Network node: As used herein, a "network node" is any node that is part of the RAN or core network of a cellular communication network / system.

[0052] Low Power Wake-up Signal (LPWUS): As used herein, "LPWUS" is a special paging signal that is sent from a relay UE to one or more remote UEs to notify the one or more remote UEs to wake up from a deep sleep state (e.g., 3GPP idle mode). LPWUS has one or more characteristics (e.g., narrow bandwidth and / or simplified modulation and coding scheme) that enable the power cost for detecting LPWUS at the remote UE to be less than the power cost for detecting a traditional WUS from a base station at the remote UE. One or more characteristics of LPWUS enable detection at the remote UE via a low power receiver (e.g., an envelope detector, a comparator, and a time domain correlator).

[0053] Please note that the description given herein focuses on 3GPP cellular communication systems, and therefore, 3GPP terminology or terminology similar to 3GPP terminology is often used. However, the concepts disclosed herein are not limited to 3GPP systems.

[0054] Note that in the description of this document, reference may be made to the term "cell"; however, particularly with respect to 5G NR concepts, beams may be used instead of cells, and therefore it is important to note that the concepts described herein apply equally to both cells and beams.

[0055] Various aspects of the present disclosure are described below under separate headings. Although the embodiments described in each section can be used independently, the embodiments described in different sections below can also be combined.

[0056] I. Low Power Wake-up Signal (LPWUS) via Relay UE

[0057] As described above, systems and methods that provide energy-saving and robust solutions are needed to wake up UEs (e.g., ultra-low power UEs) and transmit data between these UEs and base stations. For ultra-low power IoT devices (e.g., wireless sensors), placing relay nodes is a method to expand the coverage of cellular networks. For example, Cheng, X., Du, D. Z., Wang, L. et al. Relay sensor placement in wireless sensor networks, Wireless Network 14, 347-355 (2008) https: / / doi.org / 10.1007 / s11276-006-0724-8 (2008) https: / / doi.org / 10.1007 / s11276-006-0724-8 (hereinafter referred to as the "Cheng article") proposed a solution for placing relay nodes in wireless sensor networks. All wireless sensors can be connected to relay nodes, which are more powerful and can transmit data over long distances. In addition, in U.S. Patent Application Publication No. 2020 / 0163017A1 (hereinafter referred to as the "'017 Application"), it is proposed to use a relay UE to send a wake-up signal (WUS) to a remote UE (e.g., an IoT UE). However, in addition to the WUS itself, when the IoT UE wakes up from deep sleep, the time synchronization between the IoT UE and the network needs to be reestablished, which requires further signal transmission / reception. The '017 Application does not address the reestablishment of this time synchronization.

[0058] Systems and methods for solving the above and / or other problems are disclosed herein. Embodiments of the solutions disclosed herein are based on the relayed wake-up of a remote UE (e.g., an IoT UE, such as, for example, a sensor) via a relay UE and subsequent data transmission between the relay UE and the remote UE. The reason is that the distance between the relay UE (e.g., selected based on coverage) and the remote UE is much shorter than the distance between the base station and the remote UE, making such systems more robust and reducing power consumption in the remote UE.

[0059] By introducing a relay UE, embodiments of the solution disclosed herein enable ultra-low power UEs to enter / exit deep sleep without directly communicating with a base station.

[0060] While the basic idea of ​​using a relay node to send a wake-up signal to an IoT UE is described in the '017 application, multiple aspects of the embodiments disclosed herein are proposed, which are potentially independent of each other, all supporting a more energy-efficient and robust system:

[0061] A first aspect relates to mechanisms and procedures for reestablishing time and frequency synchronization of a remote UE after deep sleep with the support of a relay UE. In this regard, two time / frequency resynchronization schemes (denoted herein as "TRS1" and "TRS2") are disclosed herein to achieve various synchronization accuracies by a remote UE with the support of a relay UE.

[0062] The second aspect involves the co-design of the time and frequency (time / frequency) synchronization signal and the low power wake-up signal (LPWUS) sent by the relay UE, so that the remote UE can be more energy-efficient when performing time / frequency synchronization and LPWUS detection.

[0063] The third aspect relates to optimizations in signaling between the relay UE and the remote UE, which can minimize power consumption at the remote UE due to the shorter distance. These optimizations may include, for example, optimization of the time offset between the synchronization signal and the LPWUS, optimization of the bandwidth of the LPWUS and / or the synchronization signal, optimization related to the type of modulation and coding used for the LPWUS (e.g., can be dynamically adjusted to be more robust / less robust depending on the distance between the relay UE and the remote UE), optimization related to transmit power, etc.

[0064] Embodiments of the solutions disclosed herein may enable better coverage for UEs in deep sleep (i.e., low power) mode, may enable lower uplink transmit power from remote UEs (e.g., IoT UEs) for wake-up sequences and communications, and / or may allow simpler and lower power wake-up receiver modes within the remote UEs.

[0065] in this regard, Figure 1 A system 100 in which an embodiment of the present disclosure can be implemented is shown. As shown, the system 100 includes a base station 102 and a relay UE 104, which operates as a proxy between the base station 102 and one or more remote UEs 106-1 to 106-N, which are collectively referred to as remote UEs 106 in this document, and are individually referred to as remote UEs 106. The remote UE 106 can be, for example, an ultra-low power IoT UE. The remote UE 106 operates in a deep sleep operation mode (e.g., an idle mode) until it is awakened by a WUS or a low power WUS (LPWUS). In addition, the remote UE 106 may be located in a non-coverage area (i.e., they may have a very poor radio frequency (RF) link to the base station 102, so that the remote UE 106 in the non-coverage area cannot receive a radio signal from the base station 102 or can only receive a limited radio signal). The non-coverage area may also be referred to as a shadow area.

[0066] The base station 102 is aware (e.g., due to an authentication process) of the remote UEs 106 in the area. The base station 102 may also identify UEs (or multiple UEs) near the remote UEs 106 as relay UEs 104 for these remote UEs 106. For example, the base station 102 may estimate the locations of the UEs within its coverage and select UEs close to the remote UEs 106 as relay candidates. In addition, based on measurement reports received from the UEs, the base station 102 establishes an understanding of the coverage / signal strength, the transmit power of the UEs, the mobility of the UEs, etc., and then determines the remote UEs 106 and the relay UEs 104 for these remote UEs 106. Thereafter, the base station 102 notifies the relay UE 104 and the remote UE 106 to pair. For example, the base station 102 may share the UE ID of the remote UE 106 with the relay UE 104 and / or inform the remote UE 106 of the relay ID of the relay UE 104. Once the base station 102 receives the pairing confirmation directly from each individual remote UE 106 (or in some embodiments via a relay UE 104 representing the individual remote UE 106), the base station 102 directly notifies the remote UEs 106 (or in some embodiments via the relay UE 104) that they can enter a deep sleep mode and, upon receiving a wake-up signal, need to communicate with the relay UE 104 or directly with the base station 102.

[0067] When the base station 102 wants to wake up and acquire data from a remote UE 106 (or a remote UE group 106), the base station 102 sends a WUS including an identifier (ID) of the remote UE 106 (or the remote UE 106 group). As described in detail below, the relay UE 104 operates to receive and decode the WUS on behalf of the remote UE 106 (or the remote UE 106 group). The relay UE 104 then generates and sends a LPWUS to wake up the remote UE 106 (or the remote UE 106 group) to which the WUS from the base station 102 is directed. In one embodiment, the LPWUS is encoded with the ID of the remote UE 106 (or the ID of the remote UE group) to be woken up.

[0068] Since the distance between the relay UE 104 and the remote UE 106 is much shorter than the distance between the base station 102 and the remote UE 106, the LPWUS sent from the relay UE 104 to the remote UE 106 can be greatly simplified by using a simple radio waveform (e.g., by encoding with on-off keying (OOK)) compared to the WUS sent by the base station 102, so that the power cost of the remote UE 106 detecting the LPWUS can be much smaller than the power cost of detecting the WUS from the base station 102. For example, an orthogonal frequency division multiplexing (OFDM) transmitter can be used to generate the LPWUS as an OOK pulse. An example of an OOK wake-up signal and a corresponding low power receiver is described in J. Moody et al., "A-76dBm 7.4nWakeup Radio With Automatic Offset Compensation", ISSCC 2018. After detecting LPWUS, remote UE 106 sends LPWUS ACK only to relay node 104 instead of base station 102 that initiates wake-up signaling, which enables reducing the RF transmission power of LPWUS ACK compared to the power required to send WUS ACK to base station 102.

[0069] In addition to LPWUS, embodiments are disclosed herein to establish time and frequency resynchronization for a remote UE 106 associated with LPWUS detection. Embodiments disclosed herein optimize time / frequency synchronization and LPWUS detection for UE power conservation.

[0070] Embodiments of the present disclosure consider one or more of the following aspects for relaying UE 104 to configure synchronization signals and LPWUS:

[0071] The waveform and bandwidth of the synchronization signal, for example, an OFDM multi-carrier signal or a single-carrier signal can be used as the synchronization signal,

[0072] The coding scheme of the synchronization signal, for example, the ID of the relay UE 104 may be encoded and carried by the synchronization signal,

[0073] The time offset between the synchronization signal and the LPWUS, and

[0074] The number of instances of the synchronization signal.

[0075] The following are two example methods for re-establishing time and frequency synchronization to achieve various levels of accuracy in the remote UE 106:

[0076] Time / frequency resynchronization scheme 1 (TRS1): The relay UE 104, which is already time / frequency synchronized with the network (e.g., with the base station 102), sends a synchronization signal and then sends the LPWUS. The remote UE 106 detects the synchronization signal and performs time / frequency resynchronization (e.g., with the relay UE 104) based on the detected synchronization signal. The synchronization signal may occupy a certain amount of frequency bandwidth and / or include multiple instances so that the time / frequency synchronization in the remote UE 106 can achieve a certain level of accuracy, so that the remote UE 106 can communicate directly with the base station 102 after being awakened after detecting the LPWUS.

[0077] Time / frequency resynchronization scheme 2 (TRS2): The relay UE 104, which is already time synchronized with the network (e.g., with the base station 102), sends a simpler synchronization signal (e.g., a single carrier synchronization signal) and then sends the LPWUS. A loose time synchronization is established between the remote UE 106 and the relay UE 104, so that the remote UE 106 can communicate directly with the relay UE 104 after being awakened after detecting the LPWUS. This scheme can lead to further optimization when only a limited amount of data needs to be transmitted.

[0078] In order to reduce the power consumed by the remote UE 106 to perform time / frequency synchronization and LPWUS detection, the time offset between the synchronization signal and the LPWUS can be optimized so that the remote UE 106 can keep its active duration as short as possible when detecting the synchronization signal and the LPWUS. Therefore, in one embodiment, the LWPUS follows the synchronization signal (i.e., the LPWUS starts in the OFDM symbol immediately following the OFDM symbol in which the synchronization signal or one of the multiple instances of the synchronization signal is transmitted).

[0079] Figure 21 is a flow chart illustrating the operation of a base station 102, a relay UE 104, and a remote UE 106 according to an embodiment of the present disclosure. Optional steps are represented by dashed boxes / lines. As shown in the figure, in this embodiment, the base station 102 sends a WUS containing the UE ID of the remote UE 106 (step 200). The relay UE 104 receives and decodes the WUS for the remote UE 106 (step 202). In other words, the relay UE 104 receives the WUS and decodes the WUS to determine that the WUS includes the UE ID of the remote UE 106. Then, the relay UE 104 generates and sends a synchronization signal to the remote UE 106, and then sends a LPWUS to the remote UE 106 (step 204). More specifically, in one embodiment, the relay UE 104 sends a synchronization signal. In addition, the relay UE 104 generates a LPWUS with a sequence based on the UE ID of the remote UE 106, and sends the LPWUS after the synchronization signal. In one embodiment, the relay UE 104 sends a single instance of the synchronization signal, and the LPWUS follows (e.g., immediately follows, e.g., in the next OFDM symbol) the single instance of the synchronization signal. In another embodiment, the relay UE 104 sends multiple instances or repetitions of the synchronization signal, and the LPWUS follows (e.g., immediately follows, e.g., in the next OFDM symbol) one of the instances of the synchronization signal (e.g., immediately follows the kth instance of the synchronization signal, where N instances of the synchronization signal are sent and 1≤k≤N). Note that the LPWUS may be broadcast to all remote UEs 106, or may be unicast to its targeted remote UEs 106 via corresponding D2D or 3GPP sidelinks.

[0080] At the remote UE 106, the remote UE 106 performs time / frequency synchronization according to the synchronization signal and detects (e.g., receives and decodes) the LPWUS (step 206). In one embodiment, the LPWUS is encoded using the UE ID of the remote UE 106, and thus, the detection of the LPWUS includes determining that the UE ID with which the LPWUS is encoded matches the UE ID of the remote UE 106. In another embodiment, the LPWUS is encoded using the group ID of the remote UE 106 (see below for details on the group WUS), and the detection of the LPWUS includes determining that the group ID with which the LPWUS is encoded matches the group ID of the remote UE 106. After detecting the LPWUS (and determining that the encoded UE ID or group ID matches its own UE ID or group ID), the remote UE 106 performs one or more actions, for example, to start operating (e.g., exiting a deep sleep mode and entering a connected mode) (step 206).

[0081] Once the remote UE 106 starts running, the remote UE 106 receives data from the relay UE 104 and / or sends data to the relay UE 104 via the corresponding side link (step 208). Note that for uplink data transmission, once the relay UE 104 receives data from the remote UE 106, the relay UE 104 transmits the data to the base station 102. Similarly, for downlink data transmission, once the relay UE 104 receives data for the remote UE 106 from the base station 102, the relay UE 104 transmits the data to the remote UE 106 via the side link.

[0082] The relay node 104 may then determine whether the remote UE 106 is to return to the deep sleep mode (step 210). If so, in one embodiment, the relay UE 104 sends a deep sleep sequence for the remote UE 106 (step 212). The relay UE 104 may confirm to the base station 102 (e.g., after receiving a deep sleep ACK from the remote UE 106) that the remote UE 106 is in the deep sleep state (step 214).

[0083] Now, further description of some aspects of the present disclosure related to time / frequency synchronization will be provided. In 3GPP LTE, the base station always broadcasts a cell reference signal (CRS), which UEs (e.g., remote UEs) can use to perform time / frequency synchronization. 3GPP NR does not specify such an always-on broadcast signal from the NR base station (i.e., gNB), but instead has a dedicated synchronization signal block (SSB) that is broadcast periodically from the NRBS. By detecting the SSB, the NR UE can perform time / frequency synchronization with the NRBS.

[0084] Assuming that the relay UE 104 always maintains time / frequency synchronization with the network (e.g., with the base station 102), in one embodiment, the relay UE 104 can send / broadcast a dedicated synchronization signal and then send / broadcast the LPWUS (e.g., in step 204). By receiving the synchronization signal, the remote UE 106 (or remote UE group 106) can perform frequency / time synchronization with the relay UE 104 so that it (or they) can correctly receive / decode the LPWUS following the synchronization signal.

[0085] Two example schemes for time / frequency resynchronization (denoted herein as TRS1 and TRS2) are as follows.

[0086] TRS1: When the remote UE 106 is expected to connect to the base station 102 after waking up, the relay UE 104 can configure its synchronization signal in the time and / or frequency domain and / or samples with better signal-to-noise ratio (SNR) (e.g., via the use of more complex modulation and coding schemes) to the remote UE 106. In one embodiment, in this case, the relay UE 104 can configure its synchronization signal to the remote UE 106 using a more complex sequence that occupies more RF resources in the time and / or frequency domain (e.g., the synchronization signal sent by the relay UE 104 can be a sidelink synchronization signal specified in 3GPP LTE / NR) to ensure high accuracy of time / frequency synchronization between the remote UE and the relay UE 104 and thus the base station 102. In other words, the amount of time and / or frequency domain resources occupied by the synchronization signal sent by the relay UE 104 (or multiple instances of the synchronization signal sent by the relay UE 104) may depend on whether the remote UE 106 communicates directly with the base station 102 after waking up or communicates with the relay UE 104 after waking up (i.e., communicates with the base station 102 via the relay UE 104). For the former, more time and / or frequency resources are used to provide a sufficient level of time / frequency synchronization accuracy.

[0087] Figure 3A An example of an LTE sidelink synchronization subframe including four synchronization symbols (symbols 1, 2, 11 and 12) is shown. Figure 3A In the example of FIG. 1 , the synchronization signal (or an instance of the synchronization signal) is transmitted in symbols 1, 2, 11, and 12. These four synchronization symbols may be encoded by the ID of the relay UE 104. The subframe is transmitted by the relay UE 104. In order to wake up the remote UE 106 by the relay UE 104, in this example, symbol 13 is allocated for the transmission of the LPWUS transmission (i.e., the LPWUS is transmitted in symbol 13 in this example). Figure 3A As shown, four synchronization symbols may be allocated with a higher bandwidth than LPWUS. In other words, the synchronization signal may use a bandwidth greater than that used for LPWUS.

[0088] Note that in an alternative example, LPWUS is transmitted in symbol 3 immediately following the second sync symbol (e.g., immediately following the second instance or repetition of the sync signal in symbol 2), as shown in FIG. Figure 3B This is to illustrate that, for example, LPWUS does not necessarily need to follow (e.g., in a subframe) the last instance of a synchronization signal, but may follow (e.g., in a subframe) some previous instance of a synchronization signal. When LPWUS is allocated between synchronization signals or between instances or repetitions of synchronization signals (e.g., such as Figure 3BAs shown in , in symbol 3), the remote UE 106 may first receive symbols 1 and 2 so that the remote UE 106 may synchronize to the relay UE 104 and receive the subsequent LPWUS. If the remote UE 106 finds that the LPWUS is targeted at the remote UE 106, it may perform further time / frequency synchronization by receiving additional synchronization signal instances or repetitions in symbols 11 and 12. Otherwise, it may skip receiving additional synchronization symbols.

[0089] To further optimize the power consumption of the remote UE 106, when the D2D SNR is high enough (e.g., above a predefined SNR threshold), the remote UE 106 may receive synchronization signals with only a portion of the bandwidth. For example, the remote UE 106 may receive synchronization signals with the same bandwidth as the LPWUS reception (e.g., Figure 3A and 3B 1 and 2 in the example of LPWUS). The remote UE 106 can still be synchronized and receive subsequent LPWUS. If the remote UE 106 finds that the LPWUS is targeted at the remote UE 106, it can further perform time / frequency synchronization by receiving the synchronization signal in symbols 11 and 12 with full bandwidth and wake up its main receiver. Otherwise, it can skip the reception of other synchronization symbols.

[0090] In one embodiment, the relay UE 104 may send additional synchronization signal(s) with a time offset from the LPWUS, wherein the time offset is configured according to the duration of the wake-up procedure of the remote UE 106. When the remote UE 106 completes its wake-up procedure (triggered by the LPWUS), it may receive the synchronization signal and perform time / frequency synchronization. The remote UE 106 may receive the synchronization signal and perform time / frequency synchronization. Since multiple symbols with a high bandwidth may be used as the synchronization signal, high synchronization accuracy may be achieved between the remote UE 106 and the relay UE 104 (and the base station 102). For example, after being awakened by the LPWUS, the remote UE 106 may start random access to establish a radio connection with the base station 102.

[0091] TRS2: When the remote UE 106 is not expected to connect to the base station 102 after waking up, the relay UE 104 can configure its synchronization signal to the remote UE 106 using a simpler sequence that occupies less RF resources in the time and / or frequency domain. Figure 4AAn example is shown, where a synchronization signal is sent in symbol 2 in a reduced bandwidth and an LPWUS is sent in symbol 3 in a reduced bandwidth. Using this simpler sequence, a loose time synchronization is established between the remote UE 106 and the relay UE 104 to serve their sidelink communication needs. The scheme can be further optimized when only a limited amount of data needs to be transmitted, and the relay UE 104 can act as a proxy for such data transmissions and service requests. For example, when a simple modulation scheme (e.g., OOK) is applied to transmit a small amount of data between the relay UE 104 and the remote UE 106, the sidelink can tolerate higher time / frequency synchronization errors (compared to TRS1), so the synchronization signal can be simplified, for example, a single tone signal can be used. Figure 4B Another example is shown. In this example, OOK modulation can be used, where the synchronization signal and LPWUS can be longer than 1 OFDM symbol.

[0092] Figure 5 Operations of a base station 102, a relay UE 104, and a remote UE 106-1 (in this example) are shown according to at least some of the embodiments described above. Optional steps are represented by dashed lines / boxes. As shown, the base station 102 sends a WUS (step 500), which includes the remote UE 106-1, is encoded with the remote UE 106-1, or otherwise indicates the remote UE 106-1. The relay UE 104 receives the WUS and determines that the WUS is intended for the remote UE 106-1 (step 501). The relay UE 104 sends a synchronization signal (step 502). The remote UE 106-1 performs time / frequency synchronization according to the synchronization signal (step 504). The relay UE 104 also generates and sends a LPWUS to the remote UE 106-1 (step 506). Note that the synchronization signal and the LPWUS can be according to any of the embodiments described above. The relay UE 106-1 detects (i.e., receives and decodes) the LPWUS (step 508). In response to detecting the LPWUS, the remote UE 106-1 performs one or more actions to wake up (step 510).

[0093] In one embodiment, the LPWUS has a bandwidth that is less than the bandwidth of the WUS from the base station 102 (e.g., the WUS of step 500). In one embodiment, the LPWUS has a bandwidth that is less than 180 kilohertz (kHz). In one embodiment, the LPWUS is transmitted in at least one OFDM symbol. In one embodiment, the synchronization signal and the LPWUS are transmitted in the same subframe. In one embodiment, sending the synchronization signal in step 502 includes sending two or more instances or repetitions of the synchronization signal. The repetitions may be sent in the time domain and / or the frequency domain. In one embodiment, at least one repetition of the synchronization signal is sent before the LPWUS. In one embodiment, all repetitions of the synchronization signal (e.g., in a subframe) are sent before the LPWUS (e.g., in the same subframe). In one embodiment, the LPWUS and two or more repetitions of the synchronization signal are sent in the same subframe.

[0094] In one embodiment, the bandwidth of the synchronization signal is greater than the bandwidth of the LPWUS. In one embodiment, the bandwidth of the synchronization signal is less than or equal to the full reception bandwidth of the remote UE 106-1. In one embodiment, the remote UE 106-1 is an IoT UE. In one embodiment, the full reception bandwidth of the remote UE 106-1 is 1.4 megahertz (MHz) or 180kHz.

[0095] In one embodiment, a single instance of the synchronization signal is sent. In one embodiment, a single instance of the synchronization signal is sent in at least one OFDM symbol immediately preceding the LPWUS. In one embodiment, the bandwidth of the synchronization signal is less than the full receive bandwidth of the remote UE 106-1. In one embodiment, the remote UE 106-1 is an IoT UE. In one embodiment, the full receive bandwidth of the remote UE 106-1 is 1.4 MHz or 180 kHz.

[0096] In one embodiment, the bandwidth of the synchronization signal is the same as the bandwidth of the LPWUS.

[0097] In one embodiment, at least one instance of the synchronization signal is sent in at least one OFDM symbol immediately preceding the OFDM symbol in which the LPWUS is sent.

[0098] In one embodiment, either or both of the bandwidth of the synchronization signal and the bandwidth of the LPWUS are functions of one or more metrics related to one or more characteristics of the wireless channel between the relay UE 104 and the remote UE 106 - 1 .

[0099] In one embodiment, either or both of the modulation or coding of the synchronization signal and the modulation or coding of the LPWUS are functions of one or more metrics related to one or more characteristics of the wireless channel between the relay UE 104 and the remote UE 106-1. In one embodiment, the transmit power used to transmit the synchronization signal or the LPWUS is a function of the modulation or coding of the synchronization signal or the LPWUS, respectively.

[0100] In one embodiment, the LPWUS is encoded with the ID of the remote UE 106-1 or the ID of the remote UE 106 group.

[0101] In one embodiment, the relay UE 104 unicasts the synchronization signal and / or LPWUS to the remote UE 106-1. In another embodiment, the relay UE 104 broadcasts the synchronization signal and / or LPWUS to multiple remote UEs 106 including the remote UE 106-1.

[0102] It should be noted that although the embodiments described herein focus on LPWUS, the embodiments can be extended to be applied additionally or alternatively to a go to sleep (GTS) signal sent by the base station 102 and a low power GTS (LPGTS) signal sent from the relay UE 104 to the remote UE 106-1 to put the remote UE 106-1 into a deep sleep state.

[0103] II. Group wakeup of relays

[0104] Existing wake-up mechanisms, including the WUS signaling mechanism defined in 3GPP LTE and the WUS signaling mechanism via relay UE proposed in the '017 application, assume one-to-one wake-up signaling (from the base station to a single device at a time). It can be said that these wake-up mechanisms are suboptimal because they require the base station to run a large number of consecutive wake-up procedures (depending on the number of IoT UEs), resulting in increased latency and energy consumption.

[0105] Disclosed herein are systems and methods for solving the above-mentioned problems and / or other problems associated with traditional wake-up mechanisms. More specifically, disclosed herein are systems and methods for group wake-up of relays, i.e., wake-up signaling of relays for a group of remote UEs (e.g., an IoT UE group). Group wake-up of relays is more efficient in terms of latency and energy usage than existing wake-up mechanisms that rely on one-to-one wake-up signaling. In addition, due to the types of tasks and service functions of IoT UEs, they may exhibit very high similarity patterns in terms of geographical distribution, business type, and radio propagation status. Therefore, similar IoT UEs can be grouped, and wake-up signals can be executed in a group-by-group manner, thereby improving wake-up signaling efficiency.

[0106] Disclosed herein is an embodiment of relayed group wakeup for a remote UE group (e.g., an IoT UE group, such as a sensor group) and subsequent data transmission between a base station and the remote UE via a relay UE. The basic principle of relayed wakeup is that the distance between the relay UE and the remote UE (or remote UE group) is much shorter than the distance between the base station and the remote UE (or remote UE group), making such a system more robust and resulting in lower power consumption in the remote UE (or remote UE group). The basic principle behind group wakeup is that remote UEs may have similarities (e.g., in terms of service function type, business model, geographical distribution, etc.), so similar remote UEs can be grouped together and wakeup signaling can be performed in a group-by-group manner. This improves the efficiency of the wakeup process in terms of delay and energy used for signaling without affecting the normal operation of each remote UE. In addition, since the relay UE manages the wakeup process via side link communication, the overhead for the base station is greatly reduced.

[0107] By introducing relay nodes and a group wake-up mechanism, embodiments of the present disclosure enable ultra-low power devices to enter / exit deep sleep without directly communicating with a base station during relay wake-up signaling or during resynchronization signaling after an initial relay wake-up signal.

[0108] This document describes various aspects related to group wakeup of relays. These aspects may potentially be used independently of each other, but may be used in combination. These aspects support a more energy-efficient and robust system enabled by group wakeup of relays. These aspects include:

[0109] 1. Relayed group wake-up, where the relay UE manages the wake-up, resynchronization and potential support for processing service requests for a group of remote UEs.

[0110] 2. Guidance for grouping remote UEs based on different similarity measures.

[0111] 3. Dynamically assign one (or more) groups of remote UEs to relay UEs among multiple candidate relay UEs.

[0112] 4. Mechanisms and procedures for re-establishing time synchronization of a group of remote UEs after deep sleep.

[0113] 5. Hierarchical wake-up, in which additional relay layers (multiple layers) are introduced. This further improves the robustness and coverage of the system.

[0114] 6. Overlapping wakeup groups.

[0115] Embodiments of the present disclosure related to wake-up of relays may provide one or more of the following advantages:

[0116] Enables better coverage for devices entering deep sleep,

[0117] Enables reduction of uplink transmit power from remote UEs after wake-up,

[0118] · Causes repeated wake-up requests via selective wake-up for unresponsive remote UEs, providing more robust support for ultra-low power devices entering deep sleep,

[0119] • Allows for a simpler, lower power wake-up receiver mode within a WUS receiver that can also wake up based on a WUS from a base station.

[0120] Embodiments of the present disclosure related to group wake-up may provide one or more of the following advantages:

[0121] Improves the efficiency of the wake-up process by minimizing signaling overhead via simultaneous wake-up signaling to groups of nodes,

[0122] A differentiated wake-up solution is achieved by grouping remote UEs and assigning the groups to different relay UEs,

[0123] • Reduced signaling overhead via (multicast) group resynchronization rather than an individual node-by-node approach.

[0124] Embodiments of the present disclosure related to hierarchical wake-up may provide one or more of the following advantages:

[0125] Ability to create more robust systems with longer reach into areas not covered by base stations,

[0126] • Enable sequential wake-up, where a remote UE in deep sleep can further manage the wake-up of other units when it has been woken up.

[0127] in this regard, Figure 6A system 600 in which relayed group wake-up signaling can be used according to an example embodiment of the present disclosure is shown. As shown, the system 600 includes a base station 602 and a relay UE 604, which operates to provide relayed group wake-up signaling for a group 605 of remote UEs 606-1 to 606-N, which are collectively referred to as remote UEs 606 in this document and individually referred to as remote UEs 606. The relay UE 604 also acts as a proxy between the base station 602 and the remote UE 606. The remote UE 606 can be, for example, an ultra-low power IoT UE. The remote UE 606 operates in a deep sleep operation mode (e.g., idle mode) until it is awakened by a WUS. In addition, the remote UE 606 may be in a non-coverage area (i.e., they may have a very poor RF link to the base station 602, so that the remote UE 606 in the non-coverage area cannot receive a radio signal from the base station 602 or can only receive a limited radio signal). The non-coverage area may also be referred to as a shadow area. In a relayed group wake-up, the relay UE 604 is the link between the base station 602 and the remote UE 606 in the group 605, wherein the remote UE 606 may enter a deep sleep mode and needs to be activated by a wake-up signal. The relay UE 604 then manages the wake-up of the remote UE 606 among other things.

[0128] The base station 602 knows (e.g., due to an authentication process) the remote UE 606 and optional remote UEs 614, 616, 618, and 620 in a certain area. The base station 602 can also identify a nearby UE (or multiple UEs) as candidate relay UEs (multiple) for these remote UEs 606, 614, 616, 618, and 620. For example, the base station 602 can estimate the location of the UEs within its coverage area and select UEs close to the remote UEs 606, 614, 616, 618, and 620 as candidate relay UEs. If a remote UE is introduced into the system 600 and does not have a direct connection with the base station 602, the remote UE can search for potential relay UEs. This can be solved by, for example, a conventional D2D peer discovery process. For example, the remote UE can wake up periodically and listen to a reference signal (e.g., a synchronization signal) from a relay UE. If it detects the reference signal and decodes the relay ID, it can establish a D2D or side link channel to the relay UE.

[0129] In addition, based on the measurement reports received by the base station 602, the base station 602 can build up an understanding of the coverage / signal strength, UE transmit power, UE mobility, etc., and then use this information to create a group 605 of remote UEs 606 and select a relay UE 604 for the group 605 of remote UEs 606. The base station 602 notifies both the relay UE 604 and the remote UE 606 of the pairing. For example, the base station 602 can send the UE ID of the remote UE 606 to the relay UE 604 and / or notify the remote UE 606 of the relay ID of the relay UE 604. In addition, the base station 602 can send the group ID of the group 605 of remote UEs 606 to the relay UE 604, and in some embodiments, to the remote UEs 606 in the group 605. Once the base station 602 receives the pairing confirmation directly from each remote UE 606 (or in some embodiments via a relay UE 604 representing each remote UE 606), the base station 602 notifies the remote UEs 606 via the relay UE 604 that they can enter deep sleep mode and, upon receiving a wake-up signal, should communicate with the relay UE 604 (whose relay ID was shared during pairing).

[0130] When the base station 602 wishes to wake up the group 605 of remote UEs 606 and obtain data from the group, either by an explicit request from the base station 602 or because the relay UE acts as a proxy for some service and identifies that the group 605 of remote UEs 606 needs to be woken up, the relay UE 604 wakes up the group 605 of remote UEs 606. The relay UE 604 checks whether each remote UE 606 in the group 605 is woken up and establishes time synchronization. More specifically, in one embodiment, the base station 602 sends a WUS including the group ID of the group 605 of remote UEs 606. This WUS is referred to as a "group WUS" in this article. As described in detail below, the relay UE 604 operates to receive and decode the group WUS on behalf of the group 605 of remote UEs 606. Then, the relay UE 104 generates and sends a WUS (e.g., LPWUS as described in Section I above) to each subset of at least a subset of the group 605 of remote UEs 606, so as to wake up the remote UEs 606 in the group 605 for which the group WUS from the base station 602 is directed. Note that in one embodiment, the relay UE 604 sends a WUS (e.g., LPWUS) to each remote UE 606 in the group 605. In another embodiment, the relay UE 604 first listens for ACKs for the group WUS from the remote UEs 606 in the group 605, and sends a WUS (e.g., LPWUS) only to the remote UEs 606 in the group 605 for which it does not detect ACKs. In one embodiment, each LPWUS sent by the relay UE 604 is encoded with the UE ID of the corresponding remote UE 606. In addition, in one embodiment, the relay UE 604 supports the establishment of time resynchronization for the remote UEs 606 (e.g., by sending both a synchronization signal and an LPWUS to each remote UE 606, as described in Section I above). Once the remote UEs 606 in the group 605 are awake, the relay UE 604 provides data transmission between the base station 602 and the remote UEs 606.

[0131] Note that a suitable candidate relay UE is a UE that is in acceptable radio channel conditions relative to the base station 602. A suitable candidate relay UE itself should not enter a deep sleep state (although this is not mandatory), and it should support a signaling scheme for waking up other UEs. In addition, a suitable candidate relay UE should have a good connection with the remote UEs 606 in the group 605 that will enter a deep sleep state. The more remote UEs 606 that have good coverage provided by the candidate relay UE, the greater the chance that the candidate relay UE actually acts as a relay UE, although it is limited by the maximum number of remote UEs that this relay UE can handle. There are different standards and methods for how to assign multiple remote UEs to a group for group wake-up, which will be described in detail below.

[0132] In some embodiments, when the remote UE 606 wakes up, it can perform a sanity check to determine whether the paired relay UE 604 is responding to its request. In some other embodiments, the remote UE 606 can skip this process and directly initiate communication with the relay UE 604, and the remote UE 606 obtains the relay ID of the relay UE 604 before entering deep sleep.

[0133] It should be noted that there are several different group wakeup scenarios where additional mechanisms are proposed to further optimize energy efficiency. These additional mechanisms may include any one or more of the following:

[0134] In one embodiment, the remote UEs 606 in the group 605 communicate with the base station 602 or network services via the relay UE 604 and take actions based on the request, such as, for example, probing measurement data, receiving new settings or requesting any service via the communication channel. Each remote UE 606 has a dedicated communication channel to the base station 602 via the relay UE 604.

[0135] In one embodiment, the remote UEs 606 in the group 605 are treated as a group by the network-based service. Individual group commands or data transmissions are sent from the base station 602 to the relay UE 604, which acts as a proxy for the group 605. Instead of relaying from the base station 602 individually to each remote UE 606 in the group 605, the relay UE 604 multicasts the command / transmission to all remote UEs 606 in the group 605. This is similar to multicast support, but is managed by the relay UE 604 and optionally further includes an acknowledgement from the remote UE 606.

[0136] In one embodiment, the relay UE 604 acts completely as a proxy for service requests. When the remote UEs 606 in the group 605 are awakened, the relay UE 604 pushes data to or polls data from the remote UEs 606 in the group 605, and then commands them to return to a deep sleep state.

[0137] In one embodiment, the grouping of remote UEs 606 may be based on similarity of UE roles, traffic patterns, and spatial / geographical distribution, and / or other criteria. The spatial / geographical distribution criteria may be beneficial for differentiated wake-up signaling for different groups with different spatial / geographical characteristics, i.e., the relay UE 604 will send signals to the farther group or shadow group with more robust signaling or higher transmit power. UE grouping based on geographic proximity may also provide better beamforming in the relay UE 604 to improve WUS robustness and / or minimize interference with neighboring groups.

[0138] a. Grouping of remote UEs and allocation of relay UE groups

[0139] The establishment of the group can be performed in the designation of a relay UE (e.g., relay UE 604) so ​​that a group wake-up request from the base station 602 to the relay UE (e.g., relay UE 604) initiates the process of waking up the remote UE group (e.g., group 605 of remote UE 606). In another embodiment, the base station 602 can request the wake-up of the group by providing the identification of those remote UEs to be awakened. In both scenarios, the relay UE 604 is responsible for the complete wake-up sequence of all remote UEs 606 in the group 605, including time resynchronization. In one embodiment, if there are remote UEs 606 that are not awakened, the relay UE 604 sends information about this situation to the base station 602, and then the base station 602 performs one or more actions to migrate these remote UEs 606 or the group 605 of remote UEs 606 to another relay UE.

[0140] With respect to grouping, remote UEs may have natural similarities. One or more of the following criteria may be applied to the similarity measure to group (also referred to as cluster) the remote UEs according to some degree in the similarity measure:

[0141] Tasks (i.e. service functions performed by IoT UE)

[0142] Business model

[0143] Geographical distribution

[0144] • The quality of radio propagation experienced (e.g., severe radio shadowing).

[0145] Please note that the above criteria are examples only. Additional or alternative criteria may be used to group remote UEs.

[0146] Each defined group of remote UEs is assigned to the relay UE. Note that a maximum of one remote UE group may be assigned to the relay. However, in another embodiment, a maximum of M remote UE groups may be assigned to the relay UE (e.g., relay UE 604), where M is greater than or equal to 1. The value of "M" may be based on criteria such as, for example, the maximum number of remote UEs in a defined group, the number of UEs in a group assigned to the relay UE, one or more capabilities of the relay UE, information about expected traffic patterns for the remote UE group assigned to the relay UE, etc. The remote UE group(s) are assigned to the relay UE based on one or more of the following factors:

[0147] The number of available (candidate) relay UEs;

[0148] The geographical distribution of the (candidate) relay UEs, e.g., distances between each other, distances from the base station 602, distances from the center of each group of remote UEs, etc.;

[0149] Capabilities of the (candidate) relay UE, e.g. reliability, signaling support, battery power, computing power, etc.

[0150] If the remote UEs are used for different purposes, they are grouped according to service, so UEs with the same function or that need to be activated at similar times are grouped together. Then, a relay UE can be defined to act as a proxy for a certain function, and then the relay UE is naturally related to a certain remote UE group.

[0151] In principle, the grouping of remote UEs and the allocation of remote UEs to relay UEs can be solved jointly for optimization.Since there may be many reasons to form groups, it is not within the scope of the present disclosure to limit the embodiments described herein to one or a few of them.

[0152] like Figure 7 As shown, in one embodiment, the grouping process includes the following steps:

[0153] Step 700: The base station 602 performs an initial process to identify candidate relay UEs (eg, candidate relay UEs 608, 610, 612 and ultimately the relay UE 604 selected for the group 605). The base station 602 may identify the candidate relay UEs, for example, using 3GPP proximity service functionality.

[0154] Step 702: Based on system requirements, the base station 602 defines groups of remote UEs, each group being served by a single relay UE. Groups may be defined based on, for example, service functions, geographical distribution of nodes, traffic patterns, wake-up frequency, whether wake-up is triggered by a single external event, and / or whether the relay UE will act as a service agent for multiple remote UEs. Since there are many different possible reasons for forming groups, any desired criteria may be used to group remote UEs.

[0155] Step 704: The base station 602 assigns the relay UE to the defined remote UE group (e.g., Figure 6 In the example of , the relay UE 604 is assigned to the group 605 of the remote UE 606).

[0156] Step 706: The base station 602 notifies the relay UEs of the remote UE groups (including, for example, corresponding group IDs) that have been assigned to these relay UEs, and the relay UEs then confirm with the remote UEs in the corresponding group.

[0157] b. Group wake-up solutions and signaling mechanisms (multiple)

[0158] Figure 8The operation of a group 605 of a base station 602, a relay UE 604, and a remote UE 606 according to an example embodiment of the present disclosure is shown. Note that optional steps are represented by dashed lines / boxes. As shown, the base station 602 performs processes for grouping remote UEs and relay UE selection for the defined group, for example, as described above with respect to Figure 7 Alternatively, the groups of remote UEs and the relay UEs assigned to these groups may be defined in another way, for example, predefined or preconfigured by appropriate configuration in the UE. In this example, a group 605 of remote UEs 606 is defined and assigned to relay UE 604.

[0159] When the group 605 of remote UEs 606 needs to be woken up, the base station 602 sends a group WUS (step 802). The group WUS is encoded with or otherwise includes a group ID assigned to the group 605 of the remote UEs 606. After detecting the group WUS for the group 605 of the remote UEs 606, the relay UE 604 performs a group wake-up procedure, thereby performing wake-up of the remote UEs 606 in the group 605 (step 804). In one embodiment (see, e.g., Fig. 9 ), the relay UE 604 sends a separate WUS (e.g., a separate LPWUS) to each remote UE 606 in the group 605 (or to the entire group at once), and optionally listens for a WUS ACK from the remote UE 606. In another embodiment (see, for example, the following description Fig.10 ), the relay UE 604 first listens for a group WUS ACK from the remote UE 606 in the group 605. The remote UE 606 sends a group WUS ACK when the group WUS from the base station 602 is detected at the remote UE 606. Then, the relay UE 604 sends an individual WUS (e.g., an individual LPWUS) to each remote UE 606 in the group 605 for which the relay UE 604 did not detect the group WUS ACK.

[0160] The relay UE 604 then notifies the base station 602 of the result of the group wake-up process (step 806). The result may include, for example, information indicating that the remote UE 606 (if any) was not successfully awakened. Although not shown, the base station 602 may perform one or more actions based on the notification of step 806. For example, if all remote UEs 606 in the group 605 are successfully awakened, the base station 602 may continue to send data or commands to the group 605 of remote UEs 606. As another example, if any remote UE 606 in the group 605 is not successfully awakened, the base station 602 may move those remote UEs 606 (i.e., the UEs that were not successfully awakened) or the group 605 of remote UEs 606 to a new relay UE.

[0161] Fig. 9 is a more detailed illustration of an exemplary embodiment according to the present disclosure Figure 8 In other words, Fig. 9 9 is a flow chart illustrating the operation of the relay UE 604 performing the group wake-up procedure according to an embodiment of the present disclosure. Optional steps are represented by dashed lines / boxes. As shown, the relay UE detects the group WUS for the group 605 of the remote UE 606 (step 900), and decodes the group WUS to obtain the group ID encoded in the group WUS (step 902). For example, the group WUS can be similar to a conventional WUS, but encoded with the group ID of the group 605 of the remote UE 606.

[0162] In response to detecting a group WUS encoded using the group ID of the group 605 of remote UEs 606, the relay UE 604 generates and sends a WUS (e.g., LPWUS) to each remote UE 606 in the group 605 (step 903). Note that the IDs of the remote UEs 606 in the group 605 may be stored in the relay UE 606, for example, in a lookup table based on the group ID. As described in Section I above, in an embodiment in which the relay UE 604 sends an LPWUS to each remote UE 606, the relay node 604 may send a synchronization signal in addition to sending the LPWUS to enable the remote UE to which the LPWUS is sent to (re)synchronize. This is true for any embodiment described herein in which the relay UE 604 sends an LPWUS to the remote UE 606.

[0163] Then, the relay UE 604 sets one or more timers to receive WUS ACK from the remote UE 606 in the group 605 (step 904). In one embodiment, a single timer is set for the group 605. In another embodiment, a separate timer is set for each remote UE 606 in the group 605, wherein different remote UEs 606 may have different timer values ​​or the same timer value. While the timer is running, the relay UE 604 monitors the WUS ACK from the remote UE 606 in the group 605 (step 906).

[0164] Once the timer has expired (step 908, yes), the relay UE 604 determines whether any ACK is missing (step 910). In other words, the relay UE 604 determines whether a WUS ACK from any remote UE 606 in the group 605 is not detected. If not missing (step 910, no), the relay UE 604 notifies the base station 602 that the wake-up of all remote UEs 606 in the group 605 is successful (step 912). If a WUS ACK of one or more remote UEs 606 in the group 605 is not detected (step 910, yes), the relay UE 604 increases the attempt count index (step 914) and determines whether the maximum number of wake-up attempts has been reached (step 916). The maximum number of attempts may be predefined or preconfigured and is an integer value greater than or equal to 1. Of course, the maximum number of wake-up attempts has an upper limit related to a certain defined or configured maximum acceptable amount of time that can be used for wake-up.

[0165] If the maximum number of wake-up attempts has not been reached (step 916, no), the relay UE 604 identifies the remote UE 606 in the group 605 for which the WUS ACK has not been received (step 918). The relay UE 604 resends the WUS signal (e.g., LPWUS) to the identified remote UE 606 and resets the timer (step 920). Again, as described in Section I above, in an embodiment in which the relay UE 604 sends a synchronization signal to each identified remote UE 606, the relay node 604 may send a synchronization signal in addition to the LPWUS to enable the remote UE to which the LPWUS is sent to be (re)synchronized. This is true for any embodiment described herein in which the relay UE 604 sends the LPWUS to the remote UE 606.

[0166] After sending a WUS (e.g., LPWUS) to each identified remote UE 606, the process then returns to step 906, where the relay UE 604 monitors for a WUSACK from the remote UE 606 to which the WUS was (re)sent in step 920. The process continues until a WUS ACK is received from all remote UEs 606 in the group 605, in which case the relay node sends a notification in step 912, or until the maximum number of attempts is reached. If the maximum number of attempts has been reached (step 916, yes), the relay UE 604 notifies the base station 602 of the group wake-up failure (step 922). The failure notification may include information indicating the remote UEs 606 in the group 605 that have not been successfully awakened.

[0167] Note that if the relay UE 604 is assigned multiple remote UE groups, the relay UE 604 may perform the following operations for each group sequentially: Fig. 9 or execute it in parallel for all groups Fig. 9 process.

[0168] Fig.10 is a more detailed illustration of another exemplary embodiment according to the present disclosure. Figure 8 In other words, Fig.10 604 performs a group wake-up procedure according to an embodiment of the present disclosure. Optional steps are represented by dashed lines / boxes. As shown, the relay UE detects a group WUS for a group 605 of a remote UE 606 (step 1000), and decodes the group WUS to obtain a group ID encoded in the group WUS (step 1002). For example, the group WUS may be similar to a conventional WUS, but encoded using the group ID of the group 605 of the remote UE 606. In response to detecting a group WUS encoded using the group ID of the group 605 of the remote UE 606, the relay UE 604 sets one or more timers to receive a group WUS ACK from the remote UE 606 in the group 605 (step 1004). Note that the remote UE 606 in the group may be stored in the relay UE 606, for example, in a lookup table based on the group ID. In one embodiment, a single timer is set for the group 605. In another embodiment, a separate timer is set for each remote UE 606 in the group 605, wherein different remote UEs 606 may have different timer values ​​or the same timer value. While the timer is running, the relay UE 604 monitors the group WUS ACK from the remote UEs 606 in the group 605 (step 1006).

[0169] Once the timer has expired (step 1008, yes), the relay UE 604 determines whether any ACK is missing (step 1010). In other words, the relay UE 604 determines whether it has not detected a group WUS ACK from any remote UE 606 in the group 605. Note that the remote UE 606, upon detecting the group WUS sent by the base station 602, sends (e.g., broadcasts) a group WUS ACK including the UE ID of the remote UE 606. If there is no lack of any ACK (step 1010, no), the relay UE 604 notifies the base station 602 that the wake-up of all remote UEs 606 in the group 605 is successful (step 1012). If a group WUS ACK for one or more remote UEs 606 in the group 605 is not detected (step 1010, yes), the relay UE 604 increases the attempt count index (step 1014) and determines whether the maximum number of wake-up attempts has been reached (step 1016). The maximum number of attempts may be predefined or preconfigured and is an integer value greater than or equal to 1. Of course, the maximum number of wake-up attempts has an upper limit related to some defined or configured maximum acceptable amount of time available for wake-up. In one embodiment, the maximum number of wake-up attempts is configured by the network (e.g., by the base station 602). In one embodiment, the maximum number of wake-up attempts is preconfigured prior to receiving the group WUS. Any configuration changes after the group WUS is received are only performed for the next iteration of the group WUS. It should also be noted that the number of attempts is reset after decoding the group WUS and before the initial transmission of the LPWUS.

[0170] If the maximum number of wake-up attempts has not been reached (step 1016, no), the relay UE 604 identifies the remote UE 606 in the group 605 for which the wake-up ACK has not been received (or responds to the group WUS, or some previous (LP) WUS attempts of the relay UE 604) (step 1018). The relay UE 604 (re)sends a WUS signal (e.g., LPWUS) to the identified remote UE 606 and resets the timer (step 1020). Note that the timer can be reset to the same value used for monitoring after detecting the group WUS, or reset to a value different from the value used for monitoring after detecting the group WUS. In one embodiment, for each iteration, the transmit power used by the relay UE 604 to resend the WUS is increased relative to the transmit power used for the previous iteration. As described in Section I above, in embodiments where the relay UE 604 sends LPWUS to each identified remote UE 606, the relay node 604 may send a synchronization signal in addition to the LPWUS to enable the remote UE to which the LPWUS is sent to (re)synchronize. This is true for any of the embodiments described herein where the relay UE 604 sends LPWUS to the remote UE 606.

[0171] After sending a WUS (e.g., LPWUS) to each identified remote UE 606, the process returns to step 1006, where the relay UE 604 monitors for a WUSACK from the remote UE 606 to which the WUS was (re)sent in step 1020. The process continues until a wakeup ACK is received from all remote UEs 606 in the group 605, in which case the relay node sends a notification in step 1012, or until the maximum number of attempts is reached. If the maximum number of attempts has been reached (step 1016, yes), the relay UE 604 notifies the base station 602 of a group wakeup failure (step 1022). The failure notification may include information indicating that the remote UEs 606 in the group 605 have not been successfully awakened.

[0172] Note that if the relay UE 604 is assigned multiple remote UE groups, the relay UE 604 may perform the following operations for each group sequentially: Fig.10 or execute it in parallel for all groups Fig.10 process.

[0173] c. Group resynchronization

[0174] In one embodiment, in addition to sending the WUS to the remote UEs 606 in the group 605, the relay UE 604 may also transmit (e.g., unicast or broadcast) a set of time / frequency synchronization signals to the group 605 of remote UEs 606, e.g., via a side link or D2D channel. By detecting the synchronization signals, the remote UEs 606 may perform time / frequency synchronization, e.g., to the relay UE 604. In one embodiment, the synchronization signals are encoded with the relay ID of the relay UE 604 so that the remote UEs 606 may also decode the group ID and understand which relay UE they are synchronized with. In addition, the synchronization signals and the LPWUS may be bundled together and transmitted by the relay UE 604 (see, e.g., the description of the synchronization signals and the LPWUS in Section I above).

[0175] d. Graded awakening

[0176] In one embodiment, hierarchical wake-up (i.e., hierarchical relay wake-up) is provided. For hierarchical wake-up, at least one further relay level is introduced. This means that the relay UE that manages the wake-up of the remote UE group (or a single remote UE as described in Section I above) is not directly connected to the base station. Instead, there is another relay node between the relay UE and the base station. This concept is key to further improve the robustness and coverage of the system. This feature is very useful in different scenarios:

[0177] In areas where some remote UEs are difficult to reach even with designated relay UEs, one of the non-battery powered remote UEs may be permanently or temporarily assigned as a second relay UE to ensure better wake-up coverage in that area.

[0178] Temporarily, a remote UE with good battery condition can act as a wake-up relay for a further remote UE or a remote UE with particularly bad RF conditions. This second relay UE can be always on, meaning it will not go into deep sleep itself, or it can be allowed to go into deep sleep, but can act as a relay to support a further remote UE after being woken up.

[0179] Fig.11 An example of a system 1100 for providing hierarchical wake-up according to an embodiment of the present disclosure is shown. As shown, the system 1100 includes a base station 1102, a first relay UE 1104-1, and a second relay UE 1104-2. A remote UE group 1106-2-1 to 1106-2-N2 (generally referred to as remote UE 1106-2 herein, and individually referred to as remote UE 1106-2) is assigned to the second relay UE 1104-2. Optionally, another group of remote UEs 1106-1-1 to 1106-1-N1 (generally referred to as remote UE 1106-1 herein, and individually referred to as remote UE 1106-1) is assigned to the first relay UE 1104-1. In operation, when group 2 needs to be woken up, the base station 1102 sends a group WUS encoded with the group ID of group 2. The first relay UE 1104-1 relays the group WUS to the second relay UE 1104-2. The second relay UE 1104-2 detects the group WUS, decodes the group WUS to determine that it is for group 2, and performs the group wake-up procedure for group 2, as described above, for example, with respect to Fig.10 or Fig. 9 .

[0180] In another embodiment, a larger group of remote UEs may be defined, including Fig.11 In this case, a single group ID is assigned to the larger group. In other words, Fig.11 The groups 1 and 2 shown in FIG. 1 have the same group ID. In this case, when the larger group needs to be woken up, the base station 1102 sends a group WUS encoded with the group ID of the larger group. The first relay UE 1104-1 relays the group WUS to the second relay UE 1104-2. In addition, the first relay UE 1104-1 decodes the group WUS and determines that the group ID matches the group ID of the remote UE 1106-1 in group 1. The first relay UE 1104-1 then performs a group wake-up procedure for the remote UE 1106-1 in group 1, as described above, for example, with reference to FIG. Fig.10 or Fig. 9The second relay UE 1104-2 detects the group WUS, decodes the group WUS to determine the group ID, determines that the group ID matches the group ID of the remote UE 1106-2 in group 2, and performs a group wake-up procedure for group 2, as described above, e.g., with reference to Fig.10 or Fig. 9 .

[0181] e. Overlapping groups

[0182] In one embodiment, there may be overlapping groups of remote UEs for group wakeup. In this case, the remote UEs belong to two or more different groups at the same time. In the extreme case, there is a group of remote UEs that all belong to groups hosted by two separate relay UEs. A and R B Managed two groups G A and G B . Note, however, that there are many different configurations and scenarios involving more than two groups and groups that only partially overlap. All such configurations and scenarios can be used.

[0183] One advantage of overlapping groups is that overlapping groups can be used to provide redundancy and thus robustness to the system. For example, if conditions change, the likelihood that one of the relay UEs can contact a particular remote UE increases if the remote UE belongs to two or more groups assigned to different relay UEs. Another benefit is that it is not as critical for the remote UE to migrate to a new relay UE when the remote UE is not awakened by the WUS on its relay UE. This is particularly beneficial if the remote UE would migrate back and forth between the same two (or more) relay UEs under different conditions. Using overlapping groups, this remote UE can belong to two (or more) groups assigned to two (or more) relay UEs. Another advantage is that when relay UEs act as proxies for certain types of services, they can connect to all remote UEs belonging to those services, and since the remote UE may support multiple different services or functions, the remote UE can belong to multiple different groups for the multiple different services or functions it supports. Another advantage is that overlapping groups can enable backup of relay UEs. So, if, for example, the R in the scenario above A If it fails for some reason, there is already an R that supports the same group B Can be activated.

[0184] In this regard, Fig.12An example of a system 1200 for providing group wakeup of relays with overlapping groups according to an embodiment of the present disclosure is shown. As shown, the system 1200 includes a base station 1202, a first relay UE 1204-1, a first group (group 1) of remote UEs 1206-1, 1206-2, and 1206-3 assigned to the first relay UE 1204-1, a second relay UE 1204-2, and a second group (group 2) of remote UEs 1206-3, 1206-4, and 1206-5 assigned to the second relay UE 1204-2. Therefore, in this example, group 1 and group 2 overlap, and specifically, remote UE 1206-3 belongs to both group 1 and group 2. Thus, the remote UE 1206-3 may receive a WUS (eg, LPWUS) from the first relay UE 1204-1 as part of group wakeup for group 1 and receive a WUS (eg, LPWUS) from the second relay UE 1204-2 as part of group wakeup for group 2.

[0185] While overlapping groups provide robustness and flexibility, they also introduce a key complexity. Overlapping groups mean that, in some embodiments, remote UEs (e.g., Fig.12 The remote UE 1206-3) may receive WUS from multiple relay UEs. In this regard, Fig.13 is a flow chart illustrating the operation of a remote UE that is simultaneously in two or more groups according to an embodiment of the present disclosure. Optional steps are represented by dashed lines / boxes. For this description, use Fig.12 As an example, the remote UE 1206-3 of the first relay UE 1204-1 is taken as an example. As shown, the remote UE 1206-3 receives a WUS (e.g., LPWUS) from the first relay UE 1204-1 (step 1300). After the remote UE 1206-3 is activated based on the WUS from the first relay UE 1204-1, the remote UE 1206-3 does not respond to other relay UEs during its initialization / resynchronization phase (step 1302). In other words, the remote UE 1206-3 does not respond to other relay UEs when it wakes up in response to the WUS from the first relay UE 1204-1. In this example, at some time after waking up, the relay UE 1206-3 receives a second group of WUS from the second relay UE 1204-2 (step 1304). The relay UE 1206-3 responds to the second relay UE 1204-2 (step 1306). In one embodiment, the response is a wake-up NAK (step 1306A). This wakeup NAK may indicate that the remote UE 1206-3 has been woken up by another relay UE.

[0186] In another embodiment, the remote UE 1206-3 responds to the second relay UE 1204-2 with a wakeup ACK and communicates through the first relay UE 1204-1 and the second relay UE 1204-2 (step 1306B). This may be beneficial in scenarios where different relay UEs 1204-1 and 1204-2 manage different services. In this case, it may be relevant for the remote UE 1206-3 to respond to communications from the first relay UE 1204-1 and the second relay UE 1204-2 in active mode. This can be handled according to different methods, which are determined at the system level:

[0187] In one embodiment, only the first relay UE 1204-1 that wakes up the remote UE 1206-3 acts as a proxy. The service request from the second relay UE 1204-2 is then communicated through the first relay UE 1204-1, which can be communicated through the base station 1202. From a system perspective, this is more complex, but from the perspective of the remote UE 1206-3, this simplifies the scheme, and the resynchronization at the remote UE 1206-3 only needs to be set up to communicate with the relay UE 1204-1 via the side link. The signal to enter the sleep state can then come from one relay UE, namely the first relay UE 1204-1 that sent the first WUS.

[0188] In another embodiment, the remote UE 1206-3 can communicate with the first relay UE 1204-1 and the second relay UE 1204-2 through a separate side link after being awakened. From the perspective of the entire system, this situation is simpler because the relay UEs 1204-1 and 1204-2 can act independently to meet different needs. This increases the complexity of the remote UE 1206-3 because it needs to communicate with two different relay UEs through the side link. In one embodiment, the remote UE 1206-3 does not re-enter deep sleep until it receives a request to do so from the first relay UE 1204-1 and the second relay UE 1204-2.

[0189] III. Further details

[0190] Fig.141 is a schematic block diagram of a radio access node 1400 according to some embodiments of the present disclosure. Optional features are represented by dashed boxes. The radio access node 1400 may be, for example, a base station 102, 1102, or 1202, or a network node that implements all or part of the functionality of the base station 102, 1102, or 1202 described herein. As shown, the radio access node 1400 includes a control system 1402, which includes one or more processors 1404 (e.g., a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), and / or the like), a memory 1406, and a network interface 1408. The one or more processors 1404 are also referred to herein as processing circuits. In addition, the radio access node 1400 may include one or more radio units 1410, each of which includes one or more transmitters 1412 and one or more receivers 1414, and the receivers 1414 are coupled to one or more antennas 1416. The radio unit 1410 may be referred to as a radio interface circuit or a part thereof. In some embodiments, the radio unit 1410 is external to the control system 1402 and is connected to the control system 1402 via a wired connection (e.g., an optical cable). However, in some other embodiments, the radio unit 1410 and possible antenna 1416 are integrated with the control system 1402. The one or more processors 1404 operate to provide one or more functions of the radio access node 1400 as described herein (e.g., one or more functions of the base station 102, 1102, or 1202 as described herein). In some embodiments, the functions are implemented in software stored, for example, in the memory 1406 and executed by the one or more processors 1404.

[0191] Fig.15 1 is a schematic block diagram illustrating a virtualized embodiment of a radio access node 1400 according to some embodiments of the present disclosure. The discussion is equally applicable to other types of network nodes. In addition, other types of network nodes may have similar virtualized architectures. Again, optional features are represented by dashed boxes.

[0192] As used herein, a "virtualized" radio access node is an implementation of a radio access node 1400 in which at least a portion of the functionality of the radio access node 1400 is implemented as a virtual component (e.g., by a virtual machine executing on a physical processing node in a network). As shown, in this example, the radio access node 1400 may include a control system 1402 and / or one or more wireless units 1410, as described above. The control system 1402 may be connected to the wireless unit 1410 by, for example, an optical cable. The radio access node 1400 includes one or more processing nodes 1500, which are coupled to or are part of the network 1502. If present, the control system 1402 or the wireless unit is connected to the processing node 1500 via the network 1502. Each processing node 1500 includes one or more processors 1504 (e.g., CPU, ASIC, FPGA, and / or the like), a memory 1506, and a network interface 1508.

[0193] In this example, the functionality 1510 of the radio access node 1400 described herein (e.g., functionality of the base station 102, 1102, or 1202) is implemented at one or more processing nodes 1500 or distributed across one or more processing nodes 1500 and the control system 1402 and / or the wireless unit 1410 in any desired manner. In some specific embodiments, some or all of the functionality 1510 of the radio access node 1400 described herein is implemented as a virtual component executed by one or more virtual machines implemented in a virtual environment hosted by the processing node 1500. One of ordinary skill in the art will appreciate that additional signaling or communication between the processing node 1500 and the control system 1402 is used to perform at least some of the desired functionality 1510. It is worth noting that in some embodiments, the control system 1402 may not be included, in which case the wireless unit 1410 communicates directly with the processing node 1500 via an appropriate network interface.

[0194] In some embodiments, a computer program is provided, the computer program comprising instructions, when executed by at least one processor, the instructions cause the at least one processor to perform the functions of the radio access node 1400 or the functions of a node (e.g., processing node 1500) implementing one or more functions 1510 of the radio access node 1400 according to any embodiment described herein. In some embodiments, a carrier comprising the above-mentioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium, such as a memory).

[0195] Fig.161 is a schematic block diagram of a radio access node 1400 according to some other embodiments of the present disclosure. The radio access node 1400 includes one or more modules 1600, each of which is implemented in software. The modules 1600 provide the functionality of the radio access node 1400 described herein. The discussion also applies to Fig.15 1500 , wherein module 1600 may be implemented at one of processing nodes 1500 , or distributed across multiple processing nodes 1500 and / or across processing node 1500 and control system 1402 .

[0196] Fig.17 1 is a schematic block diagram of a UE 1700 according to some embodiments of the present disclosure. The UE 1700 may be a relay UE 104, 604, 1104-1, 1104-2, 1204-1 or 1204-2 or a remote UE 106, 606, 1106-1, 1106-2 or 1206-3. As shown, the UE 1700 includes one or more processors 1702 (e.g., CPU, ASIC, FPGA, etc.), a memory 1704, and one or more transceivers 1706, each transceiver 1706 including one or more transmitters 1708 and one or more receivers 1710, and the receiver 1710 is coupled to one or more antennas 1712. The transceiver 1706 includes a radio front-end circuit connected to the antenna 1712, which is configured to adjust the signal transmitted between the antenna 1712 and the processor 1702, as will be understood by those of ordinary skill in the art. The processor 1702 is also referred to herein as a processing circuit. The transceiver 1706 is also referred to herein as a radio circuit. In some embodiments, the functions of the above-mentioned UE 1700 (e.g., the functions of the above-mentioned relay UE 104, 604, 1104-1, 1104-2, 1204-1 or 1204-2 or the remote UE 106, 606, 1106-1, 1106-2 or 1206-3) can be implemented in whole or in part in software, which is, for example, stored in the memory 1704 and executed by the processor 1702. Note that the UE 1700 may include Fig.17 Additional components not shown in the figure, such as one or more user interface components (e.g., input / output interfaces including displays, buttons, touch screens, microphones, speakers, etc. and / or any other components for allowing information to be input into UE 1700 and / or allowing information to be output from UE 1700), power sources (e.g., batteries and associated power circuits), etc.

[0197] In some embodiments, a computer program is provided, the computer program comprising instructions, when executed by at least one processor, the instructions cause the at least one processor to perform the functions of the UE 1700 according to any embodiment described herein. In some embodiments, a carrier comprising the above-mentioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium, such as a memory).

[0198] Fig.18 1 is a schematic block diagram of a UE 1700 according to some other embodiments of the present disclosure. The UE 1700 includes one or more modules 1800, each of which is implemented in software. The modules 1800 provide the functions of the UE 1700 described herein.

[0199] refer to Fig.19 According to one embodiment, the communication system includes a telecommunications network 1900, such as a cellular network of the 3GPP type, which includes an access network 1902, such as a RAN, and a core network 1904. The access network 1902 includes a plurality of base stations 1906A, 1906B, 1906C, such as Node B, eNB, gNB or other types of wireless access points (APs), each of which defines a corresponding coverage area 1908A, 1908B, 1908C. Each base station 1906A, 1906B, 1906C can be connected to the core network 1904 via a wired or wireless connection 1910. A first UE 1912 located in the coverage area 1908C is configured to be wirelessly connected to or paged by the corresponding base station 1906C. A second UE 1914 in the coverage area 1908A can be wirelessly connected to the corresponding base station 1906A. Although multiple UEs 1912 , 1914 are shown in this example, the disclosed embodiments are equally applicable to situations where a single UE is located within the coverage area or a single UE is connected to the corresponding base station 1906 .

[0200] The telecommunications network 1900 itself is connected to a host 1916, which may be embodied in the hardware and / or software of a stand-alone server, a cloud-enabled server, a distributed server, or as a processing resource in a server farm. The host 1916 may be owned or controlled by a service provider, or may be operated by or on behalf of a service provider. The connections 1918 and 1920 between the telecommunications network 1900 and the host 1916 may extend directly from the core network 1904 to the host 1916, or may be made through an optional intermediate network 1922. The intermediate network 1922 may be a combination of one or more of a public, private, or managed network; the intermediate network 1922 (if any) may be a backbone network or the Internet; specifically, the intermediate network 1922 may include two or more sub-networks (not shown).

[0201] Fig.19 The communication system as a whole realizes the connection between the connected UE 1912, 1914 and the host 1916. The connection can be described as an Over-the-Top (OTT) connection 1924. The host 1916 and the connected UE 1912, 1914 are configured to transmit data and / or signaling through the OTT connection 1924, using the access network 1902, the core network 1904, any intermediate network 1922, and possible other infrastructure (not shown) as intermediaries. The OTT connection 1924 can be transparent because the participating communication devices through which the OTT connection 1924 passes do not know the routing of uplink and downlink communications. For example, the base station 1906 may not or need not be informed of the past routing of the incoming downlink communication of the data from the host 1916 in order to forward (e.g., handover) to the connected UE 1912. Similarly, the base station 1906 does not need to know the future routing of the outgoing uplink communication from the UE 1912 to the host 1916.

[0202] Now refer to Fig. 20 Describe an example implementation of a UE, a base station, and a host according to an embodiment. In a communication system 2000, a host 2002 includes hardware 2004, including a communication interface 2006, which is configured to establish and maintain a wired or wireless connection with an interface of different communication devices of the communication system 2000. The host 2002 further includes a processing circuit 2008, which may have storage and / or processing capabilities. Specifically, the processing circuit 2008 may include one or more programmable processors, ASICs, FPGAs, or a combination of these (not shown), which is suitable for executing instructions. The host computer 2002 further includes software 2010, which is stored in the host computer 2002 or can be accessed by the host computer 2002 and can be executed by the processing circuit 2008. The software 2010 includes a host application 2012. The host application 2012 can be used to provide services to remote users, such as UE 2014 connected by an OTT connection 2016 that terminates at UE 2014 and the host computer 2002. When providing services to remote users, the host application 2012 may provide user data for transmission using the OTT connection 2016 .

[0203] The communication system 2000 further includes a base station 2018, which is arranged in the telecommunication system and includes hardware 2020 to enable it to communicate with the host computer 2002 and the UE 2014. The hardware 2020 may include a communication interface 2022 for establishing and maintaining a wired or wireless connection. The hardware 2020 of the communication system 2000 also has an interface with different communication devices of the communication system 2000, and a communication interface 2020 for establishing and maintaining communication with the coverage area ( Fig. 20The communication interface 2022 may be configured to facilitate a connection 2028 with the host 2002. The connection 2028 may be direct, or it may be through a core network (eg, a wireless network) of the telecommunications system. Fig. 20 2018) and / or through one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware 2020 of the base station 2018 further includes processing circuitry 2030, which may include one or more programmable processors, ASICs, FPGAs, or a combination of these (not shown), adapted to execute instructions. The base station 2018 also has software 2032 stored internally or accessible via an external connection.

[0204] The communication system 2000 further includes the UE 2014 already mentioned. The hardware 2034 of the UE 2014 may include a radio interface 2036, which is configured to establish and maintain a wireless connection 2026 with a base station serving the coverage area where the UE 2014 is currently located. The hardware 2034 of the UE 2014 further includes a processing circuit 2038, which may include one or more programmable processors, ASICs, FPGAs, or a combination of these (not shown), suitable for executing instructions. The UE 2014 further includes software 2040, which is stored in the UE 2014 or accessible by the UE 2014 and can be executed by the processing circuit 2038. The software 2040 includes a client application 2042. The client application 2042 can be used to provide services to human or non-human users through the UE 2014 with the support of the host 2002. In the host 2002, the executing host application 2012 can communicate with the executing client application 2042 through the OTT connection 2016 terminated at the UE 2014 and the host 2002. When providing services to the user, the client application 2042 can receive request data from the host application 2012 and provide user data in response to the request data. The OTT connection 2016 can transmit the request data and the user data. The client application 2042 can interact with the user to generate the user data it provides.

[0205] It should be noted that Fig. 20 The host 2002, base station 2018 and UE 2014 shown in FIG. Fig.19 The host 1916, one of the base stations 1906A, 1906B, 1906C, and one of the UEs 1912, 1914 in the embodiment of the present invention are similar or identical. That is, the internal workings of these entities can be as follows: Fig. 20 shown, and independently, the surrounding network topology can be Fig.19 topology.

[0206] exist Fig. 20, OTT connection 2016 is abstractly drawn to illustrate communication between host 2002 and UE 2014 via base station 2018, without explicit reference to any intermediate devices and the precise routing of messages via these devices. The network infrastructure can determine the routing, which can be configured to be hidden from UE 2014 or the service provider operating host 2002, or both. When OTT connection 2016 is active, the network infrastructure can further make decisions by which the routing is dynamically changed (e.g., based on load balancing considerations or reconfiguration of the network).

[0207] The wireless connection 2026 between the UE 2014 and the base station 2018 is consistent with the teachings of the embodiments described in the present disclosure. One or more of the various embodiments improves the performance of OTT services provided to the UE 2014 using the OTT connection 2016, where the wireless connection 2026 forms the last leg.

[0208] A measurement program may be provided to monitor data rates, delays, and other factors that one or more embodiments improve. There may also be an optional network function for reconfiguring the OTT connection 2016 between the host computer 2002 and the UE 2014 in response to changes in the measurement results. The measurement process and / or the network function for reconfiguring the OTT connection 2016 may be implemented in the software 2010 and hardware 2004 of the host computer 2002, or in the software 2040 and hardware 2034 of the UE 2014, or in both. In some embodiments, a sensor (not shown) may be deployed in or associated with a communication device through which the OTT connection 2016 passes; the sensor may participate in the measurement process by providing the values ​​of the monitoring quantities exemplified above or providing the values ​​of other physical quantities from which the software 2010, 2040 can calculate or estimate the monitoring quantities. The reconfiguration of the OTT connection 2016 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not need to affect the base station 2018, and it may be unknown or imperceptible to the base station 2018. Such procedures and functions are known and practiced in the art. In some embodiments, the measurements may involve proprietary UE signaling to facilitate host 2002 measurements of throughput, propagation time, latency, etc. The measurements may be implemented by software 2010 and 2040 using OTT connection 2016 to send messages, particularly empty messages or "dummy" messages, while monitoring propagation time, errors, etc.

[0209] Fig.21 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host, a base station and a UE, which can be reference Fig.19 and 20 To simplify the present disclosure, this section will only include Fig.21 Drawing reference. In step 2100, the host provides user data. In sub-step 2102 of step 2100 (which may be optional), the host provides the user data by executing a host application. In step 2104, the host initiates a transmission carrying the user data to the UE. In step 2106 (which may be optional), the base station transmits the user data carried in the host-initiated transmission to the UE in accordance with the teachings of the embodiments described in the present disclosure. In step 2108 (which may also be optional), the UE executes a client application associated with the host application executed by the host.

[0210] Fig. 22 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host, a base station and a UE, which can be reference Fig.19 and 20 To simplify the present disclosure, this section will only include Fig. 22 Drawing reference of. In step 2200 of the method, the host provides user data. In an optional sub-step (not shown), the host provides the user data by executing a host application. In step 2202, the host initiates a transmission carrying the user data to the UE. According to the teachings of the embodiments described in the present disclosure, the transmission may be delivered by a base station. In step 2204 (which may be optional), the UE receives the user data carried in the transmission.

[0211] Fig.23 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host, a base station and a UE, which can be reference Fig.19 and 20 To simplify the present disclosure, this section will only include Fig.23 Drawing reference. In step 2300 (which may be optional), the UE receives input data provided by the host. Additionally or alternatively, in step 2302, the UE provides user data. In sub-step 2304 of step 2300 (which may be optional), the UE provides user data by executing a client application. In sub-step 2306 of step 2302 (which may be optional), the UE executes a client application that provides user data in response to received input data provided by the host. When providing user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data is provided, the UE initiates the transmission of the user data to the host in sub-step 2308 (which may be optional). In step 2310 of the method, the host receives user data transmitted from the UE in accordance with the teachings of the embodiments described in the present disclosure.

[0212] Fig.24 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host, a base station and a UE, which can be reference Fig.19 and 20 To simplify the present disclosure, this section will only include Fig.24 Drawing reference of. In step 2400 (which may be optional), in accordance with the teachings of the embodiments described in the present disclosure, the base station receives user data from the UE. In step 2402 (which may be optional), the base station initiates transmission of the received user data to the host. In step 2404 (which may be optional), the host receives the user data carried in the transmission initiated by the base station.

[0213] Any appropriate steps, methods, features, functions or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include multiple such functional units. These functional units may be implemented by processing circuits, which may include one or more microprocessors or microcontrollers, and other digital hardware, which may include digital signal processors (DSPs), dedicated digital logic, etc. The processing circuit may be configured to execute program codes stored in a memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache, flash memory device, optical storage device, etc. The program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more technologies described herein. In some implementations, the processing circuit may be used to cause the corresponding functional unit to perform the corresponding function according to one or more embodiments of the present disclosure.

[0214] Although the processes in the figures may show a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform operations in a different order, combine certain operations, overlap certain operations, etc.).

[0215] Although the processes in the figures may show a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform operations in a different order, combine certain operations, overlap certain operations, etc.).

[0216] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered to be within the scope of the concepts disclosed herein.

Claims

1. A method for group wake-up of a remote UE group (605) performed by a relay user equipment UE (604), the method include: receiving (802) a group wake-up signal WUS from another radio node; as well as A group wake-up procedure is performed (804) on a remote UE group (605) in an idle state, the remote UE group (605) including one or more remote UEs (606-1 to 606-N).

2. The method according to claim 1, in, Executing (804) the group wake-up process includes: detecting (900) said set of WUS received from said another radio node; decoding (902) the group WUS to determine the one or more remote UEs (606-1 to 606-N) in the group of remote UEs (605); and A WUS is generated and sent (903) to each remote UE of the one or more remote UEs (606-1 to 606-N) in the group (605).

3. The method according to claim 1, in, Executing (804) the group wake-up process includes: monitoring (906-908) a wake-up confirmation from the one or more remote UEs (606-1 to 606-N); While monitoring (906-908) the wakeup confirmation, determining (910) whether wakeup confirmations from all remote UEs of the one or more remote UEs (606-1 to 606-N) are detected; In response to determining (910) that a wake-up confirmation has not been detected for all of the one or more remote UEs (606-1 to 606-N): identifying (918) one or more remote UEs (606-1 to 606-N) in the group (605) for which a wake-up confirmation has not been detected; and A wake-up signal is sent (920) to the one or more remote UEs (606-1 to 606-N) in the group (605) for which a wake-up confirmation has not been detected.

4. The method according to claim 3, in: Performing (804) the group wake-up process further includes: setting (904) one or more timers; and Monitoring (906-908) the wakeup confirmation from the one or more remote UEs (606-1 to 606-N) includes monitoring (906-908) the wakeup confirmation from the one or more remote UEs (606-1 to 606-N) while the one or more timers are running.

5. The method according to claim 3 or 4, further comprising: include: The steps of monitoring (906-908), determining (910), identifying (918) and sending (920) are repeated until a wake-up confirmation has been detected for all remote UEs in the one or more remote UEs (606-1 to 606-N) in the group (605) or a maximum number of wake-up attempts has been reached.

6. The method according to any one of claims 2 to 5, in, Generating and sending (903) a WUS to each of the one or more remote UEs (606-1 to 606-N) in the group (605) includes generating and sending (903) a low power wake-up signal LPWUS to each of the one or more remote UEs (606-1 to 606-N) in the group (605).

7. The method according to claim 6, in, The LPWUS has one or more characteristics, and the one or more characteristics enable the power cost for detecting the LPWUS to be smaller than the power cost for detecting the wake-up signal WUS from the base station.

8. The method according to any one of claims 2 to 7, further comprising: include: A synchronization signal is generated and sent (903) for the one or more remote UEs (606-1 to 606-N) in the group (605).

9. The method according to claim 8, in, Generating and sending (903) the synchronization signal for the one or more remote UEs (606-1 to 606-N) in the group (605) includes broadcasting (903) the synchronization signal for the one or more remote UEs (606-1 to 606-N) in the group (605).

10. The method according to claim 8, in, Generating and sending (903) the synchronization signal for the one or more remote UEs (606-1 to 606-N) in the group (605) includes: generating and sending (903) a separate synchronization signal to each remote UE in the one or more remote UEs (606-1 to 606-N) in the group (605).

11. The method according to claim 1, in, Executing (804) the group wake-up process includes: detecting (1000) said set of WUS received from said another radio node; decoding (1002) the group WUS to determine the one or more remote UEs (606-1 to 606-N) in the group of remote UEs (605); monitoring (1006-1008) a wake-up confirmation from the one or more remote UEs (606-1 to 606-N); While monitoring (1006-1008) the wakeup confirmation, determining (1010) whether wakeup confirmations from all remote UEs of the one or more remote UEs (606-1 to 606-N) are detected; In response to determining (1010) that a wake-up confirmation has not been detected for all of the one or more remote UEs (606-1 to 606-N): identifying (1018) one or more remote UEs (606-1 to 606-N) in the group (605) for which a wake-up confirmation has not been detected; and A wake-up signal is sent (1020) to the one or more remote UEs (606-1 to 606-N) in the group (605) for which a wake-up confirmation has not been detected.

12. The method according to claim 11, in: Performing (804) the group wake-up process further includes: setting (1004) one or more timers; and Wherein, monitoring (1006-1008) the wake-up confirmation from the one or more remote UEs (606-1 to 606-N) includes: monitoring (1006-1008) the wake-up confirmation from the one or more remote UEs (606-1 to 606-N) while the one or more timers are running.

13. The method according to claim 11 or 12, in, Sending (1020) the wake-up signal to the one or more remote UEs (606-1 to 606-N) in the group (605) for which no wake-up confirmation has been detected includes sending (1020) a low power wake-up signal LPWUS to each of the one or more remote UEs (606-1 to 606-N) in the group (605) for which no wake-up confirmation has been detected.

14. The method according to claim 13, in, The LPWUS has one or more characteristics, and the one or more characteristics enable the power cost for detecting the LPWUS to be smaller than the power cost for detecting the wake-up signal WUS from the base station.

15. The method according to claim 11 or 14, further comprising: include: A synchronization signal is transmitted (1020) for the one or more remote UEs (606-1 to 606-N) in the group (605) for which a wake-up confirmation has not been detected.

16. The method according to claim 15, in, Sending (1020) a synchronization signal for the one or more remote UEs (606-1 to 606-N) in the group (605) for which a wake-up confirmation has not yet been detected includes: broadcasting (1020) the synchronization signal for the one or more remote UEs (606-1 to 606-N) in the group (605) for which a wake-up confirmation has not yet been detected.

17. The method according to claim 15, in, Sending (1020) a synchronization signal for the one or more remote UEs (606-1 to 606-N) in the group (605) for which a wake-up confirmation has not yet been detected includes sending (1020) a separate synchronization signal to each remote UE in the one or more remote UEs (606-1 to 606-N) in the group (605) for which a wake-up confirmation has not yet been detected.

18. The method according to any one of claims 11 to 17, further comprising: include: The steps of monitoring (1006-1008), determining (1010), identifying (1018) and sending (1020) are repeated until a wake-up confirmation has been detected for all remote UEs in the one or more remote UEs (606-1 to 606-N) in the group (605) or a predefined or preconfigured maximum number of wake-up attempts has been reached.

19. The method according to claim 18, in, For at least one iteration of repeating the steps, a transmission power used for transmitting (1020) the wake-up signal is increased.

20. The method according to claim 18 or 19, in, The predefined or preconfigured maximum number of wake-up attempts is configured by the base station.

21. The method according to any one of claims 1 to 20, in, Receiving (802) the set of WUS from the another radio node includes receiving the set of WUS from a base station via one or more additional relay UEs.

22. The method according to any one of claims 1 to 21, further comprising include: The group of WUS is relayed to one or more additional relay UEs.

23. A relay UE (604) for group wake-up of a group of remote user equipments UE (605), the relay UE (604) being adapted to: receiving (802) a group wake-up signal WUS from another radio node; and A group wake-up procedure is performed (804) on a remote UE group (605) in an idle state, the remote UE group (605) including one or more remote UEs (606-1 to 606-N).

24. The relay UE (604) according to claim 23, further adapted to perform the method according to any one of claims 2 to 22.

25. A relay UE (604) for group wakeup of a remote user equipment UE group (605), the relay UE (604) include: one or more transmitters; one or more receivers; as well as Processing circuitry associated with the one or more transmitters and the one or more receivers, the processing circuitry being configured to cause the relay UE (604): receiving (802) a group wake-up signal WUS from another radio node; and A group wake-up procedure is performed (804) on a remote UE group (605) in an idle state, the remote UE group (605) including one or more remote UEs (606-1 to 606-N).

26. The relay UE (604) according to claim 25, in, The processing circuit is further configured to cause the relay UE (604) to perform the method of any one of claims 2 to 22.

27. A method for waking up from an idle state, performed by a remote user equipment UE (1206-3), the method include: receiving (1300) a wake-up signal WUS from a first relay UE (1204-1), the wake-up signal WUS being used for group wake-up of a first remote UE group including the remote UE (1206-3); as well as When performing wakeup in response to receiving (1300) the WUS from the first relay UE (1204-1), avoiding (1302) responding to a WUS from any other relay UE for group wakeup of another remote UE group in which the remote UE (1206-3) is also included.

28. The method according to claim 27, further comprising: include: After waking up: receiving (1304) a WUS for group wakeup of a second remote UE group including the remote UE (1206-3) from a second relay UE (1204-2); and A response (1306) is made to the second relay UE (1204-2).

29. The method according to claim 28, in, Responding (1306) to the second relay UE (1204-2) includes sending a negative acknowledgement to the second relay UE (1204-2).

30. The method according to claim 28, in, Responding (1306) to the second relay UE (1204-2) includes sending a positive acknowledgement to the second relay UE (1204-2).

31. A remote user equipment UE (1206-3) for waking up from an idle state, the remote UE (1206-3) being adapted to: receiving (1300) a wake-up signal WUS from a first relay UE (1204-1), the wake-up signal WUS being used for group wake-up of a first remote UE group including the remote UE (1206-3); and When performing wakeup in response to receiving (1300) the WUS from the first relay UE (1204-1), avoiding (1302) responding to a WUS from any other relay UE for group wakeup of another remote UE group in which the remote UE (1206-3) is also included.

32. The remote UE (1206-3) according to claim 31, further adapted to perform the method of any one of claims 28 to 30.

33. A remote user equipment UE (1206-3) for waking up from an idle state, the remote UE (1206-3) include: one or more transmitters; one or more receivers; as well as A processing circuit associated with the one or more transmitters and the one or more receivers, the processing circuit being configured to cause the remote UE (1206-3): receiving (1300) a wake-up signal WUS from a first relay UE (1204-1), the wake-up signal WUS being used for group wake-up of a first remote UE group including the remote UE (1206-3); as well as When performing wakeup in response to receiving (1300) the WUS from the first relay UE (1204-1), avoiding (1302) responding to a WUS from any other relay UE for group wakeup of another remote UE group in which the remote UE (1206-3) is also included.

34. The remote UE (1206-3) according to claim 33, in, The processing circuit is further configured to cause the remote UE (1206-3) to perform the method of any one of claims 28 to 30.