WO2024035327A1 - Économies d'énergie de nœud de réseau par l'intermédiaire d'un mécanisme de réponse d'accès aléatoire flexible - Google Patents

Économies d'énergie de nœud de réseau par l'intermédiaire d'un mécanisme de réponse d'accès aléatoire flexible Download PDF

Info

Publication number
WO2024035327A1
WO2024035327A1 PCT/SE2023/050814 SE2023050814W WO2024035327A1 WO 2024035327 A1 WO2024035327 A1 WO 2024035327A1 SE 2023050814 W SE2023050814 W SE 2023050814W WO 2024035327 A1 WO2024035327 A1 WO 2024035327A1
Authority
WO
WIPO (PCT)
Prior art keywords
random
preambles
access resources
access
offset value
Prior art date
Application number
PCT/SE2023/050814
Other languages
English (en)
Inventor
Ajit Nimbalker
Ravikiran Nory
Andres Reial
Sina MALEKI
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2024035327A1 publication Critical patent/WO2024035327A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
    • H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave using a pre-established activity schedule, e.g. traffic indication frame
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0245—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal according to signal strength
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0248—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal dependent on the time of the day, e.g. according to expected transmission activity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/006—Transmission of channel access control information in the downlink, i.e. towards the terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access

Definitions

  • the present disclosure relates generally to communications, and more particularly to communication methods and related devices and nodes supporting wireless communications.
  • NR New Radio supports lean carrier design minimizing always-on signaling.
  • a cell supporting initial access transmits an synchronization signal block (SSB) periodically, and an SSB consists of primary and secondary synchronization signals and a primary broadcast channel (PBCH).
  • SSB synchronization signal block
  • PBCH primary broadcast channel
  • the MIB (master information block) is always transmitted on the broadcast channel with a periodicity (e.g., of 80 ms) and repetitions made within that periodicity, and it includes parameters that are needed to acquire SIB1 (system information block 1) from the cell.
  • the first transmission of the MIB is scheduled in pre-determined subframes as defined in specification and repetitions are scheduled according to the period of SSB.
  • the SIB 1 is transmitted on the DL-SCH (downlink - shared channel) with a periodicity (e.g., of 160 ms) and variable transmission repetition periodicity within that periodicity.
  • the default transmission repetition periodicity of SIB1 can be a first value (e.g., 20ms) but the actual transmission repetition periodicity is up to network implementation.
  • SIB1 repetition transmission period is 20 ms.
  • SIB1 transmission repetition period is the same as the SSB period (TS 38.213, clause 13).
  • SIB1 includes information regarding the availability and scheduling (e.g., mapping of SIBs to SI (scheduling information) message, periodicity, Si-window size) of other SIBs with an indication whether one or more SIBs are only provided on-demand and, in that case, the configuration needed by the UE (user equipment) to perform the SI request.
  • SIB1 is a cellspecific SIB.
  • PBCH payload in NR includes both physical layer generated signals and MIB information scheduled from higher layers.
  • the contents of NR-PBCH can be as follows :
  • DCI downlink control information
  • SI-RNTI system information - radio network temporary identifier
  • C L ' BWP is the size of CORESET 0
  • VRB-to-PRB virtual resource block-to physical resource block mapping - 1 bit according to Table 7.3.1.2.2-5
  • Redundancy version - 2 bits as defined in Table 7.3.1.1.1-2
  • RACH (random access control channel) resources are configured via higher layers (e.g., system information) and typical RACH resources may occur periodically as shown in below figure, where each cell corresponds to a slot or a subframe.
  • the UE monitors for a RACH response in a search space (e.g., ra-searchSpace, that is configured by higher layers), and if it does not receive a response within a pre-determined amount of time, the UE tries to send RACH again.
  • a search space e.g., ra-searchSpace
  • a UE In response to a PRACH (physical random access control channel) transmission, a UE attempts to detect a DCI format 1 0 with CRC scrambled by a corresponding RA-RNTI (random access RNTI) during a window controlled by higher layers.
  • the window starts at the first symbol of the earliest CORESET the UE is configured to receive PDCCH for a search space (e.g., ra-searchSpace), that is at least one symbol, after the last symbol of the PRACH occasion corresponding to the PRACH transmission.
  • the window length in number of slots is configured by higher layers.
  • Figure 2 illustrates an example of where a set of uplink resources for random access is at slot 4 and at every 10 slots afterwards.
  • Random access response mechanisms impose tight latency constraints and/or configuration restrictions on a base station and may reduce network energy saving opportunities. For example, even in cases with light and delay- tolerant traffic, requiring the network to transmit random access in a small and limited window can lead to an unnecessary increase in network energy consumption as the network cannot utilize a dual block architecture and keep the main Tx/Rx block in sleep mode while keeping a low- complexity processing block in active state to process random access preamble reception.
  • an explicit offset may be configured for at least a subset of RACH resources/preambles, where the offset indicates the start of the RAR window relative to the RACH resource/preamble occasion where a UE transmits RACH.
  • transmitting a PRACH and receiving a response for the PRACH e.g., random access response/RAR or PDCCH with DCI CRC scrambled by RA-RNTI
  • a time window e.g., RAR window
  • the beginning of time window is based on an offset indicated by the gNB relative to the time instance when PRACH is transmitted.
  • the offset e.g., whether to use a first offset value or a second offset value, wherein second offset value is larger than first offset value
  • the offset is determined based on one or more of the following:
  • gNB determines whether the gNB is in a low power consumption/low activity state or not, e.g., during the time instance when PRACH is to be transmitted (e.g., a UE using second offset only when gNB is in a low power consumption/low activity state);
  • the PRACH preamble sequence used for transmitting the PRACH e.g., a UE using second offset only when transmitting PRACH using a specific preconfigured/prespecified preamble sequence to be used when UE determines that that the gNB is in a low power consumption/low activity state
  • the PRACH preamble sequence used for transmitting the PRACH e.g., a UE using second offset only when transmitting PRACH using a specific preconfigured/prespecified preamble sequence to be used when UE determines that that the gNB is in a low power consumption/low activity state
  • the current active UL/DL BWP during PRACH transmission e.g., a UE using second offset only when active BWP is a specific preconfigured/prespecified BWP to be used when UE determines that that the gNB is in a low power consumption/low activity state.
  • the value of offset can be a configurable value and can be indicated to the UE via Ll/MAC/SIB/RRC signaling.
  • the value may be an explicit value, or indication of a first/second value selection, or an indication of resource/preamble group where each group may be associated with a certain offset.
  • a method performed by a user equipment includes acquiring a configuration of a first set of random-access resources/preambles and a second set of random-access resources/preambles, each set of random-access resources/preambles associated with a corresponding offset value.
  • the method further includes determining a RAR window offset value based on a set selected from the first set of random-access resources/preambles and the second set of random-access resources/preambles.
  • the method further includes transmitting a PRACH based on a randomaccess resource/preamble from the set selected from the first set and the second set of randomaccess resources/preambles.
  • the method further includes monitoring for a random-access response in a RAR window whose start is dependent on the offset value determined and receiving a RAR response.
  • UEs, computer programs, and computer program products are also provided.
  • Certain embodiments may provide one or more of the following technical advantage(s).
  • Various embodiments may allow a gNB to save energy by employing dual block architectures such as a main Tx/RX block and a low-complexity processing block.
  • the low- complexity processing block can be active and processes certain signals/channels such as certain PRACH resources/preambles (e.g., wake up resource/preamble) and upon detection of wakeup preamble, the main Tx/Rx block is woken up from a relatively long sleep state to provide random access response.
  • UEs save power as they can appropriately set the RAR window to monitor RAR and avoid excess PDCCH monitoring.
  • a method performed by a network node includes transmitting a configuration of a first set of random-access resources/preambles and a second set of random-access resources/preambles towards user equipments, each set of randomaccess resources/preambles associated with a corresponding offset value.
  • the method includes determining which set of the first set of random-access resources/preambles and the second set of random-access resources/preambles will be used for normal operation mode and which set of the first set of random-access resources/preambles and the second set of random-access resources/preambles will be used for energy savings mode.
  • the method includes transmitting a signal/channel/message to provide selection information for selecting between the first set of random-access resources/procedures and the second set of random-access resources/procedures.
  • Figure 1 is an illustration of a cell supporting initial access by transmitting an SS block (SSB) periodically where the SS block consists of primary and secondary synchronization signals and a primary broadcast channel (PBCH);
  • SSB SS block
  • PBCH primary broadcast channel
  • Figure 2 is an illustration of where a set of uplink resources for random access is periodically transmitted
  • Figure 3 is an illustration of a first set and a second set of random-access resources/preambles and a first offset value and second offset value in accordance with some embodiments;
  • Figure 4 is a schematic illustration of a first set and a second set of random-access resources/preambles, a first offset value and a second offset value, and RAR windows for the first set and the second set of random-access resources/preambles in accordance with some embodiments;
  • Figure 5 is a flow chart illustrating a UE acquiring a configuration of first set and a second set of random-access resources/preambles and a first offset value and second offset value, transmitting a PRACH based on a resource/preamble selected and receiving a RAR message in a RAR window whose start is dependent on the offset vale associated with the selected set in accordance with some embodiments;
  • Figure 6-9 are flow charts illustrating operations of a UE determining an offset value in accordance with various embodiments
  • Figure 10 is a block diagram illustration of a gNB having a main Tx/RX block and a low-complexity RX block in accordance with some embodiments;
  • Figure 11 is a flow chart illustrating operations of a UE determining value in a SIB in accordance with some embodiments
  • Figure 12 is a flow chart illustrating operations of a network node in accordance with some embodiments.
  • Figure 13 is a block diagram of a communication system in accordance with some embodiments.
  • Figure 14 is a block diagram of a user equipment in accordance with some embodiments
  • Figure 15 is a block diagram of a network node in accordance with some embodiments.
  • Figure 16 is a block diagram of a host computer communicating with a user equipment in accordance with some embodiments.
  • Figure 17 is a block diagram of a virtualization environment in accordance with some embodiments.
  • Figure 18 is a block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments in accordance with some embodiments.
  • FIG. 3 illustrates a configuration of first and second sets of random-access preamble/resources.
  • UE 1400 implemented using the structure of the block diagram of Figure 14 will be used.
  • modules may be stored in memory 1410 of Figure 14, and these modules may provide instructions so that when the instructions of a module are executed by respective communication device processing circuitry 1402, the UE 1400 performs respective operations
  • the UE 1400 is configured with a set of random-access resources/preambles.
  • a first set 300 of random-access resources/preambles is associated with a first offset value 302, wherein the first offset value 302 indicates an offset relative to the RA access transmission (e.g., from beginning/end of symbol/slot of RACH transmission) at which the random-access response window starts.
  • a second set 304 of random-access resources/preambles is associated with a second offset value 306, wherein the second offset value 306 indicates an offset relative to the RA access transmission (e.g., from beginning/end of symbol/slot of RACH transmission) at which the random-access response window starts.
  • the UE 1400 When the UE 1400 transmits a random-access message based on the first set 300 of random-access resources/preambles, the UE 1400 looks for the RAR response based on the first offset value 302.
  • the UE 1400 When the UE 1400 transmits a random-access message based on the second set 304 of random-access resources/preambles, the UE 1400 looks for the RAR response based on the second offset value 306.
  • the first set 300 of random-access resources/preambles and the second set 304 of random-access resources/preambles can be configured via higher layer signaling such as via a system information message, RRC signaling, etc.
  • the second offset value 306 is larger than the first offset value 302.
  • the first offset value 306 may be 0 (or not provided, e.g. follows the same behavior as legacy such as the window starts at the first symbol of the earliest CORESET the UE 1400 is configured to receive PDCCH for Typel-PDCCH CSS set, as defined in clause 10.1, that is at least one symbol, after the last symbol of the PRACH occasion corresponding to the PRACH transmission), and the second offset value 306 may be configured explicitly by higher layer signaling, or it may be pre-configured, e.g., as part of the standardization documentations.
  • the second offset value may be in units of symbols/slots, multiples of RAR window size, etc.
  • the second offset value 306 may be indicated from a set of values such as ⁇ 3,4,5. .. .50..200 ⁇ ms.
  • Figure 4 illustrates a first offset 402 and a second offset 404 from the first set of 300 of random-access resources/preambles and the second set 304 of random-access resources/preambles, respectively.
  • the RAR window 406 for the first set 300 of random-access resources/preambles is after the first offset 402.
  • the RAR window 408 for the second set 304 of random-access resources/preambles is after the second offset 404.
  • the RAR window length 410 for the first set 300 of randomaccess resources/preambles may be different than the RAR window length 412 for the second set 304 of random-access resources/preambles.
  • FIG. 5 is flowchart illustrating operations of the UE 1400 receiving a random access response, RAR, message based on the offset value of a selected set of random-access resources/preambles.
  • the UE 1400 acquires a configuration of a first set 300 of random-access resources/preambles and a second set 304 of random-access resources/preambles, each set of random-access resources/preambles associated with a corresponding offset value.
  • the first set 300 of random-access resources/preambles is associated with offset value 302 and the second set 304 of random-access resources/preambles is associated with offset value 306.
  • the UE 1400 transmits a physical random access control channel, PRACH, based on a random-access resource/preamble from a set selected from the first set 300 of random-access resources/preambles and the second set 304 of random-access resources/preambles.
  • PRACH physical random access control channel
  • the UE 1400 monitors for a random-access response in a RAR window whose start is dependent on the offset value associated with the random-access resource/preamble set selected.
  • the RAR window starts after the RAR window offset value from the end of the transmission of the PRACH - see e.g., Figure 4. For example, if the randomaccess resource/preamble set selected was from the first set 300 of random-access resources/preambles, then the UE 1400 monitors for a random-access response in a RAR window 406 whose start is dependent on the offset value 302.
  • the UE 1400 monitors for a random-access response in a RAR window 408 whose start is dependent on the offset value 306.
  • the UE 1400 receives a RAR message.
  • a gNB can utilize the first set 300 of random-access resources/preambles and the second set 304 of random-access resources/preambles for the purpose of network/gNB energy savings.
  • the gNB may employ dual block architectures such as a main Tx/RX block and a low- complexity processing block (an example is described below in Figure 10).
  • the UE 1400 can use the second set 304 of random-access resources/preambles to perform PRACH transmission when it is aware that the gNB is in a power-saving or energy saving mode or low power consumption/low activity state. This can be a state where a gNB uses or may use low-complexity processing block for preamble detection.
  • the gNB energy saving mode can be indicated to the UE 1400 using e.g., a RRC indication such as a SI message or a SIB update, or a MAC (medium access control) indication such as a MAC CE (control element), or a LI indication such as a set of DCI bits in PDCCH or via an SSB (e.g., PBCH).
  • a RRC indication such as a SI message or a SIB update
  • a MAC (medium access control) indication such as a MAC CE (control element)
  • LI indication such as a set of DCI bits in PDCCH or via an SSB (e.
  • the UE can be configured with two BWPs (bandwidth parts), BWP1 (e.g., for normal operation) and BWP2 (e.g., for operating when gNB is in energy savings mode).
  • BWP1 e.g., for normal operation
  • BWP2 e.g., for operating when gNB is in energy savings mode
  • BWP1 and BWP2 can be DL BWPs.
  • BWP1 and BWP2 can be UL BWPs.
  • the first offset value 302 and second offset value 306 may be configured as part of the first BWP configuration and the second BWP configuration, respectively.
  • the BWPs (BWP1, BWP2, etc.) can be configured via UE-specific signaling and/or cell-specific signaling (e.g., SI messages).
  • FIG. 6 An example flow chart for the UE 1400 selecting the set of resources/preambles based on gNB power saving/energy saving mode is illustrated in Figure 6.
  • the signal/channel/message may indicate whether the gNB is operating in a power-saving or energy saving mode or not, and the indication may be used to select the first set or second set.
  • the UE 1400 acquires a configuration of a first set 300 of random-access resources/preambles and a second set 304 of random-access resources/preambles, each set of random-access resources/preambles associated with a corresponding offset value.
  • the first set 300 of random-access resources/preambles is associated with offset value 302 and the second set 304 of random-access resources/preambles is associated with offset value 306.
  • the UE 1400 detects a signal/channel/message to obtain selection information for selecting between the first set 300 of random-access resources/preambles and the second set 304 of random-access resources/preambles.
  • the signal/channel/message may indicate whether the gNB is operating in a power-saving or energy saving mode or not, and the indication may be used by the UE 1400 to select the first set 300 of random-access resources/preambles or the second set 304 of random-access resources/preambles.
  • the UE 1400 transmits a physical random access control channel, PRACH, based on a random-access resource/preamble from a set selected from the first set 300 of random-access resources/preambles and the second set 304 of random-access resources/preambles.
  • PRACH physical random access control channel
  • the UE 1400 monitors for a random-access response in a RAR window whose start is dependent on the offset value associated with the random-access resource/preamble set selected. For example, if the random-access resource/preamble set selected was from the first set 300 of random-access resources/preambles, then the UE 1400 monitors for a random-access response in a RAR window 406 whose start is dependent on the offset value 302. Similarly, if the random-access resource/preamble set selected was from the second set 304 of random-access resources/preambles, then the UE 1400 monitors for a randomaccess response in a RAR window 408 whose start is dependent on the offset value 306.
  • the UE 1400 receives a RAR message.
  • the signal/channel/message may indicate whether the gNB is operating in a power-saving or energy saving mode or not, and the indication may be used to select the random access response window offset value.
  • the UE 1400 transmits a physical random access control channel, PRACH, based on a random-access resource/preamble from a set selected from the first set 300 of random-access resources/preambles and the second set 304 of random-access resources/preambles.
  • PRACH physical random access control channel
  • the UE 1400 detects a signal/channel/message to determine a RAR window offset value.
  • the UE 1400 monitors for a random-access response in a RAR window whose start is dependent on the RAR window offset value.
  • the RAR window starts after the RAR window offset value from the end of the transmission of the PRACH - see e.g., Figure 4.
  • the UE 1400 monitors RAR window 406.
  • the UE 1400 monitors RAR window 408.
  • the UE 1400 receives a RAR message.
  • Figure 8 illustrates a flowchart for determining offset value based on BWP (e.g., UE’s active BWP or the active BWP of the cell).
  • BWP e.g., UE’s active BWP or the active BWP of the cell.
  • the UE 1400 transmits a physical random access control channel, PRACH, based on a random-access resource/preamble from a set selected from the first set 300 of random-access resources/preambles and the second set 304 of random-access resources/preambles.
  • PRACH physical random access control channel
  • the UE 1400 determines a RAR window offset based on a BWP.
  • the UE 1400 may acquire a BWP configuration from the network node 1500.
  • the active BWP of UE 1400 is BWP1
  • the UE 1400 determines the RAR window offset based on the first offset value 302.
  • the active BWP for of UE 1400 is BWP2 upon transmission of PRACH
  • the UE 1400 determines the RAR window offset based on the second offset value 306.
  • BWP1 and BWP2 can be DL BWPs or can be UL BWPs.
  • the first offset value 302 and second offset value 306 may be configured as part of the first BWP configuration and the second BWP configuration, respectively.
  • the UE 1400 monitors for a random-access response in a RAR window whose start is dependent on the RAR window offset value based on the BWP.
  • the RAR window starts after the RAR window offset value from the end of the transmission of the PRACH - see e.g., Figure 4. For example, if the RAR window offset value is offset value 302, the UE 1400 monitors RAR window 406. Similarly, if the RAR window offset value is offset value 306, the UE 1400 monitors RAR window 408.
  • the UE 1400 receives a RAR message.
  • the RAR offset info can be obtained by the UE 1400 in other ways.
  • the UE 1400 can obtain the RAR offset based on which BWP is configured by the gNB or via an explicit RAR offset or a PRACH receiver mode indication.
  • Figure 9 is a flowchart illustrating an example of these embodiments.
  • the UE 1400 determines a random access response, RAR, window offset value.
  • the UE 1400 acquires a RAR window offset configuration from the network node 1500.
  • the UE 1400 may receive the RAR window offset configuration have the RAR window offset value via radio resource control, RRC, signaling.
  • the UE 1400 acquires PRACH transmission power state information from the network node 1500. In some further embodiments, the UE 1400 acquires a bandwidth part, BWP, configuration from the network node 1500 and determines the RAR window offset vale based on the BWP configuration as described herein. [0066] In block 903, the UE 1400 transmits a physical random access control channel, PRACH. In further embodiments, the UE 1400 acquires a configuration of a first set 300 of random-access resources/preambles and a second set 304 of random-access resources/preambles, each set of random-access resources/preambles associated with a corresponding offset value.
  • the determining of the offset value is based on (or dependent on) which set is selected from the first set 300 of random-access resources/preambles and the second set 304 of random-access resources/preambles.
  • the transmitting is based on a random-access resource/preamble from a set selected from the first set 300 of random-access resources/preambles and the second set 304 of random-access resources/preambles.
  • the UE 1400 monitors for a random-access response in a RAR window whose start is dependent on the RAR window offset value.
  • the RAR window starts after the RAR window offset value from the end of the transmission of the PRACH - see e.g., Figure 4. For example, if the RAR window offset value is offset value 302, the UE 1400 monitors RAR window 406. Similarly, if the RAR window offset value is offset value 306, the UE 1400 monitors RAR window 408.
  • the UE 1400 receives a RAR response.
  • Figure 10 is a block illustrating a dual block architecture, utilized by a gNB, having a main Tx/RX block 1000 and a low-complexity processing block 1002.
  • the gNB can keep the main Tx/RX block 1000 in a low power state (e. g. in a deep sleep state, where the transition time to active transmission/reception is non-negligible, e.g., 50ms) to reduce its energy consumption.
  • the gNB can have a second much lower-power consuming block (e.g., a low-complexity processing block) that can be actively listening for the uplink signaling such as random access signal from UEs.
  • a second much lower-power consuming block e.g., a low-complexity processing block
  • the main Tx/Rx block 1000 Upon detection of a signal (e.g., wakeup preamble), the main Tx/Rx block 1000 can be woken up and can handle the rest of the random access procedure such as preparing random access response, etc. Thus, overall, the gNB energy consumption is reduced since the main Tx/Rx block 1000 is activated only when there is an actual need to wake it up.
  • a signal e.g., wakeup preamble
  • the Tx/Rx functions may be implemented in a variety of ways e.g., the Tx/Rx may encompass the low complexity Rx block 1002 and all other Tx/Rx function in a single block, and the different parts (low complexity Rx block 1002 and other Tx/Rx function) may be selectively activated or placed in sleep mode also.
  • the gNB configures a first set of random-access resources/preambles such as the first set 300 of random-access resources/preambles and a second set of random-access resources/preambles such as the second set 304 of random-access resources/preambles.
  • the first set 300 of random-access resources/preambles and the second set 304 of random-access resources/preambles shall be used in the following description.
  • the gNB indicates that the first set 300 of random-access resources/preambles is associated with a first offset value 302, wherein the first offset value 302 indicates an offset relative to the RA access transmission (e.g., from beginning/end of symbol/slot of RACH transmission) at which the random-access response window starts.
  • the gNB indicates that the second set 304 of randomaccess resources/preambles is associated with a second offset value 306, wherein the second offset value 306 indicates an offset relative to the RA access transmission (e.g., from beginning/end of symbol/slot of RACH transmission) at which the random-access response window starts.
  • the second offset value 306 may be explicitly indicated via higher layer signaling, e.g., SIB. Alternatively, the second offset value 306 and associated resources can be preconfigured, e.g., as in standardization documentations. The second offset value 306 may be dependent on the wake-up time associated with the sleep status/wakeup duration for the main Tx/Rx block.
  • the first set 300 of random-access resources/preambles may be utilized by the gNB when the gNB is operating in a relatively higher power consumption mode (e.g., main Tx/Rx block 1000 is active) while the second set 304 of random-access resources/preambles may be utilized by the gNB when the gNB is operating in a relatively lower power consumption mode (e.g., main Tx/Rx block 1000 is in sleep).
  • At least the second set 304 of random-access resources/preambles may be processed by a low-complexity processing block 1002 (or a receiver/Rx block).
  • the first set 300 of random-access resources/preambles may also be processed by the low-complexity processing block 1002.
  • the main Tx/Rx block 1000 may be in a micro-sleep state when the gNB is processing at least the first set 300 of random-access resources/preambles, while the main Tx/Rx block 1000 may be in a light-sleep/deep-sleep state when the gNB is processing the second set 304 of random-access resources/preambles.
  • the main Tx/Rx block 1000 may be referred to as full TRX and the low-complexity processing block 1002 may be a lower-power preamble-RX.
  • the UE 1400 can also save power with the methods described herein since the UE 1400 can look for RAR in suitable windows. Otherwise, the UE 1400 can waste power looking for RAR while the network cannot send the info. [0077] After sending a RACH, the UE 1400 monitors for a RACH response in a search space (e.g., ra-searchSpace, that is configured by higher layers), and if the UE 1400 does not receive a response within a pre-determined amount of time, the UE 1400 may send RACH again (e.g., power ramping, etc.).
  • a search space e.g., ra-searchSpace, that is configured by higher layers
  • the UE 1400 may use the first set 300 of random-access resources/preambles or the second set 304 of random-access resources/preambles according to the latest information (e.g., if the gNB is operating in a relatively higher power consumption mode or relatively lower power consumption mode).
  • a UE 1400 may obtain the random-access preamble configuration information from a first node (e.g., a first gNB), but the actual random access preamble transmission by the UE 1400 may be processed by another node (e.g., a second gNB) which may need longer processing time to wake up its main Tx/Rx block 1000.
  • the first set 300 of random-access resources/preambles may be associated with the first node, and the second set 304 of random-access resources/preambles may be associated with the second node.
  • the various embodiments can allow a UE 1400 to efficiently wake-up a sleeping base station without increasing UE power consumption (as the UE 1400 looks for RAR in a suitable time window).
  • the UE 1400 is configured such that the UE 1400 is only allowed to transmit the second set 304 of random-access resources/preambles, if the UE 1400 has not received a response after transmitting random access associated with the first set 300 of random-access resources/preambles, or if not configured, the UE 1400 may transmit random access based on a selected resource/preamble from the first set 300 of random-access resources/preambles or the second set 304 of random-access resources/preambles.
  • the UE 1400 may receive the RAR configuration for the first set 300 of random-access resources/preambles and second set 304 of random-access resources/preambles in one of the SIBs, e.g., SIB1 transmitted from the first node, and furthermore optionally a trigger condition by which the UE 1400 is allowed to transmit using the second set 304 of random-access resources/preambles, e.g., if the UE 1400 attempts using first set 300 of random-access resources/preambles fails for one or more times, or that the quality of a downlink reference signal (e.g., received from the first node) is below a certain threshold, e.g., SINR (signal-to- Interference and Noise Ratio) or RSRP (reference signal received power) or RSRQ (reference signal received quality) below a threshold.
  • SINR signal-to- Interference and Noise Ratio
  • RSRP reference signal received power
  • RSRQ reference signal received quality
  • the UE 1400 does not support the feature (e.g., because the UE 1400 belongs to the previous releases) the UE 1400 can just ignore the second set 304 of random-access resources/preambles and attempt to access using the first set 300 of random-access resources/preambles.
  • the UE may also obtain the current RAR offset value in other ways and may not necessarily use different RACH resources/preambles for the different offset values.
  • a fixed (non-offset dependent) set of preambles may be configured by the gNB but the gNB power state is signaled using e.g., approaches described above, like SIB1, or using available (previously reserved) bits in the PBCH.
  • the power state info i.e., the indication of whether the full TRX or the lower-power preamble-RX is utilized, or equivalently, whether legacy or a modified offset value is in effect
  • the UE 1400 may properly time the RAR window monitoring.
  • the offset value for the modified offset mode may be defined in the specification or provided additionally e.g., in SIB1.
  • the offset value may be provided explicitly in the SIB1, where the offset value may assume a continuous range of values or one of more than two discrete values. This would allow the gNB to operate the preamble-RX and/or the full TRX in multiple reduced power modes with different wake-up delays.
  • Figure 11 is a flowchart illustrating an example of determining the offset value based on the gNB power state.
  • the UE 1400 transmits a physical random access control channel, PRACH, based on a random-access resource/preamble from a set selected from the first set 300 of random-access resources/preambles and the second set 304 of random-access resources/preambles.
  • PRACH physical random access control channel
  • the UE 1400 acquires an indication about a gNB power state.
  • the indication can indicate whether the gNB power state is in a relatively higher power consumption mode (e.g., main Tx/Rx block 1000 is active) or is in a relatively lower power consumption mode (e.g., main Tx/Rx block 1000 is in sleep)
  • the UE 1400 determines an offset based on the gNB power state. For example, if the indication indicates the gNB power state is in the relatively higher power consumption mode, the UE 1400 determines the offset based on which of the first set 300 of random-access resources/preambles and the second set 304 of random-access resources/procedures specified by the gNB for the relatively higher power consumption mode. If the indication indicates the gNB power state is in the relatively lower power consumption mode, the UE 1400 determines the offset based on which of the first set 300 of random-access resources/preambles and the second set 304 of random-access resources/procedures specified by the gNB for the relatively lower power consumption mode.
  • the UE 1400 monitors for a random-access response in a RAR window whose start is dependent on the RAR window offset value based on the gNB power state. For example, if the RAR window offset value is offset value 302, the UE 1400 monitors RAR window 406. Similarly, if the RAR window offset value is offset value 306, the UE 1400 monitors RAR window 408.
  • the UE 1400 receives a RAR message.
  • modules may be stored in memory 1504 of Figure 15, and these modules may provide instructions so that when the instructions of a module are executed by respective RAN node processing circuitry 1502, RAN node 1500 performs respective operations of the flow chart.
  • the network node 1500 transmits a configuration of a first set 300 of random-access resources/procedures and a second set 304 of random-access resources/procedures. towards the UEs 1400, each set associated with a corresponding offset value 302, 306, respectively.
  • the network node 1500 determines which set of the first set 300 of random-access resources/procedures and the second set 304 of random-access resources/procedures will be used for normal operation of the gNB and which set of the first set 300 of random-access resources/procedures and the second set 304 of random-access resources/procedures will be used for energy savings mode.
  • the network node 1500 transmits a signal/channel/message to provide selection information for selecting between the first set 300 of random-access resources/procedures and the second set 304 of random-access resources/procedures.
  • the network node 1500 transmits an indication of which of the first set 300 of randomaccess resources/procedures and the second set 304 of random-access resources/procedures to be selected by the UE 1400.
  • the indication can be an indication of the gNB power state (i.e., operating in a power saving / energy saving mode or not), which BWP to use, an indication in one of the SIBS, through higher level transmissions, etc.
  • the network node 1500 responsive to operating in the energy savings mode (1002), monitors for random-access resources/preambles according to the set of randomaccess resources/preambles determined to be used for energy savings mode.
  • the network node 1500 sends a wake-up message to a main transmit/receive block 1000 responsive to detecting a random-access preamble according to the set of random-access resources/preambles determined to be used for energy savings mode 1002.
  • Various operations from the flow chart of Figure 12 may be optional with respect to some embodiments of network nodes and related methods. Regarding methods of example embodiment 7 (set forth below), for example, operations of blocks 1207 and 1209 of Figure 12 may be optional.
  • Figure 13 shows an example of a communication system 1300 in accordance with some embodiments.
  • the communication system 1300 includes a telecommunication network 1302 that includes an access network 1304, such as a radio access network (RAN), and a core network 1306, which includes one or more core network nodes 1308.
  • the access network 1304 includes one or more access network nodes, such as network nodes 1310A and 1310B (one or more of which may be generally referred to as network nodes 1310), or any other similar 3 rd Generation Partnership Project (3 GPP) access node or non-3GPP access point.
  • 3 GPP 3 rd Generation Partnership Project
  • the network nodes 1310 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1312A, 1312B, 1312C, and 1312D (one or more of which may be generally referred to as UEs 1312) to the core network 1306 over one or more wireless connections.
  • UE user equipment
  • Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors.
  • the communication system 1300 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • the communication system 1300 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 1312 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 1310 and other communication devices.
  • the network nodes 1310 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 1312 and/or with other network nodes or equipment in the telecommunication network 1302 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 1302.
  • the core network 1306 connects the network nodes 1310 to one or more hosts, such as host 1316. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts.
  • the core network 1306 includes one more core network nodes (e.g., core network node 1308) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1308.
  • Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-concealing function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • the host 1316 may be under the ownership or control of a service provider other than an operator or provider of the access network 1304 and/or the telecommunication network 1302, and may be operated by the service provider or on behalf of the service provider.
  • the host 1316 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
  • the communication system 1300 of Figure 13 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z- Wave, Near Field Communication (NFC) ZigBee, LiFi (Light Fidelity), and/or any low-power wide-area network (LPWAN) standards such as LoRa (Long Range) and Sigfox.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications
  • the telecommunication network 1302 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1302 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1302. For example, the telecommunications network 1302 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive loT (Internet of Things) services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • Massive loT Internet of Things
  • the UEs 1312 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 1304 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1304.
  • a UE may be configured for operating in single- or multi -RAT or multi -standard mode.
  • a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e., being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved- UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).
  • MR-DC multi-radio dual connectivity
  • the hub 1314 communicates with the access network 1304 to facilitate indirect communication between one or more UEs (e.g., UE 1312C and/or 1312D) and network nodes (e.g., network node 1310B).
  • the hub 1314 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 1314 may be a broadband router enabling access to the core network 1306 for the UEs.
  • the hub 1314 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 1314 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data.
  • the hub 1314 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1314 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1314 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 1314 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.
  • the hub 1314 may have a constant/persistent or intermittent connection to the network node 1310B.
  • the hub 1314 may also allow for a different communication scheme and/or schedule between the hub 1314 and UEs (e.g., UE 1312C and/or 1312D), and between the hub 1314 and the core network 1306.
  • the hub 1314 is connected to the core network 1306 and/or one or more UEs via a wired connection.
  • the hub 1314 may be configured to connect to an M2M service provider over the access network 1304 and/or to another UE over a direct connection.
  • UEs may establish a wireless connection with the network nodes 1310 while still connected via the hub 1314 via a wired or wireless connection.
  • the hub 1314 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 1310B.
  • the hub 1314 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1310B, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • FIG 14 shows a UE 1400 in accordance with some embodiments.
  • a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs.
  • Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • VoIP voice over IP
  • PDA personal digital assistant
  • gaming console or device music storage device, playback appliance
  • wearable terminal device wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise
  • UEs identified by the 3rd Generation Partnership Project (3 GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • 3 GPP 3rd Generation Partnership Project
  • NB-IoT narrow band internet of things
  • MTC machine type communication
  • eMTC enhanced MTC
  • a UE may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle- to-everything (V2X).
  • D2D device-to-device
  • DSRC Dedicated Short-Range Communication
  • V2V vehicle-to-vehicle
  • V2I vehicle-to-infrastructure
  • V2X vehicle- to-everything
  • a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • the UE 1400 includes processing circuitry 1402 that is operatively coupled via a bus 1404 to an input/output interface 1406, a power source 1408, a memory 1410, a communication interface 1412, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 14. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • the processing circuitry 1402 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1410.
  • the processing circuitry 1402 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general -purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above.
  • the processing circuitry 1402 may include multiple central processing units (CPUs).
  • the input/output interface 1406 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices.
  • Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • An input device may allow a user to capture information into the UE 1400.
  • Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof.
  • An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.
  • USB Universal Serial Bus
  • the power source 1408 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used.
  • the power source 1408 may further include power circuitry for delivering power from the power source 1408 itself, and/or an external power source, to the various parts of the UE 1400 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1408.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1408 to make the power suitable for the respective components of the UE 1400 to which power is supplied.
  • the memory 1410 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable readonly memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory 1410 includes one or more application programs 1414, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1416.
  • the memory 1410 may store, for use by the UE 1400, any of a variety of various operating systems or combinations of operating systems.
  • the memory 1410 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM external mini-dual in-line memory module
  • SDRAM synchronous dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • the UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘ SIM card.’
  • eUICC embedded UICC
  • iUICC integrated UICC
  • SIM card removable UICC commonly known as ‘ SIM card.’
  • the memory 1410 may allow the UE 1400 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 1410, which may be or comprise a device-readable storage medium.
  • the processing circuitry 1402 may be configured to communicate with an access network or other network using the communication interface 1412.
  • the communication interface 1412 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1422.
  • the communication interface 1412 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network).
  • Each transceiver may include a transmitter 1418 and/or a receiver 1420 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 1418 and receiver 1420 may be coupled to one or more antennas (e.g., antenna 1422) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 1412 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof.
  • GPS global positioning system
  • Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
  • a UE may provide an output of data captured by its sensors, through its communication interface 1412, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE.
  • the output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
  • a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection.
  • the states of the actuator, the motor, or the switch may change.
  • the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.
  • a UE when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare.
  • loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal-
  • AR Augmented Reality
  • VR
  • a UE in the form of an loT device comprises circuitry and/or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 1400 shown in Figure 14.
  • a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node.
  • the UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device.
  • the UE may implement the 3GPP NB-IoT standard.
  • a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • any number of UEs may be used together with respect to a single use case.
  • a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone.
  • the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed.
  • the first and/or the second UE can also include more than one of the functionalities described above.
  • a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
  • FIG. 15 shows a network node 1500 in accordance with some embodiments.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).
  • APs access points
  • BSs base stations
  • Node Bs Node Bs
  • eNBs evolved Node Bs
  • gNBs NR NodeBs
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
  • DAS distributed antenna system
  • network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • OFDM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • positioning nodes e.g., Evolved Serving Mobile Location Centers (E-SMLCs)
  • the network node 1500 includes a processing circuitry 1502, a memory 1504, a communication interface 1506, and a power source 1508.
  • the network node 1500 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • the network node 1500 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeBs.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • the network node 1500 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • some components may be duplicated (e.g., separate memory 1504 for different RATs) and some components may be reused (e.g., a same antenna 1510 may be shared by different RATs).
  • the network node 1500 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1500, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1500.
  • RFID Radio Frequency Identification
  • the processing circuitry 1502 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 1500 components, such as the memory 1504, to provide network node 1500 functionality.
  • the processing circuitry 1502 includes a system on a chip (SOC).
  • the processing circuitry 1502 includes one or more of radio frequency (RF) transceiver circuitry 1512 and baseband processing circuitry 1514.
  • RF radio frequency
  • the radio frequency (RF) transceiver circuitry 1512 and the baseband processing circuitry 1514 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1512 and baseband processing circuitry 1514 may be on the same chip or set of chips, boards, or units.
  • the memory 1504 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 1502.
  • volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or
  • the memory 1504 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 1502 and utilized by the network node 1500.
  • the memory 1504 may be used to store any calculations made by the processing circuitry 1502 and/or any data received via the communication interface 1506.
  • the processing circuitry 1502 and memory 1504 is integrated.
  • the communication interface 1506 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 1506 comprises port(s)/terminal(s) 1516 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 1506 also includes radio front-end circuitry 1518 that may be coupled to, or in certain embodiments a part of, the antenna 1510. Radio front-end circuitry 1518 comprises filters 1520 and amplifiers 1522.
  • the radio front-end circuitry 1518 may be connected to an antenna 1510 and processing circuitry 1502.
  • the radio front-end circuitry may be configured to condition signals communicated between antenna 1510 and processing circuitry 1502.
  • the radio front-end circuitry 1518 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection.
  • the radio front-end circuitry 1518 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1520 and/or amplifiers 1522.
  • the radio signal may then be transmitted via the antenna 1510.
  • the antenna 1510 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1518.
  • the digital data may be passed to the processing circuitry 1502.
  • the communication interface may comprise different components and/or different combinations of components.
  • the network node 1500 does not include separate radio front-end circuitry 1518, instead, the processing circuitry 1502 includes radio front-end circuitry and is connected to the antenna 1510.
  • the processing circuitry 1502 includes radio front-end circuitry and is connected to the antenna 1510.
  • all or some of the RF transceiver circuitry 1512 is part of the communication interface 1506.
  • the communication interface 1506 includes one or more ports or terminals 1516, the radio front-end circuitry 1518, and the RF transceiver circuitry 1512, as part of a radio unit (not shown), and the communication interface 1506 communicates with the baseband processing circuitry 1514, which is part of a digital unit (not shown).
  • the antenna 1510 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 1510 may be coupled to the radio front-end circuitry 1518 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 1510 is separate from the network node 1500 and connectable to the network node 1500 through an interface or port.
  • the antenna 1510, communication interface 1506, and/or the processing circuitry 1502 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment.
  • the antenna 1510, the communication interface 1506, and/or the processing circuitry 1502 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.
  • the power source 1508 provides power to the various components of network node 1500 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 1508 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1500 with power for performing the functionality described herein.
  • the network node 1500 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1508.
  • the power source 1508 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.
  • Embodiments of the network node 1500 may include additional components beyond those shown in Figure 15 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • the network node 1500 may include user interface equipment to allow input of information into the network node 1500 and to allow output of information from the network node 1500. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1500.
  • FIG 16 is a block diagram of a host 1600, which may be an embodiment of the host 1316 of Figure 13, in accordance with various aspects described herein.
  • the host 1600 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm.
  • the host 1600 may provide one or more services to one or more UEs.
  • the host 1600 includes processing circuitry 1602 that is operatively coupled via a bus 1604 to an input/output interface 1606, a network interface 1608, a power source 1610, and a memory 1612.
  • processing circuitry 1602 that is operatively coupled via a bus 1604 to an input/output interface 1606, a network interface 1608, a power source 1610, and a memory 1612.
  • Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 14 and 15, such that the descriptions thereof are generally applicable to the corresponding components of host 1600.
  • the memory 1612 may include one or more computer programs including one or more host application programs 1614 and data 1616, which may include user data, e.g., data generated by a UE for the host 1600 or data generated by the host 1600 for a UE.
  • Embodiments of the host 1600 may utilize only a subset or all of the components shown.
  • the host application programs 1614 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems).
  • the host application programs 1614 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network.
  • the host 1600 may select and/or indicate a different host for over-the-top services for a UE.
  • the host application programs 1614 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.
  • HLS HTTP Live Streaming
  • RTMP Real-Time Messaging Protocol
  • RTSP Real-Time Streaming Protocol
  • MPEG-DASH Dynamic Adaptive Streaming over HTTP
  • FIG. 17 is a block diagram illustrating a virtualization environment 1700 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components.
  • Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1700 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host.
  • VMs virtual machines
  • the virtual node does not require radio connectivity (e.g., a core network node or host)
  • the node may be entirely virtualized.
  • Applications 1702 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 1700 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware 1704 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth.
  • Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1706 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1708 A and 1708B (one or more of which may be generally referred to as VMs 1708), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 1706 may present a virtual operating platform that appears like networking hardware to the VMs 1708.
  • the VMs 1708 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1706.
  • a virtualization layer 1706 Different embodiments of the instance of a virtual appliance 1702 may be implemented on one or more of VMs 1708, and the implementations may be made in different ways.
  • Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV).
  • NFV network function virtualization
  • NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
  • a VM 1708 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of the VMs 1708, and that part of hardware 1704 that executes that VM be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 1708 on top of the hardware 1704 and corresponds to the application 1702.
  • Hardware 1704 may be implemented in a standalone network node with generic or specific components. Hardware 1704 may implement some functions via virtualization. Alternatively, hardware 1704 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1710, which, among others, oversees lifecycle management of applications 1702. In some embodiments, hardware 1704 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas.
  • hardware 1704 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas.
  • Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • some signaling can be provided with the use of a control system 1712 which may alternatively be used for communication between hardware nodes and radio units.
  • Figure 18 shows a communication diagram of a host 1802 communicating via a network node 1804 with a UE 1806 over a partially wireless connection in accordance with some embodiments.
  • host 1802 Like host 1600, embodiments of host 1802 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 1802 also includes software, which is stored in or accessible by the host 1802 and executable by the processing circuitry.
  • the software includes a host application that may be operable to provide a service to a remote user, such as the UE 1806 connecting via an over-the-top (OTT) connection 1850 extending between the UE 1806 and host 1802. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 1850.
  • OTT over-the-top
  • the network node 1804 includes hardware enabling it to communicate with the host 1802 and UE 1806.
  • connection 1860 may be direct or pass through a core network (like core network 1306 of Figure 13) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • a core network like core network 1306 of Figure 13
  • intermediate networks such as one or more public, private, or hosted networks.
  • an intermediate network may be a backbone network or the Internet.
  • the UE 1806 includes hardware and software, which is stored in or accessible by UE 1806 and executable by the UE’s processing circuitry.
  • the software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1806 with the support of the host 1802.
  • a client application such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1806 with the support of the host 1802.
  • an executing host application may communicate with the executing client application via the OTT connection 1850 terminating at the UE 1806 and host 1802.
  • the UE's client application may receive request data from the host's host application and provide user data in response to the request data.
  • the OTT connection 1850 may transfer both the request data and the user data.
  • the UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT
  • the OTT connection 1850 may extend via a connection 1860 between the host 1802 and the network node 1804 and via a wireless connection 1870 between the network node 1804 and the UE 1806 to provide the connection between the host 1802 and the UE 1806.
  • the connection 1860 and wireless connection 1870, over which the OTT connection 1850 may be provided, have been drawn abstractly to illustrate the communication between the host 1802 and the UE 1806 via the network node 1804, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 1802 provides user data, which may be performed by executing a host application.
  • the user data is associated with a particular human user interacting with the UE 1806.
  • the user data is associated with a UE 1806 that shares data with the host 1802 without explicit human interaction.
  • the host 1802 initiates a transmission carrying the user data towards the UE 1806.
  • the host 1802 may initiate the transmission responsive to a request transmitted by the UE 1806.
  • the request may be caused by human interaction with the UE 1806 or by operation of the client application executing on the UE 1806.
  • the transmission may pass via the network node 1804, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1812, the network node 1804 transmits to the UE 1806 the user data that was carried in the transmission that the host 1802 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1814, the UE 1806 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1806 associated with the host application executed by the host 1802.
  • the UE 1806 executes a client application which provides user data to the host 1802.
  • the user data may be provided in reaction or response to the data received from the host 1802.
  • the UE 1806 may provide user data, which may be performed by executing the client application.
  • the client application may further consider user input received from the user via an input/output interface of the UE 1806. Regardless of the specific manner in which the user data was provided, the UE 1806 initiates, in step 1818, transmission of the user data towards the host 1802 via the network node 1804.
  • the network node 1804 receives user data from the UE 1806 and initiates transmission of the received user data towards the host 1802.
  • the host 1802 receives the user data carried in the transmission initiated by the UE 1806.
  • factory status information may be collected and analyzed by the host 1802.
  • the host 1802 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 1802 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host 1802 may store surveillance video uploaded by a UE.
  • the host 1802 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs.
  • the host 1802 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 1802 and/or UE 1806.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1850 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 1850 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1804. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 1802.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1850 while monitoring propagation times, errors, etc.
  • computing devices described herein may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing circuitry may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components.
  • a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface.
  • non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
  • processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium.
  • some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner.
  • the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.
  • Embodiment 1 A method performed by a user equipment, the method comprising: determining (703, 803, 901) a random access response, RAR, window offset value; transmitting (503, 605, 701, 801, 903, 1101) a physical random access control channel, PRACH; monitoring (505, 607, 705, 805, 905) for a random-access response in a random access response, RAR, window whose start is dependent on the offset value determined; and receiving (507, 609, 707, 807, 907, 1109) a RAR response.
  • Embodiment 2 The method of Embodiment 1, further comprising acquiring (501, 601) a configuration of a first set 300 of random-access resources/preambles and a second set 304 of random-access resources/preambles, each set of random-access resources/preambles associated with a corresponding offset value (302, 306); wherein the transmitting (503, 605, 701, 801, 1101) of the PRACH is based on a randomaccess resource/preamble from a set selected from the first set 300 of random-access resources/preambles and the second set 304 of random-access resources/preambles; and wherein the determining of the RAR window offset value is based on which set is selected from the first set 300 of random-access resources/preambles and the second set 304 of randomaccess resources/preambles.
  • Embodiment 3 The method of any of Embodiments 1-2, further comprising: acquiring (703) a RAR window offset configuration from the network node; and wherein determining the RAR window offset value comprises determining the RAR window offset value based on the RAR window offset configuration.
  • Embodiment 4 The method of any of Embodiments 1-3, further comprising: acquiring (803) a bandwidth part, BWP; configuration from the network node; wherein determining the RAR window offset value comprises determining the RAR window offset based on the BWP configuration.
  • Embodiment 5. The method of any of Embodiments 1-4, further comprising the step of: detecting (603) a signal/channel/message to obtain selection information for selecting between the first set 300 of random-access resources/preambles and the second set 304 of random-access resources/preambles.
  • Embodiment 6 The method of Embodiment 5, wherein detecting the signal/channel/message to obtain selection information comprises: determining from the signal/channel/message whether the gNB is operating in a powersaving or energy saving mode or not; and selecting the first set 300 of random-access resources/preambles or the second set 304 of random-access resources/preambles based on whether the gNB is operating in a power-saving or energy saving mode or not.
  • Embodiment 7 The method of any of the previous Embodiments, further comprising: detecting (703) a signal/channel/message to obtain a RAR window offset value; and wherein monitoring for the random-access response in the RAR window comprises monitoring (705) for the random-access response in the RAR window whose start is dependent on the RAR window offset value.
  • Embodiment 8 The method of any of Embodiments 1-7, further comprising: acquiring (1103) an indication about a gNB power state; determining (1105) an offset value based on the gNB power state; and wherein monitoring for the random-access response in the RAR window comprises monitoring for the random access response in the RAR window whose start is dependent on the RAR window offset value based on the gNB power state.
  • Embodiment 9 The method of any of Embodiments 1-8 wherein determining (703, 803, 901) the RAR window offset value comprises receiving the RAR window offset value via radio resource control, RRC, signaling.
  • Embodiment 10 The method of any of Embodiments wherein the RAR window starts after the RAR window offset value from an end of the transmission of the PRACH.
  • Embodiment 11 A method performed by a network node, the method comprising: transmitting (1201) a configuration of a first set (300) of random-access resources/preambles and a second set (304) of random-access resources/preambles towards UEs (1400), each set of random-access resources/preambles associated with a corresponding offset value (302, 306); determining (1203) which set of the first set (300) of random-access resources/preambles and the second set (304) of random-access resources/preambles will be used for normal operation mode (1000) and which set of the first set (300) of random-access resources/preambles and the second set (304) of random-access resources/preambles will be used for energy savings mode (1002); and transmitting (1205) a signal/channel/message to provide selection information for selecting between the first set 300 of random-access resources/procedures and the second set 304 of random-access resources/procedures.
  • Embodiment 12 The method of Embodiment 11, further comprising: responsive to operating in the energy savings mode (1002), monitoring (1207) for randomaccess resources/preambles according to the set of random-access resources/preambles determined to be used for energy savings mode (1002); and sending (1209) a wake-up message to a main transmit/receive block (1000) responsive to detecting a random-access preamble according to the set of random-access resources/preambles determined to be used for energy savings mode.
  • Embodiment 13 A user equipment, UE, (1312A-1312D, 1400, 1708, 1806) comprising: processing circuitry (1402); and memory (1410) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the UE to perform operations comprising: determining (703, 803, 901) a random access response, RAR, window offset value; transmitting (503, 605, 701, 801, 903, 1101) a physical random access control channel, PRACH; monitoring (505, 607, 705, 805, 905) for a random-access response in a random access response, RAR, window whose start is dependent on the offset value determined; and receiving (507, 609, 707, 807, 907, 1109) a RAR response.
  • Embodiment 14 The UE (1312A-1312D, 1400, 1708, 1806) of Embodiment 13, wherein the memory includes further instructions that when executed by the processing circuitry causes the UE to perform operations according to any of Embodiments 2-10.
  • Embodiment 15 A user equipment, UE (1312A-1312D, 1400, 1708, 1806) adapted to: determine (703, 803, 901) a random access response, RAR, window offset value; transmit (503, 605, 701, 801, 903, 1101) a physical random access control channel, PRACH; monitor (505, 607, 705, 805, 905) for a random-access response in a random access response, RAR, window whose start is dependent on the offset value determined; and receive (507, 609, 707, 807, 907, 1109) a RAR response.
  • UE 1312A-1312D, 1400, 1708, 1806 adapted to: determine (703, 803, 901) a random access response, RAR, window offset value; transmit (503, 605, 701, 801, 903, 1101) a physical random access control channel, PRACH; monitor (505, 607, 705, 805, 905) for a random-access response in a random access response, RAR, window whose start is dependent on the offset value determined
  • Embodiment 16 The UE (1312A-1312D, 1400, 1708, 1806) of Embodiment 15, wherein the UE (1312A-1312D, 1400, 1708, 1806) is adapted to perform according to any of Embodiments 2-10.
  • Embodiment 17 A computer program comprising program code to be executed by processing circuitry (1402) of a user equipment, UE, (1312A-1312D, 1400, 1708, 1806), whereby execution of the program code causes the UE (1312A-1312D, 1400, 1708, 1806) to perform operations comprising: determining (703, 803, 901) a random access response, RAR, window offset value; transmitting (503, 605, 701, 801, 903, 1101) a physical random access control channel, PRACH; monitoring (505, 607, 705, 805, 905) for a random-access response in a random access response, RAR, window whose start is dependent on the offset value determined; and receiving (507, 609, 707, 807, 907, 1109) a RAR response.
  • Embodiment 18 The computer program of Embodiment 17 comprising further program code to be executed by processing circuitry (1402) of the UE (1312A-1312D, 1400, 1708, 1806), whereby execution of the program code causes the UE (1312A-1312D, 1400, 1708, 1806) to perform operations according to any of embodiments 2-10.
  • Embodiment 19 A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (1402) of a user equipment, UE, (1312A-1312D, 1400, 1708, 1806), whereby execution of the program code causes the UE (1312A- 1312D, 1400, 1708, 1806) to perform operations comprising: determining (703, 803, 901) a random access response, RAR, window offset value; transmitting (503, 605, 701, 801, 903, 1101) a physical random access control channel, PRACH; monitoring (505, 607, 705, 805, 905) for a random-access response in a random access response, RAR, window whose start is dependent on the offset value determined; and receiving (507, 609, 707, 807, 907, 1109) a RAR response.
  • Embodiment 20 The computer program product of Embodiment 19 wherein the non-transitory storage medium includes further program code to be executed by the processing circuitry (1402) of the UE (1312A-1312D, 1400, 1708, 1806), whereby execution of the program code causes the UE (1312A-1312D, 1400, 1708, 1806) to perform operations according to any of Embodiments 2-8.
  • a network node (1312A-1312B, 1500, 1708, 1807) comprising: processing circuitry (1502); and memory (1504) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the network node (1312A- 1312B, 1500, 1708, 1807) to perform operations comprising: transmitting (1201) a configuration of a first set (300) of random-access resources/preambles and a second set (304) of random-access resources/preambles towards UEs (1400), each set of random-access resources/preambles associated with a corresponding offset value (302, 306); determining (1203) which set of the first set (300) of random-access resources/preambles and the second set (304) of random-access resources/preambles will be used for normal operation mode (1000) and which set of the first set (300) of randomaccess resources/preambles and the second set (304) of random-access resources/preambles will be used for
  • Embodiment 22 The network node (1312A- 1312B, 1500, 1708, 1807) of Embodiment 21, wherein the memory includes further instructions that when executed by the processing circuitry causes the UE to perform operations according to Embodiment 12.
  • a network node (1312A-1312B, 1500, 1708, 1807) adapted to: transmit (1201) a configuration of a first set (300) of random-access resources/preambles and a second set (304) of random-access resources/preambles towards UEs (1400), each set of random-access resources/preambles associated with a corresponding offset value (302, 306); determine (1203) which set of the first set (300) of random-access resources/preambles and the second set (304) of random-access resources/preambles will be used for normal operation mode (1000) and which set of the first set (300) of random-access resources/preambles and the second set (304) of random-access resources/preambles will be used for energy savings mode (1002); and transmit (1205) a signal/channel/message to provide selection information for selecting between the first set 300 of random-access resources/procedures and the second set 304 of random-access resources/procedures.
  • Embodiment 24 The network node (1312A- 1312B, 1500, 1708, 1807) of Embodiment 23, wherein the network node (1312A-1312B, 1500, 1708, 1807) is adapted to perform according to Embodiment 12.
  • Embodiment 25 A computer program comprising program code to be executed by processing circuitry (1502) of a network node (1312A-1312B, 1500, 1708, 1807), whereby execution of the program code causes the network node (1312A-1312B, 1500, 1708, 1807) to perform operations comprising: transmitting (1201) a configuration of a first set (300) of random-access resources/preambles and a second set (304) of random-access resources/preambles towards UEs (1400), each set of random-access resources/preambles associated with a corresponding offset value (302, 306); determining (1203) which set of the first set (300) of random-access resources/preambles and the second set (304) of random-access resources/preambles will be used for normal operation mode (1000) and which set of the first set (300) of random-access resources/preambles and the second set (304) of random-access resources/preambles will be used for energy savings mode (1002); and transmit
  • Embodiment 26 The computer program of Embodiment 25 comprising further program code to be executed by processing circuitry (1502) of the network node (1312A-1312B, 1500, 1708, 1807), whereby execution of the program code causes the network node (1312A- 1312B, 1500, 1708, 1807) to perform operations according to Embodiment 12.
  • Embodiment 27 A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (1502) of a network node (1312A-1312B, 1500, 1708, 1807), whereby execution of the program code causes the network node (1312A-1312B, 1500, 1708, 1807) to perform operations comprising: transmitting (1201) a configuration of a first set (300) of random-access resources/preambles and a second set (304) of random-access resources/preambles towards UEs (1400), each set of random-access resources/preambles associated with a corresponding offset value (302, 306); determining (1203) which set of the first set (300) of random-access resources/preambles and the second set (304) of random-access resources/preambles will be used for normal operation mode (1000) and which set of the first set (300) of random-access resources/preambles and the second set (304) of random-access resources/preambles will be used for normal
  • Embodiment 28 The computer program product of Embodiment 27 wherein the non-transitory storage medium includes further program code to be executed by the processing circuitry (1502) of the network node (1312A-1312B, 1500, 1708, 1807), whereby execution of the program code causes the network node (1312A-1312B, 1500, 1708, 1807) to perform operations according to Embodiment 12.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Un procédé mis en œuvre par un équipement utilisateur comprend l'acquisition (501, 601) d'une configuration d'un premier ensemble (300) de ressources ou de préambules d'accès aléatoire et d'un second ensemble (304) de ressources ou de préambules d'accès aléatoire, chaque ensemble de ressources ou de préambules d'accès aléatoire étant associé à une valeur de décalage correspondante (302, 306). Le procédé consiste en outre à déterminer (703, 803, 901) une valeur de décalage de fenêtre RAR sur la base d'un ensemble sélectionné parmi le premier ensemble (300) de ressources ou de préambules d'accès aléatoire et le second ensemble (304) de ressources ou de préambules d'accès aléatoire. Le procédé comprend en outre la transmission (503, 605, 701, 801, 903, 1101) d'un PRACH sur la base d'une ressource ou un préambule d'accès aléatoire de l'ensemble sélectionné parmi le premier ensemble (300) et le second ensemble (304) de ressources ou de préambules d'accès aléatoire. Le procédé comprend en outre la surveillance (505, 607, 705, 805, 905) d'une réponse d'accès aléatoire dans une fenêtre RAR dont le début dépend de la valeur de décalage déterminée et la réception (507, 609, 707, 807, 907, 1109) d'une réponse RAR.
PCT/SE2023/050814 2022-08-12 2023-08-11 Économies d'énergie de nœud de réseau par l'intermédiaire d'un mécanisme de réponse d'accès aléatoire flexible WO2024035327A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263397598P 2022-08-12 2022-08-12
US63/397,598 2022-08-12

Publications (1)

Publication Number Publication Date
WO2024035327A1 true WO2024035327A1 (fr) 2024-02-15

Family

ID=87748150

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2023/050814 WO2024035327A1 (fr) 2022-08-12 2023-08-11 Économies d'énergie de nœud de réseau par l'intermédiaire d'un mécanisme de réponse d'accès aléatoire flexible

Country Status (1)

Country Link
WO (1) WO2024035327A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200100179A1 (en) * 2018-09-21 2020-03-26 Comcast Cable Communications, Llc Activation and Deactivation of Power Saving Operation
WO2021087850A1 (fr) * 2019-11-07 2021-05-14 Qualcomm Incorporated Configuration améliorée pour masque de canal physique d'accès aléatoire et fenêtre de réponse d'accès aléatoire
US20210251012A1 (en) * 2020-02-07 2021-08-12 Qualcomm Incorporated Random access procedures for new radio (nr) networks

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200100179A1 (en) * 2018-09-21 2020-03-26 Comcast Cable Communications, Llc Activation and Deactivation of Power Saving Operation
WO2021087850A1 (fr) * 2019-11-07 2021-05-14 Qualcomm Incorporated Configuration améliorée pour masque de canal physique d'accès aléatoire et fenêtre de réponse d'accès aléatoire
US20210251012A1 (en) * 2020-02-07 2021-08-12 Qualcomm Incorporated Random access procedures for new radio (nr) networks

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Projection; Technical Specification Group Radio Access Network; NR; Physical channels and modulation (Release 17", 3GPP TS 38.211, June 2022 (2022-06-01)
"3rd Generation Partnership Projection; Technical Specification Group Radio Access Network; NR; Physical layer procedures for control (Release 17", 3GPP TS 38.213, June 2022 (2022-06-01)
"3rd Generation Partnership Projection; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 17", 3GPP TS 38.331, June 2022 (2022-06-01)

Similar Documents

Publication Publication Date Title
US11792693B2 (en) Methods and apparatuses for redirecting users of multimedia priority services
WO2023163629A1 (fr) Adaptation de puissance de transmission de réseau économe en énergie
WO2023113674A1 (fr) Fonctionnement d'équipement utilisateur (ue) avec configuration d'économie d'énergie de station de base
WO2023012705A1 (fr) Partitionnement d'accès aléatoire et rapport d'accès aléatoire
WO2024035327A1 (fr) Économies d'énergie de nœud de réseau par l'intermédiaire d'un mécanisme de réponse d'accès aléatoire flexible
WO2024093617A1 (fr) Sélection de cellule pour un accès au réseau dans un scénario de délégation de cellule
US20240172028A1 (en) Pre-configured gap status at gap configuration
WO2023207433A1 (fr) Procédés et appareils de communication dans un système de communication sans fil avec une caractéristique d'économie d'énergie de réseau
WO2024095231A1 (fr) Inclusion conditionnelle d'une combinaison de caractéristiques dans un rapport de ra
WO2024014996A1 (fr) Signalisation d'informations d'économie d'énergie dans un réseau d'accès radio
WO2023211347A1 (fr) États de déclenchement apériodiques inactifs pour économie d'énergie
WO2023209686A1 (fr) Systèmes et procédés de signalisation d'invalidation
WO2024095224A1 (fr) Transmission et réception discontinues de cellule
WO2023165970A1 (fr) Mise en œuvre d'une transmission ou transmission d'un bloc de signal de synchronisation de liaison latérale
WO2023211337A1 (fr) Procédés de détermination du retard d'application pour une commutation de groupe d'ensembles d'espaces de recherche
WO2023249529A1 (fr) Gestion de problèmes de coexistence dans un dispositif
WO2023053088A1 (fr) Procédés et appareils pour rlm pour opération mtrp entre cellules
WO2024096809A1 (fr) Signal de découverte
WO2024072307A1 (fr) Bwp et mobilité inter-cellules l1-l2
CA3223024A1 (fr) Surveillance de canal de commande de liaison descendante physique pour une planification inter-porteuses amelioree
WO2024102048A1 (fr) Adressage d'ue avec des codes wus
WO2024072281A1 (fr) Procédés pour la fabrication d'un équipement utilisateur conscient d'une transmission ou d'une réception discontinue par un réseau
WO2023132772A1 (fr) Mises à jour de commande d'alimentation pour cg-sdt
WO2024096810A1 (fr) Détermination et transmission de signal de réveil
WO2024023347A1 (fr) Correction du nombre de trames pour réception discontinue

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23757720

Country of ref document: EP

Kind code of ref document: A1