Additional random access channel (RACH) occassion (RO) configurations

Abstract

A method, system and apparatus are disclosed. 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 configuration for at least one additional random access channel, RACH, occasion, RO, the at least one additional RO being associated with an RO index and overlapping at least one first RO, the at least one first RO being configured by a first configuration; associate the at least one additional RO with a different RO index; and perform at least one action based on the configuration and the different RO index.

Description

[0001] ADDITIONAL RANDOM ACCESS CHANNEL (RACH) OCCASSION (RO) CONFIGURATIONS

[0002] FIELD

[0003] The present disclosure relates to wireless communications, and in particular, to random access channel, RACH, occasion, RO, configurations.

[0004] BACKGROUND

[0005] 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.

[0006] Network (NW) energy consumption

[0007] NW power consumption in NR has increased significantly compared to LTE, partly due to higher BW and massive number of antennas. This is still evident even if there are no UEs present in a cell. Although there is no UL or DL transmission between a specific UE and a network node, in idle mode, the network node still needs to periodically transmit signals, such as SSB and broadcast system information, e.g., SIB1. For example, SSBs can be configured with 20ms periodicity, and SIB1 can be configured with 160ms periodicity. In addition, the network node also needs to periodically monitor the preambles from a UE to cope with random access, which implies that the receiver components of the network node need to be turned on periodically, e.g., every 10 ms 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.

[0008] Random Access Channel (RACH) Configuration

[0009] 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. RACH resources are configured via higher layers (e.g., system information) and typical RACH resources may occur periodically as shown in FIG. 1, 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.

[0010] RA-RNTI

[0011] The RA-RNTI is associated with the PRACH occasion in which the Random Access Preamble is transmitted or the RA-RNTI associated with the last valid PRACH occasion in the set of PRACH occasions (as specified in TS 38.213) for Msgl repetition, is computed as:

[0012] RA — RNTI = 1 + s_id + 14 x f_id + 14 x 80 x t_id + 14 x 80 x 8 x ul_carrier_id where s_id is the index of the first OFDM symbol of the PRACH occasion (0 < s_id < 14), t_id is the index of the first slot of the PRACH occasion in a system frame (0 < t_id < 80), where the subcarrier spacing to determine t_id is based on the value of p specified in clause 5.3.2 in 3GPP TS 38.211 [8] for p = {0, 1, 2, 3}, and for p = {5, 6}, t_id is the index of the 120 kHz slot in a system frame that contains the PRACH occasion (0 < t_id < 80), f id is the index of the PRACH occasion in the frequency domain (0 < f id < 8), and ul_carrier_id is the UL carrier used for Random Access Preamble transmission (0 for NUL carrier, and 1 for SUL carrier). The range of all RNTI can be found in 3GPP TS38.321 V18.1.0 - 7.1, as shown in FIG. 2 is a Table 7.1-1 of RNTI values.

[0013] Legacy RACH occasions

[0014] Up until Rel-18 versions of the 3GPP specification (see 3GPP 38.331 V18.0.0), PRACH resources semi-statically configured in SIB1 may be updated in by the NW via the System Information Update procedure. If the RACH configuration info in the SIB1 changes, an SI update will be signalled via the paging DCI short message mechanism, in all POs 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.

[0015] Additional RACH occasions

[0016] In 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 exemplified in FIG. 3 wherein a baseline configuration is provided in SIB1 according to legacy means (top subfigure). Additional ROs are also configured in SIB1 (mid subfigure of FIG. 3) but only intended to be used when indicated by the NW. Bottom subfigure of FIG. 3 shows the sum of available ROs for the UE where the additional ROs are also activated.In RAN1_117 and RAN1_119, the following agreements have been made corresponding to PRACH adaptation:

[0017] Agreement

[0018] For adaptation of PRACH in time-domain, support at least the following case(s) • Case 1 : no time-domain overlap between the additional PRACH resources for NES-capable UEs and the PRACH resources for legacy UEs

[0019] • Case 2: time-domain overlap but no overlap in frequency domain between the additional PRACH resources for NES-capable UEs and the PRACH resources for legacy UEs

[0020] • Case 3: additional PRACH resources for NES-capable UEs and legacy PRACH resources overlap neither in time nor frequency domains

[0021] • FFS: whether additional conditions are needed to support the above cases • FFS: Additional case whether full / partial overlap in both time and frequency is allowed

[0022] • Above does not preclude discussion for the case where the configuration for additional PRACH resources contains legacy PRACH resources Agreement

[0023] At least msg 1 -Frequency Start can be configured separately for the additional PRACH resources at least for 4-step RACH.

[0024] SUMMARY FIG. 4 is a diagram of case 2 where there is time-domain overlap but no overlap in frequency between the additional PRACH resources for NES-capable UEs and the PRACH resources for legacy UEs.

[0025] If there is overlapping between the additional PRACH resources for NES-capable UEs and the PRACH resources for legacy UEs in time domain but no overlap in frequency domain as shown in FIG. 4, the Applicant has appreciated that there could be RA-RNTI ambiguity issue if legacy UE utilizes legacy RO 0 and NES-capable UE utilizes additional RO 0. This is because when the UE calculates RA-RNTI using the equation above, all parameters for that equation between the legacy UE and NES-capable UE could be same. Then there is contention between legacy UE and NES-capable UE, which may impact the RACH latency of legacy UE since the RACH configuration for legacy UE may be sparse.Some embodiments advantageously provide methods, systems, and apparatuses for random access channel, RACH, occasion, RO, configurations.

[0026] One or more embodiments described herein may solve one or more problems with existing systems and / or 3GPP specifications. That is, to solve the RA-RNTI ambiguity between the legacy UE and NES -capable UE, one or more embodiments deactivates or changes the msgl-FDM index of the ROs of the second set of RACH resources (additional ROs) which overlaps with ROs of the first set of RACH resources and generates the same RA-RNTI, if these overlapped ROs are corresponding to the same SSB beam. In one or more embodiments for those additional ROs which are overlapped with ROs of the first set of RACH resources but generate different RA-RNTIs, or correspond to different SSB beams, NW (e.g., network node) keeps them activated.

[0027] 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 configuration for at least one additional random access channel, RACH, occasion, RO, is received where the at least one additional RO is associated with an RO index and overlaps at least one first RO, and where the at least one first RO is configured by a first configuration. The at least one additional RO is associated with a different RO index. At least one action is performed based on the configuration and the different RO index.

[0028] According to one or more embodiments of this aspect, the associating of the at least one additional RO with a different RO index comprises: associating the at least one additional RO with a different RO index based on the additional RO overlapping with the at least one first RO.

[0029] According to one or more embodiments of this aspect, the associating of the at least one additional RO with a different RO index based on the additional RO overlapping with the at least one first RO comprises: associating the at least one additional RO with a different RO index based on the additional RO overlapping with the at least one first RO in a time domain but not in a frequency domain.

[0030] According to one or more embodiments of this aspect, the associating of the at least one additional RO with a different RO index comprises: changing the RO index of the at least one additional RO to the different RO index.

[0031] According to one or more embodiments of this aspect, the changing of the RO index occurs based on the at least one additional RO and the at least first RO being associated with a same Synchronization Signal Block, SSB, beam.According to one or more embodiments of this aspect, the performing of the at least one action based on the configuration and the different RO index comprises calculating a Random Access Network Temporary Identifier, RA-RNTI, associated with the at least one additional RO based on the different RO index.

[0032] According to one or more embodiments of this aspect, the at least one additional RO: at least partially overlaps in the time domain with the at least one first RO; and does not overlap in the frequency domain with the at least one first RO.

[0033] According to one or more embodiments of this aspect, prior to associating the at least one additional RO with the different RO index, the at least one additional RO and the at least one first RO correspond to a same RO index.

[0034] According to one or more embodiments of this aspect, in response to the at least one additional RO overlapping the at least one first RO in a time domain, an RO index is determined that is not occupied; and the different RO index corresponds to the RO index that is not occupied.

[0035] According to one or more embodiments of this aspect, the UE is a Network Energy Savings, NES, UE.

[0036] According to one or more embodiments of this aspect, the at least one additional RO is available.

[0037] 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 configuration for at least one additional random access channel, RACH, occasion, RO, where the at least one additional RO is associated with an RO index and overlapping at least one first RO, and the at least one first RO is configured by a first configuration. The UE is further configured to associate the at least one additional RO with a different RO index; and perform at least one action based on the configuration and the different RO index.

[0038] According to one or more embodiments of this aspect, the associating of the at least one additional RO with a different RO index comprises: associating the at least one additional RO with a different RO index based on the additional RO overlapping with the at least one first RO.

[0039] According to one or more embodiments of this aspect, the associating of the at least one additional RO with a different RO index based on the additional RO overlapping with the at least one first RO comprises: associating the at least one additional RO with adifferent RO index based on the additional RO overlapping with the at least one first RO in a time domain but not in a frequency domain.

[0040] According to one or more embodiments of this aspect, the associating of the at least one additional RO with a different RO index comprises: changing the RO index of the at least one additional RO to the different RO index.

[0041] According to one or more embodiments of this aspect, the changing of the RO index occurs based on the at least one additional RO and the at least first RO being associated with a same Synchronization Signal Block, SSB, beam.

[0042] According to one or more embodiments of this aspect, the performing of the at least one action based on the configuration and the different RO index comprises calculating a Random Access Network Temporary Identifier, RA-RNTI, associated with the at least one additional RO based on the different RO index.

[0043] According to one or more embodiments of this aspect, the at least one additional RO: at least partially overlaps in the time domain with the at least one first RO; and does not overlap in the frequency domain with the at least one first RO.

[0044] According to one or more embodiments of this aspect, prior to associating the at least one additional RO with the different RO index, the at least one additional RO and the at least one first RO correspond to a same RO index.

[0045] According to one or more embodiments of this aspect, the UE is further configured to, in response to the at least one additional RO overlapping the at least one first RO in a time domain, determine an RO index that is not occupied; and the different RO index corresponds to the RO index that is not occupied.

[0046] According to one or more embodiments of this aspect, the UE is a Network Energy Savings, NES, UE.

[0047] According to one or more embodiments of this aspect, the at least one additional RO is available.

[0048] 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. A configuration for at least one additional random access channel, RACH, occasion, RO, is transmitted where the at least one additional RO is associated with an RO index and overlaps at least one first RO, and where the at least one first RO is configured by a first configuration. The at least one additional RO is associated with a different RO index.

[0049] According to one or more embodiments of this aspect, at least one network node action is performed based on the configuration and the different RO index.According to one or more embodiments of this aspect, the associating of the at least one additional RO with a different RO index comprises: changing the RO index of the at least one additional RO to the different RO index.

[0050] According to one or more embodiments of this aspect, the changing of the RO index occurs based on the at least one additional RO and the at least one first RO being associated with a same Synchronization Signal Block, SSB, beam.

[0051] According to one or more embodiments of this aspect, a Random Access Network Temporary Identifier, RA-RNTI, associated with the at least one additional RO is calculated based on the different RO index.

[0052] According to one or more embodiments of this aspect, the at least one additional RO: at least partially overlaps in the time domain with the at least one first RO; and does not overlap in the frequency domain with the at least one first RO.

[0053] According to one or more embodiments of this aspect, prior to associating the at least one additional RO with the different RO index, the at least one additional RO and the at least one first RO correspond to a same RO index.

[0054] According to one or more embodiments of this aspect, in response to the at least one additional RO overlapping the at least one first RO in a time domain, determining an RO index is determined that to not be occupied. The different RO index corresponds to the RO index that is not occupied.

[0055] According to one or more embodiments of this aspect, the UE is a Network Energy Savings, NES, UE.

[0056] According to one or more embodiments of this aspect, the additional RO is available.

[0057] According to one or more embodiments of this aspect, the associating of the additional RO with a different RO index is based on the additional RO overlapping with the at least one first RO that is configured by the first configuration.

[0058] 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: transmit a configuration for at least one additional random access channel, RACH, occasion, RO, where the at least one additional RO is associated with an RO index and overlapping at least one first RO, and where the at least one first RO is configured by a first configuration. The network node is further configured to associate the at least one additional RO with a different RO index.According to one or more embodiments of this aspect, the network node is further configured to perform at least one network node action based on the configuration and the different RO index.

[0059] According to one or more embodiments of this aspect, the associating of the at least one additional RO with a different RO index comprises: changing the RO index of the at least one additional RO to the different RO index.

[0060] According to one or more embodiments of this aspect, the changing of the RO index occurs based on the at least one additional RO and the at least one first RO being associated with a same Synchronization Signal Block, SSB, beam.

[0061] According to one or more embodiments of this aspect, the network node is further configured to calculate a Random Access Network Temporary Identifier, RA-RNTI, associated with the at least one additional RO based on the different RO index.

[0062] According to one or more embodiments of this aspect, the at least one additional RO: at least partially overlaps in the time domain with the at least one first RO; and does not overlap in the frequency domain with the at least one first RO.

[0063] According to one or more embodiments of this aspect, prior to associating the at least one additional RO with the different RO index, the at least one additional RO and the at least one first RO correspond to a same RO index.

[0064] According to one or more embodiments of this aspect, the network node is further configured to, in response to the at least one additional RO overlapping the at least one first RO in a time domain, determine an RO index that is not occupied; and the different RO index corresponds to the RO index that is not occupied.

[0065] According to one or more embodiments of this aspect, the UE is a Network Energy Savings, NES, UE.

[0066] According to one or more embodiments of this aspect, the additional RO is available.

[0067] According to one or more embodiments of this aspect, the associating of the additional RO with a different RO index is based on the additional RO overlapping with the at least one first RO that is configured by the first configuration.

[0068] BRIEF DESCRIPTION OF THE DRAWINGS

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

[0070] FIG. 1 is a diagram of uplink resources for random access such as one RACH occasion in subframe #4 of each radio frame;

[0071] FIG. 2 is a diagram of a table of RNTI values;

[0072] FIG. 3 is a diagram of a legacy RO configuration and an additional RO configuration;

[0073] FIG. 4 is a diagram of time-domain overlap between the additional PRACH resources for NES-capable UEs and the PRACH resources for legacy UEs;

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

[0075] FIG. 6 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;

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

[0077] FIG. 8 is a flowchart of an example process in a network node according to some embodiments of the present disclosure;

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

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

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

[0081] FIG. 12 is a diagram of an example of RO configurations according to some embodiments of the present disclosure;

[0082] FIG. 13 is a diagram of another example of RO configurations according to some embodiments of the present disclosure;

[0083] FIG. 14 is a diagram of another example of RO configurations according to some embodiments of the present disclosure;

[0084] FIG. 15 is a diagram of another example of RO configurations according to some embodiments of the present disclosure; and

[0085] FIG. 16 is a diagram of another example of RO configurations according to some embodiments of the present disclosure.DETAILED DESCRIPTION

[0086] Due to existing 3GPP specifications, if there are 2 ROs overlapped in time domain, the RA-RNTI corresponding to these 2 ROs are the same. When UEs search for RAR after having transmitted a PRACH preambles, it is possible that aNES-capable UE decodes a RA-RNTI scrambled PDCCH in Type 1 CSS set successfully although the PDCCH is intended for another UE 22 such as legacy UE, and vice versa. This may confuse UEs, e.g., a UE may detect multiple PDCCH corresponding to its RA-RNTI in the RAR window. In one case, the UE may not find the RAPID, matching its preamble in the wrong RAR resource and recognize a failure in current RACH attempt. However, its own PDCCH schedules a matching RAPID. In another case, the UE finds a matching RAPID addressed by a wrong PDCCH and continues to proceed RAR steps although its RACH attempt has failed already at the first contention of preambles with other UEs.

[0087] To solve the issues above, one or more embodiments provide for deactivating the ROs of the second set which overlaps with ROs of the first set and generating the same RA-RNTI with ROs of the first set, if these overlapped ROs are corresponding to the same SSB beam.

[0088] Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to random access channel, RACH, occasion, RO, configurations.

[0089] 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.

[0090] 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 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.

[0091] 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.

[0092] 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.

[0093] 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.

[0094] 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), evolved Node B (eNB or eNodeB), Node B, multistandard 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.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.

[0095] 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).

[0096] 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.

[0097] 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 equipments and / 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.

[0098] 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 artto 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.

[0099] Some embodiments are directed to random access channel, RACH, occasion, RO, configurations.

[0100] Referring to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 5 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.

[0101] As one example, in certain embodiments, access network 12 may contain some access network nodes 16 that support 3 GPP 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 related communication 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.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.

[0102] 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 as described herein such as with respect to, for example, random access channel, RACH, occasion, RO, configurations. A user equipment 22 is configured to include a RO unit 26 which is configured to perform one or more UE 22 functions as described herein such as with respect to, for example, random access channel, RACH, occasion, RO, configurations.

[0103] 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. 6.

[0104] 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.

[0105] 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 Specific Integrated 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).

[0106] 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.

[0107] 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 as described herein.

[0108] 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.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).

[0109] 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.

[0110] 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.

[0111] 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.

[0112] 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 anycombination 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.

[0113] 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).

[0114] 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.

[0115] 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, causes the 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 22may include RO unit 26 which is configured to perform one or more UE 22 functions as described herein.

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

[0117] 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.

[0118] Although FIGS. 5 and 6 show various “units” such as configuration unit 24 and RO 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.

[0119] FIG. 7 is another example of a communication system 10 according to some embodiments. As used herein, the communication system 10 of FIG. 7 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. 3 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 60b and STA 60c 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. 5 and 6. 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.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.

[0120] 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.

[0121] 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. 7 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.

[0122] FIG. 8 is a flowchart of an example process in a network node 16 according to one or more 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 determine (Block SI 00) a configuration for one of at least one legacy random access channel, RACH, occasion, RO, and at least one additional RO, the at least one legacy RO overlapping the at least one additional RO, where the at least one additional RO being one of: deactivated and unavailable; available and associated with a different SSB beam than a synchronization signal block, SSB, beam associated with the at least one legacy RO; or available and associated with a different RO index, as described herein. Network node 16 is configured to communicate (Block SI 02) the configuration to the UE 22, as described herein.

[0123] According to one or more embodiments, the UE 22 is a non-network energy saving, NES, capable UE 22; and the configuration being for the at least one RO.According to one or more embodiments, the UE 22 is a non-network energy saving, NES, capable UE 22; and the configuration being for the at least one additional RO.

[0124] According to one or more embodiments, the overlap is in a time domain and not a frequency domain.

[0125] FIG. 9 is a flowchart of another example process in a network node 16 according to one or more 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 transmit (Block SI 04) a configuration for at least one additional random access channel, RACH, occasion, RO, where the at least one additional RO is associated with an RO index and overlaps at least one first RO, where the at least one first RO is configured by a first configuration, as described herein. Network node 16 is configured to associate (Block SI 06) the at least one additional RO with a different RO index, as described herein.

[0126] According to one or more embodiments, the network node 16 is further configured to perform at least one network node action based on the configuration and the different RO index.

[0127] According to one or more embodiments, the associating of the at least one additional RO with a different RO index comprises: changing the RO index of the at least one additional RO to the different RO index.

[0128] According to one or more embodiments, the changing of the RO index occurs based on the at least one additional RO and the at least one first RO being associated with a same Synchronization Signal Block, SSB, beam.

[0129] According to one or more embodiments, the network node 16 is further configured to calculate a Random Access Network Temporary Identifier, RA-RNTI, associated with the at least one additional RO based on the different RO index.

[0130] According to one or more embodiments, the at least one additional RO: at least partially overlaps in the time domain with the at least one first RO; and does not overlap in the frequency domain with the at least one first RO.

[0131] According to one or more embodiments, prior to associating the at least one additional RO with the different RO index, the at least one additional RO and the at least one first RO correspond to a same RO index.According to one or more embodiments, the network node 16 is further configured to, in response to the at least one additional RO overlapping at least one first RO in a time domain, determine an RO index that is not occupied; and the different RO index corresponds to the RO index that is not occupied.

[0132] According to one or more embodiments, the UE 22 is a Network Energy Savings, NES, UE 22.

[0133] According to one or more embodiments, the additional RO is available.

[0134] According to one or more embodiments, the associating of the at least one additional RO with a different RO index is based on the additional RO overlapping with the at least one first RO that is configured by the first configuration.

[0135] According to one or more embodiments, the associating of the at least one additional RO with a different RO index is based on the at least one additional RO overlapping with the at least one first RO in a time domain but not in a frequency domain.

[0136] FIG. 10 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 RO unit 26), processor 52, and / or radio interface 46. User equipment 22 is configured to receive (Block SI 08) a configuration for one of at least one legacy random access channel, RACH, occasion, RO, and at least one additional RO, where the at least one legacy RO overlap the at least one additional RO, and the at least one additional RO is one of: deactivated and unavailable; available and associated with a different SSB beam than a synchronization signal block, SSB, beam associated with the at least one legacy RO; or available and associated with a different RO index, as described herein. UE 22 is configured to perform (Block SI 10) at least one action based on the configuration, as described herein.

[0137] According to one or more embodiments, the UE 22 is a non-network energy saving, NES, capable UE 22; and the configuration being for the at least one RO.

[0138] According to one or more embodiments, the UE 22 is a non-network energy saving, NES, capable UE 22; and the configuration being for the at least one additional RO.

[0139] According to one or more embodiments, the overlap is in a time domain and not a frequency domain.

[0140] FIG. 11 is a flowchart of another example process in a user equipment 22 according to some embodiments of the present disclosure. One or more blocks describedherein may be performed by one or more elements of user equipment 22 such as by one or more of processing circuitry 50 (including the RO unit 26), processor 52, and / or radio interface 46. UE 22 is configured to receive (Block SI 12) a configuration for at least one additional random access channel, RACH, occasion, RO, where the at least one additional RO is associated with an RO index and overlaps at least one first RO, and where the at least one first RO is configured by a first configuration, as described herein. UE 22 is configured to associate (Block SI 14) the at least one additional RO with a different RO index, as described herein. UE 22 is configured to perform (Block SI 16) at least one action based on the configuration and the different RO index, as described herein.

[0141] According to one or more embodiments, the associating of the at least one additional RO with a different RO index comprises: associating the at least one additional RO with a different RO index based on the additional RO overlapping with the at least one first RO.

[0142] According to one or more embodiments, the associating of the at least one additional RO with a different RO index based on the additional RO overlapping with the at least one first RO comprises: associating the at least one additional RO with a different RO index based on the additional RO overlapping with the at least one first RO in a time domain but not in a frequency domain.

[0143] According to one or more embodiments, the associating of the at least one additional RO with a different RO index comprises: changing the RO index of the at least one additional RO to the different RO index.

[0144] According to one or more embodiments, the changing of the RO index occurs based on the at least one additional RO and the at least first RO being associated with a same Synchronization Signal Block, SSB, beam.

[0145] According to one or more embodiments, the performing of the at least one action based on the configuration and the different RO index comprises calculating a Random Access Network Temporary Identifier, RA-RNTI, associated with the at least one additional RO based on the different RO index.

[0146] According to one or more embodiments, the at least one additional RO: at least partially overlaps in the time domain with the at least one first RO; and does not overlap in the frequency domain with the at least one first RO.

[0147] According to one or more embodiments, prior to associating the at least one additional RO with the different RO index, the at least one additional RO and the at least one first RO correspond to a same RO index.According to one or more embodiments, the UE 22 is further configured to, in response to the at least one additional RO overlapping the at least one first RO in a time domain, determine an RO index that is not occupied; and the different RO index corresponds to the RO index that is not occupied.

[0148] According to one or more embodiments, the UE 22 is a Network Energy Savings, NES, UE 22.

[0149] According to one or more embodiments, the at least one additional RO is available.

[0150] 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 RO configurations.

[0151] Some embodiments provide for the configuration of RO configurations such as to, for example, avoid RA-RNTI ambiguity. One or more UE 22 functions described below may be performed by one or more of processing circuitry 50, processor 52, RO unit 26, radio interface 46, etc. One or more network node 16 functions may be performed by one or more of processing circuitry 36, processor 38, configuration unit 24, communication interface 29, etc.

[0152] One or more embodiments described herein relate to deactivating the ROs of the second set which overlaps with ROs of the first set and generating the same RA-RNTI with ROs of the first set, if these overlapped ROs are corresponding to the same SSB beam.

[0153] In one embodiment, the deactivation acts after SSB-RO mapping. In one example, if the ROs of the second set overlapping with ROs of the first set are corresponding to different SSB beams, the NES-capable UEs 22 and the first type UEs 22 can’t detect the opponent’s Type 1 CSS in their own beam. Therefore, the RA-RNTI ambiguity doesn’t impact RACH performance, as indicated by the dashed box in FIG. 12.

[0154] In another example, if the additional ROs overlapping with ROs of the first set are corresponding to the same SSB beam, the RA-RNTI ambiguity becomes an urgent issue that needs to be addressed. One solution is to deactivate the additional RO (RO of the second set of RACH resource), which is overlapped with the RO of the first set, as indicated by the bolded box in FIG. 12.

[0155] In one or more embodiments, the whole RACH slot in the bolded box of FIG. 13, is deactivated as shown in FIG. 13. In this case, NES-UEs 22 can use other additional ROfor SSB2 because additional RACH resource is much denser or use the RO of the first set for SSB2 in the bolded box frame.

[0156] In one or more embodiments, the deactivation acts before SSB-RO mapping. In one example, if the additional ROs overlapping with the RO of the first set are generating the same RA-RNTI, NW deactivates the additional RO, as shown in FIG. 14. Another alternative is to deactivate the whole RACH slot which contains the additional RO overlapped with the RO of the first set and generates the same RA-RNTI, as shown in FIG. 15.

[0157] In another embodiment, the overlapped additional RO is relabeled if there is index not occupied, e.g., the RO index is changed from 0 to 2, if the msgl-FDM equals to 2. According to the RA-RNTI equation, it results in a different value of RA-RNTI., as shown in FIG. 16.

[0158] Example

[0159] 1. NW (e.g., network node 16) provides a configuration regarding a first set of RACH resources to the first type of UEs 22 which are not NES-capable UEs 22, and a configuration regarding a second set of RACH resources to the second type of UE 22. The second type of UE 22 are NES-capable UE 22, and the RACH occasion (RO) of second set of RACH resources overlaps with the RACH occasion (RO) of first set of RACH resources (overlaps on both the first OFDM symbol and the first slot index of ROs) in time domain but not in frequency domain, the method comprising:

[0160] a. If the deactivation acts after SSB-RO mapping

[0161] ■ + for the RO of second set of RACH resources which are corresponding to different SSB beams from the RO of first set of RACH resources, NW keeps these ROs activated and NES-capable UEs 22 consider RACH resources are available.

[0162] ■ + for these overlapped RACH resources which are corresponding to the same SSB beams as the RO of the first set of RACH resources:

[0163] • + Regarding the RO of the second set of RACH resources which generate the same RA-RNTI as the RO of the first set of RACH resources (e.g., due to the same f id), NW deactivates the RO of the second set of RACH resources, and NES-capable UEs 22 consider these ROs are unavailable.• + NW deactivates all these ROs of the second set of RACH resources, and NES-capable UEs 22 consider these ROs are unavailable.

[0164] b. + If the deactivation acts before performing SSB-RO mapping,

[0165] ■ NW deactivates all these ROs of the second set of RACH resources, and NES-capable UEs consider these ROs are unavailable.

[0166] ■ NW deactivates the ROs of the second set of RACH resources which generate the same RA-RNTI as the ROs of the first set of RACH resources (e.g., due to the same f id), and NES-capable UEs 22 consider these ROs are unavailable.

[0167] c. + relabel the index of the RO of the second set of RACH resource if there is index not occupied.

[0168] One or more embodiments described herein provides one or more methods to avoid the RA-RNTI ambiguity issue between NES-capable UEs 22 and the first type of UEs 22 when there is overlapping between RO of the first and second set of RACH resources. This ensure the impact to RACH latency of the first type of UEs 22 is minimized when RACH adaptation is applied, because it alleviates the contention between the first type of UEs 22 and NES-capable UEs 22 in CBRA.

[0169] Additional Examples

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

[0171] receiving a configuration for one of at least one legacy random access channel, RACH, occasion, RO, and at least one additional RO, the at least one legacy RO overlapping the at least one additional RO, the at least one additional RO being one of:

[0172] deactivated and unavailable;

[0173] available and associated with a different synchronization signal block, SSB, beam than a SSB beam associated with the at least one legacy RO; or

[0174] available and associated with a different RO index; and

[0175] performing at least one action based on the configuration.

[0176] Example A2. The method of Example Al, wherein the UE 22 is a non-network energy saving, NES, capable UE 22; and

[0177] the configuration being for the at least one RO.

[0178] Example A3. The method of any one of Examples A1-A2, wherein the UE 22 is a non-network energy saving, NES, capable UE 22; andthe configuration being for the at least one additional RO.

[0179] Example A4. The method of any one of Examples Al -A3, wherein the overlap is in a time domain and not a frequency domain.

[0180] Example Bl. A user equipment, UE 22, configured to communicate with a network node, the UE 22 configured to, and / or comprising a radio interface 46 and / or processing circuitry 36 configured to

[0181] receive a configuration for one of at least one legacy random access channel, RACH, occasion, RO, and at least one additional RO, the at least one legacy RO overlapping the at least one additional RO, the at least one additional RO being one of:

[0182] deactivated and unavailable;

[0183] available and associated with a different synchronization signal block, SSB, beam than a SSB beam associated with the at least one legacy RO; or

[0184] available and associated with a different RO index; and

[0185] perform at least one action based on the configuration.

[0186] Example B2. The UE 22 of Example Bl, wherein the UE 22 is a non-network energy saving, NES, capable UE 22; and

[0187] the configuration being for the at least one RO.

[0188] Example B3. The UE of any one of Examples B1-B2, wherein the UE 22 is a non-network energy saving, NES, capable UE 22; and

[0189] the configuration being for the at least one additional RO.

[0190] Example B4. The UE of any one of Examples B1-B3, wherein the overlap is in a time domain and not a frequency domain.

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

[0192] determining a configuration for one of at least one legacy random access channel, RACH, occasion, RO, and at least one additional RO, the at least one legacy RO overlapping the at least one additional RO, the at least one additional RO being one of:

[0193] deactivated and unavailable;

[0194] available and associated with a different synchronization signal block, SSB, beam than a SSB beam associated with the at least one legacy RO; or

[0195] available and associated with a different RO index; and communicating the configuration to the UE 22.

[0196] Example C2. The method of Example Cl, wherein the UE 22 is a non-network energy saving, NES, capable UE 22; andthe configuration being for the at least one RO.

[0197] Example C3. The method of any one of Examples C1-C2, wherein the UE 22 is a non-network energy saving, NES, capable UE 22; and

[0198] the configuration being for the at least one additional RO.

[0199] Example C4. The method of any one of Examples C1-C3, wherein the overlap is in a time domain and not a frequency domain.

[0200] 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:

[0201] determine a configuration for one of at least one legacy random access channel, RACH, occasion, RO, and at least one additional RO, the at least one legacy RO overlapping the at least one additional RO, the at least one additional RO being one of:

[0202] deactivated and unavailable;

[0203] available and associated with a different synchronization signal block, SSB, beam than a SSB beam associated with the at least one legacy RO; or

[0204] available and associated with a different RO index; and

[0205] communicate the configuration to the UE 22.

[0206] Example D2. The network node 16 of Example D 1 , wherein the UE 22 is a nonnetwork energy saving, NES, capable UE 22; and

[0207] the configuration being for the at least one RO.

[0208] Example D3. The network node 16 of any one of Examples D1-D2, wherein the UE 22 is a non-network energy saving, NES, capable UE 22; and

[0209] the configuration being for the at least one additional RO.

[0210] Example D4. The network node 16 of any one of Examples D1-D3, wherein the overlap is in a time domain and not a frequency domain.

[0211] 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, an entirely 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 producton 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.

[0212] 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.

[0213] 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.

[0214] 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.

[0215] 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 in succession 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.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).

[0216] 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.

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

[0218] Abbreviations Explanation

[0219] NES Network Energy Saving

[0220] PRACH Physical Random-Access Channel

[0221] RA-RNTI Random Access Radio Network Temporary Identifier RAR Random Access Response

[0222] RACH Random Access Channel

[0223]

[0224] RACH Occasion

[0225] UE User Equipment

[0226] It 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 arepossible in light of the above teachings without departing from the scope of the following claims.

Claims

CLAIMS1. A method implemented in a user equipment, UE (22), that is configured to communicate with a network node (16), the method comprising:receiving (SI 12) a configuration for at least one additional random access channel, RACH, occasion, RO, the at least one additional RO being associated with an RO index and overlapping at least one first RO, the at least one first RO being configured by a first configuration;associating (SI 14) the at least one additional RO with a different RO index; andperforming (SI 16) at least one action based on the configuration and the different RO index.

2. The method of claim 1, wherein the associating of the at least one additional RO with a different RO index comprises:associating the at least one additional RO with a different RO index based on the additional RO overlapping with the at least one first RO.

3. The method of claim 2, wherein the associating of the at least one additional RO with a different RO index based on the additional RO overlapping with the at least one first RO comprises:associating the at least one additional RO with a different RO index based on the additional RO overlapping with the at least one first RO in a time domain but not in a frequency domain.

4. The method of any one of Claims 1-3, wherein the associating of the at least one additional RO with a different RO index comprises:changing the RO index of the at least one additional RO to the different RO index.

5. The method of Claim 4, wherein the changing of the RO index occurs based on the at least one additional RO and the at least first RO being associated with a same Synchronization Signal Block, SSB, beam.

6. The method of any one of Claims 1-5, wherein the performing of the at least one action based on the configuration and the different RO index comprises calculating a Random Access Network Temporary Identifier, RA-RNTI, associated with the at least one additional RO based on the different RO index.

7. The method of any one of Claims 1-6, wherein the at least one additional RO:at least partially overlaps in the time domain with the at least one first RO; and does not overlap in the frequency domain with the at least one first RO.

8. The method of any one of Claims 1-7, wherein prior to associating the at least one additional RO with the different RO index, the at least one additional RO and the at least one first RO correspond to a same RO index.

9. The method of any one of Claims 1-8, further comprising, in response to the at least one additional RO overlapping the at least one first RO in a time domain, determining an RO index that is not occupied; andthe different RO index corresponds to the RO index that is not occupied.

10. The method of any one of Claims 1-9, wherein the UE (22) is a Network Energy Savings, NES, UE (22).

11. The method of any one of Claims 1-10, wherein the at least one additional RO is available.

12. A user equipment, UE (22), that is configured to communicate with a network node (16), the UE (22) configured to:receive a configuration for at least one additional random access channel, RACH, occasion, RO, the at least one additional RO being associated with an RO index and overlapping at least one first RO, the at least one first RO being configured by a first configuration;associate the at least one additional RO with a different RO index; and perform at least one action based on the configuration and the different RO index.

13. The UE (22) of claim 12, wherein the associating of the at least one additional RO with a different RO index comprises:associating the at least one additional RO with a different RO index based on the additional RO overlapping with the at least one first RO.

14. The UE (22) of claim 13, wherein the associating of the at least one additional RO with a different RO index based on the additional RO overlapping with the at least one first RO comprises:associating the at least one additional RO with a different RO index based on the additional RO overlapping with the at least one first RO in a time domain but not in a frequency domain.

15. The UE (22) of any one of Claims 12-14, wherein the associating of the at least one additional RO with a different RO index comprises:changing the RO index of the at least one additional RO to the different RO index.

16. The UE (22) of Claim 15, wherein the changing of the RO index occurs based on the at least one additional RO and the at least one first RO being associated with a same Synchronization Signal Block, SSB, beam.

17. The UE (22) of any one of Claims 12-16, wherein the performing of the at least one action based on the configuration and the different RO index comprises calculating a Random Access Network Temporary Identifier, RA-RNTI, associated with the at least one additional RO based on the different RO index.

18. The UE (22) of any one of Claims 12-17, wherein the at least one additional RO:at least partially overlaps in the time domain with the at least one first RO; and does not overlap in the frequency domain with the at least one first RO.

19. The UE (22) of any one of Claims 12-18, wherein prior to associating the at least one additional RO with the different RO index, the at least one additional RO and the at least one first RO correspond to a same RO index.

20. The UE (22) of any one of Claims 12-19, wherein the UE (22) is further configured to, in response to the at least one additional RO overlapping the at least one first RO in a time domain, determine an RO index that is not occupied; andthe different RO index corresponds to the RO index that is not occupied.

21. The UE (22) of any one of Claims 12-20, wherein the UE (22) is a Network Energy Savings, NES, UE (22).

22. The UE (22) of any one of Claims 12-21, wherein the at least one additional RO is available.

23. A method implemented in a network node (16), that is configured to communicate with a user equipment, UE (22), the method comprising:transmitting (SI 04) a configuration for at least one additional random access channel, RACH, occasion, RO, the at least one additional RO being associated with an RO index and overlapping at least one first RO, the at least one first RO being configured by a first configuration; andassociating (SI 06) the at least one additional RO with a different RO index.

24. The method of claim 23, further comprising: performing at least one network node action based on the configuration and the different RO index.

25. The method of Claim 23 or 24, wherein the associating of the at least one additional RO with a different RO index comprises:changing the RO index of the at least one additional RO to the different RO index.

26. The method of Claim 25, wherein the changing of the RO index occurs based on the at least one additional RO and the at least one first RO being associated with a same Synchronization Signal Block, SSB, beam.

27. The method of any one of Claims 23-26, further comprising: calculating a Random Access Network Temporary Identifier, RA-RNTI, associated with the at least one additional RO based on the different RO index.

28. The method of any one of Claims 23-27, wherein the at least one additional RO:at least partially overlaps in the time domain with the at least one first RO; and does not overlap in the frequency domain with the at least one first RO.

29. The method of any one of Claims 23-28, wherein prior to associating the at least one additional RO with the different RO index, the at least one additional RO and the at least one first RO correspond to a same RO index.

30. The method of any one of Claims 23-29, further comprising, in response to the at least one additional RO overlapping at least one first RO in a time domain, determining an RO index that is not occupied; andthe different RO index corresponds to the RO index that is not occupied.

31. The method of any one of Claims 23-30, wherein the UE (22) is a Network Energy Savings, NES, UE (22).

32. The method of any one of Claims 23-31, wherein the additional RO is available.

33. The method of any one of Claims 23-32, wherein the associating of the at least one additional RO with a different RO index is based on the at least one additional RO overlapping with the at least one first RO that is configured by the first configuration.

34. A network node (16) that is configured to communicate with a user equipment, UE (22), the network node (16) configured to:transmit a configuration for at least one additional random access channel, RACH, occasion, RO, the at least one additional RO being associated with an RO index and overlapping at least one first RO, the at least one first RO being configured by a first configuration; andassociate the at least one additional RO with a different RO index.

35. The network node (16) of claim 34, wherein the network node (16) is further configured to perform at least one network node action based on the configuration and the different RO index.

36. The network node (16) of Claim 34 or 35, wherein the associating of the at least one additional RO with a different RO index comprises:changing the RO index of the at least one additional RO to the different RO index.

37. The network node (16) of Claim 36, wherein the changing of the RO index occurs based on the at least one additional RO and the at least one first RO being associated with a same Synchronization Signal Block, SSB, beam.

38. The network node (16) of any one of Claims 34-37, wherein the network node (16) is further configured to calculate a Random Access Network Temporary Identifier, RA-RNTI, associated with the at least one additional RO based on the different RO index.

39. The network node (16) of any one of Claims 34-38, wherein the at least one additional RO:at least partially overlaps in the time domain with the at least one first RO; and does not overlap in the frequency domain with the at least one first RO.

40. The network node (16) of any one of Claims 34-39, wherein prior to associating the at least one additional RO with the different RO index, the at least one additional RO and the at least one first RO correspond to a same RO index.

41. The network node (16) of any one of Claims 34-40, wherein the network node (16) is further configured to, in response to the at least one additional RO overlapping at least one first RO in a time domain, determine an RO index that is not occupied; andthe different RO index corresponds to the RO index that is not occupied.

42. The network node (16) of any one of Claims 34-41, wherein the UE (22) is a Network Energy Savings, NES, UE (22).

43. The network node (16) of any one of Claims 34-42, wherein the additional RO is available.

44. The network node (16) of any one of Claims 34-43, wherein the associating of the at least one additional RO with a different RO index is based on the at least one additional RO overlapping with the at least one first RO that is configured by the first configuration.

Images