SUPPORTING HYPERCYCLIC PREFfix Maximum RECEPTION TIME DIFFERENCE FOR

Abstract

Apparatus, systems, and methods for supporting a hyper-cyclic prefix (CP) maximum receive time difference (MRTD) configured for multiple transmit-receive points (mTRP), such as in 5G NR systems and higher versions. The UE may report to a network (e.g., to a base station of the network) that the UE supports an MRTD greater than the CP network settings. The report may be transmitted via at least one of a medium access control (MAC) control element (CE), a physical random access channel (PRACH) resource, or radio resource control (RRC) signaling. The UE may be configured to receive a group-based beam reporting configuration from the network, such as based on support of the UE for MRTD greater than the CP. Further, the UE may be configured to employ beam reporting criteria based on support of the UE for MRTD greater than CP based on the group-based beam reporting configuration.

Description

Technical Field

[0001] This invention relates to wireless communication, and more particularly to apparatus, systems, and methods for supporting maximum receive time difference (MRTD) of supercyclic prefix (CP) for multiple transmit-receive point (mTRP) configurations, such as in cellular systems (e.g., 5G NR systems) and later.

[0002] Related technical descriptions The use of wireless communication systems is growing rapidly. In recent years, wireless devices such as smartphones, wearable devices or accessories, and tablet computers have become increasingly sophisticated. In addition to supporting telephone calls, many mobile devices now offer access to the Internet, email, text messaging, and navigation using the Global Positioning System (GPS), and can operate complex applications that utilize these functions.

[0003] Long Term Evolution (LTE) is currently the technology of choice for most wireless network operators worldwide, providing mobile broadband data and high-speed internet access to their subscriber base. LTE was first proposed in 2004 and first standardized in 2008. Since then, with the exponential growth in the use of wireless communication systems, the demand from wireless network operators to support higher capacity for a higher density of mobile broadband users has also increased. Therefore, research into new radio access technologies began in 2015, and in 2017, the first version of 5G New Radio (5G NR) was standardized.

[0004] 5G-NR (also known as NR for short) offers higher capacity for higher density mobile broadband users compared to LTE, while also supporting ultra-reliable and massive machine-type communication between devices, as well as lower latency and / or lower battery consumption. Furthermore, NR allows for more flexible UE scheduling compared to current LTE. Therefore, ongoing development of 5G-NR is underway to leverage the potentially higher throughput at higher frequencies. Summary of the Invention

[0005] The implementation scheme relates to wireless communication, and more specifically to apparatus, systems, and methods for supporting, for example, the maximum receive time difference (MRTD) of the supercyclic prefix (CP) for multiple transmit-receive point (mTRP) configurations in 5G NR systems and later.

[0006] For example, in some implementations, the UE may be configured to report to the network (e.g., to a base station of the network) that the UE supports MRTDs greater than the CP network setting. The report may be transmitted via at least one of a Media Access Control (MAC) control element (CE), Physical Random Access Channel (PRACH) resources, or Radio Resource Control (RRC) signaling. The UE may be configured to receive from the network a group-based beam reporting configuration, for example, based on the UE's support for MRTDs greater than the CP. Furthermore, the UE may be configured to adopt beam reporting criteria based on the UE's support for MRTDs greater than the CP based on this group-based beam reporting configuration.

[0007] For example, in some implementations, the network (e.g., a base station of the network) may be configured to receive reports from the UE that the UE supports MRTDs greater than the CP network setting. In some instances, the reports may be received via at least one of a Media Access Control (MAC) control element (CE), Physical Random Access Channel (PRACH) resources, or Radio Resource Control (RRC) signaling. Furthermore, the network may be configured to transmit (or send) group-based beamforming configurations to the UE, for example, based on the UE's support for MRTDs greater than the CP.

[0008] The technologies described herein can be implemented in and / or used with a variety of different types of devices, including but not limited to any of the following computing devices: unmanned aerial vehicles (UAVs), unmanned aerial vehicle controllers (UACs), UTM servers, base stations, access points, cellular phones, tablet computers, wearable computing devices, portable media players, and various other computing devices.

[0009] The present invention is intended to provide a brief overview of some of the subjects described in this document. Therefore, it should be understood that the above features are merely illustrative and should not be construed as narrowing the scope or substance of the subjects described herein in any way. Other features, aspects, and advantages of the subjects described herein will become apparent from the following detailed description, drawings, and claims. Attached Figure Description

[0010] A better understanding of the subject matter can be obtained by considering the following detailed description of various embodiments in conjunction with the accompanying drawings, in which: Figure 1A Example wireless communication systems according to some implementation schemes are illustrated.

[0011] Figure 1B Examples of base stations and access points communicating with user equipment (UE) devices according to some implementation schemes are illustrated.

[0012] Figure 2 Example block diagrams of base stations according to some implementation schemes are shown.

[0013] Figure 3 Example block diagrams of servers according to some implementation schemes are shown.

[0014] Figure 4 Example block diagrams of a UE according to some implementation schemes are shown.

[0015] Figure 5 Example block diagrams of cellular communication circuits according to some implementation schemes are shown.

[0016] Figure 6A Examples of 5G network architectures according to some implementation schemes are illustrated, which combine both 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access to 5GCN.

[0017] Figure 6B Examples of 5G network architectures according to some implementation schemes are illustrated, which combine dual 3GPP (e.g., LTE and 5G NR) access to 5GCN and non-3GPP access.

[0018] Figure 7 Examples of baseband processor architectures for UEs according to some implementation schemes are illustrated.

[0019] Figure 8 An example is shown where the UE receives signals from multiple TRPs.

[0020] Figure 9 and Figure 10 A block diagram illustrating an example of a method for wireless communication when MRTD is greater than CP, according to some implementation schemes.

[0021] While the features described herein may be readily modified and substituted in various ways, specific embodiments thereof are shown by way of example in the accompanying drawings and described in detail herein. However, it should be understood that the drawings and their detailed description are not intended to limit one to the specific forms disclosed, but rather to cover all modifications, equivalents, and alternatives falling within the substance and scope of the subject matter as defined by the appended claims. Detailed Implementation

[0022] Acronyms Various acronyms are used throughout this disclosure. Definitions of the most frequently used acronyms that may appear throughout this disclosure are provided below: • 3GPP: Third Generation Partnership Project • UE: User Equipment • RF: Radio Frequency • DL: Downlink • UL: Uplink • LTE: Long Term Evolution • NR: New Radio • 5GS: 5G system • 5GMM: 5GS Mobility Management • 5GC / 5GCN: 5G core network • IE: Information Elements • CE: Control Element • MAC: Media Access Control • SSB: Synchronization Signal Block • CSI: Channel State Information • CSI-RS: Channel State Information Reference Signal • CMR: Channel Measurement Resources • PDCCH: Physical Downlink Control Channel • PDSCH: Physical Downlink Shared Channel • RRC: Radio Resource Control • RRM: Radio Resource Management • CORESET: Control Resource Set • TCI: Send configuration indicator • DCI: Downlink Control Indicator • NPN: Non-Public Network • SNPN: Independent NPN • CAG: Closed Access Group • SON: Self-Organizing Network • MDT: Minimum Drive Testing Terms The following is a glossary of terms used in this disclosure: Memory medium—Any of various types of nontransitory memory devices or storage devices. The term "memory medium" is intended to include mounting media, such as CD-ROMs, floppy disks, or magnetic 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, such as hard disk drives or optical storage devices; registers or other similar types of memory elements, etc. Memory media may also include other types of nontransitory memory or combinations thereof. Furthermore, memory media may reside in a first computer system executing a program, or may reside in a different second computer system connected to the first computer system via a network such as the Internet. In the latter example, 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, which may reside in different locations in different computer systems connected via, for example, a network. Memory media may store program instructions (e.g., embodied in a computer program) that can be executed by one or more processors.

[0023] Carrier medium —Memory media as described above, and physical transmission media, such as buses, networks and / or other physical transmission media for transmitting signals (such as electrical signals, electromagnetic signals or digital signals).

[0024] Programmable hardware element —This includes a variety of hardware devices, which comprise multiple programmable functional 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 functional blocks can range from fine-grained (combinational logic or lookup tables) to coarse-grained (arithmetic logic units or processor cores). Programmable hardware elements can also be referred to as “configurable logic units.”

[0025] Computer system (or computer) - Any of various types of computing or processing systems, including personal computer systems (PCs), mainframe computer systems, workstations, network appliances, internet-connected appliances, personal digital assistants (PDAs), television systems, grid computing systems, or other devices or combinations thereof. Generally, 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.

[0026] User equipment (UE) (or "UE device") —Any type of computer system device that is mobile or portable and performs wireless communication. Examples of UE devices include mobile phones or smartphones (e.g., iPhone).™ Based on Android ™ Telephones), portable gaming devices (e.g., Nintendo DS) ™ PlayStation Portable ™ Gameboy Advance ™ iPhone ™ ), laptops, wearable devices (e.g., smartwatches, smart glasses), PDAs, portable internet devices, music players, data storage devices, other handheld devices, unmanned aerial vehicles (UAVs) (e.g., drones), UAV controllers (UACs), etc. Generally speaking, the term "UE" or "UE device" can be broadly defined to encompass any electronic device, computing device, and / or telecommunications device (or combination of devices) that is easily transportable by the user and capable of wireless communication.

[0027] Base station The term “base station” has the full range of its general meaning and includes at least a wireless communication station that is installed in a fixed location and used for communication as part of a wireless telephone system or radio system.

[0028] Processing element (or processor) – refers to various elements or combinations of elements capable of performing the functions in a device (such as user equipment or cellular network equipment). Processing elements may include, for example: processors 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.

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

[0030] Frequency band– The term “band” has the full range of its general meaning and includes at least a segment of spectrum (e.g., radio frequency spectrum) in which a channel is used or reserved for the same purpose.

[0031] Wi-Fi The term "Wi-Fi" (or WiFi) has the full range of its usual meaning and includes at least wireless communication networks or RATs, which are provided by and through wireless LAN (WLAN) access points to provide connectivity to the Internet. Most modern Wi-Fi networks (or WLAN networks) are based on the IEEE 802.11 standard and are marketed under the name "Wi-Fi". Wi-Fi (WLAN) networks are different from cellular networks.

[0032] 3GPP access —Refers to access technologies specified by 3GPP standards (e.g., radio access technologies). These access technologies include, but are not limited to, GSM / GPRS, LTE, LTE-A, and / or 5G NR. Generally speaking, 3GPP access refers to various types of cellular access technologies.

[0033] Non-3GPP access —This refers to any access not specified by 3GPP standards (e.g., radio access technologies). These accesses include, but are not limited to, WiMAX, CDMA2000, Wi-Fi, WLAN, and / or fixed networks. Non-3GPP access can be divided into two categories, "trusted" and "untrusted": trusted non-3GPP access can interact directly with the Evolved Packet Core (EPC) and / or 5G Core (5GC), while untrusted non-3GPP access interoperates with the EPC / 5GC via network entities such as Evolved Packet Data Gateways and / or 5G NR Gateways. Generally speaking, non-3GPP access refers to various types of non-cellular access technologies.

[0034] Automatically— This refers to the action or operation performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuits, programmable hardware elements, ASICs, etc.) without requiring direct user input to specify or perform the action or operation. Therefore, the term "automatic" contrasts with an action performed or specified manually by the user (where the user provides input to directly perform the action). An automatic process may be initiated by user-provided input, but the subsequent actions performed "automatically" are not specified by the user; that is, they are not performed "manually," where the user specifies each action to be performed. For example, a user filling out a form by selecting each field and providing input to specify information (e.g., by typing information, selecting a checkbox, radio selection, etc.) is considered manually filling out the form, even though the computer system must update the form in response to the user's actions. The form can be automatically filled out by a computer system (e.g., software executed on the computer system) which analyzes the fields of the form and fills it out without any user input specifying answers for the fields. As indicated above, the user may invoke the automatic filling of the form but does not participate in the actual filling of the form (e.g., the user does not manually specify answers for the fields, but they are completed automatically). This manual provides various examples of operations that can be performed automatically in response to actions taken by the user.

[0035] Approximately – refers to a value that is nearly correct or precise. For example, “approximately” could mean a value within 1% to 10% of the precise (or expected) value. However, it should be noted that the actual threshold (or tolerance) can be application-dependent. For example, in some implementations, “approximately” could mean within 0.1% of some specified or expected value, while in various other implementations, the threshold could be, for example, 2%, 3%, 5%, etc., depending on the expectations or requirements of a particular application.

[0036] Concurrently – refers to parallel execution or implementation, in which tasks, processes, or programs are executed in a manner that is at least partially overlapping. For example, concurrency can be achieved using “strong” or strict parallelism, in which tasks are executed in parallel (at least partially) on corresponding computing elements; or using “weak parallelism”, in which tasks are executed in an interleaved manner (e.g., by time multiplexing of execution threads).

[0037] Various components can be described as being "configured" to perform one or more tasks. In this context, "configured" is a broad expression generally meaning "having a structure" that performs one or more tasks during operation. Therefore, a component can be configured to perform a task even when it is not currently performing one (e.g., a set of electrical conductors can be configured to electrically connect one module to another, even when the two modules are not connected). In some contexts, "configured" can be a broad expression generally meaning "having a circuit" that performs one or more tasks during operation. Therefore, a component can be configured to perform a task even when it is not currently powered on. Generally, the circuit forming the structure corresponding to "configured" can include hardware circuitry.

[0038] 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". Statements describing a component as configured to perform one or more tasks are explicitly intended not to invoke the interpretation of 35 USC § 112(f) for that component.

[0039] Figure 1A and Figure 1B : communication system Figure 1A A simplified example wireless communication system according to some implementation schemes is illustrated. It should be noted that... Figure 1A The system described herein is merely one example of a possible system, and the features of this disclosure can be implemented in any of a variety of systems as needed.

[0040] As shown in the figure, an exemplary wireless communication system includes a base station 102A that communicates with one or more wireless devices (such as user equipment 106A, 106B, etc. to 106N) and accessory devices (such as user equipment 107A, 107B) via a transmission medium. Each user equipment may be referred to herein as a "user equipment" (UE). Therefore, user equipment 106 and 107 are referred to as UEs or UE devices.

[0041] Base station (BS) 102A may be a transceiver base station (BTS) or a cell site (“cellular base station”), and may include hardware that enables wireless communication with UEs 106A to 106N and UEs 107A and 107B.

[0042] The communication area (or coverage area) of a base station may be referred to as a "cell". Base station 102A and UE 106 / 107 can be configured to communicate via a transmission medium using any of a variety of Radio Access Technologies (RATs), also known as wireless communication technologies or telecommunications standards, such as GSM, UMTS (associated with air interfaces such as WCDMA or TD-SCDMA), LTE, LTE-Advanced (LTE-A), 5G New Radio (5G NR), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc. Note that if base station 102A is implemented in an LTE environment, its alternative location may be referred to as an "eNodeB" or "eNB". Note that if base station 102A is implemented in a 5G NR context, its alternative location may be referred to as a "gNodeB" or "gNB".

[0043] As shown in the figure, base station 102A can also be configured to communicate with network 100 (e.g., in various possibilities, the core network of a cellular service provider, telecommunications networks such as the Public Switched Telephone Network (PSTN), and / or the Internet). Therefore, base station 102A facilitates communication between user equipments and / or between user equipments and network 100. Specifically, cellular base station 102A can provide UEs 106 / 107 with various telecommunications capabilities such as voice, SMS, and / or data services.

[0044] 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 services to UE 106A-N and similar devices over a geographical area via one or more cellular communication standards.

[0045] Therefore, although base station 102A can act as the "serving cell" for UE 106 / 107 illustrated in Figure 1, each UE 106 / 107 can also be able to receive signals (and possibly within its communication range) from one or more other cells (which may be provided by base stations 102B-102N and / or any other base station), which can be referred to as "neighboring cells". Such cells can also facilitate communication between user equipments and / or between user equipments and network 100. Such cells can include "macro" cells, "micro" cells, "pecimen" cells and / or any other cells of various other granularities providing service area size. For example, base stations 102A-B illustrated in Figure 1 may be macro cells, while base station 102N may be a pico cell. Other configurations are also possible.

[0046] In some implementations, base station 102A may be a next-generation base station, such as a 5G New Radio (5G NR) base station or a “gNB”. In some implementations, the gNB may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, a gNB cell may include one or more transition and receive points (TRPs). Additionally, a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.

[0047] It should be noted that UE 106 / 107 can communicate using multiple wireless communication standards. For example, UE 106 / 107 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.) other than 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.)). If desired, UE 106 / 107 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 broadcasting standards (e.g., ATSC-M / H or DVB-H), and / or any other wireless communication protocol. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0048] It should be noted that accessory devices 107A / 107B may include cellular communication capabilities and therefore can communicate directly with cellular base station 102A via cellular RAT. However, since accessory devices 107A / 107B may be limited in one or more of the following aspects: communication, output power, and / or battery. Therefore, in some instances, accessory devices 107A / 107B may selectively utilize UE 106A / 106B as a proxy for communication purposes with base station 102A and thus with network 100. In other words, accessory devices 107A / 107B may selectively use the cellular communication capabilities of their companion devices (e.g., UE 106A / 106B) for cellular communication. The limitations on the communication capabilities of accessory devices 107A / 107B may be permanent, for example, due to limitations in output power or supported RAT, or temporary, for example, due to various conditions such as current battery status, inability to access the network, or poor reception.

[0049] Figure 1BExamples of user equipment 106 (e.g., one of devices 106A to 106N) and accessory equipment (or user equipment) 107 (e.g., one of devices 107A or 107B) communicating with base station 102 and access point 112, and communicating with each other, are illustrated according to some embodiments. UE 106 / 107 can be devices with cellular and non-cellular communication capabilities (e.g., Bluetooth, Wi-Fi, etc.), such as mobile phones, wearable devices, handheld devices, computers or tablets, or virtually any type of wireless device. Accessory equipment 107 can be a wearable device such as a smartwatch. Accessory equipment 107 can include cellular communication capabilities and is capable of communicating directly with base station 102, as shown. When accessory equipment 107 is configured to communicate directly with the base station, it can be said that the accessory equipment is in "autonomous mode". Furthermore, accessory device 107 may also be able to communicate with another device (e.g., UE 106) (referred to as a proxy device, intermediate device, or companion device) using a short-range communication protocol; for example, according to some embodiments, accessory device 107 may be “paired” with UE 106, which may include establishing a communication channel and / or trusted communication relationship with UE 106. In some cases, accessory device 107 may use the cellular functionality of the proxy device to transmit cellular voice and / or data with base station 102. In other words, accessory device 107 may provide voice and / or data packets intended for base station 102 to UE 106 via a short-range link, and UE 106 may use its cellular functionality to send (or relay) the voice and / or data to the base station on behalf of accessory device 107. Similarly, voice and / or data packets sent by the base station and intended for accessory device 107 may be received by the cellular functionality of UE 106 and then relayed to accessory device via a short-range link. As described above, UE 106 can be a mobile phone, tablet computer, or any other type of handheld device, media player, computer, laptop, or virtually any type of wireless device. It should be noted that when accessory device 107 is configured to communicate indirectly with base station 102 using the cellular functionality of an intermediary or proxy device, the accessory device can be said to be in "relay mode".

[0050] UE 106 / 107 may include a processor configured to execute program instructions stored in memory. UE 106 / 107 may execute any method implementation of the method implementations described herein by executing such stored instructions. Alternatively or additionally, UE 106 / 107 may include programmable hardware elements, such as a field-programmable gate array (FPGA) configured to perform any of the method implementations described herein or any portion thereof.

[0051] UE 106 / 107 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 / Advanced LTE, or 5G NR using a single shared radio component and / or GSM, LTE, Advanced LTE, or 5G NR using a single shared radio component. The shared radio component may be coupled to a single antenna or to multiple antennas (e.g., for MIMO) for performing wireless communication. Generally, the radio component may include any combination of baseband processor, analog 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 component may use the aforementioned hardware to implement one or more receive chains and transmit chains. For example, UE 106 / 107 may share one or more portions of the receive chain and / or transmit chain among various wireless communication technologies such as those discussed above.

[0052] In some implementations, UE 106 / 107 may include separate transmit and / or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol configured to communicate therewith. As another possibility, UE 106 / 107 may include one or more radio components shared among multiple wireless communication protocols, as well as one or more radio components uniquely used by a single wireless communication protocol. For example, UE 106 / 107 may include shared radio components for communication using either LTE or 5G NR (or LTE or 1xRTT, or LTE or GSM), and separate radio components for communication using each of Wi-Fi and Bluetooth. Other configurations are also possible.

[0053] Figure 2 : block diagram of a base station Figure 2 Example block diagrams of base station 102 according to some implementation schemes are shown. It should be noted that... Figure 3 The base station shown is merely one example of a possible base station. As illustrated, base station 102 may include processor 204, which executes program instructions for base station 102. Processor 204 may also be coupled to memory management unit (MMU) 240, which may be configured to receive addresses from processor 204 and translate these addresses into locations in memory (e.g., memory 260 and read-only memory (ROM) 250) or into other circuitry or devices.

[0054] Base station 102 may include at least one network port 270. Network port 270 may be configured to be coupled to a telephone network and provide access to multiple devices, such as UE device 106, as described above in Figure 1 and... Figure 2 Access to the telephone network described in the text.

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

[0056] In some implementations, base station 102 may be a next-generation base station, such as a 5G New Radio (5G NR) base station, or “gNB”. In such implementations, 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 receive points (TRPs). Additionally, UEs capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.

[0057] Base station 102 may include at least one antenna 234, and may include multiple antennas. At least one antenna 234 may be configured to operate as a wireless transceiver and may be further configured to communicate with UE device 106 via radio component 230. Antenna 234 communicates with radio component 230 via communication link 232. Communication link 232 may be a receive link, a transmit link, or both. Radio component 230 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, etc.

[0058] Base station 102 can be configured to perform wireless communication using multiple wireless communication standards. In some instances, base station 102 may include multiple radio components that enable base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, base station 102 may include an LTE radio component for performing communication according to LTE and a 5G NR radio component for performing communication according to 5G NR. In this case, base station 102 may be able to operate as both an LTE base station and a 5G NR base station. As another possibility, base station 102 may include a multimode radio component capable of performing communication according to any 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.).

[0059] As further described herein, BS 102 may include hardware and software components for implementing or supporting specific implementations of the features described herein. The processor 204 of base station 102 may be configured, for example, to implement or support some or all of the methods described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium). Alternatively, processor 204 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array), or as an ASIC (Application-Specific Integrated Circuit), or a combination thereof. Alternatively (or in addition), in conjunction with one or more of other components 230, 232, 234, 240, 250, 260, 270, the processor 204 of BS 102 may be configured to implement or support implementations of some or all of the features described herein.

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

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

[0062] Figure 3 : block diagram of a server Figure 3 Example block diagrams of server 104 according to some implementation schemes are shown. Note that... Figure 3 The server shown is merely one example of a possible server. As illustrated, server 104 may include processor 344 capable of executing program instructions for server 104. Processor 344 may also be coupled to memory management unit (MMU) 374, which may be configured to receive addresses from processor 344 and translate those addresses into locations in memory (e.g., memory 364 and read-only memory (ROM) 354) or into other circuitry or devices.

[0063] Server 104 can be configured to provide access to network functions to multiple devices, such as base station 102, UE device 106 and / or UTM 108, for example, as further described herein.

[0064] In some implementations, server 104 may be part of a radio access network, such as a 5G New Radio (5G NR) access network. In some implementations, server 104 may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network.

[0065] As further described herein, server 104 may include hardware and software components for implementing or supporting the implementation of the features described herein. Processor 344 of server 104 may be configured, for example, to implement or support some or all of the methods described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium). Alternatively, processor 344 may be configured as a programmable hardware element such as a 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 other components 354, 364, and / or 374, processor 344 of server 104 may be configured to implement or support some or all of the features described herein.

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

[0067] Figure 4 : Block diagram of a UE Figure 4 Simplified block diagrams of communication devices 106 / 107 according to some implementation schemes are shown. Note that... Figure 4 The block diagram of the communication device is merely an example of a possible communication device. According to the implementation, communication device 106 / 107 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 computer, notebook computer, or portable computing device), a wearable device, a tablet computer, an unmanned aerial vehicle (UAV), a UAV controller (UAC), and / or a combination of devices, as well as other devices. As shown, communication device 106 / 107 may include a set of components 400 configured to perform core functions. For example, this set of components may be implemented as a system-on-a-chip (SOC), which may include portions for various purposes. Alternatively, this set of components 400 may be implemented as individual components or groups of components for various purposes. This set of components 400 may be (e.g., communicatively; directly or indirectly) coupled to various other circuitry of communication device 106.

[0068] For example, communication devices 106 / 107 may include various types of memory (e.g., including NAND flash memory 410), input / output interfaces such as connector I / F 420 (e.g., for connection to a computer system; docking station; charging station; input devices such as microphone, camera, keyboard; output devices such as speaker; etc.), display 460 (which may be integrated with or external to communication devices 106 / 107), and wireless communication circuitry 430. Wireless communication circuitry 430 may include a cellular modem 434 such as for 5G NR, LTE, GSM, etc., and short-to-mid-range wireless communication logic components 436 (e.g., Bluetooth). ™ (and WLAN circuitry). In some embodiments, communication devices 106 / 107 may include wired communication circuitry (not shown), such as, for example, a network interface card for Ethernet.

[0069] Wireless communication circuitry 430 may be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as antennas 435a, 435b, and 435c (e.g., 435a-435c) as shown. Wireless communication circuitry 430 may include local area network (LAN) logic component 432, cellular modem 434, and / or short-range communication logic component 436. LAN logic component 432 may be used to enable UE device 106 / 107 to perform LAN communications, such as Wi-Fi communications over an 802.11 network, and / or other WLAN communications. Short-range communication logic component 436 may be used to enable UE device 106 / 107 to perform communications according to a short-range RAT, such as Bluetooth or UWB communications. In some scenarios, cellular modem 434 may be a low-power cellular modem capable of performing cellular communications according to one or more cellular communication technologies.

[0070] In some embodiments, as further described below, the cellular modem 434 may include dedicated receive chains for multiple RATs (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radio components) (e.g., a first receive chain for LTE and a second receive chain for 5G NR). Furthermore, in some embodiments, the cellular modem 434 may include a single transmit chain that can be switched between radio components dedicated to a particular RAT. For example, a first radio component may be dedicated to a first RAT, such as LTE, and may communicate with a dedicated receive chain and a transmit chain shared with additional radio components, such as a second radio component that may be dedicated to a second RAT (e.g., 5G NR) and may communicate with a dedicated receive chain and a shared transmit chain.

[0071] The communication devices 106 / 107 may also include one or more user interface elements and / or be configured to be used with one or more user interface elements. The user interface elements may include any of a variety of elements such as a display 460 (which may be a touch screen display), a keyboard (which may be a separate keyboard or may be implemented as part of a touch screen display), a mouse, a microphone and / or a speaker, one or more cameras, one or more buttons, and / or any of a variety of other elements capable of providing information to the user and / or receiving or interpreting user input.

[0072] The communication device 106 / 107 may further include one or more smart cards 445 with SIM (Subscriber Identity Module) functionality, such as one or more UICC (Universal Integrated Circuit Card) cards 445. It should be noted that the term "SIM" or "SIM entity" is intended to include any of various types of SIM implementations or SIM functions, such as one or more UICC cards 445, one or more eUICCs, one or more eSIMs, removable or embedded, etc. In some embodiments, the UE 106 / 107 may include at least two SIMs. Each SIM may execute one or more SIM applications and / or otherwise implement SIM functionality. Thus, each SIM may be a single smart card that can be embedded, for example, soldered to a circuit board in the UE 106 / 107, or each SIM 410 may be implemented as a removable smart card. Therefore, a SIM may be one or more removable smart cards (such as UICC cards, sometimes referred to as "SIM cards"), and / or SIM 410 may be one or more embedded cards (such as embedded UICCs (eUICCs), sometimes referred to as "eSIMs" or "eSIM cards"). In some implementations (such as when the SIM includes an eUICC), one or more SIMs within the SIM can implement embedded SIM (eSIM) functionality; in such implementations, a single SIM within the SIM can execute multiple SIM applications. Each SIM may include components such as a processor and / or memory; instructions for performing SIM / eSIM functionality may be stored in memory and executed by the processor. In some implementations, UE106 / 107 may include, as needed, a combination of removable smart cards and fixed / non-removable smart cards (such as one or more eUICC cards implementing eSIM functionality). For example, UE 106 / 107 may include two embedded SIMs, two removable SIMs, or a combination of one embedded SIM and one removable SIM. Various other SIM configurations are also envisioned.

[0073] As described above, in some implementations, UE 106 / 107 may include two or more SIMs. Including two or more SIMs in UE 106 / 107 allows UE 106 / 107 to support two different phone numbers and allows UE 106 / 107 to communicate on two or more corresponding networks. For example, the first SIM may support a first RAT such as LTE, and the second SIM 410 may support a second RAT such as 5G NR. Other specific implementations and RATs are also possible. In some implementations, when UE 106 / 107 includes two SIMs, UE 106 / 107 may support Dual SIM Dual Standby (DSDA) functionality. DSDA functionality allows UE 106 / 107 to connect to two networks simultaneously (and use two different RATs), or allows maintaining two connections simultaneously on the same or different networks supported by two different SIMs using the same or different RATs. DSDA functionality also allows UE 106 / 107 to receive voice calls or data traffic simultaneously on either phone number. In some implementations, voice calls may be packet-switched communications. In other words, voice calls can be received using LTE-based Voice (VoLTE) and / or NR-based Voice (VoNR) technologies. In some implementations, UE 106 / 107 may support Dual SIM Dual Standby (DSDS) functionality. DSDS allows either of the two SIMs in UE 106 / 107 to standby for voice calls and / or data connections. In DSDS, when a call / data connection is established on one SIM, the other SIM is no longer active. In some implementations, DSDx functionality (DSDA or DSDS functionality) can be implemented using a single SIM (e.g., eUICC) that performs multiple SIM applications for different carriers and / or RATs.

[0074] As shown in the figure, the SOC 400 may include a processor 402 and display circuitry 404. The processor executes program instructions from the communication device 106, and the display circuitry performs graphics processing and provides display signals to the display 460. The processor 402 may also be coupled to a memory management unit (MMU) 440, which may be configured to receive addresses from the processor 402 and translate those addresses into locations in memory (e.g., memory 406, read-only memory (ROM) 450, NAND flash memory 410), and / or coupled to other circuitry or devices (such as display circuitry 404, short-to-mid-range wireless communication circuitry 429, cellular communication circuitry 430, connector I / F 420, and / or display 460). The MMU 440 may be configured to perform memory protection and page table translation or setup. In some embodiments, the MMU 440 may be included as part of the processor 402.

[0075] As noted above, communication device 106 can be configured to communicate using wireless and / or wired communication circuits. Communication device 106 can be configured to perform methods for supporting super CP MRTD configurations for mTRP, as further described herein, for example in 5G NR systems and later versions.

[0076] As described herein, communication devices 106 / 107 may include hardware and software components for implementing the features described above to communicate 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 storage medium), the processor 402 of communication devices 106 / 107 may be configured to implement some or all of the features described herein. Alternatively (or in addition), the processor 402 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Alternatively (or in addition), in conjunction with one or more of other components 400, 404, 406, 410, 420, 429, 430, 440, 445, 450, 460, the processor 402 of communication device 106 may be configured to implement some or all of the features described herein.

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

[0078] Furthermore, as described herein, the cellular communication circuit 430 and the short-to-mid-range wireless communication circuit 429 may each include one or more processing elements. In other words, one or more processing elements may be included in the cellular communication circuit 430, and similarly, one or more processing elements may be included in the short-to-mid-range wireless communication circuit 429. Therefore, the cellular communication circuit 430 may include one or more integrated circuits (ICs) configured to perform the functions of the cellular communication circuit 430. 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 circuit 430. Similarly, the short-to-mid-range wireless communication circuit 429 may include one or more ICs configured to perform the functions of the short-to-mid-range wireless communication circuit 429. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the short-to-mid-range wireless communication circuit 429.

[0079] Figure 5 : block diagram of cellular communication circuit Figure 5 Simplified block diagrams of cellular communication circuits according to some implementation schemes are shown. Note that... Figure 5 The block diagram of the cellular communication circuit is merely one example of a possible cellular communication circuit. According to the implementation, the cellular communication circuit 530 (which may be the cellular modem circuit 434) may be included in a communication device such as the communication device 106 / 107 described above. As mentioned above, among other devices, the communication device 106 / 107 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, a wearable device, and / or a combination of devices.

[0080] Cellular communication circuitry 530 may (e.g., communicatively; directly or indirectly) be coupled to one or more antennas, such as antennas 535a-535c (which may be...). Figure 4 Antennas 435a-435c in the example. In some embodiments, cellular communication circuitry 530 may include dedicated receive chains for various RATs (including and / or coupled to (e.g., communicative ground; directly or indirectly) dedicated processors and / or radio components) (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, as... Figure 5 As shown, the cellular communication circuit 530 may include a modem 510 and a modem 520. The modem 510 may be configured for communication according to a first RAT (e.g., such as LTE or LTE-A), and the modem 520 may be configured for communication according to a second RAT (e.g., such as 5G NR).

[0081] As shown, modem 510 may include one or more processors 512 and memory 516 communicating with processors 512. Modem 510 may communicate with radio frequency (RF) front end 530. RF front end 530 may include circuitry for transmitting and receiving radio signals. For example, RF front end 530 may include receiver circuitry (RX) 532 and transmitter circuitry (TX) 534. In some embodiments, receiver circuitry 532 may communicate with downlink (DL) front end 550, which may include circuitry for receiving radio signals via antenna 535a.

[0082] Similarly, modem 520 may include one or more processors 522 and memory 526 communicating with processor 522. Modem 520 may communicate with RF front end 540. RF front end 540 may include circuitry for transmitting and receiving radio signals. For example, RF front end 540 may include receiving circuitry 542 and transmitting circuitry 544. In some embodiments, receiving circuitry 542 may communicate with DL front end 560, which may include circuitry for receiving radio signals via antenna 535b.

[0083] In some implementations, switch 570 may couple transmitting circuitry 534 to uplink (UL) front-end 572. Additionally, switch 570 may couple transmitting circuitry 544 to UL front-end 572. UL front-end 572 may include circuitry for transmitting radio signals via antenna 535c. Therefore, when cellular communication circuitry 530 receives an instruction to transmit according to a first RAT (e.g., supported by modem 510), switch 570 may be switched to a first state allowing modem 510 to transmit signals according to the first RAT (e.g., via a transmission chain including transmitting circuitry 534 and UL front-end 572). Similarly, when cellular communication circuitry 530 receives an instruction to transmit according to a second RAT (e.g., supported by modem 520), switch 570 may be switched to a second state allowing modem 520 to transmit signals according to the second RAT (e.g., via a transmission chain including transmitting circuitry 544 and UL front-end 572).

[0084] In some implementations, the cellular communication circuit 530 may be configured to perform methods for supporting super CP MRTD configurations for mTRP, as further described herein.

[0085] As described herein, modem 510 may include hardware and software components for implementing the features described above or for UL data used in time-division multiplexing NSANR operation, as well as various other techniques described herein. For example, processor 512 may be configured to implement some or all of the features described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium). Alternatively (or in addition), processor 512 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Alternatively (or in addition), processor 512 may be configured to implement some or all of the features described herein by combining with one or more of other components 530, 532, 534, 550, 570, 572, 535a-535c.

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

[0087] As described herein, modem 520 may include hardware and software components for implementing the aforementioned features of a super CP MRTD configured for mTRP, such as in 5G NR systems and later, as well as various other technologies described herein. For example, processor 522 may be configured to implement some or all of the features described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium). Alternatively (or in addition), processor 522 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Alternatively (or in addition), processor 522 may be configured to implement some or all of the features described herein by combining one or more of other components 540, 542, 544, 550, 570, 572, 535a-535c.

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

[0089] Figure 6A 、 Figure 6B and Figure 7 : 5G core network architecture - Interworking with Wi-Fi In some implementations, access to the 5G core network (CN) can be made via (or through) cellular connections / interfaces (e.g., via 3GPP communication architecture / protocols) and non-cellular connections / interfaces (e.g., non-3GPP access architecture / protocols such as Wi-Fi connections). Figure 6AAn example of a 5G network architecture according to some implementation schemes is illustrated, which combines both 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access to the 5G CN. As shown, a user equipment device (e.g., such as UE 106) can access the 5G CN through both a radio access network (RAN, such as gNB 604, which can be base station 102) and an access point (such as AP 612). AP 612 may include a connection to the Internet 600 and a connection to a non-3GPP interoperability function (N3IWF) 603 network entity. N3IWF may include a connection to the core access and mobility management function (AMF) 605 of the 5G CN. AMF 605 may include an instance of 5G mobility management (5G MM) function associated with UE 106 / 107. In addition, the RAN (e.g., gNB 604) may also have a connection to AMF 605. Therefore, the 5G CN can support unified authentication on both connections and allow simultaneous registration for UE 106 / 107 accessing via both gNB 604 and AP 612. As shown, AMF 605 can communicate with Location Management Function (LMF) 609 via a network interface such as the NL interface. LMF 609 can receive measurement and assistance information from the RAN (e.g., gNB 604) and UE (e.g., UE 106) via AMF 605. LMF 609 can be a server (e.g., server 104) and / or a functional entity performing on a server. Furthermore, based on the measurement and / or assistance information received from the RAN and UE, LMF can determine the UE's location. Furthermore, AMF 605 may include one or more functional entities associated with the 5G CN (e.g., Network Slice Selection Function (NSSF) 620, Short Message Service Function (SMSF) 622, Application Function (AF) 624, Unified Data Management (UDM) 626, Policy Control Function (PCF) 628, and / or Authentication Server Function (AUSF) 630). It should be noted that these functional entities can also be supported by the 5G CN's Session Management Functions (SMF) 606a and SMF 606b. AMF 605 can connect to (or communicate with) SMF 606a. Additionally, gNB 604 can communicate with (or connect to) User Plane Function (UPF) 608a, which can also communicate with SMF 606a. Similarly, N3IWF 603 can communicate with UPF 608b, which can also communicate with SMF 606b. Both UPFs can communicate with data networks (e.g., DN610a and 610b) and / or the Internet 600 and the Internet Protocol (IP) Multimedia Subsystem / IP Multimedia Core Network Subsystem (IMS) Core Network 610.

[0090] Figure 6B An example of a 5G network architecture according to some implementation schemes is illustrated, which combines both dual 3GPP (e.g., LTE and 5G NR) and non-3GPP access to the 5GCN. As shown, user equipment (e.g., such as UE106) can access the 5G CN through both a radio access network (RAN, such as gNB 604 or eNB 602, which can be base station 102) and an access point (such as AP 612). AP 612 may include a connection to the Internet 600 and a connection to the N3IWF 603 network entity. N3IWF may include a connection to the AMF 605 of the 5G CN. AMF 605 may include an instance of 5G MM functionality associated with UE 106 / 107. Furthermore, the RAN (e.g., gNB 604) may also have a connection to AMF 605. Therefore, the 5G CN can support unified authentication on both connections and allow simultaneous registration for UE 106 / 107 access via both gNB 604 and AP 612. Furthermore, the 5G CN can support dual registration for UEs on both legacy networks (e.g., LTE via eNB 602) and 5G networks (e.g., via gNB 604). As shown, eNB 602 can have connections to Mobility Management Entity (MME) 642 and Serving Gateway (SGW) 644. MME 642 can have connections to both SGW 644 and AMF 605. Additionally, SGW 644 can have connections to both SMF 606a and UPF 608a. As shown in the figure, AMF 605 can communicate with LMF 609 via a network interface (such as NL) as described above and may include one or more functional entities associated with the 5G CN (e.g., NSSF 620, SMSF 622, AF 624, UDM 626, PCF 628, and / or AUSF 630). It should be noted that UDM 626 may also include Home Subscriber Server (HSS) functionality, and PCF may also include Policy and Charging Rules (PCRF) functionality. It should also be noted that these functional entities may also be supported by SMF 606a and SMF 606b of the 5G CN. AMF 606 can connect to (or communicate with) SMF 606a. Furthermore, gNB 604 can communicate with (or connect to) UPF 608a, which can also communicate with SMF 606a. Similarly, N3IWF 603 can communicate with UPF 608b, which in turn can communicate with SMF 606b. Both UPFs can communicate with data networks (e.g., DN 610a and 610b) and / or the Internet 600 and IMS core network 610.

[0091] It should be noted that, in various implementations, one or more of the network entities described above may be configured to perform methods for supporting, for example, super CP MRTD configuration for mTRP in 5G NR systems and later versions, as further described herein.

[0092] Figure 7 Examples of baseband processor architectures for UEs (e.g., such as UE 106) according to some implementation schemes are illustrated. Figure 7 The baseband processor architecture 700 described herein can be implemented on one or more radio components (e.g., radio components 429 and / or 430) or modems (e.g., modems 510 and / or 520) as described above. As shown, the non-access stratum (NAS) 710 may include a 5G NAS 720 and a traditional NAS 750. The traditional NAS 750 may include a communication connection with a traditional access stratum (AS) 770. The 5G NAS 720 may include communication connections with a 5G AS 740, a non-3GPP AS 730, and a Wi-Fi AS 732. The 5G NAS 720 may include functional entities associated with both access strata. Therefore, the 5G NAS 720 may include multiple 5G MM entities 726 and 728 and 5G session management (SM) entities 722 and 724. The traditional NAS 750 may include functional entities such as Short Message Service (SMS) entity 752, Evolved Packet System (EPS) Session Management (ESM) entity 754, Session Management (SM) entity 756, EPS Mobility Management (EMM) entity 758, and Mobility Management (MM) / GPRS Mobility Management (GMM) entity 760. Furthermore, the traditional AS 770 may include functional entities such as LTE AS 772, UMTS AS 774, and / or GSM / GPRS AS 776.

[0093] Therefore, the baseband processor architecture 700 allows for a common 5G-NAS for both 5G cellular and non-cellular (e.g., non-3GPP access) networks. It's important to note that, as shown in the figure, the 5G MM can maintain separate connection management and registration management state machines for each connection. Furthermore, a device (e.g., UE 106) can register to a single PLMN (e.g., a 5G CN) using both 5G cellular and non-cellular access. Additionally, a device can be connected in one access and idle in another, or vice versa. Finally, for both accesses, there may be common 5G-MM procedures (e.g., registration, deregistration, identification, authentication, etc.).

[0094] It should be noted that, in various implementations, one or more of the aforementioned functional entities of the 5G NAS and / or 5G AS may be configured to perform methods for supporting, for example, super CP MRTD configuration for mTRP in 5G NR systems and later versions, as further described herein.

[0095] Supporting hyper-CP MRTD for mTRP configurations 3GPP Release 18 work item regarding requirements for downlink reception of multiple receiver chains in the new radio (NR) frequency range 2 (FR2) has the objective of introducing necessary requirements for enhanced FR2-1 (e.g., 24.25 GHz to 52.6 GHz) user equipment equipment to perform simultaneous DL reception from different directions on a single component carrier with different QCL Type D reference signals. Enhanced radio resource management (RRM) requirements to be studied and / or specified include Layer 1 (L1) reference signal received power (RSRP) measurement delay, Layer 3 (L3) measurement delay (e.g., both cell detection delay and measurement period may be considered), radio link management (RLM) and beam fault detection (BFD) / candidate beam detection (CBD) requirements, scheduling and / or measurement constraints, transmit configuration indication (TCI) state switching delay with dual TCI, and / or reception timing difference between different directions (different QCL Type D RS).

[0096] On this point, it has been agreed to define RRM requirements for the maximum receive time difference (MRTD) less than the cyclic prefix (CP). It should be noted that MRTD is defined as the maximum receive time difference between signals from two directions on the same carrier, for example, as... Figure 8 As illustrated. It should be further noted that for a single downlink control information (DCI), all supported modes (e.g., SDM / FDM / SFM) are based on the assumption that the MRTD is less than the CP. Furthermore, for multiple DCIs (mDCI), the assumption remains that the MRTD is less than the CP. However, to support MRTDs greater than the CP, the UE may require separate timing tracking loops and FFT operations. Therefore, improvements are desired.

[0097] The implementation described herein provides systems, methods, and mechanisms for supporting super-CP MRTDs for mTRP configurations, including systems, methods, and mechanisms for indicating network indications that support MRTDs greater than CP in mTRP configurations, enhanced group-based beam reporting mechanisms, enhanced quasi-co-location (QCL) attributes, and parameter sets for dynamic adaptation.

[0098] For example, in some instances, the network (e.g., a base station such as base station 102) may notify (e.g., indicate) a UE (such as UE 106) via Radio Resource Control (RRC) signaling (e.g., cell-wide, such as via System Information Block (SIB), or UE-specific), Media Access Control (MAC) control element (CE), or via physical layer signaling such as DCI, that for an mTRP configuration (or scenario), the UE needs to operate in an MRTD greater than the CP setting. In some instances, the UE may report its ability to support an MRTD greater than the CP network setting by indicating either the capability to support an MRTD greater than the CP for both sDCI and mDCI, or by indicating a separate capability to support an MRTD greater than the CP for either sDCI or mDCI. Furthermore, the network may configure enhanced group-based beam reporting, including Interference Measurement Resources (IMR), to UEs that support MRTDs greater than the CP setting. In some instances, because the network indicates an MRTD greater than the CP setting, the UE may assume that it needs to follow enhanced group-based beam reporting.

[0099] For example, in some instances, a UE (such as UE 106) may report to the network (e.g., to base station 102) its ability to support a network-configured MRTD greater than CP for both sDCI and mDCI, either by indicating the ability to support a MRTD greater than CP for either sDCI or mDCI. Furthermore, the network may configure enhanced group-based beam reporting, including interference measurement resources (IMR), for UEs supporting MRTDs greater than CP. Additionally, the network may explicitly instruct the UE to comply with enhanced group-based beam reporting as part of the enhanced group-based beam reporting configuration.

[0100] For example, once a UE (such as UE 106) knows that it needs to comply with enhanced group-based beamreporting, the UE can adopt beamreporting criteria, which can be specified by the network (e.g., specified by 3GPP technical specifications and / or signaled to the UE by the network). For example, the UE can adopt beamreporting criteria such as those based on signal-to-interference-plus-noise ratio (SINR), where the minimum SINR of the first beam (B1) and the SINR of the second beam (B2) must be greater than or equal to a SINR threshold, as shown in Equation 1 below. Alternatively, the UE can adopt beamreporting criteria based on SINR and RSRP, where the minimum RSRP of the first beam (B1) and the RSRP of the second beam (B2) must be greater than an RSRP threshold, and the minimum SINR of the first beam (B1) and the SINR of the second beam (B2) must be greater than or equal to a SINR threshold, as shown in Equation 2 below.

[0101] [1] [2] In some instances, the SINR threshold may be predefined as a single value. In other instances, the SINR threshold may be defined as a range of values. The range of values ​​may be signaled to the UE by the network when configuring group-based beam reporting, and / or may be reported to the network by the UE as part of its capabilities. Similarly, in some instances, the RSRP threshold may be predefined as a single value and / or may be defined as a range of values. The range of values ​​may be signaled to the UE by the network when configuring group-based beam reporting, and / or may be reported to the network by the UE as part of its capabilities. In some instances, to support Layer 4 downlink MIMO for sDCI, the network may signal a specific SINR threshold.

[0102] In some instances, QCL attributes can be introduced and / or specified to handle different downlink receive timing references. In some instances, a QCL attribute may be referred to as "DL Rx Timing" and may indicate that the source and target signals share the same downlink receive timing. This type of QCL attribute can be added to other QCL attributes, including Doppler shift, Doppler spread, average delay, delay spread, and spatial Rx parameters. Note that the originating QCL source can be defined as the QCL source at the beginning of the chain of QCL configurations. In some instances, the originating QCL source of the "DL Rx Timing" QCL attribute may be only a Synchronization Block (SSB) or a Tracking Reference Signal (TRS), such as one or both of the NZP-CSI-RS resources in the Non-Zero Power Channel State Information Reference Signal (NZP-CSI-RS) resource set configured using the parameter "trs-Info" set to "True".

[0103] In some instances, QCL attributes associated with different downlink receive timing references (e.g., "DLRx timing") may be included in QCL Type E. It should be noted that current types include QCL Type A (which includes Doppler shift, Doppler spread, average delay, and delay spread), QCL Type B (which includes Doppler shift and Doppler spread), QCL Type C (which includes Doppler shift and average delay), and QCL Type D (which includes spatial Rx parameters). In some instances, QCL Type E may include QCL attributes associated with different downlink receive timing references (e.g., "DL Rx timing"). In some instances, QCL Type E may include QCL attributes associated with different downlink receive timing references (e.g., "DLRx timing"), and one or more other QCL attributes (e.g., one or more of Doppler shift, Doppler spread, average delay, and / or delay spread).

[0104] In some instances, QCL attributes associated with different downlink receive timing references (e.g., such as "DLRx timing") may be included in QCL Type A. Therefore, QCL Type A may be enhanced to include QCL attributes associated with different downlink receive timing references (e.g., such as "DL Rx timing").

[0105] In some instances, when QCL attributes associated with different downlink receive timing references (e.g., "DLRx timing") are included in the QCL type, an additional QCL source may be included in the TCI state configuration. Note that the current TCI state configuration may have up to two QCL sources. The first QCL source needs to be configured and can be one of QCL Type A, QCL Type B, or QCL Type C. The second QCL source is optional and is used for QCL Type D, such as the spatial Rx parameter. In some instances, an additional or third QCL source may be optional (e.g., it may or may not be configured). An additional or third QCL source can be used for QCL attributes associated with different downlink receive timing references (e.g., "DL Rx timing").

[0106] In some instances, when QCL attributes associated with different downlink receive timing references (e.g., "DLRx timing") are included in the QCL type, the QCL attributes can be included in the existing QCL source configuration included in the TCI state configuration. For example, a first QCL source or a second QCL source may include QCL attributes.

[0107] In some instances, a UE (such as UE 106) can dynamically report whether it has observed an MRTD greater than CP. In some instances, dynamic reporting can be based on MAC CE, physical random access channel (PRACH), and / or RRC. In some instances, when dynamic reporting is based on MAC CE and the UE has uplink (UL) grants, the UE can use the UL grant to transmit the corresponding MAC-CE, including the dynamic report, on the physical uplink shared channel (PUSCH). In some instances, when dynamic reporting is based on MAC CE and the UE does not have UL grants, the UE can transmit a scheduling request (SR) requesting UL grants to transmit the dynamic report. In some instances, when dynamic reporting is based on PRACH, PRACH resources can be divided into a first group for MRTDs less than or equal to CP and a second group for MRTDs greater than CP. In such instances, the UE can use the second group of PRACH resources to transmit the dynamic report. Furthermore, QCP attributes can be introduced to handle different downlink receive timing references. In some instances, when dynamic granting is based on RRC, the UE can transmit dynamic reports as part of UE Assistance Information (UAI). It should be noted that in some instances, the UE may only be allowed to trigger / send dynamic reports under specific conditions. For example, the first condition could be whether the measured Rx reception timing difference is greater than a threshold. The threshold can be configured by the network or fixed to a value, such as a CP. Alternatively, the second condition could be based on a counter; for example, the UE could trigger / send a dynamic report only after observing a specified number of consecutive measurements that satisfy the first condition.

[0108] In some instances, the network (e.g., base station 102) can dynamically change the CP (Orthogonal Frequency Division Multiplexing) parameter set, including subcarrier spacing (SCS), extended CP, and / or regular CP. In some instances, dynamic changes can be signaled via MAC CE or based on DCI (e.g., as part of DCI 1_1, DCI 1_2, and / or DCI 1_3). It should be noted that a smaller SCS has a longer duration CP compared to a larger SCS. Further note that, given the same SCS, an extended CP has a longer duration CP but fewer symbols per timeslot. In some instances, various constraints can be considered for the CP OFDM parameter set. For example, a scheduled Physical Downlink Shared Channel (PDSCH) may not be expected to have different Rx receive timings exceeding the CP. Also, a scheduled PDSCH may not be expected to operate in sDCI / mDCI where the MRTD is greater than the CP. It should be noted that scheduling constraints can be applied to PDSCHs scheduled by the Common Search Space (CSS) and / or PDSCHs scheduled by the Downlink Backoff DCI (e.g., such as DCI Format 1_0).

[0109] Figure 9 and Figure 10 A block diagram illustrating an example of a method for wireless communication when MRTD is greater than CP, according to some implementation schemes. Among other devices, Figure 9 and Figure 10 The methods shown can also be used in conjunction with any of the systems, methods, or devices shown in the figures. In various embodiments, some of the method elements shown may be executed concurrently in a different order than shown, or may be omitted. Additional method elements may also be executed as needed.

[0110] Go to Figure 9 As shown in the figure, this method can be operated as follows.

[0111] At 902, the UE (such as UE 106) may report to the network (e.g., to a base station of the network, such as base station 102) that the UE supports a maximum receive time difference (MRTD) greater than the cyclic prefix (CP) network setting. In some instances, in order to report to the network that the UE supports an MRTD greater than the CP network setting, the UE may report to the network via at least one of a Media Access Control (MAC) control element (CE), a Physical Random Access Channel (PRACH) resource, or a Radio Resource Control (RRC) signaling.

[0112] In some instances, for MAC CE-based reporting, the UE can determine whether it has an uplink grant, and in response to determining that it has an uplink grant, use the uplink grant to transmit the report via MAC CE on the Physical Uplink Shared Channel (PUSCH). Furthermore, in response to determining that it does not have an uplink grant, the UE can transmit a scheduling request (SR) requesting an uplink grant to the network, and use the requested uplink grant to transmit the report via MAC CE on the PUSCH.

[0113] In some instances, for reports based on PRACH resources, PRACH resources can be divided into a first group for MRTDs less than or equal to CP and a second group for MRTDs greater than CP, and the UE can transmit reports via PRACH resources associated with the second group.

[0114] In some instances, for RRC-based reports, the UE can transmit the report as part of UE Assistance Information (UAI).

[0115] In some instances, the UE can determine that the measured reception timing difference is greater than a threshold, and a report can be triggered based on this determination. The threshold can be configured by the network or associated with a value such as CP.

[0116] In some instances, the UE can determine that the received timing difference of a measurement is greater than a threshold of a specified number of consecutive measurements, and a report can be triggered based on this determination. The threshold can be configured by the network or associated with a value such as CP. Furthermore, the specified number can be indicated by the network.

[0117] In some instances, to report to the network that the UE supports an MRTD greater than the CP network setting, the UE can report to the network via UE capabilities that it supports an MRTD greater than the CP network setting for both single downlink control information (sDCI) and multiple DCI (mDCI). In some instances, to report to the network that the UE supports an MRTD greater than the CP network setting, the UE can report to the network via a first UE capability associated with the sDCI and a second UE capability associated with the mDCI.

[0118] At 904, the UE can receive group-based beam reporting configuration from the network. The group-based beam reporting configuration may be based on the UE's support for MRTDs greater than the CP setting. In some instances, the group-based beam reporting configuration may include interference measurement resources (IMR). In some instances, such as when the network does not indicate an MRTD greater than the CP setting to the UE, the group-based beam reporting configuration may include an indication that the UE needs to follow a group-based beam reporting configuration based on the UE's support for MRTDs greater than the CP setting.

[0119] At 906, the UE can adopt a beam reporting criterion based on the UE's support for MRTD greater than CP, based on the group-based beam reporting configuration.

[0120] In some instances, beam reporting criteria may be based at least in part on a first signal-to-interference-plus-noise ratio (SINR) of a first reference signal received on a first beam and a second SINR of a second reference signal received on a second beam. Furthermore, beam reporting criteria may include a minimum value of the first SINR and the second SINR being greater than or equal to a SINR threshold. The SINR threshold may be specified via a standard or signaled to the UE by the network. Additionally, the SINR threshold may be predefined as a single value or a range of predefined values. In some instances, the UE may receive a range of SINR threshold values ​​from the network based on the range of SINR threshold values ​​configured for group-based beam reporting. In some instances, the UE may report a range of SINR threshold values ​​to the network as a UE capability. In some instances, the UE may perform beam reporting when the minimum value of the first SINR and the second SINR is greater than or equal to the SINR threshold.

[0121] In some instances, beam reporting criteria may be based at least in part on a first SINR of a first reference signal received on a first beam and a second SINR of a second reference signal received on a second beam, as well as the first reference signal received power (RSRP) of the first reference signal received on the first beam and the second RSRP of the second reference signal received on the second beam. Furthermore, beam reporting criteria may include a minimum of the first and second SINR values ​​being greater than or equal to a SINR threshold, and a minimum of the first and second RSRP values ​​being greater than an RSRP threshold. The SINR and RSRP thresholds may be specified via a standard or signaled to the UE by the network. In some instances, the SINR threshold may be predefined as a first value, and the RSRP threshold may be predefined as a second value. In some instances, the SINR threshold may be predefined as a first range of values, and the RSRP threshold may be predefined as a second range of values. In some instances, the UE may receive the first range of SINR threshold values ​​and the second range of RSRP threshold values ​​from the network based on the UE being configured for group-based beam reporting. In some instances, the UE may report the first range of SINR threshold values ​​and the second range of RSRP threshold values ​​to the network as a UE capability. In some instances, the UE can perform beam reporting when the minimum of the first SINR and the second SINR is greater than or equal to the SINR threshold and the minimum of the first RSRP and the second RSRP is greater than the RSRP threshold.

[0122] In some instances, the UE can receive a specific SINR threshold from the network to support Layer 4 downlink multiple-input multiple-output for single downlink control information (sDCI) communication.

[0123] In some instances, the UE may receive from the network an indication that the source and target signals share the same downlink receive timing quasi-co-location (QCL) attribute. The QCL attribute may be included in QCL Type A and / or QCL Type E. In some instances, QCL Type E may include only the QCL attribute. In other instances, QCL Type E may also include one or more additional QCL attributes. In such instances, one or more additional QCL attributes may include at least one of Doppler shift, Doppler spread, average delay, delay spread, and / or DL ​​Rx timing. In some instances, the origin QCL source of the QCL attribute may be a synchronization signal block (SSB) or at least one of the NZP-CSI-RS resources in a non-zero power channel state information reference signal (NZP-CSI-RS) resource set configured using the parameter trs-Info set to "true". In some instances, the QCL attribute may be a DLRx timing QCL attribute.

[0124] In some instances, QCL attributes can be indicated as QCL information parameters via the qcl-Type3 field in the Transmit Control Information (TCI) status configuration. The qcl-Type3 field can be an optional field in the TCI status configuration. In other instances, QCL attributes can be indicated as QCL information parameters via either the qcl-Type1 field or the qcl-Type2 field in the TCI status configuration.

[0125] In some instances, the UE may receive changes to the CP (Orthogonal Frequency Division Multiplexing) parameter set from the network. These changes may include alterations to one or more of the subcarrier spacing (SCS), extended CP, and / or conventional CP. The changes may be received via either MACCE or DCI. The DCI may be in DCI 1_1 format, DCI 1_2 format, or DCI 1_3 format.

[0126] In some instances, the UE may receive from the network an instruction that the UE needs to operate within an MRTD greater than the CP setting. In such instances, this instruction may be received via at least one of RRC signaling, MAC CE, or physical layer signaling. RRC signaling may be received via either UE-specific signaling or System Information Block (SIB). Physical layer signaling may be received via DCI.

[0127] Go to Figure 10 As shown in the figure, this method can be operated as follows.

[0128] At 1002, the network (e.g., a base station of the network, such as base station 102) may receive a report from the UE (such as UE 106) that the UE supports a maximum receive time difference (MRTD) greater than the cyclic prefix (CP) network setting. In some instances, the report may be received via at least one of a Media Access Control (MAC) control element (CE), a Physical Random Access Channel (PRACH) resource, or a Radio Resource Control (RRC) signaling.

[0129] In some instances, for MAC CE-based reporting, when the UE has an uplink grant, the network can use that uplink grant to receive the report via MAC CE on the Physical Uplink Shared Channel (PUSCH). Furthermore, when the UE does not have an uplink grant, the network can receive a scheduling request (SR) requesting an uplink grant, and then use the requested uplink grant to receive the report via MAC CE on the PUSCH.

[0130] In some instances, for reports based on PRACH resources, PRACH resources can be divided into a first group for MRTDs less than or equal to CP and a second group for MRTDs greater than CP, and the network can receive reports via PRACH resources associated with the second group.

[0131] In some instances, for RRC-based reports, the network can receive the report as part of UE Assistance Information (UAI).

[0132] In some instances, a report may be triggered based on the UE determining that the measured reception timing difference is greater than a threshold. The threshold may be configured by the network or associated with a value such as CP.

[0133] In some instances, a report may be triggered based on the UE determining that the received timing difference of a measurement exceeds a threshold of a specified number of consecutive measurements. The threshold may be configured by the network or associated with a value such as CP. Furthermore, the specified number may be indicated by the network.

[0134] In some instances, the report can indicate UE support for MRTDs greater than the CP network configuration via UE capabilities for both single downlink control information (sDCI) and multiple DCIs (mDCI). In some instances, the report can indicate UE support for MRTDs greater than the CP network configuration via a first UE capability associated with sDCI and a second UE capability associated with mDCI.

[0135] At point 1004, the network may transmit (or send) group-based beam reporting configuration to the UE. The group-based beam reporting configuration may be based on the UE's support for MRTDs greater than the CP setting. In some instances, the group-based beam reporting configuration may include interference measurement resources (IMR). In some instances, such as when the network does not indicate to the UE an MRTD greater than the CP setting, the group-based beam reporting configuration may include an indication that the UE needs to follow a group-based beam reporting configuration based on the UE's support for MRTDs greater than the CP.

[0136] In some instances, the UE can adopt beam reporting criteria based on the UE's support for MRTDs greater than CP, based on the group-based beam reporting configuration.

[0137] In some instances, beam reporting criteria may be based at least in part on a first signal-to-interference-plus-noise ratio (SINR) of a first reference signal received on a first beam and a second SINR of a second reference signal received on a second beam. Furthermore, beam reporting criteria may include a minimum of the first and second SINR values ​​being greater than or equal to a SINR threshold. The SINR threshold may be specified via a standard or signaled to the UE by the network. Additionally, the SINR threshold may be predefined as a single value or a range of predefined values. In some instances, the network may transmit (or send) a range of SINR threshold values ​​to the UE based on the UE's configuration for group-based beam reporting. In some instances, the network may receive a range of SINR threshold values ​​from the UE as a UE capability. In some instances, beam reporting may be triggered at the UE when the minimum of the first and second SINR values ​​is greater than or equal to the SINR threshold.

[0138] In some instances, beam reporting criteria may be based at least in part on a first SINR of a first reference signal received on a first beam and a second SINR of a second reference signal received on a second beam, as well as the first reference signal received power (RSRP) of the first reference signal received on the first beam and the second RSRP of the second reference signal received on the second beam. Furthermore, beam reporting criteria may include a minimum of the first and second SINR values ​​being greater than or equal to a SINR threshold, and a minimum of the first and second RSRP values ​​being greater than an RSRP threshold. The SINR and RSRP thresholds may be specified via a standard or signaled to the UE by the network. In some instances, the SINR threshold may be predefined as a first value, and the RSRP threshold may be predefined as a second value. In some instances, the SINR threshold may be predefined as a first range of values, and the RSRP threshold may be predefined as a second range of values. In some instances, the network may transmit (or send) a first range of SINR threshold values ​​and a second range of RSRP threshold values ​​to the UE based on the UE being configured for group-based beam reporting. In some instances, the network may receive the first range of SINR threshold values ​​and the second range of RSRP threshold values ​​from the UE as UE capabilities. In some instances, beam reporting can be triggered at the UE when the minimum of the first SINR and the second SINR is greater than or equal to the SINR threshold and the minimum of the first RSRP and the second RSRP is greater than the RSRP threshold.

[0139] In some instances, the network may transmit (or send) specific SINR thresholds to the UE to support Layer 4 downlink multiple-input multiple-output for single downlink control information (sDCI) communication.

[0140] In some instances, the network may transmit (or send) a quasi-co-location (QCL) attribute to the UE indicating that the source and target signals share the same downlink receive timing. The QCL attribute may be included in QCL Type A and / or QCL Type E. In some instances, QCL Type E may include only the QCL attribute. In other instances, QCL Type E may also include one or more additional QCL attributes. In such instances, one or more additional QCL attributes may include at least one of Doppler shift, Doppler spread, average delay, delay spread, and / or DL ​​Rx timing. In some instances, the origin QCL source of the QCL attribute may be a synchronization signal block (SSB) or at least one of the NZP-CSI-RS resources in a non-zero power channel state information reference signal (NZP-CSI-RS) resource set configured using the parameter trs-Info set to "true". In some instances, the QCL attribute may be a DL Rx timing QCL attribute.

[0141] In some instances, QCL attributes can be indicated as QCL information parameters via the qcl-Type3 field in the Transmit Control Information (TCI) status configuration. The qcl-Type3 field can be an optional field in the TCI status configuration. In other instances, QCL attributes can be indicated as QCL information parameters via either the qcl-Type1 field or the qcl-Type2 field in the TCI status configuration.

[0142] In some instances, the network may transmit (or send) changes to the CP (Orthogonal Frequency Division Multiplexing) parameter set to the UE. These changes may include alterations to one or more of the subcarrier spacing (SCS), extended CP, and / or conventional CP. The changes may be received via either the MAC CE or the DCI. The DCI may be in DCI 1_1 format, DCI 1_2 format, or DCI 1_3 format.

[0143] In some instances, the network may transmit (or send) an instruction to the UE that the UE needs to operate within an MRTD greater than the CP setting. In such instances, this instruction may be received via at least one of RRC signaling, MAC CE, or physical layer signaling. RRC signaling may be received via one of UE-specific signaling or System Information Block (SIB). Physical layer signaling may be received via DCI.

[0144] Embodiments of this disclosure can be implemented in any of a variety of forms. For example, some embodiments can be implemented as a computer-implemented method, a computer-readable storage medium, or a computer system. Other embodiments can be implemented using one or more custom-designed hardware devices such as ASICs. Other embodiments can be implemented using one or more programmable hardware elements such as FPGAs.

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

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

[0147] By interpreting each message / signal X received by the user equipment (UE) in the downlink as a message / signal X sent by the base station, and interpreting each message / signal Y sent by the UE in the uplink as a message / signal Y received by the base station, any of the methods described herein for operating the UE can serve as the basis for a corresponding method for operating the base station.

[0148] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the above disclosure is fully understood. It is intended that the following claims be construed as encompassing all such variations and modifications.

Claims

1. A method for wireless communication, the method comprising: Report to the network that the User Equipment (UE) supports a maximum Receive Time Difference (MRTD) greater than the Cyclic Prefix (CP) network setting. Receive group-based beam report configuration from the network, wherein the group-based beam report configuration is based on the UE's support for MRTD greater than CP; as well as The beam reporting criterion is adopted based on the group-based beam reporting configuration and the UE's support for MRTD greater than CP.

2. The method according to claim 1, The beam reporting criterion is based, at least in part, on a first signal-to-interference-plus-noise ratio (SINR) of a first reference signal received on a first beam and a second SINR of a second reference signal received on a second beam.

3. The method according to claim 2, The criteria mentioned include that the minimum value of the first SINR and the second SINR is greater than or equal to the SINR threshold.

4. The method according to claim 3, The SINR threshold is specified via a standard or signaled to the UE by the network.

5. The method according to claim 3, The SINR threshold is predefined as a single value.

6. The method according to claim 3, The SINR threshold is predefined as a range of values.

7. The method according to claim 6, further comprising: The range of values ​​for the SINR threshold is based on the UE being configured to receive group-based beam reports from the network.

8. The method according to claim 6, further comprising: The range of values ​​for the SINR threshold is reported to the network as a UE capability.

9. The method according to claim 3, further comprising: Beam reporting is performed when the minimum value of the first SINR and the second SINR is greater than or equal to the SINR threshold.

10. The method according to claim 1, The beam reporting criteria mentioned therein are based, at least in part, on: The first signal-to-interference-plus-noise ratio (SINR) of the first reference signal received on the first beam and the second SINR of the second reference signal received on the second beam; and The first reference signal received power (RSRP) of the first reference signal received on the first beam and the second RSRP of the second reference signal received on the second beam.

11. The method according to claim 10, The criteria mentioned include: The minimum value of the first SINR and the second SINR is greater than or equal to the SINR threshold; as well as The minimum of the first RSRP and the second RSRP is greater than the RSRP threshold.

12. The method according to claim 11, The SINR threshold and the RSRP threshold are specified via a standard or signaled to the UE by the network.

13. The method according to claim 11, The SINR threshold is predefined as a first value; and The RSRP threshold is predefined as a second value.

14. The method according to claim 11, The SINR threshold is predefined as a first range of values; and The RSRP threshold is predefined as a second range of values.

15. The method according to claim 14, further comprising: The UE is configured to receive a first range of the SINR threshold value and a second range of the RSRP threshold value from the network based on group-based beam reporting.

16. The method of claim 14, further comprising: The first range of the SINR threshold value and the second range of the RSRP threshold value are reported to the network as UE capabilities.

17. The method according to claim 11, further comprising: Beam reporting is performed when the minimum value of the first SINR and the second SINR is greater than or equal to the SINR threshold and the minimum value of the first RSRP and the second RSRP is greater than the RSRP threshold.

18. The method according to claim 3, further comprising: Receive a specific SINR threshold from the network to support Layer 4 downlink multiple-input multiple-output for single downlink control information (sDCI) communication.

19. The method according to claim 1, further comprising: The source and target signals received from the network share the same quasi-co-address (QCL) attribute for downlink receive timing.

20. The method according to claim 19, The QCL attribute mentioned above is included in QCL TypeA.

21. The method according to claim 19, The QCL attribute mentioned above is included in QCL TypeE.

22. The method according to claim 21, The QCL TypeE mentioned therein also includes one or more additional QCL attributes.

23. The method according to claim 22, The one or more additional QCL attributes mentioned above include at least one of the following: Doppler shift; Doppler extension; Average delay; Delayed expansion; or DL Rx timing.

24. The method according to claim 19, The origin of the QCL attribute is at least one of the following: Synchronization Signal Block (SSB); or The NZP-CSI-RS resources in the Non-Zero Power Channel State Information Reference Signal (NZP-CSI-RS) resource set are configured using the parameter trs-Info, which is set to "True".

25. The method according to claim 19, The QCL attribute mentioned above is the DL Rx timing QCL attribute.

26. The method according to claim 19, The QCL attribute is indicated as a QCL information parameter via the qcl-Type3 field in the Transmit Control Information (TCI) status configuration.

27. The method according to claim 26, The qcl-Type3 field is an optional field in the TCI status configuration.

28. The method according to claim 19, The QCL attribute is indicated as a QCL information parameter via either the qcl-Type1 field or the qcl-Type2 field in the Transmit Control Information (TCI) status configuration.

29. The method according to claim 1, Reporting to the network that the UE supports an MRTD greater than the CP network setting includes reporting to the network that the UE supports an MRTD greater than the CP network setting via at least one of the following: Media Access Control (MAC) Control Element (CE); Physical Random Access Channel (PRACH) resources; Radio Resource Control (RRC) signaling.

30. The method according to claim 29, For reports based on MAC CE, the method further includes: Determine whether the UE has an uplink grant; In response to determining that the UE has an uplink grant, the report is transmitted via MAC CE on the Physical Uplink Shared Channel (PUSCH) using the uplink grant; as well as In response to determining that the UE does not have an uplink grant, Transmit a scheduling request (SR) to the network requesting the uplink to grant a scheduling permission. and Use the requested uplink grant to transmit the report on PUSCH via MAC CE.

31. The method according to claim 29, For reports based on PRACH resources, the PRACH resources are divided into a first group for MRTDs less than or equal to the CP and a second group for MRTDs greater than the CP; and The method further includes: The report is transmitted via the PRACH resource associated with the second group.

32. The method according to claim 29, For RRC-based reports, the method further includes: The report is transmitted as part of UE Assistance Information (UAI).

33. The method of claim 29, further comprising: The UE The timing difference of the received measurement is determined to be greater than a threshold, and the report is triggered based on the determination.

34. The method according to claim 33, The threshold is configured by the network or associated with a value.

35. The method according to claim 34, The value mentioned therein is the CP.

36. The method of claim 29, further comprising: The UE The timing difference of the received measurement is determined to be greater than a threshold of a specified number of consecutive measurements, wherein the report is triggered based on the determination.

37. The method according to claim 36, The threshold is configured by the network or associated with a value.

38. The method according to claim 37, The value mentioned therein is the CP.

39. The method according to claim 36, The specified quantity is indicated by the network.

40. The method according to claim 1, further comprising: The UE Changes are received from the network to the CP orthogonal frequency division multiplexing (OFDM) parameter set, wherein the changes include changes to one or more of the following: Subcarrier spacing (SCS); Extend CP; or Standard CP.

41. The method according to claim 40, The change is received via either a Media Access Control (MAC) control element (CE) or a Downlink Control Information (DCI).

42. The method according to claim 41, The DCI mentioned therein is one of DCI 1_1 format, DCI 1_2 format, or DCI 1_3 format.

43. The method according to claim 1, The reporting to the network that the UE supports an MRTD greater than the CP network setting includes: The UE reports to the network via its capability that it supports the MRTD for single downlink control information (sDCI) and multiple DCI (mDCI) that is greater than the CP network setting.

44. The method according to claim 1, The reporting to the network that the UE supports an MRTD greater than the CP network setting includes: The UE reports to the network via a first UE capability associated with a single downlink control information (sDCI) and a second UE capability associated with multiple DCI (mDCI), that the UE supports the MRTD greater than that set by the CP network.

45. The method according to claim 1, The group-based beam reporting configuration includes an interference measurement resource (IMR).

46. ​​The method according to claim 1, The group-based beam reporting configuration includes an instruction that the UE needs to follow the group-based beam reporting configuration based on the UE's support for MRTDs greater than CP.

47. The method according to claim 1, further comprising: The UE The network receives an instruction from the UE that it needs to operate in the MRTD that is greater than the CP setting.

48. The method according to claim 47, The instruction is received via at least one of the following: Radio Resource Control (RRC) signaling; Media Access Control (MAC) control element (CE); or Physical layer signaling.

49. The method according to claim 48, The RRC signaling is transmitted via either UE-specific signaling or a System Information Block (SIB).

50. The method according to claim 48, The physical layer signaling mentioned above is transmitted via downlink control information (DCI).

51. A user equipment (UE) device, the user equipment (UE) device comprising: At least one antenna; At least one radio component, the at least one radio component communicating with the at least one antenna and configured to communicate according to at least one radio access technology (RAT); and One or more processors, the one or more processors communicating with the at least one radio component and configured to cause the UE to perform the method according to any one of claims 1 to 50.

52. An apparatus comprising: Memory; and At least one processor, the at least one processor communicating with the memory and configured to perform the method according to any one of claims 1 to 50.

53. A non-transitory computer-readable storage medium storing program instructions executable by processing circuitry of a user equipment (UE) to perform the method according to any one of claims 1 to 50.

Images