[go: up one dir, main page]

WO2025095839A1 - Procédés, appareil et supports lisibles par ordinateur associés à un rapport d'état dans des réseaux sans fil - Google Patents

Procédés, appareil et supports lisibles par ordinateur associés à un rapport d'état dans des réseaux sans fil Download PDF

Info

Publication number
WO2025095839A1
WO2025095839A1 PCT/SE2024/050924 SE2024050924W WO2025095839A1 WO 2025095839 A1 WO2025095839 A1 WO 2025095839A1 SE 2024050924 W SE2024050924 W SE 2024050924W WO 2025095839 A1 WO2025095839 A1 WO 2025095839A1
Authority
WO
WIPO (PCT)
Prior art keywords
user equipment
network node
network
report
conditions
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.)
Pending
Application number
PCT/SE2024/050924
Other languages
English (en)
Inventor
Ali Nader
Martin Van Der Zee
Tuomas TIRRONEN
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 WO2025095839A1 publication Critical patent/WO2025095839A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

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/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower
    • H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower using a pre-established activity schedule, e.g. traffic indication frame
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]

Definitions

  • the disclosure relates to methods for status reporting in wireless networks, and nodes configured to operate in accordance with those methods.
  • UE User Equipment
  • the UE is only allowed to relax when the “low mobility” and “not-at-cell- edge” criterion are met (see 3GPP 38.331, V17.6.0), i.e. when the UE is stationary and in good coverage.
  • FIG. 1 is a schematic diagram illustrating DRX concepts.
  • DRX in connected mode allows a UE to sleep (during sleeping time 102) when there is no traffic transmitted/received for some time, i.e. drx-InactivityTimer 104 expires (e.g., following a period of data activity 105) (see 3GPP 38.321, vl7.6.0).
  • drx-InactivityTimer 104 expires (e.g., following a period of data activity 105) (see 3GPP 38.321, vl7.6.0).
  • the UE has to be awake and monitor the Physical Downlink Control Channel (PDCCH) to be able to receive Downlink (DL) data from the gNB.
  • PDCH Physical Downlink Control Channel
  • RAN4 defined a DRX state referred to as “no DRX is used” which is identical to the RAN2 Active Time, except it excludes the drx-OnDurationTimer 108.
  • the UE performs RLM/BFD measurements based on periodic Synchronization Signal Block (SSB) or Channel State Information Reference Signal (CSLRS) transmissions from the gNB.
  • the UE is required to measure/ evaluate when these RLM/BFD measurements drop below a threshold Qout, based on a number of Layer 1 (LI) measurement samples using Layer 3 (L3) filtering/averaging (e.g. 10) during an evaluation period (Tevaluate); see 3GPP 38.133, V18.3.0.
  • LI Layer 1
  • L3 filtering/averaging e.g. 10
  • the evaluation period (Tevaluate) is longer when the UE is allowed to perform “relaxed” RLM/BFD measurements, i.e. when stationary and in good coverage. This allows the UE to skip RLM/BFD measurements during some SSB/CSLRS occasions and save power.
  • the RLM/BFD measurements requirements are defined in terms of SSB/CSLRS periodicity and DRX cycle length, to ensure that the UE does not need to wake-up from DRX (deep/light sleep) just to do the RLM/BFD measurements, i.e. the UE can perform the measurements during Active Time.
  • UE assistance information is defined in terms of SSB/CSLRS periodicity and DRX cycle length, to ensure that the UE does not need to wake-up from DRX (deep/light sleep) just to do the RLM/BFD measurements, i.e. the UE can perform the measurements during Active Time.
  • the UE assistance information is a general framework, which allows the UE to send assistance information to the gNB (when configured), that can assist the gNB with respect to configuration and diagnostics.
  • RLM/BFD relaxation state reporting, i.e. the UE can report its relaxation state (relaxed, not relaxed) to the gNB.
  • the UE is only allowed to relax when the conditions described above are met. It is up to the UE implementation to relax when it is allowed.
  • the UE generates a relaxation state report, when the UE is configured to do so, and when the relaxation state changes.
  • RAN4 specified that the UE is not allowed to relax when “no DRX is used”, i.e. when the UE is in Active Time (excluding drx- OnDurationTimef).
  • Active Time excluding drx- OnDurationTimef.
  • the UE would trigger a “relaxed” report.
  • this Uplink (UL) transmission triggers the UE to start the drx-InactivityTimer and enter Active Time.
  • the UE is not allowed to relax during Active Time. This leads to a problem that, when the UE reports “relaxed”, the UE’s relaxation state is actually “not relaxed”.
  • RAN2 agreed a solution to reduce the negative impact described above by changing the report trigger to exclude relaxation state changes caused by DRX state changes. However, this still causes incorrect reporting and reduced power saving.
  • Embodiments of the disclosure may be divided into two categories which solve the problems discussed above:
  • one aspect of the disclosure provides a method performed by a user equipment for status reporting.
  • the method comprises: responsive to one or more first conditions being met, entering a relaxed state for performing measurements on reference signals transmitted by one or more network nodes; and, responsive to one or more second conditions being met, refraining from immediately transmitting, to a first network node, a report comprising an indication that the user equipment has entered the relaxed state.
  • a second aspect provides a method performed by a user equipment for status reporting.
  • the method comprises: responsive to one or more first conditions being met, entering a relaxed state for performing measurements on reference signals transmitted by one or more network nodes; transmitting, to a first network node, a report comprising an indication that the user equipment has entered the relaxed state; and, responsive to one or more second conditions being met, refraining from entering an active time of a DRX cycle upon transmitting the report.
  • a third aspect provides a method performed by a network node for configuring status reporting by a user equipment.
  • the method comprises: transmitting to the user equipment, a configuration message comprising an instruction or permission for the user equipment to refrain from immediately transmitting a report comprising an indication that the user equipment has entered a relaxed state responsive to one or more second conditions being met.
  • a fourth aspect provides a method performed by a network node for handling status reporting by a user equipment.
  • the method comprises: receiving, from the user equipment, a report comprising an indication that the user equipment has entered a relaxed state for performing measurements on reference signals transmitted by one or more network nodes; and, responsive to one or more second conditions being met, performing one of: immediately instructing the user equipment to enter a sleep state of a DRX cycle; and considering the user equipment to be in the sleep state of the DRX cycle.
  • Certain embodiments may provide one or more of the following technical advantage(s).
  • the UE power saving gain is not reduced due to relaxation state reporting (e.g., the power saving achieved by moving to the relaxed state for measurements is not offset by transmitting a report indicating that the UE has moved to the relaxed state).
  • the second category of solution benefits from the same advantage.
  • the UE reports its “relaxed” status such a report is accurate (e.g., the report is transmitted and accurately describes the UE’s status as “relaxed”).
  • Fig. l is a schematic diagram illustrating DRX concepts
  • FIGS. 2 to 5 are flow charts illustrating methods in accordance with some embodiments
  • FIG. 6 shows an example of a communication system in accordance with some embodiments
  • FIG. 7 shows a UE in accordance with some embodiments
  • FIG. 8 shows a network node in accordance with some embodiments
  • FIG. 9 is a block diagram of a host
  • FIG. 10 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.
  • FIG. 11 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 UE does not initiate a transmission immediately if said transmission is only related to the relaxation state reporting. Rather the relaxation state reporting is postponed and may be “piggy-backed” together with other transmissions. In other words, the UE does not enter the Connected Mode/State DRX (C-DRX) Active Time, i.e., the drx-InactivityTimer is not started when the trigger condition to send the report is met, but the report is sent when the UE is in Active Time due to other UL/DL traffic.
  • C-DRX Connected Mode/State DRX
  • the first alternative can be implemented by specifying it explicitly in a specification implemented by the UE, that the UE will not initiate a transmission to send the relaxation report; that is, the UE will not trigger the transmission of UEAssistancelnformation Radio Resource Control (RRC) message including bfd-MeasRelaxatioState or rlm- MeasRelaxationState fields if there is no other UL information or UL traffic to be sent at the moment.
  • RRC Radio Resource Control
  • it may be specified in detail when and how the UE does send the relaxation status information once the UE is back in Active Time again.
  • the UEAssistancelnformation may be built by the UE beforehand (e.g., before Active Time), but sent to the UE uplink buffer (to trigger uplink transmission) when other uplink user plane or signaling (control plane) data arrives at the UE.
  • the first alternative can also be implemented by introducing an indication in the system information or UE-specific RRC configuration to indicate that the UE may delay sending the relaxation status information to the gNB/network in the case where there is no other uplink traffic to be sent.
  • the actual implementation on the UE side on how to do this may be left up to UE implementation (e.g., not specified in a specification).
  • a further way to implement the first alternative is to not have any specification impact, i.e. no indication to the UE and nothing is captured in the procedural text of the specification about delaying the report, but the UE delays in a UE-implementation specific way. In this case the delaying is uncontrolled from the network perspective, but the UE may be able to save power.
  • Figure 2 depicts a method in accordance with particular embodiments. The method of Figure 2 may be performed by a UE or wireless device (e.g. the UE 612 or UE 700 as described later with reference to Figures 6 and 7 respectively).
  • a UE or wireless device e.g. the UE 612 or UE 700 as described later with reference to Figures 6 and 7 respectively.
  • the method begins at step 202 in which, optionally, the UE receives a configuration message from a first network node (e.g., a serving base station or gNB) comprising an instruction or permission for the UE to refrain from immediately transmitting the report responsive to one or more second conditions being met.
  • the configuration message may comprise a UE-specific message (e.g., a RRC configuration message) or a broadcast message (e.g., system information, SSB, etc).
  • the configuration message comprises an instruction
  • the UE is expected to comply and refrain from so transmitting the report.
  • the configuration message comprises permission
  • the UE may refrain from so transmitting the report; whether the UE actually refrains from transmitting the report is left to the UE implementation.
  • the configuration message may comprise an indication of the one or more second conditions; alternatively, the condition(s) may be pre-programmed in the UE and/or set out in one or more technical specifications implemented by the UE.
  • the UE enters a relaxed state for performing measurements on reference signals transmitted by one or more network nodes (e.g., measurements for BFD and/or RLM).
  • the one or more first conditions may comprise one or more of the user equipment has low mobility; the user equipment is not operating at or near a cell edge; and the user equipment is experiencing good radio coverage.
  • the term “relaxed state” may be understood by comparison to the normal mode of operation of the UE.
  • the UE may be further operable in a normal state for performing measurements on reference signals transmitted by one or more network nodes.
  • the relaxed state may then comprise one or more of the UE performing measurements less frequently than in the normal state; the UE averaging measured values over a longer time period than in the normal state; and the UE evaluating measured values over a longer time period than in the normal state.
  • the UE may be in a connected state, such as RRC CONNECTED. Additionally or alternatively, the UE may be configured with DRX, which is known as C-DRX when in the connected state.
  • step 206 responsive to one or more second conditions being met, the UE refrains from immediately transmitting, to the first network node, a report comprising an indication that the user equipment has entered the relaxed state. For example, the UE may refrain from transmitting (i.e. not transmit) the report until one or more third conditions have been met; see step 208 discussed below. Additionally or alternatively, the UE may refrain from initiating a DRX inactivity timer (e.g., drx-InactivityTimef) responsive to the one or more second conditions being met.
  • a DRX inactivity timer e.g., drx-InactivityTimef
  • the one or more second conditions may comprise one or more of the user equipment has no data to transmit to the network other than the report; the user equipment has no control signalling to transmit to the network other than the report; the user equipment entering the relaxed state is the only trigger for a transmission to the network. Additionally or alternatively, the one or more second conditions may comprise: the user equipment is configured with a DRX cycle; and the entrance of the user equipment to the relaxed state occurs while the user equipment is not in an active time of the DRX cycle. That is, the UE may be configured with a DRX cycle (such as connected state DRX, C-DRX), and enter the relaxed state for measurements while not in an active time of that DRX cycle.
  • a DRX cycle such as connected state DRX, C-DRX
  • active time may correspond to one or more of a time window in which any of an on-duration timer (e.g., drx-OnDurationTimer) and an inactivity timer (e.g., drx-InactivityTimef) are running, e.g., RAN2 Active Time; and a time window in which an inactivity timer is running, e.g., RAN4 no DRX is used (corresponding to RAN2 ActiveTime but excluding the on-duration timer.
  • an on-duration timer e.g., drx-OnDurationTimer
  • an inactivity timer e.g., drx-InactivityTimef
  • the UE transmits the report to the first network node.
  • the one or more third conditions may comprise one or more of: the user equipment entering an active time of a DRX cycle.
  • the report may comprise or be contained within a UE assistance information message.
  • Step 208 may comprise the UE preparing the report prior to the one or more third conditions being met, and then transmitting the report to the first network node once the one or more third conditions have been met.
  • the prepared report may be forwarded to an uplink buffer for transmission to the first network node.
  • Figure 3 depicts a method in accordance with particular embodiments.
  • the method of Figure 3 may be performed by a network node (e.g. the network node 610 or network node 800 as described later with reference to Figures 6 and 8 respectively).
  • the method of Figure 3 may correspond to the method of Figure 2, but from the perspective of the network instead of the user equipment. The methods of Figures 2 and 3 may therefore be read in conjunction.
  • the method begins at step 302, in which the network node transmits a configuration message to a UE (e.g., a served UE) comprising an instruction or permission for the UE to refrain from immediately transmitting, responsive to one or more second conditions being met, a report to the network node indicating that the UE has entered a relaxed state for performing measurements.
  • the configuration message may comprise a UE-specific message (e.g., a RRC configuration message) or a broadcast message (e.g., system information, SSB, etc).
  • the configuration message comprises an instruction
  • the UE is expected to comply and refrain from so transmitting the report.
  • the configuration message comprises permission
  • the UE may refrain from so transmitting the report; whether the UE actually refrains from transmitting the report is left to the UE implementation.
  • the term “relaxed state” may be understood by comparison to the normal mode of operation of the UE.
  • the UE may be further operable in a normal state for performing measurements on reference signals transmitted by one or more network nodes.
  • the relaxed state may then comprise one or more of the UE performing measurements less frequently than in the normal state; the UE averaging measured values over a longer time period than in the normal state; and the UE evaluating measured values over a longer time period than in the normal state.
  • the UE may be in a connected state, such as RRC CONNECTED. Additionally or alternatively, the UE may be configured with DRX, which is known as C-DRX when in the connected state.
  • the configuration message may comprise an indication of the one or more second conditions.
  • the second condition(s) themselves may be preprogrammed in the UE and/or specified in a technical specification implemented by the UE.
  • the one or more second conditions may comprise one or more of the user equipment has no data to transmit to the network other than the report; the user equipment has no control signalling to transmit to the network other than the report; the user equipment entering the relaxed state is the only trigger for a transmission to the network.
  • the one or more second conditions may comprise: the user equipment is configured with a DRX cycle; and the entrance of the user equipment to the relaxed state occurs while the user equipment is not in an active time of the DRX cycle.
  • the UE may be configured with a DRX cycle (such as connected state DRX, C-DRX), and enter the relaxed state for measurements while not in an active time of that DRX cycle.
  • active time may correspond to one or more of a time window in which any of an on-duration timer (e.g., drx-OnDurationTimer) and an inactivity timer (e.g., drx-InactivityTimer) are running, e.g., RAN2 Active Time; and a time window in which an inactivity timer is running, e.g., RAN4 no DRX is used (corresponding to RAN2 ActiveTime but excluding the on-duration timer.
  • an on-duration timer e.g., drx-OnDurationTimer
  • an inactivity timer e.g., drx-InactivityTimer
  • the coupling of relaxation state reporting and the C-DRX state is removed.
  • the UE does initiate a transmission in order to report the relaxation state even if the transmission is related only to the relaxation state reporting.
  • the UE does not start drx-InactivityTimer when it sends the relaxation report without other UL traffic, i.e. the UE does not enter C-DRX Active Time when it sends only the report.
  • the gNB receives a relaxation report then the gNB also does not enter Active Time, if it was outside Active Time.
  • a timer with a shorter length may be started in conjunction with the transmission instead of the full-length drx-InactivityTimer for example, drx- InactivityTimer may be set to 0 length.
  • the network may send e.g. DRX Command MAC CE to the UE immediately after it has received the relaxation state report to command the UE to go back to DRX from active time.
  • This alternative may also be implemented by explicitly specifying (e.g., in a technical specification implemented by the UE and the network node) for example the used drx- InactivityTimer length in the case where the UE is (only) sending the relaxation report. Or, alternatively, nothing may be captured in the technical specifications and it is left to UE implementation.
  • the gNB might think that the UE is in Active Time after it has received the relaxation report, and think that the UE is reachable, when the UE is not reachable.
  • Figure 4 depicts a method in accordance with particular embodiments. The method of Figure 4 may be performed by a UE or wireless device (e.g. the UE 612 or UE 700 as described later with reference to Figures 6 and 7 respectively).
  • a UE or wireless device e.g. the UE 612 or UE 700 as described later with reference to Figures 6 and 7 respectively.
  • the method begins at step 402, in which, optionally, the UE receives a configuration message from a first network node (e.g., a serving base station or gNB) comprising an instruction or permission for the user equipment, upon one or more second conditions being met, to refrain from entering an active time of a DRX cycle upon transmitting the report indicating that the UE has entered a relaxed state for performing measurements.
  • the configuration message may comprise a UE-specific message (e.g., a RRC configuration message) or a broadcast message (e.g., system information, SSB, etc). Where the configuration message comprises an instruction, the UE is expected to comply and refrain from so entering active time.
  • the UE may refrain from so entering the active time; whether the UE actually refrains from entering the active time is left to the UE implementation.
  • the configuration message may comprise an indication of the one or more second conditions; alternatively, the condition(s) may be pre-programmed in the UE and/or set out in one or more technical specifications implemented by the UE.
  • step 404 responsive to one or more first conditions being met, the UE enters a relaxed state for performing measurements on reference signals transmitted by one or more network nodes (e.g., measurements for BFD and/or RLM).
  • the one or more first conditions may comprise one or more of: the user equipment has low mobility; the user equipment is not operating at or near a cell edge; and the user equipment is experiencing good radio coverage.
  • the term “relaxed state” may be understood by comparison to the normal mode of operation of the UE.
  • the UE may be further operable in a normal state for performing measurements on reference signals transmitted by one or more network nodes.
  • the relaxed state may then comprise one or more of: the UE performing measurements less frequently than in the normal state; the UE averaging measured values over a longer time period than in the normal state; and the UE evaluating measured values over a longer time period than in the normal state.
  • the UE may be in a connected state, such as RRC CONNECTED. Additionally or alternatively, the UE may be configured with DRX, which is known as C-DRX when in the connected state.
  • step 406 the UE transmits, to the first network node, a report comprising an indication that the user equipment has entered the relaxed state.
  • the report may comprise or be contained within a UE assistance information message.
  • step 408 responsive to one or more second conditions being met, the UE refrains from entering an active time of a DRX cycle upon transmitting the report.
  • the one or more second conditions may comprise one or more of: the UE transmits the report without one or more of: user data; additional control signalling. That is, where the report is transmitted in step 406 without additional content, such as user data or further control signalling, the UE may refrain from entering active time of the DRX cycle.
  • the UE may be configured with the DRX cycle, and the entrance of the user equipment to the relaxed state may occur while the UE is not in the active time of the DRX cycle.
  • active time may correspond to one or more of: a time window in which any of an on-duration timer (e.g., drx-OnDurationTimer) and an inactivity timer (e.g., drx- InactivityTimer) are running, e.g., RAN2 Active Time; and a time window in which an inactivity timer is running, e.g., RAN4 no DRX is used (corresponding to RAN2 ActiveTime but excluding the on-duration timer.
  • an on-duration timer e.g., drx-OnDurationTimer
  • an inactivity timer e.g., drx- InactivityTimer
  • Step 408 may comprise the UE refraining from initiating a DRX inactivity timer, such as drx-InactivityTimer .
  • step 408 may comprise the UE initiating a DRX inactivity timer (such as drx-InactivityTimer) which is set to zero duration.
  • Figure 5 depicts a method in accordance with particular embodiments.
  • the method of Figure 5 may be performed by a network node (e.g. the network node 610 or network node 800 as described later with reference to Figures 6 and 8 respectively).
  • the method of Figure 5 may correspond to the method of Figure 4, but from the perspective of the network instead of the user equipment.
  • the methods of Figures 4 and 5 may therefore be read in conjunction with each other.
  • the method begins at step 502, in which the network node receives, from a UE (e.g., a served UE), a report comprising an indication that the user equipment has entered a relaxed state for performing measurements on reference signals transmitted by one or more network nodes.
  • the report may comprise or be contained within a UE assistance information message.
  • the UE may enter a relaxed state for performing measurements on reference signals transmitted by one or more network nodes (e.g., measurements for BFD and/or RLM). Entrance to the relaxed state may be based on one or more first conditions being met, such as one or more of: the user equipment has low mobility; the user equipment is not operating at or near a cell edge; and the user equipment is experiencing good radio coverage.
  • one or more network nodes e.g., measurements for BFD and/or RLM.
  • the term “relaxed state” may be understood by comparison to the normal mode of operation of the UE.
  • the UE may be further operable in a normal state for performing measurements on reference signals transmitted by one or more network nodes.
  • the relaxed state may then comprise one or more of: the UE performing measurements less frequently than in the normal state; the UE averaging measured values over a longer time period than in the normal state; and the UE evaluating measured values over a longer time period than in the normal state.
  • the UE may be in a connected state, such as RRC CONNECTED. Additionally or alternatively, the UE may be configured with DRX, which is known as C-DRX when in the connected state.
  • step 504 responsive to one or more second conditions being met, the network node immediately instructs the UE to enter a sleep state of a DRX cycle (e.g., not Active Time).
  • a sleep state of a DRX cycle e.g., not Active Time
  • step 506 the network node considers the UE to be in the sleep state (e.g., not Active Time) of the DRX cycle. That is, the network node assumes the UE is in the sleep state without having to instruct the UE to enter the sleep state.
  • Step 506 may complement the method of Figure 4, in which the UE refrains from entering Active Time upon transmitting a report indicating that it has entered the relaxed state, responsive to the one or more second conditions being met.
  • the one or more second conditions may comprise one or more of: the UE transmits the report without one or more of: user data; additional control signalling. That is, where the report is received in step 502 without additional content, such as user data or further control signalling, the network node may immediately (e.g., upon receiving the report) instruct the UE to enter the sleep state as in step 504, or consider the UE to be in the sleep state as in step 506.
  • the one or more second conditions may additionally or alternatively comprise one or more of: the user equipment is configured with the DRX cycle, and the entrance of the user equipment to the relaxed state occurs while the user equipment is not in an active time of the DRX cycle.
  • active time may correspond to one or more of: a time window in which any of an on-duration timer (e.g., drx-OnDurationTimer) and an inactivity timer (e.g., drx-InactivityTimef) are running, e.g., RAN2 Active Time; and a time window in which an inactivity timer is running, e.g., RAN4 no DRX is used (corresponding to RAN2 ActiveTime but excluding the on-duration timer).
  • an on-duration timer e.g., drx-OnDurationTimer
  • an inactivity timer e.g., drx-InactivityTimef
  • Figure 6 shows an example of a communication system 600 in accordance with some embodiments.
  • the communication system 600 includes a telecommunication network 602 that includes an access network 604, such as a radio access network (RAN), and a core network 606, which includes one or more core network nodes 608.
  • the access network 604 includes one or more access network nodes, such as network nodes 610a and 610b (one or more of which may be generally referred to as network nodes 610), or any other similar 3 rd Generation Partnership Project (3 GPP) access nodes or non-3GPP access points.
  • a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor.
  • the telecommunication network 602 includes one or more Open-RAN (ORAN) network nodes.
  • ORAN Open-RAN
  • An ORAN network node is a node in the telecommunication network 602 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 602, including one or more network nodes 610 and/or core network nodes 608.
  • ORAN Open-RAN
  • Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O- CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification).
  • a near-real time control application e.g., xApp
  • rApp non-real time control application
  • the network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface.
  • an ORAN access node may be a logical node in a physical node.
  • an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized.
  • the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the 0-RAN Alliance or comparable technologies.
  • the network nodes 610 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 612a, 612b, 612c, and 612d (one or more of which may be generally referred to as UEs 612) to the core network 606 over one or more wireless connections.
  • UE user equipment
  • Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors.
  • the communication system 600 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 600 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 612 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 610 and other communication devices.
  • the network nodes 610 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 612 and/or with other network nodes or equipment in the telecommunication network 602 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 602.
  • the core network 606 connects the network nodes 610 to one or more hosts, such as host 616. 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 606 includes one more core network nodes (e.g., core network node 608) 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 608.
  • 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 616 may be under the ownership or control of a service provider other than an operator or provider of the access network 604 and/or the telecommunication network 602, and may be operated by the service provider or on behalf of the service provider.
  • the host 616 may host a variety of applications to provide one or more services. Examples of such applications include the provision of live and/or pre-recorded audio/video content, data collection services, for example, 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 600 of Figure 6 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • the telecommunication network 602 is a cellular network that implements 3 GPP standardized features. Accordingly, the telecommunications network 602 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 602. For example, the telecommunications network 602 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive loT services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • the hub 614 communicates with the access network 604 to facilitate indirect communication between one or more UEs (e.g., UE 612c and/or 612d) and network nodes (e.g., network node 610b).
  • the hub 614 may be a controller, router, a content source and analytics node, or any of the other communication devices described herein regarding UEs.
  • the hub 614 may be a broadband router enabling access to the core network 606 for the UEs.
  • the hub 614 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 614 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 610b.
  • the hub 614 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 610b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • FIG. 7 shows a UE 700 in accordance with some embodiments.
  • a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs.
  • Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless 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, vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • VoIP voice over IP
  • PDA personal digital assistant
  • LME laptop-embedded equipment
  • LME laptop-mounted equipment
  • CPE wireless customer-premise equipment
  • UEs identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • 3GPP 3rd Generation Partnership Project
  • NB-IoT narrow band internet of things
  • MTC machine type communication
  • eMTC enhanced MTC
  • a UE may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), orvehicle- to-everything (V2X).
  • a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • the UE 700 includes processing circuitry 702 that is operatively coupled via a bus 704 to an input/output interface 706, a power source 708, a memory 710, a communication interface 712, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 7. 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 702 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 710.
  • the processing circuitry 702 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 702 may include multiple central processing units (CPUs).
  • the processing circuitry 702 may be operable to provide, either alone or in conjunction with other UE 700 components, such as the memory 710, UE 700 functionality.
  • the processing circuitry 702 may be configured to cause the UE 702 to perform the methods as described with reference to one or more of Figures 2 and 4.
  • the input/output interface 706 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 700.
  • 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.
  • the power source 708 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 708 may further include power circuitry for delivering power from the power source 708 itself, and/or an external power source, to the various parts of the UE 700 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 708.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 708 to make the power suitable for the respective components of the UE 700 to which power is supplied.
  • the memory 710 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory 710 includes one or more application programs 714, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 716.
  • the memory 710 may store, for use by the UE 700, any of a variety of various operating systems or combinations of operating systems.
  • the memory 710 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM external mini-dual in-line memory module
  • SDRAM synchronous dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • the UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘ SIM card.’
  • the memory 710 may allow the UE 700 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 710, which may be or comprise a device-readable storage medium.
  • the processing circuitry 702 may be configured to communicate with an access network or other network using the communication interface 712.
  • the communication interface 712 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 722.
  • the communication interface 712 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 718 and/or a receiver 720 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 718 and receiver 720 may be coupled to one or more antennas (e.g., antenna 722) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 712 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof.
  • GPS global positioning system
  • Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/intemet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
  • CDMA Code Division Multiplexing Access
  • WCDMA Wideband Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GSM Global System for Mobile communications
  • LTE Long Term Evolution
  • NR New Radio
  • UMTS Worldwide Interoperability for Microwave Access
  • WiMax Ethernet
  • TCP/IP transmission control protocol/intemet protocol
  • SONET synchronous optical networking
  • ATM Asynchronous Transfer Mode
  • QUIC Hypertext Transfer Protocol
  • HTTP Hypertext Transfer Protocol
  • a UE may provide an output of data captured by its sensors, through its communication interface 712, 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 controls a robotic arm performing a medical procedure according to the received input.
  • a UE when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare.
  • loT device are devices which are or which are embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-
  • AR Augmented Reality
  • a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node.
  • the UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device.
  • the UE may implement the 3 GPP NB-IoT standard.
  • a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • 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. 8 shows a network node 800 in accordance with some embodiments.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), 0-RAN nodes or components of an 0-RAN node (e.g, O-RU, O-DU, O-CU).
  • APs access points
  • BSs base stations
  • eNBs evolved Node Bs
  • gNBs NR NodeBs
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g, in an 0-RAN access node) and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
  • DAS distributed antenna system
  • network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g. Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • OFDM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • positioning nodes e.g. Evolved Serving Mobile Location Centers (E-SMLCs)
  • the network node 800 includes processing circuitry 802, a memory 804, a communication interface 806, and a power source 808, and/or any other component, or any combination thereof.
  • the network node 800 may be composed of multiple physically separate components (e.g, a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • the network node 800 comprises multiple separate components (e.g, BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeBs.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • the network node 800 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 804 for different RATs) and some components may be reused (e.g., a same antenna 810 may be shared by different RATs).
  • the network node 800 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 800, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z- wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 800.
  • RFID Radio Frequency Identification
  • the processing circuitry 802 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 800 components, such as the memory 804, network node 800 functionality.
  • the processing circuitry 802 may be configured to cause the network node to perform the methods as described with reference to one or more of Figures 3 and 5.
  • the processing circuitry 802 includes a system on a chip (SOC). In some embodiments, the processing circuitry 802 includes one or more of radio frequency (RF) transceiver circuitry 812 and baseband processing circuitry 814. In some embodiments, the radio frequency (RF) transceiver circuitry 812 and the baseband processing circuitry 814 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 812 and baseband processing circuitry 814 may be on the same chip or set of chips, boards, or units.
  • SOC system on a chip
  • the processing circuitry 802 includes one or more of radio frequency (RF) transceiver circuitry 812 and baseband processing circuitry 814.
  • the radio frequency (RF) transceiver circuitry 812 and the baseband processing circuitry 814 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 memory 804 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 802.
  • volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-
  • the memory 804 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 802 and utilized by the network node 800.
  • the memory 804 may be used to store any calculations made by the processing circuitry 802 and/or any data received via the communication interface 806.
  • the processing circuitry 802 and memory 804 is integrated.
  • the communication interface 806 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 806 comprises port(s)/terminal(s) 816 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 806 also includes radio front-end circuitry 818 that may be coupled to, or in certain embodiments a part of, the antenna 810. Radio front-end circuitry 818 comprises filters 820 and amplifiers 822.
  • the radio front-end circuitry 818 may be connected to an antenna 810 and processing circuitry 802.
  • the radio front-end circuitry may be configured to condition signals communicated between antenna 810 and processing circuitry 802.
  • the radio front-end circuitry 818 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 818 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 820 and/or amplifiers 822.
  • the radio signal may then be transmitted via the antenna 810.
  • the antenna 810 may collect radio signals which are then converted into digital data by the radio front-end circuitry 818.
  • the digital data may be passed to the processing circuitry 802.
  • the communication interface may comprise different components and/or different combinations of components.
  • the network node 800 does not include separate radio front-end circuitry 818, instead, the processing circuitry 802 includes radio front-end circuitry and is connected to the antenna 810. Similarly, in some embodiments, all or some of the RF transceiver circuitry 812 is part of the communication interface 806. In still other embodiments, the communication interface 806 includes one or more ports or terminals 816, the radio frontend circuitry 818, and the RF transceiver circuitry 812, as part of a radio unit (not shown), and the communication interface 806 communicates with the baseband processing circuitry 814, which is part of a digital unit (not shown).
  • the antenna 810 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 810 may be coupled to the radio front-end circuitry 818 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 810 is separate from the network node 800 and connectable to the network node 800 through an interface or port.
  • the antenna 810, communication interface 806, and/or the processing circuitry 802 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 810, the communication interface 806, and/or the processing circuitry 802 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.
  • the power source 808 provides power to the various components of network node 800 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 808 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 800 with power for performing the functionality described herein.
  • the network node 800 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 808.
  • the power source 808 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 800 may include additional components beyond those shown in Figure 8 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 800 may include user interface equipment to allow input of information into the network node 800 and to allow output of information from the network node 800. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 800.
  • FIG. 9 is a block diagram of a host 900, which may be an embodiment of the host 616 of Figure 6, in accordance with various aspects described herein.
  • the host 900 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm.
  • the host 900 may provide one or more services to one or more UEs.
  • the host 900 includes processing circuitry 902 that is operatively coupled via a bus 904 to an input/output interface 906, a network interface 908, a power source 910, and a memory 912.
  • processing circuitry 902 that is operatively coupled via a bus 904 to an input/output interface 906, a network interface 908, a power source 910, and a memory 912.
  • 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 7 and 8, such that the descriptions thereof are generally applicable to the corresponding components of host 900.
  • the memory 912 may include one or more computer programs including one or more host application programs 914 and data 916, which may include user data, e.g., data generated by a UE for the host 900 or data generated by the host 900 for a UE.
  • Embodiments of the host 900 may utilize only a subset or all of the components shown.
  • the host application programs 914 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems).
  • the host application programs 914 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network.
  • the host 900 may select and/or indicate a different host for over-the-top services for a UE.
  • the host application programs 914 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.
  • HLS HTTP Live Streaming
  • RTMP Real-Time Messaging Protocol
  • RTSP Real-Time Streaming Protocol
  • MPEG-DASH Dynamic Adaptive Streaming over HTTP
  • FIG. 10 is a block diagram illustrating a virtualization environment 1000 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components.
  • Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1000 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 virtualization environment 1000 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.
  • Applications 1002 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware 1004 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 1006 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1008a and 1008b (one or more of which may be generally referred to as VMs 1008), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 1006 may present a virtual operating platform that appears like networking hardware to the VMs 1008.
  • the VMs 1008 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1006. Different embodiments of the instance of a virtual appliance 1002 may be implemented on one or more of VMs 1008, 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 1008 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 1008, and that part of hardware 1004 that executes that VM be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 1008 on top of the hardware 1004 and corresponds to the application 1002.
  • Hardware 1004 may be implemented in a standalone network node with generic or specific components. Hardware 1004 may implement some functions via virtualization. Alternatively, hardware 1004 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 1010, which, among others, oversees lifecycle management of applications 1002.
  • hardware 1004 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • some signaling can be provided with the use of a control system 1012 which may alternatively be used for communication between hardware nodes and radio units.
  • FIG 11 shows a communication diagram of a host 1102 communicating via a network node 1104 with a UE 1106 over a partially wireless connection in accordance with some embodiments.
  • host 1102 Like host 900, embodiments of host 1102 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 1102 also includes software, which is stored in or accessible by the host 1102 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 1106 connecting via an over-the-top (OTT) connection 1150 extending between the UE 1106 and host 1102.
  • OTT over-the-top
  • a host application may provide user data which is transmitted using the OTT connection 1150.
  • the network node 1104 includes hardware enabling it to communicate with the host 1102 and UE 1106.
  • the connection 1160 may be direct or pass through a core network (like core network 606 of Figure 6) 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 1106 includes hardware and software, which is stored in or accessible by UE 1106 and executable by the UE’s processing circuitry.
  • the software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1106 with the support of the host 1102.
  • a client application such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1106 with the support of the host 1102.
  • an executing host application may communicate with the executing client application via the OTT connection 1150 terminating at the UE 1106 and host 1102.
  • 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 1150 may transfer both the request data and the user data.
  • the UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT
  • the OTT connection 1150 may extend via a connection 1160 between the host 1102 and the network node 1104 and via a wireless connection 1170 between the network node 1104 and the UE 1106 to provide the connection between the host 1102 and the UE 1106.
  • the connection 1160 and wireless connection 1170, over which the OTT connection 1150 may be provided, have been drawn abstractly to illustrate the communication between the host 1102 and the UE 1106 via the network node 1104, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 1102 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 1106.
  • the user data is associated with a UE 1106 that shares data with the host 1102 without explicit human interaction.
  • the host 1102 initiates a transmission carrying the user data towards the UE 1106.
  • the host 1102 may initiate the transmission responsive to a request transmitted by the UE 1106.
  • the request may be caused by human interaction with the UE 1106 or by operation of the client application executing on the UE 1106.
  • the transmission may pass via the network node 1104, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1112, the network node 1104 transmits to the UE 1106 the user data that was carried in the transmission that the host 1102 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1114, the UE 1106 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1106 associated with the host application executed by the host 1102.
  • the UE 1106 executes a client application which provides user data to the host 1102.
  • the user data may be provided in reaction or response to the data received from the host 1102.
  • the UE 1106 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 1106. Regardless of the specific manner in which the user data was provided, the UE 1106 initiates, in step 1118, transmission of the user data towards the host 1102 via the network node 1104.
  • the network node 1104 receives user data from the UE 1106 and initiates transmission of the received user data towards the host 1102.
  • the host 1102 receives the user data carried in the transmission initiated by the UE 1106.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 1106 using the OTT connection 1150, in which the wireless connection 1170 forms the last segment. More precisely, the teachings of these embodiments may improve the power consumption and thereby provide benefits such as extended battery lifetime.
  • factory status information may be collected and analyzed by the host 1102.
  • the host 1102 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 1102 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host 1102 may store surveillance video uploaded by a UE.
  • the host 1102 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 1102 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 1102 and/or UE 1106.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1150 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 1150 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1104. 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 1102.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1150 while monitoring propagation times, errors, etc.
  • computing devices described herein may include the illustrated combination of hardware components
  • 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.
  • a method performed by a user equipment for status reporting comprising: responsive to one or more first conditions being met, entering a relaxed state for performing measurements on reference signals transmitted by one or more network nodes; and responsive to one or more second conditions being met, refraining from immediately transmitting, to a first network node, a report comprising an indication that the user equipment has entered the relaxed state.
  • the one or more second conditions comprise one or more of: the user equipment has no data to transmit to the network other than the report; the user equipment has no control signalling to transmit to the network other than the report; the user equipment entering the relaxed state is the only trigger for a transmission to the network.
  • the one or more second conditions comprise: the user equipment is configured with a discontinuous reception, DRX, cycle; and the entrance of the user equipment to the relaxed state occurs while the user equipment is not in an active time of the DRX cycle.
  • the active time of the DRX cycle corresponds to one or more of: a time window in which any of an on-duration timer and an inactivity timer are running, e.g., RAN2 Active Time; and a time window in which an inactivity timer is running, e.g., RAN4 no DRX is used.
  • the method of any one of the preceding embodiments further comprising, responsive to the one or more second conditions being met, refraining from initiating a DRX inactivity timer.
  • the method of any one of the preceding embodiments further comprising receiving a configuration message from the first network node comprising an instruction or permission for the user equipment to refrain from immediately transmitting the report responsive to the one or more second conditions being met.
  • the method of any one of the preceding embodiments further comprising transmitting the report to the first network node responsive to one or more third conditions being met.
  • the method of embodiment 7, wherein the one or more third conditions comprise one or more of: the user equipment entering an active time of a DRX cycle.
  • a method performed by a user equipment for status reporting comprising: responsive to one or more first conditions being met, entering a relaxed state for performing measurements on reference signals transmitted by one or more network nodes; transmitting, to a first network node, a report comprising an indication that the user equipment has entered the relaxed state; and responsive to one or more second conditions being met, refraining from entering an active time of a DRX cycle upon transmitting the report.
  • the one or more second conditions comprise one or more of: the user equipment transmits the report without one or more of: user data; additional control signalling.
  • refraining from entering the active time comprises refraining from initiating a DRX inactivity timer.
  • refraining from entering the active time comprises initiating a DRX inactivity timer which is set to zero duration.
  • the report is contained within a UE assistance information message.
  • the user equipment is further operable in a normal state for performing measurements on reference signals transmitted by one or more network nodes, and wherein the relaxed state comprises one or more of: the user equipment performing measurements less frequently than in the normal state; the user equipment averaging measured values over a longer time period than in the normal state; the user equipment evaluating measured values over a longer time period than in the normal state.
  • the configuration message comprises one of: a radio resource control, RRC, message; and system information.
  • the one or more second conditions comprise one or more of: the user equipment has no data to transmit to the network other than the report; the user equipment has no control signalling to transmit to the network other than the report; the user equipment entering the relaxed state is the only trigger for a transmission to the network.
  • the one or more second conditions comprise: the user equipment is configured with a discontinuous reception, DRX, cycle; and the entrance of the user equipment to the relaxed state occurs while the user equipment is not in an active time of the DRX cycle.
  • the active time of the DRX cycle corresponds to one or more of: a time window in which any of an on-duration timer and an inactivity timer are running, e.g., RAN2 Active Time; and a time window in which an inactivity timer is running, e.g., RAN4 no DRX is used.
  • a method performed by a network node for handling status reporting by a user equipment comprising: receiving, from the user equipment, a report comprising an indication that the user equipment has entered a relaxed state for performing measurements on reference signals transmitted by one or more network nodes; and responsive to one or more second conditions being met, performing one of: immediately instructing the user equipment to enter a sleep state of a DRX cycle; and considering the user equipment to be in the sleep state of the DRX cycle.
  • the one or more second conditions comprise one or more of: the user equipment transmits the report without one or more of: user data; additional control signalling.
  • the one or more second conditions comprise one or more of: the user equipment is configured with the DRX cycle, and the entrance of the user equipment to the relaxed state occurs while the user equipment is not in an active time of the DRX cycle.
  • the active time of the DRX cycle corresponds to one or more of: a time window in which any of an on-duration timer and an inactivity timer are running, e.g., RAN2 Active Time; and a time window in which an inactivity timer is running, e.g., RAN4 no DRX is used.
  • the user equipment is further operable in a normal state for performing measurements on reference signals transmitted by one or more network nodes, and wherein the relaxed state comprises one or more of: the user equipment performing measurements less frequently than in the normal state; the user equipment averaging measured values over a longer time period than in the normal state; the user equipment evaluating measured values over a longer time period than in the normal state.
  • a user equipment comprising: processing circuitry configured to cause the user equipment to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry.
  • a network node comprising: processing circuitry configured to cause the network node to perform any of the steps of any of the Group B embodiments; power supply circuitry configured to supply power to the processing circuitry.
  • a user equipment comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.
  • UE user equipment
  • a host configured to operate in a communication system to provide an over-the-top (OTT) service, the host: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.
  • OTT over-the-top
  • the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.
  • UE user equipment
  • a communication system configured to provide an over-the-top (OTT) service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.
  • OTT over-the-top

Landscapes

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

Abstract

Un procédé mis en oeuvre par un équipement utilisateur (700), le procédé consistant à, en réponse à la satisfaction d'une ou de plusieurs premières conditions, entrer (204) un état assoupli pour effectuer des mesures sur des signaux de référence transmis par un ou plusieurs noeuds de réseau (800) ; le procédé consiste en outre à, en réponse à la satisfaction d'une ou de plusieurs deuxièmes conditions, s'abstenir (206) de transmettre immédiatement, à un premier noeud de réseau, un rapport comprenant une indication selon laquelle l'équipement utilisateur a entré l'état assoupli.
PCT/SE2024/050924 2023-11-03 2024-10-30 Procédés, appareil et supports lisibles par ordinateur associés à un rapport d'état dans des réseaux sans fil Pending WO2025095839A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202363595929P 2023-11-03 2023-11-03
US63/595,929 2023-11-03

Publications (1)

Publication Number Publication Date
WO2025095839A1 true WO2025095839A1 (fr) 2025-05-08

Family

ID=93460866

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2024/050924 Pending WO2025095839A1 (fr) 2023-11-03 2024-10-30 Procédés, appareil et supports lisibles par ordinateur associés à un rapport d'état dans des réseaux sans fil

Country Status (1)

Country Link
WO (1) WO2025095839A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023014264A1 (fr) * 2021-08-04 2023-02-09 Telefonaktiebolaget Lm Ericsson (Publ) Réduction de rapports de relaxation de mesure radio inutile
WO2023122670A1 (fr) * 2021-12-21 2023-06-29 Interdigital Patent Holdings, Inc. Relaxation de mesure pour surveillance de liaison radio et rapport de l'état de relaxation de mesure dans des systèmes sans fil
US20230308924A1 (en) * 2021-02-07 2023-09-28 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Measurement method, terminal device, and network device

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230308924A1 (en) * 2021-02-07 2023-09-28 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Measurement method, terminal device, and network device
WO2023014264A1 (fr) * 2021-08-04 2023-02-09 Telefonaktiebolaget Lm Ericsson (Publ) Réduction de rapports de relaxation de mesure radio inutile
WO2023122670A1 (fr) * 2021-12-21 2023-06-29 Interdigital Patent Holdings, Inc. Relaxation de mesure pour surveillance de liaison radio et rapport de l'état de relaxation de mesure dans des systèmes sans fil

Similar Documents

Publication Publication Date Title
KR20240090510A (ko) 트래픽 흐름 정보를 갖는 다수의 drx 구성들
WO2023022642A1 (fr) Signalisation de surchauffe prédite d'ue
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
US20240407042A1 (en) Systems and methods for connected mode discontinuous reception using short cycles
US20250280423A1 (en) Methods in determining the application delay for search-space set group-switching
WO2024150178A1 (fr) Procédé et appareil de fonctionnement de répéteur lorsque le réseau est dans un état d'économie d'énergie
US20240357704A1 (en) Methods for supporting multiple discontinuous reception (drx) configurations
WO2024028838A1 (fr) Économie d'énergie de réseau dans un ng-ran scindé
EP4437753A1 (fr) Rapport mdt journalisé faisant intervenir une mobilité inter-rat
WO2023059238A1 (fr) Calcul d'état de mobilité de dispositif de communication à l'aide d'une fréquence de référence
WO2025095839A1 (fr) Procédés, appareil et supports lisibles par ordinateur associés à un rapport d'état dans des réseaux sans fil
US20240413869A1 (en) Temporary reference signal-based secondary cell activation via radio resource control
US20250150220A1 (en) Discontinuous reception timer handling with semi-persistent scheduling hybrid automatic repeat request feedback
US20250048416A1 (en) Methods and apparatuses for rlm for inter-cell mtrp operation
US20250267562A1 (en) Communication device assistance for network configuration optimization
US20240334226A1 (en) Early radio measurement relaxation reporting
WO2024028814A1 (fr) Informations d'assistance en provenance de l'ue sur la manière dont la qoe est affectée par le schéma de sommeil d'un réseau
WO2024072281A1 (fr) Procédés pour la fabrication d'un équipement utilisateur conscient d'une transmission ou d'une réception discontinue par un réseau
WO2024023347A1 (fr) Correction du nombre de trames pour réception discontinue
WO2024231414A1 (fr) Gestion de réseau de dispositifs d'économie d'énergie
EP4595263A1 (fr) Surveillance de détection de défaillance de faisceau
WO2025172756A1 (fr) Configuration et rapport améliorés de mesures de mode de veille/inactif
WO2025034155A1 (fr) Sélection de cellule lors d'une reprise sur défaillance rapide pour un ue configuré avec une mobilité déclenchée par l1/l2
EP4612989A1 (fr) Transmission et réception discontinues de cellule
WO2024035306A1 (fr) Stockage de configuration de transfert conditionnel

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

Country of ref document: EP

Kind code of ref document: A1