WO2025097900A1

WO2025097900A1 - Management of access

Info

Publication number: WO2025097900A1
Application number: PCT/CN2024/111073
Authority: WO
Inventors: Ran YUE; Yuantao Zhang; Hongmei Liu; Min Xu
Original assignee: Lenovo Beijing Ltd
Current assignee: Lenovo Beijing Ltd
Priority date: 2024-08-09
Filing date: 2024-08-09
Publication date: 2025-05-15
Anticipated expiration: 2027-02-09

Abstract

Various aspects of the present disclosure relate to management of access. In one aspect, a UE obtains, in an RRC_IDLE state or RRC_INACTIVE state, information related to NES. In turn, the UE determines, based on the information, behaviour of the UE related to access to a cell of a base station

Description

MANAGEMENT OF ACCESS

TECHNICAL FIELD

The present disclosure relates to wireless communications, and more specifically to user equipment (UE) and method for supporting management of access.

BACKGROUND

A wireless communications system may include one or multiple network communication devices, such as base stations, which may be otherwise known as an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology. Each network communication devices, such as a base station may support wireless communications for one or multiple user communication devices, which may be otherwise known as UE, or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) . Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G) ) .

In legacy, information related to access to a cell is always transmitted, and a UE can use the acquired information to perform access attempt.

Referring to the progress of on-demand synchronization signal block (SSB) , at least one on-demand SSB burst is periodically transmitted within a period or from a time instance.

Referring to the discussion in the Third Generation Partnership Project (3GPP) , the UE can access the cell at least when on-demand SSB is transmitting. However, it is not clear whether the UE can access the cell after the on-demand SSB transmission is stopped.

SUMMARY

The present disclosure relates to UE and method that support management of access. With the present disclosure, the UE can determine whether the UE can access a cell during or after no always-on SSB transmission.

Some implementations of a UE described herein may include a processor and a transceiver coupled to the processor, wherein the processor is configured to: obtain, in a radio resource control (RRC) _IDLE state or RRC_INACTIVE state, information related to network energy saving (NES) ; and determine, based on the information, behaviour of the UE related to access to a cell of a base station.

In some implementations, the information related to NES comprises a first indication indicating that the UE can camp on the cell but cannot perform at least one of the following: access to the cell, initiating access to the cell, initiating a random access to the cell, monitoring paging occasions associated with the cell, monitoring a paging channel associated with the cell, or monitoring a short message from the cell. In such implementations, the processor is configured to determine the behaviour of the UE based on the first indication.

In some implementations, the processor is configured to determine the behaviour of the UE based on the first indication by: determining to trigger or perform cell selection or cell reselection based on the first indication.

In some implementations, the information related to NES comprises a second indication indicating that the UE can camp on the cell but cannot perform at least one of the following when or after a no always-on synchronization signal block (SSB) transmission from the cell is stopped: access to the cell, initiating access to the cell, initiating a random access to the cell, monitoring paging occasions associated with the cell, monitoring a paging channel associated with the cell, or monitoring a short message from the cell. In such implementations, the processor is configured to determine the behaviour of the UE based on the second indication.

In some implementations, the processor is configured to determine the behaviour of the UE based on the second indication by: determining to trigger or perform cell selection or cell reselection based on the second indication.

In some implementations, the processor is further configured to: receive, via the transceiver from the base station, information related to access to the cell during a no always-on synchronization signal block (SSB) transmission from the cell. In such implementations, the information related to NES comprises a third indication indicating whether the UE is allowed to use the information related to access to the cell when or after the no always-on SSB transmission is stopped. In such implementations, the processor is configured to determine the behaviour of the UE based on the third indication.

In some implementations, the information related to NES comprises a fourth indication indicating whether the UE can perform at least one of the following: access attempt to the cell, initiating access to the cell, initiating a random access to the cell, monitoring paging occasions associated with the cell, monitoring a paging channel associated with the cell, or monitoring a short message from the cell. In such implementations, the processor is configured to determine the behaviour of the UE based on the fourth indication.

In some implementations, the information related to NES comprises a fifth indication indicating whether the UE can perform at least one of the following when or after a no always-on SSB transmission from the cell is stopped: access attempt to the cell, initiating access to the cell, initiating a random access to the cell, monitoring paging occasions associated with the cell, monitoring a paging channel associated with the cell, or monitoring a short message from the cell. In such implementations, the processor is configured to determine the behaviour of the UE based on the fifth indication.

In some implementations, the processor is configured to obtain the information related to NES by monitoring at least one of the following: paging occasions associated with the cell, a paging channel associated with the cell, or a short message from the cell.

In some implementations, the processor is configured to determine the behaviour of the UE by: based on determining that a paging message for the UE is received on the paging occasions or the paging channel or determining that the short message is received, reselecting a further cell or initiating access to the further cell.

In some implementations, the information related to NES comprises a length of a timer. In such implementations, the processor is further configured to: start the timer upon receiving the length of the timer, via the transceiver from the base station or when a no always-on SSB transmission from the cell is stopped. In such implementations, the processor is configured to determine the behaviour of the UE by determining at least one of the following is not allowed when the timer expires: access to the cell, initiating access to the cell, initiating a random access to the cell, monitoring paging occasions associated with the cell, monitoring a paging channel associated with the cell, or monitoring a short message from the cell.

In some implementations, the information related to NES comprises a time instance. In such implementations, the processor is configured to determine the behaviour of the UE by determining at least one of the following is allowed before the time instance: access to the cell, initiating access to the cell, initiating a random access to the cell, monitoring paging occasions associated with the cell, monitoring a paging channel associated with the cell, or monitoring a short message from the cell.

In some implementations, the processor is configured to obtain the information related to NES by: receiving, via the transceiver from the cell, system information or a paging message or a short message or an RRC message which comprises the information related to NES.

In some implementations, the information related to NES is predefined.

In some implementations, the processor is configured to obtain the information related to NES by: receiving, via the transceiver from the cell, a no always-on SSB transmission. In such implementations, the processor is configured to determine the behaviour of the UE based on a status of the no always-on SSB transmission and predefinition.

In some implementations, the processor is configured to determine the behaviour of the UE by: determining the behaviour of the UE when or after the no always-on SSB transmission is stopped is the same as second behaviour of the UE during the no always-on SSB transmission.

In some implementations, the processor is configured to determine the behaviour of the UE by: determining at least one of the following is allowed or not allowed when or after the no always-on SSB transmission is stopped: access to the cell, initiating access to the cell, initiating a random access to the cell, monitoring paging occasions associated with the cell, monitoring a paging channel associated with the cell, or monitoring a short message from the cell.

In some implementations, the processor is configured to obtain the information related to NES by: receiving, via the transceiver from the cell, system information during a no always-on SSB transmission from the cell. In such implementations, the processor is configured to determine the behaviour of the UE based on validity of the system information.

In some implementations, the processor is configured to determine the behaviour of the UE based on the validity of the system information by: based on determining that the system information is valid after the no always-on SSB transmission is stopped, determining, based on the system information, at least one of the following is allowed when or after the no always-on SSB transmission is stopped: access to the cell, initiating access to the cell, initiating a random access to the cell, monitoring paging occasions associated with the cell, monitoring a paging channel associated with the cell, or monitoring a short message from the cell.

In some implementations, the processor is configured to determine the behaviour of the UE based on the validity of the system information by: based on determining that the system information is invalid after the no always-on SSB transmission is stopped, determining, based on the system information, at least one of the following is not allowed when or after the no always-on SSB transmission is stopped: access to the cell, initiating access to the cell, initiating a random access to the cell, monitoring paging occasions associated with the cell, monitoring a paging channel associated with the cell, or monitoring a short message from the cell.

In some implementations, the information related to NES comprises a sixth indication indicating a no always-on SSB transmission from the cell is stopped. In such implementations, the processor is configured to determine the behaviour of the UE by: determining to trigger or perform cell selection or cell reselection based on the sixth indication.

In some implementations, the information related to NES comprises information related to a no always-on SSB transmission from the cell. In such implementations, the processor is configured to determine the behaviour of the UE by: determining the no always-on SSB transmission is stopped based on the information related to the no always-on SSB transmission; and determining to trigger or perform cell selection or cell reselection.

In some implementations, the information related to NES comprises a seventh indication indicating the cell is an NES cell. In such implementations, the processor is configured to determine the behaviour of the UE by: determining to trigger or perform cell selection or cell reselection based on the seventh indication.

In some implementations, the information related to NES comprises a first configuration for a dedicated feature for NES-capable UEs or a combination of features, the combination of features comprises the dedicated feature for NES-capable UEs, the dedicated feature for NES-capable UEs is associated with a dedicated set of random access resources for NES-capable UEs.

In some implementations, the information related to NES comprises a first priority for the dedicated feature for NES-capable UEs.

In some implementations, the processor is configured to determine the behaviour of the UE by: determining a second priority for random access resources which are not associated with the combination of features is the same as the first priority for the dedicated feature for NES-capable UEs.

In some implementations, the information related to NES comprises a second configuration for a dedicated set of random access resources for NES-capable UEs. In such implementations, the processor is configured to determine the behaviour of the UE by:based on determining the dedicated set of random access resources for NES-capable UEs overlaps with a first set of random access resources associated with a first feature, determining the dedicated set of random access resources is unavailable or available for random access.

In some implementations, the information related to NES comprises a second configuration for a dedicated set of random access resources for NES-capable UEs, the dedicated set of random access resources is not associated with a dedicated feature for NES-capable UEs.

Some implementations of a method described herein may include: obtaining, in an RRC_IDLE state or RRC_INACTIVE state, information related to NES; and determining, based on the information, behaviour of the UE related to access to a cell of a base station.

Some implementations of a processor described herein may include at least one memory and a controller coupled with the at least one memory and configured to cause the controller to: obtain, in an RRC_IDLE state or RRC_INACTIVE state, information related to NES; and determine, based on the information, behaviour of the UE related to access to a cell of a base station.

It is to be understood that the summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become easily comprehensible through the following description.

BRIEF DESCRIPTION OF THE DRAWINGS

Fig. 1 illustrates an example of a wireless communications system that supports management of access in accordance with aspects of the present disclosure;

Fig. 2 illustrates a flowchart of a method that supports management of access in accordance with aspects of the present disclosure;

Fig. 3A illustrates an example of on-demand SSB transmission in legacy;

Figs. 3B, 3C and 3D illustrate an example of on-demand SSB transmission in accordance with some aspects of the present disclosure, respectively;

Fig. 4A illustrates an example of a first set of random access resources associated with a first feature in accordance with some aspects of the present disclosure;

Fig. 4B illustrates an example of the first set of random access resources and a dedicated set of random access resources for NES-capable UEs in accordance with some aspects of the present disclosure;

Fig. 5 illustrates a flowchart of a method that supports management of access in accordance with aspects of the present disclosure;

Fig. 6 illustrates an example of a device that supports management of access in accordance with some aspects of the present disclosure; and

Fig. 7 illustrates an example of a processor that supports management of access in accordance with aspects of the present disclosure.

DETAILED DESCRIPTION

Principles of the present disclosure will now be described with reference to some embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. The disclosure described herein may be implemented in various manners other than the ones described below.

In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.

References in the present disclosure to “one embodiment, ” “an example embodiment, ” “an embodiment, ” “some embodiments, ” and the like indicate that the embodiment (s) described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment (s) . Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

It shall be understood that although the terms “first” and “second” or the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element could also be termed as a second element, and similarly, a second element could also be termed as a first element, without departing from the scope of embodiments. As used herein, the term “and/or” includes any and all combinations of one or more of the listed terms.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a” , “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” , “comprising” , “has” , “having” , “includes” and/or “including” , when used herein, specify the presence of stated features, elements, and/or components etc., but do not preclude the presence or addition of one or more other features, elements, components and/or combinations thereof.

As described above, referring to the discussion in 3GPP, the UE can access the cell at least when on-demand SSB is transmitting. However, it is not clear whether the UE can access the cell after the on-demand SSB transmission is stopped.

In view of the above, the present disclosure provides a solution that supports management of access. In this solution, a UE obtains, in an RRC_IDLE state or RRC_INACTIVE state, information related to NES. In turn, the UE determines, based on the information, behaviour of the UE related to access to a cell of a base station. With this solution, the UE can determine whether the UE can access a cell during or after no always-on SSB transmission.

Aspects of the present disclosure are described in the context of a wireless communications system.

Fig. 1 illustrates an example of a wireless communications system 100 that supports management of access in accordance with aspects of the present disclosure. The wireless communications system 100 may include one at least one of network entities 102 (also referred to as network equipment (NE) ) , one or more terminal devices or UEs 104, a core network 106, and a packet data network 108. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including institute of electrical and electronics engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA) , frequency division multiple access (FDMA) , or code division multiple access (CDMA) , etc.

The network entities 102 may be collectively referred to as network entities 102 or individually referred to as a network entity 102. Hereinafter, some implementations of the present disclosure will be described by taking a base station as an example of the network entity 102. Thus, the network entity 102 may be used interchangeably with the base station 102.

The network entities 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the network entities 102 described herein may be or include or may be referred to as a network node, a base station (BS) , a network element, a radio access network (RAN) node, a base transceiver station, an access point, a NodeB, an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology. A network entity 102 and a UE 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, a network entity 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.

A network entity 102 may provide a geographic coverage area 112 for which the network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc. ) for one or more UEs 104 within the geographic coverage area 112. For example, a network entity 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc. ) according to one or multiple radio access technologies. In some implementations, a network entity 102 may be moveable, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas 112 may be associated with different network entities 102. Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

The one or more UEs 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a remote unit, a handheld device, or a subscriber device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an internet-of-things (IoT) device, an internet-of-everything (IoE) device, or machine-type communication (MTC) device, among other examples. In some implementations, a UE 104 may be stationary in the wireless communications system 100. In some other implementations, a UE 104 may be mobile in the wireless communications system 100.

The one or more UEs 104 may be devices in different forms or having different capabilities. Some examples of UEs 104 are illustrated in Fig. 1. A UE 104 may be capable of communicating with various types of devices, such as the network entities 102, other UEs 104, or network equipment (e.g., the core network 106, the packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or another network equipment) , as shown in Fig. 1. Additionally, or alternatively, a UE 104 may support communication with other network entities 102 or UEs 104, which may act as relays in the wireless communications system 100.

A UE 104 may also be able to support wireless communication directly with other UEs 104 over a communication link 114. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 114 may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

A network entity 102 may support communications with the core network 106, or with another network entity 102, or both. For example, a network entity 102 may interface with the core network 106 through one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) . The network entities 102 may communicate with each other over the backhaul links 116 (e.g., via an X2, Xn, or another network interface) . In some implementations, the network entities 102 may communicate with each other directly (e.g., between the network entities 102) . In some other implementations, the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106) . In some implementations, one or more network entities 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC) . An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs) .

In some implementations, the network entity 102 may be implemented as a satellite. For example, the network entity 102-1 may be implemented as a satellite. Thus, network entity 102-1 is also referred to as a satellite 102-1. The network entity 102-1 may have full or part of an eNB/gNB on board. The communication link 110 between the satellite 102-1 and the UE 104, the communication link 116 between the satellite 102-1 and the network entity 102, and the communication link 116 between the satellite 102-1 and the core network 106 may be used for a non-terrestrial network (NTN) transparent mode. The communication link 110 between the satellite 102-1 and the UE 104, and the communication link 116 between the satellite 102-1 (with a base station on board) and the core network 106 may be used for a NTN regenerative mode.

In some implementations, a network entity 102 may be configured in a disaggregated architecture, which may be configured to utilize a protocol stack physically or logically distributed among two or more network entities 102, such as an integrated access backhaul (IAB) network, an open radio access network (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance) , or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN) ) . For example, a network entity 102 may include one or more of a central unit (CU) , a distributed unit (DU) , a radio unit (RU) , a RAN intelligent controller (RIC) (e.g., a near-real time RIC (Near-RT RIC) , a non-real time RIC (Non-RT RIC) ) , a service management and orchestration (SMO) system, or any combination thereof.

An RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) . One or more components of the network entities 102 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 102 may be located in distributed locations (e.g., separate physical locations) . In some implementations, one or more network entities 102 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU) ) .

Split of functionality between a CU, a DU, and an RU may be flexible and may support different functionalities depending upon which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof) are performed at a CU, a DU, or an RU. For example, a functional split of a protocol stack may be employed between a CU and a DU such that the CU may support one or more layers of the protocol stack and the DU may support one or more different layers of the protocol stack. In some implementations, the CU may host upper protocol layer (e.g., a layer 3 (L3) , a layer 2 (L2) ) functionality and signaling (e.g., radio resource control (RRC) , service data adaption protocol (SDAP) , packet data convergence protocol (PDCP) ) . The CU may be connected to one or more DUs or RUs, and the one or more DUs or RUs may host lower protocol layers, such as a layer 1 (L1) (e.g., physical (PHY) layer) or an L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160.

Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU and an RU such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack. The DU may support one or multiple different cells (e.g., via one or more RUs) . In some implementations, a functional split between a CU and a DU, or between a DU and an RU may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU, a DU, or an RU, while other functions of the protocol layer are performed by a different one of the CU, the DU, or the RU) .

A CU may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU may be connected to one or more DUs via a midhaul communication link (e.g., F1, F1-c, F1-u) , and a DU may be connected to one or more RUs via a fronthaul communication link (e.g., open fronthaul (FH) interface) . In some implementations, a midhaul communication link or a fronthaul communication link may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 102 that are in communication via such communication links.

The core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC) , or a 5G core (5GC) , which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management functions (AMF) ) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a packet data network (PDN) gateway (P-GW) , or a user plane function (UPF) ) . In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc. ) for the one or more UEs 104 served by the one or more network entities 102 associated with the core network 106.

The core network 106 may communicate with the packet data network 108 over one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) . The packet data network 108 may include an application server 118. In some implementations, one or more UEs 104 may communicate with the application server 118. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the core network 106 via a network entity 102. The core network 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server 118 using the established session (e.g., the established PDU session) . The PDU session may be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106) .

In the wireless communications system 100, the network entities 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) ) to perform various operations (e.g., wireless communications) . In some implementations, the network entities 102 and the UEs 104 may support different resource structures. For example, the network entities 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the network entities 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the network entities 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures) . The network entities 102 and the UEs 104 may support various frame structures based on one or more numerologies.

One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames) . Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols) . In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing) , a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (510 MHz –7.125 GHz) , FR2 (24.25 GHz –52.6 GHz) , FR3 (7.125 GHz –24.25 GHz) , FR4 (52.6 GHz –114.25 GHz) , FR4a or FR4-1 (52.6 GHz –71 GHz) , and FR5 (114.25 GHz –300 GHz) . In some implementations, the network entities 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the network entities 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data) . In some implementations, FR2 may be used by the network entities 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies) . For example, FR1 may be associated with a first numerology (e.g., μ=0) , which includes 15 kHz subcarrier spacing; a second numerology (e.g., μ=1) , which includes 30 kHz subcarrier spacing; and a third numerology (e.g., μ=2) , which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies) . For example, FR2 may be associated with a third numerology (e.g., μ=2) , which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., μ=3) , which includes 120 kHz subcarrier spacing.

Fig. 2 illustrates a flowchart of a method 200 that supports management of access in accordance with aspects of the present disclosure. In some implementations, the method 200 can be implemented at a UE, such as the UE 104 as shown in Fig. 1. For the purpose of discussion, the method 200 will be described with reference to Fig. 1.

At 210, the UE 104 in an RRC_IDLE state or RRC_INACTIVE state obtains information related to network energy saving (NES) .

In the context of the present disclosure, NES may involve many kinds of NES techniques such as on-demand system information request/transmission, adaptation transmission of SSB, cell discontinuous transmission (DTX) /discontinuous reception (DRX) , on-demand SSB or the like.

In some implementations, the UE 104 may be a network energy saving (NES) -capable UE or a UE supporting on-demand SSB or a UE supporting at least one NES technique.

In the context of the present disclosure, the term “an NES-capable UE” or the term “aUE with NES capability” may be used interchangeably with “aUE supporting NES” . The term “aUE supporting NES” may be used interchangeably with “aUE supporting an NES technique of on-demand system information request/transmission or “aUE supporting an NES technique of adaptation transmission of SSB” or “UE supporting an NES technique of on-demand SSB” . The term “acell supporting NES” may be used interchangeably with “acell supporting an NES technique of on-demand system information request/transmission or “acell supporting an NES technique of adaptation transmission of SSB” or “acell supporting an NES technique of on-demand SSB” .

In the context of the present disclosure, the term “no always-on SSB transmission” may refer to an SSB transmission which cannot be always transmitted by a gNB or acquired by a UE.

In some implementations, the “no always-on SSB transmission” may comprise on-demand SSB transmission or adaptation transmission of SSB or adaptation of SSB in time domain. Hereinafter, the term “adaptation transmission of SSB” may be may be used interchangeably with the term “adaptation of SSB” or “adaptation SSB transmission” .

In the context of the present disclosure, the term “on-demand SSB transmission” may be used interchangeably with the term “on-demand SSB” or “on-demand SSB burst” .

In the context of the present disclosure, reference to “on-demand SSB transmission” or “on-demand SSB” or “on-demand SSB burst” means that the SSB is not always broadcast periodically from a base station while the SSB can be transmitted after a UE transmits an UL signal (e.g. wake-up signal or any other suitable signals existing or to be developed in future) as a request for the SSB to the base station or the SSB can be transmitted without request from a UE.

In some implementations, the on-demand SSB may be one of the following: CD-SSB, NCD-SSB, or not CD-SSB.

In some implementations, the CD-SSB may be an SSB with remaining minimum system information (RMSI) associated.

In some implementations, the NCD-SSB may be an SSB without RMSI associated.

At 220, the UE 104 determines, based on the information, behaviour of the UE related to access to a cell of the base station 102.

With the method 200, the UE 104 can determine whether the UE 104 can access a cell during or after no always-on SSB transmission.

Fig. 3A illustrates an example 300A of SSB transmission in legacy. In the example 300A, SSB is broadcast periodically from a base station and SSB can always be acquired by a UE. Thus, system information can always be acquired by the UE.

Fig. 3B illustrates an example 300B of on-demand SSB transmission in accordance with some aspects of the present disclosure.

In the example 300B, the UE 104 may expect, based on the information related to the no always-on SSB transmission, that at least one SSB burst is transmitted on a cell from time instance A to time instance B and not transmitted on the cell after time instance B.

In some implementations, the information related to the no always-on SSB transmission comprises at least one of the following: a pattern of the no always-on SSB transmission, a duration of the no always-on SSB transmission, a period of the no always-on SSB transmission, start time of the no always-on SSB transmission, end time of the no always-on SSB transmission, or the number of times of the no always-on SSB transmission.

In some implementations, the UE 104 may expect at least one on-demand SSB burst is transmitted on a cell from time instance A to time instance B and not transmitted on the cell after time instance B. For example, the UE 104 may expect that at least one CD-SSB burst 310 is transmitted on the cell from time instance A 330 to time instance B 332 and not transmitted after time instance B 332. The UE 104 may also expect that at least one CD-SSB burst 320 is transmitted on the cell from time instance A 334 to time instance B 336 and not transmitted after time instance B 336. Hereinafter, the at least one CD-SSB burst 310 and at least one CD-SSB burst 320 are also referred to as a CD-SSB transmission 310 and a CD-SSB transmission 320, respectively.

After the CD-SSB transmission on the cell is stopped at time instance B 332, other RS is transmitted. In the example 300B, after the CD-SSB transmission on the cell is stopped at time instance B 332, channel state information reference signal (CSI-RS) is transmitted.

Fig. 3C illustrates an example 300C of on-demand SSB transmission in accordance with some aspects of the present disclosure.

In the example 300C, the UE 104 may expect, based on the information related to the no always-on SSB transmission, that at least one on-demand SSB burst is periodically transmitted from time instance A until the base station 102 turns OFF the on-demand SSB. For example, the UE 104 may expect that at least one CD-SSB burst 340 is transmitted on the cell from time instance A 360 until the base station 102 turns OFF the on-demand SSB at time instance 362.

After the CD-SSB transmission on the cell is stopped at time instance B 362, NCD-SSB 345 is transmitted.

Then, the UE 104 may expect that at least one CD-SSB burst 350 is transmitted on the cell from time instance A 364 until the base station 102 turns OFF the on-demand SSB at time instance 366.

Hereinafter, the at least one CD-SSB burst 340 and the at least one CD-SSB burst 350 are also referred to as a CD-SSB transmission 340 and a CD-SSB transmission 350.

Fig. 3D illustrates an example 300D of on-demand SSB transmission in accordance with some aspects of the present disclosure.

In the example 300D, the UE 104 may expect, based on the information related to the no always-on SSB transmission, that at least one on-demand SSB burst is periodically transmitted from time instance A until the base station 102 turns OFF the on-demand SSB. For example, the UE 104 may expect that at least one CD-SSB burst 370 is transmitted on the cell from time instance A 390 until the base station 102 turns OFF the on-demand SSB at time instance 392. Hereinafter, the at least one CD-SSB burst 370 is also referred to as a CD-SSB transmission 370.

In the example 300D, after the CD-SSB transmission on the cell is stopped at time instance B 392, no RS is transmitted. Then, the UE 104 may expect that at least one NCD-SSB burst 380 is transmitted on the cell from time instance A 394 until the base station 102 turns OFF the on-demand SSB at time instance 396. Hereinafter, the at least one NCD-SSB burst 380 is also referred to as an NCD-SSB transmission 380.

In some implementations, during at least one of the CD-SSB transmissions 310, 340 and 370, NCD-SSB transmission may be performed.

Hereinafter, some implementations of the information related to NES and the behaviour of the UE 104 will be described.

In some implementations, the information related to NES may comprise a first indication. The first indication indicates that the UE 104 can camp on the cell but cannot perform at least one of the following:

● access to the cell,

● initiating access to the cell,

● initiating a random access to the cell,

● monitoring paging occasions associated with the cell,

● monitoring a paging channel associated with the cell, or

● monitoring a short message from the cell.

In such implementations, the UE 104 may determine the behaviour of the UE 104 based on the first indication. For example, the UE 104 may determine, based on the first indication, that the UE 104 can camp on the cell but cannot perform at least one of the above. Because the UE 104 can camp on the cell, unnecessary cell reselection may be avoided.

Alternatively or additionally, in some implementations, the information related to NES may comprise a second indication. The second indication indicates that the UE 104 can camp on the cell but cannot perform at least one of the following when or after a no always-on SSB transmission from the cell is stopped:

● access to the cell,

● initiating access to the cell,

● initiating a random access to the cell,

● monitoring paging occasions associated with the cell,

● monitoring a paging channel associated with the cell, or

● monitoring a short message from the cell.

In such implementations, the UE 104 may determine the behaviour of the UE 104 based on the second indication. For example, the UE 104 may determine, based on the second indication, that the UE 104 can camp on the cell but cannot perform at least one of the above when or after a no always-on SSB transmission from the cell is stopped. Because the UE 104 can camp on the cell, unnecessary cell reselection may be avoided.

Alternatively or additionally, in some implementations, the UE 104 may receive, from the base station 102, information related to access to the cell during a no always-on SSB transmission from the cell. In such implementations, the information related to NES may comprise a third indication. The third indication indicates whether the UE 104 is allowed to use the information related to access to the cell when or after the no always-on SSB transmission is stopped. In such implementations, the UE 104 may determine the behaviour of the UE 104 based on the third indication. For example, the UE 104 may determine, based on the third indication, that whether the UE 104 is allowed to use the information related to access to the cell when or after the no always-on SSB transmission is stopped.

In some implementations, the information related to access to the cell may comprise at least one of the following: a configuration for random access channel (RACH) , a configuration for monitoring paging occasions associated with the cell, a configuration for monitoring a paging channel associated with the cell, a configuration for monitoring a short message from the cell.

Alternatively or additionally, in some implementations, the information related to NES may comprise a fourth indication. The fourth indication indicates whether the UE 104 can perform at least one of the following:

● access attempt to the cell,

● initiating access to the cell,

● initiating a random access to the cell,

● monitoring paging occasions associated with the cell,

● monitoring a paging channel associated with the cell, or

● monitoring a short message from the cell.

In such implementations, the UE 104 may determine the behaviour of the UE 104 based on the fourth indication. For example, the UE 104 may determine, based on the fourth indication, whether the UE 104 can perform at least one of the above.

Alternatively or additionally, in some implementations, the information related to NES may comprise a fifth indication. The fifth indication indicates whether the UE 104 can perform at least one of the following when or after a no always-on SSB transmission from the cell is stopped:

● access attempt to the cell,

● initiating access to the cell,

● initiating a random access to the cell,

● monitoring paging occasions associated with the cell,

● monitoring a paging channel associated with the cell, or

● monitoring a short message from the cell.

In such implementations, the UE 104 may determine the behaviour of the UE 104 based on the fifth indication. For example, the UE 104 may determine, based on the fifth indication, whether the UE 104 can perform at least one of the above when or after a no always-on SSB transmission from the cell is stopped.

In some implementations, the UE 104 may obtain the information related to NES by monitoring at least one of the following: paging occasions associated with the cell, a paging channel associated with the cell, or a short message from the cell.

In some implementations, if a paging message for the UE 104 is received on the paging occasions or the paging channel or the UE 104 determines that the short message is received, the UE 104 may reselect a further cell or initiating access to the further cell. The further cell is different from the cell associated with the paging occasions, the paging channel or the short message which is being monitored. Or the further cell is the target cell of the UE 104 for cell reselection.

Alternatively, in some implementations, the information related to NES may comprise a length of a timer. The timer may be used to control how long the access to the cell is allowed. The UE 104 may start the timer upon receiving the length of the timer from the base station 102 or when a no always-on SSB transmission from the cell is stopped. The UE 104 may determine at least one of the following is not allowed when the timer expires:

● access to the cell,

● initiating access to the cell,

● initiating a random access to the cell,

● monitoring paging occasions associated with the cell,

● monitoring a paging channel associated with the cell, or

● monitoring a short message from the cell.

In such implementations, the UE 104 may determine at least one of the above is allowed before the timer expires.

Consider the example 300B in Fig. 3B. The UE 104 may receive the length of the timer at time instance 337, and the UE 104 may start the timer at time instance 337. The timer expires at time instance 338. The UE 104 may determine at least one of the above is allowed before the timer expires at time instance 338. The UE 104 may determine at least one of the above is not allowed when the timer expires at time instance 338.

Alternatively, in the example 300B in Fig. 3B, the UE 104 may receive the length of the timer at time instance 332, and the UE 104 may start the timer at time instance 332. The timer expires at time instance 338. The UE 104 may determine at least one of the above is allowed before the timer expires at time instance 338. The UE 104 may determine at least one of the above is not allowed when the timer expires at time instance 338.

Alternatively, in some implementations, the information related to NES may comprise a time duration. The time duration may be used to control how long the access to the cell is allowed. The time duration starts from a timer instance when the UE 104 receives the time duration from the base station 102 or when a no always-on SSB transmission from the cell is stopped. The UE 104 may determine at least one of the following is not allowed when the time duration expires:

● access to the cell,

● initiating access to the cell,

● initiating a random access to the cell,

● monitoring paging occasions associated with the cell,

● monitoring a paging channel associated with the cell, or

● monitoring a short message from the cell.

In such implementations, the UE 104 may determine at least one of the above is allowed before the time duration expires.

Alternatively, in some implementations, the information related to NES may comprise a time instance. The UE 104 may determine at least one of the following is allowed before the time instance:

● access to the cell,

● initiating access to the cell,

● initiating a random access to the cell,

● monitoring paging occasions associated with the cell,

● monitoring a paging channel associated with the cell, or

● monitoring a short message from the cell.

In some implementations, if at least one of the following is allowed: access to the cell, initiating access to the cell, initiating a random access to the cell, monitoring paging occasions associated with the cell, monitoring a paging channel associated with the cell, or monitoring a short message from the cell, the UE 104 may determine that the information related to access to the cell can be used to perform at least one of the above.

In some implementations, the UE 104 may obtain the information related to NES by receiving system information from the cell of the base station 102. For example, the system information may comprise Master Information Block (MIB) , System Information Block Type 1 (SIB1) or other SIB. The MIB, SIB1 or other SIB may comprise the information related to NES.

Alternatively, in some implementations, the UE 104 may receive, from the base station 102, a paging message or a short message or an RRC message which may comprise the information related to NES.

Alternatively, in some implementations, the information related to NES may be predefined.

In some implementations, the first indication may be predefined. In such implementations, it may be predefined that the UE 104 can camp on the cell but cannot perform at least one of the following:

● access to the cell,

● initiating access to the cell,

● initiating a random access to the cell,

● monitoring paging occasions associated with the cell,

● monitoring a paging channel associated with the cell, or

● monitoring a short message from the cell.

Alternatively or additionally, in some implementations, the second indication may be predefined. In such implementations, it may be predefined that the UE 104 can camp on the cell but cannot perform at least one of the following when or after a no always-on SSB transmission from the cell is stopped:

● access to the cell,

● initiating access to the cell,

● initiating a random access to the cell,

● monitoring paging occasions associated with the cell,

● monitoring a paging channel associated with the cell, or

● monitoring a short message from the cell.

Alternatively or additionally, in some implementations, the third indication may be predefined. In such implementations, it may be predefined whether the UE 104 is allowed to use the information related to access to the cell when or after the no always-on SSB transmission is stopped.

Alternatively or additionally, in some implementations, the fourth indication may be predefined. In such implementations, it may be predefined whether the UE 104 can perform at least one of the following:

● access attempt to the cell,

● initiating access to the cell,

● initiating a random access to the cell,

● monitoring paging occasions associated with the cell,

● monitoring a paging channel associated with the cell, or

● monitoring a short message from the cell.

Alternatively or additionally, in some implementations, the fifth indication may be predefined. In such implementations, it may be predefined whether the UE 104 can perform at least one of the following when or after a no always-on SSB transmission from the cell is stopped:

● access attempt to the cell,

● initiating access to the cell,

● initiating a random access to the cell,

● monitoring paging occasions associated with the cell,

● monitoring a paging channel associated with the cell, or

● monitoring a short message from the cell.

Alternatively, in some implementations, the length of the timer may be predefined.

Alternatively, in some implementations, the timer duration may be predefined.

In some implementations, the UE 104 may obtain the information related to NES by receiving, from the cell, a no always-on SSB transmission. In such implementations, the UE 104 may determine the behaviour of the UE 104 based on a status of the no always-on SSB transmission and predefinition.

In some implementations, the UE 104 may determine the behaviour of the UE 104 when or after the no always-on SSB transmission is stopped is the same as second behaviour of the UE 104 during the no always-on SSB transmission. In such implementations, optionally, whether the access to the cell is allowed may be updated when next no always-on SSB transmission is transmitted.

Alternatively, in some implementations, it may be predefined that at least one of the following is allowed or not allowed when or after the no always-on SSB transmission is stopped:

● access to the cell,

● initiating access to the cell,

● initiating a random access to the cell,

● monitoring paging occasions associated with the cell,

● monitoring a paging channel associated with the cell, or

● monitoring a short message from the cell.

Alternatively, in some implementations, the UE 104 may obtain the information related to NES by receiving, from the cell, system information during a no always-on SSB transmission from the cell. The UE 104 may determine the behaviour of the UE 104 based on validity of the system information. Some implementations of determining the validity of the system information when or after the no always-on SSB transmission is stopped will be described later with reference to Fig. 5.

In some implementations, if the system information is valid after the no always-on SSB transmission is stopped, the UE 104 may determine, based on the system information, at least one of the following is allowed when or after the no always-on SSB transmission is stopped:

● access to the cell,

● initiating access to the cell,

● initiating a random access to the cell,

● monitoring paging occasions associated with the cell,

● monitoring a paging channel associated with the cell, or

● monitoring a short message from the cell.

In some implementations, if the system information is valid for a timer duration after the no always-on SSB transmission is stopped, the UE 104 may determine, based on the system information, at least one of the following is allowed when or after the no always-on SSB transmission is stopped:

● access to the cell,

● initiating access to the cell,

● initiating a random access to the cell,

● monitoring paging occasions associated with the cell,

● monitoring a paging channel associated with the cell, or

● monitoring a short message from the cell.

In some implementations, if the system information is invalid after the no always-on SSB transmission is stopped, the UE 104 may determine, based on the system information, at least one of the following is not allowed when or after the no always-on SSB transmission is stopped:

● access to the cell,

● initiating access to the cell,

● initiating a random access to the cell,

● monitoring paging occasions associated with the cell,

● monitoring a paging channel associated with the cell, or

● monitoring a short message from the cell.

In some implementations, as described above with reference to Fig. 3B, after the CD-SSB transmission on the cell is stopped at time instance B 332, other RS is transmitted. For example, after the CD-SSB transmission on the cell is stopped at time instance B 332, CSI-RS may be transmitted. If other RS is transmitted on the cell after no always-on SSB transmission is stopped, it may seem like the cell disappeared to the UE 104 in the RRC_IDLE state or RRC_INACTIVE state. The UE 104 may perform cell reselection after measurement for a while, which introduces the unnecessary measurement in the disappeared cell. To address this issue, the UE 104 may determine to trigger or perform cell selection or cell reselection based on determining that the no always-on SSB transmission is stopped. In this way, the delay for cell selection or cell reselection may be reduced and energy power of the UE 104 may be saved.

Hereinafter, some implementations of determining to trigger or perform cell selection or cell reselection will be described.

In some implementations, the information related to NES may comprise a sixth indication. The sixth indication indicates a no always-on SSB transmission from the cell is stopped. The UE 104 may determine to trigger or perform cell selection or cell reselection based on the sixth indication.

Alternatively, in some implementations, the information related to NES may comprise information related to a no always-on SSB transmission from the cell. The UE 104 may determine the no always-on SSB transmission is stopped based on the information related to the no always-on SSB transmission. In turn, the UE 104 may determine to trigger or perform cell selection or cell reselection.

● access to the cell,

● initiating access to the cell,

● initiating a random access to the cell,

● monitoring paging occasions associated with the cell,

● monitoring a paging channel associated with the cell, or

● monitoring a short message from the cell.

In such implementations, the UE 104 may determine to trigger or perform cell selection or cell reselection based on the first indication.

● access to the cell,

● initiating access to the cell,

● initiating a random access to the cell,

● monitoring paging occasions associated with the cell,

● monitoring a paging channel associated with the cell, or

● monitoring a short message from the cell.

In such implementations, the UE 104 may determine to trigger or perform cell selection or cell reselection based on the second indication.

Alternatively or additionally, in some implementations, the information related to NES may comprise a seventh indication indicating the cell is an NES cell. The UE 104 may determine to trigger or perform cell selection or cell reselection based on the seventh indication.

Alternatively, in some implementations, the UE 104 may determine the cell is an NES cell based on detection of signals received from the cell. Then, the UE 104 may determine to trigger or perform cell selection or cell reselection.

In some implementations, the cell selection may be any cell selection. For example, the UE 104 camps on the cell and cannot initiate access to the cell, or the system information is not valid.

In some implementations, intra-frequency cell reselection indication may be used if the system information is considered as valid or intra-frequency cell reselection indication in MIB may be used if NCD-SSB is received by the UE 104.

Currently, it has been agreed that NES-capable UEs can use both additional physical random access channel (PRACH) resources and PRACH resources for legacy UEs. If Release 17 or 18 random access partition is applied, it needs to study how the additional PRACH resources for NES-capable UEs be configured.

In some implementations, to address this issue, a dedicated feature for NES-capable UEs may be defined. In such implementations, the information related to NES may comprise a first configuration for a dedicated feature for NES-capable UEs or a combination of features. The combination of features may comprise the dedicated feature for NES-capable UEs. The dedicated feature for NES-capable UEs is associated with a dedicated set of random access resources for NES-capable UEs.

In some implementations, the UE 104 may receive, from the base station 102, the first configuration for the dedicated feature for NES-capable UEs or the combination of features via an FeatureCombination information element (IE) as shown in Table 1:

Table 1

In Table 1, the FeatureCombination IE indicates a feature or a combination of features to be associated with a set of random access resources (i.e. an instance of FeatureCombinationPreambles) . If a field “NES-capable UE” is present in the FeatureCombination IE, the filed indicates that “NES-capable UE” is part of this feature combination. The field “NES-capable UE” is set to “true” for the dedicated set of random access resources for NES-capable UEs. The random access resources in the dedicated set of random access resources for NES-capable UEs is also referred to as “additional PRACH resources” .

In some implementations, the UE 104 may consider the dedicated set of random access resources for NES-capable UEs as not available for a random access procedure for which the dedicated feature is not applicable.

In some implementations, the UE 104 may consider a set of random access resources which is not configured with FeatureCombination to be not associated with any feature except for the dedicated feature. In other words, the UE 104 may consider the set of random access resources which are not configured with FeatureCombination to be associated with the dedicated feature.

In some implementations, the information related to NES may comprise a first priority for the dedicated feature for NES-capable UEs.

In some implementations, the UE 104 may determine a second priority for random access resources which are not associated with the combination of features is the same as the first priority for the dedicated feature for NES-capable UEs.

In some implementations, among the available sets of random access resources for a random access procedure, the UE 104 may identify those configured with a feature which has the highest priority assigned in a filed “featurePriorities” among all the features applicable to this random access procedure. The filed “featurePriorities” indicates priorities for features.

Alternatively, in some implementations, the dedicated feature for NES-capable UEs may not be defined. In such implementations, the information related to NES may comprise a second configuration for a dedicated set of random access resources for NES-capable UEs. The dedicated set of random access resources is not associated with a dedicated feature for NES-capable UEs.

In such implementations, the dedicated set of random access resources can only be used by NES-capable UEs.

In such implementations, the UE 104 may consider the dedicated set of random access resources which is not configured with FeatureCombination to be not associated with any feature (PRACH resources for legacy UEs) and to be available for the NES-capable UEs.

In some implementations, the information related to NES may comprise a second configuration for a dedicated set of random access resources for NES-capable UEs. In such implementations, if the dedicated set of random access resources for NES-capable UEs overlaps with a first set of random access resources associated with a first feature, the UE 104 may determine the dedicated set of random access resources is unavailable or available for random access. This will be described later with reference to Fig. 4A.

Fig. 4A illustrates an example of a first set of random access resources 410 associated with a first feature in accordance with some aspects of the present disclosure. For example, the first feature may be one of the following: reduced capability (RedCap) , enhanced reduced capability (eRedCap) , or small data transmission (SDT) .

Fig. 4B illustrates an example of the first set of random access resources 410 and a dedicated set of random access resources for NES-capable UEs 420 in accordance with some aspects of the present disclosure. As shown in Fig. 4B, in addition to the first set of random access resources 410, the base station 102 may also configure a dedicated set of random access resources for NES-capable UEs 420. The dedicated set of random access resources for NES-capable UEs 420 overlaps with the first set of random access resources 410 associated with the first feature. The UE 104 may determine the dedicated set of random access resources 420 is unavailable for random access. Alternatively, the UE 104 may determine the dedicated set of random access resources 420 is available for random access.

Similarly, in some implementations, if the dedicated set of random access resources for NES-capable UEs overlaps with a second set of random access resources for legacy UEs, the UE 104 may determine the dedicated set of random access resources is unavailable or available for random access.

Fig. 5 illustrates a flowchart of a method 500 that supports management of access in accordance with aspects of the present disclosure. The method 500 may be considered as an example implementation of the method 200. In some implementations, the method 500 can be implemented at a UE, such as the UE 104 as shown in Fig. 1. For the purpose of discussion, the method 500 will be described with reference to Fig. 1.

At 510, the UE 104 in an RRC_IDLE state or RRC_INACTIVE state receives, from the cell, system information during a no always-on SSB transmission from the cell.

At 520, the UE 104 obtains information related to the no always-on SSB transmission from the base station 102 to the UE 104.

At 530, the UE 104 determines validity of system information based on the information related to the no always-on SSB transmission.

In some implementations, before determining validity of the system information, the UE 104 may receive the system information from the base station 102. The UE 104 may store the received system information. In turn, the UE 104 may determine validity of the stored system information.

In some implementations, the UE 104 may receive the system information based on the no always-on SSB transmission. For example, the system information may be scheduled by the no always-on SSB transmission.

In some implementations, the UE 104 may receive, from the base station 102, the system information or a paging message or a short message or an RRC message which comprises the information related to the no always-on SSB transmission. For example, the system information may comprise MIB, SIB1 or other SIB. The MIB, SIB1 or other SIB may comprise the information related to the no always-on SSB transmission. For example, the RRC message may be an RRCRelease message when the UE 104 is released to IDLE/INACTIVE state.

In some implementations, the information related to the no always-on SSB transmission may comprise a first indication indicating whether the system information is valid or invalid when or after the no always-on SSB transmission is stopped. The UE 104 may determine validity of system information based on the first indication. For example, the first indication may be an indicator of one bit. The indicator set to 1, “true” or “yes” may indicate the system information is valid when or after the no always-on SSB transmission is stopped. The indicator set to 0, “false” or “no” may indicate the system information is invalid when or after the no always-on SSB transmission is stopped.

Alternatively, in some implementations, the information related to the no always-on SSB transmission may be predefined. In some implementations, the UE 104 may determine validity of system information based on the predefinition. For example, it may be predefined that the system information is valid or invalid when or after the no always-on SSB transmission is stopped.

Alternatively, in some implementations, a first timer may be used to determine whether the system information is valid or invalid. For example, the first timer may be used to determine whether the system information received in a cell supporting on-demand SSB is valid or invalid. Alternatively, the first timer may be used to determine whether the system information received in a cell supporting on-demand SSB is valid or invalid when the on-demand SSB transmission is stopped.

In such implementations, the information related to the no always-on SSB transmission may comprise a first length of the first timer.

In some implementations, the no always-on SSB transmission may comprise a first no always-on SSB transmission. The UE 104 may start the first timer when the system information is successfully received during the first no always-on SSB transmission or when the first no always-on SSB transmission is stopped. Then, the UE 104 may consider the system information is valid till the first timer expires or consider the system information is invalid once the timer expires. The UE 104 may apply the system information acquisition procedure when the first timer expires.

In some implementations, the UE 104 may receive, from the base station 102, the system information or a paging message or a short message or an RRC message which comprises a length of the first timer. For example, the system information may comprise MIB, SIB1 or other SIB. The MIB, SIB1 or other SIB may comprise the length of the first timer.

Consider the example 300B in Fig. 3B. The no always-on SSB transmission may comprise the first no always-on SSB transmission. The first no always-on SSB transmission may be the CD-SSB transmission 310. The first timer may be used to determine whether the system information received in a cell supporting CD-SSB transmission is valid or invalid. Alternatively, the first timer may be used to determine whether the system information received in a cell supporting CD-SSB transmission is valid or invalid when the CD-SSB transmission is stopped at time instance B 332.

The UE 104 may start the first timer when the system information is successfully received during the CD-SSB transmission 310. That is, the UE 104 may start the first timer at a time instance between time instance A 330 and time instance B 332. Alternatively, the UE 104 may start the first timer when the CD-SSB transmission 310 is stopped at time instance B 332. Then, the UE 104 may consider the system information is valid till the first timer expires or consider the system information is invalid once the timer expires.

In some implementations, the system information is received during a first no always-on SSB transmission, and the information related to the no always-on SSB transmission comprise information related to a second no always-on SSB transmission subsequent to the first no always-on SSB transmission. In such implementations, the UE 104 may consider the system information is valid at least till the second no always-on SSB transmission.

Consider the example 300B in Fig. 3B. The system information is received during the first no always-on SSB transmission. The first no always-on SSB transmission may be the CD-SSB transmission 310. The second no always-on SSB transmission may be the CD-SSB transmission 320. The information related to the no always-on SSB transmission comprise information related to the CD-SSB transmission 320. In such implementations, the UE 104 may consider the system information is valid at least till the CD-SSB transmission 320. For example, the UE 104 may consider the system information is valid at least till the time instance A 334.

In some implementations, the information related to the no always-on SSB transmission may comprise at least one of the following:

● a pattern of the second no always-on SSB transmission,

● a duration of the second no always-on SSB transmission,

● a period of the second no always-on SSB transmission,

● start time of the second no always-on SSB transmission,

● end time of the second no always-on SSB transmission, or

● the number of times of the second no always-on SSB transmission.

In some implementations, the UE 104 may determine the second no always-on SSB transmission based on the information related to the no always-on SSB transmission.

For example, in the example 300B in Fig. 3B, the information related to the no always-on SSB transmission may comprise at least one of the following:

● a pattern of the CD-SSB transmission 320,

● a duration of the CD-SSB transmission 320, e.g., a duration from time instance A 334 to time instance B 336,

● a period of the CD-SSB transmission 320,

● start time of the CD-SSB transmission 320, e.g., the time instance A 334,

● end time of the CD-SSB transmission 320, e.g., the time instance B 336, or

● the number of times of the CD-SSB transmission 320.

In some implementations, the no always-on SSB transmission may comprise adaptation SSB transmission. In such implementations, the information related to the no always-on SSB transmission may comprise at least one of the following:

● a pattern of the adaptation SSB transmission,

● a duration of the adaptation SSB transmission, e.g., a duration from time instance A to time instance B,

● a duration of the adaptation SSB transmission with periodicity m, e.g., a duration from time instance A to time instance B,

● a period of the adaptation SSB transmission,

● a period of the adaptation SSB transmission with periodicity m,

● start time of the adaptation SSB transmission, e.g., the time instance A,

● start time of the adaptation SSB transmission with periodicity m, e.g., the time instance A,

● end time of the adaptation SSB transmission, e.g., the time instance B,

● end time of the adaptation SSB transmission with periodicity m, e.g., the time instance B,

● the number of times of the adaptation SSB transmission, e.g., adaptation SSB transmission 320 in Fig. 3B,

● the number of times of the adaptation SSB transmission with periodicity m, or

● the number of times of the CD-SSB transmission, e.g., adaptation SSB transmission 320 in Fig. 3B.

Alternatively, in some implementations, the information related to the no always-on SSB transmission may comprise a second length of a second timer.

In some implementations, the UE 104 may receive, from the base station 102, the system information or a paging message or a short message or an RRC message which comprises a length of the second timer. For example, the system information may comprise MIB, SIB1 or other SIB. The MIB, SIB1 or other SIB may comprise the length of the second timer.

In some implementations, the UE 104 may start the second timer when the system information is successfully received during the first no always-on SSB transmission or when the first no always-on SSB transmission is stopped. The UE 104 may determine the second no always-on SSB transmission based on the second timer.

In some implementations, the UE 104 may determine start time of the second no always-on SSB transmission based on expiry of the second timer. In other words, upon expiry of the second timer, the UE 104 may start to receive the second on-demand SSB transmission.

Consider the example 300B in Fig. 3B. The system information is received during the first no always-on SSB transmission. The first no always-on SSB transmission may be the CD-SSB transmission 310. The second no always-on SSB transmission may be the CD-SSB transmission 320. The information related to the no always-on SSB transmission comprise information related to the CD-SSB transmission 320.

The UE 104 may start the second timer when the system information is successfully received during the CD-SSB transmission 310. That is, the UE 104 may start the second timer at a time instance between time instance A 330 and time instance B 332. Alternatively, the UE 104 may start the second timer when the CD-SSB transmission 310 is stopped at time instance B 332. Then, when the second timer expires, the UE 104 starts to receive the CD-SSB transmission 320. The UE 104 may consider the system information is valid at least till the CD-SSB transmission 320.

In some implementations, the system information is received during the no always-on SSB transmission. In such implementations, the UE 104 may consider the system information is invalid when the no always-on SSB transmission is stopped.

● a pattern of the no always-on SSB transmission,

● a duration of the no always-on SSB transmission,

● a period of the no always-on SSB transmission,

● start time of the no always-on SSB transmission,

● end time of the no always-on SSB transmission, or

● the number of times of the no always-on SSB transmission.

Consider the example 300B in Fig. 3B. The system information is received during the no always-on SSB transmission. The no always-on SSB transmission may be the CD-SSB transmission 310. The UE 104 may consider the system information is invalid when the CD-SSB transmission 310 is stopped at time instance B 332.

Alternatively, in some implementations, the system information is received during the no always-on SSB transmission. In such implementations, the UE 104 may consider the system information is invalid when the no always-on SSB transmission is not detected.

Consider the example 300B in Fig. 3B. The system information is received during the first no always-on SSB transmission. The first no always-on SSB transmission may be the CD-SSB transmission 310. The second no always-on SSB transmission may be the CD-SSB transmission 320. The UE 104 may consider the system information is invalid when the CD-SSB transmission 320 is not detected.

Alternatively, in some implementations, the system information is received during the no always-on SSB transmission. In such implementations, the UE 104 may consider the system information is invalid when a first number of times of the no always-on SSB transmission is completed.

Consider the example 300B in Fig. 3B. The system information is received during the no always-on SSB transmission. The first number of times of the no always-on SSB transmission is equal to 2. The first number of times of the no always-on SSB transmission comprise the CD-SSB transmission 310 and the CD-SSB transmission 320. The UE 104 may consider the system information is invalid when the CD-SSB transmission 310 and the CD-SSB transmission 320 are completed.

Alternatively, in some implementations, the system information is received during the no always-on SSB transmission, and the information related to the no always-on SSB transmission may comprise information related to termination of the no always-on SSB transmission. The UE 104 may consider the system information is invalid upon receiving information related to termination of the no always-on SSB transmission from the base station 102.

In some implementations, the information related to termination of the no always-on SSB transmission may comprise at least one of the following:

● a pattern of the no always-on SSB transmission,

● a duration of the no always-on SSB transmission,

● a period of the no always-on SSB transmission,

● start time of the no always-on SSB transmission,

● end time of the no always-on SSB transmission, or

● the number of times of the no always-on SSB transmission.

Alternatively, in some implementations, the system information is received during a first no always-on SSB transmission. The UE 104 may detect all information received in a second no always-on SSB transmission subsequent to the first no always-on SSB transmission. Or if the UE 104 determines that the system information is valid, the UE 104 may detect all information received in a second no always-on SSB transmission subsequent to the first no always-on SSB transmission. In turn, the UE 104 may determine the detected information as updated system information.

Consider the example 300B in Fig. 3B. The system information is received during the first no always-on SSB transmission. The first no always-on SSB transmission may be the CD-SSB transmission 310. The second no always-on SSB transmission may be the CD-SSB transmission 320. The UE 104 determines that the system information is valid. Then, the UE 104 may detect all information received in the CD-SSB transmission 320. In turn, the UE 104 may determine the detected information as updated system information.

In some implementations, the information related to the no always-on SSB transmission comprise a third indication. The third indication indicates the UE 104 to detect all the information received in the second no always-on SSB transmission. The UE 104 may detect all the information received in the second no always-on SSB transmission subsequent based on the third indication.

In some implementations, the UE 104 may receive, from the base station 102, the system information or a paging message or a short message or an RRC message which comprises the third indication. For example, the system information may comprise MIB, SIB1 or other SIB. The MIB, SIB1 or other SIB may comprise the third indication.

At 540, the UE 104 determines the behaviour of the UE 104 based on validity of the system information.

Fig. 6 illustrates an example of a device 600 that supports management of access in accordance with aspects of the present disclosure. The device 600 may be an example of a network entity 102 or a UE 104 as described herein. The device 600 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof. The device 600 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 602, a memory 604, a transceiver 606, and, optionally, an I/O controller 608. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .

The processor 602, the memory 604, the transceiver 606, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the processor 602, the memory 604, the transceiver 606, or various combinations or components thereof may support a method for performing one or more of the operations described herein.

In some implementations, the processor 602, the memory 604, the transceiver 606, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) . The hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some implementations, the processor 602 and the memory 604 coupled with the processor 602 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 602, instructions stored in the memory 604) .

For example, the processor 602 may support wireless communication at the device 600 in accordance with examples as disclosed herein. The processor 602 may be configured to operable to support a means for performing the following: obtaining, in an RRC_IDLE state or RRC_INACTIVE state, information related to NES; and determining, based on the information, behaviour of the UE related to access to a cell of a base station.

The processor 602 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) . In some implementations, the processor 602 may be configured to operate a memory array using a memory controller. In some other implementations, a memory controller may be integrated into the processor 602. The processor 602 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 604) to cause the device 600 to perform various functions of the present disclosure.

The memory 604 may include random access memory (RAM) and read-only memory (ROM) . The memory 604 may store computer-readable, computer-executable code including instructions that, when executed by the processor 602 cause the device 600 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code may not be directly executable by the processor 602 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some implementations, the memory 604 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The I/O controller 608 may manage input and output signals for the device 600. The I/O controller 608 may also manage peripherals not integrated into the device M02. In some implementations, the I/O controller 608 may represent a physical connection or port to an external peripheral. In some implementations, the I/O controller 608 may utilize an operating system such as or another known operating system. In some implementations, the I/O controller 608 may be implemented as part of a processor, such as the processor 606. In some implementations, a user may interact with the device 600 via the I/O controller 608 or via hardware components controlled by the I/O controller 608.

In some implementations, the device 600 may include a single antenna 610. However, in some other implementations, the device 600 may have more than one antenna 610 (i.e., multiple antennas) , including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 606 may communicate bi-directionally, via the one or more antennas 610, wired, or wireless links as described herein. For example, the transceiver 606 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 606 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 610 for transmission, and to demodulate packets received from the one or more antennas 610. The transceiver 606 may include one or more transmit chains, one or more receive chains, or a combination thereof.

A transmit chain may be configured to generate and transmit signals (e.g., control information, data, packets) . The transmit chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM) , frequency modulation (FM) , or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM) . The transmit chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmit chain may also include one or more antennas 610 for transmitting the amplified signal into the air or wireless medium.

A receive chain may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receive chain may include one or more antennas 610 for receive the signal over the air or wireless medium. The receive chain may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal. The receive chain may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receive chain may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

Fig. 7 illustrates an example of a processor 700 that supports management of access in accordance with aspects of the present disclosure. The processor 700 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 700 may include a controller 702 configured to perform various operations in accordance with examples as described herein. The processor 700 may optionally include at least one memory 704, such as L1/L2/L3 cache. Additionally, or alternatively, the processor 700 may optionally include one or more arithmetic-logic units (ALUs) 706. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .

The processor 700 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 700) or other memory (e.g., random access memory (RAM) , read-only memory (ROM) , dynamic RAM (DRAM) , synchronous dynamic RAM (SDRAM) , static RAM (SRAM) , ferroelectric RAM (FeRAM) , magnetic RAM (MRAM) , resistive RAM (RRAM) , flash memory, phase change memory (PCM) , and others) .

The controller 702 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 700 to cause the processor 700 to support various operations in accordance with examples as described herein. For example, the controller 702 may operate as a control unit of the processor 700, generating control signals that manage the operation of various components of the processor 700. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

The controller 702 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 704 and determine subsequent instruction (s) to be executed to cause the processor 700 to support various operations in accordance with examples as described herein. The controller 702 may be configured to track memory address of instructions associated with the memory 704. The controller 702 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 702 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 700 to cause the processor 700 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 702 may be configured to manage flow of data within the processor 700. The controller 702 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 700.

The memory 704 may include one or more caches (e.g., memory local to or included in the processor 700 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementation, the memory 704 may reside within or on a processor chipset (e.g., local to the processor 700) . In some other implementations, the memory 704 may reside external to the processor chipset (e.g., remote to the processor 700) .

The memory 704 may store computer-readable, computer-executable code including instructions that, when executed by the processor 700, cause the processor 700 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 702 and/or the processor 700 may be configured to execute computer-readable instructions stored in the memory 704 to cause the processor 700 to perform various functions. For example, the processor 700 and/or the controller 702 may be coupled with or to the memory 704, the processor 700, the controller 702, and the memory 704 may be configured to perform various functions described herein. In some examples, the processor 700 may include multiple processors and the memory 704 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.

The one or more ALUs 706 may be configured to support various operations in accordance with examples as described herein. In some implementation, the one or more ALUs 706 may reside within or on a processor chipset (e.g., the processor 700) . In some other implementations, the one or more ALUs 706 may reside external to the processor chipset (e.g., the processor 700) . One or more ALUs 706 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 706 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 706 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 706 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 706 to handle conditional operations, comparisons, and bitwise operations.

The processor 700 may support wireless communication at the device 600 in accordance with examples as disclosed herein. The processor 700 may be configured to operable to support a means for performing the following: obtaining, in an RRC_IDLE state or RRC_INACTIVE state, information related to NES; and determining, based on the information, behaviour of the UE related to access to a cell of a base station.

It shall be noted that implementations of the present disclosure which have been described with reference to Figs. 1 to 5 are also applicable to the device 600 and the processor 700.

It should be noted that the methods described herein describes possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined.

The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

As used herein, including in the claims, an article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of” or “one or both of” ) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) . Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

A user equipment (UE) , comprising:

a processor; and

a transceiver coupled to the processor;

wherein the processor is configured to:

obtain, in a radio resource control (RRC) _IDLE state or RRC_INACTIVE state, information related to network energy saving (NES) ; and

determine, based on the information, behaviour of the UE related to access to a cell of a base station.
The UE of claim 1, wherein the information related to NES comprises a first indication indicating that the UE can camp on the cell but cannot perform at least one of the following:

access to the cell,

initiating access to the cell,

initiating a random access to the cell,

monitoring paging occasions associated with the cell,

monitoring a paging channel associated with the cell, or

monitoring a short message from the cell; and

wherein the processor is configured to determine the behaviour of the UE based on the first indication.
The UE of claim 2, wherein the processor is configured to determine the behaviour of the UE based on the first indication by:

determining to trigger or perform cell selection or cell reselection based on the first indication.
The UE of claim 1, wherein the information related to NES comprises a second indication indicating that the UE can camp on the cell but cannot perform at least one of the following when or after a no always-on synchronization signal block (SSB) transmission from the cell is stopped:

access to the cell,

initiating access to the cell,

initiating a random access to the cell,

monitoring paging occasions associated with the cell,

monitoring a paging channel associated with the cell, or

monitoring a short message from the cell; and

wherein the processor is configured to determine the behaviour of the UE based on the second indication.
The UE of claim 4, wherein the processor is configured to determine the behaviour of the UE based on the second indication by:

determining to trigger or perform cell selection or cell reselection based on the second indication.
The UE of claim 1, wherein the information related to NES comprises a fifth indication indicating whether the UE can perform at least one of the following when or after a no always-on synchronization signal block (SSB) transmission from the cell is stopped:

access attempt to the cell,

initiating access to the cell,

initiating a random access to the cell,

monitoring paging occasions associated with the cell,

monitoring a paging channel associated with the cell, or

monitoring a short message from the cell; and

wherein the processor is configured to determine the behaviour of the UE based on the fifth indication.
The UE of claim 1, wherein the processor is configured to obtain the information related to NES by monitoring at least one of the following:

paging occasions associated with the cell,

a paging channel associated with the cell, or

a short message from the cell.
The UE of claim 7, wherein the processor is configured to determine the behaviour of the UE by:

based on determining that a paging message for the UE is received on the paging occasions or the paging channel or determining that the short message is received, reselecting a further cell or initiating access to the further cell.
The UE of claim 1, wherein the information related to NES comprises a time instance;

wherein the processor is configured to determine the behaviour of the UE by determining at least one of the following is allowed before the time instance:

access to the cell,

initiating access to the cell,

initiating a random access to the cell,

monitoring paging occasions associated with the cell,

monitoring a paging channel associated with the cell, or

monitoring a short message from the cell.
The UE of claim 1, wherein the information related to NES is predefined.
The UE of claim 1, wherein the processor is configured to obtain the information related to NES by:

receiving, via the transceiver from the cell, a no always-on synchronization signal block (SSB) transmission; and

wherein the processor is configured to determine the behaviour of the UE based on a status of the no always-on SSB transmission and predefinition.
The UE of claim 1, wherein the processor is configured to obtain the information related to NES by:

receiving, via the transceiver from the cell, system information during a no always-on synchronization signal block (SSB) transmission from the cell; and

wherein the processor is configured to determine the behaviour of the UE based on validity of the system information.
The UE of claim 1, wherein the information related to NES comprises a sixth indication indicating a no always-on synchronization signal block (SSB) transmission from the cell is stopped; and

wherein the processor is configured to determine the behaviour of the UE by:

determining to trigger or perform cell selection or cell reselection based on the sixth indication.
The UE of claim 1, wherein the information related to NES comprises information related to a no always-on synchronization signal block (SSB) transmission from the cell; and

wherein the processor is configured to determine the behaviour of the UE by:

determining the no always-on SSB transmission is stopped based on the information related to the no always-on SSB transmission; and

determining to trigger or perform cell selection or cell reselection.
The UE of claim 1, wherein the information related to NES comprises a seventh indication indicating the cell is an NES cell; and

wherein the processor is configured to determine the behaviour of the UE by:

determining to trigger or perform cell selection or cell reselection based on the seventh indication.
The UE of claim 1, wherein the information related to NES comprises a first configuration for a dedicated feature for NES-capable UEs or a combination of features, the combination of features comprises the dedicated feature for NES-capable UEs, the dedicated feature for NES-capable UEs is associated with a dedicated set of random access resources for NES-capable UEs.
The UE of claim 16, wherein the information related to NES comprises a first priority for the dedicated feature for NES-capable UEs.
The UE of claim 1, wherein the information related to NES comprises a second configuration for a dedicated set of random access resources for NES-capable UEs; and

wherein the processor is configured to determine the behaviour of the UE by:

based on determining the dedicated set of random access resources for NES-capable UEs overlaps with a first set of random access resources associated with a first feature, determining the dedicated set of random access resources is unavailable or available for random access.
A processor for wireless communication, comprising:

at least one memory; and

a controller coupled with the at least one memory and configured to cause the controller to:

obtain, in a radio resource control (RRC) _IDLE state or RRC_INACTIVE state, information related to network energy saving (NES) ; and

determine, based on the information, behaviour of the UE related to access to a cell of a base station.
A method performed by a user equipment (UE) , comprising:

obtaining, in a radio resource control (RRC) _IDLE state or RRC_INACTIVE state, information related to network energy saving (NES) ; and

determining, based on the information, behaviour of the UE related to access to a cell of a base station.