Fallback procedure between user equipment and network apparatus

Abstract

This application relates to a fallback process between a user equipment and a network device. An apparatus includes at least one processor and at least one memory storing instructions. When executed by the at least one processor, the instructions in the at least one memory cause the apparatus to perform a method comprising: receiving from the network device a Dedicated Random Access (RA) configuration indicating a first type of Physical Random Access Channel (RO); sending to the network device a number of Contention-Free Random Access (CFRA) requests, the number of CFRA requests including a first preamble set and the first type of RO; and sending to the network device a Contention-Based Random Access (CBRA) request.

Description

Technical Field

[0001] Various examples relate to the efficient transmission of information, and more specifically, to the efficient transmission of information between user equipment (UE) and network devices. Background Technology

[0002] Wireless networking offers significant advantages to user mobility. The ability to maintain connectivity while on the move not only provides advantages for users but also contributes to greater efficiency and productivity for society as a whole. As expectations for connection reliability, data speed, and lower power consumption increase, the technologies used in wireless networks must keep pace. Therefore, there is ongoing interest in improving wireless networking technologies. Summary of the Invention

[0003] According to various aspects of this 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 in the at least one memory cause the apparatus to perform a method comprising: receiving from a network device a Dedicated Random Access (RA) configuration indicating a first type of Physical Random Access Channel (RO); sending to the network device a number of Contention-Free Random Access (CFRA) requests, the number of CFRA requests including a first preamble set and the first type of RO; and sending to the network device a Contention-Based Random Access (CBRA) request.

[0004] On one hand, the first type of RO is a subband non-overlapping full-duplex (SBFD) RO, and the number of CFRA requests is based on the SBFD counter.

[0005] On the one hand, the first type of RO is the traditional RO, and the number of CFRA requests is based on a traditional counter.

[0006] On one hand, a CBRA request includes a randomly selected set of preambles.

[0007] On the one hand, CBRA requests include a second type of RO.

[0008] In one aspect, the method also includes marking the first type of RO as invalid.

[0009] On one hand, each of the number of CFRA requests, including the first preamble set and the first type of RO, is unsuccessful.

[0010] On one hand, the first type of RO is SBFD RO.

[0011] On the one hand, the second type of RO is traditional RO.

[0012] In one respect, the device is a user equipment (UE).

[0013] According to various aspects of this disclosure, a method in a user equipment (UE) includes: receiving from a network device a dedicated random access (RA) configuration indicating a physical random access channel timing (RO) of a first type; sending to the network device a number of contention-free random access (CFRA) requests, the number of CFRA requests including a first preamble set and the first type of RO; and sending to the network device a contention-based random access (CBRA) request.

[0014] According to various aspects of this disclosure, a method in a network apparatus includes: sending a Dedicated Random Access (RA) configuration to a User Equipment (UE) indicating a Physical Random Access Channel (RO) timing of a first type; receiving from the UE a number of Contention-Free Random Access (CFRA) requests, the number of CFRA requests including a first preamble set and a first type of RO; and receiving from the UE a Contention-Based Random Access (CBRA) request including a second type of RO.

[0015] The independent claims provide the subject matter for several aspects. Additional aspects are defined in the dependent claims. Attached Figure Description

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

[0017] Figure 1 This is a diagram illustrating an example aspect of wireless networking between a network system and a user equipment (UE) according to one aspect of this disclosure; Figure 2 This is a diagram of an example component of a network system according to one aspect of this disclosure; Figure 3 This is a diagram illustrating an example aspect of a contention-based random access procedure according to one aspect of this disclosure; Figure 4 This is a flowchart illustrating an example of communication between a UE and a network device according to one aspect of this disclosure; Figure 5 This is a flowchart illustrating another example of communication between a UE and a network device according to one aspect of this disclosure; Figure 6 This is a flowchart illustrating other examples of communication between a UE and a network device according to various aspects of this disclosure; Figure 7 This is an illustration of an example of a component of a user equipment or network device according to one aspect of this disclosure. Detailed Implementation

[0018] This disclosure relates to a fallback procedure used after an unsuccessful attempt to send or receive information. More specifically, this disclosure relates to apparatus and methods for employing a fallback procedure between a user equipment (UE) and a network apparatus after an unsuccessful attempt to send or receive a random access (RA) request.

[0019] In the following description, certain specific details are set forth in order to provide a thorough understanding of the disclosed aspects. However, those skilled in the art will recognize that the aspects can be practiced without one or more of these specific details or using 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 the description of the aspects.

[0020] Throughout this specification, references to "an aspect" or "one aspect" mean that a particular feature, structure, or characteristic described in connection with that aspect is included in at least one aspect. Therefore, the phrases "in an aspect" or "in one aspect" appearing in various places throughout this specification do not necessarily refer to the same aspect. Furthermore, a particular feature, structure, or characteristic may be combined in one or more aspects in any suitable manner.

[0021] The aspects described in this disclosure can be implemented in wireless networking devices, such as, but not limited to, devices utilizing Global Microwave Access Interoperability (WiMAX), Global System for Mobile Communications (GSM, 2G), GSM EDGE Radio Access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunications System based on Basic Wideband Code Division Multiple Access (W-CDMA) (UMTS, 3G), High-Speed ​​Packet Access (HSPA), Long Term Evolution (LTE), Advanced LTE, Enhanced LTE (eLTE), 5G New Radio (5G NR), 5G Advanced, 6G (and above), and 802.11ax (Wi-Fi 6), and other wireless networking systems. The term "eLTE" here refers to LTE evolution connected to a 5G core. LTE is also referred to as Evolved UMTS Terrestrial Radio Access (EUTRA) or Evolved UMTS Terrestrial Radio Access Network (EUTRAN).

[0022] This disclosure may use the term "serving network device" to refer to a network node or network device (or part thereof) serving a UE. As used herein, the terms "send toward," "send to," "receive from," and "cooperate with" (and variations thereof) include communication that may or may not involve communication via one or more intermediate devices or nodes. The term "acquire" (and variations thereof) includes acquiring in a first instance or reacquiring after a first instance. The term "connection" may refer to a physical connection or a logical connection.

[0023] This disclosure uses 5G NR as an example of a wireless network, and may use smartphones and / or extended reality headsets as examples of UEs. It is intended and should be understood that such examples are merely illustrative, and this disclosure applies to other wireless networks and user equipment.

[0024] Figure 1 This is a diagram illustrating an example of wireless networking between network system 100 and user equipment (UE) 150. Network system 100 may include one or more network nodes 120, one or more servers 110, and / or one or more network devices 130 (e.g., test equipment). Network node 120 will be described in more detail below. As used herein, the term "network apparatus" may refer to any component of network system 100, such as server 110, network node 120, network device 130, any of the foregoing components, and / or any other component of network system 100. Examples of network apparatus include, but are not limited to, apparatuses for implementing various aspects of 5G NR. This disclosure describes aspects related to 5G NR and aspects relating to aspects defined by the 3rd Generation Partnership Project (3GPP). However, aspects contemplated in relation to other wireless networking technologies are covered within the scope of this disclosure.

[0025] The following description provides further details of examples of network nodes. In a 5G NR network, a gNodeB (also known as a gNB) may include, for example, a node that provides the UE with New Radio (NR) user plane and control plane protocol termination and is connected to the 5G core (5GC) via an NG interface, such as, according to Section 3.2 of 3GPP TS 38.300 V 16.6.0 (2021-06), which is incorporated herein by reference.

[0026] gNB supports various protocol layers, such as Layer 1 (L1) - the physical layer, Layer 2 (L2) and Layer 3 (L3).

[0027] NR's Layer 2 (L2) is divided into the following sublayers: Media Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), and Service Data Adaptation Protocol (SDAP), among which, for example: ○ The physical layer provides a transmission channel to the MAC sublayer; ○ The MAC sublayer provides logical channels to the RLC sublayer; ○ The RLC sublayer provides RLC channels to the PDCP sublayer; ○ The PDCP sublayer provides radio bearers to the SDAP sublayer; ○ The SDAP sublayer provides Quality of Service (QoS) flows to 5GC; ○ The control channels include the Broadcast Control Channel (BCCH) and the Physical Control Channel (PCCH).

[0028] Layer 3 (L3) includes, for example, Radio Resource Control (RRC) according to Section 6 of 3GPP TS 38.300 V16.6.0 (2021-06), which is incorporated herein by reference.

[0029] The gNB Central Unit (gNB-CU) comprises, for example, a logical node that hosts, the radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) of the gNB, or the RRC and PDCP protocols of the en-gNB, and controls the operation of one or more gNB Distributed Units (gNB-DUs). The gNB-CU terminates the F1 interface connected to the gNB-DU. The gNB-CU may also be referred to herein as a CU, central unit, centralized unit, or control unit.

[0030] A gNB Distributed Unit (gNB-DU) comprises, for example, a logical node that hosts the Radio Link Control (RLC), Media Access Control (MAC), and Physical (PHY) layers of a gNB or en-gNB, and its operation is partially controlled by the gNB-CU. A gNB-DU supports one or more cells. A cell is supported by only one gNB-DU. The gNB-DU terminates the F1 interface connected to the gNB-CU. The gNB-DU may also be referred to herein as a DU or Distributed Unit.

[0031] The gNB-CU-Control Plane (gNB-CU-CP) includes, for example, logical nodes that host the RRC and control plane portion of the PDCP protocol for the gNB-CU, such as for the en-gNB or gNB. The gNB-CU-CP terminates the E1 interface connected to the gNB-CU-User Plane (gNB-CU-UP) and the F1-C interface connected to the gNB-DU.

[0032] The gNB-CU-User Plane (gNB-CU-UP) includes, for example, the user plane portion of the gNB-CU that hosts the PDCP protocol for the en-gNB, and the user plane portions of the PDCP and SDAP protocols for the gNB-CU. The gNB-CU-UP terminates the E1 interface connected to the gNB-CU-CP and the F1-U interface connected to the gNB-DU, for example, according to Section 3.1 of 3GPPTS 38.401 V16.6.0 (2021-07), which is incorporated herein by reference.

[0033] As used herein, the term "network node" may refer to any one or any combination of gNB, gNB-CU, gNB-DU, gNB-CU-CP, or gNB-CU-UP.

[0034] RAN (Radio Access Network) nodes or network nodes (such as gNB, gNB-CU, or gNB-DU, or portions thereof) can be implemented using means, for example, having at least one processor and / or at least one memory having processor-readable instructions (“programs”) configured to support and / or provide and / or process CU and / or DU-related functionalities and / or features, and / or at least one protocol (sub)layer (e.g., layer 2 and / or layer 3) of the RAN (Radio Access Network). Different functional divisions between central and distributed units are possible. The following will combine... Figure 4 Examples describing such devices and components.

[0035] The gNB-CU and gNB-DU portions can be co-located or physically separated, for example. The gNB-DU can even be further divided into, for example, two parts, one including processing equipment and the other including an antenna. The Central Unit (CU) can also be referred to as a Baseband Unit / Radio Equipment Controller / Cloud-RAN / Virtual-RAN (BBU / REC / C-RAN / V-RAN), Open RAN (O-RAN), or a portion thereof. The Distributed Unit (DU) can also be referred to as a Remote Radio Head / Remote Radio Unit / Radio Equipment / Radio Unit (RRH / RRU / RE / RU), or a portion thereof. In the various examples of this disclosure below, a network node supporting at least one of the Central Unit functions or Layer 3 protocols of a radio access network can be, for example, a gNB-CU. Similarly, a network node supporting at least one of the Distributed Unit functions or Layer 2 protocols of a radio access network can be, for example, a gNB-DU.

[0036] A gNB-CU can support one or more gNB-DUs. A gNB-DU can support one or more cells, and therefore can support the serving cell for a user equipment (UE), or candidate cells for handover, dual connectivity and / or carrier aggregation and other procedures.

[0037] User equipment (UE) 150 may be or include wireless or mobile devices, devices having a radio interface for interacting with a RAN (Radio Access Network), smartphones, in-vehicle devices, IoT devices, or M2M devices, and other types of user equipment. Such a UE 150 may include: at least one processor; and at least one memory including program code; wherein the at least one memory and the computer program code are configured, together with the at least one processor, to enable the device to perform at least certain operations, such as an RRC connection to the RAN. Figure 4 Examples of components of the UE are described below. In various aspects, UE 150 can be configured to generate messages to be transmitted to the RAN via radio (e.g., including a cell ID) (e.g., to reach and communicate with the serving cell). In various aspects, UE 150 can generate, transmit, and receive RRC messages containing one or more RRC PDUs (Packet Data Units). Those skilled in the art will understand the RRC protocol and other processes that the UE can perform.

[0038] Continue to refer to Figure 1 In the example of a 5G NR network, network system 100 provides one or more cells that define the coverage area of ​​network system 100. As described above, network system 100 may include a gNB of the 5G NR network, or may include any other means configured to control radio communications and manage radio resources within the cell. As used herein, the term "resource" may refer to radio resources such as resource blocks (RBs), physical resource blocks (PRBs), radio frames, subframes, time slots, subbands, frequency regions, subcarriers, beams, etc. In all aspects, network node 120 may be referred to as a base station.

[0039] Figure 1 Examples are provided, and only network system 100 and UE 150 are shown. Those skilled in the art will understand that network system 100 includes... Figure 1 Components not shown in the diagram, and it will be understood that other user equipment can communicate with network system 100.

[0040] Figure 2 yes Figure 1 A block diagram of example components of network system 100. A 5G NR network can be described as an example of network system 100, and the aspects described below should also be applicable to other types of network systems. The network system can be configured according to... Figure 1The signals and connections shown operate to enable UE 150 to communicate with network system 100 via radio access network (RAN) 225. Additionally, the network system can be divided into user plane components and functions and control plane components and functions, as shown and described herein. Unless otherwise stated, the terms “component,” “function,” and “service” are used interchangeably herein and can refer to instructions executed by and implemented by one or more processors.

[0041] The following describes example functionality of the components. This example functionality is merely illustrative, and it should be understood that additional operations and functions can be performed by the components described herein. Furthermore, connections between components can be virtual connections based on service interfaces, allowing any component to communicate with any other component. In this way, any component can act as a service "producer" for any other component acting as a service "consumer," providing services for network functions.

[0042] 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 Open Function (NEF) 215, a Network Repository Function (NRF) 216, and a Unified Data Management Function (UDM) 217, which may include a Unified Data Repository (UDR) 224.

[0043] Additional components and functions of the core network 210 may include application functions (AF) 218, policy control functions (PCF) 219, network data analysis functions (NWDAF) 220, analytical data repository functions (ADRF) 221, management data analysis functions (MDAF) 222, and operation and management functions (OAM) 223.

[0044] The user plane includes UE 150, Radio Access Network (RAN) 225, User Plane Function (UPF) 226, and Data Network (DN) 227. RAN 225 may include a combination of Figure 1 The RAN 225 describes one or more components, such as one or more network nodes. However, the RAN 225 may not be limited to such components. The UPF 226 provides connectivity for data transmitted through the RAN 225. For example, the UPF 226 identifies service providers, internet access, and third-party services.

[0045] AMF 212 handles connectivity and mobility tasks. AUSF 211 receives authentication requests from AMF 212 and interacts with UDM 217 to authenticate and verify network responses to determine successful authentication. SMF 213 performs Packet Data Unit (PDU) session management and manages session context with UPF 226.

[0046] NSSF 214 can select a Network Slice Instance (NSI) and determine the allowed Network Slice Selection Assistance Information (NSSAI). This selection and determination are used to set up AMF 212 to provide services to UE 150. NEF 215 ensures third-party access to network services to create private network services. NRF 216 acts as a repository for storing network functions to allow functions to register and discover each other.

[0047] UDM 217 generates authentication vectors for use by AUSF 211 and AMF 212 and provides user identity processing. UDM 217 can connect to UDR 224, which stores data associated with authentication, applications, etc. AF 218 provides application services (e.g., streaming services) to users. PCF 219 provides policy control functions. For example, PCF 219 can assist in network slicing and mobility management, as well as provide Quality of Service (QoS) and accounting functions.

[0048] NWDAF 220 collects data (e.g., from UE 150 and network systems) to perform network analytics and provide insights into the capabilities that leverage analytics when providing services. ADRF 221 allows consumers to store, retrieve, and remove data and analytics. MDAF 222 provides additional data analytics services for network functions. OAM 223 provides provisioning and management processing capabilities to manage network elements or components connected to the network (e.g., UE 150, network nodes, etc.).

[0049] Figure 2 This is merely an example of components of a network system, and variations are expected within the scope of this disclosure. In various respects, the network system may include... Figure 2 Other components not shown. In various aspects, the network system may not include... Figure 2 Each component is shown. In various aspects, components and connections can be used with... Figure 2 The connections shown are implemented using different connections. These and other aspects are considered to be within the scope of this disclosure.

[0050] The process by which a UE establishes communication with a target cell is called a random access procedure. Random access procedures can be used for initial access, inactive small data transmissions and the transition from RRC_Inactive to RRC_Connected, as well as for beam fault recovery, connection reconstruction, handover and cell addition, and other procedures that those skilled in the art will recognize.

[0051] There are two types of random access procedures: contention-based random access (CBRA) and contention-free random access (CFRA). Figure 3 This is a diagram illustrating an example of a contention-based random access (CBRA) procedure. In the example shown, these signals include a random access preamble (MSG1) sent by UE 350 to network node 310 (e.g., gNodeB or a portion thereof), a random access response (MSG2) sent from network node 310 to UE 350, a scheduling transport (MSG3) sent from UE 350 to network node 310, and a contention resolution (MSG4) sent from network node 310 to UE 350.

[0052] For MSG1, UE 350 selects the available random access preamble based on information elements in the Signal Synchronization Block (SSB). UE 350 sends the random access preamble (MSG1) to network node 310 using a specific time and frequency resource called the Random Access Opportunity (RO). UE 350 also provides the network with an identifier called the Random Access Radio Network Temporary Identifier (RA-RNTI), which allows the network to address it in the next step.

[0053] For MSG2, network node 310 detects the preamble, calculates various quantities, and sends a Physical Uplink Shared Channel (PUSCH) Uplink (UL) grant to UE 350. This is called a Random Access Response (RAR), which is sent as MSG2 addressed to UE 350 with the relevant RA-RNTI, and instructs UE 350 where and when it can send MSG3 on the PUSCH in terms of frequency and time.

[0054] For MSG3, in response to receiving MSG2 from network node 310, UE 350 uses the UL authorization provided in the RAR to send MSG3. Because the RAR provides time resource allocation, UE 350 sends MSG3 to network node 310 at the time specified by the time resource allocation, and it is a scheduled transmission. This MSG3 can be referred to as a Radio Resource Control (RRC) Connection Request message.

[0055] For MSG4, network node 310 can send MSG4 to UE 350 for contention-based resolution. Contention-based resolution can operate in the manner specified by 3GPP for 5G NR. After the random access procedure, assuming the contention-based resolution is favorable, UE 350 becomes connected to network node 310. After connection establishment, various procedures will be handled by gNB-CU according to CU-DU splitting. Other aspects of contention-based random access (CBRA) will be understood by those skilled in the art.

[0056] Another type of random access procedure is Contention-Free Random Access (CFRA) (not shown). In CFRA (not shown), network node 310 sends the assigned random access preamble to UE 350. UE 350 receives the assigned random access preamble and sends it as MSG1 to network node 310 in its random access request. MSG2 and MSG3 are then similar to those described in conjunction with CBRA. Based on the use of the assigned random access preamble, no contention resolution is required in CFRA. Other aspects of Contention-Free Random Access (CFRA) will be understood by those skilled in the art.

[0057] As described above, according to various aspects of this disclosure, this disclosure relates to various methods for determining whether an active time period in a beam transmitted by the network has a sufficiently long duration for the UE to receive any or all random access responses (RARs) from the network.

[0058] Typically, when a UE sends a Random Access Preamble (RAR) to the network, the UE either receives the RAR from the network or fails to receive it. If the UE does not receive the RAR from the network, it can send another RAR. This process can continue until the UE receives the RAR from the network, which may result in wasted time and energy. As used herein, according to various aspects of this disclosure, a "preamble" includes a set of preambles.

[0059] As used herein, the term "S-beam" refers to a satellite beam coverage area, which is a radio beam transmitted by a satellite, and can correspond to a full cell, a partial cell, or an NR beam. The term "NR beam" refers to a beam as described in the context of the 3GPP NR system. For example, an NR cell can be divided into multiple NR beams.

[0060] In radio access networks (RANs), different standards are used to implement and facilitate wireless communication. One such standard includes a requirement that, when using a contention-free random access (CFRA) procedure, the network device will indicate the type of physical random access channel timing (RO) to be used by the SBFD-aware user equipment (UE) (subband non-overlapping full-duplex (SBFD) or conventional RO). The standard also states support for two options in a cell-only random access channel (RACH) configuration: 1) RACH configuration option 1 with Alt 1-1; or 2) RACH configuration option 2. Under this standard, if a specific RO type is indicated to the SBFD UE, and random access (RA) fails after a maximum number of attempts (as indicated in the RO type), the random access will be declared unsuccessful. However, if the UE is SBFD-aware or SBFD-capable, it may also be beneficial for the UE to attempt an RA in another RO type, as the collision and interference levels on the other RO type may differ. For example, the following aspects and examples consider a process for falling back from an RO type to another RA type, and also consider a scenario for falling back from a CFRA to a contention-based random access (CBRA).

[0061] Now refer to Figures 4 to 6 The diagram illustrates flowcharts illustrating various examples of communication between a device (e.g., a UE) including at least one processor and at least one memory, and a network device according to various aspects of this disclosure. In some cases, communication between the network device and the user equipment (UE) fails for various reasons. In these cases, attempts to achieve successful communication between the network device and the UE can continue. Figures 4 to 6 The flowcharts in the document illustrate different examples of fallback procedures for continuing attempts at successful communication between a network device and a UE, according to various aspects of this disclosure.

[0062] For details, please refer to the following: Figure 4 This illustrates the first aspect of the fallback process. Here, operation 400 indicates that the UE is in a connected state with a network device (identified as "NW" in several figures). In the aspect shown, the UE is a sub-band non-overlapping full-duplex (SBFD) sensing device. Operation 410 shows the network device sending a dedicated random access (RA) configuration (e.g., "RACH-ConfigDedicated") to the UE, and the UE receiving it, which indicates a first type of physical random access channel timing (RO) (e.g., SBFDRO).

[0063] At operation 420, the UE sends multiple contention-free random access (CFRA) requests to the network device using a first type of RO (i.e., SBFD RO). The network device receives multiple contention-free random access (CFRA) requests from the UE using the first type of RO. In each aspect, the requests in operation 420 include a first preamble. Furthermore, operation 420 indicates that the number of requests made is defined as "preambleTransMax" in the preamble. In each aspect, the number of requests made meets or exceeds a Reference Signal Received Power (RSRP) threshold.

[0064] like Figure 4 As shown, multiple CFRA requests failed. That is, even after the UE has performed the maximum number of CFRA requests (e.g., as defined in the preamble), the transmission failed for at least one of a variety of reasons; the network device did not receive any CFRA requests.

[0065] At operation 430, the network device sends a 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 traditional RO) to the UE. The UE receives the dedicated RA configuration indicating the second type of RO from the network device.

[0066] At operation 440, the UE sends at least one request (e.g., a CFRA request) to the network device, including a first preamble and a second type of RO (i.e., a conventional RO). The network device receives at least one request from the UE, including the first preamble and the second type of RO. Furthermore, operation 440 indicates that the maximum number of requests made is defined as "preambleTransMax" in the preamble.

[0067] Figure 4 The operations described herein are merely illustrative, and variations may be considered within the scope of this disclosure. In various aspects, the operations may include... Figure 4 Other operations not shown. Operations may not be included in any aspect. Figure 4 Each operation is shown in the diagram. In each aspect, the operation can be related to... Figure 4 The different orders shown are implemented. These and other aspects are considered to be within the scope of this disclosure. Those skilled in the art will understand that although the various example components are described as performing various functions, other components may perform... Figure 4 The functions described in [the document].

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

[0069] Specific reference Figure 5 The second aspect of the fallback process is illustrated. Here, operation 500 indicates that the UE and network device NW are in a connected state. In the illustrated aspect, the UE is a sub-band non-overlapping full-duplex (SBFD) sensing device. Operation 510 shows the network device sending a dedicated random access (RA) configuration (e.g., “RACH-ConfigDedicated”) to the UE, and the UE receiving it, which indicates a first type of physical random access channel timing (RO) (e.g., SBFD RO). Additionally, the RA includes a field “preambleTransMax_SBFD” that defines the maximum number of RA attempts that the SBFD-sensing UE can perform in the RO type (e.g., “SBFD RO”).

[0070] At operation 520, the UE performs CFRA multiple times in SBFD RO. The number of times is set by RA in a field that defines the maximum number of such attempts.

[0071] like Figure 5 As shown, multiple CFRA requests failed. That is, even after the UE has performed the maximum number of CFRA requests (e.g., as defined in the preamble), the transmission failed for at least one of a variety of reasons; the network device did not receive any CFRA requests.

[0072] At operation 530, the UE retryes the CFRA request and sends at least one request (e.g., a CFRA request) to the network device, including a second type of RO (i.e., a conventional RO) (as opposed to the first type of RO (SBFD RO) used in operation 520), using the same preamble or set of preambles as the CFRA request performed in operation 520. The network device receives at least one request including the second type of RO from the UE using the same preamble or set of preambles as the CFRA request performed in operation 520. The maximum number of requests or attempts to send information is the same as indicated in operation 520 and is defined, for example, by “preambleTransMax_SBFD” in the RA.

[0073] Figure 5 The operations described are merely illustrative, and variations are considered to be within the scope of this disclosure. In various aspects, the operations may include... Figure 5 Other operations not shown. Operations may not be included in any aspect. Figure 5 Each operation is shown in the diagram. In each aspect, the operation can be related to... Figure 5 The different orders shown are implemented. These and other aspects are considered to be within the scope of this disclosure. Those skilled in the art will understand that although the various example components are described as performing various functions, other components may perform... Figure 5 The functions described in [the document].

[0074] Now for reference Figure 6 The third and fourth aspects of the fallback process are illustrated. Here, operation 600 indicates that the UE and network device NW are in a connected state. In the illustrated aspect, the UE is a sub-band non-overlapping full-duplex (SBFD) sensing device. Operation 610 shows that the network device sends a dedicated random access (RA) configuration (e.g., "RACH-ConfigDedicated") to the UE, and the UE receives it, which indicates a first type of physical random access channel timing (RO) (e.g., SBFD RO). Additionally, the RA may include a field "preambleTransMax_SBFD" that defines the maximum number of RA attempts that the SBFD-sensing UE can perform in the RO type (e.g., "SBFD RO").

[0075] At operation 620, the UE performs CFRA multiple times in SBFD RO. The number of times is set by RA in a field that defines the maximum number of such attempts.

[0076] like Figure 6 As shown, multiple CFRA requests failed. That is, even after the UE has performed the maximum number of CFRA requests (e.g., as defined in the preamble), the transmission failed for at least one of a variety of reasons; the network device did not receive any CFRA requests.

[0077] At operation 625, which is part of the third aspect and is an optional step, the UE determines that the RA configuration of the network device does not include the conventional RO and / or the field "preambleTransMax_SBFD" which defines the maximum number of RA attempts that the UE can perform in the RO type (e.g., "SBFD RO").

[0078] At operation 630, the network device sends a dedicated RA configuration that differs from the dedicated RA configuration used in operation 610. The UE receives the dedicated RA configuration from the network device, which differs from the dedicated RA configuration used in operation 610. Here, the dedicated RA configuration is "RACH-ConfigCommon," which may include ROs different from "RACH-ConfigDedicated" in operation 610. More specifically, the RA configuration in operation 630 may include conventional ROs, unlike the SBFD ROs included in operation 610.

[0079] At operation 635, which is part of the third aspect and is an optional step, the UE marks the SBFD RO or the RO in the downlink (DL) slot as invalid during the RO verification phase.

[0080] At operation 640, which is part of the third aspect and is an optional step, the UE sends a contention-based random access (CBRA) procedure in the conventional RO. The network device receives the CBRA procedure from the UE in the conventional RO. The CBRA is performed by randomly selecting a preamble for each of the Synchronization Signal / Physical Broadcast Channel (SS / PBCH) block beam or the Channel State Information (CSI) Reference Signal beam, where it has previously attempted a CFRA in operation 620.

[0081] Figure 6 The operations described herein are merely illustrative, and variations are considered to be within the scope of this disclosure. In various aspects, the operations may include... Figure 6 Other operations not shown. Operations may not be included in any aspect. Figure 6 Each operation is shown in the diagram. In each aspect, the operation can be related to... Figure 6 The different orders shown are implemented. These and other aspects are considered to be within the scope of this disclosure. Those skilled in the art will understand that although the various example components are described as performing various functions, other components may perform... Figure 6 The functions described in [the document].

[0082] Figures 4 to 6 The examples included are merely illustrative, and variations and other aspects are considered to be within the scope of this disclosure.

[0083] Now for reference Figure 7This diagram illustrates a block diagram of example components of a UE or network device. The device includes an electronic storage device 710, a processor 720, a memory 750, and a network interface 740. The various components can be communicatively coupled to each other. The processor 720 can 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-a-chip (SoC), or any other type of processor. The memory 750 can be a volatile type of memory, such as RAM, or a non-volatile type of memory, such as NAND flash memory. The memory 750 includes processor-readable instructions that can be executed by the processor 720 to cause the device to perform various operations, including those mentioned herein, such as... Figures 3 to 6 The operation.

[0084] Electronic storage device 710 can be and includes any type of electronic storage device for storing data, such as hard disk drives, solid-state drives, and / or optical disks, as well as other types of electronic storage devices. Electronic storage device 710 stores processor-readable instructions for causing the device to perform its operations, and stores data associated with such operations, such as data related to the 5G NR standard and other data. Network interface 740 can implement wireless networking technologies, such as 5G NR and / or other wireless networking technologies.

[0085] Figure 7 The components shown are merely examples, and those skilled in the art will understand that the apparatus includes other components not shown, and may include multiples of any of the components shown. These and other aspects are considered to be within the scope of this disclosure.

[0086] Other aspects of this disclosure include the following examples.

[0087] Example 1.1 An apparatus comprising: At least one processor; and At least one memory storing instructions that, when executed by at least one processor, cause the device to perform a method comprising: Receive from the network device a Dedicated Random Access (RA) configuration indicating the first type of Physical Random Access Channel Opportunity (RO); Send to the network device a plurality of contention-free random access (CFRA) requests, including a first preamble set and the first type of RO; and The dedicated RA configuration indicating the second type of RO is received from the network device.

[0088] Example 1.2 The apparatus according to Example 1.1, wherein the method further comprises: after receiving a dedicated RA configuration indicating a second type of RO from the network device, sending a request to the network device including a first preamble set and a second type of RO.

[0089] Example 1.3 The apparatus according to Example 1.2 includes a first preamble set and a second type of RO, wherein the request is a CFRA request.

[0090] Example 1.4 The apparatus according to Example 1.1, wherein the method further includes: sending an additional CFRA request to the network device after receiving a dedicated RA configuration indicating a second type of RO from the network device.

[0091] Example 1.5 The apparatus according to any one of Examples 1.1-1.4, wherein the first type of RO is a subband non-overlapping full-duplex (SBFD) RO.

[0092] Example 1.6 The apparatus according to any one of Examples 1.1-1.5, wherein the second type of RO is conventional RO.

[0093] Example 1.7 An apparatus according to any one of Examples 1.1-1.6, wherein the method further comprises: after receiving a dedicated RA configuration indicating a second type of RO from the network device, sending an additional CFRA request to the network device including a first preamble set and a second type of RO.

[0094] Example 1.8 An apparatus according to any one of Examples 1.1-1.7, wherein a plurality of CFRA requests in the CFRA requests exceed a reference signal received power (RSRP) threshold.

[0095] Example 1.9 An apparatus according to any one of Examples 1.1-1.8, wherein each of the plurality of CFRA requests, including a first preamble set and a first type of RO, is unsuccessful.

[0096] Example 1.10 An apparatus according to any one of Examples 1.1-1.9, wherein the apparatus is an SBFD sensing device.

[0097] Example 1.11 An apparatus according to any one of Examples 1.1-1.10, wherein the apparatus is a user equipment (UE).

[0098] Example 1.12 A method in a user equipment (UE) comprising: Receive from the network device a Dedicated Random Access (RA) configuration indicating the first type of Physical Random Access Channel Opportunity (RO); Sending multiple contention-free random access (CFRA) requests to the network device, including a first preamble set and a first type of RO; and Receive a dedicated RA configuration indicating the second type of RO from the network device.

[0099] Example 1.13 The method according to Example 1.12 further includes: after receiving a dedicated RA configuration indicating a second type of RO from the network device, sending a request to the network device including a first preamble set and a second type of RO.

[0100] Example 1.14 The method described in Example 1.13 includes a first preamble set and a second type of RO, wherein the request is a CFRA request.

[0101] Example 1.15 The method according to Example 1.12 further includes: after receiving the dedicated RA configuration indicating the second type of RO from the network device, sending an additional CFRA request to the network device.

[0102] Example 1.16 The method according to any one of Examples 1.12-1.15, wherein the RO of the first type is a subband non-overlapping full-duplex (SBFD) RO.

[0103] Example 1.17 The method according to any one of Examples 1.12-1.16, wherein the second type of RO is a conventional RO.

[0104] Example 1.18 The method according to any one of Examples 1.12-1.17, wherein the method further comprises: after receiving a dedicated RA configuration indicating a second type of RO from the network device, sending an additional CFRA request to the network device including a first preamble set and a second type of RO.

[0105] Example 1.19 The method according to any one of Examples 1.12-1.18, wherein a plurality of CFRA requests in the CFRA requests exceed a reference signal received power (RSRP) threshold.

[0106] Example 1.20 The method according to any one of Examples 1.12-1.19, wherein each of the plurality of CFRA requests including the first preamble set and the first type of RO is unsuccessful.

[0107] Example 1.21 The method according to any one of Examples 1.12-1.20, wherein the device is an SBFD sensing device.

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

[0109] Example 1.23 A method in a network device, comprising: Send a Dedicated Random Access (RA) configuration indicating the first type of Physical Random Access Channel Opportunity (RO) to the User Equipment (UE); Receives multiple contention-free random access (CFRA) requests from the UE, including a first preamble set and a first type of RO; Send a dedicated RA configuration indicating the second type of RO to the UE; and Receive a CFRA request from the UE, which includes a first preamble set and a second type of RO.

[0110] Example 1.24 The method according to Example 1.23 further includes: after sending a dedicated RA configuration indicating the second type of RO to the UE, receiving from the UE a request including a first preamble set and the second type of RO.

[0111] Example 1.25 The method described in Example 1.24 includes a first preamble set and a second type of RO, wherein the request is a CFRA request.

[0112] Example 1.26 The method according to Example 1.23 further includes: after sending a dedicated RA configuration indicating the second type of RO to the UE, receiving an additional CFRA request from the UE.

[0113] Example 1.27 The method according to any one of Examples 1.23-1.26, wherein the RO of the first type is a subband non-overlapping full-duplex (SBFD) RO.

[0114] Example 1.28 The method according to any one of Examples 1.23-1.27, wherein the second type of RO is conventional RO.

[0115] Example 1.29 The method according to any one of Examples 1.23-1.28, wherein the method further comprises: after sending a dedicated RA configuration indicating a second type of RO to the UE, receiving from the UE an additional CFRA request including a first preamble set and a second type of RO.

[0116] Example 1.30 The method according to any one of Examples 1.23-1.29, wherein a plurality of CFRA requests in the CFRA requests exceed a reference signal received power (RSRP) threshold.

[0117] Example 1.31 The method according to any one of Examples 1.23-1.30, wherein each of the multiple CFRA requests of a first preamble set and a first type of RO is unsuccessful.

[0118] Example 1.32 The method according to any one of Examples 1.23-1.31, wherein the device is an SBFD sensing device.

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

[0120] Example 4.1 An apparatus comprising: At least one processor; and At least one memory storing instructions, which, when executed by the at least one processor, cause the device to perform a method, the method comprising: Receive from the network device a Dedicated Random Access (RA) configuration indicating the first type of Physical Random Access Channel Opportunity (RO); Send a number of contention-free random access (CFRA) requests to the network device, including a first preamble set and a first type of RO, and Send a contention-based random access (CBRA) request to the network device.

[0121] Example 4.2 The apparatus according to 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 an SBFD counter.

[0122] Example 4.3 An apparatus according to any one of Examples 4.1-4.2, wherein the first type of RO is a conventional RO, and wherein the number of CFRA requests is based on a conventional counter.

[0123] Example 4.4 An apparatus according to any one of Examples 4.1-4.3, wherein the CBRA request comprises a randomly selected set of preambles.

[0124] Example 4.5 An apparatus according to any one of Examples 4.1-4.4, wherein the CBRA request includes a second type of RO.

[0125] Example 4.6. The apparatus according to any one of Examples 4.1-4.5, wherein the method further includes marking the RO of the first type as invalid.

[0126] Example 4.7 An apparatus according to any one of Examples 4.1-4.6, wherein each of the number of CFRA requests of the first preamble set and the first type of RO is unsuccessful.

[0127] Example 4.8 The apparatus according to any one of Examples 4.1-4.7, wherein the first type of RO is SBFDRO.

[0128] Example 4.9 The apparatus according to Example 4.8, wherein the CBRA request includes a second type of RO, and wherein the second type of RO is a conventional RO.

[0129] Example 4.10 An apparatus according to any one of Examples 4.1-4.9, wherein the apparatus is a user equipment (UE).

[0130] Example 4.11 A method in a user equipment (UE) comprising: Receive from the network device a Dedicated Random Access (RA) configuration indicating the first type of Physical Random Access Channel Opportunity (RO); Send a number of contention-free random access (CFRA) requests to the network device, the number of CFRA requests including a first preamble set and the first type of RO; and Send a contention-based random access (CBRA) request to the network device.

[0131] Example 4.12 The method described in 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 an SBFD counter.

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

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

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

[0135] Example 4.16. The method according to any one of Examples 4.11-4.15, wherein the method further includes marking the RO of the first type as invalid.

[0136] Example 4.17 The method according to any one of Examples 4.11-4.16, wherein each of the first preamble set and the number of CFRA requests of the first type of RO is unsuccessful.

[0137] Example 4.18 The method according to any one of Examples 4.11-4.17, wherein the first type of RO is an SBFD RO.

[0138] Example 4.19 The method described in Example 4.18, wherein the CBRA request includes a second type of RO, and wherein the second type of RO is a conventional RO.

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

[0140] Example 4.21 A method in a network device, comprising: Send a Dedicated Random Access (RA) configuration indicating the Physical Random Access Channel Timing (RO) of the first type to the User Equipment (UE); and The UE receives a number of contention-free random access (CFRA) requests, the number of CFRA requests including a first preamble set and the first type of RO; The UE receives a contention-based random access (CBRA) request, including a second type of RO.

[0141] Example 4.22 The method described in 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 an SBFD counter.

[0142] Example 4.32 The method according to any one of Examples 4.21-4.22, wherein the first type of RO is a conventional RO, and wherein the number of CFRA requests is based on a conventional counter.

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

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

[0145] Example 4.26. The method according to any one of Examples 4.21-4.25, wherein the method further includes marking the RO of the first type as invalid.

[0146] Example 4.27 The method according to any one of Examples 4.21-4.26, wherein each of the first preamble set and the number of CFRA requests of the first type of RO is unsuccessful.

[0147] Example 4.28 The method according to any one of Examples 4.21-42.7, wherein the first type of RO is an SBFD RO.

[0148] Example 4.29 The method described in Example 4.28, wherein the CBRA request includes a second type of RO, and wherein the second type of RO is a conventional RO.

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

[0150] The embodiments and aspects disclosed herein are examples of this disclosure and may be embodied in various forms. For example, although certain aspects herein are described as separate aspects, each aspect herein may be combined with one or more other aspects herein. The specific structural and functional details disclosed herein should not be construed as limiting, but rather serve as the basis for the claims and as a representative basis for teaching those skilled in the art to employ this disclosure differently with virtually any suitable detailed structure. Throughout the description of the accompanying drawings, the same reference numerals may refer to similar or identical elements.

[0151] The phrases “in one respect,” “in all respects,” “in all aspects,” “in some respects,” or “in other respects” may each refer to one or more of the same or different respects under this disclosure. The phrase “multiple” may refer to two or more.

[0152] The phrases “in an embodiment,” “in multiple embodiments,” “in various embodiments,” “in some embodiments,” or “in other embodiments” may each refer to one or more of the same or different embodiments according to this disclosure. The phrase “A or B” means “(A), (B), or (A and B).” The phrase “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).”

[0153] Any method, program, algorithm, or code described herein can be translated into or expressed in a programming language or computer program. As used herein, the terms "programming language" and "computer program" each include any language used to specify instructions to a computer, and include (but are not limited to) the following languages ​​and their derivatives: assembly language, 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, meta-languages ​​that specify their own programs, and all first-, second-, third-, fourth-, fifth-, and more generation computer languages. Databases and other data schemas, and any other meta-languages, are also included. There is no distinction between languages ​​that are interpreted, compiled, or use compilation and interpretation methods. There is no distinction between compiled and source versions of a program. Therefore, a reference to a program in which a programming language can exist in more than one state (such as source, compiled, object, or linked) is a reference to any and all such states. A reference to a program can encompass the actual instructions and / or the intent of those instructions.

[0154] While various aspects of this disclosure have been shown in the accompanying drawings, they are not intended to be limited thereto, as the scope of this disclosure is intended to be as broad as will be permitted in the art, and the specification is read in the same manner. Therefore, the above description should not be construed as restrictive, but merely as an example of particular aspects. Other modifications within the scope and spirit of the appended claims will be contemplated by those skilled in the art.

[0155] Furthermore, the various implementations of this disclosure can be described with reference to the following terms, and their features can be combined in any reasonable manner.

[0156] Clause 1. An apparatus for communication, comprising: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the apparatus to perform a method, the method comprising: receiving from a network device a dedicated random access (RA) configuration indicating a first type of physical random access channel timing (RO); sending to the network device a number of contention-free random access (CFRA) requests, the number of CFRA requests including a first preamble set and the first type of RO; and sending to the network device a contention-based random access (CBRA) request.

[0157] Clause 2. The apparatus according to Clause 1, wherein the first type of RO is a sub-band non-overlapping full-duplex SBFDRO, and wherein the number of CFRA requests is based on an SBFD counter.

[0158] Clause 3. The apparatus according to Clause 1, wherein the first type of RO is a conventional RO, and wherein the number of CFRA requests is based on a conventional counter.

[0159] Clause 4. The apparatus according to Clause 1, wherein the CBRA request comprises a randomly selected set of preambles.

[0160] Clause 5. The apparatus described in Clause 1, wherein the CBRA request includes a second type of RO.

[0161] Clause 6. The apparatus as described in Clause 4, wherein the CBRA request includes a second type of RO.

[0162] Clause 7. The apparatus according to Clause 1, wherein the method further includes marking the RO of the first type as invalid.

[0163] Clause 8. The apparatus according to Clause 1, wherein each of the number of CFRA requests of the first preamble set and the first type of RO is unsuccessful.

[0164] Clause 9. The apparatus according to Clause 1, wherein the first type of RO is SBFD RO.

[0165] Clause 10. The apparatus according to Clause 9, wherein the CBRA request includes a second type of RO, and wherein the second type of RO is a conventional RO.

[0166] Clause 11. The apparatus as described in Clause 1, wherein the apparatus is a user equipment (UE).

[0167] Clause 12. A method in a user equipment (UE) comprising: receiving from a network device a dedicated random access (RA) configuration indicating a physical random access channel timing (RO) of a first type; sending to the network device a number of contention-free random access (CFRA) requests, the number of CFRA requests including a first preamble set and the RO of the first type; and sending to the network device a contention-based random access (CBRA) request.

[0168] Clause 13. A method in a network apparatus, comprising: sending a dedicated random access RA configuration to a user equipment (UE) indicating a physical random access channel timing (RO) of a first type; receiving from the UE a number of contention-free random access (CFRA) requests, the number of CFRA requests including a first preamble set and the first type of RO; and receiving from the UE a contention-based random access (CBRA) request including a second type of RO.

Claims

1. A device for communication, comprising: At least one processor; as well as At least one memory storing instructions, which, when executed by the at least one processor, cause the device to perform a method, the method comprising: Receive from the network device a dedicated random access RA configuration indicating the timing of the first type of physical random access channel (RO); Send a number of contention-free random access (CFRA) requests to the network device, the number of CFRA requests including a first preamble set and a RO of the first type; and Send a contention-based random access (CBRA) request to the network device.

2. The apparatus of claim 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 an SBFD counter.

3. The apparatus of claim 1, wherein the first type of RO is a conventional RO, and wherein the number of CFRA requests is based on a conventional counter.

4. The apparatus of claim 1, wherein the CBRA request comprises a randomly selected set of preambles.

5. The apparatus of claim 1, wherein the CBRA request includes a second type of RO.

6. The apparatus of claim 4, wherein the CBRA request includes a second type of RO.

7. The apparatus of claim 1, wherein the method further comprises marking the RO of the first type as invalid.

8. The apparatus of claim 1, wherein each of the first preamble set and the number of CFRA requests of the first type of RO is unsuccessful.

9. The apparatus of claim 1, wherein the first type of RO is SBFD RO.

10. The apparatus of claim 9, wherein the CBRA request includes a second type of RO, and wherein the second type of RO is conventional RO.

Images