Masking on additional random access channel (RACH) occasion

Abstract

A user equipment, UE (22), that is configured to communicate with a network node (16) is provided. The UE (22) is configured to receive a bitmap indicating an activation status of each of a plurality of Random Access Channel, RACH, Occasions, ROs; and communicate with the network node (16) based on the bitmap.

Description

[0001] MASKING ON ADDITIONAL RANDOM ACCESS CHANNEL (RACH) OCCASION FIELD

[0002] The present disclosure relates to wireless communications, and in particular, to masking of Random Access Channel, RACH, occasions, ROs.

[0003] BACKGROUND

[0004] The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile user equipments (UE), as well as communication between network nodes and between UEs. The 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks.

[0005] NW energy consumption

[0006] Network (NW) power consumption in NR has increased significantly compared to LTE, partly due to higher bandwidth (BW) and massive number of antennas. This is still evident even if there are no UEs present in a cell. Although there is no uplink (UL) or downlink (DL) transmission between a specific UE and a network node in idle mode, the network node may still need to periodically transmit signals, such as Synchronization Signal Block (SSB) and broadcast system information, e.g., System Information Block 1 (SIB1). For example, SSBs can be configured with 20ms periodicity, and SIB1 can be configured with 160ms periodicity. In addition, the network node may also need to periodically monitor the preambles from a UE to support random access, which implies that the receiver components of the network node may need to be turned on periodically, e.g., every 10ms or less. Hence, although increasing the sleep time of a network node can reduce the NW energy consumption, the sleep time of the network node is constrained by the periodicity of transmit and receive.

[0007] RACH Configuration

[0008] The RACH in 5G is a fundamental uplink channel used by UE to establish communication with the network node. It is part of the Random- Access Procedure, which enables initial access, connection re-establishment, handovers, and other scenarios where the UE needs to synchronize with the network or request resources. Random Access Channel (RACH) resources are configured via higher layers (e.g., system information),and typical RACH resources may occur periodically as shown in FIG. 1 (illustrating uplink resources for random access (e.g., one RACH occasion in subframe #4 of each radio frame)), where each cell corresponds to a slot or a subframe. After sending a RACH, UE monitors for a RACH response in a search space (e.g., ra-searchSpace, that is configured by higher layers), and if it does not receive a response within a pre-determined amount of time, the UE tries to send RACH again.

[0009] Legacy RACH occasions

[0010] Up until 3GPP Release 18 (Rel-18) versions of the 3GPP specification (see, e.g., 3GPP Technical Specification (TS) 38.331 V18.0.0), PRACH resources semi-statically configured in SIB1 may be updated in by the NW via the System Information (SI) Update procedure. If the RACH configuration info in the SIB1 changes, an SI update will be signalled via the paging Downlink Control Information (DCI) short message mechanism, in all RACH Occasions (ROs) for the current cell during a SI modification period to ensure the info is received by all UEs camping on the cell. The actual change takes place after the SI modification period.

[0011] Additional RACH occasions

[0012] In 3GPP Release 19 (Rel-19) Network Energy Saving (NES) Work Item (WI) introduces dynamic adaptation of RACH occasions. As such, additional ROs will be provided beyond a baseline RO configuration. This is illustrated in FIG. 2 (illustrating a configuration of legacy (top) and additional (middle) random access opportunities (RO)) wherein a baseline configuration is provided in SIB1 according to legacy means (FIG. 2, top subfigure). Additional ROs are also configured in SIB1 (FIG. 2, mid subfigure) but only intended to be used when indicated by the NW. The bottom subfigure of FIG. 2 shows the sum of available ROs for the UE where the additional ROs are also activated.

[0013] In RAN1_119, the following agreements have been made corresponding to PRACH adaptation:

[0014] Agreement

[0015] For DCI-based adaptation for additional PRACH resources, select only from the following alternatives:

[0016] • Alt 1 : (PRACH resource configuration level) DCI-based adaptation to indicate whether the additional PRACH resources provided by semi-static signalling are available or not

[0017] o FFS: details• Alt 2: (subset of PRACH resource level) DCI-based adaptation to indicate whether a subset of the additional PRACH resources provided by semi-static signalling are available or not

[0018] o FFS: Maximum number of subsets of the additional PRACH resources= [2 or 3 or 4 or 16]

[0019] o FFS: whether the subset of the additional PRACH resources is in ■ Alt 2-1: RO level per SSB

[0020] ■ Alt 2-2: SSB-to-RO mapping cycle level

[0021] ■ Alt 2-3: PRACH association period level

[0022] ■ Alt 2-4: PRACH association pattern period level

[0023] ■ Alt 2-5: SFN level

[0024] ■ Alt 2-6: Network configured time period

[0025] Agreement

[0026] For DCI-based adaptation for additional PRACH resources, select only from the following alternatives:

[0027] • Alt 1 : DCI-based adaptation to indicate whether the additional PRACH resources provided by semi-static signalling are available or not

[0028] o [DCI payload size = 1 bit]

[0029] o FFS: A single PRACH mask provided by semi-static signalling is used to identify the subset of the additional PRACH resources

[0030] o FFS: details

[0031] SUMMARY

[0032] Some embodiments advantageously provide methods, systems, and apparatuses for masking of ROs.

[0033] Existing agreements on NW energy saving topic in 3GPP allows NW to adapt RACH resources. And RACH adaptation can provide denser ROs than legacy RACH configuration. However, to optimize the NW energy consumption and obtain more sleeping opportunities for NW, it is necessary to deactivate a part of additional ROs and generate condensed ROs when additional RACH configuration is activated.

[0034] Embodiments described herein relate to deactivation of a part of additional ROs for network energy saving propose. For example, in some embodiments, a bitmap is configured in system information to indicate to the UEs the activation status of additional ROs at system-frame-number (SFN) level. The bitmap may take a maximum of 16 bits, and with a periodic pattern (e.g. 4-bits), the bitmap field size can be much shorter.In some embodiments, masking related information is exchanged via NW interfaces, including Fl and Xn.

[0035] In some embodiments, for NES-capable UEs, NW (e.g., via network node) configures a bitmap in SI to indicate the activation status of additional ROs. Each bit in the bitmap represents an interval. The interval can be one or multiple SFN / Physical RACH (PRACH) association period level / PRACH association pattern period level. The activation / deactivation state of additional ROs in a specific interval is represented by 0 and 1. The bitmap is semi-dynamically configured in SI, which means DCI indication is not needed for it.

[0036] Hence, embodiments described herein may be less complex to implement and offer greater flexibility to improve provisioning of additional PRACH resource that are complementary to legacy RACH resources.

[0037] Further, signalling of masking related information via NW interfaces enables enhanced coordination of RACH configurations including better reuse / utilization of PRACH resources.

[0038] According to one aspect of the present disclosure, a method implemented in a user equipment, UE, that is configured to communicate with a network node is provided. A bitmap indicating an activation status of each of a plurality of Random Access Channel, RACH, Occasions, ROs, is received. Communication with the network node is based on the bitmap.

[0039] According to one or more embodiments of this aspect, the bitmap comprises a plurality of bits, each of the plurality of bits corresponding to a respective interval; and each of the plurality of bits indicates an activation status of the one or more ROs of the plurality of ROs in the respective interval.

[0040] According to one or more embodiments of this aspect, the interval comprises: one or more System Frame Numbers, SFNs; one or more Physical Random Access Channel, PRACH, association periods; one or more PRACH association pattern periods; or one or more Synchronization Signal Block, SSB, beams.

[0041] According to one or more embodiments of this aspect, a plurality of bits in the bitmap map to an interval, the interval being at a System Frame Number, SFN, level; and the plurality of bits indicates activation statuses of the plurality of ROs in a plurality of SFNs.

[0042] According to one or more embodiments of this aspect, a plurality of bits in the bitmap map to an interval, the interval being at a Physical Random Access Channel,PRACH, association period level or at a PRACH association patern period level; and the plurality of bits indicating activation statuses of the plurality of ROs in a plurality of PRACH association periods or a plurality of PRACH association patern periods.

[0043] According to one or more embodiments of this aspect, a plurality of bits in the bitmap map to an interval at a Synchronization Signal Block, SSB, level; and the plurality of bits indicate activation statuses of the plurality of ROs associated with a plurality of SSB beams.

[0044] According to one or more embodiments of this aspect, the bitmap is configured to apply periodically to the plurality of ROs.

[0045] According to one or more embodiments of this aspect, the bitmap is indicated in one or both of System Information, SI, and an SI update.

[0046] According to one or more embodiments of this aspect, the communicating with the network node based on the bitmap comprises transmiting Physical Random Access Channel, PRACH, signaling in a RACH resource selected from an RO of the one or more ROs of the plurality of ROs having an activation status as active.

[0047] According to one or more embodiments of this aspect, a first configuration for RACH resources is received, where the first configuration is associated with first ROs. A second configuration for RACH resources is received, where the second configuration is associated with additional ROs. The bitmap is configured to apply to the second configuration and not the first configuration.

[0048] According to another aspect of the present disclosure, a user equipment, UE, that is configured to communicate with a network node is provided. The UE is configured to: receive a bitmap indicating an activation status of each of a plurality of Random Access Channel, RACH, Occasions, ROs; and communicate with the network node based on the bitmap.

[0049] According to one or more embodiments of this aspect, the bitmap comprises a plurality of bits, each of the plurality of bits corresponding to a respective interval; and each of the plurality of bits indicates an activation status of the one or more ROs of the plurality of ROs in the respective interval.

[0050] According to one or more embodiments of this aspect, the interval comprises: one or more System Frame Numbers, SFNs; one or more Physical Random Access Channel, PRACH, association periods; one or more PRACH association pattern periods; or one or more Synchronization Signal Block, SSB, beams.According to one or more embodiments of this aspect, a plurality of bits in the bitmap map to an interval, the interval being at a System Frame Number, SFN, level; and the plurality of bits indicating activation statuses of the plurality of ROs in a plurality of SFNs.

[0051] According to one or more embodiments of this aspect, a plurality of bits in the bitmap map to an interval, the interval being at a Physical Random Access Channel, PRACH, association period level or at a PRACH association pattern period level; and the plurality of bits indicating activation statuses of the plurality of ROs in a plurality of PRACH association periods or a plurality of PRACH association pattern periods.

[0052] According to one or more embodiments of this aspect, a plurality of bits in the bitmap map to an interval at a Synchronization Signal Block, SSB, level; and the plurality of bits indicate activation statuses of the plurality of ROs associated with a plurality of SSB beams.

[0053] According to one or more embodiments of this aspect, the bitmap is configured to apply periodically to the plurality of ROs.

[0054] According to one or more embodiments of this aspect, the bitmap is indicated in one or both of System Information, SI, and an SI update.

[0055] According to one or more embodiments of this aspect, the communicating with the network node based on the bitmap comprises transmitting Physical Random Access Channel, PRACH, signaling in a RACH resource selected from an RO of the one or more ROs of the plurality of ROs having an activation status as active.

[0056] According to one or more embodiments of this aspect, a first configuration for RACH resources is received, where the first configuration is associated with first ROs;

[0057] A second configuration for RACH resources is received, where the second configuration is associated with additional ROs. The bitmap is configured to apply to the second configuration and not the first configuration.

[0058] According to another aspect of the present disclosure, a method implemented in a network node that is configured to communicate with a user equipment, UE is provided. The UE is configured with a bitmap indicating an activation status of each of a plurality of Random Access Channel, RACH, Occasions, ROs. Communicate with the UE based on the bitmap.

[0059] According to one or more embodiments of this aspect, the bitmap comprises a plurality of bits, each of the plurality of bits corresponding to a respective interval; andeach of the plurality of bits indicates an activation status of the one or more ROs of the plurality of ROs in the respective interval.

[0060] According to one or more embodiments of this aspect, the interval comprises: one or more System Frame Numbers, SFNs; one or more Physical Random Access Channel, PRACH, association periods; one or more PRACH association pattern periods; or one or more Synchronization Signal Block, SSB, beams.

[0061] According to one or more embodiments of this aspect, the plurality of bits in the bitmap map to an interval, where the interval is at a System Frame Number, SFN, level; and the plurality of bits indicate activation statuses of the plurality of ROs in the plurality of SFNs.

[0062] According to one or more embodiments of this aspect, a plurality of bits in the bitmap map to an interval, the interval being at a Physical Random Access Channel, PRACH, association period level or at a PRACH association pattern period level; and the plurality of bits indicating activation statuses of the plurality of ROs in a plurality of PRACH association periods or a plurality of PRACH association pattern periods.

[0063] According to one or more embodiments of this aspect, a plurality of bits in the bitmap map to an interval at a Synchronization Signal Block, SSB, level; and the plurality of bits indicate activation statuses of the plurality of ROs associated with a plurality of SSB beams.

[0064] According to one or more embodiments of this aspect, the bitmap is configured to apply periodically to the plurality of ROs.

[0065] According to one or more embodiments of this aspect, the bitmap is indicated in one or both of System Information, SI, and an SI update.

[0066] According to one or more embodiments of this aspect, the communicating with the UE based on the bitmap comprises receiving Physical Random Access Channel, PRACH, signaling in a RACH resource selected from an RO of the one or more ROs of the plurality of ROs having an activation status as active.

[0067] According to one or more embodiments of this aspect, a first configuration for RACH resources is transmitted, where the first configuration is associated with first ROs. A second configuration for RACH resources is transmitted, where the second configuration is associated with additional ROs. The bitmap is configured to apply to the second configuration and not the first configuration.According to one or more embodiments of this aspect, masking related information for PRACH coordination is received from another network node, the masking related information indicating the bitmap.

[0068] According to one or more embodiments of this aspect, masking related information for PRACH coordination is transmitted to one or more other network nodes, where the masking related information indicates the bitmap.

[0069] According to another aspect of the present disclosure, a network node that is configured to communicate with a user equipment, UE, is provided. The network node is configured to: configure the UE with a bitmap indicating an activation status of each of a plurality of Random Access Channel, RACH, Occasions, ROs; and communicate with the UE based on the bitmap.

[0070] According to one or more embodiments of this aspect, the bitmap comprises a plurality of bits, each of the plurality of bits corresponding to a respective interval; and each of the plurality of bits indicates an activation status of the one or more ROs of the plurality of ROs in the respective interval.

[0071] According to one or more embodiments of this aspect, the interval comprises: one or more System Frame Numbers, SFNs; one or more Physical Random Access Channel, PRACH, association periods; one or more PRACH association pattern periods; or one or more Synchronization Signal Block, SSB, beams.

[0072] According to one or more embodiments of this aspect, the plurality of bits in the bitmap map to an interval, the interval is at a System Frame Number, SFN, level; and the plurality of bits indicate activation statuses of the plurality of ROs in the plurality of SFNs.

[0073] According to one or more embodiments of this aspect, a plurality of bits in the bitmap map to an interval, the interval being at a Physical Random Access Channel, PRACH, association period level or at a PRACH association pattern period level; and the plurality of bits indicates activation statuses of the plurality of ROs in a plurality of PRACH association periods or a plurality of PRACH association pattern periods.

[0074] According to one or more embodiments of this aspect, a plurality of bits in the bitmap map to an interval at a Synchronization Signal Block, SSB, level; and the plurality of bits indicate activation statuses of the plurality of ROs associated with a plurality of SSB beams.

[0075] According to one or more embodiments of this aspect, the bitmap is configured to apply periodically to the plurality of ROs.According to one or more embodiments of this aspect, the bitmap is indicated in one or both of System Information, SI, and an SI update.

[0076] According to one or more embodiments of this aspect, the communicating with the UE based on the bitmap comprises receiving Physical Random Access Channel, PRACH, signaling in a RACH resource selected from an RO of the one or more ROs of the plurality of ROs having an activation status as active.

[0077] According to one or more embodiments of this aspect, the network node is further configured to: transmit a first configuration for RACH resources, where the first configuration is associated with first ROs; transmit a second configuration for RACH resources, and where the second configuration is associated with additional ROs; and the bitmap is configured to apply to the second configuration and not the first configuration.

[0078] According to one or more embodiments of this aspect, masking related information for PRACH coordination is received from another network node, the masking related information indicating the bitmap.

[0079] According to one or more embodiments of this aspect, the network node is further configured to transmit masking related information for PRACH coordination to one or more other network nodes, the masking related information indicating the bitmap.

[0080] BRIEF DESCRIPTION OF THE DRAWINGS

[0081] A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

[0082] FIG. 1 is a diagram of resources for random access;

[0083] FIG. 2 is a diagram of configurations for random access opportunities;

[0084] FIG. 3 is a schematic diagram of an example network architecture illustrating a communication system according to principles disclosed herein;

[0085] FIG. 4 is a block diagram of a network node in communication with a user equipment over a wireless connection according to some embodiments of the present disclosure;

[0086] FIG. 5 is a schematic diagram of another example network architecture illustrating a communication system according to principles disclosed herein;FIG. 6 is a flowchart of an example process in a network node according to some embodiments of the present disclosure;

[0087] FIG. 7 is a flowchart of another example process in a network node according to some embodiments of the present disclosure;

[0088] FIG. 8 is a flowchart of an example process in a user equipment according to some embodiments of the present disclosure;

[0089] FIG. 9 is a flowchart of another example process in a user equipment according to some embodiments of the present disclosure;

[0090] FIG. 10 is a schematic diagram of another example network architecture illustrating a communication system according to principles disclosed herein;

[0091] FIG. 11 is a diagram of additional ROs before applying mask according to some embodiments of the present disclosure;

[0092] FIG. 12 is a diagram of additional ROs after applying mask according to some embodiments of the present disclosure;

[0093] FIG. 13 is a diagram of unevenly distributed additional ROs after applying mask FIG. 14 is a diagram of additional ROs before applying a mask according to some embodiments of the present disclosure;

[0094] FIG. 15 is a diagram of additional ROs after applying a mask according to some embodiments of the present disclosure; and

[0095] FIG. 16 is a diagram of additional ROs after applying a mask according to some embodiments of the present disclosure.

[0096] DETAILED DESCRIPTION

[0097] Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to masking of ROs. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

[0098] As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose ofdescribing particular embodiments only and is not intended to be limiting of the concepts described herein. 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,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0099] In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.

[0100] In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and / or wireless connections.

[0101] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. 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,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0102] The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), gNB -centralized unit (CU), gNB-distributed unit (DU), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell / multicast coordination entity (MCE), relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node,positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a user equipment (UE) such as a wireless device (WD) or a radio network node.

[0103] In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The UE herein can be any type of user equipment capable of communicating with a network node or another UE over radio signals, such as a wireless device (WD). The UE may also be a radio communication device, target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine communication (M2M), low-cost and / or low-complexity UE, a sensor equipped with UE, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device etc.

[0104] Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell / multicast Coordination Entity (MCE), relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

[0105] Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and / or New Radio (NR) and / or 6G, may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. It is contemplated that other 3GPP systems may make use of the concepts and arrangements disclosed herein. For example, a disclosure relating to NR may also be implementable in a 6G system and / or an LTE system, a disclosure relating to 6G may also be implementable in a NR and / or LTE system, and a disclosure relating to LTE may also be implementable in a NR and / or 6G system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

[0106] Note further, that functions described herein as being performed by a user equipment or a network node may be distributed over a plurality of user equipmentsand / or network nodes. In other words, it is contemplated that the functions of the network node and user equipment described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

[0107] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0108] Some embodiments are directed to masking of ROs.

[0109] Referring to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 3 a schematic diagram of a communication system 10, according to an embodiment, such as a 3 GPP-type cellular network that may support standards such as LTE and / or NR (5G) and / or 6G, which comprises an access network 12, such as a radio access network, and a core network 14. The core network 14 includes one or more network nodes 15. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first user equipment (UE) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second UE 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of UEs 22a, 22b (collectively referred to as user equipments 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding network node 16. Note that although only two UEs 22 and three network nodes 16 are shown for convenience, the communication system may include many more UEs 22 and network nodes 16.

[0110] As one example, in certain embodiments, access network 12 may contain some access network nodes 16 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 16 support (or the same access network nodes 16 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, communication system 10 may support multiple generations of relatedcommunication standards (e.g., 4G, 5G and 6G 3GPP communication standards) and, as a result, may include an access network 12 and / or a core network 14 that supports multiple different standard generations or may include multiple access networks 12 and / or multiple core networks 14 with individual networks supporting different standards generations.

[0111] Also, it is contemplated that a UE 22 can be in simultaneous communication and / or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a UE 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, UE 22 can be in communication with an eNB for LTE / E-UTRAN, a gNB for NR / NG-RAN (i.e., being configured for multiradio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC) and / or Wi-Fi.

[0112] A network node 16 (eNB or gNB) is configured to include a configuration unit 24 which is configured to perform one or more network node 16 functions described herein, including functions related to masking of ROs. A user equipment 22 is configured to include an implementation unit 26 which is configured to perform one or more UE 22 functions described herein, including functions related to masking of ROs.

[0113] Example implementations, in accordance with an embodiment, of the UE 22 and network node 16 discussed in the preceding paragraphs will now be described with reference to FIG. 4.

[0114] The communication system 10 includes a network node 16 provided in a communication system 10 and including hardware 28 enabling it to communicate with the UE 22. The hardware 28 may include a communication interface 29 comprising a radio interface 30 for setting up and maintaining at least a wireless connection 32 with a UE 22 located in a coverage area 18 served by the network node 16. The radio interface 30 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The radio interface 30 includes an array of antennas 34 to radiate and receive signal(s) carrying electromagnetic waves.

[0115] In the embodiment shown, the hardware 28 of the network node 16 further includes processing circuitry 36. The processing circuitry 36 may include a processor 38 and a memory 40. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 36 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application SpecificIntegrated Circuitry) adapted to execute instructions. The processor 38 may be configured to access (e.g., write to and / or read from) the memory 40, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0116] Thus, the network node 16 further has software 42 stored internally in, for example, memory 40, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 42 may be executable by the processing circuitry 36. The processing circuitry 36 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by network node 16.

[0117] Processor 38 corresponds to one or more processors 38 for performing network node 16 functions described herein. The memory 40 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 42 may include instructions that, when executed by the processor 38 and / or processing circuitry 36, causes the processor 38 and / or processing circuitry 36 to perform the processes described herein with respect to network node 16. For example, processing circuitry 36 of the network node 16 may include configuration unit 24 which is configured to perform one or more network node 16 functions described herein, including functions related to masking of ROs.

[0118] The network node 16 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 16 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 16 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 40 or portions of memory 40 for different RATs) and some components may be reused (e.g., a same antenna may be shared by different RATs). The network node 16 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 16, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), Zigbee, Z-wave, LoRaWAN,Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 16.

[0119] In certain alternative embodiments, network node 16 may be capable of wireless communication but does not include separate radio front-end circuitry, instead, the processing circuitry 36 includes radio front-end circuitry and is connected to the antenna 34. Similarly, in some embodiments, all or some of the RF receivers, transmitters and / or transceivers are part of the radio interface 30. In still other embodiments, the communication interface 29 includes one or more ports or terminals, the radio interface 30, and the RF receiver, transmitter and / or transceiver, and the communication interface 31 communicates with baseband processing circuitry, which is part of a digital unit (not shown).

[0120] The antenna 34 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 34 may be coupled to the radio front-end circuitry in radio interface 30 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 34 is separate from the network node 16 and connectable to the network node 16 through one or more interfaces or ports.

[0121] Network node 15 can include one or more components described above with respect to network node 16, e.g., communication interface 29, radio interface 30, antenna 34, ports, processing circuitry 36, processor 38, memory 40 and software 42. These elements of network node 15 can be arranged such that network node 15 can perform various core network functions. Network node 15 can communicate wirelessly or via a wired connection with network nodes 16 via communication link 59.

[0122] The communication system 10 further includes the UE 22 already referred to. The UE 22 may have hardware 44 that may include a radio interface 46 configured to set up and maintain a wireless connection 32 with a network node 16 serving a coverage area 18 in which the UE 22 is currently located. The radio interface 46 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The radio interface 46 includes an array of antennas 48 to radiate and receive signal(s) carrying electromagnetic waves.

[0123] Communication functions of the radio interface 46 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, data communication, voice communication,multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0124] The hardware 44 of the UE 22 further includes processing circuitry 50. The processing circuitry 50 may include a processor 52 and memory 54. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 50 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 52 may be configured to access (e.g., write to and / or read from) memory 54, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0125] Thus, the UE 22 may further comprise software 56, which is stored in, for example, memory 54 at the UE 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the UE 22. The software 56 may be executable by the processing circuitry 50. The software 56 may include a client application 58. The client application 58 may be operable to provide a service to a human or non-human user via the UE 22.

[0126] The processing circuitry 50 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by UE 22. The processor 52 corresponds to one or more processors 52 for performing UE 22 functions described herein. The UE 22 includes memory 54 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 56 and / or the client application 58 may include instructions that, when executed by the processor 52 and / or processing circuitry 50, causesthe processor 52 and / or processing circuitry 50 to perform the processes described herein with respect to UE 22. For example, the processing circuitry 50 of the user equipment 22 may include implementation unit 26 which is configured to perform one or more UE 22 functions described herein, including functions related to masking of ROs.

[0127] In some embodiments, the inner workings of the network node 16 and UE 22 may be as shown in FIG. 4 and independently, the surrounding network topology may be that of FIG. 3.

[0128] The wireless connection 32 between the UE 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and / or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc. In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.

[0129] Although FIGS. 3 and 4 show various “units” such as configuration unit 24 and implementation unit 26 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

[0130] FIG. 5 is another example of a communication system 10 according to some embodiments. As used herein, the communication system 10 of FIG. 5 includes multiple access points (APs) 60 (with four example APs 60a, 60b, 60c, and 60d being depicted) and multiple wireless devices, referred to in the context of communication system 10 of FIG. 5 as stations (STAs) 62 (referred to individually as STA 62a, STA 62b, STA 62c, STA 62d, and STA 62e). STA 62a is served by AP 60a in a first basic service set (BSS) 64a. STA 62b and STA 62c are served by AP 60b in a second BSS, BSS 64b. STA 62d is served by AP 60c in a third BSS, BSS 64c. STA 62e is served by AP 60d in a fourth BSS, BSS 64d. Stations 62 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like, including UEs 22 that are shown and described with respect to FIGS. 3 and 4. In other words, in some embodiment, STA 62 is a UE 22. Further, stations 62 could, for example,correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0131] Each of STAs 62 may connect through a radio link to one of APs 60. For example, depending on location or channel conditions experienced by a given STA 62, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.

[0132] Each AP 60 may provide data connectivity to STAs 62 connected to a particular AP 60. As illustrated, APs 60 may be connected to a data network 66. In this way, APs 60 may also provide data connectivity between STAs 62 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like.

[0133] Accordingly, the radio link established between a given STA 62 and its serving AP 60 may be used for providing various kinds of services to STA 62, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 62 and / or on a device linked to STA 62. By way of example, FIG. 5 illustrates an application service platform 68 provided in data network 66. The application(s) executed on STA 62 and / or on one or more other devices linked to STA 62 may use the radio link for data communication with one or more other STA 62 and / or the application service platform 68, thereby enabling utilization of the corresponding service(s) at STA 62.

[0134] FIG. 6 is a flowchart of an example process in a network node 16 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 36 (including the configuration unit 24), processor 38, and / or radio interface 30. Network node 16 configured to configure the UE 22 with a bitmap indicating activation status of one or more Random Access Channel, RACH, Occasions, ROs (Block SI 00). Network node 16 configured to communicate with the UE 22 based on the bitmap (Block SI 02).

[0135] In some embodiments, each bit in the bitmap represents an interval, the interval being one or more of: a System Frame Number, SFN, / Physical RACH, PRACH, association period level; and a PRACH association pattern period level.In some embodiments, the bitmap is semi-dynamically configured in System Information, SI.

[0136] FIG. 7 is a flowchart of another example process in a network node 16 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 36 (including the configuration unit 24), processor 38, and / or radio interface 30. Network node 16 is configured to configure (Block S104) the UE with a bitmap indicating an activation status of each of a plurality of Random Access Channel, RACH, Occasions, ROs, as described herein. Network node 16 is configured to communicate (Block SI 06) with the UE 22 based on the bitmap, as described herein.

[0137] According to one or more embodiments, the bitmap comprises a plurality of bits, each of the plurality of bits corresponding to a respective interval; and each of the plurality of bits indicates an activation status of the one or more ROs of the plurality of ROs in the respective interval.

[0138] According to one or more embodiments, the interval comprises: one or more System Frame Numbers, SFNs; one or more Physical Random Access Channel, PRACH, association periods; one or more PRACH association pattern periods; or one or more Synchronization Signal Block, SSB, beams.

[0139] According to one or more embodiments, the plurality of bits in the bitmap map to an interval, the interval being at a System Frame Number, SFN, level; and the plurality of bits indicating activation statuses of the plurality of ROs in a plurality of SFNs.

[0140] According to one or more embodiments, a plurality of bits in the bitmap map to an interval, where the interval is at a Physical Random Access Channel, PRACH, association period level or at a PRACH association pattern period level; and the plurality of bits indicates activation statuses of the plurality of ROs in a plurality of PRACH association periods or a plurality of PRACH association pattern periods.

[0141] According to one or more embodiments, a plurality of bits in the bitmap map to an interval at a Synchronization Signal Block, SSB, level; and the plurality of bits indicate activation statuses of the plurality of ROs associated with a plurality of SSB beams.

[0142] According to one or more embodiments, the bitmap is configured to apply periodically to the plurality of ROs.

[0143] According to one or more embodiments, the bitmap is indicated in one or both of System Information, SI, and an SI update.According to one or more embodiments, the communicating with the UE 22 based on the bitmap comprises receiving Physical Random Access Channel, PRACH, signaling in a RACH resource selected from an RO of the one or more ROs of the plurality of ROs having an activation status as active.

[0144] According to one or more embodiments, the network node 16 is further configured to: transmit a first configuration for RACH resources, the first configuration being associated with first ROs; transmit a second configuration for RACH resources, the second configuration being associated with additional ROs; and the bitmap is configured to apply to the second configuration and not the first configuration.

[0145] According to one or more embodiments, masking related information for PRACH coordination is received from another network node, the masking related information indicating the bitmap.

[0146] According to one or more embodiments, the network node 16 is further configured to transmit masking related information for PRACH coordination to one or more other network nodes, the masking related information indicating the bitmap.

[0147] FIG. 8 is a flowchart of an example process in a user equipment 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of user equipment 22 such as by one or more of processing circuitry 50 (including the implementation unit 26), processor 52, and / or radio interface 46. UE 22 is configured to receive a bitmap indicating activation status of one or more Random Access Channel, RACH, Occasions, ROs (Block SI 08). UE 22 is configured to communicate with the network node 16 based on the bitmap (Block SI 10).

[0148] In some embodiments, each bit in the bitmap represents an interval, the interval being one or more of: a System Frame Number, SFN, / Physical RACH, PRACH, association period level; and a PRACH association pattern period level.

[0149] In some embodiments, the bitmap is semi-dynamically configured in System Information, SI.

[0150] FIG. 9 is a flowchart of another example process in a user equipment 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of user equipment 22 such as by one or more of processing circuitry 50 (including the implementation unit 26), processor 52, and / or radio interface 46. UE 22 is configured to receive (Block SI 12) a bitmap indicating an activation status of each of a plurality of Random Access Channel, RACH, Occasions,ROs, as described herein. UE 22 is configured to communicate (Block SI 14) with the network node 16 based on the bitmap, as described herein.

[0151] According to one or more embodiments, the bitmap comprises a plurality of bits, each of the plurality of bits corresponding to a respective interval; and each of the plurality of bits indicates an activation status of the one or more ROs of the plurality of ROs in the respective interval.

[0152] According to one or more embodiments, the interval comprises: one or more System Frame Numbers, SFNs; one or more Physical Random Access Channel, PRACH, association periods; one or more PRACH association pattern periods; or one or more Synchronization Signal Block, SSB, beams.

[0153] According to one or more embodiments, a plurality of bits in the bitmap map to an interval, the interval being at a System Frame Number, SFN, level; and the plurality of bits indicates activation statuses of the plurality of ROs in a plurality of SFNs.

[0154] According to one or more embodiments, a plurality of bits in the bitmap map to an interval, where the interval is at a Physical Random Access Channel, PRACH, association period level or at a PRACH association pattern period level; and the plurality of bits indicates activation statuses of the plurality of ROs in a plurality of PRACH association periods or a plurality of PRACH association pattern periods.

[0155] According to one or more embodiments, a plurality of bits in the bitmap map to an interval at a Synchronization Signal Block, SSB, level; and the plurality of bits indicate activation statuses of the plurality of ROs associated with a plurality of SSB beams.

[0156] According to one or more embodiments, the bitmap is configured to apply periodically to the plurality of ROs.

[0157] According to one or more embodiments, the bitmap is indicated in one or both of System Information, SI, and an SI update.

[0158] According to one or more embodiments, the communicating with the network node 16 based on the bitmap comprises transmitting Physical Random Access Channel, PRACH, signaling in a RACH resource selected from an RO of the one or more ROs of the plurality of ROs having an activation status as active.

[0159] According to one or more embodiments, the UE 22 is further configured to receive a first configuration for RACH resources, the first configuration being associated with first ROs; receive a second configuration for RACH resources, the second configuration being associated with additional ROs; and the bitmap is configured to apply to the second configuration and not the first configuration.In one or more embodiments, the bitmap indicates a plurality of activation statuses of a plurality of ROs.

[0160] For example, in some embodiments, the telecommunication system 10 includes one or more Open-RAN (ORAN) network nodes 16. An ORAN network node 16 is a node in the telecommunication system 10 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication system 10, including one or more network nodes 16 in the access network 12 and / or core network nodes 14.

[0161] Examples of an ORAN network node 16 include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 16 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 22a, 22b, 22c, and 22d (one or more of which may be generally referred to as UEs 22) to the core network 14 over one or more wireless connections.

[0162] FIG. 10 is a block diagram illustrating a virtualization environment 94 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions describedherein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 94 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 94 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

[0163] Applications 96 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 94 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0164] Hardware 98 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth.

[0165] Software may be executed by the processing circuitry to instantiate one or more virtualization layers 100 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 102a and 102b (one or more of which may be generally referred to as VMs 102), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 100 may present a virtual operating platform that appears like networking hardware to the VMs 102.

[0166] The VMs 102 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 100. Different embodiments of the instance of a virtual appliance 96 may be implemented on one or more of VMs 102, and the implementations may be made in different ways.

[0167] Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0168] In the context of NFV, a VM 102 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 102, and that part of hardware 98 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of theVMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 102 on top of the hardware 98 and corresponds to the application 96.

[0169] Hardware 98 may be implemented in a standalone network node with generic or specific components. Hardware 98 may implement some functions via virtualization. Alternatively, hardware 98 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 104, which, among others, oversees lifecycle management of applications 96. In some embodiments, hardware 98 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 106 which may alternatively be used for communication between hardware nodes and radio units.

[0170] Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for masking of ROs.

[0171] Example embodiments may be described in the context of SFN for explanatory purposes. These example embodiments can be extended to other interval definitions, such as PRACH association period level / PRACH association pattern period level / SSB beam index, etc.

[0172] In at least one embodiment, the mask bitmap contains maximum 16 bits, which corresponds to 16 SFNs. In an example, if the additional RO in one SFN is activated, the corresponding bit in bitmap is 1. Otherwise, the corresponding bit takes the value of 0, as shown in FIG. 11 (depicting additional ROs before applying mask) and FIG. 12 (depicting additional ROs after applying mask).

[0173] Two types of RACH configuration are included in FIG. 11, namely, RACH #2 and RACH #7. The NW (e.g., via network node 16) can deactivate the additional ROs in SFN 0 / 4 / 8 / 12 by using a bit map 0111,0111,0111,0111 and the bitmap is applied to the SFNs in a cyclic manner. Therefore, NW (e.g., via network node 16) gets 10ms sleeping opportunity every 40ms. Since the RO muting pattern is periodic, the bit map can beshorter, e.g., 0111, which takes only four bits that can be applied to the SFNs in a cyclic manner.

[0174] This approach can also provide ROs that are unevenly distributed, such as 1100,0100,1100,0100. This means the additional ROs in SFN2 / 3 / 4 / 6 / 7 / 10 / 11 / 12 / 14 / 15 are muted, as shown in FIG. 13 (depicting unevenly distributed additional ROs after applying mask). This bit map can further be simplified to 1100,0100, which takes only eight bits. Therefore, this method provides better flexibility than PRACH mask defined, e.g., in 3 GPP TS 38.321, because the mask index values must be predefined.

[0175] This bit map concept can also be applied to PRACH association period level or PRACH association pattern period level. An example on PRACH association period level is shown in In FIG. 14, NW (e.g., via network node 16) has two SSB beams, and each SSB is mapped to two additional ROs. In FIG. 15, the additional RO mask 1010 is applied. Each bit in bitmap represents one PRACH association period. The bit map can be further simplified to 10, which takes only two bits.

[0176] In another example, each bit of bitmap corresponds to an SSB beam. For example, a bitmap 01 means the additional ROs for SSBO are deactivated, as shown in FIG. 16. This method can provide additional ROs to specific SSB beams.

[0177] This bitmap should be provided from NW (e.g., via network node 16) in SI. When changing the bitmap, a SI update and notification may be needed.

[0178] A UE 22 acquires a configuration regarding a first set of RACH resources, and a configuration regarding a second set of RACH resources. The UE 22 further receives a PRACH mask that is applicable to the second set of RACH resources, wherein the PRACH mask is based on a bitmap, and wherein each bit of the bitmap is associated with a SFN and denotes the activation or deactivation status of the ROs associated with the second set of RACH resources within that SFN. The PRACH mask may be applied in a periodic fashion to the ROs in a SFN cycle. For example, assuming the PRACH mask is of length-4, and given by bits bO, bl, b2, b3. The bit bO denotes the activation or deactivation status of ROs associated with the second set of RACH resources in SFNs given by SFN0, SFN4, SFN8 and so on. Likewise, bit bl denotes the activation or deactivation status of ROs associated with the second set of RACH resources in SFNs given by SFN1, SFN5, SFN9 and so on.

[0179] The UE 22 determines the activated RACH resources from the second set of RACH resources based on the PRACH mask. The UE 22 transmits PRACH in a RACH resource selected the activated ROs associated with the second set of RACH resources.Upon RACH transmission, the UE 22 monitors for RAR in a PDCCH search space based on an RA-RNTI. In an embodiment, the UE 22 is aNES-capable UE that can transmit RACH according to first set and / or second set of RACH resources.

[0180] Signaling of masking related information via NW interfaces (e.g., via network node 16) for enhanced PRACH coordination

[0181] According to certain embodiments, masking related information is signaled via NW interfaces, e.g., for PRACH coordination among cells of one RAN node (e.g., network node 16) or among cells of different RAN nodes (e.g., network nodes 16).

[0182] Masking related information may comprise a mask bitmap applied to a PRACH configuration used in a cell. Masking related information may also comprise multiple mask bitmaps for multiple PRACH configurations of multiple cells. A certain mask bitmap may be applied / associated to one or more PRACH configurations.

[0183] In at least one embodiment, masking related information is sent from a first logical entity of a RAN node to a second logical entity of the RAN node. In an example, the first logical entity of the RAN node is a gNB-DU, and the second logical entity of the RAN node is a gNB-CU. In another example, the first logical entity of the RAN node is a gNB-CU, and the second logical entity of the RAN node is a gNB-DU. In both examples, the masking related information is sent over the Fl interface.

[0184] In at least one embodiment, masking related information is sent from a first RAN node to a second RAN node. For example, masking related information is sent from a first network node 16, where the PRACH configuration including the associated mask bitmap is decided and used (in a cell), to one or more second / neighboring network nodes.

[0185] Masking related information is exchanged via NW interfaces, e.g., for intra-node and inter-node coordination of masked PRACH configurations, where certain PRACH occasions / resources are inactive. Masking enables the reuse of the same PRACH configuration in neighboring cells without causing inter-cell interference or confusion on PRACH, provided that orthogonal masks are applied so that the active PRACH occasions / resources are separated, e.g., the mask bitmaps “10” and “01,” or the mask bitmaps “1010,” and “0101.”

[0186] A first logical entity of a first RAN node, e.g., gNB-DU 1, may decide the mask of a PRACH configuration (used in a first cell of the first RAN node) and send the mask to a second logical entity of the first RAN node, e.g., gNB-CU 1. The gNB-DU 1 may send the mask to gNB-CU 1 via GNB-DU CONFIGURATION UPDATE message, e.g., as part ofthe NR PRACH Configuration IE, in an appropriately enhanced version, or as part of the NR PRACH Configuration List IE, in an appropriately enhanced version.

[0187] The second logical entity of the first RAN node may then send the mask to a first logical entity of a second RAN node, e.g., gNB-CU 2. gNB-CU 1 may send the mask to gNB-CU 2 viaNG-RAN NODE CONFIGURATION UPDATE message.

[0188] The first logical entity of a second RAN node may then send the mask to a second logical entity of the second RAN node, e.g., gNB-DU 2. gNB-CU 2 may send the mask to gNB-DU 2 via GNB-CU CONFIGURATION UPDATE message, e g., included in the Neighbour NR Cells for SON List IE. gNB-DU 2 can consider the masking related information when determining the PRACH configuration including a mask for one or more cells of the second RAN node, which may be neighboring cells of the first cell of the first RAN node.

[0189] Examples

[0190] Example Al . A method implemented in a user equipment (UE 22) that is configured to communicate with a network node 16, the method comprising:

[0191] receiving a bitmap indicating activation status of one or more Random Access Channel, RACH, Occasion, ROs; and

[0192] communicating with the network node 16 based on the bitmap.

[0193] Example A2. The method of Example Al , wherein each bit in the bitmap represents an interval, the interval being one or more of:

[0194] a System Frame Number, SFN, / Physical RACH, PRACH, association period level; and

[0195] a PRACH association pattern period level.

[0196] Example A3. The method of Example Al, wherein the bitmap is semi-dynamically configured in System Information, SI.

[0197] Example BL A user equipment (UE 22) configured to communicate with a network node 16, the UE 22 configured to, and / or comprising a radio interface 46 and / or processing circuitry 50 configured to:

[0198] receive a bitmap indicating activation status of one or more Random Access Channel, RACH, Occasion, ROs; and

[0199] communicate with the network node 16 based on the bitmap.

[0200] Example B2. The UE 22 of Example Bl, wherein each bit in the bitmap represents an interval, the interval being one or more of:a System Frame Number, SFN, / Physical RACH, PRACH, association period level; and

[0201] a PRACH association patern period level.

[0202] Example B3. The UE 22 of Example Bl, wherein the bitmap is semi-dynamically configured in System Information, SI.

[0203] Example Cl. A method implemented in a network node 16 that is configured to communicate with a user equipment (UE 22) the method comprising:

[0204] configuring the UE 22 with a bitmap indicating activation status of one or more Random Access Channel, RACH, Occasion, ROs; and

[0205] communicating with the UE 22 based on the bitmap.

[0206] Example C2. The method of Example Cl, wherein each bit in the bitmap represents an interval, the interval being one or more of:

[0207] a System Frame Number, SFN, / Physical RACH, PRACH, association period level; and

[0208] a PRACH association patern period level.

[0209] Example C3. The method of Example Cl, wherein the bitmap is semi-dynamically configured in System Information, SI.

[0210] Example DI . A network node 16 configured to communicate with a user equipment (UE 22), the network node 16 configured to, and / or comprising a radio interface 30 and / or comprising processing circuitry 36 configured to:

[0211] configure the UE 22 with a bitmap indicating activation status of one or more Random Access Channel, RACH, Occasion, ROs; and

[0212] communicate with the UE 22 based on the bitmap.

[0213] Example D2. The network node 16 of Example DI, wherein each bit in the bitmap represents an interval, the interval being one or more of:

[0214] a System Frame Number, SFN, / Physical RACH, PRACH, association period level; and

[0215] a PRACH association patern period level.

[0216] Example D3. The network node 16 of Example DI, wherein the bitmap is semi-dynamically configured in System Information, SI.

[0217] As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and / or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, anentirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and / or functionality described herein may be performed by, and / or associated to, a corresponding module, which may be implemented in software and / or firmware and / or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0218] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0219] These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function / act specified in the flowchart and / or block diagram block or blocks.

[0220] The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0221] It is to be understood that the functions / acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown insuccession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality / acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0222] Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0223] Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and / or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

[0224] Abbreviations that may be used in the preceding description include:

[0225] Abbreviation Explanation

[0226] NES Network Energy Saving

[0227] PRACH Physical Random- Access Channel

[0228] RACH Random Access Channel

[0229] RAR Random Access Response

[0230] RA-RNTI Random Access Radio Network Temporary Identifier RO RACH OccasionIt will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.

Claims

33CLAIMS1. A method implemented in a user equipment, UE (22), that is configured to communicate with a network node (16), the method comprising:receiving (S112)a bitmap indicating an activation status of each of a plurality of Random Access Channel, RACH, Occasions, ROs; andcommunicating (S 114) with the network node (16) based on the bitmap.

2. The method of Claim 1, wherein the bitmap comprises a plurality of bits, each of the plurality of bits corresponding to a respective interval; andeach of the plurality of bits indicates an activation status of the one or more ROs of the plurality of ROs in the respective interval.

3. The method of Claim 2, wherein the interval comprises:one or more System Frame Numbers, SFNs;one or more Physical Random Access Channel, PRACH, association periods; one or more PRACH association pattern periods; orone or more Synchronization Signal Block, SSB, beams.

4. The method of Claim 1, wherein a plurality of bits in the bitmap map to an interval, the interval being at a System Frame Number, SFN, level; andthe plurality of bits indicating activation statuses of the plurality of ROs in a plurality of SFNs.

5. The method of Claim 1, wherein a plurality of bits in the bitmap map to an interval, the interval being at a Physical Random Access Channel, PRACH, association period level or at a PRACH association pattern period level; andthe plurality of bits indicating activation statuses of the plurality of ROs in a plurality of PRACH association periods or a plurality of PRACH association pattern periods.

6. The method of Claim 1, wherein a plurality of bits in the bitmap map to an interval at a Synchronization Signal Block, SSB, level; and34the plurality of bits indicating activation statuses of the plurality of ROs associated with a plurality of SSB beams.

7. The method of any one of Claims 4-6, wherein the bitmap is configured to apply periodically to the plurality of ROs.

8. The method of any one of Claims 1-7, wherein the bitmap is indicated in one or both of System Information, SI, and an SI update.

9. The method of any one of Claims 1-8, wherein the communicating with the network node (16) based on the bitmap comprises transmitting Physical Random Access Channel, PRACH, signaling in a RACH resource selected from an RO of the one or more ROs of the plurality of ROs having an activation status as active.

10. The method of any one of Claims 1-9, further comprising:receiving a first configuration for RACH resources, the first configuration being associated with first ROs;receiving a second configuration for RACH resources, the second configuration being associated with additional ROs; andthe bitmap is configured to apply to the second configuration and not the first configuration.

11. A user equipment, UE (22), that is configured to communicate with a network node (16), the UE (22) configured to:receive a bitmap indicating an activation status of each of a plurality of Random Access Channel, RACH, Occasions, ROs; andcommunicate with the network node (16) based on the bitmap.

12. The UE (22) of Claim 11, wherein the bitmap comprises a plurality of bits, each of the plurality of bits corresponding to a respective interval; andeach of the plurality of bits indicates an activation status of the one or more ROs of the plurality of ROs in the respective interval.

13. The UE (22) of Claim 12, wherein the interval comprises:one or more System Frame Numbers, SFNs;one or more Physical Random Access Channel, PRACH, association periods; one or more PRACH association pattern periods; orone or more Synchronization Signal Block, SSB, beams.

14. The UE (22) of Claim 11, wherein a plurality of bits in the bitmap map to an interval, the interval being at a System Frame Number, SFN, level; andthe plurality of bits indicating activation statuses of the plurality of ROs in a plurality of SFNs.

15. The UE (22) of Claim 11, wherein a plurality of bits in the bitmap map to an interval, the interval being at a Physical Random Access Channel, PRACH, association period level or at a PRACH association pattern period level; andthe plurality of bits indicating activation statuses of the plurality of ROs in a plurality of PRACH association periods or a plurality of PRACH association pattern periods.

16. The UE (22) of Claim 11, wherein a plurality of bits in the bitmap map to an interval at a Synchronization Signal Block, SSB, level; andthe plurality of bits indicating activation statuses of the plurality of ROs associated with a plurality of SSB beams.

17. The UE (22) of any one of Claims 11-16, wherein the bitmap is configured to apply periodically to the plurality of ROs.

18. The UE (22) of any one of Claims 11-17, wherein the bitmap is indicated in one or both of System Information, SI, and an SI update.

19. The UE (22) of any one of Claims 11-18, wherein the communicating with the network node (16) based on the bitmap comprises transmitting Physical Random Access Channel, PRACH, signaling in a RACH resource selected from an RO of the one or more ROs of the plurality of ROs having an activation status as active.

20. The UE (22) of any one of Claims 11-19, further comprising:receiving a first configuration for RACH resources, the first configuration being associated with first ROs;receiving a second configuration for RACH resources, the second configuration being associated with additional ROs; andthe bitmap is configured to apply to the second configuration and not the first configuration.

21. A method implemented in a network node (16) that is configured to communicate with a user equipment, UE (22), the method comprising:configuring (SI 04) the UE (22) with a bitmap indicating an activation status of each of a plurality of Random Access Channel, RACH, Occasions, ROs; and communicating (SI 06) with the UE (22) based on the bitmap.

22. The method of Claim 21, wherein the bitmap comprises a plurality of bits, each of the plurality of bits corresponding to a respective interval; andeach of the plurality of bits indicates an activation status of the one or more ROs of the plurality of ROs in the respective interval.

23. The method of Claim 22, wherein the interval comprises:one or more System Frame Numbers, SFNs;one or more Physical Random Access Channel, PRACH, association periods; one or more PRACH association pattern periods; orone or more Synchronization Signal Block, SSB, beams.

24. The method of Claim 21, wherein the plurality of bits in the bitmap map to an interval, the interval being at a System Frame Number, SFN, level; andthe plurality of bits indicating activation statuses of the plurality of ROs in the plurality of SFNs.

25. The method of Claim 21, wherein a plurality of bits in the bitmap map to an interval, the interval being at a Physical Random Access Channel, PRACH, association period level or at a PRACH association pattern period level; and37the plurality of bits indicating activation statuses of the plurality of ROs in a plurality of PRACH association periods or a plurality of PRACH association pattern periods.

26. The method of Claim 21, wherein a plurality of bits in the bitmap map to an interval at a Synchronization Signal Block, SSB, level; andthe plurality of bits indicating activation statuses of the plurality of ROs associated with a plurality of SSB beams.

27. The method of any one of Claims 24-26, wherein the bitmap is configured to apply periodically to the plurality of ROs.

28. The method of any one of Claims 21-27, wherein the bitmap is indicated in one or both of System Information, SI, and an SI update.

29. The method of any one of Claims 21-28, wherein the communicating with the UE (22) based on the bitmap comprises receiving Physical Random Access Channel, PRACH, signaling in a RACH resource selected from an RO of the one or more ROs of the plurality of ROs having an activation status as active.

30. The method of any one of Claims 21-29, further comprising: transmitting a first configuration for RACH resources, the first configuration being associated with first ROs;transmitting a second configuration for RACH resources, the second configuration being associated with additional ROs; andthe bitmap is configured to apply to the second configuration and not the first configuration.

31. The method of any one of Claims 21-30, wherein masking related information for PRACH coordination is received from another network node, the masking related information indicating the bitmap.3832. The method of any one of Claims 21-31, further comprising transmitting masking related information for PRACH coordination to one or more other network nodes (16), the masking related information indicating the bitmap.

33. A network node (16) that is configured to communicate with a user equipment, UE (22), the network node (16) configured to:configure the UE (22) with a bitmap indicating an activation status of each of a plurality of Random Access Channel, RACH, Occasions, ROs; andcommunicate with the UE (22) based on the bitmap.

34. The network node (16) of Claim 33, wherein the bitmap comprises a plurality of bits, each of the plurality of bits corresponding to a respective interval; and each of the plurality of bits indicates an activation status of the one or more ROs of the plurality of ROs in the respective interval.

35. The network node (22) of Claim 34, wherein the interval comprises: one or more System Frame Numbers, SFNs;one or more Physical Random Access Channel, PRACH, association periods; one or more PRACH association pattern periods; orone or more Synchronization Signal Block, SSB, beams.

36. The network node (16) of Claim 33, wherein the plurality of bits in the bitmap map to an interval, the interval being at a System Frame Number, SFN, level; and the plurality of bits indicating activation statuses of the plurality of ROs in the plurality of SFNs.

37. The network node (16) of Claim 33, wherein a plurality of bits in the bitmap map to an interval, the interval being at a Physical Random Access Channel, PRACH, association period level or at a PRACH association pattern period level; and the plurality of bits indicating activation statuses of the plurality of ROs in a plurality of PRACH association periods or a plurality of PRACH association pattern periods.3938. The network node (16) of Claim 33, wherein a plurality of bits in the bitmap map to an interval at a Synchronization Signal Block, SSB, level; andthe plurality of bits indicating activation statuses of the plurality of ROs associated with a plurality of SSB beams.

39. The network node (16) of any one of Claims 36-38, wherein the bitmap is configured to apply periodically to the plurality of ROs.

40. The network node (16) of any one of Claims 33-39, wherein the bitmap is indicated in one or both of System Information, SI, and an SI update.

41. The network node (16) of any one of Claims 33-40, wherein the communicating with the UE (22) based on the bitmap comprises receiving Physical Random Access Channel, PRACH, signaling in a RACH resource selected from an RO of the one or more ROs of the plurality of ROs having an activation status as active.

42. The network node (16) of any one of Claims 33-41, wherein the network node (16) is further configured to:transmit a first configuration for RACH resources, the first configuration being associated with first ROs;transmit a second configuration for RACH resources, the second configuration being associated with additional ROs; andthe bitmap is configured to apply to the second configuration and not the first configuration.

43. The network node (16) of any one of Claims 33-42, wherein masking related information for PRACH coordination is received from another network node (16), the masking related information indicating the bitmap.

44. The network node (16) of any one of Claims 33-43, wherein the network node (16) is further configured to transmit masking related information for PRACH coordination to one or more other network nodes, the masking related information indicating the bitmap.

Images