Fallback procedures between user equipment and network apparatuses

Abstract

An apparatus includes at least one processor and at least one memory storing instructions. When executed by the at least one processor, the instructions of the at least one memory causes the apparatus to perform a method that includes: receiving, from a network apparatus, a dedicated random access (RA) configuration indicating a first type of physical random-access channel occasion (RO); transmitting, to the network apparatus, a plurality of contention-free random access (CFRA) requests including a first set of preambles and the first type of RO; and receiving, from the network apparatus, the dedicated RA configuration indicating a second type of RO.

Description

FALLBACK PROCEDURES BETWEEN USER EQUIPMENT AND NETWORK APPARATUSESFIELD

[0001] Various example aspects relate to efficient transfer of information, more particularly, to the efficient transfer of information between a user equipment (UE) and a network apparatus.BACKGROUND

[0002] Wireless networking provides significant advantages for user mobility. A user’s ability to remain connected while on the move provides advantages not only for the user, but also provides greater efficiency and productivity for society as a whole. As expectations for connection reliability, data speed, and lower power consumption, become more demanding, technology for wireless networking must also keep pace with such expectations. Accordingly, there is continuing interest in improving wireless networking technology.SUMMARY

[0003] In accordance with aspects of the disclosure, an apparatus includes at least one processor and at least one memory storing instructions. When executed by the at least one processor, the instructions of the at least one memory causes the apparatus to perform a method that includes: receiving, from a network apparatus, a dedicated random access (RA) configuration indicating a first type of physical random-access channel occasion (RO); transmitting, to the network apparatus, a plurality of contention-free random access (CFRA) requests including a first set of preambles and the first type of RO; and receiving, from the network apparatus, the dedicated RA configuration indicating a second type of RO.

[0004] In an aspect, the method further comprises transmitting, to the network apparatus, a request including the first set of preambles and the second type of RO after receiving, from the network apparatus, the dedicated RA configuration indicating the second type of RO.

[0005] In an aspect, the request including the first set of preambles and the second type of RO is a CFRA request.

[0006] In an aspect, the method further comprises transmitting, to the network apparatus, an additional CFRA request after receiving, from the network apparatus, the dedicated RA configuration indicating the second type of RO.

[0007] In an aspect, the first type of RO is a sub-band non-overlapping full duplex (SBFD) RO.

[0008] In an aspect, the second type of RO is a legacy RO.

[0009] In an aspect, the method further comprises transmitting, to the network apparatus, an additional CFRA request including the first set of preambles and the second type of RO after receiving, from the network apparatus, the dedicated RA configuration indicating the second type of RO.

[0010] In an aspect, the plurality of requests of the CFRA requests exceeds a reference signal received power (RSRP) threshold.

[0011] In an aspect, each request of the plurality of CFRA requests including the first set of preambles and the first type of RO is unsuccessful.

[0012] In an aspect, the apparatus is a SBFD-aware apparatus.

[0013] In an aspect, the apparatus is a user equipment (UE).

[0014] In accordance with aspects of the disclosure, a method in a user equipment (UE) includes: receiving, from a network apparatus, a dedicated random access (RA) configuration indicating a first type of physical random-access channel occasion (RO); transmitting, to the network apparatus, a plurality of contention-free random access (CFRA) requests including a first set of preambles and the first type of RO; and receiving, from the network apparatus, the dedicated RA configuration indicating a second type of RO.

[0015] In accordance with aspects of the disclosure, a method in a network apparatus includes: transmitting, to a user equipment (UE), a dedicated random access (RA) configuration indicating a first type of physical random-access channel occasion (RO); receiving, from the UE, a plurality of contention-free random access (CFRA) requests including a first set of preambles and the first type of RO; transmitting, to the UE, the dedicated RA configuration indicating a second type of RO; an receiving, from the UE, a CFRA request including the first set of preambles and the second type of RO..

[0016] According to some aspects, there is provided the subject matter of the independent claims. Some further aspects are defined in the dependent claims.BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Some example aspects will now be described with reference to the accompanying drawings.

[0018] FIG. 1 is a diagram of an example aspect of wireless networking between a network system and a user equipment (UE), according to one illustrated aspect of the disclosure;

[0019] FIG. 2 is a diagram of example components of a network system, according to one illustrated aspect of the disclosure;

[0020] FIG. 3 is a diagram of an example aspect of a contention-based random access procedure, according to one illustrated aspect of the disclosure;

[0021] FIG. 4 is a flow chart illustrating an example of communications between a UE and a network apparatus, according to an aspect of the disclosure;

[0022] FIG. 5 is a flow chart illustrating another example of communications between a UE and a network apparatus, according to an aspect of the disclosure;

[0023] FIG. 6 is a flow chart illustrating other examples of communications between a UE and a network apparatus, according to aspects of the disclosure;

[0024] FIG. 7 is a diagram of an example of components of a user equipment or of a network apparatus, according to one illustrated aspect of the present disclosure.DETAILED DESCRIPTION

[0025] The present disclosure relates to fallback procedures for use after unsuccessful attempts to transmit or receive information. More particularly, the present disclosure relates to apparatuses and methods for employing fallback procedures between user equipment (UE) and network apparatuses after unsuccessful attempts to transmit or receive a random access (RA) request.

[0026] In the following description, certain specific details are set forth in order to provide a thorough understanding of disclosed aspects. However, one skilled in the relevant art will recognize that aspects may be practiced without one or more of these specific details or with other methods, components, materials, etc. In other instances, well-known structures associated with transmitters, receivers, or transceivers have not been shown or described in detail to avoid unnecessarily obscuring descriptions of the aspects.

[0027] Reference throughout this specification to “one aspect” or “an aspect” means that a particular feature, structure, or characteristic described in connection with the aspect is included in at least one aspect. Thus, the appearances of the phrases “in one aspect” or “in an aspect” in various places throughout this specification are not necessarily all referring to the same aspect. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more aspects.

[0028] Aspects described in the present disclosure may be implemented in wireless networking apparatuses, such as, without limitation, apparatuses utilizing Worldwide Interoperability for Microwave Access (WiMAX), Global System for Mobile communications (GSM, 2G), GSM EDGE radio access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunication System (UMTS, 3G) based on basic wideband-code division multiple access (W-CDMA), high-speed packet access (HSPA), Long Term Evolution (LTE), LTE-Advanced, enhanced LTE (eLTE), 5GNew Radio (5GNR), 5G Advance, 6G (and beyond) and 802.1 lax (Wi-Fi 6), among other wireless networking systems. The term ‘eLTE’ here denotes the LTE evolution that connectsto a 5G core. LTE is also known as evolved UMTS terrestrial radio access (EUTRA) or as evolved UMTS terrestrial radio access network (EUTRAN).

[0029] The present disclosure may use the term “serving network device” to refer to a network node or network device (or a portion thereof) that services a UE. As used herein, the terms “transmit toward,” “transmit to,” “receive from,” and “cooperate with,” (and their variations) include communications that may or may not involve communications through one or more intermediate devices or nodes. The term “acquire” (and its variations) includes acquiring in the first instance or reacquiring after the first instance. The term “connection” may mean a physical connection or a logical connection.

[0030] The present disclosure uses 5G NR as an example of a wireless network and may use smartphones and / or extended reality headsets as an example of UEs. It is intended and shall be understood that such examples are merely illustrative, and the present disclosure is applicable to other wireless networks and user equipment.

[0031] FIG. 1 is a diagram depicting an example of wireless networking between a network system 100 and a user equipment (UE) 150. The network system 100 may include one or more network nodes 120, one or more servers 110, and / or one or more network equipment 130 (e.g., test equipment). The network nodes 120 will be described in more detail below. As used herein, the term “network apparatus” may refer to any component of the network system 100, such as the server 110, the network node 120, the network equipment 130, any component(s) of the foregoing, and / or any other component(s) of the network system 100. Examples of network apparatuses include, without limitation, apparatuses implementing aspects of 5G NR, among others. The present disclosure describes aspects related to 5G NR and aspects that involve aspects defined by 3rd Generation Partnership Project (3GPP). However, it is contemplated that aspects relating to other wireless networking technologies are encompassed within the scope of the present disclosure.

[0032] The following description provides further details of examples of network nodes. In a 5G NR network, a gNodeB (also known as gNB) may include, e.g., a node that provides new radio (NR) user plane and control plane protocol terminations towards the UE and that is connected via a NG interface to the 5G core (5GC), e.g., according to 3GPP TS 38.300 V16.6.0 (2021-06) section 3.2, which is hereby incorporated by reference herein.

[0033] A gNB supports various protocol layers, e.g., Layer 1 (LI) - physical layer, Layer 2 (L2), and Layer 3 (L3).

[0034] The layer 2 (L2) of NR is split into the following sublayers: Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP) and Service Data Adaptation Protocol (SDAP), where, e.g. :o The physical layer offers to the MAC sublayer transport channels;o The MAC sublayer offers to the RLC sublayer logical channels;o The RLC sublayer offers to the PDCP sublayer RLC channels;o The PDCP sublayer offers to the SDAP sublayer radio bearers;o The SDAP sublayer offers to 5GC quality of service (QoS) flows;o Control channels include broadcast control channel (BCCH) and physical control channel (PC CH).

[0035] Layer 3 (L3) includes, e.g., radio resource control (RRC), e.g., according to 3GPP TS 38.300 V16.6.0 (2021-06) section 6, which is hereby incorporated by reference herein.

[0036] A gNB central unit (gNB-CU) includes, e.g., a logical node hosting, e.g., radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) protocols of the gNB or RRC and PDCP protocols of the en-gNB, that controls the operation of one or more gNB distributed units (gNB-DUs). The gNB-CU terminates the Fl interface connected with the gNB-DU. A gNB-CU may also be referred to herein as a CU, a central unit, a centralized unit, or a control unit.

[0037] A gNB Distributed Unit (gNB-DU) includes, e.g., a logical node hosting, e.g., radio link control (RLC), media access control (MAC), and physical (PHY) layers of the gNB or en-gNB, and its operation is partly controlled by the gNB-CU. One gNB-DU supports one or multiple cells. One cell is supported by only one gNB-DU. The gNB-DU terminates the Fl interface connected with the gNB-CU. A gNB-DU may also be referred to herein as DU or a distributed unit.

[0038] A gNB-CU-Control Plane (gNB-CU-CP) includes, e.g., a logical node hosting, e.g., the RRC and the control plane part of the PDCP protocol of the gNB-CU for an en-gNB or a gNB. The gNB-CU-CP terminates the El interface connected with the gNB-CU-User Plane (gNB-CU-UP) and the Fl-C interface connected with the gNB-DU.

[0039] A gNB-CU-User Plane (gNB-CU-UP) includes, e.g., a logical node hosting, e.g., the user plane part of the PDCP protocol of the gNB-CU for an en-gNB, and the user plane part of the PDCP protocol and the SDAP protocol of the gNB-CU for a gNB. The gNB-CU-UP terminates the El interface connected with the gNB-CU-CP and the Fl-U interface connected with the gNB-DU, e.g., according to 3GPP TS 38.401 V16.6.0 (2021-07) section 3.1, which is hereby incorporated by reference herein.

[0040] As used herein, the term “network node” may refer to any of a gNB, a gNB-CU, a gNB-DU, a gNB-CU-CP, or a gNB-CU-UP, or any combination of them.

[0041] A RAN (radio access network) node or network node such as, e.g., a gNB, gNB-CU, or gNB-DU, or parts thereof, may be implemented using, e.g., an apparatus with at least one processor and / or at least one memory with processor-readable instructions (“program”) configured to support and / or provision and / or process CU and / or DU related functionality and / or features, and / or at leastone protocol (sub-)layer of a RAN (radio access network), e.g., layer 2 and / or layer 3. Different functional splits between the central and distributed unit are possible. An example of such an apparatus and components will be described in connection with FIG. 4 below.

[0042] The gNB-CU and gNB-DU parts may, e.g., be co-located or physically separated. The gNB-DU may even be split further, e.g., into two parts, e.g., one including processing equipment and one including an antenna. A central unit (CU) may also be called baseband unit / radio equipment controller / cloud-RAN / virtual-RAN (BBU / REC / C-RAN / V-RAN), open-RAN (O-RAN), or part thereof. A distributed unit (DU) may also be called remote radio head / remote radio unit / radio equipment / radio unit (RRH / RRU / RE / RU), or part thereof. Hereinafter, in various example aspects of the present disclosure, a network node, which supports at least one of central unit functionality or a layer 3 protocol of a radio access network, may be, e.g., a gNB-CU. Similarly, a network node, which supports at least one of distributed unit functionality or a layer 2 protocol of the radio access network, may be, e.g., a gNB-DU.

[0043] A gNB-CU may support one or multiple gNB-DUs. A gNB-DU may support one or multiple cells and, thus, could support a serving cell for a user equipment (UE) or support a candidate cell for handover, dual connectivity, and / or carrier aggregation, among other procedures.

[0044] The user equipment (UE) 150 may be or include a wireless or mobile device, an apparatus with a radio interface to interact with a RAN (radio access network), a smartphone, an in-vehicle apparatus, an loT device, or a M2M device, among other types of user equipment. Such UE 150 may include: at least one processor; and at least one memory including program code; where the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to perform certain operations, such as, e.g., RRC connection to the RAN. An example of components of a UE will be described in connection with FIG. 4. In aspects, the UE 150 may be configured to generate a message (e.g., including a cell ID) to be transmitted via radio towards a RAN (e.g., to reach and communicate with a serving cell). In aspects, the UE 150 may generate and transmit and receive RRC messages containing one or more RRC PDUs (packet data units). Persons skilled in the art will understand RRC protocol as well as other procedures a UE may perform.

[0045] With continuing reference to FIG. 1, in the example of a 5G NR network, the network system 100 provides one or more cells, which define a coverage area of the network system 100. As described above, the network system 100 may include a gNB of a 5G NR network or may include any other apparatus configured to control radio communication and manage radio resources within a cell. As used herein, the term “resource” may refer to radio resources, such as a resource block (RB), a physical resource block (PRB), a radio frame, a subframe, a time slot, a sub-band, a frequency region, a sub-carrier, a beam, etc. In aspects, the network node 120 may be called a base station.

[0046] FIG. 1 provides an example and is merely illustrative of a network system 100 and a UE 150. Persons skilled in the art will understand that the network system 100 includes components not illustrated in FIG. 1 and will understand that other user equipment may be in communication with the network system 100.

[0047] FIG. 2 is a block diagram of example components of the network system 100 of FIG. 1. A 5G NR network may be described as an example of the network system 100, and it is intended that aspects of the following description shall be applicable to other types of network systems, as well. The network system may operate in accordance with the signals and connections shown in FIG. 1 such that the UE 150 is in communication with the network system 100 through the radio access network (RAN) 225. Additionally, the network system may be divided into user plane components and functions and control plane components and functions, as shown and described herein. Unless indicated otherwise, the terms “component”, “function”, and “service” may be used interchangeably herein, and they may refer to and be implemented by instructions executed by one or more processors.

[0048] Example functions of the components are described below. The example functions are merely illustrative, and it shall be understood that additional operations and functions may be performed by the components described herein. Additionally, the connections between components may be virtual connections over service-based interfaces such that any component may communicate with any other component. In this manner, any component may act as a service “producer,” for any other component that is a service “consumer,” to provide services for network functions.

[0049] For example, a core network 210 is described in the control plane of the network system. The core network 210 may include an authentication server function (AUSF) 211, an access and mobility management function (AMF) 212, and a session management function (SMF) 213. The core network 210 may also include a network slice selection function (NSSF) 214, a network exposure function (NEF) 215, a network repository function (NRF) 216, and a unified data management function (UDM) 217, which may include a uniform data repository (UDR) 224.

[0050] Additional components and functions of the core network 210 may include an application function (AF) 218, policy control function (PCF) 219, network data analytics function (NWDAF) 220, analytics data repository function (ADRF) 221, management data analytics function (MDAF) 222, and operations and management function (0AM) 223.

[0051] The user plane includes the UE 150, a radio access network (RAN) 225, a user plane function (UPF) 226, and a data network (DN) 227. The RAN 225 may include one or more components described in connection with FIG. 1, such as one or more network nodes. However, the RAN 225 may not be limited to such components. The UPF 226 provides connection for data being transmitted over the RAN 225. The UPF 226 identifies services from service providers, Internet access, and third party services, for example.

[0052] The AMF 212 processes connection and mobility tasks. The AUSF 211 receives authentication requests from the AMF 212 and interacts with UDM 217 to authenticate and validate network responses for determination of successful authentication. The SMF 213 conducts packet data unit (PDU) session management, as well as manages session context with the UPF 226.

[0053] The NSSF 214 may select a network slicing instance (NSI) and determine the allowed network slice selection assistance information (NSSAI). This selection and determination is utilized to set the AMF 212 to provide service to the UE 150. The NEF 215 secures access to network services for third parties to create specialized network services. The NRF 216 acts as a repository to store network functions to allow the functions to register with and discover each other.

[0054] The UDM 217 generates authentication vectors for use by the AUSF 211 and AMF 212 and provides user identification handling. The UDM 217 may be connected to the UDR 224 which stores data associated with authentication, applications, or the like. The AF 218 provides application services to a user (e.g., streaming services, etc.). The PCF 219 provides policy control functionality. For example, the PCF 219 may assist in network slicing and mobility management, as well as provide quality of service (QoS) and charging functionality.

[0055] The NWDAF 220 collects data (e.g., from the UE 150 and the network system) to perform network analytics and provide insight to functions that utilize the analytics in the providing of services. The ADRF 221 allows the storage, retrieval, and removal of data and analytics by consumers. The MDAF 222 provides additional data analytics services for network functions. The 0AM 223 provides provisioning and management processing functions to manage elements in or connected to the network (e.g., UE 150, network nodes, etc.).

[0056] FIG. 2 is merely an example of components of a network system, and variations are contemplated to be within the scope of the present disclosure. In aspects, the network system may include other components not illustrated in FIG. 2. In aspects, the network system may not include every component illustrated in FIG. 2. In aspects, the components and connections may be implemented with different connections than those illustrated in FIG. 2. Such and other aspects are contemplated to be within the scope of the present disclosure.

[0057] A procedure for a UE to establish communications with a target cell is referred to as random access procedure. Random access procedure may be used for initial access, small data transmissions in inactive and transition from RRC Inactive to RRC Connected, as well as in beam failure recovery, connection re-establishment, handover, and cell addition, among other procedures which persons skilled in the art will recognize.

[0058] Two types of random access procedures include contention-based random access (CBRA) and contention-free random access (CFRA). FIG. 3 is a diagram of an example of a contention-based random access (CBRA) procedure. In the illustrated example, the signals include a random accesspreamble (MSG1) transmitted by the UE 350 towards the network node 310 (e.g., gNodeB, or part thereof), a random access response (MSG2) transmitted from the network node 310 towards the UE 350, a schedule transmission (MSG3) transmitted from the UE 350 towards the network node 310, and a contention resolution (MSG4) transmitted from the network node 310 towards the UE 350.

[0059] For MSG1, the UE 350 selects a usable random access preamble based on information elements in a signal synchronization block (SSB). The UE 350 sends the random access preamble (MSG1) towards the network node 310 using a specific time and frequency resource known as random access occasion (RO). The UE 350 also provides an identity, called random access radio network temporary identity (RA-RNTI), to the network so that the network can address it in the next step.

[0060] For MSG2, the network node 310 detects the preamble, calculates various quantities, and sends a physical uplink shared channel (PUSCH) uplink (UL) grant towards the UE 350. This is called the random access response (RAR), which is sent as MSG2 addressed to the UE 350 with the relevant RA-RNTI and indicates to the UE 350 where in frequency and when in time it can transmit MSG3 on the PUSCH.

[0061] For MSG3, in response to receiving the MSG2 from the network node 310, the UE 350 sends MSG3 using the UL grant provided in the RAR. Because the RAR provides a time resource allocation, the UE 350 sends MSG3 towards the network node 310 at a timing specified by the time resource allocation and is a scheduled transmission. This MSG3 may be called a radio resource control (RRC) connection request message.

[0062] For MSG4, the network node 310 may send MSG4 towards the UE 350 for contention resolution. Contention resolution may operate in the manner specified by 3GPP for 5G NR. After the random access procedure, assuming contention resolution is resolved favorably, the UE 350 becomes connected to the network node 310. After establishing a connection, various procedures would be handled by a gNB-CU in accordance with the CU-DU split. Other aspects of contention-based random access (CBRA) will be understood by persons skilled in the art.

[0063] Another type of random access procedure is contention-free random access (CFRA) (not shown). In CFRA (not shown), the network node 310 transmits an allocated random access preamble towards the UE 350. The UE 350 receives the allocated random access preamble and sends the random access preamble to the network node 310 in a random access request as MSG1. Then, MSG2 and MSG3 are similar to those described in connection with CBRA. No contention resolution is needed in CFRA based on use of an allocated random access preamble. Other aspects of contention-free random access (CFRA) will be understood by persons skilled in the art.

[0064] As mentioned above, in accordance with aspects of the present disclosure, the present disclosure relates to various approaches for determining whether the active time period in a beamtransmitted by the network has a long enough duration for a UE to receive any or all of the random access response (RAR) from the network.

[0065] Typically, when a UE transmits a random access preamble to a network, the UE either receives a RAR from the network or fails to receive a RAR from the network. In instances where the UE does not receive a RAR from the network, the UE may transmit another RA preamble. This process may continue until the UE receives the RAR from the network, which can lead to wasted time and energy. As used herein, “preamble” includes a set of preambles, in accordance with aspects of the disclosure.

[0066] As used herein, the term “S-beam” denotes a satellite beam footprint, which is a radio beam transmitted by a satellite and may correspond to a full cell, part of a cell, or an NR-beam. The term “NR-beam” denotes a beam as described in the context of 3rd Generation Partnership Project (3 GPP) NR Systems. For instance, an NR cell may be divided into a plurality of NR-beams.

[0067] In Radio Access Networks (RANs), different standards are utilized to enable and facilitate wireless communication. One such standard includes that when using a contention-free random access (CFRA) procedure, the network apparatus will indicate the type of physical randomaccess channel occasion (RO) (sub-band non-overlapping full duplex (SBFD) or legacy RO) to be used by a SBFD-aware user equipment (UE). The standard also states two options are supported in a cell only type of random-access channel (RACH) configuration: 1) a RACH configuration option 1 with Alt 1-1; or 2) a RACH configuration option 2. Under this standard, if a particular RO type is indicated to the SBFD UE, and if random access (RA) fails after trying a maximum number of attempts (as indicated in the RO type), the random access will be declared as unsuccessful. However, if the UE is SBFD aware or capable, it may be beneficial for the UEs to attempt the RA in another RO type as well, since collision level and interference level on the other RO type could be different. The follows aspects and examples consider procedures for falling back from RO type to another RA type, for instance, and also consider scenarios for falling back from CFRA to a contention-based random access (CBRA).

[0068] Referring now to FIGS. 4-6, flow charts illustrating examples of various communications between an apparatus including at least one processor and at least one memory (e.g., a UE) and a network apparatus, according to aspects of the disclosure, are shown. In some circumstances, communication between a network apparatus and a user equipment (UE) is unsuccessful for a variety of reasons. In these situations, continued attempts for a successful communication between the network apparatus and the UE may take place. The flow charts in FIGS. 4-6 illustrate different examples of fallback procedures used for continued attempts at successful communication between the network apparatus and the UE, according to aspects of the disclosure.

[0069] With particular reference to FIG. 4, a first aspect of a fallback procedure is shown. Here, operation 400 indicates that a UE is in a connected state with the network apparatus (identified in several figures as “NW”). In the illustrated aspect, the UE is a sub-band nonoverlapping full duplex (SBFD)-aware apparatus. Operation 410 shows the network apparatus transmitting to the UE, and the UE receiving, a dedicated random access (RA) configuration (e.g., “RACH-ConfigDedicated”) indicating a first type of physical random-access channel occasion (RO) (e g., a SBFD RO).

[0070] At operation 420, the UE transmits to the network apparatus a plurality of contention-free random access (CFRA) requests utilizing the first type of RO (i.e., the SBFD RO). The network apparatus receives from the UE the plurality of contention-free random access (CFRA) requests utilizing the first type of RO. In aspects, the requests in operation 420 include a first preamble. Further, operation 420 indicates that the number of requests made are defined in the preamble as “preambleTransMax.” In aspects, the number of requests made meets or exceeds a reference signal received power (RSRP) threshold.

[0071] As shown in FIG. 4, the plurality of CFRA requests is unsuccessful. That is, even after the UE performs the CFRA requests a maximum number of times (e.g., as defined in the preamble), the transmissions are unsuccessful for at least one of a variety of reasons; the network apparatus does not receive any of the CFRA requests.

[0072] At operation 430, the network apparatus transmits to the UEa dedicated RA configuration (e.g., “RACH-ConfigDedicated”; which is the same configuration used in operation 410) indicating a second type of RO (e.g., a legacy RO). The UE receives from the network apparatus the dedicated RA configuration indicating the second type of RO.

[0073] At operation 440, the UE transmits to the network apparatus at least one request (e.g., a CFRA request) including the first preamble and the second type of RO (i.e., the legacy RO). The network apparatus receives from the UE the at least one request including the first preamble and the second type of RO. Further, operation 440 indicates that the maximum number of requests made are defined in the preamble as “preambleTransMax.”

[0074] The operations of FIG. 4 are merely illustrative, and variations are contemplated to be within the scope of the present disclosure. In aspects, the operations may include other operations not illustrated in FIG. 4. In aspects, the operations may not include every operation illustrated in FIG. 4. In aspects, the operations may be implemented in a different order than that illustrated in FIG. 4. Such and other aspects are contemplated to be within the scope of the present disclosure. Persons of skill in the art will appreciate that, although various example components are described as performing various functions, other components may perform those functions described in FIG. 4.

[0075] The following describes an apparatus (such as UE) including at least one processor, and at least one memory storing instructions. When executed by the at least one process, the memory storing instructions may cause the apparatus to perform a method, which may include: receiving, from a network apparatus, a dedicated random access (RA) configuration indicating a first type of physical random-access channel occasion (RO) (e.g., operation 410); transmitting, to the network apparatus, a plurality of contention-free random access (CFRA) requests including a first preamble and the first type of RO (e.g., operation 420); and receiving, from the network apparatus, the dedicated RA configuration indicating a second type of RO (e.g., operation 430).

[0076] With particular reference to FIG. 5, a second aspect of a fallback procedure is shown. Here, operation 500 indicates that a UE is in a connected state with the network apparatus NW. In the illustrated aspect, the UE is a sub-band non-overlapping full duplex (SBFD) -aware apparatus. Operation 510 shows the network apparatus transmitting to the UE, and the UE receiving, a dedicated random access (RA) configuration (e.g., “RACH-ConfigDedicated”) indicating a first type of physical random-access channel occasion (RO) (e.g., a SBFD RO). Additionally, the RA includes a field defining the maximum number of RA attempts the SBFD-aware UE can perform in an RO type (e.g., “SBFD RO”) - “preambleTransMax SBFD.”

[0077] At operation 520, the UE performs the CFRA in SBFD ROs a number of times. The number of times is set by the RA in the field defining the maximum number of such attempts.

[0078] As shown in FIG. 5, the plurality of CFRA requests is unsuccessful. That is, even after the UE performs the CFRA requests the maximum number of times (e.g., as defined in the preamble), the transmissions are unsuccessful for at least one of a variety of reasons; the network apparatus does not receive any of the CFRA requests.

[0079] At operation 530, the UE retries a CFRA request and transmits to the network apparatus at least one request (e.g., a CFRA request) including a second type of RO (i.e., a legacy RO) (in contrast with the first type of RO (SBFD RO) used in operation 520) using the same preamble or set of preambles as the CFRA requests conducted in operation 520. The network apparatus receives from the UE the at least one request including the second type of RO using the same preamble or set of preambles as the CFRA requests conducted in operation 520. The maximum number of requests or attempts to transmit the information is the same as indicated in operation 520, and is defined by “preambleTransMax SBFD” in the RA, for instance.

[0080] The operations of FIG. 5 are merely illustrative, and variations are contemplated to be within the scope of the present disclosure. In aspects, the operations may include other operations not illustrated in FIG. 5. In aspects, the operations may not include every operation illustrated in FIG. 5. In aspects, the operations may be implemented in a different order than that illustrated in FIG. 5. Such and other aspects are contemplated to be within the scope of the present disclosure. Persons of skillin the art will appreciate that, although various example components are described as performing various functions, other components may perform those functions described in FIG. 5.

[0081] Referring now to FIG. 6, third and fourth aspects of fallback procedures are shown. Here, operation 600 indicates that a UE is in a connected state with the network apparatus NW. In the illustrated aspect, the UE is a sub-band non-overlapping full duplex (SBFD) -aware apparatus. Operation 610 shows the network apparatus transmitting to the UE, and the UE receiving, a dedicated random access (RA) configuration (e.g., “RACH-ConfigDedicated”) indicating a first type of physical random-access channel occasion (RO) (e.g., a SBFD RO). Additionally, the RA may include a field defining the maximum number of RA attempts the SBFD-aware UE can perform in an RO type (e.g., “SBFD RO”) - “preambleTransMax SBFD.”

[0082] At operation 620, the UE performs the CFRA in SBFD ROs a number of times. The number of times is set by the RA in the field defining the maximum number of such attempts.

[0083] As shown in FIG. 6, the plurality of CFRA requests is unsuccessful. That is, even after the UE performs the CFRA requests the maximum number of times (e.g., as defined in the preamble), the transmissions are unsuccessful for at least one of a variety of reasons; the network apparatus does not receive any of the CFRA requests.

[0084] At operation 625, which is an optional step that is part of the third aspect, the UE determines that the RA configuration of the network apparatus does not include the legacy RO and / or the field defining the maximum number of RA attempts the SBFD-aware UE can perform in an RO type (e.g., “SBFD RO”) - “preambleTransMax SBFD.”

[0085] At operation 630, the network apparatus transmits a dedicated RA configuration that is different from the dedicated RA configuration utilized in operation 610. The UE receives from the network apparatus the dedicated RA configuration that is different from the dedicated RA configuration utilized in operation 610. Here, the dedicated RA configuration is “RACH-ConfigCommon,” which may include a different RO than the “RACH-ConfigDedicated” in operation 610. More particularly, the RA configuration in operation 630 may include a legacy RO, in contrast with the SBFD RO included in operation 610.

[0086] At operation 635, which is an optional step that is part of the fourth aspect, during the RO validation stage, the UE marks the SBFD ROs or the ROs in the downlink (DL) slots as invalid.

[0087] At operation 640, which is an optional step that is part of the third aspect, the UE transmits a contention-based random access (CBRA) procedure in legacy RO. The network apparatus receives from the UE the CBRA procedure in legacy RO. This CBRA is performed by randomly selecting the preambles for each of the Synchronization Signal / Physical Broadcast Channel (SS / PBCH) block beams or channel state information (CSI) reference signal beam where it had previously been attempted the CFRA in operation 620.

[0088] The operations of FIG. 6 are merely illustrative, and variations are contemplated to be within the scope of the present disclosure. In aspects, the operations may include other operations not illustrated in FIG. 6. In aspects, the operations may not include every operation illustrated in FIG. 6. In aspects, the operations may be implemented in a different order than that illustrated in FIG. 6. Such and other aspects are contemplated to be within the scope of the present disclosure. Persons of skill in the art will appreciate that, although various example components are described as performing various functions, other components may perform those functions described in FIG. 6.

[0089] The examples included in FIGS. 4-6 are merely illustrative, and variations and other aspects are contemplated to be within the scope of the present disclosure.

[0090] Referring now to FIG. 7, there is shown a block diagram of example components of a UE or a network apparatus. The apparatus includes an electronic storage 710, a processor 720, a memory 750, and a network interface 740. The various components may be communicatively coupled with each other. The processor 720 may be and may include any type of processor, such as a single-core central processing unit (CPU), a multi-core CPU, a microprocessor, a digital signal processor (DSP), a System-on-Chip (SoC), or any other type of processor. The memory 750 may be a volatile type of memory, e.g., RAM, or a non-volatile type of memory, e.g., NAND flash memory. The memory 750 includes processor-readable instructions that are executable by the processor 720 to cause the apparatus to perform various operations, including those mentioned herein, such as the operations of FIGS. 3-6.

[0091] The electronic storage 710 may be and include any type of electronic storage used for storing data, such as hard disk drive, solid state drive, and / or optical disc, among other types of electronic storage. The electronic storage 710 stores processor-readable instructions for causing the apparatus to perform its operations and stores data associated with such operations, such as storing data relating to 5G NR standards, among other data. The network interface 740 may implement wireless networking technologies such as 5G NR and / or other wireless networking technologies.

[0092] The components shown in FIG. 7 are merely examples, and persons skilled in the art will understand that an apparatus includes other components not illustrated and may include multiples of any of the illustrated components. Such and other aspects are contemplated to be within the scope of the present disclosure.

[0093] Further aspects of the present disclosure include the following examples.

[0094] Example 1.1. An apparatus comprising:at least one processor; andat least one memory storing instructions which, when executed by the at least one processor, causes the apparatus to perform a method including:receiving, from a network apparatus, a dedicated random access (RA) configuration indicating a first type of physical random-access channel occasion (RO);transmitting, to the network apparatus, a plurality of contention-free random access (CFRA) requests including a first set of preambles and the first type of RO; and receiving, from the network apparatus, the dedicated RA configuration indicating a second type of RO.

[0095] Example 1.2. The apparatus of Example 1.1, wherein the method further comprises transmitting, to the network apparatus, a request including the first set of preambles and the second type of RO after receiving, from the network apparatus, the dedicated RA configuration indicating the second type of RO.

[0096] Example 1.3. The apparatus of Example 1.2, wherein the request including the first set of preambles and the second type of RO is a CFRA request.

[0097] Example 1.4. The apparatus of Example 1.1, wherein the method further comprises transmitting, to the network apparatus, an additional CFRA request after receiving, from the network apparatus, the dedicated RA configuration indicating the second type of RO.

[0098] Example 1.5. The apparatus of any of Examples 1.1-1.4, wherein the first type of RO is a sub-band non-overlapping full duplex (SBFD) RO.

[0099] Example 1.6. The apparatus of any of Examples 1.1-1.5, wherein the second type of RO is a legacy RO.

[0100] Example 1.7. The apparatus of any of Examples 1.1-1.6, wherein the method further comprises transmitting, to the network apparatus, an additional CFRA request including the first set of preambles and the second type of RO after receiving, from the network apparatus, the dedicated RA configuration indicating the second type of RO.

[0101] Example 1.8. The apparatus of any of Examples 1.1-1.7, wherein the plurality of requests of the CFRA requests exceeds a reference signal received power (RSRP) threshold.

[0102] Example 1.9. The apparatus of any of Examples 1.1-1.8, wherein each request of the plurality of CFRA requests including the first set of preambles and the first type of RO is unsuccessful.

[0103] Example 1.10. The apparatus of any of Examples 1.1-1.9, wherein the apparatus is a SBFD-aware apparatus.

[0104] Example l.il. The apparatus of any of Examples 1.1-1.10, wherein the apparatus is a user equipment (UE).

[0105] Example 1.12. A method in a user equipment (UE), comprising:receiving, from a network apparatus, a dedicated random access (RA) configuration indicating a first type of physical random-access channel occasion (RO);transmitting, to the network apparatus, a plurality of contention-free random access (CFRA) requests including a first set of preambles and the first type of RO; andreceiving, from the network apparatus, the dedicated RA configuration indicating a second type of RO.

[0106] Example 1.13. The method of Example 1.12, further comprising transmitting, to the network apparatus, a request including the first set of preambles and the second type of RO after receiving, from the network apparatus, the dedicated RA configuration indicating the second type of RO.

[0107] Example 1.14. The method of Example 1.13, wherein the request including the first set of preambles and the second type of RO is a CFRA request.

[0108] Example 1.15. The method of Example 1.12, further comprising transmitting, to the network apparatus, an additional CFRA request after receiving, from the network apparatus, the dedicated RA configuration indicating the second type of RO.

[0109] Example 1.16. The method of any of Examples 1.12-1.15, wherein the first type of RO is a sub-band non-overlapping full duplex (SBFD) RO.

[0110] Example 1.17. The method of any of Examples 1.12-1.16, wherein the second type of RO is a legacy RO.

[0111] Example 1.18. The method of any of Examples 1.12-1.17, wherein the method further comprises transmitting, to the network apparatus, an additional CFRA request including the first set of preambles and the second type of RO after receiving, from the network apparatus, the dedicated RA configuration indicating the second type of RO.

[0112] Example 1.19. The method of any of Examples 1.12-1.18, wherein the plurality of requests of the CFRA requests exceeds a reference signal received power (RSRP) threshold.

[0113] Example 1.20. The method of any of Examples 1.12-1.19, wherein each request of the plurality of CFRA requests including the first set of preambles and the first type of RO is unsuccessful.

[0114] Example 1.21. The method of any of Examples 1.12-1.20, wherein the apparatus is a SBFD-aware apparatus.

[0115] Example 1.22. The method of any of Examples 1.12-1.21, wherein the apparatus is a user equipment (UE).

[0116] Example 1.23. A method in a network apparatus, comprising:transmitting, to a user equipment (UE), a dedicated random access (RA) configuration indicating a first type of physical random-access channel occasion (RO);receiving, from the UE, a plurality of contention-free random access (CFRA) requests including a first set of preambles and the first type of RO;transmitting, to the UE, the dedicated RA configuration indicating a second type of RO; and receiving, from the UE, a CFRA request including the first set of preambles and the second type of RO.

[0117] Example 1.24. The method of Example 1.23, further comprising receiving, from the UE, a request including the first set of preambles and the second type of RO after transmitting, to the UE, the dedicated RA configuration indicating the second type of RO.

[0118] Example 1.25. The method of Example 1.24, wherein the request including the first set of preambles and the second type of RO is a CFRA request.

[0119] Example 1.26. The method of Example 1.23, further comprising receiving, from the UE, an additional CFRA request after transmitting, to the UE, the dedicated RA configuration indicating the second type of RO.

[0120] Example 1.27. The method of any of Examples 1.23-1.26, wherein the first type of RO is a sub-band non-overlapping full duplex (SBFD) RO.

[0121] Example 1.28. The method of any of Examples 1.23-1.27, wherein the second type of RO is a legacy RO.

[0122] Example 1.29. The method of any of Examples 1.23-1.28, wherein the method further comprises receiving, from the UE, an additional CFRA request including the first set of preambles and the second type of RO after transmitting, to the UE, the dedicated RA configuration indicating the second type of RO.

[0123] Example 1.30. The method of any of Examples 1.23-1.29, wherein the plurality of requests of the CFRA requests exceeds a reference signal received power (RSRP) threshold.

[0124] Example 1.31. The method of any of Examples 1.23-1.30, wherein each request of the plurality of CFRA requests including the first set of preambles and the first type of RO is unsuccessful.

[0125] Example 1.32. The method of any of Examples 1.23-1.31, wherein the apparatus is a SBFD-aware apparatus.

[0126] Example 1.33. The method of any of Examples 1.23-1.32, wherein the apparatus is a user equipment (UE).

[0127] Example 2.1. An apparatus comprising:at least one processor; andat least one memory storing instructions which, when executed by the at least one processor, causes the apparatus to perform a method including:receiving, from a network apparatus, a dedicated random access (RA) configuration indicating a sub-band non-overlapping full duplex (SBFD) physical random-access channel occasion (RO);transmitting, to the network apparatus, a plurality of contention-free random access (CFRA) requests including a first set of preambles and the SBFD RO; and receiving, from the network apparatus, the dedicated RA configuration indicating a legacy RO.

[0128] Example 2.2. The apparatus of Example 2.1, further comprising transmitting, to the network apparatus, an additional CFRA request, after receiving, from the network apparatus, the dedicated RA configuration indicating a legacy RO.

[0129] Example 2.3. The apparatus of Example 2.2, wherein the additional CFRA request includes the first set of preambles.

[0130] Example 2.4. The apparatus of any of Examples 2.2-2.3, wherein the additional CFRA request includes the legacy RO.

[0131] Example 2.5. The apparatus of Example 2.4, wherein the additional CFRA request includes the first set of preambles.

[0132] Example 2.6. The apparatus of Example 2.5, wherein the first set of preambles includes at least one of a dedicated preamble for each Synchronization Signal / Physical Broadcast Channel (SS / PBCH) Block beam or a dedicated preamble for each Channel State Information (CSI) Reference Signal beam.

[0133] Example 2.7. The apparatus of any of Examples 2.1-2.6, wherein each request of the plurality of CFRA requests including the first set of preambles and the SBFD RO is unsuccessful.

[0134] Example 2.8. The apparatus of any of Examples 2.1-2.7, wherein the apparatus is a SBFD-aware apparatus.

[0135] Example 2.9. The apparatus of any of Examples 2.1-2.8, wherein the apparatus is a user equipment (UE).

[0136] Example 2.10. A method in a user equipment (UE), comprising:receiving, from a network apparatus, a dedicated random access (RA) configuration indicating a sub-band non-overlapping full duplex (SBFD) physical random-access channel occasion (RO); transmitting, to the network apparatus, a plurality of contention-free random access (CFRA) requests including a first set of preambles and the SBFD RO; andreceiving, from the network apparatus, the dedicated RA configuration indicating a legacy RO.

[0137] Example 2.11. The method of Example 2.10, further comprising transmitting, to the network apparatus, an additional CFRA request, after receiving, from the network apparatus, the dedicated RA configuration indicating a legacy RO.

[0138] Example 2.12. The method of Example 2.11, wherein the additional CFRA request includes the first set of preambles.

[0139] Example 2.13. The method of any of Examples 2.11-2.12, wherein the additional CFRA request includes the legacy RO.

[0140] Example 2.14. The method of Example 2.13, wherein the additional CFRA request includes the first set of preambles.

[0141] Example 2.15. The method of Example 2.14, wherein the first set of preambles includes at least one of a dedicated preamble for each Synchronization Signal / Physical Broadcast Channel (SS / PBCH) Block beam or a dedicated preamble for each Channel State Information (CSI) Reference Signal beam.

[0142] Example 2.16. The method of any of Examples 2.10-2.15, wherein each request of the plurality of CFRA requests including the first set of preambles and the SBFD RO is unsuccessful.

[0143] Example 2.17. The method of any of Examples 2.10-2.16, wherein the apparatus is a SBFD-aware apparatus.

[0144] Example 2.18. The method of any of Examples 2.10-2.17, wherein the apparatus is a user equipment (UE).

[0145] Example 2.19. A method in a network apparatus, comprising:transmitting, to a user equipment (UE), a dedicated random access (RA) configuration indicating a sub-band non-overlapping full duplex (SBFD) physical random-access channel occasion (RO);receiving, from the UE, a plurality of contention-free random access (CFRA) requests including a first set of preambles and the SBFD RO, wherein each request of the plurality of CFRA requests including the first set of preambles and the SBFD RO is unsuccessful;transmitting, to the UE, the dedicated RA configuration indicating a legacy RO; and receiving, from the UE, a CFRA request including the first set of preambles and the legacy RO.

[0146] Example 2.20. The method of Example 2.19, further comprising receiving, from the UE, an additional CFRA request, after receiving, from the network apparatus, the dedicated RA configuration indicating a legacy RO.

[0147] Example 2.21. The method of Example 2.20, wherein the additional CFRA request includes the first set of preambles.

[0148] Example 2.22. The method of any of Examples 2.20-2.21, wherein the additional CFRA request includes the legacy RO.

[0149] Example 2.23. The method of Example 2.22, wherein the additional CFRA request includes the first set of preambles.

[0150] Example 2.24. The method of Example 2.23, wherein the first set of preambles includes at least one of a dedicated preamble for each Synchronization Signal / Physical BroadcastChannel (SS / PBCH) Block beam or a dedicated preamble for each Channel State Information (CSI) Reference Signal beam.

[0151] Example 2.25. The method of any of Examples 2.19-2.24, wherein each request of the plurality of CFRA requests including the first set of preambles and the SBFD RO is unsuccessful.

[0152] Example 2.26. The method of any of Examples 2.19-2.25, wherein the apparatus is a SBFD-aware apparatus.

[0153] Example 2.27. The method of any of Examples 2.19-2.26, wherein the apparatus is a user equipment (UE).

[0154] Example 3.1. An apparatus comprising:at least one processor; andat least one memory storing instructions which, when executed by the at least one processor, causes the apparatus to perform a method including:receiving, from a network apparatus, a dedicated random access (RA) configuration indicating a first type of physical random-access channel occasion (RO), a sub-band nonoverlapping full duplex (SBFD) counter, and a legacy counter; andtransmitting, to the network apparatus, a number of contention-free random access (CFRA) requests including a first set of preambles and the first type of RO, wherein the number of CFRA requests is based on one of the SBFD counter or the legacy counter.

[0155] Example 3.2. The apparatus of Example 3.1, further comprising transmitting, to the network apparatus, a number of CFRA requests including the second type RO.

[0156] Example 3.3. The apparatus of Example 3.2, wherein the number of CFRA requests including the second type of RO also includes the first set of preambles.

[0157] Example 3.4. The apparatus of Example 3.3, wherein the first set of preambles includes at least one of a dedicated preamble for each Synchronization Signal / Physical Broadcast Channel (SS / PBCH) Block beam or a dedicated preamble for each Channel State Information (CSI) Reference Signal beam.

[0158] Example 3.5. The apparatus of Example 3.2, wherein the second type of RO is a legacy RO, and wherein the number of CFRA requests including the second type of RO, a maximum amount of CFRA requests is based on the legacy counter.

[0159] Example 3.6. The apparatus of Example 3.3, wherein the second type of RO is a legacy RO, and wherein the number of CFRA requests including the second type RO, a maximum amount of CFRA requests is based on the legacy counter.

[0160] Example 3.7. The apparatus of any of Examples 3.1-3.6, wherein each request of the number of CFRA requests including the first set of preambles and the first type of RO is unsuccessful.

[0161] Example 3.8. The apparatus of any of Examples 3.1-3.7, wherein the first type of RO is a SBFD RO.

[0162] Example 3.9. The apparatus of Example 3.8, wherein the second type of RO is a legacy RO.

[0163] Example 3.10. The apparatus of any of Examples 3.1-3.9, wherein the apparatus is a SBFD-aware apparatus.

[0164] Example 3.11. The apparatus of any of Examples 3.1-3.10, wherein the apparatus is a user equipment (UE).

[0165] Example 3.12. A method in a user equipment (UE), comprising:receiving, from a network apparatus, a dedicated random access (RA) configuration indicating a first type of physical random-access channel occasion (RO);transmitting, to the network apparatus, a number of contention-free random access (CFRA) requests including a first set of preambles and the first type of RO, wherein the number of CFRA requests is based on a sub-band non-overlapping full duplex (SBFD)counter; andreceiving, from the network apparatus, the dedicated RA configuration indicating a second type of RO.

[0166] Example 3.13 The method of Example 3.12, further comprising transmitting, to the network apparatus, a number of CFRA requests including the second type RO.

[0167] Example 3.14. The method of Example 3.13, wherein the number of CFRA requests including the second type of RO also includes the first set of preambles.

[0168] Example 3.15. The method of Example 3.14, wherein the first set of preambles includes at least one of a dedicated preamble for each Synchronization Signal / Physical Broadcast Channel (SS / PBCH) Block beam or a dedicated preamble for each Channel State Information (CSI) Reference Signal beam.

[0169] Example 3.16. The method of Example 3.13, wherein the second type of RO is a legacy RO, and wherein the number of CFRA requests including the second type of RO, a maximum amount of CFRA requests is based on the legacy counter.

[0170] Example 3.17. The method of Example 3.14, wherein the second type of RO is a legacy RO, and wherein the number of CFRA requests including the second type RO, a maximum amount of CFRA requests is based on the legacy counter.

[0171] Example 3.18. The method of any of Examples 3.12-3.17, wherein each request of the number of CFRA requests including the first set of preambles and the first type of RO is unsuccessful.

[0172] Example 3.19. The method of any of Examples 3.12-3.18, wherein the first type of RO is a SBFD RO.

[0173] Example 3.20. The method of Example 3.19, wherein the second type of RO is a legacy RO.

[0174] Example 3.21. The method of any of Examples 3.12-3.20, wherein the apparatus is a SBFD-aware apparatus.

[0175] Example 3.22. The method of any of Examples 3.12-3.21, wherein the apparatus is a user equipment (UE).

[0176] Example 3.23. A method in a network apparatus, comprising:transmitting, to a user equipment (UE), a dedicated random access (RA) configuration indicating a first type of physical random-access channel occasion (RO);receiving, from the UE, a number of contention-free random access (CFRA) requests including a first set of preambles and the first type of RO, wherein the number of CFRA requests is based on a sub-band non-overlapping full duplex (SBFD) counter;transmitting, to the UE, the dedicated RA configuration indicating a second type of RO; and receiving, from the UE, a number of CFRA requests including the second type of RO.

[0177] Example 3.24. The method of Example 3.23, further comprising receiving, from the UE, a number of CFRA requests including the second type RO.

[0178] Example 3.25. The method of Example 3.24, wherein the number of CFRA requests including the second type of RO also includes the first set of preambles.

[0179] Example 3.26. The method of Example 3.25, wherein the first set of preambles includes at least one of a dedicated preamble for each Synchronization Signal / Physical Broadcast Channel (SS / PBCH) Block beam or a dedicated preamble for each Channel State Information (CSI) Reference Signal beam.

[0180] Example 3.27. The method of Example 3.24, wherein the second type of RO is a legacy RO, and wherein the number of CFRA requests including the second type of RO, a maximum amount of CFRA requests is based on the legacy counter.

[0181] Example 3.28. The method of Example 3.15, wherein the second type of RO is a legacy RO, and wherein the number of CFRA requests including the second type RO, a maximum amount of CFRA requests is based on the legacy counter.

[0182] Example 3.29. The method of any of Examples 3.23-3.28, wherein each request of the number of CFRA requests including the first set of preambles and the first type of RO is unsuccessful.

[0183] Example 3.30. The method of any of Examples 3.23-3.29, wherein the first type of RO is a SBFD RO.

[0184] Example 3.31. The method of Example 3.30, wherein the second type of RO is a legacy RO.

[0185] Example 3.32. The method of any of Examples 3.23-3.31, wherein the apparatus is a SBFD-aware apparatus.

[0186] Example 3.33. The method of any of Examples 3.23-3.32, wherein the apparatus is a user equipment (UE).

[0187] Example 4.1. An apparatus comprising:at least one processor; andat least one memory storing instructions which, when executed by the at least one processor, causes the apparatus to perform a method including:receiving, from a network apparatus, a dedicated random access (RA) configuration indicating a first type of physical random-access channel occasion (RO);transmitting, to the network apparatus, a number of contention-free random access (CFRA) requests including a first set of preambles and the first type of RO, and transmitting, to the network apparatus, a contention-based random access (CBRA) request.

[0188] Example 4.2. The apparatus of Example 4.1, wherein the first type of RO is a subband non-overlapping full duplex (SBFD) RO, and wherein the number of CFRA requests is based on a SBFD counter.

[0189] Example 4.3. The apparatus of any of Examples 4.1-4.2, wherein the first type of RO is a legacy RO, and wherein the number of CFRA requests is based on a legacy counter.

[0190] Example 4.4. The apparatus of any of Examples 4.1-4.3, wherein the CBRA request includes a randomly selected set of preambles.

[0191] Example 4.5. The apparatus of any of Examples 4.1-4.4, wherein the CBRA request includes a second type of RO.

[0192] Example 4.6. The apparatus of any of Examples 4.1-4.5, wherein the method further comprises marking the first type of RO as invalid.

[0193] Example 4.7. The apparatus of any of Examples 4.1-4.6, wherein each request of the number of CFRA requests including the first set of preambles and the first type of RO is unsuccessful.

[0194] Example 4.8. The apparatus of any of Examples 4.1-4.7, wherein the first type of RO is a SBFD RO.

[0195] Example 4.9. The apparatus of Example 4.8, wherein the CBRA request includes a second type of RO, and wherein the second type of RO is a legacy RO.

[0196] Example 4.10. The apparatus of any of Examples 4.1-4.9, wherein the apparatus is a user equipment (UE).

[0197] Example 4.11 A method in a user equipment (UE), comprising:receiving, from a network apparatus, a dedicated random access (RA) configuration indicating a first type of physical random-access channel occasion (RO);transmitting, to the network apparatus, a number of contention-free random access (CFRA) requests including a first set of preambles and the first type of RO; andtransmitting, to the network apparatus, a contention-based random access (CBRA) request.

[0198] Example 4.12. The method of Example 4.11, wherein the first type of RO is a subband non-overlapping full duplex (SBFD) RO, and wherein the number of CFRA requests is based on a SBFD counter.

[0199] Example 4.13. The method of any of Examples 4.11-4.12, wherein the first type of RO is a legacy RO, and wherein the number of CFRA requests is based on a legacy counter.

[0200] Example 4.14. The method of any of Examples 4.11-4.13, wherein the CBRA request includes a randomly selected set of preambles.

[0201] Example 4.15. The method of any of Examples 4.11-4.14, wherein the CBRA request includes a second type of RO.

[0202] Example 4.16. The method of any of Examples 4.11-4.15, wherein the method further comprises marking the first type of RO as invalid.

[0203] Example 4.17. The method of any of Examples 4.11-4.16, wherein each request of the number of CFRA requests including the first set of preambles and the first type of RO is unsuccessful.

[0204] Example 4.18. The method of any of Examples 4.11-4.17, wherein the first type of RO is a SBFD RO.

[0205] Example 4.19. The method of Example 4.18, wherein the CBRA request includes a second type of RO, and wherein the second type of RO is a legacy RO.

[0206] Example 4.20. The method of any of Examples 4.11-4.19, wherein the apparatus is a user equipment (UE).

[0207] Example 4.21. A method in a network apparatus, comprising:transmitting, to a user equipment (UE), a dedicated random access (RA) configuration indicating a first type of physical random-access channel occasion (RO); andreceiving, from the UE, a number of contention-free random access (CFRA) requests including a first set of preambles and the first type of RO;receiving, from the UE, a contention-based random access (CBRA) request including a second type of RO.

[0208] Example 4.22. The method of Example 4.21, wherein the first type of RO is a subband non-overlapping full duplex (SBFD) RO, and wherein the number of CFRA requests is based on a SBFD counter.

[0209] Example 4.23. The method of any of Examples 4.21-4.22, wherein the first type of RO is a legacy RO, and wherein the number of CFRA requests is based on a legacy counter.

[0210] Example 4.24. The method of any of Examples 4.21-4.23, wherein the CBRA request includes a randomly selected set of preambles.

[0211] Example 4.25. The method of any of Examples 4.21-4.24, wherein the CBRA request includes a second type of RO.

[0212] Example 4.26. The method of any of Examples 4.21-4.25, wherein the method further comprises marking the first type of RO as invalid.

[0213] Example 4.27. The method of any of Examples 4.21-4.26, wherein each request of the number of CFRA requests including the first set of preambles and the first type of RO is unsuccessful.

[0214] Example 4.28. The method of any of Examples 4.21-4.27, wherein the first type of RO is a SBFD RO.

[0215] Example 4.29. The method of Example 4.28, wherein the CBRA request includes a second type of RO, and wherein the second type of RO is a legacy RO.

[0216] Example 4.30. The method of any of Examples 4.21-4.29, wherein the apparatus is a user equipment (UE).

[0217] The embodiments and aspects disclosed herein are examples of the present disclosure and may be embodied in various forms. For instance, although certain aspects herein are described as separate aspects, each of the aspects herein may be combined with one or more of the other aspects herein. Specific structural and functional details disclosed herein are not to be interpreted as limiting, but as a basis for the claims and as a representative basis for teaching one skilled in the art to variously employ the present disclosure in virtually any appropriately detailed structure. Like reference numerals may refer to similar or identical elements throughout the description of the figures.

[0218] The phrases “in an aspect,” “in aspects,” “in various aspects,” “in some aspects,” or “in other aspects” may each refer to one or more of the same or different aspects in accordance with this present disclosure. The phrase “a plurality of’ may refer to two or more.

[0219] The phrases “in an embodiment,” “in embodiments,” “in various embodiments,” “in some embodiments,” or “in other embodiments” may each refer to one or more of the same or different embodiments in accordance with the present disclosure. A phrase in the form “A or B” means “(A), (B), or (A and B) ” A phrase in the form “at least one of A, B, or C” means “(A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C) .”

[0220] Any of the herein described methods, programs, algorithms or codes may be converted to, or expressed in, a programming language or computer program. The terms “programming language” and “computer program,” as used herein, each include any language used to specify instructions to a computer, and include (but is not limited to) the following languages and their derivatives: Assembler, Basic, Batch files, BCPL, C, C+, C++, Delphi, Fortran, Java, JavaScript, machine code, operating system command languages, Pascal, Perl, PL1, Python, scripting languages, Visual Basic,metalanguages which themselves specify programs, and all first, second, third, fourth, fifth, or further generation computer languages. Also included are database and other data schemas, and any other meta-languages. No distinction is made between languages which are interpreted, compiled, or use both compiled and interpreted approaches. No distinction is made between compiled and source versions of a program. Thus, reference to a program, where the programming language could exist in more than one state (such as source, compiled, object, or linked) is a reference to any and all such states. Reference to a program may encompass the actual instructions and / or the intent of those instructions.

[0221] While aspects of the present disclosure have been shown in the drawings, it is not intended that the present disclosure be limited thereto, as it is intended that the present disclosure be as broad in scope as the art will allow and that the specification be read likewise. Therefore, the above description should not be construed as limiting, but merely as exemplifications of particular aspects. Those skilled in the art will envision other modifications within the scope and spirit of the claims appended hereto.

Claims

WHAT IS CLAIMED IS:

1. An apparatus comprising:at least one processor; andat least one memory storing instructions which, when executed by the at least one processor, causes the apparatus to perform a method including:receiving, from a network apparatus, a dedicated random access (RA) configuration indicating a first type of physical random-access channel occasion (RO);transmitting, to the network apparatus, a plurality of contention-free random access (CFRA) requests including a first set of preambles and the first type of RO; and receiving, from the network apparatus, the dedicated RA configuration indicating a second type of RO.

2. The apparatus according to claim 1, wherein the method further comprises transmitting, to the network apparatus, a request including the first set of preambles and the second type of RO after receiving, from the network apparatus, the dedicated RA configuration indicating the second type of RO.

3. The apparatus according to claim 2, wherein the request including the first set of preambles and the second type of RO is a CFRA request.

4. The apparatus according to claim 1, wherein the method further comprises transmitting, to the network apparatus, an additional CFRA request after receiving, from the network apparatus, the dedicated RA configuration indicating the second type of RO.

5. The apparatus according to any one of claims 1 to 4, wherein the first type of RO is a sub-band non-overlapping full duplex (SBFD) RO.

6. The apparatus according to any one of claims 1 to 5, wherein the second type of RO is a legacy RO.

7. The apparatus according to any one of claim 1 to 6, wherein the method further comprises transmitting, to the network apparatus, an additional CFRA request including the first set of preambles and the second type of RO after receiving, from the network apparatus, the dedicated RA configuration indicating the second type of RO.

278. The apparatus according to any one of claims 1 to 7, wherein the plurality of requests of the CFRA requests exceeds a reference signal received power (RSRP) threshold.

9. The apparatus according to any one of claims 1 to 8, wherein each request of the plurality of CFRA requests including the first set of preambles and the first type of RO is unsuccessful.

10. The apparatus according to any one of claims 1 to 9, wherein the apparatus is a SBFD-aware apparatus.

11. The apparatus according to any one of claims 1 to 10, wherein the apparatus is a user equipment (UE).

12. A method in a user equipment (UE), comprising:receiving, from a network apparatus, a dedicated random access (RA) configuration indicating a first type of physical random-access channel occasion (RO);transmitting, to the network apparatus, a plurality of contention-free random access (CFRA) requests including a first set of preambles and the first type of RO; andreceiving, from the network apparatus, the dedicated RA configuration indicating a second type of RO.

13. A method in a network apparatus, comprising:transmitting, to a user equipment (UE), a dedicated random access (RA) configuration indicating a first type of physical random-access channel occasion (RO);receiving, from the UE, a plurality of contention-free random access (CFRA) requests including a first set of preambles and the first type of RO;transmitting, to the UE, the dedicated RA configuration indicating a second type of RO; and receiving, from the UE, a CFRA request including the first set of preambles and the second type of RO.

Images