Beam Failure Recovery

Abstract

The techniques discussed herein facilitate beam failure recovery (BFR) for a secondary cell (SCell) or a primary SCell (PSCell). An exemplary implementation includes an apparatus configured to be employed in a user equipment (UE), the apparatus including: one or more processors configured to: generate a physical random access channel (PRACH) associated with a beam failure recovery request (BFRQ); generate a physical uplink shared channel (PUSCH) message associated with the BFRQ, wherein the PUSCH message includes at least one medium access control (MAC) control element (CE), the at least one MAC CE including one or more of an index associated with a cell in which a beam failure is detected or an index associated with a new beam; and process a physical downlink shared channel (PDSCH) as a random access response (RAR) associated with the PRACH and the PUSCH message.

Description

[0001] Cross - reference to related applications

[0002] This application claims priority to U.S. Provisional Patent Application No. 62 / 825,510, filed on Mar. 28, 2019, entitled "SYSTEM AND METHOD FOR BEAM FAILURE RECOVERY", which is incorporated herein by reference in its entirety for all purposes. BACKGROUND OF THE INVENTION

[0003] In the 3rd Generation Partnership Project (3GPP) Release 15 (Rel-15), beam failure recovery (BFR) for a primary-secondary cell (PSCell) is supported, which allows a user equipment (UE) to transmit a beam failure recovery request (BFRQ) to a base station (BS), such as a next-generation Node B (gNB), via a physical random access channel (PRACH) when the UE declares that all control channels have failed. New beam information can be implicitly carried by the PRACH, which is based on the downlink reference signal associated with the PRACH. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] Figure 1 is a block diagram showing the architecture of a system including a core network (CN), such as a 5th Generation (5G) CN (5GC), according to various embodiments.

[0005] Figure 2 is a diagram showing exemplary components of an infrastructure equipment device, such as a base station (BS), that can be employed according to various aspects discussed herein.

[0006] Figure 3 is a diagram showing exemplary components of a user equipment (UE) device that can be employed according to various aspects discussed herein.

[0007] Figure 4 is a block diagram showing a system that facilitates beam failure recovery (BFR) at a secondary cell (SCell) or a primary SCell (PSCell) according to various embodiments discussed herein.

[0008] Figure 5 is a diagram showing a two-step RACH process in combination with various aspects discussed herein.

[0009] Figure 6 is a flowchart showing an exemplary method that can be employed at a UE according to various embodiments discussed herein, which facilitates beam failure recovery (BFR) via a physical uplink shared channel (PUSCH) of a message A (MsgA) including content that facilitates PSCell / SCell BFR.

[0010] Figure 7 is a flowchart showing an exemplary method that can be employed at a base station (BS) according to various embodiments discussed herein. The exemplary method facilitates beam failure recovery (BFR) via a physical uplink shared channel (PUSCH) of a message A (MsgA) that includes content for facilitating PSCell / SCell BFR.

[0011] Figure 8 is an exemplary timing diagram showing timing options for applying a new beam after successful BFR according to various embodiments discussed herein. DETAILED DESCRIPTION

[0012] The present disclosure will now be described with reference to the accompanying drawings, where like reference numerals are used throughout to refer to like elements, and where the structures and devices shown are not necessarily drawn to scale. As used herein, the terms “component,” “system,” “interface,” etc. are intended to refer to computer-related entities, hardware, software (e.g., in execution), and / or firmware. For example, a component can be a processor (e.g., a microprocessor, a controller, or other processing device), a process running on the processor, a controller, an object, an executable, a program, a storage device, a computer, a tablet, and / or a user equipment with a processing device (e.g., a mobile phone or other device configured to communicate via a 3GPP RAN, etc.). By way of example, an application running on a server and the server can also be a component. One or more components can reside within a process, and components can be located on one computer and / or distributed between two or more computers. A group of elements or a group of other components may be described herein, where the term “group” can be interpreted as “one or more” unless the context indicates otherwise (e.g., “an empty group,” “a group of two or more X,” etc.).

[0013] In addition, these components can execute from various computer-readable storage media having various data structures stored thereon, such as, for example, using modules. Components can communicate, for example, according to signals having one or more data packets via local and / or remote processes (e.g., data from one component interacts with another component in a local system, a distributed system, and / or across a network such as the Internet, a local area network, a wide area network, or a similar network to other systems via signals).

[0014] As another example, a component can be a device with a specific function, where the specific function is provided by a mechanical component operated by an electrical or electronic circuit, and the electrical or electronic circuit can be operated by a software application or a firmware application executed by one or more processors. The one or more processors can be inside or outside the device and can execute at least a part of the software or firmware application. As yet another example, a component can be a device that provides a specific function through an electronic component without a mechanical component; the electronic component can include one or more processors therein to execute software and / or firmware that at least partially endows the electronic component with its function.

[0015] The use of the term "exemplary" is intended to present concepts in a concrete manner. As used in this application, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or". That is, unless otherwise specified or clear from the context, "X employs A or B" is intended to mean any natural inclusive arrangement. That is, if X employs A; X employs B; or X employs both A and B, then in any of the foregoing cases, "X employs A or B" is satisfied. Additionally, the articles "a" and "an" as used in this application and the appended claims should generally be construed to mean "one or more" unless otherwise specified or clearly apparent from the context to be singular. Further, to the extent that the terms "comprising", "including", "having", "has", "with", or variants thereof are used in the detailed description and claims, such terms are intended to be inclusive in a manner similar to the term "containing". Additionally, in the case of discussing one or more numbered items (e.g., "first X", "second X", etc.), generally, the one or more numbered items can be different or they can be the same, but in some cases, the context may indicate that they are different or indicate that they are the same.

[0016] As used herein, the term "circuit" can refer to, can be part of, or can include the following: an application specific integrated circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and / or a memory (shared, dedicated, or group) that executes one or more software or firmware programs, combinational logic circuits, and / or other suitable hardware components that provide the recited function. In some embodiments, the circuit can be implemented in one or more software or firmware modules, or the functions associated with the circuit can be implemented by one or more software or firmware modules. In some embodiments, the circuit can include logic that is at least partially operable in hardware.

[0017] The various aspects discussed herein can relate to facilitating wireless communications, and the nature of these communications can vary.

[0018] As is known, the use of personally identifiable information should follow privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of inadvertent or unauthorized access or use, and the nature of the authorized use should be clearly explained to users.

[0019] The embodiments described herein can be implemented into a system using any appropriately configured hardware and / or software. Figure 1 The architecture of a system 100 including a core network (CN) 120 (first to twenty-fourth additional embodiments, such as a fifth-generation (5G) CN (5GC)) is shown according to various embodiments. System 100 is shown as including: a UE 101, which can be the same as or similar to one or more other UEs discussed herein; a 3rd Generation Partnership Project (3GPP) radio access network (radio AN or RAN) or other (e.g., non-3GPP) AN, (R)AN 210, which can include one or more RAN nodes (such as a base station (e.g., evolved Node B (eNB))), a next-generation Node B (gNB, and / or other nodes) or other nodes or access points; and a data network (DN) 203, which can be, for example, a carrier service, Internet access, or a third-party service; and a fifth-generation core network (5GC) 120. 5GC 120 can include one or more of the following functions and network components: an authentication server function (AUSF) 122; an access and mobility management function (AMF) 121; a session management function (SMF) 124; a network exposure function (NEF) 123; a policy control function (PCF) 126; a network repository function (NRF) 125; a unified data management (UDM) 127; an application function (AF) 128; a user plane (UP) function (UPF) 102; and a network slice selection function (NSSF) 129.

[0020] The UPF 102 can act as an anchor point for mobility within and between RATs, an external protocol data unit (PDU) session point interconnected with the DN 103, and a branching point for supporting multi-homed PDU sessions. The UPF 102 can also perform packet routing and forwarding, perform packet inspection, perform the user plane part of policy rules, legally intercept packets (UP collection), perform traffic usage reporting, perform QoS handling on the user plane (e.g., packet filtering, gating, uplink (UL) / downlink (DL) rate enforcement), perform uplink traffic verification (e.g., service data flow (SDF) to QoS flow mapping), perform transport-level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. The UPF 102 can include an uplink classifier for supporting routing traffic to the data network. The DN 103 can represent various network operator services, Internet access, or third-party services. The DN 103 can include or be similar to an application server. The UPF 102 can interact with the SMF 124 via the N4 reference point between the SMF124 and the UPF 102.

[0021] The AUSF 122 can store the data for the authentication of the UE 101 and handle the functions related to authentication. The AUSF 122 can facilitate a common authentication framework for various access types. The AUSF 122 can communicate with the AMF 121 via the N12 reference point between the AMF 121 and the AUSF 122; and can communicate with the UDM 127 via the N13 reference point between the UDM 127 and the AUSF 122. Additionally, the AUSF 122 can present an interface based on the Nausf service.

[0022] The AMF 121 can be responsible for registration management (e.g., responsible for registering the UE 101, etc.), connection management, reachability management, mobility management, and legal interception of AMF-related events, and access authentication and authorization. The AMF 121 can be the termination point of the N11 reference point between the AMF 121 and the SMF124. The AMF 121 can provide transmission for the SM messages between the UE 101 and the SMF 124 and act as a transparent proxy for routing SM messages. The AMF 121 can also be for the UE 101 and the short message service (SMS) function (SMSF)( Figure 1Provide transmission of SMS messages between (not shown in the figure). The AMF 121 can act as a Security Anchor Function (SEAF), which can include interactions with the AUSF 122 and the UE 101 and / or receive intermediate keys established due to the UE 101 authentication process. In the case of using Global User Identity Module (USIM)-based authentication, the AMF 121 can retrieve security materials from the AUSF 122. The AMF 121 can also include a Single Connectivity Mode (SCM) function that receives keys from the SEA for deriving access network-specific keys. In addition, the AMF 121 can be a termination point of the Radio Access Network (RAN) control plane (CP) interface, which can include or be the N2 reference point between the (R)AN 110 and the AMF 121; and the AMF 121 can be a termination point of the Non-Access Stratum (NAS) (N1) signaling and perform NAS encryption and integrity protection.

[0023] The AMF 121 can also support NAS signaling with the UE 101 through the Non-3GPP (N3) Interworking Function (IWF) interface. The N3IWF can be used to provide access to untrusted entities. The N3IWF can be a termination point of the N2 interface between the (R)AN 110 and the AMF 121 in the control plane and can be a termination point of the N3 reference point between the (R)AN 110 and the UPF 102 in the user plane. Therefore, the AMF 121 can process N2 signaling for PDU sessions and QoS from the SMF 124 and the AMF 121, encapsulate / decapsulate packets for Internet Protocol (IP) security (IPSec) and N3 tunneling, mark N3 user plane packets on the uplink, and perform QoS requirements corresponding to the N3 packet marking, thus taking into account the QoS requirements associated with such markings received through N2. The N3IWF can also relay uplink and downlink control plane NAS signaling between the UE 101 and the AMF 121 via the N1 reference point between the UE 101 and the AMF 121 and relay uplink and downlink user plane packets between the UE 101 and the UPF 102. The N3IWF also provides a mechanism for establishing an IPsec tunnel with the UE 101. The AMF 121 can present a Namf service-based interface and can be a termination point of the N14 reference point between two AMF 121s and the N17 reference point between the AMF 121 and the 5G Equipment Identity Register (5G-EIR) ( Figure 1 not shown in the figure).

[0024] UE 101 can register with the AMF 121 to receive network services. Registration Management (RM) is used to register or deregister the UE 101 with the network (e.g., AMF 121), and establish a UE context in the network (e.g., AMF 121). The UE 101 can operate in the RM-REGISTRED state or the RM-DEREGISTRED state. In the RM-DEREGISTERED state, the UE 101 is not registered with the network, and the UE context in the AMF 121 does not hold the valid location or routing information of the UE 101, so the AMF 121 cannot reach the UE 101. In the RM-REGISTERED state, the UE 101 is registered with the network, and the UE context in the AMF 121 can hold the valid location or routing information of the UE 101, so the AMF 121 can reach the UE 101. In the RM-REGISTERED state, the UE 101 can perform a mobility registration update process, perform a periodic registration update process triggered by the expiration of a periodic update timer (e.g., notify the network that the UE 101 is still active), and perform a registration update process to update UE capability information or renegotiate protocol parameters with the network, etc.

[0025] The AMF 121 can store one or more RM contexts of the UE 101, where each RM context is associated with a specific access to the network. The RM context can be a data structure, a database object, etc., which particularly indicates or stores the registration status and periodic update timer for each access type. The AMF 121 can also store a 5GC Mobility Management (MM) context, which can be the same as or similar to the (Enhanced Packet System (EPS)) MM ((E)MM) context. In various embodiments, the AMF 121 can store the Coverage Enhancement (CE) mode B restriction parameters of the UE 101 in the associated MM context or RM context. The AMF 121 can also derive values from the usage setting parameters of the UE that have been stored in the UE context (and / or MM / RM context) when needed.

[0026] Connection Management (CM) can be used to establish and release a signaling connection between the UE 101 and the AMF 121 via the N1 interface. The signaling connection is used to enable NAS signaling exchange between the UE 101 and the CN 120, and includes a signaling connection between the UE and the AN (e.g., an RRC connection for non-3GPP access or a UE-N3IWF connection) and an N2 connection between the UE 101 between the AN (e.g., the RAN 110) and the AMF 121. The UE 101 can operate in one of two CM states (CM IDLE mode or CM-CONNECTED mode). When the UE 101 operates in the CM-IDLE state / mode, the UE 101 may not have a NAS signaling connection established with the AMF 121 via the N1 interface, and there may be an (R)AN 110 signaling connection for the UE 101 (e.g., N2 and / or N3 connections). When the UE 101 operates in the CM-CONNECTED state / mode, the UE 101 may have a NAS signaling connection established with the AMF 121 via the N1 interface, and there may be an (R)AN 110 signaling connection for the UE 101 (e.g., N2 and / or N3 connections). Establishing an N2 connection between the (R)AN 110 and the AMF 121 can cause the UE 101 to transition from the CM-IDLE mode to the CM-CONNECTED mode, and when the N2 signaling between the (R)AN 110 and the AMF 121 is released, the UE 101 can transition from the CM-CONNECTED mode to the CM-IDLE mode.

[0027] The SMF 124 may be responsible for session management (SM) (e.g., session establishment, modification, and release, including tunnel maintenance between the UPF and the AN node); UE IP address allocation and management (including optional authorization); selection and control of the UPF function; configuring the traffic steering of the UPF to route traffic to the correct destination; terminating the interface towards the policy control function; the policy enforcement and the control part of QoS; lawful interception (for SM events and the interface with the lawful interception (LI) system); terminating the SM part of the NAS message; downlink data notification; initiating AN-specific SM information sent to the AN via the AMF over N2; and determining the session and service continuity (SSC) mode of the session. SM may refer to the management of the PDU session, and the PDU session or "session" may refer to the PDU connection service that provides or enables the PDU exchange between the UE 101 and the data network (DN) 103 identified by the data network name (DNN). The PDU session may be established upon request by the UE 101 using the NAS SM signaling exchanged between the UE 101 and the SMF 124 over the N1 reference point, modified upon request by the UE 101 and the 5GC 120, and released upon request by the UE 101 and the 5GC 120. When requested from the application server, the 5GC 120 may trigger a specific application in the UE 101. In response to receiving the trigger message, the UE101 may pass the trigger message (or the relevant part / information of the trigger message) to one or more identified applications in the UE 101. The identified applications in the UE 101 may establish a PDU session with a specific DNN. The SMF 124 may check whether the UE101 request complies with the user subscription information associated with the UE 101. In this regard, the SMF 124 may retrieve and / or request updated notifications from the UDM 127 regarding the subscription data at the SMF 124 level.

[0028] The SMF 124 may include the following roaming functions: handling local enforcement to apply the QoS service level agreement (SLA) (visited public land mobile network (VPLMN)); charging data collection and charging interface (VPLMN); lawful interception (for SM events and the interface with the LI system, in the VPLMN); and supporting the interaction with the external DN to transmit the signaling for PDU session authorization / authentication over the external DN. In the roaming scenario, the N16 reference point between two SMF 124s may be included in the system 100, which may be between the SMF 124 in the visited network and another SMF 124 in the home network. Additionally, the SMF 124 may present an Nsmf service-based interface.

[0029] The NEF 123 can provide components for securely exposing the services and capabilities provided by 3GPP network functions to third parties, internal exposure / re - exposure, application functions (e.g., AF 128), edge computing or fog computing systems, etc. In such embodiments, the NEF 123 can authenticate, authorize, and / or restrict the AF. The NEF 123 can also transform the information exchanged with the AF 128 and the information exchanged with internal network functions. For example, the NEF 123 can transform between AF service identifiers and internal 5GC information. The NEF 123 can also receive information from other network functions (NFs) based on the exposure capabilities of other network functions. This information can be stored at the NEF 123 as structured data, or stored at a data - storing NF using a standardized interface. Then, the stored information can be re - exposed by the NEF 123 to other NFs and AFs, and / or used for other purposes such as analysis. Additionally, the NEF123 can present an interface based on the Nnef service.

[0030] The NRF 125 can support service discovery functions, receive NF discovery requests from NF instances, and provide information about the discovered NF instances to NF instances. The NRF 125 also maintains information about available NF instances and the services they support. As used herein, terms such as "instantiation" can refer to the creation of an instance, and an "instance" can refer to a specific occurrence of an object, which can occur, for example, during the execution of program code. Additionally, the NRF 125 can present an interface based on the Nnrf service.

[0031] The PCF 126 can provide control - plane functions for executing their policy rules and can also support a unified policy framework for managing network behavior. The PCF 126 can also implement an FE to access subscription information related to policy decisions in the UDR of the UDM 127. The PCF 126 can communicate with the AMF 121 via the N15 reference point between the PCF 126 and the AMF 121, which can include the PCF 126 in the visited network and the AMF 121 in a roaming scenario. The PCF 126 can communicate with the AF 128 via the N5 reference point between the PCF 126 and the AF 128; and communicate with the SMF 124 via the N7 reference point between the PCF 126 and the SMF 124. The system 100 and / or the CN 120 can also include an N24 reference point between the PCF 126 (in the home network) and the PCF 126 (in the visited network). Additionally, the PCF 126 can present an interface based on the Npcf service.

[0032] The UDM 127 can process subscription-related information to support the handling of communication sessions by network entities and can store the subscription data of the UE 101. For example, subscription data can be transmitted between the UDM 127 and the AMF 121 via the N8 reference point between the UDM 127 and the AMF. The UDM 127 can include two parts: an Application Function Entity (FE) and a Unified Data Repository (UDR) (the FE and the UDR are not shown in Figure 1 ). The UDR can store the subscription data and policy data of the UDM 127 and the PCF 126, and / or the structured data for exposure and application data of the NEF123 (including Packet Flow Descriptions (PFDs) for application detection, application request information of multiple UEs 101). The Nudr service-based interface can be presented by the UDR 221 to allow the UDM 127, the PCF 126, and the NEF 123 to access a specific set of the stored data, as well as read, update (e.g., add, modify), delete, and subscribe to notifications of relevant data changes in the UDR. The UDM can include a UDM-FE, which is responsible for handling credentials, location management, subscription management, etc. In different transactions, several different FEs can serve the same user. The UDM-FE accesses the subscription information stored in the UDR and performs authentication credential processing, user identification processing, access authorization, registration / mobility management, and subscription management. The UDR can interact with the SMF 124 via the N10 reference point between the UDM 127 and the SMF 124. The UDM 127 can also support SMS management, where the SMS-FE implements similar application logic as discussed elsewhere in this document. Additionally, the UDM 127 can present a Nudm service-based interface.

[0033] The AF 128 can provide the influence of the application on traffic routing, provide access to the NEF 123, and interact with the policy framework for policy control. The 5GC 120 and the AF 128 can provide information to each other via the NEF 123, which can be used for edge computing implementations. In such implementations, network operators and third-party services can be hosted near the access point of the attached UE101 to achieve efficient service delivery by reducing the end-to-end latency and the load on the transport network. For edge computing implementations, the 5GC can select a UPF 102 near the UE 101 and perform traffic steering from the UPF 102 to the DN 103 via the N6 interface. This can be based on the UE subscription data, the UE location, and the information provided by the AF 128. In this way, the AF 128 can influence UPF (re)selection and traffic routing. Based on the operator deployment, when the AF 128 is considered a trusted entity, the network operator can allow the AF 128 to directly interact with the relevant NFs. Additionally, the AF 128 can present a Naf service-based interface.

[0034] The NSSF 129 may select a set of network slice instances to serve the UE 101. The NSSF 129 may also appropriately determine the allowed Network Slice Selection Assistance Information (NSSAI) and the mapping to the subscribed single NSSAI (S-NSSAI). The NSSF 129 may also determine, based on appropriate configuration and possibly by querying the NRF 125, the set of AMFs, or a list of candidate AMFs 121, that will be used to serve the UE 101. The selection of a set of network slice instances for the UE 101 may be triggered by the AMF 121, where the UE 101 registers by interacting with the NSSF 129, which may cause the AMF 121 to change. The NSSF 129 may interact with the AMF 121 via the N22 reference point between the AMF 121 and the NSSF 129; and may communicate with another NSSF 129 in the visited network via the N31 reference point ( Figure 1 not shown in the figure). Additionally, the NSSF 129 may present an interface based on the Nnssf service.

[0035] As previously discussed, the CN 120 may include an SMSF, which may be responsible for SMS subscription checking and verification, and relaying SM messages to / from the UE 101 to / from other entities such as the SMS-Gateway Mobile Switching Center (GMSC) / Interworking MSC (IWMSC) / SMS Router. The SMSF may also interact with the AMF 121 and the UDM 127 for a notification procedure that the UE 101 can use for SMS transmission (e.g., setting the UE unreachable flag and notifying the UDM 127 when the UE 101 is available for SMS).

[0036] The CN 120 may also include Figure 1 other elements not shown, such as data storage systems / architectures, 5G-EIR, Security Edge Protection Proxy (SEPP), etc. The data storage system may include a Structured Data Storage Function (SDSF), an Unstructured Data Storage Function (UDSF), etc. Any NF may store unstructured data into the UDSF (e.g., UE context) or retrieve it from the UDSF via the N18 reference point between any NF and the UDSF ( Figure 1 not shown in the figure). Each NF may share the UDSF for storing its respective unstructured data, or each NF may have its own UDSF located at or near each NF. Additionally, the UDSF may present an interface based on the Nudsf service. Figure 1(not shown in the figure). The 5G-EIR can be an NF that checks the status of the Permanent Equipment Identifier (PEI) to determine whether to blacklist a specific piece of equipment / entity from the network; and the SEPP can be a non-transparent proxy that performs topology hiding, message filtering, and policing on the inter-PLMN control plane interface.

[0037] In addition, there can be more reference points and / or service-based interfaces between NF services in the NF; however, for clarity, Figure 1 these interfaces and reference points are omitted. In one example, the CN 120 can include an Nx interface, which is an inter-CN interface between the MME (e.g., non-5G MME) and the AMF 121 to enable interoperability between the CN 120 and a non-5G CN. Other exemplary interfaces / reference points can include the N5g-EIR service-based interface presented by the 5G-EIR, the N27 reference point between the Network Repository Function (NRF) in the visited network and the NRF in the home network; and the N31 reference point between the NSSF in the visited network and the NSSF in the home network.

[0038] Referring to Figure 2 , an exemplary component of the infrastructure equipment device 200 according to some embodiments is shown. The infrastructure equipment 200 (or "system 200") can be implemented as a base station (e.g., eNB, gNB, etc.), a radio headend, a RAN node (such as the nodes of the RAN 110 shown and described previously), another access point (AP) or base station (BS), an application server, and / or any other element / device discussed herein. In other examples, the system 200 can be implemented in or by a UE.

[0039] The system 200 includes: an application circuit 205, a baseband circuit 210, one or more Radio Front-End Modules (RFEMs) 215, a memory circuit 220, a Power Management Integrated Circuit (PMIC) 225, a power splitter circuit 230, a network controller circuit 235, a network interface connector 240, a satellite positioning circuit 245, and a user interface 250. In some embodiments, the device 200 can include additional elements, such as a memory / storage device, a display, a camera, a sensor, or an Input / Output (I / O) interface. In other embodiments, the following components can be included in more than one device. For example, the circuits can be separately included in more than one device for CRAN, vBBU, or other similar implementations.

[0040] The application circuit 205 may include circuitry such as, but not limited to, one or more processors (or processor cores), cache memory, and one or more of the following: low dropout regulators (LDOs), interrupt controllers, serial interfaces such as SPI, I2C, or general purpose programmable serial interface modules, real-time clocks (RTCs), timers (including interval timers and watchdog timers), general purpose input / output (I / O or IO), memory card controllers such as Secure Digital (SD) Multimedia Card (MMC) or the like, Universal Serial Bus (USB) interfaces, Mobile Industry Processor Interface (MIPI) interfaces, and Joint Test Action Group (JTAG) test access ports. The processor (or core) of the application circuit 205 may be coupled to or may include memory / storage elements and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the system 200. In some embodiments, the memory / storage elements may be on-chip memory circuitry that may include any suitable volatile and / or non-volatile memory such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid state memory, and / or any other type of memory device technology such as those discussed herein.

[0041] The processor of the application circuit 205 may include, for example, one or more processor cores (CPUs), one or more application processors, one or more graphics processing units (GPUs), one or more reduced instruction set computing (RISC) processors, one or more Acorn RISC Machine (ARM) processors, one or more complex instruction set computing (CISC) processors, one or more digital signal processors (DSPs), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or any suitable combination thereof. In some embodiments, the application circuit 205 may include or may be a dedicated processor / controller for operating in accordance with the various embodiments herein. As an example, the processor of the application circuit 205 may include one or more processors, processors; Advanced Micro Devices (AMD) processors, accelerated processing units (APUs), or processors; ARM-based processors licensed by ARM Holdings, Ltd., such as the ARM Cortex-A series processors provided by Cavium(TM), Inc. and MIPS-based designs from MIPS Technologies, Inc., such as MIPS Warrior P-class processors; and so on. In some embodiments, system 200 may not utilize application circuit 205 and, instead, may include a dedicated processor / controller to process, for example, IP data received from an EPC or 5GC.

[0042] User interface circuit 250 may include one or more user interfaces designed to enable a user to interact with system 200 or a peripheral component interface designed to enable a peripheral component to interact with system 200. The user interface may include, but is not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., a light-emitting diode (LED)), a physical keyboard or keypad, a mouse, a touchpad, a touchscreen, a speaker or other audio-emitting device, a microphone, a printer, a scanner, headphones, a display screen or display device, etc. The peripheral component interface may include, but is not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, a power interface, etc.

[0043] Figure 2 The components shown may communicate with each other using an interface circuit that may include any number of buses and / or interconnect (IX) technologies, such as Industry Standard Architecture (ISA), Extended ISA (EISA), Peripheral Component Interconnect (PCI), Peripheral Component Interconnect Extended (PCIx), PCI express (PCIe), or any number of other technologies. The bus / IX may be a proprietary bus, e.g., a proprietary bus used in an SoC-based system. Other bus / IX systems may be included, such as an I2C interface, an SPI interface, a point-to-point interface, and a power bus, and so on.

[0044] Referring Figure 3 , an example of a platform 300 (or "device 300") according to various embodiments is shown. In an embodiment, computer platform 1400 may be adapted to be used as a UE 101 and / or any other element / device discussed herein. Platform 300 may include any combination of the components shown in the example. The components of platform 300 may be implemented as an integrated circuit (IC), a portion of an IC, discrete electronic devices, or other modules, logic, hardware, software, firmware, or combinations thereof adapted within computer platform 300, or as components otherwise incorporated within the chassis of a larger system. Figure 3 The block diagram of is intended to show a high-level view of the components of computer platform 300. However, some of the components shown may be omitted, additional components may exist, and different arrangements of the shown components may occur in other implementations.

[0045] The application circuit 305 includes circuitry such as, but not limited to, one or more processors (or processor cores), cache memory, and one or more of an LDO, an interrupt controller, a serial interface (such as SPI), an I2C or a general-purpose programmable serial interface module, an RTC, timers (including interval timers and watchdog timers), general-purpose I / Os, a memory card controller (such as an SD MMC or a similar controller), a USB interface, a MIPI interface, and a JTAG test access port. The processor (or core) of the application circuit 305 may be coupled to or may include memory / storage elements and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the system 300. In some embodiments, the memory / storage elements may be on-chip memory circuitry that may include any suitable volatile and / or non-volatile memory such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory device technology such as those discussed herein.

[0046] As an example, one or more processors of the application circuit 305 may include general-purpose or special-purpose processors such as the A-series processors (e.g., A13 Bionic) available from Inc., Cupertino, CA or any other such processor. The processor of the application circuit 305 may also be one or more of the following: an Advanced Micro Devices (AMD) processor or an accelerated processing unit (APU); a core processor from Inc., a Snapdragon processor from TM Technologies, Inc., a Texas Instruments, Open Multimedia Applications Platform (OMAP) TM processor; a MIPS-based design from MIPS Technologies, Inc. such as MIPS Warrior M-class, Warrior I-class, and Warrior P-class processors; an ARM-based design licensed from ARM Holdings, Ltd. such as ARM Cortex-A, Cortex-R, and Cortex-M series processors; etc. In some embodiments, the application circuit 305 may be part of a system-on-chip (SoC) where the application circuit 305 and other components are formed as a single integrated circuit or a single package.

[0047] The baseband circuit 310 may be implemented as, for example, a soldered-in substrate that includes one or more integrated circuits, a single-packaged integrated circuit soldered to the main circuit board, or a multi-chip module that includes two or more integrated circuits.

[0048] The platform 300 may also include interface circuitry (not shown) for connecting external devices to the platform 300. External devices connected to the platform 300 via this interface circuitry include sensor circuit 321 and electromechanical components (EMC) 322, as well as a removable memory device coupled to removable memory circuit 323.

[0049] The battery 330 may power the platform 300, but in some examples, the platform 300 may be installed and deployed in a fixed location and may have a power source coupled to the power grid. The battery 330 may be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in V2X applications, the battery 330 may be a typical lead-acid automotive battery.

[0050] Various embodiments may employ techniques discussed herein that can facilitate beam failure recovery (BFR) for a PSCell or SCell. These techniques include (1) the content of RACH PUSCH (e.g., MsgA PUSCH, Msg3PUSCH, etc.) that can facilitate BFR for PSCell / SCell, and / or (2) assumptions of UE QCL and / or spatial relation information for downlink (DL) and / or uplink (UL) control channels and data channels after RACH-based (e.g., 2-step RACH, 4-step RACH) BFR is completed.

[0051] Referring to Figure 4 , a block diagram of a system 400 is shown that can be employed at a UE (user equipment), a next-generation node B (g-node B or gNB), or another BS (base station) / TRP (transmit / receive point) or component of a 3GPP (Third Generation Partnership Project) network (e.g., a 5GC (Fifth Generation Core Network) component or function such as a UPF (User Plane Function)) according to various embodiments discussed herein, which facilitates beam failure recovery (BFR) at a PSCell or SCell. The system 400 may include a processor 410, a communication circuit 420, and a memory 430. The processor 410 (e.g., which may include Figure 2 or Figure 3One or more processors, etc.) may include processing circuitry and associated interfaces. The communication circuitry 420 may include, for example, circuitry for wired and / or wireless connections (e.g., radio front-end module 215 or 315, etc.), which may include transmitter circuitry (e.g., associated with one or more transmit chains) and / or receiver circuitry (e.g., associated with one or more receive chains), where the transmitter circuitry and the receiver circuitry may employ common and / or different circuit elements, or combinations thereof. The memory 430 may include one or more memory devices (e.g., memory circuitry 220 or 320, removable memory 323, local memory (e.g., including the CPU registers of the processors discussed herein), etc.), and the one or more memory devices may have any of various storage media (e.g., volatile and / or non-volatile according to any of various techniques / constructions, etc.), and may store instructions and / or data associated with one or more of the processor 410 or the transceiver circuitry 420.

[0052] A particular type of implementation of the system 400 (e.g., a UE implementation) may be indicated via a subscript (e.g., system 400 UE includes a processor 410 UE , a communication circuitry 420 UE , and a memory 430 UE ). In some implementations, such as a BS implementation (e.g., system 400 gNB ) and a network component (e.g., UPF (User Plane Function), etc.) implementation (e.g., system 400 UPF ), the processor 410 gNB (etc.), the communication circuitry (e.g., 420 gNB etc.) and the memory (e.g., 430 gNB etc.) may be in a single device or may be included in different devices, such as part of a distributed architecture. In an implementation, signaling or messaging between different implementations of the system 400 (e.g., 400 1 and 400 2 ) may be generated by the processor 410 1 , transmitted by the communication circuitry 420 1 through a suitable interface or reference point (e.g., 3GPP air interface N3, N4, etc.), received by the communication circuitry 420 2 , and processed by the processor 410 2 . Depending on the type of interface, additional components (e.g., antennas, network ports, etc. associated with the system 400 1 and 400 2 ) may participate in the communication.

[0053] In various aspects discussed herein, signals and / or messages may be generated and output for transmission, and / or transmitted messages may be received and processed. Depending on the type of signal or message generated, output for transmission (e.g., by processor 410, etc.) may include one or more of the following operations: generating a set of associated bits indicative of the content of the signal or message, encoding (e.g., may include adding cyclic redundancy check (CRC) and / or encoding via one or more of turbo codes, low density parity check (LDPC) codes, truncated convolutional codes (TBCC), etc.), scrambling (e.g., based on a scrambling seed), modulating (e.g., via one of binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), or some form of quadrature amplitude modulation (QAM), etc.) and / or resource mapping to one or more resource elements (REs) (e.g., a scheduled resource set, a set of time and frequency resources authorized for uplink transmission, etc.), where each RE may span one subcarrier in the frequency domain and one symbol in the time domain (e.g., where the symbol may be according to any of a variety of access schemes, such as orthogonal frequency division multiplexing (OFDM), single carrier frequency division multiple access (SC-FDMA), etc.). Depending on the type of signal or message received, processing (e.g., by processor 410, etc.) may include one or more of the following operations: identifying the physical resources associated with the signal / message, detecting the signal / message, de-interleaving groups of resource elements, demodulating, descrambling, and / or decoding.

[0054] In various aspects, one or more of information (e.g., system information, resources associated with signaling, etc.), features, parameters, etc. may be configured to a UE via signaling (e.g., associated with one or more layers, such as L1 signaling or higher layer signaling (e.g., MAC, RRC, etc.)) from a gNB or other access point (e.g., via signaling generated by processor 410 gNB generated, transmitted by communication circuitry 420 gNB transmitted, by communication circuitry 420 UE received, and processed by processor 410 UE The type of signaling employed and / or the exact details of the operations performed at the UE and / or gNB during processing (e.g., signaling structure, PDU / SDU processing, etc.) may vary depending on the type of information, features, parameters, etc. However, for convenience, such operations may be referred to herein as configuring information / features / parameters / etc. to the UE, generating or processing configuration signaling, or via similar terms.

[0055] Various embodiments relate to techniques that can facilitate beam failure recovery, such as in conjunction with a primary secondary cell (PSCell) and / or a secondary cell (SCell). A first set of techniques relates to information that can be transmitted via a physical uplink shared channel (PUSCH) associated with a random access channel (RACH) procedure (e.g., the PUSCH of message A (MsgA) in a two-step RACH procedure, the PUSCH of message 3 (Msg3) in a four-step RACH procedure, etc.). A second set of techniques relates to assumptions that can be adopted for quasi-co-location, spatial relation information, and / or power control after beam failure recovery. Various embodiments can employ techniques from the first set of techniques and / or the second set of techniques, and can be employed at a UE or a BS such as a gNB.

[0056] As described above, Rel-15 provides support for BFR for the PSCell. In Rel-16, BFR for the secondary cell (SCell) will be supported, and the UE can transmit the failed cell index and new beam information to the gNB during the BFR procedure. In various aspects, this information can be carried by a MAC control element (CE).

[0057] Referring to Figure 5 , a schematic diagram showing a two-step RACH procedure 500 is illustrated in connection with various aspects discussed herein. One possible way to transmit a beam failure recovery request (BFRQ) is to use the two-step RACH procedure 500, where in a first message 510, the UE 504 can transmit a PRACH as well as a PUSCH (MsgA), and after detecting the PRACH and decoding the MsgA PUSCH, the gNB 502 can send a random access response (RAR) to the UE via a PDSCH (MsgB) at 520. Additionally, although for illustrative purposes, Figure 5 a two-step RACH procedure is shown, and the exemplary embodiments discussed herein relate to techniques in conjunction with the two-step RACH procedure to provide specific exemplary embodiments, the techniques discussed herein can also be employed in conjunction with a four-step RACH procedure.

[0058] However, the prior art fails to define the information to be transmitted by the MsgA PUSCH to support BFR in the PsCell and SCell.

[0059] In addition, since the same gNB-UE beam pair link can be applied to both the uplink and the downlink, after BFR is completed, the prior art cannot define the quasi-co-location (QCL) assumptions for the downlink control channel and data channel by the UE, and the spatial relation information assumptions for the uplink control channel and data channel.

[0060] As discussed in more detail herein, various implementations that may be employed, for example, at a UE or a base station (e.g., a node of the RAN such as a gNB), may facilitate BFR for a PSCell or an SCell. A first set of techniques includes techniques for generating a RACH PUSCH (e.g., MsgA PUSCH, Msg3 PUSCH, etc.) that includes content that may facilitate BFR for a PSCell / SCell. A second set of techniques includes techniques for applying power control, UE QCL, and / or spatial relation information assumptions for downlink (DL) and / or uplink (UL) control channels and data channels after completion of RACH-based (e.g., 2-step RACH, 4-step RACH) BFR.

[0061] Contents of MsgA / Msg3 PUSCH for BFR requests

[0062] To support BFR in a PSCell, in various aspects, a UE may transmit at least new beam information to a gNB, which may include the identity of the new beam and / or the beam quality of the new beam (e.g., reference signal (RS) received power (RSRP), RS received quality (RSRQ), signal-to-interference-plus-noise ratio (SINR)). In some cases, as a result of UE capability limitations, the number of downlink reference signals for beam failure detection (BFD) may be less than the number of control resource sets (CORESETs) in the active bandwidth part (BWP) available for partial beam failure recovery. Thus, in some aspects, the UE may also report the failed CORESET information to the gNB.

[0063] In various implementations, (in addition to the UE ID for contention resolution, e.g., a cell radio network temporary ID (C-RNTI)), at least one of the following types of information may also be carried by the MsgA / Msg3 PUSCH to support PsCell BFR: (1) the failed CORESET index and / or (2) the new beam quality.

[0064] In some implementations, the failed CORESET index may be indicated based on a bitmap, where each bit may be used to indicate the status of a CORESET. For example, "0" may indicate that the CORESET is not failed or the UE has not detected the status of the CORESET, and "1" indicates that the CORESET has failed (or vice versa).

[0065] The new beam quality may include the reference signal received power (RSRP) or the reference signal received quality (RSRQ) of the newly identified beam.

[0066] In the same or other embodiments, (as a supplement to the UE ID for contention resolution, e.g., the Cell Radio Network Temporary ID (C-RNTI)), at least one of the following types of information may also be carried by the MsgA / Msg3 PUSCH to support SCell BFR or BFR for all cells: (1) the index of the failed serving cell; (2) the index of the failed CORESET; and / or (3) new beam information.

[0067] The new beam information may include new beam quality (e.g., RSRP or SINR, etc.) and / or new beam index, where a predefined value may be used to indicate that no new beam is recognized in such cases. If BFR for all cells is supported, the index of the failed serving cell may be based on the PSCell and SCell indices, or different Medium Access Control (MAC) control elements (CEs) may be used for BFR of the PSCell and SCell with different logical channel IDs.

[0068] In various embodiments, any information in the information transmitted via the MsgA / Msg3 PUSCH (e.g., including the C-RNTI, etc.) may be transmitted via one or more MAC control elements (CEs). As an example, in some embodiments, a separate MAC-CE may be used to carry the C-RNTI and beam information. As another example, in other embodiments, the information may be transmitted via a new MAC-CE, which may be defined to carry both the C-RNTI and beam information.

[0069] As described above, although for illustrative purposes, some embodiments, examples, and figures specifically relate to the MsgA PUSCH content for the 2-step RACH process, the same content may also be transmitted in the Msg3 for the 4-step RACH process. As an example, the beam information may be transmitted as a separate MAC CE in the Msg3, or via a new MAC CE in the Msg3 that includes both the C-RNTI and beam information.

[0070] For the above embodiments, the PRACH and MsgA / Msg3 PUSCH may be transmitted in the PCell or PsCell, and the random access response may be transmitted in another serving cell, which may be configured by higher layer signaling or is the failed serving cell whose cell index is indicated by the MsgA PUSCH.

[0071] Refer to Figure 6, which shows a flowchart of an exemplary method that can be adopted at a UE according to various embodiments discussed herein. This exemplary method promotes BFR via a MsgA PUSCH that includes content for promoting PSCell / SCell BFR. In other aspects, a machine-readable medium may store instructions associated with method 600, which when executed may cause the UE (e.g., adopting system 400 UE ) to perform the actions of method 600.

[0072] At 610, in response to determining that a PSCell or SCell beam has experienced a beam failure, the UE may generate a Beam Failure Recovery Request (BFRQ) and transmit it to the BS (e.g., gNB) via a RACH MsgA. The BFRQ includes a PRACH request and a PUSCH message. In various embodiments, the PUSCH may include one or more of the following: (1) the index of the failed serving cell (e.g., for PSCell and / or SCell); (2) the index of the failed CORESET; and / or (3) new beam information (e.g., new beam index and / or RSRP, RSRQ, SINR, etc.). The new beam information may also indicate whether a new beam has been identified.

[0073] At 620, in response to the MsgA transmitted at 610, the UE may receive a Random Access Response (RAR) as MsgB of a two-step RACH procedure based on the information included in the MsgA PUSCH to indicate a successful BFR.

[0074] Additionally or alternatively, method 600 may include one or more other actions described herein in connection with various embodiments and a first set of techniques of the UE and / or associated systems (e.g., 101, 300, 400 UE etc.). Furthermore, as described above, although Figure 6 a two-step RACH procedure is shown, in various embodiments, similar techniques may be employed in conjunction with a four-step RACH procedure (e.g., using Msg3 that includes content similar to the content of MsgA in method 600).

[0075] Referring to Figure 7 , which shows a flowchart of an exemplary method that can be adopted at a BS (e.g., gNB, etc.) according to various embodiments discussed herein. This exemplary method promotes BFR via a MsgA PUSCH that includes content for promoting PSCell / SCell BFR. In other aspects, a machine-readable medium may store instructions associated with method 600, which when executed may cause the BS (e.g., adopting system 400 UE ) to perform the actions of method 600.

[0076] At 710, the BFRQ can be detected from the UE via the PRACH.

[0077] At 720, the MsgA PUSCH from the UE can be received and decoded, where the PUSCH message can include one or more of the following: (1) the index of the failed serving cell (e.g., for the PSCell and / or SCell); (2) the index of the failed CORESET; and / or (3) new beam information (e.g., new beam index and / or RSRP, RSRQ, SINR, etc.).

[0078] At 730, in response to the BFRQ, the RAR can be transmitted to the UE as MsgB of a two-step RACH procedure.

[0079] Additionally or alternatively, method 700 can include one or more other actions described herein in connection with various embodiments and a first set of techniques of the UE and / or associated systems (e.g., nodes of (R)AN110, 200, 400 gNB 、400 eNB etc.). Further, as described above, although Figure 7 a two-step RACH procedure is shown, in various embodiments, similar techniques can be employed in conjunction with a four-step RACH procedure (e.g., using Msg3 that includes content similar to that of MsgA in method 700).

[0080] UE QCL / Spatial relationship information assumptions after receiving MsgB

[0081] Since the same beam can be applied to both the uplink channel and the downlink channel, when a beam failure occurs on the downlink, a beam failure typically also occurs on the uplink. Thus, in various embodiments, after receiving MsgB (for a two-step RACH procedure) or Msg4 (for a four-step RACH procedure), the UE can reset the QCL and / or spatial relationship information assumptions for the uplink channel and the downlink channel, which assumptions are based on the newly identified beam.

[0082] In various embodiments, K time slots after the UE receives the MsgB / Msg4 PDSCH, the UE can apply the newly identified beam to the uplink and / or downlink control and / or data channels, where K can be configured by higher layer signaling or be predefined (e.g., in the specifications of the 3rd Generation Partnership Project (3GPP), etc.), can be determined by each subcarrier spacing or the UE capabilities across all subcarrier spacings, or can be based on the minimum subcarrier spacing in the DL and UL.

[0083] In other embodiments, K time slots (e.g., 2 time slots, 3 time slots, 4 time slots, etc.) after the UE transmits an acknowledgement (ACK) of the MsgB / Msg4 PDSCH or the UE transmits a PUSCH according to the UL grant indicated in MsgB / Msg4, the UE may apply newly identified beams to UL and / or DL control channels and / or data channels, where K may be configured by higher layer signaling or predefined (e.g., in 3GPP specifications, etc.), may be determined by each subcarrier spacing or the UE capabilities across all subcarrier spacings, or may be based on the minimum subcarrier spacing in DL and UL.

[0084] Additionally, in various embodiments, the value of K for when to apply a new beam may be the same or different for UL channels and DL channels.

[0085] In embodiments that employ both the first set of techniques and the second set of techniques, a new beam may be applied as an additional action at some point after 620, where the timing of when to apply the new beam may depend on the specific embodiment (e.g., K time slots after the UE receives the MsgB / Msg4 PDSCH, K time slots after the UE transmits an ACK for the MsgB / Msg4 PDSCH, K time slots after the UE transmits a PUSCH via the UL grant indicated by MsgB / Msg4, etc.).

[0086] Referring to Figure 8 , an exemplary timing diagram showing timing options for applying a new beam after a successful BFR is shown in accordance with various embodiments discussed herein. At 810, the UE may transmit a PRACH and a MsgA PUSCH (or alternatively, a Msg3 PUSCH). At 820, the UE may receive a MsgB PDSCH (or alternatively, Msg4). In some embodiments, as discussed herein, at 830, the UE may apply a new beam K time slots after receiving the MsgB (or Msg4) PDSCH. At 840, the UE may transmit an ACK for the MsgB (or Msg4) PDSCH. In some embodiments, as discussed herein, at 850, the UE may apply a new beam K time slots after transmitting the ACK for the MsgB (or Msg4) PDSCH (or K time slots after the UE transmits a PUSCH according to the UL grant indicated in MsgB / Msg4).

[0087] In various embodiments, when a UE begins to apply a new beam to a downlink channel, the UE can do one of the following: apply the new beam to CORESET 0, apply the new beam to all CORESETS, or apply the new beam to all CORESETS and all PDSCHs. Additionally, in various embodiments, when a UE begins to apply a new beam to an uplink channel, the UE can apply the new beam to one or more of the following: PUCCH, PUSCH scheduled by DCI format 0_0, PUSCH scheduled by DCI format 0_1, SRS for codebook-based or non-codebook-based transmission, or SRS for antenna switching.

[0088] To apply a newly identified beam to a downlink channel and / or an uplink channel, the UE may assume that the corresponding downlink channel is quasi co-located with the downlink reference signal identified at least with respect to spatial reception parameters during new beam identification, and the UE may apply the same spatial domain transmission filter as the spatial domain downlink filter used for receiving the new beam.

[0089] Additionally, in various embodiments, since power control is beam-specific, when the UE transmits an uplink channel using a new beam, the original power control parameters (which were used for the previous beam) are no longer suitable for transmission on the new beam. In various embodiments, after applying the new beam to the corresponding uplink channel, the power control parameters P 0 and α may be based on default power control parameters predefined or configured by higher layer signaling. Additionally, in various embodiments, the downlink reference signal for path loss measurement should be based on the downlink reference signal associated with the newly identified beam. Additionally, in various embodiments, for cases where cumulative closed-loop power control is enabled, the closed-loop power parameters may be reset.

[0090] Additional embodiments

[0091] Examples herein may include subject matter such as a method, components for performing actions or blocks of the method, at least one machine-readable medium including executable instructions that, when executed by a machine (e.g., a processor having a memory, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), etc.), cause the machine to perform actions of a method or apparatus or system for concurrent communication using multiple communication technologies according to the described embodiments and examples.

[0092] Example 1 may include a method (e.g., performed by circuitry of a user equipment (UE)) that includes transmitting a beam failure recovery request for a primary serving cell (PsCell) and a secondary cell (SCell) through a two-step random access procedure and determining spatial relation information for an uplink channel and signals and quasi co-location (QCL) for a downlink channel.

[0093] Embodiment 2 may include the method according to Embodiment 1 or some other embodiment herein, wherein the first message is carried by a PRACH and a message A (MsgA) PUSCH.

[0094] Embodiment 3 may include the method according to Embodiment 1 or some other embodiment herein, wherein, as a supplement to the UE ID for contention resolution, such as a cell radio network temporary ID (C-RNTI), at least one of the following information should also be carried by the MsgA PUSCH to support PsCell BFR: the failed CORESET index, the new beam quality.

[0095] Embodiment 4 may include the method according to Embodiment 3 or some other embodiment herein, wherein the new beam quality may be the reference signal received power (RSRP) or the reference signal received quality (RSRQ) of the newly identified beam.

[0096] Embodiment 5 may include the method according to Embodiment 1 or some other embodiment herein, wherein, as a supplement to the UE ID for contention resolution, i.e., the cell radio network temporary ID (C-RNTI), at least one of the following information should also be carried by the MsgA PUSCH to support SCell BFR or BFR for all cells: the failed serving cell index, the failed CORESET index, and the new beam information.

[0097] Embodiment 6 may include the method according to Embodiment 5 or some other embodiment herein, wherein if BFR for all cells is supported, the failed serving cell index may be at least based on the PsCell and SCell indices, or different MAC CEs may be used for PsCell BFR and SCell BFR with different logical channel IDs.

[0098] Embodiment 7 may include the method according to Embodiment 5 or some other embodiment herein, wherein a separate MAC-CE may be used to carry the C-RNTI and the beam information.

[0099] Embodiment 8 may include the method according to Embodiment 5 or some other embodiment herein, wherein the MAC-CE may be defined to carry the C-RNTI and the beam information.

[0100] Embodiment 9 may include the method according to Embodiment 1 or some other embodiment herein, wherein after K time slots after the UE receives the MsgB PDSCH, the UE applies the newly identified beam to the uplink and / or downlink control channel and / or data channel.

[0101] Embodiment 10 may include the method according to Embodiment 1 or some other embodiment herein, wherein K slots after the UE transmits an ACK for the MsgB PDSCH or after the UE transmits a PUSCH according to the UL grant indicated in MsgB, the UE applies the newly identified beam to the uplink and / or downlink control channel and / or data channel.

[0102] Embodiment 11 may include the method according to Embodiments 9 to 10 or some other embodiment herein, wherein K may be configured by higher layer signaling or predefined, or determined by each subcarrier spacing or the UE capabilities across all subcarrier spacings, or at least based on the minimum subcarrier spacing in DL and UL.

[0103] Embodiment 12 may include the method according to Embodiments 9 to 10 or some other embodiment herein, wherein when the UE starts to apply a new beam to the downlink channel, the UE may apply the new beam to Control Resource Set (CORESET) 0, or all CORESETs, or all CORESETs and all PDSCHs.

[0104] Embodiment 13 may include the method according to Embodiments 9 to 10 or some other embodiment herein, wherein when the UE starts to apply a new beam to the uplink channel, the UE may apply the new beam to the PUCCH, and / or the PUSCH scheduled by DCI format 0_0, and / or the PUSCH scheduled by DCI format 0_1, and / or the SRS for codebook - based or non - codebook - based transmission, and / or the SRS for antenna switching.

[0105] Embodiment 14 may include the method according to Embodiments 9 to 13 or some other embodiment herein, wherein after applying the new beam to the corresponding uplink channel, the power control parameters P0 and α should be at least based on the default power control parameters predefined or configured by higher layer signaling.

[0106] Embodiment 15 may include the method according to Embodiments 9 to 13 or some other embodiment herein, wherein the downlink reference signal for path loss measurement should be at least based on the downlink reference signal associated with the newly identified beam.

[0107] Embodiment 16 may include the method according to Embodiments 9 to 13 or some other embodiment herein, wherein if cumulative closed - loop power control is enabled, the closed - loop power parameters should be reset.

[0108] Embodiment 17 may include the method according to Embodiment 1 or some other embodiment herein, wherein the PRACH and MsgA PUSCH may be transmitted in the PCell or PsCell.

[0109] Embodiment 18 may include the method according to Embodiment 1 or some other embodiment herein, wherein the random access response may be transmitted in another serving cell, and the another serving cell may be configured by higher layer signaling or be a failed serving cell whose cell index is indicated by MsgA PUSCH.

[0110] Embodiment 19 may include a method for a user equipment (UE) in a wireless network, the method including: transmitting a beam failure recovery request (BFRQ) through a physical random access channel (PRACH) and a physical uplink shared channel (PUSCH); and receiving a random access response (RAR) through a physical downlink shared channel (PDSCH).

[0111] Embodiment 20 may include the method according to Embodiment 19 and / or some other embodiment herein, wherein the BFRQ is for a secondary cell (SCell) or a primary SCell (PsCell).

[0112] Embodiment 21 may include the method according to Embodiment 19 and / or some other embodiment herein, the method further including: transmitting the BFRQ as a separate medium access control (MAC) control element (CE).

[0113] Embodiment 22 may include the method according to Embodiment 19 and / or some other embodiment herein, the method further including: resetting the quasi-co-location (QCL) assumption or the spatial relation information assumption for the uplink channel and the downlink channel at least based on the newly identified beam.

[0114] Embodiment 23 may include the method according to Embodiment 19 and / or some other embodiment herein, the method further including: applying the newly identified beam to the uplink and / or downlink control channel and / or data channel.

[0115] Embodiment 24 may include the method according to Embodiment 19 and / or some other embodiment herein, the method further including: determining the power control parameter at least based on the default power control parameter predefined or configured by higher layer signaling.

[0116] Embodiment 25 may include the method according to Embodiment 19 and / or some other embodiment herein, wherein the message in the PUSCH includes a cell radio network temporary ID (C-RNTI), a failed serving cell index, a failed CORESET index, or a new beam quality of the newly identified beam.

[0117] Embodiment 26 may include the method according to Embodiment 25 and / or some other embodiment herein, wherein the new beam quality includes the reference signal received power (RSRP) or the reference signal received quality (RSRQ) of the newly identified beam.

[0118] Embodiment 27 may include the method according to Embodiment 25 and / or some other embodiment herein, wherein the failed serving cell index is at least based on the PsCell and SCell indices, or carries different MAC CEs carrying PsCell BFR and SCell BFR with different logical channel IDs.

[0119] Embodiment 28 may include the method according to any one of Embodiments 19 to 27 and / or some other embodiment herein, wherein the method is performed by a device implemented in or adopted by a UE.

[0120] Embodiment 29 may include a method for a next-generation node B (gNB) in a wireless network, the method including: detecting a beam failure recovery request (BFRQ) via a physical random access channel (PRACH); decoding a message in a physical uplink shared channel (PUSCH); and transmitting a random access response (RAR) via a physical downlink shared channel (PDSCH).

[0121] Embodiment 30 may include the method according to Embodiment 29 and / or some other embodiment herein, wherein the BFRQ is for a secondary cell (SCell) or a primary SCell (PsCell).

[0122] Embodiment 31 may include the method according to Embodiment 29 and / or some other embodiment herein, the method further including: receiving the BFRQ as a separate medium access control (MAC) control element (CE).

[0123] Embodiment 32 may include the method according to Embodiment 29 and / or some other embodiment herein, the method further including: indicating power control parameters by higher layer signaling.

[0124] Embodiment 33 may include the method according to Embodiment 29 and / or some other embodiment herein, wherein the message in the PUSCH includes a cell radio network temporary ID (C-RNTI), a failed serving cell index, a failed CORESET index, or a new beam quality of a newly identified beam.

[0125] Embodiment 34 may include the method according to Embodiment 33 and / or some other embodiment herein, wherein the new beam quality includes the reference signal received power (RSRP) or the reference signal received quality (RSRQ) of the newly identified beam.

[0126] Embodiment 35 may include the method according to Embodiment 33 and / or some other embodiment herein, wherein the failed serving cell index is at least based on the PsCell and SCell indexes, or carries different MAC CEs carrying PsCell BFR and SCell BFR with different logical channel IDs.

[0127] Embodiment 36 may include the method according to Embodiments 29 to 35 and / or some other embodiment herein, wherein the method is performed by a device implemented in or adopted by the gNB.

[0128] Embodiment 37 may include a device that includes means for performing one or more elements of the method according to any one of Embodiments 1 to 36 or related thereto, or any other method or process described herein.

[0129] Embodiment 38 may include one or more non-transitory computer-readable media that include instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of the method according to any one of Embodiments 1 to 36 or related thereto, or any other method or process described herein.

[0130] Embodiment 39 may include a device that includes logic components, modules, or circuits for performing one or more elements of the method according to any one of Embodiments 1 to 36 or related thereto, or any other method or process described herein.

[0131] Embodiment 40 may include the method, technique, or process according to any one of Embodiments 1 to 36 or related thereto, or a part or component thereof.

[0132] Embodiment 41 may include a device that includes: one or more processors and one or more computer-readable media that include instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, technique, or process according to any one of Embodiments 1 to 36 or related thereto, or a part thereof.

[0133] Embodiment 42 may include a signal as described in or related to any one of Embodiments 1 to 36, or a part or component thereof.

[0134] Embodiment 43 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message according to any one of Embodiments 1 to 36 or related thereto, or otherwise described in the present disclosure, or a part or component thereof.

[0135] Example 44 may include a signal encoded with data as described in or related to any one of Examples 1 to 36 or otherwise described in the present disclosure, or a part or component thereof.

[0136] Example 45 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any one of Examples 1 to 36 or otherwise described in the present disclosure, or a part or component thereof.

[0137] Example 46 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process as described in or related to any one of Examples 1 to 36, or a part thereof.

[0138] Example 47 may include a computer program that includes instructions, wherein execution of the program by a processing element will cause the processing element to perform a method, technique, or process as described in or related to any one of Examples 1 to 36, or a part thereof.

[0139] Example 48 may include a signal in a wireless network as shown and described herein.

[0140] Example 49 may include a method of communicating in a wireless network as shown and described herein.

[0141] Example 50 may include a system for providing wireless communication as shown and described herein.

[0142] Example 51 may include a device for providing wireless communication as shown and described herein.

[0143] A first additional example is a device configured to be employed in a user equipment (UE), the device including: one or more processors configured to: generate a physical random access channel (PRACH) associated with a beam failure recovery request (BFRQ); generate a physical uplink shared channel (PUSCH) message associated with the BFRQ, wherein the PUSCH message includes at least one medium access control (MAC) control element (CE), the at least one MAC CE including one or more of an index associated with a cell in which a beam failure is detected or an index associated with a new beam; and process a physical downlink shared channel (PDSCH) as a random access response (RAR) associated with the PRACH and the PUSCH message.

[0144] A second additional example includes the subject matter according to any variation of the first additional example, wherein the cell is a secondary cell (SCell).

[0145] The third additional embodiment includes the subject matter according to any variation of the first to second additional embodiments, wherein the one or more processors are further configured to apply the quasi-co-location parameters of the new beam to one or more control resource sets (CORESETs) on the cell at K time slots after the PDSCH.

[0146] The fourth additional embodiment includes the subject matter according to any variation of the third additional embodiment, wherein one or more CORESETs of the cell are all the CORESETs on the cell.

[0147] The fifth additional embodiment includes the subject matter according to any variation of the third to fourth additional embodiments, wherein K is predefined.

[0148] The sixth additional embodiment includes the subject matter according to any variation of the first to fifth additional embodiments, wherein the one or more processors are further configured to apply the spatial domain filter of the new beam to one or more uplink (UL) channels on the cell at K time slots after the PDSCH.

[0149] The seventh additional embodiment includes the subject matter according to any variation of the sixth additional embodiment, wherein K is predefined.

[0150] The eighth additional embodiment includes the subject matter according to any variation of the sixth to seventh additional embodiments, wherein the one or more processors are further configured to use power for one or more UL channels based at least on one or more default parameters.

[0151] The ninth additional embodiment includes the subject matter according to any variation of the first to eighth additional embodiments, wherein the PUSCH message is one of a message A (MsgA) PUSCH message or a message 4 (Msg4) PUSCH message.

[0152] The tenth additional embodiment includes the subject matter according to any variation of the first to ninth additional embodiments, wherein the cell is a primary secondary cell (PSCell).

[0153] The eleventh additional embodiment includes the subject matter according to any variation of the first to tenth additional embodiments, wherein at least one medium access control (MAC) control element (CE) includes a beam quality metric of the new beam, and the beam quality metric is one of a reference signal received power (RSRP), a reference signal received quality (RSRQ), or a signal-to-interference-plus-noise ratio (SINR).

[0154] The twelfth additional embodiment is a user equipment, and the user equipment includes the subject matter according to any variation of the first to eleventh additional embodiments.

[0155] The thirteenth exemplary embodiment is a device configured to be employed in a base station (BS), the device comprising: one or more processors configured to: process a Physical Random Access Channel (PRACH) associated with a Beam Failure Recovery Request (BFRQ); decode a Physical Uplink Shared Channel (PUSCH) message associated with the BFRQ, wherein the PUSCH message comprises at least one Medium Access Control (MAC) Control Element (CE), the at least one MAC CE comprising one or more of an index associated with a cell in which a beam failure is detected or an index associated with a new beam; and generate a Physical Downlink Shared Channel (PDSCH) as a Random Access Response (RAR) associated with the PRACH and the PUSCH message.

[0156] The fourteenth additional embodiment includes the subject matter according to any variant of the thirteenth additional embodiment, wherein the cell is a Secondary Cell (SCell).

[0157] The fifteenth additional embodiment includes the subject matter according to any variant of the thirteenth to fourteenth additional embodiments, wherein the cell is a Primary and Secondary Cell (PSCell).

[0158] The sixteenth additional embodiment includes the subject matter according to any variant of the thirteenth to fifteenth additional embodiments, wherein the PUSCH message is one of a Message A (MsgA) PUSCH message or a Message 4 (Msg4) PUSCH message.

[0159] The seventeenth exemplary embodiment is a machine-readable medium comprising instructions that, when executed, cause a User Equipment (UE) to: generate a Physical Random Access Channel (PRACH) associated with a Beam Failure Recovery Request (BFRQ); generate a Physical Uplink Shared Channel (PUSCH) message associated with the BFRQ, wherein the PUSCH message comprises at least one Medium Access Control (MAC) Control Element (CE), the at least one MAC CE comprising one or more of an index associated with a Secondary Cell (SCell) in which a beam failure is detected or an index associated with a new beam; and process a Physical Downlink Shared Channel (PDSCH) as a Random Access Response (RAR) associated with the PRACH and the PUSCH message.

[0160] The eighteenth additional embodiment includes the subject matter according to any variant of the seventeenth additional embodiment, wherein the instructions, when executed, further cause the UE to apply quasi-co-location parameters of the new beam to all Control Resource Sets (CORESETs) on the SCell at K time slots after the PDSCH, where K is predefined.

[0161] The nineteenth additional embodiment includes the subject matter according to any variation of the seventeenth to eighteenth additional embodiments, wherein the instructions, when executed, further cause the UE to apply a spatial domain filter of a new beam to one or more uplink (UL) channels on the SCell in K time slots after the PDSCH, where K is predefined.

[0162] The twentieth additional embodiment includes the subject matter according to any variation of the seventeenth to nineteenth additional embodiments, wherein the instructions, when executed, further cause the UE to use power for one or more UL channels based at least on one or more default parameters.

[0163] The twenty - first additional embodiment includes the subject matter according to any variation of the seventeenth to twentieth additional embodiments, wherein the PUSCH message is one of a Message A (MsgA) PUSCH message or a Message 4 (Msg4) PUSCH message.

[0164] The twenty - second additional embodiment includes an apparatus that includes means for performing any of the operations described according to the first to twenty - first additional embodiments.

[0165] The twenty - third additional embodiment includes a machine - readable medium that stores instructions for execution by a processor to perform any of the operations described according to the first to twenty - first additional embodiments.

[0166] The twenty - fourth additional embodiment includes an apparatus that includes: a memory interface; and a processing circuit configured to: perform any of the operations described according to the first to twenty - first additional embodiments.

[0167] The foregoing description of illustrative embodiments of the subject matter of the present disclosure, which includes what is described in the abstract of the specification, is not intended to be exhaustive or to limit the disclosed embodiments to the precise forms disclosed. While specific embodiments and examples are described herein for illustrative purposes, various modifications can be contemplated within the scope of such embodiments and examples, as will be recognized by those of ordinary skill in the relevant art.

[0168] In this regard, while the subject matter of the present invention has been described in connection with various embodiments and the corresponding drawings, it should be understood that other similar embodiments may be used or modifications and additions may be made to the described embodiments to perform the same, similar, alternative, or substitute functions of the disclosed subject matter without departing from the described embodiments. Accordingly, the disclosed subject matter should not be limited to any single embodiment described herein, but should be construed in accordance with the breadth and scope of the following appended claims.

[0169] Particularly with respect to the various functions performed by the above-described components or structures (assemblies, devices, circuits, systems, etc.), unless otherwise specified, the terms used to describe such components (including references to "means") are intended to correspond to any component or structure that performs the specified function of the described component (e.g., functionally equivalent), even if not structurally equivalent to the disclosed structure that performs the function in the exemplary specific implementations shown herein. Additionally, although a particular feature has been disclosed with respect to only one of a plurality of specific implementations, for any given or particular application, such feature may be combined with one or more other features of one or more other specific implementations, which may be desirable and advantageous.

Claims

1. An apparatus configured to be employed in a user equipment UE, the apparatus comprising: one or more processors configured to: as part of a two-step random access RACH procedure on a primary cell PCell or a primary-secondary cell PSCell, transmit a physical random access channel PRACH message associated with a beam failure recovery request BFRQ and a physical uplink shared channel PUSCH message associated with the BFRQ, wherein the PUSCH message includes at least one medium access control MAC control element CE and a separate MAC CE, the at least one medium access control MAC control element CE includes information, the information includes an index associated with a secondary cell SCell where a beam failure is detected, an indication of an index associated with a new beam, and the separate MAC CE includes a cell radio network temporary identifier C-RNTI of the UE; receive a physical downlink shared channel PDSCH message as a random access response RAR associated with the PRACH message and the PUSCH message; and use quasi-co-location parameters of the new beam for all control resource sets CORESETs on the SCell after 2 time slots after the PDSCH.

2. The apparatus according to claim 1, wherein the one or more CORESETs of the cell are all CORESETs on the cell.

3. The apparatus according to claim 1, wherein the one or more processors are further configured to apply a spatial domain filter of the new beam to one or more uplink UL channels on the cell K time slots after the RAR.

4. The apparatus according to claim 3, wherein K is predefined.

5. The apparatus according to claim 3, wherein the one or more processors are further configured to use power for one or more UL channels based at least on one or more default parameters.

6. The apparatus according to any one of claims 1 to 5, wherein the PUSCH message is a message A MsgA PUSCH message.

7. The apparatus according to any one of claims 1 to 5, wherein the at least one medium access control MAC control element CE includes a beam quality metric of the new beam, and the beam quality metric is one of a reference signal received power RSRP, a reference signal received quality RSRQ, or a signal-to-interference-plus-noise ratio SINR.

8. A UE comprising the apparatus according to any one of claims 1 to 7.

9. An apparatus configured to be employed in a base station BS, the apparatus comprising: one or more processors configured to: as part of a two-step random access RACH procedure on a primary cell PCell, receive a physical random access channel PRACH message associated with a beam failure recovery request BFRQ and a physical uplink shared channel PUSCH message associated with the BFRQ, Wherein the PUSCH message includes at least one medium access control (MAC) control element (CE) and a separate MAC CE, the at least one MAC control element CE includes information, the information includes an index associated with a secondary cell (SCell) where a beam failure is detected, an indication of an index associated with a new beam, and the separate MAC CE includes the cell radio network temporary identifier (C-RNTI) of the UE; Transmit a physical downlink shared channel (PDSCH) message as a random access response (RAR) in response to the PRACH message and the PUSCH message; and Use the quasi-co-location parameters of the new beam for all control resource sets (CORESETs) on the SCell after 2 time slots after the PDSCH.

10. The apparatus according to claim 9, wherein the PUSCH message is a Message A (MsgA) PUSCH message.

11. A machine-readable medium comprising instructions that, when executed, cause a user equipment (UE) to: Transmit a physical random access channel (PRACH) message associated with a beam failure recovery request (BFRQ) and a physical uplink shared channel (PUSCH) message associated with the BFRQ on a primary cell (PCell) or a primary-secondary cell (PSCell) as part of a two-step random access (RACH) procedure, Wherein the PUSCH message includes at least one MAC control element CE and a separate MAC CE, the at least one MAC control element CE includes information, the information includes an index associated with an SCell where a beam failure is detected, an indication of an index associated with a new beam, and the separate MAC CE includes the C-RNTI of the UE; Receive a PDSCH message as a RAR associated with the PRACH message and the PUSCH message; and Use the quasi-co-location parameters of the new beam for all CORESETs on the SCell after 2 time slots after the PDSCH.

12. The machine-readable medium according to claim 11, wherein the instructions, when executed, further cause the UE to apply a spatial domain filter of the new beam to one or more uplink (UL) channels on the SCell K time slots after the RAR, where K is predefined.

13. The machine-readable medium according to claim 12, wherein the instructions, when executed, further cause the UE to use power for one or more UL channels based at least on one or more default parameters.

14. The machine-readable medium according to any one of claims 11 to 13, wherein the PUSCH message is a MsgA PUSCH message.

15. The machine-readable medium according to claim 11, wherein the one or more CORESETs of the SCell are all CORESETs on the SCell.

16. The machine-readable medium according to any one of claims 11 to 13 or 15, wherein the at least one medium access control (MAC) control element (CE) includes a beam quality metric of the new beam, and the beam quality metric is one of a reference signal received power (RSRP), a reference signal received quality (RSRQ), or a signal-to-interference-plus-noise ratio (SINR).

17. A method of communication, comprising: transmitting, on a primary cell (PCell) or a primary and secondary cell (PSCell), as part of a two-step random access (RACH) procedure, a physical random access channel (PRACH) message associated with a beam failure recovery request (BFRQ) and a physical uplink shared channel (PUSCH) message associated with the BFRQ, wherein the PUSCH message includes at least one medium access control (MAC) control element (CE) and a separate MAC CE, the at least one MAC CE includes information, the information includes an index associated with a secondary cell (SCell) in which a beam failure is detected, an indication of an index associated with a new beam, and the separate MAC CE includes a cell radio network temporary identifier (C-RNTI) of the UE; receiving a physical downlink shared channel (PDSCH) message as a random access response (RAR) associated with the PRACH message and the PUSCH message; and using quasi-co-location parameters of the new beam for all control resource sets (CORESETs) on the SCell after 2 time slots after the PDSCH.

18. The method according to claim 17, wherein the one or more CORESETs of the cell are all CORESETs on the cell.

19. The method according to claim 17, further comprising: applying a spatial domain filter of the new beam to one or more uplink (UL) channels on the cell K time slots after the RAR.

20. The method according to claim 19, wherein K is predefined.

21. The method according to claim 20, further comprising: using power for the one or more UL channels based at least on one or more default parameters.

22. The method according to any one of claims 17 to 21, wherein the PUSCH message is a message A (MsgA) PUSCH message.

23. The method according to any one of claims 17 to 21, wherein the at least one medium access control (MAC) control element (CE) includes a beam quality metric of the new beam, and the beam quality metric is one of a reference signal received power (RSRP), a reference signal received quality (RSRQ), or a signal-to-interference-plus-noise ratio (SINR).

24. A method of communication, comprising: receiving, on a primary cell (PCell) or a primary and secondary cell (PSCell), as part of a two-step random access (RACH) procedure, a physical random access channel (PRACH) message associated with a beam failure recovery request (BFRQ) and a physical uplink shared channel (PUSCH) message associated with the BFRQ, Wherein the PUSCH message includes at least one medium access control (MAC) control element (CE) and a separate MAC CE, the at least one MAC CE includes information, the information includes an index associated with a secondary cell (SCell) where a beam failure is detected, an indication of an index associated with a new beam, and the separate MAC CE includes a cell radio network temporary identifier (C-RNTI) of the UE; Transmit a physical downlink shared channel (PDSCH) message as a random access response (RAR) associated with the PRACH and the PUSCH message; and Use the quasi-co-location parameters of the new beam for all control resource sets (CORESETs) on the SCell after 2 time slots after the PDSCH.

25. The method according to claim 24, wherein the PUSCH message is one of a message A MsgA PUSCH message or a message 4 Msg4 PUSCH message.

26. A base station, the base station includes the apparatus according to any one of claims 9 to 10.

27. A machine-readable medium including instructions, the instructions when executed cause a base station (BS) to: Receive, on a primary cell (PCell), as part of a two-step random access (RACH) procedure, a physical random access channel (PRACH) message associated with a beam failure recovery request (BFRQ) and a physical uplink shared channel (PUSCH) message associated with the BFRQ, Wherein the PUSCH message includes at least one medium access control (MAC) control element (CE) and a separate MAC CE, the at least one medium access control (MAC) control element (CE) includes information, the information includes an index associated with a secondary cell (SCell) where a beam failure is detected, an indication of an index associated with a new beam, and the separate MAC CE includes a cell radio network temporary identifier (C-RNTI) of the UE; Transmit a physical downlink shared channel (PDSCH) message as a random access response (RAR) associated with the PRACH and the PUSCH message; and Use the quasi-co-location parameters of the new beam for all control resource sets (CORESETs) on the SCell after 2 time slots after the PDSCH.

28. The machine-readable medium according to claim 27, wherein the PUSCH message is a message A MsgA PUSCH message.

Images