Methods for Enhanced RACH and SR Processes

Abstract

This disclosure relates to methods and apparatus for enabling user equipment (UE) with a low-power wake-up signal receiver (LP-WUR) to reduce its power consumption during random access and / or scheduling request procedures, respectively.

Description

Technical Field

[0001] This disclosure relates to wireless communication systems, and more specifically to methods and apparatus for energy saving on the user equipment (UE) side of a wireless communication system. Background Technology

[0002] 5G systems are designed and developed for both mobile phones and vertical use cases. Besides latency, reliability, and availability, UE energy efficiency is also crucial for 5G. Currently, 5G devices may need to be recharged weekly or daily, depending on individual usage time. Generally, 5G devices consume tens of milliwatts in RRC idle / inactive mode and hundreds of milliwatts in RRC connected mode. Designs that extend battery life are essential for improving energy efficiency and achieving a better user experience.

[0003] Energy efficiency is even more critical for UEs without a continuous power source (e.g., UEs using small rechargeable batteries and single coin cells). In vertical industry use cases, sensors and actuators are widely deployed for monitoring, measurement, charging, and more. Typically, their batteries are not rechargeable and are expected to last for at least several years, as described in TR 38.875. Wearable devices include smartwatches, rings, electronic health-related devices, and medical monitoring devices. Achieving a battery life of 1 to 2 weeks on demand, given typical battery capacities, is challenging.

[0004] Power consumption depends on the configured wake-up period length, such as the paging cycle. To meet the aforementioned battery life requirements, it is anticipated that eDRX cycles with large values ​​will be used, resulting in high latency, which is unsuitable for services requiring both long battery life and low latency. For example, in fire detection and suppression use cases, the actuator should close the fireproof roller shutter and activate the automatic sprinkler system within 1 to 2 seconds from when the sensor detects a fire; long eDRX cycles cannot meet the latency requirements. Clearly, eDRX is unsuitable for latency-critical use cases. Therefore, the intention is to investigate ultra-low power mechanisms capable of supporting low latency (e.g., lower than eDRX latency) in Rel-18.

[0005] Currently, UEs need to be woken up periodically every DRX cycle, which constitutes a major power consumption during periods without signaling or data traffic. Power consumption could be significantly reduced if UEs could be woken up only when triggered (e.g., paging). This can be achieved by using a wake-up signal to trigger the main radio and a separate receiver, which has the ability to monitor the wake-up signal with ultra-low power. The main radio is dedicated to data transmission and reception and can be turned off or put into deep sleep unless it is turned on.

[0006] The power consumption used to monitor the wake-up signal depends on the wake-up signal design and the hardware modules of the wake-up receiver used for signal detection and processing.

[0007] The research primarily focuses on low-power WUS / WUR for power-sensitive, small form factor devices, including IoT use cases such as industrial sensors, controllers, and wearables. Other use cases, such as XR / smart glasses and smartphones, are not excluded.

[0008] To reduce power consumption, Discontinuous Reception (DRX) has been introduced in 3GPP (3rd Generation Partnership Project) wireless communication systems. Essentially, in DRX, the UE periodically enters sleep mode and remains dormant for a specified duration, during which time it does not monitor the Physical Downlink Control Channel (PDCCH). It then wakes up and remains awake for the specified duration to monitor the PDCCH for possible downlink control data. The amount of power saved depends on how long the UE remains dormant and how often. Naturally, the longer the UE remains dormant, the greater the power savings.

[0009] In order to enhance energy efficiency without sacrificing latency in 5G or New Radio (NR) wireless communication systems, 3GPP is willing to define a new architecture for UEs (see, for example, Technical Report TR 38.869).

[0010] Essentially, current UEs need to be woken up periodically once per DRX cycle, which constitutes the main energy consumption during periods without signaling or data traffic. If UEs could be woken up only when triggered (e.g., paging), energy consumption could be significantly reduced. As studied by 3GPP, this is achieved by providing the UE with both a main radio MR unit and a low-power wake-up receiver (LP-WUR).

[0011] Basically, the MR unit corresponds to the 5G NR wireless communication unit, and the LP-WUR corresponds to the wireless communication unit used for low-power monitoring of wake-up signals. Once a wake-up signal is detected, the LP-WUR can trigger the MR unit, which can then transition from a low-power state to an active state.

[0012] The active state of the MR unit corresponds to the state in which the radio access network (RAN) of the wireless communication system exchanges data. The low power state corresponds to any state in which the MR unit cannot exchange data with the RAN.

[0013] "Low power" means that the average power consumption of the MR cell in the low power state is lower (and preferably significantly lower, for example, ten times or even a hundred times lower) than the average power consumption of the MR cell in the active state.

[0014] A "low-power" wake-up receiver means that the LP-WUR is used to receive wake-up signals when the MR unit is in a low-power state. Of course, the monitoring of the wake-up signal should be performed at low power, and therefore, the average power consumption of the LP-WUR should be lower than (and preferably significantly lower, for example, ten or even a hundred times lower) the average power consumption of the MR unit when it is active.

[0015] However, in certain processes, it is necessary to further reduce energy consumption.

[0016] During random access and / or scheduling request procedures, the UE applies the on / off mode provided by the network to further reduce power consumption. If low-priority and high-priority UE types use the same on / off mode, there is a high risk of contention and thus increased UE power consumption. Therefore, a single on / off mode is not suitable for all UE types or network conditions.

[0017] The on / off modes of the network configuration indicate when to activate and deactivate MR's monitoring of DL response and / or LP-WUR's monitoring of LP-WUS, respectively.

[0018] A UE in RRC_INACTIVE mode may temporarily measure an LP-WuS reference signal below a threshold, for example, due to temporary obstruction or poor reception conditions. As a result, the UE will unnecessarily (or prematurely) activate its main radio (MR) and waste energy.

[0019] The random access procedure enables the UE to establish communication with the RAN. For this purpose, a random access channel (RACH) is configured, allowing the UE to attempt to establish communication and notify the RAN of its desire to do so. Typically, in 5G or New Radio (NR) wireless communication systems, the UE sends a first message (also known as the msg1 message) via the RACH, which includes a predetermined random access preamble. The RAN can then respond to the random access preamble with a random access response RAR (also known as the msg2 message) including an initial uplink grant during the RAR window. If the RAR is successfully received, the UE then sends another message (also known as the msg3 message) via the Physical Uplink Shared Channel (PUSCH) using an initial uplink grant. The RAN can then respond to this msg3 message with a contention resolution message (also known as the msg4 message) during the contention resolution timer window. Summary of the Invention

[0020] This disclosure aims to improve this situation. In particular, this disclosure aims to address at least some of the limitations of the prior art discussed above. Specifically, this disclosure aims to propose a solution for reducing the duration during which the MR unit needs to remain active during a DL response period for sending DL responses to uplink requests sent respectively during random access or scheduling request procedures. For example, the DL response period corresponds to a RAR time window, a contention resolution timer value, or a scheduling request prohibition timer value discussed above. Furthermore, a single on / off mode is not suitable for all UE types and network conditions. If low-priority and high-priority UE types will use the same mode, there is a high risk of contention and thus increased UE power consumption.

[0021] According to a first aspect, this disclosure relates to a method for exchanging data in a wireless communication system, the method being implemented by a wireless device of the wireless communication system, wherein the wireless device includes: a master radio (MR) unit configured to exchange data with a radio access network (RAN) of the wireless communication system; and a low-power wake-up receiver (LP-WUR) configured to monitor a wake-up signal transmitted by the RAN and trigger a transition of the MR unit to an active state in response to detecting the wake-up signal, wherein the wireless device is configured to perform a random access procedure by transmitting an uplink UL request to the RAN and by receiving a DL response to the UL request during a downlink DL response period, wherein the DL response period includes an inactive sub-period and a subsequent active sub-period, and the method includes, during the DL response period:

[0022] - During the inactive sub-period, wake-up signal monitoring is performed by the LP-WUR, wherein the MR unit is in a low-power state.

[0023] - In response to the detection of a wake-up signal during the inactive sub-period: trigger the transition of the MR unit to the active state, and perform DL response monitoring during the active sub-period.

[0024] In some embodiments, the method according to the first aspect may also include one or more of the following optional features, either individually or in any technically possible combination.

[0025] In some embodiments of the method according to the first aspect, in response to the absence of a wake-up signal during the inactive sub-period, the MR unit remains in the low-power state during the active sub-period.

[0026] In some embodiments of the method according to the first aspect, the LP-WUR does not perform wake-up signal monitoring during the active period in response to the absence of a wake-up signal during the inactive sub-period.

[0027] In some embodiments, the method according to the first aspect includes receiving a DL response period configuration, the DL response period configuration defining the inactive sub-periods and the active sub-periods within the DL response period, as well as an additional time offset value to be applied before the start of the sub-period.

[0028] In some embodiments of the method according to the first aspect, the DL response time configuration is received in system information broadcast by the RAN, and / or the DL response time configuration is received in a Radio Resource Control (RRC) message sent by the RAN.

[0029] In some embodiments of the method according to the first aspect, the DL response period includes multiple active sub-periods, and / or the DL response period includes multiple inactive sub-periods.

[0030] In some embodiments, the method according to the first aspect includes receiving from the RAN an indication of whether the DL response period begins with an active sub-period or an inactive sub-period and / or whether an additional time offset value should be applied before the sub-period begins.

[0031] In some embodiments of the method according to the first aspect, the indication is received in system information broadcast by the RAN, and / or the indication is received in a Radio Resource Control (RRC) message sent by the RAN.

[0032] In some embodiments of the method according to the first aspect:

[0033] - The UL request corresponds to the msg1 message of the random access procedure, and the DL response period corresponds to the RAR window, and / or

[0034] - The UL request corresponds to the msg3 message of the random access procedure, and the DL response period corresponds to the contention resolution timer window.

[0035] According to a second aspect, this disclosure relates to a wireless device including at least one memory and at least one processor, the at least one processor being configured to implement a method according to any one of the embodiments of the first aspect.

[0036] According to a third aspect, this disclosure relates to a user equipment (UE) that includes a wireless means according to any one of the embodiments of this disclosure.

[0037] According to a fourth aspect, this disclosure relates to a method for exchanging data in a wireless communication system, the method being implemented by a base station (BS) of a radio access network (RAN) of the wireless communication system, wherein the BS is configured to exchange data with a wireless device, wherein the wireless device includes a main radio (MR) unit and a low-power wake-up receiver (LP-WUR), wherein the LP-WUR is configured to detect a wake-up signal transmitted by the BS and trigger a transition of the MR unit to an active state in response to detecting the wake-up signal transmitted by the BS, wherein the BS is configured to perform a random access procedure by monitoring an uplink UL channel for receiving UL requests from the wireless device and by transmitting a downlink DL response to the UL request during a DL response period in response to detecting the UL request from the wireless device, wherein the DL response period includes at least an inactive sub-period and at least one active sub-period, and wherein the BS is configured to transmit the DL response to the wireless device only during the at least one active sub-period of the DL response period.

[0038] In some embodiments, the method according to the fourth aspect may also include one or more of the following optional features, either individually or in any technically possible combination.

[0039] In some embodiments, the method according to the fourth aspect includes, in response to determining that the DL response will be sent in an active sub-period following an inactive sub-period of the DL response period: sending a wake-up signal to the wireless device in the inactive sub-period.

[0040] In some embodiments, the method according to the fourth aspect includes sending a DL response period configuration to the wireless device, wherein the DL response period configuration defines at least one inactive sub-period and at least one active sub-period within the DL response period, as well as an additional time offset value to be applied before the start of the sub-period.

[0041] In some embodiments of the method according to the fourth aspect, the DL response period configuration is sent in system information broadcast by the RAN, and / or the DL response period configuration is sent in a Radio Resource Control (RRC) message sent to the radio device.

[0042] In some embodiments, the method according to the fourth aspect includes sending to the wireless device an indication of whether the DL response period begins with an active sub-period or an inactive sub-period and / or whether an additional time offset value should be applied before the sub-period begins.

[0043] In some embodiments of the method according to the fourth aspect, the indication is sent in system information broadcast by the RAN, and / or the indication is sent in a Radio Resource Control (RRC) message sent by the RAN.

[0044] According to a fifth aspect, this disclosure relates to a base station (BS) including at least one memory and at least one processor, the at least one processor being configured to implement a method according to any one of the embodiments of the fourth aspect.

[0045] According to a sixth aspect, this disclosure relates to a wireless communication system comprising at least one base station according to any one of the embodiments of this disclosure and at least one user equipment according to any one of the embodiments of this disclosure.

[0046] According to a seventh aspect, this disclosure relates to a computer program product comprising instructions that, when executed by at least one processor, configure the at least one processor to implement a method for exchanging data according to any of the embodiments of this disclosure. The computer program product may use any programming language and may be in the form of source code, object code, or any intermediate form between source code and object code, such as a partially compiled form, or any other desired form.

[0047] According to an eighth aspect, this disclosure relates to a (non-transitory) computer-readable storage medium comprising instructions that, when executed by at least one processor, configure the at least one processor to implement a method for sending control messages according to any one of the embodiments of this disclosure. Attached Figure Description

[0048] The invention will be better understood after reading the following description, which is given by way of non-limiting example and with reference to the accompanying drawings, which illustrate:

[0049] - Figure 1 UE RRC status

[0050] - Figure 2 The SR process, including the sr-ProhibitTimer period, involves monitoring the PDCCH for UL-authorized purposes during this time.

[0051] - Figure 3 : A schematic representation of the SR monitoring time window (including the time period of sr-ProhibitTimer and the overlaid on / off mode).

[0052] - Figure 4 UE behavior

[0053] - Figure 5 :BS behavior,

[0054] In these figures, the same reference numerals in each figure denote the same or similar elements. For clarity, unless otherwise explicitly stated, the elements shown are not drawn to scale. Detailed Implementation

[0055] The detailed description set forth below with reference to the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In particular, although the embodiments described herein may be exemplified in this disclosure using terminology from 3GPP 5G NR, this should not be construed as limiting the scope of the invention.

[0056] Some embodiments of the ideas contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are also included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited to the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0057] Generally, unless a different meaning is clearly given and / or implied from the context of the use of the term, all terms used herein shall be interpreted according to their common meaning in the relevant art. Unless otherwise expressly stated, all references to a / an / said element, device, component, element, step, etc. shall be interpreted openly as referring to at least one instance of said element, device, component, element, step, etc. The steps of any method disclosed herein need not be performed in the exact order disclosed, unless a step is explicitly described as occurring after or before another step and / or implied therein that a step must occur after or before another step. Where appropriate, any feature of any of the embodiments disclosed herein may be applied to any other embodiment. Similarly, any advantage of any of the embodiments may be applied to any other embodiment, and vice versa. Other objects, features, and advantages of the appended embodiments will be apparent from the following description.

[0058] In some embodiments, the more general term "network node" may be used, and the term may correspond to any type of radio network node or any network node that communicates with the UE (directly or via another node) and / or with another network node. Examples of network nodes are NodeB, MeNB, eNB, network nodes belonging to MCG or SCG, base station (BS), multi-standard radio (MSR) radio nodes (such as MSR BS), eNodeB (eNB), gNodeB (gNB), network controller, radio network controller (RNC), base station controller (BSC), repeater, donor node controlling repeater, base transceiver station (BTS), access point (AP), transport point, transport node, RRU, RRH, nodes in distributed antenna system (DAS), core network nodes (e.g., Mobile Switching Center (MSC), Mobility Management Entity (MME), etc.), Operation and Maintenance (O&M), Operation Support System (OSS), Self-Optimizing Network (SON), location nodes (e.g., Evolved Services Mobile Location Center (E-SMLC)), Minimized Drive Test (MDT), test equipment (physical node or software), etc.

[0059] In some embodiments, the non-limiting terms User Equipment (UE) or Wireless Device may be used, and the term may refer to any type of wireless device communicating with a network node and / or with another UE in a cellular or mobile communication system. Examples of UEs are target devices, device-to-device (D2D) UEs, machine-type UEs or UEs capable of machine-to-machine (M2M) communication, PDAs, PADs, tablet computers, mobile terminals, smartphones, laptop embedded devices (LEE), laptop mounted devices (LME), USB dongles, UE class M1, UE class M2, ProSe UE, V2V UE, V2X UE, etc.

[0060] Furthermore, terms such as base station / gNodeB and UE should be considered non-restrictive and, in particular, do not imply any hierarchical relationship between them; generally speaking, "gNodeB" can be considered device 1 and "UE" can be considered device 2, and the two devices communicate with each other through a radio channel. And in the following text, a transmitter or receiver can be either a gNodeB (gNB) or a UE.

[0061] As those skilled in the art will understand, aspects of the embodiments can be embodied as systems, apparatus, methods, or program products. Therefore, embodiments can take the form of entirely hardware embodiments, entirely software embodiments (including firmware, resident software, microcode, etc.), or embodiments combining software and hardware aspects.

[0062] For example, the disclosed embodiments can be implemented as hardware circuitry, including custom-designed very large-scale integration (“VLSI”) circuitry or gate arrays, off-the-shelf semiconductors (such as logic chips, transistors, or other discrete components). The disclosed embodiments can also be implemented in programmable hardware devices such as field-programmable gate arrays, programmable array logic, programmable logic devices, etc. As another example, the disclosed embodiments may include one or more physical or logical blocks of executable code, which may, for example, be organized as objects, procedures, or functions.

[0063] Furthermore, embodiments may take the form of a program product embodied in one or more computer-readable storage devices, which store machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage device may be tangible, non-transitory, and / or non-transferable. The storage device may not embody signals. In one embodiment, the storage device uses only signals to access the code.

[0064] Any combination of one or more computer-readable media may be used. A computer-readable medium may be a computer-readable storage medium. A computer-readable storage medium may be a storage device for storing code. A storage device may be, for example, but not limited to, electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor systems, devices, or apparatuses, or any suitable combination thereof.

[0065] More specific examples of storage devices (a non-exhaustive list) will include the following: electrical connections having one or more wires; portable computer floppy disks; hard disks; random access memory (“RAM”); read-only memory (“ROM”); erasable programmable read-only memory (“EPROM” or flash memory); portable optical disc read-only memory (“CD-ROM”); optical storage devices; magnetic storage devices; or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium can be any tangible medium that can contain or store programs for use by or in conjunction with an instruction execution system, device, or apparatus.

[0066] The code used to perform the operations of the embodiments can be any number of lines and can be written in any combination of one or more programming languages, including object-oriented programming languages ​​(such as Python, Ruby, Java, Smalltalk, C++, etc.), as well as conventional procedural programming languages ​​(such as the "C" programming language, etc.) and / or machine languages ​​(such as assembly language). The code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer via any type of network (including a local area network ("LAN"), a wireless LAN ("WLAN"), or a wide area network ("WAN"), or can be connected to an external computer (e.g., via the Internet through an Internet service provider ("ISP").

[0067] Furthermore, the features, structures, or characteristics described in the embodiments can be combined in any suitable manner. Numerous specific details, such as examples of programming, software modules, user selection, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., are provided in the following description to provide a thorough understanding of the embodiments. However, those skilled in the art will recognize that the embodiments can be practiced without one or more of the specific details described or using other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the embodiments. References to “an embodiment,” “embodiment,” or similar language throughout the specification mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Therefore, unless expressly specified otherwise, the phrases “in one embodiment,” “in an embodiment,” and similar language appearing throughout the specification may, but not necessarily all, refer to the same embodiment, but rather mean “one or more, but not all, embodiments.” Unless expressly specified otherwise, the terms “comprising,” “including,” “having,” and variations thereof mean “including, but not limited to,” “including.” Unless expressly specified otherwise, the enumeration list of items does not imply that any or all of the items are mutually exclusive. Unless otherwise expressly specified, the terms “a,” “an,” and “the” also refer to “one or more.”

[0068] The following description refers to schematic flowcharts and / or schematic block diagrams of methods, apparatus, systems, and program products according to embodiments. It should be understood that each block and combination of blocks in the schematic flowcharts and / or schematic block diagrams can be implemented by code. This code can be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to produce a machine, such that instructions executable by the processor of the computer or other programmable data processing apparatus create means for implementing the functions / actions specified in the flowcharts and / or block diagrams.

[0069] The code may also be stored in a storage device that can instruct a computer, other programmable data processing device or other means to operate in a particular manner, such that the instructions stored in the storage device produce an article of art including instructions that implement the functions / actions specified in the flowchart and / or block diagram.

[0070] Code can also be loaded onto a computer, other programmable data processing device or other apparatus such that a series of operational steps to be performed on the computer, other programmable device or other apparatus produce a computer-implemented process, such that the code executing on the computer or other programmable device provides a process for implementing the functions / actions specified in the flowchart and / or block diagram.

[0071] The flowcharts and / or block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of devices, systems, methods, and program products according to various embodiments. In this regard, each box in the flowcharts and / or block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function.

[0072] It should also be noted that in some alternative implementations, the functions indicated in the boxes may not occur in the order shown in the diagram. For example, depending on the functionality involved, two boxes shown consecutively may actually be executed substantially concurrently, or the boxes may sometimes be executed in reverse order. Other steps and methods that are functionally, logically, or effectically equivalent to one or more boxes or portions thereof shown in the diagram can be envisioned.

[0073] While various arrow and line types may be used in flowcharts and / or block diagrams, they are not intended to limit the scope of the corresponding embodiments. In practice, some arrows or other connecting symbols may be used to indicate only the logical flow of the depicted embodiment. For example, arrows may indicate waiting or monitoring periods of unspecified duration between enumerated steps of the depicted embodiment. It should also be noted that each block in the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, may be implemented by a system based on dedicated hardware or a combination of dedicated hardware and code that performs the specified function or action.

[0074] The description of each element in each figure can be referenced to the elements in the preceding figures. The same numbers in all figures refer to the same elements, including alternative embodiments of the same elements.

[0075] The detailed description set forth below with reference to the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. For example, although 3GPP terms from, for example, 5G NR may be used in this disclosure to exemplify embodiments herein, this should not be considered as limiting the scope of this disclosure.

[0076] This disclosure relates to a wireless communication system, such as a 5G NR wireless communication system. More specifically, it refers to a RAN (Radio Access Network) that exchanges data with a UE via radio signals. For example, the RAN can send data (downlink DL) to the UE, such as data received from the core network (CN). The RAN can also receive data from the UE (uplink UL), which can be forwarded to the CN.

[0077] In the example shown, the RAN includes a base station (BS). Of course, the RAN can include more than one BS to increase the coverage of the wireless communication system. Depending on the implemented wireless communication standard, each of these BSs can be called an NB, eNodeB (or eNB), gNodeB (or gNB, in the case of a 5G NR wireless communication system), access point, etc.

[0078] The UE is located within the coverage area of ​​the BS. The coverage area of ​​the BS corresponds, for example, to the region where the UE can decode the PDCCH sent by the BS.

[0079] Examples of wireless devices suitable for implementing any of the methods discussed in this disclosure at the UE correspond to devices that provide wireless connectivity to a RAN (Radio Range) of a wireless communication system and can be used to exchange data with said RAN. Such wireless devices can be included in the UE. The UE can be, for example, a cellular phone, a wireless modem, a wireless communication device, a handheld device, a laptop computer, etc. The UE can also be an Internet of Things (IoT) device, such as a wireless camera, a smart sensor, a smart meter, smart glasses, a vehicle (manned or unmanned), a GPS device, etc., or any other device capable of running applications that require the exchange of data with a remote receiver via a wireless device.

[0080] The wireless device includes one or more processors and one or more memories. The one or more processors may include, for example, a central processing unit (CPU), a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), etc. The one or more memories may include any type of computer-readable volatile and non-volatile memory (magnetic hard disk, solid-state drive, optical disk, electronic storage, etc.). The one or more memories may store a computer program product in the form of a set of program code instructions, to be executed by the one or more processors, to implement all or part of the steps of a method for exchanging data at the UE side according to any of the embodiments disclosed herein.

[0081] The wireless device may also include a main radio (MR) unit. The MR unit corresponds to the main wireless communication unit of the wireless device, which is used to exchange data with the BS of the RAN using radio signals. The MR unit can implement one or more wireless communication protocols and can be, for example, a 3G, 4G, 5G, NR, WiFi, WiMax, or other transceivers. In a preferred embodiment, the MR unit corresponds to a 5G NR wireless communication unit.

[0082] The detailed description set forth below with reference to the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In particular, although the embodiments described herein may be exemplified in this disclosure using terminology from 3GPP 5G NR, this should not be construed as limiting the scope of the invention.

[0083] Some embodiments of the ideas contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are also included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited to the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0084] Generally, unless a different meaning is clearly given and / or implied from the context of the use of the term, all terms used herein shall be interpreted according to their common meaning in the relevant art. Unless otherwise expressly stated, all references to a / an / said element, device, component, element, step, etc. shall be interpreted openly as referring to at least one instance of said element, device, component, element, step, etc. The steps of any method disclosed herein need not be performed in the exact order disclosed, unless a step is explicitly described as occurring after or before another step and / or implied therein that a step must occur after or before another step. Where appropriate, any feature of any of the embodiments disclosed herein may be applied to any other embodiment. Similarly, any advantage of any of the embodiments may be applied to any other embodiment, and vice versa. Other objects, features, and advantages of the appended embodiments will be apparent from the following description.

[0085] In some embodiments, the more general term "network node" may be used, and the term may correspond to any type of radio network node or any network node that communicates with the UE (directly or via another node) and / or with another network node. Examples of network nodes are NodeB, MeNB, ENB, network nodes belonging to MCG or SCG, base stations (BS), multi-standard radio (MSR) radio nodes (such as MSR BS), eNodeB, gNodeB, network controller, radio network controller (RNC), base station controller (BSC), repeater, donor node controlling repeater, base transceiver station (BTS), access point (AP), transport point, transport node, RRU, RRH, nodes in distributed antenna system (DAS), core network nodes (e.g., mobile switching center (MSC), mobility management entity (MME), etc.), operations and maintenance (O&M), operations support system (OSS), self-optimizing network (SON), location nodes (e.g., evolved servicing mobile location center (E-SMLC)), minimized drive test (MDT), test equipment (physical node or software), etc.

[0086] In some embodiments, the non-limiting terms User Equipment (UE) or Wireless Device may be used, and the term may refer to any type of wireless device communicating with a network node and / or with another UE in a cellular or mobile communication system. Examples of UEs are target devices, device-to-device (D2D) UEs, machine-type UEs or UEs capable of machine-to-machine (M2M) communication, PDAs, PADs, tablet computers, mobile terminals, smartphones, laptop embedded devices (LEE), laptop mounted devices (LME), USB dongles, UE class M1, UE class M2, ProSe UE, V2V UE, V2X UE, etc.

[0087] Furthermore, terms such as base station / gNodeB and UE should be considered non-restrictive and, in particular, do not imply any hierarchical relationship between them; generally speaking, "gNodeB" can be considered device 1 and "UE" can be considered device 2, and the two devices communicate with each other through a radio channel. And in the following text, a transmitter or receiver can be either a gNodeB (gNB) or a UE.

[0088] As those skilled in the art will understand, aspects of the embodiments can be embodied as systems, apparatus, methods, or program products. Therefore, embodiments can take the form of entirely hardware embodiments, entirely software embodiments (including firmware, resident software, microcode, etc.), or embodiments combining software and hardware aspects.

[0089] For example, the disclosed embodiments can be implemented as hardware circuitry, including custom-designed very large-scale integration (“VLSI”) circuitry or gate arrays, off-the-shelf semiconductors (such as logic chips, transistors, or other discrete components). The disclosed embodiments can also be implemented in programmable hardware devices such as field-programmable gate arrays, programmable array logic, programmable logic devices, etc. As another example, the disclosed embodiments may include one or more physical or logical blocks of executable code, which may, for example, be organized as objects, procedures, or functions.

[0090] Furthermore, embodiments may take the form of a program product embodied in one or more computer-readable storage devices, which store machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage device may be tangible, non-transitory, and / or non-transferable. The storage device may not embody signals. In one embodiment, the storage device uses only signals to access the code.

[0091] Any combination of one or more computer-readable media may be used. A computer-readable medium may be a computer-readable storage medium. A computer-readable storage medium may be a storage device for storing code. A storage device may be, for example, but not limited to, electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor systems, devices, or apparatuses, or any suitable combination thereof.

[0092] More specific examples of storage devices (a non-exhaustive list) will include the following: electrical connections having one or more wires; portable computer floppy disks; hard disks; random access memory (“RAM”); read-only memory (“ROM”); erasable programmable read-only memory (“EPROM” or flash memory); portable optical disc read-only memory (“CD-ROM”); optical storage devices; magnetic storage devices; or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium can be any tangible medium that can contain or store programs for use by or in conjunction with an instruction execution system, device, or apparatus.

[0093] The code used to perform the operations of the embodiments can be any number of lines and can be written in any combination of one or more programming languages, including object-oriented programming languages ​​(such as Python, Ruby, Java, Smalltalk, C++, etc.), as well as conventional procedural programming languages ​​(such as the "C" programming language, etc.) and / or machine languages ​​(such as assembly language). The code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer via any type of network (including a local area network ("LAN"), a wireless LAN ("WLAN"), or a wide area network ("WAN"), or can be connected to an external computer (e.g., via the Internet through an Internet service provider ("ISP").

[0094] Furthermore, the features, structures, or characteristics described in the embodiments can be combined in any suitable manner. Numerous specific details, such as examples of programming, software modules, user selection, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., are provided in the following description to provide a thorough understanding of the embodiments. However, those skilled in the art will recognize that the embodiments can be practiced without one or more of the specific details described or using other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the embodiments. References to “an embodiment,” “embodiment,” or similar language throughout the specification mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Therefore, unless expressly specified otherwise, the phrases “in one embodiment,” “in an embodiment,” and similar language appearing throughout the specification may, but not necessarily all, refer to the same embodiment, but rather mean “one or more, but not all, embodiments.” Unless expressly specified otherwise, the terms “comprising,” “including,” “having,” and variations thereof mean “including, but not limited to,” “including.” Unless expressly specified otherwise, the enumeration list of items does not imply that any or all of the items are mutually exclusive. Unless otherwise expressly specified, the terms “a,” “an,” and “the” also refer to “one or more.”

[0095] The following description refers to schematic flowcharts and / or schematic block diagrams of methods, apparatus, systems, and program products according to embodiments. It should be understood that each block and combination of blocks in the schematic flowcharts and / or schematic block diagrams can be implemented by code. This code can be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to produce a machine, such that instructions executable by the processor of the computer or other programmable data processing apparatus create means for implementing the functions / actions specified in the flowcharts and / or block diagrams.

[0096] The code may also be stored in a storage device that can instruct a computer, other programmable data processing device or other means to operate in a particular manner, such that the instructions stored in the storage device produce an article of art including instructions that implement the functions / actions specified in the flowchart and / or block diagram.

[0097] Code can also be loaded onto a computer, other programmable data processing device or other apparatus such that a series of operational steps to be performed on the computer, other programmable device or other apparatus produce a computer-implemented process, such that the code executing on the computer or other programmable device provides a process for implementing the functions / actions specified in the flowchart and / or block diagram.

[0098] The flowcharts and / or block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of devices, systems, methods, and program products according to various embodiments. In this regard, each box in the flowcharts and / or block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function.

[0099] It should also be noted that in some alternative implementations, the functions indicated in the boxes may not occur in the order shown in the diagram. For example, depending on the functionality involved, two boxes shown consecutively may actually be executed substantially concurrently, or the boxes may sometimes be executed in reverse order. Other steps and methods that are functionally, logically, or effectically equivalent to one or more boxes or portions thereof shown in the diagram can be envisioned.

[0100] While various arrow and line types may be used in flowcharts and / or block diagrams, they are not intended to limit the scope of the corresponding embodiments. In practice, some arrows or other connecting symbols may be used to indicate only the logical flow of the depicted embodiment. For example, arrows may indicate waiting or monitoring periods of unspecified duration between enumerated steps of the depicted embodiment. It should also be noted that each block in the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, may be implemented by a system based on dedicated hardware or a combination of dedicated hardware and code that performs the specified function or action.

[0101] The following explanation provides a detailed description of the mechanism for pre-configuring and signaling specific information about model selection using the association between models and index values. AI / ML-based technologies are currently applied in many different applications, and 3GPP has also begun its research into these technologies for application to multiple use cases based on observed potential benefits. The AI / ML lifecycle can be divided into several phases, such as data collection / preprocessing, model training, model testing / validation, model deployment / update, and model monitoring, each of which is equally important for achieving the target performance of any particular model. One of the challenging issues when applying AI / ML models to any use case or application is managing the lifecycle of the AI / ML model. This is primarily because data / model drift occurs during model deployment / inference, leading to performance degradation of the AI / ML model. Fundamentally, dataset statistics change after the model is deployed, and the model's inference capabilities are also affected by the unseen data as input. Similarly, the statistical properties of the dataset and the relationship between the input and output of the trained model can change with drift. In this context, model selection is a key issue in maintaining model performance because model performance (such as inference and / or training) depends on different model execution environments with varying configuration parameters. To address this, collaboration between the UE and gNB is crucial for tracking model performance and reconfiguring models to suit different environments. Since model performance cannot be consistently maintained due to drift, AI / ML models require model monitoring after deployment, followed by providing update feedback for retraining / updating the model or selecting an alternative model. When deploying wireless communication networks supporting AI / ML models, it is important to consider how to handle AI / ML models during radio device activation and reconfiguration operations such as model training, inference, and updates. Therefore, when RAN-based model operations support a set of multiple specific AI / ML models, specifications regarding signaling methods and gNB-UE behavior are needed, along with new mechanisms for gNB-UE behavior and procedures to avoid any performance impact on model operations caused by using multiple specific AI / ML models.

[0102] The detailed description set forth below with reference to the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. For example, although 3GPP terms from, for example, 5G NR may be used in this disclosure to exemplify embodiments herein, this should not be considered as limiting the scope of this disclosure.

[0103] Generally, unless a different meaning is clearly given and / or implied from the context of the use of the term, all terms used herein will be interpreted according to their common meaning in the relevant art. Unless otherwise expressly stated, all references to a / an / said element, device, component, element, step, etc., will be interpreted openly as referring to at least one instance of said element, device, component, element, step, etc. Furthermore, the order of steps of any method disclosed herein, particularly in the figures, is provided for illustrative purposes only and is not intended to limit the disclosure. The disclosure may be applied where the same steps are performed in a different order and / or where steps are performed in parallel or in combination, unless a step is explicitly described as occurring after or before another step and / or where it is implied that a step must occur after or before another step. Moreover, in a figure, steps enclosed by dashed lines should be considered optional for the embodiment represented in that figure. Where appropriate, any feature of any of the embodiments disclosed herein may be applied to any other embodiment. Similarly, any advantage of any of the embodiments may be applied to any other embodiment, and vice versa. Other objects, features, and advantages of the appended embodiments will be apparent from the following description.

[0104] Figure 1 This indicates the UE's RRC state. Under both RRC_IDLE and RRC_INACTIVE, the UE performs neighboring cell measurements and can perform cell reselection. Under RRC_CONNECTED, UE mobility is controlled by the network, and handover can be initiated. Under RRC_IDLE, UE paging is initiated by the CN. Under RRC_INACTIVE, UE paging is initiated by the NG-RAN. To page the UE, its location must be known. Under RRC_IDLE, this is the Tracking Area (RA). Under RRC_INACTIVE, this is the RAN-based Notification Area (RNA), and the UE can initiate RNA updates.

[0105]

[0106] When the UE monitors LP-WUS via the Low Power Wake-up Receiver (LR), the UE's Main Receiver (MR) enters sleep mode and does not monitor the PDCCH. This sleep mode can be light / shallow / deep sleep. Once the UE detects LP-WUS, it wakes up the MR and begins PDCCH monitoring via the MR. If the UE decides to stop PDCCH monitoring via the MR, it can put the MR into sleep mode and use the LR to monitor LP-WUS to further reduce power consumption.

[0107] According to the current MAC specification, after sending the random access preamble (Msg1), the UE monitors the PDCCH in response to the random access response (RAR) message (Msg2). The response window (ra-ResponseWindow) begins at a defined time interval after the preamble transmission. All UEs apply the common value of ra-ResponseWindow received via system information messages. As mentioned in TS38.331, the value of ra-ResponseWindow is up to 80 slots. For example, if the gNB configures ra-ResponseWindow to sl40, this means that the gNB can send the RAR within 40 slots after receiving the random access preamble. Therefore, the UE may need to monitor the RAR for up to 40 slots after sending the random access preamble. Similarly, the UE starts a contention resolution timer after the transmission of msg3. It can be configured with a value between 8 and 64 subframes (i.e., 8 ms and 64 ms) (in RACH-ConfigCommon).

[0108] In the example, the RAN includes one base station (BS). Of course, the RAN can include more than one BS to increase the coverage of the wireless communication system. Depending on the implemented wireless communication standard, each of these BSs can be called an NB, eNodeB (or eNB), gNodeB (or gNB, in the case of 5G NR wireless communication systems), access point, etc.

[0109] Figure 2 The SR procedure is illustrated, which includes a period of sr-ProhibitTimer during which the UE monitors the PDCCH in response to a UL authorization indication. The SR procedure is used by the UE to request radio resources for new uplink transmissions. A MAC entity can be configured with zero or one SR configurations. Each SR configuration corresponds to one or more logical channels (LCHs). Each logical channel can be mapped to zero or one SR configuration, as configured by the RRC.

[0110] The purpose of this mapping between SR configuration and LCH is to allow the network to know, to some extent, which service type is requesting uplink resources. By creating a mapping between LCH and SR configuration, the network learns which LCH triggered the SR.

[0111] For example, each specific logical channel can be configured with a different SR configuration, so that when an SR is received, the network learns the LCH.

[0112] When the prohibition timer (sr-ProhibitTimer) is active, no additional SRs are initiated. sr-prohibitTimer is configured for each SR, and its value is at most 128 ms. (Refer to TS38.331 6.3.2SchedulingRequestConfig).

[0113] If the gNB configures the sr-ProhibitTimer to 32 ms, this means that the gNB can allocate uplink resources within 32 ms after receiving the SR. The UE may need to monitor the PDCCH for up to 32 ms after sending the SR.

[0114] In the example not shown, two UEs are represented. The UEs are located within the coverage area of ​​the BS. The coverage area of ​​the BS corresponds, for example, to the region where the UEs can decode the PDCCH transmitted by the BS.

[0115] One implementation is represented as an example of a wireless device suitable for implementing any method discussed in this disclosure performed at the UE. Essentially, the wireless device corresponds to a device that provides wireless connectivity to a RAN of a wireless communication system and can be used to exchange data with said RAN.

[0116] Such wireless devices can be included in the UE. The UE can be, for example, a cellular phone, a wireless modem, a wireless communication device, a handheld device, a laptop computer, etc. The UE can also be Internet of Things (IoT) devices, such as wireless cameras, smart sensors, smart meters, smart glasses, vehicles (manned or unmanned), GPS devices, etc., or any other equipment that can run applications that require exchanging data with a remote receiver via the wireless device 25.

[0117] The wireless device includes one or more processors and one or more memories. The one or more processors may include, for example, a central processing unit (CPU), a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), etc. The one or more memories may include any type of computer-readable volatile and non-volatile memory (magnetic hard disk, solid-state drive, optical disk, electronic storage, etc.). The one or more memories may store a computer program product in the form of a set of program code instructions, to be executed by the one or more processors, to implement all or part of the steps of a method for exchanging data at the UE side according to any of the embodiments disclosed herein.

[0118] The wireless device also includes a main radio (MR) unit and a low-power wake-up signal receiver (LP-WUR).

[0119] As discussed above, the MR unit corresponds to the main wireless communication unit of the wireless device, which is used to exchange data with the BS of the RAN using radio signals. The MR unit can implement one or more wireless communication protocols and can be, for example, a 3G, 4G, 5G, NR, WiFi, WiMax, etc. transceiver. In a preferred embodiment, the MR unit corresponds to a 5G NR wireless communication unit.

[0120] The LP-WUR corresponds to the secondary wireless communication unit of a wireless device, which is used to monitor a wake-up signal transmitted by the RAN's BS in a low-power manner. The wake-up signal can take any form that enables it to be detected in a low-power manner. Non-limiting examples of wake-up signals and LP-WURs are provided in technical report TR 38.869. It should be noted that in some examples, the wake-up signal can even be, for example, a specific 5G NR signal using a low-order modulation and coding scheme (MCS). In this case, the LP-WUR can include components of the 5G NR wireless communication unit that are strictly required to detect such a specific 5G NR signal.

[0121] As discussed above, the primary purpose of the LP-WUR is to monitor and detect wake-up signals (DL) sent by the RAN of the wireless communication system. Therefore, the LP-WUR can be unidirectional only, i.e., having only receive (DL) capability and no transmit (UL) capability. However, in some examples, the LP-WUR can also have transmit capability, allowing it to send (UL) data to the RAN.

[0122] The wireless device is adapted to operate in at least two operating modes, including a normal operating mode and a low-power operating mode:

[0123] - In normal operating mode, the MR unit is active.

[0124] - In low-power operation mode, the MR unit is in a low-power state, and the LP-WUR is configured to trigger a transition to normal operation mode in response to the detection of a wake-up signal sent by the RAN. If configured, an additional time offset is applied before monitoring of DL signals from the BS begins.

[0125] As discussed above, the activity status corresponds to any status in which the MR unit can exchange data with the RAN without being triggered by the LP-WUR.

[0126] Low-power states correspond to the state where the MR unit cannot exchange data with the RAN without being triggered by the LP-WUR. For example, a low-power state corresponds to the MR unit always being in sleep mode. However, thanks to the LP-WUR, the MR unit does not need to be periodically woken up in low-power states, so the MR unit can be in deep sleep and even be turned off, as the LP-WUR can be used to turn on the MR unit. Moreover, it should be noted that different low-power states with correspondingly different average power consumption can be considered for the MR unit. For example, an extremely low-power state with the lowest average power consumption and one or more medium-low-power states with average power consumption greater than that of the extremely low-power state can be considered. For example, an extremely low-power state can correspond to the MR unit being turned off, and a medium-low-power state can correspond to the MR unit being in sleep mode but not turned off.

[0127] It should be noted that in some examples, the LP-WUR can also be configured to trigger the MR unit when other conditions are verified. For example, the LP-WUR can be configured to trigger the MR unit if a predetermined timer has expired without a detected wake-up signal. This timer can be used to ensure that the wireless device can return to an active state when, for example, the wireless device has moved out of the wake-up signal's coverage area. Of course, the timer should be long enough to ensure that the MR unit remains in a low-power state for a sufficiently long period.

[0128] The BS includes one or more processors and one or more memories. The one or more processors may include, for example, a CPU, DSP, FPGA, ASIC, etc. The one or more memories may include any type of computer-readable volatile and non-volatile memory (magnetic hard disk, solid-state drive, optical disk, electronic storage, etc.). The one or more memories may store a computer program product in the form of a set of program code instructions, all or part of the steps of a method for exchanging data performed at the RAN side according to any of the embodiments disclosed herein, to be executed by the one or more processors.

[0129] like Figure 3 The diagram illustrates the main approach. The network (e.g., gNB) determines a mapping between type values ​​or unique identifiers associated with radio devices and network characteristics and random access and / or scheduling request configurations. Radio device characteristics may include, among others, user and / or device subscribed data, device type and capabilities, data service modes and / or history. Network characteristics may include, among others, user and / or device subscribed data, network type and capabilities, device mobility and data service modes and / or history, radio cell load, and contention level, such as the number of failed access attempts or failed scheduling requests within a predefined time interval.

[0130] Based on the determined mapping, the network (e.g., gNB) provides a random access and / or scheduling request procedure configuration, which includes at least one or more indications for activating and deactivating the UE's MR and / or LP-WUR monitoring of DL signals during random access and / or scheduling request procedure-related DL response periods (e.g., RAR monitoring window, contention resolution monitoring window, scheduling request prohibition time window).

[0131] When the gNB transitions a UE from RRC connectivity to RRC inactivity mode, the gNB provides a new or updated configuration. The gNB provides this new or updated configuration via a dedicated UE-specific RRC message (e.g., an RRC release message). The gNB determines the appropriate configuration based on the UE's subscription, type, and data service history / characteristics, as well as cell load or other network-level metrics.

[0132] gNB can provide a mapping (table) between unique type values ​​or identifiers and RACH configurations (RAR monitoring window, contention resolution monitoring window) through system information messages and / or dedicated RRC messages, including different on / off modes.

[0133] When an inactive RRC UE triggers the RACH procedure, it applies an on / off mode corresponding to its UE type within the RAR monitoring and contention resolution monitoring window. The gNB can change the on / off mode based on cell load or other network-level metrics. This method also applies to other RRC states. This method reduces contention between UEs and thus reduces UE power consumption.

[0134]

[0135] UE behavior during the "Open-Close Period" in the RAR monitoring window: When the "Close Period" expires, the UE begins the "Open Period." During the "Open Period," the UE-MR monitors the RAR from the gNB, and the UE LP-WUR is in sleep mode. When the "Open Period" expires, the UE begins the "Close Period." During the "Close Period," the UE-MR is in sleep mode, and the UE LP-WUR monitors the LP-WUS from the gNB. If the UE detects the LP-WUS during the "Close Period," the UE activates the MR, and if configured, applies an additional time offset before starting RAR monitoring for the next "Open Period." If the UE does not detect the LP-WUS during the "Close Period," the UE-MR skips monitoring the RAR for the next "Open Period."

[0136] UE Behavior During the "Open-Close Period" in the "Content Resolution Timing Window": When the "Close Period" expires, the UE begins the "Open Period." During the "Open Period," the UE-MR monitors for contention resolution messages from the gNB, and the UE LP-WUR is in sleep mode. When the "Open Period" expires, the UE begins the "Close Period." During the "Close Period," the UE-MR is in sleep mode, and the UE LP-WUR monitors for LP-WUS from the gNB. If the UE detects LP-WUS during the "Close Period," the UE activates the MR, and if configured, applies an additional time offset before starting to monitor for contention resolution messages for the next "Open Period." If the UE does not detect LP-WUS during the "Close Period," the UE-MR skips monitoring for contention resolution messages for the next "Open Period."

[0137] The gNB configures UE #1 as type #2, UE #2 as type #3, and UE #3 as type #1. If UE #2 performs a RACH procedure, it will use RACH configuration #3 and apply on / off mode #3 during the RAR monitoring window.

[0138]

[0139] The gNB configures SR resources for the UE in RRC inactive mode. The gNB provides a mapping (table) between UE types and SR resources, including different on / off modes, via system information messages and / or dedicated RRC messages. When an RRC-inactive UE triggers an SR procedure, it applies the on / off mode corresponding to its UE type within the SR response monitoring window. The gNB can change the on / off mode based on cell load or other network-level metrics. The gNB configures UE #1 as type #2, UE #2 as type #3, and UE #3 as type #1. For example, if UE #2 performs an SR procedure, it will use SR configuration #3 and apply on / off mode #3 during the SR response monitoring window.

[0140]

[0141] UE Behavior During the "Open-Close Period" in the SR Monitoring Window: When the "Close Period" expires, the UE begins the "Open Period." During the "Open Period," the UE-MR monitors the PDCCH for UL authorization from the gNB, and the UE LP-WUR is in sleep mode. When the "Open Period" expires, the UE begins the "Close Period." During the "Close Period," the UE-MR is in sleep mode, and the UE LP-WUR monitors the LP-WUS from the gNB. If the UE detects the LP-WUS during the "Close Period," the UE activates the MR, and if configured, applies an additional time offset before starting to monitor the PDCCH for UL authorization for the next "Open Period." If the UE does not detect the LP-WUS during the "Close Period," the UE-MR skips monitoring the PDCCH for UL authorization for the next "Open Period."

[0142] A preferred embodiment is characterized in that the gNB knows the UE's subscription, type, and data service history / characteristics, and classifies the UE accordingly (RRC inactive and connected). For example, a larger RAR window can be assigned to a sensor-type UE, or an on / off period can be assigned at the end of a larger RAR window. A shorter RAR window will be assigned to an XR-type UE, or an on / off period will be assigned at the beginning of the RAR window. The gNB determines the mapping of UE types in different on / off periods based on the UE's subscription, type, data service history / characteristics, and cell load or other metrics. When the gNB puts the UE into RRC inactive mode, a new or updated configuration is provided via an RRC release message.

[0143] Another preferred embodiment is characterized in that, when the UE moves under RRC_INACTIVE, it can leave its original RNA. When a new RNA is detected (e.g., the SIB of a new gNB), the UE performs an RNA update procedure. During the RNA update procedure, the UE receives updated LP-WUS configuration information from the network (e.g., an RNA update procedure response message). When in RRC_INACTIVE, the UE can perform either RA-SDT or CG-SDT procedures. The network can provide the updated LP-WUS configuration via another RRC release message.

[0144] The process flow of BS is as follows Figure 5As shown, the BS further includes a wireless communication unit configured to exchange data with the UE using radio signals, and more specifically, to exchange data with the MR unit of a wireless device included in these UEs. The wireless communication unit can be, for example, a 3G, 4G, 5G, NR, WiFi, WiMax, or other transceivers. In a preferred embodiment, the wireless communication unit of the BS corresponds to a 5G NR transceiver.

[0145] The BS also includes a wake-up signal transmitter (WUT) configured to send a wake-up signal to a UE having a wireless device including an LP-WUR. The WUT is represented separately from the wireless communication unit. However, for example, if the wireless communication unit is a 5G NR transceiver and if the wake-up signal is a specific 5G NR signal, the WUT may also be included in the wireless communication unit.

[0146] If separate from the wireless communication unit, the primary purpose of the WUT is to transmit (DL) wake-up signals. Therefore, the WUT can be unidirectional only, i.e., having only transmit (DL) capability and no receive (UL) capability. However, in some examples, the WUT can also have receive capability, allowing it to receive (UL) data from the UE's LP-WUR.

[0147] The BS may also include a network communication unit configured to exchange data with other base stations in the RAN and / or with the CN. The network communication unit may support one or more suitable communication protocols, which may be wired (including optical) and / or wireless.

[0148] As discussed above, this disclosure aims to further reduce the power consumption of wireless devices during random access and / or scheduling request processes.

[0149] As discussed above, during the random access procedure, the radio device typically sends an uplink UL request to the RAN and can receive a downlink DL response from the RAN during the DL response period.

[0150] For example, a UL request is sent by the MR unit of an active UE. However, in other examples, the UL request may be sent by the LP-WUR (provided the LP-WUR has transmission capability), in which case the MR unit may be in a low-power state when the LP-WUR sends the UL request.

[0151] For example, a UL request may correspond to a random access preamble transmitted in a UL channel (typically a random access channel RACH). In this case, a DL response typically corresponds to a random access response RAR, which may be transmitted via a DL channel (e.g., a physical downlink control channel PDCCH), and the DL response period corresponds to the RAR window.

[0152] According to another example, a UE's UL request may correspond to a msg3 message sent in the UL channel (e.g., in the PUSCH). In this case, the DL response typically corresponds to a msg4 message, which may be sent via the DL channel (e.g., the Physical Downlink Control Channel PDCCH), and the DL response period corresponds to the SR monitoring window.

[0153] To reduce the need to keep the UE's MR unit active during the DL response period, it is proposed to divide the DL response period into multiple sub-periods, which include:

[0154] - One or more inactive sub-periods during which the RAN will not send DL responses to the radio device; and

[0155] - One or more active sub-periods during which the RAN may send DL responses to the radio device.

[0156] Since the DL response cannot be received during the inactive sub-segments of the DL response period, the MR unit of the wireless device can be kept in a low-power state during each inactive sub-segment of the DL response period, so that the MR unit no longer needs to be active for the entire duration of the DL response period. Furthermore, and as will be discussed below, if the DL response period includes an active sub-segment following an inactive sub-segment, the RAN can use the inactive sub-segment to indicate whether it intends to send a DL response during the subsequent active sub-segment. For example, this indication can be sent as a wake-up signal for detection by the wireless device's LP-WUR. Therefore, if a wake-up signal is detected during an inactive sub-segment of the DL response period, the MR unit can transition to an active state during the subsequent active sub-segment of the DL response period. Conversely, if no wake-up signal is detected during an inactive sub-segment, the MR unit can remain in a low-power state during the subsequent active sub-segment. Furthermore, in some cases, if the LP-WUR does not detect a wake-up signal during the inactive sub-period of the DL response period, the LP-WUR can also transition to a low-power state (e.g., be turned off) for the duration of the subsequent active sub-period of the DL response period to further reduce energy consumption during the DL response period. In some examples, the LP-WUR can also be kept in a low-power state (e.g., be turned off) during all active sub-periods of the DL response period.

[0157] As discussed above, a DL response period may include one or more active sub-periods and one or more inactive sub-periods, arranged such that the DL response period consists of alternating active and inactive sub-periods. In other words, one active sub-period cannot be immediately followed by another active sub-period, and one inactive sub-period cannot be immediately followed by another inactive sub-period. Preferably, an active sub-period is always followed by an inactive sub-period, so as to indicate to the radio device whether its MR unit needs to be active during the subsequent active sub-period. Additionally, the network (e.g., gNB) may be configured with an additional time offset for the UE to apply before it begins monitoring DL response signals (e.g., RAR or CR messages, UL authorization indications).

[0158] In the context of a random access procedure, this division of the DL response period can be used for the RAR window and / or the contention resolution timer window. Of course, using this division for both the RAR window and the contention resolution timer window reduces the power consumption of the wireless device.

[0159] Figure 3 The illustrations represent different examples of DL response time monitoring configurations.

[0160] exist Figure 3In the example shown, the DL response period consists of six sub-periods. More specifically, the DL response period begins with a first active sub-period (on period), followed by an inactive sub-period (off period), then a second active sub-period, and so on.

[0161] In some examples, it's possible to consider all inactive sub-periods and all active sub-periods having the same duration. However, it's also possible to consider inactive sub-periods having a different duration than active sub-periods. Furthermore, inactive sub-periods can all have the same duration, or their duration can vary between different inactive sub-periods. Similarly, active sub-periods can all have the same duration, or their duration can vary between different active sub-periods.

[0162] Other DL response time monitoring configurations could be considered, for example, with Figure 3 Compared to the examples provided, additional active and / or inactive sub-periods are included. Additionally, the network (e.g., gNB) can be configured with additional time offsets to be applied before the start of the active and / or inactive sub-periods. The selection of monitoring configurations for specific DL response periods corresponds to specific, but not limiting, embodiments of this disclosure.

[0163] In some examples, the DL response period configuration can be predefined. In other examples, the DL response period configuration can be set by the radio device or by the RAN. In the latter case, the DL response period monitoring configuration to be used by the radio device is received by the radio device, for example, in system information broadcast by the RAN's BS and / or in Radio Resource Control (RRC) messages (e.g., RRC reconfiguration or release messages) sent by the RAN's BS. Of course, the RAN or CN can use other control messages to send the DL response period monitoring configuration to the radio device.

[0164] In some cases, the RAN may also send an indication to the radio device whether the DL response period begins with an active sub-period or an inactive sub-period. This indication may be included in or separate from the DL response period monitoring configuration. If this indication (regarding whether the DL response period begins with an active or inactive sub-period) is sent separately from the DL response period configuration, the structure of the DL response period can be dynamically adapted by modifying only the type of the sub-period that begins the DL response period (i.e., inactive or active sub-period). This indication may, for example, be included in system information broadcast by the RAN and / or in Radio Resource Control (RRC) messages sent by the RAN. This indication may, for example, consist of a single bit. For example, a value '0' may be used to indicate that the DL response period begins with an inactive sub-period, while a value '1' may be used to indicate that the DL response period begins with an active sub-period.

[0165] It should be noted that a BS can set the same DL response time period monitoring configuration for all UEs within its coverage area, or it can set different DL response time period monitoring configurations for all or some UEs within its coverage area. For example, a BS can set a UE-specific DL response time period monitoring configuration.

[0166] Figure 3 The paper also illustrates, in a non-limiting manner, a non-limiting example of how wireless devices can reduce their power consumption by assuming a DL response time monitoring configuration.

[0167] like Figure 4 As shown, the UE or radio device receives a configuration including the corresponding on / off mode. The UE applies the on / off mode within the RAR monitoring window, contention resolution monitoring window, and / or SR response monitoring window based on the UE type value.

[0168] Therefore, the wireless device assumes it may receive a DL response during a subsequent DL response period (e.g., a RAR window or a contention resolution timer window). Since the DL response period begins with a first active sub-period, the MR unit is active for the duration of the first active sub-period, during which the wireless device can receive a DL response (e.g., via PDCCH). However, no DL response is received during the first active sub-period.

[0169] Since no DL response will be received during the first inactive sub-period, the MR unit can be kept in a low-power state for the duration of the first inactive sub-period. However, the LP-WUR performs wake-up signal monitoring during the first inactive sub-period. If no wake-up signal is detected during the first inactive sub-period, it means that the RAN does not intend to send a DL response during the subsequent sub-period (i.e., the second active sub-period). Therefore, the MR unit can remain in a low-power state during the second active sub-period. Moreover, the LP-WUR does not need to perform wake-up signal monitoring during the second active sub-period. Therefore, the LP-WUR can be kept in a low-power state during the second active sub-period. For example, the LP-WUR can be turned off during the second active sub-period. In some examples, the LP-WUR can also be kept in a low-power state (e.g., turned off) during all active sub-periods of the DL response period.

[0170] Since no DL response will be received during the second inactive sub-period, the MR unit can remain in a low-power state for the duration of the second inactive sub-period. However, the LP-WUR performs wake-up signal monitoring during the second inactive sub-period. Figure 3In the example shown, the LP-WUR detects a wake-up signal at time T1 during the second inactive sub-period, meaning the RAN can send a DL response during the subsequent active sub-period (i.e., the third active sub-period). Therefore, the LP-WUR transitions the MR unit to an active state and maintains it for the duration of the third active sub-period, during which time the radio device can receive DL responses to its UL requests. The MR unit receives the DL response (e.g., msg2 or msg4 message) at time T2. If configured by the gNB, the UE's MR applies an additional time offset before starting to monitor for DL ​​response signals.

[0171] Figure 5 A diagram illustrating steps of an exemplary embodiment of a method for exchanging data implemented by a BS. Figure 4 The diagram illustrates corresponding steps of an exemplary embodiment of a method for exchanging data implemented by a wireless device of a UE.

[0172] It should be noted that Figure 3 Only three inactive sub-periods and three active sub-periods of equal length are shown, but if the DL response period includes fewer or more inactive sub-periods and / or active sub-periods of different lengths, the corresponding steps may also be repeated.

[0173] As discussed above, the DL response period includes one or more inactive sub-periods and one or more active sub-periods, and the BS is configured to send the DL response to the UE's radio device only during the active sub-periods. In other words, no DL response is sent to the radio device during the inactive sub-periods of the DL response period.

[0174] As discussed above, DL response periods (e.g., RAR windows or contention resolution timer windows) are typically triggered by the wireless device sending a UL request (e.g., a random access preamble / msg1 message or msg3 message) via a UL channel (e.g., RACH or PUSCH).

[0175] In some examples, the method for exchanging data includes the step of sending a DL response period monitoring configuration to the radio device. As discussed above, the DL response period monitoring configuration can be sent, for example, in system information broadcast by the BS and / or in a Radio Resource Control (RRC) message sent to the radio device. As discussed above, an indication can also be sent to the radio device whether the DL response period begins in an inactive period or an active period. Additionally, the gNB can configure an additional time offset for the UE's MR to apply before it begins monitoring the DL response signal.

[0176] As discussed above, Figure 4A diagram illustrating corresponding steps of an exemplary embodiment of a method for exchanging data, which can be implemented in a BS. Figure 5 The method shown for exchanging data is implemented by a wireless device.

[0177] The method for exchanging data includes a step of monitoring for a wake-up signal by the LP-WUR during an inactive sub-period (when the MR unit is in a low-power state) during a DL response period. If no wake-up signal is detected during the current inactive sub-period, DL response monitoring is not performed during the subsequent active sub-period, and the MR unit may remain in a low-power state for the duration of the subsequent active sub-period (and in some examples, the LP-WUR does not monitor for a wake-up signal during the subsequent active sub-period and may keep it in a low-power state). Furthermore, the method for exchanging data includes a step of triggering the transition of the MR unit to an active state and a step of monitoring for a DL response during the subsequent active sub-period.

[0178] As discussed above, a DL response period (e.g., a RAR window or a contention resolution timer window) is typically triggered by the radio device sending a UL request (e.g., a random access preamble / msg1 message or msg3 message) via a UL channel (e.g., RACH or PUSCH). The method for exchanging data includes a step of evaluating whether to send a UL request to the RAN. If a UL request is to be sent, the method for exchanging data includes the step of sending the UL request, which triggers the DL response period. Otherwise, the DL response period is not triggered.

[0179] In some examples, the method for exchanging data includes receiving from the RAN the DL response period monitoring configuration to be used during the DL response period. As discussed above, the DL response period and the UE's MR configuration are received, for example, in system information broadcast by the RAN and / or in Radio Resource Control (RRC) messages sent by the RAN. As discussed above, the radio device may also receive from the RAN an indication of whether the DL response period begins as an inactive period or an active period.

[0180] It is emphasized that this disclosure is not limited to the exemplary embodiments described above. Variations of the exemplary embodiments described above are also within the scope of this disclosure. The subject matter of this application is also applicable to other RRC states and will reduce contention between UEs and thus reduce UE power consumption.

Claims

1. A method for exchanging data in a wireless communication system, the method being implemented by a wireless device of the wireless communication system, wherein the wireless device comprises: A main radio MR unit, the MR unit being configured to exchange data with the radio access network (RAN) of the wireless communication system; And a low-power wake-up receiver (LP-WUR), the LP-WUR being configured to monitor wake-up signals sent by the RAN and to trigger a transition of the MR unit to an active state in response to the detection of a wake-up signal, wherein the radio device is configured to perform a random access and / or scheduling request process according to a received configuration, the received configuration including at least an indication for activating and / or deactivating the monitoring of the MR's response to the DL and / or the monitoring of the LP-WUR to the LP-WUS.

2. The method of claim 1, wherein the RAN node, such as the base station gNB, determines a mapping between type values ​​or unique identifiers related to the radio device and network characteristics and random access and / or scheduling request configurations.

3. The method according to claim 1 or 2, wherein the wireless device characteristics include, but are not limited to, user and / or device subscription data, device type and capabilities, data service mode and / or history.

4. The method according to claims 1 to 3, wherein network characteristics include, but are not limited to, user and / or device subscription data, network type and capabilities, device mobility and data service patterns and / or history, radio cell load and contention level, such as the number of failed access attempts or failed scheduling requests in a predefined time interval.

5. The method according to claims 1 to 4, wherein the random access and / or scheduling request configuration includes at least an indication for activating and deactivating the monitoring of the MR to the DL response or the monitoring of the LP-WUR to the LP-WUS, respectively, the DL response being, for example, a random access response and / or contention resolution response message, or a scheduling request response message, for example, a PDCCH for UL authorization.

6. The method according to claims 1 to 5, wherein the RAN node, such as the base station gNB, provides the random access and / or scheduling request configuration via system information messages and / or dedicated messages, such as RRC messages, the random access and / or scheduling request configuration including at least an indication for respectively activating and deactivating the monitoring of the MR's response to the DL and / or the monitoring of the LP-WUR's response to the LP-WUS.

7. The method according to claims 1 to 6, wherein the RAN node, such as the base station gNB, changes or updates the configuration by sending a dedicated message, such as an RRC release message, the configuration including at least an indication for respectively activating and deactivating the monitoring of the MR's response to the DL and / or the monitoring of the LP-WUR's response to the LP-WUS.

8. The method according to claims 1 to 7, wherein the RAN node, such as the base station gNB, is capable of changing or updating the configuration based on network-level analysis and metrics, the configuration including an indication for respectively activating and deactivating the monitoring of the MR's response to the DL and / or the monitoring of the LP-WUR's response to the LP-WUS, the network-level analysis and metrics being, for example, radio cell load and contention level, such as the number of failed access attempts or failed scheduling requests in a predefined time interval.

9. The method according to the preceding claim, wherein the wireless device performs a random access procedure by sending an uplink UL request to the RAN and by receiving a downlink DL response to the UL request during a DL response period, wherein the DL response period includes an inactive sub-period and an active sub-period, and the method includes, during the DL response period: - Wake-up signal monitoring is performed by the LP-WUR during the inactive sub-period, wherein the MR unit is in a low-power state; in response to the detection of a wake-up signal during the inactive sub-period: the MR unit is triggered to transition to the active state, and, if configured, an additional time offset is applied before DL response monitoring begins during the active sub-period, wherein, Based on at least one received instruction for activating and deactivating monitoring during the RAR monitoring window, the UE behavior is further characterized by: ○ When the "closed period" expires, the UE begins the "open period": ▪ During the "on period", the UE-MR monitors the RAR from the gNB, and the UE LP-WUR is in sleep mode; ○ When the "open period" expires, the UE begins the "closed period": ▪ During the "off period", the UE-MR is in the sleep mode, and the UE LP-WUR monitors the LP-WUS from the gNB: ● If the UE detects LP-WUS during the "off period", the UE activates MR, and if configured, applies an additional time offset before starting RAR monitoring for the next "on period". ● If the UE does not detect LP-WUS during the "off period", the UE-MR skips monitoring RAR for the next "on period".

10. A method for exchanging data in a wireless communication system, the method being implemented by a wireless device of the wireless communication system, wherein the wireless device comprises: A main radio MR unit, the MR unit being configured to exchange data with the radio access network (RAN) of the wireless communication system; and a low-power wake-up receiver (LP-WUR), the LP-WUR being configured to monitor a wake-up signal transmitted by the RAN and trigger a transition of the MR unit to an active state in response to detecting the wake-up signal, wherein the radio device is configured to perform a random access procedure by transmitting an uplink UL request to the RAN and by receiving a DL response to the UL request during a downlink DL response period, wherein the DL response period includes an inactive sub-period and an active sub-period, and the method includes during the DL response period: - During the inactive sub-period, wake-up signal monitoring is performed by the LP-WUR (254), wherein the MR unit is in a low-power state; in response to the detection of a wake-up signal during the inactive sub-period: (S71) the MR unit is triggered to transition to the active state, and (S72) if configured, an additional time offset is applied before starting DL response monitoring during the active sub-period, wherein, based on at least one received indication for activating and deactivating monitoring while the contention resolution timer is running, the UE behavior is characterized by, ○ When the "closed period" expires, the UE begins the "open period": ▪ During the "open period", the UE-MR monitors contention resolution messages from the gNB, and the UE LP-WUR is in sleep mode; ○ When the "open period" expires, the UE begins the "closed period": ▪ During the "off period", the UE-MR is in the sleep mode, and the UE LP-WUR monitors the LP-WUS from the gNB: - If the UE detects LP-WUS during the "off period", the UE activates MR, and if configured, applies an additional time offset before starting to monitor contention resolution messages for the next "on period". ● If the UE does not detect LP-WUS during the "off period", the UE-MR skips the monitoring contention resolution message for the next "on period".

11. A method for exchanging data in a wireless communication system, the method being implemented by a wireless device of the wireless communication system, wherein the wireless device comprises: A main radio MR unit, the MR unit being configured to exchange data with the radio access network (RAN) of the wireless communication system; and a low-power wake-up receiver (LP-WUR), the LP-WUR being configured to monitor a wake-up signal transmitted by the RAN and trigger a transition of the MR unit to an active state in response to detecting the wake-up signal, wherein the radio device is configured to perform a scheduling request process by sending an uplink UL request to the RAN and by receiving a DL response to the UL request during a downlink DL response period, wherein the DL response period includes an inactive sub-period and an active sub-period, and the method includes during the DL response period: - Wake-up signal monitoring is performed by the LP-WUR (254) during the inactive sub-period, wherein the MR unit is in a low-power state. - In response to detecting a wake-up signal during the inactive sub-period: (S71) triggering the transition of the MR unit to the active state, and (S72) if configured, applying an additional time offset before starting DL response monitoring during the active sub-period, wherein, based on at least one received indication for activating and deactivating monitoring while the scheduling disable timer is running, the UE behavior is characterized by, ○ When the "closed period" expires, the UE begins the "open period": ▪ During the "on period", the UE-MR monitors the PDCCH for UL authorization indication from the gNB, and the UE LP-WUR is in sleep mode; ○ When the "open period" expires, the UE begins the "closed period": ▪ During the "off period", the UE-MR is in the sleep mode, and the UE LP-WUR monitors the LP-WUS from the gNB: ● If the UE detects LP-WUS during the "off period", the UE activates MR, and if configured, applies an additional time offset before starting to monitor the PDCCH for UL authorization indication for the next "on period". ● If the UE does not detect LP-WUS during the "off period", the UE-MR skips monitoring the PDCCH for UL authorization indication for the next "on period".

12. The method according to any one of the preceding claims, wherein in response to no wake-up signal being detected during the inactive sub-period, the MR unit remains in the low-power state during the active sub-period.

13. The method according to any one of the preceding claims, wherein the LP-WUR does not monitor for wake-up signals during the active period in response to the absence of a wake-up signal during the inactive sub-period.

14. The method according to any one of the preceding claims, comprising receiving a DL response period configuration, the DL response period configuration defining the inactive sub-periods and the active sub-periods within the DL response period, and an additional time offset value to be applied before the start of the sub-period.

15. The method according to any one of the preceding claims, wherein the DL response time configuration is received in system information broadcast by the RAN, and / or the DL response time configuration is received in a Radio Resource Control (RRC) message sent by the RAN.

16. The method according to any one of the preceding claims, wherein the DL response period includes a plurality of active sub-periods, and / or the DL response period includes a plurality of inactive sub-periods.

17. The method according to any one of the preceding claims, comprising: The RAN receives an indication of whether the DL response period begins with an active or inactive sub-period and / or whether an additional time offset value should be applied before the sub-period begins.

18. The method according to any one of the preceding claims, wherein the indication is received in system information broadcast by the RAN, and / or the indication is received in a Radio Resource Control (RRC) message sent by the RAN.

19. The method according to any one of the preceding claims, wherein: - The UL request corresponds to the msg1 message of the random access procedure, and the DL response period corresponds to the random access response window, and / or - The UL request corresponds to the msg3 message of the random access procedure, and the DL response period corresponds to the contention resolution timer window.

20. A wireless device comprising at least one memory and at least one processor, said at least one processor being configured to implement the method according to any one of the preceding claims.

21. A user equipment (UE) comprising the wireless means according to claim 20.

22. A base station (BS) comprising the wireless device according to claim 20.

23. A wireless communication system, wherein a base station includes a processor coupled to a memory storing computer program instructions configured to perform the steps of the method as claimed in claims 1 to 20, wherein a user equipment (UE) includes a processor coupled to a memory storing computer program instructions configured to perform the steps of the method as claimed in claims 1 to 20.

24. A method for exchanging data in a wireless communication system, the method being implemented by a base station (BS), such as a gNB, of a radio access network (RAN) of the wireless communication system, wherein the BS is configured to exchange data with a wireless device, wherein the wireless device includes a main radio (MR) unit and a low-power wake-up receiver (LP-WUR), wherein the LP-WUR is configured to detect a wake-up signal transmitted by the BS and, in response to detecting the wake-up signal transmitted by the BS, trigger a transition of the MR unit to an active state, wherein the BS is configured to perform a random access procedure by monitoring an uplink UL channel to receive a UL request from the wireless device and, in response to detecting the UL request from the wireless device, by transmitting a downlink DL response to the UL request during a DL response period, wherein the DL response period includes at least one inactive sub-period and at least one active sub-period, and wherein the BS is configured to transmit the DL response to the wireless device only during at least one active sub-period of the DL response period, wherein... The BS provides configuration to the UE, which includes at least an indication for activating and / or deactivating the UE's MR to DL response monitoring and / or the LP-WUR to LP-WUS monitoring.

25. The method of claim 22, wherein the RAN node, such as a base station gNB, determines a mapping between a type value or unique identifier associated with the radio device and network characteristics and a random access and / or scheduling request configuration.

26. The method according to claims 22 to 23, wherein the wireless device characteristics include, but are not limited to, user and / or device subscription data, device type and capabilities, data service mode and / or history.

27. The method according to claims 22 to 24, wherein network characteristics include, but are not limited to, user and / or device subscription data, network type and capabilities, device mobility and data service patterns and / or history, radio cell load, and contention level, such as the number of failed access attempts or failed scheduling requests in a predefined time interval.

28. The method according to any one of the preceding claims, wherein the RAN node, such as the base station gNB, provides the random access and / or scheduling request configuration via system information messages and / or dedicated messages, such as RRC messages, the random access and / or scheduling request configuration including at least an indication for respectively activating and deactivating the monitoring of the MR's response to the DL and / or the monitoring of the LP-WUR's response to the LP-WUS.

29. The method according to any one of the preceding claims, wherein when the UE is switched from an RRC connection to an RRC inactive mode, the RAN node, such as a base station gNB, provides the random access and / or scheduling request configuration, for example by providing a UE-specific RRC release message, the random access and / or scheduling request configuration including at least an indication for activating and deactivating the monitoring of the MR response to the DL and / or the monitoring of the LP-WUR to the LP-WUS, respectively.

30. The method according to any one of claims 22 to 27, wherein the gNB provides a mapping table between type values ​​or unique identifiers and RACH configurations, wherein, The RACH configuration includes at least a RAR monitoring window and / or a contention resolution monitoring window, wherein the RAR monitoring window and / or the contention resolution monitoring window include different open / close modes configured via system information messages and / or dedicated RRC messages.

31. According to any one of claims 22 to 28, the gNB is capable of changing and / or updating the on / off mode based on network-level analysis and metrics, such as radio cell load and contention level, for example, the number of failed access attempts or failed scheduling requests in a predefined time interval.

32. The method according to any one of claims 22 to 29, comprising: In response to determining that the DL response will be sent in an active sub-period following the inactive sub-period of the DL response period, a wake-up signal is sent to the wireless device in the inactive sub-period.

33. The method according to any one of claims 22 to 30, comprising (S64) sending a DL response period configuration to the wireless device, wherein the DL response period configuration defines at least one inactive sub-period and at least one active sub-period within the DL response period, and an additional time offset value to be applied before the start of the sub-period.

34. The method according to any one of claims 22 to 31, wherein the DL response period configuration is sent in system information broadcast by the RAN, and / or the DL response period configuration is sent in a Radio Resource Control (RRC) message sent to the radio device.

35. The method according to any one of claims 22 to 32, comprising sending to the wireless device an indication of whether the DL response period begins with an active sub-period or an inactive sub-period and / or whether an additional time offset value should be applied before the start of the sub-period.

36. The method according to any one of claims 22 to 33, wherein the indication is sent in system information broadcast by the RAN, and / or the indication is sent in a Radio Resource Control (RRC) message sent by the RAN.

37. A base station gNB BS, comprising at least one memory and at least one processor (300), said at least one processor being configured to implement the method according to any one of claims 22 to 34.

38. A wireless communication system comprising at least one base station according to claim 35 and at least one user equipment (20) according to claim 21.

39. A computer program product comprising instructions that, when executed by at least one processor, configure the at least one processor to perform the method (70) according to any one of claims 1 to 19 or the method (60) according to any one of claims 22 to 34.

40. A computer-readable storage medium comprising instructions that, when executed by at least one processor, configure the at least one processor to perform the method according to any one of claims 1 to 19 or the method according to any one of claims 22 to 34.

Images