[go: up one dir, main page]

WO2023211359A1 - Signal de réveil pour stations de base utilisant un canal d'accès aléatoire - Google Patents

Signal de réveil pour stations de base utilisant un canal d'accès aléatoire Download PDF

Info

Publication number
WO2023211359A1
WO2023211359A1 PCT/SE2023/050412 SE2023050412W WO2023211359A1 WO 2023211359 A1 WO2023211359 A1 WO 2023211359A1 SE 2023050412 W SE2023050412 W SE 2023050412W WO 2023211359 A1 WO2023211359 A1 WO 2023211359A1
Authority
WO
WIPO (PCT)
Prior art keywords
network node
gnb
wake
preamble
configuration
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/SE2023/050412
Other languages
English (en)
Inventor
Xu Zhu
Sina MALEKI
Andres Reial
Ilmiawan SHUBHI
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of WO2023211359A1 publication Critical patent/WO2023211359A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] 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
    • H04W52/0235—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 where the received signal is a power saving command
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0686—Hybrid systems, i.e. switching and simultaneous transmission
    • H04B7/0695—Hybrid systems, i.e. switching and simultaneous transmission using beam selection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0203—Power saving arrangements in the radio access network or backbone network of wireless communication networks
    • H04W52/0206—Power saving arrangements in the radio access network or backbone network of wireless communication networks in access points, e.g. base stations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] 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. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0261—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level
    • H04W52/0274—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof
    • H04W52/028—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof switching on or off only a part of the equipment circuit blocks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/0085—Hand-off measurements
    • H04W36/0094—Definition of hand-off measurement parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/20—Selecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states

Definitions

  • the present disclosure relates to methods, apparatuses, and systems for improving the power efficiency of cellular networks.
  • a User Equipment performs Public Land Mobile Network (PLMN) selection, cell selection/reselection, and initial access to register/re-register itself to a network (NW) when the UE needs to establish connections to the NW.
  • the PLMN is selected by reading PLMN identities, as specified in Third Generation Partnership Project (3GPP) Technical Specification (TS) 38.331, version 16.8.0, 2022/04/14, in the strongest cell and reporting them to the Non- Access Stratum (NAS) as high-quality PLMNs without a Reference Signal Received Power (RSRP) value if the RSRP is greater than or equal to -110 decibel-milliwatt (dBm) or reporting the PLMN identities with corresponding RSRP values if the UE has been able to read these PLMN identities and none of them satisfy the high-quality criteria as specified in 3GPP TS 38.304, version 17.0.0, 2022/04/13.
  • 3GPP Third Generation Partnership Project
  • TS Technical Specification
  • NAS Non- Access Stratum
  • the cell selection procedure can be performed following a process including: (1) initial cell selection with no prior knowledge of which Radio Frequency (RF) channels are New Radio (NR) frequencies or (2) cell selection by leveraging stored information.
  • the selected cell may fulfill criteria of cell selection reception (RX) level value (“Srxlev”) and cell selection quality value (“Squal”), which are partly based on RSRP and System Information Block 1 (SIB 1) as specified in 3 GPP TS 38.133, version 17.5.0, 2022/04/01. If no suitable cell fulfills the cell selection criteria, the UE will camp on an acceptable cell or may be stuck in “Any Cell Selection,” at which point only emergency phone services may be available.
  • RX cell selection reception
  • SIB 1 System Information Block 1
  • the UE can start uplink synchronization with Physical Random Access Channel (PRACH), e.g., by transmitting a preamble as specified in 3GPP TS 38.321, version 17.0.0, 2022/04/14.
  • PRACH Physical Random Access Channel
  • the UE transmits a preamble through PRACH to start a random access procedure.
  • RACH Random Access Channel
  • SIB1 e.g., preamble format and RACH occasion as per 3GPP TS 38.331, version 16.8.0, 2022/04/14, and 3GPP TS 38.213, version 17.1.0, 2022/04/08.
  • the preamble used by the UE can be transmitted at a specified RACH occasion which is a part of a RACH slot.
  • the UE Upon completion of the RACH procedure, the UE will camp on a cell and be registered in a Radio Resource Control (RRC) connected state.
  • RRC Radio Resource Control
  • NR has been expected to improve energy efficiency of the network due to lean signal design, e.g., use of periodic reference signals instead of always-on signals.
  • LTE Long Term Evolution
  • BW bandwidth
  • gNB Next Generation Node B or NR NodeB
  • gNB Next Generation Node B
  • SI system information
  • the gNB only transmits Synchronization Signal Blocks (SSBs) and configured system information (SI) in idle mode, and the periodicity of these signals can be extended to tens or hundreds of milliseconds. This, in turn, allows for both deeper and longer periods of sleep for the gNB when there is no ongoing data transmission, which can have a significant impact on the overall network energy consumption.
  • SSBs Synchronization Signal Blocks
  • SI system information
  • a sleeping gNB uses its receiver, preferably a Low- Power (or wake-up) Receiver (LPR), to monitor for a wake-up signal of the UE.
  • the receiver (e.g., LPR) of the gNB can continuously monitor pre-configured frequency resources for such a wake-up signal, or the receiver of the gNB can monitor pre-configured frequency resources for such a wake-up signal at specified times (Wake-Up Signal (WUS) opportunities).
  • WUS Wake-Up Signal
  • the gNB cannot achieve a complete sleep. That is, the gNB cannot turn off all its transceivers and their related components. Therefore, the gNB is unable to achieve the maximum reduction in power consumption. New techniques are needed to improve network energy efficiency.
  • a method is performed by a first network node.
  • the method includes entering into a sleep mode and informing a second network node that the first network node has entered into the sleep mode.
  • the method further includes receiving, from the second network node, a signal to wake-up, and waking-up responsive to the receiving the signal to wake-up from the second network node.
  • Certain embodiments may provide one or more technical advantages.
  • the methods, apparatuses, and computer readable media proposed in the present disclosure can save energy consumed by network nodes such as the disclosed first network node by placing the first network node into a sleep mode.
  • the first network node method further includes transmitting System Information (SI) to the second network node and/or a User Equipment (UE), and/or monitoring, by the first network node, a Wake-Up signal of Physical Random Access Channel (WU-PRACH) on a predefined resource.
  • the method further includes transmitting a configuration of the WU-PRACH from the first network node to the UE, and/or resuming, at the first network node, a transmitting one or more signals and/or one or more channels at an output power after waking up.
  • the WU-PRACH is a fixed network-wide configuration.
  • the output power of the first network node is a full output power of the first network node.
  • the output power of the first network node is a stepwise power less than the full output power of the first network node.
  • a method is performed by a second network node.
  • the method includes receiving, from a first network node, an indication that the first network node has entered into a sleep mode, receiving a preamble from a UE, and transmitting, to the first network node, a signal to wake-up the first network node responsive to receiving the preamble from the UE.
  • the second network node method further includes broadcasting to the UE, by the second network node, a configuration or information, wherein the configuration or information includes information about when, how, and/or where the UE is allowed to transmit the preamble to trigger the second network node to wake-up one or more neighboring network nodes that are in the sleep mode.
  • the configuration or information indicates that the UE can transmit the preamble to trigger the second network node to wake-up the one or more neighboring network nodes that are in the sleep mode when the UE is in an idle or an inactive state and the UE does not find a cell to camp on.
  • the configuration or information indicates that the UE can transmit the preamble to trigger the second network node to wake-up the one or more neighboring network nodes that are in the sleep mode when the UE is in a connected state and the UE loses a connection with a serving network node before a handover is triggered.
  • the configuration or information indicates that the UE can transmit the preamble to trigger the second network node to wake-up the one or more neighboring network nodes that are in the sleep mode: (a) when the UE can receive system information from one or more neighboring network nodes and/or receive synchronization signals from the one or more neighboring network nodes; (b) during a Random Access Channel (RACH) occasion of the second network node if the UE is in the idle or the inactive state; or (c) when the UE will lose its connection when the UE is in the connected state.
  • RACH Random Access Channel
  • the configuration or information indicates a preamble resource over a Physical Random Access Channel (PRACH), and a specific number of repetitions for a transmission of the preamble to trigger wake-up of the one or more neighboring network nodes that are in the sleep mode.
  • the configuration or information indicates the second network node as a network node to which the UE is to transmit the preamble.
  • the configuration or information indicates how often the UE can transmit the preamble to request wake-up of a sleeping network node.
  • the configuration or information indicates one or more areas of a cell served by the second network node in which the UE is allowed, or not allowed, to request wake-up of the one or more neighboring network nodes that are in the sleep mode.
  • the one or more areas of the cell are defined by a specific Public Land Mobile Network (PLMN).
  • PLMN Public Land Mobile Network
  • the specific PLMN is one or more of (a) a PLMN selected by a Non-Access Stratum (NAS); (b) a registered PLMN on which a certain location registration outcome has occurred; or (c) an equivalent PLMN of an equivalent PLMN list.
  • the one or more areas of the cell are defined by one or more specific beams associated to one or more specific Synchronization Signal Blocks (SSBs).
  • SSBs Synchronization Signal Blocks
  • the preamble is a PRACH preamble.
  • the preamble is a Wake-Up Signal (WUS).
  • the method further includes determining, by the second network node, that the preamble is the WUS when the second network node: (a) determines a direction and a distance of the UE based on an SSB index and Timing Advance (TA) information; and (b) determines that the TA of the UE exceeds a predefined threshold or a signal strength of the preamble is lower than the predefined threshold.
  • the UE is in an idle state or an inactive state.
  • the method further includes receiving, measurement results of a Reference Signal Received Power (RSRP) of the second network node and an RSRP of a first network node; and transmitting, a signal for requesting: (a) a first network node to wake-up, and (b) the first network node to transmit SI of the first network node to the second network node and/or the UE.
  • the transmitting the signal includes transmitting, the signal when the RSRP of the second network node falls below a predefined threshold and the RSRP of the first network node does not satisfy one or more criteria for a handover.
  • the method further includes requesting, to switch a direction of a powered-on beam of the first network node.
  • a method is performed by a UE.
  • the method includes obtaining a configuration or information indicating when, how, and/or where the UE is allowed, via a second network node, to request a wake-up of one or more first network nodes that are in a sleep state, wherein the configuration or information indicates the second network node as a network node to which the UE is to transmit the preamble; and transmitting, to the second network node, a preamble to request the wake-up of the one or more first network nodes that are in the sleep state.
  • the configuration or information indicates a preamble resource over a PRACH and a specific number of repetitions for a transmission of the preamble to trigger wake-up of the one or more neighboring network nodes that are in the sleep mode. In some embodiments, the configuration or information indicates how often the UE can transmit the preamble to request wake-up of a sleeping network node. In some embodiments, the configuration or information indicates one or more areas of a cell served by the second network node in which the UE is allowed, or not allowed, to request wake-up of the one or more neighboring network nodes that are in the sleep mode.
  • the obtaining the configuration or information includes retrieving the configuration or information from a storage of the UE, wherein the configuration or information is predefined in accordance with a standard. In some embodiments, the obtaining the configuration or information includes receiving the configuration or information from the second network node. In some embodiments, the UE is connected via a Radio Resource Control (RRC). In some embodiments, the UE is in an idle state or an inactive state.
  • RRC Radio Resource Control
  • a UE in another aspect, includes processing circuitry configured to cause the UE to: obtain a configuration or information indicating when, how, and/or where the UE is allowed, via a second network node, to request a wake-up of one or more first network nodes that are in a sleep state, wherein the configuration or information indicates the second network node as a network node to which the UE is to transmit the preamble; and transmit, to the second network node, a preamble to request the wake-up of the one or more first network nodes that are in the sleep state.
  • first node, second node, and UE apparatuses and computer readable media are disclosed.
  • the apparatuses include processing circuitry that performs any method as described above and elsewhere in this patent disclosure.
  • Certain embodiments may provide one or more of the following technical advantages.
  • the methods, apparatuses, and computer readable media proposed in the present disclosure can save energy consumed by idle Next Generation Node Bs or NR NodeBs (gNBs) when transmitting periodic signals while avoiding the impact on the registration of RRC Idle UEs and the mobility of RRC Inactive/Connected UEs when, for example, UEs are in or about to enter a coverage hole.
  • gNBs Next Generation Node Bs or NR NodeBs
  • Figure 1 shows an example of a Next Generation Node B (gNB) in a sleep mode, in accordance with some embodiments.
  • gNB Next Generation Node B
  • FIG. 2 shows an example of a User Equipment (UE) entering a coverage hole caused by powering off a gNB, in accordance with some embodiments.
  • UE User Equipment
  • Figure 3 shows an example flow chart detailing a process related to Figure 1, in accordance with some embodiments.
  • Figure 4 shows an example flow chart detailing a process related to Figure 2.
  • Figure 5 shows an example of a communication system, in accordance with some embodiments.
  • Figure 6 shows a UE, in accordance with some embodiments.
  • Figure 7 shows a network node, in accordance with some embodiments.
  • Figure 8 shows a host, in accordance with some embodiments.
  • Figure 9 illustrates a virtualization environment, in accordance with some embodiments.
  • Figure 10 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection, in accordance with some embodiments.
  • the present disclosure describes embodiments of a method for a network node (e.g., a base station such as, e.g., a Next Generation Node B (gNB)) to enter a sleep mode and wake-up, when necessary, with minimal impact to any User Equipment (UE) which is in a coverage hole or is entering a coverage hole.
  • a network node e.g., a base station such as, e.g., a Next Generation Node B (gNB)
  • UE User Equipment
  • the network node is a gNB; however, the embodiments described herein are not limited thereto.
  • the embodiments described herein are equally relevant to gNB sleeping in parts of the hosted cell, e.g., sectors, beams.
  • a cell goes to sleep in all sectors and beams and thus can go into a deeper sleep mode, compared to the latter where the sleep mode in one example performs in a reduced capability mode, e.g., with a fewer number of beams, sectors, or less coverage, etc.
  • the gNB may determine to sleep partially for some transmissions only. For example, the gNB may stay in a sleep mode for a certain bandwidth, certain channels, certain channels when including certain information, or for certain signals but not for other signals/channels/ or channels when including certain other information.
  • Radio Resource Control (RRC) connected UE moving into these areas may face handover trouble since the neighboring gNB may fall asleep and the serving gNB cannot trigger a handover based on MeasurementReport unless the sleeping gNB is woken up by the serving gNB.
  • RRC Radio Resource Control
  • switching a gNB from an idle mode to sleep mode may have a negative effect on another neighboring gNB especially when not fully overlapping in coverage.
  • Any potential UE at the border of the gNB may, due to the power being off, choose to camp and even start transmission of its traffic on a neighboring gNB instead, which may increase the burden on the neighboring gNB and reduce the quality of service for the UE since the neighboring gNB is not the optimal gNB for the UE.
  • Embodiments of the present disclosure propose to introduce (i) signaling between a UE and a gNB and (ii) signaling between multiple gNBs, for waking up a gNB in sleep mode when the UE loses coverage.
  • signaling between the UE and the gNB uses Physical Random Access Channel (PRACH) resources (which may be referred to as Wake-Up PRACH or “WU- PRACH”) for the UE to ask at least one gNB (currently in sleep mode) to wake-up and resume transmission of, e.g., reference signals.
  • PRACH Physical Random Access Channel
  • signaling between the gNBs enables the gNBs to inform each other when entering/exiting sleep mode.
  • a gNB asks another gNB in sleep mode to wake-up and start to transmit signals, e.g., system information (SI).
  • SI system information
  • a method performed by the network includes one or more of the following aspects:
  • a first gNB operating in a sleep mode 1.
  • a neighboring gNB broadcasts a configuration for when/how/where UEs may request waking up the sleeping gNB.
  • the “when” in the configuration further includes
  • a UE can receive system information of surrounding gNBs, e.g., Synchronization Signal Block (SSB) and System Information Block 1 (SIB1).
  • SSB Synchronization Signal Block
  • SIB1 System Information Block 1
  • An RRC Idle/Inactive UE should request to wake-up a sleeping gNB at RACH occasions of another gNB that the UE is receiving system information from.
  • Waking-up can be requested by a serving gNB when RRC Connected UE will lose the connection.
  • the “how” is the configuration for a specific preamble resource over PRACH including a specific number of repetitions for better reachability through which the UE may ask to wake-up the sleeping gNB.
  • the “how” includes a configuration for indicating to a UE which gNB the UE should transmit preamble resource to.
  • the “how” further includes a configuration for how often the UE may transmit a preamble resource to ask to wake-up the sleeping gNB.
  • the “where” in the configuration includes areas of the cell staying in the sleep mode in which the UE is allowed to ask to wake-up the sleeping gNB.
  • the area may be defined by specific beams e.g., wide beams defined/associated to SSBs) in which the UE is allowed/not allowed to ask to wake-up the sleeping gNB.
  • the area may be defined by a specific Public Land Mobile Network (PLMN), e.g., the UE is only allowed to ask to wake-up the sleeping gNB when the cell is part of either:
  • PLMN Public Land Mobile Network
  • the gNB that is in the sleep mode stays powered on for at least a certain duration.
  • a first gNB informs a second gNB that it is in sleep mode.
  • the first gNB informs the second gNB that the first gNB is in the sleep mode
  • the second gNB asks to wake-up the first gNB based on internal stimuli (e.g., Reference Signal Received Power (RSRP) measurements)
  • RSRP Reference Signal Received Power
  • the second gNB asks the first gNB in which direction or beam the signal power will be directed.
  • a UE asks for turning on surrounding gNBs via PRACH if it cannot find any cell that fulfills cell (re)selection criteria to camp on but can still receive system information of surrounding gNBs
  • the UE may receive a configuration from a gNB including information about whether there is a gNB nearby is currently operating in sleep mode, if a gNB broadcast such information
  • the UE obtains a configuration about when/how/where it may ask for waking up a gNB through defined specifications / a gNB’s broadcast
  • the UE performs RSRP measurement on reference signals broadcast by the gNBs and obtains Rx levels associated to the gNBs.
  • the UE looks for suitable cell to camp on or waits for a handover.
  • a gNB that is in sleep mode is depicted in Figure 1. It can be seen that the gNB-B, of which the complete area depicted with dashed line, has lost its coverage while sleeping. The gNB-B enters a sleep mode when it is not serving any traffic. For example, the gNB-B may not have any UEs in certain beams.
  • Step 100 Entering into sleep mode (by the gNB-B).
  • the gNB-B may first decide to enter a reduced capability sleep mode for a first-time duration, e.g., reducing the number beams, Multiple Input Multiple Output (MIMO) antennas, Bandwidth (BW,) sectors, panels and so on.
  • MIMO Multiple Input Multiple Output
  • BW Bandwidth
  • the gNB-B may go to a deeper sleep mode, e.g., totally turn off operation at the radio and antenna.
  • the gNB-B may still transmit SSB and System Information (SI) broadcasting signals and listen to PRACH, while in the latter case (the deeper sleep mode), the gNB-B may decide to also turn off those signals thereby going to the deep sleep mode.
  • SI System Information
  • the gNB may still transmit a minimum signaling, e.g., SSB and potentially with a higher periodicity e.g., 160ms instead of 20 ms, and further include a flag, e.g., a bit with a value of “1” as an indication that the cell is in the sleep mode.
  • the flag can be mapped to a different sleep mode of the gNB e.g., bit values: “00” to indicate deep sleep, “01” to indicate light sleep, “10” to indicate microsleep, and “11” to indicate idle mode.
  • the bits can be extended to include several definitions such as number of beams, MIMO antennas, BW, sectors, panels, and so on.
  • Step 102 Informing gNB-B’s sleep mode to gNB-A.
  • the gNB-B informs neighboring gNBs (e.g., the gNB-A) of its sleep mode and then goes to sleep.
  • the gNB-B informs other gNBs (e.g., the gNB-A in Figure 1) that the gNB-B will go to sleep mode and not transmit any SI while sleeping.
  • the gNB-B may also provide information, e.g., (a) how long it will stay in the sleep mode, (b) which frequency, (c) which beam will be muted, and (d) the reactive time (from the sleep mode to an active mode), to other gNBs. This information may be spread through a Central Unit (CU)-gNB if the gNB-B and other gNBs are affiliated to the same CU-gNB or through higher level if they are not affiliated in the same CU-gNB.
  • CU Central Unit
  • Optional step 104A Broadcasting a configuration and/or information to other entities (e.g., the UE) (by the gNB-A).
  • the gNB-A may broadcast that a neighboring gNB (e.g., the gNB- B in Figure 1) is operating in the sleep mode.
  • the gNB-A may broadcast a configuration (e.g., a RACH configuration) for waking up the neighboring gNB.
  • the broadcasted configuration may include areas of the cell the UE may reside in for being allowed to ask for a gNB wake-up.
  • the area may be defined by specific beams (e.g., wide beams defined/associated to SSBs) in which the UE is allowed/not allowed to ask for gNB wake-up.
  • the area may be defined by one or more thresholds. For example, the UE may only be allowed to ask for gNB wake-up when its measured reception (Rx) level is below a first threshold value and above a second threshold value.
  • the broadcasted information may comprise sleeping gNBs around the UE or whether the gNB-B is still sleeping.
  • a UE can be informed by the gNB-A that there is at least one gNB in sleep mode e.g., the gNB-B in Figure 1) through broadcasting the configuration and/or the information.
  • the UE can transmit a preamble to the gNB-A at one of one or more occasions determined by the configuration (e.g., the RACH configuration) of the gNB-A, or a preconfigured occasion.
  • the specific preamble can itself be either configured by the network, e.g., configured by the gNB-A in a SIB, or pre-configured as in standardization documentations.
  • the UE does not need to camp on the gNB-A but let the gNB-A wake-up the gNB-B that can provide better RSRP when active.
  • the gNB-A can wake-up all neighboring gNBs that are sleeping.
  • the gNB-A may broadcast information about all neighboring gNBs that are sleeping, for example, to the UE.
  • the gNB-A can determine a rough direction toward the sleeping gNB from the SSB, and the beam index and the gNB-A wakes up the sleeping gNB on that direction. Since a UE is only allowed to send a preamble at the RACH occasion of the gNB-A.
  • the gNB-A is expected to be able to receive a preamble from the UE (that should be in the gNB-B coverage) with a received power equal to or larger than a certain threshold value when the UE uses a certain transmit power level.
  • the threshold value may be set as a predetermined value, e.g., via standardization.
  • the threshold value may be derived from other factors, e.g., the gNB-B coverage, the expected path loss (including the carrier frequency), the location of the gNB-A, and optionally, the UE capability. If such requirements are not, or are expected to not be, fulfilled by the gNB-A, the gNB-B may need to inform its sleep mode to more than one gNBs, so that at least one gNB (other than the gNB-A) can receive the above-noted preamble from the UE with sufficient received power.
  • Step 104A is optional because the 3GPP standards may standardize the configuration and/or the information, thus the gNB-A does not need to broadcast the configuration and/or the information.
  • Step 104B The UE obtains the configuration or the information. From the UE’s perspective, in some embodiments, the UE receives the configuration from the gNB-A including information about whether there is a gNB nearby is currently operating in sleep mode, if the gNB-A broadcast such information in the configuration. In other words, the UE obtains the configuration about when/how/where the UE may ask to wake-up a sleeping gNB (e.g., the gNB- B) based on the received configuration, or alternatively, based on predetermined 3 GPP standards.
  • a sleeping gNB e.g., the gNB- B
  • Step 106 The UE transmitting a preamble (and gNB-A receiving the preamble from the UE) that triggers the gNB-A to wake-up the gNB-B.
  • the preamble is a PRACH.
  • the UE requests to wake-up surrounding gNBs via the PRACH (the preamble) when the UE cannot find any cell that fulfills cell (re)selection criteria to camp on but can still receive system information of surrounding gNBs.
  • the gNB-A receives the preamble from the UE, which may be a Wake-Up Signal (WUS) or not.
  • WUS Wake-Up Signal
  • the preamble is a WUS.
  • the UE transmits, to the gNB-A, the preamble as a signal to wake-up sleeping gNBs, such as the gNB-B.
  • the UE can send a preamble which can tolerate strong transmission attenuation (low Bit Error Rate (BER) in low Signal to Noise Ratio (SNR)).
  • BER Bit Error Rate
  • SNR Signal to Noise Ratio
  • this emergency preamble can be assigned a clean channel (time, frequency, spatial resource) to get rid of interference.
  • the preamble of a UE is not predefined for WUS.
  • the gNB-A can tell the direction and the distance of the UE based on SSB index and Timing Advance (TA) info. If the TA of the UE exceeds a predefined threshold or the signal strength of the preamble is lower than a predefined threshold, the gNB-A can determine that the preamble is a WUS.
  • TA Timing Advance
  • a UE can perform a blind request for gNB-B wake-up, which means the UE does not need to indicate the sleep mode of sleeping gNBs.
  • the UE chooses a gNB which has the highest RSRP of a reference signal as a target for sending a preamble.
  • the UE could choose any gNB randomly as a target for sending a preamble.
  • the preamble is not a WUS.
  • the UE can transmit a preamble resource (e.g., a sequence, a cyclic shift, a location on time and frequency plane) to the gNB-A at those occasions determined by the (RACH) configuration that the gNB-A transmitted to the UE in the above step.
  • a preamble resource e.g., a sequence, a cyclic shift, a location on time and frequency plane
  • the UE can still receive the signals from the gNB-A, e.g., SSB and SIBs, and thereby the UE becomes informed about the PRACH resources. Nevertheless, since the received signal does not fulfill the PLMN conditions (e.g., RSRP is lower than a specific threshold), the UE cannot join the gNB-A. Thus, the UE can transmit a specific (PRACH) preamble to inform the gNB-A that the UE can detect the gNB-A but cannot join the gNB-A.
  • PRACH specific
  • only specific UEs are configured to be allowed to ask for gNB wake-up.
  • the network may want only some UEs with reduced reception capability (e.g., RedCap devices) to ask for gNB wake-up rather than all UEs.
  • Step 108 Informing the gNB-B to wake-up (by the gNB-A).
  • the gNB-A may inform the gNB-B to wake-up. For example, the gNB-A transmits a WUS to the gNB-B.
  • Step 110 Resuming the gNB-B output power based on the WUS.
  • the gNB-B after receiving the WUS from the gNB-A, resumes its full output power.
  • the gNB-B may wake-up and level up its output power stepwise. In that case, the UE and the gNB-A may repeat the above steps until the cell (re)selection criteria are fulfilled.
  • gNB-B RRC Connected UE on a sleeping gNB
  • Figure 2 depicts a RRC connected UE entering a coverage hole caused by powering off the gNB-B.
  • the UE is going to lose connection with the gNB-A due to its mobility, but a handover would not be triggered in time because the UE cannot measure the RSRP of the gNB- B.
  • the gNB-B enters the sleep mode.
  • the gNB-B informs its sleep mode to the gNB-A.
  • Optional step 200 Measurements of RSRPs (by the UE)
  • a RRC connected UE measures the RSRP of the gNB-A and the RSRP of the gNB-B as the serving gNB-A requests. That is, the UE performs RSRP measurement on reference signals broadcast by the gNBs and obtains Rx levels associated to the gNBs. In some embodiments, the UE searches for a suitable cell to camp on or waits for a handover.
  • Optional step 202 Receiving the measurements of RSRPs (by the gNB-A)
  • the RRC Connected UE reports the measurement result (the RSRP of the gNB-A and the gNB-B) to the gNB-A.
  • Optional step 204 Requesting (by the gNB-A) the gNB-B to wake-up and transmit SI.
  • the gNB-A may request the gNB-B to wake-up to transmit SI (step 204A).
  • the gNB-B may wake-up and transmit the SI to the UE and/or the gNB-A (step 204B).
  • the UE and the gNB-A may repeat the above steps until the handover criteria are fulfilled.
  • the gNB-B may power up its output level to make sure the connection between the UE and the gNB-B.
  • the gNB-A instead of waking up the gNB-B, increases its coverage, e.g., by increasing the power, potentially in specific direction of the UE, such that the UE can join the gNB-A, and the gNB-B can remain sleeping.
  • the gNB-A may inform the gNB-B that the gNB-B does not have to leave the sleep mode, as the gNB-A can cover the UE.
  • the gNB-A can inform the gNB-B to only wake-up in a specific direction to the UE and thus, the gNB-B does not need to leave the sleep (power saving) mode all together.
  • the gNB-B can enter sleep mode, but still transmit a flagging signal expressing its presence, e.g., a bit in transmitted SSB and potentially with lower periodicity, e.g., 160ms instead of 20ms periodicity.
  • the UE can transmit a specific preamble on specific configured PRACH, e.g., a wake-up receiver configured on the gNB-B, and thereby waking up the gNB-B without the need to coordinate with the gNB-A.
  • the UE when the gNB-B is in sleep mode, the UE may be in poor coverage of the gNB-A so that the (PRACH) preamble cannot be successfully received by the gNB-A.
  • the currently sleeping gNB-B may be performing no downlink (DL) transmissions but may be monitoring for WU-PRACH transmission on predefined resources. This may be done using a main receiver or a special-purpose, reduced-power receiver.
  • the WU-PRACH resource and a WUS procedure may be defined as in one of the following ways:
  • the WU-PRACH may be a fixed NW-wide configuration that applies in areas of “no coverage,” i.e. when the UE cannot detect an SSB with signal quality above a threshold value.
  • the configuration of the WU-PRACH e.g., information about the predefined resources carrying the WU-PRACH
  • NW coverage disappears in contrast to traditional PRACH transmitted in response to detecting the SSB. This may be viewed as an emergency contact attempt in the absence of any detected NW activity.
  • the configuration of the WU-PRACH may be provided by the gNB-B while in an active (non-sleep) state. If the UE does not move and the coverage disappears, the UE may transmit a WU-PRACH towards the gNB-B using the configured resources (based on the configuration received from the gNB-B).
  • Transmission towards the gNB-B, and/or avoiding uncontrolled transmission towards the gNB-A or another NW node may be ensured, for example, by (1) establishing that the UE has not moved/rotated since the last gNB-B SSB reception, or tracking such movement with inertial sensors; transmitting PRACH in the direction consistent with the presumed gNB-B direction, (2) establishing that no SSB signals are detected, or their power is below a threshold in the transmission direction; transmitting in directions where no SSB is detected, and/or avoiding transmissions in directions where SSB are detected.
  • such PRACH transmissions directed at the gNB-B in sleep mode may apply a power ramping policy that differs from an initial access or connection requesting PRACH transmissions.
  • the power ramping may be limited in range or in the number of steps, or may be allowed up to a maximum absolute power, or disabled, to avoid creating interference towards neighboring cells.
  • the initial power may be based on a previous gNB-B power estimate (if the UE has not moved since that power estimate), or as a reference power value for cell-center or cell-edge access.
  • the WU-PRACH resource may include a time of an observation window.
  • the UE may transmit in a transmission window based on the previous time synch with the gNB-B or based on timing obtained from the gNB-A, if available. If no previous gNB-B or the current gNB-A signals have been observed, or the time elapsed is long, the UE may transmit the WU-PRACH preamble tentatively at multiple time occasions until there is a response, or up to a maximum number of attempts.
  • Figure 3 shows a flow chart summarizing the steps discussed above and illustrated in Figure 1.
  • the following steps from 100 to 110 may occur when the UE is in an idle state or an inactive state.
  • the gNB-B enters into sleep mode.
  • the gNB-B (that is in sleep mode) stays powered on for at least a certain duration based on a request received from the UE or the gNB-A.
  • step 102 the gNB-B informs its sleep mode to the gNB-A (a neighboring gNB).
  • the gNB-A broadcasts a configuration and/or information to other entities like the UE.
  • This step 104A can be optional because the 3GPP standards may standardize the configuration and/or the information, thus the gNB-A does not need to broadcast the configuration or the information.
  • the UE may obtain the configuration or the information from the gNB-A or, alternatively, by retrieving the configuration or the information (that is/are determined in accordance with relevant standards) from a storage of the UE (step 104B).
  • the configuration or information comprises information about when, how, and/or where the UE is allowed to transmit a preamble to trigger the second network node (e.g., gNB-A) to wake-up one or more neighboring network nodes that are in the sleep mode.
  • the second network node e.g., gNB-A
  • the configuration or information indicates that the UE can transmit a preamble to trigger the second network node (e.g., gNB-A) to wake-up one or more neighboring nodes that are in sleep mode when the UE is in an idle or inactive state and the UE does not find a suitable cell to camp on.
  • the second network node e.g., gNB-A
  • the configuration or information indicates that the UE can transmit a preamble to trigger the second network node (e.g., gNB-A) to wake-up one or more neighboring nodes that are in sleep mode when the UE is in a connected state and the UE loses a connection with a serving network node before a handover is triggered.
  • the second network node e.g., gNB-A
  • the configuration or information indicates that the UE can transmit a preamble to trigger the second network node (e.g., gNB-A) to wake-up one or more neighboring nodes that are in sleep mode: when the UE can receive system information from one or more surrounding network nodes and/or receive synchronization signals from one or more surrounding network nodes; and/or during a RACH occasion of the second network node (e.g., gNB-A) if the UE is in an idle or inactive state; and/or when the UE will lost its connection when the UE is in a connected state.
  • the configuration or information indicates a specific preamble resource over PRACH and a specific number of repetitions for the transmission of the preamble to trigger wake-up of one or more neighboring network nodes that are in sleep mode.
  • the configuration or information indicates the second network node (e.g., gNB-A) as a network node to which the UE is to transmit the preamble.
  • the second network node e.g., gNB-A
  • the configuration or information indicates how often the UE can transmit a preamble resource to request wake-up of a sleeping network node.
  • the configuration or information indicates one or more areas of a cell served by the second network node (e.g., gNB-A) in which the UE is allowed or not allowed to request wake-up of one or more neighboring nodes that are in sleep mode.
  • the second network node e.g., gNB-A
  • the one or more areas are defined by a specific Public Land Mobile Network, PLMN.
  • PLMN Public Land Mobile Network
  • the specific PLMN is one or more of (a) a PLMN selected by a NAS, (b) a registered PLMN on which a certain location registration outcome has occurred, and (c) a PLMN of an equivalent PLMN list.
  • the one or more areas are defined by one or more specific beams (e.g., associated to one or more specific SSBs).
  • step 106 the UE transmits a preamble, and the gNB-A receives the preamble from the UE.
  • the preamble is a PRACH.
  • the preamble may be a WUS or not.
  • the preamble when the preamble is a WUS, the preamble is a signal to wake-up the sleeping gNB-B.
  • the preamble is a simply designed preamble that tolerates strong transmission attenuation.
  • the gNB-A determines that the preamble is a WUS when the gNB- A (a) determines a direction and a distance of the UE based on SSB index and TA info and (b) determines that the TA of the UE exceeds a predefined threshold or a signal strength of the preamble is lower than a predefined threshold.
  • the gNB-A transmits a signal to wake-up the gNB-B based on the preamble received from the UE.
  • step 110 the gNB-B wakes up based on the signal received from the gNB-A and resumes output power.
  • the output power is the gNB-B’s full output power. In some embodiments, the output power is a stepwise power level less than the gNB-B’s full output power.
  • Figure 4 is a flow chart summarizing the steps discussed above and illustrated in Figure 2. The following steps from 200 to 206 may occur when the UE is RRC connected.
  • Step 200 The UE measures a RSRP of the gNB-A and a RSRP of the gNB-B.
  • Step 202 The UE reports, to the gNB-A, the results of the RSRP measurements.
  • Step 204 After receiving the results of the RSRP measurements from the UE, when the RSRP of the gNB-A falls below a certain threshold and the RSRP of the gNB-B does not fulfill the criteria of handover, the gNB-A transmits, to the gNB-B, a signal for requesting the gNB-B’s wake-up and transmitting the gNB-B’s SI to the gNB-A and/or the UE (step 204A).
  • the gNB-A requests the gNB-B a direction for the powered beam of the gNB-A.
  • the gNB-B After receiving, from the gNB-A, the signal for requesting the gNB-B’s wake-up and transmitting the gNB-B’s SI, the gNB-B wakes up and transmits its SI to the gNB and/or the UE (step 204B).
  • Step 206 The gNB-B monitors WU-PRACH on a predefined resource.
  • the step of monitoring the WU-PRACH is performed by a main receiver or a special-purpose, reduced-power receiver.
  • the WU-PRACH is a fixed network-wide configuration.
  • a configuration of the WU-PRACH is provided to the UE by the gNB-B.
  • Figure 5 shows an example of a communication system 500 in accordance with some embodiments.
  • the communication system 500 includes a telecommunication network 502 that includes an access network 504, such as a Radio Access Network (RAN), and a core network 506, which includes one or more core network nodes 508.
  • the access network 504 includes one or more access network nodes, such as network nodes 510A and 510B (one or more of which may be generally referred to as network nodes 510), or any other similar Third Generation Partnership Project (3GPP) access node or non-3GPP Access Point (AP).
  • 3GPP Third Generation Partnership Project
  • the network nodes 510 facilitate direct or indirect connection of User Equipment (UE), such as by connecting UEs 512A, 512B, 512C, and 512D (one or more of which may be generally referred to as UEs 512) to the core network 506 over one or more wireless connections.
  • UE User Equipment
  • Network nodes 510 can implement features described above with respect gNB-A or gNB- B or other network node as detailed above in Figures 1-4.
  • 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 500 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 500 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 512 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 510 and other communication devices.
  • the network nodes 510 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 512 and/or with other network nodes or equipment in the telecommunication network 502 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 502.
  • the core network 506 connects the network nodes 510 to one or more hosts, such as host 516. 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 506 includes one more core network nodes (e.g., core network node 508) 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 508.
  • 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 516 may be under the ownership or control of a service provider other than an operator or provider of the access network 504 and/or the telecommunication network 502, and may be operated by the service provider or on behalf of the service provider.
  • the host 516 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 500 of Figure 5 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system 500 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 Second, Third, Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards, or any applicable future generation standard (e.g., Sixth Generation (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, and/or any Low Power Wide Area Network (LPWAN) standards such as LoRa and Sigfox.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile
  • the telecommunication network 502 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunication network 502 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 502. For example, the telecommunication network 502 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 Internet of Things (loT) services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB enhanced Mobile Broadband
  • mMTC massive Machine Type Communication
  • LoT massive Internet of Things
  • the UEs 512 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 504 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 504.
  • a UE may be configured for operating in single- or multi-Radio Access Technology (RAT) or multi-standard mode.
  • RAT Radio Access Technology
  • a UE may operate with any one or combination of WiFi, New Radio (NR), and LTE, i.e., be configured for Multi-Radio Dual Connectivity (MR-DC), such as Evolved Universal Mobile Telecommunications Service (UMTS) Terrestrial RAN (E-UTRAN) NR - Dual Connectivity (EN-DC).
  • UMTS Evolved Universal Mobile Telecommunications Service
  • E-UTRAN Evolved Universal Mobile Telecommunications Service
  • E-UTRAN Evolved Universal Mobile Telecommunications Service
  • EN-DC Dual Connectivity
  • a hub 514 communicates with the access network 504 to facilitate indirect communication between one or more UEs (e.g., UE 512C and/or 512D) and network nodes (e.g., network node 510B).
  • the hub 514 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 514 may be a broadband router enabling access to the core network 506 for the UEs.
  • the hub 514 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 514 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 514 may be a content source. For example, for a UE that is a Virtual Reality (VR) headset, display, loudspeaker or other media delivery device, the hub 514 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 514 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 514 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 514 may have a constant/persistent or intermittent connection to the network node 510B.
  • the hub 514 may also allow for a different communication scheme and/or schedule between the hub 514 and UEs (e.g., UE 512C and/or 512D), and between the hub 514 and the core network 506.
  • the hub 514 is connected to the core network 506 and/or one or more UEs via a wired connection.
  • the hub 514 may be configured to connect to a Machine-to-Machine (M2M) service provider over the access network 504 and/or to another UE over a direct connection.
  • M2M Machine-to-Machine
  • UEs may establish a wireless connection with the network nodes 510 while still connected via the hub 514 via a wired or wireless connection.
  • the hub 514 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 510B.
  • the hub 514 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and the network node 510B, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • a UE refers to a device capable, configured, arranged, and/or operable to communicate wirelessly with network nodes and/or other UEs.
  • a UE include, but are not limited to, a smart phone, mobile phone, cell phone, Voice over Internet Protocol (VoIP) phone, wireless local loop phone, desktop computer, Personal Digital Assistant (PDA), wireless camera, 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.
  • Other examples include any UE identified by the 3 GPP, including a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • NB-IoT Narrowband Internet of Things
  • MTC Machine Type Communication
  • eMTC
  • 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), Vehi cl e-to- Vehicle (V2V), Vehicle-to-Infrastructure (V2I), or Vehicle- to-Everything (V2X).
  • D2D Device-to-Device
  • DSRC Dedicated Short-Range Communication
  • V2V Vehi cl e-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
  • the UE 600 includes processing circuitry 602 that is operatively coupled via a bus 604 to an input/output interface 606, a power source 608, memory 610, a communication interface 612, and/or any other component, or any combination thereof.
  • processing circuitry 602 that is operatively coupled via a bus 604 to an input/output interface 606, a power source 608, memory 610, a communication interface 612, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 6. 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 602 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 610.
  • the processing circuitry 602 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 602 may include multiple Central Processing Units (CPUs).
  • the input/output interface 606 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 600.
  • 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 608 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 608 may further include power circuitry for delivering power from the power source 608 itself, and/or an external power source, to the various parts of the UE 600 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging the power source 608.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 608 to make the power suitable for the respective components of the UE 600 to which power is supplied.
  • the memory 610 may be or be configured to include memory such as Random Access Memory (RAM), Read Only Memory (ROM), Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory 610 includes one or more application programs 614, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 616.
  • the memory 610 may store, for use by the UE 600, any of a variety of various operating systems or combinations of operating systems.
  • the memory 610 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 RAM (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a tamper resistant module in the form of a Universal Integrated Circuit Card (UICC) including one or more Subscriber Identity Modules (SIMs), such as a Universal SIM (USIM) and/or Internet Protocol Multimedia Services Identity Module (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 Dual In-line Memory Module
  • the UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as a ‘SIM card.’
  • the memory 610 may allow the UE 600 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 610, which may be or comprise a device-readable storage medium.
  • the processing circuitry 602 may be configured to communicate with an access network or other network using the communication interface 612.
  • the communication interface 612 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 622.
  • the communication interface 612 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 618 and/or a receiver 620 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 618 and receiver 620 may be coupled to one or more antennas (e.g., the antenna 622) and may share circuit components, software, or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 612 may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, NFC, 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 according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, Transmission Control Protocol/Internet Protocol (TCP/IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), Quick User Datagram Protocol Internet Connection (QUIC), Hypertext Transfer Protocol (HTTP), and so forth.
  • a UE may provide an output of data captured by its sensors, through its communication interface 612, or 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 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.
  • Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a television, 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 VR, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or itemtracking device, a sensor for
  • 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 3 GPP context be referred to as an MTC device.
  • the UE may implement the 3 GPP NB-IoT standard.
  • a UE may represent a vehicle, such as a car, a bus, a truck, a ship, 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. 7 shows a network node 700 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.
  • Examples of network nodes include, but are not limited to, APs (e.g., radio APs), Base Stations (BSs) (e.g., radio BSs, Node Bs, evolved Node Bs (eNBs), and NR. Node Bs (gNBs)).
  • APs e.g., radio APs
  • BSs Base Stations
  • Node Bs Node Bs
  • eNBs evolved Node Bs
  • gNBs Node Bs
  • Network node 700 can implement features described above with respect to gNB-A or gNB-B or other network node as detailed in Figures 1-4.
  • 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 BS such as centralized digital units and/or Remote Radio Units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such RRUs may or may not be integrated with an antenna as an antenna integrated radio.
  • Parts of a distributed radio BS 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 BS 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 Transmission Point
  • MSR Multi -Standard Radio
  • RNCs Radio Network Controllers
  • BSCs Base Transceiver Stations
  • MCEs Multi-Cell/Multicast Coordination Entities
  • OFM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • the network node 700 includes processing circuitry 702, memory 704, a communication interface 706, and a power source 708.
  • the network node 700 may be composed of multiple physically separate components (e.g., a Node B component and a Radio Network Controller (RNC) component, or a Base Transceiver Station (BTS) component and a Base Station Controller (BSC) component, etc.), which may each have their own respective components.
  • RNC Radio Network Controller
  • BTS Base Transceiver Station
  • BSC Base Station Controller
  • the network node 700 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate memory 704 for different RATs) and some components may be reused (e.g., an antenna 710 may be shared by different RATs).
  • the network node 700 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 700, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, Long Range Wide Area Network (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 the network node 700.
  • the processing circuitry 702 may comprise a combination of one or more of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, 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 700 components, such as the memory 704, to provide network node 700 functionality.
  • the processing circuitry 702 includes a System on a Chip (SOC). In some embodiments, the processing circuitry 702 includes one or more of Radio Frequency (RF) transceiver circuitry 712 and baseband processing circuitry 714. In some embodiments, the RF transceiver circuitry 712 and the baseband processing circuitry 714 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 the RF transceiver circuitry 712 and the baseband processing circuitry 714 may be on the same chip or set of chips, boards, or units.
  • SOC System on a Chip
  • the processing circuitry 702 includes one or more of Radio Frequency (RF) transceiver circuitry 712 and baseband processing circuitry 714.
  • RF transceiver circuitry 712 and the baseband processing circuitry 714 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 the
  • the memory 704 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, RAM, 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 702.
  • volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, RAM, 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
  • the memory 704 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 702 and utilized by the network node 700.
  • the memory 704 may be used to store any calculations made by the processing circuitry 702 and/or any data received via the communication interface 706.
  • the processing circuitry 702 and the memory 704 are integrated.
  • the communication interface 706 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 706 comprises port(s)/terminal(s) 716 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 706 also includes radio front-end circuitry 718 that may be coupled to, or in certain embodiments a part of, the antenna 710.
  • the radio front-end circuitry 718 comprises filters 720 and amplifiers 722.
  • the radio front-end circuitry 718 may be connected to the antenna 710 and the processing circuitry 702.
  • the radio front-end circuitry 718 may be configured to condition signals communicated between the antenna 710 and the processing circuitry 702.
  • the radio front-end circuitry 718 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 718 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters 720 and/or the amplifiers 722.
  • the radio signal may then be transmitted via the antenna 710.
  • the antenna 710 may collect radio signals which are then converted into digital data by the radio front-end circuitry 718.
  • the digital data may be passed to the processing circuitry 702.
  • the communication interface 706 may comprise different components and/or different combinations of components.
  • the network node 700 does not include separate radio front-end circuitry 718; instead, the processing circuitry 702 includes radio front-end circuitry and is connected to the antenna 710. Similarly, in some embodiments, all or some of the RF transceiver circuitry 712 is part of the communication interface 706. In still other embodiments, the communication interface 706 includes the one or more ports or terminals 716, the radio frontend circuitry 718, and the RF transceiver circuitry 712 as part of a radio unit (not shown), and the communication interface 706 communicates with the baseband processing circuitry 714, which is part of a digital unit (not shown).
  • the antenna 710 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 710 may be coupled to the radio front-end circuitry 718 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 710 is separate from the network node 700 and connectable to the network node 700 through an interface or port.
  • the antenna 710, the communication interface 706, and/or the processing circuitry 702 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node 700. Any information, data, and/or signals may be received from a UE, another network node, and/or any other network equipment. Similarly, the antenna 710, the communication interface 706, and/or the processing circuitry 702 may be configured to perform any transmitting operations described herein as being performed by the network node 700. Any information, data, and/or signals may be transmitted to a UE, another network node, and/or any other network equipment.
  • the power source 708 provides power to the various components of the network node 700 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 708 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 700 with power for performing the functionality described herein.
  • the network node 700 may be connectable to an external power source (e.g., the power grid or an electricity outlet) via input circuitry or an interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 708.
  • the power source 708 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 700 may include additional components beyond those shown in Figure 7 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 700 may include user interface equipment to allow input of information into the network node 700 and to allow output of information from the network node 700. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 700.
  • Figure 8 is a block diagram of a host 800, which may be an embodiment of the host 516 of Figure 5, in accordance with various aspects described herein.
  • the host 800 may be or comprise various combinations of 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 800 may provide one or more services to one or more UEs.
  • the host 800 includes processing circuitry 802 that is operatively coupled via a bus 804 to an input/output interface 806, a network interface 808, a power source 810, and memory 812.
  • processing circuitry 802 that is operatively coupled via a bus 804 to an input/output interface 806, a network interface 808, a power source 810, and memory 812.
  • 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 6 and 7, such that the descriptions thereof are generally applicable to the corresponding components of the host 800.
  • the memory 812 may include one or more computer programs including one or more host application programs 814 and data 816, which may include user data, e.g., data generated by a UE for the host 800 or data generated by the host 800 for a UE.
  • Embodiments of the host 800 may utilize only a subset or all of the components shown.
  • the host application programs 814 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), Moving Picture Experts Group (MPEG), VP9) and audio codecs (e.g., Free Lossless Audio Codec (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, and heads-up display systems).
  • VVC Versatile Video Coding
  • HEVC High Efficiency Video Coding
  • AVC Advanced Video Coding
  • MPEG Moving Picture Experts Group
  • VP9 Moving Picture Experts Group
  • audio codecs e.g., Free Lossless Audio Codec (FLAC), Advanced Audio Coding (AAC), MPEG, G.711
  • FLAC Free Lossless Audio Codec
  • AAC Advanced Audio Coding
  • the host application programs 814 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. Accordingly, the host 800 may select and/or indicate a different host for Over-The-Top (OTT) services for a UE.
  • the host application programs 814 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 (DASH or MPEG-DASH), etc.
  • FIG. 9 is a block diagram illustrating a virtualization environment 900 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 virtualization environments 900 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 902 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 900 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware 904 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 906 (also referred to as hypervisors or VM Monitors (VMMs)), provide VMs 908A and 908B (one or more of which may be generally referred to as VMs 908), and/or perform any of the functions, features, and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 906 may present a virtual operating platform that appears like networking hardware to the VMs 908.
  • the VMs 908 comprise virtual processing, virtual memory, virtual networking, or interface and virtual storage, and may be run by a corresponding virtualization layer 906. Different embodiments of the instance of a virtual appliance 902 may be implemented on one or more of the VMs 908, 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 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.
  • NFV Network Function Virtualization
  • a VM 908 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 908, and that part of the hardware 904 that executes that VM be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs 908, forms separate virtual network elements.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 908 on top of the hardware 904 and corresponds to the application 902.
  • the hardware 904 may be implemented in a standalone network node with generic or specific components.
  • the hardware 904 may implement some functions via virtualization.
  • the hardware 904 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 910, which, among others, oversees lifecycle management of the applications 902.
  • the hardware 904 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 RAN or a BS.
  • some signaling can be provided with the use of a control system 912 which may alternatively be used for communication between hardware nodes and radio units.
  • Figure 10 shows a communication diagram of a host 1002 communicating via a network node 1004 with a UE 1006 over a partially wireless connection in accordance with some embodiments.
  • Example implementations, in accordance with various embodiments, of the UE (such as the UE 512A of Figure 5 and/or the UE 600 of Figure 6), the network node (such as the network node 510A of Figure 5 and/or the network node 700 of Figure 7), and the host (such as the host 516 of Figure 5 and/or the host 800 of Figure 8) discussed in the preceding paragraphs will now be described with reference to Figure 10.
  • embodiments of the host 1002 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 1002 also includes software, which is stored in or is accessible by the host 1002 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 1006 connecting via an OTT connection 1050 extending between the UE 1006 and the host 1002.
  • a host application may provide user data which is transmitted using the OTT connection 1050.
  • the network node 1004 includes hardware enabling it to communicate with the host 1002 and the UE 1006 via a connection 1060.
  • the connection 1060 may be direct or pass through a core network (like the core network 506 of Figure 5) and/or one or more other 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 1006 includes hardware and software, which is stored in or accessible by the UE 1006 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 the UE 1006 with the support of the host 1002.
  • an executing host application may communicate with the executing client application via the OTT connection 1050 terminating at the UE 1006 and the host 1002.
  • 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 1050 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 connection 1050.
  • the OTT connection 1050 may extend via the connection 1060 between the host 1002 and the network node 1004 and via a wireless connection 1070 between the network node 1004 and the UE 1006 to provide the connection between the host 1002 and the UE 1006.
  • the connection 1060 and the wireless connection 1070, over which the OTT connection 1050 may be provided, have been drawn abstractly to illustrate the communication between the host 1002 and the UE 1006 via the network node 1004, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 1002 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 1006.
  • the user data is associated with a UE 1006 that shares data with the host 1002 without explicit human interaction.
  • the host 1002 initiates a transmission carrying the user data towards the UE 1006.
  • the host 1002 may initiate the transmission responsive to a request transmitted by the UE 1006.
  • the request may be caused by human interaction with the UE 1006 or by operation of the client application executing on the UE 1006.
  • the transmission may pass via the network node 1004 in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1012, the network node 1004 transmits to the UE 1006 the user data that was carried in the transmission that the host 1002 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1014, the UE 1006 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1006 associated with the host application executed by the host 1002.
  • the UE 1006 executes a client application which provides user data to the host 1002.
  • the user data may be provided in reaction or response to the data received from the host 1002.
  • the UE 1006 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 1006. Regardless of the specific manner in which the user data was provided, the UE 1006 initiates, in step 1018, transmission of the user data towards the host 1002 via the network node 1004.
  • the network node 1004 receives user data from the UE 1006 and initiates transmission of the received user data towards the host 1002.
  • the host 1002 receives the user data carried in the transmission initiated by the UE 1006.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 1006 using the OTT connection 1050, in which the wireless connection 1070 forms the last segment. More precisely, the teachings of these embodiments may improve data rate, latency, power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, improved content resolution, better responsiveness, extended battery lifetime.
  • factory status information may be collected and analyzed by the host 1002.
  • the host 1002 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 1002 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host 1002 may store surveillance video uploaded by a UE.
  • the host 1002 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 1002 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 1050 may be implemented in software and hardware of the host 1002 and/or the UE 1006.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1050 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or by supplying values of other physical quantities from which software may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 1050 may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not directly alter the operation of the network node 1004. 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 1002.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1050 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 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 hardwired 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.
  • any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses.
  • Each virtual apparatus may comprise a number of these functional units.
  • These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein.
  • the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according to one or more embodiments of the present disclosure.
  • Embodiment 1 A method comprising: at a first network node (e.g., gNB-B): entering (100) into sleep mode, informing (102) a second network node (e.g., gNB-A) that the first network node (e.g., gNB-B) has entered into the sleep mode; receiving (108), from the second network node (e.g., gNB-A), the signal to wake-up; and waking up (110) responsive to receiving (108) the signal to wake-up from the second network node (e.g., gNB-A).
  • a first network node e.g., gNB-B
  • entering (100) into sleep mode informing (102) a second network node (e.gNB-A) that the first network node (e.g., gNB-B) has entered into the sleep mode
  • Embodiment 2 A method comprising: at the second network node (e.g., gNB-A): receiving (102), from a first network node (e.g., gNB-B), an indication that informs the second network node (e.g., gNB-A) that the first network node (e.g., gNB-B) has entered into the sleep mode; receiving (106) a preamble from a User Equipment (UE); and transmitting (108), to the first network node (e.g., gNB-B), a signal to wake-up the first network node (e.g., gNB-B) responsive to receiving (106) the preamble from the UE.
  • UE User Equipment
  • Embodiment 3 The method of embodiment 1 or 2, further comprising, at the second network node (e.g., gNB-A), broadcasting (104A) a configuration and/or information to the UE.
  • the second network node e.g., gNB-A
  • broadcasting 104A
  • Embodiment 4 The method of embodiment 3, wherein the configuration and/or information comprises information about when, how, and/or where the UE is allowed to transmit a preamble to trigger the second network node (e.g., gNB-A) to wake-up one or more neighboring network nodes that are in the sleep mode.
  • the second network node e.g., gNB-A
  • Embodiment 5 The method of embodiment 3 or 4, wherein the configuration and/or information indicates that the UE can transmit a preamble to trigger the second network node (e.g., gNB-A) to wake-up one or more neighboring nodes that are in sleep mode when the UE is in an idle or inactive state and the UE does not find a suitable cell to camp on.
  • the second network node e.g., gNB-A
  • Embodiment 6 The method of embodiment 3 or 4, wherein the configuration and/or information indicates that the UE can transmit a preamble to trigger the second network node (e.g., gNB-A) to wake-up one or more neighboring nodes that are in sleep mode when the UE is in a connected state and the UE loses a connection with a serving network node before a handover is triggered.
  • the second network node e.g., gNB-A
  • Embodiment 7 The method of embodiment 5 or 6, wherein the configuration and/or information indicates that the UE can transmit a preamble to trigger the second network node (e.g., gNB-A) to wake-up one or more neighboring nodes that are in sleep mode: when the UE can receive system information from one or more surrounding network nodes and/or receive synchronization signals from one or more surrounding network nodes; and/or during a Random Access Channel (RACH) occasion of the second network node (e.g., gNB-A) if the UE is in an idle or inactive state; and/or when the UE will lose its connection when the UE is in a connected state.
  • the second network node e.g., gNB-A
  • RACH Random Access Channel
  • Embodiment 8 The method of any of embodiments 3 to 7, wherein the configuration and/or information indicates a specific preamble resource over Physical Random Access Channel (PRACH) and a specific number of repetitions for the transmission of the preamble to trigger wake-up of one or more neighboring network nodes that are in sleep mode.
  • PRACH Physical Random Access Channel
  • Embodiment 9 The method of embodiment 3 to 8, wherein the configuration and/or information indicates the second network node (e.g., gNB-A) as a network node to which the UE is to transmit the preamble.
  • Embodiment 10 The method of embodiment 3 to 9, wherein the configuration and/or information indicates how often the UE can transmit a preamble resource to request wake-up of a sleeping network node.
  • Embodiment 11 The method of embodiment 3 to 10, wherein the configuration and/or information indicates one or more areas of a cell served by the second network node (e.g., gNB- A) in which the UE is allowed or not allowed to request wake-up of one or more neighboring nodes that are in sleep mode.
  • the second network node e.g., gNB- A
  • Embodiment 12 The method of embodiment 11, wherein the one or more areas are defined by a specific Public Land Mobile Network (PLMN).
  • PLMN Public Land Mobile Network
  • Embodiment 13 The method of embodiment 12, wherein the specific PLMN is one or more of (a) a PLMN selected by a Non-Access Stratum, NAS, (b) a registered PLMN on which a certain location registration outcome has occurred, and (c) a PLMN of an equivalent PLMN list.
  • the specific PLMN is one or more of (a) a PLMN selected by a Non-Access Stratum, NAS, (b) a registered PLMN on which a certain location registration outcome has occurred, and (c) a PLMN of an equivalent PLMN list.
  • Embodiment 14 The method of embodiment 11, wherein the one or more areas are defined by one or more specific beams (e.g., associated to one or more specific SSBs).
  • one or more specific beams e.g., associated to one or more specific SSBs.
  • Embodiment 15 The method of any of embodiments 1 to 14, wherein the preamble is a Physical Random Access Channel.
  • Embodiment 16 The method of any of embodiments 1 to 14, wherein the preamble is a Wake-Up signal (WUS).
  • WUS Wake-Up signal
  • Embodiment 17 The method of any of embodiments 1 to 14, wherein the preamble is a simply designed preamble that tolerates strong transmission attenuation.
  • Embodiment 18 The method of any of embodiments 1 to 17, further comprising determining, by the second network node (e.g., gNB-A), that the preamble is a Wake-Up Signal, WUS, when the second network node (e.g., gNB-A) (a) determines a direction and a distance of the UE based on Synchronization Signal Block (SSB) index and timing advance (TA) info and (b) determines that the TA of the UE exceeds a predefined threshold or a signal strength of the preamble is lower than a predefined threshold.
  • SSB Synchronization Signal Block
  • TA timing advance
  • Embodiment 19 The method of any of embodiments 1 to 18, further comprising, at the first network node (e.g., gNB-B), resuming output power after waking up (100).
  • the first network node e.g., gNB-B
  • Embodiment 20 The method of embodiment 19, wherein the output power of the first network node (e.g., gNB-B) is the first network node’s full output power.
  • the first network node e.g., gNB-B
  • Embodiment 21 The method of embodiment 19, wherein the output power of the first network node (e.g., gNB-B) is a stepwise power less than the first network node’s full output power.
  • Embodiment 22 The method of any of embodiments 1 to 21, wherein the UE is idle or inactive.
  • Embodiment 23 A method comprising: at a second network node (e.g., gNB-A): receiving (202), from a User Equipment measurement results of a Reference Signal Received Power of the second network node (e.g., gNB-A) and a RSRP of a first network node (e.g., gNB- B); transmitting (204 A), to a first network node (e.g., gNB-B), a signal for requesting (a) the first network node (e.g., gNB-B)’ s wake-up and (b) transmitting the first network node (e.g., gNB- B)’s system information, SI, to the second network node (e.g., gNB-A) and/or the UE.
  • a second network node e.g., gNB-A
  • receiving (202) from a User Equipment measurement results of a Reference Signal Received Power of the second network node (e.g
  • Embodiment 24 The method of embodiment 23, further comprising: at the first network node (e.g., gNB-B): receiving (204B), from the second network node (e.g., gNB-A), a signal for wake-up and transmitting the SI to the second network node (e.g., gNB-A) and/or the UE.
  • the first network node e.g., gNB-B
  • receiving (204B) from the second network node (e.g., gNB-A)
  • a signal for wake-up and transmitting the SI to the second network node (e.g., gNB-A) and/or the UE.
  • Embodiment 25 The method of embodiment 24, wherein transmitting (204), from the second network node (e.g., gNB-A) to the first network node (e.g., gNB-B), the signal comprises transmitting (204), from the second network node (e.g., gNB-A) to the first network node (e.g., gNB-B), the signal when the RSRP of the second network node (e.g., gNB-A) falls below a certain threshold and the RSRP of the first network node (e.g., gNB-B) does not fulfill the criteria of handover.
  • transmitting (204), from the second network node (e.g., gNB-A) to the first network node (e.g., gNB-B) comprises transmitting (204), from the second network node (e.g., gNB-A) to the first network node (e.g., gNB-B), the signal when the RSRP of the
  • Embodiment 26 The method of embodiment 23 to 25, further comprising requesting, by the second network node (e.g., gNB-A), the first network node (e.g., gNB-B) to which direction of the first network node (e.g., gNB-B)’s powered on beam is directed.
  • the second network node e.g., gNB-A
  • the first network node e.g., gNB-B
  • direction of the first network node e.g., gNB-B
  • Embodiment 27 The method of any of embodiments 22 to 26, further comprising monitoring (206), by the gNB-B, a Wake-Up signal of Physical Random Access Channel (WU- PRACH) on a predefined resource.
  • WU- PRACH Physical Random Access Channel
  • Embodiment 28 The method of embodiment 27, wherein the WU-PRACH is a fixed network-wide configuration.
  • Embodiment 29 The method of embodiment 28, further comprising transmitting a configuration of the WU-PRACH from the gNB-B to the UE.
  • Embodiment 30 The method of any of embodiments 23 to 29, wherein the UE is Radio Resource Control, RRC, connected.
  • RRC Radio Resource Control
  • Embodiment 31 A method performed by a User Equipment, UE, comprising: obtaining (104B) configuration and/or information that indicates when, how, and/or on where the UE is allowed to request wake-up of one or more first network nodes (e.g., gNB-B) that are in a sleep state; and transmitting (106), to a second network node (e.g., gNB-A), a preamble to request wake-up the one or more first network nodes (e.g., gNB-B) that are in sleep state.
  • obtaining (104B) configuration and/or information comprises retrieving configuration and/or information from the UE’s storage wherein the configuration and/or the information is/are pre-defined in accordance with a standard.
  • Embodiment 33 The method of embodiment 31, obtaining (104B) configuration and/or information comprises receiving configuration and/or information from the second network node (e.g., gNB-A).
  • the second network node e.g., gNB-A
  • Embodiment 34 A first network node (e.g., gNB-B) adapted to: enter (100) into sleep mode; inform (102) a second network node (e.g., gNB-A) that the first network node (e.g., gNB- B) has entered into the sleep mode; receive (108), from the second network node (e.g., gNB-A), the signal to wake-up; and wake-up (110) responsive to receiving (108) the signal to wake-up from the second network node (e.g., gNB-A).
  • a second network node e.g., gNB-A
  • Embodiment 35 The first network node (e.g., gNB-B) of embodiment 34 wherein the first network node (e.g., gNB-B) is further adapted to perform the method of any of embodiments 3 to 22.
  • the first network node e.g., gNB-B
  • Embodiment 36 A first network node (e.g., gNB-B) comprising processing circuitry configured to cause the first network node (e.g., gNB-B) to: enter (100) into sleep mode; inform (102) a second network node (e.g., gNB-A) that the first network node has entered into the sleep mode; receive (108), from the second network node (e.g., gNB-A), the signal to wake-up; and wake-up (110) responsive to receiving (108) the signal to wake-up from the second network node (e.g., gNB-A).
  • a first network node e.g., gNB-B
  • processing circuitry configured to cause the first network node (e.g., gNB-B) to: enter (100) into sleep mode; inform (102) a second network node (e.g., gNB-A) that the first network node has entered into the sleep mode; receive (108), from the second network node (
  • Embodiment 37 The first network node (e.g., gNB-B) of embodiment 36 wherein the processing circuitry is further configured to cause the first network node (e.g., gNB-B) to perform the method of any of embodiments 3 to 22.
  • the processing circuitry is further configured to cause the first network node (e.g., gNB-B) to perform the method of any of embodiments 3 to 22.
  • Embodiment 38 A second network node (e.g., gNB-A) adapted to: receive (102), from a first network node (e.g., gNB-B), an indication that informs the second network node (e.g., gNB-A).
  • a first network node e.g., gNB-B
  • an indication that informs the second network node e.g., gNB-
  • the first network node e.g., gNB-B
  • a signal to wake-up the first network node e.g., gNB-B
  • the first network node e.g., gNB-B
  • Embodiment 39 The second network node (e.g., gNB-A) of embodiment 38 wherein the second network node (e.g., gNB-A) is further adapted to perform the method of any of embodiments 3 to 22.
  • Embodiment 40 A second network node (e.g., gNB-A) comprising processing circuitry configured to cause the second network node (e.g., gNB-A) to: receive (102), from a first network node (e.g., gNB-B), an indication that informs the second network node (e.g., gNB-A) that the first network node (e.g., gNB-B) has entered into the sleep mode; receive (106) a preamble from a User Equipment (UE); and transmit (108), to the first network node (e.g., gNB- B), a signal to wake-up the first network node (e.g., gNB-B) responsive to receiving (106) the preamble
  • Embodiment 41 The second network node (e.g., gNB-A) of embodiment 40 wherein the processing circuitry is further configured to cause the second network node (e.g., gNB-A) to perform the method of any of embodiments 3 to 22.
  • the processing circuitry is further configured to cause the second network node (e.g., gNB-A) to perform the method of any of embodiments 3 to 22.
  • Embodiment 42 A second network node (e.g., gNB-A) adapted to: receive (202), from a User Equipment, measurement results of a Reference Signal Received Power of the second network node (e.g., gNB-A) and a RSRP of a first network node (e.g., gNB-B); and transmit (204A), to a first network node (e.g., gNB-B), a signal for requesting (a) the first network node (e.g., gNB-B)’ s wake-up and (b) transmitting the first network node (e.g., gNB-B)’ s system information, SI, to the second network node (e.g., gNB-A) and/or the UE.
  • a first network node e.g., gNB-B
  • SI system information
  • Embodiment 43 The second network node (e.g., gNB-A) of embodiment 42 wherein the second network node (e.g., gNB-A) is further adapted to perform the method of any of embodiments 24 to 30.
  • the second network node e.g., gNB-A
  • Embodiment 44 A second network node (e.g., gNB-A) comprising processing circuitry configured to cause the second network node (e.g., gNB-A) to: receive (202), from a User Equipment, UE, measurement results of a Reference Signal Received Power, RSRP, of the second network node (e.g., gNB-A) and a RSRP of a first network node (e.g., gNB-B); and transmit (204 A), to a first network node (e.g., gNB-B), a signal for requesting (a) the first network node (e.g., gNB-B)’ s wake-up and (b) transmitting the first network node's (e.g., gNB- B) system information, SI, to the second network node (e.g., gNB-A) and/or the UE.
  • a first network node e.g., gNB-B
  • Embodiment 45 The second network node (e.g., gNB-A) of embodiment 44 wherein the processing circuitry is further configured to cause the second network node (e.g., gNB-A) to perform the method of any of embodiments 24 to 30.
  • the processing circuitry is further configured to cause the second network node (e.g., gNB-A) to perform the method of any of embodiments 24 to 30.

Landscapes

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

Abstract

Sont divulgués ici des procédés, des appareils et des supports lisibles par ordinateur pour améliorer l'efficacité énergétique de réseaux cellulaires. Dans un aspect, un procédé mis en œuvre par un premier nœud de réseau est divulgué. Le procédé consiste à entrer en mode veille et à informer un second noeud de réseau que le premier noeud de réseau est entré en mode veille ; à recevoir, en provenance du second noeud de réseau, un signal de réveil et à se réveiller en réponse à la réception du signal de réveil provenant du second noeud de réseau.
PCT/SE2023/050412 2022-04-28 2023-04-28 Signal de réveil pour stations de base utilisant un canal d'accès aléatoire Ceased WO2023211359A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263336010P 2022-04-28 2022-04-28
US63/336,010 2022-06-07

Publications (1)

Publication Number Publication Date
WO2023211359A1 true WO2023211359A1 (fr) 2023-11-02

Family

ID=88519439

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2023/050412 Ceased WO2023211359A1 (fr) 2022-04-28 2023-04-28 Signal de réveil pour stations de base utilisant un canal d'accès aléatoire

Country Status (1)

Country Link
WO (1) WO2023211359A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4404638A1 (fr) * 2023-01-18 2024-07-24 DELTA DORE RADEMACHER GmbH Procédé de fonctionnement d'une première unité d'une installation domotique
WO2025199296A1 (fr) * 2024-03-22 2025-09-25 Ofinno, Llc Notification entre points d'accès
US12457552B2 (en) 2023-12-04 2025-10-28 Nokia Solutions And Networks Oy Network energy saving

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012042375A2 (fr) * 2010-09-28 2012-04-05 Alcatel Lucent Station de base, équipement utilisateur et procédé permettant de réduire la consommation énergétique dans une station de base
WO2014056174A1 (fr) * 2012-10-11 2014-04-17 Broadcom Corporation Économie d'énergie au sein de réseaux cellulaires
EP2941063A1 (fr) * 2014-04-29 2015-11-04 NTT Docomo, Inc. Découverte et activation de petites cellules assistées de macrocellules
EP2982189A2 (fr) * 2013-04-03 2016-02-10 Google Technology Holdings LLC Procédés et dispositifs de recherche de cellule
EP2993945A1 (fr) * 2014-09-04 2016-03-09 Alcatel Lucent Émetteur-récepteur, noeud de réseau, procédé et programme informatique
US9775121B1 (en) * 2017-01-19 2017-09-26 Sprint Spectrum L.P. Dynamic control of reference-signal transmission power based on reference signal coverage quality at or near half-way point between base stations
WO2023274371A1 (fr) * 2021-07-01 2023-01-05 华为技术有限公司 Procédé d'accès à une cellule, appareil de communication et support d'enregistrement informatique
WO2023066915A1 (fr) * 2021-10-19 2023-04-27 Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V. Récepteur ou signal de réveil de cellule

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012042375A2 (fr) * 2010-09-28 2012-04-05 Alcatel Lucent Station de base, équipement utilisateur et procédé permettant de réduire la consommation énergétique dans une station de base
WO2014056174A1 (fr) * 2012-10-11 2014-04-17 Broadcom Corporation Économie d'énergie au sein de réseaux cellulaires
EP2982189A2 (fr) * 2013-04-03 2016-02-10 Google Technology Holdings LLC Procédés et dispositifs de recherche de cellule
EP2941063A1 (fr) * 2014-04-29 2015-11-04 NTT Docomo, Inc. Découverte et activation de petites cellules assistées de macrocellules
EP2993945A1 (fr) * 2014-09-04 2016-03-09 Alcatel Lucent Émetteur-récepteur, noeud de réseau, procédé et programme informatique
US9775121B1 (en) * 2017-01-19 2017-09-26 Sprint Spectrum L.P. Dynamic control of reference-signal transmission power based on reference signal coverage quality at or near half-way point between base stations
WO2023274371A1 (fr) * 2021-07-01 2023-01-05 华为技术有限公司 Procédé d'accès à une cellule, appareil de communication et support d'enregistrement informatique
WO2023066915A1 (fr) * 2021-10-19 2023-04-27 Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V. Récepteur ou signal de réveil de cellule

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Management and orchestration; Energy efficiency of 5G (Release 17)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 28.310, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V17.3.0, 23 December 2021 (2021-12-23), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 34, XP052083272 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4404638A1 (fr) * 2023-01-18 2024-07-24 DELTA DORE RADEMACHER GmbH Procédé de fonctionnement d'une première unité d'une installation domotique
US12457552B2 (en) 2023-12-04 2025-10-28 Nokia Solutions And Networks Oy Network energy saving
WO2025199296A1 (fr) * 2024-03-22 2025-09-25 Ofinno, Llc Notification entre points d'accès

Similar Documents

Publication Publication Date Title
JP7696053B2 (ja) ランダムアクセスパーティショニングおよびランダムアクセスレポート
US20240214849A1 (en) Relaxed Measurement Mode of Operation when UE Performs High-Priority Actions
WO2023211359A1 (fr) Signal de réveil pour stations de base utilisant un canal d'accès aléatoire
US20250142470A1 (en) Efficient Usage of Receivers for Paging-Early-Indication Reception
WO2023113674A1 (fr) Fonctionnement d'équipement utilisateur (ue) avec configuration d'économie d'énergie de station de base
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
US20250119777A1 (en) Reduction of unnecessary radio measurement relaxation reports
WO2024093617A1 (fr) Sélection de cellule pour un accès au réseau dans un scénario de délégation de cellule
WO2024150178A1 (fr) Procédé et appareil de fonctionnement de répéteur lorsque le réseau est dans un état d'économie d'énergie
CN118140531A (zh) 用于nb-iot中的rrc重建的主动测量过程
WO2023095037A1 (fr) Rapport mdt journalisé faisant intervenir une mobilité inter-rat
WO2025113008A1 (fr) Dispositif terminal, nœud de réseau et procédés de resélection de cellule
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
US20240334226A1 (en) Early radio measurement relaxation reporting
WO2024162884A1 (fr) Procédés de fonctionnement de wur sans veille
EP4595584A1 (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
WO2025178542A1 (fr) Surveillance de liaison radio à l'aide d'un récepteur de réveil
WO2025127991A1 (fr) Équipement utilisateur, nœud de réseau radio et procédés associés pour procédures de mesure dépendant de l'énergie
WO2025005864A1 (fr) Dtx/drx de réseau par rapport à un ue dans un état non connecté
WO2023163630A1 (fr) Adaptation de puissance de transmission de réseau économe en énergie
EP4612989A1 (fr) Transmission et réception discontinues de cellule
WO2024102048A1 (fr) Adressage d'ue avec des codes wus
WO2025226192A1 (fr) Amélioration de sdt dans une cellule utilisant nes
WO2024231414A1 (fr) Gestion de réseau de dispositifs d'économie d'énergie
WO2025178543A1 (fr) Adaptation de liaison de signal de réveil

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: 23796931

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 23796931

Country of ref document: EP

Kind code of ref document: A1