UE, apparatus, and medium for radio link monitoring based on multiple DCI transmissions

Abstract

The present invention provides an apparatus, system, and method for a user equipment device (UE) to perform a method for radio link monitoring based on multiple DCI transmissions. The UE may receive a configuration for multiple downlink control information (DCI) mode operation from a network node, wherein a physical downlink shared channel (PDSCH) is scheduled by multiple DCIs from multiple control resource sets (CORESETs). The number of CORESETs may exceed the number of CORESETs that the UE can monitor. The UE may determine a set of CORESETs to monitor based at least in part on one or more CORESET attributes. The set of CORESETs to monitor may be less than the number of CORESETs. In addition, the UE may monitor the set of CORESETs for at least one of a radio link failure or a beam failure.

Description

Technical Field

[0001] The present application relates to wireless devices, and more particularly, to apparatuses, systems, and methods for wireless devices to perform radio link monitoring on multi-DCI based transmissions.

[0002] Related technical description

[0003] The use of wireless communication systems is growing rapidly. In recent years, wireless devices such as smartphones and tablets have become increasingly sophisticated. In addition to supporting phone calls, many mobile devices now also provide access to the Internet, email, text messaging, and navigation using the Global Positioning System (GPS), and are capable of operating sophisticated applications that utilize these capabilities.

[0004] Long Term Evolution (LTE) has become the technology of choice for most wireless network operators worldwide, enabling them to provide mobile broadband data and high-speed internet access to their subscriber base. LTE defines multiple downlink (DL) physical channels, categorized as transport or control channels, to carry information blocks received from the medium access control (MAC) and higher layers. LTE also defines the number of uplink (UL) physical layer channels.

[0005] For example, LTE defines the Physical Downlink Shared Channel (PDSCH) as a DL transport channel. The PDSCH is the primary data-bearing channel allocated to users on a dynamic and opportunistic basis. The PDSCH carries data in transport blocks (TBs) corresponding to MAC protocol data units (PDUs), which are delivered from the MAC layer to the physical (PHY) layer once per transmission time interval (TTI). The PDSCH is also used to transmit broadcast information such as system information blocks (SIBs) and paging messages.

[0006] For example, LTE defines the Physical Downlink Control Channel (PDCCH) as a DL control channel that carries the UE's resource allocation contained in the Downlink Control Information (DCI) message. Multiple PDCCHs can be transmitted in the same subframe using Control Channel Elements (CCEs), each of which is nine groups of four resource elements called Resource Element Groups (REGs). The PDCCH uses Quadrature Phase Shift Keying (QPSK) modulation, with four QPSK symbols mapped to each REG. In addition, depending on the channel conditions, 1, 2, 4, or 8 CCEs can be used to ensure sufficient robustness.

[0007] In addition, LTE defines the Physical Uplink Shared Channel (PUSCH) as an UL channel shared by all devices (user equipment, UE) in a radio cell to transmit user data to the network. The scheduling of all UEs is under the control of the LTE base station (enhanced Node B or eNB). The eNB uses an uplink scheduling grant (DCI format 0) to inform the UE of the resource block (RB) allocation and the modulation and coding scheme to be used. The PUSCH typically supports QPSK and orthogonal amplitude modulation (QAM). In addition to user data, the PUSCH also carries any control information required to decode the information, such as the transport format indicator and multiple-input multiple-output (MIMO) parameters. The control data is multiplexed with the information data before being expanded by the digital Fourier transform (DFT).

[0008] The next telecommunications standard proposed to surpass the current International Mobile Telecommunications Advanced (IMT-Advanced) standard is called the 5th Generation Mobile Network or 5th Generation Wireless System, or simply 5G (also known as 5G-NR for 5G New Radio, and also simply NR). Compared to the current LTE standard, 5G-NR proposes higher capacity for a higher density of mobile broadband users, while supporting ultra-reliable and massive machine-to-device communications, as well as lower latency and lower battery consumption. In addition, the 5G-NR standard can allow for less restricted UE scheduling than the current LTE standard. Therefore, efforts are underway to take advantage of the higher throughput possible at higher frequencies in the ongoing development of 5G-NR. Summary of the Invention

[0009] Embodiments relate to apparatus, systems, and methods for a UE to perform radio link monitoring on multiple DCI-based transmissions.

[0010] In some embodiments, a wireless device, such as a user equipment device (UE), may be configured to receive a configuration from a network node for multiple downlink control information (DCI) mode operation, in which a physical downlink shared channel (PDSCH) is scheduled by multiple DCIs from multiple control resource sets (CORESETs). The number of CORESETs may exceed the number of CORESETs that the UE can monitor. In other words, the number of configured CORESETs may exceed the number of CORESETs that the UE can monitor simultaneously. The wireless device may be configured to determine a set of CORESETs to monitor based at least in part on one or more CORESET attributes. The set of CORESETs to monitor may be less than the number of CORESETs. Additionally, the wireless device may be configured to monitor a set of CORESETs for at least one of a radio link failure or a beam failure. In some embodiments, the one or more CORESET attributes may include a higher layer index and a monitoring periodicity for a search space associated with the CORESET. In some embodiments, the wireless device may be configured to select a CORESET based on a monitoring periodicity from lowest to highest, or vice versa. In some embodiments, when CORESETs have the same (or equivalent) monitoring periodicity, the wireless device may be configured to select from CORESETs with the same (or equivalent) monitoring periodicity based on the higher layer index of the CORESET. In some embodiments, the wireless device may select from the highest higher layer index to the lowest higher layer index, or vice versa. In some embodiments, the wireless device may be configured to select from the CORESETs with the same (or equivalent) higher layer index based on the monitoring periodicity. In some embodiments, the wireless device may select from the highest monitoring periodicity to the lowest monitoring periodicity, or vice versa. In some embodiments, when CORESETs have the same (or equivalent) higher layer index, the wireless device may be configured to select from the CORESETs with the same (or equivalent) higher layer index based on the monitoring periodicity. In some embodiments, the wireless device may select from the highest monitoring periodicity to the lowest monitoring periodicity, or vice versa.

[0011] The techniques described herein may be implemented in and / or used with a number of different types of devices, including, but not limited to, any of cellular telephones, tablet computers, wearable computing devices, portable media players, and various other computing devices.

[0012] This summary is intended to provide a brief overview of some of the subject matter described in this document. Therefore, it should be understood that the above-described features are merely examples and should not be construed as narrowing the scope or spirit of the subject matter described herein in any way. Other features, aspects, and advantages of the subject matter described herein will become apparent from the following detailed description, accompanying drawings, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] A better understanding of the present subject matter may be obtained when the following detailed description of various embodiments is considered in conjunction with the following drawings, in which:

[0014] Figure 1A An exemplary wireless communication system is shown in accordance with some embodiments.

[0015] Figure 1B Examples of base stations (BSs) and access points communicating with user equipment (UE) devices are shown in accordance with some embodiments.

[0016] Figure 2 An exemplary simplified block diagram of a WLAN access point (AP) is shown in accordance with some embodiments.

[0017] Figure 3 An exemplary block diagram of a UE according to some embodiments is shown.

[0018] Figure 4 An exemplary block diagram of a BS according to some embodiments is shown.

[0019] Figure 5 An example block diagram of cellular communication circuitry is shown in accordance with some embodiments.

[0020] Figure 6A An example of the connection between the EPC network, LTE base stations (eNBs), and 5G NR base stations (gNBs) is shown.

[0021] Figure 6B Examples of protocol stacks for eNB and gNB are shown.

[0022] Figure 7A An example of a 5G network architecture according to some embodiments is shown, which combines 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access to the 5G CN.

[0023] Figure 7B An example of a 5G network architecture according to some embodiments is shown, which combines dual 3GPP (e.g., LTE and 5G NR) access to the 5G CN as well as non-3GPP access.

[0024] Figure 8An example of a baseband processor architecture for a UE according to some embodiments is shown.

[0025] Figures 9 to 11D Various examples of selecting a CORESET according to some embodiments are shown.

[0026] Figure 12 A block diagram illustrating an example of a method for performing radio link monitoring for multiple DCI based transmissions according to some embodiments is shown.

[0027] While the features described herein are susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and described in detail herein. It should be understood, however, that the drawings and detailed description thereof are not intended to limit this disclosure to the particular forms disclosed, but on the contrary, are intended to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the subject matter as defined by the appended claims. DETAILED DESCRIPTION

[0028] the term

[0029] The following is a glossary of terms used in this disclosure:

[0030] Memory medium - any of various types of non-transitory memory devices or storage devices. The term "memory medium" is intended to include installation media, such as CD-ROMs, floppy disks, or tape devices; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory such as flash memory, magnetic media, for example, hard drives or optical storage devices; registers or other similar types of memory elements, etc. The memory medium may also include other types of non-transitory memory or a combination thereof. In addition, the memory medium may be located in the first computer system that executes the program, or may be located in a different second computer system that is connected to the first computer system via a network such as the Internet. In the latter case, the second computer system may provide program instructions to the first computer for execution. The term "memory medium" may include two or more memory media that may reside in different locations in different computer systems connected, for example, via a network. The memory medium may store program instructions (e.g., expressed as a computer program) that can be executed by one or more processors.

[0031] Carrier Medium—storage media as described above, and physical transmission media such as a bus, network, and / or other physical transmission media that transport signals such as electrical, electromagnetic, or digital signals.

[0032] Programmable hardware elements—include various hardware devices that include multiple programmable function blocks connected via programmable interconnects. Examples include FPGAs (field programmable gate arrays), PLDs (programmable logic devices), FPOAs (field programmable object arrays), and CPLDs (complex PLDs). Programmable function blocks can range from fine-grained (combinational logic units or lookup tables) to coarse-grained (arithmetic logic units or processor cores). Programmable hardware elements may also be referred to as "configurable logic units."

[0033] Computer System—Any of various types of computing or processing systems, including a personal computer system (PC), a mainframe computer system, a workstation, a network appliance, an Internet appliance, a personal digital assistant (PDA), a television system, a grid computing system, or other devices or combinations of devices. In general, the term "computer system" can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

[0034] User Equipment (UE) (or "UE device") - any of various types of computer system devices that are mobile or portable and that perform wireless communication. Examples of UE devices include mobile phones or smartphones (e.g., iPhones, TM , based on Android TM phones), portable gaming devices (e.g., Nintendo DS TM PlayStation Portable TM 、Gameboy Advance TM , iPhone TM ), laptop computers, wearable devices (e.g., smart watches, smart glasses), personal digital assistants, portable Internet devices, music players, data storage devices or other handheld devices, etc. In general, the term "UE" or "UE device" can be broadly defined to cover any electronic device, computing device and / or telecommunication device (or combination of devices) that is easy for a user to carry and capable of wireless communication.

[0035] Base Station—The term “base station” has the full breadth of its ordinary meaning and includes at least a wireless communication station that is installed at a fixed location and used to communicate as part of a wireless telephone system or radio system.

[0036] Processing Element—refers to any element or combination of elements capable of performing a function in a device such as user equipment or a cellular network device. A processing element may include, for example, a processor and associated memory, portions or circuits of individual processor cores, entire processor cores, processor arrays, circuits such as ASICs (Application Specific Integrated Circuits), programmable hardware elements such as field programmable gate arrays (FPGAs), and any combination thereof.

[0037] Channel - the medium used to transmit information from a sender (transmitter) to a receiver. It should be noted that since the characteristics of the term "channel" may vary according to different wireless protocols, the term "channel" as used in the present invention may be considered to be used in a manner that is consistent with the standard of the type of device to which the term is used. In some standards, the channel width may be variable (e.g., depending on device capabilities, frequency band conditions, etc.). For example, LTE may support scalable channel bandwidths of 1.4 MHz to 20 MHz. In contrast, a WLAN channel may be 22 MHz wide, while a Bluetooth channel may be 1 MHz wide. Other protocols and standards may include different definitions of channels. In addition, some standards may define and use multiple types of channels, such as different channels for uplink or downlink and / or different channels for different purposes such as data, control information, etc.

[0038] Frequency band—The term “frequency band” has the full breadth of its ordinary meaning and includes at least a segment of the spectrum (eg, radio frequency spectrum) in which channels are used or set aside for the same purpose.

[0039] Automatic—refers to an action or operation performed by a computer system (e.g., software executed by the computer system) or a device (e.g., a circuit, a programmable hardware element, an ASIC, etc.) without requiring user input to directly specify or execute the action or operation. Thus, the term "automatic" is in contrast to manual execution or specification of an action by a user, where the user provides input to directly execute the action. An automatic process may be initiated by input provided by a user, but the subsequent actions performed "automatically" are not specified by the user, i.e., they are not performed "manually," where the user specifies each action to be performed. For example, a user filling out an electronic form by selecting each field and providing input specifying information (e.g., by typing information, selecting checkboxes, radio selections, etc.) is manually filling out the form, even though the computer system must update the form in response to the user's actions. The form may be automatically filled out by a computer system, where the computer system (e.g., software executed on the computer system) analyzes the fields of the form and fills it out without requiring any user input to specify the answers to the fields. As indicated above, a user may invoke automatic filling of a form without participating in the actual filling out of the form (e.g., the user does not manually specify the answers to the fields, but rather they are automatically completed). This specification provides various examples of operations that are automatically performed in response to actions that a user has taken.

[0040] About—refers to a value that is close to being correct or exact. For example, about can refer to a value that is within 1% to 10% of the exact (or desired) value. However, it should be noted that the actual threshold value (or tolerance) may depend on the application. For example, in some embodiments, "about" may mean within 0.1% of some specified or desired value, while in various other embodiments, the threshold value may be, for example, 2%, 3%, 5%, etc., depending on the desires or requirements of a particular application.

[0041] Concurrency - refers to parallel execution or implementation, where tasks, processes, or programs are executed in an at least partially overlapping manner. For example, concurrency can be achieved using "strong" or strict parallelism, where tasks are executed (at least partially) in parallel on respective computing elements, or using "weak parallelism," where tasks are executed in an interleaved manner (e.g., by time multiplexing of execution threads).

[0042] Various components may be described as being "configured to" perform one or more tasks. In such contexts, "configured to" is a broad statement that generally means "having a structure" to perform one or more tasks during operation. Thus, a component can be configured to perform a task even when the component is not currently performing the task (e.g., a set of electrical conductors can be configured to electrically connect a module to another module even when the two modules are not connected). In some contexts, "configured to" can be a broad statement that generally means "having a structure" to carry out one or more tasks during operation. Thus, a component can be configured to perform a task even when the component is not currently turned on. Typically, the circuitry that forms the structure corresponding to "configured to" may include hardware circuitry.

[0043] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to." Representing a component as being configured to perform one or more tasks expressly intends that the component not be interpreted under 35 U.S.C. §112(f).

[0044] Figure 1A and Figure 1B -Communication system

[0045] Figure 1A A simplified exemplary wireless communication system according to some embodiments is shown. Note that the system of Figure 1 is only one example of a possible system, and features of the present disclosure may be implemented in any of a variety of systems as desired.

[0046] As shown, the exemplary wireless communication system includes a base station 102A that communicates with one or more user devices 106A, 106B, 106N, etc. via a transmission medium. Each user device may be referred to herein as a "user equipment" (UE). Therefore, user device 106 is referred to as a UE or UE device.

[0047] Base station (BS) 102A may be a base transceiver station (BTS) or a cell site ("cellular base station") and may include hardware that enables wireless communications with UEs 106A through 106N.

[0048] The communication area (or coverage area) of a base station may be referred to as a "cell". The base station 102A and the UE 106 may be configured to communicate over a transmission medium using any of a variety of radio access technologies (RATs), also known as wireless communication technologies or telecommunication standards, such as GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-Advanced (LTE-A), 5G New Radio (5G NR), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), and the like. Note that if the base station 102A is implemented in the context of LTE, it may alternatively be referred to as an "eNodeB" or "eNB". Note that if the base station 102A is implemented in the context of 5G NR, it may alternatively be referred to as a "gNodeB" or "gNB".

[0049] As shown, base station 102A may also be configured to communicate with network 100 (e.g., a cellular service provider's core network, a telecommunications network such as the Public Switched Telephone Network (PSTN), and / or the Internet, among other possibilities). Thus, base station 102A may facilitate communications between user devices and / or between user devices and network 100. In particular, cellular base station 102A may provide UE 106 with various communication capabilities, such as voice, SMS, and / or data services.

[0050] Base station 102A and other similar base stations (such as base stations 102B...102N) operating according to the same or different cellular communication standards can therefore be provided as a network of cells that can provide continuous or nearly continuous overlapping service to UEs 106A-106N and similar devices over a geographic area via one or more cellular communication standards.

[0051] Thus, while base station 102A may serve as a "serving cell" for UEs 106A-106N as shown in FIG1 , each UE 106 may also be able to receive signals from (and potentially be within communication range of) one or more other cells (which may be provided by base stations 102B-102N and / or any other base stations), which may be referred to as "neighboring cells." Such cells may also be able to facilitate communications between user devices and / or between user devices and network 100. Such cells may include "macro" cells, "micro" cells, "pico" cells, and / or cells of any other variety of granularity in terms of service area size. For example, base stations 102A-102B shown in FIG1 may be macro cells, while base station 102N may be a micro cell. Other configurations are also possible.

[0052] In some embodiments, base station 102A may be a next-generation base station, such as a 5G New Radio (5G NR) base station or "gNB." In some embodiments, a gNB may be connected to a legacy Evolved Packet Core (EPC) network and / or to a New Radio Communications Core (NRC) network. Furthermore, a gNB cell may include one or more Transition and Reception Points (TRPs). Furthermore, a UE capable of operating in accordance with 5G NR may connect to one or more TRPs within one or more gNBs.

[0053] It should be noted that the UE 106 is capable of communicating using multiple wireless communication standards. For example, in addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc.), the UE 106 can be configured to communicate using wireless networking (e.g., Wi-Fi) and / or peer-to-peer wireless communication protocols (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.). If desired, the UE 106 can also or alternatively be configured to communicate using one or more global navigation satellite systems (GNSS, such as GPS or GLONASS), one or more mobile television broadcast standards (e.g., ATSC-M / H or DVB-H), and / or any other wireless communication protocols. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0054] Figure 1B A user equipment 106 (e.g., one of devices 106A through 106N) is shown in accordance with some embodiments in communication with a base station 102 and an access point 112. The UE 106 may be a device having cellular and non-cellular communication capabilities (e.g., Bluetooth, Wi-Fi, etc.), such as a mobile phone, handheld device, computer or tablet, or virtually any type of wireless device.

[0055] The UE 106 may include a processor configured to execute program instructions stored in a memory. The UE 106 may perform any of the method embodiments described herein by executing such stored instructions. Alternatively or in addition, the UE 106 may include a programmable hardware element, such as a field programmable gate array (FPGA) configured to perform any of the method embodiments described herein or any portion of any of the method embodiments described herein.

[0056] UE 106 may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, UE 106 may be configured to communicate using, for example, CDMA2000 (1xRTT / 1xEV-DO / HRPD / eHRPD), LTE / LTE-Advanced, or 5G NR using a single shared radio and / or GSM, LTE, LTE-Advanced, or 5G NR using a single shared radio. The shared radio may be coupled to a single antenna or to multiple antennas (e.g., for MIMO) for performing wireless communications. Typically, the radio may include any combination of a baseband processor, analog radio frequency (RF) signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.), or digital processing circuitry (e.g., for digital modulation and other digital processing). Similarly, the radio may implement one or more receive and transmit chains using the aforementioned hardware. For example, UE 106 may share one or more portions of a receive and / or transmit chain between multiple wireless communication technologies such as those discussed above.

[0057] In some embodiments, the UE 106 may include a separate transmit chain and / or receive chain (e.g., including separate antennas and other radio components) for each wireless communication protocol with which it is configured to communicate. As another possibility, the UE 106 may include one or more radio components shared between multiple wireless communication protocols, and one or more radio components used exclusively by a single wireless communication protocol. For example, the UE 106 may include a shared radio component for communicating using either LTE or 5GNR (or LTE or 1xRTT, or LTE or GSM), and a separate radio component for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible.

[0058] Figure 2 —Access Point Block Diagram

[0059] Figure 2 An exemplary block diagram of an access point (AP) 112 is shown. Note that Figure 2 The block diagram of the AP 112 is only one example of a possible system. As shown, the AP 112 may include a processor 204 that may execute program instructions for the AP 112. The processor 204 may also be coupled (directly or indirectly) to a memory management unit (MMU) 240 or other circuit or device that may be configured to receive addresses from the processor 204 and translate those addresses into locations in memory (e.g., memory 260 and read-only memory (ROM) 250).

[0060] AP 112 may include at least one network port 270. The network port 270 may be configured to couple to a wired network and provide access to the Internet to multiple devices, such as UE 106. For example, network port 270 (or an additional network port) may be configured to couple to a local network, such as a home network or an enterprise network. For example, port 270 may be an Ethernet port. The local network may provide connectivity to additional networks, such as the Internet.

[0061] The AP 112 may include at least one antenna 234, which may be configured to operate as a wireless transceiver and may be further configured to communicate with the UE 106 via wireless communication circuitry 230. The antenna 234 communicates with the wireless communication circuitry 230 via a communication chain 232. The communication chain 232 may include one or more receive chains, one or more transmit chains, or both. The wireless communication circuitry 230 may be configured to communicate via Wi-Fi or WLAN (e.g., 802.11). For example, when the AP is co-located with a base station in a small cell scenario, or in other scenarios where it may be desirable for the AP 112 to communicate via various different wireless communication technologies, the wireless communication circuitry 230 may also or alternatively be configured to communicate via various other wireless communication technologies, including, but not limited to, 5G NR, Long Term Evolution (LTE), LTE-Advanced (LTE-A), Global System for Mobile (GSM), Wideband Code Division Multiple Access (WCDMA), CDMA2000, and the like.

[0062] In some embodiments, as further described below, AP 112 may be configured to perform the method for radio link monitoring for multiple DCI based transmissions as further described herein.

[0063] Figure 3 —UE block diagram

[0064] Figure 3 1 shows an exemplary simplified block diagram of a communication device 106 according to some embodiments. Note that Figure 3The block diagram of the communication device is only an example of a possible communication device. Depending on the embodiment, the communication device 106 can be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (such as a laptop, notebook or portable computing device), a tablet computer and / or a combination of devices, in addition to other devices. As shown, the communication device 106 may include a group of components 300 configured to perform core functions. For example, the group of components can be implemented as a system on a chip (SOC), which may include parts for various purposes. Alternatively, the group of components 300 can be implemented as a separate component or group of components for various purposes. This group of components 300 can be coupled (e.g., communicatively; directly or indirectly) to various other circuits of the communication device 106.

[0065] For example, the communication device 106 may include various types of memory (e.g., including NAND flash memory 310), input / output interfaces such as a connector I / F 320 (e.g., for connecting to a computer system; a docking station; a charging station; input devices such as a microphone, a camera, a keyboard; output devices such as a speaker; etc.), a display 360 that may be integrated with the communication device 106 or external to the communication device 106, and cellular communication circuitry 330 such as for 5G NR, LTE, GSM, etc., and short-range to medium-range wireless communication circuitry 329 (e.g., Bluetooth TM and WLAN circuitry). In some embodiments, the communication device 106 may include wired communication circuitry (not shown), such as, for example, a network interface card for Ethernet.

[0066] Cellular communication circuitry 330 may be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as antennas 335 and 336, as shown. Short-range to medium-range wireless communication circuitry 329 may also be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as antennas 337 and 338, as shown. Alternatively, short-range to medium-range wireless communication circuitry 329 may be (e.g., communicatively; directly or indirectly) coupled to antennas 335 and 336, in addition to or in lieu of being (e.g., communicatively; directly or indirectly) coupled to antennas 337 and 338. Short-range to medium-range wireless communication circuitry 329 and / or cellular communication circuitry 330 may include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams, such as in a multiple-input, multiple-output (MIMO) configuration.

[0067] In some embodiments, as further described below, the cellular communication circuitry 330 can include dedicated receive chains (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radios) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G-NR). Furthermore, in some embodiments, the cellular communication circuitry 330 can include a single transmit chain that can switch between radios dedicated to specific RATs. For example, a first radio can be dedicated to a first RAT, such as LTE, and can communicate with a dedicated receive chain and a transmit chain shared with an additional radio, such as a second radio that can be dedicated to a second RAT (e.g., 5G NR) and can communicate with both the dedicated receive chain and the shared transmit chain.

[0068] The communication device 106 may also include and / or be configured for use with one or more user interface elements. User interface elements may include various elements such as a display 360 (which may be a touch screen display), a keyboard (which may be a separate keyboard or may be implemented as part of the touch screen display), a mouse, a microphone and / or speakers, one or more cameras, one or more buttons, and / or any of a variety of other elements capable of providing information to a user and / or receiving or interpreting user input.

[0069] The communication device 106 may also include one or more smart cards 345 having SIM (Subscriber Identity Module) functionality, such as one or more UICC cards (one or more Universal Integrated Circuit Cards) 345 .

[0070] As shown, the SOC 300 may include a processor 302 that may execute program instructions for the communication device 106 and a display circuit 304 that may perform graphics processing and provide display signals to a display 360. The one or more processors 302 may also be coupled to a memory management unit (MMU) 340 (the MMU may be configured to receive addresses from the one or more processors 302 and translate those addresses into locations in memory (e.g., memory 306, read-only memory (ROM) 350, NAND flash memory 310)) and / or to other circuits or devices (such as the display circuit 304, short-range to medium-range wireless communication circuitry 329, cellular communication circuitry 330, connector I / F 320, and / or display 360). The MMU 340 may be configured to perform memory protection and page table translation or setup. In some embodiments, the MMU 340 may be included as part of the processor 302.

[0071] As described above, the communication device 106 may be configured to communicate using wireless and / or wired communication circuitry.The communication device 106 may be configured to perform a method for radio link monitoring for multiple DCI based transmissions as further described herein.

[0072] As described herein, the communication device 106 may include hardware and software components for implementing the above-described features of the communication device 106 to send a scheduling profile for power saving to the network. For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), the processor 302 of the communication device 106 may be configured to implement some or all of the features described herein. Alternatively (or in addition), the processor 302 may be configured as a programmable hardware element, such as an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit). Alternatively (or in addition), in combination with one or more of the other components 300, 304, 306, 310, 320, 329, 330, 340, 345, 350, 360, the processor 302 of the communication device 106 may be configured to implement some or all of the features described herein.

[0073] Furthermore, as described herein, processor 302 may include one or more processing elements. Thus, processor 302 may include one or more integrated circuits (ICs) configured to perform the functions of processor 302. Furthermore, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform one or more functions of processor 302.

[0074] Further, as described herein, the cellular communication circuitry 330 and the short-range to medium-range wireless communication circuitry 329 may each include one or more processing elements. In other words, one or more processing elements may be included in the cellular communication circuitry 330, and similarly, one or more processing elements may be included in the short-range to medium-range wireless communication circuitry 329. Thus, the cellular communication circuitry 330 may include one or more integrated circuits (ICs) configured to perform the functions of the cellular communication circuitry 330. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the cellular communication circuitry 330. Similarly, the short-range to medium-range wireless communication circuitry 329 may include one or more ICs configured to perform the functions of the short-range to medium-range wireless communication circuitry 329. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the short-range to medium-range wireless communication circuitry 329.

[0075] Figure 4 —Block diagram of a base station

[0076] Figure 41 shows an exemplary block diagram of a base station 102 according to some embodiments. Note that Figure 4 The base station 102 is only one example of a possible base station. As shown, the base station 102 may include a processor 404 that may execute program instructions for the base station 102. The processor 404 may also be coupled to a memory management unit (MMU) 440 or other circuit or device that may be configured to receive addresses from the processor 404 and translate those addresses into locations in memory (e.g., memory 460 and read-only memory (ROM) 450).

[0077] The base station 102 may include at least one network port 470. The network port 470 may be configured to couple to a telephone network and provide access to the network as described above in FIG. Figure 2 Multiple devices of the telephone network described in, such as UE device 106.

[0078] The network port 470 (or an additional network port) may also or alternatively be configured to couple to a cellular network, such as a core network of a cellular service provider. The core network may provide mobility-related services and / or other services to multiple devices, such as the UE device 106. In some cases, the network port 470 may couple to a telephone network via the core network, and / or the core network may provide a telephone network (e.g., in other UE devices served by the cellular service provider).

[0079] In some embodiments, base station 102 may be a next-generation base station, such as a 5G New Radio (5G NR) base station, or "gNB." In such embodiments, base station 102 may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, base station 102 may be considered a 5G NR cell and may include one or more transition and reception points (TRPs). Furthermore, UEs capable of operating in accordance with 5G NR may connect to one or more TRPs within one or more gNBs.

[0080] Base station 102 may include at least one antenna 434 and possibly multiple antennas. The at least one antenna 434 may be configured to function as a wireless transceiver and may be further configured to communicate with UE device 106 via radio 430. Antenna 434 communicates with radio 430 via communication chain 432. Communication chain 432 may be a receive chain, a transmit chain, or both. Radio 430 may be configured to communicate via various wireless communication standards, including but not limited to 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, and the like.

[0081] The base station 102 may be configured to perform wireless communications using multiple wireless communication standards. In some cases, the base station 102 may include multiple radios that enable the base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, the base station 102 may include an LTE radio component for performing communications according to LTE and a 5G NR radio component for performing communications according to 5G NR. In this case, the base station 102 may be capable of operating as both an LTE base station and a 5G NR base station. As another possibility, the base station 102 may include a multimode radio component capable of performing communications according to any one of multiple wireless communication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

[0082] As further described later herein, the base station 102 may include hardware and software components for implementing or supporting the implementation of the features described herein. The processor 404 of the base station 102 may be configured to implement or support a portion or all of the implementation of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor 404 may be configured as a programmable hardware element such as an FPGA (field programmable gate array), or as an ASIC (application-specific integrated circuit) or a combination thereof. Alternatively (or in addition), in combination with one or more of the other components 430, 432, 434, 440, 450, 460, and 470, the processor 404 of the base station 102 may be configured to implement or support a portion or all of the specific implementation of the features described herein.

[0083] Furthermore, as described herein, processor 404 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in processor 404. Thus, processor 404 may include one or more integrated circuits (ICs) configured to perform the functions of processor 404. Furthermore, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 404.

[0084] Additionally, as described herein, radio 430 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in radio 430. Thus, radio 430 may include one or more integrated circuits (ICs) configured to perform the functions of radio 430. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of radio 430.

[0085] Figure 5:Block diagram of cellular communication circuit

[0086] Figure 5 An exemplary simplified block diagram of a cellular communication circuit according to some embodiments is shown. Note that Figure 5 The block diagram of the cellular communication circuitry is only one example of one possible cellular communication circuitry. Depending on the embodiment, the cellular communication circuitry 330 may be included in a communication device such as the communication device 106 described above. As described above, the communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet computer, and / or a combination of devices, among other devices.

[0087] Cellular communication circuitry 330 may be (eg, communicatively; directly or indirectly) coupled to one or more antennas, such as ( Figure 3 In some embodiments, the cellular communication circuit 330 may include dedicated receive chains (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radio components) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G-NR). For example, Figure 5 As shown, cellular communication circuitry 330 may include a modem 510 and a modem 520. Modem 510 may be configured for communication according to a first RAT, such as, for example, LTE or LTE-A, and modem 520 may be configured for communication according to a second RAT, such as, for example, 5G NR.

[0088] As shown, the modem 510 may include one or more processors 512 and a memory 516 in communication with the processor 512. The modem 510 may communicate with a radio frequency (RF) front end 530. The RF front end 530 may include circuitry for transmitting and receiving radio signals. For example, the RF front end 530 may include receive circuitry (RX) 532 and transmit circuitry (TX) 534. In some embodiments, the receive circuitry 532 may communicate with a downlink (DL) front end 550, which may include circuitry for receiving radio signals via antenna 335a.

[0089] Similarly, the modem 520 may include one or more processors 522 and a memory 526 in communication with the processor 522. The modem 520 may communicate with an RF front end 540. The RF front end 540 may include circuitry for transmitting and receiving radio signals. For example, the RF front end 540 may include receive circuitry 542 and transmit circuitry 544. In some embodiments, the receive circuitry 542 may communicate with a DL front end 560, which may include circuitry for receiving radio signals via the antenna 335b.

[0090] In some embodiments, the switch 570 can couple the transmit circuitry 534 to the uplink (UL) front end 572. Furthermore, the switch 570 can couple the transmit circuitry 544 to the UL front end 572. The UL front end 572 can include circuitry for transmitting radio signals via the antenna 336. Thus, when the cellular communication circuitry 330 receives an instruction to transmit according to a first RAT (e.g., via a transmit chain including the transmit circuitry 534 and the UL front end 572), the switch 570 can be switched to a first state that allows the modem 510 to transmit signals according to the first RAT (e.g., via a transmit chain including the transmit circuitry 534 and the UL front end 572). Similarly, when the cellular communication circuitry 330 receives an instruction to transmit according to a second RAT (e.g., via a transmit chain including the transmit circuitry 544 and the UL front end 572), the switch 570 can be switched to a second state that allows the modem 520 to transmit signals according to the second RAT (e.g., via a transmit chain including the transmit circuitry 544 and the UL front end 572).

[0091] In some embodiments, the cellular communication circuitry 330 may be configured to perform a method for radio link monitoring for multi-DCI based transmissions as further described herein.

[0092] As described herein, the modem 510 may include hardware and software components for implementing the above-described features or for time-division multiplexing UL data for NSA NR operations and various other technologies described herein. For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), the processor 512 may be configured to implement part or all of the features described herein. Alternatively (or in addition), the processor 512 may be configured as a programmable hardware element such as an FPGA (field programmable gate array) or as an ASIC (application-specific integrated circuit). Alternatively (or in addition), in combination with one or more of the other components 530, 532, 534, 550, 570, 572, 335, and 336, the processor 512 may be configured to implement part or all of the feature parts described herein.

[0093] Furthermore, as described herein, processor 512 may include one or more processing elements. Thus, processor 512 may include one or more integrated circuits (ICs) configured to perform the functions of processor 512. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 512.

[0094] As described herein, the modem 520 may include hardware and software components intended to implement the above-described features for transmitting a power-saving scheduling profile to a network, as well as various other techniques described herein. The processor 522 may be configured to implement a portion or all of the features described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), the processor 522 may be configured as a programmable hardware element such as an FPGA (field programmable gate array), or as an ASIC (application-specific integrated circuit). Alternatively (or additionally), in combination with one or more of the other components 540, 542, 544, 550, 570, 572, 335, and 336, the processor 522 may be configured to implement a portion or all of the features described herein.

[0095] Furthermore, as described herein, processor 522 may include one or more processing elements. Thus, processor 522 may include one or more integrated circuits (ICs) configured to perform the functions of processor 522. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 522.

[0096] 5G NR architecture with LTE

[0097] In some implementations, fifth generation (5G) wireless communications will initially be deployed concurrently with current wireless communication standards (e.g., LTE). For example, dual connectivity between LTE and 5G New Radio (5G NR or NR) has been specified as part of the initial deployment of NR. Figures 6A to 6B As shown, the Evolved Packet Core (EPC) network 600 can continue to communicate with the current LTE base station (e.g., eNB 602). In addition, the eNB 602 can communicate with the 5G NR base station (e.g., gNB 604), and data can be transferred between the core network 600 and the gNB 604. Thus, the EPC network 600 can be used (or reused), and the gNB 604 can serve as additional capacity for user equipment, for example, to provide increased downlink throughput for the UE. In other words, LTE can be used for control plane signaling, and NR can be used for user plane signaling. Thus, LTE can be used to establish a connection to the network, and NR can be used for data services.

[0098] Figure 6B The proposed protocol stacks for eNB 602 and gNB 604 are shown. As shown, eNB 602 may include a medium access control (MAC) layer 632 that interfaces with radio link control (RLC) layers 622a-622b. RLC layer 622a may also interface with packet data convergence protocol (PDCP) layer 612a, and RLC layer 622b may interface with PDCP layer 612b. Similar to dual connectivity specified in LTE-Advanced Release 12, PDCP layer 612a may interface with EPC network 600 via a master cell group (MCG) bearer, while PDCP layer 612b may interface with EPC network 600 via a separate bearer.

[0099] In addition, as shown, the gNB 604 may include a MAC layer 634 that interfaces with RLC layers 624a-624b. The RLC layer 624a may interface with the PDCP layer 612b of the eNB 602 via an X2 interface for information exchange and / or coordination (e.g., scheduling UEs) between the eNB 602 and gNB 604. Furthermore, the RLC layer 624b may interface with the PDCP layer 614. Similar to the dual connectivity specified in LTE-Advanced Release 12, the PDCP layer 614 may interface with the EPC network 600 via a secondary cell group (SCG) bearer. Thus, the eNB 602 may be considered a master node (MeNB), while the gNB 604 may be considered a secondary node (SgNB). In some cases, a UE may be required to maintain connectivity with both the MeNB and the SgNB. In such a scenario, the MeNB may be used to maintain a radio resource control (RRC) connection with the EPC, while the SgNB may be used for capacity (e.g., additional downlink and / or uplink throughput).

[0100] 5G Core Network Architecture—Interoperability with Wi-Fi

[0101] In some embodiments, the 5G core network (CN) can be accessed via (or through) a cellular connection / interface (e.g., via a 3GPP communication architecture / protocol) and a non-cellular connection / interface (e.g., a non-3GPP access architecture / protocol such as a Wi-Fi connection). Figure 7AAn example of a 5G network architecture according to some embodiments is shown, combining 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access to a 5G CN. As shown, a user equipment device (e.g., UE 106) can access the 5G CN via both a radio access network (RAN, e.g., a gNB or base station 604) and an access point, such as AP 112. AP 112 may include a connection to the Internet 700 and a connection to a non-3GPP interworking function (N3IWF) 702 network entity. N3IWF may include a connection to the core access and mobility management function (AMF) 704 of the 5G CN. AMF 704 may include an instance of a 5G mobility management (5G MM) function associated with UE 106. In addition, the RAN (e.g., gNB 604) may also have a connection to AMF 704. Thus, the 5G CN may support unified authentication across both connections and allow UE 106 to be registered for access via both the gNB 604 and AP 112 simultaneously. As shown, the AMF 704 may include one or more functional entities associated with the 5G CN (e.g., a network slice selection function (NSSF) 720, a short message service function (SMSF) 722, an application function (AF) 724, a unified data management (UDM) 726, a policy control function (PCF) 728, and / or an authentication server function (AUSF) 730). Note that these functional entities may also be supported by the 5G CN's session management function (SMF) 706a and SMF 706b. The AMF 706 may be connected to (or in communication with) the SMF 706a. Furthermore, the gNB 604 may be in communication with (or in communication with) a user plane function (UPF) 708a, which may also be in communication with the SMF 706a. Similarly, the N3IWF 702 may be in communication with the UPF 708b, which may also be in communication with the SMF 706b. Both UPFs may communicate with data networks (eg, DNs 710 a and 710 b ) and / or the Internet 700 and the IMS core network 710 .

[0102] Figure 7BAn example of a 5G network architecture according to some embodiments is shown, which combines dual 3GPP (e.g., LTE and 5G NR) access to the 5G CN as well as non-3GPP access. As shown, a user equipment device (e.g., UE 106) can access the 5G CN through both the radio access network (RAN, e.g., gNB or base station 604 or eNB or base station 602) and an access point such as AP 112. AP 112 can include a connection to the Internet 700 and a connection to the N3IWF 702 network entity. The N3IWF can include a connection to the 5G CN's AMF 704. The AMF 704 can include an instance of the 5G MM function associated with the UE 106. In addition, the RAN (e.g., gNB 604) can also have a connection to the AMF 704. Thus, the 5G CN can support unified authentication across both connections and allow the UE 106 to be registered for access via both the gNB 604 and the AP 112 simultaneously. In addition, the 5GCN can support dual registration of UEs on both legacy networks (e.g., LTE via base station 602) and 5G networks (e.g., via base station 604). As shown, base station 602 can have connections to a mobility management entity (MME) 742 and a serving gateway (SGW) 744. The MME 742 can have connections to both the SGW 744 and the AMF 704. In addition, the SGW 744 can have connections to both the SMF 706a and the UPF 708a. As shown, the AMF 704 can include one or more functional entities associated with the 5GCN (e.g., NSSF 720, SMSF 722, AF 724, UDM 726, PCF 728, and / or AUSF 730). Note that the UDM 726 can also include Home Subscriber Server (HSS) functionality, and the PCF can also include a Policy and Charging Rules Function (PCRF). Note that these functional entities are also supported by the 5G CN's SMF 706a and SMF 706b. The AMF 706 can connect to (or communicate with) the SMF 706a. Furthermore, the gNB 604 can communicate with (or connect to) the UPF 708a, which can also communicate with the SMF 706a. Similarly, the N3IWF 702 can communicate with the UPF 708b, which can also communicate with the SMF 706b. Both UPFs can communicate with data networks (e.g., DNs 710a and 710b) and / or the Internet 700 and the IMS core network 710.

[0103] Note that, in various embodiments, one or more of the aforementioned network entities may be configured to perform a method for radio link monitoring for multiple DCI based transmissions, eg, as further described herein.

[0104] Figure 8 An example of a baseband processor architecture for a UE (e.g., UE 106) according to some embodiments is shown. As described above, Figure 8 The baseband processor architecture 800 described in the figure can be implemented on one or more radio components (e.g., radio components 329 and / or 330 described above) or modems (e.g., modems 510 and / or 520) as described above. As shown, the non-access layer 810 may include a 5G NAS 820 and a traditional NAS 850. The traditional NAS 850 may include a communication connection with a traditional access layer (AS) 870. The 5G NAS 820 may include a communication connection with a 5G AS 840 and a non-3GPP AS 830, as well as a Wi-Fi AS 832. The 5G NAS 820 may include functional entities associated with the two access layers. Therefore, the 5G NAS 820 may include multiple 5G MM entities 826 and 828 and 5G session management (SM) entities 822 and 824. The traditional NAS 850 may include functional entities such as a short message service (SMS) entity 852, an evolved packet system (EPS) session management (ESM) entity 854, a session management (SM) entity 856, an EPS mobility management (EMM) entity 858, and a mobility management (MM) / GPRS mobility management (GMM) entity 860. In addition, the traditional AS 870 may include functional entities such as an LTE AS 872, a UMTS AS 874, and / or a GSM / GPRS 876.

[0105] Thus, the baseband processor architecture 800 allows for a common 5G-NAS for both 5G cellular and non-cellular (e.g., non-3GPP access). Note that, as shown, 5G MM can maintain separate connection management and registration management state machines for each connection. In addition, a device (e.g., UE 106) can register to a single PLMN (e.g., 5GCN) using both 5G cellular access and non-cellular access. Furthermore, a device can be in a connected state in one access and idle state in another access, or vice versa. Finally, there may be common 5G-MM procedures (e.g., registration, deregistration, identification, authentication, etc.) for both accesses.

[0106] Note that in various embodiments, one or more of the above-mentioned functional entities of the 5G NAS and / or 5G AS may be configured to perform a method for radio link monitoring for multi-DCI based transmission, e.g., as further described herein.

[0107] RLM for multi-DCI based transmission

[0108] In current implementations, a mobile station may monitor radio link conditions (e.g., primary cell (Pcell) monitoring and / or radio link monitoring (RLM)) to help detect and mitigate radio link failure (RLF). For example, in 3GPP Release 15 (Rel-15), a mobile station may monitor the radio link quality of multiple downlink signals (e.g., by monitoring multiple synchronization signal blocks (SSBs) and / or by monitoring channel state information reference signal (CSI-RS) resources). In some implementations, if configured via radio resource control (RRC) signaling, SSB / CSI-RS resources may be quasi-co-located (QCLed) within different control resource sets (CORESETs). Alternatively, CSI-RS resources configured in the transmission configuration indication (TCI) state of a CORESET may be used for RLM. Note that in some implementations, if configured in the TC If multiple CSI-RS resources are configured in the I state, the CSI-RS resources used to indicate quasi co-location (QCL) type D (e.g., spatial reception parameters) may be used for RLM. In some implementations, the number of SSBs may be used to determine the number of downlink signals to be monitored. For example, for 4 SSBs, 2 downlink signals may be monitored, and for 8 SSBs, 4 downlink signals may be monitored. In addition, if the quality of all corresponding SSBs / CSI-RS resources is below a threshold, the mobile station may indicate an out-of-sync condition (or failure) to higher layers. The higher layers may monitor the number of out-of-sync indications and may declare an RLF if the number of out-of-sync indications exceeds a threshold.

[0109] In addition, in 3GPP Release 16 (Rel-16), a wireless station can be configured to be in a multiple downlink control information (multi-DCI) mode, where the physical downlink shared channel (PDSCH) can be scheduled by multiple DCIs from different CORESETs with different TCIs and from different transmission resource patterns (TRPs). In some implementations, a higher layer index can be configured in the CORESET to imply a TRP index. In addition, the maximum number of CORESETs can be increased from 3 to 5. However, with this increase in multiple DCI modes, if the RRC signaling does not explicitly configure the SSD / CSI-RS for RLM, it is unclear how to select the SSB / CSI-RS resources to monitor. For example, when 5 CORESETs are configured and there are 8 SSBs, it is not known which reference signals (e.g., which 4 resource signals should be monitored).

[0110] In addition, in some implementations, such as Rel-15, it may not be possible to configure aperiodic and semi-persistent CSI-RS for RLM. In addition, since the TCI for aperiodic and semi-persistent CSI-RS may be updated too quickly (e.g., via DCI / MAC CE), for periodic CSI-RS, only RRC can be used to update the TCI. In contrast, in some implementations, such as Rel-16, MAC CE can be introduced to update the TCI for periodic CSI-RS. However, since the latency of MAC CE is much smaller than that of RRC, maintaining the RLM process may become a problem (note that similar problems may occur in beam failure detection (BFD)).

[0111] Embodiments described herein provide systems, methods, and mechanisms for a user equipment device (UE), such as UE 106, to perform radio link monitoring for transmissions based on multiple DCIs. In some embodiments, if / when a reference signal (RS) for radio link monitoring (RLM) is not configured via radio resource control (RRC) signaling, e.g., for a multiple DCI mode, the UE may monitor the RS in a TCI state for a CORESET with a higher layer index K for RLM. For example, in some embodiments, K may be predefined. In some embodiments, K may be configured via higher layer signaling, such as RRC signaling.

[0112] In some embodiments, if / when the RS for RLM is not configured by RRC, for example, for a multi-DCI mode, the UE may determine the RS in the TCI state for the CORESET based at least in part on the monitoring periodicity of the search space associated with the CORESET and / or the CORESET ID (e.g., a higher layer index). In some embodiments, if / when multiple search spaces are associated with a CORESET, the search space may be selected based at least in part on one or more of the minimum monitoring periodicity, the maximum monitoring periodicity, the minimum CORESET ID, and / or the maximum CORESET ID. For example, the UE may select the CORESET with the minimum monitoring periodicity, and if / when the monitoring periodicity is the same for two or more selected CORESETs, the UE may select the CORESET with the largest CORESET ID. For another example, the UE may select the CORESET with the largest monitoring periodicity, and if / when the monitoring periodicity is the same for two or more selected CORESETs, the UE may select the CORESET with the smallest CORESET ID. Note that such combinations are exemplary and other combinations are possible.

[0113] In some embodiments, if / when the RS for RLM is not configured by RRC, for example, for multi-DCI mode, the UE may determine the RS in the TCI state of the CORESET based on the monitoring periodicity of the search space associated with the CORESET, the CORESET ID, and the higher layer index configured in the CORESET. In some embodiments, the CORESET with the smallest monitoring periodicity may be selected. In some embodiments, the CORESET with the largest monitoring periodicity may be selected. In some embodiments, the CORESET with the smallest CORESET ID may be selected. In some embodiments, the CORESET with the largest CORESET ID may be selected. For example, the UE may sort (or count) the RSs based on the following priorities: (1) higher layer index in the CORESET, (2) monitoring periodicity of the CORESET, and (3) CORESET ID.

[0114] In some embodiments, such mechanisms for monitoring radio link failures as described herein may also be implemented for beam failure detection. In some embodiments, when more than one RS is configured in the TCI, the RS for the TCI in the CORESET may indicate an RS configured for QCL-type D in the TCI. In some embodiments, a MAC CE may not be used to update the TCI state of the periodic CSI-RS for radio link monitoring. In such embodiments, the MAC CE may be used to update the TCI state of the periodic CSI-RS for other purposes. Additionally, in some embodiments, the MAC CE may not be used to update the TCI state of the periodic CSI-RS for beam failure detection. In some embodiments, after the UE applies the new TCI state indicated by the MAC CE, the counters for RLM (e.g., counter N310 and / or counter N311) may be reset. In some embodiments, counter N310 may be used for desynchronization and counter N311 may be used for synchronization. Additionally, in some embodiments, after the UE applies the new TCI state indicated by the MAC CE, the BFI_counter and / or beamFailureRecoveryTimer may be reset. For example, in some embodiments, a standards document, such as 3GPP TS 38.321, may be updated to describe:

[0115] 1> If the upper layer reconfigures beamFailureDetectionTImer, beamFailureInstanceMaxCount or any reference signal used for beam failure detection, or the TCI status of any reference signal used for beam failure detection:

[0116] 2> Set BFI_COUNTER to 0.

[0117] Figures 9 to 11D Various examples of selecting a CORESET according to some embodiments are shown. For example, Figure 9 As shown, when configured in multi-DCI mode, a UE such as UE 106 may determine which CORESETs to monitor based on a value k of a higher layer index (HLI). In some embodiments, the value of the HLI for monitoring may be predefined (e.g., specified by a standard) and / or configured via higher layer signaling such as RRC signaling. Figure 9 As shown, the value of the HLI for monitoring may be set to 0 (e.g., k=0). Thus, the UE may select a CORESET for monitoring based on the HLI value included in each CORESET. As shown, the UE may select CORESETs 902, 904, and 906 for monitoring based on the corresponding HLI values ​​of these CORESETs being 0, and may not monitor CORESETs 908 and 910 because these CORESETs have an HLI value of 1.

[0118] For example, 10A to 10D As shown, a UE, such as UE 106, when configured in multi-DCI mode, may determine which CORESETs to monitor based on a comparison of monitoring periodicities of search spaces associated with the CORESETs. FIG. 10A to FIG. 10B As shown in FIG, the UE may select a CORESET based on the monitoring periodicity, selecting the CORESET from the minimum (or lowest) monitoring periodicity to the maximum (or highest) monitoring periodicity. FIG. 10A to FIG. 10B As shown, the UE can select CORESET 1002 with a monitoring periodicity of 2 time slots and CORESETs 1004 and 1008 with a monitoring periodicity of 4 time slots. However, since CORESETs 1006 and 1010 have the same monitoring periodicity (8 time slots), the UE can select between CORESETs 1006 and 1010 based on the HLI values ​​of the CORESETs. For example, Figure 10A As shown, the UE may select a CORESET with a higher HLI value, for example, the UE may select CORESET 1010 instead of CORESET 1006 for monitoring. Figure 10B As another example, the UE may select a CORESET with a lower HLI value. For example, the UE may select CORESET 1006 instead of CORESET 1010 for monitoring.

[0119] In addition, if FIG. 10C to FIG. 10DAs shown in FIG, the UE may select a CORESET based on the monitoring periodicity, selecting a CORESET from the maximum (or highest) monitoring periodicity to the minimum (or lowest) monitoring periodicity. FIG. 10C to FIG. 10D As shown, the UE can select CORESETs 1016 and 1020 with a monitoring periodicity of 8 time slots and CORESET 1018 with a monitoring periodicity of 4 time slots. However, since CORESETs 1012 and 1014 have the same monitoring periodicity (2 time slots), the UE can select between CORESETs 1012 and 1014 based on the HLI values ​​of the CORESETs. For example, Figure 10C As shown, the UE may select a CORESET with a higher HLI value, for example, the UE may select CORESET 1014 instead of CORESET 1012 for monitoring. Figure 10D As another example, the UE may select a CORESET with a lower HLI value, for example, the UE may select CORESET 1012 instead of CORESET 1014 for monitoring.

[0120] For example, 11A to 11D As shown, a UE, such as UE 106, when configured in multi-DCI mode, may determine which CORESETs to monitor based on a comparison of the values ​​of the HLIs associated with the CORESETs. Figures 11A to 11B As shown in FIG, the UE can select a CORESET based on the HLI value, and select a CORESET from the minimum (or lowest) HLI value to the maximum (or highest) HLI value. Figures 11A to 11B As shown, the UE may select CORESETs 1102, 1104, and 1106 based on each having an HLI value of 0 compared to CORESETs 1108 and 1110 having an HLI value of 1. Note that since CORESETs 1108 and 1110 have the same HLI value (1), the UE may select between CORESETs 1108 and 1110 based on the monitoring periodicity of the search space associated with the CORESETs. For example, Figure 11A As shown, the UE may select a CORESET with a smaller monitoring periodicity value, for example, the UE may select CORESET 1108 instead of CORESET 1110 for monitoring. Figure 11B As another example, the UE may select a CORESET with a larger monitoring periodicity value. For example, the UE may select CORESET 1110 instead of CORESET 1108 for monitoring.

[0121] In addition, if Figures 11C to 11DAs shown in FIG, the UE can select a CORESET based on the HLI value, and select a CORESET from the maximum (or highest) HLI value to the minimum (or lowest) HLI value. Figures 11C to 11D As shown, the UE may select CORESETs 1116, 1118, and 1120 based on each having an HLI value of 1 compared to CORESETs 1112 and 1114 having an HLI value of 0. Note that since CORESETs 1112 and 1114 have the same HLI value (0), the UE may select between CORESETs 1112 and 1114 based on the monitoring periodicity of the search space associated with the CORESETs. For example, Figure 11C As shown, the UE may select a CORESET with a smaller monitoring periodicity value, for example, the UE may select CORESET 1112 instead of CORESET 1114 for monitoring. Figure 11D As another example, the UE may select a CORESET with a larger monitoring periodicity value. For example, the UE may select CORESET 1114 instead of CORESET 1112 for monitoring.

[0122] Figure 12 A block diagram illustrating an example of a method for performing radio link monitoring for a multi-DCI based transmission according to some embodiments is shown. Figure 12 The method shown in the figure can also be used together with any one of the systems, methods or devices shown in the figure. In various embodiments, some of the method elements shown can be performed concurrently in an order different from the order shown, or can be omitted. Additional method elements can also be performed as needed. As shown in the figure, the method can be operated as follows.

[0123] At 1202, a UE, such as UE 106, may receive a configuration for a multiple downlink control information (DCI) mode of operation from a network node, such as gNB 604, wherein a physical downlink shared channel (PDSCH) may be scheduled by multiple DCIs from multiple control resource sets (CORESETs). In other words, multiple DCIs may schedule PDSCHs from multiple CORESETs. In some embodiments, the number of CORESETs may exceed the number of CORESETs that can be monitored (simultaneously). In other words, there may be more CORESETs (e.g., 5) than the number (e.g., 4) that the UE can monitor simultaneously. In other words, the number of CORESETs may exceed the number of CORESETs that the UE can monitor simultaneously. In some embodiments, the multiple CORESETs may have different transmission control indices (TCIs). In some embodiments, the multiple CORESETs may be from different TRPs.

[0124] At 1204, the UE may determine a set of CORESETs to monitor, for example, based at least in part on attributes associated with the CORESET. In some embodiments, the attributes may include a higher layer index and / or a monitoring periodicity of a search space associated with the CORESET. In some embodiments, the higher layer index may be specified (or defined) by a standard and / or by higher layer signaling, such as radio resource control (RRC) signaling. In such embodiments, the UE may select a CORESET based on the higher layer index.

[0125] In some embodiments, the UE may select a CORESET based on monitoring periodicity from the lowest monitoring periodicity to the highest monitoring periodicity. In such embodiments, when multiple CORESETs have the same monitoring periodicity, the UE may select a CORESET from the multiple CORESETs from the lowest higher layer index to the highest higher layer index. Alternatively, in some embodiments, when multiple CORESETs have the same monitoring periodicity, the UE may select a CORESET from the multiple CORESETs from the highest higher layer index to the lowest higher layer index.

[0126] In some embodiments, the UE may select a CORESET based on monitoring periodicity from the highest monitoring periodicity to the lowest monitoring periodicity. In such embodiments, when multiple CORESETs have the same monitoring periodicity, the UE may select a CORESET from the multiple CORESETs from the lowest higher layer index to the highest higher layer index. Alternatively, in some embodiments, when multiple CORESETs have the same monitoring periodicity, the UE may select a CORESET from the multiple CORESETs from the highest higher layer index to the lowest higher layer index.

[0127] In some embodiments, the UE may select a CORESET based on a higher layer index from the lowest higher layer index to the highest higher layer index. In such embodiments, when multiple CORESETs have the same higher layer index, the UE may select a CORESET from the multiple CORESETs from the lowest monitoring periodicity to the highest monitoring periodicity. Alternatively, in some embodiments, when multiple CORESETs have the same higher layer index, the UE may select a CORESET from the multiple CORESETs from the highest monitoring periodicity to the lowest monitoring periodicity.

[0128] In some embodiments, the UE may select a CORESET based on a higher layer index from the highest higher layer index to the lowest higher layer index. In such embodiments, when multiple CORESETs have the same higher layer index, the UE may select a CORESET from the multiple CORESETs from the lowest monitoring periodicity to the highest monitoring periodicity. Alternatively, in some embodiments, when multiple CORESETs have the same higher layer index, the UE may select a CORESET from the multiple CORESETs from the highest monitoring periodicity to the lowest monitoring periodicity.

[0129] At 1206, the UE may monitor a set of CORESETs for at least one of radio link failure and / or beam failure. In other words, the UE may select a CORESET for both radio link monitoring and beam failure detection. In some embodiments, the UE may receive a medium access control (MAC) control element (CE) from the network node, the MAC CE indicating a new transmission configuration indication (TCI) state for a purpose that does not include radio link monitoring and / or beam failure detection. In such embodiments, the UE may reset one or more counters associated with radio link monitoring and / or beam failure detection. In some embodiments, the N310 counter may be used for out-of-sync failure detection (or indication). In some embodiments, the N311 counter may be used for in-sync failure detection (or indication). In some embodiments, a beam failure indication counter, such as BFI_COUNTER or BFI_counter, may be reset. In some embodiments, a beam failure recovery timer, such as beamFailureRecoveryTimer or rbeamFailureDetectionTimer, may be reset.

[0130] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly stated to users.

[0131] The embodiments of the present disclosure may be implemented in any of a variety of forms. For example, some embodiments may be implemented as computer-implemented methods, computer-readable storage media, or computer systems. Other embodiments may be implemented using one or more custom-designed hardware devices such as ASICs. Other embodiments may be implemented using one or more programmable hardware elements such as FPGAs.

[0132] In some embodiments, a non-transitory computer-readable storage medium may be configured such that it stores program instructions and / or data, wherein the program instructions, if executed by a computer system, cause the computer system to perform a method, such as any one of the method embodiments described herein, or any combination of the method embodiments described herein, or any subset of any of the method embodiments described herein or any combination of such subsets.

[0133] In some embodiments, a device (e.g., UE 106) may be configured to include a processor (or a group of processors) and a memory medium, wherein the memory medium stores program instructions, wherein the processor is configured to read and execute the program instructions from the memory medium, wherein the program instructions are executable to implement any of the various method embodiments described herein (or any combination of the method embodiments described herein, or any subset of any of the method embodiments described herein, or any combination of such subsets). The device may be implemented in any of various forms.

[0134] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to encompass all such variations and modifications.

Claims

1. A user equipment device UE, comprising: at least one antenna; at least one radio component, wherein the at least one radio component is configured to perform cellular communications using at least one radio access technology (RAT); one or more processors coupled to the at least one radio, wherein the one or more processors and the at least one radio are configured to perform voice and / or data communications; The one or more processors are configured to cause the UE to: receiving, from a network node, a configuration for a multiple downlink control information (DCI) mode of operation, wherein a physical downlink shared channel (PDSCH) is scheduled by multiple DCIs from multiple control resource sets (CORESETs), the multiple CORESETs including a higher layer index (HLI) associated with a group of one or more CORESETs; For a particular group of one or more CORESETs associated with the same HLI value, sorting reference signals (RSs) in a transmission configuration indication (TCI) state of the CORESETs in the one or more CORESETs for selection for monitoring based on a monitoring periodicity of a search space associated with the CORESET and a CORESET index ID; as well as The RS with the TCI status of the CORESET is monitored for beam failure detection.

2. The UE according to claim 1, The HLI and the monitoring periodicity are attributes of the one or more CORESETs.

3. The UE according to claim 1, in, The one or more processors are further configured to: The CORESET is selected based on monitoring periodicity from lowest monitoring periodicity to highest monitoring periodicity.

4. The UE according to claim 3, in, When two or more CORESETs have the same monitoring periodicity, the one or more processors are further configured to select a CORESET from the two or more CORESETs from a lowest higher layer index to a highest higher layer index.

5. The UE according to claim 3, in, When two or more CORESETs have the same monitoring periodicity, the one or more processors are further configured to select a CORESET from the two or more CORESETs from a highest higher layer index to a lowest higher layer index.

6. The UE according to claim 1, in, The one or more processors are further configured to: The CORESET is selected based on the monitoring periodicity from the highest monitoring periodicity to the lowest monitoring periodicity.

7. The UE according to claim 6, in, When two or more CORESETs have the same monitoring periodicity, the one or more processors are further configured to select a CORESET from the two or more CORESETs from a lowest higher layer index to a highest higher layer index.

8. The UE according to claim 6, in, When two or more CORESETs have the same monitoring periodicity, the one or more processors are further configured to select a CORESET from the two or more CORESETs from a highest higher layer index to a lowest higher layer index.

9. The UE according to claim 1, The higher layer index is specified by one of standard signaling or higher layer signaling.

10. An apparatus for wireless communication, comprising: Memory; as well as a processing element in communication with the memory, wherein the processing element is configured to: receiving, from a network node, a configuration for a multiple downlink control information (DCI) mode of operation, wherein a physical downlink shared channel (PDSCH) is scheduled by multiple DCIs from multiple control resource sets (CORESETs), the multiple CORESETs including a higher layer index (HLI) associated with a group of one or more CORESETs; For a particular group of one or more CORESETs associated with the same HLI value, sorting reference signals (RSs) in a transmission configuration indication (TCI) state of the CORESETs in the one or more CORESETs for selection for monitoring based on a monitoring periodicity of a search space associated with the CORESET and a CORESET index ID; as well as The RS with the TCI status of the CORESET is monitored for beam failure detection.

11. The device according to claim 10, wherein the processing element is further configured to: receiving a Medium Access Control Element, MAC CE, from the network node, the MAC CE indicating a new Transmission Configuration Indication, TCI, state for a purpose that does not include radio link monitoring and / or beam failure detection; and One or more counters associated with radio link monitoring and / or beam failure detection are reset.

12. The device according to claim 10, The HLI and the monitoring periodicity are attributes of the one or more CORESETs.

13. The device according to claim 10, in, The processing element is further configured to: A CORESET is selected based on higher level indexes from lowest higher level index to highest higher level index.

14. The device according to claim 13, in, When two or more CORESETs have the same higher layer index, the processing element is further configured to select a CORESET from the two or more CORESETs from lowest monitoring periodicity to highest monitoring periodicity.

15. The device according to claim 13, in, When two or more CORESETs have the same higher layer index, the processing element is further configured to select a CORESET from the two or more CORESETs from a highest monitoring periodicity to a lowest monitoring periodicity.

16. A non-transitory computer-readable memory medium storing program instructions, the program instructions being executable by a processing circuit to cause a user equipment device (UE) to: receiving, from a network node, a configuration for a multiple downlink control information (DCI) mode of operation, wherein a physical downlink shared channel (PDSCH) is scheduled by multiple DCIs from multiple control resource sets (CORESETs), the multiple CORESETs including a higher layer index (HLI) associated with a group of one or more CORESETs; For a particular group of one or more CORESETs associated with the same HLI value, sorting reference signals (RSs) in a transmission configuration indication (TCI) state of the CORESETs in the one or more CORESETs for selection for monitoring based on a monitoring periodicity of a search space associated with the CORESET and a CORESET index ID; and The RS with the TCI status of the CORESET is monitored for beam failure detection.

17. The non-transitory computer-readable memory medium of claim 16, The HLI and the monitoring periodicity are attributes of the one or more CORESETs.

18. The non-transitory computer-readable memory medium of claim 16, in, The program instructions are further configured to: A CORESET is selected based on the higher layer index from the highest higher layer index to the lowest higher layer index.

19. The non-transitory computer-readable memory medium of claim 18, in, When two or more CORESETs have the same higher layer index, the program instructions are further configured to select a CORESET from the two or more CORESETs from lowest monitoring periodicity to highest monitoring periodicity.

20. The non-transitory computer-readable memory medium of claim 18, in, When two or more CORESETs have the same higher layer index, the program instructions are further configured to select a CORESET from the two or more CORESETs from a highest monitoring periodicity to a lowest monitoring periodicity.

Images