Beam Management Extension for Discontinuous Reception (DRX) Operation

Abstract

To extend beam management for user equipment (UE) operating in an intermittent reception (DRX) mode.SOLUTION: UE processes upper layer signaling that configures, for a cell, signaling that, at each time during a DRX cycle, includes a synchronization signal block (SSB) associated with time and a beam or a channel state information reference signal (CSI-RS) associated with the time and beam, and that is associated with the time and a first beam, in which the time depends on whether ability of the UE meets a minimum performance level of the beam, and includes a first time within a DRX-on duration of the UE, a second time outside the DRX-on duration of the UE, or both first time and second time, measures signaling associated with the time and beam, and determines if a beam failure of the beam has occurred on the basis of the measured signaling associated with the time and the beam.SELECTED DRAWING: Figure 10

Description

Technical Field

[0001] The present disclosure relates to wireless technology, and more specifically, to techniques associated with extending beam management for user equipment (UE) operating in discontinuous reception (DRX) mode.

Background Art

[0002] The Third Generation Partnership Project (3GPP) Fifth Generation (5G) New Radio (NR) radio access technology (RAT) is a newly developed radio interface for 5G. 5G NR uses frequency bands within two separate frequency ranges: Frequency Range 1 (FR1) including sub-6 GHz frequency bands, and Frequency Range 2 (FR2) including frequency bands above 6 GHz (e.g., including millimeter wave (mmWave) with frequency bands above 24 GHz).

Brief Description of the Drawings

[0003]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

DETAILED DESCRIPTION OF THE INVENTION

[0004] Here, the present disclosure will be described with reference to the accompanying drawings, where like reference numerals are used throughout to refer to like elements, and the structures and devices illustrated are not necessarily drawn to scale. As used herein, terms such as "component", "system", "interface", etc. are intended to refer to computer-related entities, hardware, (e.g., executing) software, and / or firmware. For example, a component can be a processor (e.g., a microprocessor, a controller, or other processing device), a process executing on the processor, a controller, an object, an executable file, a program, a storage device, a computer, a tablet PC, and / or a user device (e.g., a mobile phone, etc.) equipped with a processing device. As an example, an application executing on a server and the server itself can also be components. One or more components can reside within a process, one component can be localized on one computer, and / or can be distributed between two or more computers. In this specification, sets of elements or other sets of components may be described, where the term "set" can be interpreted as "one or more".

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

[0006] As another example, a component can be a device having a specific functionality provided by a mechanical part 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 functionality through an electronic component without a mechanical part, and the electronic component can include one or more processors for executing software and / or firmware that at least partially imparts the functionality of the electronic component.

[0007] The use of the word "exemplary" is intended to concretely represent an idea. The term "or" as used in this application is intended to mean an inclusive "or" rather than an exclusive "or". That is, unless otherwise specified or clear from the context, "X uses A or B" is intended to mean any of all possible permutations. That is, in the case where "X uses A", in the case where "X uses B", or in the case where "X uses both A and B", each of the foregoing cases satisfies "X uses A or B". In addition, the articles "a" and "an" used in this application and the appended claims should generally be construed to mean "one or more" unless otherwise specified or it is clear from the context that they refer to the singular form. Further, when "including", "includes", "having", "has", "with", or variations thereof are used in either the embodiments for carrying out the invention or the claims, these terms are intended to be as inclusive as the term "comprising". Further, in situations where one or more numbered items are detailed (e.g., "the first X", "the second X", etc.), in some situations, the context may indicate whether the one or more numbered items are distinct or the same, but generally, these one or more numbered items can be distinct or the same.

[0008] As used herein, the term "circuit" may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and / or a memory (shared, dedicated, or group), combinational logic circuit, and / or other suitable hardware components that execute one or more software programs or firmware programs, or provide the described functionality. In some embodiments, the circuit may be implemented in one or more software or firmware modules, or the functionality associated with the circuit may be executed by one or more software or firmware modules. In some embodiments, the circuit may include logic that is at least partially operable in hardware.

[0009] The various aspects described herein may be related to facilitating wireless communications, and the nature of these communications may vary.

[0010] It should be well understood that the use of personally identifiable information should comply with privacy policies and practices that meet or exceed industry or government requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled to minimize the risk of unintended or unauthorized access or use, and the nature of the permitted use should be clearly disclosed to the user.

[0011] FR1 overlaps with and / or shares some frequency bands used by other RATs (e.g., Fourth Generation (4G) Long Term Evolution (LTE) bands), while FR2 is a design feature specific to 5G NR, which not only offers numerous advantages but also poses challenges. FR2 enables the UE to access much higher bandwidths, which can be beneficial for services that benefit from high data speeds and / or low latency. However, FR2 has the drawback of increased path loss compared to lower frequencies. To address this, beamforming can be used for communication in FR2.

[0012] Due to the directivity of the beam as a property, beam management can be performed at the UE and radio access network (RAN) nodes such as the next-generation Node B (gNB). FR2 operation typically relies on analog beamforming. As a result, the UE is assumed to measure the quality of different beams by time-division multiplexing (TDM) for beam management, which can consume a significant amount of resource overhead and increase latency. Furthermore, the UE beam can change frequently for various reasons. Since the beam is more directional, a slight rotation of the UE or a change in the environment can dramatically change the optimal beam direction. Additionally, due to the higher frequency of FR2, beam blockage is more severe, which results in significantly worse penetration loss and path loss.

[0013] Furthermore, FR2 operation may involve increased power consumption and thermal issues. The increased power consumption can be attributed to baseband processing, transmission for the highest possible data rates via FR2, and even access point (AP) loading. To offset these drawbacks, discontinuous transmission (DTX) and / or discontinuous reception (DRX) can be used, which can essentially reduce the UE uplink (UL) and downlink (DL) duty cycles.

[0014] Aspects described in this specification can be implemented in a system using any suitably configured hardware and / or software. FIG. 1 shows the architecture of a system 100 that includes a core network (CN) 120, e.g., a 5th generation (5G) CN (5GC), according to various embodiments. As shown in the figure, system 100 includes a UE 101 that can be the same as or similar to one or more other UEs described herein, a 3rd Generation Partnership Project (3GPP) radio access network (radio AN or RAN) or other (e.g., non-3GPP) AN, one or more RAN nodes (e.g., evolved Node B (eNB), next generation Node B (gNB), and / or other nodes) or other nodes or access points, which can be included in (R)AN 210, a data network (DN) 203, which can be, for example, an operator service, Internet access, or a third-party service, and a 5th generation core network (5GC) 120. 5GC 120 can include one or more of the following functions and network components: Authentication Server Function (AUSF) 122, Access and Mobility Management Function (AMF) 121, Session Management Function (SMF) 124, Network Exposure Function (NEF) 123, Policy Control Function (PCF) 126, Network Repository Function (NRF) 125, Unified Data Management (UDM) 127, Application Function (AF) 128, User Plane (UP) function (UPF) 102, and Network Slice Selection Function (NSSF) 129.

[0015] UPF102 can function as an anchor point for mobility within and between RATs, an external protocol data unit (PDU) session point for interconnecting with DN103, and a branching point for supporting multi-home PDU sessions. UPF102 also performs packet routing and forwarding, packet inspection, enforces the user plane part of policy rules, lawfully intercepts packets (UP collection), performs traffic usage reporting, performs QoS processing for the user plane (e.g., packet filtering, gating, uplink (UL) / downlink (DL) rate enforcement), performs uplink traffic verification (e.g., mapping from service data flow (SDF) to quality of service (QoS) flow), performs transport level packet marking for both uplink and downlink, and can perform downlink packet buffering and downlink data notification triggering. UPF102 may include an uplink classifier for supporting routing traffic flows to the data network. DN103 can present various network operator services, Internet access, or third-party services. DN103 may include or be similar to an application server. UPF102 can interact with SMF124 via the N4 reference point between SMF124 and UPF102.

[0016] The AUSF 122 can store the data for authenticating the UE 101 and handle authentication-related functionality. 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. In addition, the AUSF 122 can present an Nausf service-based interface.

[0017] The AMF 121 can be involved in registration management (for example, registering the UE 101, etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, as well as access authentication and authorization. The AMF 121 can be a termination point for the N11 reference point between the AMF 121 and the SMF 124. The AMF 121 can provide the transport of SM messages between the UE 101 and the SMF 124 and function as a transparent proxy for routing SM messages. The AMF 121 can also provide the transport of SMS messages between the UE 101 and a Short Message Service Function (SMSF) (not shown in FIG. 1). The AMF 121 can function as a Security Anchor Function (SEAF) that can include the interaction with the AUSF 122 and the UE 101 and / or the reception of an intermediate key established as a result of the UE 101 authentication process. When Universal Subscriber Identity Module (USIM)-based authentication is used, the AMF 121 can obtain security materials from the AUSF 122. The AMF 121 can also include a Single-Connection Mode (SCM) function that receives a key used to derive an access network-specific key from the SEA. Further, the AMF 121 can be a termination point of the Radio Access Network (RAN) Control Plane (CP) interface that is or can include the N2 reference point between the (R)AN 110 and the AMF 121, and the AMF 121 can also be a termination point for Non-Access Stratum (NAS) (N1) signaling and can perform NAS encryption and integrity protection.

[0018] AMF121 can also support NAS signaling with UE101 via the Non-3GPP (N3) Inter Working Function (IWF) interface. The N3IWF can be used to provide access to untrusted entities. The N3IWF can serve as a termination point for the N2 interface between the (R)AN110 and the AMF121 for the control plane, and can serve as a termination point for the N3 reference point between the (R)AN110 and the UPF102 for the user plane. Thus, the AMF121 can handle N2 signaling from the SMF124 and the AMF121 for PDU sessions and QoS, encapsulate / decapsulate packets for Internet Protocol (IP) security (IPSec) and N3 tunneling, mark the N3 user plane packets in the uplink, and enforce QoS corresponding to the N3 packet marking taking into account the QoS requirements associated with such marking received via N2. The N3IWF can also relay the uplink and downlink control plane NAS signaling between the UE101 and the AMF121 via the N1 reference point between the UE101 and the AMF121, and can relay the uplink user plane packets and downlink user plane packets between the UE101 and the UPF102. The N3IWF also provides a mechanism for establishing an IPsec tunnel with the UE101. The AMF121 can present a Namf service-based interface and can be a termination point for the N14 reference point between two AMF121s and for the N17 reference point between the AMF121 and the 5G Equipment Identity Register (5G-EIR) (not shown in Figure 1).

[0019] UE101 can register with the AMF121 to receive network services. Registration Management (RM) is used to register or deregister the UE101 with the network (e.g., AMF121) and establish a UE context within the network (e.g., AMF121). UE101 can operate in the RM-REGISTERED state or the RM-DEREGISTERED state. In the RM-DEREGISTERED state, UE101 is not registered with the network, and the UE context in the AMF121 does not hold valid location or routing information regarding UE101 so that UE101 cannot be reached by the AMF121. In the RM-REGISTERED state, UE101 is registered with the network, and the UE context in the AMF121 can hold valid location or routing information for UE101 so that UE101 can be reached by the AMF121. In the RM-REGISTERED state, among other things, UE101 can execute a mobility registration update procedure, execute a periodic registration update procedure triggered by the expiration of a periodic update timer (e.g., to notify the network that UE101 is still active), update UE capability information, or execute a registration update procedure, among other things, to renegotiate protocol parameters with the network.

[0020] The AMF 121 can store one or more RM contexts for the UE 101, and each RM context is associated with a specific access to the network. The RM context can be, among other things, a data structure, a database object, etc. that indicates or stores the registration state and the periodic update timer for each access type. The AMF 121 can also store a 5GC mobility management (MM) context that can be the same as or similar to the (Enhanced Packet System (EPS)) mobility management (MM) (Enterprise Mobility Management ((E)MM)) context. In various embodiments, the AMF 121 can store the UE 101's Coverage Enhancement (CE) mode B regulation parameters in the associated MM context or RM context. The AMF 121 can also derive values from the UE usage setting parameters already stored in the UE context (and / or MM / RM context) as needed.

[0021] Connection Management (CM) can be used for the establishment and release of signaling connections via the N1 interface between the UE 101 and the AMF 121. The signaling connection is used to enable NAS signaling exchange between the UE 101 and the CN 120, and includes both a signaling connection between the UE and the AN (e.g., a Radio Resource Control (RRC) connection for non-3GPP access or a UE-N3IWF connection) and an N2 connection for the UE 101 between the AN (e.g., the RAN 110) and the AMF 121. The UE 101 can operate in either of two CM states: the CM-IDLE mode or the CM-CONNECTED mode. When the UE 101 is operating in the CM-IDLE state / mode, there may not be an established NAS signaling connection via the N1 interface to the AMF 121, but there may be a (R)AN 110 signaling connection (e.g., N2 and / or N3 connections) for the UE 101. When the UE 101 is operating in the CM-CONNECTED state / mode, the UE 101 can have an established NAS signaling connection via the N1 interface to the AMF 121, and there may be a (R)AN 110 signaling connection (e.g., N2 and / or N3 connections) for the UE 101. The establishment of the N2 connection between the (R)AN 110 and the AMF 121 enables 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.

[0022] SMF124 can be involved in the following: 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, configuration of traffic steering in the UPF for routing traffic to the appropriate destination, termination of the interface with the policy control function, policy enforcement and partial control of QoS, lawful interception (of SM events and the interface with the Lawful Interception (LI) system), termination of the SM part of NAS messages, downlink data notification, initiation of AN-specific SM information sent to the AN via the AMF over N2, determination of the session and service continuity (SSC) mode of the session. SM can refer to the management of PDU sessions, and a PDU session or "session" can refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE101 and a data network (DN) 103 identified by a Data Network Name (DNN). The PDU session is established in response to a request from the UE101 using NAS SM signaling exchanged between the UE101 and the SMF124 via the N1 reference point, modified in response to requests from the UE101 and the 5GC120, and released in response to requests from the UE101 and the 5GC120. The 5GC120 can trigger a specific application in the UE101 when requested by an application server. In response to the receipt of a trigger message, the UE101 can pass the trigger message (or the relevant part / information of the trigger message) to one or more identified applications within the UE101. The identified applications within the UE101 can establish a PDU session to a specific DNN. The SMF124 can check whether the request from the UE101 conforms to the user subscription information associated with the UE101.At that time, the SMF 124 can obtain and / or request to receive an update notification regarding the SMF 124 level subscription data from the UDM 127.

[0023] The SMF 124 may include the following roaming functions: local enforcement processing for applying a QoS service level agreement (SLA) (visited public land mobile network (VPLMN)), collection of charging data and charging interface (VPLMN), lawful interception (of SM events within the VPLMN and the interface to the LI system), support for interaction with an external DN for the transmission of signaling for authorization / authentication of a PDU session by the external DN. The N16 reference point between two SMFs 124 may be included in the system 100 and, in a roaming scenario, this may be between another SMF 124 within the visited network and the SMF 124 within the home network. In addition, the SMF 124 can present an Nsmf service-based interface.

[0024] NEF123 can provide means for securely exposing services and capabilities provided by 3GPP network functions to third parties, internal disclosure / re-disclosure, application functions (e.g., AF128), edge computing or fog computing systems, etc. In such embodiments, NEF123 can authenticate, authorize, and / or filter the AF. NEF123 can also convert information exchanged with the AF128 and information exchanged with internal network functions. For example, NEF123 can perform conversion between an AF service identifier and internal 5GC information. NEF123 can also receive information from other network functions (NFs) based on the exposed capabilities of other network functions. This information can be stored in NEF123 as structured data or in a data storage NF using a standardized interface. The stored information can then be re-exposed by NEF123 to other NFs and AFs and / or used for other purposes such as analysis. Additionally, NEF123 can present an Nnef service-based interface.

[0025] NRF125 can support a service discovery function, receive NF discovery requests from NF instances, and provide information on the discovered NF instances to the NF instances. NRF125 also maintains information on available NF instances and the services they support. As used herein, the terms "instantiate", "instantiation", etc. can refer to the creation of an instance, and an "instance" can refer to a specific occurrence of an object that can occur, for example, during the execution of program code. Additionally, NRF125 can present an Nnrf service-based interface.

[0026] The PCF 126 can provide policy rules to the control plane function and enforce them, and can also support an integrated policy framework to control network behavior. The PCF 126 can also implement a functional entity (FE) to access subscription information related to policy decision-making in the Unified Data Repository (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 may include the PCF 126 and the AMF 121 within the visited network in the case of 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 can 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 may also include an N24 reference point between the PCF 126 (within the home network) and the PCF 126 within the visited network. Further, the PCF 126 can present an Npcf service-based interface.

[0027] UDM127 can handle subscription-related information to support the processing of communication sessions by network entities and can store the subscription data of UE101. For example, the subscription data can be communicated between UDM127 and AMF121 via the N8 reference point between UDM127 and AMF. UDM127 may include two parts, an application function entity (FE) and an integrated data repository (UDR) (the FE and UDR are not shown in FIG. 1). The UDR can store the subscription data and policy data of UDM127 and PCF126, and / or structured data for the disclosure of NEF123 and application data (including Packet Flow Description (PFD) for application detection, application request information for multiple UEs101). The Nudr service-based interface can be presented by UDR221, enabling UDM127, PCF126, and NEF123 to access a specific set of stored data and perform read, update (e.g., add, modify), delete, and notification subscription of related data changes within the UDR. The UDM may include a UDM FE responsible for processing such as credentials, location management, and subscription management. Several different FEs can provide services to the same user in different transactions. 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 SMF124 via the N10 reference point between UDM127 and SMF124. UDM127 can also support SMS management where the SMS-FE implements application logic similar to that described elsewhere in this specification. In addition, UDM127 can present a Nudm service-based interface.

[0028] AF128 can affect application traffic routing, provide access to NEF123, and interact with the policy framework for policy control. 5GC120 and AF128 can provide each other with information that can be used in edge computing implementations via NEF123. In such an implementation form, network operator and third-party services can be hosted close to the access point of the UE101 attachment to achieve efficient service delivery through reduced end-to-end latency and load of the transport network. For edge computing implementations, 5GC can select UPF102 close to UE101 and perform traffic steering from UPF102 to DN103 via the N6 interface. This can be based on UE subscription data, UE location, and information provided by AF128. In this way, AF128 can affect UPF (re)selection and traffic routing. Based on the operator's arrangement, when AF128 is considered a trustworthy entity, the network operator can allow AF128 to interact directly with the related NF. In addition, AF128 can present a Naf service-based interface.

[0029] The NSSF 129 can select a set of network slice instances that provide services to the UE 101. The NSSF 129 can also, if necessary, determine the mapping to the permitted Network Slice Selection Assistance Information (NSSAI) and the subscribed single NSSAI (S-NSSAI). The NSSF 129 can also, based on a suitable configuration, sometimes query the NRF 125 to determine the set of AMFs or the list of candidate AMFs 121 used to provide services to the UE 101. The selection of the set of network slice instances for the UE 101 can be triggered by the AMF 121 in which the UE 101 is registered by interacting with the NSSF 129, which can result in a change of the AMF 121. The NSSF 129 can interact with the AMF 121 via the N22 reference point between the AMF 121 and the NSSF 129 and communicate with another NSSF 129 in the visited network via the N31 reference point (not shown in Figure 1). In addition, the NSSF 129 can present an Nnssf service-based interface.

[0030] As described above, the CN 120 can include an SMSF that is involved in checking and verifying SMS subscriptions and relaying SM messages transmitted and received between the UE 101 and other entities such as, for example, a SMS-Gateway Mobile Services Switching Center (SMS-GMSC) / Inter-Working Mobile Switching Center (IWMSC) / SMS router. The SMSF can also interact with the AMF 121 and the UDM 127 for procedures to notify that the UE 101 is available for SMS forwarding (e.g., set the UE unreachable flag and notify the UDM 127 when the UE 101 is available for SMS).

[0031] CN120 may also include other elements not shown in FIG. 1, such as a data storage system / architecture, a 5G-EIR, a Security Edge Protection Proxy (SEPP), etc. The data storage system may include a Structured Data Storage Function (SDSF), an Unstructured Data Storage Function (UDSF), and / or the like. All NFs can store / acquire unstructured data (e.g., UE context) from / to the UDSF via an N18 reference point (not shown in FIG. 1) between any NF and the UDSF. Individual NFs can share the UDSF to store each unstructured data, or each individual NF can have its own UDSF at or near the individual NF. In addition, the UDSF can present a Nudsf service-based interface (not shown in FIG. 1). The 5G-EIR can be an NF that checks the status of a Permanent Equipment Identifier (PEI) to determine whether a specific device / entity is listed in the network's blacklist, and the SEPP can be a non-transparent proxy that performs topology hiding, message filtering, and policing on the PLMN-to-PLMN control plane interface.

[0032] In addition, there may be many more reference points and / or service-based interfaces between NF services within the NF. However, in FIG. 1, these interfaces and reference points are omitted for clarity. In one example, CN120 may include an Nx interface, which is an inter-CN interface between a Mobility Management Entity (MME) (e.g., a non-5G MME) and AMF121 to enable interworking between CN120 and a non-5G CN. Other exemplary interfaces / reference points may include an N5g-EIR service-based interface presented by the 5G-EIR, an N27 reference point between the Network Repository Function (NRF) in the visited network and the NRF in the home network, and an N31 reference point between the NSSF in the visited network and the NSSF in the home network.

[0033] FIG. 2 shows exemplary components of a device 200 according to some embodiments. In some embodiments, device 200 may include at least an integrated application circuit 202, a baseband circuit 204, a radio frequency (RF) circuit 206, a front-end module (FEM) circuit 208, one or more antennas 210, and a power management circuitry (PMC) 212, as shown at least in the figure. The components of device 200 shown in the figure may be included in a UE or a RAN node. In some embodiments, device 200 may include fewer elements (e.g., a RAN node may not utilize application circuit 202 and instead may include a processor / controller for processing IP data received from a CN such as 5GC 120 or an Evolved Packet Core (EPC)). In some embodiments, device 200 may include additional elements such as, for example, a memory / storage device, a display, a camera, a sensor, or an input / output (I / O) interface. In other embodiments, the components described below may be included in two or more devices (e.g., the above circuits may be separately included in two or more devices for a Cloud-RAN (C-RAN) implementation).

[0034] The application circuit 202 may include one or more application processors. For example, the application circuit 202 may include, but is not limited to, circuits such as one or more single-core processors or multi-core processors. The processor may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processor may be coupled to a memory / storage device or may include a memory / storage device, and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to be executed on the device 200. In some embodiments, the processor of the application circuit 202 can process IP data packets received from the EPC.

[0035] The baseband circuit 204 may include, but is not limited to, circuits such as one or more single-core processors or multi-core processors. The baseband circuit 204 may include one or more baseband processors or control logics to process the baseband signal received from the receive signal path of the RF circuit 206 and generate a baseband signal for the transmit signal path of the RF circuit 206. The baseband processing circuit 204 can interface with the application circuit 202 to generate and process the baseband signal and control the operation of the RF circuit 206. For example, in some embodiments, the baseband circuit 204 includes a third-generation (3G) baseband processor 204A, a fourth-generation (4G) baseband processor 204B, a fifth-generation (5G) baseband processor 204C, or other baseband processors 204D of other existing generations, generations under development, or future generations (e.g., second-generation (2G), sixth-generation (6G), etc.). The baseband circuit 204 (e.g., one or more of the baseband processors 204A to 204D) can handle various radio control functions that enable communication with one or more radio networks via the RF circuit 206. In another embodiment, some or all of the functions of the baseband processors 204A to 204D may be included in modules stored in the memory 204G and executed via the central processing unit (CPU) 204E. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuit of the baseband circuit 204 may include fast-Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuit of the baseband circuit 204 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity-check (LDPC) encoder / decoder functionality.Embodiments of modulation / demodulation and encoder / decoder functions are not limited to these examples and may include other suitable functions in other embodiments.

[0036] In some embodiments, baseband circuit 204 may include one or more audio digital signal processors (DSPs) 204F. The audio DSP 204F may include elements for compression / decompression and echo cancellation and, in other embodiments, may include other suitable processing elements. The components of the baseband circuit may be suitably combined within a single chip, a single chipset, or, in some embodiments, may be arranged on the same circuit board. In some embodiments, some or all of the constituent components of baseband circuit 204 and application circuit 202 may be integrally implemented, for example, on a system on a chip (SOC).

[0037] In some embodiments, baseband circuit 204 can provide communication compatible with one or more wireless technologies. For example, in some embodiments, baseband circuit 204 can support communication with next generation (NG)-radio access network (RAN), evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area network (WMAN), wireless local area network (WLAN), wireless personal area network (WPAN), etc. Embodiments in which baseband circuit 204 is configured to support wireless communication of two or more wireless protocols can be referred to as multi-mode baseband circuits.

[0038] The RF circuit 206 can enable communication with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuit 206 can include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. The RF circuit 206 can include a receive signal path that can include circuitry for down-converting the RF signal received from the FEM circuit 208 and providing the baseband signal to the baseband circuit 204. The RF circuit 206 can also include a transmit signal path that can include circuitry for up-converting the baseband signal provided by the baseband circuit 204 and providing an RF output signal for transmission to the FEM circuit 208.

[0039] In some embodiments, the receive signal path of the RF circuit 206 can include a mixer circuit 206a, an amplifier circuit 206b, and a filter circuit 206c. In some embodiments, the transmit signal path of the RF circuit 206 can include a filter circuit 206c and a mixer circuit 206a. The RF circuit 206 can also include a synthesizer circuit 206d for synthesizing the frequencies used by the mixer circuit 206a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuit 206a of the receive signal path can be configured to down-convert the RF signal received from the FEM circuit 208 based on the synthesized frequency provided by the synthesizer circuit 206d. The amplifier circuit 206b can be configured to amplify the down-converted signal, and the filter circuit 206c can be a low-pass filter (LPF) or a band-pass filter (BPF) configured to remove unwanted signals from the down-converted signal and generate an output baseband signal. The output baseband signal may be provided to the baseband circuit 204 for further processing. In some embodiments, the output baseband signal can be a zero-frequency baseband signal, but this is not a requirement. In some embodiments, the mixer circuit 206a of the receive signal path can include a passive mixer, but the scope of the embodiments is not limited in this regard.

[0040] In some embodiments, the mixer circuit 206a of the transmission signal path may be configured to up-convert an input baseband signal based on the combined frequency provided by the combining circuit 206d to generate an RF output signal for the FEM circuit 208. The baseband signal may be provided by the baseband circuit 204 and may be filtered by the filter circuit 206c.

[0041] In some embodiments, the mixer circuit 206a of the receive signal path and the mixer circuit 206a of the transmission signal path may include two or more mixers and may be arranged for quadrature down-conversion and quadrature up-conversion, respectively. In some embodiments, the mixer circuit 206a of the receive signal path and the mixer circuit 206a of the transmission signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley-type image rejection). In some embodiments, the mixer circuit 206a of the receive signal path and the mixer circuit 206a may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, the mixer circuit 206a of the receive signal path and the mixer circuit 206a of the transmission signal path may be configured for superheterodyne operation.

[0042] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, but the scope of the embodiments is not limited in this regard. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, the RF circuit 206 may include an analog-to-digital converter (ADC) and a digital-to-analog converter (DAC) circuit, and the baseband circuit 204 may include a digital baseband interface for communicating with the RF circuit 206.

[0043] In some dual-mode embodiments, separate radio IC circuits may be provided to process the signals of each spectrum, but the scope of the embodiments is not limited to this point.

[0044] In some embodiments, the synthesizer circuit 206d may be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, but the scope of this embodiment is not limited to this point because other types of frequency synthesizers may be suitable. For example, the synthesizer circuit 206d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer with a phase-locked loop having a frequency divider.

[0045] The synthesizer circuit 206d may be configured to synthesize the output frequency used by the mixer circuit 206a of the RF circuit 206 based on the frequency input and the divider control input. In some embodiments, the synthesizer circuit 206d may be a fractional-N / N+1 synthesizer.

[0046] In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), but this is not a requirement. The divider control input may be provided by either the baseband circuit 204 or the application processor 202 according to the desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a look-up table based on the channel indicated by the application processor 202.

[0047] The synthesizer circuit 206d of the RF circuit 206 may include a divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide an input signal (e.g., based on execution) into either N or N + 1 to provide a fractional division ratio. In some exemplary embodiments, the DLL may include a set of cascaded tunable delay elements, a phase detector, a charge pump, and D-type flip-flops. In these embodiments, the delay elements can be configured to divide the VCO period into packets of equal phase of Nd, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0048] In some embodiments, the synthesizer circuit 206d may be configured to generate a carrier frequency as the output frequency. In other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency), and can be used in conjunction with an orthogonal generator and a divider circuit to generate multiple signals at carrier frequencies having multiple different phases relative to each other. In some embodiments, the output frequency may be the LO frequency (fLO). In some embodiments, the RF circuit 206 may include an IQ / polarity converter.

[0049] The FEM circuit 208 may include a receive signal path that operates on RF signals received from one or more antennas 210, amplifies the received signals, and provides an amplified version of the received signals to the RF circuit 206 for further processing. The FEM circuit 208 may also include a transmit signal path that includes circuitry configured to amplify signals provided by the RF circuit 206 for transmission by one or more of the one or more antennas 210. In various embodiments, amplification through the transmit signal path or the receive signal path can be performed in only the RF circuit 206, only in the FEM 208, or in both the RF circuit 206 and the FEM 208.

[0050] In some embodiments, the FEM circuit 208 may include a TX / RX switch for switching between transmit mode and receive mode operations. The FEM circuit may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit may include a Low Noise Amplifier (LNA) for amplifying received RF signals and providing the amplified received RF signals as an output (e.g., to the RF circuit 206). The transmit signal path of the FEM circuit 208 may include a power amplifier (PA) for amplifying an input RF signal (e.g., provided by the RF circuit 206) and one or more filters for generating an RF signal for subsequent transmission (e.g., by one or more of the one or more antennas 210).

[0051] In some embodiments, the PMC 212 can manage the power supplied to the baseband circuit 204. Specifically, the PMC 212 can control power selection, voltage scaling, battery charging, or DC-DC conversion. When the device 200 is powered by a battery, for example, when this device is included in a UE, the PMC 212 can often be included. The PMC 212 can increase the power conversion efficiency while imparting desirable mounting size and heat dissipation characteristics.

[0052] FIG. 2 shows PMC212 coupled only to baseband circuit 204. However, in other embodiments, PMC212 may be additionally or alternatively coupled to other components including, but not limited to, application circuit 202, RF circuit 206, or FEM 208, etc., to perform similar power management operations.

[0053] In some embodiments, PMC212 can control or otherwise be part of various power saving mechanisms of device 200. For example, if the device 200 is in the RRC_Connected state still connected to the RAN node as it is expected to receive traffic soon, after a certain inactive period, the device can enter a state known as discontinuous reception mode (DRX). During this state, device 200 can save power by powering down at short intervals.

[0054] If there is no data traffic activity for a long period, device 200 can transition to the RRC_Idle state where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. Device 200 enters a very low power state and performs paging where it wakes up periodically to listen for the network and then powers down again. Device 200 cannot receive data in this state. To receive data, it can transition back to the RRC_Connected state.

[0055] In an additional power saving mode, the device may be allowed to be unavailable from the network for a period longer than the paging interval (ranging from seconds to hours). During this time, the device may be completely unreachable to the network and may power down completely. If there is data transmitted during this time, there will be a significant delay, but the delay is considered acceptable.

[0056] Using the processors of the application circuit 202 and the baseband circuit 204, elements of one or more instances of the protocol stack can be executed. For example, the processors of the baseband circuit 204 can be used alone or in combination to execute the functionality of layer 3, layer 2, or layer 1, while the processor of the application circuit 204 can utilize the data received from these layers (e.g., packet data) to further execute the functionality of layer 4 (e.g., the transmission communication protocol (TCP) layer and the user datagram protocol (UDP) layer). As described above in this specification, layer 3 may include a radio resource control (RRC) layer, which will be described in more detail below. As described above in this specification, layer 2 may include a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, which will be described in more detail below. As described above in this specification, layer 1 may include the physical (PHY) layer of the UE / RAN node, which will be described in more detail below.

[0057] Figure 3 shows an exemplary interface of a baseband circuit according to some embodiments. As described above, the baseband circuit 204 of FIG. 2 may include processors 204A to 204E and a memory 204G utilized by these processors. Each of the processors 204A to 204E may respectively include memory interfaces 304A to 304E for transmitting and receiving data to and from the memory 204G.

[0058] The baseband circuit 204 may further include one or more interfaces for communicatively coupling to other circuits / devices, such as a memory interface 312 (e.g., an interface for transmitting and receiving data between the baseband circuit 204 and an external memory), an application circuit interface 314 (e.g., an interface for transmitting and receiving data between the application circuit 202 of FIG. 2), an RF circuit interface 316 (e.g., an interface for transmitting and receiving data between the RF circuit 206 of FIG. 2), a wireless hardware connectivity interface 318 (e.g., an interface for transmitting and receiving data between Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components), and a power management interface 320 (e.g., an interface for transmitting and receiving power or control signals between the PMC 212).

[0059] In various aspects, the embodiments described herein can facilitate beam management of a UE operating in DRX via one or more of the various techniques described herein.

[0060] As described above, FR2 operation may include beam management related to analog beamforming used for transmission and reception in FR2. Due to the increased data rates in FR2, operation in FR2 can increase power consumption and thermal issues. DRX operation can mitigate concerns related to power consumption and thermal issues, but there is a conflict between long DRX cycles and reliable beam management. For power savings, it may be beneficial to configure long DRX cycles. However, long DRX cycles may result in a lower frequency of beam management execution by the UE in at least existing systems, which can reduce beam quality and reliability.

[0061] To address these issues, various embodiments can use one or more of the techniques described herein that can facilitate extended beam management for the DRX operation of a UE. The various techniques described herein can be used in connection with long or short DRX cycles to provide advantages over existing approaches, although some of these techniques can provide even greater advantages over existing approaches when used in connection with long DRX cycles as compared to long DRX cycles of existing systems. Various embodiments can use any of the various techniques described herein, including various combinations. These techniques are grouped herein into three related sets of techniques associated with (1) transmission of a scheduling request (SR) and beam sweeping, (2) extended beam outage recovery, and (3) extended measurement and reporting of burst beams.

[0062] The first set of techniques described herein relates to extensions associated with the transmission of a scheduling request (SR) by a UE operating in DRX mode. The second set of techniques described herein relates to extensions associated with the detection and recovery of beam outages by a UE operating in DRX mode. The third set of techniques described herein relates to extensions associated with the measurement and reporting of beams by a UE operating in DRX mode. Various embodiments can use one or more of the techniques of the first set of techniques, the second set of techniques, and / or the third set of techniques.

[0063] Referring to FIG. 4, a block diagram of a system 400 that can be used for functions such as a UE (User Equipment), a next-generation Node B (gNodeB or gNB), or other BS (Base Station) / TRP (Transmit / Receive Point), or other components of a 3GPP (3rd Generation Partnership Project) network (e.g., 5GC (5th Generation Core Network)) component, or a UPF (User Plane Function), etc., which facilitates one or more extensions to beam management for the discontinuous reception (DRX) operation of the UE according to various embodiments described herein is shown. System 400 may include a processor 410, a communication circuit 420, and a memory 430. (For example, it may include one or more of 202 and / or 204A - 204F, etc.) The processor 410 may include a processing circuit and interfaces associated therewith (e.g., a communication interface (e.g., RF circuit interface 316) for communicating with the communication circuit 420, a memory interface (e.g., memory interface 312, etc.) for communicating with the memory 430). The communication circuit 420 may include, for example, circuits for wired and / or wireless connections (e.g., 206 and / or 208) (e.g., a transmitter circuit (associated with one or more transmit chains) and / or a receiver circuit (associated with one or more receive chains)), and the transmitter circuit and the receiver circuit can use common and / or separate circuit elements, or combinations thereof. The memory 430 may be any of various storage media (e.g., volatile and / or non-volatile by any of various technologies / configurations), (e.g., memory 204G, local memory of the processor (including CPU registers) described herein), and may include one or more memory devices that can store instructions and / or data associated with one or more processors 410 or transceiver circuits 420.

[0064] A particular type of embodiment of system 400 (e.g., an embodiment of a UE) may have subscripts (e.g., processor 410 UE , communication circuit 420 UE , and memory 430 UE of system 400 that includesUE ) can be shown via. Embodiments of the BS (e.g., system 400 gNB ) and embodiments of network components (e.g., UPF (User Plane Function), etc. (e.g., system 400 UPF ), in the processor 410 gNb (etc.), a communication circuit (e.g., 420 gNB etc.), and a memory (e.g., 430 gNB etc.) may be included in a single device or may be included in different devices such as part of a distributed architecture. In an embodiment, signaling or messaging between different embodiments of system 400 (e.g., 400 1 and 400 2 ) is generated by the processor 410 1 and transmitted by the communication circuit 420 through an appropriate interface or reference point (e.g., 3GPP radio interface, N3, N4, etc.), received by the communication circuit 420 1 and can be processed by the processor 410 2 . Depending on the type of interface, additional components (e.g., antennas, network ports, etc. associated with system 400 2 and 400 1 and 400 2 ) may be involved in this communication.

[0065] In various aspects described herein, signals and / or messages can be generated and output for transmission, and / or transmitted messages can be received and processed. Depending on the type of signal or message being generated (e.g., by processor 410, etc.), the output for transmission can include one or more of the following: generation of a set of associated bits indicating the content of the signal or message, encoding (which can include, for example, addition of a Cyclic Redundancy Check (CRC), and / or encoding via one or more of a turbo code, a Low-Density Parity-Check (LDPC) code, a TailBiting Convolution Code (TBCC), etc.), scrambling (e.g., based on a scrambling seed), modulation (e.g., via one of some forms such as Binary Phase Shift Keying (BPSK), Quadrature Phase Shift Keying (QPSK), or Quadrature Amplitude Modulation (QAM)), and / or resource mapping to one or more Resource Elements (REs) (e.g., a set of scheduled resources, a set of permitted time and frequency resources for uplink transmission, etc.). Here, each RE can include one subcarrier in the frequency domain and one symbol in the time domain (e.g., the symbol can be based on any of various access schemes such as Orthogonal Frequency Division Multiplexing (OFDM), Single Carrier Frequency Division Multiple Access (SC-FDMA), etc.). Depending on the type of received signal or message, the processing (e.g., by processor 410, etc.) can include one or more of the following: identification of the physical resources associated with the signal / message, detection of the signal / message, deinterleaving of resource element groups, demodulation, descrambling, and / or decoding.

[0066] In various aspects, one or more of information (e.g., system information, resources associated with signaling, etc.), features, parameters, etc. are via signaling from a gNB or other access point (e.g., associated with one or more layers of L1 signaling or higher layer signaling (e.g., MAC, RRC, etc.)) (e.g., by processor 410 gNB generated, transmitted by communication circuit 420 gNB and received by communication circuit 420 UE and processed by processor 410 UE configured in the UE. Depending on the type of information, features, parameters, etc. and the type of signaling used, the type of signaling used and / or the exact details of the operations performed in the UE and / or gNB during processing (e.g., signaling structure, handling of PDUs / SDUs, etc.) can vary. However, for convenience, such operations may be referred to herein as configuration of information / features / parameters / etc. in the UE, generation or processing of configuration signaling, or similar terms.

[0067] Various embodiments relate to an extension of the operation of one or more of the UE and / or a node of the 3GPP RAN (e.g., gNB) with respect to beam management of the UE during DRX operation. Briefly, a UE in DRX mode can operate according to a DRX cycle (e.g., a long DRX cycle or a short DRX cycle) that enables discontinuous monitoring of a physical downlink control channel (PDCCH) etc. to provide power consumption reduction (e.g., by processor 410 UE executed by etc., e.g., via the media access control (MAC) entity of the UE). The DRX operation is via radio resource control (RRC) (e.g., generated by processor 410 gNB transmitted by communication circuit 420 gNB received by communication circuit 420 UE and processed by processor 410UE It can be controlled and / or configured by configuring a number of parameters associated with DRX operation via RRC signaling processed thereby. These parameters may include parameters related to the following: DRX on-duration timer (e.g., via the drx-onDurationTimer parameter), DRX inactivity timer (e.g., via the drx-InactivityTimer), start of the DRX cycle (e.g., via the drx-LongCycleStartOffset), optional parameters related to short DRX cycles (e.g., drx-ShortCycle and drx-ShortCycleTimer). Various embodiments may include, but are not limited to, operations during and / or prior to the DRX on-duration, and operations related to actions taken with respect to the DRX on-duration timer and / or the DRX inactivity timer, and may be related to operations during (e.g., long or short) DRX cycles (e.g., by the UE and / or gNB). Techniques related to the transmission of scheduling requests (SRs) using beam sweeping

[0068] The first set of techniques includes techniques related to the transmission of scheduling requests (SRs) by a UE operating in DRX mode in relation to one or more cells (e.g., a Primary Cell (PCell), optionally only a Primary Secondary Cell (PSCell), or one or more additional Secondary Cells (SCs) from one or more gNBs (e.g., using system 400 gNB etc.) added thereto). UE etc.).

[0069] In various embodiments, a UE (e.g., a UE having UL data to transmit but not yet having a Physical Uplink Shared Channel (PUSCH) grant associated therewith) can transmit a SR via a selected beam during the DRX on-duration of the UE's (e.g., long or short) DRX cycle (e.g., by processor 410 UE generated by, and transmitted by communication circuitry 420 UE and received by communication circuitry 420 gNB and processed by processor 410 gNB . In various embodiments, the selected beam can be the best beam among one or more candidate beams determined as described herein based on one or more of a Channel State Information Reference Signal (CSI-RS) and / or Synchronization Signal Block (SSB) (e.g., generated by processor 410 gNB generated by, and transmitted by communication circuitry 420 gNB and received by communication circuitry 420 UE and processed by processor 410 UE ) transmitted by the gNB. Alternatively, in other embodiments, the selected beam can be a previously used beam that was pre-determined as the best beam (e.g., during or prior to a previous DRX on-duration) (e.g., as described herein).

[0070] Furthermore, in various embodiments, for each DRX-on duration of the UE (or each N DRX-on durations, where N is a positive integer; for example, in some embodiments, N is greater than 1 (N>1) such as for short DRX cycles, etc.), the SSB and / or CSI-RS can be configured so that the UE can check the quality of each of the multiple beams. For one or more of these beams (for each beam among the multiple beams that the UE detects the SSB and / or CSI-RS), the UE can, based on the signaling (e.g., SSB and / or CSI-RS) for that beam, measure relevant beam quality metrics (e.g., Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Signal-to-Interference-plus-Noise Ratio (SINR), etc.) (e.g., via processor 410 UE and / or communication circuit 420 UE . In various embodiments, based on the relevant beam quality metrics of one or more beams, the UE can select the best beam from among the one or more measured beams based on the associated beam quality metrics. Alternatively, in some embodiments, the UE can select a previously used beam (e.g., one previously selected as the best beam for one or more DRX cycles), and in some such embodiments, the UE can ignore the SSB and / or CSI-RS and further minimize power consumption.

[0071] In some embodiments, the SSB and / or CSI-RS can be during the DRX-on duration, but in other embodiments, they can be outside the DRX-on duration of the UE. In various embodiments where the SSB and / or CSI-RS are outside the DRX-on duration of the UE, they can be configured immediately before the start of the DRX-on duration of the UE (e.g., in the one or more slots immediately before), thereby minimizing power consumption at the UE.

[0072] In various embodiments, one or more sets of Physical Uplink Control Channel (PUCCH) resources may be configured for the UE for SR transmission, and each of the configured PUCCH resources may have a fixed mapping to one or more of the SSB and / or CSI-RS (and, equivalently, to one or more gNB beams to which one or more SSB and / or CSI-RS are transmitted). Thus, once the UE selects a beam for transmission (e.g., via processor 410 UE ), the UE can determine which PUCCH resources to use for SR transmission from this beam selection (e.g., by processor 410 UE ). In some embodiments, the mapping between the PUCCH and the SSB / CSI-RS may be one-to-one, with a separate PUCCH resource configured for each SSB / CSI-RS. In other embodiments, the mapping between the PUCCH and the SSB / CSI-RS may be many-to-one, with the same PUCCH resource configured for multiple SSB / CSI-RS (e.g., in the case of 4 SSB / CSI-RS, a single PUCCH resource may be configured for all 4 SSB / CSI-RS, or two PUCCH resources may be configured, each for a separate two of the SSB / CSI-RS). Further, in some embodiments (e.g., in embodiments using a one-to-one mapping, or in embodiments using a many-to-one mapping for one or more PUCCH resources), the previously selected beam may be associated with a configured dedicated PUCCH resource for the previously selected beam. This gives the UE the option to omit SSB / CSI-RS measurements, or SSB / CSI-RS measurements for other beams (e.g., still measuring it to determine whether the beam quality metric of the previously selected beam is sufficient), thereby further minimizing UE power consumption.

[0073] In various embodiments where a plurality of PUCCHs are configured for SR transmission in a UE, each of the plurality of PUCCHs may be associated with a separate beam of a plurality of beams. Thus, once the UE selects a beam (e.g., the best beam according to the techniques described herein) for SR transmission, the UE can determine the associated PUCCH resource (e.g., by the processor 410 UE ).

[0074] In various embodiments (e.g., those having two or more PUCCH resources), the mapping of PUCCH resources to SSB / CSI-RS can be pre-configured for the UE a period before the transmission of SSB / CSI-RS (e.g., before the DRX on-duration, etc.). In embodiments where the PUCCH resource is dedicated to a previously selected beam, these dedicated PUCCH resources can also be pre-configured (e.g., simultaneously). Further, in various embodiments, a threshold can be configured for the associated beam quality metric such that the transmission of SR by the UE can depend on a beam (e.g., the best beam, a previously selected beam, a first compliant beam, etc.) having an associated beam quality metric above a configured threshold selected by the UE, thereby reducing latency. Further, in some embodiments using a configured threshold for the associated beam quality metric, the UE can optionally omit subsequent measurements once it is found that at least one beam has an associated beam quality metric that meets the threshold, thereby reducing power consumption.

[0075] Regarding SR / PUCCH power control, (e.g., by the processor 410 UE and the communication circuit 420 UEThe UE path loss estimate thus determined is determined from a reference signal (RS) or synchronization signal (SS) used to detect the selected (e.g., best) beam, and a receive beam used to receive the selected beam. In various embodiments, the UE can be configured with a minimum number of samples or measurement durations to ensure that the UE obtains a reliable path loss estimate for power control. In scenarios where the number of samples or measurement durations for the selected (e.g., best) beam is sufficient, the UE can use the PUCCH resource of the selected beam to transmit the SR at the transmission power determined by the UE based on the estimated path loss. In scenarios where the number of samples or measurement durations for the selected (e.g., best) beam is insufficient, in some embodiments, the UE can use the selected beam for SR transmission and use the transmission power based on the path loss previously determined for the selected beam. Alternatively, in other embodiments, in such scenarios, the UE can use a different beam for which an accurate path loss estimate is possible for SR transmission (e.g., via the PUCCH resource associated with this different beam).

[0076] After transmitting the SR via an appropriate PUCCH resource, the UE can monitor and / or receive via a physical downlink control channel (PDCCH) or a physical downlink shared channel (PDSCH) (including, for example, downlink control information (DCI) indicating a UL grant in response to the SR) using the beam used for SR transmission, and / or transmit via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH).

[0077] Referring to Figure 5, an example timing diagram of an example scenario that may be used to facilitate SR transmissions for a UE operating in DRX mode, according to various embodiments described herein. While Figure 5 illustrates an example scenario performing one or more of the techniques detailed with respect to the first set of techniques, it should be understood that other techniques may be implemented and / or the same techniques may be performed in different scenarios. Figure 5 illustrates an example scenario of CSI-RS 502 transmitted in a TDM manner (e.g., with each separate set of CSI-RS transmitted at a different time) from a gNB to a UE. i 504 (where, for example, the CSI-RS (which in other scenarios may be SSB) is represented by a plurality of beam pairs 504 (each including a gNB beam used for CSI-RS transmit (Tx) and a UE beam used for CSI-RS receive (Rx)). i via the processor 410 gNB and the communication circuit 420 gNB and the communication circuit 420 UE and the processor 410 UE In the example of FIG. 5, the beam pair 504 is processed by, which may vary depending on the embodiment. i For each beam pair 504, SR is generated via the UE beam (e.g., during the UE's DRX on duration). i Separate resource for 506 i In the example of FIG. 5, the UE selects the third beam pair (504 3 ) and select Beam vs. 504 3 SR transmits a scheduling request via the UE beam (e.g., where SR is the processor 410 UE and the communication circuit 420 UE and the communication circuit 420 gNB and the processor 410 gNB The UE then determines whether an SR was transmitted (e.g., the beam pair 504 in the example of FIG. 5). 3Using the UE beam, monitor (e.g., monitor DCI such as UL grant indicating in response to SR) the PDCCH / PDSCH 508, and / or receive through them, and / or transmit through the PUCCH / PUSCH 510.

[0078] Referring to FIG. 6, there is shown a flow diagram of an exemplary method available for a UE that facilitates transmission of a scheduling request (SR) by the UE when operating in an intermittent reception (DRX) mode according to various embodiments described herein. In other aspects, a machine-readable medium can store instructions associated with method 600 that, when executed (e.g., using system 400 UE can cause the UE to execute the operations of method 600.

[0079] At 610, for each beam of one or more beams, based on the signaling transmitted through that beam (e.g., SSB and / or CSI-RS), relevant beam quality metrics (e.g., RSRP, RSRQ, SINR, etc.) can be measured. In various embodiments, the signaling can be transmitted during the UE's DRX on duration or before the UE's DRX on duration (e.g., immediately before it).

[0080] At 620, based on the relevant beam quality metrics, a selected (e.g., best) beam (e.g., a beam having the highest determined beam quality metric (e.g., RSRP, etc.), a pre-determined beam, or other beam having sufficient beam quality) can be determined.

[0081] Optionally, at 630, for SR transmission, a PUCCH resource associated with the selected (e.g., best) beam can be selected from a plurality of PUCCH resources (e.g., a PUCCH resource uniquely associated with the selected beam, or a PUCCH resource associated with the selected beam and one or more other beams), for example, a PUCCH resource mapped to the signaling received via the selected beam. In other embodiments, a many-to-one mapping that obviates this selection and provides a single PUCCH resource can be used.

[0082] At 640, the SR can be transmitted via the selected (e.g., best) beam during the UE's DRX on-duration. In some embodiments, the transmission of the SR via the selected (e.g., best) beam can depend on whether the associated beam quality metric of the selected (e.g., best) beam meets or exceeds a threshold. In various embodiments, the transmission power of the SR can be based on the path loss estimated for the selected beam if there is sufficient information to measure its path loss. Otherwise, in some embodiments, the previously estimated path loss for that beam can be used for determining the transmission power. In other embodiments, if the first selection for the selected beam does not have sufficient information to determine the path loss, at 620, a different beam for which sufficient information is available can be selected.

[0083] Optionally, at 650, one or more of PDCCH / PDSCH can be monitored / received and / or PUCCH / PUSCH can be transmitted via the selected beam used for SR transmission. This can include, for example, monitoring downlink control information (DCI) indicating a UL grant in response to the SR according to the UE's active time (e.g., based on a DRX on-duration timer and / or an inactive duration timer), and transmitting a PUSCH via the UL grant.

[0084] Additionally or alternatively, method 600 may include one or more other operations described herein with respect to various embodiments of the first set of techniques, the UE, and / or the system 400. UE may include one or more other operations described herein with respect to various embodiments of the first set of techniques.

[0085] Referring to FIG. 7, a flowchart of an exemplary method available at a gNB that facilitates transmission of a scheduling request (SR) at a UE operating in a discontinuous reception (DRX) mode, according to various embodiments described herein, is shown. In other aspects, a machine-readable medium can store instructions associated with method 700 that, when executed (e.g., using system 400), can cause the gNB to execute the operations of method 700. gNB can cause the gNB to execute the operations of method 700 when executed (e.g., using system 400).

[0086] At 710, one or more PUCCH resources that can be used to generate an SR can be configured for the UE. The PUCCH resources can be associated one-to-one or many-to-one with a plurality of SSBs and / or CSI-RSs transmitted to the UE for beam selection.

[0087] At 720, the SSB and / or CSI-RS can be transmitted in a TDM manner via a plurality of beams at or before (e.g., immediately before) the start of the UE's DRX on-duration.

[0088] At 730, a scheduling request can be received from a UE that requests a UL grant. The scheduling request can be transmitted via a selected beam of the UE for further communication (e.g., PDCCH / PDSCH / PUCCH / PUSCH, etc.). Further, in various embodiments, the PUCCH resource used for beam transmission can be associated with one or more of the SSBs and / or CSI-RSs transmitted at 720.

[0089] At 740, the selected beam of the UE can be determined based on the SR and / or the PUCCH resource.

[0090] Optionally, at 750, in response to the SR, a UL grant can be sent to the UE via the gNB beam corresponding to the selected beam of the UE to allocate PUSCH resources for UL data.

[0091] Additionally or alternatively, method 700 may include one or more other operations described herein with respect to various embodiments of the first set of techniques and the gNB and / or system 400 gNB may include one or more other operations described herein with respect to various embodiments of the first set of techniques. Techniques related to beam obstruction detection and recovery

[0092] The second set of techniques relates to techniques related to beam obstruction detection and recovery by a UE operating in DRX mode with respect to one or more cells (e.g., a PCell, optionally only a PSCell, or one or more other SCell(s) from one or more gNBs (e.g., using the system 400 gNB etc.). Except as otherwise specified, in various embodiments of the second set of techniques, each beam can be handled separately, such that the techniques described herein can be applied separately by the UE and / or gNB with respect to one or more beams.

[0093] In various embodiments, during a (long or short, for example) DRX cycle of a UE, signaling (e.g., SSB and / or CSI-RS) can be configured for the UE to detect beam failure (BF) on a given beam. The signaling configured for BF can include signaling within the DRX on-duration of the UE. Further, in various embodiments (e.g., for a DRX cycle with a threshold duration, e.g., 320 ms or more), the signaling configured for BF can also include signaling outside the DRX on-duration of the UE. In various embodiments, the UE can measure the signaling for BF during the DRX on-duration and, optionally, can either not measure any, measure a portion, or measure all of the signaling for BF outside the DRX on-duration (e.g., more measurements lead to more accurate decisions but can result in increased power consumption), which depends on whether the UE's capabilities meet the minimum performance level of the beam. Referring to FIG. 8, a plurality of CSI-RS and / or SSB 802 configured for BF detection by a DRX mode UE according to various embodiments described herein i is shown in an exemplary timing diagram. In the exemplary scenario shown in FIG. 8, four sets 802 1 ~802 4 of signaling for BF detection / recovery are configured during each DRX cycle of the UE, and one of them (802 1 ) is configured during the DRX on-duration of the UE. The number of times signaling for BF is configured during a DRX cycle can be more or less in various embodiments.

[0094] Further, during the DRX on-duration, UL resources can be used for reporting beam failure by the UE (e.g., generated by processor 410 UE , transmitted by communication circuit 420 UE , received by communication circuit 420 gNB , and processed by processor 410 gNBconfigured to be used to send a BF recovery request to be processed thereby. The nature of these resources may vary based on the type of cell associated with a given beam. For example, in the case of a PCell or a PSCell, for BF reporting by the UE, a contention-based Physical Random Access Channel (PRACH) or a contention-free PRACH may be configured. In some embodiments, a separate PRACH can be configured one-to-one for each beam, while in other embodiments, for example, a many-to-one mapping can be used that can be the same as the mapping used between the SSB / CSI-RS and the PUCCH described above with respect to a first set of techniques (e.g., related to the detection and selection of candidate beams). In the case of an SCell, the configured resources for BF reporting and / or recovery may include PUCCH / SR resources or may include UL PUSCH grants.

[0095] Furthermore, when a beam failure is detected by the UE and / or when a beam failure recovery is requested, the operation of one or more DRX timers (e.g., DRX on-duration timer, DRX inactivity timer) may be affected. For example, in various embodiments, when a beam failure is detected, if the DRX on-duration timer and / or the DRX inactivity timer are active, they may be stopped. In various embodiments, one or more DRX timers can be paused when BF is detected and a BF recovery request is about to be sent. Furthermore, in some embodiments, one or more DRX timers can also optionally be reset to zero (otherwise, they may remain paused at their current value). During BF recovery (e.g., after sending a BF recovery request, while waiting for a BF recovery response from the gNB, etc.), one or more DRX timers may remain stopped. When the UE receives a BF recovery request response from the network (e.g., generated by the processor 410 gNB and transmitted by the communication circuit 420 gNB and received by the communication circuit 420 UE and received by the processor 410 UEWhen the UE successfully receives a response that can be processed thereby, the UE can restart and / or reset one or more DRX timers (e.g., DRX on-duration timer, DRX inactivity timer) by (processor 410 UE thereby).

[0096] Referring to FIG. 9, an exemplary timing diagram showing the operation of the DRX on-duration timer for aspects of a second set of techniques according to various embodiments described herein is shown. At 902, signaling for BF detection can be sent by the gNB (before, in various embodiments, signaling 502 for candidate beam selection, detailed above with respect to the first set of techniques i ). If BF is detected, the UE can pause the active DRX on-duration timer (e.g., pause it at its current value), or alternatively, reset the DRX on-duration timer to 0 (as described at the bottom of FIG. 9). At 904, the UE can send a BF recovery request, and the UE can keep the DRX on-duration timer paused until the UE receives a response to the BF recovery request at 906, at which point the DRX on-duration timer can be restarted.

[0097] Alternatively, if BF recovery fails, at least one DRX timer (e.g., DRX on-duration timer, etc.) can expire, and the UE can enter the sleep state. In such a situation, the UE can wake up at the next DRX on-duration and attempt BF recovery again.

[0098] For a UE operating in carrier aggregation (CA) mode, if a given beam is a beam on a SCell, in some embodiments, BF can be processed in the same way as those on the PCell or PSCell. However, in other embodiments, one or more of the above techniques may vary for the beams of the SCell. For example, in some embodiments, the BF of the SCell may not affect one or more DRX timers. In such embodiments, if the UE transmits an SR for PUSCH grant for sending a BF recovery request but does not receive a response from the gNB before the DRX on-duration timer expires, the UE may enter the sleep state and can retry BF recovery during the next DRX on-duration. Additionally, in such embodiments, instead of receiving an acknowledgment (ACK) / negative acknowledgment (NACK) (e.g., DCI with the same UL hybrid automatic repeat request (HARQ) process ID scheduled and the new data indicator (NDI) switched) before one or more DRX timers expire, the UE can receive a UL PUSCH grant for BF recovery and can transmit a medium access control (MAC) control element (CE) (MAC-CE) (generated by, e.g., processor 410 UE and transmitted by communication circuit 420 UE and received by communication circuit 420 gNB and processed by processor 410 gNB ). In such scenarios, depending on the embodiment, one or more DRX timers (e.g., DRX on-duration timer, DRX inactivity timer) can be extended, or the UE can enter the sleep state and retry BF recovery during the next DRX on-duration.

[0099] Referring to FIG. 10, there is shown a flow diagram of an exemplary method available to a UE that facilitates detection and recovery of beam failure (BF) by the UE when operating in an intermittent reception (DRX) mode, according to various embodiments described herein. In other aspects, a machine-readable medium can store instructions associated with method 1000 that, when executed (e.g., using system 400 UE ), can cause the UE to execute the operations of method 1000.

[0100] At 1010, receive higher layer signaling that constitutes one or more occasions of signaling for BF of a beam in a cell for the DRX cycle of the UE, including at least one occasion during the DRX on-duration of the UE and optional occasions outside the DRX on-duration (e.g., SSB and / or CSI-RS).

[0101] At 1020, for at least one of the one or more occasions, measure the signaling for BF (e.g., by determining associated beam quality metrics).

[0102] At 1030, based on the measured signaling for BF, determine whether BF of the beam has occurred.

[0103] Optionally, at 1040, if BF has occurred, a BF recovery request can be sent. This can include sending the BF recovery request via a PRACH (e.g., contention-based or contention-free) or in response to an SR via PUCCH and via a UL grant.

[0104] Optionally, at 1050, as detailed with respect to the second set of techniques, at least one DRX timer (e.g., DRX on-duration timer and / or DRX inactivity timer) can have one or more of pause, reset, stop, resume, or expiration based on one or more of the detected BF, BF recovery request, or response to the received BF recovery request. For example, in response to the detected BF, the DRX on-duration timer and / or DRX inactivity timer can be paused and / or reset (or, e.g., in the case of a SCell, in some embodiments the operation can continue). In response to a BF recovery success response, the DRX on-duration timer and / or DRX inactivity timer can be resumed. Alternatively, in various embodiments, in response to a determination that BF recovery has failed, one or more DRX timers can be expired and the UE can enter a sleep state.

[0105] Additionally or alternatively, method 1000 can include one or more other operations described herein with respect to various embodiments of the second set of techniques for the UE and / or system 400 UE and the UE.

[0106] Referring to FIG. 11, a flowchart of an exemplary method available for a gNB that facilitates detection and recovery of beam failure (BF) when operating in an intermittent reception (DRX) mode, according to various embodiments described herein, is shown. In other aspects, a machine-readable medium can store instructions associated with method 1100 that, when executed (e.g., using system 400 gNB ), can cause the gNB to execute the operations of method 1100.

[0107] At 1110, configuration signaling can be transmitted that configures one or more SSB / CSI-RS for BF detection during the DRX cycle of the UE, and the one or more SSB / CSI-RS can include a first SSB / CSI-RS during the DRX on-duration of the UE and one or more other SSB / CSI-RS outside the DRX on-duration of the UE.

[0108] At 1120, the configured SSB / CSI-RS for BF can be transmitted during the configured occasion.

[0109] At 1130, resources for generating BF recovery requests can be configured for the UE. Depending on the cell, this can include configuring non-conflicting or contention-based PRACH (which may include, for example, different PRACH resources for different beams in some embodiments), or transmitting DCI that schedules UL grants in response to SR from the UE.

[0110] At 1140, BF recovery requests can be received from the UE via the resources configured for BF recovery requests.

[0111] At 1150, responses to BF recovery requests can be transmitted to the UE.

[0112] Additionally or alternatively, method 1100 can include one or more other operations described herein with respect to various embodiments of the second set of techniques for gNB and / or system 400 gNB and one or more other operations described herein with respect to various embodiments of the second set of techniques. Techniques related to measurement and reporting of burst beams

[0113] A third set of techniques includes techniques related to measurement and reporting of beams by a UE operating in DRX mode with respect to one or more cells (e.g., including a PCell, optionally only a PSCell, or adding one or more other SCell from one or more gNBs (such as using system 400 gNB etc.)). Except as otherwise specified, in various embodiments of the third set of techniques, each beam can be handled separately, such that the techniques described herein can be applied separately by the UE and / or gNB in relation to one or more beams.

[0114] Signaling (e.g., SSB and / or CSI-RS) can be configured to perform beam measurement or reporting during (e.g., at the start of) the UE's DRX on-duration or prior to the DRX on-duration. The beam measurement report can be a periodic report (e.g., via PUCCH at such start or prior to the DRX on-duration), a semi-persistent configured report (e.g., that can be activated simultaneously with the activation of a long DRX cycle), and / or an aperiodic report (e.g., in various embodiments, that can be triggered by the gNB or by the UE, as detailed below). In some embodiments, the burst beam management update by a third set of techniques can be part of the UE's DRX on-duration or at the start of the UE's DRX on-duration. In various embodiments, whether the UE performs burst beam management can be indicated to the UE via a power saving signal (e.g., a Wake Up Signal (WUS)).

[0115] In various embodiments, a wake-up request signal can be used, which can be a signal requesting DRX wake-up of the UE from the gNB, sent by the UE, (e.g., generated by the processor 410 UE and sent by the communication circuit 420 UE and received by the communication circuit 420 gNB and processed by the processor 410 gNB in the wake-up request signal). In various scenarios, the UE can detect a significant beam change that may not be recognized by the gNB, (e.g., based on a UE sensor (e.g., detecting rotation, movement, etc.) and / or SSB / CSI-RS from the gNB). In various embodiments, when the UE detects a significant beam change (e.g., based on one or more thresholds, etc.), the UE can send a wake-up request signal requesting DRX wake-up from the gNB. In some such embodiments, the wake-up request signal can also be processed as a request for aperiodic CSI-RS for beam management update.

[0116] In various embodiments, prior to the DRX-on duration, the gNB may configure one or more UL signals (e.g., PRACH, PUCCH, PUSCH grant, etc.) that can be used by the UE as wake-up request signals. In some embodiments, different resources can be configured for different UE beams. In various embodiments, the beam used for transmitting the UE wake-up request signal can be preconfigured as a sounding reference signal (SRS) resource indicator (RI), SRI, or transmission configuration indicator (TCI). In various embodiments, the beam used for transmitting the UE wake-up request signal can use a resource that can be mapped in a one-to-one or many-to-one manner to the SSB / CSI-RS for beam measurement and / or candidate beam selection (e.g., in its associated physical channel) as detailed herein.

[0117] Referring to FIG. 12, an exemplary timing diagram showing two different types of beam measurement reports according to various embodiments described herein is shown. In FIG. 12, prior to the first DRX-on duration, the SSB and / or CSI-RS 1202 can be transmitted by the gNB for a beam management report 1204 that is periodically configured by the UE and can be generated based on the measurement of the SSB / CSI-RS 1202 by the UE. Further, during the second DRX-on duration in FIG. 12, it is shown that the DCI 1206 is scheduling the CSI-RS 1208 of an aperiodic beam management report 1210 (via PUSCH) that can be generated based on the measurement of the CSI-RS 1208 by the UE.

[0118] Referring to FIG. 13, an exemplary timing diagram showing a beam measurement report triggered by UE signaling according to various aspects described herein is shown. In FIG. 13, the SSB / CSI-RS for beam measurement 1302 can be measured by the UE, and based on the measured SSB / CSI-RS and / or UE sensors, the UE can transmit a UE wake-up request signal 1304. In response to the UE wake-up request signal 1304, the UE wakes up (e.g., starts the DRX on-duration), and the gNB can schedule an aperiodic CSI-RS 1308 (via DCI 1306) that the UE can use for burst beam measurement, and this aperiodic UE beam measurement report can be transmitted via PUSCH 1310.

[0119] Referring to FIG. 14, a flow diagram of an exemplary method available to a UE that facilitates beam measurement and reporting by the UE when operating in an intermittent reception (DRX) mode according to various embodiments described herein is shown. In other aspects, a machine-readable medium can store instructions associated with method 1400 that, when executed (e.g., using system 400 UE ), can cause the UE to execute the operations of method 1400.

[0120] At 1410, optionally, a wake-up request signal can be transmitted to trigger an aperiodic beam measurement report. The wake-up request signal can be transmitted, for example, in response to the UE's determination that a significant change has occurred or may have occurred in the beam, based on the measured SSB / CSI-RS and / or UE sensors.

[0121] At 1420, optionally, the UE can receive a wake-up signal or other power-saving signal indicating that the UE should perform a burst beam management update.

[0122] At 1430, the UE can be configured with signaling for beam measurement (e.g., SSB and / or CSI-RS) to perform beam measurement and reporting (e.g., within the DRX-on duration, prior to the DRX-on duration) along with resources for the UE to transmit a beam measurement report (e.g., during the DRX-on duration). Depending on the nature of the report (e.g., periodic, aperiodic, semi-persistent, etc.), the channels, resources, and configuration methods may vary.

[0123] At 1440, the associated beam quality metrics of a beam can be measured for the beam based on the configured signaling for beam measurement received via that beam.

[0124] At 1450, a beam measurement report indicating the associated beam quality metrics can be transmitted via the configured resources and associated physical channels.

[0125] Additionally or alternatively, method 1400 may include one or more other operations described herein with respect to various embodiments of the UE and / or system 400 UE and the third set of techniques.

[0126] Referring to FIG. 15, a flowchart of an exemplary method available for a gNB to facilitate beam measurement and reporting by a UE when operating in an intermittent reception (DRX) mode, according to various embodiments described herein, is shown. In other aspects, a machine-readable medium can store instructions associated with method 1500 that, when executed, can cause a gNB (e.g., using system 400 gNB to perform the operations of method 1500).

[0127] At 1510, optionally, a wake-up request signal can be received to trigger an aperiodic beam measurement report. The wake-up request signal can be transmitted, for example, in response to a UE determination that a significant change has occurred or may occur in a beam, based on, for example, a measured SSB / CSI-RS and / or a UE sensor.

[0128] At 1420, optionally, a wake-up signal or other power-saving signal indicating that the UE should perform burst beam management updates can be sent to the UE.

[0129] At 1430, signaling for beam measurement (e.g., SSB and / or CSI-RS) for performing beam measurement and reporting (e.g., within the DRX-on duration, before the DRX-on duration) can be configured for the UE, along with resources for the UE to send a beam measurement report (e.g., during the DRX-on duration). Depending on the nature of the report (e.g., periodic, aperiodic, semi-persistent, etc.), the channel, resources, and configuration method can vary.

[0130] At 1440, configured signaling for beam measurement can be sent via the beam.

[0131] At 1450, a beam measurement report indicating relevant beam quality metrics can be received via the configured resources and associated physical channels.

[0132] Additionally or alternatively, method 1500 can include one or more other operations described herein with respect to various embodiments of the third set of techniques for the gNB and / or system 400 gNB and can include at least one machine-readable medium containing executable instructions that, when executed by a machine (e.g., a processor with memory such as a processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), etc.), cause the machine to perform the operations of a method or an apparatus or a system for simultaneous communication using the multiple communication techniques according to the embodiments and examples described herein. Additional Examples

[0133] Examples herein can include a method, means for performing an operation or block of the method, at least one machine-readable medium containing executable instructions that, when executed by a machine (e.g., a processor with memory such as a processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), etc.), cause the machine to perform the operations of a method or an apparatus or a system for simultaneous communication using the multiple communication techniques according to the embodiments and examples described herein, etc.

[0134] Example 1 is an apparatus configured to be used in a UE (User Equipment), and for each beam of one or more beams, based on the signaling associated with that beam, which includes one or more of the synchronization signal block (SSB) associated with that beam or the channel state information reference signal (CSI-RS) associated with that beam, measure the associated beam quality metrics for that beam, determine the best beam among the one or more beams based on the associated beam quality metrics determined for each beam of the one or more beams, and generate a scheduling request (SR) for transmission via the best beam during the UE's discontinuous reception (DRX) on-duration. The apparatus comprises one or more processors.

[0135] Example 2 includes the subject matter of any variation of Example 1, wherein for each beam of one or more beams, the signaling associated with that beam is mapped to a set of associated time-frequency resources within the DRX on-duration.

[0136] Example 3 includes the subject matter of any variation of Example 1, wherein for each beam of one or more beams, the signaling associated with that beam is mapped to a set of associated time-frequency resources before the DRX on-duration.

[0137] Example 4 includes the subject matter of any variation of Examples 1 to 3, wherein the one or more processors are further configured to map the SR to a set of resources of a physical uplink control channel (PUCCH) that is uniquely associated with the signaling associated with the best beam.

[0138] Example 5 includes the subject matter of any variation of Example 4, where for each beam of one or more beams, one or more processors are configured to generate an SR based on a determination that the associated beam quality metric of the best beam is above a threshold.

[0139] Example 6 includes the subject matter of any variation of Examples 1 to 3, where one or more beams include a first beam different from the best beam, and one or more processors are further configured to map the SR to a set of resources of a physical uplink control channel (PUCCH) associated with both the signaling associated with the best beam and the signaling associated with the first beam.

[0140] Example 7 includes the subject matter of any variation of Examples 1 to 6, where the associated beam quality metric measured for the best beam is based on at least a threshold number of measurements for estimating the path loss associated with the best beam, and one or more processors are further configured to estimate the path loss associated with the best beam based at least in part on the associated beam quality metric and select the transmission power of the SR based on the estimated path loss associated with the best beam.

[0141] Example 8 includes the subject matter of any variation of Examples 1 to 6, where the associated beam quality metric measured for a first beam of one or more beams is the highest associated beam quality metric, and the highest associated beam quality metric is based on less than a threshold number of measurements for estimating the path loss associated with the best beam, and one or more processors are further configured to select the first beam or one of the previous best beams associated with a previous path loss estimate as the best beam and select the transmission power of the SR based on the previous path loss estimate.

[0142] Example 9 includes the subject matter of any variation of Examples 1 to 8, where one or more processors are further configured to monitor one or more of downlink control information (DCI) for uplink (UL) grant, physical downlink shared channel (PDSCH), physical uplink control channel (PUCCH), or physical uplink shared channel (PUSCH) via the best beam to which the generated SR is transmitted.

[0143] Example 10 is a device configured to be used in a user equipment (UE), which at each of one or more times during the UE's discontinuous reception (DRX) cycle, includes signaling associated with that time and a first beam of the UE, where the signaling includes one or more of a synchronization signal block (SSB) associated with that time and the first beam or a channel state information reference signal (CSI-RS) associated with that time and the first beam, and one or more of the times include a first time within the UE's DRX on-duration. The device processes higher layer signaling that configures the cell with the signaling associated with that time and the first beam, measures the signaling associated with at least one of the one or more times and the first beam of the UE, and is configured to determine whether a beam failure of the first beam has occurred based on the measured signaling associated with at least one of the one or more times and the first beam of the UE, and includes one or more processors.

[0144] Example 11 includes the subject matter of any variation of Example 10, where one or more times during the UE's discontinuous reception (DRX) cycle include a second time outside the UE's DRX on-duration.

[0145] In Embodiment 12, when it is determined that a beam obstruction of a first beam has occurred, one or more processors are further configured to generate a beam obstruction recovery request and map the beam obstruction recovery request to a set of resources. When the cell is a primary cell (PCell) or a primary secondary cell (PSCell), the set of resources is associated with one of a contention-based physical random access channel (PRACH) or a non-contention PRACH. When the cell is a secondary cell, the set of resources is associated with a physical uplink shared channel (PUSCH) grant of the UE, including the subject matter of any variation of Embodiment 10 or 11.

[0146] Embodiment 13 includes the subject matter of any variation of Embodiment 12, where one or more processors are further configured to stop a DRX on-duration timer in response to a determination that a beam obstruction of a first beam has occurred.

[0147] Embodiment 14 includes the subject matter of any variation of Embodiment 13, where one or more processors are further configured to reset a DRX on-duration timer in response to a determination that a beam obstruction of a first beam has occurred.

[0148] Embodiment 15 includes the subject matter of any variation of Embodiment 13 or 14, where one or more processors are further configured to resume a DRX on-duration timer in response to processing a beam obstruction recovery success response.

[0149] Embodiment 16 includes the subject matter of any variation of Embodiment 13 or 14, where one or more processors are further configured to determine that a beam obstruction recovery request has failed, expire a DRX on-duration timer, and enter a sleep state in response to the expiration of the DRX on-duration timer.

[0150] Example 17 includes the subject matter of any of the variations of Examples 12 to 14, further configured such that one or more processors stop a DRX inactivity timer in response to a determination that a beam obstruction of a first beam has occurred.

[0151] Example 18 includes the subject matter of any of the variations of Example 17, further configured such that one or more processors reset a DRX inactivity timer in response to processing a beam obstruction recovery success response.

[0152] Example 19 includes the subject matter of any of the variations of Example 17 or 18, further configured such that one or more processors resume a DRX inactivity timer in response to processing a beam obstruction recovery success response.

[0153] Example 20 is a device configured to be used in a UE (User Equipment), comprising one or more processors configured to generate a beam measurement report that measures a beam quality metric of a beam based on beam-associated signaling that includes one or more of a synchronization signal block (SSB) associated with the beam or a channel state information reference signal (CSI-RS) associated with the beam, mapped to a set of associated time-frequency resources within or before the DRX on-duration of the UE, and is configured as one of a periodic report, a semi-persistent report, or an aperiodic report indicating the beam quality metric.

[0154] Example 21 includes the subject matter of any of the variations of Example 20, further configured such that one or more processors generate a beam measurement report in response to a power saving signal indicating that the UE wakes up.

[0155] Example 22 includes the subject matter of any variation of Example 20 or 21, where the beam measurement report is aperiodic and one or more processors are further configured to detect that the beam has changed by at least a threshold amount and generate a request for DRX wake-up.

[0156] Example 23 is an apparatus configured to be used in a next-generation NodeB (gNB), comprising one or more processors, which for each beam of one or more beams, generate signaling associated with that beam, the signaling associated with that beam including one or more of a synchronization signal block (SSB) associated with that beam or a channel state information reference signal (CSI-RS) associated with that beam, and is further configured to process a scheduling request (SR) for transmission via a selected beam of the one or more beams during a discontinuous reception (DRX) on-duration of a user equipment (UE).

[0157] Example 24 includes the subject matter of any variation of Example 23, where for each beam of one or more beams, the signaling associated with that beam is mapped to a set of associated time-frequency resources within the DRX on-duration.

[0158] Example 25 includes the subject matter of any variation of Example 23, where for each beam of one or more beams, the signaling associated with that beam is mapped to a set of associated time-frequency resources before the DRX on-duration.

[0159] Example 26 includes the subject matter of any variation of Examples 23 to 25, where the SR is mapped to a set of resources of a physical uplink control channel (PUCCH) that is uniquely associated with the signaling associated with the selected beam.

[0160] Example 27 includes the subject matter of any of the variations of Examples 23 to 25, where one or more beams include a first beam different from the selected beam, and the SR is mapped to a set of resources of a physical uplink control channel (PUCCH) associated with both the signaling associated with the selected beam and the signaling associated with the first beam.

[0161] Example 28 includes the subject matter of any of the variations of Examples 23 to 27, where one or more processors are further configured to generate downlink control information (DCI) for an uplink (UL) grant in response to the SR via the selected beam over which the generated SR was transmitted.

[0162] Example 29 is a device configured to be used in a next-generation NodeB (gNB), which generates upper-layer signaling that constitutes a cell, including signaling associated with that time and the gNB's first beam at each of one or more times during the discontinuous reception (DRX) cycle of a user equipment (UE), where the signaling includes one or more of a synchronization signal block (SSB) associated with that time and the first beam or a channel state information reference signal (CSI-RS) associated with that time and the first beam, and one or more of the times include a first time within the UE's DRX on-duration, and is configured to process a beam failure recovery request associated with the first beam, and includes one or more processors.

[0163] Example 30 includes the subject matter of any of the variations of Example 29, where one or more times during the UE's DRX cycle include a second time outside the UE's DRX on-duration.

[0164] Embodiment 31 includes the subject matter of any variation of Embodiment 29 or 30, where a beam failure recovery request is mapped to a set of resources, and when the cell is a primary cell (PCell) or a primary secondary cell (PSCell), the set of resources is associated with one of a contention-based physical random access channel (PRACH) or a PRACH without contention, and when the cell is a secondary cell, the set of resources is associated with a physical uplink shared channel (PUSCH) grant of the user equipment (UE).

[0165] Embodiment 32 is an apparatus configured to be used in a next-generation node B (gNB), generating signaling associated with a beam, including one or more of a synchronization signal block (SSB) associated with the beam or a channel state information reference signal (CSI-RS) associated with the beam, and mapped to a set of associated time-frequency resources within or prior to the discontinuous reception (DRX) on-duration of a user equipment (UE), and processing a beam measurement report configured as one of a periodic report, a semi-persistent report, or an aperiodic report that indicates a beam quality metric associated with the beam, and comprising one or more processors.

[0166] Embodiment 33 includes the subject matter of any variation of Embodiment 32, where one or more processors are further configured to generate a power-saving signal indicating to wake up the UE.

[0167] Embodiment 34 includes the subject matter of any variation of Embodiment 32, where the beam measurement report is aperiodic and one or more processors are further configured to process a request for DRX wake-up.

[0168] Embodiment 35 includes an apparatus comprising means for performing any of the operations described in Embodiments 1 to 34.

[0169] Example 36 includes a machine-readable medium storing instructions that are executed by a processor to perform any of the operations described in Examples 1 to 34.

[0170] Example 37 includes an apparatus comprising a memory interface and a processing circuit configured to perform any of the operations described in Examples 1 to 34.

[0171] Including the content described in the abstract, the above description of the exemplary embodiments of the disclosed subject matter is not intended to be exhaustive or to limit the disclosed embodiments to the exact forms disclosed. Specific embodiments and examples are described herein for purposes of illustration, but as will be recognized by those of ordinary skill in the art, various equivalent modifications are possible within the scope of these specific embodiments and examples.

[0172] In this regard, although the disclosed subject matter has been described in connection with various embodiments and the corresponding drawings, other similar embodiments can be used, where applicable, to perform the same, similar, alternative, or substitute functions as the disclosed subject matter, or modifications and additions can be made without departing from the described embodiments. Therefore, the disclosed subject matter should not be limited to any single embodiment described herein, but rather should be construed in accordance with the breadth and scope of the following appended claims.

[0173] In particular, with respect to the various functions performed by the above-described components or structures (assemblies, devices, circuits, systems, etc.), the terms used to describe such components (including descriptions related to "means") are, unless otherwise specified, intended to correspond to any component or structure that performs the specific function of the described component, even if not structurally equivalent to the disclosed structure that performs the functions of the exemplary implementations of the invention illustrated herein (e.g., functionally equivalent). Further, although a particular feature may be disclosed with respect to only one of several implementations, such a feature may be combined with one or more other features of one or more other implementations so as to be desirable and advantageous for any given or particular application.

Claims

1. A baseband circuit comprising: A memory for storing instructions; one or more processors coupled to the memory that, when executing the instructions, process higher layer signaling to configure a cell with signaling associated with one or more times during a discontinuous reception (DRX) cycle of the UE, the signaling associated with that time and a first beam of the UE, the signaling including one or more of a synchronization signal block (SSB) associated with that time and the first beam or a channel state information reference signal (CSI-RS) associated with that time and the first beam, the one or more times depending on whether a capability of the UE meets a minimum performance level of the first beam, the signaling including a first time within a DRX on duration of the UE, a second time outside a DRX on duration of the UE, or both the first time and the second time; For at least one time of the one or more times, measure the at least one time and the signaling associated with the first beam; and one or more processors configured to determine whether a beam failure of the first beam has occurred based on the at least one time and the measured signaling associated with the first beam.

2. When it is determined that the beam failure of the first beam has occurred, the one or more processors: Generate a beam failure recovery request; further configured to map the beam failure recovery request to a set of resources; When the cell is a Primary Cell (PCell) or a Primary Secondary Cell (PSCell), the set of resources is associated with one of a contention-based Physical Random Access Channel (PRACH) or a contention-free PRACH; The baseband circuit of claim 1 , wherein the set of resources is associated with a Physical Uplink Shared Channel (PUSCH) grant of the UE when the cell is a secondary cell.

3. 3. The baseband circuit of claim 2, wherein the one or more processors are further configured to stop a DRX on duration timer in response to the determination that the beam failure of the first beam has occurred.

4. 4. The baseband circuit of claim 3, wherein the one or more processors are further configured to reset and restart the DRX on duration timer in response to the determination that the beam failure of the first beam has occurred.

5. the one or more processors: determining that the beam failure recovery request has failed; Allowing the DRX on duration timer to expire; The baseband circuit of claim 3 , further configured to enter a sleep state in response to expiration of the DRX on duration timer.

6. 3. The baseband circuit of claim 2, wherein the one or more processors are further configured to stop a DRX inactivity timer in response to the determination that the beam failure of the first beam has occurred.

7. 7. The baseband circuit of claim 6, wherein the one or more processors are further configured to reset or restart the DRX inactivity timer in response to processing a beam failure recovery success response.

8. A UE (User Equipment), an RF circuit configured to convert between RF signals and baseband signals; one or more processors coupled to the RF circuitry and configured to process the baseband signals, the UE comprising: receiving a signaling configuration for beam measurements of one or more beams; measuring a beam quality metric of a beam among the one or more beams based on the signaling associated with the beam, the signaling associated with the beam being mapped to an associated set of time-frequency resources within or prior to a discontinuous reception (DRX) on duration of the UE; transmitting beam measurement reports configured as one of periodic reports, semi-persistent reports, or aperiodic reports indicating the beam quality metrics; A UE comprising one or more processors configured to cause a scheduling request (SR) to be transmitted during a discontinuous reception (DRX) on duration of the UE based on the beam measurement report.

9. The UE of claim 8 , wherein the one or more processors are configured to aperiodically transmit the beam measurement report in response to a power save signal indicating to the UE to wake up.

10. The beam measurement reports are aperiodic, and the one or more processors: Detecting that the beam has changed by at least a threshold amount based on the beam measurement report; 10. The UE of claim 8 or 9, further configured to generate a request for DRX wake-up.

11. The beam measurement report is configured as a semi-persistent report and is triggered with a long DRX cycle trigger.

10. The UE according to claim 8 or 9.

12. The beam measurement report is configured at the start of a DRX on duration of the UE.

10. The UE according to claim 8 or 9.

13. the beam measurement report is configured before each of the DRX on durations.

10. The UE according to claim 8 or 9.

14. the beam measurement report is configured as a periodic report.

10. The UE according to claim 8 or 9.

Images